Creating a ListResultPage struct as part of Unit Tests issue

Feature Request
I'm trying to create a ListResultPage struct with some test data which I aim to use in a mocked subscriptions list method https://github.com/Azure/azure-sdk-for-go/blob/master/services/preview/subscription/mgmt/2018-03-01-preview/subscription/subscriptions.go#L118.
The following is an initial attempt but when I try to call the Vaules() method on the ListResultPage struct I get an empty list. I cannot seem to find any tests in these packages or indeed any samples on the web on how to construct this ListResult and ListResultPage.
Any help would be much appreciated?
`
func (mock *MockedSubscriptionClient) List(ctx context.Context) (result subscription.ListResultPage, err error) {
id := "1234"
subid := "1234"
displayName := "test"
lr := subscription.ListResult{autorest.Response{}, &[]subscription.Model{{ID: &id, SubscriptionID: &subid, DisplayName: &displayName},{ID: &id, SubscriptionID: &subid, DisplayName: &displayName},}, nil}
a := func(context.Context, subscription.ListResult)  (subscription.ListResult, error) {
	return lr, nil
}
return subscription.NewListResultPage(a), nil

}
`
Do you have any tests for this code, which would help also?
Thanks,
Adrian

lrp := subscription.NewListResultPage(a)
lrp.Next() <- This was required
return lrp


Bump ubuntu-console to 16.04, add man

Bump ubuntu-console to 16.04, add man
Also, minor image cleanups (use cached layers to build faster).

Why man?


[Feature]: Ability to customize the durability warning

As of now (2.6.3) the durability warning comes up when the item is below 8% durability.
This is, imo, too low.
It should be customizable, since some armors have a low durability in the first place.
E.g. for a Leather Helmet, that means the warning comes up when there's only 4 uses left, which is often too late.
For the default settings, I'd orient myself along vanillas durability bar, which displays its last sliver of red when the durability is below roughly 11.5%.
(For reference, a leather helmet would have 6 uses left. Still not a lot, but better.)
Additionally there should be a bottom absolute value, (e.g. a default of 16, ideally also customizable) for exactly those low durability items.
[Maybe one could also add an even stronger warning, when the durability bar turns completely black (which is below roughly 3.85%)
(15 uses for Netherite Helmet; 22 uses for Netherite Chestplate)
But I am not sure about this idea.]

Has this project been abandoned?

it most likely will be.

It's little complicate to implement and make great UI 🤔 and I don't have much time for make new features and porting it to all versions

I mean, it doesn't have to be a great UI. A simple vanilla style slider/textfield to enter a value would suffice.
Or just being able to edit a value in the config would already be enough imo


D410 not enforced

Code to reproduce:

Running ruff v 0.0.275:

D400 is well detected, proving that ruff indeed checked the file.
However D410 no-blank-line-after-section goes undetected (there should be a blank line before the Returns section.
This is an issue when trying to use pydoclint alongside ruff (to replace the annoyingly slow flake8 - darglint combo) as the error messages of pydoclint become unclear when this happens.
Here is the content of my pyproject.toml file:
[tool.ruff]
line-length = 120
select = ["D", "E", "F", "I", "W"]

ignore = [ # Set of rules tested on mts-api-python
    "D102", # Missing docstring in public method
    "D107", # Missing docstring in __init__
    "D203", # 1 blank line required before class docstring, conflicts with D211 no blank line before class docstring
    "D205", # 1 blank line required between summary line and description, very strict
    "D212", "D213", # Summary should start at the first or second line, both are ignored by default
    "D404", # First word of the docstring should not be "This"
]

[tool.ruff.per-file-ignores]
"__init__.py" = ["D104"] # ignore no docstrings in __init__.py
"tests/*" = ["D"] # ignore all docstrings related linting in tests
"*.ipynb" = ["D"] # ignore all docstrings related linting in notebooks

Looks like a bug, but need to check whether pydocstyle flags this.

pydocstyle doesn't catch this either. I think part of the problem is that we're not recognizing it as two separate sections.

Fixed in the next release, thanks.


Vendor boringtun library into this repository

For the actual wireguard logic, we depend on https://github.com/cloudflare/boringtun.
Unfortunately, the repository isn't very well maintained. PRs and issues opened long ago don't receive any attention, see https://github.com/cloudflare/boringtun/issues/391 for example.
snownet is almost entirely sans-IO except for boringtun which calls Instant::now in a couple of places. This makes our unit-tests that simulate time advancing not as effective as they could be. In addition, due to the low maintenance of boringtun, it doesn't receive any dependency updates (see https://github.com/cloudflare/boringtun/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aopen+author%3Aapp%2Fdependabot for open dependabot PRs).
My proposal is to:

Vendor the boringtun library into this repository
Strip it off everything that we don't use, like the boringtun-cli
Refactor the interface to how we think sans-IO should be done
Once the API is stable, put it in a separate repository

Once the API is stable, put it in a separate repository

The reason I put this there is because it could be nice to then post this to HN and / or the boringtun issue tracker and thus attract more attention to the our GitHub org :)
There are plenty of users that would like a more actively maintained WG library: https://github.com/cloudflare/boringtun/issues/407


Skip models that don't have table

When I ran bin/rails orthoses:rails --trace on a Rails app, the following error was raised. It seems orthoses-rails is trying to generate RBS for ActionText::RichText the corresponding table of which does not exist. I think we better skip in that case.
/work/web$ bin/rails orthoses:rails --trace
** Invoke orthoses:rails (first_time)
** Execute orthoses:rails
W, [2024-10-22T21:41:55.025094 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:normalize_env in {:methods=>[:normalize_env], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.082050 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:caching? in {:methods=>[:caching?], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.158310 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:queue_adapter in {:methods=>[:queue_adapter], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.474829 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:model_name in {:methods=>[:model_name], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.477097 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:model_name in {:methods=>[:model_name], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.541078 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:destroy_association_async_job in {:methods=>[:destroy_association_async_job], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.544203 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:type_for_attribute in {:methods=>[:type_for_attribute, :column_for_attribute], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.548555 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:column_for_attribute in {:methods=>[:type_for_attribute, :column_for_attribute], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.557334 #566112]  WARN -- : [ActiveSupport::Delegation] Ignore since missing type for Class#:model_name in {:methods=>[:model_name], :to=>:class, :prefix=>nil, :allow_nil=>nil, :private=>nil}
W, [2024-10-22T21:41:55.725730 #566112]  WARN -- : Could not find table 'action_text_rich_texts'
W, [2024-10-22T21:41:55.726719 #566112]  WARN -- : Could not find table 'action_text_rich_texts'
W, [2024-10-22T21:41:55.728560 #566112]  WARN -- : Could not find table 'active_storage_variant_records'
W, [2024-10-22T21:41:55.729649 #566112]  WARN -- : Could not find table 'active_storage_attachments'
W, [2024-10-22T21:41:55.731315 #566112]  WARN -- : Could not find table 'active_storage_blobs'
W, [2024-10-22T21:41:55.732670 #566112]  WARN -- : Could not find table 'action_mailbox_inbound_emails'
bin/rails aborted!
ActiveRecord::StatementInvalid: Could not find table 'action_text_rich_texts' (ActiveRecord::StatementInvalid)
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/sqlite3_adapter.rb:476:in `table_structure'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/abstract/schema_statements.rb:109:in `columns'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:345:in `block (2 levels) in columns'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:395:in `with_connection'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:344:in `block in columns'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:343:in `fetch'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:343:in `columns'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:354:in `block in columns_hash'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:353:in `fetch'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:353:in `columns_hash'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:54:in `columns_hash'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/connection_adapters/schema_cache.rb:198:in `columns_hash'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/model_schema.rb:594:in `load_schema!'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/counter_cache.rb:187:in `load_schema!'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/encryption/encryptable_record.rb:127:in `load_schema!'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/model_schema.rb:541:in `block in load_schema'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/model_schema.rb:538:in `synchronize'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/model_schema.rb:538:in `load_schema'
/usr/local/bundle/gems/activerecord-7.2.1/lib/active_record/model_schema.rb:429:in `columns_hash'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/persistence.rb:16:in `block (2 levels) in call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/persistence.rb:12:in `each'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/persistence.rb:12:in `block in call'
<internal:kernel>:90:in `tap'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/persistence.rb:11:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/has_one.rb:11:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/has_many.rb:11:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/generated_attribute_methods.rb:33:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/enum.rb:17:in `block in call'
<internal:trace_point>:261:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:50:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:74:in `trace_instance_method'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:58:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/call_tracer/lazy.rb:30:in `trace'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/enum.rb:16:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/delegated_type.rb:17:in `block in call'
<internal:trace_point>:261:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:50:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:74:in `trace_instance_method'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:58:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/call_tracer/lazy.rb:30:in `trace'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/delegated_type.rb:16:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_record/belongs_to.rb:11:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_model/has_secure_password.rb:19:in `block in call'
<internal:trace_point>:261:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:50:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:74:in `trace_instance_method'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:58:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/call_tracer/lazy.rb:30:in `trace'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_model/has_secure_password.rb:18:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_model/attributes.rb:31:in `block in call'
<internal:trace_point>:261:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:50:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:74:in `trace_instance_method'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/lazy_trace_point.rb:58:in `enable'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/call_tracer/lazy.rb:30:in `trace'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/active_model/attributes.rb:30:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/action_mailer/base.rb:11:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:57:in `call'
/usr/local/bundle/bundler/gems/orthoses-rails-0fde7870ae3e/lib/orthoses/rails/application.rb:47:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/missing_name.rb:10:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/outputable/avoid_recursive_ancestor_error.rb:13:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/outputable/constantizable_filter.rb:13:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/outputable/uniq_content_body.rb:13:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/create_file_by_name.rb:45:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/outputable.rb:22:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:23:in `call'
/usr/local/bundle/bundler/gems/orthoses-492cfc1772d8/lib/orthoses/builder.rb:57:in `call'
/work/web/lib/tasks/orthoses/rails.rake:36:in `block (2 levels) in <main>'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:281:in `block in execute'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:281:in `each'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:281:in `execute'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:199:in `synchronize'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/task.rb:188:in `invoke'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:188:in `invoke_task'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:138:in `block (2 levels) in top_level'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:138:in `each'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:138:in `block in top_level'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:147:in `run_with_threads'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:132:in `top_level'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/commands/rake/rake_command.rb:27:in `block (2 levels) in perform'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/application.rb:214:in `standard_exception_handling'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/commands/rake/rake_command.rb:27:in `block in perform'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/commands/rake/rake_command.rb:44:in `block in with_rake'
/usr/local/bundle/gems/rake-13.2.1/lib/rake/rake_module.rb:59:in `with_application'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/commands/rake/rake_command.rb:41:in `with_rake'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/commands/rake/rake_command.rb:20:in `perform'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/command.rb:156:in `invoke_rake'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/command.rb:73:in `block in invoke'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/command.rb:149:in `with_argv'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/command.rb:69:in `invoke'
/usr/local/bundle/gems/railties-7.2.1/lib/rails/commands.rb:18:in `<main>'
<internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
<internal:/usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
/usr/local/bundle/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:4:in `<main>'
Tasks: TOP => orthoses:rails

@hibariya  Thank you for reporting.
I will fix the problem.
As a temporary solution, you can use Orthoses::Filter to remove any model from the RBS generation target.
use Orthoses::Filter do |name, _content|
  name != "ActionText::RichText"
end

What a surprise!
There was already a patch. Thank you!

Failure of CI appears to be an existing problem. I will try to fix it.

v1.7.0 has been released!


Updating package names for rp sdks

Updating RP sdk package names and namespaces
Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify - Updating package name ad namespace for rp of agrifood.

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. ASAP
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. June
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[x] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@ArcturusZhang @msyyc , can you please review the package name change?

Removed WaitForARMFeedback since the pr does not require ARM review.

The name change is expected for python


Scenario: Improve the local database development experience

We have several issues that need to be resolved for this end to end to come together nicely (and to reduce the friction)

[x] - https://github.com/dotnet/aspire/issues/398
[ ] - https://github.com/dotnet/aspire/issues/837

[x] - https://github.com/dotnet/aspire/issues/1437

[ ] - https://github.com/dotnet/aspire/issues/1199
[ ] - https://github.com/dotnet/aspire/issues/923
[x] - https://github.com/dotnet/aspire/issues/740
[ ] - https://github.com/dotnet/aspire/issues/1151
[x] - https://github.com/dotnet/aspire/issues/1936
[x] - https://github.com/dotnet/aspire/issues/1920
[ ] - https://github.com/dotnet/aspire/issues/1023 - Slowness booting up SQL on MacOS
[x] https://github.com/dotnet/aspire/issues/1132

This sample shows the state of the art today:

https://github.com/dotnet/aspire-samples/tree/main/samples/DatabaseContainers

Big issues that have been themes:

Calling AddDatabase on our database server types, should create the database at dev time (with an opt out).
We have to come up with guidance on how people run EF migrations when using aspire
We should make it easy to use a persistent volume (and persistent container?) when working with a database locally
We should make it easier to use database tools with databases orchestrated by aspire (today we generate random passwords)

Moved to P4

Good day @davidfowl and @JamesNK. I started a proof of concept for some new API changes at https://github.com/dotnet/aspire/issues/2090. Would greatly appreciate your thoughts. Thank you!

Moving this to the backlog,

Closing this tracking issue


Add SimpleIdentifier definition to avoid dependency with the SimpleIdentifier extension

At present, the Data Review Tool doesn't apply dependencies. (And, similarly, neither does the Extension Registry Python Package.)
I don't know if this is by design or not (e.g. following dependency chains is annoying for applications, so maybe we just want a single level of dependencies).
In any case, publishers who are using the master branch of the lots extension would now see an error in the Data Review Tool.
The simplest option is to copy the SimpleIdentifier definition. When the lots extension transitions to OCDS 1.2 (if it isn't merged into OCDS itself), we can remove this definition, as it is already in OCDS itself.


[bug] Fix gitbhub workflow Run Cargo linters / cargo-lint errors

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

Bugfix

What is the current behavior?

In github workflow Run Cargo linters / cargo-lint reports errors.
Resolves: #NA
What is the new behavior?

Pass Run Cargo linters / cargo-lint test
Does this introduce a breaking change?

Other information

Any idea why foundry tests are failing?


feat(progress-bar): add determinate progress-bar

Added a determinate progress bar style using the built-in<progress> tag and made sure it was cross-browser compatible. Unfortunately the original indeterminate progress bar isn't be supported in Firefox with the <progress> tag, so old method is still prefered using <div>. No breaking changes.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Looking for a chair for upcoming performance meetings

Hi everybody,
Due to personal reasons & developments, I'm having hard time chairing the performance meetings. Currently, I'm the only person who has access to Youtube and Zoom, that regularly attends the meetings.
Therefore, I'd like to publicly ask if there is a Node.js collaborator who'd like to chair the upcoming performance meetings?
Ideally, this person will get access to Zoom & Youtube accounts of Node.js (through GitHub.com/nodejs/admin) and start & live-stream meetings, and take meeting notes.
PS: We could also potentially explore to have a co-chair in case the new chair is unavailable in the future.
cc @nodejs/performance @nodejs/tsc

I nominate myself.
I also nominate @H4ad and @rluvaton

I usually have a regularly scheduled meeting on my work at the same time as the performance team meeting, so even if I want to be the co-chair I don't know if I can join the meetings.

I served as a co-chair for the performance meetings in the past, but unfortunately, the current time slot doesn't align well with my schedule. However, I am more than happy to help onboarding new co-chair(s) and explain all the details regarding the zoom settings and streaming details 😄

Seems to be a universal experience that the time slot is not great. Same sentiment here. 🙈

The same applies to me. I'm wondering if we could integrate the nodejs/diagnostics with nodejs/performance meetings.
Both meetings don't fit in my calendar, but we could find a better time and host both topics.

@RafaelGSS I liked the idea, currently I don't think the topics for the performance will take the whole hour, if we join both topics we maybe can use the whole time of the meeting and cover all the topics with more people.

Makes sense to me, especially given most diag wg sessions have mainly been about async_hooks perf for awhile now. 😅


Vim runs Sniffer running multiple times

I'm using 0.3.5 and I find that when I save a single file my tests get run 2 or 3 times.
Any pointers for diagnosing this issue?
I'm using Ubuntu Linux, my sniffer instance is running inside a docker container, I'm editing the file (mounted locally on my host) with vim.

One of our developers is using PyCharm (with the same docker setup) and when he saves the file it only runs the tests once. So it looks like this might be being caused by vim.

Hey @andrewmichaelsmith,
Is your vim creating temporary files in the same directory? Sniffer might be picking those temporary files as changes to cause it to re-run the tests.
If you pass the --debug flag you can see which files cause sniffer to rerun the tests:
$ sniffer --debug
Did not find 'scent.py', running nose:
...
----------------------------------------------------------------------
Ran 3 tests in 0.009s

OK
In good standing
callback - changed  /Users/jeff/workspace/sniffer/sniffer/tests/test_api.py

Hi @jeffh
I have vim's swap files being created in /tmp/ so (assuming my understanding that sniffer is only looking in my cwd is correct) I think that rules those out.
Didn't realise there was a debug flag, I've experimented with that (grepping for "event" or "callback") and I get the following:
(All of this call backs come from me doing a single save of a single file in vim)
event: deleted /vol/app/tests/functional_tests.py
callback - deleted  /vol/app/tests/functional_tests.py
event: created /vol/app/tests/functional_tests.py
callback - created  /vol/app/tests/functional_tests.py
event: modified /vol/app/tests/functional_tests.py
callback - changed  /vol/app/tests/functional_tests.py

What's unusual is that when the tests run after this "deleted" event, it's still running the tests in functional_tests.py (I made one fail and it shows up for that run and all subsequent runs). Suggesting that file hasn't actually been deleted.
I'm a bit stumped to be honest!

Not sure if this helps but I did a quick test using inotifywait, I had a file open in vim and saved it. These are the actions recorded (for a simple :w):
./ CREATE 4913
./ OPEN 4913
./ ATTRIB 4913
./ CLOSE_WRITE,CLOSE 4913
./ DELETE 4913
./ MOVED_FROM a.py
./ CREATE a.py
./ OPEN a.py
./ MODIFY a.py
./ CLOSE_WRITE,CLOSE a.py
./ ATTRIB a.py

I think it might be a race condition. Sniffer tries to run per event, but FS events occur asynchronously, so by the time it runs the test, the files were already fully saved.
I don't have a linux box to test this on, but that's my basic understanding of the issue.

I think this issue is because of vim's saving of files using swap files - it ends up saving, creating and moving a file on save.
I have (finally!) managed to work around this issue in vim using:
set noswapfile
In my vimrc


Serverside blips are completely broken

I've tested these 2 and both don't work:

RadiusBlip -> Simply doesnt show up at all

Player blips (AltAsync.CreateBlip( BlipType.Ped, player ); // attach to player -> this crashes the server as soon as it's created(I tried on player connect):

   at AltV.Net.Server.CreateBlip(AltV.Net.Elements.Entities.IPlayer, Byte, AltV.Net.Elements.Entities.IEntity)
   at AltV.Net.Alt.CreateBlip(AltV.Net.Elements.Entities.BlipType, AltV.Net.Elements.Entities.IEntity)
   at AltV.Net.Async.AltAsync+<>c__DisplayClass11_0.<CreateBlip>b__0()
   at AltV.Net.Async.ActionTickScheduler+ActionContainer4`1[[System.__Canon, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Run()
   at AltV.Net.Async.ActionTickScheduler.Tick()
   at AltV.Net.Async.AsyncResource.OnTick()
   at AltV.Net.ModuleWrapper.OnTick()```

client.Blip = await AltAsync.CreateBlip( AltV.Net.Elements.Entities.BlipType.Ped, client );

It doesnt seem to crash on this though (untested if it actually shows anything ingame):
await AltAsync.CreateBlip( AltV.Net.Elements.Entities.BlipType.Radius, Position );

People on altV discord mentioned that server-side blips work fine on JS, so must be a C# thing, hence the issue here and not in altV issues board.

Same issue here

Test attached blips on 9.0.9-dev61 c# module version and nuget again.


turtlebot3_teleop does not repeat messages on Windows

ISSUE TEMPLATE ver. 0.4.0

Which TurtleBot3 platform do you use?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which ROS is working with TurtleBot3?

[ ] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[X] ROS 1 Noetic Ninjemys
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[ ] ROS 2 Foxy Fitzroy
[ ] etc (Please specify your ROS Version here)

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Intel Joule 570x
[X] Raspberry Pi 3B+
[ ] Raspberry Pi 4
[ ] etc (Please specify your SBC here)

Which OS you installed on SBC?

[ ] Raspbian distributed by ROBOTIS
[ ] Ubuntu MATE (16.04/18.04/20.04)
[X] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)

Which OS you installed on Remote PC?

[ ] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Ubuntu 20.04 LTS (Focal Fossa)
[X] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: Not Relevant
Firmware version: Not relecant

Specify the commands or instructions to reproduce the issue.

On the Windows 10 PC, open a ROS terminal and run roslaunch turtlebot3_teleop turtlebot3_teleop_key.launch
On the Windows 10 PC, open a new ROS terminal and run rostopic echo /cmd_vel

Copy and Paste the error messages on terminal.

No error message

Please describe the issue in detail.

When I press, for example, w to send a linear velocity command, a corresponding twist message is echoed in the echo terminal only once. The message is not repeated. As a consequence, the TurtleBot moves a little and stops.
On a Linux machine, the same teleop node repeats the twist message every 0.1s, so the robot moves as it should.

Hello @rlkamalapurkar
Thanks for asking and sorry for the late reply
e-manual was tested on Intel NUC with windows installed instead of raspberry pi (SBC).
This SBC Setup section for Windows is tested with Intel Up² or Intel NUC on TurtleBot3.
Unfortunately, there is no test support in Remote PC windows & SBC raspberry pi environment,
so it is difficult to accurately support.
Therefore, I am attaching a good link for your reference.
Please check your windows firewall
In addition, If you contact the ROS Forum below, you will receive a quick and accurate answer.
ROS Forum
Thanks for your understanding.

Thanks for the response. The SBC is irrelevant, though, you do not even need a TurtleBot3 to reproduce this issue.
The turtlebot3_teleop package, when installed on Windows 10, does not repeat messages. On Linux, it does. Any ideas that will help me understand why would be appreciated!

@ashekim I found the problem, but I am not sure how to fix it. The Windows implementation of the getKey function in the python code is this:
    if os.name == 'nt':
        if sys.version_info[0] >= 3:
            return msvcrt.getch().decode()
        else:
            return msvcrt.getch()

The problem is that getch() is blocking. So, unless a key is pressed on the keyboard, the execution gets stuck inside getKey and the while loop on line 144 only publishes once per keypress.
The Linux implementation includes a 0.1 second timeout, the windows implementation does not. I tried
    if os.name == 'nt':
        timeout = 0.1
        startTime = time.time()
        while(1):
            if msvcrt.kbhit():
                print("""keypress""")
                if sys.version_info[0] >= 3:
                    return msvcrt.getch().decode()
                else:
                    return msvcrt.getch()
            elif time.time() - startTime > timeout:
                return ''

but unfortunately, for some reason, msvcrt.kbhit() is unable to read Ctrl key. Any ideas on how a timeout for getch() can be added to the Windows implementation?

Hi @rlkamalapurkar.
Thank you for your contribution.
Your PR will be tested and merged into the develop branch.
Once again, thank you for your help and supports.
Have a good day! :)


a bug in Save-AzureVMImage help topic

SYNOPSIS
    Captures and saves the image of a running Windows Azure virtual machine.
DESCRIPTION
    The Save-AzureVMImage cmdlet makes a running virtual machine available as an image for reuse.

It should be a stopped virtual machine.

Old issue. Closing issue.


Possible hash collision of OVS cookies

The current solution uses md5 checksum of the VTEP (IP address of the destination node) to calculate the cookie assigned to the corresponding flow rules. The md5 method can result in hash collisions because only first 8 bytes are used.
Result of hash collisions will be apparent in deletion of nodes (deleting one node may result in deletion of rules of another node, rendering that subnet unreachable).
Need to fix this such that the cookie is always unique.

Fixed with #89


Feed update bug

HI everybody,
I encountered a rather strange bug with miniflux. In particular I cannot see the latest item ("Highlights der Blitzangebote von Amazon für den 11.12") from the feed "http://www.mydealz.de/rss/feed". According to the feed the item was published at 11. Dezember 2015 07:59 but it is still not in the visible in miniflux at time 08:10. Picofeed grabs the feed without problem.
I don't know what else I can do to debug additional info, but generally speaking the feed works ok in miniflux.
Best Regards
Andy

Would you please enable debug logging (Preferences => general => Enable debug mode), refresh the feed manually and paste the output of Preferences => about => Console).
Which miniflux version are you using?

Thanks for the quick reply. I am using miniflux v 1.1.8
I check debuggin already a few days ago, is it possible to read the full log not only the one which is displayed in the browser?
Strange thing, if I refresh the feed nothing is written into the log.

I'm not sure if I got your question.

I enabled debugging mode already a few days ago, is it possible to read the full log not only the one which is displayed in the browser?

Well, it is the full log. But it will be overwritten with every action to limit the size.

Strange thing, if I refresh the feed nothing is written into the log.

Indeed that's strange. Even if the feed is unchanged, something should be written to log.
Would you please check whether you have a the <miniflux>/data/debug.log on your server.
Is something logged if you refresh another feed?

Sorry for the misunderstanding. I enabled debug logging a few days ago due to a feeling that some feeds do not refresh adequatly. Today, however, I could trace that feeling to a concrete incident.
I have the file with the debug log on my server but there is no additional info in it.
Yes, the refresh procedure of other feeds are written into the log. Though, the second refresh is logged, see below. Possibly it was overwritten by other refreshes before.
[2015-12-11 09:39:22] PicoFeed\Client\Curl Fetch URL: http://feeds.feedburner.com/mydealz
[2015-12-11 09:39:22] PicoFeed\Client\Curl Etag provided: q++KrCzJfqtTahn4vZkmRrECqIc
[2015-12-11 09:39:22] PicoFeed\Client\Curl Last-Modified provided: Thu, 10 Dec 2015 23:02:37 GMT
[2015-12-11 09:39:22] PicoFeed\Client\Curl cURL total time: 0.021335
[2015-12-11 09:39:22] PicoFeed\Client\Curl cURL dns lookup time: 0.002085
[2015-12-11 09:39:22] PicoFeed\Client\Curl cURL connect time: 0.005347
[2015-12-11 09:39:22] PicoFeed\Client\Curl cURL speed download: 0
[2015-12-11 09:39:22] PicoFeed\Client\Curl cURL effective url: http://feeds.feedburner.com/mydealz
[2015-12-11 09:39:22] PicoFeed\Client\HttpHeaders HTTP status code: 304
[2015-12-11 09:39:22] PicoFeed\Client\HttpHeaders HTTP header: Date => Fri, 11 Dec 2015 08:39:22 GMT
[2015-12-11 09:39:22] PicoFeed\Client\HttpHeaders HTTP header: Server => GSE
[2015-12-11 09:39:22] PicoFeed\Client\HttpHeaders HTTP header: Connection => close
[2015-12-11 09:39:22] PicoFeed\Client\Curl Resource not modified

There is definitely a mismatch here, because the feed was modified numerous times after "Thu, 10 Dec 2015 23:02:37 GMT"

Yeah I guess I see what's wrong here and it looks like an issue with the server that host the feed.
Feedburner seems to have problems with their own Etag. The Etag is for caching purpose. Webserver can send you a special marker with every response: the Etag. If you provide this Etag with your next request, the Server can easily decide whether the content has been changed or not. The Server will either reply 304 Not Modified or send you the (changed) content.
Even if your last received eTag is form around midnight (more likly it is older), feedburner webserver is still the opinion that the feed is unchanged.
I guess they have some kind of problem, since feedburner doesn't send eTags for new requests any more, but still evaluates received eTags. Additionally, feedburner doesn't evaluated (any more?) the Last-Modified Date.
@aschilling A quick and easy workaround: Remove all feeds hosted by feedburner and add them again.
@BernhardPosselt Probably interesting for you as well. I guess you will receive reports soon. Any idea what we can do to workaround the feedburner issue?
$ curl -I "http://feeds.feedburner.com/mydealz" --header 'If-None-Match: q++KrCzJfqtTahn4vZkmRrECqIc' --header 'If-Modified-Since: Thu, 10 Dec 2015 23:02:37 GMT'
HTTP/1.1 304 Not Modified
Date: Fri, 11 Dec 2015 08:55:47 GMT
Server: GSE

$ curl -I "http://feeds.feedburner.com/mydealz" --header 'If-Modified-Since: 11 Dec 2015 09:27:02 GMT'
HTTP/1.1 200 OK
Content-Type: text/xml; charset=UTF-8
Last-Modified: Fri, 11 Dec 2015 09:27:02 GMT
Date: Fri, 11 Dec 2015 09:27:43 GMT
Expires: Fri, 11 Dec 2015 09:27:43 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Server: GSE
Transfer-Encoding: chunked
Accept-Ranges: none
Vary: Accept-Encoding

$ curl -I "http://feeds.feedburner.com/mydealz"
HTTP/1.1 200 OK
Content-Type: text/xml; charset=UTF-8
Last-Modified: Fri, 11 Dec 2015 09:27:02 GMT
Date: Fri, 11 Dec 2015 09:33:32 GMT
Expires: Fri, 11 Dec 2015 09:33:32 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Server: GSE
Transfer-Encoding: chunked
Accept-Ranges: none
Vary: Accept-Encoding

Ok, so just for a better understanding: feedburner dropped the E-Tag in their response, however if you send one you get a 304. Instead they are going for only Last-Modified?

Near to correct summary. Looks like Last-Modified isn't evaluated at all.
Hopefully they fix their server soon.

Maybe contact them by mail?

Feedburner fixed their server:
[2015-12-13 11:18:11] PicoFeed\Client\Curl Fetch URL: http://www.mydealz.de/rss/feed
[2015-12-13 11:18:11] PicoFeed\Client\Curl Etag provided: q++KrCzJfqtTahn4vZkmRrECqIc
[2015-12-13 11:18:11] PicoFeed\Client\Curl Last-Modified provided: Thu, 10 Dec 2015 23:02:37 GMT
[2015-12-13 11:18:12] PicoFeed\Client\Curl cURL total time: 0.466031
[2015-12-13 11:18:12] PicoFeed\Client\Curl cURL dns lookup time: 0.004138
[2015-12-13 11:18:12] PicoFeed\Client\Curl cURL connect time: 0.058583
[2015-12-13 11:18:12] PicoFeed\Client\Curl cURL speed download: 87625
[2015-12-13 11:18:12] PicoFeed\Client\Curl cURL effective url: http://www.mydealz.de/rss/feed
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP status code: 200
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Date => Sun, 13 Dec 2015 11:18:12 GMT
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Content-Type => text/xml; charset=utf-8
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Transfer-Encoding => chunked
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Connection => close
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Set-Cookie => navi=YTo5OntzOjg6ImhvbWVwYWdlIjtzOjg6ImZlYXR1cmVkIjtpOjE7czozOiJob3QiO2k6MjtzOjM6ImhvdCI7aTozO3M6MzoiaG90IjtpOjQ7czozOiJuZXciO2k6NTtzOjM6Im5ldyI7aTo2O3M6MzoibmV3IjtpOjc7czozOiJuZXciO3M6NDoidmlldyI7czo0OiJsaXN0Ijt9; expires=Mon, 14-Dec-2015 11:18:12 GMT; path=/; domain=.mydealz.de
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Cache-Control => private
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Pragma => private
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: X-HUKD-Cache => MISS
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Content-Encoding => gzip
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Vary => Accept-Encoding,User-Agent
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: Server => cloudflare-nginx
[2015-12-13 11:18:12] PicoFeed\Client\HttpHeaders HTTP header: CF-RAY =><PHONE_NUMBER>1e2720-FRA
[2015-12-13 11:18:12] PicoFeed\Parser\Rss20: HTTP Encoding "utf-8" ; XML Encoding ""
[2015-12-13 11:18:12] PicoFeed\Parser\Rss20: begin parsing
[2015-12-13 11:18:12] PicoFeed\Parser\Rss20
Feed::id = http://www.mydealz.de/rss/feed
Feed::title = HUKD - MyDealz.de
Feed::feed_url = http://www.mydealz.de/rss/feed
Feed::site_url = http://www.mydealz.de/
Feed::language =
Feed::description = -
Feed::logo =
Feed::date = Sun, 13 Dec 15 11:18:12 +0000
Feed::isRTL() = false
Feed::items = 25 items

And miniflux removes the not any longer provided ETag as well as the last modified information from the database.
@aschilling would you please close the ticket.

Thanks for the reply. As suggested on Friday I added the mydealz feed manually and compared the feed updated with my stand-alone feedreader (ReadKit). It is true that miniflux updates the feed again.
However, there are still some feed items which did not show up in miniflux during the last two days. Unfortunately, I cannot reproduce the missing feed items at the moment as all items show up if I add the feed manually. My gut feeling is that miniflux has problems with the feed because of its non-linear structure (i.e. feed items are not always added at the top of the feed)
If it is ok with you, I would like to monitor the behavior in the next few days and report if I find a concrete incident where miniflux does not fetch all items.

However, there are still some feed items which did not show up in miniflux during the last two days.

Just to make sure that I got it correctly. You have some feeds which have missing items (e.g. you see the latest item but you are missing items in between) but in general they update fine?
@aschilling As usual, would you please provide links to those feeds, even if you can't reproduce the problem at the moment!
I'm aware of two shortcomings in miniflux which could result in items which get unintentionally marked as read:
Assuming you're reading your items in miniflux and the cronjob fetches new items. If you hit the "mark all/mark feed as read" link before reloading the page, those new items get marked as read as well and you never have a chance to notice that there where new unread items.
Assuming you're using a fever api client and you're using the "mark all/mark feed as read" functionality of the fever client, something similar as described before could happen. But in that case it's a different shortcoming. Miniflux stores only the item date supplied by the feed in the database. The fever api clients are aware of that item date. If you choose to "mark all/mark feed as read", the fever client sends either the last known item date or the last known feed refresh time along. But, if miniflux fetched new items in the meantime and the date of these items is older than the date known by the fever client, they will get marked as read as well.
Long story short: Miniflux needs to store the time an items was first seen in a feed and all datetime related comparisions need to be done against the "first seen date".
It's quite common that a feed has items dated early as the latest overall date stored in the database. For instance if a feed can't be reached for a few hours.

My gut feeling is that miniflux has problems with the feed because of its non-linear structure (i.e. feed items are not always added at the top of the feed)

@aschilling have you had a look whether your missing items are simply marked read because of the shortcomings I've described above? As far as I know, Miniflux doesn't care about item dates when fetching items from feeds. As soon as the id of an item is unknown, it will be added to the database. Independent of any dates.

If it is ok with you, I would like to monitor the behavior in the next few days and report if I find a concrete incident where miniflux does not fetch all items.

I prefer to use one ticket per issue. To me, the new reported issue doesn't sound relevant to your initial reported. But decide by yourself.

Thanks for your help and the quick reply.
This morning I discovered three items in the mydealz feed (http://www.mydealz.de/rss/feed) which were not listed in miniflux. This reinforced a suspicion which I got three days ago when I noticed that the heise top feed (http://www.heise.de/newsticker/heise-top-atom.xml) showed relatively few new items.
Unfortunately, my first attempt this morning was to check if I can reproduce the problem, by removing the feed and adding it again. Thus, I can't check if the item was mark as read. In the next days, however, I will definitely do so, as soon as I discover any missing item.
Nevertheless, I don't think that this particular problem is related to your described known shortcomings as I haven't used the "mark all/mark feed as read" functionality at all during the last two days.
Generally, I consume miniflux solely via the Fever API using Mr. Reader on my iPad and ReadKit on my Mac.
I agree, in order to keep the issues as simple as possible it is better to open a new issue as soon as I can better describe the particular problem with the missing items.
If I have time the next couple of days I will have a look if I can program some kind of diff matching procedure between the feed items from miniflux and my old setup which was based on Fever. Do you think that this is worthwhile or do you already have such tool?

Do you think that this is worthwhile or do you already have such tool?

I don't have such a tool. It might be usefully for this specific issue, since it allows you to detect missing items.
If you encounter the issue again:

please save you logfile
try to get a copy of the feed from the original source
create a database backup (prefs => database => Download the entire database)


💡 Change wording of SR list view filter box

Is there an existing issue for this?

[X] I have searched the existing issues

Is your proposal related to a problem or functionality gap?
No response
Describe your proposal
Please consider changing the wording in the filter box (currently "Filter by dataset") to more closely fit the true function, which is to filter on the "name" column, not the "dataset" column. I appreciate that this is somewhat confusing on the BE given the naming of fields in the ScanReport model 😆
Describe alternatives you've considered
No response
I'm part of a Project Team
No response
Anything else?
No response
Are you willing to contribute to developing this feature?
None

Yep this is due to the backend model which has to reflected in the API. But the fix is to be able to override this in the data table component with a prop. Should be straightforward to fix.


Source code static & dynamic analysis

As a dcp developer
I want to run static analysis tools on my code
to help not ship code with gaping security holes in it.
There has been talk of running trufflehog, a tool to find embedded secrets in code before it is pushed.
The DevSecOps team needs to decide what static analysis tools to encourage/mandate.
Then we update the tickets in the component repos with these instructions.

This has been done for the repos owned by the secondary analysis team

@rhiananthony - I don't understand your reference to done for ...secondary analysis above (or why it's in a matrix service issue). This issue is part of an epic that's blocked by - https://github.com/humancellatlas/dcp/issues/307 - basically a clarification from the DevSecOps team. Can you advise?

I thought that we had already determined which 3rd party analysis tools we would be using - specifically, Snyk and Trufflehog. Based off of my conversations with Sarah I implemented Snyk with the secondary analysis repos. If this is in error please let me know.

If Trufflehog was decided, then it needs to be clarified in https://github.com/HumanCellAtlas/dcp/issues/307 - which is the issue blocking https://github.com/HumanCellAtlas/dcp/issues/91 the containing epic for this issue.

This issue has now been unblocked.  It has been decided that 'Trufflehog' is the only analysis tool we will utilize at this time.  Please setup analysis of your repos using Trufflehog.  See commentary in https://app.zenhub.com/workspaces/dcp-backlogs-5ac7bcf9465cb172b77760d9/issues/humancellatlas/dcp/91 for more details and advice on how to do this.

@calvinnhieu - believe you're the best person to own this ticket. Please update as appropriate.
Related, we discussed implementing trufflehog at the org level during the security + compliance session of the June DCP F2F.

Quick update: The DevSecOps team is actively working to see if we can implement Trufflehog from a central location as a check on each PR. This ticket will be closed upon confirmation that this is possible and work is completed. In the meantime, I'm assigning this ticket to the Q3 release.
@calvinnhieu - could you advise if Trufflehog has already been implemented for this repo, individually?


Re organize

All the stuff right now, is not arranged well

[ ] Programs are missing flowchart

[ ] Programs are missing algorithms

[ ] Programs are missing outputs

[ ] Automatically generate svg for code

[ ] Automatic pdf generator (with copyright)

not required anymore


guest has not initialized the display (yet)

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
with no vGPU I can run the win10 vm
our gpu does not support disply=on,ramfb=on
so config as follow：
    devices:
      gpus:
      - deviceName: xxx.com/qs50
        name: gpu
      virtualGPUOptions:
          display:
            enabled: false

run win 10 vm
virtctl vnc win10vm
then I got :
guest has not initialized the display (yet)
in the k8s work I can run the win10 vm correctly
sudo qemu-system-x86_64 -enable-kvm -smp 2  -device vfio-pci,id=ua-gpu-gpu1,sysfsdev=/sys/bus/mdev/devices/c4f702ca-c69d-4d7d-a526-5fdcf78d3428,display=off ......
What you expected to happen:
could see win10 desktop normal
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
the gpu driver in win10vm can not be install until the vm up, we need Manual installation vGPU driver after startup
Manual installation after startup
Environment:

KubeVirt version (use virtctl version):0.49
Kubernetes version (use kubectl version):1.23
VM or VMI specifications:win10
Cloud provider or hardware configuration: x86
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):5.4. ubuntu 20.04
Install tools:kubeadm
Others:

@vladikr could you take a look here, please? Thank you!

kubectl logs virt-launcher-win10vm6-bdnjp -c compute
{"component":"virt-launcher","level":"warning","msg":"PCI_RESOURCE_******** not set for resource mthreads.com/S30","pos":"addresspool.go:50","timestamp":"2022-02-25T09:53:20.366455Z"}
{"component":"virt-launcher","level":"info","msg":"host-device created: 56a4c4e2-c81f-4cba-82bf-af46c30ea32d","pos":"hostdev.go:85","timestamp":"2022-02-25T09:53:20.366477Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"win10vm6","namespace":"default","pos":"server.go:190","timestamp":"2022-02-25T09:53:20.367194Z","uid":"7ce7a41d-e1e8-4515-9c22-2e9219d50de5"}
and in the HOST
use
sudo ./qemu-kvm  ****** -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
the vm can not run properly
sudo ./qemu-kvm  ****** -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x3
or
qemu-kvm  ******  -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x4
the vm run ok
addr 0X2 is wrong ?

in the host I tested
sudo ./qemu-kvm -name guest=default_win10vm5,debug-threads=on -machine pc-q35-6.0,accel=kvm,usb=off,dump-guest-core=off,memory-backend=pc.ram -cpu Icelake-Server,ss=on,vmx=on,hypervisor=on,tsc-adjust=on,avx512ifma=on,sha-ni=on,rdpid=on,md-clear=on,stibp=on,arch-capabilities=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,hle=off,rtm=off,clwb=off,la57=off,wbnoinvd=off,intel-pt=off,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff -m 4096 -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296}' -overcommit mem-lock=off -smp 2,sockets=2,dies=1,cores=1,threads=1 -object '{"qom-type":"iothread","id":"iothread1"}' -uuid c725ce3c-84a2-54cd-a41d-c2161fc521aa -smbios type=1,manufacturer=KubeVirt,product=None,uuid=c725ce3c-84a2-54cd-a41d-c2161fc521aa,family=KubeVirt -no-user-config -nodefaults  -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x3
-device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x3.0x1
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x3.0x2
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x3.0x3
-device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x3.0x4
-device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x3.0x5
-device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x3.0x6
-device VGA,id=video0,vgamem_mb=16,bus=pcie.0,addr=0x4
-device vfio-pci,id=ua-gpu-gpu1,sysfsdev=/sys/bus/mdev/devices/973069b7-2025-406b-b3c9-301016af3150,display=off,bus=0x5
-device virtio-balloon-pci-non-transitional,id=balloon0,bus=pci.6,addr=0x0
-device qemu-xhci,id=usb,bus=pci.2,addr=0x0
-device virtio-serial-pci-non-transitional,id=virtio-serial0,bus=pci.4,addr=0x0
-device virtio-scsi-pci-non-transitional,id=scsi0,bus=pci.3,addr=0x0
-device usb-tablet,id=ua-tablet,bus=usb.0,port=1
-spice port=12222,disable-ticketing=on
-hda ubuntu.img
-nic user,hostfwd=tcp::3333-:22 -net nic
the vm can run correctl
but actually kubevirt use
-device vfio-pci,id=ua-gpu-gpu1,sysfsdev=/sys/bus/mdev/devices/973069b7-2025-406b-b3c9-301016af3150,display=off,bus=pci.5  \
so i think the topology of pci cause this issue, or our gpu is not support this topology.
is there any config in the vm yaml could set the vgpu pci  topology?

@luckyuuuu hi, could you please post the permittedHostDevices section from your kubevirt CR? Thanks

@luckyuuuu is this device that you are adding is a virtual GPU, such as a mediated device, or is it a PCI device?
What is the vendor of this device?
Looking at the qemu command line, you are adding a PCI device not MDEV - therefore, this is not a virtual GPU. Hence, the virtualGPU display will not be enabled for PCI devices and you shouldn't set anything in this API field.

@jean-edouard @vladikr
our company focus on GPU research and development, like intel & NVIDIA，our Product coming soon，so i am sorry i can not tell you the vendor now.
I reference this to create vGPU and deploy kubevirt to KS8  https://kubevirt.io/2021/intel-vgpu-kubevirt.html#validate-vgpu-detection
create vGPU
ExecStart=/bin/sh -c "echo '56a4c4e2-c81f-4cba-82bf-af46c30ea32d' > /sys/devices/pci0000:00/0000:00:02.0/mdev_supported_types/xxx/create" ExecStart=/bin/sh -c "echo '973069b7-2025-406b-b3c9-301016af3150' > /sys/devices/pci0000:00/0000:00:02.0/mdev_supported_types/xxx/create"
add vGPU by
spec:
  configuration:
    developerConfiguration:
      featureGates:
      - GPU
    permittedHostDevices:
      mediatedDevices:
      - mdevNameSelector: "xxxgpu-Standard"
        resourceName: "xxx.com/x30"

create vm by
        devices:
          gpus:
          - deviceName:xxx.com/x30
            name: gpu1
            virtualGPUOptions:
              display:
                enabled: false
                ramFB:
                enabled: false
          disks:

in the virt-launcher pod libvirtd log

but i got

so i try to launch the vm in the host and the qemu command line from the libvirtd log
I meant to add virtual GPU such as a mediated device, did I do anything wrong at any of the above steps？

@luckyuuuu Hi, have you resolved this issue?


Updates to short version of Self-service Data Studio workshop (from QA)

WMS 5501
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

@michmattora - You are not listed on the workshop team in WMS. Please check with the workshop author to add you to the workshop and confirm if these changes can be approved.

Hi Anoosha,
Jayant is the main author and I have been working with him and Kevin Lazarz.  The changes should be good to approve but by all means check with Jayant.
Regards,
Mike
On 20 Mar 2023, at 22:42, Anoosha Pilli @.***> wrote:

@michmattorahttps://urldefense.com/v3/__https://github.com/michmattora__;!!ACWV5N9M2RV99hQ!OXO6GbzeTo1EFNxB6mA0oRGWkstOZr-GPvHiHii7stlb_poh_H05-So14YoMIJkNDUkvbzu4EqN-t99QdnQPmBmbXvE$ - You are not listed on the workshop team in WMS. Please check with the workshop author to add you to the workshop and confirm if these changes can be approved.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/oracle-livelabs/adb/pull/152*issuecomment-1477040894__;Iw!!ACWV5N9M2RV99hQ!OXO6GbzeTo1EFNxB6mA0oRGWkstOZr-GPvHiHii7stlb_poh_H05-So14YoMIJkNDUkvbzu4EqN-t99QdnQP3r-9fvI$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AUYVYICUOU32HZQYER4MOK3W5DMN3ANCNFSM6AAAAAAWBI66BQ__;!!ACWV5N9M2RV99hQ!OXO6GbzeTo1EFNxB6mA0oRGWkstOZr-GPvHiHii7stlb_poh_H05-So14YoMIJkNDUkvbzu4EqN-t99QdnQP_0acvyQ$.
You are receiving this because you were mentioned.Message ID: @.***>


add spopt description in changelog

Hello! Please make sure to check all these boxes before submitting a Pull Request
(PR). Once you have checked the boxes, feel free to remove all text except the
justification in point 5.

[ ] You have run tests on this submission, either by using Travis Continuous Integration testing testing or running nosetests on your changes?
[ ] This pull request is directed to the pysal/master branch. This is important, as any PRs submitted against any other branches will be delayed.
[ ] This pull introduces new functionality covered by
docstrings and
unittests?
[ ] You have assigned a
reviewer and added relevant labels
[ ] The justification for this PR is:

@sjsrey Please take a look!

@sjsrey Please take a look!


How to write bullet points?

Hi, first of all I want to thank you for your efforts on this one. It really helped a lot of people.
As for my question, I think this is related to this issue which was submitted a year ago. Seeing as bullet is a special character, I want to know if this is possible now. I saw from this thread that it is possible with pdfbox 2.0 but I think this library isn't updated yet to that version.
Thanks again for this port!

It is possible if you use the LiberationSans font for example. You may still have trouble using other unicode characters, but I was able to get the bullet point to write to a PDF.


So... I found this while helping someone with a problem with this method....

https://github.com/DV8FromTheWorld/JDA/blob/7160efdd5f655d32ff315235f6842966932f92c7/src/main/java/net/dv8tion/jda/core/managers/GuildController.java#L144

Uhm Kant, you are Staff, if you cant help yourself something is wrong. I'ld replace the second member with voice channel. Going to PR it.

@Sanduhr32 There is a possibility that he is unable to make a PR to fix this. Making issues is also standard procedure so you can keep track on version progress.

na... I just posted here for future reference
Just gonna add that change to some other commit and don't mention it

👍

Its also not urgent enough to do right now. Just add it to the next push of a "proper" commit/change

Fixed in #440


feat: VSCode dev support

I haven't personally spent much time with VSCode (so I may be missing some fairly obvious gotcha's here), but it's an incredibly popular editor and it would be really nice to enable its users to try out our server. After some tinkering I was able to get a development debug build to work:

I pieced this together by looking over similar implementations in htmx-lsp and surrealql-lsp. (Both are well-worth checking out)
cc: @Ce11an, I got most of the way there by copying your implementation in surrealql-lsp. Hope that's ok 😄

I haven't personally spent much time with VSCode (so I may be missing some fairly obvious gotcha's here), but it's an incredibly popular editor and it would be really nice to enable its users to try out our server. After some tinkering I was able to get a development debug build to work:

I pieced this together by looking over similar implementations in htmx-lsp and surrealql-lsp. (Both are well-worth checking out)
cc: @Ce11an, I got most of the way there by copying your implementation in surrealql-lsp. Hope that's ok 😄

Of course! I copied the majority from rust-analyzer 😆

Of course! I copied the majority from rust-analyzer 😆

😆

P.S. I also added bits into the CI to check for linting and formatting errors. As well as making sure the package can be built. Not too much effort to add in if you fancied it.

Awesome! I'll spend some time trying to get that working with the existing CI now :)


Fix the confusing versioning problem per #108

Fixes #108.
Would anybody like to volunteer to help us with #76?

Pull Request Test Coverage Report for Build 781

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
33 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.09%) to 88.188%

Files with Coverage Reduction
New Missed Lines
%

pyuavcan/transport/udp/_session/_input.py
1
84.89%

.test_dsdl_generated/uavcan/internet/udp/OutgoingPacket_0_1.py
1
85.34%

.test_dsdl_generated/uavcan/node/port/List_0_1.py
1
86.96%

.test_dsdl_generated/uavcan/primitive/scalar/Real16_1_0.py
1
83.67%

.test_dsdl_generated/uavcan/si/unit/power/Scalar_1_0.py
1
83.67%

.test_dsdl_generated/uavcan/time/GetSynchronizationMasterInfo_0_1.py
1
86.44%

pyuavcan/_cli/_main.py
3
91.67%

.test_dsdl_generated/uavcan/register/Value_1_0.py
24
86.27%

Totals

Change from base Build 778:
-0.09%

Covered Lines:
18422

Relevant Lines:
20221

💛  - Coveralls


Add permissions handler for slash commands

Changes this PR makes:
Adds PUT permissions handler for slash commands, without introducing any breaking changes. Too good to be true, isn't it?

@DTrombett wanna review???

Approved

JK

@DTrombett Hi. :white_heart:

:skull:

Should be good now


How Japanese CC12M was generated

Thank you very much for great work.
I would like to know how Japanese CC12M was generated. Did you translate it by your own machine translation model, or any other public services?

@lyakaap Hi! We used Google Cloud Translation.

Thanks!


Advent of Code example

This example should show off a typical advent of code solution and best practices/tips like this one.

Are you sure this is high priority?

I think the key thing we want to highlight here is that it's ok to use List U8 and converting a Str using Str.toUtf8 for some problems. Having an Advent of Code example would be very helpful to direct people to. It can explain this in a context that is concrete and specific, unblocking people.
There are other Advent of Code examples around if people go looking, but they aren't always kept up to date with the latest language features.
I agree with Anton this is a priority, particularly with AoC coming up and much having changed since last year.
Though this should be a pretty small example I think, mostly just to help people see the key features in one place (like maybe importing/ingesting files etc).

:100: Luke said it well :)

Making this example will require less time than explaining the same things repeatedly on zulip.


Adding support for looking up ARNs into account alias names

The change translates the ARNs into human readable account names (technically aliases). That way, the account id in the ARN doesn't have to be looked up or remembered when someone is having multiple AWS accounts.

I've also added a fallback in the second commit, when no alias is available. That's a possible scenario.

@jmhale Could you please take a look at this?


Add and style Issues badge for PPP

Extends from #513.
Same thing, but for issues.

Codecov Report

Merging #529 (6b5174a) into master (4820eaf) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #529   +/-   ##
=========================================
  Coverage     65.25%   65.25%
  Complexity      737      737
=========================================
  Files           147      147
  Lines          2590     2590
  Branches        282      282
=========================================
  Hits           1690     1690
  Misses          749      749
  Partials        151      151

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Represent torrent status as enum

Will build a new version soon. Do you plan to add something new soon?


Wanted: Pro License (1 Year + Free Updates)

What do you want to change?
Paid support.
This project is too important to be supported by donations alone.
I'd like a way to purchase a commercial license with one year of free upgrades.
(I don't care about expansion as much as fewer bugs, quicker turnaround, and peace of mind that the project will still be maintained in 5 years)
Along with that, I'm disappointed that the project is becoming diluted by trying to be everything to everyone. I think paying users would benefit from a return to the Unix philosophy, which is echoed in the Go Proverbs and the Go community: "Do one thing, and do it well".
It seems like this would easily lend itself to a family of separately licensable products, such as

[Database Parser] + [Code Generator]
PostgreSQL -> JSON + JSON -> Go
SQLite3 -> JSON + JSON -> Kotlin

I'd like to get a license for a database and a language, or perhaps a bundle that includes others.
From what I can see most businesses and projects:

center around just one database, not several
are forced to use multiple programming languages

On a current project I'm working on we happen to be using two different SQL databases and two programming languages, but I don't think that's common.
What database engines need to be changed?
PostgreSQL
What programming language backends need to be changed?
Go

If you'd like to financially support the project, sponsorships are the best way to do that right now. The higher tiers include support as well.
If you aren't happy with the direction sqlc is taking, you are free to fork the project.


Add infinite loop into language?

Probably a good idea
Any other things we wanna add?

If we do this, we would have to add a way to break out of the execution. This could maybe be achieved by having a variable that we check the value of after executing each statement.


chore(main): release sandworm-utils 1.10.2

:robot: I have created a release beep boop
1.10.2 (2022-12-05)
Bug Fixes

better deprecated manifest license handling (df50b52)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-utils/releases/tag/sandworm-utils-v1.10.2 :sunflower:


Consolidating local setup instructions into single document

Changes
This PR consolidates the instructions for setting up Tekton on a local environment (i.e. Minikube or Docker Desktop) into a single document. Previously, there were conflicting version in DEVELOPMENT.md and docs/tutorial.md; those documents now contain links to the new file.
(continues from #3010 )
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

/lgtm


[regression test](broker load) add case for num_as_string

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


v2.18.0 may have a breaking change

Greenkeeper warned us of react-dates breaking when moment is updated to v2.18.0.
When pinned to v2.17.1, tests pass.
I don't have time right now to investigate further, but whatever changed in v2.18.0 that caused this breakage, could you please revert and publish? The test failures imply it might be locale-related.

Thanks for the heads-up!
It looks like your test failures are due to v2.18.0's improvements in the 'L' formats for the Thai and Chinese locales.  We generally do not consider locale data updates like this to be a major version breaking change.
IMO, most of the point of using the 'L' formats is that you're wanting to adopt improvements in our locale data, so I think it's strange that you're making such strict assertions about the exact string formats.  If you actually care about getting an exact set of localized strings in each locale (as implied by your test assertions), then IMO you should really be maintaining your own formatting strings for each locale.  Otherwise I'd suggest that you move away from expecting a particular set of exact localized strings in your tests.

Closing since this doesn't seem to be an actual breaking change on our end.  Feel free to re-open this (or to file a new issue) if you uncover anything else in 2.18.0 that we need to investigate further.

Interesting, OK - typically any observable change like this would be considered breaking. Thanks for clarifying your policy.

More than half of all moment changes are locale "improvements". Saying that those are breaking is a bit extreme. If we just bumped the major with every single release everyone will be happy.

Also, I'm not convinced that "typically any obsesrvable change like this would be considered breaking" (emphasis added).  Approximately zero other JS libraries are willing to maintain their own localization data -- most libraries that can generate localized strings use external data sources that may or may not be bundled with their library in certain distributions.  AFAICT, those libraries generally don't change their major version number every time somebody else changes the data that they depend upon, even if their generated strings change as a result.

I haven't yet had a chance to investigate the failures, but it seems like some of them are actually fixing the ordering of month/day/year in some locales - these i'd consider a patch - but others cause dates that previously parsed in a locale to stop parsing as valid at all - and that's what i suspect i'd consider breaking.

If you have examples of parse failures in your tests I'd be somewhat interested to see that -- I thought they were all formatting errors when I looked at your Travis output.
That said, does this mean that you're trying to parse with 'L'?  That isn't documented or supported -- that token is only intended for formatting, not parsing.

Looking at #3608, I'm now pretty convinced this was a patch; sorry for the noise.
If we find a new parsing failure when fixing the tests I'll follow up here.

Sounds good, thanks!


added logo and name on the home page

Type of change

[ ] Added new project
[x] Bug fix
[ ] New features
[ ] Enhanced documentation

Changes proposed in this pull request

Project name : #212

Thankyou for your contribution!

@Anishkagupta04 , @varshith257. You can give me GSOS and level 2 label inside this PR


No numpad with an USB PC keyboard

What does the enhancement look like, and what's its purpose?
In desktop configuration, I use my MacBook with a USB PC keyboard (fr-azerty).
I was used to set my keyboard with OSS on Linux or Windows, so I found this project.
I have tested:

y-xkb-fr-oss.keylayout
y-xkb-fr-oss_Sundeadkeys.keylayout
y-xkb-fr-oss_latin9.keylayout
y-xkb-fr-oss_nodeadkeys.keylayout
y-xkb-ml-fr-oss.keylayout

I never got the numpad working.
I suggest to add numpad to all layouts.
What alternatives are there?
For now, I use the standard OSX FR-PC keyboard layout that handle the numpad.
Add anything else that is related and can be relevant. Go wild!
I someone know what should be added to the XML of .keylayout file, let me know ;)

I added this:
      <key code="89" output="7" />
      <key code="91" output="8" />
      <key code="92" output="9" />
      <key code="86" output="4" />
      <key code="87" output="5" />
      <key code="88" output="6" />
      <key code="83" output="1" />
      <key code="84" output="2" />
      <key code="85" output="3" />
      <key code="82" output="0" />
      <key code="65" output="." />

Inside the <keyMap index="0"> and it's good.


Other data sets(ACDC)

Hello Author! Have you used the ACDC dataset before in that paper model? Can I use ACDC dataset for 3D medical image segmentation? I don't know about the memory usage.

Hello, I haven't tried the ACDC dataset. However, the model can be used for any 3D dataset for segmentation tasks. To train this model, you need at least a 40GB GPU. You can try reducing the image's batch size and patch size to reduce GPU usage.


API 404's not registered flask error handler

Everything defaults to HTTP 500 (which is logged and clutters management console).
Maybe as simple as ?
@app.errorhandler(404)
def page_not_found(e):
        response = jsonify({"message": "API endpoint not found"})
        response.status_code = 404
        return response

I think it really is that simple. Whoops. I remember meaning to fix this prior to 2019.
fixed w/ ed91cac


[now-build-utils] Add monorepo packages to "dependencies"

When writing a community Runtime, you need to bring in
@now/build-utils as a dependency in order to have TypeScript
access to the types. When trying to compile, @now/frameworks and
@now/routing-utils are not present because they are not listed
as dependencies of this project, causing the build to fail:
$ tsc
node_modules/@now/build-utils/dist/detect-framework.d.ts:1:27 - error TS2307: Cannot find module '@now/frameworks'.

1 import { Framework } from '@now/frameworks';
                            ~~~~~~~~~~~~~~~~~

node_modules/@now/build-utils/dist/detect-routes.d.ts:1:23 - error TS2307: Cannot find module '@now/routing-utils'.

1 import { Route } from '@now/routing-utils';
                        ~~~~~~~~~~~~~~~~~~~~

Found 2 errors.

The versions listed are a result of invoking lerna add ….

Well I don't really consider it "fixed", but if it's wont-fix then ya.

Ok closing as won't fix 👍


Feature/unr 407

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
Describe your changes here.
Tests
How did you test these changes prior to submitting this pull request?
What automated tests are included in this PR?
Documentation
How is this documented (for example: release note, upgrade guide, feature page, in-code documentation)?
Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.

closing this PR in favour of https://github.com/spatialos/UnrealGDK/pull/369


[hpx] Update to 1.8.1

Fixes #30306.

All features passed with following triplets:
x86-windows
x64-windows

@LilyWangLL I've added you suggestions to the fork. Should I mark that the this package with all the features is windows-only (original package can be built on Linux/Mac)?

@LilyWangLL I've added you suggestions to the fork. Should I mark that the this package with all the features is windows-only (original package can be built on Linux/Mac)?

This is not needed, I just tested the features on windows. You should refer to the following steps to update version files of hpx.
##[error]versions/h-/hpx.json(2,): error : while parsing versions for hpx from version/h-/hpx.json
Version 1.8.1 was not found in versions file.
Run:
vcpkg x-add-version hpx
to add the new port version.
To attempt to resolve all errors at once, run:
vcpkg x-add-version --all


HTC V10 Preview Seriously Zoomed

The RFC preview is a tiny fraction of the actual photo size, both portrait and landscape, both photo and video. For RFC video, the video itself seems zoomed, not just the preview. FFC seems fairly normal across the board.
Oddly, the preview frame captures are not being saved, even though this device is configured for the classic engine. Try to get that working first, to determine whether the problem is with the preview frames or with the rendering on the TextureView.

No longer reproducible.


Better management of on-up callbacks

The purpose of this PR is to simplify the management of the callbacks that should be called after services are up.
Currently: propagate the IP address of the WordPress container to itself, the slic and the chrome one.

Fiddled with the order of operations. The callbacks now only execute after relevant services have been started.

This work caused https://github.com/the-events-calendar/tribe-common/pull/1806 test Actions to pass. Merging.


Rocket.Chat Plugin: Rename button "Hilfe beenden"

Issue
When closing a request / livechat, one user will use the button "Hilfe beenden". The button will close the room. However, a user might  think that pressing the button will just close the knowledge base and not the room(feedback from real user).
Solution
Rename the button in "Chat beenden".

Moved to: https://github.com/mrsimpson/Rocket.Chat/issues/69


Links are not working

SQL edge docker image is not available in mcr site as well as docker hub. Is the links no more valid?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: dbe1e70e-26f2-4c1c-fff5-9421a4f92d4f
Version Independent ID: b1b986bd-f8d4-9873-9014-6452a4567df1
Content: Deploy Azure SQL Edge with Docker - Azure SQL Edge
Content Source: articles/azure-sql-edge/disconnected-deployment.md
Service: sql-edge
GitHub Login: @rwestMSFT
Microsoft Alias: randolphwest

Acknowledged. I think I know why this has happened, and I'll look into it.

This issue is resolved.
#please-close


Add support for Pyright as a quality-checking tool

I'm interested in using this tool to check our diffs so that we can migrate some projects to using Pyright type checking (stricter than the mypy we are currently using) without having to fix all of our errors at once or having our CI broken for a long time. I hope others would also find this useful. I can probably find time to flesh out my little plugin for this to a proper driver for it as long as I could count on someone being available to review it some time.

Yep, im still here and do reviews. This is a solo project that I maintain on personal time so I cant promise im always avaliable. But Ill communicate if I think its gonna be a bit before I can review

Yeah, that's totally understandable, thanks!


Read-the-docs documentation

Following #100, we need a read-the-docs page to explain how the API works and give working examples with test data files.
A separate section for developers defining our software design principles, code style, and how to contribute instructions

Redundant, @nickkprice has started this in #116


URA-872 - AWS authentication via access keys

add ability to authenticate with AWS via access keys defined as environment variables

ability to use SSO/IAM retained through use of AWS_DEFAULT_PROFILE

adjust tests for new changes
add github action to add comment to new PRs with reminder to run e2e tests manually
line numbers in .secrets.baseline changed due to tests updating
update readme with new Authentication section

This change is

⚠ Reminder to manually run end to end tests in https://github.com/eastgenomics/s3_upload/tree/main/tests/e2e

All end to end tests passing:
jethro@jethro-T490:~/Projects/s3_upload$ python3 -m pytest -v   tests/e2e/
============================================================= test session starts ==============================================================
platform linux -- Python 3.8.10, pytest-7.0.1, pluggy-1.0.0 -- /usr/bin/python3
cachedir: .pytest_cache
metadata: {'Python': '3.8.10', 'Platform': 'Linux-5.15.0-124-generic-x86_64-with-glibc2.29', 'Packages': {'pytest': '7.0.1', 'pluggy': '1.0.0'}, 'Plugins': {'Faker': '14.0.0', 'repeat': '0.9.3', 'subtests': '0.11.0', 'html': '4.1.0', 'metadata': '3.0.0', 'mock': '3.11.1', 'cov': '4.0.0', 'random-order': '1.1.1'}}
Test order randomisation NOT enabled. Enable with --random-order or --random-order-bucket=<bucket_type>
rootdir: /home/jethro/Projects/s3_upload
plugins: Faker-14.0.0, repeat-0.9.3, subtests-0.11.0, html-4.1.0, metadata-3.0.0, mock-3.11.1, cov-4.0.0, random-order-1.1.1
collected 23 items

tests/e2e/test_one_complete_run_upload_to_one_remote_path.py::TestSingleCompleteRun::test_no_errors_in_logs PASSED                       [  4%]
tests/e2e/test_one_complete_run_upload_to_one_remote_path.py::TestSingleCompleteRun::test_remote_files_upload_correctly PASSED           [  8%]
tests/e2e/test_one_complete_run_upload_to_one_remote_path.py::TestSingleCompleteRun::test_slack_post_message_after_uploading_as_expected PASSED [ 13%]
tests/e2e/test_one_complete_run_upload_to_one_remote_path.py::TestSingleCompleteRun::test_upload_log_file_for_fully_uploaded_run_correct PASSED [ 17%]
tests/e2e/test_one_complete_run_upload_to_one_remote_path.py::TestSingleCompleteRun::test_uploaded_run_not_picked_up_to_upload_again PASSED [ 21%]
tests/e2e/test_one_complete_run_upload_to_one_remote_path.py::TestSingleCompleteRun::test_when_nothing_to_upload_that_exit_code_is_zero PASSED [ 26%]
tests/e2e/test_regex_filtering_against_sample_names.py::TestConfigRegexPatternsAgainstSampleNames::test_no_errors_in_logs PASSED                                            [ 30%]
tests/e2e/test_regex_filtering_against_sample_names.py::TestConfigRegexPatternsAgainstSampleNames::test_no_upload_log_generated_for_run_3 PASSED                            [ 34%]
tests/e2e/test_regex_filtering_against_sample_names.py::TestConfigRegexPatternsAgainstSampleNames::test_remote_files_uploaded_correctly PASSED                              [ 39%]
tests/e2e/test_regex_filtering_against_sample_names.py::TestConfigRegexPatternsAgainstSampleNames::test_slack_post_message_after_uploading_as_expected PASSED               [ 43%]
tests/e2e/test_regex_filtering_against_sample_names.py::TestConfigRegexPatternsAgainstSampleNames::test_upload_log_files_for_fully_uploaded_run_1_correct PASSED            [ 47%]
tests/e2e/test_regex_filtering_against_sample_names.py::TestConfigRegexPatternsAgainstSampleNames::test_upload_log_files_for_fully_uploaded_run_2_correct PASSED            [ 52%]
tests/e2e/test_resuming_partially_uploaded_runs.py::TestInterruptAndResume::test_complete_upload_log_file_as_expected PASSED                                                [ 56%]
tests/e2e/test_resuming_partially_uploaded_runs.py::TestInterruptAndResume::test_error_message_for_failed_upload_in_partial_upload_log PASSED                               [ 60%]
tests/e2e/test_resuming_partially_uploaded_runs.py::TestInterruptAndResume::test_partially_uploaded_log_file_as_expected PASSED                                             [ 65%]
tests/e2e/test_resuming_partially_uploaded_runs.py::TestInterruptAndResume::test_slack_post_messages_as_expected PASSED                                                     [ 69%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_no_errors_in_logs PASSED                              [ 73%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_remote_file_uploaded_correctly PASSED                 [ 78%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_slack_post_message_after_uploading_as_expected PASSED [ 82%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_upload_log_files_for_fully_uploaded_run_1_correct PASSED [ 86%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_upload_log_files_for_fully_uploaded_run_2_correct PASSED [ 91%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_uploaded_run_not_picked_up_to_upload_again PASSED     [ 95%]
tests/e2e/test_two_complete_runs_upload_to_two_remote_paths.py::TestTwoCompleteRunsInSeparateMonitorDirectories::test_when_nothing_to_upload_that_exit_code_is_zero PASSED  [100%]

=============================================================================== 23 passed in 10.85s ===============================================================================


[utfcpp] Use vcpkg_install_cmake instead of copying include files directly

Is your feature request related to a problem? Please describe.
utfcpp does provide exported targets, which in my opinion is always better than find_path or find_library, but the current portfile for utfcpp doesn't use vcpkg_install_cmake, so we doesn't have exported targets to work on.
Proposed solution
Switch to vcpkg_install_cmake

Good point, thanks for this issue!


What should i do to surround the text with prefix including space

i want to surround the text like this: Yellow

Unfortunately surround doesn't work with spaces, since spaces are the delimiters for the left and right surround text.
I will look into adding \ to escape the space delimiter.

@luoluorushi since release 0.4.3, the escape character \ has been added to escape the space delimiter.
Surrounding text with TEXT should now be possible with :surround  .


Nginx configuration script is no longer ruinning

@aknot242, can you provide more details?

Sure. When the deployment loads, it still seems to have an "old" nginx config. For example,  missing the websockets directives, etc. Also, I see no evidence in the logs that the nginx.sh script has run at all (which it may not have before - just not seeing any evidence that it is throwing any errors. Manually running the script is the current workaround.

Looks like there is an error in the startup script:
root@k3s:/# systemctl status udf-setup
● udf-setup.service - Setup UDF
     Loaded: loaded (/etc/systemd/system/udf-setup.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Sat 2022-07-02 19:47:30 UTC; 1min 47s ago
    Process: 701 ExecStart=/root/modern_app_jumpstart_workshop/setup/scripts/udf-setup.sh (code=exited, status=0/SUCCESS)
   Main PID: 701 (code=exited, status=0/SUCCESS)

Jul 02 19:47:13 k3s systemd[1]: Started Setup UDF.
Jul 02 19:47:13 k3s udf-setup.sh[703]: fatal: not a git repository (or any of the parent directories): .git
Jul 02 19:47:13 k3s udf-setup.sh[710]: fatal: not a git repository (or any of the parent directories): .git
Jul 02 19:47:15 k3s udf-setup.sh[808]: The connection to the server <IP_ADDRESS>:6443 was refused - did you specify the right host or port?
Jul 02 19:47:15 k3s udf-setup.sh[724]: waiting for kube api to be up...
Jul 02 19:47:27 k3s udf-setup.sh[1223]: No resources found in default namespace.
Jul 02 19:47:30 k3s systemd[1]: udf-setup.service: Succeeded.

PR #21 fixes this issue

nominated new UDF blueprint with the updated code


Export Raw Data in Mzmine 3

Dear all,
I am following the untargeted LC-MS workflow found on this link:  https://mzmine.github.io/mzmine_documentation/workflows/lcmsworkflow/lcms-workflow.html
I'm always got the error when trying to export raw data (after importing one data in)
I use "Export raw data" > "Export MS(n) trees"
The error I have is : "Could not open file C:\Program Files\ Mzmine for writing"
The main point of getting MS(n) trees out is to have a better view of the MS/MS spectra to set up the parameters for m/z tolerance and retention time tolerance.
All in all, our project is to find effective way to analyze LC-MS data (.mzXML) based on MS/MS, retention time, m/z and intensity across all data/samples. I wonder what is the ultimate way to do so.
Best,
Thao.

Hey Thao,
check out the MZmine documentation page there is a lot of information.
ALso we have some videos on youtube on how to start with MZmine.
In general try the MZmine processing wizard to setup batch processing. It contains the most important steps and also allows annotation by spectral library matching.
You can also import and double click on a file in mzmine to look at spectra and chromatograms.
cheers
Robin


[Release-1.21] - k3s secrets-encrypt status is not able to connect to API not bound to <IP_ADDRESS>

Backport fix for k3s secrets-encrypt status is not able to connect to API not bound to <IP_ADDRESS>

#5006

Reproduced the issue on k3s v1.21.9+k3s1 passing non-default bind-address <IP_ADDRESS>
sudo k3s server --cluster-init --secrets-encryption --bind-address=<ip>

Error while fetching the status
$ sudo k3s secrets-encrypt status
FATA[2022-02-14T20:37:02.887599501Z] failed to get CA certs: Get "https://<IP_ADDRESS>:6443/cacerts": dial tcp <IP_ADDRESS>:6443: connect: connection refused

Validated fix on release-1.21 branch using commit id c88374a3adf235c5026a865c4ad02a33cfe38188 passing the server flag

$ sudo k3s secrets-encrypt status --server https://<ip>:6443
Encryption Status: Enabled
Current Rotation Stage: start
Server Encryption Hashes: All hashes match

Active  Key Type  Name
------  --------  ----
 *      AES-CBC   aescbckey

Validated using config.yaml
$ cat /etc/rancher/k3s/config.yaml
bind-address: <ip>
secrets-encryption: true

Validated on k3s version v1.21.10-rc1+k3s1 (471f5eb3)
sudo /usr/local/bin/k3s secrets-encrypt status --server https://<ip>:6443
Encryption Status: Enabled
Current Rotation Stage: start
Server Encryption Hashes: All hashes match

Active  Key Type  Name
------  --------  ----
 *      AES-CBC   aescbckey


Unable to Mount Docker Volume from Self-Hosted Agent

Required Information
Question, Bug, or Feature?
Type: Bug
Enter Task Name: DockerCompose@0
Environment

Server - Azure Pipelines

Account & Team: https://dev.azure.com/PartechGSS/TDP

Build: partech_web.diagnostics-service/202106.26

Agent - Private:

OS: Ubuntu 18.04
Agent Version: 2.181.2 (commit a673867)

Issue Description
We use a docker-compose run task to run our tests.  It relies on an otherwise clean MySQL instance spinning up as a sidecar with several scripts in /docker-entrypoint-initdb.d mounted like so:
volumes:
  - mysql-data:/var/lib/mysql
  - $SYSTEM_WORKDIR/docker/mysql-test/config/init.d:/docker-entrypoint-initdb.d

This works fine using a cloud agent but the volume mount silently fails with the private agent. ls -lh /docker-entrypoint-initdb.d inside the running container shows an empty directory instead of the 5 *.sql scripts that exist at $SYSTEM_WORKDIR/docker/mysql-test/config/init.d in the host/agent container.
Task logs
diagnostics-service-202106.26.zip
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
There are no error messages.  The mounted directory is simply not available inside the running container.

/remove stale

/remove stale


[10.x] add test case method for checking all registered namespace.

Write a test case that will check whether all registered namespace returns or not.

Seems these tests still fail. Feel free to resend this with passing tests. Thanks


HomeKit open sourced 🤯

https://github.com/apple/HomeKitADK

To be precise, that is not the Homekit sourcecode but that is just the Development Kit to write code that uses homekit.


Support for S1

Hi
Great project!
could you also add a profile for S1/X1?
This JS repo has support for it: https://github.com/Poket-Jony/vanbike-lib
I would to use your tool in HomeAssistant HACS

hey! I don't have an electrified S1/X1 to test with but pull requests are very welcome if you have that model.

Hi! Awesome project 👍
I have a S2 and I try to add support for it. It will most likely work for the S1/X1 too as they seem very similar when looking at vanbike-lib. I am not an expert in BLE but will see how it goes.


Standalone-container: Scala code in  converted to Java

Note: scala-library Maven dependency is currently kept in standalone-container/pom.xml due to a runtime dependency in container-di that is excluded in container-dev.

Merge at will


Setup tone analyzer service [3082]

By Mathias Lykke Pedersen (mat0pad -<EMAIL_ADDRESS>on 2017-02-10 16:47:01.474
Create tone analyzer service on bluemix

Migrated from https://hub.jazz.net/ccm41/resource/itemName/com.ibm.team.workitem.WorkItem/3082