Version 0.10.0 - Object prototype may only be an Object or null: undefined

Runtime Error
Object prototype may only be an Object or null: undefined
Stack
TypeError: Object prototype may only be an Object or null: undefined
    at setPrototypeOf (<anonymous>)
    at __extends (http://localhost:8100/build/main.js:107679:9)
    at http://localhost:8100/build/main.js:107776:5
    at Object.<anonymous> (http://localhost:8100/build/main.js:107781:2)
    at __webpack_require__ (http://localhost:8100/build/main.js:20:30)
    at Object.<anonymous> (http://localhost:8100/build/main.js:96292:79)
    at __webpack_require__ (http://localhost:8100/build/main.js:20:30)
    at Object.<anonymous> (http://localhost:8100/build/main.js:130015:70)
    at __webpack_require__ (http://localhost:8100/build/main.js:20:30)
    at http://localhost:8100/build/main.js:66:18

Ionic Framework: 2.0.1
Ionic Native: 2.4.1
Ionic App Scripts: 1.0.0
Angular Core: 2.2.1
Angular Compiler CLI: 2.2.1
Node: 7.4.0
OS Platform: Windows 10
Navigator Platform: Win32
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
If I downgrade to 0.5.0 it works.
Fresh project works fine though.

It is breaking 0.9.0 onwards.

0.9.1 works fine for me so it must be something on your side.

It is fine after 0.11.0

Could you close this issue then, @arsyed04, please? Thanks.

I'm getting this exact error with this setup:


Defaults aren't applied to duplicated profile until saved

Windows Terminal version (or Windows build number)
main 6657d2c
Other Software
No response
Steps to reproduce

Set your default font size to 9.
Make a duplicate of the "PowerShell" profile.

Expected Behavior
The font size for the duplicated profile should display as 9.
Actual Behavior
The font size for the duplicated profile is shown as 12. Clicking save updates the profile and the default font size is applied.
https://user-images.githubusercontent.com/5821575/135661487-61af3bf8-cde4-4eb1-a5e2-fed0768c6bbf.mp4
This is not a problem in stable (1.10.2383.0).

That doesn't make sense to me. The duplicate should be a new child of the defaults profile object, which should allow it to see all settings (saved or not!) that are present on that object.
It's just like this:

Set the default font size at 9
Go to a different profile page (already existent) and observe the font size to be 9!

wait what the heck is going on
No saving

@ianjoneill quick question, did you save the settings before making the duplicate?
If I:
1. Set your default font size to 9.

2. Save the settings

3. Make a duplicate of the "PowerShell" profile.

Then the duplicate will have the font size set to 9.

My default font size is 9 - that's state that has existed since time immemorial on my machine.
If I duplicate the PowerShell profile from a brand new terminal instance (i.e. the terminal is loaded up with the defaults set with a font size of 9), I see the issue.
Stepping through the code, there's definitely something wrong.
If I stick this:
                std::wstringstream ss;
                ss << L"Original size " << profile.FontInfo().FontSize() << L" Duplicated size " << duplicated.FontInfo().FontSize() << L"\n";
                OutputDebugStringW(ss.str().c_str());

before line 215 here:
https://github.com/microsoft/terminal/blob/main/src/cascadia/TerminalSettingsEditor/MainPage.cpp#L215
I get Original size 9 Duplicated size 12 printed out.
TerminalSettings::CreateWithProfile() doesn't look at the font size from the default settings, it gets it straight out of the profile - which has the size set to 12, so the terminal preview on the settings page shows the font size as 12.
https://github.com/microsoft/terminal/blob/c727762602b8bd12e4a3a769053204d7e92b81c5/src/cascadia/TerminalSettingsModel/TerminalSettings.cpp#L65


Sending Decred page needs margin fix

The margins on the top of the Sending Decred page don't match the margins on the other pages, the text is too close to the edge. The fonts in the lower part of the page (Fee, Estimated Size, Balance After) also seem overly large, but seem to have proper margins.

I can't reproduce the error described.

Closed in #391


[Suggestion] Add a 'back to top' button in every section.

In the README.md file, add a 'back to top' button after every section. Makes navigation much smoother.

Good idea, but I am not sure if that is possible in Markdown on GH?

It think it is possible. I'll you know if it is possible.

Yeah I can do it. Assign me

Added a back to top button after every H2 ( ' ## ' ) element.

Navigates back to Table of Contents
See changes: click here

Should I send a PR or do you want me to add back to top buttons after ever sub menu H3  ( ' ### ' ) element?

I'd recommend PR'ing what you have now.

Fixed in above PR. Thank you @samyabrata-maji


[fix][meta] fix getChildren in MemoryMetadataStore and EtcdMetadataStore

Motivation
In the current implementation, the getChildren will return incorrect results when getting children paths of / and some special path in MemoryMetadataStore and EtcdMetadataStore, because we use replace lead to the basePath has been replaced many times.
Modifications
Use replaceFirst instead of replace.
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as testGetChildren.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/coderzc/pulsar/pull/16

Codecov Report

Merging #18172 (40d4456) into master (6c65ca0) will increase coverage by 14.23%.
The diff coverage is 53.84%.

@@              Coverage Diff              @@
##             master   #18172       +/-   ##
=============================================
+ Coverage     34.91%   49.15%   +14.23%
- Complexity     5707     6916     +1209
=============================================
  Files           607      398      -209
  Lines         53396    43552     -9844
  Branches       5712     4474     -1238
=============================================
+ Hits          18644    21407     +2763
+ Misses        32119    19785    -12334
+ Partials       2633     2360      -273

Flag
Coverage Δ

unittests
49.15% <53.84%> (+14.23%)
:arrow_up:

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

Impacted Files
Coverage Δ

.../service/SystemTopicBasedTopicPoliciesService.java
62.57% <0.00%> (+10.98%)
:arrow_up:

.../pulsar/broker/stats/BrokerOperabilityMetrics.java
98.21% <ø> (+5.56%)
:arrow_up:

...g/apache/pulsar/compaction/CompactedTopicImpl.java
69.28% <0.00%> (+58.57%)
:arrow_up:

.../org/apache/pulsar/broker/admin/v2/Namespaces.java
56.85% <50.00%> (+48.82%)
:arrow_up:

...apache/pulsar/proxy/server/DirectProxyHandler.java
63.63% <50.00%> (ø)

...broker/delayed/InMemoryDelayedDeliveryTracker.java
65.00% <75.00%> (+65.00%)
:arrow_up:

...pulsar/broker/admin/impl/PersistentTopicsBase.java
52.57% <100.00%> (+41.17%)
:arrow_up:

...rg/apache/pulsar/broker/service/BrokerService.java
57.65% <100.00%> (+9.65%)
:arrow_up:

.../pulsar/broker/service/SharedConsumerAssignor.java
3.70% <0.00%> (-64.82%)
:arrow_down:

...rvice/schema/KeyValueSchemaCompatibilityCheck.java
21.62% <0.00%> (-45.95%)
:arrow_down:

... and 380 more

/pulsarbot run-failure-checks


Add LSF and slurm batch scripts

We should add LSF and slurm batch scripts to examples.

Here's a rudimentary example modified from one of @lnaden's scripts, though this one seems to depend on MPS:
#!/bin/bash
#BSUB -W 24:00
#BSUB -o abl-imatinib-explicit.%J.log
#BSUB -env "all, LSB_START_JOB_MPS=Y"
#BSUB -n 4 -R "rusage[ngpus_excl_p=1,mem=8]"
#BSUB -m ls-gpu
#BSUB -J "abl-imatinib-explicit"

# Run the simulation with verbose output:
#source activate yank16
export PREFIX="explicit"
build_mpirun_configfile  "yank script --yaml=$PREFIX.yaml"
mpiexec.hydra -f hostfile -configfile configfile

I think the LSF part is done now and the slurm part is left.


The template can be successfully installed via Cookiecutter with cookiecutter <template-url> and, with the user prompts filled/selected, completes without encountering any errors.

Doesn't seem to work.
╰─λ cookiecutter https://github.com/UnoYakshi/modern-python-template.git
Unable to render variable 'project_name'
Error message: 'collections.OrderedDict object' has no attribute 'project_name'
Context: {
"_cookiecutter": {
"author_name": "{{ cookiecutter.author_name }}",
"license": [
"MIT license",
"BSD license",
"ISC license",
"Apache Software License 2.0",
"GNU General Public License v3",
"Not open source"
],
"main_branch_name": [
"master",
"main"
],
"project_name": "{{ cookiecutter.project_name }}",
"project_short_description": "Python Boilerplate contains all the boilerplate you need to create a Python package.",
"project_slug": "{{ cookiecutter.project_name.lower().replace(' ', '_').replace('-', '_') }}",
"version": "0.1.0"
},
"cookiecutter": {
"author_name": "{{ cookiecutter.author_name }}",
"license": [
"MIT license",
"BSD license",
"ISC license",
"Apache Software License 2.0",
"GNU General Public License v3",
"Not open source"
],
"main_branch_name": [
"master",
"main"
],
"project_name": "{{ cookiecutter.project_name }}",
"project_short_description": "Python Boilerplate contains all the boilerplate you need to create a Python package.",
"project_slug": "{{ cookiecutter.project_name.lower().replace(' ', '_').replace('-', '_') }}",
"version": "0.1.0"
}
}

Nah, author_name is problematic, too.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix "attempt to write a readonly database"

With adding the appuser when copying in the demo db the appuser doesn't have permission to write to it since docker defaults to adding this as root. This adds the demo db with the correct permissions.
Closes #502 #503

tyty, deploying to heroku demo env now.


Upgrading from 0.1.6 to 1.0.0

I have a project using roar-rails 0.1.6 and everything is working great :ok_hand:
I want to upgrate to 1.0.0 but when I tried to do so I started receiving the following error in my specs:
Failure/Error: post v1_groups_path, json(:group), headers_for(:json)
     NoMethodError:
       undefined method `group_url' for #<Api::V1::GroupsController:0x007fcd83e7d5a8>
     # ./app/controllers/api/v1/groups_controller.rb:25:in `create'
     # ./spec/api/v1/groups_spec.rb:31:in `block (3 levels) in <top (required)>'

Everything except for the #create action is working fine. For some reason calling respond_with @group in #create throws the above error.
This is my GroupsController:
module Api
  module V1
    class GroupsController < ApplicationController
      include Roar::Rails::ControllerAdditions

      before_action :set_group, only: [:show, :update, :destroy]
      respond_to :json

      def index
        @groups = Group.paginate(page: params[:page], per_page: params[:per_page])

        respond_with @groups
      end

      def show
        respond_with @group
      end

      def create
        @group = consume! Group.new
        @group.save

        respond_with @group
      end

      def update
        consume! @group
        @group.save

        respond_with @group
      end

      def destroy
        @group.destroy

        head :no_content
      end

      private

      def set_group
        @group = Group.find params[:id]
      end
    end
  end
end

Any idea what's going on? Missing something simple maybe?

Oh... and my GroupRepresenter:
module Api
  module V1
    class GroupRepresenter < BaseDecorator
      property :name
      property :video_playlists
      property :audio_playlists
      property :users

      link :self do
        v1_group_url represented
      end
    end
  end
end

I think group_url might be called because the responder wants to redirect to the created group. This helper is not available in the controller (apparently). Is group the correct name? It looks like it should be v1_group?
I am guessing the namespacing doesn't work, but that must be a responder problem. Did you also upgrade Rails or anything?

Ahh ok. It's curious that all the other actions are fine but #create is throwing the error. Which name are you referring to?
v1_group is the correct helper.
My controllers and representers are in the Api::V1 namespace while my models are not namespaced. This is the route:
Rails.application.routes.draw do
  scope module: :api, defaults: { format: :json } do
    namespace :v1 do
      resources :groups
    end
  end
end

I kept rails and all the other gems the same when upgrading. I am using rails 4.1.5.

That's probably because create is the only place where the responder computes a URL to redirect you.
It grabs the model and infers the URL path name, and since the model is not namespaced, it invokes group_path. I don't exactly know why that happens, but it must be something in the responder code. Can you find out whether the actual creation works, just to make sure it's not directly roar's fault?

Yep!
Just pried into the #create method and the creation of @group works and saves a group to the DB fine. It's only the respond_with @group call that seems to be causing the problem.

So I did some digging  and this is what I find out :satisfied:....
In version 0.1.6 roar-rails overrode the method #render_to_body of the AbstractController. This prevented Rails from calling it's own #render_to_body method, which   eventually calls #process_options, which then calls #url_for(location) (where location is the group in this case) if a location exists. And this is where the error is occurring with v1.0.0 :boom:
Since v1.0.0 no longer overrides this method, it is reaching this point (because we no longer have this conditional) and trying to call #url_for(location). Here is an example of the options hash given to #process_options when creating a group:
{:status=>201,
 :location=>
  [#<Group id: 18, name: "Mr. Daren Block18", created_at: "2015-01-05 04:37:05", updated_at: "2015-01-05 04:37:05">],
 :prefixes=>["api/v1/groups", "application"],
 :template=>"create",
 :json=>
  #<Roar::Rails::Responder::Response:0x007fdcd5a0db38
   @body=
    "{\"name\":\"Mr. Daren Block18\",\"video_playlists\":[],\"audio_playlists\":[],\"users\":[],\"links\":[{\"rel\":\"self\",\"href\":\"http://<IP_ADDRESS>:3000/v1/groups/18\"}]}",
   @content_type=
    #<Mime::Type:0x007fdccc593570
     @string="application/json",
     @symbol=:json,
     @synonyms=["text/x-json", "application/jsonrequest"]>>,
 :layout=>
  #<Proc:0x007fdccd7d6070@/Users/ari/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/actionview-4.1.5/lib/action_view/layouts.rb:386>}

Execution never reaches any of the new methods, #_render_option_*, that were added to v1.0.0 before the exception is raised, as you can see in rails source here.

Argh, when this change was introduced I knew something is gonna break. :facepunch:
Are you interested in resolving this?

Yea definitely. I'll put in a PR :+1:

@apotonick This doesn't seem to be an issue with roar-rails. The exception occurs because of the way I have defined my routes/namespacing and the way in which rails handles the Location header by default.
By default, Rails sets the location to be equal to the resources array which is what is passed to respond_with in the controller. In the example above, this is an array with an instance of Group, [#<Group id: 18, name: "Mr. Daren Block18", created_at: "2015-01-05 04:37:05", updated_at: "2015-01-05 04:37:05">]. It then calls url_for with this array. Since my url helper is defined as v1_groups this doesn't work and attempts to call group_url which is not defined.
However, overriding the location like this does work:
def create
  @group = consume! Group.new
  @group.save

  respond_with @group, location: [:v1, @group]
end

Yeah, that's what I guessed. But how does Rails usually know that it has to prepend the controller's namespace v1_ to the url helper?

Well by default RaiIs just passes along the resources passed to #respond_with. So, auto determining the location doesn't seem to be based on the controller being used at all. I could be wrong, but I think the only way Rails would know this automatically when using #respond_with in my case is if I were to namespace my models in the V1 namespace, which I don't want to do.
It would be nice if Rails looked-up the correct url helper in the routes for the created resource based on the current controller instance.

But then let me ask you, how did it work before? Why did it call v1_group_url instead of group_url? Or are we both wrong and before the update it didn't call a URL helper at all (because doing something else, like sending back the representation document or so)?
Can you verify that the behaviour, other than the wrong URL helper, is identical to the old behaviour?
We can implement generic logic that considers namespaces in roar-rails or in the upcoming Endpoint layer in Trailblazer.

Both wrong haha. Before the update it didn't call a URL helper at all. Because of the way roar-rails was overriding #render_to_body before the update, it wasn't setting the Location header and was not calling #url_for.
The new behavior sets the content-type and the location headers.
Implementing some general logic that considers this sounds like a good idea to me :+1: . Are you thinking logic that is solely based on namespacing or something that is also based on a rails routes lookup?

So the old behaviour was wrong?
I am thinking about something completely decoupled from Rails, so we can use it in Trailblazer and run that in Sinatra, Lotus, etc., too. Because that's the long-term goal of Trb.

Yep, the old behavior was wrong and was fixed by https://github.com/apotonick/roar-rails/pull/74 . The only reason my code worked before was because of the incorrect behavior in 0.1.6.

 Good question. We have confirmed that roar-rails #respond_with behavior is now correct! And also that when namespacing routes you often have to set the location manually since rails just passes the resource to #url_for.

And this is what we could change in roar-rails and Trailblazer. A representer could have a configured namespace and use that knowledge.


Apply lastet update merge policy to hazelcast map configuration

Sometimes when running controller with cluster mode, hazelcast split brain syndrome was occurred.
so i apply lastet update merge policy to resolve it.

LGTM


Fix transparency processing

Related to #1.

add test

Codecov Report

Merging #26 (7a5863a) into main (e2d9170) will decrease coverage by 0.85%.
The diff coverage is 93.93%.

@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
- Coverage   98.69%   97.83%   -0.86%
==========================================
  Files           2        2
  Lines         153      185      +32
==========================================
+ Hits          151      181      +30
- Misses          1        2       +1
- Partials        1        2       +1

Impacted Files
Coverage Δ

fileconverter.go
93.10% <93.93%> (+0.79%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


feat(storage): support compaction group split and merge

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Previously, we implemented the concept of compaction groups for hummock to achieve write/configuration isolation and to create new compaction groups via the table-level move function.
Previously, we implemented the concept of compaction groups for hummock to achieve write/configuration isolation and to create new compaction groups via the table-level move function.
Since the sst key range generated by the move function is not contiguous, this makes it difficult to re-combine the resulting independent compaction groups (currently not supported). Because of this concern, we set the move threshold very high, fearing that the resulting compaciton group will not be able to be merged again, thus creating a large number of compaction groups.
This concern is contrary to our expectation that in scenarios with high write throughput (backfill, etc.), we would like to split the compaction to achieve parallel compaction, increase the overall compaction throughput, and make full use of the compactor node's scale capability.
Therefore, we redesigned hummock's scalability by implementing split / merge instead of move, in order to obtain the following capabilities.

adopt more lenient split conditions to cope with high write/burst write traffic scenarios, to extend compaction capability horizontally.
auto-merge compaction groups after write throughput is restored.
refine the granularity of Split from table to key_range, to split huge compaction groups at a finer granularity
Better O&M tools to manually split and merge compaction groups.

For the current PR, we expect to implement table-level Split/Merge capability (phase 1), and plan to further implement Key-level Split in the subsequent PRs, and make CN not aware of the concept of group_id. Here are the changes involved in this PR for review.

add the concept of estimated_size to SstableInfo for more accurate Compaction policy calculation.
based on table_id level Split function, compatible with the original Split interface.

Fix key_range/table_id/estimated size after sst split.
Use (table_id, vnode = 0, epoch = 0) as split key for splitting.

merge compaction group
schedule capability for automatic split/merge.
compactor iterator support key_range filter

I'll summarise the changes to the file, for your code reivew:

src/meta/src/hummock/manager/commit_epoch.rs adapt the logic of commit_epoch so that all NewTableFragmentInfo creates a new compaction group
src/meta/src/hummock/manager/compaction/compaction_group_schedule.rs introduce helper functions that facilitate splitting, refactor the split interface based on the new implementation, and provide a simple auto split/merge strategy. (The auto split strategy is based on the previous design).
src/meta/src/hummock/manager/timer_task.rs  periodically call the try function provided by schedule to implement auto split/merge.
src/storage/hummock_sdk/src/compaction_group/hummock_version_ext.rs reimplemented split logic based on split_key.
src/storage/hummock_sdk/src/compaction_group/mod.rs provides a wrapper for the split_key based sst / level split implementation.
src/storage/hummock_sdk/src/version.rs removed cg2 / cg3 special assumptions.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Btw, I think the PR is larger than I expected. To reduce the risk of this PR, is it possible to further breaking it into small ones so that we can merge small PRs one by one.

Btw, I think the PR is larger than I expected. To reduce the risk of this PR, is it possible to further breaking it into small ones so that we can merge small PRs one by one.

Thanks, let's review the code framework first  before "ready to review"


Regarding train engine with some input image and produce Face match Result

@aybassiouny
can you help me regarding, how can i train the engine with some images i have and then how can  i  do face matching ?.
kindly provide list of commands and steps for doing that .

Hey, sorry this is just an implementation that uses already trained models. Please refer to the original cmu repo for training questions.


Fix performance issue with WinUI 3

It turns out that ResourceMap is incredibly slow in a WinUI 3 app. On my computer it needs almost 15ms for a single TryGetValue call.
Add a cache to fix the performance issue.

Would it be possible to add a code comment explaining this change?

Yes. Will do it later.


Error in the code!

the word2index of the answers in the notebook is wrong because wordcount is not right.
Look at the 2 keys "alarm" and "alarm,"

i think the solution is to fix this function
frequencies(' '.join(train_raw_y).split(' '))
we must split the answers by the ' ' and ',' NOT just ' ' alone
Am i right?

Thanks a lot! I will check this issue in the weekend. It definitely should not be the case.

Thanks for letting me know about the issue. Now I keep whole answers.


Short solution needed: "How to use filter_complex" (ffmpeg)

Please help us write most modern and shortest code solution for this issue:
How to use filter_complex (technology: ffmpeg)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to use filter_complex to apply filters to videos


[IAPI-588] Add Celonis certificated connector

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

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

Hello @souchoudhary sorry for my silling doubt but which name shall I use?
I see in the .gitignore file
icon files should not be checked into Open Source repos
icon.png
icon.jpg
Thanks!

Hey @emilio-alves-fulgencio-celonis ,
Apologies. you don't need to submit icon file here. Thanks

Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio or update your submission using your latest commit ID, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio. Please make sure that the icon meets all the requirements, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.
After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this page at step 6.
Please Create an environment in the Preview region. You will use this environment later to test your connector after Microsoft is done with the functional verification for your connector.
We expect all tests to be completed within 1-2 weeks.
If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.
Please let me know if you have any questions or run into any problems while creating or updating your submission.
Thank you very much for working with us.


[Automation] Generate Fluent Lite from Swagger dynatrace#package-2023-04-27

[Automation] Generate Fluent Lite from Swagger dynatrace#package-2023-04-27

API change check
API changes are not detected in this pull request.


Mount instead of syncing

Is it possible to use the same API to mount the folder instead of syncing? Seems like a legit scenario for some use cases. Something WebDAV like?

AFAIK, it's not stored as a folder on the backend so there are distinct upload and download steps. Unfortunately not as simple as having a one to one mapping in structure.


test: extract_image_block_types parameter usage

This PR updates the unit test function to test if image metadata image_base64 and image_mime_type are present when extract_image_block_types parameter is given.

LGTM but I don't know if it's necessary or if that's the right place for this
How these arguments are parsed is entirely up to Request class so maybe we just write a single test which shows that passing either one of ["str1", "str2"] or '["str1", "str2"]' as a value is equivalent and do not tie it to specific usages?
Following this PR we should probably update def test_ocr_languages_param() as well for consistancy because it also takes a parameter with a list as value.
I'd expect different parameters in this test to differ in contents of the array not how that array is represented.

I think it's necessary and we need to make sure that unstructured API can parse different input formats for same list parameter (e.g. ["str1", "str2"] or '["str1", "str2"]')
For test_ocr_languages_param(),  I updated the function in PR #375.


Nested 'self' field in Serializer

Is that possible somehow to have nested serializers, which contain object of the same class?
For example:
class PersonSerializer(serpy.Serializer):
    name = serpy.Field()
    age = serpy.IntField()
    childrens = PersonSerializer(many=True)

This code of course is invalid, but it should visualize my problem.
Marshmallow have something like:
childrens = fields.Nested('self', many=True)
If it's not possible I may try to implement feature like this.

http://serpy.readthedocs.io/en/latest/#nested-example


Mark sorbet_i_objIsKindOf as const

Remove sorbet_isa in favor of a direct call to sorbet_i_objIsKindOf, and mark sorbet_i_objIsKindOf as const. Also change the return type of sorbet_i_objIsKindOf to _Bool, matching the other type testing intrinsics.
Motivation

Cleaning up generated code, coalescing calls to sorbet_i_objIsKindOf when possible.
Test plan

See included automated tests.

Is it intentional that there are no tests? Would a filecheck test be possible?

It was intentional, but I think you're right that it would be nice to have a test to verify the coalescing.

OK, I had trouble writing a test to verify the behavior I expected because the function that I removed, sorbet_isa, is marked const and was coalescing before inlining to a sorbet_i_objIsKindOf call. The result is that this PR should basically be a no-op, but will leave the door open to sorbet_isa calls coalescing later than sorbet_isa would have.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_KhSU1LCyIOvaih
→ https://go/builds/bui_KhSUyy3B0YHCpV


HTTP Cookie handling

I've added HTTP Cookie handling.
It's not entirely finished as there's still 3 TODO:s left as far as I see it, but I wouldn't mind comments on how to solve that in the best way.
The HTTP::Cookie.parse one is probably the biggest one, I'm not entierly sure what's the idiomatic way of solving the error handling there. Same with HTTP.parse_time.
The last one is in HTTP.rfc1123_string and that's because Time can't handle timezone names as far as i can tell. That name could probably use some work too.
All feedback is welcome.

@netfeed This is great, thank you!!
I have to review this with @waj. I'm not sure cookies should always be parsed, maybe only if you ask for them (lazily). Maybe not all HTTP servers need cookie information.

This is true, didn't think of that. But i like that idea

Something like this maybe?

@netfeed see this comment on your gist: https://gist.github.com/netfeed/78389deddaae8d35313d#gistcomment-1567682

@netfeed Are you going to finish this any time soon ? If not I can get your branch and continue on it.

I'm waiting for a response from @asterite if the patch should stay or go. It's "done" otherwise.
There might be one or two things that i might wanna do to it though. The date stuff should probably be in Cookie instead of HTTP as the Date-header has another format than the Cookie header(god damn it http!)

@netfeed We discussed this and we think it's better if cookies are lazily created. We also don't want cookies in the constructors of Request and Response, you can always set them later via .cookies. Could you rebase and apply this changes? Then we'll merge this. Thanks!

Sure, i'll do it sometime later this week.

Good! Can't wait, it will solve half of #1392 :) I will probably take care of other half after that..

@asterite so, i think that's that. Give me a holler if something else is needed

LGTM :+1:

I think this is looking really good now. @ysbaddaden would you mind opening an issue or PR to further discuss the naming/ internal interface? I think it's minor enough to not hold off this PR any longer.

Thanks for the hard work!
Naming ain't much of a problem, but maybe the headers method should already mix @cookies when its present, so both headers and cookies are always kept in sync.
Also, what happens if we receive a request, load request.cookies then proxy the request to another server? Will cookies be duplicated in headers? If so, maybe we should clear headers["Cookies"] and headers["Set-Cookie"] before adding them back.

Yes, both sound reasonable. Writing a spec for the latter case should be easy enough, just construct a Request with cookie headers, add one and serialize. I can look into them later if you don't want to.


Did the recent update break the exe?

When I click on the .exe, it opens for a couple seconds and then closes. I've redownloaded it several times, no clue what to do.

works fine for me

I got exactly the same issue as @finnaboeuf
I'm on W11 22H2.

Under Troubleshooting: Game isn't starting when you click "Start game"? Untick 'Disable Steam check'
Does this solve the issue?

It's not the game that is failing, it's the 'EldenRingFPSUnlockAndMore.exe' that shows this behavior.
When opening the software in Windows, this app opens and closes within ~3 seconds.
Data from event viewer:
Faulting application name: EldenRingFPSUnlockAndMore.exe, version: <IP_ADDRESS>, time stamp: 0x937fce65
Faulting module name: KERNELBASE.dll, version: 10.0.22621.900, time stamp: 0xba3bd2f7
Exception code: 0xe0434352
Fault offset: 0x00000000000903ec
Faulting process id: 0x0x7218
Faulting application start time: 0x0x1D90BB16078F4F1
Faulting application path: D:\Games\Steam Folder\steamapps\common\ELDEN RING\EldenRingFPSUnlockAndMore.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 0c5cc64b-5c88-45e9-8029-bff574f4d0c4
Faulting package full name:
Faulting package-relative application ID:
Exception code: 0xe0434352 may point towards a faulty .NET installation, however reinstalling didn't solve the issue.


FR: svg image support

This plugin can be super useful. I used to use it as a template. But with the plugin , apparently it's not possible to publish a note containing an svg image. Is it because it's more complicated to implement or too heavy to host? If not, would it be possible to implement it?

Is it because it's more complicated

Not at all, I just have a whitelist of allowed types to make things safe. SVG is now added, so share away! 😊
Example shared note with SVG


Helm chart and CI changes for upstreaming

This PR moves some of the SUSE CI and Helm Chart changes into the main files, so when we upstream, those will work.

Codecov Report

Merging #519 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #519   +/-   ##
=======================================
  Coverage   57.80%   57.80%
=======================================
  Files        1061     1061
  Lines       34403    34403
  Branches     4891     4891
=======================================
  Hits        19888    19888
  Misses      14515    14515


Automatic PR from RestAPI-PR1251

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1251

Codecov Report

Merging #1193 into master will decrease coverage by 0.22%.
The diff coverage is 26.16%.

@@            Coverage Diff             @@
##           master    #1193      +/-   ##
==========================================
- Coverage   55.22%   54.99%   -0.23%
==========================================
  Files        2242     2255      +13
  Lines       61921    62408     +487
==========================================
+ Hits        34197    34323     +126
- Misses      27724    28085     +361

Impacted Files
Coverage Δ

azure-mgmt-sql/azure/mgmt/sql/models/database.py
100% <ø> (ø)
:arrow_up:

.../mgmt/sql/operations/failover_groups_operations.py
10.79% <10.79%> (ø)

...e/mgmt/sql/models/database_blob_auditing_policy.py
35.71% <100%> (+2.38%)
:arrow_up:

azure-mgmt-sql/azure/mgmt/sql/models/__init__.py
100% <100%> (ø)
:arrow_up:

azure-mgmt-sql/azure/mgmt/sql/version.py
100% <100%> (ø)
:arrow_up:

...ure-mgmt-sql/azure/mgmt/sql/operations/__init__.py
100% <100%> (ø)
:arrow_up:

...e-mgmt-sql/azure/mgmt/sql/sql_management_client.py
100% <100%> (ø)
:arrow_up:

...ure/mgmt/sql/models/sql_management_client_enums.py
100% <100%> (ø)
:arrow_up:

...tions/server_azure_ad_administrators_operations.py
14.54% <14.54%> (ø)

...t/sql/operations/vnet_firewall_rules_operations.py
15.84% <15.84%> (ø)

... and 24 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f42959a...7e8dbcc. Read the comment docs.

Version 0.5.2

Added support for server active directory administrator, failover groups, and virtual network rules
Minor changes to database auditing support

@lmazuel can you publish ? Thanks

Includes #1187 #1177 #1164 #1136


Objects inside CanvasLayers are not visible in camera preview

I downloaded this addon and put it in my game, however it seems that the camera preview doesn't show any sprites or other objects that are children of a CanvasLayer (see image)

Good catch! I haven't worked much with canvas layers, but I'll look into it and see if there's a way to include them


forgotPassword component import twice

forgotPassword component import twice we need to remove one see, here-https://github.com/MonalikaPatnaik/UMatter/blob/74e9e64c961dcea9a4336f44b38e9e3d190e3019/src/Components/Signin/index.js#L18-L23
Mentors:
@Mansi168 @MonalikaPatnaik @i-am-SnehaChauhan

@MonalikaPatnaik
i am GSSOC'23 contributor
i am interested in doing this
so kindly assign me this

@Shikhar02347893 no please look for another issues


Suppress map card in the absence of US territory representation

Currently, Vega does not support displaying information for US territories.
Until progress is made on #815, we want to hide the map card.

We sure make sure that when we hide the map card, the paired charts still line up in compare views

Does https://github.com/SatcherInstitute/health-equity-tracker/pull/853 deprecate this issue?

Yes, I believe so

Closing as #853 fixed this


x/sync/errgroup: should use context.Context from stdlib

The x/sync/errgroup/errgroup.go file reads:
// Package errgroup provides synchronization, error propagation, and Context
// cancelation for groups of goroutines working on subtasks of a common task.
package errgroup

import (
	"sync"

	"golang.org/x/net/context"
)

// [...]

// WithContext returns a new Group and an associated Context derived from ctx.
//
// The derived Context is canceled the first time a function passed to Go
// returns a non-nil error or the first time Wait returns, whichever occurs
// first.
func WithContext(ctx context.Context) (*Group, context.Context) {
	ctx, cancel := context.WithCancel(ctx)
	return &Group{cancel: cancel}, ctx
}

it should probably import and use "context" instead of "golang.org/x/net/context" (once AppEngine jumps to Go1.8)

We'll do this when Go 1.9 is released. (We generally try to support the past few Go releases in the golang.org/x/* repos)

I ran into this today on Go 1.9, any chance to get this fixed?

Yes, I think we can make this change now.  Want to send a patch?

What are the compatibility requirements, should I use conditional compilation? or can I simply just use "context".  Additionally, where is the repository for this?  I suppose I need to set up gerrit as a go contributor, but is the x/sync packaged hosted somewhere else?

I think we can just use "context".  At least, we can see if anyone complains.
You can fetch the package via go get golang.org/x/sync.  That will give you a git repo that should work with Gerrit.

First go commit, I think I did everything correctly.  Changeset here:
https://go-review.googlesource.com/c/sync/+/66651

https://golang.org/cl/84481 replace context without complexity. So, it can be merged when App Engine will move to Go1.8 ("the policy they decided upon is to wait until January 2nd" - by Joe Tsai)

Update on the issue from the CL thread. If anyone wants to follow -

the App Engine team at Google has decided that Go 1.6 users need to be supported for longer, so the decision was made to continue to use golang.org/x/net/context for some time in all the golang.org/x/* (non-Google) repos. We don't have test coverage of them at https://build.golang.org/, but we're relying on them being tested via other testing dashboards.

It'd be nice if the App Engine team made an official statement somewhere about the policy Go now needs to follow, even if it's not tested.

@jba - Should this be pushed to 1.13 ? Doesn't look like there has been any change to AppEngine policy.

AppEngine has changed. This can be fixed now.

Great, thanks !

This is done now. The CL was just marked as merged as the change was already in effect.


Using appsetting.json:  "connectionGlobalHeaders": "Authorization=Basic cause error:  illegal_argument_exception Reason: "Illegal base64 character

A few questions before you begin:

Is this an issue related to the Serilog core project or one of the sinks or
community projects.
This issue list is intended for Serilog Elasticsearch Sink issues. If this issue relates to another sink or to the code project,
please log on the related repository.  Please use Gitter chat and Stack Overflow  for discussions and questions.

Does this issue relate to a new feature or an existing bug?

[x ] Bug
[ ] New Feature

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
8.4.1
What is the target framework and operating system? See target frameworks & net standard matrix.

[ ] netCore 2.0
[ ] netCore 1.0
[ ] 4.7
[ ] 4.6.x
[ ] 4.5.x
[ X] 5.0

Please describe the current behavior?
Selflog: 2021-09-15T14:06:35.3773884Z Caught exception while preforming bulk operation to Elasticsearch: Elasticsearch.Net.ElasticsearchClientException: Could not authenticate with the specified node. Try verifying your credentials or check your Shield configuration.. Call: Status code 401 from: POST /_bulk. ServerError: Type: security_exception Reason: "invalid basic authentication header encoding" CausedBy: "Type: illegal_argument_exception Reason: "Illegal base64 character 2d""
Please describe the expected behavior?
No errors in selflog
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem
Configuration in application
Using appsetting.json:  "connectionGlobalHeaders": "Authorization=Basic " again ES with auth.

@pczabans  have you tried with
"connectionGlobalHeaders": "Authorization=Basic YWRtaW46YWRtaW4="

YWRtaW46YWRtaW4= this is a base64 string with credential like username:password

Hello @AntoCanza, this is a bit late but thanks, it works, you can configure basic auth using appsettings.json.
  "Serilog": {
    "Using": [ "Serilog.Sinks.Console", "Serilog.Sinks.Elasticsearch" ],
    "MinimumLevel": {
      "Default": "Debug",
      "Override": {
        "Microsoft": "Warning",
        "System": "Error"
      }
    },
    "WriteTo": [
      { "Name": "Console" },
      {
        "Name": "Elasticsearch",
        "Args": {
          "nodeUris": "http://elasticsearch-url:9200",
          "indexFormat": "myapi-logs-{0:yyyy.MM}",
          "autoRegisterTemplate": true,
          "connectionGlobalHeaders": "Authorization=Basic dXNlcm5hbWU6cGFzc3dvcmQ=" // dXNlcm5hbWU6cGFzc3dvcmQ= is username:password encoded in base64
        }
      }
    ],
    "Enrich": [ "FromLogContext" ],
    "Properties": {
      "Application": "YourApplicationName"
    }
  },
  "AllowedHosts": "*"
}


feat(import): use local cache if provided

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

v1.11.0
GitHub release

Your semantic-release bot :package::rocket:


Put back @heywooddogwood's updated spectrum info dialog

Plus:

fix em dash on slide 1 which was appearing as "&emdash;" on my computer. (@heywooddogwood, hopefully that didn't break the emdashes for you.)
move blue boxes of text on slides 1-4 to top
even up column width of text on slides 1-4 so blue box stays in same location.

Issues:

Voila doesn't know how to find the images. They only appear when app is run in jupyter notebook.
Vue doesn't seem to be observing "no-transition" and is swiping the text in from the right for slide changes.

Images are now displaying properly in both Voila and Jupyter Notebook after merging in #89 to this branch.

Everything looks good on my review! Some unsuccessful checks reported, but it sounds like that's not an issue on our end, but rather github.


add get-help tests for alias

this is to resolve #4167
added help alias tests.
For other concerns of the issue:

SaveTests are located at UpdatableHelpSystem.Tests.ps1

Major methods of HelpProviderWithCache are never implemented as all the classes derived from the class have implemented override methods of SearchHelp and ExactMatchHelp:

\src\System.Management.Automation\help\CommandHelpProvider.cs(30):    internal class CommandHelpProvider : HelpProviderWithCache
\src\System.Management.Automation\help\DscResourceHelpProvider.cs(15):    internal class DscResourceHelpProvider : HelpProviderWithCache
\src\System.Management.Automation\help\HelpFileHelpProvider.cs(24):    internal class HelpFileHelpProvider : HelpProviderWithCache
\src\System.Management.Automation\help\HelpProviderWithFullCache.cs(20):    internal abstract class HelpProviderWithFullCache : HelpProviderWithCache
\src\System.Management.Automation\help\ProviderHelpProvider.cs(22):    internal class ProviderHelpProvider : HelpProviderWithCache
\src\System.Management.Automation\help\PSClassHelpProvider.cs(15): 	internal class PSClassHelpProvider : HelpProviderWithCache

thanks, your comment is resolved @adityapatwardhan

@adityapatwardhan your comment is resolved


Remove devAdv10WinCon

This subfolder of WinCon was for staging of an update of the WinCon package from nfoTools.  That's not the way to do that.  The way to stage a replacement and confirm there is no regression and than any procedures are updated is in a branch, not a subfolder of WinCon.

I have to restructure.  I want something like the way VCrayApp installs and the folder structure involved.  I don't know that I need a cache, unless it becomes tedious to recompile everything.  But it should be close to the VCrayApp model.
I think I will use it simply to have the cache/ holding of *.opt files and some others.  I will also need to refine the app/ structure over time, after figuring out an installer.


Adds instructions to enable non-staff hijacks

Coverage remained the same at 96.198% when pulling 7375e3ec8b63f8cc37d39d4f8d81b5d10a18555f on freespace:master into 2e2d4c76f1cca71ffea4d6d40621cfe6cb16bfd3 on arteria:master.

Hi @freespace,
Thank you for your contribution. I am afraid, I don't fully understand what you are trying to achieve with your patch.
Might I suggestion you start a discussion first, so we can find the best possible solution together? I will close the PR, since it's old. Again, simply open a discussion, if you want to continue your work on this feature.
Best,
Joe

Hi @freespace,
Thank you for your contribution. I am afraid, I don't fully understand what you are trying to achieve with your patch.
Might I suggestion you start a discussion first, so we can find the best possible solution together? I will close the PR, since it's old. Again, simply open a discussion, if you want to continue your work on this feature.
Best,
Joe


bump rpc-graphql to latest

Bumps @solana/rpc-graphql and @solana/web3.js to the latest commit.

Current dependencies on/for this PR:

main

PR #14   👈

PR #15

PR #16

PR #17

PR #18

This stack of pull requests is managed by Graphite.

Merge activity

Dec 21, 9:39 AM: @@buffalojoec started a stack merge that includes this pull request via Graphite.


feat: add core.autopush to separate push/autosync behavior

feat: add core.autopush to separate push/autosync behavior

This change adds a `core.autopush` configuration option (which defaults
to a value of `true`). This new configuration option is used in
post-write-ish actions, to determine if the remote repository should be
pushed to. In doing this, we support workflows where a user may want to
always push to the remote, but disable the behavior of "sync", which
fetches updates from remotes for all mounts (including the root store).

Closes: gopasspw/gopass#2551

For sure. I had to wrestle with CI a bit (cough cough, if it builds, it works! ... right, test pipelines? right?), but sans any input from you, we're ready to merge this whenever you have the time for a proper review.

woohoo! i'm glad this made it in, it's been a personal pet peeve for a while.
please feel free to cc me on any issue that comes up related to this config property.


Performance of this deep equal implementation is generally proportionally between 5x slower and 700x slower compared to native deepStrictEqual

I have a test implemented here using my test/benchmark library. I've also taken the plot that this generates and hosted it publicly on the net here: https://unphased.github.io/static-sharing/2024-03-29/deepequal_perf/deepequal_perf_collisions.html
I like this method of sharing benchmark results in HTML format since the plot made with uplot allows for interacting with series and zooming in.
The general summary based on the above plotting is that although this deep-equal implementation does not have an asymptotic algorithmic shortcoming compared to the builtin (as demonstrated by the straight lines in the first plot), it is consistently between 5x slower (if I compare large arrays filled with integers) and 700x (!!) slower (if I compare large arrays filled with objects). Obviously being implemented in js as opposed to presumably C++ will necessitate a 2-10x performance hit, something seems suboptimal here because this is a lot slower than that.
I first became aware of the issue being in this library by seeing it show up in the chrome profiler. I haven't reviewed the code yet, but based on the flamegraph that I saw, the implementation appears to be a recursive one. And that doesn't bode well for performance, but I would expect even a recursive implementation to be faster than what I'm seeing.
Please let me know if any of this is unclear.

If there's a way to maintain correctness and compatibility while increasing performance, I'm all for it.


Select2 - No effect on after .trigger('change') when using ajax data

I’m trying to programmatically change a value from a select2 that uses remote data but it has no effect, the value is not changed.
The code i use is the one bellow:
 $("#example1").val('39840932').trigger('change');
The value ‘39840932’ represents the google/googletest option from the select.
Full code is there https://jsbin.com/qirixah/edit?html,js,console,output
Steps to reproduce the problem:

Go to the full code https://jsbin.com/qirixah/edit?html,js,console,output
Click on the button "changeVal" or paste the same code above
See that no change is made.

Other thing I noticed that this code above works only if you follow the steps:

manually select the google/googletest option from the select
manually change for any other option
run the code above

It looks like it needs the data to come from the server and then you can programmatically change its value, but it should not be this way.

Same with jQuery 3.6.0
select2 - 4.1.0-rc.0


Manifold OAuth

Document how OAuth is currently implemented in Manifold so that others can easily maintain it.

I finished up some documentation. Here is the link: https://picolabs.atlassian.net/wiki/spaces/docs/pages/382697473/OAuth+2.0+Implementation+in+Manifold
Adam reviewed it and liked it.


FAB-13140 added SetTransient and GetTransient Method to MockStub

Signed-off-by: Zzocker<EMAIL_ADDRESS>

made the requested change.


Parse error

I was hoping to build this into a Gradle plugin to automate downloading timezone data into an Android app (along with another library to convert to Java) but ran into an error running the script per instructions in readme:
getting data for Argentina
downloading from overpass
waiting 4 seconds
Success, decreasing overpass request gap
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
combining border
error converting geojson to geometry
error converting overpass result to geojson
n {}

/Users/phil/.../timezone-boundary-builder/index.js:210
            throw e
            ^
[object Object]

I just tried this out locally and it worked.  The error you saw was likely the result of some kind of invalid geometry that occurred in OpenStreetMap that this library couldn't process, however it must have already been fixed in OpenStreetMap.  FYI, running the whole timezone boundary building script should be considered unstable because these errors happen frequently.  I'd recommend instead making your gradle plugin download a file from the latest release instead.

Thanks for the info @evansiroky.
It is working for me now too but will use the release as you suggested.


RuntimeError: CUDA out of memory

So far I have been able to execute the code up to where I need to do 3D estimation. I am following the steps listed in the Google Colab notebook (https://colab.research.google.com/gist/eyaler/886ecdff6429ef9cd585d5dc8fdd51ec/openpose-video2bvh.ipynb#scrollTo=Oq64m1nPHm5E).
When I run the Convert 3D pose from camera coordinates to world coordinates block, I get this error: RuntimeError: CUDA out of memory. Tried to allocate 828.00 MiB (GPU 0; 6.00 GiB total capacity; 1.78 GiB already allocated; 0 bytes free; 1.81 GiB reserved in total by PyTorch)
I have tried several things online, including empty_cache().
Does anyone have a solution to this?

do you finish this question?

do you research about 3d pose evalution?if you research this can i ask some questions ?


Auto-detect and bypass featureCounts execution if biotype doesn't exist in GTF

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint .).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

This will have to be reviewed again on the merge from dev and I really would like to run the full-sized tests today...


Drop dependency on typer

As there are no signs of typer improving its maintenance status, removing it now looks like the right approach, especially as it is not compatible with newer click versions.
Related: https://github.com/tiangolo/typer/issues/300

As typer developement resumed, that is no longer needed.


CFS not support windows and mac os

CFS will use Hole Punching for delete small file, but the macos do not support this API in systemcall

yes, it can only support centos

可以用用go-fastdfs试试

CFS will use Hole Punching for delete small file, but the macos do not support this API in systemcall

Thanks for your feedback.
Yes indeed, the Linux kernel based operating system is required currently.
We propose to use our docker tool script run_docker.sh under the docker folder. It makes ability to build ChubaoFS or run a minimal cluster with full components on your local docker environment by single command.


Benthos V4 Implementation Plan

V4 Implementation Plan
Now that the majority of V4 functionality is implemented (new plugin APIs, templating, etc) we can finally begin the work of cutting a V4 release. This process is not one of adding features but of removing old and deprecated ones, with the end goal of freeing us of burdens that are currently preventing (or hindering) efforts to improve the service further.
The main risk with cutting V4 is that for a period of time we will have two hot branches, one containing our V4 work while it's in progress, and one providing features and fixes for V3 users in the meantime. Ideally we want to minimize this period of time by getting the first stable release of V4 out as soon as possible, and this way we can cool down the V3 work to only focus on back-porting fixes for occasional patch releases.
A huge amount of effort has already gone into this by implementing V4 features in a backwards compatible way so that they're available and tested within V3 releases. This should also hopefully relieve a lot of the burden of migrations for users, as they've able to gradually adopt V4 functionality in increments.
However, for this final stretch of work there are a few issues remaining that will need implementing during the cut (anything marked as blocked: https://github.com/Jeffail/benthos/projects/2) as they involve breaking changes. Therefore in order to make this transition as smooth as possible we're going to do it in the following phases.
Phase 1 - Delete
We begin our journey by creating a new branch off master called v4. The purpose of master will remain the same (all features, bug fixes and releases). On the v4 branch we will delete every single deprecated component, field, and API. During this time our diffs should be mostly red with a few exceptions, and it is important that nothing is moved as this will make it more difficult to keep this branch up to date with master.
Once we have all deprecated features removed from v4 it will make any future refactoring smoother.
We will also need to create a new migration section in the documentation that we will keep up to date with our changes, at this stage we will simply need to list the things we're deleting. If the list of deprecated components is unreasonably long then we can reconsider whether they need to explicitly listed at all.
Phase 2 - Change
Once we're finished with deletions we can move onto adding new functionality, all of the blocked items on the V4 board: https://github.com/Jeffail/benthos/projects/2 can be worked on. Ideally we would want to minimize the fingerprint of these diffs in order to help keep us in sync with master.
Each issue will require a separate entry within the migration guides in the docs. For large impact ones like the metrics changes this could even be an entire page.
Phase 3 - Move
Once the main body of breaking changes are done the last requirement is to hide all of the old packages from lib. Ideally we will eventually find new homes for all of this functionality in more appropriate locations. However, in the interest of minimizing risk it is enough to simply hide the entire package into something like internal/old, which minimizes the diff into just renaming paths.
When we're renaming package paths we should also rename the module itself from github.com/Jeffail/benthos/v3 to the new module github.com/benthosdev/benthos/v4 as we're moving the repo into benthosdev when the release is cut.
Phase 4 - Review
After this process we will need to wait for the next major version release before we can break things again, which will hopefully be way into the future. As such it's worth reviewing all components that are left, Bloblang, configuration formats, etc for breaking changes that could be made that would significantly improve them.
This should be a conservative effort as every breaking change we add increases the burden on users when they plan their upgrade. A small and seemingly insignificant break to you might translate to long hours of investigation for someone experiencing the break, so please keep this in mind when proposing changes.
Phase 5 - Test
Once we're happy with what we have we need to test it to oblivion. Testing here isn't just important from a stability point of view but also from a usability point of view. If we've introduced a breaking change thinking it makes life easier but it turns out it's worse for users than what we had before then that's something we need to capture as soon as possible.
The number one priority of a breaking change is to make functionality more consistent, more seamless, and more intuitive. The absolute worst outcome is that we end up with something more complicated, let's not allow that to happen by making sure we have lots of testing time.
During this phase we will create a new v3 branch from master which will contain all future V3 work (bug fixes) as we begin to cool V3 off. A new main branch will be created from v4, which we can retire as we make main the default branch. Finally, we move the project to the benthosdev organisation.
Hopefully by cooling off V3 we can encourage users to try out V4. We will start by asking users to try nightly builds but once we're more confident we'll start putting release candidates out.
Phase 6 - Release
When we're happy with our V4 testing we can finally put a release out. We first need to ensure a full snapshot of the documentation site is hosted somewhere, maybe v3.benthos.dev. Then we can tag a proper release and update the site branch to the shiny new goodies.

Phase 1 in progress: https://github.com/Jeffail/benthos/tree/v4
For those interested I'm streaming most of the work here, first part is here: https://youtu.be/Ny9E0SAji0I

Some of the libraries that benthos' go.mod file https://github.com/Jeffail/benthos/blob/v4/go.mod depends on are
cloud.google.com/*
github.com/Azure/*
There may not be many scenarios where cloud services like this are used, so I would like to remove direct dependencies on these in go.mod and import them when needed. This would remove a lot of non-essential libraries and reduce the compiled version and memory footprint.
The use of plugins shouldn't be flexible for users to configure, and shouldn't integrate a lot of non-core plugins into the core of benthos
Translated with www.DeepL.com/Translator (free version)

@luxixing yep thats something we're working on, in V4 you'll be able to cherry-pick which groups of plugins you build into your binary.

Sorry, forgot to update this issue but we're well into phase 3 now, the package movements are done, just working up the courage to click move on the project repo (and some final touches on migration guide). Phase 4 coming soon.

Phase 3 done, 🥁 ENTERING PHASE 4 🥁

Into phase 5 now with a release candidate: https://github.com/benthosdev/benthos/releases/tag/v4.0.0-rc1, there will be more so there's still time for changes, make sure you get your feedback in.

V4 PROPER IS DONE, thank you to everyone that tested, gave feedback, contributed code, contributed emotional support and all the other junk. I'm leaving this issue pinned for now.
https://github.com/benthosdev/benthos/releases/tag/v4.0.0


aya: Add loaded_programs() API to list all loaded programs

This uses a Programs iterator to yield all loaded bpf programs using bpf_prog_get_next_id.
Example program here
Signed-off-by: Dave Tucker<EMAIL_ADDRESS>

I went with iter_programs() and re-exported at the root of the crate for convenience.
Docs have been added also... and hopefully all missing punctuation has been added 😆

Nits fixed. Merging


[WFCORE-5740] Add the ability to ignore unavailable realms for a distributed-realm

https://issues.redhat.com/browse/EAP7-1862
https://issues.redhat.com/browse/WFCORE-5740
https://issues.redhat.com/browse/ELY-2305

Core - Full Integration Build 11399 outcome was FAILURE using a merge of 841ee8e39f9df740c55861f4e2bfd9d1dd996fe4
Summary: Compilation error: Compiler (new) Build time: 00:03:48

Core - Full Integration Build 11271 outcome was FAILURE using a merge of 841ee8e39f9df740c55861f4e2bfd9d1dd996fe4
Summary: Compilation error: Compiler (new) Build time: 00:04:03

@lvydra Just FYI, I've submitted a PR for the Elytron subsystem bump:
https://github.com/wildfly/wildfly-core/pull/4980

@fjuma Thanks for notification

Core - Full Integration Build 11298 outcome was FAILURE using a merge of 70fa124824b4260a89dae8da12a8baca7ec0667d
Summary: Compilation error: Compiler (new) Build time: 00:01:27

Core - Full Integration Build 11431 outcome was FAILURE using a merge of 70fa124824b4260a89dae8da12a8baca7ec0667d
Summary: Compilation error: Compiler (new) Build time: 00:04:35

Hi @fjuma, I do think, that most of your comments should be addressed now.

Core - Full Integration Build 11308 outcome was FAILURE using a merge of b2fccb6bb2f32e4779c1d623047e2895a9450747
Summary: Compilation error: Compiler (new) Build time: 00:01:31

@Skyllarr Please review this one too when you get a chance. Thanks!

Thanks @fjuma

@fjuma @lvydra LGTM

Core - Full Integration Build 11389 outcome was FAILURE using a merge of 11be243509f27937ffe9279413049fdee4b7cb46
Summary: Compilation error: Compiler (new) Build time: 00:01:21

Core - Full Integration Build 11529 outcome was FAILURE using a merge of 11be243509f27937ffe9279413049fdee4b7cb46
Summary: Compilation error: Compiler (new) Build time: 00:01:26

Hi @fjuma, conflicts should be resolved by now.

Just FYI, this PR is still active. This is an RFE so this needs a pre-check before merging.

Hello, lvydra. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

Core -> WildFly Preview Integration Build 11883 outcome was FAILURE using a merge of 11be243509f27937ffe9279413049fdee4b7cb46
Summary: Compilation error: Compiler (new) Build time: 00:01:15

Core -> Full Integration Build 11733 outcome was FAILURE using a merge of 11be243509f27937ffe9279413049fdee4b7cb46
Summary: Compilation error: Compiler (new) Build time: 00:01:16

Core -> Full Integration Build 11901 outcome was FAILURE using a merge of 11be243509f27937ffe9279413049fdee4b7cb46
Summary: Compilation error: Compiler (new) Build time: 00:01:41

Just FYI, this PR is still active. This is an RFE so this needs a pre-check before merging.

Just FYI, this PR is still active. This is an RFE so this needs a pre-check before merging.


Privacy mode tests

This PR implements most of the missing tests of #96; closes #96.
Not implemented: tests for the open mode, because we're lacking anything meaningful on that front as of yet :)
YUP     member cannot create invite
YUP     moderator can create invite
YUP     admin can create invite
YUP     non-members cannot connect to room / finish connection establishment / query room for others??
YUP     alias resolving should not work (returns error if attempted)

community mode:
YUP     member can create invite
YUP     moderator can create invite
YUP     admin can create invite
YUP     non-members can connect to room / conn establishment works

open mode:
can't really test, as we don't have this functinality in other places?

honestly no idea why i had to patch https://github.com/ssb-ngi-pointer/go-ssb-room/pull/200/commits/d9bc17e8b9d4031c77d46115cd7bcd07f8b3346c, didn't touch anything around aliases other than add tests (the tweak in setup_tests.go? something introduced prior to this PR? wat)


Implemented moving lines up and down with Alt+Up/Down.

Use Alt+Up/Down to move selected lines up/down respectively.
PR Type
What kind of change does this PR introduce?
Feature
Other information

@JasonStein Plz check the implementation if it passes all cases. I haven't faced any issue so far.

@soumyamahunt oh wow, this is amazing, does it work for the current line too or just selection. By current line I mean where the cursor site currently.

@soumyamahunt oh wow, this is amazing, does it work for the current line too or just selection. By current line I mean where the cursor site currently.

Yes, works that way too.

@soumyamahunt Found a bug, fixed here: https://github.com/JasonStein/Notepads/commit/9a18776b5ab2adc6c7a4743ebe89cfa31ce811f1

Found another issue:

Try Alt+Up and then Alt+Down

Found another issue:

Replicate screenshot above and then try do Alt+Up and then Alt+Down

Fixed in #557.


This dependency was not found

Hi
I tried to use this package.
But I got This dependency was not found error.
This dependency was not found:
* vue-eva-icons in ./plugins/vue-eva-icons.js

I suspect that this package isn't contain build.

I created pull request #3

Hello @ChikuwaJB
To use vue-eva-icons you must install via npm i vue-eva-icons in your project, not just download the repository. Аnd then follow the instructions https://github.com/antonreshetov/vue-eva-icons#install File demo.html is autogenerated by vue-cli and is not intended to be used.


Uploading image with same name as previous upload doesn't work

Expected behaviour: Every time I upload an image my previous image gets replaced, regardless of filename or attributes
IRL: If uploaded image has same filename as current image, the current image does not get replaced

It looks like the file input gets loaded with the image and stores a fake filepath. Re-uploading of the same name will result in the same filepath so it doesn't think anything's changed. Resolution to this will be just scrapping the value of input once the image has been uploaded and rendered into the image.
e.g. ```js
fileInput.value = '';

@bedeoverend still an issue in 1.0?

@seaneking yeah pretty sure it is - I think what should be needed here is clearing the File Input after each upload e.g. this.$.fileInput.value = null. Otherwise it doesn't think its "changed" on the next upgrade


Document usage of nativescript plugins

We should document native plugin usage like here https://github.com/halfnelson/svelte-native-grocery/blob/4e5accdae6accbc53b67db938fe96f7c934ba37d/app/app.ts#L12

A simple section in the docs (docs_src/content/docs) is probably enough

Added a section to the docs


fix variable name

Can one of the admins verify this patch?

Thanks!
Jenkins, test this please.

Grrr, math_grad_test and cloud_file_block_cache flakiness.


Clear warnings

main purpose : remove warnings
1.Use camel case instead of underscores for type names
2.for functions and variables never used comment out
3.for field never be read or enum never be constructed add underscore
4.there is another warning which is 'unnecessary unsafe block' seems like a Incorrect warning: https://github.com/rust-lang/rust/issues/49112

Codecov Report

Merging #131 (88b7c51) into main (473a3e0) will increase coverage by 1.41%.
The diff coverage is 75.09%.

@@            Coverage Diff             @@
##             main     #131      +/-   ##
==========================================
+ Coverage   63.24%   64.65%   +1.41%
==========================================
  Files          96       97       +1
  Lines       17006    18477    +1471
==========================================
+ Hits        10755    11947    +1192
- Misses       6251     6530     +279

Impacted Files
Coverage Δ

taos-query/src/common/raw/data.rs
29.91% <0.00%> (ø)

taos-query/src/common/raw/meta.rs
40.42% <0.00%> (ø)

taos-query/src/common/raw/views/lengths.rs
75.71% <ø> (ø)

taos-query/src/common/raw/views/mod.rs
71.62% <0.00%> (-7.49%)
:arrow_down:

taos-query/src/lib.rs
42.57% <0.00%> (ø)

taos-query/src/tmq/mod.rs
43.03% <0.00%> (-5.27%)
:arrow_down:

taos-query/src/util/inline_write.rs
50.00% <0.00%> (ø)

taos-sys/build.rs
0.00% <ø> (ø)

taos-sys/src/ffi.rs
0.00% <ø> (ø)

taos-sys/src/stmt/bind.rs
54.61% <ø> (-4.54%)
:arrow_down:

... and 68 more

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

Merged manually in other commits, close this.


Null pointer solved and text field removed

Null pointer solved in case there is no is_echo, removed text field it's already in the parent class

@danielemaddaluno, can you create a pull request directly to our master? This is so TRAVIS CI can initiate the build with your changes on it.

Ok, no problem, I'll do it as soon as possible 👍 ☺

Thank you! Once you've done that, please close this one and I'll let you know if there are any feedback on the other one.

Pull replied in the master


Decoupling: Force isSaving/isEnabled state when saving meta boxes

Background
The WordPress story editor supports a WordPress-specific feature called "custom meta boxes" that allows other WordPress plugins to integrate with the editor by showing their custom UI for customizing some story settings. This is particularly useful for SEO plugins like All in One SEO or Yoast SEO, as users can configure some SEO metadata from within the editor this way.
See #5048 for a demo.
Due to the way custom meta boxes work in WordPress, we need hook into the saving process of the editor and save any custom meta boxes in a separate HTTP request.
So basically, whenever the story has just been saved (but it wasn't an autosave), we save the meta boxes as well.
The interesting part:
Whether we are saving the story itself or the meta boxes, we show a loading spinner next to the publish buttons. This happens here:
https://github.com/google/web-stories-wp/blob/9ab1bd62ab46ed47362ffe4db30a2b78beb8c416/packages/story-editor/src/app/story/storyProvider.js#L167
Similarly, we always allow updating the story when there are any custom meta boxes, even if the story itself hasn't changed:
https://github.com/google/web-stories-wp/blob/9ab1bd62ab46ed47362ffe4db30a2b78beb8c416/packages/story-editor/src/components/header/buttons/update.js#L70-L74
Proof-of-concept
Recently, @sayedtaqui has been working on extracting all custom meta boxes logic from packages/story-editor into packages/wp-story-editor.
See https://github.com/rtCamp/web-stories-wp/pull/763 for a POC.
Now, solving the isSaving and isEnabled parts is really the last remaining piece for finalizing this.
With all custom meta boxes functionality moved to wp-story-editor, how can we force the isSaving state while meta boxes are saving, without having any meta boxes logic within story-editor itself? And how can we enforce isEnabled if there are any meta boxes present?
Context
Gutenberg has faced the same question and has basically solved this by moving the whole header area with the publish/update button to the edit-post package (which is basically wp-story-editor), but keep the individual components to assemble the header in the editor package (aka story-editor), with forceIsSaving props to override the state.
Source:
https://github.com/WordPress/gutenberg/blob/408170a9b4007857166b41041aceedb1cef012c8/packages/edit-post/src/components/header/index.js#L66-L82
https://github.com/WordPress/gutenberg/blob/a7e2895829c16ecd77a5ba22d84f1dee1cfb0977/packages/editor/src/components/post-saved-state/index.js#L72-L76
https://github.com/WordPress/gutenberg/blob/9580b45e6e18dd06076af9f7e1ea66babee22bf5/packages/editor/src/components/post-publish-button/label.js#L51-L65
Implementation Brief
In theory, we could do the same thing as Gutenberg, which would make implementations a bit easier on other platforms.
For example, a standalone playground doesn't need a "Publish" button anyway, just "Preview", so the playground would simply not render that component.
But perhaps there are alternatives.

@choumx @barklund Would love to hear your thoughts on this

@sayedtaqui Curious about your thoughts as well of course. Perhaps a proof-of-concept for the above idea would help

I think the Gutenberg approach makes a lot of sense, let me try a POC.

@swissspidy
Updated the existing proof-of-concept
I think we need more granular control over the components and therefore the core editor would need to export all the pieces of header so that they can be assembled in the wp-story-editor package.
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/story-editor/src/components/header/index.js#L17-L22
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/wp-story-editor/src/components/header/index.js#L48-L59
The first step would be to export Layout from the story-editor so that we can pass the header as one of its props and we can use its children as add extra content ( For example to pass MetaBoxes component, instead of sending it via StoryEditor configuration )
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/story-editor/src/index.js#L24
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/story-editor/src/components/layout/index.js#L92-L95
Then use it in the wp-story-editor
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/wp-story-editor/src/components/layout/index.js#L19-L55
And now, since we are assembling the header pieces in wp-story-editor, we can grab the loader from its neck and update isSaving as we need.
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/wp-story-editor/src/components/header/buttons/index.js#L61-L68
And pass an extra prop to handle isEnabled
https://github.com/google/web-stories-wp/blob/e3c00112889d4527129b082bf77a637bfa1a46ba/packages/wp-story-editor/src/components/header/buttons/index.js#L113

This will also open the door for giving more control of the configuration like changing some labels which may not be relevant for non-WordPress environments or allowing more InterfaceSkeleton props ( like library, inspector ) if required, instead of passing all the configuration via StoryEditor component.


improve readability in forc doc

close #4432

Hey @sarahschwartz would you mind including a screen cap of the changes?

Ah I see what you mean now! I'm not sure if we want the previews under since it will make the page much longer vertically but I'll defer to  @mitchmindtree & @JoshuaBatty

I could go either way on this one, though my inclination is to stick to the table-style approach following suit with docs.rs (e.g.), mostly because these pages can become very dense depending on the number of items in the module, and the idea is more to show an overview/list of the items that exist within the module where the user can click in to learn more.
I guess the problem with the table style approach is that sometimes you have to look close to see which preview is associated with each line. Perhaps we should use some kind of visual cue like a colour offset for every second row to make it a bit clearer?
Happy to go with what you recommend @sarahschwartz as you probably get the most feedback about the forc-doc UX!

I could go either way on this one, though my inclination is to stick to the table-style approach following suit with docs.rs (e.g.), mostly because these pages can become very dense depending on the number of items in the module, and the idea is more to show an overview/list of the items that exist within the module where the user can click in to learn more.
I guess the problem with the table style approach is that sometimes you have to look close to see which preview is associated with each line. Perhaps we should use some kind of visual cue like a colour offset for every second row to make it a bit clearer?
Happy to go with what you recommend @sarahschwartz as you probably get the most feedback about the forc-doc UX!

I like the idea about offsetting the color of each second line but keeping the old layout

Generally tables are used to display charts of data or statistics like a spreadsheet with column and row headers. I don't think it makes sense to use a table format for this type of content, but I do see the possible need to split some of the content up into different pages if they are too long. Pushing the content into a smaller space may allow it to fit in a smaller space, but this becomes less accessible / readable as well.
I also understand the desire to mirror Rust, but I don't believe this type of UI design jn particular is something that was well done or something developers really love about Rust.

@sarahschwartz I changed the description of the PR so that it is a little more descriptive in git log once it is merged. Feel free to revert it back if you feel like it.

I don't think it makes sense to use a table format for this type of content, but I do see the possible need to split some of the content up into different pages if they are too long.

Ohhh there might be some confusion w.r.t. the intentions for these module pages!
Originally, these were actually just lists of items to act as a point of easy navigation from the module level to the items it contains. The one-liner preview of the docs was added on the right just to show a little more context on what you can navigate into. Most of those item-level docs are very small right now and just happen to almost fit into the one line, however eventually (once sway-lib-std is documented properly) they be should be much more extensive with multiple tested examples, information about performance trade-offs, context on when and where to use them, etc.
Does this help to clarify the original intent a little? Knowing this, do you still think we might be better with the line breaks and larger previews? I think I'm still open to it, though I think we'd want to have some nice heuristic for trimming previews to a couple lines, or just the first sentence or something so that we don't make it too hard to quickly scan through all the items.

Hm, I still think it may be better keep the original formatting since it aligns with how cargo doc produces documentation. If it's a matter of being able to find what you're looking for there is an issue open for organising links alphabetically? In general, forc doc is immature in comparison to the cargo documenter, and with the growth it will have in the coming month I believe it will make the user interface more friendly and keeping it familiar to rust users is definitely the priority.
In general, I think the right approach is to follow in cargo doc's footsteps. I appreciate the want to make forc doc better though, and there are a good number of issues I think would be good first issues to tackle such as the aforementioned alphabetization one.

I'm not confused about this, but I appreciate you explaining your logic.
For the Dev Rel team, we frequently receive requests to better document the standard library.
We believe that the official Fuel documentation should eventually (soon) have a consistent Fuel branding and design system, which won't exactly mirror Rust's. Unless you think we should create an entirely separate documentation resource for the standard library, this documentation will eventually have to align with that design system.
This PR was meant to be a sort of quick fix to improve the accessibility of these docs for the time being. I'm definitely open to different designs and solutions, but I strongly believe a table format is not the correct format here.

Unless you think we should create an entirely separate documentation resource for the standard library, this documentation will eventually have to align with that design system.

If that's the case it may make more sense to do that

This PR was meant to be a sort of quick fix to improve the accessibility of these docs for the time being. I'm definitely open to different designs and solutions, but I strongly believe a table format is not the correct format here.

I understand the Dev rel team has a goal in mind for how they would like the documentation for the standard library to look, but I don't think it makes sense to change the look of the documentation produced by forc doc just to serve this purpose.
I would recommend working out the design for the standard library documentation in an issue and if it's decided that the structure of forc doc should stray from cargo's we can go from there.


Unable to instantiate BraketBackend for Lucy QPU Gate Type 'ecr' not supported

Hello,
I was trying to use pytket-braket to create a BraketBackend
import boto3
from braket.aws import AwsSession, AwsDevice
region = "eu-west-2"
braket_client = boto3.client('braket', region_name = region)
b = BraketBackend(device_type="qpu", provider="oqc", device="Lucy", region="eu-west-2", aws_session = sess)

Yields the below error:
KeyError                                  Traceback (most recent call last)
Input In [163], in
----> 1 b = BraketBackend(device_type="qpu",
2                   provider="oqc",
3                   device='Lucy',
4                   region="eu-west-2",
5                   aws_session = sess)
File ~/repos/quoir/venv/lib/python3.8/site-packages/pytket/extensions/braket/backends/braket.py:329, in BraketBackend.init(self, local, device, region, s3_bucket, s3_folder, device_type, provider, aws_session)
326         self._variance_min_shots = rtminshots
327         self._variance_max_shots = rtmaxshots
--> 329 self._singleqs, self._multiqs = self._get_gate_set(
330     supported_ops, self._device_type
331 )
333 arch, self._all_qubits = self._get_arch_info(props, self._device_type)
334 self._characteristics: Optional[Dict] = None
File ~/repos/quoir/venv/lib/python3.8/site-packages/pytket/extensions/braket/backends/braket.py:386, in BraketBackend._get_gate_set(supported_ops, device_type)
384     raise NotImplementedError("Device must support cnot, rx, rz and x gates.")
385 for t in supported_ops:
--> 386     tkt = _gate_types[t]
387     if tkt is not None:
388         if t in _multiq_gate_types:
KeyError: 'ecr'
aws_devices = AwsDevice.get_devices(aws_session = sess, names = ["Lucy"])
lucy_ops = aws_devices[0].properties.dict()['action']['braket.ir.jaqcd.program']['supportedOperations']
lucy_ops

['ccnot',
'cnot',
'cphaseshift',
'cswap',
'cy',
'cz',
'h',
'i',
'phaseshift',
'rx',
'ry',
'rz',
's',
'si',
'swap',
't',
'ti',
'v',
'vi',
'x',
'y',
'z',
'ecr',
'start_verbatim_box',
'end_verbatim_box']
If you look at
https://github.com/CQCL/pytket-extensions/blob/develop/modules/pytket-braket/pytket/extensions/braket/backends/braket.py#L105-L141
You can see that it's not in the supported set of gate ops.
Did a little more research and found implementations in Qiskit:
https://qiskit.org/documentation/stubs/qiskit.circuit.library.ECRGate.html
ECR includes another gate which isn't in pytket base
https://qiskit.org/documentation/stubs/qiskit.circuit.library.RZXGate.html
Do you have any timeline on when these gates/Lucy will be reported in the future?
Did some digging in pytket-extensions but couldn't find anything.
Thank you all so much for developing and maintaining this package I know Lucy just came out so not expecting it to be ready yet :)
Relevant Package versions:
amazon-braket-schemas           1.7.3.dev0
amazon-braket-sdk               1.16.0
pytket                          1.0.0rc14
pytket-braket                   0.17.0
Python version: 3.8.8

Thanks for the report. Yes, this is an issue we come across occasionally when new devices come online. We will be working on a fix for this very soon. (Pytket does support the ECR gate so it should not be difficult to make this work.)


Microsoft terminal exploits

Windows Terminal version
No response
Windows build number
No response
Other Software
No response
Steps to reproduce
// Okay then I guess I will look through Terminal files and not tell you about what I see other words I'll make a repo about your Microsoft terminal exploits for everybody to know you decided to do that  lol
@zadjii-msft
Expected Behavior
No response
Actual Behavior
//

Searching our code for words that you think make us look bad is not going to generate a particularly good blog post.

... what?

If you find an actual security issue in any Microsoft product and want to practice responsible disclosure, you are welcome to follow the security issue guidance available in our bug reporter.


Changing combat tag check to support CombatTagPlus

Fixing https://github.com/Civcraft/PrisonPearl/issues/65
@rourke750 That's how you wanted it, right?

Can one of the admins verify this patch?  Type 'ok to test' to test.

ok to test

uh sort of, I want it to support both.

Okay, changed it to work with both.

perfect


Remove STAGING_ERROR_NOTIFICATIONS and SAVE_FRONTEND_STACKTRACES

Looks like we get to remove another variable; other than that, lgtm.

Merged, thanks @andersk!


Is there any teamcity / continous integration plugin?

So we'd know how things change over time?

I'd really like to see this as a teamcity plugin. Could we consider options for injecting reporters (similar to jshint)?


speed up caching by prepared function inspection

Coverage decreased (-0.02%) to 70.828% when pulling a63f0372fab278c56c168ade27f6a296255fc883 on gertjanvanzwieten:immutable into bb522cf897d95f2879483c13545d40ffb45f00af on nutils:master.

Coverage decreased (-0.02%) to 70.828% when pulling a63f0372fab278c56c168ade27f6a296255fc883 on gertjanvanzwieten:immutable into bb522cf897d95f2879483c13545d40ffb45f00af on nutils:master.

Coverage decreased (-0.02%) to 70.828% when pulling 73c7424b000f60a8aff04484944fae9efca5af94 on gertjanvanzwieten:immutable into bb522cf897d95f2879483c13545d40ffb45f00af on nutils:master.


[#32211] Fail job on SDK worker disconnect, instead of hanging forever.

In working on OnWindowExpiry, it shows SDK side disconnects would cause the job to hang indefinitely if there were outstanding ProcessBundleRequests.
Instead, the job should fail (as SDK disconnects are not WAI behavior), and terminate execution instead.
Not testable as a closed form Go side without a more involved set up, but obvious in certain Python and Java side test failures. Clean job termination leads to better iteration than hangs do.
Part of #32211

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damondouglas


[FEAT] Copy debug info to clipboard

A button users can push to copy internal GM_info strings, browser version info, etc. to the clipboard when submitting a bug report

Added in 2.0.0-rc.36
Copies the following to clipboard:
navigator.platform
navigator.userAgent
GM_info.scriptHandler
GM_info.isIncognito
localStorage["kes-settings"]


Android : Where to request permissions?

My Xamarin Android app is composed of a splash screen activity, a login activity and a main activity.
I'm wondering where I should ask for permissions?
For me it has to be on application startup outside any custom activity. Am I wrong about this?
I would be tempted to use the plugin in MainApplication.cs. Can I do that? If not should I create a specific activity to request permissions?
Also a sample with external storage access would be a plus.

That is up to you, I only like to call them before I need them. Some apps display a nice welcome screen to request permissions if they are required.


Warnings from the build step causes the action to fail even though CI is set to false

Here is the part of my workflow:
cypress-run:
runs-on: ubuntu-latest
steps:
  - name: Checkout
    uses: actions/checkout@v2
  - run: CI=false
  # Install NPM dependencies, cache them correctly
  # and run all Cypress tests
  - name: Cypress run
    uses: cypress-io/github-action@v2
    with:
      build: yarn build
      start: yarn start
    env:
      CI: false

Here is the error produced by workflow:
"Treating warnings as errors because process.env.CI = true.
Most CI servers set it automatically.
Failed to compile."
My project is producing warnings in the build step and this causes the action to fail. Because it says CI is set to true even though i have assigned it to false.
How can i set it correctly?

@Yusuf-YENICERI Did you ever figure this out? Happening for me too-- have tried also:
        env:
          CI: false

        env:
          CI: ''

        - run: CI=false

@Yusuf-YENICERI Did you ever figure this out? Happening for me too-- have tried also:
        env:
          CI: false

        env:
          CI: ''

        - run: CI=false

        - run: CI=''

        with:
          build: CI= yarn build

        with:
          build: CI='' yarn build

        with:
          build: CI=false yarn build

I have resolved this problem in the following workflow:
https://github.com/Yusuf-YENICERI/Hatim-Dagit/blob/main/.github/workflows/firebase-hosting-merge.yml
Probably the reason setting CI to false is not working probably related with the cypress's own environment.

@Yusuf-YENICERI Thank you!

Closing, since the submitter wrote that the problem is resolved.


Display tabs for matching / maybe matching / non-matching products in products lists

Lists of products should use tabs to display:

all products in the list
products matching the user preferences
products that may match the user preferences (but we may be missing some data)
products that do not match the user preferences

See the personal search feature on the OFF web site for a sample implementation.
(the personal search feature is currently in alpha-testing on the OFF web site, to have access to it, please send me your OFF username so that I can turn it on for you).

The problem is that if you're not connected to OFF (and given the access to the alpha version), attribute_groups is not populated by the following "category" query: https://world.openfoodfacts.org/pnns-group-2/breakfast-cereals/1?lc=en&fields=product_name%2Cbrands%2Ccode%2Cnutrition_grade_fr%2Cimage_small_url%2Cselected_images%2Cquantity%2Cserving_size%2Cproduct_quantity%2Cnutriments%2Cnutrient_levels%2Cnutriment_energy_unit%2Cadditives_tags%2Cingredients_analysis_tags%2Clabels_tags%2Cenvironment_impact_level_tags%2Ccategories_tags%2Clang%2Cattribute_groups&json=1
As we're not logged in to OFF with flutter, we see the "normal" version, without attribute_groups. I wasted hours saying "Am I crazy or what?" and "This is a f*cking nightmare!": what I saw on the web (logged in) was not what I saw in flutter.
No alpha version, no attribute_groups. No attribute_groups, no match. No match, no match.
Same thing for "keywords": https://world.openfoodfacts.org/cgi/search.pl?page_size=500&tagtype_0=categories&tag_contains_0=contains&tag_0=Salmon&search_terms&lc=en&fields=%2Cproduct_name%2Cbrands%2Ccode%2Cnutrition_grade_fr%2Cimage_small_url%2Cselected_images%2Cquantity%2Cserving_size%2Cproduct_quantity%2Cnutriments%2Cnutrient_levels%2Cnutriment_energy_unit%2Cadditives_tags%2Cingredients_analysis_tags%2Clabels_tags%2Cenvironment_impact_level_tags%2Ccategories_tags%2Clang%2Cattribute_groups&json=1
Obviously the problem is on the server side, @stephanegigandet can you create the corresponding issue in the appropriate place? And possibly fix it.
PS: actually I get the attribute_groups even logged off for the "barcode search" https://world.openfoodfacts.org/api/v0/product/17601223.json?lc=en&fields=%2Cproduct_name%2Cbrands%2Ccode%2Cnutrition_grade_fr%2Cimage_small_url%2Cselected_images%2Cquantity%2Cserving_size%2Cproduct_quantity%2Cnutriments%2Cnutrient_levels%2Cnutriment_energy_unit%2Cadditives_tags%2Cingredients_analysis_tags%2Clabels_tags%2Cenvironment_impact_level_tags%2Ccategories_tags%2Clang%2Cattribute_groups

Now we're definitely stuck also for #32, #33, #34, #36, #37, as long as we don't get attribute groups from bulk http queries.
I think we also need https://github.com/openfoodfacts/openfoodfacts-dart/pull/61 to be merged.

It looks like we have relevant data now, cool!

It looks like we have relevant data now, cool!

Merged by #67.

Merged by #67.


Added a link to the quoter tool

hmm.. I don't want people to have to login for the calculator.
The aim is to allow the PSEs to sit with a customer and play with this tool, on screen in front of everyone. I totally get the point that we don't want to set expectations but I challenge you by saying that people already are doing that.. just without our knowledge :)
It might be different in AMER, but here in APAC we struggle to get included in these conversations as the platform team believe they need to do this without our input. This tool is a means for us to at least get visibility of who they are talking to and what they are saying.


Git: hygiene check fails does not report properly when committing

Steps to Reproduce:

have a hygiene error (e.g. layer breaker)
try to commit

=> you see a generic git error, not even an action to show output

A bit unhappy, since we have multi line error messages, we only show the first line:

At least there's the Open Git Log action.