Language selection guides

I can help do it translate into Russian language. Would it be possible to put on the site for language selection guides?

@whdigger Thanks for offering to help.  We are going to release a new guide with 2.3.  At that point, getting a russian translation would be great.  Thanks!

For translate I need to fork the project, checkout v2.3.0-pre.13, and translate folder guides, and later send pull request
Tell me how to generate the html page via documentjs ./node_modules/.bin/documentjs  which must be the generation of project files?

@whdigger facepalm learn english http://babeleo.com
kiddin`

@whitecolor I feel you want to help me?

@whdigger ping me on skype alex.oshchepkov


download MODIS (crs: SR-ORG:6974) data appears obscured

Dear Developers:
Thank you so much for being able to develop the awesome xee.
I was downloading the MODIS series product (MODIS/061/MOD16A2GF) and noticed that the downloaded data was shaded.
I think it's a problem with the crs.
Here are the images and code:
ic_name = 'MODIS/061/MOD16A2GF'

ic = ee.ImageCollection(ic_name) \
  .select("ET") \
  .filterDate('2013-06-02', '2013-06-03')

ds = xarray.open_dataset(
    ic, engine='ee',
    crs = 'EPSG:4326',
    scale=0.25
)
ds

ds.to_netcdf('test.nc')

r = xr.open_dataarray('test.nc')
r

r \
    .assign_attrs(crs='EPSG:4326') \
    .transpose() \
    .plot(
    vmin=0, vmax=300,
    levels=[i for i in range(0, 270, 30)],
    colors=['#ffffff', '#fcd163', '#99b718', '#66a000',
            '#3e8601', '#207401', '#056201', '#004c00', '#011301']
)

What specifically do you mean by "shaded"?

I'm sorry. Maybe I didn't describe it properly.
This image is ok on GEE.
var dataset = ee.ImageCollection('MODIS/NTSG/MOD16A2/105');
var ET = dataset.select('ET').filterDate('2013-06-02', '2013-06-03');
var ETVis = {
  min: 0,
  max: 300,
  palette:
      ['#ffffff', '#fcd163', '#99b718', '#66a000',
            '#3e8601', '#207401', '#056201', '#004c00', '#011301'],
};
Map.addLayer(ET, ETVis, 'Evapotranspiration');

But exporting locally using xee results in something like the following:

Ah, you mean the weird yellow area over Americas and Antarctica. I agree this is wrong.

Indeed. But xee is so good that I just can't live without it, so I'm looking for a solution here

Let's see what the actual developers say - I'm just another xee user

Have you tried this with different times or different bands and does it yield the same result? I am also having a problem with bringing MODIS data across via xee, though a bit different to what you are showing.

Have you tried this with different times or different bands and does it yield the same result? I am also having a problem with bringing MODIS data across via xee, though a bit different to what you are showing.

I've tried different periods and it's the same problem :(

What I notice about this dataset is that each band has a different scale, which is the same case as #122. There is a chunk of code in get_info where xee infers a number of collection-wide attributes like the primary coordinate. Just spitballing, but maybe that has something to do with it? Like that data differs between bands with different scales?

Hi @tylere,
I don't know what happed, but I think the bug has been fixed, here is the same example i reproduced.
https://colab.research.google.com/drive/1QL8-_NL_Y4vupzhdAvfpvlWD0IYf7OZX?usp=sharing

Hi @cug-xyx,
I'm not able to access the Colab link you shared. Could you either:

share your Colab notebook on Drive publicly (Share -> Anyone with the link), or
share the Colab notebook as a GitHub Gist (File -> Save a copy as a GitHub Gist)

Hi @tylere
I changed the permissions and now you should be able to access the link!


Video player fixes

fixes #2442

@mrEuler this is work in progress but this will allow us to have test cases for the video playing logic so we can have it more stable.
About the video orientation, I will add the possibility to get the preferred SkMatrix for that video.

@mrEuler I have more improvements I want to bring to this feature but in the meantime, here we have a basis to collaborate, we can add examples, test cases, and follow different issues on the topic


HELP！！！ImportError: /home/z。。/。。/PyTorch_Test/src/mmdetection/mmdet/ops/roi_align/roi_align_cuda.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _ZN3c1019UndefinedTensorImpl10_singletonE

Idon't know what is this mean.how to dealwith it?If you can help me ,thank you so much!!!!!!!!!!!!

Please follow the Error report issue template.

Thank you for replying me.But I still have a question, where is the Error report?Is that a document in the github? thank you so much!

When you click New issue to open a new issue, please select the Error report.


New blog posts shouldn't be auto featured on blog

This is an enhancement suggestion.
On top of the front page, now the three most recent posts are featured. That's a wrong practice. Usually, that's the spot where you want to place more important stuff. There should be an option to mark posts featured.

Agreed, would be great to be able to pin posts.

I like part if this is because it orders by post id index. It would be nice to see it use the date, as those can be modified, unlike the post id.


Segmentation Fault in Atom after installing atom-ide-ui package

If I open a file like,
$atom test.py
the main window is opening after a long wait, even after it opens, it's not responsive so i have to force close it. After force closing it, this is arriving in terminal,
/usr/bin/atom: line 129:  3930 Segmentation fault      (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
Can someone tell me how can I provide more information about this bug?
Atom: 1.20.1
OS: Fedora 26
atom-ide-ui: 0.3.3

Thanks for the report - it looks like you opened an issue in the atom-ide-ui repository, that's probably a better place for this issue if the error happens specifically after install atom-ide-ui (assuming that if you disable or uninstall the package, things work ok?).  Also, for future issues, please fill out the issue template, it's super helpful for us and provides a lot of baseline information.

Thanks for your response. Yes the issue is specific to atom-ide-ui.
If i disable the package this doesn't happen.


feat: a collection of small improvements

Once CI passes, it can be merged.

@anonrig You can merge it now.


[wasm] Remove WScript LoadWasm

Remove WScript LoadWasm since SExprParser is now removed.

Hi @commonlisp, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

lgtm


python311Packages.sensirion-ble: 0.1.0 -> 0.1.1

Diff: https://github.com/akx/sensirion-ble/compare/refs/tags/v0.1.0...v0.1.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 254987 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.sensirion_ble
python310Packages.sensirion-ble
python310Packages.sensirion-ble.dist
python311Packages.sensirion-ble
python311Packages.sensirion-ble.dist


ddagrab stuttering and cursor issues

Hi, it seems ddagrab is currently broken in the latest builds.
The cursor causes a tail effect and the frame rate skips/jumbles.

Works fine for me on latest win64 build.
Make sure your graphics driver is in working condition.

Hi, same issue.  Latest drivers for intel XE graphics.
It also has the same issue on a cloud A4000 nvidia GPU PC.
https://github.com/BtbN/FFmpeg-Builds/assets/127526527/8a2d76cb-bb5e-4500-a62b-1d6046eb3229

I have just tested it, and it works perfectly for me. So I'm not sure what to tell you or what I should do about it.

Hi, even this sample command causes such an issue;
ffmpeg -filter_complex ddagrab=output_idx=0:framerate=60,hwdownload,format=bgra -c:v libx264 -crf 18 output.mp4

Your command also works perfectly fine for me, and produces clean and intact output.
This looks much more like some weird driver side issue than anything related to FFmpeg, let alone these specific builds of it.

Hi, even software encoding, it does not work (no drivers required), same issue.
I've tested on several machines with latest Windows 10, same issue.

ddagrab is quite low level and directly interfaces with the graphics driver.
It works perfectly for me on both Nvidia and Intel Iris Xe, so my suspicion is that it's some bug in older Intel GPU drivers or something.
It's probably fallout from https://github.com/FFmpeg/FFmpeg/commit/21c6d12449a2230a959da79f224b7443fe89d6d3 but without that patch capturing is completely broken in different ways.
The patch still looks correct to me, and it's likely a driver bug where it does not honor the correct order of operations for some reason.

The encoder is not involved in this, so not sure why you keep bringing it up.
ddagrab always interfaces with the graphics driver.
And like I said before, I am completely unable to reproduce this on both an Nvidia and an Intel machine.

Can you run a debugger on this? Since I can't reproduce this, I have no chance of fixing it otherwise.
Run ffmpeg like this:
./ffmpeg.exe -v debug -init_hw_device d3d11va=dbgdev:-1,debug=1 -filter_hw_device dbgdev -filter_complex ddagrab=0:framerate=60 -c:v hevc_nvenc -preset slow -cq:v 20 -y out.mp4
The output side doesn't matter, feel free to replace nvenc with x264 or whatever.
Run https://learn.microsoft.com/en-us/sysinternals/downloads/debugview before and while invoking ffmpeg like that. It should capture any D3D11 debug messages from ffmpeg, hopefully giving an explanation for this.
For me it comes up completely empty outside of a bit of noise on shutdown.
For this to work, you need to have the d3d11 debug layers installed.
You can check by running where.exe d3d11_1sdklayers.dll. It it's missing, you might have to install the "Graphical Tools" Optional Feature, or the full on D3D SDK.

After quite a wild chase for this, we finally found the root cause and fixed it in https://github.com/FFmpeg/FFmpeg/commit/b47abd5737eed9304fc808bc7a1043c55b21263f
I still don't fully understand why these flags are different per system or screen. But they are. And depending on what they are, it can break in multiple ways.


fix: fix wrong return types + add missing fields

Description
https://github.com/asyncapi/event-gateway is already implementing partially this API. During the development, I found out some return types are wrong and a missing method on Schema.

Good catch 🦅 👀


Rename PathFollow's offsets to progress & progress_ratio

Partially closes https://github.com/godotengine/godot-proposals/issues/5104
As brought up in https://github.com/godotengine/godot/issues/54161#issuecomment-1214436401.
Properties containing "offset" are very vaguely utilised across the language. Often that's fine, but for both PathFollow2D and PathFollow3D it's particularly egregious. There's offset, unit_offset, h_offset and v_offset. The latter two refer to the visual offset, and unlike other classes (such as Sprite2D), these cannot be unified as a single Vector2 value, because the singular offset property already exists, referring to the offset along the curve. This PR attempts to fix one part of that.
For both PathFollow2D and PathFollow3D:
offset -> progress
unit_offset -> progress_ratio
I find the name "progress" to be quite suitable and a much more specific term. Think of "The progress along the track, measured in units of distance".
Meanwhile, "ratio" fits a lot more than "unit" to to imply the range between 0.0 and 1.0. The new name also allows it to be grouped better along with "progress" This name would also bring more consistency with this other PR: https://github.com/godotengine/godot/pull/64665
Applies for both PathFollow2D and PathFollow3D. Updates documentation and project converter, as well.

This time the log on the Android Build is not exactly being helpful...

I don't think this is a good idea.
progress is very strongly associated with Godot update loop, which is also called _process() and _physics_process(). Neither of which the PathFollow offset property has no correlation with.
offset on the other hand is used with Sprite offset and Texture offset for example. Both properties which will move the "thing" from the origin point by some value. Which is exactly what PathFollow's offset also does. Maybe this is more obvious if you got accustomed in using PathFollow2D before you use the 3D variant?
unit_offset also makes sense to me, as it evokes association with the normalized unit vector (so I know it's going to be between 0.0 and 1.0), but personally I would think offset_percent would work as well (however then I would expect values from 0.0 to 100.0)

First I've heard of progress being used in the update loop aka _process or _physics_process.

Thanks!


Add a tutorial for getting started with MSON

I think this is a fantastic start! One thing I'm wondering is whether it would be useful to show how the data structures might look as JSON. It may help people more familiar with JSON data to visualize how the MSON works and what exactly it is describing.

Great start! :tada: I'm missing a little word about nesting, but otherwise it's awesome!

@kylef love it. Waiting for and ending tho – are you going to add something else to it, feels unfinished. Note I would really love to keep it this short (or not much more longer).

@danielgtaylor @kylef I somewhat like the fact that they are no JSONs here. In fact, JSON isn't even mentioned in the tutorial! This is great! MSON isn't another way to write JSON and I believe this can put the emphasis on it.
Note, I am fine with JSON rendering examples in README but really love the way Kyle wrote it without JSON...

:+1: on this as it is, but im sure it could be expanded upon plenty for enums and stuff. I'll be happy to add to it when it's in.

Just the very minor feedback above. Otherwise I'd say this is ready to be merged!

Thanks @danielgtaylor, I've addressed your feedback (and also fixed a few other minor spelling mistakes).


refactor: Lightning Dir for Gateway

This PR refactors the Gateway's lightning implementations into a lighting directory.
Started as a hack to get the gateway to work with the alby api, but halfway through realized this would be a good refactor for adding additional implementations and apis as lightning options for the gateway in the future.

sweet! Just resolved conflicts and pushed


[Docs] Dead links in contributing doc

Describe the issue
Several dead links exist in the contributing doc - specifically, those pointing to documentation and showcase links (https://miroiu.github.io/nodify/docs and https://miroiu.github.io/nodify/showcase/ respectively).
Screenshots

Additional context
Dead links were mentioned previously but never resolved (https://github.com/miroiu/nodify/pull/74).

Thanks for your contribution!


Evaluation of user data using Unitxt

Here is the suggested flow. Let's discuss in a meeting to see it makes sense and modify as needed:
Evaluation command [ilab model evaluate new_data] will have the following parameters:
1 - csv_path for user data

A csv file with two required column ('instruction','input') and two optional columns ('answer','context')
'context' column is for the RAG task only
'answer' is the golden truth, if available
'instruction' explain the task ("Summarize this text", "Complete this sentence", "Classify this input to one of the following: ... ")

2 - task_type out of the following options:

Classification
Question Answering [Let's discuss if we want to explicitly offer QA multichoice and simple QA as two separate options]
Summarization
Generation
RAG
Other [Let's discuss if this can actually be removed as it will get the same treatment as QA behind the scenes]

3 - use_llmaaj (False by default)

False - default standard metric for the task

for some tasks the default is llmaaj to begin with: QA, Generation, Other
llmaaj will be used if golden answers are not available

True - Uses judge (with templates pre defined for the task type)

4 - num_shots (0 by default)

Do we want to allow the user select num shots?
Do we want to drop this option, run a few configurations (0, 2, 5 shots) and inform the user which is the best setting?

Following the command, unitxt will  run the provided data with the task of choice, and replace the metric if llmaaj is selected.
The data will be run in multiple configurations (fitted into different templates that match the task).
Results will include a recommendation for the best template of those used.

@alimaredia Following yesterday's meeting, could you please share the evaluation notebook you prepared? This will help us understand the plan better and identify what contribution can be offered with unitxt

@danmcp @alimaredia  regarding the linked PR -  I have addressed all issues, except the parameterization of the unitxt recipe, which I believe is no longer relevant to our current discussion. Perhaps it is better to close it and open a new one once we've defined the features it will contain?

@danmcp @alimaredia regarding the linked PR - I have addressed all issues, except the parameterization of the unitxt recipe, which I believe is no longer relevant to our current discussion. Perhaps it is better to close it and open a new one once we've defined the features it will contain?

I don't have a strong preference whether we close it of leaving it hanging out for a bit.  Agree if we do settle in on a different design it should be a new PR.


Add instructions to document current data classification.

Refresh onboarding documentation for data team to mention the
Google Docs spreadsheet and mention the dedicated Slack channel for
the data team to direct inquiries accordingly.
(This was discussed during last night's meeting; feel free to tweak or reject as needed.)

These look like good edits to me - thanks for adding them to the documentation!

Merging into the 'master' branch since this is what is deployed to our live website. I'll then merge the master branch back into dev so that docs changes are the same on both branches.


Output directories should match configured region names

Historically, output directories were constructed using additional parameters to provide context in a systematic way (e.g. "city-codename_region_year"), but it becomes messy when the city codename needs to have a year to differentiate longitudinal entries across time (e.g. 'las_palmas_2022' would look like 'las_palmas_2022_es_2022').
A better approach would be to direct users to pick a consistent codename schema for their regions (e.g. "country_city_year") and leave that responsibility with them, with files and folders accordingly using that name -- not constructing one which likely contains repetitions.
For example, the above example name should probably be 'es_las_palmas_2022', so when there were other cities like 'es_barcelona_2022' and 'es_las_palmas_2023' these are clearly well ordered and have corresponding output folders.
Care should be taken implementing this change to ensure file and folder paths still work through out the workflow.

This is in principle simple to implement, just by changing the following line in _project_setup.py:
https://github.com/global-healthy-liveable-cities/global-indicators/blob/04fc3897ee10d376becaa1e221e41bd542c6aabb/process/subprocesses/_project_setup.py#L141
to
    r['study_region'] = region

The only thing is, for people with already processed regions and databases, these would no longer be recognised so they would have to re-process from scratch and be aware that any future analyses would be in that folder.
The further thing to be aware of is the increased importance of choosing a sensible naming schema.  I believe the recommendation should to use 2-letter country code, then city name, then year.
For example for an analysis of Melbourne in Australia in 2023: 'AU_Melbourne_2023', or the included example of Las Palmas in Spain would be 'example_ES_Las_Palmas_2023'.
In this way further study regions that could otherwise be ambiguous can be included:

AU_Melbourne_2023
AU_Melbourne_2016
US_Melbourne_2023
US_Florida_Melbourne_2023
AU_Victoria_Melbourne_2023
ES_Valencia_2023
VE_Valencia_2023

etc (so Valencia in Venezuela and Spain are differentiated, and Melbourne in US and Australia likewise; this avoids some ambiguities if some analysts happened to use the study for multiple study regions and timepoints).
In the above examples, it is implicit that the definition of study region names is flexible and at discretion of the analyst; likewise it is their responsibility to choose something sensible to ensure the region remains correctly identified with regard to time and place being targetted for analysis.

Further consideration - currently, region code names are lower case, but treatment of region code names using mixed case could potentially cause issues in SQL code if not accounted for.  At least, it should be tested that this works with all the SQL code (name needs to be put in quotes so case is preserved).

This was addressed in #218


Wrong message type! Expected ActionResponseMessage, got:

Hi,
zeus doesn't work for my test_envioroment, whenever i start it, i get this:

[medistrano] zeus start               13:03:11  ☁  feature/consume-kraken ☂ ⚡ ✭
Starting Zeus server
ready   : boot
ready   : default_bundle
ready   : development_environment
ready   : prerake
EOF
Wrong message type! Expected ActionResponseMessage, got:
ready   : test_environment
died    : test_environment

My OS is Mac OS X 10.7.4
ruby:  ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.0]  (ruby-1.9.3-p194-perf)
zeus: 0.11.0
zeus.json:
{
  "command": "ruby -rubygems -rzeus/rails -eZeus.go",

  "plan": {
    "boot": {
      "default_bundle": {
        "development_environment": {
          "prerake": {"rake": []},
          "runner": ["r"],
          "console": ["c"],
          "server": ["s"],
          "generate": ["g"]
        },
        "test_environment": {
          "cucumber_environment": {"cucumber": []},
          "test_helper": {"test": ["rspec", "testrb"]}
        }
      }
    }
  }
}

My gem file looks like this:
source :rubygems

gem 'rails', '~>3.0.0'
gem 'mysql2', '0.2.18'

# NB: rest-client must be require after right_http_connection.
# We don't depend on either directly, but chef & dynec_rest use rest-client;
# and right_aws uses right_http_connection
gem 'right_http_connection'
gem 'rest-client'

gem 'octokit', '1.8.1'
gem 'capistrano'
gem 'open4', '0.9.3'
gem 'syntax', '1.0.0'
gem 'hashie'
gem 'httparty'
gem 'newrelic_rpm'
gem 'json'
gem 'wicked_pdf', :git => 'git://github.com/mileszs/wicked_pdf.git'
gem 'dynect_rest'
gem 'ubuntu_ami'
gem 'fastercsv', '1.5.4'
gem 'delayed_job_active_record'
gem 'rack-active_record_status', '0.4', :require => 'rack/active_record_status'
gem 'acts_as_audited'
gem 'memcache-client'
gem 'fog', '>=1.5'
gem 'excon'
gem 'plist'
gem 'rubycas-client'
gem 'chef', '>= 0.10'
gem "cancan", "1.6.7" # previous was 1.6.5
gem 'mauth-client', :git => 'git@github.com:mdsol/mauth-client.git', :tag => 'v2.3.0'
gem 'eureka-client', :git => 'git@github.com:mdsol/eureka-client.git', :tag => 'v2.0.1' # 2.0.2 failed
gem 'mdsol-uri', :git => 'git@github.com:mdsol/mdsol-uri.git', :tag => 'v0.1.0'

gem "rspec-rails", :group => [:test, :development]

group :development do
  gem 'passenger'
  gem 'ruby-debug19'
  gem 'growl'
  gem "fakeweb"
  gem 'ruby_gntp'
end

group :test do
  gem "cucumber-rails", '>= 1.1.1', :require => false
  gem 'mocha', '0.9.8', :require => nil
  gem 'autotest-rails'
  gem 'autotest-growl', :require => 'autotest/growl'
  gem 'ZenTest', '4.4.1'
  gem 'factory_girl', '2.6.4'
  gem 'factory_girl_rails'
  gem 'shoulda'
  gem 'minitest'
  gem 'term-ansicolor'
  gem 'turn'
  gem "capybara"
  gem "guard-rspec"
  gem "guard-cucumber"
  gem "launchy"
  gem "database_cleaner"
  gem 'selenium-webdriver'#, '0.2.1'
  gem "pickle"
  gem "growl" # guard asks for this gem
  gem "fakeweb"
end

Thanks,
Rodrigo

I had the same issue. It turned out to be caused by not installed gems from my Gemfile. After bundle it started working again.

I also get into this issue with Zeus 0.15.1. And this is weird because I was doing nothing with the environment. Just restarted Zeus and got this Wrong message type!.
Apparently the reason was in updating Gemfile by another guy. When I pulled down the update and restarted Zeus it broke. So I did bundle install and it worked.

Thanks @somebody32!  I didn't realize I had new gems that needed to be installed via bundle install, which cleared up the issue for me.


Alter Database Linger value

https://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-ddl-enhance.html#rnfb30-ddl-enhance-linger
 ALTER DATABASE SET LINGER TO {seconds};
 ALTER DATABASE DROP LINGER; (or set to 0 seconds)

Also, currently Fr loads the linger value just once, if you change it via alter database, you need to disconnect and reconnect from DB

Hi @arvanus
Could you please retest this issue on FlameRobin <IP_ADDRESS> and close it if it is no longer reproducible?
Thanks in advance,
Luciano


Plugin cannot handle points in the note name

Great idea. In my case very helpful to keep an eye on todos over a lot of daily notes.

I use the standard plug-in for daily notes. I use the german standard format for the date: 02.22.2021 (DD.MM.YYYY). The plugin basically doesn't seem to be able to handle dots in the note name.
As can be seen in the picture, these notes are sorted as "undefined".

It is possible to fix that?

I think the tag in list is redundant and not necessary (for me).
There might be an option to toggle the tag on and off in the sidebar.

I will definitely get no.1 fixed.
With no.2 you don't actually have to tag each todo item you just tag a block and it will pick up all todo's in that block. That being said I think it's a good idea to strip the match tag out out of the checklist when rendering. I'll include that in next release as well.

I will definitely get no.1 fixed.
With no.2 you don't actually have to tag each todo item you just tag a block and it will pick up all todo's in that block. That being said I think it's a good idea to strip the match tag out out of the checklist when rendering. I'll include that in next release as well.

Sounds greate.
Thank you!

Sounds greate.
Thank you!


Allow local installation to be performed as a privileged user

Depending on the way the role is installed the local installation
steps will fail with a permission denied error.
Specifically I've encountered the issue in an Vagrant + Ansible Local
setup scenario, where the roles are installed using the pattern
described in the Vagrant docs:
https://archive.is/m8ZgO#install-galaxy-roles-in-a-path-owned-by-root

This role can be installed with this Vagrantfile

This role can be installed with this Vagrantfile

You're using the ansible provider in that Vagrantfile, the issue is when using the ansible_local provider (roles are installed as root inside the VM)

@bbaassssiiee let me know how you'd like that variable to be called. I can't think of a good name.
I guess it would be a variable that defaults to false and it's interpolated/expanded in the become directives I have commented out in my previous PR.

@bbaassssiiee let me know how you'd like that variable to be called. I can't think of a good name.
I guess it would be a variable that defaults to false and it's interpolated/expanded in the become directives I have commented out in my previous PR.

vault_privileged_install

vault_privileged_install


Variations

I'd like to show two different radio groups, 1 using roving tabindex and 1 using aria-activedescendant. What do you all think would be the best way to handle variations of a pattern?

Interesting! From the top of my head I see the following options:

Completely separate elements, feels a little weird tho
Some sort of comment syntax to denote alternatives and you can switch between them in the UI. This kinda assumes that the changes needed for the different alternatives are very local.
Using the alternatives in different elements and linking to each other in the comments (something like “Instead of using roving tabindex you could be using activedescendant. See <dash-checkbox> for an example). I like this version the best, as it minimizes duplication and encourages more reading, but not sure if it is sufficient for what you are planning.

I think we can go with option 3 to make things easy


fix: Prevent displaying renamed file names

Problem
When renaming a file and staging it, the original file name is displayed with incorrect highlighting.

Solution
Modify the display to avoid showing the line immediately after the line with status "R".
Since I'm still learning, please feel free to point out any mistakes or errors in my pull request. Your feedback is greatly appreciated.

Thank you for your pull request.
I'm sorry to left it unattended.

No worries at all.
Thank you for your response!


adding unitless dimensions for lansen devices (0x3a)

adding a handler for unitless dimensions sent by lansen OMS devices like Lansen Pulse Counter.
formerly the vif has been identified as unknown which gets ignored by pymbus later down the line.
this creates a new unit called "unitless dimension", which will be processed by pymbus by default.

Looks good to me


Do you accept 'Rails' functions ?

Such as present?

You mean that you want to port Rails-specific methods out of Rails, or do you have a new method that would be Rails-only?

I want to port Rails methods outside of it.

No, sorry. We designed FM to play nicely alongside major projects like Rails and Rack; porting methods would mean dealing with conflicts.

Clarification: if you want to add some logic that only exists in Rails, we would consider that, however it cannot conflict with Rails.
e.g. if you want to add the same logic as present?, perhaps there's a synonymous word we could use.
Were you thinking of any other methods?

I like to use blank? too

Perhaps we can borrow a few Rails methods, and only activate them when in a non-Rails environment. We'll consider it, but a pull request is always welcome.

@nicolas-besnard it sounds like you want a bunch of those methods - why not simply use the activesupport gem directly?

#5

After some internal discussion, we've agreed that Finishing Moves must continue to be Rails-agnostic: it should work perfectly fine on it own, and play nice when loaded in a Rails environment.
If you want to use a specific piece of Ruby logic, then you should load the appropriate gem. Rails broke itself out into multiple gems for this very purpose.


OAuthError is not callable

Checklist

[X] The issue can be reproduced in the auth0-react sample app (or N/A).
[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
Introduced in https://github.com/auth0/auth0-react/pull/638; trying to call new OAuthError('name', 'message') returns the following error:
errors.tsx:10 Uncaught TypeError: Class constructor d cannot be invoked without 'new'
    at new OAuthError (errors.tsx:10:1)
    at <anonymous>:1:1

In this case d refers to GenericError.
Expected result is to return an error object.
Reproduction

Call new OAuthError('name', 'message')

Additional context
No response
auth0-react version
2.2.3
React version
17.0.2
Which browsers have you tested in?
Chrome

Thanks for reporting @elstgav
Fixed in https://github.com/auth0/auth0-react/releases/tag/v2.2.3


Implement DAO for GC history

1, design the scheme for gc history.
2, Implement DAO.
3, Add API to query history.

Close it as no use DB to store GC history, just store the latest results with file in the registry container, and expose the API to get it in UI.


Thaw a paused container in cgroup v1 when it is forcely deleted.

If force is not given, and cgroups is v1 and container is frozen, display error saying could not be killed as it was forzen. If force option is given, and cgroups is v1 and container is frozen, thaw it and send the kill signal. If cgroups is v2 , nothing special needs to be done.
Fix: #1129
Signed-off-by: Chen Yiyang<EMAIL_ADDRESS>

Codecov Report

Merging #1204 (e9dbb3c) into main (281c0a9) will decrease coverage by 0.13%.
The diff coverage is 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1204      +/-   ##
==========================================
- Coverage   69.29%   69.15%   -0.14%
==========================================
  Files         118      118
  Lines       12474    12499      +25
==========================================
  Hits         8644     8644
- Misses       3830     3855      +25

Hey @cyyzero , I was going through implementation of runc of this, and one thing I noticed is that for single or multiple (https://github.com/opencontainers/runc/blob/main/libcontainer/container_linux.go#L370) , they first signal the processes, in the frozen state ( in fact they seem to freeze the cgroup before sending kill signal in case of all https://github.com/opencontainers/runc/blob/1c3b8dbaf440d16653d834b612258bbb28268730/libcontainer/init_linux.go#L530) then send kill signal, and then thaw the cgroup
In the PR you seem to thaw the cgroup before sending the kill signal. One of the issues with this is that between the time you get all processes from the cgroup and the time you send signal, there might be additional processes spawned as cgroup is not frozen. The runc's way seems to avoid it.
Also once you are done with the initial implementation that is in the current state, can I ask you to add --all option in the cmd interface? It is a pretty small change, and the value of it will be given as all argument to the  kill. That will help us to pass one of the containerd test.
Thank you!

I might know why integration test TestContainerKillInitPidHost fails.  It seems the first kill has no options.  In the previous implementation, the container status becomes stopped after kill, and subsequent kill --alls can't pass the can_kill check, so the child process could not be killed correctly.
In fact, in the runc source code, it doesn't do status check for --all option.
https://github.com/opencontainers/runc/blob/1102f3fc9d5208961f19d70618c3be251466ee3f/libcontainer/container_linux.go#L361-L371

@cyyzero Apologies for the delay in my response. I have updated the comments, and if you can change the process exit to return result and add the --all option to the cli part (liboci-cli  and the youki actually invoking the command), this PR is fine. Can you make that change and un-draft this PR, so we can approve and merge it? Thanks a lot!
@utam0k , as this does change the behavior of kill slightly, and adds an --all flag, should we bump the version of youki, liboci-cli and libcontainers?
Again, apologies to both for the delay on my side :sweat_smile:

@utam0k , as this does change the behavior of kill slightly, and adds an --all flag, should we bump the version of youki, liboci-cli and libcontainers?

I'm planning to release v0.0.4 soon if the contained test is passed with youki after merging this PR, so there is no problem. Thanks for your concern ;)

https://github.com/containers/youki/blob/6d05dd2f60198aaecb7c93d08c08d7db4fbc6600/crates/liboci-cli/src/kill.rs#L5-L11
@YJDoc2 Thanks for your review! It seems that the --all option has been added to the liboci-cli before. And I have changed some exit(0) to return Ok(()).

Hey @cyyzero Thanks for your contribution and efforts ! :)


Fix issue 92, 88  and CounterVisibleProperty, TextFontSize, PlaceholderFontSize

The PR is disabled all underline in EntryField when AlwaysShowUnderline is set false.

Hi. I am also currently refactoring MaterialTextField. Can you checkout dev-textfield-editor branch?
I can't accept the commit for changing the FontSize property because it causes some bugs during layout. I reverted the changes from this PR. The current container of the text field is set to 56, I'm doing a refactor by using an Editor instead of Entry to accept multi-line inputs, where I check the size changes of the Editor to adjust the container's height. Perhaps I'm gonna do the font size changing.
I also fixed issue 88 already.
The AlwaysShowUnderline property is used to place an underline indicator when the BackgroundColor was set to Transparent. If you want not to show the underline animation, perphaps a ShouldAnimateUnderline property is much better. You can add a condition here in this block inside the AnimatePlaceholder method, just like when the FloatingPlaceholderEnabled is false:

If you want, I can also do these changes myself.

Hi, changes has been applied.


Create pt-br.json

Portuguese (Brazilian) Translation

Thank you for your contribution! :+1:

You're welcome! <3


Cannot run Inventory example

I'm sure this is entirely due to my own lack of understanding regarding composer and github, so I really appreciate any advice. I followed the installation instructions using composer, and I got the "Get the official eBay time" example working with no problem.
However, running the "02-create-or-replace-inventory-item.php" example (copy/paste of the code into my own test.php script) failed. The first attempt gave the following error:
PHP Fatal error: Class 'DTS\eBaySDK\Inventory\Services\InventoryService' not found in /path/test.php
I checked my server and found the "vendor/dts/ebay-sdk-php/src/DTS/eBaySDK" folder did not contain an "Inventory" subfolder (among several others). So I manually downloaded the master source from github, and uploaded via FTP, skipping any existing files. Now when I run my test.php script I get a different error:
PHP Fatal error: Call to undefined function DTS\eBaySDK\applyDebug() in /path/vendor/dts/ebay-sdk-php/src/DTS/eBaySDK/ConfigurationResolver.php on line 59
I checked out ConfigurationResolver.php and it makes no request for the applyDebug() function anywhere.
I imagine I missed a simple composer step or something..?

Have you tried, next to composer, one of the other methods of installation explained here: http://devbay.net/sdk/guides/getting-started/installation.html?

I had tried them yesterday but ran into some conflicts because I was running PHP 5.4 but they needed 5.5. Had my host install 5.5 separately today and did some testing:
The .phar method results in the same applyDebug() undefined function error
The .zip method seems to be working so far
So I'll stick with the .zip file for now


[EVENT] sprite "pointermove" event emited from all document body area

PIXI 4.5.4
this emitted even when i moving mouse outside canvas
sprite.on('pointermove', function(){
  console.log('pointermove')
})

Is this a bug?
black is canvas:

If not, then this behavior is not intuitive. Let's hang one global "pointermove" handler on the canvas element, and in it filter the sprites which have a "pointermove" handler, and to emit events directly on them

Could you provide an example please on somewhere like jsfiddle?

https://www.youtube.com/watch?v=N9h9UX1K8Ms

@themoonrat https://jsfiddle.net/o43ssr1t/2/

If you look at
https://jsfiddle.net/themoonrat/3v1ez4jt/3/
you can see that by adding
app.renderer.plugins.interaction.moveWhenInside = true;
you can replicate the behaviour you require
The documentation for this variable and why it is like it is can be found at http://pixijs.download/dev/docs/PIXI.interaction.InteractionManager.html#moveWhenInside

@themoonrat Excuse me, but is this behavior not a bug? It emit pointermove evet in sprite, even the cursor is not over the sprite. When can this be necessary?

As explained in the docs, it's by design, although in the docs it also says that default behavior could change in a future version.
Someone may come and correct me, but I believe because some methods of dragging a sprite could fail if you tried to drag very quickly and moved your mouse quickly from over the sprite to not over the sprite. The cursor wouldn't be over the sprite anymore, so no moves given. By always emitting the event, you can always compare the starting point on mouse down to any more events points.

But the behavior of dragndrop always involves setting the handler to the parent container, because that's where the element will move, is not it?

For pixi v5, a re-think of how we do interaction is on the cards :) We understand that v4 interaction is not quite where we want it, but any major changes to how it works would break compatibility.

break compatibility.
How I hate this thing, and at the same time I love. XD


Create rockcraft projects for pytorch full CPU image

Why it needs to get done
The DSS project allows users to select the image of the Notebook server to be used, some of which are built and distributed by this team.
What needs to get done

Create a rockcraft project for the pytorch full Notebook Server image. Use this Dockerfile for reference.
Add sanity tests to the rock.

When is the task considered done
When the pytroch full CPU image is published in the CKF team Dockerhub repository.

Today I was working on this looks like we already have this rock created for kubeflow here.  After discussion on daily we decided to use those rocks form kubeflow-rocks repo. On top of these we will install mlflow library. At the time of planning we forgot about those rocks.

Checking the code in here today. I found out that the upstream branch 1.8-branch has changed completely so we can no longer build the rocks the same way as we did originally. Key differences:

each sub base image (jupyter, jupyter-pytorch) is not installing key requirements from requirements.txts but rather inside the docker file example
names of the files has changed e.g. ther is no longer cpu-requirements.txt in jupyter-pytorch folder.
upstream uses mamba to install dependancies to support arm64

because of this we need to rewrite each rockcraft yaml.

After talking with @DnPlas we agreed on following:

I will rewrite the pytorch cpu jupyter ROCK to match the upstream Dockerfile except the s6 updates which are not needed for this task. PR is here.
I will open this issue.

During the testing of the new ROCK I was facing problems with trivy timing out. I openned this PR to increase the default timeout https://github.com/canonical/charmed-kubeflow-workflows/pull/51


no start.bat

there is no start.bat. and if i do main.py it just closes instantly

did you install all packages?

yea
On Mon, Mar 11, 2024 at 2:29 PM ApfelTeeSaft @.***>
wrote:

did you install all packages?
—
Reply to this email directly, view it on GitHub
https://github.com/ApfelTeeSaft/Fortnite-GS-Uptime-Announcer/issues/1#issuecomment-1989267223,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFDZJ5LYQEVPWDKL54SFHITYXYA2LAVCNFSM6AAAAABDDF2MNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBZGI3DOMRSGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

okay
On Wed, Mar 13, 2024 at 5:40 PM ApfelTeeSaft @.***>
wrote:

try to first start your gameserver and when the window title changes,
start the python script
—
Reply to this email directly, view it on GitHub
https://github.com/ApfelTeeSaft/Fortnite-GS-Uptime-Announcer/issues/1#issuecomment-1996011630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFDZJ5LVODUCWJMN6IVJAXDYYDIULAVCNFSM6AAAAABDDF2MNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJWGAYTCNRTGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Anything wrong about the result?

Here is the result of GZSL on CUB:
[0.0]     novel=0.0190, seen=0.0024, h=0.0042 , loss=5.0547
[1.0]     novel=0.0067, seen=0.0037, h=0.0048 , loss=4.8157
[2.0]     novel=0.0057, seen=0.0051, h=0.0054 , loss=4.6095
[3.0]     novel=0.0040, seen=0.0123, h=0.0060 , loss=4.4239
[4.0]     novel=0.0040, seen=0.0143, h=0.0063 , loss=4.2417
[5.0]     novel=0.0037, seen=0.0199, h=0.0062 , loss=4.0880
[6.0]     novel=0.0040, seen=0.0214, h=0.0067 , loss=3.9427
[7.0]     novel=0.0040, seen=0.0220, h=0.0068 , loss=3.7959
[8.0]     novel=0.0037, seen=0.0220, h=0.0063 , loss=3.6719
[9.0]     novel=0.0047, seen=0.0231, h=0.0078 , loss=3.5571
[10.0]     novel=0.0047, seen=0.0240, h=0.0078 , loss=3.4314
[11.0]     novel=0.0047, seen=0.0250, h=0.0079 , loss=3.3595
[12.0]     novel=0.0047, seen=0.0249, h=0.0079 , loss=3.2751
[13.0]     novel=0.0043, seen=0.0254, h=0.0074 , loss=3.1913
[14.0]     novel=0.0043, seen=0.0260, h=0.0074 , loss=3.0842
[15.0]     novel=0.0040, seen=0.0275, h=0.0070 , loss=3.0107
[16.0]     novel=0.0030, seen=0.0281, h=0.0054 , loss=2.9473
[17.0]     novel=0.0027, seen=0.0281, h=0.0049 , loss=2.8864
[18.0]     novel=0.0027, seen=0.0286, h=0.0049 , loss=2.8150
[19.0]     novel=0.0027, seen=0.0286, h=0.0049 , loss=2.7325
[20.0]     novel=0.0030, seen=0.0281, h=0.0054 , loss=2.7147
[21.0]     novel=0.0030, seen=0.0281, h=0.0054 , loss=2.6553
[22.0]     novel=0.0027, seen=0.0292, h=0.0049 , loss=2.5960
0.00489604612812
I think something must be wrong so that I get such result.

Which setup did you use? The one below?
python single_experiment.py --dataset CUB --num_shots 0 --generalized True
If you use the data and packages as described in the readme, you should not get such a result.

Should I use the same version of the required packages in the readme?
For example, my torch is 0.4.0 while torch==0.4.1 in the readme.

I come across the same problem. How do you fix it?

@Hanzy1996 try to configure your environment as the same as the author proposed exactly

Thanks so much! I will try.


Great work! Direction?

Hey man, I like your lib, dead simple. Have you thought about adding "channels" and synchronization for goroutines in python?
If you are not planning on implementing, have you thought about some way to implement that?

But due to the single-threaded concurrency characteristics of Python, "Channels" are not practical in Python, maybe i will try multi-processing  but this lib can not achieve the same performance as Go.


MM-32350 - Integrations

Summary
Create subsections for Integrations Section

Integration Management
Bot Accounts
GIF
CORS

Ticket Link
https://mattermost.atlassian.net/browse/MM-32350
Related Pull Requests

Has server changes (https://github.com/mattermost/mattermost-server/pull/17097)
Has redux changes (https://github.com/mattermost/mattermost-redux/pull/1404)

Screenshots

Hi @sbishel
Can you pleaser resolve the conflict ?

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.


change S3 key format; add leading zeros in month, day, hour, and minute path segments

As mentioned in https://github.com/codeforpdx/opentransit-collector/issues/3, S3 keys created by Orion did not have leading zeros in the components with 2 digit numbers like months, days, hours, minutes, and seconds, so an alphabetic sort of the S3 keys doesn't put them in the correct order. This PR adds leading zeros to all path components and uses the luxon library (https://moment.github.io/luxon/#/) to simplify the code.
This PR also changes the format of S3 keys created by opentransit-collector to be consistent with the format used by opentransit-metrics, for example:
state/v1/trimet/2022/02/12/19/07/trimet_v1_1644692835014.json.gz
S3 keys now have the prefix "state", which makes it possible to use the same S3 bucket for opentransit-collector and opentransit-metrics, so that people don't need to create two different S3 buckets if they want to run their own backend. The "state" prefix is also consistent with the new name of opentransit-state-api, which provides an API for the data contained under that prefix. However, compute_new.py in opentransit-metrics currently also uses the "state" prefix to keep track of the last date of statistics computed. Since we don't really have any statistics yet we could just rename the prefix used by compute_new.py to something else so that people don't think that this data is related to opentransit-state-api.
Like the S3 keys created by opentransit-metrics, the S3 key also contains a version code (v1) which would make migration easier if we change the data format in the future.
This PR also removes the seconds from the S3 path component since it doesn't seem like anything used it. This reduces the number of clicks when browsing the S3 bucket.
To run the new code locally, developers may need to run docker-compose build first to install the luxon library in the docker container.
This change would also require changing opentransit-state-api accordingly.

Thanks for making these changes Jesse.

The luxon library is very convenient and simple.
Leading zeros and removing the second path are good calls.
I like the "state" prefix and I agree we should change the "state" reference in compute_new.py. Let's make sure there's an "issue" for that change so we don't forget.


feat(goal_planner): prioritize pull over path by curvature

Description
prioritize low curvature pull over path rather than high curvature one.
before

after

NOTE:
Currently, the curvature is calculated between the start and end poses. There is no prioritization among high curvatures, but it may be necessary to improve this by reducing the priority of paths with high curvature close to the curb, etc.

Related links
Parent Issue:

Link

Private Links:

https://tier4.atlassian.net/browse/RT1-6546

How was this PR tested?
psim
2024/07/03 https://evaluation.tier4.jp/evaluation/reports/e544fff5-a209-56e3-ac19-47e3f7c2620a?project_id=prd_jt
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

@soblin
checked scenario tests : https://evaluation.tier4.jp/evaluation/reports/e544fff5-a209-56e3-ac19-47e3f7c2620a?project_id=prd_jt
so could you review this PR?


Added "Footer" and "Scroll to top" button in Privacy policy and Terms Pages

Hey @Akshatchaube01 | Closes #331
I have added Added "Footer" and "Scroll to top" button in Privacy policy and Terms Pages

can you give some space before the footer, about 30px


Add forceCleanup option for 'startReplaceSegments' API

The current API will not attempt to proactively clean
up the lineage entry and throw the exception. When the
offline flow fails in the middle of the replacement
protocol, the second attempt will directly fail due to
the duplicate entry for 'segmentsFrom'. In this case,
having 'forceCleanup' option will help us to move forward.
If the flag is on, we proactively revert the previous
lineage entry and delete segments from 'segmentsTo'.

Codecov Report

Merging #7744 (a99bd24) into master (af01aa5) will decrease coverage by 49.63%.
The diff coverage is 69.23%.

@@              Coverage Diff              @@
##             master    #7744       +/-   ##
=============================================
- Coverage     64.23%   14.59%   -49.64%
+ Complexity     3985       80     -3905
=============================================
  Files          1568     1531       -37
  Lines         80194    78690     -1504
  Branches      11929    11770      -159
=============================================
- Hits          51510    11486    -40024
- Misses        25022    66360    +41338
+ Partials       3662      844     -2818

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
14.59% <69.23%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ces/PinotSegmentUploadDownloadRestletResource.java
41.17% <0.00%> (-13.58%)
:arrow_down:

...ntroller/helix/core/PinotHelixResourceManager.java
60.65% <72.00%> (+16.62%)
:arrow_up:

...ain/java/org/apache/pinot/core/data/table/Key.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/spi/utils/BooleanUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/data/table/Record.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/util/GroupByUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/data/MetricFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/pinot/spi/utils/BigDecimalUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/common/tier/TierFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/common/utils/StringUtil.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1405 more

Continue to review full report at Codecov.

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

LGTM, thanks for addressing the comments.

(nit) I think we can use SegmentLineageAccessHelper.getSegmentLineage() instead of getSegmentLineageZNRecord() in both startReplceSegments and endReplaceSegments.

@jtao15 We use getSegmentLineageZNRecord() because I need to extract version information which is part of ZNRecord but not the SegmentLineage.

@jtao15 We use getSegmentLineageZNRecord() because I need to extract version information which is part of ZNRecord but not the SegmentLineage.
I see, you are right.

#7813


When programmatically scrolling calendar, didSelectDate gets called.

I need a way to determine whether the calendar is scrolling because the user swiped it or because I changed it programmatically.
Note for example that when we programmatically scroll a UITableView, the scrollViewDidEndDecelerating doesn't get called also when programmatically selecting a cell in a table view, didSelectRowAtIndexPath doesn't get called.
However, when I programmatically scroll a calendar view by calling scrollToDate then didScrollToDateSegmentStartingWith:endingWithDate: does get called.

Looking into this. Will some something in some hours.

Hey. I just added an upgrade to master branch of this repository, can you check it out and see if it works for you?
If all is well, then in will release a new cocoa pod version in a couple hours after testing.

After taking an update from Master branch, you can now call the function like this:
calendarView.scrollToDate(date, triggerScrollToDateDelegate: false)

Thanks. This is exactly what I was looking for.

Hmm... I noticed that calendar(calendar, didScrollToDateSegmentStartingWith startDate, endingWithDate endDate) still gets called when the calendar is being constructed. In my book, that's a programatic change as well. I need a method that will only get called when the user initiates the scroll.
I'm trying to integrate the calendar with a unidirectional flow system and that's hard to do if I can't distinguish user input from system output. Thanks.

Ok looking into it.

For my project, the calendar didn't need to distinguish between programatic vs user change, so I never added the code to do this.
But What you say make sense. Calendar construction is a programatic change an not user initiated. I'll make this change in a bit.  Since the project originally didn't need distinguish who initiated the change, if you find any other issues, let me know.

I'm happy to. Thanks for the great library.

Thanks man.
Btw i had one question and needed a suggestion from you.
When the calendar is just created, i call the didScoll delegate to inform the user on which month/day they are currently on. When the delegate is called, a developer will hook into the function and update any UILabels that have that shows which month they are currently on etc.
If i remove this feature, on calendar creation, then this would be problematic. I am still thinking of ideas ok, but do you have any suggestions that will make both you, and the other devs currently using this library happy?

IMHO, on calendar creation, the calendar should not be telling the client which month/day it is currently on. Instead the client should be telling the calendar what month/day to start on. I would make it an extra return value for the configureCalendar method. Make a precondition that currentDate must be <= startDate and < endDate.
Something like:
func configureCalendar(calendar: JTAppleCalendarView) -> (startDate: NSDate, currentDate: NSDate, endDate: NSDate, calendar: NSCalendar)

Makes sense man. Thanks for the input. Working on it right now.

updated to version 3.0.0
Thanks for the help. If the issue is resolved you can close this one till the next time you bug me :)


Vmware notification and event api update

Fixes #
Proposed Changes

Attaching few screenshots for UI changes, you can refer these to get an understanding about the look and feel of UI.

Field “Log Types” is a drop down, user can select which kind of logs they would like to push to workspace.

There are 3 sections : API Credentials, SIEM API Credentials and AWS S3 Bucket Credentials.

2a. If the user has selected “Audit” as one of the Log Types. API Credentials section will appear, and the fields will be made mandatory, if “Audit” is not selected, this section will not appear on UI.

2b. If the user has selected “Event” as one of the Log Types. AWS S3 Bucket Credentials section will appear and the fields will be made mandatory, if “Event” is not selected, this section will not appear on UI.

2c. For “Alerts”, user should select either “Alert supported with SIEM API Credential” or “Alert supported with AWS S3 bucket credentials”, based on whether they have S3 bucket credentials or SIEM credentials.
i.	If the user has selected “Alert supported with SIEM API Credential” as one of the Log Types. SIEM API Credential section will appear and the fields will be made mandatory, otherwise this section will not appear on UI.

ii.	If the user has selected “Alert supported with AWS S3 bucket credentials” as one of the Log Types. AWS S3 bucket credentials section will appear, and the fields will be made mandatory, otherwise this section will not appear on UI.

2d. If all the log types are selected, all 3 sections will appear on UI.

so there is currently no supported CarbonBlack connector for Sentinel?
i.e. the connector in the Sentinel Content Hub is obsolete?


bdist_wheel doesn't allow any flags

In fact some of these flags are unneeded, instead distutils prefs should be used. So maybe custom steps are unneeded too.

@KOLANICH Please elaborate.
Are you unable to install lightgbm from Python wheel? What error is raised?

Are you unable to install lightgbm from Python wheel?

I'm unable to build a wheel using the prebuilt library, since no custom command class is implemented for that command.
https://github.com/Microsoft/LightGBM/blob/d8d01e39843c4e93d6e9cb9d2c17bc6d138f4975/python-package/setup.py#L275L279
IMHO these "custom cmd classes" inherited from the original ones are too dirty hacky approaches, instead setuptools should be redesigned into a graph of stages with possibility to insert an own stage between any 2.
IMHO these
https://github.com/Microsoft/LightGBM/blob/d8d01e39843c4e93d6e9cb9d2c17bc6d138f4975/python-package/setup.py#L185L198
flags shouldn't be used, instead it should always use the lib prebuilt with CMake.

I'm unable to build a wheel using the prebuilt library

Please share your use-case where you need this.

instead it should always use the lib prebuilt with CMake.

How to build, say, MPI version with pip in this case?

Please share your use-case where you need this.

It is more convenient for me to use CMake for building. I don't use Visual Studio for building, instead I use MinGW-w64 and Ninja as a low level build tool, all the libraries are situated in unexpected folders.

How to build, say, MPI version with pip in this case?

Just enable that option in CMakeCache.txt ?

. I don't use Visual Studio for building, instead I use MinGW-w64 and Ninja as a low level build tool

Just use --mingw option with correctly configured PATH to build with MinGW.
But why you need wheel file for this?

Just enable that option in CMakeCache.txt ?

Please elaborate. At present, I can just execute pip install lightgbm --install-option=--mpi. How to do it without those options?

Also, we already have the option to use prebuilt library file.
python setup.py install --precompile

Have you seen it?

But why you need wheel file for this?

Because I prefer to store wheels of working versions of binary libraries as backups. So if something goes wrong, I just install the old wheel.

How to do it without those options?

As usual when using CMake. Prebuild the library enabling USE_MPI and then install using the prebuilt library.

Just use --mingw option

this option is unneeded and should be removed. The compiler to be used is configured in distutils.cfg and your stuff should not override it.

Because I prefer to store wheels of working versions of binary libraries as backups

Ah, got it! However, this is very uncommon case because usually wheel distribution is made by developers, not users. However, if it's important for you, you can work with wheel file just like with ordinary archive: build library file and replace the default one in wheel.

As usual when using CMake. Prebuild the library with CMake enabling USE_MPI and then b8ild and install the package using the prebuilt library.

Do you agree, that it's more inconvenient way, compared with one-line command?

The compiler to be used is configured in distutils.cfg and your stuff should not override it.

This is legacy document.
Installing Python Modules (Legacy version)
Also, nothing is overridden while LightGBM installation.

This branch explicitly uses Visual Studio.

Uses, but not overrides.
LightGBM achieves it's best performance if compiled with VS, not MinGW. You can read more about it in FAQ Question 4 and 8. This is the reason why VS is used by default. But, as I've already said, you are able to build LightGBM with MinGW via one-line command.

In order to make a wheel without rebuilding the lib we need to fix the scripts.

I don't think so. As I've said earlier, building special versions of wheels is very rare need for usual users and moreover can be achieved by some manual steps.
In general, the current implementation of the installation process is well-tested by the time, comfortable for ordinary users and works without any additional modifications of source files. I think that it doesn't worth to steal from users all present facilities available through options in order to implement unclaimed feature.

However, you are very welcome to contribute the changes which will allow preserve the current comfort for ordinary users and enhance the installation process with additional features.

@StrikerRUS any updates for this issue? should it be in the feature request?

@guolinke According to the no references and comments for a quite long time, it seems that this feature is not demanded.

In general, the current implementation of the installation process is well-tested through the time, comfortable for ordinary users and works without any additional modifications of source files. I think that it doesn't worth to steal from users all present facilities available through options in order to implement unclaimed feature.


Scope Back-up Tasks Strategy

[ ] Document back-up task questions
[ ] Provide best practice recommendations
[ ] Jared to review Freshworks for strategy docs we can leverage

Team meeting with Jeremy Vernon to discuss data-backup options on Aug 25.

Closed as duplicate of #10


Where is grip_ready pose defined?

After fixing another minor issue in the panda_mvp_grasp.py file regarding logging, I'm facing this error:
$ rosrun mvp_grasping panda_mvp_grasp.py
[ INFO] - [/moveit_python_wrappers_1579259656982902166::core::RobotModel::buildModel::93]: Loading robot model 'panda'...
[ INFO] - [/moveit_python_wrappers_1579259656982902166::core::RobotModel::buildModel::93]: Loading robot model 'panda'...
[ INFO] - [/moveit_python_wrappers_1579259656982902166::planning_interface::MoveGroupInterface::MoveGroupInterfaceImpl::MoveGroupInterfaceImpl::178]: Ready to take commands for planning group panda_arm_hand.
No weight. Success? [1/0]0
Name of this experiment? asdasd
Press Enter to Start.
[ERROR] - [/moveit_python_wrappers_1579259656982902166::planning_interface::MoveGroupInterface::setNamedTarget::1690]: The requested named target 'grip_ready' does not exist
Traceback (most recent call last):
  File "/home/ap/mvp_ws/src/mvp_grasp/mvp_grasping/ros_nodes/panda_mvp_grasp.py", line 62, in <module>
    agc.go()
  File "/home/ap/mvp_ws/src/mvp_grasp/mvp_grasping/src/mvp_grasping/panda_base_grasping_controller.py", line 307, in go
    self.pc.goto_named_pose('grip_ready', velocity=0.25)
  File "/home/ap/mvp_ws/src/mvp_grasp/franka_control_wrappers/src/franka_control_wrappers/panda_commander.py", line 146, in goto_named_pose
    self.active_group.set_named_target(pose_name)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/moveit_commander/move_group.py", line 326, in set_named_target
    raise MoveItCommanderException("Unable to set target %s. Is the target within bounds?" % name)
moveit_commander.exception.MoveItCommanderException: Unable to set target grip_ready. Is the target within bounds?

My best guess is you having this pose defined somewhere else on your system, possibly via the MoveIt Setup Assistant. The same is probably true of  the drop_box pose.
Maybe we could set them inside PandaCommander instead of there, so they're available here as well for configuration?

I noticed few things:
to pass number of argument error we need to use self.active_group.remember_joint_values( 'grip_ready', pose). So there is no need to use self.
this_pose = self.active_group.get_current_pose(); doesn't work because of panda I believe. Because eef_link = self.active_group.get_end_effector_link() doesn't return anything. I could pass it by writing something like this this_pose = self.active_group.get_current_pose(end_effector_link = "panda_link8").pose
But now I'm confused because get_current_pose return a pose but in self.active_group.remember_joint_values we talk about join instead of pose.
So I thought to use something like this:
this_pose = self.active_group.get_current_joint_values()
self.active_group.remember_joint_values("grip_ready", this_pose) #)
self.active_group.remember_joint_values("drop_box", this_pose)
It throw following error:
catkin_ws/src/mvp_grasp/franka_control_wrappers/src/franka_control_wrappers/panda_commander.py", line 165, in goto_named_pose
self.active_group.set_named_target(pose_name)
File "/opt/ros/melodic/lib/python2.7/dist-packages/moveit_commander/move_group.py", line 326, in set_named_target
raise MoveItCommanderException("Unable to set target %s. Is the target within bounds?" % name)
moveit_commander.exception.MoveItCommanderException: Unable to set target grip_ready. Is the target within bounds?
Any Idea @aPonza @dougsm

I can see where my error was: I wasn't including the two joint values for the fingers. Anyways it's weird, because it goes to "ready" but not to "grip_ready"... and then again, after going to "ready" I get a similar error to the previous one about the end effector, so maybe that part still has to be fixed before anything works. Maybe @dougsm has made edits to their panda_moveit_config?

The only changes that I would have made to the panda_moveit_config would be to add the named poses to the srdf, and nothing else.
Regarding the other issues, I have to admit that I'm unsure.  However, do keep in mind that the franka_ros and panda_moveit_config code have undergone fairly major changes in the last ~12 months.  If you're having problems with the moveit interface, it might be better to ask over on their repo.
Also, see my above post with the ACRV panda control wrappers which may simplify things for you by abstracting some of the franka libraries.

I checked panda_moveit_config and I only see trajopt changes and a couple extra default poses, but nothing that would bother a missing end effector. Similarly, for franka_ros, I can see tens of commits regarding dual arm usage, the services being moved, but nothing which should affect the end effector. Are you referring to something in particular? I tried rebuilding with an updated franka_ros (both 0.7.0 and master) and panda_moveit_config (master) but nothing seemed to change.

@aPonza I fixed the end effector error. The error has something to do with group_name in the panda_commander.py. Here what I did:

def init(self, group_name='panda_arm_hand'):
self.robot = moveit_commander.RobotCommander()
self.scene = moveit_commander.PlanningSceneInterface()
self.groups = {}
self.active_group = None

  self.set_group("panda_arm")

Mmm you might actually want to change this line https://github.com/dougsm/mvp_grasp/blob/48330d45a135a5cf1bb058909ed1323be200069f/mvp_grasping/src/mvp_grasping/panda_base_grasping_controller.py#L170 to say 'panda_arm', instead of the other two edits you made.
It does do more than before, but since method go is not implemented in MVPGraspController it goes to call BaseGraspController's go which uses its own __velo_control_loop() instead of MVPGraspController's. Some methods need to be overridden, you can temporarily copy MVPGraspController's body in BaseGraspController's method.
This leads to tensorflow issues, which is what I suspected would happen installing tensorflow instead of tensorflow-gpu. Not sure this one is solvable:
[ERROR] - [/ap_grasping_velo::_invoke_callback::753]: bad callback: <bound method MVPGraspController.__update_callback of <__main__.MVPGraspController object at 0x7f5b41563550>>
Traceback (most recent call last):
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/topics.py", line 750, in _invoke_callback
    cb(msg)
  File "/home/ap/mvp_ws/src/mvp_grasp/mvp_grasping/src/mvp_grasping/panda_base_grasping_controller.py", line 226, in __update_callback
    res = self.entropy_srv()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 515, in call
    responses = transport.receive_once()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_base.py", line 727, in receive_once
    p.read_messages(b, msg_queue, sock)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 353, in read_messages
    self._read_ok_byte(b, sock)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 336, in _read_ok_byte
    raise ServiceException("service [%s] responded with an error: %s"%(self.resolved_name, str))
ServiceException: service [/grasp_entropy_node/update_grid] responded with an error: error processing request: Error while reading resource variable conv2d_transpose_3/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Resource localhost/conv2d_transpose_3/bias/N10tensorflow3VarE does not exist.
	 [[{{node conv2d_transpose_3/BiasAdd/ReadVariableOp}}]]

[...similar errors follow...]

@aPonza I'm in the same stage with following error:
the grasp_entropy_service node returns errors like:
[ERROR] [1581593428.562427]: Error processing request: 2 root error(s) found.
(0) Failed precondition: Error while reading resource variable cos_out/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Resource localhost/cos_out/bias/N10tensorflow3VarE does not exist.
[[{{node cos_out/BiasAdd/ReadVariableOp}}]]
[[sin_out/BiasAdd/_39]]
(1) Failed precondition: Error while reading resource variable cos_out/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Resource localhost/cos_out/bias/N10tensorflow3VarE does not exist.
[[{{node cos_out/BiasAdd/ReadVariableOp}}]]
0 successful operations.
0 derived errors ignored.
['Traceback (most recent call last):\n', '  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 629, in _handle_request\n    response = convert_return_to_response(self.handler(request), self.response_class)\n', '  File "/home/seivazi/catkin_ws/src/mvp_grasp/mvp_grasping/ros_nodes/grasp_entropy_node.py", line 128, in update_service_handler\n    points, angle, width_img, _ = predict(depth_crop, process_depth=False, depth_nan_mask=depth_nan_mask)\n', '  File "/home/seivazi/catkin_ws/src/mvp_grasp/ggcnn/src/ggcnn/ggcnn.py", line 67, in predict\n    pred_out = model.predict(depth.reshape((1, 300, 300, 1)))\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow/python/keras/engine/training.py", line 1078, in predict\n    callbacks=callbacks)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow/python/keras/engine/training_arrays.py", line 363, in model_iteration\n    batch_outs = f(ins_batch)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow/python/keras/backend.py", line 3292, in call\n    run_metadata=self.run_metadata)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1458, in call\n    run_metadata_ptr)\n', 'FailedPreconditionError: 2 root error(s) found.\n  (0) Failed precondition: Error while reading resource variable cos_out/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Resource localhost/cos_out/bias/N10tensorflow3VarE does not exist.\n\t [[{{node cos_out/BiasAdd/ReadVariableOp}}]]\n\t [[sin_out/BiasAdd/_39]]\n  (1) Failed precondition: Error while reading resource variable cos_out/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Resource localhost/cos_out/bias/N10tensorflow3VarE does not exist.\n\t [[{{node cos_out/BiasAdd/ReadVariableOp}}]]\n0 successful operations.\n0 derived errors ignored.\n']
@dougsm any suggestion?

$ git diff ggcnn/src/ggcnn/ggcnn.py
diff --git a/ggcnn/src/ggcnn/ggcnn.py b/ggcnn/src/ggcnn/ggcnn.py
index 396e627..8a49dc5 100644
--- a/ggcnn/src/ggcnn/ggcnn.py
+++ b/ggcnn/src/ggcnn/ggcnn.py
@@ -8,10 +8,17 @@ import tensorflow as tf
 from tensorflow.keras.models import load_model

 from dougsm_helpers.timeit import TimeIt
+from tensorflow.python.keras.backend import set_session

+session = tf.keras.backend.get_session()
+init = tf.global_variables_initializer()
+session.run(init)
+
+graph = tf.get_default_graph()
+
+set_session(session)
 MODEL_FILE = 'models/epoch_29_model.hdf5'
 model = load_model(path.join(path.dirname(__file__), MODEL_FILE))
-graph = tf.get_default_graph()

 TimeIt.print_output = False  # For debugging/timing

@@ -58,12 +65,16 @@ def process_depth_image(depth, crop_size, out_size=300, return_mask=False, crop_

 def predict(depth, process_depth=True, crop_size=300, out_size=300, depth_nan_mask=None, filters=(2.0, 1.0, 1.0)):
+    global sess
+    global graph
+
     if process_depth:
         depth, depth_nan_mask = process_depth_image(depth, crop_size, out_size, True)

     # Inference
     depth = np.clip((depth - depth.mean()), -1, 1)
     with graph.as_default():
+        set_session(session)
         pred_out = model.predict(depth.reshape((1, 300, 300, 1)))

     points_out = pred_out[0].squeeze()

as per this, which then leads to this:
[ERROR] - [/ap_grasping_velo::_invoke_callback::753]: bad callback: <bound method MVPGraspController.__update_callback of <__main__.MVPGraspController object at 0x7fd5dfc2fb10>>
Traceback (most recent call last):
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/topics.py", line 750, in _invoke_callback
    cb(msg)
  File "/home/ap/mvp_ws/src/mvp_grasp/mvp_grasping/src/mvp_grasping/panda_base_grasping_controller.py", line 226, in __update_callback
    res = self.entropy_srv()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 515, in call
    responses = transport.receive_once()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_base.py", line 727, in receive_once
    p.read_messages(b, msg_queue, sock)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 353, in read_messages
    self._read_ok_byte(b, sock)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 336, in _read_ok_byte
    raise ServiceException("service [%s] responded with an error: %s"%(self.resolved_name, str))
ServiceException: service [/grasp_entropy_node/update_grid] responded with an error: error processing request: Weights sum to zero, can't be normalized

Please note I'm not used to tensorflow, the code can be improved.

Ok, actually it seems to almost work, I did not have any pickable under the camera, but adding one started moving the robot and the eef went some centimeters off of it. Now it's likely just a matter of publishing the correct transform from the flange to the camera, which is bound to be wrong since we're using panda_arm instead of panda_arm_hand.
I'm guessing the division by zero errors are due to not having anything pickable, they could be handled more gracefully, I'll try tomorrow.

Looking forward to test your solution tomorrow. I also noticed about offset of transformation. I couldn't figure out where should I changed it.

Hi @aPonza I tried your changes to session but still get the same error as before  Error processing request: 2 root error(s) found....
Could you check once again what was your last changes? I can see for example a problem with global sess (which is unused).
Could you tell me which version of tensorflow and cuda are you using? I use tf 14 and Cuda 10 an wonder whether that is the problem.

I don't have a gpu on my workbench at the moment (hence

This leads to tensorflow issues, which is what I suspected would happen installing tensorflow instead of tensorflow-gpu

from here). The global sess is a mistake (use global session instead), might be useless since it's probably in the same thread as where the global variable is declared and overall is a copy-paste job at best.
I'm on tensorflow==1.14.0, no CUDA here since the GPU is elsewhere at the moment.
I have other changes on mvp_grasping/ros_nodes/panda_mvp_grasp.py and mvp_grasping/src/mvp_grasping/panda_base_grasping_controller.py but I thought they were mostly cosmetic (it's what I did instead of copying MVPController's body into the base controller). I'll send a PR with everything as soon as I can get the transform right on the final bit before the grasp, setting it up so that whoever uses panda_arm_hand gets it right still.
Can you maybe post the 2 errors you get, see if I had them and didn't realize?

Thank you for your point. The problem could be tensorflow-gpu. I'm now trying to play with different version of tf. The 2 Error is as below:
[ERROR] [1581673861.842248]: Error processing request: 2 root error(s) found.
(0) Unknown: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above.
[[{{node conv2d_1/Conv2D}}]]
(1) Unknown: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above.
[[{{node conv2d_1/Conv2D}}]]
[[sin_out/BiasAdd/_351]]
0 successful operations.
0 derived errors ignored.
['Traceback (most recent call last):\n', '  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 629, in _handle_request\n    response = convert_return_to_response(self.handler(request), self.response_class)\n', '  File "/home/seivazi/catkin_ws/src/mvp_grasp/mvp_grasping/ros_nodes/grasp_entropy_node.py", line 128, in update_service_handler\n    points, angle, width_img, _ = predict(depth_crop, process_depth=False, depth_nan_mask=depth_nan_mask)\n', '  File "/home/seivazi/catkin_ws/src/mvp_grasp/ggcnn/src/ggcnn/ggcnn.py", line 100, in predict\n    pred_out = model.predict(depth.reshape((1, 300, 300, 1)))\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow_core/python/keras/engine/training.py", line 908, in predict\n    use_multiprocessing=use_multiprocessing)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow_core/python/keras/engine/training_arrays.py", line 723, in predict\n    callbacks=callbacks)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow_core/python/keras/engine/training_arrays.py", line 394, in model_iteration\n    batch_outs = f(ins_batch)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow_core/python/keras/backend.py", line 3476, in call\n    run_metadata=self.run_metadata)\n', '  File "/home/seivazi/.local/lib/python2.7/site-packages/tensorflow_core/python/client/session.py", line 1472, in call\n    run_metadata_ptr)\n', 'UnknownError: 2 root error(s) found.\n  (0) Unknown: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above.\n\t [[{{node conv2d_1/Conv2D}}]]\n  (1) Unknown: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above.\n\t [[{{node conv2d_1/Conv2D}}]]\n\t [[sin_out/BiasAdd/_351]]\n0 successful operations.\n0 derived errors ignored.\n']

@aPonza with tensorflow-cpu I don't get the error as above anymore. but then I get a similar error as yours with ZeroDivisionError but for me is like even with object located under camera view.
seivazi/catkin_ws/src/mvp_grasp/mvp_grasping/ros_nodes/grasp_entropy_node.py", line 231, in update_service_handler\n    d_from_prev_view += np.clip(1 - (np.sqrt((self._xv - x)**2 + (self._yv - y)*2 + 0(cam_p.z - z)**2)/self.dist_from_prev_view_scale), 0, 1) * (1-kl)\n', 'ValueError: operands could not be broadcast together with shapes (72,68) (68,72) (72,68) \n']

The distance from previous view was an extra loss for the next best view calculation which favoured viewpoints which were different from the current viewpoint (hence the x,y,z distance calculation), though we didn't end up using this in order to simplify the controller.  You can comment out that line if you want and set d_from_prev_view to zero, or as I assume you've done, set the config value to a non-zero number.

with tensorflow-cpu I don't get the error as above anymore

You might have an incompatible cuDNN, maybe?

Thank you @aPonza
do you have any idea which version of cuDNN should I use? @dougsm

@seivazi @aPonza
I have replied in the other issue which was about tensorflow versions.  (I have also pushed some small updates that fix things that you were discussing).
Are the moveit related issues here fixed?
Now that I have some time, I am updating the mvp_grasping package to work with our in-house panda controllers (https://roboticvisionorg.github.io/) which should help abstract away a lot of the issues that you have been having, and will definitely then be working with the newest libfranka and moveit configs.

Cheers! I should probably push a PR with the changes before you start then.

@aPonza it will be great if you could push your changes any time soon. I have a problem with franka movement commands:
at panda_base_grasping_controller.py when I try to use self.pc.goto_named_pose('grip_ready', velocity=0.25) or any other goto pose method from panda commander (to bring the robot in top of the picking and dropping box) franka shakes a lot and stop. Somehow it works for one iteration and then such behaviour appear. I tried different poses but no chance yet.

The implemented panda controller is a demo one, they probably have a better controller on their own repository as Doug suggests. I suggest you use your own (or theirs), which is what I'll do as soon as I can finish these changes.

@aPonza I'm not sure I understand what you mean by the controller being a demo one.  We don't have anything particularly special control wise implemented here, just a nicer wrapper around the franka ros api and moveit.
@seivazi Those commands are just direct calls to moveit. There definitely should be nothing causing them to make the robot shake.  That sounds like it could be a much more low level problem with the robot.

I look to the (https://roboticvisionorg.github.io/). It is similar to the panda_commander.py in this git. It is normal Moveit commands so it should work as @dougsm pointed out.
Strange enough it always works in first run of the program but then it fails. I try to use rospy.sleep() or .stop but problem still stay the same. @dougsm do you use any specific moveit planner?
@aPonza have run the program for several iteration? is it working for you with moveit commands or do you use something else for moving the robot?

The controller can be improved, as you say yourself, and I haven't checked your company's implementation, I had assumed it would be an improved version. I apologize, it all came out rougher than I meant to.
I see the same oscillations/shaking Shahram sees, but it's independent of the run, it happens on the first as well. I resolved the issue in the past by enforcing some stricter soft joint limits: the oscillations happen because the robot is nearby the joint limits which triggers the safeties. You can do so in two ways:

(easy) change the limits in franka_description/robots/panda_arm.xacro;
(less easy) you can rebuild the JointModelGroup for Panda from scratch at runtime (I still haven't got around to doing it myself).

I'm referring to e.g. lines 64, 97 of that file, just using lower numbers for the soft limits. This however doesn't always work and sometimes it really seems to depend on the starting position of the arm and the starting position(s) of the object(s) to pick.

You are right it really depends on the arm position.
A the end I use RV driver for panda. https://roboticvisionorg.github.io/

Hi, thank you for your contribution. I am new to this error
moveit_commander.exception.MoveItCommanderException: Unable to set target grip_ready. Is the target within bounds?
Tried to follow what has been discussed here but still not work. I was wondering what would be the suggested solution to this "grip_ready" issue? Thank you so much!

Hi, thank you for your contribution. I am new to this error
moveit_commander.exception.MoveItCommanderException: Unable to set target grip_ready. Is the target within bounds?
Tried to follow what has been discussed here but still not work. I was wondering what would be the suggested solution to this "grip_ready" issue? Thank you so much!


Constent write by the Homarr container to disk

Environment
Docker
Version
0.14.2
Describe the problem
When the Homarr container is running it does write quite a lot to disk (around 20KB per minute) which is considerable when using something like eMMC that their lifespan is limited.
Logs
Nothing except the errors for pings that are failed for the apps that are down.
Context
No response
Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

20KB / minute is not significant. You can avoid disk wear using SSD cache or log.

@manuel-rw  Thank you for the answer.
I already have log2ram on but it seems no different how I can set it to use ram instead?

I don't know, this depends on many factors (your OS, your software, how you're running Homarr, ...).
Personally, I use TrueNAS with a cache and log to flush data as fast as possible to disk and flush it later to HDDs.
20Kbps would be more concerning, but 0.3Kbps is quite normal. Compare it to your computer: There will always be some activity, even with "nothing running".
I will close this issue now. I hope you understand that this is expected usage and we cannot really do much about it.


Fix README headings

They were not being displayed correctly due to missing spaces.

[ ] I've read and understood the Contributing guidelines and have done my best effort to follow them. [The file doesn't seem to exist.]
[x] I've read and agree to the Code of Conduct.
[x] I've been mindful about doing atomic commits, adding documentation to my changes, not refactoring too much.
[x] I've a descriptive title and added any useful information for the reviewer. Where appropriate, I've attached a screenshot and/or screencast (gif preferably).
[x] I've written tests to cover the new code and functionality included in this PR.
[ ] I've read, agree to, and signed the Contributor License Agreement (CLA). [Not going to sign a complicated legal document I don't fully understand to add a few spaces.]

PR Summary

e.g. New functionality for producing whatsits.

Related Issues

e.g. Fixes #206 and closes #230

Test strategy

e.g. Add tests around whatsit production.

Coverage remained the same at 29.268% when pulling ccdda4098535fc7ba9f486898ec1dbd7e27cbce1 on pieterdd:patch-1 into 1d28f686ba87ef8cc518a8e8a95a2c5631e9f9c1 on slackhq:master.

Looks obsolete now.


npm run react:15 fails on Windows

after running this:
git checkout v2.8.2
npm update

The following command fails on Windows
npm run react:15

The same commands work on my Mac.
On Windows, the error is:
c:\sources\enzyme> npm run react:15

><EMAIL_ADDRESS>react:15 c:\sources\enzyme
> rimraf node_modules/.bin/npm && npm run react:clean && npm i react@15 react-dom@15 create-react-class@15 <EMAIL_ADDRESS>&& npm instal
l

><EMAIL_ADDRESS>react:clean c:\sources\enzyme
> rimraf node_modules/react node_modules/react-dom node_modules/react-addons-test-utils node_modules/react-test-renderer

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "c:\\sources\\enzyme\\node_modules\\npm\\bin\\npm-cli.js" "i" "react@15" "react-dom@15" "create-
react-class@15" <EMAIL_ADDRESS>
npm ERR! node v7.4.0
npm ERR! npm  v2.14.8
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "c:\\sources\\enzyme\\node_modules\\npm\\bin\\npm-cli.js" "i" "react@15" "react-dom@15" "create-
react-class@15" <EMAIL_ADDRESS>
npm ERR! node v7.4.0
npm ERR! npm  v2.14.8
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "c:\\sources\\enzyme\\node_modules\\npm\\bin\\npm-cli.js" "i" "react@15" "react-dom@15" "create-
react-class@15" <EMAIL_ADDRESS>
npm ERR! node v7.4.0
npm ERR! npm  v2.14.8
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "c:\\sources\\enzyme\\node_modules\\npm\\bin\\npm-cli.js" "i" "react@15" "react-dom@15" "create-
react-class@15" <EMAIL_ADDRESS>
npm ERR! node v7.4.0
npm ERR! npm  v2.14.8
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     c:\sources\enzyme\npm-debug.log

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "react:15"
npm ERR! node v7.4.0
npm ERR! npm  v4.0.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>react:15: `rimraf node_modules/.bin/npm && npm run react:clean && npm i react@15 react-dom@15 create-react-class@15 react-test
<EMAIL_ADDRESS>&& npm install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>react:15 script 'rimraf node_modules/.bin/npm && npm run react:clean && npm i react@15 react-dom@15 create-react
-class@15 <EMAIL_ADDRESS>&& npm install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the enzyme package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rimraf node_modules/.bin/npm && npm run react:clean && npm i react@15 react-dom@15 create-react-class@15 <EMAIL_ADDRESS>&&
 npm install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs enzyme
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls enzyme
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\sources\enzyme\npm-debug.log

Why are you running npm 2 on node 7? node 7 ships with npm 4, iirc.

My npm was close to up-to-date is up to date (4.someting). I don't know where the versions come from. I have updated npm to the latest:
npm --version
4.6.1

and I stil get the same error:
c:\sources\enzyme> npm run react:15

><EMAIL_ADDRESS>react:15 c:\sources\enzyme
> rimraf node_modules/.bin/npm && npm run react:clean && npm i react@15 react-dom@15 create-react-class@15 <EMAIL_ADDRESS>&& npm instal
l

><EMAIL_ADDRESS>react:clean c:\sources\enzyme
> rimraf node_modules/react node_modules/react-dom node_modules/react-addons-test-utils node_modules/react-test-renderer

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "c:\\sources\\enzyme\\node_modules\\npm\\bin\\npm-cli.js" "i" "react@15" "react-dom@15" "create-
react-class@15" <EMAIL_ADDRESS>
npm ERR! node v7.4.0
npm ERR! npm  v2.14.8
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'internal/fs'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "c:\\sources\\enzyme\\node_modules\\npm\\bin\\npm-cli.js" "i" "react@15" "react-dom@15" "create-
react-class@15" <EMAIL_ADDRESS>
npm ERR! node v7.4.0
npm ERR! npm  v2.14.8
npm ERR! code MODULE_NOT_FOUND

<<TRUNCATED HERE>>

Since it's still printing npm ERR! npm  v2.14.8  , this suggests that your node installation is somehow broken.

It turns out this exact sequence causes the issue:
rimraf node_modules
npm update
npm run react:15

but this sequence works fine:
rimraf node_modules
npm run react:15

Installing the project dependencies seem to have a side effect. I have checked the log output of the npm install command and at some point I see this:
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

Hmm - there is a dependency that installs npm 2, which is why rimraf node_modules/.bin/npm is part of npm run react:15. However, it's possible that that fix (5cece32a721f28f19cccf0f92a77d0db2cd03816) doesn't work on windows. Before running the react:15 command, what are the contents of node_modules/.bin (specifically looking for npm)?

The contents of npm.cmd is
@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe"  "%~dp0\..\npm\bin\npm-cli.js" %*
) ELSE (
  @SETLOCAL
  @SET PATHEXT=%PATHEXT:;.JS;=;%
  node  "%~dp0\..\npm\bin\npm-cli.js" %*
)

and running npm --version from that folder print out:
c:\sources\enzyme\node_modules\.bin> npm --version
2.14.8

whereas here I get:
c:\sources\enzyme> npm --version
4.2.0

more info:
c:\sources\enzyme> where npm
C:\Program Files\nodejs\npm
C:\Program Files\nodejs\npm.cmd

c:\sources\enzyme> "C:\Program Files\nodejs\npm.cmd" --version
4.2.0

aha, it sounds like npm.cmd is the issue. If you remove that file and rerun npm run react:15, does it work?

Running  rimraf node_modules\.bin\npm does not delete npm.cmd.
Yes after deleting npm.cmd it works.

Awesome, thanks.


feat: first major

github issue

[.] add docs :

[ ] isntall
[○] OPTS :

[x] ssh
[ ] maps

[○] feat :

[x] list
[ ] screenshot

[○] requirement :

[ ] install
[x] list

[x] get list issue, body can update,
[x] feature :

[x] update issue (body)
[x] list history issue
[x] delete history issue
[x] delete issue
[x] add author
[x] add label
[x] edit issue by file number

[x] OPTS :

[x] list info
[x] mapping

[x] conflict :

[x] git config pull.rebase false
[x] git pull
[x] use plugin merge conflict to change
[x] git commit

[x] refactor :

[x] split :

[x] get issue
[x] issue data to header info then add update
[x] helper

git

[x] git add select
[x] gsv
[x] gsp
[x] flow
[x] merge
[x] conflict

Tes comment

Jdldjdjffg
Ggg
G
G
Ihfibdibfknfi.ff
If
.fi.fir
Infi.fi
Fk.fif
.fif
If
If


Accessibility fix

Accessibility can suffer with outline: none.
Changed to outline: 0; as recommended here:
http://www.outlinenone.com/

LGTM.
@addyosmani You know more about this than I do. Thoughts?

oh TIL :) :+1:


I can't open the extensions, i'm running VS Code on Zorin 16.2

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

/duplicate


Not display warnings

A couple of wanrings are displayed now, they are confusing.

/usr/lib/python3.11/site-packages/urllib3/connectionpool.py:1045: InsecureRequestWarning: Unverified HTTPS request is being made to host 'translate.fedoraproject.org'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(
/usr/lib/python3.11/site-packages/urllib3/connectionpool.py:1045: InsecureRequestWarning: Unverified HTTPS request is being made to host 'cloud.memsource.com'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

Better to hide them

Maybe change this to false.


Click between two epochs in timeline removes highlight

Steps to reproduce

Click between two epochs

Observed behavior
No epoch is highlighted, but also no event is fired to load a different epoch.
Expected behavior
The highlight should stay consistent and not be removed. Or if removed, then the loaded data in matrix must be removed, too.

Some other related bugs:

Clicking a small range deselects single epoch:

Done with last PR.


add unlink/unlinkat parsing to strace.go, and add Delete field to FileInfo

Fixes #250

Awesome!
There is a schema for the BigQuery import as well - see https://github.com/ossf/package-analysis/blob/main/function/loader/schema.json