Add a cop to enforce aggregating examples

The "one expectation per example" rule has been relaxed and allows for several expectations to be set in the same example.
https://github.com/rubocop-hq/rspec-style-guide#expectations-per-example
In cases the examples don't have any setup, metadata, or even a docstring, and may be aggregated into one thus saving on sometimes expensive context setup.
The cop still does report the cases when the examples might be aggregated, but with some risk, e.g. when matchers with side effects are used. It makes sense to do so since eventually those matchers might be fixed to leave the subject in its original state.
Block expectation syntax is deliberately not supported due to:

subject { -> { ... } } syntax being hard to detect
aggregation should use composition with .and
aggregation of the not_to is barely possible when a matcher doesn't
provide a negated variant
aggregation of block syntax with non-block syntax should be in a
specific order

Known caveats:
The usages if its that are testing private methods/readers will result in spec failure. It's up to the user whether to replace with __send__, or test only public interface.
Original idea and initial implementation by @palkan
https://github.com/palkan/test-prof/blob/master/lib/test_prof/cops/rspec/aggregate_failures.rb
Total effort: 65h

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the changelog if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

If you have created a new cop:

[x] Added the new cop to config/default.yml.
[x] The cop documents examples of good and bad code.
[x] The tests assert both that bad code is reported and that good code is not reported.

Bump.

@bquorning Thanks for the review.
Actually, explicit subject [is supported as well]
(https://github.com/rubocop-hq/rubocop-rspec/pull/726/files#diff-65c1681945efcb2fb8eb9ebe1afd5bd6R325) (spec):
      describe do
        it { expect(division.result).to eq(5) }
        it { expect(division.modulo).to eq(3) }
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Aggregate with the example above.
      end

I used implicit subject in examples to avoid additional subject(...) { ... } line.
I completely get your point, unit tests are already fast enough usually to aggregate them, however sometimes aggregation might be used to reduce the size of the spec file.
The usual suspect of this cop are integration tests, if the setup is shared across several examples, and it's only the expectations differ, those can actually be aggregated. In the codebase I'm mostly working on it's was a rather frequent case.
This started off relaxing the "one expectation per example" rule, as it wasn't that strict in betterspecs compared to rspec-style-guide, then active development of this cop, and I believe is helping to reduce the effort to change the code, since if some part of the functionality is extracted, fewer examples should be changed, and smaller the chances to leave some legacy examples in the code.
I feel responsible for it, and Maxim is familiar with the code as well, as he was doing a number of internal code reviews.
I really hope that the size of the cop will be reduced eventually as its node matchers are extracted when the other cops find those parts useful.
Let's pair and I will walk you through the code if you like.
I'm not sure what is the best approach to highlight the disabled cops, just mention them in the docs? Inject into project's .rubocop-todo.yml somehow? The enabled/disabled distinction looks way too strict, I would rather go for recommended/optional, and would ask users to explicitly disable even those that are optional.

@bquorning I think I understand what you mean concerning the disabling by default.
There was a convention regarding cop versioning and enabling previously introduced disabled cops in next minor versions.
There are different styles of tests, and for some, it might not be a good fit, as it pivots the way the tests are written. However, while applying it to a big codebase I didn't see any really big issues with it (apart from numerous that I have addressed already, e.g. deliberately skipped block syntax and matchers with side effects).
Amongst codebases I've seen, there were always a good amount of disabled cops.
On the other hand, AggregateExamples is mutually exclusive with MultipleExpectations. However, it might be perceived as a single cop with two styles (like MessageExpectation that has two opposite style options), but split. I don't consider joining the two together as a good option though, as the former has grown huge already.
That being said, do you think this cop should remain disabled forever, or until the next minor rubocop-rspec release?

Updated to use the Language::RUNNERS from master.

I’ve read most of the code now, but as mentioned above I’m still struggling with the actual cop implementation. It may well be that I just need to pull myself together and focus :-)

Soon after its anniversary 50th commit, the cop is ready for another review @Darhazer, @bquorning.
Please find the reasoning behind some design decisions that I've made below.
What's new

significantly improved its support;
fixed --auto-correct showing all detected offenses as corrected;
fixed offense detection of matchers with side effects with qualifiers;
removed redundant spec coverage;
divided the code into logical parts (more on that below), that allowed removing disabling of Metrics/ClassLength on the cop;
extracted specs for its and matchers with side effects to dedicated spec files;
... and much more!

Why not object-oriented approach to divide the cop?
I tried to cleanly separate parts of the cop into self-contained objects and miserably failed.
Extraction to self-contained functional modules
The first approach I made was to extract logically related node matchers into modules. However, it turns out it's impossible to use other class's methods in node pattern, e.g.:
module Example
  module_function

  def_node_matcher :with_expectations_only, '...'
end

def_node_matcher :example_for_autocorrect?, <<-PATTERN
  [
    #Example.with_expectations_only?
    ...
  ]
PATTERN

So it comes with a burden of defining delegators, which made things look unreadable.
Extraction to self-contained classes
Another approach, which worked, was to extract all aggregation related logic to Aggregator class, that an autocorrect would pass up and RuboCop would call call upon.
Oddly, range_by_whole_lines that I make use of expects @processed_source to be accessible, so I had to pass it as an argument to Aggregator.new as well.
Furthermore, it needed cop_config, so I had to pass it as well. I ended up with:
    def autocorrect(example_node)
      clusters = example_clusters_for_autocorrect(example_node)
      return if clusters.empty?

      Aggregator.new(clusters, @processed_source, cop_config)
    end

    class Aggregator
      prepend Its
      include Metadata
      include RangeHelp

      attr_reader :cop_config, :clusters

      def initialize(clusters, processed_source, cop_config)
        @clusters = clusters
        @processed_source = processed_source
        @cop_config = cop_config
      end

      def call(corrector)
        clusters.each do |metadata, examples|
          range = range_for_replace(examples)
          replacement = aggregated_example(examples, metadata)
          corrector.replace(range, replacement)
          examples[1..-1].map { |example| drop_example(corrector, example) }
        end
      end

      # Plus a bunch of private methods
    end

It worked, but I wouldn't say it's less tangled.
Includable modules
I ended up with a design that I initially considered an interim one, modules all included into the cop.
Using prepending I achieved functional inheritance, that helped to hide the complexity behind some methods, specifically new_body and message_for being extended in MatchersWithSideEffects and Its.
Another sudden benefit was that documentation laid out quite well across those files.
How the documentation for the cop's is split across several files?
The intention was to spread the documentation over source files where it would correspond to the source code, e.g. core usage, usage of its, and usage with matchers with side effects.
Initially I was going to put it all on the class level, but it hit me by surprise that yard overrides the docs when is defined in several files for the same class (see this issue), it's impossible to spread the docs to several files so that they are compiled into one document (manual).
So I added support for gathering cop docs from modules in cop's namespace.
Please let me know what you think.

Updated with the latest master.
Please take a look.
I'm all for addressing your concerns, including making required systematic changes e.g. to how we recommend new cops.

@pirj could you explain how it's expected to aggregate these two examples:
subject { -> { do_side_effect } }

it 'has effect on this' do
  is_expected.to change {
    check_effect_this_way
  }.from(42).to(43)
end

it 'has effect on that' do
  is_expected.to change {
    check_effect_that_way
  }.from('foo').to('bar')
end

Consider I managed to aggregate two examples into one. Now I want to test the second one in isolation (because it has a bug). How it's expected to be done?
For me it's the same ani-pattern as iterationg overt tests like this
['foo', 'bar', 'baz'].each do |subject|
  test_it(subject)
end

because you can't run single example in isolation

@bolshakov Thanks for asking. Yes, that one would be easy:
def has_effect_on_this
  change {
    check_effect_this_way
  }.from(42).to(43)
end

def has_effect_on_that
  change {
    check_effect_that_way
  }.from('foo').to('bar')
end

it 'does this and that' do
  expect { do_side_effect }
    .to has_effect_on_this
    .and has_effect_on_that
end

You are testing side effects of calling do_side_effects. What do you mean by testing it in isolation, what would be the reason for that isolation? I'm not sure I correctly understand your question.
With aggregate_failures turned on, you will see all the expectation failures, even if there are several of them in the same example.
I'm not going to reason about to SRP, since the tests are usually just indicators of the production code flaws, and if the code does this and that doesn't necessarily mean that testing those two side effects is a benefit.
You might be interested in an open rspec-style-guide ticket to recommend against implicit block syntax.
The reasoning behind recommending against using iterators is different than lack of ability to test the expectations separately, it's:

When another developer adds a feature to one of the items in the iteration, they must then break it out into a separate test - they are forced to edit code that has nothing to do with their pull request.

The main reason someone may use such a cop is to improve spec performance. This is good to be noted in the docs.

This can easily lead to breaking the max example length or max expectations count. Should the cop be aware of those? Maybe the cop should wrap the example in aggregate_failures
I believe those two are mutually exclusive cops.

Just in case if someone would like to use this, the cop has found a place in test-prof.


[Enhancement] Decouple the static privilege check function from PrivilegeManager

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 241 / 403 (59.80%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/http/rest/GetLoadInfoAction.java
0
1
00.00%
[82]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadFunctionalExprProvider.java
0
1
00.00%
[253]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadFunctionalExprProvider.java
0
1
00.00%
[163]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
15
13.33%
[276, 326, 378, 402, 403, 495, 595, 802, 830, 844, 845, 1018, 1493]

:large_blue_circle:
com/starrocks/http/BaseAction.java
1
5
20.00%
[304, 317, 318, 319]

:large_blue_circle:
com/starrocks/privilege/PrivilegeActions.java
117
247
47.37%
[29, 42, 43, 44, 45, 46, 47, 48, 58, 59, 60, 61, 62, 63, 64, 78, 79, 80, 91, 92, 93, 94, 95, 96, 97, 110, 111, 112, 113, 114, 115, 116, 127, 128, 129, 130, 131, 132, 133, 144, 145, 146, 147, 148, 149, 150, 161, 162, 163, 164, 165, 166, 167, 180, 181, 182, 183, 184, 185, 186, 197, 198, 199, 200, 201, 202, 203, 215, 216, 217, 218, 219, 220, 222, 234, 235, 236, 237, 238, 239, 241, 259, 260, 261, 262, 263, 264, 266, 271, 275, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 306, 307, 308, 309, 355, 356, 357, 358, 405, 406, 407, 408, 409, 410, 411, 412, 427, 428, 429, 430, 431, 432, 433, 438, 439, 441, 443, 445, 447]

:large_blue_circle:
com/starrocks/load/ExportMgr.java
1
2
50.00%
[233]

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzerUtils.java
1
2
50.00%
[161]

:large_blue_circle:
com/starrocks/qe/ShowExecutor.java
9
12
75.00%
[1268, 1487, 1543]

:large_blue_circle:
com/starrocks/privilege/PrivilegeBuiltinConstants.java
4
5
80.00%
[20]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeCheckerV2.java
67
73
91.78%
[307, 1048, 1165, 1324, 1762, 1767]

:large_blue_circle:
com/starrocks/mysql/privilege/AuthUpgrader.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeStatusStmt.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/DataDescription.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/qe/ConnectScheduler.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowBasicStatsMetaStmt.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/privilege/PrivilegeManager.java
22
22
100.00%
[]

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ResourceGroupMgr.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ResourceMgr.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/service/InformationSchemaDataSource.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeJobStmt.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowHistogramStatsMetaStmt.java
1
1
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 252 / 410 (61.46%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/http/rest/GetLoadInfoAction.java
0
1
00.00%
[82]

:large_blue_circle:
com/starrocks/load/routineload/RoutineLoadFunctionalExprProvider.java
0
1
00.00%
[253]

:large_blue_circle:
com/starrocks/load/streamload/StreamLoadFunctionalExprProvider.java
0
1
00.00%
[163]

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
2
15
13.33%
[276, 326, 378, 402, 403, 495, 595, 802, 830, 844, 845, 1018, 1493]

:large_blue_circle:
com/starrocks/http/BaseAction.java
1
5
20.00%
[304, 317, 318, 319]

:large_blue_circle:
com/starrocks/privilege/PrivilegeActions.java
125
252
49.60%
[29, 46, 47, 48, 58, 59, 60, 61, 62, 63, 64, 78, 79, 80, 91, 92, 93, 94, 95, 96, 97, 110, 111, 112, 113, 114, 115, 116, 127, 128, 129, 130, 131, 132, 133, 144, 145, 146, 147, 148, 149, 150, 161, 162, 163, 164, 165, 166, 167, 180, 181, 182, 183, 184, 185, 186, 197, 198, 199, 200, 201, 202, 203, 215, 216, 217, 218, 219, 220, 222, 234, 235, 236, 237, 238, 239, 241, 259, 260, 261, 262, 263, 264, 266, 271, 275, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 306, 307, 308, 309, 355, 364, 365, 366, 367, 414, 415, 416, 417, 418, 419, 420, 421, 436, 437, 438, 439, 440, 441, 442, 447, 448, 450, 452, 454, 456]

:large_blue_circle:
com/starrocks/load/ExportMgr.java
1
2
50.00%
[233]

:large_blue_circle:
com/starrocks/qe/ShowExecutor.java
9
12
75.00%
[1271, 1490, 1546]

:large_blue_circle:
com/starrocks/privilege/PrivilegeBuiltinConstants.java
4
5
80.00%
[20]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeCheckerV2.java
67
73
91.78%
[307, 1048, 1165, 1324, 1762, 1767]

:large_blue_circle:
com/starrocks/mysql/privilege/AuthUpgrader.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeStatusStmt.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/DataDescription.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/qe/ConnectScheduler.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowBasicStatsMetaStmt.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/privilege/PrivilegeManager.java
22
22
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/AnalyzerUtils.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
3
3
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ResourceGroupMgr.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/ResourceMgr.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/service/InformationSchemaDataSource.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowAnalyzeJobStmt.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/ast/ShowHistogramStatsMetaStmt.java
1
1
100.00%
[]

run starrocks_admit_test

@Mergifyio backport branch-3.0


[QUESTION] Query DSL validator

Hello,
I was wondering if a OpenSearch Query DSL (https://opensearch.org/docs/latest/opensearch/query-dsl/index/) validator exists. My main goal is to validate query before executing search(); without using try, except.
Thanks in advance.

Update: for the moment, I request for validation at /_validate/query endpoint. See: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-validate.html


⚠ Spryr has degraded performance

In f6251d8, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3507 ms

Resolved: Spryr performance has improved in 09d7891 after 7 minutes.


Wireshark can't capture packets when running as normal user

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

Add programs.wireshark.enable = true; and programs.wireshark.package = pkgs.wireshark; to your system and add yourself to the wireshark group.
Try to capture anything, when starting wireshark on your user account (not root). It doesn't work

Expected behavior
Capturing packets works from my current user.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
I expected dumpcap to have an owner of wireshark and to have it's capabilities set as per https://github.com/NixOS/nixpkgs/blob/nixos-24.05/nixos/modules/programs/wireshark.nix.
[nix-shell:~]$ ls -l $(which wireshark)
lrwxrwxrwx 1 root root 76 Jan  1  1970 /run/current-system/sw/bin/wireshark -> /nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/wireshark

[nix-shell:~]$ ls -ahl /nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/*{wireshark,dumpcap}*
-r-xr-xr-x 1 root root 20K Jan  1  1970 /nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/dumpcap
-r-xr-xr-x 1 root root 20K Jan  1  1970 /nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/wireshark
[nix-shell:~]$ sudo getcap -v /nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/dumpcap
/nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/dumpcap

[nix-shell:~]$

Simply running wireshark as root also doesn't solve the issue, because I am testing a custom plugin (I didn't code it, I simply fixed some compilation errors). The custom plugin loads successfully on my user, but doesn't on root. (yes, I installed it both on root and on my user)
Notify maintainers
@bjornfor
@fpletz
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.32-rt32, NixOS, 24.05 (Uakari), 24.05.20240619.dd457de`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(root): `"nixos-24.05"`
 - nixpkgs: `/nix/store/2lvj8bm21ymxra61dqrc4xpzr8njgywj-source`

Add a :+1: reaction to issues you find important.

I believe (basing on code) dumpcap should be first found in PATH in /run/wrappers directory and there the binary/script/wrapper should be owned by wireshark group and have those needed caps set.

Weird, this works for me on unstable and I don't see any relevant changes to the wireshark module since the 24.05 release. What is the result of which dumpcap on your system and does /run/wrappers/bin/dumpcap exist?

After a couple of reboots the file permissions and caps suddenly changed to what you'd expect.
which dumpcap points to /run/wrappers/bin/dumpcap.
/run/wrappers/bin/dumpcap previously was a symlink to /nix/store/56wlcg8nixrcsrgyc0dqfpm0r72ylnwb-wireshark-qt-4.2.5/bin/dumpcap (similar to wireshark) with root:root owner and no caps.
now it is just a direct binary afaict, and it owned by root:wireshark with the appropriate caps.
Idk why just rebooting fixed this. I did not even do any rebuilding/updating at all.


Last release sources are missing on pypi

Hello.
I'm looking at the packaging of the latest release for Debian and found that there is no source on the last pypi published release.
The problem is that the Debian tools track only the sources and so don't see the good last release: https://tracker.debian.org/pkg/pytest-salt
Please, could you upload the sources on pypi in addition of the wheel?
Regards.

I missed that step when release, sorry.
The source tarbal is now also uploaded.

Thanks a lot.


envoy process is consuming consistant memory both during idle (no traffic) and drastic memory during traffic with envoy-alpine 1.21.5

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
<EMAIL_ADDRESS>where the issue will be triaged appropriately.
Title: envoy getting OOM killed during load testing
Description:

We have been using envoy proxy from past 4 years and now the latest version 1.21.5 is giving memory issues during our load tests
previous version 1.17.4 with v2 config did not had any such issue whereas its getting killed 30min -1 hour after the load starts with continuous heap increase .

Is there anyway to debug the issue as to what is exact reason for such a memory consumption and if anyone can guide on any particular config or factors to looked upon it will be really helpful
[optional Relevant Links:]

A profile would always be helpful for the  performance problem or potential memory leak.
See https://github.com/envoyproxy/envoy/blob/main/bazel/PPROF.md

And could you provide your load test config? (And it would also be great if you can try the latest envoy version 1.24.0 first to see if this problem is fixed or not


Simple JSON response.

If 'application/json' header, return JSON instead.

Referenced in commit https://github.com/zapier/django-knowledge/commit/311fbb12df0a569795dc5d8b40658b94327a07c2

Might be a narrow use case.


Add animation when navigate between Composables

As we know latest versions of Compose had made us control the navigation animation, as its still beta but I personally use it on the apps I am building and I believe it is worth to be added here 😃
https://twitter.com/ianhlake/status/1661465396585848832?s=20
Part of GTC open source initiative

Hey there, i will love to add the animation to this project, can you assign it to me?

Hey @arriolac Can You Please Assign This task To Me


Node version support

From → flyjs/fly/issues/56
co can work with as little as 0.11, however package.json is just listing
  "engines": {
    "iojs": ">= 1.0.0",
    "node": ">= 0.12.0"
  }

Is there any reason for this that I may have missed?

@bucaran I think it is purely a decision from a maintainer perspective, i.e. not having to check yet another version which isn't widely adopted. This requirement is not strict so npm will still install co with a warning but the package works fine with node 0.11 even if not "officially sanctioned".

@ruimarinho Thanks! Makes sense to me.


Resource lookup errors when using shared libraries

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): bug occurs with both
TensorFlow version (use command below): 2.3.2 CPU
Python version: 3.10
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 9.3.0
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
Using the C API (libtensorflow.so and libtensorflow_framework.so) in conjunction with tensorflow-text (or any library loading custom ops) throws errors like:
Invalid argument: Trying to access resource using the wrong type. Expected N10tensorflow6lookup15LookupInterfaceE got N10tensorflow6lookup15LookupInterfaceE
This is caused by the same bug as issue #44209.  In tensorflow/core/framework/type_index.h, the address of a static variable is used as a hash, leading to a false mismatch when called from a shared library.  That poster suggested that the bug did not occur on Linux because of the GNU unique symbol extension.  In my case, it still happens even on Linux.
Looking at the shared libraries, I think I can see why:
$ nm -C /usr/local/lib/libtensorflow.so | grep LookupInterface.*hash_bit
0000000008e091ac b tensorflow::TypeIndex::Make<tensorflow::lookup::LookupInterface>()::hash_bit
                 ^ BSS symbol

$ nm -C /usr/local/lib/libtensorflow_framework.so | grep LookupInterface.*hash_bit
0000000001c656ec u tensorflow::TypeIndex::Make<tensorflow::lookup::LookupInterface>()::hash_bit
                 ^ UNIQUE symbol

In libtensorflow_framework.so, the hash_bit is a unique symbol, but in libtensorflow.so, it is not.  I wondered why this problem was not happening when running Tensorflow from Python, so I checked the Python shared library:
$ nm -C ./_pywrap_tensorflow_internal.so | grep LookupInterface.*hash_bit
000000001de2842c u tensorflow::TypeIndex::Make<tensorflow::lookup::LookupInterface>()::hash_bit
                 ^ UNIQUE symbol

Sure enough, unique symbol.  So the question is why does libtensorflow.so get this symbol in BSS when every other library has it as unique?  I don't know enough about Bazel to inspect how these libraries are being linked, so I'm hoping someone here can help.
Describe the expected behavior
This error should not be thrown.

I was able to hack my way around this by taking the fix in tensorflow/core/framework/type_index.h that was done for MacOS and removing the #ifdef guard (enabling it on all platforms), then rebuilding the library with bazel build --config=opt --cxxopt=-D_GLIBCXX_USE_CXX11_ABI=0 tensorflow:libtensorflow.so.  But this kind of hack really shouldn't be necessary.

@bplevin36,
TensorFlow v2.3 is not compatible with Python 3.10. Please take a look at the tested build configurations for more information.

Version
Python version
Compiler
Build tools

tensorflow-2.4.0
3.6-3.8
GCC 7.3.1
Bazel 3.1.0

tensorflow-2.3.0
3.5-3.8
GCC 7.3.1
Bazel 3.1.0

tensorflow-2.2.0
3.5-3.8
GCC 7.3.1
Bazel 2.0.0

Could you please check if you are facing the same issue with Python 3.8 as well? Thanks!

@amahendrakar Thanks for the quick response.  I included my Python version just in case Python was somehow being used by the build process, but my actual program is written in Rust and includes no Python.  It only uses the shared libraries.

@amahendrakar  Just in case, I reran the entire process using Python 3.8, but the issue remains.

@bplevin36 @jvishnuvardhan, I've run into this issue with TensorFlow 2.4. Is this fixed in later versions?

This might be fixed in TF 2.6 via this PR https://github.com/tensorflow/tensorflow/pull/47072

Hi @bplevin36 ,
Could you please check with latest versions, if you are facing the same issue? Please take a look at the installation process for more information.
Thank you!


Changing the Host header of HTTP CONNECT proxy request.

The Host header should be set to the authority of the server that we
want to connect to as opposed to the name of the proxy server.
Given this change, I also added a small optimization to the proxy
configuration check so that we don't have to do an additional
malloc/free if we don't need to.

What's necessary to finish this discussion?

Me finishing the design of LB behind a proxy...
On Tue, Nov 29, 2016 at 1:41 PM, Eric Anderson<EMAIL_ADDRESS>wrote:

What's necessary to finish this discussion?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/8248#issuecomment-263708316, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-P7c51Zpctyyi2viOE9NV7pevHvu7Zks5rDJwTgaJpZM4KKut7
.

Julien, we could fix the Host: header even before the broader LB discussion is resolved.

Sure. It looks like this code is moving quite a bit right now (currently
reviewing #8782). I'll do that after your PR is in.
On Tue, Nov 29, 2016 at 2:09 PM, Mark D. Roth<EMAIL_ADDRESS>wrote:

Julien, we could fix the Host: header even before the broader LB
discussion is resolved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/8248#issuecomment-263715726, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-P7fnB-tXbAsCdHz-fzkJo14C-MIVPks5rDKKOgaJpZM4KKut7
.

I wound up fixing the Host: header as part of #8795, so I think this PR isn't needed anymore.

sgtm, thanks for taking care of that.
On Mon, Dec 12, 2016 at 9:38 AM, Mark D. Roth<EMAIL_ADDRESS>wrote:

I wound up fixing the Host: header as part of #8795
https://github.com/grpc/grpc/pull/8795, so I think this PR isn't needed
anymore.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/8248#issuecomment-266497495, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-P7QQPzv0f_HaK3uLSRcHiobGO_nrNks5rHYamgaJpZM4KKut7
.


Switch disconnect to the unload event instead of beforeunload

Because the room disconnect is called on the beforeunload event users aren't able to add their own beforeunload confirmation warning. This is because the user will be disconnected from the room even if they decide to stay on the page.
For example, when a recording is in progress in our application we want to warn a user before they leave to remind them to stop the recording.
This switches the room disconnect to the unload event so in our client code we are able to add the confirm navigation warning.
As far as I know there shouldn't be an issue with the disconnect happening on unload instead of beforeunload, but let me know.

hi @wcarle,
that's a good point.
It seems generally recommended not to use the unload event at all anymore.
pagehide seems to be preferable. (https://developer.chrome.com/blog/page-lifecycle-api/#legacy-lifecycle-apis-to-avoid)
I haven't done any tests yet to determine whether pagehide fires the disconnect rather reliably, but am happy to take a closer look if you could confirm that switching to pagehide would mitigate the issue you're having?

@lukasIO reading a bit further in that doc to the section on beforeunload, it actually has the same limitations as unload:
https://developer.chrome.com/blog/page-lifecycle-api/#the-beforeunload-event
So technically neither of them are good as end of session signals in the same way:

The beforeunload event has a similar problem to the unload event, in that when present it prevents browsers from caching the page in their back/forward cache.
The difference between beforeunload and unload, though, is that there are legitimate uses of beforeunload. For instance, when you want to warn the user that they have unsaved changes they'll lose if they continue unloading the page.
Since there are valid reasons to use beforeunload but using it prevents pages from being added to the back/forward cache, it's recommended that you only add beforeunload listeners when a user has unsaved changes and then remove them immediately after the unsaved changes are saved.

So if I'm reading that correctly, both events have the same downsides, the only reason they say beforeunload is ok is for the specific case of the unsaved changes warning

I really should've read the docs on beforeunload prior to using it in the SDK. It seems pagehide is the better path forward. @wcarle I believe beforeunload is still fired before pagehide. So in that case it should satisfy your needs?

If this article is still accurate, then there is a possibility that none of the events under discussion will work reliably for mobile browsers.

You cannot rely on pagehide, beforeunload, and unload events to fire on mobile platforms. This is not a bug in your favorite browser; this is due to how all mobile operating systems work. An active application can transition into a "background state" via several routes:

The user can click on a notification and switch to a different app.
The user can invoke the task switcher and move to a different app.
The user can hit the "home" button and go to homescreen.
The OS can switch the app on users behalf - e.g. due to an incoming call.

On mobile browsers visibilitychange it the last reliably fired event:
addEventListener("visibilitychange", (event) => {});
This claim is supported by MDN:

Transitioning to hidden is the last event that's reliably observable by the page, so developers should treat it as the likely end of the user's session (for example, for sending analytics data).

On desktop, switching tabs should obviously not disconnect the participant from the LiveKit-session. So maybe we need to implement different session-ended-detection-logics for mobile and desktop?

@wcarle are you interested in changing this PR to reflect @davidzhao 's suggestions?
If not, I'd start working on this in a separate PR.

superseded by https://github.com/livekit/client-sdk-js/pull/627
thanks @wcarle for the report!


[superlu] Fix the CONTROL file

as a drive-by, make the error easier to read

I had already open a PR #13315


Revert "Merge pull request #313 from qlli/ebitenAudio"

This reverts commit bd0c27af58394fa5fc605d8857a39231db02854e, reversing changes made to 175be7ae754ed6dd9d7c9395d93a8d5d53e15d0c.
ebitenAudio can not parse .mp3 with free bitrate.

close due to #325


MANIFEST.in: Add tests and docs to sdist

Also add exclusion in setup() to prevent tests in sdist
from being an installed package.
Closes https://github.com/InfoAgeTech/django-core/issues/4

Coverage decreased (-0.05%) to 66.794% when pulling bf22ca4cb0d5e01d096a22faae478c571843c56d on jayvdb:sdist-tests into 9664a145473b75120bf71e1644e9c8086e7e8955 on InfoAgeTech:master.


-lint always fails

I've just started using yamlfmt since v0.4.0, so I don't know how it worked before, but I think this issue was introduced in v0.4.0 because of the new diff library.
https://github.com/RageCage64/multilinediff seems to always return non-empty string but https://github.com/google/yamlfmt/blob/f3eff05a45d691309d88ccb76b1fc00bd3819a25/engine/engine.go#L95 detects lint errors by checking if a return value is empty or not. As a result, running yamlfmt with -lint always fails even if there's no diff.
Similarly, -dry always outputs all contents.

Thank you for making an issue!
Pretty silly oversight on my part, when I was testing this I only tested it on yaml that needed changes, and forgot the test case of a yaml file that's already formatted. :anguished:
I can get a patch release out for this tomorrow.

While fixing this I found another thing that I meant to fix on v0.4.0, which is that the multiline diffing always assumed \n. This was a bit of a bigger change than I expected that required an API change, so I'll be doing this in a new minor release.

Thank you for your quick work!

v0.5.0 is released! Thank you for your patience and hopefully this works better.

I confirmed it's been fixed! Thank you!


[#98] Clang Sanitizer Compiler Options

I'll add the int16_t and int64_t changes as well later.

Merged.
Thanks for your contribution !


Relations and connections

Relations and connections
Created a Tweet model and installed a single link with User
import mongoose from 'mongoose'
import { UserTC } from './user'
import composeWithMongoose from 'graphql-compose-mongoose'

const TweetSchema = new mongoose.Schema({
	  text: String,
	  userId: {
	    type: mongoose.Schema.Types.ObjectId,
	    ref: 'User'
          }
}, { timestamps: true } )

export const Tweet = mongoose.model('Tweet', TweetSchema)
export const TweetTC = composeWithMongoose(Tweet)

TweetTC.addRelation(
	  'user',
	  {
	    resolver: () => UserTC.getResolver('findById'),
	    prepareArgs: {
	      _id: source => source.userId
	    },
	    projection: { userId: true },
	  }
)

Created a User model and installed a multiple link with Tweet
import mongoose from 'mongoose'
import { TweetTC } from './tweet'
import composeWithMongoose from 'graphql-compose-mongoose'

const UserSchema = new mongoose.Schema({
    username: {
	    type: String,
	    unique: true
	  },
	  firstName: String,
	  lastName: String,
	  avatar: String,
	  password: String,
	  email: String,
	  tweetsIds: [{
	    type: mongoose.Schema.Types.ObjectId,
	    ref: 'Tweet'
	  }],
}, { timestamps: true })

export const User = mongoose.model('User', UserSchema)
export const UserTC = composeWithMongoose(User)

UserTC.addRelation(
	  'tweets',
	  {
	    resolver: () => TweetTC.getResolver('findByIds'),
	    prepareArgs: {
	      _ids: (source) => source.tweetsIds || [],
	    },
	    projection: { tweetsIds: true },
	  }
)

I create a mutation where in the userId field I pass the users id
mutation {
  tweetCreate(record: {
    text: "Get tweet"
    userId: "5a0b3cde2c6afb534933fc5b"
  }) {
    recordId
  }
}

As a result, the tweet was created
{
  "_id": ObjectId("5a0b47fcb4f0015a0d59b6d6"),
  "text": "Get tweet",
  "userId": ObjectId("5a0b3cde2c6afb534933fc5b"),
}

, but the array with the user's field tweetsIds is empty
 {
    "_id": "5a0b3cde2c6afb534933fc5b",
    "username": "sun",
    "tweetsIds": [],
},

The whole project lies here
Where am I mistaken?

Yep, tweetsIds should be empty. graphql-compose-mongoose does not change related models. It may bring complexity to the codebase and bring unexpected behavior. Right now I do not serve ref, but maybe it would be changed in future.
For now, in your case you may create a custom mutation:
TweetTC.addResolver({
  kind: 'mutation',
  name: 'createTweetWithRels',
  type: TweetTC.getResolver('createOne').getType(),
  args: TweetTC.getResolver('createOne').getArgs(),
  resolve: (rp) => {
     ...custom logic
     return $shapeOfOutputType;
  },
});

And then use this createTweetWithRels resolver in your schema.
Or even better do not store tweetIds in User collection and make such relation with sorting & limiting:
UserTC.addRelation(
	  'tweets',
	  {
	    resolver: () => TweetTC.getResolver('findMany'),
	    prepareArgs: {
	      filter: (source) => ({ userId: source._id }),
	    },
	    projection: { _id: true },
	  }
)

PS> Do not forget add index TweetSchema.index({ userId: 1 }, { background: true }); for performance.

I went according to the script, which is better
Аccording to the instructions, the model was modified:

Create tweet

But tweets to the user were not added

Mongoose

All code

The northwind project implements this task.

Tried to do also, but I do not know why the array of tweets is duplicated to each user

With relations was a problem which is fixed in<EMAIL_ADDRESS>It incorrectly converts ObjectId for filter argument. Just update package and all should work.

I guess if my questions are stupid, but for me it is important to understand how to link collections, as in my opinion this is the basis for working with the database
The first mutation created the user and got it ID

The second mutation create tweet and send  userID

but the tweetConnection is empty

at the current time the model looks like this
UserSchema
const UserSchema = new mongoose.Schema({
  userID: {
    type: Number,
    description: 'User unique ID',
    unique: true,
  },
  username: {
    type: String,
    unique: true
  },
  firstName: String,
  lastName: String,
  avatar: String,
  password: String,
  email: String,
}, { timestamps: true })

export const User = mongoose.model('User', UserSchema)
export const UserTC = composeWithRelay(composeWithMongoose(User))

UserTC.addRelation('tweetConnection', {
  resolver: () => TweetTC.getResolver('connection'),
  prepareArgs: {
    filter: source => ({ userID: source.userID }),
  },
  projection: { userID: true },
})

TweetSchema
const TweetSchema = new mongoose.Schema({
  tweetID: {
    type: Number,
    description: 'Tweet unique ID',
    unique: true,
  },
  text: String,
  userID: String
}, { timestamps: true })

TweetSchema.index({ userID: 1 }, { background: true })

export const Tweet = mongoose.model('Tweet', TweetSchema)
export const TweetTC = composeWithRelay(composeWithMongoose(Tweet))

TweetTC.addRelation('user', {
  resolver: () => UserTC.getResolver('findOne'),
  prepareArgs: {
    filter: source => ({ userID: source.userID }),
    skip: null,
    sort: null,
  },
  projection: { userID: true },
})

What's wrong?

id contains Relay Global Id (about purpose of this field written here https://facebook.github.io/relay/docs/graphql-object-identification.html )
_id contains mongo id

So you need to use mongo id _id for userID field (not relay id).

After fix id, I see

The mongo necklace shows that the IDs have been added

../model/user.js
UserTC.addRelation(
	  'tweets',
	  {
	    resolver: () => TweetTC.getResolver('findMany'),
	    prepareArgs: {
	      filter: (source) => ({ userID: source._id }),
	    },
	    projection: { _id: true },
	  }
)

../model/tweet.js
TweetTC.addRelation('user', {
  resolver: () => UserTC.getResolver('findOne'),
  prepareArgs: {
    filter: source => ({ userID: source._id }),
    skip: null,
    sort: null,
  },
  projection: { _id: true },
})

but fields tweets  is empty, why?

All Code

Thank you very much for working example of linking collections. I filled my house with joy
for those who stalknetsya with my task, I will leave it here:
../models/user/js
const UserSchema = new mongoose.Schema({
  // remove this for simplicity, cause `_id` will be crated automatically
  // userID: {
  //   type: Number,
  //   description: 'User unique ID',
  //   unique: true,
  // },
  username: {
    type: String,
    // unique: true , remove this for simplicity
  },
  firstName: String,
  lastName: String,
  password: String,
  email: {
    type: String,
    unique: true
  },
}, { timestamps: true })

export const User = mongoose.model('User', UserSchema)
export const UserTC = composeWithMongoose(User)

UserTC.addRelation(
	  'tweets',
	  {
	    resolver: () => TweetTC.getResolver('findMany'),
	    prepareArgs: {
      filter: source => ({ userID: source._id }),
	    },
	    projection: { _id: true },
	  }
)

../models/tweet.js
const TweetSchema = new mongoose.Schema({
  // _id this field created automatically

  // remove this for simplicity
  // tweetID: {
  //   type: Number,
  //   description: 'Tweet unique ID',
  //   unique: true,  <====== this requires that all records should have unique values
  // },

  text: String,
  userID: {
    type: String,
    index: true,
  },
}, { timestamps: true })

// simle index created via model `index: true` option
// following index just allow to create complex indexes
// TweetSchema.index({ userID: 1 }, { background: true })

export const Tweet = mongoose.model('Tweet', TweetSchema)
export const TweetTC = composeWithMongoose(Tweet)

TweetTC.addRelation('user', {
  resolver: () => UserTC.getResolver('findById'),
  prepareArgs: {
    _id: source => source._id,
    skip: null,
    sort: null,
  },
  projection: { _id: true },
})

working!!!

Why does this custom resolver return "user": null ?
TweetTC.addRelation('user', {
  resolver: () => UserTC.getResolver('findById'),
  prepareArgs: {
    _id: source => source._id,
    skip: null,
    sort: null,
  },
  projection: { _id: true },
})

Should be
- _id: source => source._id
+ _id: source => source.userID

"stalknetsya"?

@dandv  met))


Intel AI Tools Images rebased

This PR changes the base of the jupyter images of intel AI Tools from runtime images to the intel-gpu base images for TF and PyTorch and ubi9-python for Intel ML. This is done to remove the dependency on runtime images and reduce the size of the images.
Description

Intel AI Tools TF Jupyter image's base image changed to Intel GPU base image
Intel AI Tools PyTorch Jupyter image's base image changed to Intel GPU base image
Intel AI Tools ML Jupyter image's base image changed to Python UBI9 base image
Installation of Intel oneAPI basekit replaced with individual necessary components for Intel AI Tools PyTorch and TF Runtime images.

How Has This Been Tested?

Ran tests with make commands
Merge criteria:

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

/ok-to-test

This PR on OpenShift release repo needs to be reviewed and merged for the tests to work. Basically it reverts the changes that were merged to test the split Intel AI Tools CPU GPU containers.

/retest

/retest

/retest

Thank you @sharvil10 for your PR, I will move your changes to main branch.
That's right the habana notebook failed builds are not related to your changes, i will override the tests in order you get your PR merged.
/override ci/prow/images
/override ci/prow/notebooks-e2e-tests
/lgtm
/approve
I am not sure but as a next step to update the intel imagestreams with the newly build images.  For example here


RuntimeError: Something went wrong after call_sampler.

I'm fitting my data about 50 csv files but Prophet crashes and throwing runtime errors. This only happened when I switched to Ubuntu 16. On Windows, prophet runs without error.
`Optimization terminated with error:
Line search failed to achieve a sufficient decrease, no more progress can be made
Traceback (most recent call last):
File "get_predictions.py", line 283, in
m.fit(df)
File "/home/arvin/anaconda3/envs/devenv/lib/python3.5/site-packages/fbprophet-0.1.1-py3.5.egg/fbprophet/forecaster.py", line 536, in fit
params = model.optimizing(dat, init=stan_init, iter=1e4, **kwargs)
File "/home/user/anaconda3/envs/devenv/lib/python3.5/site-packages/pystan/model.py", line 510, in optimizing
ret, sample = fit._call_sampler(stan_args)
File "stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8714900159976324877.pyx", line 814, in stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8714900159976324877.StanFit4Model._call_sampler (/tmp/tmp6in6jxib/stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8714900159976324877.cpp:16904)
File "stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8714900159976324877.pyx", line 401, in stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8714900159976324877._call_sampler (/tmp/tmp6in6jxib/stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8714900159976324877.cpp:8973)
RuntimeError: Something went wrong after call_sampler.
`
TIA

This is my data there are daily close of a stock price.
ds,y 04/01/2016,0.072 04/04/2016,0.069 04/05/2016,0.061 04/06/2016,0.063 04/07/2016,0.062 04/08/2016,0.062 04/11/2016,0.061 04/12/2016,0.065 04/13/2016,0.064 04/14/2016,0.065 04/15/2016,0.064 04/18/2016,0.062 04/19/2016,0.062 04/20/2016,0.062 04/21/2016,0.059 04/22/2016,0.058 04/25/2016,0.057 04/26/2016,0.057 04/27/2016,0.054 04/28/2016,0.054 04/29/2016,0.058 05/02/2016,0.055 05/03/2016,0.055 05/04/2016,0.055 05/05/2016,0.055 05/06/2016,0.055 05/10/2016,0.054 05/11/2016,0.057 05/12/2016,0.058 05/13/2016,0.058 05/16/2016,0.059 05/17/2016,0.059 05/18/2016,0.058 05/19/2016,0.058 05/20/2016,0.055 05/23/2016,0.054 05/24/2016,0.054 05/25/2016,0.052 05/26/2016,0.052 05/27/2016,0.053 05/30/2016,0.053 05/31/2016,0.058 06/01/2016,0.058 06/02/2016,0.058 06/03/2016,0.058 06/06/2016,0.059 06/07/2016,0.061 06/08/2016,0.061 06/09/2016,0.059 06/10/2016,0.058 06/13/2016,0.057 06/14/2016,0.056 06/15/2016,0.058 06/16/2016,0.059 06/17/2016,0.058 06/20/2016,0.059 06/21/2016,0.061 06/22/2016,0.062 06/23/2016,0.062 06/24/2016,0.059 06/27/2016,0.059 06/28/2016,0.059 06/29/2016,0.059 06/30/2016,0.058 07/01/2016,0.058 07/04/2016,0.059 07/05/2016,0.058 07/07/2016,0.058 07/08/2016,0.058 07/11/2016,0.06 07/12/2016,0.06 07/13/2016,0.059 07/14/2016,0.088 07/15/2016,0.099 07/18/2016,0.094 07/19/2016,0.102 07/20/2016,0.107 07/21/2016,0.097 07/22/2016,0.099 07/25/2016,0.099 07/26/2016,0.099 07/27/2016,0.1 07/28/2016,0.118 07/29/2016,0.114 08/01/2016,0.109 08/02/2016,0.108 08/03/2016,0.105 08/04/2016,0.103 08/05/2016,0.103 08/08/2016,0.103 08/09/2016,0.101 08/10/2016,0.103 08/11/2016,0.095 08/12/2016,0.093 08/15/2016,0.095 08/16/2016,0.099 08/17/2016,0.097 08/18/2016,0.095 08/19/2016,0.095 08/22/2016,0.094 08/23/2016,0.097 08/24/2016,0.093 08/25/2016,0.093 08/26/2016,0.1 08/30/2016,0.098 08/31/2016,0.095 09/01/2016,0.093 09/02/2016,0.094 09/05/2016,0.098 09/06/2016,0.098 09/07/2016,0.107 09/08/2016,0.1 09/09/2016,0.099 09/13/2016,0.093 09/14/2016,0.094 09/15/2016,0.096 09/16/2016,0.101 09/19/2016,0.1 09/20/2016,0.096 09/21/2016,0.099 09/22/2016,0.1 09/23/2016,0.102 09/26/2016,0.098 09/27/2016,0.095 09/28/2016,0.099 09/29/2016,0.098 09/30/2016,0.097 10/03/2016,0.094 10/04/2016,0.094 10/05/2016,0.094 10/06/2016,0.094 10/07/2016,0.094 10/10/2016,0.094 10/11/2016,0.094 10/12/2016,0.09 10/13/2016,0.083 10/14/2016,0.089 10/17/2016,0.087 10/18/2016,0.085 10/19/2016,0.086 10/20/2016,0.085 10/21/2016,0.084 10/24/2016,0.084 10/25/2016,0.085 10/26/2016,0.084 10/27/2016,0.084 10/28/2016,0.083 11/02/2016,0.083 11/03/2016,0.083 11/04/2016,0.084 11/07/2016,0.082 11/08/2016,0.082 11/09/2016,0.078 11/10/2016,0.078 11/11/2016,0.075 11/14/2016,0.073 11/15/2016,0.072 11/16/2016,0.073 11/17/2016,0.073 11/18/2016,0.077 11/21/2016,0.075 11/22/2016,0.072 11/23/2016,0.07 11/24/2016,0.071 11/25/2016,0.07 11/28/2016,0.068 11/29/2016,0.071 12/01/2016,0.068 12/02/2016,0.07 12/05/2016,0.069 12/06/2016,0.071 12/07/2016,0.069 12/08/2016,0.068 12/09/2016,0.07 12/12/2016,0.074 12/13/2016,0.072 12/14/2016,0.072 12/15/2016,0.07 12/16/2016,0.07 12/19/2016,0.066 12/20/2016,0.065 12/21/2016,0.065 12/22/2016,0.063 12/23/2016,0.062 12/27/2016,0.062 12/28/2016,0.062 12/29/2016,0.063 01/03/2017,0.064 01/04/2017,0.068 01/05/2017,0.069 01/06/2017,0.069 01/09/2017,0.069 01/10/2017,0.071 01/11/2017,0.07 01/12/2017,0.07 01/13/2017,0.072 01/16/2017,0.073 01/17/2017,0.074 01/18/2017,0.07 01/19/2017,0.071 01/20/2017,0.072 01/23/2017,0.071 01/24/2017,0.072 01/25/2017,0.072 01/26/2017,0.072 01/27/2017,0.072 01/30/2017,0.07 01/31/2017,0.071 02/01/2017,0.069 02/02/2017,0.068 02/03/2017,0.067 02/06/2017,0.065 02/07/2017,0.065 02/08/2017,0.066 02/09/2017,0.066 02/10/2017,0.065 02/13/2017,0.064 02/14/2017,0.065 02/15/2017,0.065 02/16/2017,0.065 02/17/2017,0.066 02/20/2017,0.067 02/21/2017,0.066 02/22/2017,0.065 02/23/2017,0.066 02/24/2017,0.066 03/02/2017,0.066 03/03/2017,0.065 03/06/2017,0.065 03/07/2017,0.064 03/08/2017,0.064 03/09/2017,0.065 03/10/2017,0.067 03/13/2017,0.065 03/14/2017,0.064 03/15/2017,0.064 03/16/2017,0.072 03/17/2017,0.074 03/20/2017,0.075 03/21/2017,0.075 03/22/2017,0.073 03/23/2017,0.073 03/24/2017,0.074 03/27/2017,0.079 03/28/2017,0.078 03/29/2017,0.08 03/30/2017,0.078 03/31/2017,0.074 04/03/2017,0.071 04/04/2017,0.074 04/05/2017,0.072 04/06/2017,0.071 04/07/2017,0.073 04/10/2017,0.07 04/11/2017,0.07 04/12/2017,0.071 04/17/2017,0.072 04/18/2017,0.075 04/19/2017,0.074 04/20/2017,0.072 04/21/2017,0.072 04/24/2017,0.088 04/25/2017,0.085 04/26/2017,0.087 04/27/2017,0.093 05/02/2017,0.092 05/03/2017,0.091 05/04/2017,0.092 05/05/2017,0.093 05/08/2017,0.09 05/09/2017,0.086 05/09/2017,0.086 05/10/2017,0.089 05/11/2017,0.089 05/12/2017,0.089 05/15/2017,0.086 05/16/2017,0.087 05/17/2017,0.087 05/18/2017,0.085 05/19/2017,0.087 05/22/2017,0.087

I'm getting the same error on Mac:
Disabling weekly seasonality. Run prophet with weekly_seasonality=True to override this.
RuntimeError                              Traceback (most recent call last)
 in ()
3 ts=pd.DataFrame(data={'ds': store_info.index.values, 'y':  store_info['trade']})
4 pr = Prophet()
----> 5 pr.fit(ts)
6 #future = pr.make_future_dataframe(periods=12)
7 #future
/Users/szelvenskiy/anaconda2/lib/python2.7/site-packages/fbprophet/forecaster.pyc in fit(self, df, **kwargs)
533
534         else:
--> 535             params = model.optimizing(dat, init=stan_init, iter=1e4, **kwargs)
536             for par in params:
537                 self.params[par] = params[par].reshape((1, -1))
/Users/szelvenskiy/anaconda2/lib/python2.7/site-packages/pystan/model.pyc in optimizing(self, data, seed, init, sample_file, algorithm, verbose, as_vector, **kwargs)
508         stan_args = pystan.misc._get_valid_stan_args(stan_args)
509
--> 510         ret, sample = fit._call_sampler(stan_args)
511         pars = pystan.misc._par_vector2dict(sample['par'], m_pars, p_dims)
512         if not as_vector:
stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8842012118624695346.pyx in stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8842012118624695346.StanFit4Model._call_sampler (/var/folders/sp/05s637fx0q3f0dm7ws_2618r0000gp/T/tmpMejYXT/stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8842012118624695346.cpp:16904)()
stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8842012118624695346.pyx in stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8842012118624695346._call_sampler (/var/folders/sp/05s637fx0q3f0dm7ws_2618r0000gp/T/tmpMejYXT/stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_8842012118624695346.cpp:8973)()
RuntimeError: Something went wrong after call_sampler.

Here is the data:
ds	y
0	2012-05-01	1
1	2012-08-01	1
2	2012-11-01	2
3	2013-04-01	1
4	2013-06-01	1
5	2013-08-01	1
6	2014-05-01	1
7	2015-11-01	1
8	2016-06-01	1
9	2016-07-01	2
10	2016-10-01	1
11	2016-11-01	1
12	2016-12-01	2
13	2017-01-01	1
14	2017-02-01	3

In fact, it's not related to data. Same data is processed fine until. Now any call to .fit method fails. Even if it worked before with the same dataset.

Got it fixed when I upgraded to ubuntu 16.0 weird huh

I have the same error:
here is the data that I got error:
"ds","y"
2017-03-10,166
2017-03-11,167
2017-03-12,168
2017-03-13,169
2017-03-14,170
but when I change the data to this, it run successfully:
"ds","y"
2017-03-10,1
2017-03-11,2
2017-03-12,3
2017-03-13,4
2017-03-14,5

here is the error:
File "./prophet.py", line 10, in
m.fit(df);
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/fbprophet/forecaster.py", line 535, in fit
params = model.optimizing(dat, init=stan_init, iter=1e4, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pystan/model.py", line 510, in optimizing
ret, sample = fit._call_sampler(stan_args)
File "stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_3890433898330113621.pyx", line 814, in stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_3890433898330113621.StanFit4Model._call_sampler (/var/folders/_3/fj7g23z935150t_q4s8xdsz00000gn/T/tmp_u6cg9mb/stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_3890433898330113621.cpp:16904)
File "stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_3890433898330113621.pyx", line 401, in stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_3890433898330113621._call_sampler (/var/folders/_3/fj7g23z935150t_q4s8xdsz00000gn/T/tmp_u6cg9mb/stanfit4anon_model_7a788197ac3493030b72020b9ffdbe7d_3890433898330113621.cpp:8973)
RuntimeError: Something went wrong after call_sampler.

Same error
Input:
example.txt
Error:
RuntimeError                              Traceback (most recent call last)
 in ()
1 # Fit data
----> 2 p.fit(data)
F:\Anaconda3\lib\site-packages\fbprophet\forecaster.py in fit(self, df, **kwargs)
533
534         else:
--> 535             params = model.optimizing(dat, init=stan_init, iter=1e4, **kwargs)
536             for par in params:
537                 self.params[par] = params[par].reshape((1, -1))
F:\Anaconda3\lib\site-packages\pystan\model.py in optimizing(self, data, seed, init, sample_file, algorithm, verbose, as_vector, **kwargs)
508         stan_args = pystan.misc._get_valid_stan_args(stan_args)
509
--> 510         ret, sample = fit._call_sampler(stan_args)
511         pars = pystan.misc._par_vector2dict(sample['par'], m_pars, p_dims)
512         if not as_vector:
stanfit4anon_model_9c941523472e65f75f241e35a8769919_8513495007735644422.pyx in stanfit4anon_model_9c941523472e65f75f241e35a8769919_8513495007735644422.StanFit4Model._call_sampler (C:\Users\ALEXAN~1\AppData\Local\Temp\tmpocoa45n9\stanfit4anon_model_9c941523472e65f75f241e35a8769919_8513495007735644422.cpp:17112)()
stanfit4anon_model_9c941523472e65f75f241e35a8769919_8513495007735644422.pyx in stanfit4anon_model_9c941523472e65f75f241e35a8769919_8513495007735644422._call_sampler (C:\Users\ALEXAN~1\AppData\Local\Temp\tmpocoa45n9\stanfit4anon_model_9c941523472e65f75f241e35a8769919_8513495007735644422.cpp:8986)()
RuntimeError: Something went wrong after call_sampler.
Running on Python3 in Windows environment.

OK it seems that in some situations the LBFGS optimizer is failing to converge, and this is making pystan error out. In https://github.com/facebookincubator/prophet/commit/f7becb0942cd0a005d72ae307aefee431fa962d7, if LBFGS fails we fall back to Newton. This fixes the issue for the dataset from @arvindacumos . Could others who are running into this issue install from github and see if this commit fixes it for you?

@bletham Thanks - resolves my issue.


Updated description for connector sample

Docs Build status updates of commit 8b4387b:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 8b4387b:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 8b4387b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8b4387b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Single-cell phenotyping with contrastive learning

Self-supervised learning of single-cell image patches with contrastive triplet loss.

@ziw-liu looks like you are powering through the refactor. Awesome.
Couple of notes:

Please integrate the current contrastive learning training script into the CLI, via a required flag like --model OR via a config field for the lighting module. The latter may be a seamless and low-maintenance route as we implement lightning modules for tasks like semantic segmentation.
applications/contrastive_phenotyping/dataloader_test.py can be moved to viscy/scripts. It can also be improved in the future PR to write a CLI for testing and logging parallelized data loading for given configuration.

@mattersoflight does #116 need to be fixed in this PR?


feat: proxy request message + adding a course by URL

This pull request introduces a new message for proxying fetch requests from the foreground through the background scripts. We use this mainly for adding courses by their links

This change is

( this is some stuffs for #291 )

does anyone have a teriyaki chicken recipe btw

ty ty


Npm build / Docker build fails

Describe the bug
I wasn't able to compile the source code using docker build -t cloudproxy:latest . (or not inside the docker, it doesn't really matter in that case), it would give me the following errors:
1 package is looking for funding
  run `npm fund` for details

2 vulnerabilities (1 moderate, 1 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 7.0.8 -> 7.14.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.14.0>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice

><EMAIL_ADDRESS>build
> tsc

src/captcha/anti-captcha.ts(3,53): error TS2339: Property 'userAgent' does not exist on type 'SolverOptions'.
src/captcha/anti-captcha.ts(3,64): error TS2339: Property 'proxy' does not exist on type 'SolverOptions'.
src/captcha/anti-captcha.ts(3,71): error TS2339: Property 'apiKey' does not exist on type 'SolverOptions'.
npm notice
npm notice New minor version of npm available! 7.0.8 -> 7.14.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.14.0>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code 2
npm ERR! path /home/node/cloudproxy
npm ERR! command failed
npm ERR! command sh -c tsc

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2021-05-25T12_44_18_247Z-debug.log
The command '/bin/sh -c npm install &&     npm run build &&     rm -rf src tsconfig.json &&     npm prune --production' returned a non-zero code: 2

To Reproduce
Steps to reproduce the behavior:
docker build -t somename:latest .
Expected behavior
A docker image of the program.
Suggested Solution
So I've done some digging and I found out the following commit broke the code:
https://github.com/NoahCardoza/CloudProxy/commit/280a640d814e39aac9f459b8214ed1b8efd080ff
so I reverted that commit using
git revert 280a640d814e39aac9f459b8214ed1b8efd080ff

and then everything seemed to compile and build successfully, and afterwards I tested the program against a website I wanted to try, and it succeeded.
I hope it would be of some help.

Great work!
It just occurred to me that this issue stems from a captcha plugin someone added...
I'd rather fix that issue than revert, so if anyone wants to open a PR that would be great! Otherwise it might take me a little time to get to it.
Btw, does it still bypass CF @grobek ? I heard they were changing things around as you probably saw us chatting about in the Discord server...
Thanks a bunch for your work though!

Hey @NoahCardoza, yes, it does still pass CF, just now the only thing that’s needed to utilize is browser agent, ip and the generated cf_clearance.
Though I didn’t try to check if it passes captcha and whatnot.

Great to hear! I think this should be a somewhat simple fix. Some more fields need to be added to the SolverOptions interface it looks like.


Remove default environment variable DOCKER_VERNEMQ_KUBERNETES_NAMESPACE from Dockerfile (#70)

This PR should solve #70, enable the new mechanism introduced by #71 and relates to pull request #69

@codeadict could you have a quick look at this?

Thanks!


merge from template-arlac77-github

.github/workflows/ci.yml

chore(deps): add 20.12.2 remove 20.12.1 (jobs.test-node.strategy.matrix.node-version)
chore: add 20.12.2 (jobs.release.steps.with.node-version)

.github/workflows/codeql_analysis.yml

chore: add 20.12.2 (jobs.analyze.steps.with.node-version)

.github/workflows/update_package_lock.yml

chore(deps): add 20.12.2 remove 20.12.1 (jobs.update_package_lock.strategy.matrix.node-version)

.github/workflows/update_readme_api.yml

chore: add 20.12.2 (jobs.update_readme_api.steps.with.node-version)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
89

Relevant Lines:
369

💛  - Coveralls


how to add value into process of Jaeger UI

I use opencensus to create spans.
span.putAttribute(key,value)-----> jaeger UI's  tags
span.annotation---->jaeger UI's logs
My question is that on Jaeger Ui, How to add things into process?

I am not sure how you can add them with OpenCensus. Jaeger libraries support the notion of "tracer tags" that are added to Process. Similarly, Jaeger agent supports "agent tags" that are also added to the Process. If you are only using OpenCensus library & agent before sending data to Jaeger, then you  should open a ticket with them asking about it.

Just to complement @yurishkuro's answer, the "agent tags" can be set by passing a comma-separated list of key=value pairs via the flag --jaeger-tags. Tracer tags can be passed using the same notation via the JAEGER_TAGS env var.

@zheyiyi - We used this sheet as reference while writing the OC proto -> Jaeger proto translation.
There was no direct mapping from OC proto for the Process field, but it should be populated when StackTrace is populated in the OC span.
Hope this helps.

I am closing this as it is a question.
The tracer library/agent/collector you are using should support adding process level tags. In OpenTelemetry Java Jaeger exporter adds tags https://github.com/open-telemetry/opentelemetry-java/blob/ba1819996f07554df2cd3795f27f62edc84cb340/exporters/jaeger/src/main/java/io/opentelemetry/exporters/jaeger/JaegerGrpcSpanExporter.java#L86. For example resource object will be converted to process https://github.com/open-telemetry/opentelemetry-java/blob/master/sdk/src/main/java/io/opentelemetry/sdk/resources/Resource.java.


old-style engine.cfg choking on 'img' identifier

Operating system or device:
Linux 64-bit
Issue description (what happened, and what was expected):
Old project won't show in Project Manager now. Get this error:
ERROR: load: ConfgFile::load - /home/dana/Projects/HiddanOjbexxRetchro/engine.cfg:6 error: Unexpected identifier: 'img'.
   At: core/io/config_file.cpp:180.

Expected it would import into the Project Manager list.
Steps to reproduce:
Try to import project with custom boot logo in engine.cfg
Link to minimal example project (optional but very welcome):
https://gitlab.com/shine-upon-thee/hiddan-ojbexx-retchro/repository/archive.zip?ref=master

custom boot logo in engine.cfg is no longer supported, but I'm surprised this no longer works, I added compatibility..

Will check later, but it's weird because I added the code to parse it..
On Mon, Feb 22, 2016 at 5:48 AM, Dana Olson<EMAIL_ADDRESS>wrote:

Operating system or device:
Linux 64-bit
Issue description (what happened, and what was expected):
Old project won't show in Project Manager now. Get this error:
ERROR: load: ConfgFile::load - /home/dana/Projects/HiddanOjbexxRetchro/engine.cfg:6 error: Unexpected identifier: 'img'.
At: core/io/config_file.cpp:180.
Expected it would import into the Project Manager list.
Steps to reproduce:
Try to import project with custom boot logo in engine.cfg
Link to minimal example project (optional but very welcome):
https://gitlab.com/shine-upon-thee/hiddan-ojbexx-retchro/repository/archive.zip?ref=master
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3798.

Yeah, I figure I could probably just load my project by simply deleting that line. But I looked at the code and saw it was supposed to be supported, so that's why I reported it, as I'm sure it's something good to fix before 2.0 release.

OK, so, I don't know WTF happened yesterday, but this seems to be fine with a fresh checkout of the 2.0 stable branch. Closing.


.NET Core RTM?

It's me again. :) Any chance @domaindrivendev has a plan for the release of the RTM-supported version? Or an ETA on when?

There is a separate project see https://github.com/domaindrivendev/Ahoy

So - same question. Is there an ETA on the availability of a NuGet package supporting the 1.0 Core release?

Install-Package Swashbuckle -Pre - you should probably ask over on the other project :)


Bump go-kit to 0.12.0

go-kit 0.11.0 has a dependency on github.com/dgrijalva/jwt-go which has
a few vulns. Namely https://github.com/dgrijalva/jwt-go/issues/428.
go-kit switched to the properly maintained fork in
https://github.com/go-kit/kit/issues/1026 so this commit bumps up to
0.12.0 in order to pick up that change and remove the dependency on the
vulnerable lib
Short description of the changes

Bump go-kit to 0.12.0 to remote dependency on github.com/dgrijalva/jwt-go

please resubmit the PR from a non-main branch in your fork, otherwise it would not pass the CI


Change default password to ailab

The current ticket requests to change the default password to ailab without any special characters that might be on different keys  using a different keyboard layout.
Background
See also #211
First-try out by PM showed that

Default password is ai-lab.
On the German keyboard, the minus character "-" is on key "?ß"
After creating the VM the user can only change the keyboard layout after logging in.

This ticket was triggered by feedback from PM


Bug Freeze Enchant.

Reproduction Steps

Enchant random sword Freeze Enchant
Kill other player
Infinity Freezes in player.
...

Expected Result
Upon death, the player should not have a residual freeze effect
Screenshots and Videos
No response
Operating System
Windows 10
Mod Version
3.0.7
Minecraft Version
1.19.2
Forge Version
1.19.2-43.2.14
Other Mods
No response
Additional Context
No response

Does this only happen when killing with a Freezing sword? I've just tested with a Freezing bow and it did not occur.

Yes, I checked the sword. I don't know about the axe and stuff.

I'm curious about a bow or if it's just the sword.

I'm curious about a bow or if it's just the sword.

wait bro, i give you video.

https://youtu.be/UminQ4VFdqY

This seems to be client/server desync. I'll work to fix this within about a week.


[Event Request] Codeunit 80 "Sales-Post" - PostItemChargeLine & OnAfterPostItemChargeLine

Hello Team,
In Codeunit 80, please provide the possibility of passing SalesLine by reference to PostItemChargeLine as well as the Publisher OnAfterPostItemChargeLine (existing) event.

PostItemChargeLine

OnAfterPostItemChargeLine

This would allow users to edit values of SalesLine without a MODIFY in the subscriber, as this causes an error:

Thank you!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Added filter options to fetch threats.

Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status

[x] In Progress
[ ] Ready
[ ] In Hold - (Reason for hold)

Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Must have

[ ] Tests
[ ] Documentation

@anirudh-metron - why are there so many files in this PR?
If our fork is not updated please ask Parag/Kapil to update
You code should only contain changes to S1


[Node] Use real conventions

Use real conventions (from the creators of dotenv)! https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use

Fixed merge conflicts. This is a convention used by modern JS frameworks as well.

uhh... what happen with this: https://github.com/motdotla/dotenv#should-i-have-multiple-env-files? From the creator of JS dotenv too, and I agree with him.

Why was plain .env removed? Isn't it better to err on the safe side? The cited conventions say "depends" for .env
Even then, that's the Ruby package. The guidance in the readme for the Node package is different:

Should I commit my .env file?
No. We strongly recommend against committing your .env file to version
control.

Should I have multiple .env files?
No. We strongly recommend against having a "main" .env file and an "environment" .env file like .env.test.

People and frameworks use different conventions - .gitignore should reflect how things are in practice, it's not the place to impose a convention.


Wrong parameters for gemma:7b

What is the issue?
Type ollama show gemma:7b: the parameters are 9b, not 7b.
OS
No response
GPU
No response
CPU
No response
Ollama version
No response

We are releasing weights in two sizes: Gemma 2B and Gemma 7B.
https://cloud.google.com/blog/products/ai-machine-learning/gemma-model-available-in-vertex-ai-and-via-gke?hl=en

I see, but the problem is the parameter should not be 9b.

https://ollama.com/library/gemma:7b
There is only 2b and 7b. Can you explain the issue here?

The issue is type ollama gemma:7b: the parameter shown on the screen is 9b.

The issue is type ollama show gemma:7b: the parameter shown on the screen is 9b.

Ah, now I see what you mean: "num_params":<PHONE_NUMBER> for gemma 7b
https://ollama.com/library/gemma:7b/blobs/ef311de6af9d
There is a discussion going on out about that: https://huggingface.co/google/gemma-7b/discussions/34
Not a bug in ollama, the information is right there. But I understand your confusion here.

Thank you. I also observed the same issue for gemma 2b. The parameter shown on the screen is 3b.

It's just the way Google wanted to market the LLMs. The actual parameter counts are correct. The 2b and 9b are their marketing terms.


Verbiage change for detach operation complete

Verbiage change for detach operation complete - pls check me.

Fixes #50.


Remove explicit input encoding for bibliography

The template explicitly sets latin1 for input encoding of the bibliography. Unrelated to the package options utf8, latin1, or ansinew.
I assume that the bibliography should be encoded in the same encoding as the original tex file.
If not, the user should be able to specify the encoding by himself.

Well as you probably know, BibTeX can not handle UTF8 correctly. Therefore I changed it to latin1 to match at least the old status.
You are, however, right, that the encoding should be customizable (similar to biblatex) (although this is not part of my actual mandate).

I tried it without this setting and bibtex works perfectly with UTF8 😊 -
or did I do something wrong at
https://github.com/latextemplates/LNI/tree/lni-bibtex?files=1
Am 07.01.2017 09:40 schrieb "Martin Sievers"<EMAIL_ADDRESS>
Well as you probably know, BibTeX can not handle UTF8 correctly. Therefore
I changed it to latin1 to match at least the old status.
You are, however, right, that the encoding should be customizable (similar
to biblatex) (although this is not part of my actual mandate).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sieversMartin/LNI/pull/19#issuecomment-271071174, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABTafsTWfV8DJzt8L48aZzvuDJdst9Mwks5rP0-ZgaJpZM4LdXb7
.


How can I easily use this as a C library in place of libwebrtc?

This project is incomplete and does not support the management of media devices. For example, audio capture and playback. so I think it needs you to extend by yourself

I would say that it will be extremely hard to use C with this as this project also uses async for which you need your own async executors. I would imagine that the FFI story is bad with async whether the 'other' language supports async or not. I wish there was a more threaded simple sync API, would at least make the FFI story better. Moreover, C does not have the lifetime checks and guarantees which are provided by rustc.

Yes, i am thinking why don't support simple sync API.


Problems with execution dmn-xlsx-cli-0.2.0.jar

Hi!
I’m trying to use excel table to DMN table converter by executing command
java -jar dmn-xlsx-cli-0.2.0.jar --inputs A --outputs B "C:\xlsdmn\test2.xlsx" "C:\xlsdmn\test2.dmn"
But it throws an exception
PS C:\xlsdmn> java -jar dmn-xlsx-cli-0.2.0.jar --inputs A --outputs B "C:\xlsdmn\test2.xlsx" "C:\xlsdmn\test2.dmn" log4j:WARN No appenders could be found for logger (org.docx4j.jaxb.Context). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Could not convert file: Could not determine worksheet java.lang.RuntimeException: Could not determine worksheet         at org.camunda.bpm.dmn.xlsx.XlsxConverter.convert(XlsxConverter.java:65)         at org.camunda.bpm.dmn.xlsx.cli.CommandLineConverter.main(CommandLineConverter.java:71) Caused by: java.lang.NullPointerException         at org.camunda.bpm.dmn.xlsx.XlsxConverter.convert(XlsxConverter.java:63)         ... 1 more
excel document
Does anybody know what’s the problem with this?

Try using this -
dmn-xlsx-cli-0.2.1-SNAPSHOT.jar.zip
I was downloading the xlsx file via google spreadsheets.
I was also getting the same error - During debugging, I found that the converter jar is failing when getting the properties, hence giving exception. By adding an extra check, worked like a charm.
https://github.com/camunda/camunda-dmn-xlsx/pull/28


https not supported?

Ran the adapter against https://healthright.app.medicmobile.org and received the following error:
> var couch2pg = require('couch2pg');
undefined
> couch2pg().then(function () { console.log('done'); }).catch(function (err) {co
nsole.log(err);});
lib$rsvp$promise$$Promise {
  _id: 8,
  _label: undefined,
  _state: undefined,
  _result: undefined,
  _subscribers: [] }
> [Error: Protocol "https:" not supported. Expected "http:".]

when changing it to http://healthright.app.medicmobile.org, I managed to download 1,500some records into postgres quite quickly with no problems.
Not sure where this error originates from: does a library not support https or is healthright's https support lacking?

Went to import from Baglung and it forces a redirect from http to https, so I cannot get data off of it. Time to solve this problem.

For cereal?
I'm using Node's HTTP library.
https://github.com/medic/medic-analytics/blob/master/index.js#L2
https://nodejs.org/api/http.html
There's a wholly separate library for HTTPS.
https://nodejs.org/api/https.html
Apparently there is not some nice library that handles both cases simultaneously. Should be easy enough to change the library from http to https.

Still gives the same error (scheme must be http://). Let's see if the https library disassembles http:// schemed urls, ignores the scheme, and connects securely anyway.

Nope! 301 redirect.

Just for posterity, this is the actual error message when using http:// (regardless of http or https lib). There is no status text, only a status code. Not sure where the forward URL is kept.
> couch2pg().then(function () { console.log('done'); }).catch(function (err) {co
nsole.log(err);});
lib$rsvp$promise$$Promise {
  _id: 8,
  _label: undefined,
  _state: undefined,
  _result: undefined,
  _subscribers: [] }
> Invalid status code: 301,

No problem connecting to https://www.google.com/ with https lib.
I wonder if the issue is https://user:pass@site/? http://user:pass@site/ works fine.

Looks like the issue was scope. It was using system-installed version of software not local version I had modified. Installed local version to global and it connects now. I'll modify the code to always use https.


zeromq package is missing optional features provided by other distributions

Describe the bug
The zeromq package providing libzmq is missing several features that other distributions enable by default.
Some examples:

Upstream Debian Packaging: https://github.com/zeromq/libzmq/blob/1f4dd54f94009cb57bb68bfc856edc1c0bd3df06/packaging/debian/rules#L46
Arch Linux Packaging: https://gitlab.archlinux.org/archlinux/packaging/packages/zeromq/-/blob/main/PKGBUILD?ref_type=heads#L53-67
Fedora Packaging: https://src.fedoraproject.org/rpms/zeromq/blob/rawhide/f/zeromq.spec#_70

Features like ENABLE_CURVE and WITH_LIBSODIUM should probably be enabled by default. I was expecting curve support from the package and even saw libsodium in the package's inputs, yet I ran into an ENOTSUP on zmq_curve_keypair.

See the unused libsodium input: https://github.com/NixOS/nixpkgs/blob/31fb372aa93926f3e05401c7474cc560e197c765/pkgs/development/libraries/zeromq/4.x.nix#L7
See the ENOTSUP error here: https://libzmq.readthedocs.io/en/latest/zmq_curve_keypair.html

Expected behavior
An we should probably provide build options similar to the upstream RHEL packaging. See https://github.com/zeromq/libzmq/blob/1f4dd54f94009cb57bb68bfc856edc1c0bd3df06/packaging/redhat/zeromq.spec#L184-L193
Most should probably be enabled by default.
Notify maintainers

@fpletz

Add a :+1: reaction to issues you find important.

I'll work on this tomorrow, but I'd rather follow what Debian does:
override_dh_auto_configure:
	dh_auto_configure -- --with-pgm --with-libsodium --with-norm=yes \
		--with-libgssapi_krb5=yes --disable-Werror

Certainly we need to enable the flag to use libsodium.

About CurveZMQ, I'd say the best option is to provide an input flag as false that can be overridden by those who prefer it.

Since we depend on libsodium anyway I don't think there is any harm in enabling CurveZMQ by default - even without a flag. Are there negative side effects when enabling CurveZMQ?

override_dh_auto_configure:
	dh_auto_configure -- --with-pgm --with-libsodium --with-norm=yes \
		--with-libgssapi_krb5=yes --disable-Werror

Is OpenPGM or NORM even present in nixpkgs? I don't think that we can enable these.

About CurveZMQ, I'd say the best option is to provide an input flag as false that can be overridden by those who prefer it.

Since we depend on libsodium anyway I don't think there is any harm in enabling CurveZMQ by default - even without a flag. Are there negative side effects when enabling CurveZMQ?

Sorry, I was confusing the CurveCP protocol, which is supported by enabling libsodium,
with CurveZMQ, which is a CurveCP implementation but its a whole different library that depends on libzmq.
There is no flag related to CurveZMQ on ZeroMQ. But we do need to enable the flag to build with CurveCP support.

override_dh_auto_configure:
	dh_auto_configure -- --with-pgm --with-libsodium --with-norm=yes \
		--with-libgssapi_krb5=yes --disable-Werror

Is OpenPGM or NORM even present in nixpkgs? I don't think that we can enable these.

Yes, sure, if the flag doesn't apply to Nix then it will not be considered.

Closed by #338064.
(Why it wasn't closed automatically if it was linked?)


Use the correct published docker containers for the front end config based on the users machine/OS

Currently the VegaCapsule net_confs/config_frontends.hcl use published docker containers/images that are not compatible with Mac M1 computers.
Work is to be done in the following issue to publish docker containers/images that support M1 Macs.

https://github.com/vegaprotocol/frontend-monorepo/issues/1058

We need a way in VegaCapsule to ensure that based on the users machine/OS the correct containers/images are used.
It is expected that early users of VegaCapsule (market makers / people building strategies) will need the front ends and could very well be using M1 macs. Currently these users are unable to do so.

Blocked until the following is completed

https://github.com/orgs/vegaprotocol/projects/110/views/25

current PR: https://github.com/vegaprotocol/frontend-monorepo/pull/1104/files
thread for issue: https://vegaprotocol.slack.com/archives/C8WS7M50E/p1661245219957939


Document check style setup in Contributing

File -> Settings -> Tools -> Checkstyle
Add a new Configuration File

It will ask you about the properties defined in the config:
set the suppressions.xml

Open a SpongeAPI class
Go in the CheckStyle tab, make sure you are using the Sponge rules and run check module

Note: the suppressions rules may not be updated
Originally posted by @ImMorpheus in https://github.com/SpongePowered/SpongeAPI/pull/2237#issuecomment-736797213

That's probably outdated, see https://github.com/SpongePowered/SpongeAPI/commit/305d9d5fa22ea1eed13657a2118ad4f8ae320217

This is still probably worthehile at some level just for the real time feedback, but it doesn't have to be in depth at all


Incorrect query result on custom add driver (MariaDB)

System information:

Operating system (distribution) and version : Windows 11
DBeaver version : <IP_ADDRESS>112091630 ( from windows store )
Additional extensions : None

Connection specification:

Database name and version : 10.5.12-MariaDB MariaDB Server
Driver name : org.mariadb.jdbc - version 2.62
Do you use tunnels or proxies (SSH, SOCKS, etc)?  : No

Describe the problem you're observing:
Query shows incorrect result when using custom add driver, even with the same version as the default driver connection
Steps to reproduce, if exist:
Prepare database for simulation

get MariaDB columnstore docker ( docker pull MariaDB/columnstore )
run the above image
create database and Import dump file  from attached file ( dump-test.zip)

dump-test.zip
DBeaver simulation default connection

Create database connection with default provided mariadb driver
run the query ( please see the query below )
run the query multiple times, can test it to run 5 times, the result is correct and not changing

DBeaver simulation custom add driver

Open driver manager
Create a new driver connection with the same jar file as used in the above driver (default driver)
create a database connection with just created driver
run the query ( please see the query below )
run the query multiple times, can test it to run 5 times, the result is incorrect and keeps changing

Query :
select month(baldate), sum(balamount)
from vacc_plant_expense_a
where map4 = 'Plant Expenses - Exclude COGS and Others'
group by 1
order by 1
Include any warning/errors/backtraces from the logs

@BambangSumitra Hello. Please specify what is the difference in results.

@Matvey16
whenever i execute the query, query result show incorrect result and if executed multiple times the result keep changing.
please find attached video
https://user-images.githubusercontent.com/39480480/150245639-595249e3-833f-469b-8a88-a0a3219ac356.mp4

@BambangSumitra Thank you for the report, I reproduced this issue. We will look at the cause of this, but as a workaround you can copy MariaDB driver in driver manager and change the desired properties instead of creating a new one from scratch

@Matvey16
Is this issue caused by the mariadb driver or connection properties in DBeaver?

@BambangSumitra That is a bug in how new driver is created in DBeaver

Unfortunatelly, we can't just copy MariaDB driver - it turns into MySQL driver.
And we can't create MariaDB driver from the Drivers Manager - MariaDB driver is not in the list.
Maybe we should do something with these problems.

Hello @BambangSumitra
I have a question for you. Why do you use a custom provider instead of an official one? What's the point?

Hi Anastasiya,
Actually the actual problem raised on metabase, i'am using metabase and
mariadb columnstore as our database warehouse, why i'am using the custom
driver, just to make sure using the same driver as included in metabase and
to reproduce the same issues in metabase (metabase.com )
Thanks
Regards,
Bambang Sumitra
On Tue, Aug 2, 2022 at 10:18 PM Anastasiya @.***> wrote:

Hello @BambangSumitra https://github.com/BambangSumitra
I have a question for you. Why do you use a custom provider instead of an
official one? What's the point?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/15188#issuecomment-1202802163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJNGZIEAF6W6TNYYDE7FHK3VXE35PANCNFSM5MCQ2EEQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


[IDEA/REQUEST] custom font for front matter

Is your feature request related to a problem? Please describe.
I want to make the front matter more distinguishable
Describe the solution you'd like
A style setting to set a custom font for it.

Easy enough to do. Added to the Roadmap.


List the libraries use for the creation of the demo app

As a User of the demo app
I want to know the denpencies of the app
So that I have a list of all the libraries used in the app
What needs to be provided:

The list of the libraries used to build the app
The list of libraries used by the ODS code library
For each library identify the license associated to it

There is already a THIRD_PARTY.txt file in the repository. I suppose you want to display this in the app too?

This could be good to finalize this issue before the v1 @B3nz01d, what do you think?

@paulinea I understand the list provided in the about > "Third party library" contains all the libs used by the demo app. Where would the list of the lib itself's dependency be available?

This list includes the dependencies used by the library.

@paulinea is it possible to isolate in this file ODS lib dependencies from the demo app dependencies?

@B3nz01d Yes but we have to define how. Some libraries are used for the demo app and for the lib so we will have redundant things.

I propose this format and list the lib first and then the full app list (redundancy is ok, just make sure that transitive redundancies are not necessary):
In the ODS Lib
Material Components
Copyright 2017 The Android Open Source Project
https://github.com/material-components/material-components-android
Apache License 2.0
Coil
Copyright 2023 Coil Contributors
https://github.com/coil-kt/coil
Apache License 2.0
In the app
Copyright 2020 The Android Open Source Project
https://github.com/google/accompanist
Apache License 2.0
AndroidX
Copyright 2021 The Android Open Source Project
https://github.com/androidx/androidx
Apache License 2.0
Coil
Copyright 2023 Coil Contributors
https://github.com/coil-kt/coil
Apache License 2.0
Dagger
Copyright 2012 The Dagger Authors
https://github.com/google/dagger
Apache License 2.0
Firebase
Copyright 2019 Google LLC
https://github.com/firebase/firebase-android-sdk
Apache License 2.0
Google services
Copyright (C) 2023 The Android Open Source Project
https://github.com/google/play-services-plugins/tree/master/google-services-plugin
Apache License 2.0
JUnit
https://github.com/junit-team/junit5/
Eclipse Public License 2.0
KotlinPoet
Copyright 2017 Square, Inc.
https://github.com/square/kotlinpoet
Apache License 2.0
Kotlin Symbol Processing
https://github.com/google/ksp
Apache License 2.0
Material Components
Copyright 2017 The Android Open Source Project
https://github.com/material-components/material-components-android
Apache License 2.0
ODS libraries
Copyright (c) Orange SA
https://github.com/Orange-OpenSource/ods-android
MIT License
Roboto fonts
https://fonts.google.com/specimen/Roboto
Apache License 2.0
Timber
Copyright 2013 Jake Wharton
https://github.com/JakeWharton/timber
Apache License 2.0