Is it possible to make this chart scroll horizontally?

What do you mean exactly with "scroll horizontally"? Panning? Programmatically? etc

Yes panning

https://github.com/i-schuetz/SwiftCharts/wiki/View-hierarchy-and-transforms#making-the-chart-scrollable


MDX Sanitizer Technical Design

Feature technical design
Summary
Describe the new feature from a technical perspective.
Describe how it integrates/relates/communicates with existing features/packages/services.
Describe the problem solved by this feature.
Currently remotely loaded MDX pages might error out or break the application for a number of reasons:

Component used that is not recognized by the platform (regardless of whether or not it has a corresponding import)
An import (or export) statement being used (we don't allow any)
A usage of an imported value someplace in the mdx
Inline styles that are strings instead of objects
Inclusion of HTML comments
General Markdown parsing errors

The idea is to catch these occurrences and handle them before they get to the top-level and error out.
Create a [PRIVATE] "MdxSanitizer" package that exports a plugin that can be injected into the mdx parser, receive the AST information when called and look for the various unsupported code and errors and handling in the following way:

Replace Unknown Components with "UnknownComponent notification"
- (will need list of HTMLTags to ignore: https://github.com/carbon-design-system/carbon-platform/blob/b0fc88e7de39623d667819732008b3f122a0ed9a/packages/mdx-sanitizer/src/main/html-tags.mjs)
- will need to receive list of supported custom component keys
- Will need list of supported components to link out to

Imports/Exports -> Replace entire tree with the "Unsupported Imported/Export Component notification"

If unable to parse stringified mdx source, show "ParsingError" Component

The package will also export a "sanitizeStringMdxSource" function that will:

Remove HTML Comments
- we have to do this BEFORE parsing, otherwise it breaks

 // remove HTML comments  sanitizedUsageFileSource = usageFileSource.replace(/<!--(.|\n)*?-->/g, '')

This package will be used from the web-app service to obtain a "sanitized" version of the remotely-retrieved mdxSource before rendering.
Lastly, if for any reason the parsed MDX cannot be successfully rendered in the web app UI, this error shall be caught and replaced by a "FullPageError" component:

Research

[x] Approved?

Unanswered questions

Will we actually be able to catch the rendering error and swap it?
Do we use regex to remove HTML comments? or is there another option?
List of components to link out to: link out to storybook? in-web-app page? .md docs? - Link to Storybook
What should we show if unable to retrieve content from github?

New technologies
  - For MDX parsing and tapping into the AST tree:
          - @mdx-js/mdx
-  mdast-util-mdx-jsx: types
- mdast-util-mdxjs-esm: types
- remark: *might not need this
- remark-mdx: needed to parse strings into MDAST, will be needed for testing
- remark-parse: needed Parse strings into MDAST, will be needed for testing
- unified: used to power remark (remark-mdx, remark-parse)
- unist-util-remove:  Remove nodes from tree that meet certain criteria (specific components, specific attributes...)
- unist-util-visit: Find nodes in tree that meet certain criteria (specific components, specific attributes...)

Proofs of concept
  - Working POC with slightly different behavior: https://github.com/carbon-design-system/carbon-platform/pull/740

UI/UX design

[x] Approved?

Designs for error handling and AST conversion: https://www.figma.com/file/WyfqQh9R1VXYZErfmsNDVH/MDX-errors?node-id=0%3A1

TBD: What should we show if unable to retrieve content from github? - Fullpage error

APIs

[x] Approved?

Programmatic APIs
  - List any APIs that will be developed and made available in the @carbon-platform/api package,
    including function/class/method names, parameters, and return values.
--

@carbon-platform/api/mdx-sanitizer
Exports:

mdxSanitizerPlugin(customComponentsKeys): Function (mdxPlugin type)
sanitizeStringMdxSource(string): string

Data graph
  - N/A, eventually the github function that retrieves the mdx source probably moves onto a data-graph microservice but that is out of scope for this issue.

Messages
  - N/A

Security

[x] Approved?

What new data is created/stored/collected/transmitted by this feature? How is that data secured? Who
is allowed to access it? How is that access controlled?
Think like a hacker. How might someone attempt to break or abuse this feature?

Imports and exports are an mdx security concern but we're already covering for that by not allowing and stopping MDX parsing full out when we find them
inline scripts: Confirmed with https://github.com/francinelucca/mdx-testing/blob/main/test-sec.mdx that scripts can be passed to the remote MDX file and will be triggered in the app, what should we do to prevent this? Probably replace entire tree with "scripts are not supported error" or something similar?

Error handling

[x] Approved?

Ignore the happy path. What can go wrong with this feature? How will the error conditions manifest
through the APIs? How will users be informed about these errors?

Parsing error - handled
Full page error - handled
Failure to retrieve remote mdx contents: Need a design for this (NotFound, or whatever error)

Test strategy

[x] Approved?

How will the new feature be tested? (e.g. unit tests, manual verification, automated e2e testing,
etc.)
What interesting edge cases should be considered and tested?
Will use monorepo's standard unit testing library, 'ava'. Will have mdx local files inside package to test against various use-cases:

Mdx with no errors (should stay exactly the same)
Mdx with Custom (supported) component
Mdx with Unknown component
Mdx with Exports
Mdx with Imports
Mdx with parsing error
Mdx with HTML comments
Mdx with script tag

Parse remote files into MDAST, use mdxSanitizer to "sanitize" content, then manually "visit" the resulting tree to confirm what was expected to be added/removed happened successfully
Logging

[x] Approved?

Detail any FFDC data (info, warning, error, debug logs) to be captured by this feature.

These "error" cases are considered to be fairly common and can mostly be solved by the user so we'd want to steer away from filling our logs with them.
For FullPageError when parsed mdx can't be rendered due to an error, log a "warning" message in case we need to track special cases.

File and code layout

[x] Approved?

Describe how the files and code for this feature will fit into the rest of the mono repo. Will there
be a new package/service? Are there existing files/directories in which the new logic should live?

packages/api/mdx-sanitizer
/src/
-main/
-html-tags.js
-mdx-sanitizer-plugin.js
-index.js
-utils
-test/
-mdx-sanitizer-plugin.test.js
test-files/*

-services/web-app/utils/mdx <- will be used to create a function that will generate the parser that injects and consumes the plugin (this logic needs to be taken out of github.js in the web-app)
Issue and work breakdown

[x] Approved?

List any issues that should be created prior to starting work on this feature

Epics
  - Mdx Sanitizer
Issues
  - Unit Test Remote MDX Sanitizer Plugin: https://github.com/carbon-design-system/carbon-platform/issues/752
  - Close: Scrub remote MDX content to remove imports and unsupported MDX components https://github.com/carbon-design-system/carbon-platform/issues/692
Create components: FullPageError(Render, Parsing), InlineError (Imports/Exports, UnknownComponent)
Create MdxSanitizerPackage
Design: "we couldn't retrieve this" UI (Failure to retrieve remote mdx contents, 404, 500...)
Design: inline error - remove script tags

Create a [PRIVATE] "MdxSanitizer" package

Why private? Why not let the world potentially benefit from it as well? 😄

I'm still not sold on this as a solution to comments breaking the parsing. I'd like to see some exploration in this area with a few options before we decide on this as the approach. Ideally, this plugin would be a one-stop-shop for sanitizing input MDX with no additional calls needed.
Some ideas to try/questions to answer:

Has anyone already solved this problem when parsing MDX in another plugin or package?
Is there a different plugin "hook" that allows some level of pre-parsing?
Would it make sense to do two separate parsing passes; one that's for standard markdown (where HTML comments should be valid) and a second for MDX?

Feature technical design
Summary

Describe the new feature from a technical perspective.

Describe the problem solved by this feature.

Describe how it integrates/relates/communicates with existing features/packages/services.

Currently remotely loaded MDX pages might error out or break the application for a number of reasons:

Component used that is not recognized by the platform (regardless of whether or not it has a corresponding import)
An import (or export) statement being used (we don't allow any)
A usage of an imported value someplace in the mdx
Inline styles that are strings instead of objects
Inclusion of HTML comments
General Markdown parsing errors
The idea is to catch these occurrences and handle them before they get to the top-level and error out.

Expected Solution Behavior:
1 - Unknown Components have to be swapped out with an inline error:

2 - Imports and Exports statements will replace the entire content with a Full Page Error:

3 - MDX files with HTML comments have to be able to render
4 - Script tags cannot be executed. Instead, an inline error notification will be rendered to display information on it along with a code snipped containing the script code. The rest of the mdx content should be able to render

5 - If an error occurs when trying to serialize MDX content other than the ones outlined above, display a "Error compiling MDX" inline error:

6 - If a React error occurs when trying to render parsed MDX content, display a "Content not rendering" inline error:

7 - If there's an error attempting to retrieve the MDX content from github, display a full page "The page you're looking for cannot be found" information

Solution
Create a [PUBLIC] "MdxSanitizer" package that exports an unified attacher that can be injected into the mdx processor, this attacher will be thorough enough to cover all of platform's use cases but be general enough that can still be valuable for projects outside of the carbon ecosystem to use.
The attacher will:

Receive a config param object including:

customComponentKeys: array of allowed custom component keys, defaults to []
fallbackComponent: component that will replace the content when a component that isn't allowed is identified, defaults to undefined
allowImports: whether import statements should be allowed in parsed mdx content, default to true
allowExports: whether export statements should be allowed in parsed mdx content, defaults to true
stripHTMLComments: whether HTML comments should be removed from parsed mdx content, defaults to true
tagReplacements: object containing entries of html or component tags that should be replaced, accompanied by a replace function that returns the content these tags should be replaced with, defaults to {}

Rewrite the processor "parse" function to remove comments for the string mdx source, using the html-comment-regex lib

Return a transformer function that will:

Research

[ ] Approved?

Unanswered questions

List any unknowns and unanswered questions that need answers prior to beginning development.

New technologies

List new technologies that need to be explored in detail before beginning development.

Proofs of concept

List proofs of concept that need to be completed before beginning development.

UI/UX design

[ ] Approved?

Does this feature have any associated UI/UX? If so, describe any design that needs to be
completed/red-lined prior to development.

APIs

[ ] Approved?

Programmatic APIs

List any APIs that will be developed and made available in the @carbon-platform/api package,
including function/class/method names, parameters, and return values.

Data graph

List any new query resolvers and/or data models being included in the data-graph and/or data-graph
API package.

Messages

List any new/changed RabbitMQ messages introduced by this feature, the message payload structure
associated with them, whether they are queries or emits, and their expected return values (for
queries).

Security

[ ] Approved?

What new data is created/stored/collected/transmitted by this feature? How is that data secured?
Who is allowed to access it? How is that access controlled?

Think like a hacker. How might someone attempt to break or abuse this feature?

Error handling

[ ] Approved?

Ignore the happy path. What can go wrong with this feature? How will the error conditions manifest
through the APIs? How will users be informed about these errors?

Test strategy

[ ] Approved?

How will the new feature be tested? (e.g. unit tests, manual verification, automated e2e testing,
etc.)

What interesting edge cases should be considered and tested?

Logging

[ ] Approved?

Detail any FFDC data (info, warning, error, debug logs) to be captured by this feature.

File and code layout

[ ] Approved?

Describe how the files and code for this feature will fit into the rest of the mono repo. Will
there be a new package/service? Are there existing files/directories in which the new logic should
live?

Issue and work breakdown

[ ] Approved?

List any issues that should be created prior to starting work on this feature.

Epics

[ ]

Issues

[ ]


Path doesn't exist error while streaming from Delta table in Azure Data Lake Gen2

While evaluating delta for streaming use case, I came across the following issue.
Data flow:
1. Rate data to kafka:
val df = spark.readStream.format("rate").option("rowsPerSecond", 10).option("numPartitions", 1).load().selectExpr("to_json(named_struct('timestamp',timestamp,'value',value)) as value")
df.writeStream.format("kafka").option("kafka.bootstrap.servers","***:9094").option("topic", "ratedata").option("checkpointLocation", "stream/ratedataproducer/").start().awaitTermination()
2. kafka to Delta
3. Delta to console
import org.apache.spark.sql.streaming.Trigger
val df =<EMAIL_ADDRESS>df.createOrReplaceTempView("ratedata")
val wdf = spark.sql("select id,  date_format(cast(timestamp as timestamp), 'HH:mm:ss') as sourcetime,date_format(current_timestamp(),'HH:mm:ss') as currenttime from ratedata")
wdf.writeStream.format("console").option("checkpointLocation", "/tmp/ratedataconsumer").outputMode("append").trigger(Trigger.ProcessingTime("1 SECONDS")).start().awaitTermination()
It streams fine for sometime and randomly throws the following error:
_java.io.FileNotFoundException: Operation failed: "The specified path does not exist.", 404, GET, https://shddatalakesta.dfs.core.windows.net/datalake-uat?upn=false&resource=filesystem&maxResults=500&directory=stream/rateda
ta/delta_log&timeout=90&recursive=false, PathNotFound, "The specified path does not exist.
I have tested this with multiple storage containers and tables, and I am able to reproduce this consistently.

Hi @rajasekarv, are you still getting this issue?
From your description it seems like a storage issue, and not specific to Delta.

I can still reproduce the issue. Let me raise the issue with Azure and will update here.

Has it been resolved? How?

has it been resolved? if yes then how?

@zsxwing yes https://github.com/delta-io/delta/issues/1277

I can still reproduce the issue. Let me raise the issue with Azure and will update here.

@rajasekarv have you managed to solve it?

I am getting yet with other spark job and other storage account container on which i have public access set:
"Caused by: java.io.FileNotFoundException: 10m/per_ip/_delta_log is not found"

Sorry for the delated response @0xdarkman . We didn't bother with Azure team even though we should. We tried the same by mounting blob-fuse and it seemed fine with that. So I guess the issue is not in the blob storage and might be in the Hadoop HDFS implementation which Spark uses. It is easily reproducible so you can try raising this in Hadoop Jira or else go with the workaround I mentioned.

@rajasekarv i opened ticket to microsoft, produced data for them, they looked into it and they confirmed it is a known bug to them. so it means Microsoft Azure has confirmed it is on them.

@rajasekarv i opened ticket to microsoft, produced data for them, they looked into it and they confirmed it is a known bug to them. so it means Microsoft Azure has confirmed it is on them.

@0xdarkman Glad to hear. However it is bit  surprising to me. Since blob fuse is working fine. Blobfuse is using Goland SDK behind. So I assumed the issue might be coming from either Java Azure storage SDK or from HDFS implementation of Azure storage. If possible please update here if the issue is resolved for you.

@0xdarkman Glad to hear that MSFT figured out the issue. Could you post this information in the open ticket https://github.com/delta-io/delta/issues/1277 ? Thanks!


Corrected spelling of loaded tag 'wagtailimages_tags'

Corrected spelling in getting started documentation. From 'wagtailimages_tag' to 'wagtailimages_tags'

Fixes #...
Just corrected spelling of loaded tags in the getting started documentation.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks again! Merged in 6fcf52808b665d747d12eb9a9af0520f583eb98b.


Bot doesn't catch.......

The bot seams not catch all pokemon, maybe?

If you mean dev version than same with me. It just walk, spin and hatch egg.

yes dev version, sometimes catch but rarely........so? we need to install master version?

Up to you. If you want get more XP then use master version (at least now).

Yes no pokemons are caught. That's sad


Add trace_segment_ref_limit_per_segment configuration mechanism to avoid OOM

Add trace_segment_ref_limit_per_segment configuration mechanism to avoid OOM

[ ] Add a unit test to verify that the fix works.
[x] Explain briefly why the bug exists and how to fix it.

There maybe an exception in some plugins, which causes the span to fail to exit, which results in the ThreadLocal not being cleaned up, and this data of TraceSegmentRef is increasing. This configuration will constrain the memory size occupied by TraceSegmentRef and avoid OOM. Note that this configuration is only used to avoid oom, and cannot solve the problem that ThreadLocal cannot be cleaned from the root cause.

It will be hold until 8.5.0 release tagged.

If you want to avoid ref-OOM, take a look at AbstractTracingSpan#refs, which is the real place hosting the reference obj

If you want to avoid ref-OOM, take a look at AbstractTracingSpan#refs, which is the real place hosting the reference obj

Get it, I will try to optimize this.


Text modules being incorrectly decorated in server-expanded layers,

causing them to be requested again.

LGTM

OpenNTF » JavascriptAggregator #615 SUCCESS
This pull request looks good
(what's this?)


edits adding publications/thesis

👷 Deploy Preview for erick-romero processing.
🔨 Explore the source changes: ff0f72a5bc04e2c0246e49f478fb6cb9d4ba3c05
🔍 Inspect the deploy log: https://app.netlify.com/sites/erick-romero/deploys/61d7e7c30ddf0d0008984e89


Group subscriptions by app url.

Is your feature request related to a problem? Please describe.
A user could have multiple active subscriptions for the same dApp which results in duplicated app items.
Describe the solution you'd like
Deduplicate apps by metadata.url
Describe alternatives you've considered
No alternative.
Additional context
See Slack discussion

No longer relevant as the SDKs will prevent multiple subscriptions with the same url


add a function to find all signatures

That's on the TODO list after rewriting it as a multithreaded system driver. Won't be until summer.


Contracts

ISee Eiffel for an example of core language support, C#/.NET and Java (including http://go/cofoja developed at Google) for less pretty but fully functional implementations.
This is a complex feature, filing now so it can be considered at the appropriate time.
(It might appeal to the people who have been asking for non nullable types.)
The major pieces that are needed are:

Tagging with predicates
1.1 Tagging of classes with predicates: invariants
1.2 Tagging of methods with predicates: preconditions, postconditions, (exceptional postconditions)

New keywords or functions for use in postconditions
2.1 "result" refers to the method result
2.2 "old(foo)" refers to the value of foo on method entry

Contract evaluation at runtime: execute before and after method invocations
3.1 But not when evaluating a contract predicate
3.2 With facility to enable/disable contracts by library
3.3 With invariants ignored for "private" method calls (whatever this means for Dart)
3.4 Inheriting contract predicates from superclasses, interfaces

A way to disable contracts and have the code execute as quickly as if there were no contracts

FYI. The addition of native C# support for method contracts was discussed at the Jan 21, 2015 C# Design Meeting. The issue used to track this specific feature is https://github.com/dotnet/roslyn/issues/119.


Bad doc link

The link to "views" from https://github.com/Rediker-Software/doac/blob/master/docs/index.md is bad.  Without good docs, people won't adopt the App.

Yup, this repo sounds like what I'm looking for, but the documentation is incomplete and I have no idea what it actually does.


new feature: Add event when data loaded from rest

New Feature
Add an event when data loaded with choice by url.
What is the current behavior?
No event
What is the expected behavior?
An event that can trigger if array of data returned by rest api is empty so  we can hide and disable the  input

The QuestionSelectBase has choicesChangedCallback. It's called on choices has been changed.
You can see sample usage here - https://github.com/surveyjs/widgets/blob/master/src/select2.js
Probably we need to document it

Ok so we would be able to track if array returned by rest service is empty or not.
But is it possible to to hide the survey element (dropdown, checkbox ...) if array is empty

The visible property overide  the visibleif property  ?

@andrewtelnov A global event in survey, or event per question?

An easy test could be if the rest api return an empty array the question must not be visible

@xibman Other choice can be an option in the case

specific object returned by the api could be used
http error code returned by api  like this
{ "code": 21211, "message": "The 'To' number<PHONE_NUMBER> is not a valid phone number.", "more_info": "https://www.twilio.com/docs/errors/21211", "status": 400 }

The following event has been added:
  /**
   * The event is fired after choices for radiogroup, checkbox and dropdown has been loaded from the RESTful service and before they are assign to the question.
   * You may change the choices, before it was assign or disable/enabled make visible/invisible question, based on loaded results
   *
 question - the question where loaded choices are going to be assigned
   *
 choices - the loaded choices. You may change them to assign the correct one
   *
 serverResult - a result that comes from the server as it is.
   */
  public onLoadChoicesFromServer: Event< (sender: SurveyModel, options: any) => any,  any
> = new Event<(sender: SurveyModel, options: any) => any, any>();

Here is the code for you needs:
  survey.onLoadChoicesFromServer.add(function(survey, options) {
    options.question.visible = options.choices.length > 0;
  });

We will likely make a new update tomorrow on Saturday.
Thank you,
Andrew


refactor(gbd): use wide instead of long format

Convert GBD into wide format to improve performance and simplify code.

@spoonerf feel free to merge or close this as you wish.


implementing #160

Alright, fog got merged, so I'll aim to release this by EOD Wednesday AEST. (probably much sooner) Need to write some tests for this and run the integration suite over.

If you need any help - just let me know! I'll be happy to :)

Right now the acceptance tests are failing:
$ bundle exec rake acceptance:smoke
 1) provider/google/provisioner/shell it should behave like provider/provisioner/shell provisions with the shell script
     Failure/Error: assert_execute("vagrant", "up", "--provider=#{provider}")
       expected command to exit with 0 but got exit code: 1

       stdout: You appear to be running Vagrant outside of the official installers.
       Note that the installers are what ensure that Vagrant has all required
       dependencies, and Vagrant assumes that these dependencies exist. By
       running outside of the installer environment, Vagrant may not function
       properly. To remove this warning, install Vagrant using one of the
       official packages from vagrantup.com.
       Bringing machine 'default' up with 'google' provider...
       ==> default: Launching an instance with the following settings...
       ==> default:  -- Name:            i-2018062511-cab04630
       ==> default:  -- Project:         graphite-sandbox
       ==> default:  -- Type:            n1-standard-1
       ==> default:  -- Disk type:       pd-standard
       ==> default:  -- Disk size:       10 GB
       ==> default:  -- Disk name:
       ==> default:  -- Image:
       ==> default:  -- Image family:    debian-9
       ==> default:  -- Instance Group:
       ==> default:  -- Zone:            us-central1-f
       ==> default:  -- Network:         default
       ==> default:  -- Network Project: graphite-sandbox
       ==> default:  -- Metadata:        '{}'
       ==> default:  -- Labels:          '{}'
       ==> default:  -- Network tags:    '[]'
       ==> default:  -- IP Forward:
       ==> default:  -- Use private IP:  false
       ==> default:  -- External IP:
       ==> default:  -- Internal IP:     #<Object:0x00007fcd4d480720>
       ==> default:  -- Preemptible:     false
       ==> default:  -- Auto Restart:    true
       ==> default:  -- On Maintenance:  MIGRATE
       ==> default:  -- Autodelete Disk: true

       stderr: /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/http_command.rb:218:in `check_status': invalid: Invalid value for field 'resource.networkInterfaces[0].networkIP': '#<Object:0x00007fcd4d480720>'. Requested internal IP is not a single IP. (Google::Apis::ClientError)
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/api_command.rb:116:in `check_status'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/http_command.rb:183:in `process_response'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/http_command.rb:299:in `execute_once'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/http_command.rb:104:in `block (2 levels) in execute'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/retriable-3.1.2/lib/retriable.rb:61:in `block in retriable'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/retriable-3.1.2/lib/retriable.rb:56:in `times'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/retriable-3.1.2/lib/retriable.rb:56:in `retriable'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/http_command.rb:101:in `block in execute'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/retriable-3.1.2/lib/retriable.rb:61:in `block in retriable'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/retriable-3.1.2/lib/retriable.rb:56:in `times'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/retriable-3.1.2/lib/retriable.rb:56:in `retriable'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/http_command.rb:93:in `execute'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/lib/google/apis/core/base_service.rb:360:in `execute_or_queue_command'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/google-api-client-0.23.0/generated/google/apis/compute_v1/service.rb:6877:in `insert_instance'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/fog-google-1.6.0/lib/fog/compute/google/requests/insert_server.rb:111:in `insert_server'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/fog-google-1.6.0/lib/fog/compute/google/models/server.rb:485:in `save'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/fog-core-2.1.0/lib/fog/core/collection.rb:50:in `create'
       	from /Users/temikus/Dropbox/Code/vagrant-google/lib/vagrant-google/action/run_instance.rb:196:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/Dropbox/Code/vagrant-google/lib/vagrant-google/action/warn_ssh_keys.rb:28:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/Dropbox/Code/vagrant-google/lib/vagrant-google/action/warn_networks.rb:28:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builtin/provision.rb:80:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builder.rb:116:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/runner.rb:66:in `block in run'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/util/busy.rb:19:in `busy'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/runner.rb:66:in `run'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builtin/call.rb:53:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/Dropbox/Code/vagrant-google/lib/vagrant-google/action/connect_google.rb:44:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builtin/box_check_outdated.rb:36:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/warden.rb:34:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/builder.rb:116:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/runner.rb:66:in `block in run'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/util/busy.rb:19:in `busy'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/action/runner.rb:66:in `run'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/machine.rb:239:in `action_raw'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/machine.rb:208:in `block in action'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/environment.rb:598:in `lock'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/machine.rb:194:in `call'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/machine.rb:194:in `action'
       	from /Users/temikus/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/bundler/gems/vagrant-dbba41a7ec3d/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

@mattimatti PTAL

Closing this - please reopen if there's interest.


Documentation: update binaryninja.interaction.get_save_filename_input documentation to reflect binaryninja.interaction.get_open_filename_input

In binaryninja.interaction.get_save_filename_input there's missing documentation for (supported, I tested that myself!) sample syntax of multiple file types like in binaryninja.interaction.get_open_filename_input

What I mean is the difference below:

While you're correct that it's missing, the right fix is actually removing the extension entirely as a parameter. That parameter is actually not even used at all in the save prompt since it's up to the user to select/type a filename and the extension they return is all that matters.
A save dialog box doesn't actually require a specific extension, it would be up to any code that uses the extension to decide whether to accept the value or not. I'm not sure why the API was designed that way in the first place, except for symmetry but that argument isn't used at all in the native code that implements that API.
Given that I'm just going to close it as "wontfix" for now since I think the proper fix is to actually remove that parameter entirely, but that would have some compatibility issues with other plugins so I want to think about how we do that first.


Domain based routing problem.

Description
First of all, I am extremely sorry for creating this issue. Actually, I am facing a problem with domain based routing for a long time. I already try all existing support platform like- Github Discussion, Stack Overflow, Radit. My following is my link-

I create first discussion here, about 3 months ago. I didn't get any reply.
Then I try myself and try to get help from ai, I didn't get anything, Yesterday I create second discussion here, almost 1 day.
I also create stack overflow question here.
On the raddit I also try to get help. Here is link

My Problem
I want to create a nextjs i18 app with subdomain based locale, like-
example.com //It is default locale, on default locale I want to use en
fr.example.com
de.example.com
I don't want to use prefix like-
fr.example.com/fr
de.example.com/de
That's why disable the locale prefix. Following is my code-
i18n.ts-
import { notFound } from "next/navigation";
import { getRequestConfig } from "next-intl/server";

const locales = ["en", "fr", "de"];

export default getRequestConfig(async ({ locale }) => {
    if (!locales.includes(locale as any)) notFound();
    return {
        messages: (await import(`../translate/${locale}.json`)).default
    };
});

middleware.ts-
import createMiddleware from "next-intl/middleware";

export default createMiddleware({
    locales: ["en", "fr", "de"],
    defaultLocale: "en",
    localePrefix: "never",
    domains: [
        {
            domain: "dev.localhost:3000",
            locales: ["en"],
            defaultLocale: "en"
        },
        {
            domain: "fr.dev.localhost:3000",
            locales: ["fr"],
            defaultLocale: "fr"
        },
        {
            domain: "de.dev.localhost:3000",
            locales: ["de"],
            defaultLocale: "de"
        }
    ]
});

export const config = {
    matcher: ['/((?!api|_next|.*\\..*).*)']
};

So, here you can see that, I use this localePrefix: "never",. Now it is not auto redirecting.
What I want?
I want to auto redirect to subdomain based routing without adding locale prefix. Suppose, detection locale is fr, but I am going to root domain example.com, it automatically should redirect  to fr.example.com.
Again suppose, detection locale is en, but I am trying to go fr.example.com it should redirect to example.com, as here I want to use root domain for en locale.
Same as, if I previously switch locale is fr, next-intl is saving this onto cookie, then I try to go example.com, it should redirect to fr.example.com.
Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://github.com/siamahnaf/next-intl-domain-based-routing
Reproduction description
I have no idea, how can I solve this problem.
Expected behaviour
Just give me one example or idea please.

Hey, the issue tracker is really not for usage questions—I hope you can understand. I've replied to your question in https://github.com/amannn/next-intl/discussions/1159.

Thanks. I said sorry for creating this issue.


BugFix: Marioclock use of fillPoly adjustments

Problem:
Pyramids float above ground. Possibly due to changes to fillPoly function
Solution:
Adjust Pyramid Y values

Thanks!


Add normalization to support abstract field federation

This PR adds the three operation normalization passes outlined in #328
to support abstract field federation. The new passes 1) "expand" inline
fragments with interface type conditions into inline fragments with
concrete type conditions, 2) "expand" interface selections to selections
that have inline fragments with the corresponding concrete types, and 3)
eliminate invalid inline fragments as the result of passes (1) and (2).
These passes run after fragment inlining but before inline fragment
merging. In the code I note that we may also want to implement merging
of inline fragment siblings that match.
A lot of tests needed to be updated due to these changes. The REST and
JSON data source tests were updated, but it isn't clear to me if
existing REST and JSON datasources will be compatible with these
changes; they need to return the appropriate "__typename" in responses
(since resolver fields now have OnTypeName conditions). Guidance on this
topic would be appreciated.
I also updated the ValidateByFieldList function to "expand" interface
types used in block and allow conditions to the corresponding concrete
types. This is what I'd expect (if Character "name" isn't allowed, then
Human "name" shouldn't be allowed either), but I could be mistaken about
the exact use of this function.
Depends on #336. (This is a stacked PR; the parent PR is expected to be
merged into master, followed by this PR, instead of merging this PR into
the parent PR directly.)

@jensneuse, stacked PRs don't work very well with forked repos. I'll create a new upstream PR once the parent PR is merged. (Another alternative is to create a branch for the parent PR in the upstream repo, but then keeping the branch up-to-date is a bit of a pain.)

Closing all the old graphql-go-tools PRs. We ended up using Apollo Gateway to create query plans (which can be done statically), which we then execute via a small, custom Go execution engine.


adding matrix transpose in python

Have you read the Contributing Guidelines on Pull Requests?
yes
Description
issue #5125
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
issue #5125

@ankitaggarwal23 I have made the changes , can you please review my pr


refactor: replace got with node-fetch on functions-with-args.test.js

Summary
refactor: replace got with node-fetch on functions-with-args.test.js
related to #5695

For us to review and ship your PR efficiently, please perform the following steps:

[ ] Open a bug/issue before writing your code 🧑💻. This ensures we can discuss the changes and get feedback from everyone that should be involved.
[x] Read the contribution guidelines 📖. This ensures your code follows our style guide and
passes our tests.
[x] Update or add tests (if any source code was changed or added) 🧪
[ ] Update or add documentation (if features were changed or added) 📝
[ ] Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

Due to some GitHub actions working against this, currently merging this into another branch and trying to merge that new branch back into main (😓)


Enable parallel spek test discovery

https://github.com/spekframework/spek/releases/tag/2.0.13

This should speed up the test discovery phase.


iOS 13

There does not appear to be any reason for why the class should be @available only on iOS 14+.
Please consider relaxing the @available rule to what is actually required by the implementation & in-line with 74aa40a398688b90ee7724797861185e5a696aca :–)

The implementation uses StateObject, which is only available on iOS 14+

Would it be possible to use @State with a value-type Proxy to bring this to iOS 13?

#2

Providing an iOS 13 compatible variant requires a lot of workarounds which may impact performance and stability


chore(release): upgrade release branch to 0.5.0

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 4 committers have signed the CLA.:white_check_mark: madecki:white_check_mark: jbeveland27:x: tangollama:x: nr-opensource-botYou have signed the CLA already but the status is still pending? Let us recheck it.


prometheusremotewrite: Support OTel resource attribute promotion

Add support to OTLP ingestion for promoting OTel resource attributes to labels.
We agreed to test this functionality in our Prom fork before proposing it upstream.

Wonder you thought about this already, I think this could get more efficient if we sort the configured promote attributes when read from configuration once, then range on settings.PromoteResourceAttributes, append when incoming attribute exist in the settings.

@ying-jeanne what you gain by sorting the configured attributes to promote beforehand is to avoid sorting promotedAttrs? You also have to make sure that the list of attributes to promote is unique though, this is why I range over resourceAttrs instead. There should be relatively few attributes to promote (assuming a limit prevents the user from promoting too many), so I guess iterating over this list, after making sure it's unique, should be fast.

You also have to make sure that the list of attributes to promote is unique though, this is why I range over resourceAttrs instead.

@ying-jeanne in retrospect I realize that it doesn't matter if the list of attributes has duplicates, since labels stemming from promoted attributes are only added if the label isn't already in the set. This is effectively deduplication.
I've pushed a revision optimizing the promotion loop, PTAL.

Closing in favour of upstream PR (already merged).


make package pip installable

I would like for the package to be pip installable. It seems like we could just follow the instructions https://packaging.python.org/tutorials/packaging-projects/ to get it set up. I don't think we will necessarily need to put this up on the PyPI, but at least this will make it easier for users to download the package from this repo and get it working relatively quickly and easily

From reading the above tutorial, it looks like we just need to make a setup.py for the package and move copies of the README.md and LICENSE files inside of the package directory...

After discussions, it seems that it would actually be beneficial to get this hosted on PyPI if possible


[git_branch][slack][ensure_git_branch] unify logic of Actions.git_branch helper and git_branch action

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Supersedes #15035
Resolves #13346
Resolves #15034
Closes #17527
Timeline:

#13346 issue was open in September 2018 and closed in December 2018 due to inactivity
#15034 issue and #15035 PR were open in July 2019 to fix the issue above
The PR above was closed in July 2020 probably because the PR had a lot of back and forth and took too long. The author decided to close it without an explanation 🤷
#17527 was open by @revolter in October 2020 to fix just slack action, in another simpler (and less generic) way. It was just a proposal though, it didn't fix the existing specs at that time.
This PR aims to fix the root cause of the issue rather than just fix slack action specifically. It also fixes e.g. ensure_git_branch action, for instance.

Actions.git_branch and git_branch have slightly different implementations, even though their behavior should probably be very similar.
Actions.git_branch looks up the GIT_BRANCH env var and falls back to git rev-parse --abbrev-ref HEAD, which results in either a branch name or "HEAD". (note: AFAICT it's not possible to have it return nil as the code suggests. Tested in the field)
git_branch looks up a bunch of CI-specific env vars for git branch detection, and falls back to git symbolic-ref HEAD --short 2>/dev/null, which results in either a branch name or an empty string, as documented.
It has been expressed by users that other fastlane tools that make use of Actions.git_branch have been unable to detect the right branch because the action wouldn't take into account all the CI env vars that git_branch action does. Since CI checks out the repo under no branch (i.e. "HEAD" ref.), those actions (e.g. slack and ensure_git_branch ) do not work properly.
Description
This PR unifies both utilities to look up the same information: first env vars that represent git branches in multiple CI envs (starting with GIT_BRANCH for backwards compatibility), and falling back to git rev-parse --abbrev-ref HEAD. The decision to use this git command to print the branch is because it never fails and it prints either the branch name or HEAD. Since the git_branch action documents that it returns an empty string when a branch can't be located (and it's not only documented, it currently does behave like that), then when Actions.git_branch returns "HEAD" (which means no branch was found), then it will translate that into an empty string.
By moving away from git symbolic-ref HEAD --short 2>/dev/null to git rev-parse --abbrev-ref HEAD, it also implicitly fixed Windows environments running git_branch action.
Testing Steps
To test this branch, modify your Gemfile as:
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "rogerluan/unify-git-branch-utilities"

And run bundle install to apply the changes.

@rogerluan great work! Glad to see this is finally fixed.


test: enable cypress retries

As discussed in https://github.com/freeCodeCamp/freeCodeCamp/issues/41009

Do we need to undo the changes that I made in #41010 to see this in action? Or the we need to increase the delay regardless.

I was expecting to see some other flaky tests, not just the one we've been seeing recently.  I've pushed https://github.com/freeCodeCamp/freeCodeCamp/tree/feat/enable-cypress-retries so we can look in the dashboard and check I didn't mess up the config.

we need to increase the delay regardless.

In the short term, sure, but we really should not need to - the tests should not be taking anywhere near that amount of time.

According to their status page, GitHub Actions is experiencing degraded performance. Could this be the cause of tests timing out?


Fee help pdf link updates

Updates the external links for the fee remission form guide & fee remission form pdf's.

This is just copy change, looks fine to me!

Thanks @dotemacs !


Image Can't show All

I used your src file in android studio,Build success and run , But the image can't show all.

I find this problem only in sumsung Galaxy S7  (SM-G9300),android 6.0.1,arm64...


Improve folder structure for tests -> all tests in one file

At the moment, when app is created, there is only one test file, where it holds all tests.
It is better to have controller testing, middlewares or other items be in their own folder.
Also, it should make sure that tests are running.

Hi @ezkemboi can I have a go at this please?

Sure, thanks and welcome.
Go ahead and rais a PR.

Assigned to you @its-tayo.

Hi @ezkemboi, can you please let me know what the new test directory structure should look like?

Something like
    tests
        - controllers
              - user.js
        - middleware
             - middleware.js
        - routes
             - routes.js

It might not be good the first time, but the idea is to have different files/folders for different parts that are testable. Something like models might be tested easily when controllers and other items have been tested.
We just want to get rid of the test file being a single file.
In case of any clarification you need or help with the codebase, do let me know.
Looking forward to your PR.

@its-tayo we can schedule a call if you need assistance with any part of the codebase or any assistance whatsoever.

Alright, thanks. I went through the codebase thoroughly yesterday hence the delay. Submitting my pr in a bit. But we could still schedule a call though.

@its-tayo thanks for your efforts.
I do really appreciate and welcome to the team.
Probably about the call, I will send you an email on the same.

You're welcome. Looking forward to our call.


Proofed working Basic Latin keyboard support for Android

Ah thank you for tidying this up and confirming it all works