random number not handling invalid keypress

[Nov 28 09:51:49] WARNING[50136][C-0000003d] pbx.c: Invalid extension '8', but no rule 'i' or 'e' in context 'random_number'

is this true for any context that uses destination_context?


Neo4j outsode kubernetes

@steveteuber   Hi can i use the plugin to visualize kubernetes resources even if neo4j is installed outside kubernetes?how can i call kubernetes resources in my cypher query from neo4j which is running outside kubernetes

Hi @myrulezzz,
Thank you for opening this issue. With this kubectl plugin it doesn't matter where your Neo4j database is running.
You just need to fetch all desired resources and then import them into your Neo4j database.
For more details please take a look into the Quickstart guide.
PS: This kubectl plugin outputs Cypher statements from kubernetes resources.

@steveteuber If you add more pods lets say and you want to update your graph how you will do it?


Server crash

Information

Minecraft Version: 1.16.5
Fabric API Version: 0.32.9
OS: IDK
Other installed mods: https://www.curseforge.com/minecraft/modpacks/simpearth (not all of them, there are also server-side mods too)

Describe the issue
Server crashes upon start-up
Crash/Error logs
https://paste.srnyx.xyz/inotifijaz.sql
Expected behavior
Server should start
Additional Context
I just recently updated Gunpowder Base to the latest version.

I think this is the cause of the issue:

Kotlin doesn't compile default methods as java does unless you tell it to, it makes an inner class to the interface called DefaultImpls, then adds synthetic implementation methods that call static methods in that inner class to classes that do not override the 'default' methods.
However, most gunpowder modules have not been recompiled against this new version of gunpowder-base, and so do not have these synthetic implementing methods and crash with an AbstractMethodError.

damn you kotlin
I'll fix this later tonight


Flaky test: Scraping metrics from Kubescape

Our e2e tests are flaky when it comes to scraping metrics from kubescape. E.g. https://github.com/gitpod-io/observability/runs/5964858522?check_suite_focus=true
We should understand why that is happening and fix it

Happend here.
@ArthurSens, can you share your thoughts on this? If there is no easy solution, can we disable the flaky test until we found a solution?

The flaky test is making sure Prometheus is able to scrape metrics from Kubescape. We do that by querying Prometheus for a metric that we know that it comes from Kubescape.
I suspect the flakiness comes from scrape timing. Kubescape is intentionally scraped less often because we don't need to scan our clusters every 15s for vulnerabilities. Maybe we're timing out too early, and Prometheus still hasn't scraped Kubescape yet.
It is just a thought tho, I haven't looked deep into it.

Obviously, the preferred option would be to fix the flaky test, but if we don't have time for that at the moment I'd prefer to unmark this test as a "Required" on the Pull Request protection. That way we still the test for all pull requests, but we don't block merge on failures

Looks like #159 didn't solve it 🙁

Flaky test solved by removing it 😆
https://github.com/gitpod-io/observability/pull/278


Core module won't compile for ios_arm64

Hello,
I'm using your library within a kotlin multiplatform mobile project. My Android module is planed to use the separate Jetpack compose functionality directly. For iOS however I planed to access my shared kotlin multiplatform module from my Swift code, to receive a list of the libraries/licences that are used in the common/shared kotlin native business layer.
Once retrieved, I would simply pass this list of libraries/licences to my ios specific license library to generate a complete list of all the used libraries (KMM, Cocoapods, Swift Package Manager).
Unfortunately building the kmm shared layer fails with the following message:
`Execution failed for task ':sharedDomainLayer:cinteropJWTDecodeIosSimulatorArm64'.

Could not resolve all files for configuration ':sharedDomainLayer:iosSimulatorArm64JWTDecodeCInterop'.
Could not resolve com.mikepenz:aboutlibraries-core:10.3.0.
Required by:
project :sharedDomainLayer
No matching variant of com.mikepenz:aboutlibraries-core:10.3.0 was found. The consumer was configured to find a usage of 'kotlin-cinterop' of a library, with the library elements 'cinterop-klib', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native', attribute 'org.jetbrains.kotlin.native.target' with value 'ios_simulator_arm64' but:
- Variant 'commonMainMetadataElements' capability com.mikepenz:aboutlibraries-core:10.3.0 declares a usage of 'kotlin-api' of a library:
- Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about its elements (required them with the library elements 'cinterop-klib')
- Doesn't say anything about org.jetbrains.kotlin.native.target (required 'ios_simulator_arm64')
- Variant 'debugApiElements-published' capability com.mikepenz:aboutlibraries-core:10.3.0 declares an API of a library:
- Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about its elements (required them with the library elements 'cinterop-klib')
- Doesn't say anything about org.jetbrains.kotlin.native.target (required 'ios_simulator_arm64')
- Variant 'debugRuntimeElements-published' capability com.mikepenz:aboutlibraries-core:10.3.0 declares a runtime of a library:
- Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native'
- Other compatible attributes:
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about its elements (required them with the library elements 'cinterop-klib')
- Doesn't say anything about org.jetbrains.kotlin.native.target (required 'ios_simulator_arm64')`

As your documentation only mentions Android and app-desktop, I guess that as of now, kotlin native simply isn't supported. Another issue could be that I'm using Apple Silicon (M1) which is always a good guess for incompatibility issues.
used Version:
val kotlinVersion = "1.7.0"
val aboutLibsVersion = "10.3.0"

@xoif added the additional simulator targets, if you could please check out if it works now?


Add Page Picker into form widget

Hi,
Please implement page picker into form widget. This is very useful for client easily pick that page to display my custom form plugin using builder. Please consider.

@claudchan see https://github.com/rainlab/builder-plugin/issues/258#issuecomment-435602432. Duplicate of #258.


Extremely long POST request

Apologies if this isn't the right forum.
We use the postmark-rails gem to send mail. Earlier today we had an issue where it appears (from New Relic) that mail delivery spent 975 seconds in a POST request to api.postmark.com.
This coincides roughly with an incident in the postmark service (https://status.postmarkapp.com/incidents/6862) - which is fine - but why did the POST request take 975 seconds and not timeout earlier?
From my reading of the gem, it uses Net::HTTP and from TFM the default timeouts for Net::HTTP all appear around the 60 seconds mark - so I'd expect the POST to have died a lot sooner.
I care because this happened in a background worker that because it was stuck for 975 seconds caused all kinds of alarms to fire - and if possible I'd like to not fire the alarms in the future.

Hey @jbarber. If I had to guess, it’s DNS. (Because it’s always DNS 🙃). The default YARV implementation of TCPSocket (used internally by Net::HTTP) relies on a deprecated DNS resolution method that blocks the entire VM, so it’s “immune” to the open_timeout setting. Even if you wrap the entire call to Postmark (or any other HTTP API) in a timeout, it can still get stuck for a long time. Not sure if we can do something about this aside from switching away from net/http, which comes with its own problems.


Compile January data for WC Combined Monthly Statistics Report

[https://wellcomecloud.sharepoint.com/:x:/r/sites/VisitorInsights/_layouts/15/Doc.aspx?sourcedoc={97E28F8D-C866-419A-B260-9238101BAA86}&file=WC combined stats report template.xlsx&action=default&mobileredirect=true](
)

Now complete.


Show gravitino logo in IDEA

@totalo
Please modify the PR description as others have done.

@totalo thanks a lot for your contribution, can you please create a related issue for this, also please update the PR title and description to follow this project's rule? Thanks a lot.

@totalo Please modify the PR description and title as others have done.

Ok.

@totalo thanks a lot for your contribution, can you please create a related issue for this, also please update the PR title and description to follow this project's rule? Thanks a lot.

ok.


inherit keyword as shorthand to refer to super class fields and methods.

Search Terms
Inherit, inheritance, type inference, subclass, superclass, override,
Suggestion
This issue addresses the lack of easy way to refer to types of fields or methods of a base class or implemented interfaces without a high amount of repetition.  Proposed is a keyword inherit which will act as a type alias which is contextually resolved for the corresponding type of the base class.
A simpler way to understand this proposal is to think of it as a solution to #10570 by offering an explicit but convenient way to refer to the base class, let us look at a typical example:
abstract class Geometry {
    public abstract model: "square" | "circle";
}

class Canvas extends Geometry {
    // initially set to square but still allow to change to circle later.
    public model = "square";
    // ERROR  ^ Type 'string' is not assignable to type '"square" | "circle"'
}

In this case we want to preserve the same type for field model from the class Geometry. the most obvious solution is to rewrite "square" | "circle" but we can do a little better by instead using Geometry["model"] to allow for changes in the base class to propagate automatically.
class Canvas extends Geometry {
    public model: Geometry["model"] = "square";
    //  This way we explicitly inherit the same type as base class.
}

This is better but still requires us to refer to the base class and rewrite the field name for each field initialized in this way. The proposed solution is to add a keyword inherit which will use the base class and the field name to resolve to the appropriate type.
class Canvas extends Geometry {
    public model: inherit = "square";
    //  This would be equivalent to above example using Geometry["model"]
}

Here is an example playground where I define inherit as a type alias where the arguments could be gained automatically from the context of where it is used.
This would also support being used in method parameters and return types which would be equivalent to using Parameters and ReturnType where appropriate.  For example each of these 3 declarations would be equivelent to the following comment
class WithInherit extends Base {
    a: inherit;
    // a: Base["a"]
    b: inherit;
    // b: Base["b"]
    foo(param: inherit): inherit {}
    // foo(param: Parameters<Base["foo"]>[0]): ReturnType<Base["foo"]>{}
}

This would also address #2000 with additional capability, if all parameters and return type use inherit it will ensure the call signature exactly matches the super class. except without forcing redefining it and allowing extensions as shown below.
Use Cases and Examples
Composition
The proposed keyword would not be required to use alone but could be used like any other type alias. This means that further additions to the original type can be done such as Partial<inherit> or similar. Consider this example where we want to override a method doAction to accept additional kinds of parameters:
class FlyingRobot extends Robot {
    doAction(action: inherit | "fly"){
        // type of input is either "fly" or something the base class supports
        if(action == "fly"){
            // support our case
            return this.fly()
        } else {
            // any other value must be valid to base class since we used inherit.
            return super.doAction(action);
        }
    }
    fly(){}
}

This allows us to support an obvious variation of the type defined by the base class and can be easily understood and written without even looking at the original declaration of Robot[“doAction”].
Interfaces and Multiple Implementations
In the event that a class implements several interfaces, inherit will look up fields on an intersection of the base class (if present) and all implemented interfaces:
class Foo extends Base implements A, B {
    a: inherit; // resolves to (Base & A & B)["a"]
}

For cases where multiple interfaces would define the same method or field inherit would resolve to the intersection of all necessary values, or in the case of method overrides resolve only to the last method to remain consistent with Parameters and similar constructs.
Constraints, Valid and Invalid Uses.
The inherit keyword only makes sense inside a class that either extends another class and/or implements at least one interface. If there is no base class then an error should be raised. As well the inherit keyword would only be applicable in one of the following positions:

Instance field
Getter return value
Setter parameter
Method parameter
Method rest parameter
Method return value

For parameters and return types, if the corresponding field on the base class is not a function then a compile error should be thrown. Either with a very similar message to the one thrown by Parameters<0> or one more specific like “cannot inherit parameter when super field “foo” is not a function”.
For rest parameters, inherit should be equivalent to a extends / infer statement with the same number of other parameters as specified, with all other types set to any for the inference. So if the function is written like foo(a: number, b: string, …rest: inherit) the inherit would resolve like this:
Base[“foo”] extends (a:any, b:any, ...rest: infer T)=>any ? T : never. And the never there would never be used since if Base[“foo”] is not a function then a compile error is thrown. Any other case even where Base[“foo”] takes only 1 parameter will still give valid results for the rest parameter.
Note that for fields initialized to arrow functions, it is not valid to use inherit in the parameters or return type of the arrow function. Instead the full field can use inherit then the parameters will be inferred using normal means: Playground Link
class Example implements Base {
    // a and b here are automatically typed when `inherit` resolves to a valid function type. this is nothing new.
    foo: inherit = (a, b) => {};
}

Cases that don’t work
Methods with several overloads and methods with generics are 2 cases where the currently existing Parameters and similar construct cannot fully capture the information. This proposal would suggest that no additional work be done to let inherit do any extra work in these cases but does recognize that that would be possible in the future.  This means that if a method has a generic the inherit keyword will only use the constraint without preserving the generic. Similarly when a method has several overloads inherit will only use the type specified in the last overload which without specifying the other necessary call signatures is not valid.
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code *
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

* in order to not break any existing code that may use a type alias called inherit, this would need to allow the keyword to be shadowed similar to other built in names.

I would personally prefer inherit to be an actual prefix keyword (like readonly) rather than part of the type annotation so that entire method declarations can inherit types:
class Foo extends Base {
  inherit method(arg1, arg2) {}
  method(inherit arg1, inherit arg2) {}
  method(arg1: number, arg2: string) {} // Explicitly type
}

I would personally prefer inherit to be an actual prefix keyword (like readonly) rather than part of the type annotation

See the example of FlyingRobot in the initial post, by using it in the type position it allows composition like a: Readonly<inherit> or doAction(action: inherit | "fly"), if the only use case was to copy the entire field / method type signature then I doubt the team would have been so hesitant to implement a feature like this a long time ago.


Request: variable-width bar chart / "histogram"

I'm trying to graph the election margin prediction market state; I've munged the data down to the following:
-538, -280,    11, 12, 11, 11, 12
-279, -210,    12, 13, 12, 12, 13
-209, -150,    18, 19, 18, 18, 19
-149, -100,    13, 14, 13, 13, 14
-99,  -60,     6,  7,  6,  6,  7
-59,  -30,     5,  5,  4,  4,  5
-29,  -10,     4,  4,  3,  3,  4
-9,   -1,      2,  3,  2,  2,  3
0,    9,       3,  4,  3,  3,  4
10,   29,      6,  6,  5,  5,  6
30,   59,      10, 10, 9,  9,  10
60,   99,      12, 12, 11, 11, 12
100,  149,     10, 10, 9,  9,  10
150,  209,     5,  6,  5,  5,  6
210,  279,     2,  3,  2,  2,  3
280,  538,     4,  5,  4,  4,  5

However, I don't see variable-width bar chart graphing as an option.
Could that be added?
Thank you.

I know this issue is quite old, but it should be possible with the new RAWGraphs 2.
Please let us know if the issue is solved.


Include transaction details and action buttons on host dashboard contributions view

When you view a transaction on the Collective's transaction page, it looks like this:

When you view the same transaction on the host dashboard contributions tab, it looks like this:

As a host admin, I need to access those functions in the first screenshot, but it's much easier for me to locate the transaction using the dashboard. I want to be able to refund a transaction, etc, from the host dashboard view.

Same as https://github.com/opencollective/opencollective/issues/4163#issuecomment-833416356, it's not a "Transaction" but an "Order".


Implement updateScienceMetadata REST end point

Implement updateScienceMetadata REST end point.

Also fix GET /hsapi/scimeta to return properly serialized XML+RDF.  The current implementation returns an escaped string rather than raw UTF-8 XML:
"
<?xml version=\"1.0\"?>\n
<!DOCTYPE rdf:RDF PUBLIC \"-//DUBLIN CORE//DCMES DTD     2002/07/31//EN\"\n\"http://dublincore.org/documents/2002/07/31/dcmes-xml/dcmes-xml-dtd.dtd\">\n
<rdf:RDF
xmlns:dcterms=\"http://purl.org/dc/terms/\"

This makes for unnecessary awkward handling by user agents.

This is part of #299

@sblack-usu  close or act on if needed

This is covered with bag ingestion.


Add support for Windows (for some utilities)

Not sure if we really care about this, so I'm making it a pull request.  I have essentially abstracted RawFd into RawObject, which is a RawFd on Unix and a RawHandle on Windows (I may add support for RawSocket as well, as I am thinking about implementing UtilRead and UtilWrite for TcpStream).
Note that a few tests still fail for cat and head on Windows.  It may just have been because git replaced the line endings for the fixtures though.

Note that this is only failing due to cargo fmt.  I’d like feedback before I fix that issue.

This is temporarily broken on Windows due to changes I've made without access to a Windows laptop.

If no one objects I am inclined to just merge this (or close this pull request and just push my code to master) as it no longer is just changes related to adding Windows support.

I'm OK with the Windows support.


Added optional leading backslash to YAML frontmatter regex pattern

When using YAML frontmatter with Haml files, the string '---' is considered invalid syntax. The hyphen is reserved for executing Ruby code and needs to be escaped to be output as plain text ('---').

Frontmatter should already be removed before the file is passed to template engines, this must be a bug.

Thanks for jumping in! The frontmatter gets removed no problem, that isn't the issue here. What is the issue is that the usage of YAML frontmatter in Haml forces you to save the file with an incorrect syntax and also shows up as errors in editors such as Sublime Text and RubyMine. The hyphen character is reserved in Haml for executing Ruby code and needs to be escaped to be interpreted as plain text.

So you're saying you want \--- to be a valid delimiter?

shows up as errors in editors such as Sublime Text and RubyMine

Ah, it's breaking the syntax highlighting/linting in your editor? So this is not actually an error in Middleman;  the test is just there to show that \--- is now allowed as a delimiter?
In that case, please fix the test as mentioned above (I think you probably just need to change When I go to "/front-matter.haml" to When I go to "/front-matter.html") and remove the content.sub!(/\\---/, '---') line as it's not needed.
Will let @tdreyno decide if this should be added.

Exactly, I do want --- to be a valid delimiter since that's the only way that the hyphen character can get escaped in Haml if it's the first character in a line. Middleman still works functionally when --- is used in Haml files, but that is not a correct method of adding frontmatter since it leaves the file in an errored state based on the Haml spec.

Thing is, there's a world of filetypes out there that would need different delimiters and stuff, not just Haml. The yaml data itself should be a syntax error too, not just the delimiters.
My editor highlights frontmatter correctly for markdown and some other filetypes - this is an editor problem, nothing to do with the Haml spec.

Thing is, there's a world of filetypes out there that would need different delimiters and stuff, not just Haml.

While true, there's a limited number of file types supported in Middleman, and as far as I know, Haml is the only one that needs this particular delimiter.

The yaml data itself should be a syntax error too, not just the delimiters.

Not really, the yaml data is just treated as plain text in Haml.

My editor highlights frontmatter correctly for markdown and some other filetypes - this is an editor problem, nothing to do with the Haml spec.

Again, Haml is the only file type supported by Middleman that breaks a syntax rule by including yaml frontmatter. Consider for a moment that this is actually an editor problem. What does it mean for us to ask an editor to ignore a syntax rule for a particular file type? How then would we guarantee that files made with such an editor will work for someone else? What if we want to use the Haml files elsewhere without a bunch of hackery? What do you think?

I think I have the frontmatter fixture set up correctly as of ea67ec130d30c8ad18b08339f82aef8e23df786e, but I can't for the life of me figure out why the test still fails. Seems the Haml template isn't getting converted to HTML and therefore isn't found. Am I missing something?
Scenario: Rendering Haml (yaml)                    # features/front-matter.feature:31
    Given the Server is running at "frontmatter-app" # lib/middleman-core/step_definitions/server_steps.rb:57
    When I go to "/front-matter-haml.html"           # lib/middleman-core/step_definitions/server_steps.rb:66
    Then I should see "
This is the title
"   # lib/middleman-core/step_definitions/server_steps.rb:78
      expected "
File Not Found

/front-matter-haml.html
" to include "
This is the title
" (RSpec::Expectations::ExpectationNotMetError)
      ./lib/middleman-core/step_definitions/server_steps.rb:79:in `/^I should see "([^\"]*)"$/'
      features/front-matter.feature:34:in `Then I should see "
This is the title
"'
    Then I should not see "---"                      # lib/middleman-core/step_definitions/server_steps.rb:90

I think the file needs to be renamed: front-matter-haml.haml → front-matter-haml.html.haml

Thanks @Arcovion, that allowed the HTML to be output at least. The test still fails because the frontmatter hasn't been parsed out. My regex changes will likely have to be corrected.

The last commit passes my test, are we good to go?

@Arcovion is there any way this could become a config option so anyone can pick different delimiters and all the variations don't have to be in core? Or is the regex too complicated?

Sure, that'd be easy. What would it look like in the config?
config[:frontmatter_delims] = {json: [%w[;;; ;;;]], yaml: [%w[--- ---], %w[--- ...]]}
config[:frontmatter_delims][:yaml] << %w[\\--- \\---]

Hard part for me would be testing it, and idk off by heart how to get config options from within the Middleman::Util::Data::parse method.

app.config[:frontmatter_delims][:yaml] should do it. Seems like the tests provided in this PR might handle the rest.

I guess that's a successful first pull request then?

@tdreyno That raises:
undefined local variable or method `app' for Middleman::Util::Data:Module (NameError)

This works:
Middleman::Application.config[:frontmatter_delims]

But only picks up the ones from application.rb in define_setting:
# Set textual delimiters that denote the start and end of frontmatter
define_setting :frontmatter_delims, {
  json: [%w(;;; ;;;)],
  yaml: [%w(--- ---), %w(--- ...)]
}, 'Allowed frontmatter delimiters'

Not the stuff set in middleman/middleman-core/fixtures/frontmatter-app/config.rb,
which is where I'm doing:
config[:frontmatter_delims][:yaml] << %w(\\--- \\---)

Setting it to anything there has no effect.
Is it even possible to get config options in that method after configuration?

@Arcovion I'll poke around

@Arcovion The non-instanced path (Application) is the default settings, they are immutable.
Regarding app, I thought you were in the front matter extension, not the util file.
You'll just have to add another parameter and pass it from further up where needed.

Thanks for considering these changes!


Feature request: Ability to add annotations via the YouTube API.

Having the ability to add annotations via the YouTube API would be fantastic.
Something like:
	upload := &youtube.Video{
		Snippet: &youtube.VideoSnippet{
			Title:       "Test Title",
			Description: "Test Description", // can not use non-alpha-numeric characters
			CategoryId:  "22",
		},
		Status: &youtube.VideoStatus{PrivacyStatus: "private"},
		Annotations: &youtube.VideoAnnotations{
			{
				Type: "SpeechBubble",
				StartTime: 1.21,
				EndTime: 88.6,
				Text: "1.21 Gigawatts!",
				Font: "Arial",
				Color: "White",
				Background: "#f00",
			},
			{
				Type: "Note",
				StartTime: 25.0,
				EndTime: 30.0,
				Text: "Check out this merchandise!",
				Link: {
					Type: "Merch",
					URL: "http://merchant.partner/uri",
				},
			},
		},
	}

We can only do what the API supports.
If you can figure out how to do this with the YouTube API:
https://developers.google.com/youtube/v3/
and are able to perform a working test with the API Explorer:
https://developers.google.com/apis-explorer/#p/youtube/v3/youtube.videos.insert
then please let me know if you can not do the same thing with the google-api-go-client and I will see what I can do to get it working.
Otherwise, we will need to contact the YouTube API team and ask them to support what you would like.
So please play around with that and let me know.  Meanwhile, I'll see if I can find the owners of the YouTube API and discuss this with them.

Thank you, @gmlewis.
It's not possible with the YouTube API, unfortunately.  (Only invideoPromotion is.)
The annotations API appears to be simple enough and well-designed, based on watching the network requests.  Would I be penalized if I created (and used) a hack to add annotations along with the videos I upload using the YouTube API?

Hmmm... I'm not that familiar with the YouTube or Annotation APIs to know the answer to your question...
But speaking for myself only (not Google), it seems to me that if you can figure out how to add annotations to your video uploads that you should try it out and see if you can get it to work.  I personally don't see the harm in that.
I'll close this issue, but if you have updates from your experiments, feel free to post them here so others can find them easily.

Thanks again.  I'll give it a shot. :)
Would updates include non-API solutions?

I would certainly like to see solutions, and it doesn't hurt to add comments here if you want to... we may not be able to incorporate them into this auto-generated library, but I think others may also appreciate seeing your solutions.


[ffigen] Release 11 Stable

Release 11 stable with the latest fixes on Dart 3.2 before starting to depend on a Dart 3.3-dev version.
Should be merged after:

https://github.com/dart-lang/native/pull/869

And before:

https://github.com/dart-lang/native/pull/860

coverage: 92.648% (+0.06%) from 92.584%
when pulling 7a49e708fc4a72658585b92855e0389379dd19fb on ffigen-11
into 0ffdccc3a190c9d6d292f2fd77637ff13f4cdc8c on main.


Update ai.py

Just adding the comments in the code for people to understand what exactly is going on

Okay it can’t approved now because of the errors and issues . Could you
like us to rectify it sir
On Thu, Jun 15, 2023 at 12:29 AM Daniel Fjeldstad @.***>
wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/AntonOsika/gpt-engineer/pull/28#pullrequestreview-1480448640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BASR7VVKN5I7HQGBGJ4QZ5LXLJCO3ANCNFSM6AAAAAAZGJANOU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I think it's self explanatory for senior developers, will close, but thanks for trying to make it easier for beginners @AayushTech

Protip:
You can use chatGPT to explain code if you feel something is hard to understand. You can also ask it to explain it in a non-technical way, to simplify the language.


Additional events

Hello Team. Thanks for great plugin. Could you please expand  list of event handlers? It would be usefull to listen events like onLegendClick, onDoubleClick and etc.
Thank you.

Note to myself :

Use all listed events here : https://github.com/plotly/react-plotly.js/#event-handler-props
Could add a combo box to select an event and use one single associated text area to write the script


Described all controllers and beans for Swagger

Done by https://github.com/baradist/restful-money-transfer/pull/19


BlazorLeaflet not working in blazor hybrid (Maui-android)

You have to report the error too.

Project is dead?


rustup-toolchain: Rename ensure_installed() to install() and deprecate is_installed()

Rename ensure_installed() to install() for brevity. Deprecate is_installed() to make it clear it is not needed around install().

I want to get a release out today of all crates, so I will merge this right away.
Normally I try to do wait a day or two before I merge significant PRs.


add unit tests for server.py

Can we update the README with instructions on running the tests?

can you also create a requirements-dev.txt and add pytest package as a dependency?

can you also create a requirements-dev.txt and add pytest package as a dependency?

you read my mind.
jsut to be clear you want a seperate requirements file for development? Should I make a second setup.py type file or just include instruction to also install requirements-dev.txt

Note to self: check if there is a way to specify a list of test cases in a file or something for local testing


Stateless to Stateful refactoring crashes if the component includes props destructuring

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


Android Cursor Pointer is off center

Steps to Reproduce
Steps to reproduce

create new project flutter create -i swift -a kotlin cursor_pointer
add a text field

code sample

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or simply save your changes to "hot reload" in a Flutter IDE).
        // Notice that the counter didn't reset back to zero; the application
        // is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.display1,
            ),
            TextField(),
          ],
        ),
      ),

      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Occurs on all android devices

logs
jasons-mbp:cursor_pointer jasonzheng$ flutter run --verbose
[  +22 ms] executing: [/Volumes/Data/Sources/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +42 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] e70236e36ce1d32067dc68eb55519ec3e14b6b01
[        ] executing: [/Volumes/Data/Sources/flutter/] git describe --match v*.*.* --first-parent --long --tags
[  +19 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.10.7-0-ge70236e36
[   +7 ms] executing: [/Volumes/Data/Sources/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +13 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/beta
[        ] executing: [/Volumes/Data/Sources/flutter/] git ls-remote --get-url origin
[  +11 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +62 ms] executing: [/Volumes/Data/Sources/flutter/] git rev-parse --abbrev-ref HEAD
[  +12 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] beta
[  +14 ms] executing: sw_vers -productName
[  +27 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +23 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.14.6
[        ] executing: sw_vers -buildVersion
[  +26 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 18G103
[  +37 ms] executing: /usr/bin/xcode-select --print-path
[  +17 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +1 ms] executing: /usr/bin/xcodebuild -version
[ +125 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[   +3 ms] Xcode 11.2.1
           Build version 11B500
[  +63 ms] executing: /Users/jasonzheng/Library/Android/sdk/platform-tools/adb devices -l
[   +8 ms] Exit code 0 from: /Users/jasonzheng/Library/Android/sdk/platform-tools/adb devices -l
[        ] List of devices attached
           emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:5
[  +19 ms] executing: /Volumes/Data/Sources/flutter/bin/cache/artifacts/libimobiledevice/idevice_id -h
[  +51 ms] /usr/bin/xcrun simctl list --json devices
[ +150 ms] More than one device connected; please specify a device with the '-d <deviceId>' flag, or use '-d all' to act on all
devices.
[   +5 ms] /Users/jasonzheng/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell getprop
[  +38 ms] ro.hardware = ranchu
[   +5 ms] Android SDK built for x86 • emulator-5554                        • android-x86 • Android 9 (API 28) (emulator)
[   +1 ms] iPhone 8                  • 80FF753B-2016-49AD-B175-4663153BAB6D • ios         •
com.apple.CoreSimulator.SimRuntime.iOS-13-2
           (simulator)
[  +18 ms] "flutter run" took 650ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:276:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:528:11)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:457:33)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:157:29)
<asynchronous suspension>
#5      _rootRun (dart:async/zone.dart:1124:13)
#6      _CustomZone.run (dart:async/zone.dart:1021:19)
#7      _runZoned (dart:async/zone.dart:1516:10)
#8      runZoned (dart:async/zone.dart:1463:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:156:18)
<asynchronous suspension>
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:446:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:416:21)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:157:29)
<asynchronous suspension>
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:156:18)
<asynchronous suspension>
#19     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:367:19)
<asynchronous suspension>
#20     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:112:14)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:251:18)
#24     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:63:22)
<asynchronous suspension>
#25     _rootRun (dart:async/zone.dart:1124:13)
#26     _CustomZone.run (dart:async/zone.dart:1021:19)
#27     _runZoned (dart:async/zone.dart:1516:10)
#28     runZoned (dart:async/zone.dart:1500:12)
#29     run.<anonymous closure> (package:flutter_tools/runner.dart:61:18)
<asynchronous suspension>
#30     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:157:29)
<asynchronous suspension>
#31     _rootRun (dart:async/zone.dart:1124:13)
#32     _CustomZone.run (dart:async/zone.dart:1021:19)
#33     _runZoned (dart:async/zone.dart:1516:10)
#34     runZoned (dart:async/zone.dart:1463:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:156:18)
<asynchronous suspension>
#36     runInContext (package:flutter_tools/src/context_runner.dart:63:24)
<asynchronous suspension>
#37     run (package:flutter_tools/runner.dart:50:10)
#38     main (package:flutter_tools/executable.dart:65:9)
<asynchronous suspension>
#39     main (file:///Volumes/Data/Sources/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#40     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:303:32)
#41     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

jasons-mbp:cursor_pointer jasonzheng$ flutter analyze
Analyzing cursor_pointer...
No issues found! (ran in 2.8s)

Jasons-MacBook-Pro:flutter jasonzheng$ flutter doctor -v
[✓] Flutter (Channel beta, v1.11.0, on Mac OS X 10.14.6 18G103, locale en-US)
    • Flutter version 1.11.0 at /Volumes/Data/Sources/flutter
    • Framework revision 856a90e67c (2 weeks ago), 2019-11-08 18:00:01 -0800
    • Engine revision af04338413
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/jasonzheng/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 35.2.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.40.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.6.0

[✓] Connected device (2 available)
    • Android SDK built for x86 • emulator-5554                        •
      android-x86 • Android 9 (API 28) (emulator)
    • iPhone 8                  • 80FF753B-2016-49AD-B175-4663153BAB6D • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)

• No issues found!

Hi @StrawHt
I'm experiencing the situation you described also
with flutter create --androidx <my_app>
and Flutter Channel stable, v1.9.1+hotfix.6

sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {

  @override
  Widget build(BuildContext context) => MaterialApp(home:MyHomePage());
}

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {

  @override
  Widget build(BuildContext context) => Scaffold(
    body: Center(
      child: TextField(),
    ),
  );
}

thank you for your contribution

Issue exist

flutter doctor -v
[✓] Flutter (Channel dev, v1.18.0-6.0.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.18.0-6.0.pre at /Users/taha/Code/flutter_dev
    • Framework revision 84c84fb249 (3 days ago), 2020-04-20 21:35:01 -0400
    • Engine revision 2bde4f0ae4
    • Dart version 2.9.0 (build 2.9.0-1.0.dev a12c36dd97)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1
[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
[✓] VS Code (version 1.44.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1
[✓] Connected device (4 available)
    • Android SDK built for x86 • emulator-5554 • android-x86    • Android 10
      (API 29) (emulator)
    • macOS                     • macOS         • darwin-x64     • Mac OS X
      10.15.4 19E287
    • Chrome                    • chrome        • web-javascript • Google Chrome
      81.0.4044.122
    • Web Server                • web-server    • web-javascript • Flutter Tools
• No issues found!

This can also be seen in the StackOverflow question provided for issue #57591. It seems it may be showing up too aggressively.

Preview

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (4 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.0

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

[✓] Flutter (Channel master, 1.26.0-2.0.pre.179, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-2.0.pre.179 at /Users/tahatesser/Code/flutter_master
    • Framework revision a293c82251 (5 hours ago), 2021-01-05 04:04:03 -0500
    • Engine revision b7352132cd
    • Dart version 2.12.0 (build 2.12.0-179.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 10 (API 29)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 11.1 20C69 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 87.0.4280.88

• No issues found!

Preview

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (4 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.0

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

[✓] Flutter (Channel master, 1.26.0-2.0.pre.179, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-2.0.pre.179 at /Users/tahatesser/Code/flutter_master
    • Framework revision a293c82251 (5 hours ago), 2021-01-05 04:04:03 -0500
    • Engine revision b7352132cd
    • Dart version 2.12.0 (build 2.12.0-179.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.0

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 10 (API 29)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 11.1 20C69 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 87.0.4280.88

• No issues found!

This issue is reproducible on the latest stable and master channels. Verified on Samsung Galaxy Tab A7 Lite, Android 12 OneUI 4.1, SM-T225.

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.3.10 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (13 hours ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.7.0-10.0.pre.15, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.7.0-10.0.pre.15 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 76bb8ead5a (13 minutes ago), 2022-12-15 19:38:53 -0800
    • Engine revision 29196519c1
    • Dart version 3.0.0 (build 3.0.0-21.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

/cc @Renzo-Olivares


indentation in functions not reported correctly

goog.scope(function() {

  goog.foo = function() {
  alert(1)
}

})

Run:
jscs --preset=google test.js
Expected:
I would expect the indentation of alert to be flagged
Actual:
No error
This is particularly painful when running the auto-formatter because it will auto-format the goog.foo = ... line to the correct indentation, but format everything relative to it incorrectly

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11622901-indentation-in-functions-not-reported-correctly?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Duplicate of #1144

great, thanks!


Consider to use the lowest possible Rust version

Most of libraries which I used, needed to use the lowest possible Rust version(usually support latest 10 versions, so if newest is 1.58, latest supported is 1.48)
Lofty currently require Rust 1.57.0, which is only 1 release behind official Rust release.
To pack software for Ubuntu 20.04 I need to use specific Rust version, 1 week ago it was Rust 1.53.0, but now it is Rust 1.57.0(https://packages.ubuntu.com/search?keywords=rust&searchon=names&suite=impish&section=all)
For future I think that it would be great if lofty would pin to some older version of Rust to help to package apps which use this libraries on older/specific OS.

Hm, I hadn't thought about setting a MSRV. While I don't want to speak too early, I don't think it'll need to go above 1.57 anytime soon, since I just needed it for try_reserve. I can't guarantee that till 1.0, though.
And I wasn't aware that some distros were that far behind, thanks for bringing that to my attention. I'll take that into consideration if I do ever try to bump the version.

Looks that lofty needs now Rust 1.65.0 due https://github.com/rust-lang/rust/pull/96709
error[E0658]: generic associated types are unstable
   --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/lofty-0.10.0/src/traits.rs:137:2
    |
137 | /     type RefKey<'a>
138 | |     where
139 | |         Self: 'a;
    | |_________________^
    |
    = note: see issue #44265 <https://github.com/rust-lang/rust/issues/44265> for more information

It's unfortunate how far behind Ubuntu is, 1.65.0 is almost 2 months old at this point. Do they have a rule that they only push out the 4th release of rustc? Having gone 1.57.0 -> 1.61.0, I'd assume 1.65.0 is on its way sometime soon?


Update README.md

clarification about where to add the .env file
What does this PR do?
What issues does this PR fix or reference?
#
The PR fulfills these requirements:
[ ] Tests for the proposed changes have been added/updated.
[ ] Code linting and formatting was performed.
Functionality Before
<insert gif and/or summary>
Functionality After
<insert gif and/or summary>

Thanks for the suggestion.


[SCB-989]scan RestController to to make springmvc controller publish as ServiceComb Rest easier

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.01%) to 86.386% when pulling 058af34690a60504107bfd23f95599e9e9d8e8cf on liubao68:rest-controller into 344473f6e848cd858ee5393cfe8984881451b1d8 on apache:master.


Generated code for 2019-05-01/resources.

Installing AutoRest version: latest

@Abhijeet, do I need to keep this file?

Refers to: src/SDKs/_metadata/resources_resource-manager.txt:1 in 14dc580. [](commit_id = 14dc580c5a3149c86b6aca95f640429806c6b310, deletion_comment = False)


Handle clocks going backwards in BlazeRuntime.java

See https://groups.google.com/d/msgid/bazel-discuss/bb1ec5f3-7d73-4e5e-a089-a2beee0498df%40googlegroups.com?utm_medium=email&utm_source=footer.

Assigning Nathan based on the "random person on core" approach.


ENOTEMPTY tree_merger-temp_dest_dir on almost every compile, not making symlinks, 30 sec build time on Windows

This is a follow-up to: https://github.com/ember-cli/ember-cli/issues/4375 and https://github.com/broccolijs/broccoli/issues/232
I keep getting ENOTEMPTY tree_merger-temp_dest_dir errors on almost every compile, 30 sec build time on:
Windows 7
ember-cli 0.2.7
node 0.12.2
The error references rmkidsSync at rmdirSync in ember-cli\node_modules\quick-temp\node_modules\rimraf\rimraf.js.  I am not sure how to get the actual error output.
I have taken all the precautions related to getting rid of Broccoli compilation errors:
--no Sublime Text tmp monitoring
--ember-cli-windows
--antivirus not scanning folders
--Windows Defender, Windows search disabled in those folders
--only one CMD window open to my project root at a time
--reinitialized project (removed tmp,node_modules,bower_components, reinstalled everything according to Ember-CLI upgrade procedure
However, I still get ENOTEMPTY tree_merger-temp_dest_dir... errors every time, and compilation of my app takes 30 seconds.
One answer I might have is that, while mklink works find for making symlinks in an Admin window for me, npm's can-symlink says that I am unable to make symlinks.  Could this be related?

Although not perfect, we have greatly improved windows performance. We have not reach a perfect state, but has improved since 2015. Also since then windows folks have made it possible for developers to utilize symlinks: https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/
the linked issue has also been closed: https://github.com/ember-cli/ember-cli/issues/4375#issuecomment-166503798
I am also going to close this one.
For future windows related performance issues:

hard-errors should be reported (although ideally on the plugin they originated from)
performance issues, please be sure you are using windows provided symlinks before reporting.


fix: Pass disabledLanguages to InstallGuide

When opening the InstallGuide, pass disabledLanguages so it can be made
available to nested components.

How are the Vue components getting access to the information from the analyzer in python.disabled.ts? The analyzer is in the extension, but the Vue components are in a dependency (@appland/components).

Sorry for being unclear. I haven't followed the entire execution chain, but the data from the analyzers eventually ends up in the projects prop (line 43 of InstallGuide.vue). I found that when I was rendering the project picker, the data in projects was sufficient—I didn't end up using the disabledLanguages prop.

Yup! I'll remove disabledLanguages 👍


Update russian translations for week(s)

Update russian translations for week(s)

Codecov Report

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

@@          Coverage Diff          @@
##           master   #654   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      8
  Lines        1548   1548
  Branches      237    237
=====================================
  Hits         1548   1548

Impacted Files
Coverage Δ

arrow/locales.py
100% <ø> (ø)
:arrow_up:

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 29c7ed9...4460395. Read the comment docs.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #654   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      8
  Lines        1548   1548
  Branches      237    237
=====================================
  Hits         1548   1548

Impacted Files
Coverage Δ

arrow/locales.py
100% <ø> (ø)
:arrow_up:

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 29c7ed9...4460395. Read the comment docs.

LGTM, but I had a general question for @rdtq or @systemcatch: why is there a list of translations for each time frame in RU rather than a single one?

LGTM, but I had a general question for @rdtq or @systemcatch: why is there a list of translations for each time frame in RU rather than a single one?

@jadchaar, it's just that in Russian language the exact spelling of the word depends on what number precedes it: 1 неделя, 2 недели, 5 недель


Reassess the handling of Hetero atoms

I am not sure the current placement (of separate Hetero Chains) is flexible enough to handle all valid ways to use hetero atoms. I propose to take a look at other PDB packages to see how they handle Hetero atoms and look again at the PDB file format to see if another placement would be better.

All PDB libraries I could find (CCTBX, Biopython) save the Hetero information in each atom individually. So I propose to rework pdbtbx to also do that.


Document .with in cheatsheet

There is a commit for that: 3a46c33e6de687032d96e262828339d4ea8cf682 But it's not published yet.


translation BaseArrayHelper

Signed-off-by: jack.spanrrows<EMAIL_ADDRESS>

Q
A

Is bugfix?
yes/no

New feature?
yes/no

Breaks BC?
yes/no

Tests pass?
yes/no

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

update


The library does not work with projects that do not support kotlin

This plugin's Android part is written in Kotlin. Of course support Kotlin.


PersistentVolumeClaim remains Pending in latest Kubernetes v1.20.0

Description
Hi there.
I recently upgraded a bare-metal Kubernetes cluster to the latest v1.20.0. But since then, I am no longer able to provision additional PersistentVolumes. Existing PVCs which were already bound prior to the upgrade still work flawlessly.
I am using OpenEBS 2.3.1.
For reference, here is a simple PVC I requested for testing :
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: demo-vol-claim
spec:
  storageClassName: openebs-jiva-default
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5G

All Persistent Volumes Claims I requested remained in a Pending state, with the following kind of events reported:
❯ kubectl describe pvc demo-vol-claim
Name:          demo-vol-claim
Namespace:     lemra-services
StorageClass:  openebs-jiva-default
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: openebs.io/provisioner-iscsi
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       <none>
Events:
  Type    Reason                Age                From                         Message
  ----        ------                    ----                  ----                             -------
  Normal  ExternalProvisioning  14s (x3 over 18s)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "openebs.io/provisioner-iscsi" or manually created by system administrator

And below are the logs of the Provisioner Pod:
I1213 21:20:58.152297       1 volume.go:73] OpenEBS volume provisioner namespace openebs                                                                                │
│ I1213 21:20:58.315842       1 main.go:108] Leader election enabled for openebs-provisioner via leaderElectionKey                                                                                │
│ I1213 21:20:58.316608       1 leaderelection.go:187] attempting to acquire leader lease  openebs/openebs.io-provisioner-iscsi...                                                                                │
│ E1213 21:21:16.902104       1 event.go:259] Could not construct reference to: '&v1.Endpoints{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"openebs.io-provisioner-iscsi", GenerateName:"",  │
│ Namespace:"openebs", SelfLink:"", UID:"b8174671-83ef-4590-b05f-32ea48de5517", ResourceVersion:"117101955", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63743490525, loc:(*time.Location)(0x1ce99c │
│ 0)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string{"control-plane.alpha.kubernetes.io/leader":"{\"holderIdentity\":\"openebs- │
│ provisioner-545b9fc548-s9scb_17bf54b0-3d89-11eb-bfae-4ed2b5bfd930\",\"leaseDurationSeconds\":15,\"acquireTime\":\"2020-12-13T21:21:16Z\",\"renewTime\":\"2020-12-13T21:21:16Z\",\"leaderTransitions\":1}"}, OwnerReference │
│ s:[]v1.OwnerReference(nil), Initializers:(*v1.Initializers)(nil), Finalizers:[]string(nil), ClusterName:""}, Subsets:[]v1.EndpointSubset(nil)}' due to: 'selfLink was empty, can't make reference'. Will not report event: │
│  'Normal' 'LeaderElection' 'openebs-provisioner-545b9fc548-s9scb_17bf54b0-3d89-11eb-bfae-4ed2b5bfd930 became leader'                                                                                │
│ I1213 21:21:16.902248       1 leaderelection.go:196] successfully acquired lease openebs/openebs.io-provisioner-iscsi                                                                                │
│ I1213 21:21:16.902402       1 controller.go:636] Starting provisioner controller openebs.io/provisioner-iscsi_openebs-provisioner-545b9fc548-s9scb_17bf54b0-3d89-11eb-bfae-4ed2b5bfd930!                                   │
│ I1213 21:21:17.102706       1 controller.go:685] Started provisioner controller openebs.io/provisioner-iscsi_openebs-provisioner-545b9fc548-s9scb_17bf54b0-3d89-11eb-bfae-4ed2b5bfd930!                                    │
│ I1213 21:21:42.119418       1 controller.go:991] provision "lemra-services/demo-vol-claim" class "openebs-jiva-default": started                                                                                │
│ E1213 21:21:42.281288       1 controller.go:1008] provision "lemra-services/demo-vol-claim" class "openebs-jiva-default": unexpected error getting claim reference: selfLink was empty, can't make reference

Expected Behavior
I expected the PVC to be bound, but maybe I'm missing something.
Current Behavior
The PVC remains Pending forever, making OpenEBS storage classes not that useful.
Possible Solution
Per the Kubernetes 1.20.0 release notes, SelfLink has been removed (deprecated in 1.16), but I may be missing something.
Until this issue gets fixed, my workaround at this time is to disable the RemoveSelfLink feature gate in the kube-apiserver system component. This is a workaround suggested in kubernetes-sigs/nfs-subdir-external-provisioner#25.
Steps to Reproduce

Kubernetes 1.20.0+
OpenEBS 2.3.1
Create a new PVC resource, e.g.:

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: demo-vol-claim
spec:
  storageClassName: openebs-jiva-default
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5G

Your Environment

Kubernetes 1.20.0
OpenEBS 2.3.1

Thanks @rm3l for reporting this. I will take this up.

I am not super familiar with the OpenEBS suite however updating k8s.io modules to v0.16.x+ should fix it, which means you need to use sig-storage-lib-external-provisioner v5 or higher (you're using 4.1.0 mostly).

Hey folks, I'm also seeing this issue on a freshly installed K8's v1.20.0 cluster:
I1215 23:15:27.132409       1 controller.go:991] provision "default/data-pg-postgresql-0" class "openebs-cstor": started
E1215 23:15:27.143808       1 controller.go:1008] provision "default/data-pg-postgresql-0" class "openebs-cstor": unexpected error getting claim reference: selfLink was empty, can't make reference

Yeah, current workaround linked above: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/25#issuecomment-742616668

Just a quick update on this one.
I am still working through refactoring the https://github.com/openebs/external-storage repo to move towards latest K8s. These provisioners are currently dependent on 1.12.
To do this, the following steps are involved and I should be able to complete them by Friday:

migrate the openebs provisioners to their own repo to make it easier to fix the current issue and also to resolve such dependencies at a faster pace in the future.
update the k8s and client-go to at least 1.18 or above.
need to get this tested with a 1.20 cluster and also with older clusters ( run the release pipelines on different k8s versions).

Till the fix is made available, the following alternatives seems to work well:

For Jiva deployments, disable the --feature-gates=RemoveSelfLink=false in the kube-apiserver as mentioned in the above comment would work.
For cStor, please consider moving towards the cStor CSI driver-based deployment as detailed here: https://github.com/openebs/cstor-operators

Great — thanks for the update @kmova !

Extracted the openebs-provisioner code to this repo. https://github.com/openebs/openebs-k8s-provisioner
Updated it to make use of 1.17.3 Kubernetes at the moment - inline with the dependencies used by other openebs provisioners. We can bump this higher for all the provisioner if required.
Development images for the provisioner with kubernetes dependency upgraded is available at: openebs/openebs-k8s-provisioner-amd64-ci:develop-e3a6a55
Can anyone here help with testing this image and let me know if this resolved the issue?

@kmova I just upgraded my OpenEBS Helm Release to use the provisioner image you mentioned:
helm upgrade --install openebs --namespace openebs openebs/openebs --version 2.3.1 \
  --set provisioner.image=openebs/openebs-k8s-provisioner-amd64-ci \
  --set provisioner.imageTag=develop-e3a6a55

I can confirm this fixes the issue on my side in my K8s v1.20.0 cluster, at least for a Jiva deployment. 👍🏿
I do not use cStor, so unfortunately cannot confirm if it is fixed for it.
Provisioner logs:
│ I1216 22:17:03.621973       1 controller.go:1211] provision "lemra-services/demo-vol-claim" class "openebs-jiva-default": started                                                                                │
│ I1216 22:17:03.784561       1 event.go:281] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"lemra-services", Name:"demo-vol-claim", UID:"313321d5-8ee9-4996-8963-86921ff66b48", APIVersion:"v1", Resourc │
│ eVersion:"117808297", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "lemra-services/demo-vol-claim"                                                          │
│ E1216 22:17:05.955346       1 volume.go:176] HTTP Status error from maya-apiserver: Not Found                                                                                │
│ I1216 22:17:05.955697       1 volume.go:105] CAS Volume Spec Created:                                                                                │
│ {"metadata":{"name":"pvc-313321d5-8ee9-4996-8963-86921ff66b48","namespace":"lemra-services","creationTimestamp":null,"labels":{"openebs.io/namespace":"lemra-services","openebs.io/persistentvolumeclaim":"demo-vol-claim" │
│ ,"openebs.io/storageclass":"openebs-jiva-default"}},"spec":{"capacity":"5G","iqn":"","targetPortal":"","targetIP":"","targetPort":"","replicas":"","casType":"","fsType":"","lun":0},"cloneSpec":{},"status":{"Phase":""," │
│ Message":"","Reason":""}}                                                                                │
│ I1216 22:17:09.090660       1 volume.go:132] volume Successfully Created:                                                                                │
│ {"apiVersion":"v1alpha1","kind":"CASVolume","metadata":{"annotations":{"openebs.io/storageclass-version":"4862"},"labels":{"openebs.io/cas-template-name":"jiva-volume-create-default-2.3.0","openebs.io/persistent-volume │
│ -claim":"demo-vol-claim","openebs.io/version":"2.3.0"},"name":"pvc-313321d5-8ee9-4996-8963-86921ff66b48"},"spec":{"accessMode":"","capacity":"5G","casType":"jiva","fsType":"","iqn":"iqn.2016-09.com.openebs.jiva:pvc-313 │
│ 321d5-8ee9-4996-8963-86921ff66b48","lun":0,"replicas":"3","targetIP":"\u003cno value\u003e","targetPort":"3260","targetPortal":"<IP_ADDRESS>:3260"},"status":{"Message":"","Phase":"","Reason":""}}                       │
│ I1216 22:17:13.383837       1 controller.go:1293] provision "lemra-services/demo-vol-claim" class "openebs-jiva-default": volume "pvc-313321d5-8ee9-4996-8963-86921ff66b48" provisioned                                    │
│ I1216 22:17:13.384046       1 controller.go:1310] provision "lemra-services/demo-vol-claim" class "openebs-jiva-default": succeeded                                                                                │
│ I1216 22:17:13.384175       1 volume_store.go:212] Trying to save persistentvolume "pvc-313321d5-8ee9-4996-8963-86921ff66b48"                                                                                │
│ I1216 22:17:13.569265       1 volume_store.go:219] persistentvolume "pvc-313321d5-8ee9-4996-8963-86921ff66b48" saved                                                                                │
│ I1216 22:17:13.569820       1 event.go:281] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"lemra-services", Name:"demo-vol-claim", UID:"313321d5-8ee9-4996-8963-86921ff66b48", APIVersion:"v1", Resourc │
│ eVersion:"117808297", FieldPath:""}): type: 'Normal' reason: 'ProvisioningSucceeded' Successfully provisioned volume pvc-313321d5-8ee9-4996-8963-86921ff66b48

❯ kubectl get pvc,pv
NAME                                                   STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS           AGE
persistentvolumeclaim/demo-vol-claim                   Bound    pvc-313321d5-8ee9-4996-8963-86921ff66b48   5G         RWO            openebs-jiva-default   4m18s

NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                           STORAGECLASS           REASON   AGE
persistentvolume/pvc-313321d5-8ee9-4996-8963-86921ff66b48   5G         RWO            Delete           Bound    lemra-services/demo-vol-claim                   openebs-jiva-default            4m8s

Thanks.

@kmova I just updated my OpenEBS installation (via Operatorhub) to use the Development Image.
I can confirm this fixes the issue on my side in my new K8s cluster (v1.20.0) with a cStor deployment. 👍
gimstein@exor ❯ kubectl get nodes
NAME                         STATUS   ROLES                           AGE    VERSION
xxxxxxxxxxxxxxxxx   Ready      control-plane,master   5d9h   v1.20.0
xxxxxxxxxxxxxxxxx   Ready      worker                           5d8h   v1.20.0
xxxxxxxxxxxxxxxxx   Ready      worker                           5d8h   v1.20.0

gimstein@exor ❯ kubectl get pods -n openebs-storage | egrep "(provisioner|pvc)"
openebs-a6lx9mun85dajn35auwd09d7f-localpv-provisioner-6c48pfvhc   1/1     Running   0          3d2h
openebs-a6lx9mun85dajn35auwd09d7f-provisioner-5bc6c8bd74-w5l9s    1/1     Running   0          5m53s
pvc-17541d5f-be35-4d62-a520-e096f7a3b547-target-bc4ffb776-q28dx   3/3     Running   0          3m47s

gimstein@exor ❯ kubectl get pvc,pv
NAME                                      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS    AGE
persistentvolumeclaim/test-cstor-volume   Bound    pvc-17541d5f-be35-4d62-a520-e096f7a3b547   500Mi      RWO            openebs-cstor   4m2s

NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                       STORAGECLASS    REASON   AGE
persistentvolume/pvc-17541d5f-be35-4d62-a520-e096f7a3b547   500Mi      RWO            Delete           Bound    default/test-cstor-volume   openebs-cstor            4m2s

Provisioner Log:
I1217 20:07:03.400964       1 leaderelection.go:252] successfully acquired lease openebs-storage/openebs.io-provisioner-iscsi
I1217 20:07:03.402969       1 event.go:281] Event(v1.ObjectReference{Kind:"Endpoints", Namespace:"openebs-storage", Name:"openebs.io-provisioner-iscsi", UID:"ae285c38-9a49-4356-8a74-88cdc7f4cec2", APIVersion:"v1", ResourceVersion:"1143884", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' openebs-a6lx9mun85dajn35auwd09d7f-provisioner-5bc6c8bd74-w5l9s_b35b575e-273a-4f4f-afc0-9ba67a74604b became leader
I1217 20:07:03.403640       1 controller.go:780] Starting provisioner controller openebs.io/provisioner-iscsi_openebs-a6lx9mun85dajn35auwd09d7f-provisioner-5bc6c8bd74-w5l9s_b35b575e-273a-4f4f-afc0-9ba67a74604b!
I1217 20:07:03.504004       1 controller.go:829] Started provisioner controller openebs.io/provisioner-iscsi_openebs-a6lx9mun85dajn35auwd09d7f-provisioner-5bc6c8bd74-w5l9s_b35b575e-273a-4f4f-afc0-9ba67a74604b!
I1217 20:08:38.359385       1 controller.go:1211] provision "default/test-cstor-volume" class "openebs-cstor": started
I1217 20:08:38.368529       1 event.go:281] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-cstor-volume", UID:"17541d5f-be35-4d62-a520-e096f7a3b547", APIVersion:"v1", ResourceVersion:"1144197", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/test-cstor-volume"
E1217 20:08:38.460819       1 volume.go:176] HTTP Status error from maya-apiserver: Not Found
I1217 20:08:38.461069       1 volume.go:105] CAS Volume Spec Created:
{"metadata":{"name":"pvc-17541d5f-be35-4d62-a520-e096f7a3b547","namespace":"default","creationTimestamp":null,"labels":{"openebs.io/namespace":"default","openebs.io/persistentvolumeclaim":"test-cstor-volume","openebs.io/storageclass":"openebs-cstor"}},"spec":{"capacity":"500Mi","iqn":"","targetPortal":"","targetIP":"","targetPort":"","replicas":"","casType":"","fsType":"","lun":0},"cloneSpec":{},"status":{"Phase":"","Message":"","Reason":""}}
I1217 20:08:38.731536       1 volume.go:132] volume Successfully Created:
{"apiVersion":"v1alpha1","kind":"CASVolume","metadata":{"labels":{"openebs.io/cas-template-name":"cstor-volume-create-default-1.5.0","openebs.io/version":"1.5.0"},"name":"pvc-17541d5f-be35-4d62-a520-e096f7a3b547"},"spec":{"accessMode":"","capacity":"500Mi","casType":"cstor","fsType":"","iqn":"iqn.2016-09.com.openebs.cstor:pvc-17541d5f-be35-4d62-a520-e096f7a3b547","lun":0,"replicas":"2","targetIP":"<IP_ADDRESS>","targetPort":"3260","targetPortal":"<IP_ADDRESS>:3260"},"status":{"Message":"","Phase":"","Reason":""}}
I1217 20:08:38.894947       1 controller.go:1293] provision "default/test-cstor-volume" class "openebs-cstor": volume "pvc-17541d5f-be35-4d62-a520-e096f7a3b547" provisioned
I1217 20:08:38.895038       1 controller.go:1310] provision "default/test-cstor-volume" class "openebs-cstor": succeeded
I1217 20:08:38.895048       1 volume_store.go:212] Trying to save persistentvolume "pvc-17541d5f-be35-4d62-a520-e096f7a3b547"
I1217 20:08:38.916799       1 volume_store.go:219] persistentvolume "pvc-17541d5f-be35-4d62-a520-e096f7a3b547" saved
I1217 20:08:38.916879       1 event.go:281] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-cstor-volume", UID:"17541d5f-be35-4d62-a520-e096f7a3b547", APIVersion:"v1", ResourceVersion:"1144197", FieldPath:""}): type: 'Normal' reason: 'ProvisioningSucceeded' Successfully provisioned volume pvc-17541d5f-be35-4d62-a520-e096f7a3b547

Thanks you @rm3l @gimstein for verifying the fix on cStor and Jiva.
The new image openebs/openebs-k8s-provisioner:2.4.1 has been created and the latest helm chart and https://github.com/openebs/charts/blob/gh-pages/openebs-operator.yaml have been updated with this new version.

As an aside - if you are already using OpenEBS in production, you can help the project reach the incubation stage by updating your usage details in https://github.com/openebs/openebs/blob/master/ADOPTERS.md or by commenting here: https://github.com/openebs/openebs/issues/2719


Bug: program kprobe_skb_2: load program: permission denied

When I used the pwru on the machine, I had an error:
# sudo ./pwru 'dst host <IP_ADDRESS> and icmp'
...
program kprobe_skb_2: load program: permission denied: invalid indirect read from stack off -40+0 size 8 (10961 line(s) omitted)

# uname -a
Linux  5.4.119-19-0008 #1 SMP Mon Sep 13 14:54:39 CST 2021 x86_64 x86_64 x86_64 GNU/Linux
# ./pwru --version
pwru v1.0.6

How should I check this question?

It's weird since we have 5.4 kernel covered in CI :joy_cat: :sob:
https://github.com/cilium/pwru/actions/runs/9267298652/job/25493627219
Would you like to try a newer version of kernel?  5.4.119 was released on 14-May-2021, a bit out of date (

Otherwise, can you provide the complete error log?

error.log
I have the same problem, the log is attached.


Batch conversions

So I've had a littlebit of experience with batch conversions with Pipeline 2 here at NLB now. I'm converting a directory of 4000+ DTBooks to EPUB3. It takes a lot of time (a couple of days probably if I tried to convert everything, I'm currently converting 100 random books at a time).
The features needed to support batch conversions using Pipeline 2 as I see it is:

the ability to associate a "batch ID" with a job
the ability to get the status for a batch ID; i.e. number of jobs in each of the possible job states
the ability to list all jobs associated with a batch ID
the ability to delete all jobs associated with a batch ID
the ability to get a HTML report for a batch ID, with links to individual jobs (execution log, detailed log, reports, outputs, option values, ...)

wdyt?

https://github.com/daisy/pipeline-framework/pull/79


[Intercom] Launcher is disabled in settings or current page does not match display conditions

Describe the bug
When I open a webgl context. the intercom vanishes. And later it prints the following message in the console.
" [Intercom] Launcher is disabled in settings or current page does not match display conditions "
To Reproduce
Steps to reproduce the behavior:

Open a webgl context
That's it!

Expected behavior
Should not be vanishing
Desktop (please complete the following information):

OS: [Mac OS]
Browser [chrome, firefox]

@adiathasan how did you resolve this? Running into the same issue.

I am seeing the same issue intermittently in our web app that embeds intercom.
Getting a 400 Bad Request returned from https://api-iam.intercom.io/messenger/web/ping


How do I use this?

As a newb, I'm not clear on how this repo works with (or instead of) zmk-firmware. I see there's a gh action to build this, but it doesn't output a uf2 to drop into my (xiao BLE) mcu board. I assume we're missing something to make use of this. Maybe this repo gets dropped into the zmk-firmware repo, and that builds the uf2?
I just don't understand yet.

You can download the firmware.zip file from actions tab which has 3 uf2 files for left, right and reset. See the actions docs for steps.

While it builds for me in your repo, my fork fails.

This is just me being a beginner.


map_view incompatible with flutter_test

Seems like map_view cannot work with Dart 2 yet.

Dup or https://github.com/google/uri.dart/issues/34
Workaround - add this to pubspec.yaml
dependency_overrides:
  quiver: ^2.0.0


i

ii

@tejaamadasu Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

ii


WTF?!

This is just a polite "fuck off" for @PyroSamurai.
You decided to try to take over the original justdelete.me project because you thought it was no longer maintained. Fair enough.
But you (or maybe @tupaschoal) decided to create a new repository from scratch and copy the code, instead of forking the old one on Github, and you don't point to the old repository anywhere. This might start to rub the line between "fair enough" and "disrespectful".
But @PyroSamurai, you opened up an issue (#86) and decided to spam everyone you saw in the other repository - hundreds of people. Why? You said, and I quote, "It was the most efficient way." The most efficient way of doing what? Spamming people?
Even worse, when people complained about what you did, you deleted their comments and finally closed the thread to prevent further complaints. This goes way beyond disrespectful.
 You're a kid and feel empowered that you're trying to take over a big project that has lots of visibility. No problem.  You're only accomplishing the exact opposite of what you intended. As in, people suggesting everyone affected reports you for abuse, or that everyone affected opens a new issue here complaining about what you did.

Sorry, but I need to do such an action to annoy someone:
👍
(Yes, I know I can use reactions 😜 )

Hello @borfast,
Let me clear some things up. We didn't think the original repo is abandoned, it is. We asked the original owner to transfer it to our ownership so we could maintain it and he said he couldn't, because he doesn't hold it anymore. It was sold to a shady organization who just placed it into a questionable domain and forgot about it.
I didn't copy the code, I forked it, but when we found out the original one was going nowhere, we decided to detach it. There are multiple downsides of being a fork, like not showing up in searches or not having the contributions counted for the people helping us. I think this still is fair enough. I haven't changed the license and it still credits the original owner.
As for tagging everyone, I won't dicuss,  because it was questionable. The idea was: "hey, this project you liked wasn't abandoned, we're keeping it alive here".
I'm keeping the issue open if anyone wants to ask or discuss anything else. I apologise!

We didn't think the original repo is abandoned, it is.

No one is questioning that. It does seem abandoned.

As for tagging everyone, I won't dicuss, because it was questionable.

No, it was not questionable, it was disrespectful and a very childish attitude, and you, as the creator of this new repo, should discuss it. Unlocking the other thread is probably not a good idea because it will only allow more spam to get through to the affected people but perhaps unlock it, post a public apology, and lock it again. You guys as a team should publicly acknowledge the mistake and apologize there.

The idea was: "hey, this project you liked wasn't abandoned, we're keeping it alive here".

I think everyone understood what the idea was but the approach, and especially the attitude towards complaints, was very, very wrong.

When I said "won't discuss it" I kind of intended to say that I wouldn't come up with any excuses, but would be open to discussing it on this thread, if  you wanted, which is what we're doing.
I've opened #88 with the public apology, I don't think it is wise to spam everyone again on #86, even more because those who disliked it the most will have already unsubscribed and won't get the message anyway.
I apologise, again.

#86

I recommend reporting it as abuse. I did. https://github.com/contact/report-abuse


⚠ Jenkins Plugins Artifactory has degraded performance

In 285942b, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1197 ms

Resolved: Jenkins Plugins Artifactory performance has improved in cee428e after 1 hour, 48 minutes.


Support https connections

Is your feature request related to a problem? Please describe.
The gRPC request client is hardcoded to use InsecureChannelCredentials: https://github.com/NVIDIA/triton-inference-server/blob/466dbdf96518e3a16fb4e39a97e29254affbe25b/src/clients/c%2B%2B/api_v1/library/request_grpc.cc#L61
Describe the solution you'd like
The option to use SecureChannelCredentials for https server URLs should be added.
Describe alternatives you've considered
N/A
Additional context
Some servers may be required to be behind https for security reasons.

@kpedro88 maybe you could get away with putting a reverse proxy in front of your triton server for TLS termination.


Update virtual-nodes.md

Updated Azure Files support to include V2

Learn Build status updates of commit f311247:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/virtual-nodes.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@MGoedtel Thank you for the suggestion, I believe I have edited the file correctly and submitted it for review. Please let me know if you aren't seeing or have any other suggestions!


[Feature Request] Better spacing and ordering of reactions

Potentially related to #753 and this desktop ticket. Below are some photos from Isaac.

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @CSab6482 in #android-requests.

Completed in full rewrite