Runtime dependency on json gem

Fluentd version 0.14.4
Building custom docker image for fluentd from alpine:3.4
Running fluentd gives the following error:
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- json (LoadError)
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.4/lib/fluent/config/literal_parser.rb:19:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.4/lib/fluent/config/element.rb:18:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.4/lib/fluent/config.rb:18:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.4/lib/fluent/supervisor.rb:20:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.4/lib/fluent/command/fluentd.rb:19:in `<top (required)>'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.14.4/bin/fluentd:5:in `<top (required)>'
	from /usr/bin/fluentd:23:in `load'
	from /usr/bin/fluentd:23:in `<main>'

The issue is resolved by running gem install json. Maybe fluentd just needs to list this as a runtime dependency? I'm new to ruby so this could also be me just misconfiguring something I don't know about.

I assume this is not the fluentd issue but I can't judge it...

If you don't hit this problem with normal environment,
the problem is caused by alpine linux's ruby or something.

Yep, I think you're right:
(alpine 3.4 w/ apk add --no-cache ruby)
/ # gem list -d

*** LOCAL GEMS ***

did_you_mean (1.0.0)
    Author: Yuki Nishijima
    Homepage: https://github.com/yuki24/did_you_mean
    License: MIT
    Installed at: /usr/lib/ruby/gems/2.3.0

    "Did you mean?" experience in Ruby

minitest (5.8.3)
    Author: Ryan Davis
    Homepage: https://github.com/seattlerb/minitest
    License: MIT
    Installed at: /usr/lib/ruby/gems/2.3.0

    minitest provides a complete suite of testing facilities supporting
    TDD, BDD, mocking, and benchmarking

net-telnet (0.1.1)
    Author: SHIBATA Hiroshi
    Homepage: https://github.com/ruby/net-telnet
    Installed at: /usr/lib/ruby/gems/2.3.0

    Provides telnet client functionality.

power_assert (0.2.6)
    Author: Kazuki Tsujimoto
    Homepage: https://github.com/k-tsj/power_assert
    Licenses: 2-clause BSDL, Ruby's
    Installed at: /usr/lib/ruby/gems/2.3.0

    Power Assert for Ruby

psych (2.0.17)
    Author: Aaron Patterson
    Homepage: http://github.com/tenderlove/psych
    License: MIT
    Installed at (default): /usr/lib/ruby/gems/2.3.0

    Psych is a YAML parser and emitter

rake (10.4.2)
    Authors: Eric Hodel, Jim Weirich
    Homepage: https://github.com/ruby/rake
    License: MIT
    Installed at: /usr/lib/ruby/gems/2.3.0

    Rake is a Make-like program implemented in Ruby

test-unit (3.1.5)
    Authors: Kouhei Sutou, Haruka Yoshihara
    Homepage: http://test-unit.github.io/
    Licenses: Ruby, PSFL
    Installed at: /usr/lib/ruby/gems/2.3.0

    An xUnit family unit testing framework for Ruby.

In that case, feel free to close this issue. It's probably worth mentioning though that the official fluentd Dockerfile is built off alpine so it might be worth including json in the gemspec just to avoid confusion when upgrading (unless you see some harm in doing so).

Okay. Could you send a patch to fluentd-docker-image to install json gem?


Introduce deadlines for sync RPC stubs

Manual CP from #14116
Fixes #14110
pr-link: #14116
change-id: cid-1be9a2ddc00881e1c03731841ce3e4a1f56af3aa

Codecov Report

:exclamation: No coverage uploaded for pull request base (branch-2.6@3423e83). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             branch-2.6   #14119   +/-   ##
=============================================
  Coverage              ?   23.73%
  Complexity            ?     4579
=============================================
  Files                 ?     1382
  Lines                 ?    80100
  Branches              ?     9750
=============================================
  Hits                  ?    19008
  Misses                ?    59695
  Partials              ?     1397

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 3423e83...1c4a11c. Read the comment docs.

alluxio-bot, merge this please


When deploying: TypeError: incompatible marshal file format (can't be read) 	format version 4.8 required; 60.60 given

I try to deploy to the server and got this error:
EDIT: when I run any nanoc command inside a existing nanoc project. When I create a new project I don't have a problem.
EDIT2: Al versions are the same: ruby, gems, nanoc, etc. So I'm certain it's has to do with my site content.

TypeError: incompatible marshal file format (can't be read)
format version 4.8 required; 60.60 given

Crashlog created at 2014-03-31 14:28:03 +0200

===== MESSAGE:

TypeError: incompatible marshal file format (can't be read)
    format version 4.8 required; 60.60 given

===== COMPILATION STACK:

  (empty)

===== STACK TRACE:

  0. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/pstore.rb:475:in `load'
  1. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/pstore.rb:475:in `load'
  2. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/pstore.rb:410:in `load_data'
  3. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/pstore.rb:327:in `transaction'
  4. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/base/store.rb:76:in `load'
  5. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/base/compilation/compiler.rb:127:in `block in load'
  6. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/base/compilation/compiler.rb:127:in `each'
  7. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/base/compilation/compiler.rb:127:in `load'
  8. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/base/source_data/site.rb:250:in `load'
  9. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/command_runner.rb:63:in `load_site'
  10. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/commands/deploy.rb:20:in `run'
  11. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/command_runner.rb:14:in `block in call'
  12. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/error_handler.rb:70:in `handle_while'
  13. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/error_handler.rb:26:in `handle_while'
  14. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/command_runner.rb:13:in `call'
  15. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/cri-2.5.0/lib/cri/command_dsl.rb:185:in `block in runner'
  16. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/cri-2.5.0/lib/cri/command.rb:298:in `call'
  17. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/cri-2.5.0/lib/cri/command.rb:298:in `run_this'
  18. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/cri-2.5.0/lib/cri/command.rb:251:in `run'
  19. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/cri-2.5.0/lib/cri/command.rb:264:in `run'
  20. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli.rb:59:in `block in run'
  21. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/error_handler.rb:70:in `handle_while'
  22. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli/error_handler.rb:26:in `handle_while'
  23. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib/nanoc/cli.rb:57:in `run'
  24. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/bin/nanoc:19:in `<top (required)>'
  25. /Users/gtheys/.rbenv/versions/2.0.0-p247/bin/nanoc:23:in `load'

===== VERSION INFORMATION:

nanoc 3.6.8 © 2007-2013 Denis Defreyne.
 /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib
  1. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/systemu-2.6.4/lib
  2. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/sass-3.3.4/lib
  3. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/redcarpet-3.1.1/../../extensions/x86_64-darwin-13/2.0.0-static/redcarpet-3.1.1
  4. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/redcarpet-3.1.1/lib
  5. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rb-readline-0.5.1/lib
  6. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rack-rewrite-1.5.0/lib
  7. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.1/../../extensions/x86_64-darwin-13/2.0.0-static/nokogiri-1.6.1
  8. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nokogiri-1.6.1/lib
  9. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/mini_portile-0.5.3/lib
  10. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/mime-types-2.2/lib
  11. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/less-2.5.0/lib
  12. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/kramdown-1.3.3/lib
  13. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/i18n-0.6.9/lib
  14. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/haml-4.0.5/lib
  15. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/tilt-2.0.1/lib
  16. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-pow-2.0.0/lib
  17. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-nanoc-1.0.2/lib
  18. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nanoc-3.6.8/lib
  19. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-livereload-2.1.2/lib
  20. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/multi_json-1.9.2/lib
  21. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-bundler-2.0.0/lib
  22. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-2.6.0/lib
  23. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib
  24. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pry-<IP_ADDRESS>/lib
  25. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/slop-3.5.0/lib
  26. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/method_source-0.8.2/lib
  27. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/lumberjack-1.0.5/lib
  28. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/listen-2.7.1/lib
  29. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rb-inotify-0.9.3/lib
  30. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rb-fsevent-0.9.4/lib
  31. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/growl-1.0.3/lib
  32. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/fssm-0.2.10/lib
  33. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/formatador-0.2.4/lib
  34. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/ffi-1.9.3/../../extensions/x86_64-darwin-13/2.0.0-static/ffi-1.9.3
  35. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/ffi-1.9.3/lib
  36. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/ffi-1.9.3/ext/ffi_c
  37. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/em-websocket-0.5.0/lib
  38. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/http_parser.rb-0.5.3/../../extensions/x86_64-darwin-13/2.0.0-static/http_parser.rb-0.5.3
  39. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/http_parser.rb-0.5.3/lib
  40. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/../../extensions/x86_64-darwin-13/2.0.0-static/eventmachine-1.0.3
  41. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib
  42. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/cri-2.5.0/lib
  43. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/commonjs-0.2.7/lib
  44. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/colored-1.2/lib
  45. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/coderay-1.1.0/lib
  46. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/celluloid-io-0.15.0/lib
  47. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nio4r-1.0.0/../../extensions/x86_64-darwin-13/2.0.0-static/nio4r-1.0.0
  48. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/nio4r-1.0.0/lib
  49. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/celluloid-0.15.2/lib
  50. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/timers-1.1.0/lib
  51. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/builder-3.2.2/lib
  52. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/adsf-1.2.0/lib
  53. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rack-1.5.2/lib
  54. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/rake-10.2.0/lib
  55. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib
  56. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/site_ruby/2.0.0
  57. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/site_ruby/2.0.0/x86_64-darwin13.0.0
  58. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/site_ruby
  59. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/vendor_ruby/2.0.0
  60. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin13.0.0
  61. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/vendor_ruby
  62. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0
  63. /Users/gtheys/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/x86_64-darwin13.0.0

☝ I believe @ddfreyne meant #418 resolves the issue.

@strand Correct—my previous comment indeed meant to say #418 rather than #409!


Suggestion/Question: Voiding Excess Item in the system?

Any way to void extra items in the system once the dedicated chest in the system is full? Planned feature or upgrade card or is there already a way to do this that I am not comprehending?
Ex.  Dumping my pocket storage into a dump chest that then sorts all the materials to a grid of chests...but the system gets clogged with all the excess cobble and deepslate and things once the chest for these items are full and then fill the overflow/unsorted/misc. chest until eventually even the dump chest has no where to put anything.  Any chance for a workaround other than having to pick up all the excess items back up out of the system?

 :).  No plans to implement item voiding at this time.


Required variables

There's now were I could find the minimum variables needed for creating a cluster.
I believe the required are:

vpc_id
security_groups
zone_id
admin_password
subnets

@lortega  thank you for reviewing the module.
We will add a README file with some examples on how to use the module and minimum settings required.

@lortega  we added usage examples and description in https://github.com/cloudposse/terraform-aws-rds-cluster/releases/tag/0.3.0
Please let us know if that answers your questions, and if you need any help.


Make MAC tag length dependent on the ciphersuite

The variable TAG_BYTES is currently a hard-coded constant. To support future ciphersuites with variable MAC tag lengths, it would be good to make this a property of the ciphersuite.

fixed in #378


update version of github-api to include endpoint settings

closes issue #1

thanks :+1:

Thanks for making this awesome plugin!


docker-compose basic auth needs dubble dollar signs

What does this PR do?

Update example of basic auth in docker-compose.yml files.
Motivation
htpasswd encrypted passwords contain dollar signs. These dollar signs get evaluated from the environment in docker-compose files. This most probably results in emptied bits of the hash, causing basic auth to always fail. A double dollar sign ($$) prevents.
Really broke my Monday ;)
More

[x] Added/updated documentation

Additional Notes

Could rebase on the branch v2.0, thanks.

Could you rephrase the comment to, somehow, show the "real" hash, so the reader could visually see the difference between "1 dollared" and "2 dollared" please?

I've added a new commit implementing the change. Is that what you were thinking of? I hope it's not too messy, as comments in a compose file example. I didn't really know where else to put it.

Thanks @muhlemmer , the change is good for me. Could you rebase on the branch v2.0 please?

Thanks @muhlemmer , the change is good for me. Could you rebase on the branch v2.0 please?

Done


Changing interval frequency field to use go standard time format

Issue #1246  - Adjust Interval frequency so that uses Go standard time format.
Should allow miliseconds, microseconds, as well as nonoseconds.
Signed-off-by: xmlviking<EMAIL_ADDRESS>

Is this going to cause configuration files made for EdgeX 1.0.x break? Is breaking backwards compatibility for configuration files considered a major-version-changing break?

Is this going to cause configuration files made for EdgeX 1.0.x break? Is breaking backwards compatibility for configuration files considered a major-version-changing break?

Michael as it sits right now this would break backward compatibility.  The request was to update scheduler interval's to use more prevalent go time format for frequency.

Codecov Report

Merging #1625 into master will decrease coverage by 0.1%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master    #1625      +/-   ##
==========================================
- Coverage   28.14%   28.03%   -0.11%
==========================================
  Files         124      124
  Lines       10988    10974      -14
==========================================
- Hits         3093     3077      -16
- Misses       7727     7728       +1
- Partials      168      169       +1

Impacted Files
Coverage Δ

internal/support/scheduler/utils.go
29.16% <36.36%> (+12.5%)
:arrow_up:

internal/support/scheduler/schedulecontext.go
66.66% <50%> (-9.81%)
:arrow_down:

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 eff56a4...ca1bf32. Read the comment docs.

Is it possible to implement this in a backward compatible way? I'm not sure what the syntactical relationship between ISO-8601 and RFC3339Nano is, but if there's no overlap between a valid ISO-8601 date and a RFC3339Nano date, then we could implement "smart parsing" which supports both formats automatically.
If there is overlap between the two formats, then perhaps for Fuji to not break backwards compatibility we add a new FrequencyFormat key which defaults to "ISO-8601" but also supports a "RFC3339Nano" value, then for services wishing to use RFC3339Nano, they could add that key and get the newer behavior.

Is it possible to implement this in a backward compatible way? I'm not sure what the syntactical relationship between ISO-8601 and RFC3339Nano is, but if there's no overlap between a valid ISO-8601 date and a RFC3339Nano date, then we could implement "smart parsing" which supports both formats automatically.
If there is overlap between the two formats, then perhaps for Fuji to not break backwards compatibility we add a new FrequencyFormat key which defaults to "ISO-8601" but also supports a "RFC3339Nano" value, then for services wishing to use RFC3339Nano, they could add that key and get the newer behavior.

Problem is the existing Intervals in an existing database.  Backward compatibility.

Problem is the existing Intervals in an existing database. Backward compatibility.

Well I'm not too familiar with the persistence implementation, but if we are storing the format specified directly then all that would happen is logic working with that would learn to also check for the FrequencyFormat specifier, if it was absent or empty it would work the same, otherwise parsing would continue based on what format was selected with that key.
If the Interval is converted to a time.Duration, then it probably would just work? If the format is deserialized out of the database into a time.Duration (i.e. just used directly) then no parsing would be necessary and it wouldn't matter if a Fuji or Edinburgh client wrote the entry into the database as both the ISO-8601 and RFC3339Nano would be serialized into the same time.Duration. If the format is yet some other different serialization (i.e. not the string from configuration.toml and also not a time.Duration), then I assume it could still work the same as described initially, checking if a FrequencyFormat key exists and basing deserialization logic on that.
Finally, I thought that @tsconn23 said we weren't going to support direct database migrations between releases even if those releases were backwards compatible?

Finally, I thought that @tsconn23 said we weren't going to support direct database migrations between releases even if those releases were backwards compatible?

@anonymouse64 You might be thinking of what I said in the fourth bullet point on this comment. The gist is that transitory data like events and readings should be drained before doing a minor version upgrade. All other data should be considered long-lived for the life of the major version as we don't want someone to have to re-provision their whole environment going from Edinburgh --> Fuji

@xmlviking can you speak to my questions about how intervals get serialized / deserialized into databases?

All other data should be considered long-lived for the life of the major version as we don't want someone to have to re-provision their whole environment going from Edinburgh --> Fuji

Understood, thanks for clarifying

Ian,
The issue with backward compatibility relates to what you mentioned.
Existing installations with Scheduler "Intervals" with the previous version
of the frequency format.  The actually date time is fine and is ISO 8601 so
we will be sticking with that for now.
Again to ensure were not breaking anyone's existing EdgeX environment were
holding off on the frequency change for now and wait till Fuji.
Eric
On Fri, Aug 16, 2019 at 9:04 AM Ian Johnson<EMAIL_ADDRESS>wrote:

@xmlviking https://github.com/xmlviking can you speak to my questions
about how intervals get serialized / deserialized into databases?
All other data should be considered long-lived for the life of the major
version as we don't want someone to have to re-provision their whole
environment going from Edinburgh --> Fuji
Understood, thanks for clarifying
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/edgexfoundry/edgex-go/pull/1625?email_source=notifications&email_token=AAXO7B6CFIHG3VASPQA6J4TQE2XWDA5CNFSM4IJMH3R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4OWL3Q#issuecomment-522020334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXO7B65VLPQSXZPZLYW6B3QE2XWDANCNFSM4IJMH3RQ
.

Thanks @xmlviking, unfortunately I didn't quite understand your comment as it doesn't seem to doesn't answer my question about how the scheduler intervals are serialized to a database like Mongodb.
In the meantime, I took the liberty of looking at the code myself and it seems that we serialize intervals with the ISO-8601 string exactly, which means that we could still implement this change in a backwards compatible manner by doing the following:

add a new FrequencyFormat string to the Interval spec (adding new strings doesn't break backwards compatibility for semver)
if the FrequencyFormat key is defined for a given Interval, then use that value to deserialize the Frequency string into a time.Duration
if the FrequencyFormat key is missing or not defined, then assume the format is ISO-8601 and deserialize appropriately

None of these changes would break an existing installation, though note I am assuming that mongo/redis can handle a new key added to a struct when serializing it.

@anonymouse64 - Ian could you please re-review this change request.  We decided that not changing the schema per say to include the format would not be required at this point.  The code simply supports both formats legacy format as well as the goLang style.  Changes have been made and implemented in the go-mod-contracts to support this bifurcation in the acceptable frequency format.  TY :)

We decided that not changing the schema per say to include the format would not be required at this point

I'm a little confused by this statement, did you change the schema or not? And is a format now included or not?

We decided that not changing the schema per say to include the format would not be required at this point

I'm a little confused by this statement, did you change the schema or not? And is a format now included or not?

No change in the schema.   No format field.   Were just accepting both old and new formats. It's the least invasion option.

We decided that not changing the schema per say to include the format would not be required at this point

I'm a little confused by this statement, did you change the schema or not? And is a format now included or not?
Ian,

Based on my analysis of the required areas in EdgeX-go I felt the path of least resistance might be a better approach.   Rather than include a new schema change to the type Interval I chose to enhance the go-mod-contracts serialize and deserialize functions.  I had to do this anyhow regardless of the approach I took.   I actually started with the full change you suggested but found I did not have to do that if I accounted for both the existing frequency time format and the proposed Go Lang standard way.
In summary I made changes to the go-mod-core contracts interval in the frequency validation section.  Additionally, I updated the validation for the interval frequency in the scheduler as well.   I have not included a schema change for any type persistence.  Nor have I included a new format field

Great, thanks for the in depth response Eric.
I personally won't be able to review this in depth this week, but it has my general +1 for the approach. If it's still open next week I will review, but feel free to merge without my approval this week

Great, thanks for the in depth response Eric.
I personally won't be able to review this in depth this week, but it has my general +1 for the approach. If it's still open next week I will review, but feel free to merge without my approval this week

still open requires rebase but requires your review Ian.   Let me know if you can't get around to this one and I can tap someone else.  Thanks :)

@brandonforster can I assume your changes have been integrated satisfactory for this PR?  I just don't want to assume they have been.

recheck


relation for borth friend

Bug description
firend table has two userid

How to reproduce
Run 'export DEBUG="*" &&  npx prisma migrate dev --preview-feature'
See error
Expected behavior

Error: Error: Database error: Error querying the database: Server error: `ERROR HY000 (1822): Failed to add the foreign key constraint. Missing index for constraint 'friends_ibfk_1' in the referenced table 'Users''
   0: migration_core::api::ApplyMigrations
             at migration-engine/core/src/api.rs:102

Prisma information

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema
datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Users {
  id        Int       @id @default(autoincrement())
  name      String
  createdAt DateTime  @default(now())
  updatedAt DateTime  @updatedAt
  Friends   Friends[]
}

model Friends {
  id           Int      @id @default(autoincrement())
  userId       Int
  friendUserId Int
  Users        Users    @relation(fields: [userId, friendUserId], references: [id, id])
  status       Boolean  @default(true)
  createdAt    DateTime @default(now())
  updatedAt    DateTime @updatedAt
}

Environment & setup

OS: macOS 10.15.7
Database: MySQL
Node.js version: v14.0.0
Prisma version:

@prisma/cli          : 2.13.0
@prisma/client       : 2.13.0
@prisma/cli          : 2.13.1
@prisma/client       : 2.13.1

Hey @CGerAJ
I am not sure what you are trying to refer here in the model. On a database level, you can't refer set it like that without a composite id on the User table.
If you want two sets of user, you can do something like this:
model Users {
  id                Int       @id @default(autoincrement())
  name              String
  createdAt         DateTime  @default(now())
  updatedAt         DateTime  @updatedAt
  userFriends       Friends[] @relation(name: "users")
  friendUserFriends Friends[] @relation(name: "friend_users")
}

model Friends {
  id           Int      @id @default(autoincrement())
  userId       Int
  friendUserId Int
  Users        Users    @relation(name: "users", fields: [userId], references: [id])
  FriendUsers  Users    @relation(name: "friend_users", fields: [friendUserId], references: [id])
  status       Boolean  @default(true)
  createdAt    DateTime @default(now())
  updatedAt    DateTime @updatedAt

  @@unique([userId, friendUserId])
}

ID
user_id
friend_id

1
1
2

2
1
3

3
2
3

User 1 has user 2 friends
User 1 has user 3 friends
User 2 has user 3 friends
user 1 friend is user 2 and user3
User 2's friend is user 3 and user 1
User 3's friend is user 1 and user 2
like this， can i do it, tks～

ID
user_id
friend_id

1
1
2

2
1
3

3
2
3

User 1 has user 2 friends
User 1 has user 3 friends
User 2 has user 3 friends
user 1 friend is user 2 and user3
User 2's friend is user 3 and user 1
User 3's friend is user 1 and user 2
like this， can i do it, tks～

The following model creates the required tables:
model Users {
  id                Int       @id @default(autoincrement())
  name              String
  createdAt         DateTime  @default(now())
  updatedAt         DateTime  @updatedAt
  userFriends       Friends[] @relation(name: "users")
  friendUserFriends Friends[] @relation(name: "friend_users")
}

model Friends {
  id        Int      @id @default(autoincrement())
  user_id   Int
  friend_id Int
  user      Users    @relation(name: "users", fields: [user_id], references: [id])
  friend    Users    @relation(name: "friend_users", fields: [friend_id], references: [id])
  status    Boolean  @default(true)
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  @@unique([user_id, friend_id])
}

You can also introspect(https://www.prisma.io/docs/concepts/components/introspection) the database if you are more comfortable in writing the schema in sql first.

The following model creates the required tables:
model Users {
  id                Int       @id @default(autoincrement())
  name              String
  createdAt         DateTime  @default(now())
  updatedAt         DateTime  @updatedAt
  userFriends       Friends[] @relation(name: "users")
  friendUserFriends Friends[] @relation(name: "friend_users")
}

model Friends {
  id        Int      @id @default(autoincrement())
  user_id   Int
  friend_id Int
  user      Users    @relation(name: "users", fields: [user_id], references: [id])
  friend    Users    @relation(name: "friend_users", fields: [friend_id], references: [id])
  status    Boolean  @default(true)
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  @@unique([user_id, friend_id])
}

You can also introspect(https://www.prisma.io/docs/concepts/components/introspection) the database if you are more comfortable in writing the schema in sql first.

Solved the problem, TKS

Solved the problem, TKS

Can anyone tell me how to query the friends table to get the friends details from the user table based on friends id from the friends table?

Probably not - close issues do not get any attention. Optimally open a new discussion and include your schema you are asking about.

@janpio ok


System.ArgumentException: oldValue is the empty string.

I had success logging in, and now I'm trying so subscribe to something.
With this code:
`public class SwitchUpdate : IHassApp
{
public async Task ExecuteAsync(EventData e, string rawData)
{
var a = "b";
return;
}
    public bool IsExecuting { get; set; }
    public string TriggeredByEntities { get; set; } = "light.*";
}`

I get the following error:
FATAL UNHANDLED EXCEPTION: System.ArgumentException: oldValue is the empty string.
I also have a similar IHassApp-implementation, triggered by sun.sun, which gives me the same error.
I'm using Xamarin, but I don't think it has anything to do with this?
I'm using Home Assistant 0.75.1.

I've now updated to the latest Home Assistant version, hoping this would fix it, but 0.76.1 now gives me:
'Unhandled Exception:
System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length occurred'

Hello friend!
Was the issue fixed? I could add you as a contributor to the repo if you
wanna fix something? 🙂
On Mon, 20 Aug 2018, 21:24 Sibren<EMAIL_ADDRESS>wrote:

Never mind.  :-D
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rille111/HomeAssistant.AppStarter/issues/2#issuecomment-414433361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ0nfujCrIjV95WKUJmS5cVyL_49HmTks5uSw0HgaJpZM4WEh_w
.


MudColor: Change ToString default mode to RGBA (#7275)

Description
Fixes #7275 by changing MudColor's ToString()-Method to default to RGBA instead of HexA.
How Has This Been Tested?
Html comparison / Visual confirmation on android device
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Shall we revert and cherry pick into the v7 branch?

Shall we revert and cherry pick into the v7 branch? But it is released already I think, right?

It's not: https://github.com/MudBlazor/MudBlazor/compare/v6.8.0...dev
Not sure how critical is the Android System WebView not supporting the 8digit rgba.
The use case is valid tho, when some app opens the page that is made on top of MudBlazor in the WebView , I use this for example in my android app when I want to show term of usage, data collection etc I just open it in the embdded view and show this information from my website.
I'm fine with this change living in v6 considering that v7 won't be released soon, I just don't know how many users we are going to break that for example compare the colors via toString again hex colors, as example

It is a bug fix then, all good.


为什么我的中文input会出现英文entity

Describe the bug
No response
Steps to reproduce
No response
Expected Behavior
No response
GraphRAG Config Used
No response
Logs and screenshots

Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

Please provide more detail about the bug you are experiencing.

my

请提供有关您遇到的错误的更多详细信息。

My input files are all in Chinese, but the extracted entities are in English, and the descriptions are also in English

You should change the default prompt for entity extraction.

You should change the default prompt for entity extraction.
I've changed it before, but English still appears.

在query那边还有几个prompt是英文的

在query那边还有几个prompt是英文的

都改了呀

把全部的prompt 改成中文，就可以了。然后自己定义好entity type

Consolidating language support issues here: #696


Move more of the Tokio setup into Bar, to keep main() simple?

We're expecting people will write their own main() to configure how the bar runs/which widgets are used, so we should try make it as simple as possible.

Done as of 86e1f4d888caddaceace0d04b3ddb879f1d64e0d.


Consideration for Q-Digest type?

Would like to get some feedback on if the format would accommodate describing Q-Digest metric types.
As Q-Digests are mergeable we've had success (albeit experimentally) merging aggregate Q-Digests across thousands of hosts for a single aggregation window and seen promising results for this data type.  We then convert to user specified quartiles and store those.
The advantage as an alternative to histograms is that no bucket selection needs to be made up front and the accuracy looks to be quite high.
This disadvantage as an alternative to histograms is that unless you store them in the storage layer they cannot be merged later with other series (unlike histograms which you can just add together).
I believe the case is compelling to support the data type so users can choose whether they want flexibility for emitting (Q-Digest) vs flexibility at query time (Histograms).

In terms of summary-based data structures / algorithms, t-digest is claimed to be mergeable and orders of magnitude more accurate than q-digest with smaller summaries . It also supports floating point numbers, while q-digest only supports integers.

There's two problems with Q-Digests/T-Digests.
Firstly they can't be sanely represented as time series, as they are mutating trees. We need things that are numbers and use labels sanely so that they can be of use and not blow-out storage for the TSDB on the other end.
Secondly you can't calculate a quantile over an arbitrary time frame like you can with a Histogram, the instrumentation library has to pre-choose the time frame and you need it to be consistent across all clients.
An additional disadvantage is that you can't pre-specify buckets. Many SLAs are written in the form 99% latency below 500ms, and people focus on the 99% rather than the 500ms. For an accurate answer as to how you're doing on your SLA you need a Histogram with a 500ms bucket.
For general background see https://github.com/prometheus/prometheus/issues/2682

I disagree with the first point as it's merely a deficiency of the current Prometheus implementation to only have a single floating point number as a value in a time series. Such a limitation should not leak into OpenMetrics.
I agree with the second point, though. The ability to calculate quantiles over arbitrary time frames is a helpful and very fundamental feature of Prometheus (rather than a limitation). See https://github.com/prometheus/prometheus/issues/2682#issuecomment-299844923 for details.
The third point is more a digression. In a situation where a fixed threshold like 500ms already exist (per SLO etc.), pre-defined buckets are indeed handy (also see http://www.apdex.org/ ). However, we are talking about situations where it is annoying to be forced to pre-define buckets, precisely because those fixed thresholds don't exist or are not in the focus if interest.

It's merely a deficiency of the current Prometheus implementation to only have a single floating point number as a value in a time series

Prometheus is not the only thing that might be on the other end, and as monitoring systems go we're already on the sophisticated side of things. Consider this data ending up in Graphite for example, where this would be an even more severe performance issue. I'd also hope for something that 100% works with the Prometheus of today, not a potential future Prometheus.
I'm partially using Prometheus as a stand-in for other monitoring systems. I would like to avoid having multiple overlapping types which require every single implementation on the other end to efficiently implement a myriad of different distribution types in order to cover all the potential use cases. Do we really need to have all the 5-6 distribution types mentioned so far? Can Summary/Histogram cover enough uses cases to be good enough?
I propose that we only accept types that are at least some way useful if the other end doesn't have first class type support as many many monitoring systems don't have such support. Neither will ad-hoc tools built to work with the format. For example even without the histogram_quantile function in Prometheus, a Histograms' buckets can still be treated as counters and graphed usefully. The Summary's quantiles can be graphed directly. That's not the case for any of the proposed digests/sketches.
A format where monitoring systems in common use have to drop a non-trivial proportion of the metrics due to not being able to support them and also have to keep that blacklist up to date isn't a great format. I'd like a format where we're forward compatible, so if a new type is added that systems that don't explicitly support it can still get something useful out of it.

I'm not advocating monitoring systems actually store Q-Digests.  We have the distinct use case, as do some others, for aggregating and calculating quartiles across a number of hosts without predefining buckets and then storing the quartiles.
Using Q-Digest in this manner is very similar to Summaries in Prometheus with the sole difference being the quartile calculation occurs by the monitoring system and as such means it can calculate an accurate quartile from readings across a large set of instances before storing calculated quartile values.

I propose that we only accept types that are at least some way useful if the other end doesn't have first class type support as many many monitoring systems don't have such support. Neither will ad-hoc tools built to work with the format. For example even without the histogram_quantile function in Prometheus, a Histograms' buckets can still be treated as counters and graphed usefully. The Summary's quantiles can be graphed directly. That's not the case for any of the proposed digests/sketches.

If you are exposing Q-Digest's at an exposition format, a naive system can very simply calculate the quartiles and store the quartile values.  Adhoc tools are very simple to write to support this use case.

Can Summary/Histogram cover enough uses cases to be good enough?

That's really the crux of the problem, we have seen very frequently that users outside of the Histogram use case want to monitor things not necessarily for SLA purposes and truly do want to just define quartiles that are accurate across multiple instances.
For instance "how long does my ML training job run for".  Defining buckets for a task that can take anywhere between 5 minutes to 5 hours becomes very tedious.  If the job suddenly takes 3x longer due to a code change you need to go update the Histogram buckets again.  If you're doing this over multiple machines Summaries starts to become a lot less useful.
The only way to achieve this is either collecting all raw samples from all instances and aggregating in a single place, or using Q-Digest and then letting a monitoring system merge them and store the quartile values.

If you are exposing Q-Digest's at an exposition format, a naive system can very simply calculate the quartiles and store the quartile values. Adhoc tools are very simple to write to support this use case.

I disagree that that's simple. That requires both first-class type support in the ingesting system and the ability to then do calculations across that data over time - something that I believe most monitoring systems lack. That implicitly also requires that monitoring systems store the Q/T-Digests.
This is the general issue I'm trying to point out, if we let in this class of thing it makes it much harder to implement as a monitoring system and practically speaking greatly restricts the class of monitoring system that can deal with it and may leads us back to the problems of vendor-specific "variations" we see with SNMP.

Defining buckets for a task that can take anywhere between 5 minutes to 5 hours becomes very tedious.

If something is taking that long, we're getting into the areas where metrics break down. Event logging is a better solution when we're into moderately long running batch tasks. We can actually manage this form of infrequent event logging with Prometheus via the pushgateway.

using Q-Digest and then letting a monitoring system merge them and store the quartile values.

If the data is over days, the question of what time period we're measuring the quantile over becomes even more important. The Prometheus Summary for example only does it over ~10m.

Closing this in favor of talking about support for metric aggregation in #69


fix(building-rollup): don't read user .browserslist

We take quite some assumptions in our config about browser support for the two different build outputs. Reading a user's browserslist is incompatible with that and can produce unexpected results or bugs.

I'm uncomfortable with clobbering user config without logging a warning

What do you mean by clobbering?
Basically this is a bug, we read a user's browserslist which can completely break the application.

To elaborate, I think a user's basic assumption will (and SHOULD) be that "if I specify a .browserslist, tools will respect it"
What I understood from your messages is that you think that would be a bug for this tool.
So my comment is not on design principles for building-rollup, it's on user expectations. If indeed you think building-rollup should in-all-cases-and-on-purpose ignore (in other words clobber) a user's config - and it's fine to take that approach - I think we should print a warning to the console to the effect that:

You are using a .browserslist config file, which @open-wc/building-rollup ignores. see https://owc.url/4jkd87 for more info

(and on that explainer doc we could give instruction on how to turn off the warning)
I'm certain that otherwise we're inviting our users to spend hours and hours debugging their toolchains when it was actually a design decision on our part to ignore their config.
Please correct me if I misunderstood anything

I see what you mean now, but I'm not sure that's a reasonable expectation. A browserslist is a very crude metric, not all tools can produce a valid outcome based on a browserslist alone. Especially when it comes to es modules, polyfilling browsers features etc.
The main clash is that we recommend users to create a separate for older browsers which don't support modern features. This means that we can't work with a single browserslist, and when people add one for eslint it breaks the build.


[Do not merge] [Data Factory] add tumbling window dependsOn property under stable

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

@haoyingli - do you have a timeline in mind for when this can be merged?

We're waiting for our backend code to be deployed in production first. The next scheduled deployment we get from ADF team is end of the week

Can one of the admins verify this patch?

Thanks @haoyingli - do you know if you are anticipating any further changes to this spec before the production roll-out finishes? Or is this spec already finalized?

@AutorestCI regenerate azure-sdk-for-go

@haoyingli - any updates on the status of this PR?

Hi, we are ready to merge the swagger. Could you please review it and let us know if it's OK to be merged to master?

I've updated the description. The format of timespan is internal only, should not expose to outside.


Add suport for virtual blockchains

Should be possible to create mini virtual blockchains for aiding with debugging of NEO smart contracts.
The blockchains should be stored as a .json file

Status: Mostly done, merged with Storage


Don't transform global position of mouse input

Fixes #25766
No idea why it was like this and if it doesn't break anything, but this is the correct behavior according to documentation (and common sense).

Seems good to me, but might break some projects if they relied on the previous wrong global position, so that should be prominently features in the changelog (@Calinou).

Thanks!

I was afraid of this commit and i tested in a too messy game project... and don´t break anything, i think it´s safe.


Added raylib-v7 and done edit as comparing between JavaScript binding…

@Rabios Great! Nice addition! 👍😄


Article idea: Javascript styleguides (not only CSS...)

The article would be about why it's important to follow a JS styleguide
It will be based on this AngularJS styleguide: https://github.com/johnpapa/angular-styleguide
What are your thoughts?

I think a comparision of various styleguides and what are interesting about each (in isolation and in comparision to each other) would be great. There is AirBNB's stylegude, Feross's Standard Stylegude and many more.

@shwetank I can write about that, focusing on pure Javascript, and only mentioning frameworks maybe.
Here is a list of Javascript styleguides:

Google Javascript Guide
Mozilla coding style
Crockford’s code conventions
Waldron’s Principles of Writing Consistent, Idiomatic JavaScript
Github coding style for Javascript
npm’s “funny” coding style
jQuery’s Javascript Style Guide
Feross' Javascript Standard Styleguide
Airbnb javascript style guide

I can write about each one, and compare the best ones in terms of style and tools provided.

Yes, that sounds great. If we can have an article which stays mostly neutral but at the same time provides a comparision of the different philosophies of each styleguide, then that would make for a great article.

@shwetank I'm gonna start working on it soon then, further hints are appreciated meanwhile.


fix: attr的path、polygon 增加相对refBBox的偏移

…pOffset 增加针对refBBox的相对平移

Description

Motivation and Context

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Enhancement (changes that improvement of current feature or performance)
[ ] Refactoring (changes that neither fixes a bug nor adds a feature)
[ ] Test Case (changes that add missing tests or correct existing tests)
[ ] Code style optimization (changes that do not affect the meaning of the code)
[ ] Docs (changes that only update documentation)
[ ] Chore (changes that don't modify src or test files)

Self Check before Merge

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

#4149 4134

#4134


WPF scroll wheel zooms to center (not to cursor)

make this work like the FormsPlot does

I remember now why this is hard: "zoom to pixel" may be wrong if display scaling is used


Update link in Github description

In the Github description you are linking to a broken Site (522 from Cloudflare)

Please update the link to https://get.foundation/emails/docs/ or something link that to avoid confusion

Done. Thanks for reporting this.


🐞 : URGENT FIX THE USER INTERFACE OF THE MAIN LANDING PAGE

:red_circle: Title : URGENT FIX THE USER INTERFACE OF THE MAIN LANDING PAGE
:red_circle: Bug : THE USER INTERFACE OF THE WEBSITE'S HOME PAGE IS TOTALLY DISTRUBE
:red_circle: Changes :   I WILL REVIEW THE CODE OF THE WHOLE USER INTERFACE OF TEH WEBSITE AND THEN BY ANALYSIS I WILL REARRANGED THE CODE AND WILL PROVIDE THE INTERACTIVE USER INTERFACE TO THE WEBSITE.
Screenshots 📷

✅ Details to Include When Taking the Issue:
Name : Dnyaneshwar Sambhaji Borse
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.):

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

fixed


Redirect for POST request does not work

I am trying to invoke POST request for a REST API. logging is enabled. From the console, i could see that addInfo is invoked, redirection happens to login page. The login page request is successful, but actual addInfo is not invoked. Not sure, what is the issue. I am using Ruby 1.9.3
RestClient.post("#{host}/addInfo", request_body_map.to_json,  {:authorization => "Basic #{Base64.strict_encode64("#{user}:#{pwd}")}", :accept => 'application/json',:content_type => 'application/json', :timeout => 30} ) { |response, request, result, &block|
if [301, 302, 307].include? response.code
puts "error code :302"
response.follow_redirection(request, result, &block)
else
response.return!(request, result, &block)
end
}

Going to close this out, but feel free to reopen.

ok fine.
with regards,
Srinivasan R
On Wed, Jan 28, 2015 at 11:54 AM, Andy Brody<EMAIL_ADDRESS>wrote:

Closed #312 https://github.com/rest-client/rest-client/issues/312.
—
Reply to this email directly or view it on GitHub
https://github.com/rest-client/rest-client/issues/312#event-225877812.


Would this work for a DLL file aswell?

Did you try it?

Traceback (most recent call last):
File "sigthief.py", line 248, in
writeCert(cert, options.targetfile, options.outputfile)
File "sigthief.py", line 120, in writeCert
flItms = gather_file_info_win(exe)
File "sigthief.py", line 27, in gather_file_info_win
flItms['MachineType'] = struct.unpack('<H', binary.read(2))[0]
struct.error: unpack requires a buffer of 2 bytes
Gives me an error. I ask this cause was this just designed to deal with EXE file?

sorry it works fine with DLL's as well. Cheers


[Feature Request] Service Worker

Hope support of Service Worker for better user experience...

Sorry, I don't want to add the Service Worker to this theme as default.
Here is why https://github.com/zzossig/hugo-theme-zzo/pull/77
You can add it by yourself though...

thanks for your reply


Power System Monitor

Summary of the new feature/enhancement
I would like to see all the system monitor infos which are offered via task manager in a small and neat form in the taskbar.

cpu usage
memory usage
incoming and outgoing network traffic
disk usages (reads and writes)
gpu usage
temperatures of cpu and gpu
fan speeds
usages over time (like in the linux screenshot)

All usages (CPU, MEM, GPU, disk, network) should be separated between system and user related processes.
In the settings the following should be configurable:

bar, pie or percent
color for each monitoring
graph over time or just current value
CPU total values or per core
Network total value or per network adapter
Fahrenheit or Celsius for temperatures

On left-click it should also open up a more detailed view.
Here are some screenshots of existing toolings:
Ubuntu

XMeters

Systempal

Have you used Speccy [by Piriform] ? Sound like that's what you're describing.

Have you used Speccy [by Piriform] ? It's a system (information) tool, it can show one thing in its taskbar icon, just without all the other things you would like to see. But maybe it'll do enough for you?

No I did not, yet. Just used XMeters so far. But Speccy sounds a lot more like HWInfo? And if it's only one icon in the taskbar it would not be enough for me...
I also prefer OS integrated tools over 3rd party. Or in this case, an open source project from the OS manufacturer over some 3rd party tooling ;)

Also, sounds similar to #5499

TaskbarStats app is great, I suggest you try it.
https://openhoangnc.github.io/taskbar-stats/

xref some features against https://github.com/microsoft/PowerToys/issues/828

Leaving comment to follow tracking of this enhancement

@CalmAussie
to subscribe to an issue, there is a dedicated button on each issue:

I know this is an old one, but I want to boost it up. There is news that Microsoft is adding support to Windows 11 to allow users to control RGB lighting on various accessories that have it. This will save users from having to install shady device-specific apps to handle that.
However, there is still a missing piece which is cooling. Both fan speed monitoring and temperature monitoring are not, and never have been included in Windows. Users who want that info have always had to install shady third party software. It's also something that only power users who can install Power Toys would be interested in.
Please add a PowerToy for monitoring temperatures and fan speeds. It's something that Windows really should have had 20+ years ago, but better late than never.

Does Dev Home's widget system work for you? https://github.com/microsoft/devhome

/needinfo

the devhome tool only works for win 11, that's why the feature has been suggested for powerToys

@kardix https://github.com/microsoft/devhome/issues/683 is that tracking issue


Replace break usage by continue 2 to remove Warning : alert

Remove warning alert cause of using break in a switch in a foreach
Alert appears by using PHP 7.3

@ZeEarth Hm... There is no any warning caused by break in switch on PHP 7.3. The continue instruction is causing the notice (see: https://3v4l.org/cRcKQ)
http://php.net/manual/en/migration73.incompatible.php#migration73.incompatible.core.continue-targeting-switch
I guess, you are still on zend-stdlib v2 (please check composer show), which is no longer supported and not compatible with PHP 7.3.

Hi @webimpress
Here you can find my composer show command result :
As you can see, I'm no more at v2 : zendframework/zend-stdlib              3.2.0
C:\dev\src\mpec\nextgen\api> composer show
bshaffer/oauth2-server-php             v1.10.0 OAuth2 Server for PHP
cakephp/cache                          3.7.4   Easy to use Caching library with support for multiple caching backends
cakephp/collection                     3.7.4   Work easily with arrays and iterators by having a battery of utility traversal methods
cakephp/core                           3.7.4   CakePHP Framework Core classes
cakephp/database                       3.7.4   Flexible and powerful Database abstraction library with a familiar PDO-like API
cakephp/datasource                     3.7.4   Provides connection managing and traits for Entities and Queries that can be reused for different datastores
cakephp/log                            3.7.4   CakePHP logging library with support for multiple different streams
cakephp/utility                        3.7.4   CakePHP Utility classes such as Inflector, String, Hash, and Security
container-interop/container-interop    1.2.0   Promoting the interoperability of container objects (DIC, SL, etc.)
doctrine/instantiator                  1.0.5   A small, lightweight utility to instantiate objects in PHP without invoking their constructors
herrera-io/json                        1.0.3   A library for simplifying JSON linting and validation.
herrera-io/phar-update                 1.0.3   A library for self-updating Phars.
justinrainbow/json-schema              1.6.1   A library to validate a json schema.
kherge/version                         1.0.1   A parsing and comparison library for semantic versioning.
michelf/php-markdown                   1.8.0   PHP Markdown
myclabs/deep-copy                      1.7.0   Create deep copies (clones) of your objects
paragonie/random_compat                v2.0.17 PHP 5.x polyfill for random_bytes() and random_int() from PHP 7
phpdocumentor/reflection-common        1.0.1   Common reflection classes used by phpdocumentor to reflect the code structure
phpdocumentor/reflection-docblock      3.3.2   With this component, a library can provide support for annotations via DocBlocks or otherwise retrieve information that is embedded in a DocBlock.
phpdocumentor/type-resolver            0.4.0
phpspec/prophecy                       1.8.0   Highly opinionated mocking framework for PHP 5.3+
phpunit/php-code-coverage              4.0.8   Library that provides collection, processing, and rendering functionality for PHP code coverage information.
phpunit/php-file-iterator              1.4.5   FilterIterator implementation that filters files based on a list of suffixes.
phpunit/php-text-template              1.2.1   Simple template engine.
phpunit/php-timer                      1.0.9   Utility class for timing
phpunit/php-token-stream               1.4.12  Wrapper around PHP's tokenizer extension.
phpunit/phpunit                        5.7.27  The PHP Unit Testing framework.
phpunit/phpunit-mock-objects           3.4.4   Mock Object library for PHPUnit
psr/container                          1.0.0   Common Container Interface (PHP FIG PSR-11)
psr/link                               1.0.0   Common interfaces for HTTP links
psr/log                                1.1.0   Common interface for logging libraries
robmorgan/phinx                        0.10.6  Phinx makes it ridiculously easy to manage the database migrations for your PHP app.
sebastian/code-unit-reverse-lookup     1.0.1   Looks up which function or method a line of code belongs to
sebastian/comparator                   1.2.4   Provides the functionality to compare PHP values for equality
sebastian/diff                         1.4.3   Diff implementation
sebastian/environment                  2.0.0   Provides functionality to handle HHVM/PHP environments
sebastian/exporter                     2.0.0   Provides the functionality to export PHP variables for visualization
sebastian/global-state                 1.1.1   Snapshotting of global state
sebastian/object-enumerator            2.0.1   Traverses array structures and object graphs to enumerate all referenced objects
sebastian/recursion-context            2.0.0   Provides functionality to recursively process PHP variables
sebastian/resource-operations          1.0.0   Provides a list of PHP built-in functions that operate on resources
sebastian/version                      2.0.1   Library that helps with managing the version number of Git-hosted PHP projects
seld/jsonlint                          1.7.1   JSON Linter
symfony/config                         v4.2.4  Symfony Config Component
symfony/console                        v4.2.4  Symfony Console Component
symfony/contracts                      v1.0.2  A set of abstractions extracted out of the Symfony components
symfony/filesystem                     v4.2.4  Symfony Filesystem Component
symfony/polyfill-ctype                 v1.9.0  Symfony polyfill for ctype functions
symfony/polyfill-mbstring              v1.10.0 Symfony polyfill for the Mbstring extension
symfony/yaml                           v3.4.14 Symfony Yaml Component
webmozart/assert                       1.3.0   Assertions to validate method input/output with nice error messages.
zendframework/zend-authentication      2.6.0   provides an API for authentication and includes concrete authentication adapters for common use case scenarios
zendframework/zend-code                2.6.3   provides facilities to generate arbitrary code using an object oriented interface
zendframework/zend-component-installer 1.1.1   Composer plugin for automating component registration in zend-mvc and Expressive applications
zendframework/zend-config              3.2.0   provides a nested object property based user interface for accessing this configuration data within application code
zendframework/zend-console             2.7.0   Build console applications using getopt syntax or routing, complete with prompts
zendframework/zend-crypt               3.3.0   Strong cryptography tools and password hashing
zendframework/zend-db                  2.9.3   Database abstraction layer, SQL abstraction, result set abstraction, and RowDataGateway and TableDataGateway implementations
zendframework/zend-debug               2.6.0   Safely dump debug information to HTML
zendframework/zend-developer-tools     1.2.1   Module for developer and debug tools for use with zend-mvc applications.
zendframework/zend-dom                 2.7.1   provides tools for working with DOM documents and structures
zendframework/zend-escaper             2.6.0   Securely and safely escape HTML, HTML attributes, JavaScript, CSS, and URLs
zendframework/zend-eventmanager        3.2.1   Trigger and listen to events within a PHP application
zendframework/zend-filter              2.8.0   provides a set of commonly needed data filters
zendframework/zend-http                2.8.2   Provides an easy interface for performing Hyper-Text Transfer Protocol (HTTP) requests
zendframework/zend-hydrator            2.4.0   Serialize objects to arrays, and vice versa
zendframework/zend-inputfilter         2.8.2   Normalize and validate input sets from the web, APIs, the CLI, and more, including files
zendframework/zend-json                3.1.0   provides convenience methods for serializing native PHP to JSON and decoding JSON to native PHP
zendframework/zend-loader              2.6.0   Autoloading and plugin loading strategies
zendframework/zend-math                3.1.1   Create cryptographically secure pseudo-random numbers, and manage big integers
zendframework/zend-modulemanager       2.8.2   Modular application system for zend-mvc applications
zendframework/zend-mvc                 3.1.1   Zend Framework's event-driven MVC layer, including MVC Applications, Controllers, and Plugins
zendframework/zend-paginator           2.8.1   zend-paginator is a flexible component for paginating collections of data and presenting that data to users.
zendframework/zend-permissions-acl     2.7.0   Provides a lightweight and flexible access control list (ACL) implementation for privileges management
zendframework/zend-permissions-rbac    2.6.0   provides a role-based access control management
zendframework/zend-router              3.2.0   Flexible routing system for HTTP and console applications
zendframework/zend-servicemanager      3.3.2   Factory-Driven Dependency Injection Container
zendframework/zend-stdlib              3.2.0   SPL extensions, array utilities, error handlers, and more
zendframework/zend-test                3.2.0   Tools to facilitate unit testing of zend-mvc applications
zendframework/zend-uri                 2.6.1   A component that aids in manipulating and validating » Uniform Resource Identifiers (URIs)
zendframework/zend-validator           2.10.2  provides a set of commonly needed validators
zendframework/zend-view                2.10.0  provides a system of helpers, output filters, and variable escaping
zfcampus/zf-api-problem                1.3.0   ZF2 Module providing API-Problem assets and rendering
zfcampus/zf-apigility                  1.4.0   Apigility module for Zend Framework
zfcampus/zf-apigility-admin            1.6.0   Apigility Admin module
zfcampus/zf-apigility-admin-ui         1.3.9   Apigility Admin UI module
zfcampus/zf-apigility-documentation    1.3.0   Apigility API documentation module
zfcampus/zf-apigility-provider         1.3.0   Apigility interfaces
zfcampus/zf-asset-manager              1.2.0   Composer plugin for copying module assets into application document roots.
zfcampus/zf-composer-autoloading       2.1.0   Sets up Composer-based autoloading for your Zend Framework modules
zfcampus/zf-configuration              1.3.3   Zend Framework module providing a REST resource for manipulating configuration
zfcampus/zf-console                    1.4.0   Library for creating and dispatching console commands
zfcampus/zf-content-negotiation        1.4.0   ZF Module providing content-negotiation features
zfcampus/zf-content-validation         1.6.1   Zend Framework module providing incoming content validation
zfcampus/zf-deploy                     1.3.0   Deployment tool for Zend Framework applications
zfcampus/zf-development-mode           3.2.0   Zend Framework development mode script
zfcampus/zf-hal                        1.5.0   ZF2 Module providing Hypermedia Application Language assets and rendering
zfcampus/zf-mvc-auth                   1.5.1   ZF2 Module providing Authentication and Authorization events and infrastructure
zfcampus/zf-oauth2                     1.5.0   ZF module for implementing an OAuth2 server
zfcampus/zf-rest                       1.5.0   ZF Module providing structure for RESTful resources
zfcampus/zf-rpc                        1.4.0   ZF2 Module for simplifying the creation of RPC services
zfcampus/zf-versioning                 1.3.0   ZF2 Module providing listeners and route prototypes for implementing API versioning
And the warning message when 7.3 is activate :

Best Regards

@ZeEarth
You are using version 3.2.0 but support of PHP 7.3 has been added in version 3.2.1 - see:
https://github.com/zendframework/zend-stdlib/releases/tag/release-3.2.1
Please run composer update to update your dependencies, or just:
composer update zendframework/zend-stdlib

to update only zend-stdlib.

crap ...
Sorry for that, I install apigility by composer command.
You can close this PR


No build provided for release 1.1.0?

Hi.
Sorry to bother you, but I have noticed that for the releases 1.0.7 and 1.1.0 you are no longer providing a .zip file with the build of the plugin (the .jar file), only the source code. I don't know how to build a plugin for IntelliJ from the source code and the builds you made with the previous releases were really helpful.
Would you consider providing a build for the latest release, please? :)
Thanks again for this great plugin and for working so hard on it. I love it so much.

that's my mistake. but i found a SSSSSS level bug, so i cancelled this release. it will comes soon.

Hi again. Thanks for your reply and for the new build :)

U are welcome. and also welcome your suggestions, bugs feed back ...


SDK Checks and waypointIndices

Wraps all registerReceiver's in SDK check: if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU).
Adds waypointIndices builder option to NavigationRoute.

Thanks a lot for looking into this, I think this fixes an issue mentioned by @Fabi755 as well regarding the SDK check 👍
Just one minor thing, could you add your changes to the CHANGELOG.md?

Added 👍

Thanks a lot for these fixes @Archdoog 👍


release v1.9.0

v1.9.0 is being tracked under the milestone at https://github.com/sparklemotion/nokogiri/milestone/16

Please note that v1.9.0.rc1 has been released. See https://github.com/sparklemotion/nokogiri/releases/tag/v1.9.0.rc1 for details.

OK - I've been waiting for libxml 2.9.9 to drop for a few weeks; regardless of whether it drops this weekend, I'll cut v1.9.0 final.

Also please note that I'm holding off on Ruby 2.6 support until the next release, which should be a fast-follow to this release. Ruby 2.6 is scheduled to drop in less than two weeks.

v1.9.0 has been shipped: https://github.com/sparklemotion/nokogiri/releases/tag/v1.9.0


Remove unnecessary dependency

Resolves #303 and #364.
By removing distrax, we can unify the way the code is written.
tensorflow-datasets is no longer necessary as example code moves to sampling-book. (btw, huggingface datasets is lightweight and meets requirements)
A few important guidelines and requirements before we can merge your PR:

[ ] If I add a new sampler, there is an issue discussing it already;
[x] We should be able to understand what the PR does from its title only;
[ ] There is a high-level description of the changes;
[x] There are links to all the relevant issues, discussions and PRs;
[x] The branch is rebased on the latest main commit;
[x] Commit messages follow these guidelines;
[x] The code respects the current naming conventions;
[x] Docstrings follow the numpy style guide
[x] pre-commit is installed and configured on your machine, and you ran it before opening the PR;
[ ] There are tests covering the changes;
[x] The doc is up-to-date;
[ ] If I add a new sampler* I added/updated related examples

Consider opening a Draft PR if your work is still in progress but you would like some feedback from other contributors.

Thank you!


Types won't import, even after following the instructions in README

Happens with IDA Pro 8.3

this will be fixed in the next update (hopefully), i think #3 fixes this

#3 did in fact fix this


Enable transport over WebSocket (with support of wasm)

I have an experimental implementation of a Connector which allows to tunnel gRPC communication over a WebSocket. This makes it possible to implement a gRPC-over-WebSocket server and more importantly also a client. With small patches of h2 and tower-buffer the client also runs in wasm32.

Implementation incl. examples: https://github.com/boxdot/tonic-ws-transport
Patch of tonic: https://github.com/boxdot/tonic/commit/b06a97dc563eb41f3ff7f4399befd7d872dae090
Patch of h2: https://github.com/boxdot/h2/commit/03838652b2b2a40c46df44a8299ebc1a9236939c
Path of tower-buffer: https://github.com/boxdot/tower/commit/1091340a3eb106da844348bc1b1ef7ce7b4a763d

If you find this useful and my approach as suitable, I would like to discuss how to move forward from here.
Feature Request
Crates

tonic (transport module)
h2
tower-buffer

Motivation
Run gRPC in browser.
Proposal
(High level)

Expose the client parts that are independent of TCP and work in wasm as a separate feature.
Use this new feature and the new tonic-ws-transport crate to enable implementations of wasm clients.

I am not sure if this should become a separate feature of tonic crate though, or we could do it differently. Due to this bug in cargo (https://github.com/rust-lang/cargo/issues/2524), we might run into problems if we choose conditional compilation based on wasm32 target arch.
Notes:

Implementation and patches are based on tokio 0.2 branch.
https://github.com/rust-lang/cargo/issues/2524
Examples are not part of the experimental crate due to another cargo bug: https://github.com/rust-lang/cargo/issues/1796

Sorry for the delayed response on this!
Is there a spec for gRPC over WS? Beyond gRPC web?

Sorry for the delayed response on this!
Is there a spec for gRPC over WS? Beyond gRPC web?

I don't think so. The idea was just to use websocket as a tunnel for the TCP transport in environments where TCP is not available but WebSocket is (e.g. browsers). Since gRPC runs on top of HTTP2, and HTTP2 on top of TCP, and my crate allows TCP to run on top of a WebSocket, it is completely transparent to gRPC.
Actually, I am now also using the tonic-ws-transport crate for an implementation of a WebSocket->Http2 reverse proxy. Just used the WsConnector in hyper::Server. So, I guess a better name for the crate would be just websocket-tcp-transport.

Yeah, lets put this on hold to get into tonic, but I want to circle back once I write the new transport and maybe we can get things to fit in so its easy to write this as an external crate.

Sure. Would it be possible to expose the parts of transport that are wasm32 compatible under a feature flag? At least this would allow to use the client in wasm. See https://github.com/boxdot/tonic/commit/b06a97dc563eb41f3ff7f4399befd7d872dae090.

Potentially, I plan to basically extract all the transport stuff so the tonic crate is just a grpc impl. That should make it much easier to get WASM things working with it.

@boxdot I'm trying to make my library buildable to WASM, I've applied your patches to this dependency but later when I tried to compile it with wasm-pack build --target web I got this amount of errors. They're coming from tonic hyper.
Is there any way to make hyper (and socket2) build to WASM?

@boxdot this seems reasonable maybe we can try getting into h2 first I see you have an issue but maybe we can talk with @seanmonstar again about it?

@LucioFranco Yes, it makes sense to start with h2, since it is a tiny patch. We just need to figure out how to make it least intrusive. I will pick up the issue there again. Thanks.

Changes for this have been upstreamed to hyper and h2. How should the discussion proceed to make this a reality in tonic?

Changes for this have been upstreamed to hyper and h2. How should the discussion proceed to make this a reality in tonic?

I will upgrade my repository and integrate the latest tonic changes. Then we will hopefully see which minimal changes are needed to tonic.

Do you have a link to those upstream changes?

h2 got an option to configure the max concurrent reset streams. The non-wasm compatible Instant::now is now only used when it is configured to be > 0. More details here: https://github.com/hyperium/h2/issues/511
The same configuration was exposed in hyper: https://github.com/hyperium/hyper/pull/2535
About my patch of tonic: I introduced a feature flag, which disabled all non-client and os-specific code in transport s.t. it compiles and runs on wasm32-unknown-unknown. This was done before the above patches were merged on version 0.3 of tonic.

This patch https://github.com/boxdot/tonic/commit/1da79d033b50ab08495ccbdfe287278a6192921e adds a feature flag to tonic which disables all non-wasm compatible parts of transports and enables compilation of generated tonic clients to wasm32. It also avoids using any browser incompatible runtime features.
@LucioFranco If you think that this approach is suitable, I can open a PR.
With this patch it is possible to tunnel any tonic client through a websocket in browser. Cf. https://github.com/boxdot/tonic-ws-transport/tree/1400e63d578044d1399fb63fa591c52c0502b6d0/examples

@boxdot Yeah, can you open a PR? I'd like to give this a review (I quickly looked over the code you posted).

Since Google updated their plan to only support grpc over WebTransport this issue should maybe closed/reworked?
It would be good for tonic to support WebTransport as an optional transport layer for the server at least. A client implementation could be useful as well tho.


Script stops abruptly if SSL error is encountered

Line 280-281 has:
except Exception as e:
     parser_error("invalid input defined or SSL error: %s" % e)

And parser_error() calls sys.exit().
This causes the following loop to terminate the execution mid-way, leaving the remaining endpoints unprocessed:
if args.domain:
    for endpoint in endpoints:

        <snipped>

        except Exception as e:
            parser_error("invalid2 input defined or SSL error: %s" % e)
        print("")

I'm not sure if this is intended behaviour - thought I'd just report the issue. Feel free to close this if you think it's not something that needs to be fixed.
Cheers,
Amal

Hi Amal,
This is actually a very interesting point you raise. Indeed when going over a bunch of domains one shouldn't trip up the entire process. I'll think about a good solution.
Regards,
Gerben


[BUG] Item "<item_id>" does not exist! error message on destruction.

Module Version: v1.6.3
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Create a magic item that will have just one charge and is destroyed on use.
Use that item.
Error message shows after item is removed.

Expected behavior
No exception
Browser:

Firefox

Foundry Version:
Game System: D&D 3.0.3
Additional context
First reported in Discord thread

Closed with 1.7.0


<Value not supported by UI, see YAML> error when copy/pasting key=value pairs

Setup

Rancher version: 2.6.2
Browser type & version: Google Chrome

Describe the bug
Error <Value not supported by UI, see YAML> when copy/pasting  key=value pairs in config map, labels, annotations, etc.
Expected Result
Old UI behavior
Screenshots

Thanks for submitting this issue. I've tested in the latest version 2.6.3 (released I think today) and this has been resolved, possibly via https://github.com/rancher/dashboard/pull/4491


How do you extract activations and select windows in your code?

Hi, @OdysseasKr
How do you extract activations and select window width in your code as written in Neural NILM?

extract activations

select window width

THANKS!

Hi @Hessen525. This code is based on the architectures of Neural NILM but uses the raw timeseries of the dataset. So there is no data augmentation and the window size is picked by the experimentor.
This repo is meant act as a boilerplate for your own experiments so I can not make suggestions in terms of data extraction, windows etc.

Hi @Hessen525. This code is based on the architectures of Neural NILM but uses the raw timeseries of the dataset. So there is no data augmentation and the window size is picked by the experimentor.
This repo is meant act as a boilerplate for your own experiments so I can not make suggestions in terms of data extraction, windows etc.

All right!Thanks!
I have another question about mains.good_sections() in your code.
Does it split the whole  test_elec.mains().all_meters()[0]  into several sections automatically?

According to NILMTK documentation

sections : list of TimeFrame objects
Each good section in df is marked with a TimeFrame. If this df ends with an open-ended good section (assessed by examining look_ahead) then the last TimeFrame will have end=None. If this df starts with an open-ended good section then the first TimeFrame will have start=None.

For NILMTK-related code it's better to refer to their documentation.


[KASPAROV] Test with ruby 2.6.6 on Kasparov

Test with ruby 2.6.6 on Kasparov

Failure with blaster outer... starting over.

Failure with blaster outer... starting over.


Webserver not working

The webserver keeps giving internal 500 error

Please let us know which server/tutorial ID/etc.


docs(samples): test_batch_process_documents_with_bad_input failing test fix

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Issue was fixed, The API was not providing public errors so would return 500


Paralel backup

To make tests in Dev machine

Codecov Report

Merging #705 (3ec262c) into dev (28b24a3) will decrease coverage by 0.16%.
The diff coverage is 1.88%.

@@            Coverage Diff             @@
##              dev     #705      +/-   ##
==========================================
- Coverage   41.57%   41.41%   -0.17%
==========================================
  Files         337      337
  Lines       24786    24891     +105
==========================================
+ Hits        10306    10308       +2
- Misses      14480    14583     +103

Flag
Coverage Δ

unittests
41.41% <1.88%> (-0.17%)
:arrow_down:

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

Impacted Files
Coverage Δ

dbaas/backup/tasks.py
38.91% <1.88%> (-10.42%)
:arrow_down:

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 28b24a3...3ec262c. Read the comment docs.


Unable to handle null values between js and the lua vm

The package does not handle null values properly when sending data structures between javascript and the lua vm.
First of all, the enableProxy setting needs to be set to false to ensure that data structures from javascript is not delivered as userdata, which is impossible to for iterate or recurse if such needs exists on the data.
If injectObjects is set to false, it will halt the execution with "decoration.target is null" when trying to deliver data to the lua vm. If injectObjects is set to true, it will successfully deliver the data structure to the lua vm, however any null-value attribute will be of type userdata.
The issue: it would be nice if null data can be delivered as nil in lua.
Example with injectObjects is false:
const lua = await factory.createEngine({ enableProxy: false, injectObjects: false  });

lua.global.set('null_isnot_nil', () => { const o={ notnil: null }; return o; });

in the lua code:
result = null_isnot_nil();
This will result in the mentioned: "decoration.target is null".
Example with injectObjects is true:
const lua = await factory.createEngine({ enableProxy: false, injectObjects: true  });
in the lua code:
result = null_isnot_nil();

print (type(result));

This will give the answer "userdata". It would be nice that null values are delivered as nil in lua. Userdata is not particularly useful and userdata from javascript is also protected, so it is impossible to get the metatable of the data.

Hi @janfrodej
When I PR'd adding the null type I wanted to have it distinct from nil because nil is equivalent to undefined in JS.
This stemmed from a need to differentiate between null and undefined from a Lua perspective when making API calls to REST APIs where you want to explicitly send null.
> JSON.stringify({ a: undefined })
'{}'
> JSON.stringify({ a: null })
'{"a":null}'

Setting a field to undefined/nil means the field is not sent at all.
If you want nil to act as null I'd recommend copying the current null type extension and instead of pushing userdata when null is seen use a lua_pushnil.
When you set injectObjects to true null is injected into Lua's global scope. So if you pass a null from JS to Lua then you can check if it's null within Lua by doing value == null.

If injectObjects is set to false, it will halt the execution with "decoration.target is null" when trying to deliver data to the lua vm. If injectObjects is set to true, it will successfully deliver the data structure to the lua vm, however any null-value attribute will be of type userdata.
The issue: it would be nice if null data can be delivered as nil in lua.

That was the behaviour before @tims-bsquare, I think it makes sense when injectObjects is false. What do you think about a builtin type extension "lightnull" to be used in this case which just convert to nil/undefined?

I've put some comments on his PR and I think overall he has a fair point but I'm not certain on the implementation


Deprecation: Swoole\Coroutine\Barrier

Swoole\Coroutine\Barrier will be deprecated in the future versions because it is confusing users, use waitGroup instead:
https://www.swoole.co.uk/docs/modules/swoole-coroutine-waitgroup

Added notice: https://github.com/openswoole/swoole-src/pull/55

Available in v4.8.0


Flatpak Build Bundle hangs

I ran flatpak build-bundle repo resolve.flatpak com.blackmagic.Resolve for 29 minutes and nothing happened. Is there something that I missed?

The build process was previously without console output. Depending on which version of the repository you tried to build, this may apply to you. Building, at least for me, took a long time (definitely over half an hour) so just be patient for a couple of hours.


OBS video format

It would be great if the videos on http://openbuildservice.org/ could be played with the default browsers in opensuse.
I'm not familiar with vimeo, but I'm assuming they have some options to change formatting of the embed player.

Maybe this changed in the meantime but vimeo serves tons of different formats by now...


Question about synchronous tasks

I'm currently investigating existing task queues for our project and had a couple of questions about how taskiq works.

Does taskiq run multiple tasks in each worker?
Not all libraries we use support asyncio.  What exactly does --max-threadpool-threads do?  Will @broker.task automatically work with synchronous functions with this, or would it be better to use loop.run_in_executor?

Also, how do you pronounce taskiq?

Hi!

Yes. Taskiq leverages asyncio at it's maximum and tries to run as many tasks as possible (We have a parameter for maximum number of concurrent tasks, though to not overload the loop). You can see how we execute tasks here: https://github.com/taskiq-python/taskiq/blob/9aae39758686fd6fbdeb3ea90559b64503d3ae76/taskiq/receiver/receiver.py#L339.

Taksiq takes care of that. You can find how it does it here: https://github.com/taskiq-python/taskiq/blob/9aae39758686fd6fbdeb3ea90559b64503d3ae76/taskiq/receiver/receiver.py#L229 If the function is sync, taskiq runs it in executor.  The max-threadpool-threads parameter configures how many threads are going to be assigned to the thread pool executor.

I pronounce it as taskick with the stress on a. But you can pronounce it as you wish.

Awesome, thanks!  One more question:  We will have some short-running tasks (e.g. 10 seconds) and some long-running tasks that are CPU bound (e.g. an hour).  This might be variable for the same task, but we could predict beforehand if it would take a very long time, so we could always split the into two tasks.  I'd like to go with a library that can support some way to handle this without the long-running tasks completely preventing the short-running tasks from being performed.
Ideally there would be some way to have some workers never accept longer tasks.  I was thinking maybe it would be nice if you could denote that a task shouldn't be run on more than x number of worker child process at the same time, though I don't know if that's feasible.  What I think maybe could be done currently would be to run taskiq worker multiple times.  Can you run taskiq worker multiple times passing different brokers so each would handle different tasks and still use the same e.g. Redis url/instance for the broker/backend?
Let me know if you have any better ideas.

Since taskiq is very flexible, you can do lot's of different setups. For this specific case, I would suggest to create  two brokers and use one for short tasks and one for long tasks.
You can swap brokers which sends task on the fly, by using kicker instead of calling kiq.

broker = Broker(...)
long_running_broker  = Broker(...)

@broker.task
async def my_task():
	pass

Then when you expect this task to run for very long time, you can call it this way, to not interfere into small tasks execution.

if long_running_expr:
	await my_task.kicker().with_broker(long_running_broker).kiq()

This way this task is going to run within long_running_broker, you will have multiple queues and worker groups, but I guess that's fine, since your idea was to keep long-running tasks and short-running tasks separate.
To run multiple worker processes, just run them with taskiq.
taskiq worker project.tkq:broker
taskiq worker project.tkq:long_running_broker

Of course, replace project.tkq with real path to the broker definition module.

Hi @s3rius! I have a similar question, does Taskiq support multiple queues? I have at least 5 different task types.
i am looking for something like https://stackoverflow.com/questions/19853378/how-to-keep-multiple-independent-celery-queues.
Thanks!

@Amitg1
You can define multiple broker in different files, with the queue specified, just make sure to add the right tasks to the different brokers
broker = JetStreamBroker("nats://localhost:4222", queue="my_queue2")
and than run the specific brokers with the cli separately
taskiq worker path.to.the.module:broker
taskiq worker path.to.the.second_queue:broker
etc


Access raw data returned from Slack

Is there any way to access raw data within the callback method? Certain properties are missing, like the team icon.

Currently I haven't put much raw info in it but it would go here: https://github.com/ueberauth/ueberauth_slack/blob/master/lib/ueberauth/strategy/slack.ex#L157
Would you be up for a PR?

Yes, will do. Thanks


Cannot upload doc

I am trying to upload the doc and I have the example curl below
curl -H "Authorization: token" \
    http://kellnr.mymachine.uk:8000/api/v1/docs/my_helper/0.1.0 \
    --upload-file doc.zip

However, I get this every time
Wrong number of path arguments for `Path`. Expected 1 but got 2. Note that multiple parameters must be extracted with a tuple `Path<(_, _)>` or a struct `Path<YourParams>`%

How do I fix this?
Cheers

Hi @tomus85. Sry for the late response. I'll have a look.

I tried to recreate the issue but failed.
cargo doc
cd target
zip -r doc.zip ./doc
curl -H "Authorization: token" http://localhost:8000/api/v1/docs/my_helper/0.1.0 --upload-file doc.zip

This uploaded the docs with no issue. Can you give me more information on your setup? Which Kellnr version do you use and can you provide the Cargo.toml of your project?

Hey, this is my compose set-up
version: "3"
name: kellnr
services:
    kellnr:
        ports:
            - 8000:8000
        environment:
            - KELLNR_ORIGIN__HOSTNAME=kellnrhost.<masked>.uk
            - KELLNR_SETUP__ADMIN_PWD=admin
            - KELLNR_SETUP__ADMIN_TOKEN=token
        volumes:
            - /home/<masked>/docker/kellnr/data:/opt/kdata
        image: ghcr.io/kellnr/kellnr:5.0.0

Ths is the Cargo.toml file
[package]
name = "my_helper"
version = "0.1.0"
authors = ["Thomas Curley <masked>"]
edition = "2018"

[dependencies]

I push publish this project without any issues.

I tried to replicate the issue with the additional information, but still failed. It works fine when I try it. I'm sorry, but I have no more ideas how to help you.

I'll close this issue, but if you have any more ideas what I can try, feel free to reopen it.

Can you give me a snippet of your config? I am still facing this issue


The fuzzy setting should compare original name with punctuation

If you want 100% to be sure and it compares e.g. "Elite: Dangerous" in library to "Elite: Dangerous" from their DB, the match isn't complete probably because it compares to the search version without punctuation.

#181

These are not quite the same as the other one talks about the search on HowLongToBeat being wrong and this one is about fuzzy matching being inaccurate. But they revolve about the same problem - punctuation not handled correctly.


[BUG] Error on every function using "Path" class on Windows

Hi there,
I've experienced an issue on multiple "get_" (and probably others that I haven't checked) function that use the "Path" class to construct the requested API URL.
Error example :
Traceback (most recent call last):
  File "C:\site-packages\requests\models.py", line 971, in json
    return complexjson.loads(self.text, **kwargs)
  File "C:\lib\json\__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "C:\lib\json\decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "C:\lib\json\decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
...SNIP...
  File "C:\pylookyloo\api.py", line 95, in get_status
    return r.json()
  File "C:\site-packages\requests\models.py", line 975, in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

After a bit of research i find that the issue was caused by this "Path" class which constructs the URL with backslash instead of normal slash under Windows. For example :
https://lookyloo.circl.lu/json\UUID\status
It happened only on Windows and I have NO problem on Linux, it just build URLs normally.
I've created this issue for people who use Windows for development and may encounter the same problem.
Congrats for this tool, it's insane !

Hi !
I've tried using as_posix in this line from the get_status function and it works well :
url = urljoin(self.root_url, str(Path('json', tree_uuid, 'status').as_posix()))
I've currently experienced only this issue but if I find another one while testing it on Windows, I'll let you know !

Perfectly working with this version !

Nice! Thank you for the feedback, I'm going to implement the same thing in a bunch of other libraries :)


Ignore non-enumerable properties on validators

fixes https://github.com/MaxLi1994/redux-validator/issues/3

Thanks for the pull request!

Thank you for your prompt response! 😄

@MaxLi1994 I know you just merged this in record time 😛  but is there any chance you might be able to make an npm release today? I'd be mighty grateful 😄

@effervescentia Done! the latest version is 0.2.2😁 Thx for your reminder

ayyyy 😎 you're the best @MaxLi1994 appreciate it!


feat: projects - [merged]

Merges feat-projects -> 14-feat-project-management
:books: Summary

Add projects model
:link: Links / References

#14

:construction_worker: Tasks

[ ] Add your tasks here if required (delete)

[ ] ~"breaking-change" Any Breaking change(s)
Breaking Change must also be notated in the commit that introduces it and in Conventional Commit Format.

[ ] ~Documentation Documentation written
All features to be documented within the correct section(s).