add flag to preserve ordering of proto fields in openapi spec schema

Requesting flag to preserve ordering of proto fields in openapi spec schema
forcing lexicographical ordering of fields is undesirable in settings where controlling the order of properties is useful.
like readability of documentation page that renders the openapi spec. original gnostic project preserves this ordering.
Example
proto message fields are not in lexicographical order

message B {
  string x = 1;
  string z = 2;
  string y = 3;
}

message SomeRequest {
  string a = 1;
  string c = 2;
  B b = 3;
}

will result in an openapi schema where the fields are in lexicographical order
    some.pkg.v1.B:
      additionalProperties: false
      description: ""
      properties:
        x:
          additionalProperties: false
          description: ""
          title: x
          type: string
        y:
          additionalProperties: false
          description: ""
          title: y
          type: string
        z:
          additionalProperties: false
          description: ""
          title: z
          type: string
      title: B
      type: object

    some.pkg.v1.SomeRequest:
      additionalProperties: false
      description: ""
      properties:
        a:
          additionalProperties: false
          description: ""
          title: a
          type: string
        b:
          $ref: '#/components/schemas/some.pkg.v1.B'
          additionalProperties: false
          description: ""
          title: b
          type: object
        c:
          additionalProperties: false
          description: ""
          title: c
          type: string
      title: SomeRequest
      type: object

which is causing json documentation page to render like this
{
  "a": "string",
  "b": {
    "x": "string",
    "y": "string",
    "z": "string"
  },
  "c": "string"
}

expected it to follow ordering of proto fields like this
{
  "a": "string",
  "c": "string",
  "b": {
    "x": "string",
    "z": "string",
    "y": "string"
  },
}

This is a good idea, but this actually appears to be an issue with how jsonschema structures things. Maps don't guarantee order, especially in Go, but there's a further issue where I'm not sure if the order would be maintained in tools that ingest this openapi spec. It looks like there may be a convention to add a field that defines the order, usually with an X- prefix. So I can use the field number as a new property (maybe X-Field-Number) but it's unlikely that any tool using this openapi spec knows how to deal with that.
See here for more information: https://github.com/json-schema-org/json-schema-vocabularies/issues/7

thanks for getting back so quickly.
original gnostic project was able to preserve the ordering from my experience. from some digging found this old thread.
might be of some use.
https://github.com/google/gnostic/issues/2#issuecomment-262604464
the tool im using to render the spec follows ordering defined in the spec as well.
sidenote great project. requires like no proto annotations to get this going and works seamlessly with server reflection. and love the base openapi spec idea. really simplifies things.

@gtshepard thanks for the praise!
I'm considering switching to https://pb33f.io/libopenapi/openapi/, which will give ordered maps for pretty much everything so it should be possible to maintain the order declared in the protobuf file. This will be a large undertaking though so I don't promise that it will be done soon :) I already made some good progress on it though, so let's see how it goes

@gtshepard I've made a new release that has a new openapi/json schema library which has the behavior that you want here. Cheers!

wow amazing! thank you


Insert contacts using a modal workflow

This PR brings the existing contact page into a modal experience and preserves the old page as a fallback for when JavaScript is disabled (we will iterate this in a separate PR).
Trello card

@benthorner updated addressing the comment, which are all valid. Let me know if the updates regarding The API bit can just be an extra and step. make sense to you.


Impossible to import already exist keystore files

Process external keystore files (UTC / JSON) and store them locally.

Please write more detailed comments, not just 'Added' or 'Fixed'.

@r8d8 Do you want to return to this PR or will just close it?


New cases for avoid_use

https://github.com/SAP/styleguides/blob/master/clean-abap/CleanABAP.md#avoid-default-key
the breakpoint rule can be merged into this rule

yea, I also have this in abapOpenChecks, https://docs.abapopenchecks.org/checks/48/
Sometimes I end up adding DEFAULT KEY for internal tables during function module calls

Working on this - can I actually just delete the breakpoint rule and merge it into avoid_use? It's simple enough, but is there anything I have to consider?


[To rel/1.2] Optimize the speed of delete by pattern

Description
cherry-pick (#10566)

coverage: 47.925% (+0.01%) from 47.914% when pulling 2d469bd5749aff7a48c6d0a8448596e12d29561c on cp_fix_delete_speed into 61c22f9f0eaea08b9fff4d037497c568504bc573 on rel/1.2.


pull request for e2e test at 12/22/2016 23:45:18

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Home Assistant Integration broken

Describe the bug
Hello, can you take a look at https://github.com/home-assistant/core/issues/97170 please? The integration seems to be broken.
To Reproduce

get a LD2410B and connect it to 5 V
it should be discovered in HA via a Esp32 Bluetooth proxy but it is not

Additional context

connection to the official app from the manufacturer works with my sensor just fine

i fear this is almost abandoned, but i have the very same problem with my ld2450_ble integration (that is obviously based on this)
i fear the issue could also be in the bluetooth-data-tools that was recently forced to 1.20 where before it was 1.19, and it can no longer be used in this old version


Settings sync producing error

Does this issue occur when all extensions are disabled?: Fresh install no extensions installed and extensions.json is blank

VS Code Version: 1.95.1
OS Version: Windows 11 Pro 10.0.26100

Steps to Reproduce:

Fresh install
Selected Backup and Sync Settings
Recieved this error "Error while turning on Settings Sync. No authentication providers are available."
Followed steps to fix error from issue #174019
Uninstalled
Deleted %APPDATA%\Code and %USERPROFILE%.vscode and then new download
Same Error was produced as above

The error was resolved not sure what happened. It started working after I installed an extension.


'!wiki' is broken

Due to DOSarrest protection on the ROBLOX wiki, the '!wiki' command has been broken.
Here's an image of the output:

And even though it appears to return a '200 OK', the returned data (which is actually HTML!) looks like this:

I have already created a thread on RBXDev asking them to remove DOSarrest protection on api.php: Remove DOSarrest protection on api.php but in the meantime, it would be nice if we could work out some form of solution to this.
Right now, I've tried this:
local res = { }
local _, code = http.request{
    url = url,
    sink = ltn12.sink.table(res), -- I had to make a new require() for this
    method = "GET",
    headers = {
        ["Host"] = "wiki.roblox.com",
        ["Accept"] = "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8",
        ["User-Agent"] = "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36"
    }
}
local body = table.concat(res, " ")
print("HTTP result:", code)

Heck, I even modified LuaSocket's http module to not use string.lower on header keys to see if that would make any difference.
Unfortunately, this made no difference as you can guess. So, as usual, I don't know what to do.

So apparently newlines in the URL aren't the greatest thing to have. The latest commit should fix that.


None of the documentation samples run in Stackblitz

Bug, feature request, or proposal:
None of the documentation samples run in Stackblitz.
What is the expected behavior?
It should build and display in Stackblitz
What is the current behavior?
Stackblitz shows 'Bundling app' and just spins indefinitely
What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/uDmqyY
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
Open any of the doc samples in StackBlitz.
What is the use-case or motivation for changing an existing behavior?
The Documents are completely useless for real code examples if they don't work in StackBlitz
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Firefox 45.4, and I cannot upgrade it (corporate setting)
Is there anything else we should know?
They used to render right there on the Doc page.  Having to navigate away every time to see the resulting rendering was a poor design choice.  When this doesn't work, you have significantly degraded the usefulness of your documentation, which frankly is pretty thin to begin with.

Not sure what you're seeing but the examples are showing up for me on the docs site as well as correctly in stackblitz. Perhaps try doing a hard cache reset of your material.angular.io page? Can you try again in incognito?
Maybe there's a particular example that's breaking for you?


Often getting the error "Request limit exceeded." using AWS API. Is aws.max_retries the solution?

When deploying a CF installation on AWS, sometimes I hit the error AWS::EC2::Errors::RequestLimitExceeded Request limit exceeded..
In some portions of the code of this CPI, some calls are wrapped around a decorator which retries the requests, but there are several calls to the API that are not wrapped but that call the AWS api via the AWS sdk library used, specially when querying the existing state (e.g. listing AMI images).
In this PR the solution is wrap all the AWS client with some retry logic in the CPI code, but as said, there are several inexplicit calls to the API  that are not wrapped.
But I do think that the configuration max_entries can solve that. bosh-aws-cpi uses the AWS sdk v1 (latest version is v2), and reviewing the SDK code it seems the requests are retried by the library.
So, if using a higher value of aws.max_entries this issue can be solved, I suggest either increase the default value and/or document the issue and the setting, as the issue is really common. I also wonder if we need to wrap the code with Bosh::Common.retryable at all.
Error example:
D, [2016-01-12 09:53:13 #18310] [] DEBUG -- DirectorJobRunner: Renewing lock: lock:deployment:matt
D, [2016-01-12 09:53:13 #18310] [create_missing_vm(runner_z1, 0/1)] DEBUG -- DirectorJobRunner: External CPI got response: {"result":null,"error":{"type":"Unknown","message":"Request limit exceeded.","ok_to_retry":false},"log":"Rescued Unknown: Request limit exceeded.. backtrace: /var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:375:in `return_or_raise'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:476:in `client_request'\n(eval):3:in `describe_images'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:72:in `describe_call'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:56:in `get_resource'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/resource.rb:235:in `block (2 levels) in define_attribute_getter'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/cacheable.rb:63:in `retrieve_attribute'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:66:in `retrieve_attribute'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/resource.rb:235:in `block in define_attribute_getter'\n/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb:120:in `build_instance_params'\n/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb:81:in `create'\n/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:127:in `block in create_vm'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_common-1.3071.0/lib/common/thread_formatter.rb:49:in `with_thread_name'\n/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:122:in `create_vm'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `public_send'\n/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `run'\n/var/vcap/packages/bosh_aws_cpi/bin/aws_cpi:28:in `<main>'"}, err: I, [2016-01-12T09:53:10.833273 #18490]  INFO -- : [AWS EC2 200 0.134925 0 retries] describe_regions()

I, [2016-01-12T09:53:11.073708 #18490]  INFO -- : [AWS EC2 200 0.229609 0 retries] describe_images(:filters=>[{:name=>"image-id",:values=>["ami-8bf7c4fc"]}])

I, [2016-01-12T09:53:13.168565 #18490]  INFO -- : [AWS EC2 503 2.078879 2 retries] describe_images(:image_ids=>["ami-8bf7c4fc"]) AWS::EC2::Errors::RequestLimitExceeded Request limit exceeded.

E, [2016-01-12T09:53:13.169478 #18490] ERROR -- : Failed to create instance: Request limit exceeded.
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:375:in `return_or_raise'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:476:in `client_request'
(eval):3:in `describe_images'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:72:in `describe_call'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:56:in `get_resource'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/resource.rb:235:in `block (2 levels) in define_attribute_getter'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/cacheable.rb:63:in `retrieve_attribute'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:66:in `retrieve_attribute'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/resource.rb:235:in `block in define_attribute_getter'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb:120:in `build_instance_params'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb:81:in `create'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:127:in `block in create_vm'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_common-1.3071.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:122:in `create_vm'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `public_send'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `run'
/var/vcap/packages/bosh_aws_cpi/bin/aws_cpi:28:in `<main>'
, exit_status: pid 18483 exit 0
E, [2016-01-12 09:53:13 #18310] [create_missing_vm(runner_z1, 0/1)] ERROR -- DirectorJobRunner: error creating vm: Unknown CPI error 'Unknown' with message 'Request limit exceeded.'

I, [2016-01-12T09:53:13.333183 #18476]  INFO -- : [AWS EC2 503 2.252245 2 retries] describe_images(:filters=>[{:name=>"image-id",:values=>["ami-8bf7c4fc"]}]) AWS::EC2::Errors::RequestLimitExceeded Request limit exceeded.

, exit_status: pid 18463 exit 0
I, [2016-01-12 09:53:13 #18310] [create_missing_vm(runner_z1, 0/1)]  INFO -- DirectorJobRunner: Cleaning up the created VM due to an error: Unknown CPI error 'Unknown' with message 'Request limit exceeded.'
D, [2016-01-12 09:53:13 #18310] [] DEBUG -- DirectorJobRunner: Worker thread raised exception: Unknown CPI error 'Unknown' with message 'Request limit exceeded.' - /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3153.0/lib/cloud/external_cpi.rb:108:in `handle_error'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3153.0/lib/cloud/external_cpi.rb:89:in `invoke_cpi_method'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_cpi-1.3153.0/lib/cloud/external_cpi.rb:51:in `create_vm'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/vm_creator.rb:41:in `create'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/resource_pool_updater.rb:51:in `create_missing_vm'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/resource_pool_updater.rb:34:in `block (4 levels) in create_missing_vms'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3153.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/resource_pool_updater.rb:32:in `block (3 levels) in create_missing_vms'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/event_log.rb:97:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/event_log.rb:97:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/event_log.rb:50:in `track'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3153.0/lib/bosh/director/resource_pool_updater.rb:31:in `block (2 levels) in create_missing_vms'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3153.0/lib/common/thread_pool.rb:77:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3153.0/lib/common/thread_pool.rb:77:in `block (2 levels) in create_thread'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3153.0/lib/common/thread_pool.rb:63:in `loop'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3153.0/lib/common/thread_pool.rb:63:in `block in create_thread'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `call'
/var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'

Following some stacktraces, I identified these points where this error can raise:
https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/blob/master/src/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb#L121
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:375:in `return_or_raise'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:476:in `client_request'
(eval):3:in `describe_images'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:72:in `describe_call'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:56:in `get_resource'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/resource.rb:235:in `block (2 levels) in define_attribute_getter'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/cacheable.rb:63:in `retrieve_attribute'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/resource.rb:66:in `retrieve_attribute'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/resource.rb:235:in `block in define_attribute_getter'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb:120:in `build_instance_params'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/instance_manager.rb:81:in `create'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:127:in `block in create_vm'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_common-1.3071.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:122:in `create_vm'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `public_send'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `run'
/var/vcap/packages/bosh_aws_cpi/bin/aws_cpi:28:in `<main>'

https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/blob/master/src/bosh_aws_cpi/lib/cloud/aws/stemcell.rb#L9
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:375:in `return_or_raise'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/core/client.rb:476:in `client_request'
(eval):3:in `describe_images'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/aws-sdk-v1-1.60.2/lib/aws/ec2/image.rb:220:in `exists?'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/stemcell.rb:9:in `find'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/stemcell_finder.rb:8:in `find_by_region_and_id'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:124:in `block in create_vm'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_common-1.3071.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/bosh_aws_cpi/lib/cloud/aws/cloud.rb:122:in `create_vm'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `public_send'
/var/vcap/packages/bosh_aws_cpi/vendor/bundle/ruby/2.1.0/gems/bosh_cpi-1.3071.0/lib/bosh/cpi/cli.rb:71:in `run'
/var/vcap/packages/bosh_aws_cpi/bin/aws_cpi:28:in `<main>'

@keymon Did you have a chance to bump max_retries in your env? Did that eliminate number of errors for your deployment size?

@cppforlife to be sincere I had no time to do a test. I might get some time later today or tomorrow.
My idea was test it by creating 32x vms in parallel with a custom manifest and increasing the threads in bosh. That will likely trigger the rate limiting consistently.

I am trying to test this now, but bad luck, now I am not able to trigger the Rate limit from AWS :(
Anyway, just comment that although the CPI code does accept this configuration from the file cpi.json, the template that renders cpi.json and the spec do not include it. It is not documented either.

I was finally able to reproduce the Rate limit issue using a bigger box (m4.xlarge, the CPU was throttling me :smile: ), 64 threads and deploying 64 vms in parallel.
Note that I manually changed the file /var/vcap/jobs/aws_cpi/config/cpi.json in my bosh director, to include the config cloud.plugin.aws.properties.aws.max_retries as follows:
{"cloud":{"plugin":"aws","properties":{"aws":{"max_retries": 16, "credentials_source":"env_or_profile",

I tested it by setting it with values 0, 2 and 16.
With 0 I immediately get the Request Limit error. With 2 (the default) happens less often, but happens. Setting max_retries: 16  it manages to create all the VMs and I can see with bosh task X --debug that the CPI is retrying:
I, [2016-01-14T19:01:44.094289 #11148]  INFO -- : [AWS EC2 200 16.495747 5 retries] describe_instances(:instance_ids=>["i-82f1180a"])
I, [2016-01-14T19:02:22.088647 #11148]  INFO -- : [AWS EC2 200 35.992445 6 retries] describe_instances(:instance_ids=>["i-82f1180a"])
I, [2016-01-14T19:02:23.600540 #11033]  INFO -- : [AWS EC2 200 63.866485 7 retries] describe_instances(:instance_ids=>["i-2eff16a6"])
I, [2016-01-14T19:01:27.567377 #10805]  INFO -- : [AWS EC2 200 8.762974 4 retries] run_instances(:block_device_mappings=>[{:device_name=>"/dev/sdb",:ebs=>{:delete_on_termination=>true,:volume_size=>10,:volume_type=>"gp2"}}],:client_token=>"...",:image_id=>"ami-8bf7c4fc",:instance_type=>"m3.medium",:key_name=>"hector_key_pair",:max_count=>1,:min_count=>1,:placement=>{:availability_zone=>"eu-west-1a"},:private_ip_address=>"<IP_ADDRESS>",:security_group_ids=>["sg-5b63193f"],:subnet_id=>"subnet-64d5c101",:user_data=>"...")
I, [2016-01-14T19:01:44.195799 #10805]  INFO -- : [AWS EC2 200 16.627039 5 retries] describe_instances(:instance_ids=>["i-8df31a05"])
I, [2016-01-14T19:02:24.349135 #10805]  INFO -- : [AWS EC2 200 33.960596 6 retries] describe_instances(:instance_ids=>["i-8df31a05"])
I, [2016-01-14T19:02:29.452754 #10803]  INFO -- : [AWS EC2 200 68.826496 7 retries] describe_instances(:instance_ids=>["i-12f1189a"])
I, [2016-01-14T19:02:30.176219 #10803]  INFO -- : [AWS EC2 200 0.721453 1 retries] describe_addresses(:filters=>[{:name=>"instance-id",:values=>["i-12f1189a"]}])

We can do more testing, but seems worth it to invest some time.
Summarising:

The configuration aws.max_retries is consumed by aws-sdk-ruby to retry failed calls to the AWS API which are secure to retry, like the rate limiting ones.
Increase this value will solve the errors related to Rate limiting.

I suggest that the next steps are:

AWS CPI already configures such option if set in cpi.json
But it is not implemented in the release job template and spec.
The option requires some documentation.
We should revisit if the retry logic for the case of Rate limit errors at the CPI level is required at all.

@keymon thanks for details notes. we'll expose max_retries configuration and document it.

https://www.pivotaltracker.com/story/show/112949377

@cppforlife thank you.
There is a PR waiting exposing this variable, and it would be really easy to review: https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release/pull/23

Exposed max_retries in v44.

After a pair of weeks of usage, with max_retries=8, we confirm that the most of the errors disappeared and the situation improved a lot.
We still experience some issues, but when we are running several deployments in parallel with 32 threads in each deployment.
I suggest we close this issue.


Update ip-addresses.md

Due to a security incident, updating the IP addresses in Azure Public Cloud section to keeping the first row only. We came to know that several of them have been released back to the Azure pool and are at risk of being leaked.

@shyamala-l : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@bwren: I'm sorry - only the author of this article, @AaronMaxwell, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@shyamala-l Please note that these are not IP addresses, but rather IP address ranges.
Which IP address ranges were released back to the Azure pool? Where can I find information on this internally?
We risk breaking customer environments if they do not have the correct IP address ranges configured in their firewall settings.

Adding Gustavo/Naveen to provide more information on this.
From: Aaron Maxwell @.>
Sent: Friday, February 18, 2022 1:25 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Shyamala Lakshminarasimhan @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update ip-addresses.md (PR #88365)
@shyamala-lhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshyamala-l&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=OlLyArrCgsNbtKhVXhjuuNRxbsU3ywUkNi6GG2EKOV0%3D&reserved=0 Please note that these are not IP addresses, but rather IP address ranges.
Which IP address ranges were released back to the Azure pool? Where can I find information on this internally?
We risk breaking customer environments if they do not have the correct IP address ranges configured in their firewall settings.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F88365%23issuecomment-1045206539&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=XzOT76yK%2Fof5CeQnOrGrY3ODJB4kBx%2BIHtMAx%2B%2BCqvo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAX25BG7WVD5CHEEFJQT2MZ3U322JHANCNFSM5OY7VD2Q&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3ANolyqVSxGcNhLEt%2BAC70CZaLCKswcnTLE3jmc8r6k%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=WDQRX1k%2BnZpE%2BojEjGdyuJcu5atRSR%2FIexyqfeVWeRQ%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=hA1LLCbSW6LdXZIkZ6fAl%2F5W09KgExQhg%2B1H4G7BM3M%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@@.***>,
Can you please respond here when you are able to? The article update is waiting on this. Thanks!
-Shyamala
From: Shyamala Lakshminarasimhan
Sent: Friday, February 18, 2022 1:27 PM
To: MicrosoftDocs/azure-docs @.>; Gustavo Lima @.>; Naveen Dixit @.>; MicrosoftDocs/azure-docs @.>
Cc: Mention @.***>
Subject: RE: [MicrosoftDocs/azure-docs] Update ip-addresses.md (PR #88365)
Adding Gustavo/Naveen to provide more information on this.
From: Aaron Maxwell<EMAIL_ADDRESS>Sent: Friday, February 18, 2022 1:25 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Shyamala Lakshminarasimhan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update ip-addresses.md (PR #88365)
@shyamala-lhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshyamala-l&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=OlLyArrCgsNbtKhVXhjuuNRxbsU3ywUkNi6GG2EKOV0%3D&reserved=0 Please note that these are not IP addresses, but rather IP address ranges.
Which IP address ranges were released back to the Azure pool? Where can I find information on this internally?
We risk breaking customer environments if they do not have the correct IP address ranges configured in their firewall settings.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F88365%23issuecomment-1045206539&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=XzOT76yK%2Fof5CeQnOrGrY3ODJB4kBx%2BIHtMAx%2B%2BCqvo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAX25BG7WVD5CHEEFJQT2MZ3U322JHANCNFSM5OY7VD2Q&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3ANolyqVSxGcNhLEt%2BAC70CZaLCKswcnTLE3jmc8r6k%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=WDQRX1k%2BnZpE%2BojEjGdyuJcu5atRSR%2FIexyqfeVWeRQ%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|shyamala%40microsoft.com|36d48b4bcd93478077c908d9f3250fce|72f988bf86f141af91ab2d7cd011db47|1|0|637808162788204890|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=hA1LLCbSW6LdXZIkZ6fAl%2F5W09KgExQhg%2B1H4G7BM3M%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

#please-close

@AaronMaxwell Note that this pull request was merged to master February 18 with sign-off from content developer @bwren. The content is live, so closing the PR doesn't affect its published status. If you want different content to be published, you can create a new pull request to put through what you want to see merged. This is a public repository. Thanks.


🐛 [v4.0.0] Error: Cannot find module './expo-plugin/withVisionCamera'

What's happening?
Hi, I just installed the new beta version and got an issue while running npx expo install: Error: Cannot find module './expo-plugin/withVisionCamera'
It looks like the path in app.plugin.js isn't correct
Reproduceable Code
Error when installing the package

Relevant log output
Error: Cannot find module './expo-plugin/withVisionCamera'
Require stack:
- /Users/[...]/node_modules/react-native-vision-camera/app.plugin.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /Users/[...]/node_modules/@expo/cli/build/bin/cli
- /Users/[...]/node_modules/expo/bin/cli

Camera Device
No device

Device
No device
VisionCamera Version
v4.0.0-beta.19
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[X] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Just tested with the v4.0.0 and got the same error

fixed in 61ed5f16


Update README.md

Add text to make friendlier.

Thanks for the suggestion, but we're opting for simplicity.


Update translations from 10/26 English catalog

Based on english updated in #22770
Note, the first commit removes all of the commented file: line numbers.
See the second commit for the content changes.
% git diff --cached --numstat
335     12      locale/de/manageiq.po
332     12      locale/es/manageiq.po
342     18      locale/fr/manageiq.po
334     13      locale/it/manageiq.po
330     13      locale/ja/manageiq.po
330     13      locale/ko/manageiq.po
332     12      locale/pt_BR/manageiq.po
329     12      locale/zh_CN/manageiq.po
330     13      locale/zh_TW/manageiq.po

I'm going to try to see if I can manually delete these commented file/line number lines as a first commit and then apply the downloaded translations on top so the second commit can be reviewed separately.

The absolute KING of deletions 👑

Semi-related to https://github.com/ManageIQ/manageiq/pull/22217 - I'm still thinking we should just remove the file/line numbers from the .pot file as well.
Regardless, we definitely don't need them in the .po files, so I'm very 👍 on this PR

The absolute KING of deletions 👑
✂ ✂ ✂ 🔥 🔥 🔥 🗑 🗑 🗑

🤣 If only they were "real" deletions

Backported to quinteros in commit ada75bced232dfd67c04e3ff1128cf0bcd39e576.
commit ada75bced232dfd67c04e3ff1128cf0bcd39e576
Author: Jason Frey<EMAIL_ADDRESS>Date:   Wed Nov 8 13:11:25 2023 -0500

    Merge pull request #22781 from jrafanie/update_translations_10_26_after_22770

    Update translations from 10/26 English catalog

    (cherry picked from commit e2d7b1fefa1dcc5984a63f3f11b4f450ebc4182d)


Excel Formating

In Excel export i cant able to format the excel cells like headers with bold, coloring etc... And Another while exporting excel cells are merged how to set width of columns

There are a number of discussions on this topic in the DataTables forums.
Because the export is really just CSV there is no option to including colouring etc. It would require a lot of work to create a real Excel file that would support these options, and while I hope to do that in future, it likely isn't going to be for some time.


Hard to make an exclusion constraint for the routing

There is a common scenario when you would like to exclude some paths from the route. E.g. in a SPA app you generally want to map all the /api routes to controllers, and all other non static files to Home\Index so that client will handle the urls in the browser (e.g. angular). It can be done like that: "template: {*url}". Now the drawback is that e.g. lib/someCode.js will also fall for this route if the static file does not exist. So in case you have a problem you won't see a 404, but rather it will return your main view which is a bit weird. To avoid that situation we can exclude the routes that contain "." e.g. It is possible to do with regex, but that's not so efficient and regex is rather nontrivial to achieve it. So it will be good to have the exclusion constraint (maybe inclusion as well) that can apply simply.

@SteveSandersonMS has already built something like that here for exactly this purpose.
https://github.com/aspnet/NodeServices/blob/master/samples/angular/MusicStore/Startup.cs#L123
https://github.com/aspnet/NodeServices/blob/master/Microsoft.AspNet.SpaServices/SpaRouteConstraint.cs

Yes, I have built it like that as well myself, and wanted to make a pull request, but there were some legal issues with that, so it's not a problem for me to make, but I thought it would be beneficial to have that constraint in the framework itself.

The problem is not that there are no catch-all route, but in the fact that the catch-all route will return the default action for all the "would be" errors (like when you don't have a .js or .html file for example).


Whats the point of nginx now?

Hi, I use to build my projects on top of express.js and nginx. But after discovering this project and seeing that supports compression and SSL not sure if make sense to use nginx anymore. Is ok if I go only with uWebSockets.js or I can lose some features nginx have that uWs.js doesn't?

I can't answer what you should or shouldn't do. It's up to you.


Request: option to replace duplicate frames with interpolated ones instead of dropping them

Usually, duplicate frames in the input video do not represent an actual ceasing of motion in the canonical events that the video is portraying. Instead, they are typically an artifact of either the video having been reformatted from 24 or 25fps to 30, or an animation style that duplicates frames to cut costs. In both of these cases, an interpolated video will be smoother if the interpolation software recognizes these duplicate frames as placeholders. For example, suppose your input video has the following frames: A, B, C, C, D, etc.
If I understand correctly, the current default behaviour (doubling the framerate) will cause the following output:
In  Out
--------
A   A
    A-B
B   B
    B-C
C   C
    C
C   C
    C-D
D   D
etc.

And using the --skip flag will produce this instead:
In  Out
-------------
A   A
    A-B
B   B
    B-C
C   C
    C-D
C   D
etc.

That is, with --skip, duplicate frames are effectively cut from the input video—which shortens the video—before interpolation. This strikes me as...let's call it "extremely counter-intuitive"...from a user experience standpoint. I'm guessing that this flag was meant to only be used in tech demos, but the fact that it's the only even remotely intelligent way of handling duplicate frames gives the opposite impression. The intuitive behaviour would be to keep the duration the same but interpolate through the pair of duplicate frames, so the output would look like this:
In  Out
-------------
A   A
    A-B
B   B
    B-C
C   C
    C-(C-D)
C   C-D
    (C-D)-D
D   D
etc.

In other words, instead of the duplicate frame being cut, it is replaced with an interpolated frame, which is then interpolated with its neighbours as normal.
What I'm proposing is changing the default behaviour such that whenever a sequence of duplicate frames in the input video, with a length of exactly 2, is found, the second one is replaced with an interpolated frame before the main, framerate-increasing interpolation is done. This would cover the two main use cases that I mentioned up top. False-positives would be both rare and minimally harmful, but a user could disable the feature through command-line options. Perhaps an option called --dupes, with the possible values of keep (the current default), absorb (the new default that I'm proposing), and skip (equivalent to the --skip flag, which would in turn be deprecated).

I amsolutely second this.

I think your idea is great! I will realize it as soon as possible.

@awebeer256 I realize this new function, it looks amazing.

We have it in Flame version and it is one of the most useful things

Just to be clear, the removal of --skip breaks interpolation when there really are static frames and when paired with an fps change results in video that freezes on every static frame.

Isn't --exp=0 supposed to handle that?
#143

As a complement to this option, wouldn't be possible to add an option to replace predefined frames? Example: An anime scene where the background is cgi and moves in all frames but the foreground is animated at half of the fps. The user could replace the static frames with some very distinct and predefined image, and then use this image as an input parameter to the algorithm. This way, the algorithm would recognize the image among the frames and replace it with a new predicted frame.

An FPS selector for the video input would be useful and solve the problem. Then you would only have to choose 15 FPS and the video would be treated as having 15 FPS before then being interpolated by Flowframes.


feat: make cdn component optional

Motivation and Context

[ ] Tests or benchmark included
[ ] Documentation is changed or added on https://app.gitbook.com/
[ ] PR title must follow conventional-commit-standard

Closed. We will make CDN a requirement to deprecate soon the router config storage on the controlplane.


Error: Can't collect styles once you've called getStyleTags!

I am using this component "styled-components": "^2.1.1" in my VulcanJS app
This code is a server-side code:
import { ServerStyleSheet } from 'styled-components';

I am using the following code in my app
const sheet = new ServerStyleSheet();
console.log(sheet.getStyleTags())

sheet.getStyleTags() is generating the following error:
url:  /
I20171025-11:02:07.279(5.5)? [Error: Can't collect styles once you've called getStyleTags!]
W20171025-11:02:07.292(5.5)? (STDERR) Wed Oct 25 2017 11:02:07 GMT+0530 (IST) 'error while server-rendering' 'Error: Can\'t collect styles once you\'ve called getStyleTags!\n    at ServerStyleSheet.collectStyles (/home/deligence/1.Projects/Streetail/node_modules/styled-components/lib/models/ServerStyleSheet.js:116:28)\n    at generateSSRData (packages/vulcan:routing/lib/server/router.jsx:58:35)\n    at sendSSRHtml (packages/vulcan:routing/lib/server/router.jsx:87:45)\n    at packages/vulcan:routing/lib/server/router.jsx:149:11\n    at /home/deligence/1.Projects/Streetail/node_modules/react-router/lib/match.js:67:5\n    at /home/deligence/1.Projects/Streetail/node_modules/react-router/lib/createTransitionManager.js:108:11\n    at done (/home/deligence/1.Projects/Streetail/node_modules/react-router/lib/AsyncUtils.js:79:19)\n    at /home/deligence/1.Projects/Streetail/node_modules/react-router/lib/AsyncUtils.js:85:7\n    at getComponentsForRoute (/home/deligence/1.Projects/Streetail/node_modules/react-router/lib/getComponents.js:11:5)\n    at /home/deligence/1.Projects/Streetail/node_modules/react-router/lib/getComponents.js:35:5'

Here this is the complete code see the line no- 57 and 59

You have to call sheet.getStyleTags() after sheet.collectStyles(), then everything will work as expected.
This is the correct order:
https://github.com/VulcanJS/Vulcan/blob/06b681d36049e1397e3d698cad8b1ac78fd64ec7/packages/vulcan-routing/lib/server/router.jsx#L57-L59

Although, I am writing my sheet.collectStyles before styleTags I still encounter this issue.
`import React from 'react'
import ReactDOMServer from 'react-dom/server';
import { Provider } from 'react-redux';
import { ConnectedRouter } from 'react-router-redux';
import store from '../../src/store';
import {createMemoryHistory } from 'history';
import { StaticRouter } from 'react-router'
import App from '../../src/containers/app';
import { ServerStyleSheet } from 'styled-components'
const path = require('path');
const fs = require('fs');
const history = createMemoryHistory({
initialEntries: ['/', '/next', '/last'],
initialIndex: 0
});
const sheet = new ServerStyleSheet();
export default (req, res, next) => {
const filePath = path.resolve(__dirname, '..', '..', 'build', 'index.html');
fs.readFile(filePath, 'utf8', (err, htmlData) => {
if (err) {
console.error('err', err);
return res.status(404).end()
}
const body = ReactDOMServer.renderToString(
sheet.collectStyles(

)
);
const styleTags = sheet.getStyleTags();
var htmlData = htmlData.replace(
'',
${styleTags}
);
var htmlData = htmlData.replace(
'',

${body}

);
return res.send(htmlData);
});
}
`

@kushalmahajan You have to create a new ServerStyleSheet on every rerender.
Conceptually this is because internally we do store a lot of styles, but for each server-side render you only want the critical ones, the ones that have been used on the given component tree.

Okay. Worked!

Okay. One more issue -  some images are rendered as "Object object" in src.

@kushalmahajan That is probably a mistake in your code. Can you please avoid posting on old issues and create a new one instead? :wink:


Median base Q filter

make a filter and annotation based on the median base quality of bases supporting an alt allele.

While we're at it, I've noticed that median read mapping quality would also catch a few.

Closed by PR #996.


add a check in getMatches that prevents an "Undefined index" error

when getMatches is called on a not-crawler user agent

❤


Fix instructions for installing via helm

Essentially there is no proper instructions for installing this via helm inside of either Rancher or straight helm CLI, missing versions or mismatch named versions cause a failure of installation.
You also cannot add this repo via Rancher UI as it does not find any versions from the main repo URL
Related: #260

@txj-xyz what was the fix? I have this happening to me today when I run the "TLDR" command from the README with helm CLI. I don't understand what tech stand you're assuming for that command - what is "straight helm cli"?

@doteater I don't know if you managed to figure it out but you can get it going by passing the version string without the "netbox-" prefix. Example: helm pull oci://ghcr.io/netbox-community/netbox-chart/netbox --version 5.0.0-beta.61
Imho this should be made clear in the docs.


Type name t yields strange constructor function names

When the type is named t, the prefix is omitted:
type t = { has_2fa: bool; } [@@deriving of_yojson];;
type t = { has_2fa: bool; }
val of_yojson : Yojson.Safe.json -> [> `Error of bytes | `Ok of t ] = <fun>

OTOH, with a different name:
type f = { has_2fa: bool; } [@@deriving of_yojson];;
type f = { has_2fa : bool; }
val f_of_yojson : Yojson.Safe.json -> [> `Error of bytes | `Ok of f ] = <fun>

I'm not sure this is a bug, since it clearly targets the Module.t case, but maybe it could be somehow restricted. Or maybe just documented, since this looks useful, but is not mentioned in the readme.

Yeah, documentation would be nice.


NestJS v9?

Hi @sandeepsuvit. Found the library very useful. Thank you.
But it fails to install on the latest nestjs version because of peer dependency failure.
I tried locally on v9 and it works fine (without extensive testing). Maybe you just need to update the peer dependencies?

@manojchandrashekar thanks for writing in. The upgrade to v9 is complete. Please check the docs for installation instructions


Give access to default branch name as build variable

Our build task needs to do some logic based on the fact the current branch is the default branch of the repository.
https://github.com/SonarSource/sonar-scanner-vsts/blob/d4da541a858af9c9080c08a96e1bb2d41295c96d/common/ts/prepare-task.ts#L92
To get this information, I'm currently doing a REST call to VSTS APIs. This is not very efficient, not talking about the fact I need a token with correct permission, and only works for TfsGit repositories, while it should also be done for GitHub repositories (today I'm simply hardcoding that the default branch is 'master' for GitHub).
Could you consider adding a new build variable that would contain the name of the default branch of the repo (both for TfsGit and GitHub repositories)?

FYI this variable is available in some other CI providers, like CirrusCI: CIRRUS_DEFAULT_BRANCH ;)

This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days


ExtractConstructions no longer works since v11.13.0

Hi!
Since version v11.13.0 the following regex no longer matches results
	buildingCountdownMatch := regexp.MustCompile(`var restTimebuilding = (\d+) -`).FindSubmatch(pageHTML)
	...
	researchCountdownMatch := regexp.MustCompile(`var restTimeresearch = (\d+) -`).FindSubmatch(pageHTML)
	...
	lfBuildingCountdownMatch := regexp.MustCompile(`var restTimelfbuilding = (\d+) -`).FindSubmatch(pageHTML)
	...
	lfResearchCountdownMatch := regexp.MustCompile(`var restTimelfresearch = (\d+) -`).FindSubmatch(pageHTML)
        ...

I think they changed how it works with the new Mechas building queue
Thanks !

You can get the new regexp here
https://github.com/0xE232FE/ogame.mod/blob/9ed75aaf095ae7e3c7d31621531a3c6801dcadfd/pkg/extractor/v11_9_0/extracts.go#L195
Example
buildingCountdownMatch := regexp.MustCompile(`new CountdownTimer\('buildingCountdown', (\d+),`).FindSubmatch(pageHTML)```


Can't put cookie jar into a request

I tried doing something like this to use the cookies from a previous response in a subsequent request:
response = HTTP.get('http://www.example.com')
cookies = response.cookies
new_response = HTTP.get('http://www.example.com').cookies(cookies)

However, this does not work as expected because response.cookies is a HTTP::CookieJar and the chainable cookies method wants a Hash.
How do I do what I'm trying to achieve here? The documentation is sparse on this point.

Reusing a HTTP::CookieJar (automatically) between requests was something I had originally suggested in the form of an HTTP::Session type: #306
It looks like you're right though, HTTP::Options#cookies does not accept an HTTP::CookieJar as an argument, and probably should.

I ran into this when replacing some cURL-ing that had been done with the justification that it was easier to use cURL to maintain the session than using http.rb or other ruby http libraries. Here's the function I used:
def cookiejar_to_hash(jar)
  hash = {}
  jar.cookies.each do |cookie|
    hash[cookie.name] = cookie.value
  end
  hash
end

Allowing you to
response = HTTP.get('http://www.example.com')
cookies = cookiejar_to_hash(response.cookies)
new_response = HTTP.get('http://www.example.com').cookies(cookies)

@odinhb there's at least 1 http ruby library supporting it

We just landed #613 which adds support for it, but it isn't released


[patch] Send model defaults to wl-schema

Companion to https://github.com/balderdashy/waterline-schema/pull/63

@sailsbot thanks bud


Add migration documentation

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2804  👈
#2796
#2790
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Sicheng-Pan and the rest of your teammates on  Graphite

Had some issue with Graphite. Please checkout https://github.com/chroma-core/chroma/pull/2796 for the updated migration documents.


GEODE-5578 Create small docker image for meta-pipeline jobs

Meta pipeline hosts a job that creates an image used in the other jobs.
Resolves chicken/egg issue with create-images-pipeline and meta itself.
Fix version of concourse-pipeline resource type. Improve pause behavior for meta pipeline
Co-authored-by: Robert Houghton<EMAIL_ADDRESS>Co-authored-by: Finn Southerland<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@smgoller @metatype Can you review this? I want your take on the new image contents/dockerfile as well

Seems legit.


[WIP] Add Vuepress for docs publishing

See finished result at: https://lyra-proj.firebaseapp.com/

#25

I think this is a pretty good start, but it needs some more work, mostly fleshing out content.


Expecto interation causes "Error: Cannot ready 'substring' of null"

Any task I execute with ionide expecto causes an error.

Although everthing works the alert is annoying.
Do you know what it can be?

Can you please open developer console ( Help |> Toggle Developer Tools ) and check if there are any errors reported there?

Can you please try on 2.25.13


Can  "esp_adc_cal_characterize" configure ADC_UNIT1 with two attens? (IDFGH-9481)

Is your feature request related to a problem?
I am using two channels of ADC_UINT1,I want use ADC_ATTEN_DB_11 for one and ADC_ATTEN_DB_0 for the other.  But how to use "esp_adc_cal_characterize "to configure two attens?
Thanks !
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response

Hi, @casitelwithdean . Which chip and which idf version are you using? If you're using v4.4, you may refer to this, there you call this esp_adc_cal_characterize twice, with 2 different attens. Then you'll get two different set of characters. And when doing calibration, you just give the characters to esp_adc_cal_raw_to_voltage respectively.

I am using esp32s3wroom1   idf4.4.3
Thanks very much

Hi, @casitelwithdean . Which chip and which idf version are you using? If you're using v4.4, you may refer to this, there you call this esp_adc_cal_characterize twice, with 2 different attens. Then you'll get two different set of characters. And when doing calibration, you just give the characters to esp_adc_cal_raw_to_voltage respectively.
I am using esp32s3wroom1 idf4.4.3
Thanks very much


Fails when running istanbul report

When running npx istanbul report --dir coverage --include input/**/coverage-final.json lcov, it fails.
Could someone help me please.
E:\xxx>npx istanbul report --dir coverage --include input/**/coverage-final.json lcov
E:\xxx\node_modules\istanbul\lib\util\file-writer.js:66
    this.queue = async.queue(this.processFile.bind(this), 20);
                       ^

TypeError: async.queue is not a function
    at new AsyncFileWriter (E:\xxx\node_modules\istanbul\lib\util\file-writer.js:66:24)
    at new FileWriter (E:\xxx\node_modules\istanbul\lib\util\file-writer.js:134:51)
    at LcovOnlyReport.writeReport (E:\xxx\node_modules\istanbul\lib\report\lcovonly.js:91:42)
    at LcovReport.writeReport (E:\xxx\node_modules\istanbul\lib\report\lcov.js:54:19)
    at E:\xxx\node_modules\istanbul\lib\reporter.js:93:20
    at Array.forEach (<anonymous>)
    at Reporter.write (E:\xxx\node_modules\istanbul\lib\reporter.js:87:30)
    at E:\xxx\node_modules\istanbul\lib\command\report.js:113:22
    at E:\xxx\node_modules\istanbul\lib\util\file-matcher.js:39:20
    at f (E:\xxx\node_modules\once\once.js:25:25)

E:\xxx>npm list
<EMAIL_ADDRESS>| E:\xxx
| xxx
`--<EMAIL_ADDRESS>  | Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale
  | git://github.com/gotwarlost/istanbul.git
  | https://github.com/gotwarlost/istanbul#readme
  +--<EMAIL_ADDRESS>  |   Like ruby's abbrev module, but in js
  |<EMAIL_ADDRESS>  |   https://github.com/isaacs/abbrev-js#readme
  +--<EMAIL_ADDRESS>  |   2KB immutable date time library alternative to Moment.js with the same modern API
  |   git+https://github.com/iamkun/dayjs.git
  |   https://day.js.org
  +--<EMAIL_ADDRESS>  | | ECMAScript code generator
  | |<EMAIL_ADDRESS>  | | http://github.com/estools/escodegen
  | +--<EMAIL_ADDRESS>deduped
  | |   ECMAScript parsing infrastructure for multipurpose analysis
  | |   git+https://github.com/jquery/esprima.git
  | |   http://esprima.org
  | +--<EMAIL_ADDRESS>  | |   ECMAScript JS AST traversal functions
  | |<EMAIL_ADDRESS>  | |   https://github.com/estools/estraverse
  | +--<EMAIL_ADDRESS>  | |   utility box for ECMAScript language tools
  | |<EMAIL_ADDRESS>  | |   https://github.com/estools/esutils
  | +--<EMAIL_ADDRESS>  | | | option parsing and help generation
  | | | git://github.com/gkz/optionator.git
  | | | https://github.com/gkz/optionator
  | | +--<EMAIL_ADDRESS>  | | |   node's assert.deepEqual algorithm except for NaN being equal to NaN
  | | |<EMAIL_ADDRESS>  | | |   https://github.com/thlorenz/deep-is#readme
  | | +--<EMAIL_ADDRESS>  | | |   Efficient implementation of Levenshtein algorithm  with locale-specific collator support.
  | | |   git+https://github.com/hiddentao/fast-levenshtein.git
  | | |   https://github.com/hiddentao/fast-levenshtein#readme
  | | +--<EMAIL_ADDRESS>  | | | | Light ECMAScript (JavaScript) Value Notation - human written, concise, typed, flexible
  | | | | git://github.com/gkz/levn.git
  | | | | https://github.com/gkz/levn
  | | | +--<EMAIL_ADDRESS>deduped
  | | | |   prelude.ls is a functionally oriented utility library. It is powerful and flexible. Almost all of its functions are curried. It is written in, and is the recommended base library for, LiveScript.
  | | | |   git://github.com/gkz/prelude-ls.git
  | | | |   http://preludels.com
  | | | `--<EMAIL_ADDRESS>deduped
  | | |     type-check allows you to check the types of JavaScript values at runtime with a Haskell like type syntax.
  | | |     git://github.com/gkz/type-check.git
  | | |     https://github.com/gkz/type-check
  | | +--<EMAIL_ADDRESS>  | | |   prelude.ls is a functionally oriented utility library. It is powerful and flexible. Almost all of its functions are curried. It is written in, and is the recommended base library for, LiveScript.
  | | |   git://github.com/gkz/prelude-ls.git
  | | |   http://preludels.com
  | | +--<EMAIL_ADDRESS>  | | | | type-check allows you to check the types of JavaScript values at runtime with a Haskell like type syntax.
  | | | | git://github.com/gkz/type-check.git
  | | | | https://github.com/gkz/type-check
  | | | `--<EMAIL_ADDRESS>deduped
  | | |     prelude.ls is a functionally oriented utility library. It is powerful and flexible. Almost all of its functions are curried. It is written in, and is the recommended base library for, LiveScript.
  | | |     git://github.com/gkz/prelude-ls.git
  | | |     http://preludels.com
  | | `--<EMAIL_ADDRESS>  | |     Wrap words to a specified length.
  | |     git+https://github.com/jonschlinkert/word-wrap.git
  | |     https://github.com/jonschlinkert/word-wrap
  | `--<EMAIL_ADDRESS>  |   | Generates and consumes source maps
  |   |<EMAIL_ADDRESS>  |   | https://github.com/mozilla/source-map
  |   `--<EMAIL_ADDRESS>  |       Provide AMD's define() API for declaring modules in the AMD format
  |       git+https://github.com/jrburke/amdefine.git
  |       http://github.com/jrburke/amdefine
  +--<EMAIL_ADDRESS>  |   ECMAScript parsing infrastructure for multipurpose analysis
  |   git+https://github.com/jquery/esprima.git
  |   http://esprima.org
  +--<EMAIL_ADDRESS>  | | a little globber
  | | git://github.com/isaacs/node-glob.git
  | | https://github.com/isaacs/node-glob#readme
  | +--<EMAIL_ADDRESS>  | | | Add callbacks to requests in flight to avoid async duplication
  | | | git+https://github.com/npm/inflight.git
  | | | https://github.com/isaacs/inflight
  | | +--<EMAIL_ADDRESS>deduped
  | | |   Run a function exactly one time
  | | |   git://github.com/isaacs/once.git
  | | |   https://github.com/isaacs/once#readme
  | | `--<EMAIL_ADDRESS>deduped
  | |     Callback wrapping utility
  | |     git+https://github.com/npm/wrappy.git
  | |     https://github.com/npm/wrappy
  | +--<EMAIL_ADDRESS>  | |   Browser-friendly inheritance fully compatible with standard node.js inherits()
  | |   git://github.com/isaacs/inherits.git
  | |   https://github.com/isaacs/inherits#readme
  | +--<EMAIL_ADDRESS>  | | | a glob matcher in javascript
  | | | git://github.com/isaacs/minimatch.git
  | | | https://github.com/isaacs/minimatch#readme
  | | `--<EMAIL_ADDRESS>  | |   | Brace expansion as known from sh/bash
  | |   | git://github.com/juliangruber/brace-expansion.git
  | |   | https://github.com/juliangruber/brace-expansion
  | |   +--<EMAIL_ADDRESS>  | |   |   Match balanced character pairs, like "{" and "}"
  | |   |   git://github.com/juliangruber/balanced-match.git
  | |   |   https://github.com/juliangruber/balanced-match
  | |   `--<EMAIL_ADDRESS>  | |       concatenative mapdashery
  | |       git://github.com/substack/node-concat-map.git
  | |       https://github.com/substack/node-concat-map#readme
  | +--<EMAIL_ADDRESS>deduped
  | |   Run a function exactly one time
  | |   git://github.com/isaacs/once.git
  | |   https://github.com/isaacs/once#readme
  | `--<EMAIL_ADDRESS>  |     Node.js 0.12 path.isAbsolute() ponyfill
  |     git+https://github.com/sindresorhus/path-is-absolute.git
  |     https://github.com/sindresorhus/path-is-absolute#readme
  +--<EMAIL_ADDRESS>  | | Handlebars provides the power necessary to let you build semantic templates effectively with no frustration
  | | git+https://github.com/wycats/handlebars.js.git
  | | http://www.handlebarsjs.com/
  | +--<EMAIL_ADDRESS>  | |   parse argument options
  | |   git://github.com/minimistjs/minimist.git
  | |   https://github.com/minimistjs/minimist
  | +--<EMAIL_ADDRESS>  | |   Neo-Async is a drop-in replacement for Async, it almost fully covers its functionality and runs faster
  | |<EMAIL_ADDRESS>  | |   https://github.com/suguru03/neo-async
  | +--<EMAIL_ADDRESS>  | |   Generates and consumes source maps
  | |<EMAIL_ADDRESS>  | |   https://github.com/mozilla/source-map
  | +--<EMAIL_ADDRESS>  | |   JavaScript parser, mangler/compressor and beautifier toolkit
  | |   git+https://github.com/mishoo/UglifyJS.git
  | |   https://github.com/mishoo/UglifyJS#readme
  | `--<EMAIL_ADDRESS>deduped
  |     Wrap those words. Show them at what columns to start and stop.
  |     git://github.com/substack/node-wordwrap.git
  |     https://github.com/substack/node-wordwrap#readme
  +--<EMAIL_ADDRESS>  | | YAML 1.2 parser and serializer
  | | git+https://github.com/nodeca/js-yaml.git
  | | https://github.com/nodeca/js-yaml
  | +--<EMAIL_ADDRESS>  | | | Very powerful CLI arguments parser. Native port of argparse - python's options parsing library
  | | | git+https://github.com/nodeca/argparse.git
  | | | https://github.com/nodeca/argparse#readme
  | | `--<EMAIL_ADDRESS>  | |     JavaScript sprintf implementation
  | |     git+https://github.com/alexei/sprintf.js.git
  | |     https://github.com/alexei/sprintf.js#readme
  | `--<EMAIL_ADDRESS>  |     ECMAScript parsing infrastructure for multipurpose analysis
  |     git+https://github.com/jquery/esprima.git
  |     http://esprima.org
  +--<EMAIL_ADDRESS>  | | Recursively mkdir, like `mkdir -p`
  | | git+https://github.com/substack/node-mkdirp.git
  | | https://github.com/substack/node-mkdirp#readme
  | `--<EMAIL_ADDRESS>deduped
  |     parse argument options
  |     git://github.com/minimistjs/minimist.git
  |     https://github.com/minimistjs/minimist
  +--<EMAIL_ADDRESS>  | | Option parsing for Node, supporting types, shorthands, etc. Used by npm.
  | | git+https://github.com/npm/nopt.git
  | | https://github.com/npm/nopt#readme
  | `--<EMAIL_ADDRESS>deduped
  |     Like ruby's abbrev module, but in js
  |<EMAIL_ADDRESS>  |     https://github.com/isaacs/abbrev-js#readme
  +--<EMAIL_ADDRESS>  | | Run a function exactly one time
  | | git://github.com/isaacs/once.git
  | | https://github.com/isaacs/once#readme
  | `--<EMAIL_ADDRESS>  |     Callback wrapping utility
  |     git+https://github.com/npm/wrappy.git
  |     https://github.com/npm/wrappy
  +--<EMAIL_ADDRESS>  |   resolve like require.resolve() on behalf of files asynchronously and synchronously
  |   git://github.com/substack/node-resolve.git
  |   https://github.com/substack/node-resolve#readme
  +--<EMAIL_ADDRESS>  | | Detect whether a terminal supports color
  | | git+https://github.com/chalk/supports-color.git
  | | https://github.com/chalk/supports-color#readme
  | `--<EMAIL_ADDRESS>  |     Check if argv has a specific flag
  |     git+https://github.com/sindresorhus/has-flag.git
  |     https://github.com/sindresorhus/has-flag#readme
  +--<EMAIL_ADDRESS>  | | Like which(1) unix command. Find the first instance of an executable in the PATH.
  | | git://github.com/isaacs/node-which.git
  | | https://github.com/isaacs/node-which#readme
  | `--<EMAIL_ADDRESS>  |     Minimal module to check if a file is executable.
  |     git+https://github.com/isaacs/isexe.git
  |     https://github.com/isaacs/isexe#readme
  `--<EMAIL_ADDRESS>      Wrap those words. Show them at what columns to start and stop.
      git://github.com/substack/node-wordwrap.git
      https://github.com/substack/node-wordwrap#readme

After I Delete node_modules sub-directory in node_modules\istanbul, the problem's gone.


Updated README

After running the RADAR-Appserver locally, I have added a few changes in README which would assist anyone who would try to do the same in the future.

Thanks, Should I merge the branch now?

yes, please go ahead


Cherry-pick #392 to sdf10: Move list of debian dependencies to packages.apt

@scpeters , ok to rebase and merge?


[BUG] Mobile API: 'Login not available right now'

Describe the bug
After inserting phone number and selecting sms...
Failed to request registration code. Please try again.
{
reason: 'blocked',
status: 'fail',
login: '1956xxx',
custom_block_screen: {
title: 'Login not available right now',
hide_date: true,
btn_secondary_url: null,
btn_secondary_text: null,
btn_primary_url: 'https://wa.me/support',
btn_primary_text: 'Contact Us',
body: 'For security reasons, we can’t log you in right now. Please try again later, or contact us if you need help with your account.'
}
}
To Reproduce
run: yarn example --mobile
Expected behavior
Receiving SMS
Environment (please complete the following information):
Tested with multiple numbers
Tested with 6.5 and 6.6

any update on this?

I also encountered this problem, did you solve it? @lauriolasw


Expose some newly added parameters in Whisper

Recently whisper added some new parameters --highlight_words, --max_line_width and --max_line_count, openai/whisper@43940fc9780cb91c4f94899755b4648e19d7b977 , these could be quite useful. Would it be possible to expose these parameters as well?

These new parameters are used when saving the segments to file, which is currently not in the scope of the faster-whisper library.
Maybe you can request these parameters in this CLI interface whisper-ctranslate2 which is built on top of faster-whisper?

These new parameters are used when saving the segments to file, which is currently not in the scope of the faster-whisper library.
Maybe you can request these parameters in this CLI interface whisper-ctranslate2 which is built on top of faster-whisper?

I saw this is completed on their end, is this something that can be added here?
https://github.com/Softcatala/whisper-ctranslate2/issues/24


Livestream tile/list: show viewer count if data is available

Update viewersById after fetching active livestreams

viewersById is usually updated by websocket, but since we have the latest data, might as well use it.

Livestream tile/list: show viewer count if data is available

As of this commit, only the Channel Page is fetching the data through the new API, which has the viewer count correctly populated.
For both "0" and "undefined", continue to show as "LIVE".

Test: kp
Ticket: #16
Known issue

Thumbnail flickers when when there is an update.  Probably need to memo the sibling component somebody.

Woohoo! Can't wait to have this everywhere. Once we're fully migrated, we can also sort wild west by it.


[Enhancement] Upgrade broker's oss-sdk from aliyunsdk-2.7.2 to jindosdk-4.6.2

Signed-off-by: xyz<EMAIL_ADDRESS>What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

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

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

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch
[x] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_admit_test

@Mergifyio backport branch-2.5


How to emphasize on the structure?

Thank you for this great work.  I learned a lot of insights of alphafold from openfold paper.
I am predicting antibody-antigen complex.  In my case,  I already know the structure of Ab-Ag complex, I generated some mutants from this Ab-Ag(say <10 mutations in CDR), now I want to predict the structures of mutants.  I found alphafold doesn't use template, because the output structure of alphafold is far away from template.  I searched the options in run_pretrained_openfold.py, I didn't find such option to make openfold to emphasize on template?  I wonder if you have a way to emphasize on initial pair-embedding when pair-embedding and single embedding are merged.
Thanks in advance

I found thread_sequence.py,  I am not sure if it is the right tool for my mutants prediction.  I read the code of thread_sequence.py,  I didn't figure out how runmodel method emphasizes on template,  I must miss something.


Updating example and tests

Suggest using switchboard.rtc.io for the example. Testing failed for datachannel closing. The member function 'readyState' prompted a node segfault, changed to 'close' and testing works fine.

Cool thanks John :)


feat(table_parser): clean up, add unit tests

extends https://github.com/alphanome-ai/sec-parser/pull/46


Breaking change for razor

Contributes to https://github.com/aspnet/Announcements/issues/459. Related to dotnet/aspnetcore.docs#22010.
Internal preview.

There are more changes too. I was planning on putting them in the Migrate from ASP.NET Core 5.0 to 6.0. One I do that, I'll update this doc.  Here's an outline
Changes to the ASP.NET Core Razor SDK
The Razor compiler in .NET 6 leverages the new source generators feature to generated compiled C# files from the Razor views and pages in a document. In previous versions:

The compilation relied on an individual RazorGenerate and RazorCompile target to produce the generated code. These targets are no longer valid. In .NET 6, both code generation and compilation are supported by a single call to the compiler.
A separate Razor assembly was generated that contained the compiled view types in an application. This behavior has been deprecated and a single assembly is produced that contains both the app types and the generated views.

Remove all the targets listed under Targets. Users can continue to use RazorComponentGenerateDependsOn to do things that need to happen before the build runs.
Under "Properties" add the EmitCompilerGeneratedFiles property to the table. For description, we can say "When set to true, it writes the generated source files to disk. Useful when debugging buggy behavior in the compiler. false by default."
Under "Properties", remove the following properties from the table as they are no longer applicable with the single-step compilation model.

RazorTargetAssemblyAttribute
RazorTargetName
EnableDefaultRazorTargetAssemblyInfoAttributes
UseRazorBuildServer


Exports/Imports multiple members in a line

This module export code
module A
  ( Element, none, text, el
  , row, wrappedRow, column
  )

will be formated:
module A
  ( Element
  , none
  , text
  , el
  , row
  , wrappedRow
  , column
  )

I think it should be possible to allow keeping members in one line, usually they are related members, such exports layout is used to make it more explanatory and more compact. The same can be applied for imports. Maybe this should be not a default behaviour but some additional wrapping mode.

Closing as I do not intend to support this.


decorators in code blocks are being treated as tags

Given this doc:
/**
 * Some Description
 *
 * ```
 * @RouteConfig([
 *   { path: '/about', component: AboutComponent, name: 'About' }
 * ])
 * ```
 */

Output looks like this:

I fixed it for now by inserting invisible space after the @ sign.
http://www.fileformat.info/info/unicode/char/200B/browsertest.htm

I encountered this behavior too.
The comment parser should not be looking for doc tags inside the code block maybe?

Related to #97

Should be fixed when #633 is released


response.body.charStream not ready

Hello,
Please accept my apologies if this is simply user error!
I need to write the response body as a character stream to a PrintWriter. With this
try (BufferedReader streamReader = new BufferedReader(response.body().charStream())) {
  while (streamReader.ready()) {
    writer.println(streamReader.readLine());
  }
}

I receive HTTP 1.1 OK response with body content but streamReader.ready() never returns true.  A workaround is to check streamReader.readLine() != null.
https://github.com/heuermh/ensembl-mart-runner/blob/main/src/main/java/com/github/heuermh/ensemblmartrunner/EnsemblMartRunner.java#L106
To reproduce
$ git clone https://github.com/heuermh/ensembl-mart-runner.git
$ mvn package

# short response
$ ./target/appassembler/bin/ensembl-mart-runner \
  -i src/test/resources/hla-a.mart-query.xml \
  -o hla-a.txt

# long response
$ ./target/appassembler/bin/ensembl-mart-runner \
  -i src/test/resources/hgnc-mapping.mart-query.xml \
  -o hgnc-mapping.txt

I believe this is consistent with how BufferedReader is designed. If you want to make it easy on yourself, consider reading lines with Okio’s BufferedSource instead.
try (BufferedSource source = response.body().source()) {
  for (String line; (line = source.readUtf8Line()) != null; ) {
    writer.println(line);
  }
}

Thank you for the quick reply, @swankjesse!  okio.BufferedSource works great.


Incorrectly filed page

This page is incorrectly located in the navigation hierarchy.

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

ID: ac6f1da6-aeea-1f1e-1a97-3260c8d4db1b
Version Independent ID: 0ac78ce5-331d-a4c8-08e7-43e37c52189e
Content: Change Data Capture and Other SQL Server Features - SQL Server
Content Source: docs/relational-databases/track-changes/change-data-capture-and-other-sql-server-features.md
Product: sql
Technology: ****
GitHub Login: @rothja
Microsoft Alias: jroth

@sardarw -- thank you for your feedback.  I am updating this article.

@sardarw -- thank you for your feedback.  I am updating this article.

@sardarw -- thank you for your feedback.  I am updating this article.

@sardarw -- thank you for your feedback.  I am updating this article.

Thank you again for your feedback.  I have updated the documentation and it should be live by tomorrow.

Thank you again for your feedback.  I have updated the documentation and it should be live by tomorrow.


ACNA-324 - Support package binding through deploy command

Is your feature request related to a problem? Please describe.
Support package binding through deploy command
Describe the solution you'd like
manifest.yml should have the following structure for a package binding
packages:
adobe-oauth:
dependencies:
# binding to shared oauth package
myauthp-shared:
location: /adobeio/oauth

ACNA-336 is a dupe of ACNA-324.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1184489). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage        ?   96.59%
=======================================
  Files           ?        9
  Lines           ?      176
  Branches        ?       15
=======================================
  Hits            ?      170
  Misses          ?        6
  Partials        ?        0

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 1184489...26091ed. Read the comment docs.


Can't access Application Class from lib to feature or login Module

First thanks for this template, but i want't to access the Custom Application class from the module but i am not able to do so, can u please help me to go through it.

@TheReprator You shouldn't be able to access app from feature/lib modules in this pattern. Can you give me the exact reason for it, maybe I can suggest a better way.


SPEC: Indicate automatic time out is only for Active LRA.

The main parts around the time out functionality in the spec

The business logic may wish to control how long an LRA should remain active
for before it becomes eligible for automatic cancellation by providing values
for the timeLimit and timeUnit element of the @LRA annotation.

But imagine following scenario

LRA starts with timeout of 1 sec

Participant A joins LRA with end=false

Participant B joins LRA with end=true

@Complete callbacks of Participant A and B are called.

Participant A @Complete replies with Compensating

Participant B @Complete replies with Compensated

Participant A @Complete should be called again to get final outcome

But before this second call to Participant A @Complete is performed, the timeout is reached and thus LRA should be cancelled?
Main problem here is that Participant B is not even aware of the LRA anymore since it can forget about the LRA besides the fact that Participant A and B could first receive event Complete and later on Compensate.
So best is to explicitly define that only an Active LRA can be automatically cancelled.

Isn't "The business logic may wish to control how long an LRA should remain active" stating that timeout is ignored when the LRA is no longer active? Which is the case in your example, because when participant B uses end = true, LRA transitions from Active state to one of the Completing or Canceling states. However, if you think this needs to be formulated differently I am not opposed :)

Yeah maybe this is slight play in words, you are correct @xstefank.
In my head I have a difference between Active state and active (not having a final state)

In any case, I see no harm in clarifying this more if there might be any kind of possible misinterpretation.

But before this second call to Participant A @complete is performed, the timeout is reached and thus LRA should be cancelled?

The LRA protocol is designed to guarantee atomic outcomes - therefore if the decision is to close the LRA all participants are told to complete (none will ever be asked to compensate). And vice versa if the LRA is cancelled (due to a timeout or otherwise).
In the outlined scenario:

Participant A @complete replies with Compensating

This would imply that A did the wrong thing and moves to the state FailedToComplete. The only legal call after this is to be told to Forget about the LRA.

So best is to explicitly define that only an Active LRA can be automatically cancelled.

"When the time limit is reached the LRA is cancelled". The only valid transition (according to the state model) to the Cancelled state is from the Active state. Therefore it is implicit that cancelling an LRA can only happen if it is already Active.

Main problem here is that Participant B is not even aware of the LRA anymore since it can forget about the LRA besides the fact that Participant A and B could first receive event Complete and later on Compensate.

So it is not a problem since B did the correct thing.
Also, receiving both events would be illegal - a participant can never received Complete and later on Compensate since that would break the "all" part of the "all or nothing" (atomicity) guarantee.

Yes, my example has an error, it should be

Participant A @complete replies with Completing

anyway, we are on the same page.

The LRA protocol is designed to guarantee atomic outcomes - therefore if the decision is to close the LRA all participants are told to complete (none will ever be asked to compensate).

So that was the reason for to explicitly mention LRA with Status Active.
Since for me an active LRA is not the same as an LRA with status Active.
But since I'm the only one and probably most people read the spec text correct, I'm closing this one.


Waypoints aren't consistent on realms

Hi there, I've noticed that CList uses the server IP to save all coord info, and on realms the IP changes whenever the server shutsdown.
Is there a way to add support for realms where it's based off the realms name, or maybe a always on option?

I hopefully fixed it and the fix will be available in the next update.


Missing hints in the IDE

Environment
Knex version: 0.95.2
OS: Windows 10
Bug
After the last update, I lost the hints in my IDE. On version 0.21.15, they were.

0.95.2

0.21.15

@kur4ch I'm open to doing non-breaking adjustments on knex side that would result in hints being restored. Can you try doing changes to knex locally and see what brings hints back? Technically speaking, index.d.ts should still work, as default export is the knex builder function, so I am confused as to why IDE wouldn't catch that properly, if TypeScript does.

Hope this help but I can still get code recommendation importing knex like this:

Version: 0.95.7
works on both Window 10 and  WLS2 Ubuntu 20.04


Support for Editions

Hi @PetteriAimonen  - are you planning to support "Protobuf Editions" as described in https://protobuf.dev/news/2023-06-29 within nanopb? A tool, prototiller, is being provided as a way to migrate the protobuf files themselves (https://protobuf.dev/editions/overview/#prototiller). Are the converted .proto files going to work with nanopb?

I have no idea - it seems there is pretty little information available, especially on how the "editions" will affect the output format from protoc to language generators.

Thanks for the insight, we'll take a "wait and see" approach.
Feel free to close out this issue, or keep it open if you feel "editions" will need a correlated issue.

Thanks for the insight, we'll take a "wait and see" approach.
Feel free to close out this issue, or keep it open if you feel "editions" will need a correlated issue.

My expectation is that most of the changes will be handled by protoc and are not be visible to nanopb generator.
But yeah, if anyone finds specific issues, feel free to reopen or add a separate issue.

Hey Petteri,
We do have some documentation on this now: https://protobuf.dev/editions/implementation/.    Protoc does handle large parts of the work, but at least your generator (which doesn't use our C++ plugin infrastructure) will need some additional support.


FIDO Key in Safari on iOS Support

Using iOS 16.5, in Safari a security key is offered as an authentication method.
Ist this officially supported? The docs aren't stating this as an supported scenario.
Using Edge on the same device, there is no security key offered.

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

ID: 5c860853-d58e-ba80-9cd4-04d33e1dd2e2
Version Independent ID: 5ff539d2-5826-4de1-6d93-55b95a7b041c
Content: Browser support of FIDO2 passwordless authentication - Microsoft Entra
Content Source: articles/active-directory/authentication/fido2-compatibility.md
Service: active-directory
Sub-service: authentication
GitHub Login: @janicericketts
Microsoft Alias: jricketts

@arpsga
Thanks for your feedback! We will investigate and update as appropriate.

Hi @arpsga
Please go through this below link for your reference. It might be helpful.
https://learn.microsoft.com/en-us/azure/active-directory/authentication/concept-certificate-based-authentication-mobile-ios

@arpsga
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#please-close

@Naveenommi-MSFT
Thank you for stating the link!
I attach a screenshot of my view on a sign-in using safari on a iphone.
It will offer me security keys as an option. "Use a certificate or smart card" isn't offered there.
Could you please clarifiy if using FIDO security keys on iOS safari is supported? As I'm able to use this option but the documentation states this as an unsupported scenario.

@janicericketts
Could you please review add comments on this, update as appropriate.


Question: Permissions not defined

I have renamed "Permission" class to "Permissions"
 class Permissions:     FOLLOW = 0x01     COMMENT = 0x02     WRITE_ARTICLES = 0x04     MODERATE_COMMENTS = 0x08     ADMINISTER = 0x80
and I didn't face any problem when using that name in python files, however when I used it in "index" for post editor rendering :
{% if current_user.can(Permissions.WRITE_ARTICLES) %}         {{ wtf.quick_form(form) }}         {% endif %}
it gave me error in jinja2 Permissions not defined !! I just tried to change the "Permissions" in the "index" to "Permission" and it worked well !!! , how can that be possible since I have it as "Permissions" in class definition!! ?
Book chapter 11
Thanks

Did you inject the new class through a context processor? That's what makes the class available to templates. See this: https://github.com/miguelgrinberg/flasky/blob/13b747fb965785b5445796eeb99b4cfefc4c6778/app/main/init.py#L11.

Aha yes yes, so this context processor injection allow what I pass ( class ) to be available for the templates isn't it ?

Correct.

Thanks