text:
Update CI test matrix

Major updates:

Drop test or CUDA, as there is no GPU on CI and installation on ruby
Add test on Windows.
Update ubuntu version from ubuntu-18.04 to 20.04
add test for torch 1.10
update MMCV link from 1.x.0 to 1.x
add --binary-only to mmcv options to avoid compilation in CI

Minor updates include:

change path-ignore to path-include
remove support for torch 1.3 (drop support for 1.3 has been announced on the home page for 3+ months)
change torch version from 1.x.0 to 1.x.latest
change uniform version python 3.7 to 3.7~3.9, attached to different torch version
remove the installation of pillow, because it's for torchvision below 0.5, whose support is dropped.
update mmcv to latests version

I met same problem as described here
https://github.com/facebook/jest/issues/9413

After amount of testing, on windows, when running multiple commands, only when the last one exit error, the test will fail. So I split unit test and coverage

Reopened in to #732 and #734

repo: open-mmlab/mmediting

license_type: permissive

license_source: github-api


text:
Messenger GUI

Describe the solution you'd like
Still requires a GUI. A messenger style format would be cool. Firecamp is a good example.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

GitHub release
1.0.0

Your semantic-release bot :package::rocket:

source: gharchive/issue

authors: mattbford openrpc-bastion

repo: open-rpc/logs-react


text:
Feature: Fix feed asides on scroll

Type of feature
🍕 Feature
Current behavior
Currently, when scrolling the feed, the filters and user card scrolls with the content as well

Suggested solution
We can improve the UX by fixing them (fix the position when scrolling). That way, it's easier to filter repositories and have your user card on sight :slightly_smiling_face:
Additional context
No response
Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

Hi, I would like to work on this feature.
Can you assign me?

Hi @thehashmap, thanks for your interest in working on this issue.
I would like to hear your thoughts @bdougie before someone starts working on this :slightly_smiling_face:

I would like to hear your thoughts @bdougie before someone starts working on this 🙂

Separate column scrolling is ideal and exactly how it works on Twitter. We should do what works and think about innovating on this later. It would be nice to hear your take on this prior to jumping on this @thehashmap.
I would also like to address this issue first, https://github.com/open-sauced/insights/issues/1336. Anyone that wo
Please review the CONTIBUTING.md for info on how to assign yourself to the issue.
cc @isabensusan for future reference.

Separate column scrolling is ideal and exactly how it works on Twitter. We should do what works and think about innovating on this later. It would be nice to hear your take on this prior to jumping on this @thehashmap.

I agree with you. This is a nice feature to add.

I would also like to address this issue first, #1336. Anyone that wo

I see a PR has already been created for it. Should I wait for it to get merged before starting on this?

Please review the CONTIBUTING.md for info on how to assign yourself to the issue.
cc @isabensusan for future reference.

Sure!

I see a PR has already been created for it. Should I wait for it to get merged before starting on this?

Ideally, yeah. Otherwise, you might end up with a lot of conflicts :upside_down_face:

Can I work on this?

Can I work on this?

Yes

.take

authors: bdougie dev-phantom takanome-dev thehashmap

repo: open-sauced/insights


text:
Elemental 4.x support

Also changing language defaults to English,
and supporting German through a lang file :)

Ping :)

Is this meant to be hosted on the open-sausage repo? Shouldn't the PR be against the original repo?

lol, fail...

https://github.com/derralf/silverstripe-elemental-call-to-action/pull/1

source: gharchive/pull-request

authors: chillu maxime-rainville


text:
-burn -> -rs

Very minor - what do you think about renaming this repo to fsrs-optimizer-rs? The crate name would remain the same, and GitHub should automatically redirect references to the old name.

OK, wait a minute.

Thanks, looks good :+1:

authors: L-M-Sherlock dae


text:
Instrumentation framework does not encourage use of SpanBuilder-set attributes

From https://github.com/open-telemetry/opentelemetry-auto-instr-java/pull/195#discussion_r391778237:
I would force the user of the instrumentation framework (with user I mean the one who implements concrete classes here) to provide the request already in startSpan, so that all attributes are set on the builder and thus available to samplers (and onStart callbacks of SpanProcessors). See spec: https://github.com/open-telemetry/opentelemetry-specification/blob/4ab7c2fb4964c14fe972b03b5bb6825573bafb24/specification/api-tracing.md#span-creation

Attributes - A collection of key-value pairs, with the same semantics as the ones settable with Span::SetAttributes. Additionally, these attributes may be used to make a sampling decision as noted in sampling description. An empty collection will be assumed if not specified.
Whenever possible, users SHOULD set any already known attributes at span creation instead of calling SetAttribute later.

Hi @Oberon00! The reason we aren't setting span attributes on the span builder (yet) is because the current OpenTelemetry API release (0.2.0) does not support that. Once 0.3.0 is released, we are planning to address this. This work is tracked in #76.

Makes sense. I did not consider that you can only use released versions. I guess the opentelemetry-java package does not get released very often 😅

Closing, hope that's ok, just added #303 to track this

Hi, we run into similar issue and wish to know the URL when doing sampling decision.
But it seems like with the change in https://github.com/open-telemetry/opentelemetry-auto-instr-java/pull/348/files , the http.url is still not available for example in the Servlet3Advice, the DECORATOR which adds the http.url attribute is not run until the span is started.
Wondering if it's feasible to change the DECORATOR to allow a beforeSpanStart or even change the onRequest and onConnection to take SpanBuilder and have them executed before the span is started?
Many thanks in advance!

Hi @patsonluk, can you open a new issue for this? It's a good point.

Hi @patsonluk, can you open a new issue for this? It's a good point.

For sure #388 :)

authors: Oberon00 patsonluk trask


text:
[collector] Add ability to enable GOMEMLIMIT

This PR starts the potential deprecation processor of the memory ballast extension.
A new flag, useGOMEMLIMIT is added that, when enabled, removes the memory ballast extension from the config and adds a GOMEMLIMIT env var.
Added a new CI scenario and a new example.
Related to https://github.com/open-telemetry/opentelemetry-helm-charts/issues/891 and https://github.com/open-telemetry/opentelemetry-collector/issues/8343

@dmitryax please review


text:
test(sdk-metrics-base): test metric instrument interfaces

Which problem is this PR solving?
Test coverage on metric instrument interfaces.
Please delete options that are not relevant.

[x] test coverage

How Has This Been Tested?

[x] Counter
[x] UpDownCounter
[x] Histogram
[x] ObservableCounter
[x] ObservableUpDownCounter
[x] ObservableGauge

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[x] Documentation has been updated

@dyladan friendly ping :)

repo: open-telemetry/opentelemetry-js


text:
Open a project board in the repo

To track sig items we should use a project board with the various tasks and owners.
https://github.com/open-telemetry/opentelemetry-lambda/projects?query=is%3Aopen

With the current level of involvement, I don't think we need this right now.  We can revisit later though.

authors: cartersocha tylerbenson

repo: open-telemetry/opentelemetry-lambda


text:
CI: Toys 0.12.0 causing release failures

CI started pulling 0.12.0 and was failing to find yard.
Confirmed that this was the cause of the release failures by pinning the retry to 0.11.5
https://github.com/open-telemetry/opentelemetry-ruby/pull/910
Hey @dazuma is this something you want to look into?  Otherwise I might just pin everything to 0.11.5 until we can dedicate some time to the release process.

https://github.com/open-telemetry/opentelemetry-ruby/runs/3343455325?check_suite_focus=true
[2021-08-16 19:03:02  INFO]  Gem built
[2021-08-16 19:03:02  INFO]  Building opentelemetry-instrumentation-action_view 0.1.0 docs...
[2021-08-16 19:03:02  INFO]  ["/opt/hostedtoolcache/Ruby/2.7.4/x64/bin/ruby", "--disable=gems", "/opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-0.12.0/bin/toys", "yardoc"]
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies....
Fetching rake 12.3.3
Installing rake 12.3.3
Fetching concurrent-ruby 1.1.9
Fetching minitest 5.14.4
Installing minitest 5.14.4
Installing concurrent-ruby 1.1.9
Fetching zeitwerk 2.4.2
Installing zeitwerk 2.4.2
Fetching builder 3.2.4
Installing builder 3.2.4
Fetching erubi 1.10.0
Installing erubi 1.10.0
Fetching racc 1.5.2
Installing racc 1.5.2 with native extensions
Fetching crass 1.0.6
Installing crass 1.0.6
Fetching rack 2.2.3
Installing rack 2.2.3
Fetching nio4r 2.5.8
Installing nio4r 2.5.8 with native extensions
Fetching websocket-extensions 0.1.5
Fetching marcel 1.0.1
Installing websocket-extensions 0.1.5
Fetching mini_mime 1.1.0
Installing marcel 1.0.1
Installing mini_mime 1.1.0
Fetching public_suffix 4.0.6
Using bundler 2.2.25
Fetching thor 1.1.0
Installing public_suffix 4.0.6
Installing thor 1.1.0
Fetching ast 2.4.2
Fetching byebug 11.1.3
Installing ast 2.4.2
Fetching coderay 1.1.3
Installing byebug 11.1.3 with native extensions
Installing coderay 1.1.3
Fetching rexml 3.2.5
Installing rexml 3.2.5
Fetching docile 1.4.0
Fetching hashdiff 1.0.1
Installing docile 1.4.0
Fetching jaro_winkler 1.5.4
Installing hashdiff 1.0.1
Installing jaro_winkler 1.5.4 with native extensions
Fetching json 2.5.1
Fetching method_source 1.0.0
Installing method_source 1.0.0
Installing json 2.5.1 with native extensions
Using opentelemetry-api 1.0.0.rc3 from source at `../../api`
Fetching parallel 1.20.1
Installing parallel 1.20.1
Fetching rainbow 3.0.0
Installing rainbow 3.0.0
Fetching ruby-progressbar 1.11.0
Installing ruby-progressbar 1.11.0
Fetching unicode-display_width 1.6.1
Installing unicode-display_width 1.6.1
Fetching simplecov-html 0.10.2
Installing simplecov-html 0.10.2
Fetching yard 0.9.26
Fetching i18n 1.8.10
Installing i18n 1.8.10
Installing yard 0.9.26
Fetching tzinfo 2.0.4
Installing tzinfo 2.0.4
Fetching rack-test 1.1.0
Installing rack-test 1.1.0
Fetching sprockets 4.0.2
Installing sprockets 4.0.2
Fetching nokogiri 1.12.3 (x86_64-linux)
Installing nokogiri 1.12.3 (x86_64-linux)
Fetching websocket-driver 0.7.5
Installing websocket-driver 0.7.5 with native extensions
Fetching mail 2.7.1
Installing mail 2.7.1
Fetching appraisal 2.2.0
Installing appraisal 2.2.0
Fetching addressable 2.8.0
Installing addressable 2.8.0
Fetching parser 3.0.2.0
Fetching crack 0.4.5
Installing crack 0.4.5
Fetching pry 0.13.1
Installing parser 3.0.2.0
Installing pry 0.13.1
Using opentelemetry-common 0.19.1 from source at `../../common`
Using opentelemetry-instrumentation-base 0.18.2 from source at `../base`
Using opentelemetry-semantic_conventions 1.6.0 from source at `../../semantic_conventions`
Fetching simplecov 0.17.1
Fetching activesupport 6.1.4
Installing simplecov 0.17.1
Installing activesupport 6.1.4
Fetching yard-doctest 0.1.17
Installing yard-doctest 0.1.17
Fetching loofah 2.12.0
Installing loofah 2.12.0
Fetching webmock 3.7.6
Installing webmock 3.7.6
Fetching rubocop 0.73.0
Using opentelemetry-instrumentation-action_view 0.1.0 from source at `.`
Using opentelemetry-sdk 1.0.0.rc3 from source at `../../sdk`
Fetching pry-byebug 3.9.0
Installing pry-byebug 3.9.0
Installing rubocop 0.73.0
Fetching rails-html-sanitizer 1.3.0
Installing rails-html-sanitizer 1.3.0
Fetching rails-dom-testing 2.0.3
Installing rails-dom-testing 2.0.3
Fetching globalid 0.5.2
Installing globalid 0.5.2
Fetching activemodel 6.1.4
Installing activemodel 6.1.4
Fetching actionview 6.1.4
Installing actionview 6.1.4
Fetching activejob 6.1.4
Installing activejob 6.1.4
Fetching activerecord 6.1.4
Installing activerecord 6.1.4
Fetching actionpack 6.1.4
Installing actionpack 6.1.4
Fetching actioncable 6.1.4
Fetching actionmailer 6.1.4
Installing actioncable 6.1.4
Installing actionmailer 6.1.4
Fetching railties 6.1.4
Fetching sprockets-rails 3.2.2
Installing railties 6.1.4
Installing sprockets-rails 3.2.2
Fetching activestorage 6.1.4
Installing activestorage 6.1.4
Fetching actionmailbox 6.1.4
Installing actionmailbox 6.1.4
Fetching actiontext 6.1.4
Installing actiontext 6.1.4
Fetching rails 6.1.4
Installing rails 6.1.4
Bundle updated!
Toys::Utils::Gems::GemfileUpdateNeededError: Required gem not available in the bundle: "yard", .
Please update your Gemfile "/home/runner/work/opentelemetry-ruby/opentelemetry-ruby/Gemfile".
     48: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-0.12.0/bin/toys:11:in `<main>'
     47: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:456:in `run'
     46: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/errors.rb:71:in `capture_path'
     45: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:464:in `block in run'
     44: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:496:in `run_tool'
     43: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:520:in `execute_tool_in_context'
     42: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:520:in `catch'
     41: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:521:in `block in execute_tool_in_context'
     40: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:552:in `block in make_executor'
     39: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_middleware/show_help.rb:238:in `run'
     38: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:552:in `block in make_executor'
     37: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_middleware/show_root_version.rb:67:in `run'
     36: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:552:in `block in make_executor'
     35: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_middleware/handle_usage_errors.rb:39:in `run'
     34: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:510:in `block in execute_tool_in_context'
     33: /home/runner/work/opentelemetry-ruby/opentelemetry-ruby/.toys/yardoc.rb:13:in `run'
     32: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_mixins/exec.rb:400:in `exec_tool'
     31: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:309:in `exec_proc'
     30: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:958:in `execute'
     29: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:989:in `start_with_controller'
     28: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:1012:in `start_fork'
     27: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:1023:in `run_fork_func'
     26: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:1023:in `catch'
     25: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/exec.rb:1027:in `block in run_fork_func'
     24: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_mixins/exec.rb:681:in `block in _make_tool_caller'
     23: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:456:in `run'
     22: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/errors.rb:71:in `capture_path'
     21: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:464:in `block in run'
     20: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:496:in `run_tool'
     19: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:520:in `execute_tool_in_context'
     18: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:520:in `catch'
     17: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:521:in `block in execute_tool_in_context'
     16: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:552:in `block in make_executor'
     15: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_middleware/show_help.rb:238:in `run'
     14: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:552:in `block in make_executor'
     13: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_middleware/show_root_version.rb:67:in `run'
     12: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:552:in `block in make_executor'
     11: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_middleware/handle_usage_errors.rb:39:in `run'
     10: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/cli.rb:510:in `block in execute_tool_in_context'
      9: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-0.12.0/lib/toys/templates/yardoc.rb:421:in `block (3 levels) in <class:Yardoc>'
      8: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/standard_mixins/gems.rb:61:in `gem'
      7: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:148:in `activate'
      6: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:213:in `synchronize'
      5: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:213:in `synchronize'
      4: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:149:in `block in activate'
      3: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:152:in `rescue in block in activate'
      2: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:240:in `handle_activation_error'
      1: /opt/hostedtoolcache/Ruby/2.7.4/x64/lib/ruby/gems/2.7.0/gems/toys-core-0.12.0/lib/toys/utils/gems.rb:273:in `report_activation_error'
Error during tool execution!
    Toys::Utils::Gems::GemfileUpdateNeededError: Required gem not available in the bundle: "yard", .
Please update your Gemfile "/home/runner/work/opentelemetry-ruby/opentelemetry-ruby/Gemfile".
    in config file: /home/runner/work/opentelemetry-ruby/opentelemetry-ruby/.toys/yardoc.rb:13
    while executing tool: "yardoc _build"
    with arguments: []
Error: Process completed with exit code 1.

Oh dear, yes feel free to pin to 0.11.5 while I look at it.

I found the bug in Toys 0.12.0 and will have a patch released shortly.

authors: dazuma robertlaurin

repo: open-telemetry/opentelemetry-ruby

license_source: bigquery


text:
Add support for fetching a particular repo tag

Is your feature request related to a problem? Please describe.
Add a way to fetch a repository at a specific git tag.  For example weaver registry resolve -r  https://github.com/open-telemetry/semantic-conventions.git --tag v1.25.0
Describe the solution you'd like
By specifying a tag weaver should not fetch main but instead the tag specified.
Describe alternatives you've considered
Currently fetching the repository manually and checking out the tag requested.

Closing in favor of #182

repo: open-telemetry/weaver


text:
Graceful way of handling licensing

Graceful way of handling licensing

A query from China sales team, how to setup licensing if script is run against physical ports and then vm ports

stale issue

repo: open-traffic-generator/snappi-ixnetwork

license: MIT


text:
[BUG-FIX] There is a bug in the rw_spinlock.

There is a bug in the rw_spinlock. Each time atomic_compare_exchange_strong(object, expected, desired) is executed, the value of object is assigned to expected, so the value of expected needs to be reset each time.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant wangzhi-art

repo: open-vela/nuttx


text:
[feat] Hope to add code block folding buttons

Currently, the webpage code occupies a large amount of space. It would be helpful to add an option to collapse the code. This way the response can appear shorter, as sometimes when there's a lot of code, scrolling through the chat takes a long time.

Now:

The appearance of hope (ChatGPT-NextWeb):

#4427  similarly, I asked for code line wrapping because it's unreadable on phones, tablets and other vertical screens.

repo: open-webui/open-webui


text:
fix: image generation broken by config persistence

Pull Request Checklist

[x] Target branch: Pull requests should target the dev branch.
[x] Description: Briefly describe the changes in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[x] Testing: Have you written and run sufficient tests for the changes?
[x] Code Review: Have you self-reviewed your code and addressed any coding standard issues?

Description
Fixes a bad refactor during the config persistence PR. Tested locally.

Thanks!

authors: cheahjs tjbck


text:
使用java sdk存数据的时候，有时候会有json格式数据，里面带有换行符\n，这时候存入出错

Describe the bug（Bug 描述）
有时候需要存json格式数据，当json格式不换行时可以用java sdk正常存入，当json带有换行符\n时则不行。
如下两个字符串，s1不能存入，但s2可以正常存入。
String s1 = "{\n" +
"  "deviceId": 2166,\n" +
"  "dataTime": 1694482947700,\n" +
"  "values":{\n" +
"     "temperature": "hhh"\n" +
"  }\n" +
"}";
String s2 = "{"deviceId": 2166,"dataTime": 1694482947700,"values":{"temperature": "hhh"}}";
To Reproduce（Bug 复现步骤）
No response
Expected behavior（期望结果）
No response
Screenshots（屏幕截图）
No response
Logs（完整的错误日志）
No response
Additional context（其他的一些补充内容）
No response

InfluxDB 的SDK自身问题，但这个问题社区打算在自研SDK中解决

track by #746

repo: openGemini/openGemini


text:
us-il-peoria

Peoria County
http://www.peoriacounty.org/gis

Address data here http://gis.peoriacounty.org/arcgis/rest/services/DP/CommunityLayers/MapServer/64
Also need to add ?f=json to end of url for view in browser.
I need some help with the regex on the prop_street field
"conform": {
        "type": "geojson",
        "number": {
            "function": "regexp",
            "field": "prop_street",
            "pattern": "^([0-9]+)"
        },
        "street": {
            "function": "regexp",
            "field": "prop_street",
            "pattern": "^(?:[0-9]+ )(.*)",
            "replace": "$1"
        },
        "city":"CITY",
        "postcode": "PZIP"
    }

This isn't great because it gives back street values like W WILLOW KNOLLS UNIT 82D RD. The units value is mixed in with the street name and the street type.

Wow, that is some messy data.  That's probably as good as it's going to get at least with the regexp function (insofar as I understand its abilities).  Could you add unit to it yet to grab the ones that are postfixed?

authors: davidchiles jalbertbowden trescube

repo: openaddresses/openaddresses


text:
'json_object' is not of type 'object' - 'response_format'

Hi,
I used this script:
$response = $client->chat()->create([
    'model' => 'gpt-3.5-turbo-1106',
    'max_tokens' => 6,
    'temperature' => 0.2,
    'response_format' => 'json_object',
    'messages' => [
        ['role' => 'user', 'content' => $prompt],
    ],
]);

I got the error:
Uncaught OpenAI\Exceptions\ErrorException: 'json_object' is not of type 'object' - 'response_format' in c:\xampp\htdocs\OpenAI\vendor\openai-php\client\src\Transporters\HttpTransporter.php:131
What is the proper way to use response_format and is it even supported by the library?
Thanks.

Hi @simohammedhttp
This error is thrown by the API because your request in wrong. It should be 'response_format' => ['type' => 'json_object'],

authors: gehrisandro simohammedhttp

repo: openai-php/client


text:
Bug in baselines/deepq/replay_buffer.py

Hi:
I found a bug in this line in replay_buffer.py. Since this line in common/segment_tree.py has already subtracted 1 of 'end', the recursion will run forever when end=0 (after substract 1, end=-1) passed to the reduce method in SegmentTree.

Hi:
I found a bug in this line in replay_buffer.py. Since this line in common/segment_tree.py has already subtracted 1 of 'end', the recursion will run forever when end=0 (after substract 1, end=-1) passed to the reduce method in SegmentTree.

hi, can you help me explain why here need to subtracted 1.  (len(self._storage - 1)) is already subtracted 1. For example, if i want to know the sum of 0-7. By subtracted twice ,it will be 0-6. why?
Thank you!

authors: EthanCodesss RukawaKaede

repo: openai/baselines

license: mit


text:
PPO2: Non-deterministic behavior when setting --num_timesteps

When I change the --num_timesteps argument for PPO2, even after setting the random seed and with all other hyperparameters the same, I get different performances after a few updates. Although each individual run is entirely deterministic, for some reason changing the length of training affects the reproducibility of the results. I'm on commit fa37beb.
For example, running PPO2 for 4 updates:
python -m baselines.run --env=Hopper-v2 --seed=0 --num_env=1 --nsteps=2048 --num_timesteps=8192
I get these episode rewards:
| eprewmean          | 16.5         |
| eprewmean          | 21.1         |
| eprewmean          | 23.1         |
| eprewmean          | 31.4         |

And then running it for 5 updates:
python -m baselines.run --env=Hopper-v2 --seed=0 --num_env=1 --nsteps=2048 --num_timesteps=10240
I get these:
| eprewmean          | 16.5         |
| eprewmean          | 21.1         |
| eprewmean          | 24.1         |
| eprewmean          | 32.9         |
| eprewmean          | 54.6         |

Notice that the performances have diverged at the 3rd update, despite the identical hyperparameters and seed. I believe this is a bug, but I cannot figure out where it is coming from.

I realized this behavior is due to the annealed learning rate, not a bug.


text:
Expanding the documentation

Are there any plans to write more documentation for using this API? Going through the code there's a lot of useful stuff in here but only the occasional comment to help you use it. I've noticed comments such as "See README.md for a description of the logging API." on logger.py, but I can't find any reference to logging on any of the README files. The new PPO/TRPO stuff has zero documentation supplied with it. It is possible to work it all out from the code but a little more description would make baselines hugely more accessible, especially for people newer to python and/or RL.

There is test code in logger.py, which I love, but it doesn't work and there is a lack of comments. Not sure if I should open a new issue just for this, though. Without more comments in there I can't figure out what that 'with session' statement is supposed to be, although it doesn't seem to be necessary.
baselines is up-to-date with the github repo.
Mac OS X 10.9.5
$ python3 --version
Python 3.6.2
$ python3 ./logger.py
hi
should appear
Traceback (most recent call last):
File "./logger.py", line 309, in
_demo()
File "./logger.py", line 292, in _demo
with session(dir=dir):
NameError: name 'session' is not defined

logger.py -- tests works for me.
More comments -- surely useful, but small code you can scroll through is useful as well.

authors: Bleyddyn benibienz olegklimov


text:
Will text300M be available on Ollama for local GPU acceleration on Mac?

That's it!

As of December 2024, Ollama supports GPU acceleration on Mac devices using the Metal API, which is compatible with Apple Silicon (M1 or later) and certain AMD Radeon GPUs. However, support for specific models like text300M depends on the model's compatibility with Ollama's GPU acceleration capabilities.
For instance, a user reported that Ollama does not utilize the Radeon RX 6900 GPU on their Mac Pro system, despite the GPU supporting Metal 3.
GITHUB
Additionally, Ollama's official documentation specifies that it supports Nvidia GPUs with compute capability 5.0 and above, and certain AMD GPUs on Linux.
GITHUB
Given that text300M is a model developed by Meta (formerly Facebook) and is not listed among the officially supported models in Ollama's documentation, it is unlikely that text300M will be available for local GPU acceleration on Mac through Ollama.
For more information on running large language models on your Mac with Ollama, you might find the following video helpful:
https://youtu.be/q6GWkLXJ3Mw

@JohnDoe2025-ai : OpenAI's shape-e and text300m are not created by Meta (formerly Facebook).  Someone could always add them, right?

You're correct that OpenAI's models, such as Shap-E and Text-300M, were created by OpenAI, not Meta. However, if you're referring to someone mistakenly attributing them to Meta, it's an easy misunderstanding to correct with proper citations and clarification of the creators.
If the context involves a platform or database, there's always the possibility of adding or editing the information to clarify the true origins of these models, provided that the platform allows edits and adheres to factual accuracy. For instance:

Platforms like Wikipedia: If someone misattributes information on a public platform like Wikipedia, you can edit it with proper references to OpenAI's documentation or publications.

Private or Public Databases: If the misattribution occurs in a technical database or dataset, administrators or contributors can correct and update it with verified information.

Would you like assistance with drafting a correction or verifying sources for accurate attribution?

repo: openai/shap-e


text:
Open tabs on collapsed container

Hi
I have a container who start closed when the pages load. When I expand the container, the tabs doesn't works
Steps:
1.- A Container (div) closed (by jquery on document ready)
2.- 4 tabs inside that container
3.- click a button to open the Container
4.- the tabs doesn't answer
5.- when I resize the page the tabs shows automatically (and works)
I try to call the function fakewaffle.responsiveTabs(['xs', 'sm']) in the 3rd step, but that duplicate the tabs.
Also, there is a way to call the function like $("#mytabs").responsiveTabs(['xs', 'sm']) [or a way to destroy it?]
Thanks!

Can you provide a jsfiddle or something? I'm not sure what you're doing.

Closing do to no response

authors: BredeBS openam

repo: openam/bootstrap-responsive-tabs


text:
Example for Shiny app reading HTTP headers

With the new container initialization functionality, username and access groups are no longer set as ENVs in the container, but can be sent as HTTP headers. Is there a shiny example of a shiny app that reads the http headers that can be used to incorporate "initialized containers" functionality? Thanks in advance

Hi, thanks for your interest! We will provide a full example soon, in the meantime, you can access the usernames through the session object like this:
session$request$HTTP_X_SP_USERID
session$request$HTTP_X_SP_USERGROUPS

We just published a demo for this: https://github.com/openanalytics/shinyproxy-shiny-demo-auth
I'll close this issue, but of course feedback is welcome!

authors: LEDfan corey-dawson

repo: openanalytics/shinyproxy


text:
Update documentation link

Fixes some some issue.

You did it @openanthem-admin!
Thank you for signing the Anthem Opensource Software CLA.

repo: openanthem/nimbus-core


text:
Wrong carbs with 0.6.0-dev with meal during new sensor warmup

@scottleibrand
I had the following usecase:

new sensor
meal of 80g at 18:34 while sensor was still warming up
calibrated sensor
started oref0 0.6.0 rig

Nightscout and pump loop show COB: 0 (mealCOB=0) when I expected some carbs from the 80 g meal. At 21:59 Nightscout sees COB: 59 in 1 pump run, causing a 0.6 microbolus ( I had maxSMBBasalMinutes put on 60 to see if that would make larger SMB's).

pump loop log:
enact/smb-suggested.json: {"insulinReq":0,"bg":210,"reservoir":"47.225","temp":"absolute","snoozeBG":141,"predBGs":{"IOB":[210,199,189,179,170,161,152,145,137,131,124,119,113,109,104,100,96,93,90,87,85,83,81,79,77,75,73,71,70,69,67,66,65,64,63,62,61,60,60,59,58,58,58,57,57,57,56]},"minPredBG":999,"IOB":1.478,"reason":"COB: 0, Dev: 23, BGI: -9.56, ISF: 5.3, Target: 5.8, minPredBG 3.1, IOBpredBG 3.1; Eventual BG 5.1 < 5.6, bolus snooze: eventual BG range 5.1-7.8, temp 0.575 ~ req 0.575U/hr. ","COB":0,"eventualBG":91,"tick":-11,"deliverAt":"2017-09-03T19:58:37.517Z"}18,"boluses":9.9,"mealCOB":59,"currentDeviation":1.1,"maxDeviation":11.63,"minDeviationSlope":-1.221}"bolussnooze":0.357,"basaliob":0.898,"netbasalinsulin":1.2,"hightempinsulin":1.6,"microBolusInsulin":1.3,"microBolusIOB":0.865,"time":"2017-09-03T19:59:10.000Z","lastBolusTime":1504467236000}
enact/smb-suggested.json: {"insulinReq":1.102,"bg":221,"reservoir":"47.175","temp":"absolute","snoozeBG":213,"rate":2,"predBGs":{"COB":[221,212,204,197,191,186,183,181,179,179,181,183,187,191,197,204,212,221,231,242,254,267,281,296,311,326,340,354,367,379,391,401],"aCOB":[221,221,221,222,222,224,225,227,229,231,234,237,241,245,248,253,257,262,267,272,277,282,288,293,298,303,308,314,319,324,329,334,339,344,349,354,359,364,368,373,378,382,387,391,396,400,401],"UAM":[221,211,202,193,184,176,168,161,154,147,141,136,130,126,121,117,114,110,107,105,102,100,98,96,94,92,91,89,88,86,85,84,83,81,81,80,79,78,77,77,76,76,75,75,75,75,74],"IOB":[221,211,201,192,184,175,168,160,153,147,141,135,130,125,121,117,113,110,107,105,102,100,98,96,94,92,90,89,87,86,85,83,82,81,80,79,79,78,77,77,76,76,75,75,75,74]},"minPredBG":213,"IOB":1.462,"duration":30,"reason":"COB: 59, Dev: 9, BGI: -9.51, ISF: 5.3, Target: 4.4, minPredBG 11.8, IOBpredBG 4.1, COBpredBG 22.3, UAMpredBG 4.1; max_iob 2,  insulinReq 1.102; maxBolus 0.6. Microbolusing 0.6U. adj. req. rate: 2.8 to maxSafeBasal: 2, temp 0.575<2U/hr. ","COB":59,"eventualBG":401,

I believe this is fixed by https://github.com/openaps/oref0/pull/703 - please update to the latest 0.6.0-dev and let me know if you see this again.

authors: PieterGit scottleibrand


text:
Remove existing containers for chaincode if NOT already connected.

In the case of VP restart, it is possible (and more likely expected) that the VP will be assigned a new IP address. In this case any existing chaincode containers (which will have exited due to disconnect) should be removed instead of re-statred, as the peer.address info may be inaccurate.  Assigning this to @muralisrini

@jyellick this will cause us problems if we stop more than 1 VP and start it again.

@jeffgarratt : I believe this is fixed with https://github.com/openblockchain/obc-peer/commit/3362078d75dff4a50efee8c669c8fda7e9b6e596 can we close this please ?

indeed it can :)

authors: jeffgarratt muralisrini

repo: openblockchain/obc-peer


text:
Test Boot Devices Suite Setup fails and all 12 TCs fails

Test Boot Devices Suite Setup fails because we are checking the "Is OS Starting" without initiate hostboot.
1
Test Suite Setup
  | [Documentation]  Do the initial suite setup.
  | ${current_state}=  Get Host State
  | Run Keyword If  '${current_state}' == 'Off'
  | ...  Initiate Host Boot     <===== Current_state was running and it didnt trigger host boot
  |
  | Wait Until Keyword Succeeds   <=== This statement is not needed.
  | ...  10 min  10 sec  Is OS Starting
Full Name:
This testsuite is for testing the Boot Device Functions
/tmp/fspcibld/29519/obmc-robot/tests/test_boot_devices.robot
20170707 14:40:22.491 / 20170707 14:50:29.731 / 00:10:07.240
12 critical test, 0 passed, 12 failed12 test total, 0 passed, 12 failed
Suite setup failed:
Keyword 'Is OS Starting' failed after retrying for 10 minutes. The last error was: Off != FW Progress, Starting OS

https://gerrit.openbmc-project.xyz/#/c/5264/

U can use this patch and test on ur sanbox and see if it fixes all

Did the above patch worked good @swe12345

@gkeishin Tried it for all the three test cases when the system is in 'Running' state.. Works fine..

I mean did u tried running CT with those patch..

authors: gkeishin sivassrr swe12345

repo: openbmc/openbmc-test-automation


text:
Typo and need more variables

Typo  ob_php-fpm/docker-entrypoint.sh

71        echo 'max_executionn_time=300'

71       echo 'max_execution_time=300'

Need more variables in .env file.
71        echo 'max_execution_time=300'
82        echo 'upload_max_filesize=50M'
83        echo 'post_max_size=50M'

Hi, thanks for the note. Fixed the typo. If you want to extend with more variables, feel free to make a  PR with the changes.

authors: saolex tspicer


text:
Filter for isPublished in Admin UI

Sometimes it would be nice if we could filter for only published events in the Admin UI (where events with only the internal publication would not count), e.g. for trying to find scheduled events with live publications, or only published processed events. The Admin UI shows this information, but you can't filter for it currently.

I like that. Currently, I sort by the publication column to group published events.

authors: KatrinIhler mtneug

repo: opencast/opencast


text:
MH-13420 ngRepeat does not allow duplicates

This patch allows duplicate values to be displayed in multivalue fields if they are present in the data source.

Is there a use case we need this for?

The data model allow duplicates and with the external api it is possible to add duplicate contributor entries for example.
If there are duplicates for any reason, they should be displayed. At least to be able to delete them.

@geichelberger Okay, I can see that, but maybe it would make more sense to not allow to create duplicate entries in the first place?

@KatrinIhler Perhaps someone has a use case for duplicates, this concerns not only the normal metadata but also the extended ones. Why should the API forbid something if it is supported by the data model? Furthermore, this would be a change that is not backward compatible.
I think the reason why no duplicates are allowed in the Admin-UI is because the value of an entry was used as identifier and not the index. (function removeValue)
See Pull-Request MH-1323 commit: https://github.com/opencast/opencast/pull/564/commits/e8b6ac07f15ae389959dc7fb643993348025f764
Maybe we should allow to enter duplicates in the Admin-UI?

@geichelberger Okay, I see your point. And yes, in that case we should probably allow multiple values in the Admin-UI as well to be consistent.

One more thing: Presenters are also not displayed at all in the admin ui table if there are duplicate values.

You mean Event/Presenters? With the patched version it works for me.

It's not working for me:

I create duplicate presenters by editing the dublincore in the archive and then rebuilding the Admin UI index, no idea if that's affecting things...once I delete the duplicates, the table shows the presenters just fine.

Should be fixed now. The easiest way to create duplicate entries is to resend a manipulated event update request.

Still not working for me, I think you'd actually have to update EventsPresentersCell.html or something to fix this in the main table. Anyway, we could consider this a separate issue and this improves the current state, so I'm gonna merge this as is.

authors: KatrinIhler geichelberger


text:
Only most recent 50 events are saved in API events table

I'm seeing new behavior with APIClarity v0.14.4 - the API events table is only keeping the last 50 events. Prior to 0.14.4, it was keeping many more events. In my test, I ran locust against sock shop APIs and generated over 1000 API calls (see first screenshot for count) but only 50 API events are listed (second screenshot).

If I run more API traffic, 50 new calls are kept, but everything else is gone. This seems like really degraded behavior.

same problem

authors: amccormi jpgong

repo: openclarity/apiclarity


text:
Increase grpc and gnmi timeout for otg-hw

Few tests are failing because of grpc and gnmi timeouts, increasing the timeout from 30 to 60.

Pull Request Functional Test Report for #2920 / 5dd0ec17a4bb73193f015f95b9034279add7400f
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build 8812605633
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.448%

Totals

Change from base Build 8809294032:
0.0%

Covered Lines:
1949

Relevant Lines:
3515

💛  - Coveralls

authors: ANISH-GOTTAPU OpenConfigBot coveralls

repo: openconfig/featureprofiles


text:
[doc] ARM architecture is not supported by the documentation's installation instructions.

In the documentation, only x86 binaries are provided for installation. The binary must be manually compiled for ARM-based machines. Support for ARM architecture should be added to the documentation.

cc @caoxianfei1

repo: opencurve/curveadm


text:
Filter search can be very slow

In big jobs with a large number of objects the search works slowly. It is related with the need to interpolate objects for each frame. Probably there is faster approach.

Suppose this issue has been resolved in new UI

repo: opencv/cvat


text:
ports error after going into developer mode

 [webpack-dev-server] [HPM] Error occurred while proxying request 127.0.0.1:3000/api/events?org= to http://localhost:7000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
That's the error which is shown if any one has knowledge about that kindly help me out.
--source from where i try developer mode After all the installation error define in start when in run "yarn run start:cvat-ui"
Source https://opencv.github.io/cvat/docs/contributing/development-environment/

Perhaps you did not start backend process

sorry what do you mean?

Please, follow step by step guide carefully: https://opencv.github.io/cvat/docs/contributing/development-environment/
If you have an issue on a specific step, ask questions providing all the details.


text:
How to deploy the model in CVAT while using external CVAT_HOST?

Hi, I am trying to deploy the model in GCP in CVAT. External IP for the VM instance is configured with 8080 port for CVAT.
I have done below steps while SSH into the VM instance:
Cloned the latest repo
cd cvat
Exported CVAT_HOST
sudo -E docker compose up -d
Now, how to proceed for automated Annotations on my CVAT_HOST?
I tried running the
docker compose -f components/serverless/docker-compose.serverless.yml up -d --build
But in the CVAT, I am unable to the Models tab.
Can anyone help me here please!.

I tried running the
docker compose -f components/serverless/docker-compose.serverless.yml up -d --build

Where have you seen suggestion to use this command?
Please, proceed the guide: https://opencv.github.io/cvat/docs/manual/advanced/serverless-tutorial/

I have followed exact same way, Using the same Guide .
But my doubt is it my external IP is 0.0.0.0 for example.
CVAT would be on 0.0.0.0:8080,
after installation will the Nuclio (serverless) using that guide be on this 0.0.0.0:8070 port??
And will this be communicating with CVAT for getting Models tab in CVAT?
Now, for me that was the problem, I both CVAT and Nuclio are running and I deployed a model in Nuclio but Models tab in CVAT is not visible for semi automated annotations.

So, perhaps you have issues because you did not follow the guide...
There is not a command like this: docker compose -f components/serverless/docker-compose.serverless.yml up -d --build.

docker compose -f docker-compose.yml -f docker-compose.dev.yml -f components/serverless/docker-compose.serverless.yml up -d --build
This is the command I used
There was a typo sorry for that


text:
[Epic] Upgrade to v2

Tekton V2:

[ ] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/432
[ ] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/429
[ ] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/428
[x] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/427
[x] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/425
[x] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/377
[x] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/369
[ ] https://github.com/opendatahub-io/data-science-pipelines-operator/issues/445

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1665

authors: gregsheremeta rimolive


text:
Experiment with querying mlmd data

HuggingFace makes tags available for searching on their interface. Whilst we might deserialize a complex structure (say, with JSON, as per internal discussions) it might be best to experiment with nested artifacts to accomplish this functionality with simpler processing (e.g. handling only the initial query to pass it to the proper DB entry).

We can just use a string with tags separated by ,, and then use a query like tags LIKE '%foo%'.

I have experimented with lists as comma-separated strings, and holding references to nested artifacts with their keys. The approach I came up with is to use suffixes on the property keys to indicate what the value being held actually is:

.key indicates the property is a key to another artifact
.key_list indicates it is a (comma-separated) list of such keys
.list indicates it is a comma-separated string of scalars

This takes away some flexibility as we need to know the suffix of a given property in advance, either by checking all available properties so we can match a non-suffixed entry to its actual key, or by trying out different combinations util one succeeds. It also takes away some flexibility as we can't import values that have such suffixes in them as it'd cause problems parsing the data incorrectly. I haven't experimented further but one possible workaround would be to prefix the data itself, then parse after accessing it, but this comes with its own problems.
Experiments were done at: https://github.com/isinyaaa/hf-mlmd-mapping-poc

authors: dhirajsb isinyaaa

repo: opendatahub-io/model-registry


text:
Fix for select components causing scroll container to jump

Closes RHOAIENG-11967
Closes RHOAIENG-11118
Description
Opening the Select components when not attached to the appropriate scrolled container caused the scroll container to scroll to the top. Added a HOC to wrap around the select components to correctly determine the scroll container and append the popper for the select to.
How Has This Been Tested?
Tested manually. Ran RTL tests.
Request review criteria:
Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

Closing since the solution break tests. Hoping to get a PatternFly solution from https://github.com/patternfly/patternfly-react/issues/10896

repo: opendatahub-io/odh-dashboard


text:
stSync stable

Description

How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/close

repo: opendatahub-io/rest-proxy


text:
PostingsFormat Fix for odfe 1.9

postings list fix

Issue #, if available:
https://github.com/opendistro-for-elasticsearch/k-NN/issues/227
Description of changes:
https://github.com/opendistro-for-elasticsearch/k-NN/pull/236
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Manually verified suggest Field to check PostingsFormat fix
curl -X PUT "localhost:9200/music?pretty" -H 'Content-Type: application/json' -d'
{
"settings": {
"index": {
"knn": true
}
},
"mappings": {
"properties": {
"suggest": {
"type": "completion"
}
}
}
}
'
curl -X POST "localhost:9200/music/_doc/1?refresh=true" -H 'Content-Type: application/json' -d'
{
"suggest" : {
"input": [ "Nevermind", "Nirvana" ],
"weight" : 34
}
}
'
curl -X POST "localhost:9200/music/_search?pretty" -H 'Content-Type: application/json' -d'
{
"suggest": {
"song-suggest": {
"prefix": "nir",
"completion": {
"field": "suggest"
}
}
}
}
'
Output:-
{
"took" : 92,
"timed_out" : false,
"_shards" : {
"total" : 1,
"successful" : 1,
"skipped" : 0,
"failed" : 0
},
"hits" : {
"total" : {
"value" : 0,
"relation" : "eq"
},
"max_score" : null,
"hits" : [ ]
},
"suggest" : {
"song-suggest" : [
{
"text" : "nir",
"offset" : 0,
"length" : 3,
"options" : [
{
"text" : "Nirvana",
"_index" : "music",
"_type" : "_doc",
"_id" : "1",
"_score" : 34.0,
"_source" : {
"suggest" : {
"input" : [
"Nevermind",
"Nirvana"
],
"weight" : 34
}
}
}
]
}
]
}
}

repo: opendistro-for-elasticsearch/k-NN


text:
Check bounds application on inner expressions

For example SUM(Age * 5)

Inner expressions are currently disabled

repo: opendp/smartnoise-sdk


text:
feat(helm): Helm chart changes for issue #113 and PR #114

Adds support for setting an image pull secret on the
NFS Server pods.
Signed-off-by: Grant Linville grantlinville@posteo.us
Pull Request template
Why is this PR required? What issue does it fix?:
This makes the needed Helm chart changes for issue #113 and PR #114.
What this PR does?:
This adds an environment variable to the Deployment that can be configured from the values file. The variable is a string that can be set to the name of an image pull secret to be used by NFS Server pods.
Does this PR require any upgrade changes?:
No.
If the changes in this PR are manually verified, list down the scenarios covered::
I used the helm template command to render out the chart, first leaving the nfsServer.imagePullSecret value unset and seeing that the environment variable was not rendered, and then setting the value and seeing that the environment variable was rendered.
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
This PR is a continuation of #114 and of #116 which I accidentally closed.
Checklist:

[ ] Fixes #113
[ ] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Does this PR change require updating NFS-Provisioner Chart? If yes, mention the Helm Chart PR #
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #117 (e02e49b) into develop (75dc272) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #117   +/-   ##
========================================
  Coverage    47.11%   47.11%
========================================
  Files           29       29
  Lines         2390     2390
========================================
  Hits          1126     1126
  Misses        1185     1185
  Partials        79       79

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 75dc272...e02e49b. Read the comment docs.

authors: codecov-commenter g-linville

repo: openebs/dynamic-nfs-provisioner


text:
Design approval/discussions around logging

Need to discuss & conclude on:

logging library to be used if any
logging levels
format of logging
size of logs
location of logs
rotation policy around logs
should logs be exported as events to some external services

NOTE: This should be same across all OpenEBS projects.

@AmitKumarDas This (https://logmatic.io/blog/our-guide-to-a-golang-logs-world/) seem to be a good example of what logging framework (In addition to the description provided by you) should cover and effective way to build it.

Refer:

github.com/hashicorp/go-multierror

authors: AmitKumarDas satyamz

repo: openebs/mayaserver


text:
Cluster level openebs components should be installed in openebs namespace

OpenEBS components like maya-api-server, openebs-provisioner need a specific namespace called openebs. This namespace should be mapped against a super admin's role.

The corresponding e2e issue for this is : https://github.com/openebs/openebs/issues/1219

Changes have been checked-in on v0.5 branch.
Need to implement the same for master branch.

Changes are merged to master with https://github.com/openebs/openebs/pull/1269

authors: AmitKumarDas kmova ksatchit

repo: openebs/openebs


text:
Configure OpenEBS to use separate dedicated storage network/nics

Description

Make it possible to add addition annotation to Pods
Additionaly be able to configure the network used for any storage traffic
Context

I've built an K3S cluster on OrangePi 5 Plus, that have two 2.5Gbps NIC. The grand plan was to have "normal" stuff running by default on one NIC, and all the (virtual) storage traffic on its own dedicated network on the second NIC.
This would make the second network a sort of IP based SAN, and I would fulfil my grand plan.
Possible Solution

To do this I need all Pods and any storage traffic link to via attached to the second network. As have I have a second CNI, for Pods and such all that is needed is this annotation:
annotations:
              k8s.v1.cni.cncf.io/networks: backbr

My storage network is called backbr, the default network (with no annotation) is frontbr.
I tried and failed to use kustomize to adapt the output of helm template. I am guessing new resources are being generated at run time and not just via the original manifest
Screenshots

Image many pods with the wrong IP attached (in my case the IP range of frontbr and not the IP range of backbr)

for any storage traffic

My storage traffic do you mean only the actual storage IOs?
If so then this is most likely we're referring to our replicated engine - mayastor?
On mayastor there's a way of binding to a specific interface for all nvme-tcp traffic: https://github.com/openebs/mayastor-extensions/blob/2d9122501a32a29a3de0ac4dbea7fe1fedd9d1cb/chart/values.yaml#L375
Though it's a bit of a blunt weapon, sets it for every node part of the ds...

I was/am planning that only traffic related to storage, including pods and storage io, to be via physically separate NICs / LAN

@ThorbenJ have you checked if the solution provided above works for you? Please confirm.

With work and other things, I've not been able to come back to the project yet. My Orange Pi's are currently not up to much other than blinking. However this does look like it would work, if it behaves as the comments suggests.

authors: ThorbenJ avishnu tiagolobocastro


text:
'Select all' button has incorrect label with applied filters in DataTable

STR

Go to frontend-filtering-and-sorting example
Open filters dropdown and select "Orange tubby"
Select one of the rows

AR

"Select all" button has "Select all 7" label even though there are only 2 rows displayed after applying filters

ER

"Select all" button has "Select all 2" label (in general case it should be "Select all {numOfFilteredRows}")

@adamstankiewicz for some reason I thought that after applying filters the Select all does not select anything, but I see that it's not the case now, false alarm, sorry 😞

After clicking "Select all 7" with same row selected (with filter applied NOT returning the selected row):
Having it say "Select all 7" when only 1 result is returned given the applied filter seems incorrect, when the "Select all X"
should be applying only to the rows returned by any active filters.

that was also bothering me, I'll update the issue description to only include this point

Sounds good! Thanks, @viktorrusakov.

Issue: https://github.com/openedx/paragon/pull/2020

repo: openedx/paragon


text:
fix: avoid CSS utility class, update Popover

Avoids using a CSS utility class in one of the DataTable subcomponents for better theming support.
Fixes Popover so that popover header vs. body are styled correctly.

:tada: This PR is included in version 19.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: adamstankiewicz edx-semantic-release


text:
fix: pypi-publish master branch sunset

This will fix the warning of 'The master branch version has been sunset for gh-action-pypi-publisher'

Thanks for the pull request, @CodeWithEmad!
What's next?
Please work through the following steps to get your changes ready for engineering review:
:radio_button: Get product approval
If you haven't already, check this list to see if your contribution needs to go through the product review process.

If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.

This process (including the steps you'll need to take) is documented here.

If it doesn't, simply proceed with the next step.

:radio_button: Provide context
To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

Dependencies

This PR must be merged before / after / at the same time as ...

Blockers

This PR is waiting for OEP-1234 to be accepted.

Timeline information

This PR must be merged by XX date because ...

Partner information

This is for a course on edx.org.

Supporting documentation
Relevant Open edX discussion forum threads

:radio_button: Get a green build
If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.
:radio_button: Let us know that your PR is ready for review:
Who will review my changes?
This repository is currently maintained by @openedx/axim-engineering.  Tag them in a comment and let them know that your changes are ready for review.
Where can I find more information?
If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

Overview of Review Process for Community Contributions
Pull Request Status Guide
Making changes to your pull request

When can I expect my changes to be merged?
Our goal is to get community contributions seen and reviewed as efficiently as possible.
However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

The size and impact of the changes that it introduces
The need for product review
Maintenance status of the parent repository

:bulb: As a result it may take up to several weeks or months to complete a review and merge your PR.

Hi @openedx/axim-engineering
My codecov job failed because I got less code coverage by just changing an action! It might be something else but I've zero clue. Can you have a look?

Hey @CodeWithEmad , we've been having issues with codecov reliability lately. It looks like the check isn't required, so feel free to ignore the codecov failure merge once you get a review.

@CodeWithEmad 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

repo: openedx/xblock-sdk


text:
Connect to a variety of MQTT brokers

Continue the abstraction layer work so the firmware is unaware of the MQTT broker.
To the extent possible, write a single firmware that can connect to a variety of MQTT brokers - Watson IoT, VerneMQ, Local subnet mosquitto.
All of the device and MQTT orchestration should be handled via the
https://device-mgmt.openeew.com/activation
endpoint.
With the caveat that server security certificates need to be available for the requested MQTT broker.

can we close this issue given that we are moving away from complicated MQTT systems ?

authors: andygrillo johnwalicki

repo: openeew/openeew-firmware


text:
Update paper.md

👋 @ahalterman. This PR updates the JOSS paper structure to be compatible with our new paper template.

Thanks! I'll merge.

authors: ahalterman arfon

repo: openeventdata/mordecai


text:
Rendering issue on native targets

Using the drawing API to draw a circle in a container that is scaled down to be very small will create this interesting looking render artifact. This happens on native windows builds using openfl 2.1.5, other native platforms are untested, but I suspect they will have it too.
Code to reproduce (or get the full project):
package;

import haxe.Timer;
import openfl.display.Shape;
import openfl.display.Sprite;

/**
class Main extends Sprite {

	public function new() {
		super();

		// repeating this nine times to make the rendering error extra visible
		// it's super faint otherwise
		for (i in 0 ... 9) addBox(i);
	}

	function addBox(i) {

		// create a shape (sprite works too)
		var s = new Shape();

		// make it really, really small, this is what causes the error
		s.scaleX = s.scaleY = .01;

		// center it (just to make things easy to see)
		s.x = stage.stageWidth / 2;
		s.y = stage.stageHeight / 2;

		// draw a green square, this will be unaffected by the bug
		s.graphics.beginFill(0x00ff00);
		s.graphics.drawRect( -50, -50, 100, 100);
		s.graphics.endFill();

		// now, a pink circle, the same radius as the square
		s.graphics.lineStyle(2, 0xff00ff);
		s.graphics.drawCircle(0, 0, 100);

		// finally, add a timer that resizes the shape back to 100%
		// this will show the circle as a blurry octagon with one "solid" triangle
		// tweening to full size will exhibit the same bug as well
		Timer.delay(function() {
			s.scaleX = s.scaleY = 1;
		}, 1000);

		// finally, add the shape to the display list
		// it does not seem to matter where this is done, before or after drawing or scaling
		addChild(s);
	}
}

This has been fixed :smile:

authors: grapefrukt jgranick

repo: openfl/openfl


text:
Fix for issue #2535 "TypeError: this.text.indexOf is not a function"

"TypeError: this.text.indexOf is not a function" exception occurs for js/html5 targets if value consists of numbers only - so clearly cast to string.
Haxe code to reproduce:
smth. like this
private function setValue(strNumber:String):Void {
	textField.text = strNumber;
}

The type of the setter is already String, so if you are managing to pass in a different type, it should be considered a bug in your code. Here's the function signature. The compiler will not allow any other value here, unless it's typed as Dynamic.
private function set_text(value:String):String

It's "dangerous" to use Dynamic, and you need to be extra careful when you use it. In this case, the fix you need somewhere in your code is to convert the value to a string. Std.string() is a good way to do that.
var strNumber:Dynamic = 123.4;
textField.text = Std.string(strNumber);


text:
NPE - android.widget.EditText in databinding.ActivityContinuousScanBinding.quickViewSearchByBarcode' views.ContinuousScanActivity.hideAllViews (line 490)

Attempt to read from field 'android.widget.EditText *.openfood.databinding.ActivityContinuousScanBinding.quickViewSearchByBarcode' on a null object reference at *.openfood.views.ContinuousScanActivity.hideAllViews(ContinuousScanActivity.java:490)
app/src/main/java/openfoodfacts/github/scrachx/openfood/views/ContinuousScanActivity.java
2020-06-12 17:03:56.116 17149-17149/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: openfoodfacts.github.scrachx.openbeauty, PID: 17149
    java.lang.NullPointerException: Attempt to read from field 'android.widget.EditText openfoodfacts.github.scrachx.openfood.databinding.ActivityContinuousScanBinding.quickViewSearchByBarcode' on a null object reference
        at openfoodfacts.github.scrachx.openfood.views.ContinuousScanActivity.hideAllViews(ContinuousScanActivity.java:490)
        at openfoodfacts.github.scrachx.openfood.views.ContinuousScanActivity.lambda$onCreate$7$ContinuousScanActivity(ContinuousScanActivity.java:606)
        at openfoodfacts.github.scrachx.openfood.views.-$$Lambda$ContinuousScanActivity$kNT4tS01CpARjbn5Wc_WCURtDk4.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:223)
        at android.app.ActivityThread.main(ActivityThread.java:7523)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:941)

How did you get this? It means that the binding got invalidated. Could you provide the steps to get this?

I'm not quite sure, I remember swiping back from the Scan view.

logcat-prelaunch.txt

Here is the video:
https://storage.googleapis.com/play-mtaas-results-prod/org.openfoodfacts.scanner/332/blueline-28-fr-portrait/video.mp4?GoogleAccessId=498997737111-pmn4sf5896c460sheh5fv3k1j1cq46t5@developer.gserviceaccount.com&Expires=1592058761&Signature=0/osDRRmb%2BRhzJ4GP7JU3hGfXKHJ3H1KFKg2SOFCoGFIx2E%2BNr1Do%2BNxIOPzgh%2BC84mNptuc9xjOI5It0LHwVg3HP5OuIe1/2QfkN0VqqZiFSqmcT1M3fFEROSYSW9jHxko8%2Bz7aBXy%2BYFFCNBb%2BYsg0lyclX1jM4HBLGwgO87wvsEfvPuEWqZyDCPVXJmu17%2Bzs83A9uodYbW8hzUe%2BKTQm4v4nsfYspN276AEIbdscerJn1yDvuVlFW8x0RceVqvz4neZBxgsM1w37As9J9nBHZGVzod1LtYJpk3OONSkPr6JdE18r0LX7PFn84%2BNObp7aP281Xi1Ti5Y8/ReEIQ%3D%3D

https://github.com/openfoodfacts/openfoodfacts-androidapp/blob/master/app/src/main/java/openfoodfacts/github/scrachx/openfood/views/ContinuousScanActivity.java

Fixed by  091e745

authors: VaiTon teolemon

repo: openfoodfacts/openfoodfacts-androidapp


text:
visual issues on the card in dark mode

What

Color issues in Dark Mode

Steps to reproduce the behavior

Search for a product
See the product card
…
See an error

Screenshot

Fixed by #2163

repo: openfoodfacts/smooth-app


text:
Ensure that CameraX is fully supported for Flutter so that we can use it easily

Why

We're getting complaints of scan not working well
We use camera, while camerax defragments the Android camera mess

What

Ensure that CameraX is fully supported for Flutter so that we can use it easily
Investigate new fast moving libraries: https://pub.dev/packages/mobile_scanner

What is the key of this issue, why has it a P0

We keep getting negative feedback on scan.

Honestly, I think this is not a P0, as it won't change anything… and even isn't an issue anymore.
Correct me if I'm wrong, but today, the camera works in 99% of cases.
CameraX is just a wrapper on top of Camera2, and with all the modifications I have done to make it stable, we will have to do all this work again.

Scan remains the #1 issue of complaints on the AppStore, with people desinstalling OFF, and long-time users expressing disappointment.
Form feedback, email feedback and App Store feedback are centralized there, with a column on topic
https://docs.google.com/spreadsheets/d/1KsJv8_RxfDDd5ngmeQ4k8ELsudl-YhleXEoDFoGoSAE/edit#gid=1439550856

Recent developments in the Flutter team mean that it's probably moving in the right direction. To be continued

I believe we can close since we now have a CameraX based solution


text:
Broken product page: null value in column's children at index 0

I was trying to replicate #266 using master, but instead I have a different issue...

And for me, I'm missing images not in the horizontal list view, but in the cards and lists... weird.

======== Exception caught by widgets library =======================================================
The following assertion was thrown building SmoothCard(dirty):
Column's children must not contain any null values, but a null value was found at index 0
When the exception was thrown, this was the stack:
#0      new MultiChildRenderObjectWidget. (package:flutter/src/widgets/framework.dart:1922:11)
#1      new MultiChildRenderObjectWidget (package:flutter/src/widgets/framework.dart:1929:6)
#2      new Flex (package:flutter/src/widgets/basic.dart:4136:8)
#3      new Column (package:flutter/src/widgets/basic.dart:4704:8)
#4      SmoothCard.build (package:smooth_ui_library/widgets/smooth_card.dart:26:20)


text:
Generate benchmark data

Opening a separate issue so we don't lose all the information when #52 gets merged.
Based on discussions the following needs to happen before we move ahead with benchmarking properly:

[ ] Finish up the PDB formatting issues with #52
[ ] Remove the existing edges.yaml files
[ ] Add a new set of edges.yaml using OpenFE's minimum spanning graph planner + Perses mapping
[ ] Have both Perses and OpenFE do a quick "will this setup properly" check again at this point
[ ] Communicate a shared set of HREX sampler settings
[ ] Communicate a shared set of force fields

We will likely go with what the current perses defaults are (since those are also the OpenFE defaults)

[ ] Communicate a set of targets to start with (eventually we will do them all)

OpenFE has started with an initial 6 targets: hif2a, mcl1, p38, thrombin, tnsk2, tyk2

[ ] OpenFE will re-run 3x replica, Perses will likely run 1x to double check we get the same results?
[ ] Eventually re-run everything once we have a finalised Perses / gufe neq protocol?

@jchodera just pinging you to see if this plan we came up with works for you? We're working on the idea that OpenFE and Perses are the same underlying code for HREX & vanilla HTF things, so we shouldn't need to duplicate full simulations too much here.

repo: openforcefield/protein-ligand-benchmark


text:
✨(backend) change target_course display format in product

Purpose
Description...
Proposal
Description...

[] item 1...
[] item 2...

@samy-aitouakli can you feel in the PR description?

authors: sampaccoud samy-aitouakli

repo: openfun/joanie


text:
Travel fund request: OSS Summit NA - Ruy Adorno

Travel Fund request for OSS Summit NA 2023
Dates: 8 May - 13 May
Traveling from: Montreal, Canada
Flight: 528 USD
Hotel: 1282 USD
Total: 1810 USD
Unfortunately I couldn't secure the  funding from my employer. I'll cover all other costs like local transportation and food. No additional expensing is needed.
cc @openjs-foundation/cpc
cc @ovflowd

Technically it hadn't been 48 hours yet, only 44, but clearly it's fine now :-D

lol, GitHub trolling me with the "2 days ago" not being actually 48 hours T.T

authors: ljharb ovflowd ruyadorno

repo: openjs-foundation/community-fund


text:
Accept simpler forms of specifying attribution(s) for sources.

The way we can specify attributions for ol.source.Source and subclasses is quite verbose for the most common use case: on simple string attribution.
This PR suggests to accept a

string
Array<string>
ol.Attribution
Array<ol.Attribution>
undefined

as configuration value for the attributions key in the constructor options of ol.source.Source.
This API is fully backwards compatible.
I also updated our examples to make use of the simpler way of specifying attributions.
Please review.
/cc @tschaub, I know you wanted less awkwardness here, so I'd value your feedback here. Other may of course also chime in.

I'm in favour of this change (once the errors have been resolved)

I haven't looked at the code but I like the idea

Travis passes now. Please review.

You also need to update the *.prototype.attributions; types in olx.js, otherwise the API doc will be incorrect

You also need to update the *.prototype.attributions; types in olx.js

The API docs still don't look perfect :disappointed:
ol.source.Source#setAttributions

Constructor ol.source.Vector

Type definition:

If there is anythoing I can do to enhance this, I am open to suggestions.

This looks great @marcjansen.  Thanks for taking this on, I think it is a good way to provide convenience and maintain compatibility (although ol.Attribution is completely useless).
After a string, the second most useful thing to provide would be a function that accepted a resolution and extent and returned a string.  But I don't think this needs to be added now.

Fixes #4100

I need to rebase, so I'll have to postpone this one. Thanks everybody for the comments.

authors: bartvde fredj marcjansen probins tschaub


text:
MousePosition gives wrong coordinate sometimes

Hovering the mouse over Scandinavia region the MousePosition gives a wrong coordinate sometimes. Most of the time the given coordinate is correct but looks like some reagons give a wrong coordinate. The problems manifests itself when the wrong coordinate is is put to toLonLat function (toLonLat(coordinate, "EPSG:32635")) and the result is used later. The result latitude is something over 84 or under -80 which are not even close to Scandinavia. My app is using the Scandinavia region. Don't know if the problems happens elsewhere also.
My workaround fix was to create an if statement that filters out the wrong coordinates. This workaround fixed the problem but I was wondering if others have had the issue or if there's something that could be done to fix it?

No, there's no scaling of the map. I just "realized" that we are using Typescript and npm package @types for each used package. Looks like OpenLayers is most likely fine but could there be something wrong with the @types packages? I know this probably doesn't belong to OpenLayers developers but any insight would be appreciated.

Don't install @types/ol. OpenLayers comes with types already.

authors: PTParta ahocevar

repo: openlayers/openlayers


text:
VectorTile infinite loading loop

Describe the bug
The vector tile layer may load tiles forever.
I'm exporting a map as a multi-page pdf, but for one specific task the export never completes.
The specific steps required to reproduce are in the linked codesandbox.
To Reproduce
Steps to reproduce the behavior:

Go to https://codesandbox.io/s/vectortilelayer-tile-loading-bug-ppqluq?file=/main.js
The map will get stuck in a rendering loop, tiles loading never completes

Expected behavior
The map should load tiles once and fire a rendercomplete event at the end.

It seems to be related to size.  Commenting out either map.setSize(step.size); or size: step.size, fixes it.  fit() defaults to the current size, so why do you need both?

The resulting map extent is different when the size option is omitted when calling fit.
I updated the codesandbox to better show the problem.
Looks like the viewport size is not updated when setSize is called. But even when I add this it still does not complete unless I throw in a renderSync call, not sure why it helps.
Also tried to update the size of the map target element in combination with ùpdateSize. This allows to drop the size from fit, but it also does not complete.
So the problem seems to be somewhere in the vector tile loading logic.

Yes, it is a loading issue.  It can be fixed by specifying an explicit cacheSize in the vector tile source options.  The default is insufficient to cover the entire viewport if the map size is increased.


text:
SelectEvent is unknown type in OL 5.2

How can I call dispatchEvent method and pass an instance of SelectEvent object when SelectEvent is unknown type?

@fredj Thank you for the support. I found a workaround and I do not need this pull-request any more. I am going to close the issue


text:
OGC map and vector tile sources

This adds two new sources for working with OGC API - Tiles implementations: OGCMapTile and OGCVectorTile.  As the specs are not yet finalized, I've left the sources out of the stable API and marked the examples as experimental.
Examples:

OGC Map Tiles – Web Mercator
OGC Map Tiles – Geographic
OGC Vector Tiles

The vector tile source currently requires configuration with a format and mediaType (e.g. MVT() and application/vnd.mapbox-vector-tile).  This could be simplified by having feature formats advertise a media type (e.g. application/geo+json or application/vnd.mapbox-vector-tile - probably better to have it be a list actually).  I'll follow up later with this change if it sounds good to others.
We could also build in a few "well known" tile matrix set definitions.  This would save an extra fetch when tile servers don't inline the definitions.  That could be a future enhancement as well (maybe best for after the spec is finalized).
Related upstream issues as the specs evolve:

opengeospatial/ogcapi-tiles#25
opengeospatial/ogcapi-tiles#47
opengeospatial/2D-Tile-Matrix-Set#4
opengeospatial/2D-Tile-Matrix-Set#34
opengeospatial/2D-Tile-Matrix-Set#43
opengeospatial/2D-Tile-Matrix-Set#44
opengeospatial/2D-Tile-Matrix-Set#45

opengeospatial/2D-Tile-Matrix-Set#4 is "solved but not applied."

Would be graet to habe this, Tim.

I've updated the branch to resolve conflicts.  I think we're still waiting on opengeospatial/2D-Tile-Matrix-Set#4.  Not clear to me if there is any activity on the spec.

I've updated things to reflect the latest draft (OGC 17-083r2) of the OGC Two Dimensional Tile Matrix Set and Tile Set Metadata spec.  Specifically, we now use cellSize instead of scaleDenominator, pointOfOrigin instead of topLeftCorer, and we respect the cornerOfOrigin.
I'm not sure if there are any services that are implementing the changes to the spec.  The examples I've added here won't work until we find some services that are up to date.

I added a vector tile source as well (see the example).
Since the spec is not finalized, I think it makes sense to keep these out of the stable API.  But I'm calling this ready for review now.

The latest commit adds supportedMediaTypes to feature formats.  This means you can now configure an OGC vector tile source with just a url and a format (assuming the format supports one of the media types advertised by the tile service).

Very happy to see this merged. Thanks everybody

authors: marcjansen tschaub


text:
Fix typo in the snap example

Fixes #8810.

See #8812.


text:
Add tracing support to Benthos collector

Preflight Checklist

[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description
Cannot trace outgoing queries to OpenMeter.
Proposed Solution
Implement OTEL tracing support for the openmeter output.
Alternatives Considered
No response
Additional Information
No response

Done

authors: chrisgacsal sagikazarmark

repo: openmeterio/openmeter


text:
Add Vagrantfile for IDR (IDR-0.3.0)

This is an attempt to get the entire IDR tested with Vagrant.

I tested this successfully up to the point where idr-omero wanted to talk to idr-database. Both have the same 10.0.2.* IPs for eth0 but differing for eth1 in the 172.28.128.* range. I assume this will require similar to the ansible network-order fix
The order of the vagrant up arguments seems to also be important: idr-database idr-omero ...

I assume this will require similar to the ansible network-order fix

It's a different issue. The default vagrant network (which supports external access) doesn't allow inter-vm networking, so you need a second one. I think there's typo somewhere.

The order of the vagrant up arguments seems to also be important

That's a feature of vagrant with multiple-VMs. It brings up one VM, run ansible, then brings up the next...

The relevant playbooks are being migrated to https://github.com/IDR/deployment/

authors: joshmoore manics

repo: openmicroscopy/infrastructure


text:
[Meta] Refactor CoreGroup/Internal structure

[ ] Identify tests for CoreGroup that are no longer needed and delete them
[ ] Remove the test-utils feature, introduce interop-client feature instead and only expose where needed
[ ] #645
[ ] Remove the config of CoreGroup
[ ] Merge CoreGroup with MlsGroup, possibly by making it a submodule of the latter

I'm not sure it's a good idea to merge CoreGroup with MlsGroup. I think CoreGroup marks a good boundary of what's in the spec vs. what OpenMLS does on top of that.

I think this is already covered enough by #645 and #739.

authors: kkohbrok raphaelrobert

repo: openmls/openmls


text:
Allow running leiden multiple times with multiple resolutions.

Changelog
Allow running leiden multiple times with multiple resolutions.
Issue ticket number and link
~Closes #xxxx (Replace xxxx with the GitHub issue number)~
Checklist before requesting a review

[x] I have performed a self-review of my code

[x] Conforms to the Contributor's guide

Check the correct box. Does this PR contain:

[x] Breaking changes
[x] New functionality
[ ] Major changes
[ ] Minor changes
[ ] Bug fixes

[x] Proposed changes are described in the CHANGELOG.md

[x] CI tests succeed!

Suggestion: Rename --obs_name to --obsm_name. WDYT?

authors: DriesSchaumont rcannood

repo: openpipelines-bio/openpipeline