Introduce a section for developers and automate the generation of documentation

Description
The documentation website appears to be solely focused on the user's perspective, rather than also incorporating the developer's viewpoint as well. Although there is a Swagger documentation available at sigstore.dev/swagger/, it is not accessible from the main documentation website. This can be fixed by including an additional link in the header of the website as shown below.

Additionally, although it is mentioned in sigstore's GSoD proposal that finding a way to “to ensure that documentation does not go out of date” is out of the scope of the GSoD project, it is actually very straightforward to  incorporate a way to automate the generation of documentation, at least from a developer's perspective. This is based on my experience with automating the documentation for  the Talawa docs website as part of GSoD 2022 of which I was a mentor.
To keep pace with the changes that occur with any number of pull requests, CI/CD pipelines can be used to automate the documentation process. Here's how it works (as illustrated in the accompanying figure):

First, when making a pull request a GitHub Action checks for any Go files in it and sees if they have comments in a specific format. If the checks are unsuccessful and changes to the files will be requested.

If the pull request is successful, another GitHub Action generates static HTML files from the comments in the changed and/or added files using the godoc command. These artefact files are then sent to the sigstore documentation repository.

Finally, another GitHub Action in the sigstore docs repository collates the HTML files and organises them into a pre-specified template, creating a comprehensive documentation page that is added to the sigstore documentation site.

Sigstore's constituent repositories (Cosign, Fulcio, Rekor, Gitsign, etc.) can automatically generate documentation utilising tools such godoc in the pipeline described above. Since the constituent repositories are all written in Go, the same pipeline with the Godoc library would suffice for each of the four aforementioned repositories. In the same vein, It would not be particularly difficult to make modifications for the repositories written in Python (sigstore-python) or Rust (sigstore-rs) or Java (sigstore-java) or another language for that matter. In all these cases, it would involve modifying of workflows found in the Talawa API and then just applying them to our use cases. This works well due to the similarity between the websites that host both Talawa and sigstore.

The first part of this is a dup of https://github.com/sigstore/docs/issues/117
I do like that idea of exploring automation and having developer focused documentation come from the repos!


Add serverless project resources

Description

~Currently only includes elasticsearch_project resources. IMO we should include at least all project types, also~ likely worthwhile including a serverless_region data source, and maybe project data sources since they should be simple to add re-using the resource read code.
This PR also include the terraform code generators, currently configured to generate the serverless resource schema and openapi client.
How Has This Been Tested?

Manually, acceptance tests. I need to add some more unit tests here.
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improves code quality but has no user-facing effect)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation

Readiness Checklist

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

I need to add more tests and docs here.

@tobio , make gen adds the license header to a bunch of files.

@tobio , I completed the review (though I skim through security_test.go and observability_test.go which look similar to elasticsearch_test.go)


Fixed NASM required in PATH when building for Win64.

Thank you so much for this great library.
We are using OpenSSL inside DCMTK (as an optional component) and ran into minor issues when building it for Win64. This pull request is based on a patch we apply for building OpenSSL to work around the issue.

If I may guess anything, it's that this PR is going nowhere.  The issue is simply resolved by making sure %PATH% is set up correctly.
Suggested action: close PR.  Anyone disagree?

No followups, and noted in issue as scheduled for future close, closing.


Added isFlagged property to rapidReviews and fullReview entities

Closing this as this work was merged via a different PR. Sorry for the confusion.

Closing this as this work was merged via a different PR. Sorry for the confusion.


build: improve README to CIDgravity/CIDgravity npm command

See https://github.com/CIDgravity/CIDgravity/issues/609

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ActivationBuffer used inconsistently re running out of data.

When you run trainSAE, it expects to run through all of the data because the line for step, acts in enumerate(tqdm(activations, total=steps)) simply exits the loop when StopIteration is raised. But evaluate simply calls acts = next(activations).to(device), so it fails if the data runs out. I think ideally this case should be handled gracefully, but it should at least be documented.
Code:
from nnsight import LanguageModel
from dictionary_learning import ActivationBuffer
from dictionary_learning.training import trainSAE
from dictionary_learning.evaluation import evaluate

model = LanguageModel("EleutherAI/pythia-70m-deduped")
submodule = model.gpt_neox.layers[1].mlp
activation_dim = 512
dictionary_size = 16 * activation_dim

data = iter(
    [
        "This is some example data",
        "In real life, for training a dictionary",
        "you would need much more data than this",
    ]
)
buffer = ActivationBuffer(
    data,
    model,
    submodule,
    out_feats=activation_dim,
    n_ctxs=3e4,
)

ae = trainSAE(
    buffer,
    activation_dim,
    dictionary_size,
    lr=3e-4,
    sparsity_penalty=1e-3,
)

buffer = ActivationBuffer(
    iter(["hello", "world"]),
    model,
    submodule,
    out_feats=activation_dim,
    n_ctxs=300,
)

print(evaluate(model, submodule, ae, buffer))

Result:
joel@simplex ~/c/mamba-sae (main)> python3.11 test.py
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
0it [00:00, ?it/s]
Traceback (most recent call last):
  File "/Users/joel/code/mamba-sae/dictionary_learning/buffer.py", line 94, in text_batch
    return [
           ^
  File "/Users/joel/code/mamba-sae/dictionary_learning/buffer.py", line 95, in <listcomp>
    next(self.data) for _ in range(batch_size)
    ^^^^^^^^^^^^^^^
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/joel/code/mamba-sae/test.py", line 46, in <module>
    print(evaluate(model, submodule, ae, buffer))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/joel/code/mamba-sae/dictionary_learning/evaluation.py", line 119, in evaluate
    acts = next(activations).to(device)
           ^^^^^^^^^^^^^^^^^
  File "/Users/joel/code/mamba-sae/dictionary_learning/buffer.py", line 76, in __next__
    self.refresh()
  File "/Users/joel/code/mamba-sae/dictionary_learning/buffer.py", line 164, in refresh
    self._refresh_std()
  File "/Users/joel/code/mamba-sae/dictionary_learning/buffer.py", line 121, in _refresh_std
    with self.model.invoke(self.text_batch(), truncation=True, max_length=self.ctx_len) as invoker:
                           ^^^^^^^^^^^^^^^^^
  File "/Users/joel/code/mamba-sae/dictionary_learning/buffer.py", line 98, in text_batch
    raise StopIteration("End of data stream reached")
StopIteration: End of data stream reached

Thanks -- I've now added a more informative error for this.


DRAFT - DCA profiles in flare

What does this PR do?

This PR will ad the profiles for the Datadog Cluster Agent in the flare when using the --profile option in the flare command.
Motivation

Dev card: https://datadoghq.atlassian.net/browse/CONT-3593
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

To test this change, you can:
1- Generate a profile in the flare command in the Cluster Agent pod:
kubectl exec -it <DCA_POD_NAME> agent flare --profile 30
2- Go the profiles folder created in the flare and use go tools to display it:
go tool pprof -http=localhost:8080 dca-1st-heap.pprof
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

@mathieucolin Can we close this PR as being superseded by #19221 ?


[ISSUE-1191, ISSUE-1208] Implemented search and pagination for schema…

… registry overview page.

[ ] Breaking change? (if so, please describe the impact and migration path for existing applications:)

What changes did you make? (Give an overview)
There were implemented search, pagination, and sorting for the schema registry page.
Is there anything you'd like reviewers to focus on?
Contract for "/api/clusters/{clusterName}/schemas" has been changed on the backend side, so we need to fix UI accordingly.
How Has This Been Tested? (put an "X" next to an item)

[ ] No need to
[ X] Manually(please, describe, when necessary)
[ X] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "X" next to an item, otherwise PR will fail)

[ X] I have performed a self-review of my own code
[X ] I have commented my code, particularly in hard-to-understand areas
[ X] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[ X] My changes generate no new warnings(e.g. Sonar is happy)
[X ] I have added tests that prove my fix is effective or that my feature works
[ X] New and existing unit tests pass locally with my changes
[ X] Any dependent changes have been merged

Check out Contributing and Code of Conduct

@ValentinPrischepa also please take a look at tests, there's one backend test failing rn

I think frontend is done
Changes that I've done

Refactored SchemaVersion and LatestVersionItem tests to testing-library and removed their snapshots
Changed schemaSlice to work with pagination and search
Updated Schemas List, Details, Edit components

Now List fetches paginated and filtered by search params results
Now Details and Edit fetch their data by themselves

Rewrote List, Details, Edit tests with their own fetching in mind
Changed fixtures to make them look clean
New useSearch hook

Main use is to work with Search component
Provides variable and a function to update it
Under the hood updates ?q search param and provides it as moised variable

Questionable stuff
In this version List and Details fetch their own data from API
Reasoning:
In previous version we fetched all schemas (unpaginated) in our schema routes components but with pagination it's not possible
Previous implementation would break when we try to open page by url if it was on page >=2
List and Details fetch both latest schema and all versions and produce two requests
We already have lastest version in all versions and we can just get first one (it's ordered by desc)
Reasoning:
If in future something with latest schema will change - we won't have too much confusion and if versions ordering will change - we don't have to change code to make it correctly select latest schema
useSearch implementation code is questionable by itself
I think i missed something there
When you search something on schemas List and click on link to schemas List in menu - search input value is not changing and search results are without search filter
Search components input is uncontrolled input by some reason - i didn't manage to change this behavior without breaking something

@Motherships PLs next time use your own branch

Testing has done successfully:

Pagination works correctly
Default sorting is right and doesn’t change during transition inside the schema and back.
Search works correctly

Functionality CrUD is preserved for all types of schemas.

@agolosen thanks! Much appreciated


Update release note 1.2.0

Coverage remained the same at 34.801% when pulling 733154b4d121488f0b0141d45e2a1478a6cd0f2e on yiyi/update_release_note_1.2.0 into 47ba0b8278b3859c9a14c044bcfe153b378324b6 on pai-1.2.y.

maybe we could include a upgrade guide?

maybe we could include a upgrade guide?

We already have a upgrade guide in OpenPAI Handbook, I think users can still follow it.

maybe we could include a upgrade guide?

We already have a upgrade guide in OpenPAI Handbook, I think users can still follow it.

good. could you include the URL to upgrade guide in the release note?

good. could you include the URL to upgrade guide in the release note?

OK, Added.


Regression in 3.13: custom matcher hash argument improperly converted to keyword args, results in ArgumentError

Subject of the issue
My project has a custom matcher defined with an optional keyword arg. After upgrading to RSpec 3.13, I get an ArgumentError that indicates that RSpec is converting a hash argument into keyword args for some reason.
Your environment

Ruby version: 3.2.2
rspec-expectations version: 3.13.0

Steps to reproduce
Create a file named rspec_bug.rb with these contents:
require "bundler/inline"

gemfile do
  source "https://rubygems.org"
  gem "rspec", ENV.fetch("RSPEC_VERSION", "3.13.0")
end

require "rspec"
require "rspec/autorun"

puts "Ruby version: #{RUBY_VERSION}"
puts "RSpec::Expectations version: #{RSpec::Expectations::Version::STRING}"

RSpec::Matchers.define :match_against_with_optional_kwarg do |hash, optional_kwarg: true|
  match { |actual| true }
end

RSpec::Matchers.define :match_against_without_optional_kwarg do |hash|
  match { |actual| true }
end

RSpec.describe "A custom matcher" do
  it "can accept an optional kwarg" do
    expect(:something).to match_against_with_optional_kwarg({5 => "five", "some" => "hash", "of" => "data", [:foo] => 10})
  end

  it "can be used without an optional kwarg" do
    expect(:something).to match_against_without_optional_kwarg({5 => "five", "some" => "hash", "of" => "data", [:foo] => 10})
  end
end

Expected behavior
I expect this spec to pass, as it does on every recent version of RSpec:
 ~/code/ RSPEC_VERSION=3.8.0 ruby rspec_bug.rb -b
Ruby version: 3.2.2
RSpec::Expectations version: 3.8.6
..

Finished in 0.00132 seconds (files took 0.04301 seconds to load)
2 examples, 0 failures

 ~/code/ RSPEC_VERSION=3.9.0 ruby rspec_bug.rb -b
Ruby version: 3.2.2
RSpec::Expectations version: 3.9.4
..

Finished in 0.00194 seconds (files took 0.04708 seconds to load)
2 examples, 0 failures

 ~/code/ RSPEC_VERSION=3.10.0 ruby rspec_bug.rb -b
Ruby version: 3.2.2
RSpec::Expectations version: 3.10.2
..

Finished in 0.00181 seconds (files took 0.04384 seconds to load)
2 examples, 0 failures

 ~/code/ RSPEC_VERSION=3.11.0 ruby rspec_bug.rb -b
Ruby version: 3.2.2
RSpec::Expectations version: 3.11.1
..

Finished in 0.00135 seconds (files took 0.04207 seconds to load)
2 examples, 0 failures

 ~/code/ RSPEC_VERSION=3.12.0 ruby rspec_bug.rb -b
Ruby version: 3.2.2
RSpec::Expectations version: 3.12.3
..

Finished in 0.00166 seconds (files took 0.04384 seconds to load)
2 examples, 0 failures

Actual behavior
On RSpec 3.13, it fails with a very odd error:
 ~/code/ RSPEC_VERSION=3.13.0 ruby rspec_bug.rb -b
Ruby version: 3.2.2
RSpec::Expectations version: 3.13.0
F.

Failures:

  1) A custom matcher can accept an optional kwarg
     Failure/Error:
       RSpec::Matchers.define :match_against_with_optional_kwarg do |hash, optional_kwarg: true|
         match { |actual| true }
       end

     ArgumentError:
       unknown keywords: 5, "some", "of", [:foo]
     # rspec_bug.rb:14:in `block in <main>'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-support-3.13.1/lib/rspec/support/with_keywords_when_needed.rb:20:in `class_exec'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-support-3.13.1/lib/rspec/support/with_keywords_when_needed.rb:20:in `class_exec'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-support-3.13.1/lib/rspec/support/with_keywords_when_needed.rb:19:in `eval'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-support-3.13.1/lib/rspec/support/with_keywords_when_needed.rb:19:in `class_exec'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-expectations-3.13.0/lib/rspec/matchers/dsl.rb:475:in `initialize'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-expectations-3.13.0/lib/rspec/matchers/dsl.rb:76:in `new'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-expectations-3.13.0/lib/rspec/matchers/dsl.rb:76:in `block in define'
     # rspec_bug.rb:24:in `block (2 levels) in <main>'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:263:in `instance_exec'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:263:in `block in run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:511:in `block in with_around_and_singleton_context_hooks'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:468:in `block in with_around_example_hooks'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/hooks.rb:486:in `block in run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/hooks.rb:624:in `run_around_example_hooks_for'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/hooks.rb:486:in `run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:468:in `with_around_example_hooks'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:511:in `with_around_and_singleton_context_hooks'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example.rb:259:in `run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example_group.rb:646:in `block in run_examples'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example_group.rb:642:in `map'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example_group.rb:642:in `run_examples'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/example_group.rb:607:in `run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:121:in `block (3 levels) in run_specs'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:121:in `map'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:121:in `block (2 levels) in run_specs'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/configuration.rb:2091:in `with_suite_hooks'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:116:in `block in run_specs'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/reporter.rb:74:in `report'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:115:in `run_specs'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:89:in `run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:71:in `run'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:45:in `invoke'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:38:in `perform_at_exit'
     # /Users/myron/.rvm/gems/ruby-3.2.2/gems/rspec-core-3.13.0/lib/rspec/core/runner.rb:24:in `block in autorun'

Finished in 0.00177 seconds (files took 0.04443 seconds to load)
2 examples, 1 failure

Failed examples:

rspec rspec_bug.rb:23 # A custom matcher can accept an optional kwarg

The error (ArgumentError: unknown keywords: 5, "some", "of", [:foo]) indicates that RSpec is somehow converting my hash of data into keyword args, even though the keys aren't valid for keyword args, and it's just a hash of data being passed as a positional arg.
This bug appears to be triggered by the presence of an optional keyword arg on the definition of the matcher itself.

Myron, thanks for reporting!
Most definitely caused by https://github.com/rspec/rspec-support/pull/591
@malcolmohare can you please have a look?

If you change your input hash to include a Symbol key, this will fail on older versions of rspec as well {5 => "five", :some => "hash", "of" => "data", [:foo] => 10}.
I think the core of this is a bug somewhere in here:
https://github.com/rspec/rspec-support/blob/main/lib/rspec/support/method_signature_verifier.rb#L84
        def has_kw_args_in?(args)
          Hash === args.last &&
            could_contain_kw_args?(args) &&
            (RubyFeatures.kw_arg_separation? || args.last.empty? || args.last.keys.any? { |x| x.is_a?(Symbol) })
        end

        # Without considering what the last arg is, could it
        # contain keyword arguments?
        def could_contain_kw_args?(args)
          return false if args.count <= min_non_kw_args

          @allows_any_kw_args || @allowed_kw_args.any?
        end

This method signature types are [optional, key].  Obviously the code is incorrectly interpreting the optional hash as a splat arg.  I think the could_contain_kw_args is correctly returning that the args COULD have kwargs in them.  I THINK the answer is that some additional case needs to be added to has_kw_args_in to specifically handle the case of RubyFeatures.kw_arg_separation? && !@allows_any_kw_args but I have to re-read the ruby 3 changes and understand the cases a bit more.

I've got a draft PR of the fix up, have a few tests to touch up and reason through.
Its a bit tricky because of the ambiguity of how the args get presented.  You can see through the little demo the args are presented the same way whether its a straight kwargs or a hash, but the assignment of the args to parameters is different.
def foo(*args)
  puts args.inspect
end

def bar(x=1, a:2)
  puts "x:#{x} a:#{a}"
end

foo(:a => 1)  # [{:a=>1}]
foo({:a => 1}) # [{:a=>1}]

bar(:a => 1). # x:1 a:1
bar({:a => 1}). # x:{:a => 1} a:2

I've opened an issue in the rspec-support project.  I attempted to fix this issue today, but ended up being stymied by a larger issue, namely that the argument forwarding to the code checking the methods is not ruby 3 kwargs behavior compatible.  I assume the mitigation / fix for this regression will be discussed there.

A couple updates here:

I've discovered that this regression is also in 3.12 if you upgrade rspec-support to 3.12.2. When the fix gets merged it could be nice for users to backport it and release it as 3.12.3.
There's a pretty simple work around for this. Instead of this:

RSpec::Matchers.define :match_against_with_optional_kwarg do |hash, optional_kwarg: true|
  match { |actual| true }
end

...do this:
RSpec::Matchers.define :match_against_with_optional_kwarg do |hash, options = {}|
  optional_kwarg = options.fetch(:optional_kwarg, true)
  match { |actual| true }
end


s/communite/communicate, attempt grammar fix

First-time contributor... nice!
Also, you should sign the CLA at some point for your future, more creative pull requests sent from interesting places around the waters.


What happens if VLMAX ends up less than 1?

For example (with VLEN=64), a vset{i}vl{i} instruction could set LMUL=1/8, SEW=32, so that an element can't "fit" in the now 8-bit register group (VLMAX=1/4). Or we could have a more sensible setting of LMUL=1/8, SEW=8, but then attempt to execute a vle16 instruction.
As far as I could find in the spec, the only thing close to explicitly addressing this case is section 6.3, which states vset{i}vl{i} instructions should set vl such that it's less than or equal to VLMAX - so for fractional VLMAX, this necessarily implies vl=0, since vl is an integer. The destination register would then be handled like any other tail elements according to vta. I also found this thread stating VLMAX<1 is "reserved", but I'm not sure what that means for us trying to implement something - should we have vset{i}vl{i} set vill, then?

The spec says: "An attempt to set an unsupported SEW and LMUL configuration sets the vill bit in vtype". Section 3.4.2. Vector Register Grouping

We weren't sure whether "supported SEW and LMUL configuration" refers to SEW/LMUL values that are out of bounds, or specific combinations of SEW and LMUL that result in VLMAX<1. The latter would lead to significantly more complicated implementation logic, as every possible combination of SEW and LMUL would have to be checked for illegality.


Output bitrate as a 'per device' setting?

Hi there,
I was wondeeing wether it was possible to set OUTPUT_BIT_RATE (from .env). on a per device setting?
This would imply, that there currently was any notion of "client device" in koel. It could be saved in the current session.
Background: with traffic still being a consideration for most users on mobile plans, it would be great to have, let's say, 128k on my phone but 320k in my browser at home.
Cheers
Thomas

This is not supported, sorry.


Implement AIP11

https://github.com/ArkEcosystem/AIPs/blob/master/AIPS/aip-11.md
See https://github.com/ArkEcosystem/core/tree/master/packages/crypto/src for reference once Core 2.6 is released.

Status update:
~95% done.
Mostly documentation and a few small changes left.
https://github.com/users/sleepdefic1t/projects/2


Azure insights trackEvent function is reporting duplicate events.

Customer has raised an issue on Microsoft Q&A
Hello,
we have implemented Azure insights in our angular application.
Sometimes trackEvent function is reporting single event multiple times.
I just want to know, is there any case/scenario when azure insights could send duplicates event data ?
https://docs.microsoft.com/en-us/answers/questions/705078/index.html

The only time ApplicationInsights will send and "event" payload more than once is if the request to send the batched events fails, at which time it will "retry" the payload and resend the entire batch events (not just the values from trackEvent. This can be disabled during initialization with the isRetryDisabled config settings


ReferenceError: DEBUG is not defined

I don't get it! I can't see anything related to planck.js.

Well, DEBUG is globally declared in many files without a keyword.
But I've webpacked planck.js without any difficulty before, so I'm not sure what's happening here. It's almost like he required a specific module directly, in strict mode.
const Body = require('plank.js/lib/Body'), maybe?
in any case, @MegaUITeam, it would help if you gave a better description of what's going on here.

@BenZed Does following helps to fix it?
if (typeof DEBUG === 'undefined') { var DEBUG = false; }

@shakiba, its @MegaUITeam  that's having the problem!
plank.js works fine for me :)

@BenZed I'm glad to hear that! :)  I asked you because you mentioned that the issue may be because of requiting a file directly in strict mode.

@MegaUITeam  Are you requiring modules directly?
I have a repo that uses webpack and planck.js, and if I import objects from the module in point, this does not happen.
import Body from 'planck.js/lib/Body'

vs
import { Body } from 'plank.js' // < causes no problems

I ran into the same problem as @MegaUITeam with bundling planck-js with webpack. Turns out I was guilty of importing in point:
import { Body } from 'planck-js/lib'

Following @BenZed example fixes the referenceError.

I change the code, so hopefully this issue is solved. I'm going to close this feel free to open it again if required.


Update Documentation for Birthdays

With reference to #59 and #114

Pull Request Test Coverage Report for Build 288

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

Totals

Change from base Build 286:
0.0%

Covered Lines:
2100

Relevant Lines:
2583

💛  - Coveralls


Fix YAML error in README files appearing on GitHub

Fix YAML error in README files appearing on GitHub.
See error message:

Fix #6897.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Testing

I have no metric to check this, so just merge once you feel like it?

I assume Testing is the result of a master thesis. There has not been any metric established yet. I agree that deliverables should not be versioned.

I think I bypass-merged these changes already. Please check yourselves


mistakes withdrawal celo CUSD TO CELO

Dear support team
Good morning and have a nice day to you
I have problems i mistake withdrawal can u cancelled and returned my mony
I withdrawal from coinlist celo CUSD to celo bainace
this is my transactions ID
0x12a0380ed055715278673d75f4ab2ef11e6c2c3e922d78c5787397dc691a0252
plz cancelled
Thanks regards

Kind reminder


Performance: Replace std::map with std::unordered_map

SFML is using trees instead of hash tables in many places
I was profiling my SFML app and noticed this:

https://github.com/SFML/SFML/blob/b762276a27efac365968c8330bdb0b5cca44bf52/include/SFML/Graphics/Font.hpp#L332 https://github.com/SFML/SFML/blob/b762276a27efac365968c8330bdb0b5cca44bf52/include/SFML/Graphics/Font.hpp#L392
Both GlyphTable and PageTable should be unordered_map. Ordered iteration is not required by the Font class, and this causes sf::Font::GetGlyph to be much slower than is necessary.
There are numerous other instances of std::map in the SFML codebase at a quick glance. Most or all of them could likely be replaced with std::unordered_map for noticeable performance gains.

Can you do the modification, and show us the results using your profiler?

Probably needless to say, but make sure you profile in Release mode and without Debugger running (these are two independent settings in MSVC).
Also, this should probably become part of the C++17 solution design. I would even go as far as saying that after C++11, std::unordered_map should be the default choice for key-value stores, not std::map. That's also what virtually every other programming language on this planet does.

I spent a few minutes trying to get SFML build, but was getting a bunch of errors. I don't entirely know how to configure it correctly. I generally just use the pre-built binaries for VS 2019 from the "Releases" section on Github so that I don't have to fiddle around with CMake.
You can set up a simple test case yourself by just rendering an sf::Text string to the window with a large enough number of characters for GetGlyph to show up in your profiler (100-200 should be plenty, more if you want to stress test it). The profiler in the screenshot above is Intel VTune, which is freely available here (https://software.intel.com/content/www/us/en/develop/tools/oneapi/components/vtune-profiler.html).
The exact performance numbers are obviously going to depend on the code and hardware, but you don't need to profile to know that std::unordered_map is O(1) amortized and std::map is O(log N). It would be more valuable for the SFML team to use their own code and hardware, rather than depend on my results, so that you can perform consistent benchmarks across future versions and changes.

The exact performance numbers are obviously going to depend on the code and hardware, but you don't need to profile to know that std::unordered_map is O(1) amortized and std::map is O(log N).

Of course, although scale matters. For a few dozen objects, the difference between hash maps and tree maps may not be visible. There's also other factors, like quality of the hash/compare function, insertion/deletion/read patterns, etc. But I agree that unordered_map is a reasonable default choice. With std::vector it's similar: it's almost always the right choice. Its cache friendlyness and fast random access are so significant that it often outperforms alternatives, even if the O-numbers speak against it.
The Rust developers realized this and advertise it in the documentation:

To get this out of the way: you should probably just use Vec or HashMap. These two collections cover most use cases for generic data storage and processing. They are exceptionally good at doing what they do. All the other collections in the standard library have specific use cases where they are the optimal choice, but these cases are borderline niche in comparison. Even when Vec and HashMap are technically suboptimal, they're probably a good enough choice to get started.

Use a LinkedList when:

...

NOTE: It is almost always better to use Vec or VecDeque because array-based containers are generally faster, more memory efficient, and make better use of CPU cache.

Of course, although scale matters. For a few dozen objects, the difference between hash maps and tree maps may not be visible.
Sure. Consider an sf::Text object with 100 characters. That's 200 map lookups. If we assume the user is only using one characterSize and ignore the m_pages lookups, then it's only 100 map lookups. If outlineThickness, bold and character index are all consistent, there likely won't be many more than ~60 glyphs in the GlyphTable. Log2(60) is still ~6 accesses (and potential cache misses) per getGlyph call vs. one access for an unordered_map. Probably not the slowest thing in your app (especially if you're drawing sf::Sprites and not batching them, which was the first major bottleneck in my code), but it's free gains.

Of course, although scale matters. For a few dozen objects, the difference between hash maps and tree maps may not be visible. There's also other factors, like quality of the hash/compare function, insertion/deletion/read patterns, etc. But I agree that unordered_map is a reasonable default choice.

Yes, you are right there are other factors which becomes important in performance comparision of std::map and std::unordered_map. The problem is we cannot test the performance over all possible cases. I mean the performance depeneds on the data fed to the data structure. In most of the cases it turns out unordered_map are fast and offers O(1) access. Whereas in some other cases the performance of unordered_map may be equal to map or even wort than map (if large number of collisons occurs). Replacing map with unordered_map is worth improvement in performance for almost all cases.

I'd say if C++11 was used when SFML was originally written, you'd need to prove that you really need std::map over std::unordered_map. So ideally I'd like to see all instances of std::map replaced to std::unoredered_map unless the order of elements really matters and we gain something by having elements be sorted.

I think we all agree here 🙂
As I wrote, TLDR:

But I agree that unordered_map is a reasonable default choice.

I think we all agree here 🙂
As I wrote, TLDR:

But I agree that unordered_map is a reasonable default choice.

Yes, should i make a PR, updating all the instances of std::map with std::unorderd_map?

Before you jump right into this, we would like to iron out the C++17 solution design a bit, so it becomes clear in what direction SFML should go, and which guidelines to use for migrations. This aims to communicate clearly what is in scope and what not, and would avoid lengthy discussions in each C++17 related issue.
I'll try to take care of that within the next days.

I believe this issue has already been handled by #1862 and can be closed.


Kmeans++ : Always the same seed

Hi,
I discuss with @Darredevil about the K means.
We solved few problems in my code and in the level.
But now I'm not able to get various seed to test the 4 different predictions.
With the previous code level, It worked, I mean, I was able to get the different seeds, and my code was successful only with seed 1.
Now I get only seed 1. So ok, my code now works all the time, but it's not the normal behavior.
I tried to change the seed, or by reloading the level (F5 in Chrome), or by changing a little bit the code. 10 times each, and always the same seed.
@nwinter, any idea ?
Vettax
PS : to be precise, With f5 under Chrome, I always get the same debug and same generated random seed :
Manannan Mac Lir's Ray| Generated random seed -172894491305 of type playerCode from sessionIDs ["53cd7fab2bb1f44d0507a06f"] app.js:59
|Manannan Mac Lir's Ray| Using seed<PHONE_NUMBER> from seedBucket 1
If I change the code, the generated random seed number is different, but it always end in the same seed bucket:
|Manannan Mac Lir's Ray| Generated random seed -172950288191 of type playerCode from sessionIDs ["53cd7fab2bb1f44d0507a06f"] app.js:59
|Manannan Mac Lir's Ray| Using seed<PHONE_NUMBER> from seedBucket 1
a link to my session:
http://codecombat.com/play/level/k-means-cluster-wars?session=53cd7fab2bb1f44d0507a06f

Moved this to the in-level Tasks list.


Course Scraper

Pulls from OSU's registration tool.
Could also consider scraping the following fields:

Credit hours
Enrollment / Seat availability
Link Identifier (used to connect lectures and recitations)

lgtm


Example for returning a list of objects as JSON

Is there an example of what would be the NTEX equivalent of the following express.js code:
app.get('/names', (req, res) => {
    names = ['John', 'Jack', 'James'];
    res.setHeader('Content-Type', 'application/json')
    res.send(JSON.stringify(names))
})

if you need client then https://docs.rs/ntex/0.3.8/ntex/http/client/struct.ClientRequest.html#method.send_json
if you need server handling then https://github.com/ntex-rs/examples/blob/6b8bb1160bdec940b8e4ec61fbc56b84466c6a48/json/src/main.rs#L14

@fafhrd91 Thanks for the quick reply. Is this the recommended way:
async fn simulators()  -> HttpResponse {
    let names: Vec<&str> = vec!["John", "Jack", "James"];
    let body = ntex::web::types::Json(names);
    HttpResponse::Ok().json(&body.0)
}

HttpResponse::Ok().json(names) should just work


Treat all unknown extensions as resources

I’m getting a bit tired of extending our whitelist like in #665.
I think we should have a “catch all” loader that uses file-loader for any unknown extensions.
This makes sense because it’s easy to explain: “if you import something that isn’t JS or CSS, it becomes a part of the build, you get its filename, and can do whatever with it”.
I think @dralletje planned to look into this.

Looking at webpack.config.dev.js, I'm wondering: why use url-loader for audio / video, but file-loader for images? In the scenarios I'm most familiar with, you'd usually do the complete opposite of that: you want essential images, like sprite sheets, to load immediately, but sound and video can wait.
I think this using file-loader for unknown resources is a good default.

Looking at webpack.config.dev.js, I'm wondering: why use url-loader for audio / video, but file-loader for images?

I didn’t really think it through. If you have better ideas for defaults please submit a PR.

@gaearon Any word on this? I wanted to use a php file, to ajax from a form. But I have to manually copy it over after the build process since there's no included loader for php

@iRoachie I think any backend files (like php) should live outside the project folder. The project folder is only meant to be for files related to the front-end client-side app.

This is a good example of working with backend APIs. It assumes Node but PHP would work similarly.

How's this similar to PHP? I'm using the php to send and email when the data from the form is posted. The link you provided assumes using Node and using endpoints to access the data.

By similar I meant that, like in that tutorial, you can put client and server code in the different folders, and you can use proxy in development to call /mybackend.php which would get resolved to the specified port. In production, you can have index.php serve built index.html.

@gaearon I messaged you on twitter

This is interesting. We are having the same issue with the angular-cli. In my opinion, regardless of "how" you treat the file (emitted with file-loader into dist, or converted to js, etc), my opinion is that you want it managed by webpack in some way or another.
A catchall unknown-source loader feels like it would be pretty beneficial. I wonder if perhaps leveraging the include property on the loader object to pass a Regex of a folder path like ./assets or w/e.

@fson, @gaearon I can take this if we agree on a few assumptions:

I don't think we should rely on naming conventions. When loading a .png and .svg works, loading a .bmp should really not feel any different to a developer. Instead, I suggest that we load anything in /src that's not already addressed by another loader.

@cesarandreu why not preferring the url-loader with 10k limit for unmatched files?

I don't think there's an explicit "use this loader if no other addresses it", so I'll suggest using a test regex a negative lookahead regex. Unfortunately that'll require re-typing all the file names handled in other loaders, but it looks like a small price to pay, I can add comments.

While at it, if everyone agrees I'll move all items that are currently handled by file loader to url-loader as well per @cesarandreu suggestion.

Let's reopen until follow up comments from #1059 are addressed.

@gaearon app is broken. When changing regex in default loader per last PR suggestion it captures the .html now. That sounds like more important than the rest.
Would you like a separate PR immediately?

Some guidance needed to complete PR comments:
In eslint config L49, should it not be [.js, .jsx] anyway?
Add .jsx to L52?
Do we need line 47 at all, or is specifying import/exensions good enough and we just remove this line?
Validation of default loader: As we could have loader regexes in test, include or exclude, I think validation that works now for most changes is more robust than trying to calculate the default matches. E.g. below naive validation for the default loader that's hard-coded to the current setting - it has false negatives but perhaps that's acceptable.
See proposed jest config - not an expert on jest, any advice for a good test?
const defaultExtensions = module.exports.module.loaders[0].exclude.slice(1);
const specificExtensions = module.exports.module.loaders.slice(1).map(
  loader => loader.test);

if (defaultExtensions.join('') !== specificExtensions.join('')) {
  throw new Error('Default loader inconsistent with other loaders.');
}

I think relying on the order of loaders to validate them is going to be very brittle. Then instead of breaking the loader config you'll break the validator.
If we think forgetting to add file types to the default file loader is going to be an issue, maybe we should just compose the loader config from separate parts like this:
var loaders = [
  {
    test: /\.(js|jsx)$/,
    loader: 'babel', ...
  },
  {
    test: /\.css$/,
    loader: ...
  },
  ...
];
var defaultLoader = {
  exclude: loaders.map((loader) => loader.test),
  loader: 'url',
};

// Then in the config:
  ...
  loaders: loaders.concat(defaultLoader),

Yes, it does add some indirection, but it's a tradeoff.

@json I was getting started with this approach but then realized this will break when someone adds include/exclude statements to existing or new loaders. In this case, chances are high that the default loader would break and would do so silently. I think the validator idea has the advantage that it serves as a pull linkage - yes it will fail on changes, but most likely failure will be verbose, which will remind the dev to update the loader and/or the validator.

Unless we take in account each test, include and exclude regex and validate that the rules don't have overlap with each other (which due to its complexity I'm not suggesting here, although it might be feasible as a separate tool) we can't protect people editing the config from all kinds of errors. We'll have to assume people who are editing the config by hand know what they're doing or at least can fix errors.
The best thing we can do is keep the config as easy to understand and simple as possible. A check at the end of the file that assumes the first loader is always the catch-all loader and has an exclude array with html as the first item and the file extensions from other loaders after that, in the correct order, is not simple or easy to understand. And it will also break for valid changes at which point you'll have to work around it.
I propose we either compose the catch-all rule from the others like I suggested above, or just have big warning comment that you must add new file extensions to the excludes.
Maybe @gaearon has something to say because he had the idea about validating the config in the first place. :)

If it's too hard don't validate. :-)

Eh - sorry @fson for calling you json above :-)) you can see my brain's loaded with loaders.
Pushed everything commented so far. Fine to leave it there - if you have any comments on the other points (eslint things I am not sure of) I'm happy to follow through.
Agree with lack of simplicity. But lets not auto-build a loader for the reasons you say, I think it would silently fail on next changes.
Jest - I'll leave the regex verification up to you in this case if you don't mind.
Thanks!

Fixed by #1059 & #1077.

Turns out our regex in the Jest moduleNameMapper config didn't work as we had thought, which caused issues when JS files with . in the module name were treated as file resources and stubbed (#1145, #1147).
As a stopgap measure, I reverted the Jest config back to the previous regex which whitelists non-JS/CSS extensions separately, but we still need to find a way to get the same behaviour as our Webpack configuration in Jest.
Maybe @cpojer can help us here? We're trying to create a Jest config that matches this Webpack config:
module: {
  loaders: [
    {
      exclude: [
        /\.html$/,
        /\.(js|jsx)$/,
        /\.css$/,
        /\.json$/
      ],
      loader: 'url',
      ...
    },
    {
      test: /\.(js|jsx)$/,
      include: paths.appSrc,
      loader: 'babel',
      ...
    },
    {
      test: /\.css$/,
      loader: 'style!css?importLoaders=1!postcss'
    },
    {
      test: /\.json$/,
      loader: 'json'
    }
  ]
},

Files with .js, .css and .json extensions are handled separately. Everything else is treated as a file – they should be stubbed in Jest.
The first attempt was a regex with a negative lookahead like this:
moduleNameMapper: {
  '^.+\\.(?!(js|jsx|css|json)$)[^\\.]+$': resolve('config/jest/FileStub.js'),
  '^.+\\.css$': resolve('config/jest/CSSStub.js')
}

However, this doesn't work because moduleNameMapper matches the module name, not the absolute file path like Webpack. Because JS files can be imported without specifying the extension, the module name doesn't necessarily end with .js. This caused false positives where imports like import assign from 'lodash.assign' or import a from '../a' were stubbed.
Is it even possible at the moment to replicate this Webpack config in Jest? I think being able to somehow match against the absolute file path would be necessary for that.

What @cpojer told me:

The idea is to use the new transform field we added in 17

You can run any transformer on any regex

Default is babel-jest for JS
But you can build a sync transformer for css

Thanks Dan for sharing my messages to you. Yes, the transform field is meant to be used for this. If you guys are building css-jest and scss-jest and all, I'm happy to support this officially in Jest – this was my long term plan so we can also have style information in JS, just like we do in react-native:
<View
  style={{
    color: 'green',
  }}
/>

etc.


Neat buttons but doesn't work.

I followed your config steps twice. IB designables aren't working at all. Didn't do anything more special than what your instructions show.

The real-time update to the IB element didn't work so I figured just run it.
The compiled app results with buttons that are not styled as they are in IB.

Best

Instantiating property in a vc + importing lib does nothing as well.


Tensorflow Layer Reshape not working for same size arrays

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
tf 2.11
Custom Code
Yes
OS Platform and Distribution
Windows 10 Pro
Mobile device
No response
Python version
3.8
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
11.8
GPU model and memory
No response
Current Behaviour?
Tensorflow Reshape layer was throwing size mismatch errors when trying to reshape an array to another of the same size.
Sometimes it was working, sometimes not. After testing found examples of Reshape not working for a target array of the exact same shape as input array.

This behaviour only seems to happen on windows and code works on linux

Standalone code to reproduce the issue
import tensorflow as tf

tensor = tf.keras.Input(shape=(512, 512, 512, 32))
out = tf.keras.layers.Reshape((512, 512, 512, 32))(tensor)

Relevant log output
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "d:\Miniconda3\envs\python\lib\site-packages\keras\utils\traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "d:\Miniconda3\envs\python\lib\site-packages\keras\layers\reshaping\reshape.py", line 118, in _fix_unknown_dimension
    raise ValueError(msg)
ValueError: Exception encountered when calling layer "reshape_1" (type Reshape).

total size of new array must be unchanged, input_shape = [512, 512, 512, 32], output_shape = [512, 512, 512, 32]

Call arguments received by layer "reshape_1" (type Reshape):
  • inputs=tf.Tensor(shape=(None, 512, 512, 512, 32), dtype=float32)

@dpm16
Please find the above implementation here gist.
Did you try this same on the Jupyter Notebook?

The error only happens on windows and works on linux. It does work on the Jupyter notebook but not an any Windows machine running it.

@dpm16
I was able to reproduce the issue on the windows. Please refer to the snapshot

This issue seems to be a keras related issue. Please post this issue on keras-team/keras repo.
To know more see;
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999.
Thank you!


[Stack]: Setting the gap property isn't working

Description
When changing the gap knob in storybook for the stack component, nothing is changing.
Component(s) impacted

https://web-components.carbondesignsystem.com/?path=/story/layout-stack--playground
Carbon for IBM.com version
v2.0.1
Severity
Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.
Package
@carbon/web-components
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

@annawen1 is this issue related to the Carbon for AI effort? If not, can you remove the area: AI label?

@mattrosno This is a component @lee-chase was using in the POC, so I think we probably expect teams to use it in tandem with the other react wrappers


Update whoopingcough

Description
Resolves # (If this PR is unrelated to a ticket, please erase this line)
Please include a summary of the change
Type of change
Please select one below (Please click check boxes AFTER submitting ticket)

[ ] Bug fix
[ ] New feature
[ ] New Documentation
[x] Other (please describe below)

How Has This Been Tested?
Please describe the tests you've added or any tests that already cover this change. Include relevant information, such as which operating system you tested on.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[ ] I have added debugging support to my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have added any new baselines to the repo
[ ] I have assigned reviewers (see VisIt's PR procedures for more information).

@brugger1
Is this ok? just an update to my workstation config file.


Add generic sizing recommendations to Best Practices setup pages

This page used to contain exact recommendations on the master node types to use for different clusters. Lots of internet resources are still referring to this page as a source of the info (this page as an example: https://learnk8s.io/kubernetes-node-size). But the recommended master node types are removed from here.
I'd really like to have this info here.
Thank you,

The text you're thinking of was:

On GCE/Google Kubernetes Engine, and AWS, kube-up automatically configures the proper VM size for your master depending on the number of nodes in your cluster. On other providers, you will need to configure it manually. For reference, the sizes we use on GCE are
1-5 nodes: n1-standard-1
6-10 nodes: n1-standard-2
11-100 nodes: n1-standard-4
101-250 nodes: n1-standard-8
251-500 nodes: n1-standard-16
more than 500 nodes: n1-standard-32
And the sizes we use on AWS are
1-5 nodes: m3.medium
6-10 nodes: m3.large
11-100 nodes: m3.xlarge
101-250 nodes: m3.2xlarge
251-500 nodes: c4.4xlarge
more than 500 nodes: c4.8xlarge

Those recommendations are:

no longer current
tied to specific, third party providers

If cloud providers want to publish their own recommendations, the Kubernetes project has no objection. We wouldn't reintroduce that list because it's difficult to cover the many cloud providers that Kubernetes can run on, and because it's out of line with our current content guide (which was one reason I proposed removing it).

/retitle Add generic sizing recommendations to Best Practices setup pages
/language en
/kind feature

@kubernetes/sig-scalability would anyone from the SIG be willing to triage this and maybe help move the work forward?

/assign @marseel
Note that Marcel is OOO this week, but he should be able to help with that once he is back.

We should update https://github.com/kubernetes/community/blob/master/sig-scalability/configs-and-limits/provider-configs.md and link it from there [though not in the current format...]
/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

As a contributor mainly to SIG Docs, I won't mark this as frozen. However, SIG Scalability folks: you are welcome to triage this as Accepted, and then also to freeze it.

Repeating https://github.com/kubernetes/website/issues/28068#issuecomment-856953198:

@kubernetes/sig-scalability would anyone from the SIG be willing to triage this and maybe help move the work forward?

/remove-lifecycle stale

/remove-lifecycle stale

We should update https://github.com/kubernetes/community/blob/master/sig-scalability/configs-and-limits/provider-configs.md and link it from there [though not in the current format...]
/remove-lifecycle stale

@wojtek-t Would this still be your recommendation as it stands today? If yes, we can open it up to contributors for edits.

/sig scalability

@wojtek-t Would this still be your recommendation as it stands today? If yes, we can open it up to contributors for edits.

Yeah - I think it's still a valid one.

Thank you so much for confirming!
@marseel would you still be interested in contributing?

/triage accepted
/priority backlog
/remove-lifecycle rotten
/lifecycle stale

@kubernetes/sig-scalability-leads : Please could you advise if anyone could help triage this PR and move this forward?


can't run calicoctl version successfully without a cluster

Expected Behavior

I expect calicoctl version to pass even if I have no cluster
Current Behavior

It fails
Possible Solution

I tried messing with KUBERNETES_MASTER and looked at the flags but nothing was useful
Steps to Reproduce (for bugs)

Have no cluster (or maybe no calico cni deployed)
calicoctl version
see exit code 1

Context

I run calicoctl version within a sandbox that has no-networking to make sure it was built correctly

What version are you using? Look like it works fine for me with the latest v3.23.3 build:
$ calicoctl version
Client Version:    v3.23.3
Git commit:        3a3559be1
Unable to detect installed Calico version

$ echo $?
0


Remove duplicate dictionary key/value pairs

(cherry picked from commit b3ddc2f)
There were a few instances of duplicate key/value pairs and this PR removes them.

Thanks, @znation !


Enable semantic release on main

What does this change?

enables semantic release on pushes to main

Why?

so we can use it

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update Erlang/OTP to 26.1

Contextually:

Update some dependencies to support OTP 26 (notably ecto, amqp and astarte_*)
Remove lager as it is not needed by rabbitmq_common anymore

Based, based on a number of PRs:

https://github.com/astarte-platform/astarte_rpc/pull/80
https://github.com/astarte-platform/astarte_core/pull/104
https://github.com/astarte-platform/astarte_data_access/pull/78

Also, https://github.com/astarte-platform/astarte_vmq_plugin/pull/84 is needed.


Correction to Windows build instructions

I finally managed to build using the Vagrant image on a Windows host, and there are two caveats that people need to be aware of:

When I did a git clone on this repository, I ended up getting the shell scripts with Windows-style line endings (\r\n).  I guess this may not happen for everyone (depends on how git was set up), but to be safe you should run dos2unix (assuming you have cygwin) on the scripts in the android folder prior to doing anything.

By default, the virtual machine is set up with a /vagrant folder which is synced/shared with the host machine.  The problem is that the Windows host (or at least Windows 7 in my case) doesn't seem to deal with very long path names that the chromium checkout procedure attempts to create.  So I ended up creating a folder in the VM (not synced with host) and building there.  i.e. after vagrant ssh, I did:

mkdir mybuild
cd mybuild
cp /vagrant/build.sh .
source ./build.sh
get_webrtc
build_apprtc

Additional note:

make sure you have ~ 24 GB of free space in the disk where the virtual machine will be created.  At least this is what I ended up using after building both Release and Debug targets.  You can open VirtualBox and configure it to create VMs in a drive with enough space, prior to starting this procedure.

@eguendelman can you test the new branch and see if it address your end-of-line issues? You should do a clean clone using the fix branch (git clone -b fix_windows_eol git@github.com:pristineio/webrtc-build-scripts.git).
I tested this partially on a Windows VM, and it seems to work

Okay, I've verified that I get the scripts with correct UNIX-style line endings on that branch.  Thanks for the fix.

@eguendelman thank you for testing my fix. I also added to the instructions information about the possible problems and your workaround.


Yarn error on docker

I'm trying to migrate from my old powerdns-admin on docker (not compose) and I run into an error with yarn:
===> DB management
---> Running DB Migration
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.env] No changes in schema detected.
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
===> Assets management
---> Running Yarn
yarn install v1.7.0
warning Skipping preferred cache folder "/var/www/.cache/yarn" because it is not writable.
warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-33".
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.22s.
Error: ENOENT: no such file or directory, open '/var/www/.yarnrc'

And it start-loop.
I have the working dir set to /powerdns-admin, /entrypoint.sh as entrypoint and empty command, I have the same env as .env plus FLASK_APP, any ideas on what did I missed ?

I have work-around that by doing:
usermod -d /powerdns-admin www-data
chown -R www-data:www-data /powerdns-admin

Right after cd /powerdns-admin in entrypoint.sh but that's probably not the best...

Docker stuff has been updated recently.


Add tags and freshness to stg_sources

Describe the feature
I'd like to be able to query data about source tags, and the freshness configuration of each source via the stg_sources model in the dbt Project Evaluator package.
Describe alternatives you've considered
Installing dbt-artifacts or elementary to be able to query source freshness configuration and source tags. We'd rather not introduce package bloat just to get at one field.
Additional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
We are using Snowflake.
Who will this benefit?
There are a number of different packages available that will auto-model metadata about the dbt project. We're trying to minimize overhead by installing a bunch of packages, and since the stg_sources model in the evaluator package is SO close to exactly what we need, it would be great if freshness and tags could be added to that model.
Are you interested in contributing this feature?

I would need a hand getting started on this if I were to contribute.

Hey @alexfetterman! definitely open to adding these fields! If you'd like to take a stab at a contribution, the steps look like

Adding the relevant fields here -- this is a model that generates 0 rows, and then gets values inserted in a post hook, so the goal is just to get the table schema determined.
Adding the logic to grab these fields from the source node in this macro -- these fields should be in the same order as the columns in the first step
Add these fields to int_all_graph_resources -- we generally try to bring everything into this table even if it's specific to a particular resource type
If you're feeling bold, you can add some freshness and some tags to the sources in the integration tests project and add a dbt test or two to prove we're extracting the data we expect!

let me know if a) you have any desire to tackle this, and if so b) if you need more guidance!

Hi @dave-connors-3  thank you! This is my first contribution to an external project -- hope this is close.
I had trouble following the integration tests suggestion, and instead attempted to install my forked version of the project on a branch of our dbt repo (using this method, referencing the github url and hash of commit). When I tried to build the dbt_evaluator_package models referencing the feature branch of the forked project, the stg_sources model did not build successfully. I got a pretty strange error:
  001003 (42000): SQL compilation error:
  syntax error line 9,773 at position 75 unexpected '.'.
  syntax error line 9,799 at position 75 unexpected '.'.
  syntax error line 9,826 at position 75 unexpected '.'.
  syntax error line 9,852 at position 75 unexpected '.'.

There's certainly not 10k lines of code in that file so I'm a little confused.
Any ideas? Seems like a simple thing to change but I'm struggling on how to actually test that it's working.

The draft PR is #447 linked above.


FTI plugin fails tests

Two FTI tests are failing on master. @ksiero could you have a look
Job #12506 failed for 028a8804d0384ec43f07a04a7faded3d916c2dfe:

The job fails with the following output:
fti_08_C: /builds/pdidev/pdi/plugins/fti/tests/fti_test_08.c:54: main: Assertion `test_size == sizeof(test)' failed.
fti_08_C: /builds/pdidev/pdi/plugins/fti/tests/fti_test_08.c:54: main: Assertion `test_size == sizeof(test)' failed.
fti_08_C: /builds/pdidev/pdi/plugins/fti/tests/fti_test_08.c:54: main: Assertion `test_size == sizeof(test)' failed.
fti_08_C: /builds/pdidev/pdi/plugins/fti/tests/fti_test_08.c:54: main: Assertion `test_size == sizeof(test)' failed.

For job #12507 the issue seems to be an incorrect installation in Docker and PDI does not find FTI
The issue of #12506 is a deeper one. Tests compile but they later fail...

created branch 168-job-failed-12506 to address this issue

The issue with the system version of FTI is a FTI bug, I am making a pull request

In GitLab by @ksiero on Oct 16, 2020, 13:13
mentioned in commit 0cc4d7b49cf1b65788261298ce44dfb73ea7a6ea


Suggestion: treat filetype *.jl as Julia, not Sawfish Window Manager's scripting language

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
The problem: Julia source files use *.jl extension. Vim, under /usr/share/vim/vim82/filetype.vim, assigns setf lisp for *.jl files among other lisp filetypes.
Problem with this is that Lisp tooling is abundant and heavyweight, and so unloading it cleanly after the filetype has changed is problematic. b:undo_ftplugin comes to rescue to an extent, but some subtle artifacts remain, including loading the auto-loaded code that should stay dormant. Here's my b:undo_ftplugin for lisp:
let b:undo_ftplugin = 'setlocal comments< define< formatoptions< iskeyword< lisp<'
            \ . '| mapclear <buffer>'

Describe the solution you'd like
Daring yet confident solution would be to detect *.jl as Julia. A sufficient compromise would be to remove the *.jl detection as lisp and let the users decide.
Additional context
Julia has been sponsored by NASA, DARPA, Mozilla, and others. It's a rather high-profile project, with Julia Computing, Inc. raising $4.7M in seed funding in June 2017.
Sawfish is a window manager configured in a dialect of Lisp, with 104 stars on Github and 33 contributors. It being first to use the extension certainly is worth considering, however this issue can be easily resolved without creating any discomfort for either side. It's been a source of problems in the past, and still remains a problem for Vim users who utilize both Lisp and Julia.

Julia support is not included in the distribution, thus recognizing *.jl as Julia isn't very useful, you need to add the runtime files anyway.
Writing Lisp file is not very common, it's fading away.  We can remove the detection of *.jl as Lisp.  it's easy enough to find another way to set the filetype for those few users who need it.


what is the "new functionality"?

what is the "new functionality" referred to at the end of the workshop?
Now, let's update your S3 hosted website and deploy the MythicalMysfits-Website stack:

cd ~/environment/workshop/cdk/
cdk deploy MythicalMysfits-Website
Refresh the Mythical Mysfits website in your browser to see the new functionality in action!

This concludes Module 4.

Proceed to Module 5

ok, it just seemed to take a while to update.

Glad it resolved itself!


How to link libc++_shared statically?

Hey, we're experiencing an issue with conflicting version of libc++_shared.so in a React Native app that depends on its own libc++_shared.so, and it's set as take first in the RN gradle configuration. Is there a way to statically link libc++_shared.a instead of libc++_shared.so? Any pointers would be much appreciated 🙏

I see a toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/aarch64-linux-android/libc++_static.a in the latest NDK 25 that I'm about to update to, but I've never used it.
Would keeping differently named libc++_shared.so libraries for each and then using patchelf, as in the doc, to link to the right one work, ie patch these Swift libraries to link against libc++_shared_25.so and rename the included libc++ library to that (you may need to change the soname too), while your React Native code can use the other version of libc++? Alternately, maybe you can put them in different directories and change the RPATHs to link to the different paths, ie Swift links against foo/libc++_shared.so with an RPATH of $ORIGIN/foo, while the RN code uses the top-level libc++.
I don't know if either of those approaches would work, as I've never faced Android dependency hell, but they may be easier than changing everything to statically linking libc++.

Closing since there's no response, feel free to let us know what you ended up trying.

We tried with patchelf --replace-needed but get an error: patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections. Could you elaborate on how the --set-rpath option would work?

Could you elaborate on how the --set-rpath option would work?

Check the rpath of the existing shared libraries with readelf -d, as shown in my doc, then prepend \$ORIGIN/foo to the existing rpath, ie patchelf --set-rpath \$ORIGIN/foo:\$ORIGIN libraries as shown there.

we're running into same patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections with --set-rpath on some (but not all) of the libraries.

more info
script
#! /bin/bash

archs=(
  "swift-5.6-android-aarch64-24-sdk"
  "swift-5.6-android-armv7-24-sdk"
  "swift-5.6-android-x86_64-24-sdk"
)

# check with `$ readelf -d lib*.so` in the /usr/lib directory
libsos=(
  "libandroid-spawn.so"
  "libicui18n.so"
  "libicuuc.so"
)

andsos=(
  "libswiftCore.so"
  "libswiftDispatch.so"
  "libswiftGlibc.so"
  "libswiftSwiftOnoneSupport.so"
  "libswift_Concurrency.so"
  "libswift_Differentiation.so"
  "libswift_MatchingEngine.so"
  "libswift_StringProcessing.so"
)

lib_path="usr/lib"
and_path="usr/lib/swift/android"

for arch in "${archs[@]}"
do
  echo "---------------------"
  echo "patching arch '$arch'..."

  # move to /libc++_shared_folder
  fold_name=libc++_shared_folder
  folder=$arch/$lib_path/$fold_name
  mkdir $folder
  mv $arch/$lib_path/libc++_shared.so $folder

  # set rpath for top lvl libs
  for so in "${libsos[@]}"
    do
      echo "setting rpath of '$so'..."
      target=$arch/$lib_path/$so
      if ! patchelf --set-rpath \$ORIGIN/$fold_name:\$ORIGIN $target
      then
        echo "failed to set rpath on $target"
        continue
      fi
  done

  # set rpath for androind libs
  for so in "${andsos[@]}"
  do
    echo "setting rpath of '$so'..."
    target=$arch/usr/lib/swift/android/$so
    if ! patchelf --set-rpath \$ORIGIN/$fold_name:\$ORIGIN $target
    then
      echo "failed to set rpath on $target"
      continue
    fi
  done
done

output
~/d/patched_libc++_shared_rpath ❱ ./fix_rpath.sh
---------------------
patching arch 'swift-5.6-android-aarch64-24-sdk'...
setting rpath of 'libandroid-spawn.so'...
setting rpath of 'libicui18n.so'...
setting rpath of 'libicuuc.so'...
setting rpath of 'libswiftCore.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswiftCore.so
setting rpath of 'libswiftDispatch.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswiftDispatch.so
setting rpath of 'libswiftGlibc.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswiftGlibc.so
setting rpath of 'libswiftSwiftOnoneSupport.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswiftSwiftOnoneSupport.so
setting rpath of 'libswift_Concurrency.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswift_Concurrency.so
setting rpath of 'libswift_Differentiation.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswift_Differentiation.so
setting rpath of 'libswift_MatchingEngine.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswift_MatchingEngine.so
setting rpath of 'libswift_StringProcessing.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-aarch64-24-sdk/usr/lib/swift/android/libswift_StringProcessing.so
---------------------
patching arch 'swift-5.6-android-armv7-24-sdk'...
setting rpath of 'libandroid-spawn.so'...
setting rpath of 'libicui18n.so'...
setting rpath of 'libicuuc.so'...
setting rpath of 'libswiftCore.so'...
setting rpath of 'libswiftDispatch.so'...
setting rpath of 'libswiftGlibc.so'...
setting rpath of 'libswiftSwiftOnoneSupport.so'...
setting rpath of 'libswift_Concurrency.so'...
setting rpath of 'libswift_Differentiation.so'...
setting rpath of 'libswift_MatchingEngine.so'...
setting rpath of 'libswift_StringProcessing.so'...
---------------------
patching arch 'swift-5.6-android-x86_64-24-sdk'...
setting rpath of 'libandroid-spawn.so'...
setting rpath of 'libicui18n.so'...
setting rpath of 'libicuuc.so'...
setting rpath of 'libswiftCore.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswiftCore.so
setting rpath of 'libswiftDispatch.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswiftDispatch.so
setting rpath of 'libswiftGlibc.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswiftGlibc.so
setting rpath of 'libswiftSwiftOnoneSupport.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswiftSwiftOnoneSupport.so
setting rpath of 'libswift_Concurrency.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswift_Concurrency.so
setting rpath of 'libswift_Differentiation.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswift_Differentiation.so
setting rpath of 'libswift_MatchingEngine.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswift_MatchingEngine.so
setting rpath of 'libswift_StringProcessing.so'...
patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections
failed to set rpath on swift-5.6-android-x86_64-24-sdk/usr/lib/swift/android/libswift_StringProcessing.so

we're running into same patchelf: cannot normalize PT_NOTE segment: non-contiguous SHT_NOTE sections with --set-rpath on some (but not all) of the libraries.

Could you try making those patchelf modifications on linux instead: one user reported similar issues running patchelf on macOS, that weren't there on linux?

That actually worked. I thought it might be the case, thx for the hint. We're testing the patch now.

okay, as you suggested, we were able to work around the issue by replacing the soname where needed to a new name. thank you for the prompt responses @buttaface, we appreciate your help and support


How to find specific ID of tile

Is there a way i can find the ID of a specific tile and then be able to repeatedly farm that tile?

You can use zone Index instead Id
gGame.m_State.m_Grid.m_Tiles
also zone index print in console:
Pirates Planet zone 83 (11, 6) progress: 0.1833868771791458 difficulty: 2

okay found the tile i wanted simple enough but how can i make the script go back to that tile instead of going to other random ones

for quick fix add
return zoneIndex;
after
const GetBestZone = function GetBestZone() {
in result you should get something like this:
const GetBestZone = function GetBestZone() {
    return 15;
    let bestZoneIdx;


WorldTime (Independent Publisher)

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.
Please note that we are experiencing a significant delay due to COVID delays, unanticipated team leaves, and high volume of connector submissions.

[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[x] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Hello @fordosa90, I hope you are doing well. I am following up with you to see how updating your artifacts are going?
Please let me know if you have any questions.
Thank you very much.

[[certify-connector]]

Hi @fordosa90 thank you for updating the artifacts. we approved the request. the certification process started for your connector. this process will take 5 to 6 weeks to complete.
Please let me know if you have any questions.
Thank you very much

@fordosa90 Congratulations! The deployment of your connector and documentation page is now complete, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program, Thanks.


(fix) Update to the latest rustc (4874ca36f 2015-01-23)

Replacing fmt::Show with fmt::Debug, fmt::String with fmt::Display.
Replacing str::StrExt::slice_from with &s[start..] notation.

Awesome! Thanks for doing this.


Add a daily build status dashbord to oncall

Fixes #3609

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: zackbutcher
Assign the PR to them by writing /assign @zackbutcher in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ldemailly sry about that, fixed

@cmluciano: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
cd1f64fcccec5820c51553b667230f57e049df9a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


hi community, when to port to flink1.14?

hi @godfreyhe

hi @godfreyhe,I have the same question

any plan to support flink1.15? @godfreyhe

any plan to support flink1.15? @godfreyhe


feat: resetAllStores helper for resetting all previously injects stores

For now, there is no possibility to reset all stores at once that were previously injected and used in the app. This PR introduces a new helper that allows resetting all the stores.

what is the use case? Why should this be in core?
IMO this kind of global helper should not be exposed in core because we don't want to encourage people to use the default $reset() behavior too much, it's more for debugging purposes. Resetting ALL stores looks more like a dangerous pattern as usually, only some stores are being reset at different moments in your application lifecycle (e.g. a store used for a form that spans over multiple pages)

As well as $reset that is available for the single store instance, there should be also a way to reset all stores at once.
Use case description: the user logged in to the application, visited some pages, and performed some actions and as a result, some pinia stores have now data saved in the state. The user logs out and the stores still contain some data. Another user (that may not have an access to some pieces of data) logs in with other credentials and can see the previously saved data in many stores. Of course, it can be fixed by manually resetting each store, but why if we can reset all of them using one function call?
If you consider it to be a DANGEROUS pattern, can we just mark it as not recommended and describe the consequences?

The user logs out and the stores still contain some data. Another user (that may not have an access to some pieces of data) logs in with other credentials and can see the previously saved data in many stores. Of course, it can be fixed by manually resetting each store, but why if we can reset all of them using one function call after logging out?

That is an app-specific design. Not all apps are built that way and even in that scenario resetting is completely overkill. It's also not explicit in its name. In your example, the logout() action should take care of all of that

The user logs out and the stores still contain some data. Another user (that may not have an access to some pieces of data) logs in with other credentials and can see the previously saved data in many stores. Of course, it can be fixed by manually resetting each store, but why if we can reset all of them using one function call after logging out?

That is an app-specific design. Not all apps are built that way and even in that scenario resetting is completely overkill. It's also not explicit in its name. In your example, the logout() action should take care of all of that

I got your point. Could you please add some technical details, why is that DANGEROUS or overkill?

Also, could you propose a better way to have all stores reset?

Keeping this exact same code in userland is totally fine!
Thanks for the PR! I'm closing this as I think it's better to keep it in userland for those few people who might need it.
dangerous because overkill because it resets every store instead of the ones that need it


TAJO-1740: Update Partition Table document

Currently, Tajo doesn't provide enough informations about partition table. Thus, we need to add more informations to following documentation.
http://tajo.apache.org/docs/current/partitioning/column_partitioning.html

Hi, @blrunner .
I reviewed your writing documents and left some inline comments.
Please check them out.

Hi @eminency
Thank you for your detailed review.
Honestly, I've changed existing contents too much. So, I'll make new PR to keep existing ones. When making new PR, I'll must reference your feedback.

I recommend you to keep a single page for column partition. Each content is too short. Later, it may be hard to see all contents at once after we add new partition type.

I saw new PR. Please ignore the last comment.
https://github.com/apache/tajo/pull/728


M05-LAB11 and M07-LAB16 Fix eShopOnWeb repo links

Contact Details
No response
What happened?
Description of issue: Update links to point to the new eShopOnWeb repository.
Lab
Other
Relevant screenshots
No response
Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

closing as it was merged (for some reason linked issue did not work)


Enhancement: handling rules as a chord diagram

When displaying the rules (i.e. implying support for direction), it is possible to get rules that have different directions but based on the same categories. E.g.:
Camping equipment -> Outdoor protection with confidence 0.31
Outdoor protection -> Camping equipment with confidence 0.6
Brunel's cord diagram will display either first one or the second one depending on the sorting order in the data set. Some approach is needed to visualize the different associations, but related to the same categories.

Yes. Actually, I think I will classify this as a defect. The chord chart is currently aggregating all "similar" chords based only on the positional fields. I think this is an error and it should only aggregate if explicitly requested to. In particular the following chart should have arc for each state, and yet they are aggregated, showing both wrong colors and tooltips:
data('sample:US States.csv') x(region) y(boys_name) chord color(state) tooltip(#all)

... and this is a little trickier, since we are currently using the D3 chord diagram as a base, and it explicitly won't handle this case. Which seems ... wrong. I will look at making our own version to handle this.

I have candidate code that fixes this; will be testing and checking in soon

Checked in new chord diagram


Shouldn't we skip ApiClient init if the adapter is not using it?

Hi there :wave:
First of all, thank you for this awesome library! :smiley:
I'm trying to use it in dev and test environments where I don't need the ApiClient. But it seems that I ways need to declare Hackney (or Finch) as dependencies because the ApiClient needs it, and the ApiClient is being initialized at application boot.
So my question is if we can avoid the init of ApiClient if our configured adapter don't need it. I'm not sure how this could be done, but I imagined that it could be the Adapter's responsibility to initialize its dependencies. What do you think?

I guess we should add a Noop API Client that simply OK on init. Do you want to add one?

@princemaple thanks for the quick response! I can do that. :+1:
The idea is to use this Noop as the default API Client instead of Hackney?

It'd be a breaking change, so not really. We'd document it that if absolutely no hackney exists and init is causing trouble, config to use Noop API Client.

Got it. I managed to get this working by setting config :swoosh, :api_client, false. Maybe just document this instead of adding a new Noop module is enough. WDYT?


[ignore for now] fix: tag-list: initial work to fix flicker

The problem I am seeing is that when d2l-filter-tags is used in Nova, which wraps filter-tags in a flex box in order to right align, we need to remove the width: 100% in order for the flex to actually work, but then there is flicker caused by continuous re-triggering of the ResizeObserver when a certain number of filters are hit which could be grouped into the +X more hidden group.
This updates tag-list to use the parentNode for the ResizeObserver or the wrapping component's parentNode. The issue seems to be basically when the parent is a non-block element that doesn't set the width at 100%.
I modified the filter-tags demo in order to show the problem.
To do:

[x] ensure visual diffs pass or change in an expected way
[ ] test with user-profile-card-tag-list-item (including consistent-eval usage)
[ ] test Daylight tag list and filter tags examples

Closing in favour of alternative PR


How to evaluate a pretrained model

Hi, thanks for your great work.
Could you give a specific command to evaluate the performance of a pre-trained model, e.g., the provided pre-trained model in the repo?
Thanks.

Hi! Please follow README. For evaluation, you just need to set --eval and --finetune.

@Andy1621 Hi, I have tried this setting by using the follow command:
python run_class_finetuning.py \
        --eval \
        --finetune path/videomamba_t16_k400_f32_res224.pth \
        --model videomamba_tiny \
         --other_params

where videomamba_t16_k400_f32_res224.pth is the model you provide in your repo.
However, I got the error like:
Auto resume checkpoint: exp/k400/videomamba_tiny/videomamba_tiny_f32_res224/checkpoint-best.pth
Traceback (most recent call last):
  File "/root/paddlejob/workspace/env_run/output/xiaohu/VideoMamba/videomamba/video_sm/run_class_finetuning.py", line 712, in <module>
    main(opts, ds_init)
  File "/root/paddlejob/workspace/env_run/output/xiaohu/VideoMamba/videomamba/video_sm/run_class_finetuning.py", line 597, in main
    utils.auto_load_model(
  File "/root/paddlejob/workspace/env_run/output/xiaohu/VideoMamba/videomamba/video_sm/utils.py", line 645, in auto_load_model
    checkpoint = torch.load(args.resume, map_location='cpu')
  File "/root/paddlejob/workspace/env_run/lib_all/anaconda3/envs/count/lib/python3.9/site-packages/torch/serialization.py", line 699, in load
    with _open_file_like(f, 'rb') as opened_file:
  File "/root/paddlejob/workspace/env_run/lib_all/anaconda3/envs/count/lib/python3.9/site-packages/torch/serialization.py", line 230, in _open_file_like
    return _open_file(name_or_buffer, mode)
  File "/root/paddlejob/workspace/env_run/lib_all/anaconda3/envs/count/lib/python3.9/site-packages/torch/serialization.py", line 211, in __init__
    super(_open_file, self).__init__(open(name, mode))
FileNotFoundError: [Errno 2] No such file or directory: 'exp/k400/videomamba_tiny/videomamba_tiny_f32_res224/checkpoint-best.pth'

Even though I tried to set --no_auto_resume, the error is still there.

Hi! You can remove --test_best which will load the models automatically~

Thanks for your response. Everything works fine now.