Resolve long wait times for hosted runners

Hosted runners for actions are taking a very long time to pick up an agent
https://github.com/microsoftgraph/msgraph-developer-proxy/actions/runs/3590639181/jobs/6044235558

@gavinbarron can we consider this issue as closed given @MIchaelMainer comment https://github.com/microsoftgraph/msgraph-developer-proxy/pull/36#issuecomment-1335864857?

Configured to support two agents.

Hey @MIchaelMainer, @gavinbarron, it seems like the issue still not solved unfortunately. Here's a screenshot of recent tasks that have been queued for over 11 hours:

We had something similar with the recent release that was queued for almost 20h and had to be restarted: https://github.com/microsoftgraph/msgraph-developer-proxy/actions/runs/3831328422/attempts/1.
Is there anything else that we could check to address this issue?

Ugh, I'm sorry this is happening. I just canceled the last remaining job. It appears that some jobs got picked up and completed. Did you do any actions that resulted in those jobs getting picked up?
I may need to go back and recreate the runner as believe there is some brittleness around setting config at creation time versus update. I don't think there is much you can do but cancel jobs and wait some time for the vm to be deallocated before requesting a new run.

Thank you, and I appreciate your help @MIchaelMainer. The only thing I've done was to follow your last recommendation, cancel and then re-start the jobs stuck in queue.

@waldekmastykarz
I suspect that this continuous getting stuck state is happening when a VM is allocated. If the VM stays allocated and is in the bad state, the subsequent jobs regardless of whether they are new or rerunning of existing jobs, won't be assigned. If the VM is shut down, and existing jobs are cancelled, and a new VM is allocated in response to the running of a job, that may be how we get unstuck.
If this is too disruptive, we can go back to using GitHub images, and we can figure this out later. Probably more like retry later and hope that the runners are more reliable by then.

@gavinbarron any preference for the path forward from your side?
To me it's an inconvenience but just that. We know that it can happen and we know a workaround. If switching back to GitHub images has other downsides, then we should keep the current setup.

We know the work around at present and it's annoying. but workable.
We're hoping to be able to use this repo as a blueprint for how we configure our open source repos going forward so it's important to me that we try to work with the 1ES systems as much as we can.
Given that I'd like to stick with the 1ES hosted agents and perhaps @MIchaelMainer can investigate the option of recreating the runner to see if that has any impact. If it becomes too onerous, we should pivot to using the GitHub runners.

Shall we close this issue for now then and reopen in the future if need be?

Yes, closing


Add Single Document Translator API definition

Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[x] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

fix https://github.com/Azure/azure-rest-api-specs/issues/26682

@chunyu3 , dotnet sdk generation failed by model name violation.
10:52:04.984 cmdout 	[Invoke-GenerateAndBuildV2.ps1]   Restored /mnt/vss/_work/1/s/azure-sdk-for-net/sdk/azure.ai.documenttranslation/Azure.AI.DocumentTranslation/src/Azure.AI.DocumentTranslation.csproj (in 2.12 sec).
10:52:07.243 cmdout 	[Invoke-GenerateAndBuildV2.ps1]   Restored /mnt/vss/_work/1/s/azure-sdk-for-net/sdk/azure.ai.documenttranslation/Azure.AI.DocumentTranslation/tests/Azure.AI.DocumentTranslation.Tests.csproj (in 4.39 sec).
10:52:07.243 cmdout 	[Invoke-GenerateAndBuildV2.ps1]   Restored /mnt/vss/_work/1/s/azure-sdk-for-net/sdk/core/Azure.Core.TestFramework/src/Azure.Core.TestFramework.csproj (in 4.39 sec).
10:52:14.198 cmdout 	[Invoke-GenerateAndBuildV2.ps1] /mnt/vss/_work/1/s/azure-sdk-for-net/sdk/azure.ai.documenttranslation/Azure.AI.DocumentTranslation/src/Generated/DocumentTranslateRequest.cs(14,26): error AZC0030: Model name 'DocumentTranslateRequest' ends with 'Request'. Suggest to rename it to 'DocumentTranslateContent' or any other appropriate name. [/mnt/vss/_work/1/s/azure-sdk-for-net/sdk/azure.ai.documenttranslation/Azure.AI.DocumentTranslation/src/Azure.AI.DocumentTranslation.csproj::TargetFramework=netstandard2.0]
10:52:14.978 cmdout 	[Invoke-GenerateAndBuildV2.ps1]   Azure.Core.TestFramework -> /mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/bin/Azure.Core.TestFramework/Debug/net47/Azure.Core.TestFramework.dll
10:52:15.221 cmdout 	[Invoke-GenerateAndBuildV2.ps1]   Azure.Core.TestFramework -> /mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/bin/Azure.Core.TestFramework/Debug/net7.0/Azure.Core.TestFramework.dll
10:52:15.271 cmdout 	[Invoke-GenerateAndBuildV2.ps1]   Azure.Core.TestFramework -> /mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/bin/Azure.Core.TestFramework/Debug/net6.0/Azure.Core.TestFramework.dll
10:52:15.380 cmdout 	[Invoke-GenerateAndBuildV2.ps1] Build FAILED.
10:52:15.380 cmdout 	[Invoke-GenerateAndBuildV2.ps1] /mnt/vss/_work/1/s/azure-sdk-for-net/sdk/azure.ai.documenttranslation/Azure.AI.DocumentTranslation/src/Generated/DocumentTranslateRequest.cs(14,26): error AZC0030: Model name 'DocumentTranslateRequest' ends with 'Request'. Suggest to rename it to 'DocumentTranslateContent' or any other appropriate name. [/mnt/vss/_work/1/s/azure-sdk-for-net/sdk/azure.ai.documenttranslation/Azure.AI.DocumentTranslation/src/Azure.AI.DocumentTranslation.csproj::TargetFramework=netstandard2.0]
10:52:15.380 cmdout 	[Invoke-GenerateAndBuildV2.ps1]     0 Warning(s)
10:52:15.381 cmdout 	[Invoke-GenerateAndBuildV2.ps1]     1 Error(s)

@msyyc looks like there has no artifact being generated for python.
10:48:43.481 info 	changelogScript is not configured
10:48:43.481 error 	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
10:48:43.481 info 	Skip artifact search
10:48:43.481 info 	Upload 0 artifact:

@MaryGao the generated JS code fails in the build.
10:46:48.364 cmderr 	[automation_generate.sh] [ERROR] Error:
10:46:48.365 cmderr 	[automation_generate.sh] [ERROR] An error occurred while run build for typespec project: "specification/translation/Azure.AI.DocumentTranslation":
10:46:48.365 cmderr 	[automation_generate.sh] [ERROR] Err: Wrong package path /mnt/vss/_work/1/s/azure-sdk-for-js/sdk/azure.ai.documenttranslation/azure-ai-documenttranslation-rest;
10:46:48.365 cmderr 	[automation_generate.sh] [ERROR] Stderr: "undefined"
10:46:48.365 cmderr 	[automation_generate.sh] [ERROR] Stdout: "undefined"
10:46:48.365 cmderr 	[automation_generate.sh] [ERROR] ErrorStack: "undefined"
10:46:48.365 cmderr 	[automation_generate.sh] [ERROR] Cannot read properties of undefined (reading 'module')

/azp run


Remove logger property from IContainerContext

In this PR, logger is set as an optional property in IContainerContext interface. In  the next release, the property will be removed from IContainerContext interface and ContainerContext class. In ContainerRuntime, last-ditch TaggedLoggerAdapter fallback is still present.
TaggedLoggerAdapter is deprecated in this PR. It can be removed once it's usage is remove from ContainerRuntime.
Resolves: https://github.com/microsoft/FluidFramework/issues/8191

will there be a followup to create and consume a container-definitons prerelease along with a breaking.md entry?

Yes - Breaking.md change is missing.
@sdeshpande3 , I'd imagine this removal should not cause build issues, but you ran it with symlinks on ?

will there be a followup to create and consume a container-definitons prerelease along with a breaking.md entry?

Yes. Once the logger property is removed in the next release, I'll update breaking.md along with it

will there be a followup to create and consume a container-definitons prerelease along with a breaking.md entry?

Yes. Once the logger property is removed in the next release, I'll update breaking.md along with it

Follow-up work item: https://github.com/microsoft/FluidFramework/issues/8902


Refactor Voice

Move away from internal Pipe based encoding, which involves heavy thread use and blocking to one that is more delegate based with DispatchSources and DispatchIO.
From @tellowkrinkle

Make two new protocols, DiscordOpusDataSource and DiscordPCMDataSource, which each require a nextAudio (or something, that name sounds kind of bad) method that throws or returns a opus/PCM encoded Data as well as an optional finishEncoding method.  These will be identical in requirement, separate only to make it obvious what type of data any given conforming class can give out.
Make DiscordOpusEncoder conform to DiscordOpusDataSource and give it an optional DiscordPCMDataSource input
Add a (non-iOS) DiscordPipedAudio class which conforms to both DataSources and manages audio from another process, has a convenience init that also includes an ffmpeg instance
Make DiscordVoiceEncoder conform to DiscordOpusDataSource, while trying to keep its user-facing features as similar as possible to the old DiscordVoiceEncoder (things like Read will have to go, but hopefully no one wanted to call Read from the client side)
Replace the encoder variable in DiscordVoiceEngine with a DiscordOpusDataSource, which will get its nextAudio method called every 20 milliseconds using a Dispatch Timer.
Replace callbacks like voiceEngineNeedsEncoder with voiceEngineNeedsDataSource (might as well keep the old one around to reduce change requirements)

@tellowkrinkle I like this idea.  It's a little more along the lines with what I had originally before I went to the current way when I was trying to get voice to work on Linux. (It actually might have been unrelated to Dispatch being crappy on linux and just misuse of vapor's WebSockets.)
My concerns:

Do you really need two source types if you're going to change DiscordVoiceEncoder to conform to DiscordOpusDataSource? With this approach (assuming the end-api for the current middleware stays mostly the same, and it still outputs raw PCM to for encoding --my preference--) the other way that this was being used is feeding straight PCM into the engine, bypassing the middleware. Would you be providing some default wrapper around PCM data, basically a middleware for PCM Data?
How do you plan on handling the UDP socket and all the blocking it does now? I would rather keep Vapor around (or find something that works everywhere that is just as easy,) than trying to manage a raw socket ourselves. I think using using something like DispatchSource and DispatchIO might be helpful.

I wouldn't worry too much about the Decoder, it's more of a toy. (Which is why I added a config to bypass it.)

Only thing left is to refactor reading from the UDP socket.


Autocomplete renderItem prop does not support arbitrary rendering

Consider this:
const fruits = [
  {id: "banana", label: "Banana, yum!"},
  // ...
];

// ...

<Autocomplete items={fruits}
  itemToString={item => (item ? item.label : '')}/>

Let's say we want to render a banana icon next to bananas by checking the id against an icon list. Autocomplete does support a renderItem prop, but it only receives baked props that look like this:
{
  "children": "Banana",
  "id": "downshift-0-item-0",
  "isHighlighted": false,
  "isSelected": false,
  "key": "Banana",
  "style": {"position": "absolute", "top": 0, "left": 0, "width": "100%", "height": 32}
}

There's no item here — all you get is the string returned by the itemToString function.  From what I can tell, there's no way to provide a custom rendering here that has access to the item. It's actually extremely limited what you can do with renderItem if you want to do this cleanly.
It's worth pointing out that the props sent to renderItem are in fact undocumented, and it's unclear that it's expected to use an AutocompleteItem; the interface is low-level and somewhat tighly coupled.
I think there's an opportunity here to distinguish between rendering the container around the item (which will have things like position, highlight/select and so on) and the contents. Consider a hypothetical renderItemContents prop:
<Autocomplete items={fruits}
  itemToString={item => (item ? item.label : '')}
  renderItemContents={item => (

      <FruitIcon fruit={item}/> {item.label}

  )}
/>

This renderer doesn't need to know about anything (selection, position, etc.), just how to render the actual item.

@atombender thanks for creating the issue! This seems like an interesting proposal. There are a ton of things about Autocomplete and SelectMenu that I would love to improve and change, but haven't had the found the time for it yet. Feel free to take a stab at it if you want.

Closing as the issue is quite stale.


Error: ContentDecodingFailed

SusAlert no longer works for me as of today and I'm unable to figure out why. Worked fine yesterday, but today this is all the window shows me:

Hey, this might be an issue with the hosting of the plugin, as I had some reports about that this week. But the plugin seems to be working just fine right now.
If the issue persists for you I would appreciate it if you could check if any errors show up in the dev console, to do this right click anywhere inside the plugin window & click inspect, then go to the console tab.

Hey, this might be an issue with the hosting of the plugin, as I had some reports about that this week. But the plugin seems to be working just fine right now.
If the issue persists for you I would appreciate it if you could check if any errors show up in the dev console, to do this right click anywhere inside the plugin window & click inspect, then go to the console tab.

Still getting errors and I got this in the dev console:

Huh, thanks for providing this. This is quite an obscure error having something to do with the underlying browser that alt1 uses (chromium/chrome). Does this happen with any other alt1 plugins?
You could try to remove the plugin from alt1 and add it again, or reinstalling alt1 all together to see if that fixes things.

Reinstalling alt1 entirely seems to have fixed the issue. No other apps on alt1 had this problem in the meantime. Thanks for the help!

Glad to see that the issue was resolved!


Adds a bool Sign to the TransactionBuildContext

At the moment, signing of a transaction is done if a password is passed to the TransactionBuildContext.
This should be explicitly stated as sometimes, the password is not passed as it is cached, resulting in the transaction not getting signed.
Related to https://github.com/stratisproject/StratisBitcoinFullNode/pull/2382

Fixed in #2525


Feature bhushan1

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

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

Files with missing lines
Coverage Δ

hw2_debugging.py
100.00% <ø> (ø)


Can not produce flux  dust

I have played ATM9 to the sky. And I can't   produce  flux. I use prism client.
To Reproduce
I  follow  the  step to produce  flux dust by place bottom with obsidian air at middle and  top  with obsidian but also I cannot left click at the obsidian on the top.
I  just need to solve it.

Try to do this, but instead of doing it on top of an obsidian block, do it on top of the bedrock block.


Unable to make this work

Make sure to check the demo app(s) for sample usage
I've tried the demo-ng. I wasn't able to get it work.
Cloned this repo, did yarn, did npm run build.all (no error), then npm run demo.ng.android, got 22 compilation errors, such as:
ERROR in ../demo-snippets/ng/tabs/tabs.component.ts:8:14 - error NG6007: The Component 'TabsComponent' is declared by more than one NgModule.
or even
SassError: Undefined variable.   ╷ 2 │     font-family: $mdi-fontFamily;
Is it just not working, is it outdated, or am I doing something wrong? Maybe the README should be updated. I'd expect the demos to just work.
If the demo apps cannot help and there is no issue for your problem, tell us about it
So i wanted to use a component in my own app.
The app is a nx workspace generated via nativescript-nx plugin.
Installed using tns plugin add @nativescript-community/ui-material-textfield
Imported the module and used in html.
After start, I got TypeError: Cannot read property 'material' of undefined.
 System.err: An uncaught Exception occurred on "main" thread.
  System.err: Unable to resume activity {org.nativescript.amelieao3/com.tns.NativeScriptActivity}: com.tns.NativeScriptException: Calling js method onCreateView failed
  System.err: TypeError: Cannot read property 'material' of undefined
  System.err:
  System.err: StackTrace:
  System.err: java.lang.RuntimeException: Unable to resume activity {org.nativescript.amelieao3/com.tns.NativeScriptActivity}: com.tns.NativeScriptException: Calling js method onCreateView failed
  System.err: TypeError: Cannot read property 'material' of undefined
  System.err:   at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4898)
  System.err:   at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4931)
  System.err:   at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:54)
  System.err:   at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
  System.err:   at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
  System.err:   at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
  System.err:   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2311)
  System.err:   at android.os.Handler.dispatchMessage(Handler.java:111)
  System.err:   at android.os.Looper.loopOnce(Looper.java:238)
  System.err:   at android.os.Looper.loop(Looper.java:357)
  System.err:   at android.app.ActivityThread.main(ActivityThread.java:8098)
  System.err:   at java.lang.reflect.Method.invoke(Native Method)
  System.err:   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
  System.err:   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1026)
  System.err: Caused by: com.tns.NativeScriptException: Calling js method onCreateView failed
  System.err: TypeError: Cannot read property 'material' of undefined
  System.err:   at com.tns.Runtime.callJSMethodNative(Native Method)
  System.err:   at com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1302)
  System.err:   at com.tns.Runtime.callJSMethodImpl(Runtime.java:1188)
  System.err:   at com.tns.Runtime.callJSMethod(Runtime.java:1175)
  System.err:   at com.tns.Runtime.callJSMethod(Runtime.java:1153)
  System.err:   at com.tns.Runtime.callJSMethod(Runtime.java:1149)
  System.err:   at com.tns.FragmentClass.onCreateView(FragmentClass.java:55)
  System.err:   at androidx.fragment.app.Fragment.performCreateView(Fragment.java:3104)
  System.err:   at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:524)
  System.err:   at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:261)
  System.err:   at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1899)
  System.err:   at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1817)
  System.err:   at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1760)
  System.err:   at androidx.fragment.app.FragmentController.execPendingActions(FragmentController.java:495)
  System.err:   at androidx.fragment.app.FragmentActivity.onResume(FragmentActivity.java:312)
  System.err:   at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1478)
  System.err:   at android.app.Activity.performResume(Activity.java:8386)
  System.err:   at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4888)
  System.err:   ... 13 more

Again - did I misconfigure something? If so, should be mentioned in the README.
Which platform(s) does your issue occur on?
Tried on Android.
Please, provide the following version numbers that your issue occurs with:

CLI: 8.4.0
Cross-platform modules: 8.4.7
Runtime(s): ???
Plugin(s):

"devDependencies": {
		"@angular-devkit/build-angular": "^15.0.0",
		"@angular/cli": "^15.1.6",
		"@angular/compiler-cli": "^15.0.0",
		"@nativescript/nx": "^4.2.0",
		"@nativescript/types": "~8.4.0",
		"@nativescript/webpack": "~5.0.0",
		"@ngtools/webpack": "^15.0.0",
		"@nrwl/eslint-plugin-nx": "15.8.5",
		"@nrwl/jest": "15.8.5",
		"@nrwl/linter": "15.8.5",
		"@nrwl/nx-cloud": "15.2.1",
		"@nrwl/workspace": "15.8.5",
		"@types/jest": "29.4.0",
		"@types/node": "16.11.7",
		"@typescript-eslint/eslint-plugin": "^5.52.0",
		"@typescript-eslint/parser": "^5.52.0",
		"core-js": "^3.29.0",
		"eslint": "~8.15.0",
		"eslint-config-prettier": "^8.1.0",
		"jest": "29.4.3",
		"jest-environment-jsdom": "29.4.3",
		"jest-preset-angular": "^13.0.0",
		"nx": "15.8.5",
		"prettier": "^2.6.2",
		"sass": "^1.32.0",
		"ts-jest": "29.0.5",
		"ts-node": "10.9.1",
		"typescript": "4.9.5"
	},
	"dependencies": {
		"@angular/animations": "^15.0.0",
		"@angular/common": "^15.0.0",
		"@angular/compiler": "^15.0.0",
		"@angular/core": "^15.0.0",
		"@angular/forms": "^15.0.0",
		"@angular/platform-browser": "^15.0.0",
		"@angular/platform-browser-dynamic": "^15.0.0",
		"@angular/router": "^15.0.0",
		"@nativescript-community/ui-material-textview": "^7.0.42",
		"@nativescript/angular": "^15.0.0",
		"@nativescript/core": "~8.4.0",
		"@nativescript/theme": "^3.0.2",
		"cheerio": "^1.0.0-rc.12",
		"rxjs": "~7.6.0",
		"tslib": "^2.3.0",
		"zone.js": "^0.12.0"
	},

Is there any code involved?
git clone https://github.com/ziacik/amelie-ao3.git
cd amelie-ao3 && git checkout ui-material
npm i
npx nx android

@ziacik sorry about the demo app. Tbh I haven't touched the angular demo for a while.
Now about your error in your app it seems to say it can't find the native android lib.
I dont use nx so I can't tell. Can you try with in a template angular app? Again I am sorry I dont use angular but I know for certain other people are using it with angular.

@farfromrefug Thanks for the quick response. I tried this with nativescript original angular template, and it seems to work (altough at first I had an error saying I must set Material theme to styles.xml, so I did). So I guess I must figure out the differences with nx template. Thanks, closing.

@ziacik ok let me know if i can help. You can also find me in the discord of N

@farfromrefug Thanks. Can't use discord because the group seems to require a phone verification which I don't want.
Anyway, I figured this out, so if anyone got into this, here's the solution:
When using nx with the NS plugin, there are two package.json-s generated, one in the root and another in the nativescript-*** app.  In the second one, the reference to material ui component needs to be added too under dependencies, with * as version (the same way as @nativescript/core). Then the platform stuff is generated correctly at build and everything works.

Why the nativescript docs are so crappy ?
Can someone update proper requirements here: https://github.com/nativescript-community/ui-material-components/tree/master/packages/bottom-navigation ?


Make the visualizer open source

Hello
The visualizer is a great tool but since it's hosted on the cloud lots of companies would not really be able to use it for development because of infosec policies. Could you release the code in order to allow developers to run it locally safely?
Thanks

We do not have plans to open source visualizer. We are constantly improving the feature set of the visualizer.  The visualizer should not be blocked from access by infosec policies.

Then, as a customer how can I be sure that my algorithm design is not made visible to people inside Google?

@mgyong I wish I could use MediaPipe in a web application as your visualizer, but appart from the "MediaPipe on the Web" article I have not so much clues about how I could achieve this.
Do you please know how I could get some help to achieve my own web integration of MediaPipe?

@mgyong I guess the #459 thread is actually answering my question

@mgyong Could the following article be mentioned on in the github README of mediapipe and eventually in the documentation?
https://blog.tensorflow.org/2020/03/face-and-hand-tracking-in-browser-with-mediapipe-and-tensorflowjs.html

@szandara Since the pipeline is described in a .pbtxt file, you can use Netron to visualize it.

@brucechou1983 Thanks a lot, it's a very good tip!

+1

I wonder in what ways is the visualizer a great tool for people who have commented. It visualizes a graph, that it does. But I have never found that useful beyond an initial aesthetic kind of pleasure  detached from purpose.
The graph of execution cannot be traversed in any way near how a regular static graph of execution of a regular programming language code project can. For example, to navigate to a subgraph one has to expand the node name to a lower cased underscore delimited pbtxt file name and locate that file in the directory hierarchy, to load that file as well. There is no drill down or drill up / show usages flow.
Clicking on a subgraph will seemingly not navigate to the corresponding tab which holds the subgraph’s definition, even after that tab has been opened following old-school method which I just described.
Even simple things like getting the top-most entry node to the graph is not a feature.
I guess it's more of a nice visualizer for very simple graphs serving as a documentation companion. It would be really nice to give it more disciplined "product" work to really make it useful. Maybe open sourcing might help as an alternative path of leverage to make it useful in a much more leveraged/real sense.


multiple instances problem

Hi,
I have a link that open a div with featherlight, I use "persist shared" because there is a form in the box that I validate in jquery (without "persist", it won't work because of duplicate fields).
That works perfectly !
But I also have this exact same link elsewhere on my page : If I click on one link, close the box and open it again with another link, the box is empty !
Any idea ?
Thanks !

I've found the problem (which was in fact the same as here : https://github.com/noelboss/featherlight/issues/149 ).
I used this on my links to open the box :
link 1 link 2
But that didn't work, when I clicked on link 1 then link 2, it would open an empty box.
So I did this :
link 1 link 2
and in JS :
$('.link').featherlight($('#box'), {persist: 'shared'});
And this is working !
It could be nicer to be able to use the first method but it works so it's fine !

This still isn't working. If you click link 1, then link 2, link 1 no longer works properly.
https://jsfiddle.net/asc4d5f1/

Use this instead and it should work :
$('#link-1, #link-2').featherlight($('#box-1'), {persist: 'shared'});


Send to Unreal: Policy violation with top level module

Hi guys, I've installed the new version of the addon in Blender 4.2 and I recieve this error in the addon tab:

Of course, the Send to Unreal tab doesn't appear in the N panel, although the Pipeline menu does exist.
I'm I missing something on the install?
Same happens with 2.4.6.

Those are warnings we need to clean up for Extensions support. The plugin should be working, there is no N panel for Send2UE

There's no N panel... true...
Well, thanks anyway!!! You're doing awesome work guys, keep the torch lit!


perf: remove extra allocations

Pull Request Test Coverage Report for Build 114
Details

15 of 18 (83.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 74.607%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cmark/inline_struct.mbt
12
15
80.0%

Totals

Change from base Build 113:
0.03%

Covered Lines:
1425

Relevant Lines:
1910

💛  - Coveralls


registerApp cannot rerun event listen

If registerApp is returned in useEffect, it will not rerun when enter to the same screen
useEffect(() => {
    const removeListener = registerApp({
      appid: Config.WECHAT_APP_ID,
      universalLink: Config.WECHAT_RETURN_URL,
    });
    return removeListener;
}, []);

PR created

https://github.com/Hector-Chong/native-wechat/pull/45


Add language to url

Hi,
I created a new plugin on wordpress 5.0 with MVC plugin.
My plugin is working properly in http://localhost/xxxx/pluginName/
On my controller I have this:
     $myLocale = get_locale();
        if(strcmp($myLocale,'en')===0){
                $myLocale = 'en_US';
        }else if(strcmp($myLocale,'es')===0){
                $myLocale = 'es_ES';
        }else{
                $myLocale = 'it_IT';
        }

.....

$this->render_view('testFolder/viewTest');

I would like to know how to do working url with languages.
Example:
http://localhost/xxxx/es/pluginName/
http://localhost/xxxx/en/pluginName/
http://localhost/xxxx/it/pluginName/
Regards,

You can accomplish this in the plugin by passing a ?lang= (or similar) parameter on the URL, or what I do is set up a multisite instance with sub-sites corresponding to the languages, and activate the plugin globally on the multisite instance. That way everything within e.g. .../it/ is in Italian, including all site-wide string translations. Good luck!


Create ConectorCiencia.md

!!DELETE THIS TEMPLATE AFTER READING
Before submitting an Issue

Merge conflicts: conflicts are more common when working locally.
Organize new PRs: Members should organize pull requests and apply labels

In your Pull Request

describe proposed changes in bullet points if appropriate
link to an issues it may be addressing fixing something? include the # of the issue

Please, could someone help me to fix this?

@FilipeBrasil.. you should see the page shortly


[DRAFT] project refactor

draft refactor in progress
will update description when ready to merge

bekind has been refactored which mean this PR must be redone.


Prune/optimize columns block for careers

See #46 for block deails.
This issue is to review block and remove what is not needed or of value for Careers

reviewed and updated for long-card


Section on "Enable Continue status" should either be expanded or removed

The current section is a tease because it mentions a feature but provides no implementation details or guidance. Also, the expect header is only related to sending data to the server, not receiving it.
If you keep this section I would suggest mentioning the following

.net clients have this setting enabled by default
It will cause 2 round trips for every POST/PUT request.
Response to the 100 expect is handled transparently by http.sys, so it needs to be explained how to configure the allowed size for a particular host and clarified that it will apply to every request.

This material will be updated as suggested

@JohnPWSharp can update the status of this?

This issue has been addressed. The published version already includes the changes.

This is complete, but I don’t have the rights to update the status.
From: Christopher Bennage<EMAIL_ADDRESS>Sent: 26 May 2015 22:33
To: mspnp/azure-guidance
Cc: John Sharp
Subject: Re: [azure-guidance] Section on "Enable Continue status" should either be expanded or removed (#11)
@JohnPWSharphttps://github.com/JohnPWSharp can update the status of this?
—
Reply to this email directly or view it on GitHubhttps://github.com/mspnp/azure-guidance/issues/11#issuecomment-105670881.
The information in this email is private and confidential. Any disclosure, copying, distribution or any action taken, or omitted to be taken, in reliance on it, is not permitted and may be unlawful. If you are not the intended recipient please destroy it immediately, contacting us so we can correct our records. CM Group does not accept liability for any statements made which are the senders own and not expressly made on behalf of CM Group. We cannot accept any liability for any loss or damage sustained as a result of software viruses. It is your responsibility to carry out such virus checking as is necessary before opening any email or attachment. CM Group Ltd. Tortworth House, Tortworth, Wotton-Under-Edge, South Gloucestershire, GL12 8HQ, UK. Tel +44 (0)1454 269222. Fax +44 (0)1454 269333. www.cm-group.co.uk


[Doc] Remove first and last newline in code block

Search before asking

[X] I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?
Every code block in pulsar document has redundant newlines:

If I click the copy button, \n was copied as well, which is inconvenient to change args and may run commands unexpectedly because of the tailing \n:

What is your suggestion?
Trim all redundant newlines of code blocks like this:

Any reference?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Make sense. I'm doing this when touching related documents. I don't make a patch to apply it globally yet, though. If you have some time to do it and we get two or more committers' approval, we can try to take the move. Otherwise, it's quite easily to conflict with continuous contributions.

cc @Anonymitaet @momo-jun @Huanli-Meng

I'm working on this. https://github.com/apache/pulsar/pull/17355

I've already been working on this: #17355.

Seems great, thanks.  I'll close this issue.


[Bug]:  Unexpected sequence & found at index 0

Minimal, reproducible example
import puppeteer from "puppeteer";

(async () => {
    const browser = await puppeteer.launch();
    const page = await browser.newPage();

    await page.setContent(`

Title 1

                            1
                            2

Random text 1

Title 2

                            1
                            2

Random text 2

    `);

    const $div = await page.waitForSelector("div");
    const $tables = await $div!.$$("& > table");

    await browser.close();
})();

Error string
Unexpected sequence & found at index 0
Bug behavior

[ ] Flaky
[ ] PDF

Background
I would like to select all tables inside the div, but only the child elements. Some tables may contain another table, but I need only the children, and there may be another child elements like h1 or p next to the tables
This worked with 22.8.0, but fails with the error in title with 22.11.0. I upgraded from 22.8.0 to 22.11.0 directly.
Expectation
I expected... to get the elements by selector like before.
Reality
In reality, ... I get an error message.
Puppeteer configuration file (if used)
No response
Puppeteer version
22.11.0
Node version
21.7.2
Package manager
npm
Package manager version
10.5.0
Operating system
Linux

Thanks! it is a bug with nested selector parsing.

await $div!.$$(":scope > table") should yield same results as a workaround.

Thank you! If it will be fixed, then I will wait for it. Much easier than changing everywhere the code.

BTW, which one is the better to use? & > table or :scope > table?
I ask because I see the fix, and as I understand that is a fallback solution.

The :scope is an older feature from the Selector 4 spec https://drafts.csswg.org/selectors/#the-scope-pseudo and CSS nesting is a newer one from the css nesting module spec https://www.w3.org/TR/css-nesting-1/ I think you can use & > table since all modern browsers support it already. In Puppeteer, we use a selector parser to provide additional features and it does not support & > table  out of the box yet but that it was broken for you is a bug, we should fallback to CSS if the parser is not able to parse a selector.


Example doesn't work

Hello.  I am new to using Azure Cloud Shell (normally use PowerShell locally).  I am running into issues trying to get the example to work.  First, the language about what to do seems incorrect.  It says "If you choose to install and use the PowerShell locally instead of from the Azure Cloud shell, this tutorial requires the Azure PowerShell module. Run Get-Module -ListAvailable Az to find the version. If you need to upgrade, see Install Azure PowerShell module. If you're running PowerShell locally, you also need to run Connect-AzAccount to create a connection with Azure."
However, in Azure Cloud Shell I had to log in using Connect-AzAccount.  Not really a problem but it should be pointed out.
With the authentication issue out of the way, the PS code also fails.  It sounds like there's something wrong with the template:
PS Azure:> $resourceGroupName = Read-Host -Prompt "Enter the Resource Group name"
Enter the Resource Group name: LabTest20-RG
Azure:/
PS Azure:> $location = Read-Host -Prompt "Enter the location (i.e. centralus)"
Enter the location (i.e. centralus): westus
Azure:/
PS Azure:> $adminUsername = Read-Host -Prompt "Enter the administrator username"
Enter the administrator username: CORP\LabTest2-Admin
Azure:/
PS Azure:> $adminPassword = Read-Host -Prompt "Enter the administrator password" -AsSecureString
Enter the administrator password: ************
Azure:/
PS Azure:> $dnsLabelPrefix = Read-Host -Prompt "Enter an unique DNS name for the public IP"
Enter an unique DNS name for the public IP: TEST20.corp.contoso.com
Azure:/
PS Azure:>
Azure:/
PS Azure:> New-AzResourceGroup -Name $resourceGroupName -Location "$location"
ResourceGroupName : LabTest20-RG
Location          : westus
ProvisioningState : Succeeded
Tags              :
ResourceId        : /subscriptions/ae1e8d96-081a-4f6d-9438-3807c445eb4c/resourceGroups/LabTest20-RG
Azure:/
PS Azure:> New-AzResourceGroupDeployment >>     -ResourceGroupName $resourceGroupName
>>     -TemplateUri "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-vm-simple-windows/azuredeploy.json" >>     -adminUsername $adminUsername
>>     -adminPassword $adminPassword `
>>     -dnsLabelPrefix $dnsLabelPrefix
New-AzResourceGroupDeployment : 6:08:25 PM - Error: Code=InvalidTemplateDeployment; Message=The template deployment 'azuredeploy' is not valid according to the validation procedure. The tracking id is 'bd3e6f1c-4232-450e-bd04-fedbc68e5ff3'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.
At line:1 char:1

New-AzResourceGroupDeployment `

CategoryInfo          : NotSpecified: (:) [New-AzResourceGroupDeployment], Exception
FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

New-AzResourceGroupDeployment : 6:08:25 PM - Error: Code=InvalidDomainNameLabel; Message=The domain name label TEST20.corp.contoso.com is invalid. It must conform to the following regular expression: ^[a-z][a-z0-9-]{1,61}[a-z0-9]$.
At line:1 char:1

New-AzResourceGroupDeployment `

CategoryInfo          : NotSpecified: (:) [New-AzResourceGroupDeployment], Exception
FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

New-AzResourceGroupDeployment : The deployment validation failed
At line:1 char:1

New-AzResourceGroupDeployment `

CategoryInfo          : CloseError: (:) [New-AzResourceGroupDeployment], InvalidOperationException
FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

Azure:/
PS Azure:>
Azure:/
PS Azure:>  (Get-AzVm -ResourceGroupName $resourceGroupName).name
I have tried this from Azure Cloud Shell and PowerShell locally and get the same errors.  Can someone please look into this?  Thank you!

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

ID: b3a1f07d-4e24-e4e6-d64a-90560d90b321
Version Independent ID: 7cedcb52-393e-5298-6a78-fabf89be864d
Content: Create a Windows VM from a template in Azure
Content Source: articles/virtual-machines/windows/ps-template.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! We are currently investigating and will update you shortly.

@RichardKForester I tried the example both in Cloud Shell and Local and it ran as expected
PS Azure:\> $resourceGroupName = Read-Host -Prompt "Enter the Resource Group name"
Enter the Resource Group name: templatetest

PS Azure:\> $location = Read-Host -Prompt "Enter the location (i.e. centralus)"
Enter the location (i.e. centralus): eastus

PS Azure:\> $adminUsername = Read-Host -Prompt "Enter the administrator username"
Enter the administrator username: azureuser

PS Azure:\> $adminPassword = Read-Host -Prompt "Enter the administrator password" -AsSecureString
Enter the administrator password: ******************

PS Azure:\> $dnsLabelPrefix = Read-Host -Prompt "Enter an unique DNS name for the public IP"
Enter an unique DNS name for the public IP: micahtemplatetest

Location          : eastus
ProvisioningState : Succeeded
Tags              :
ResourceId        : /subscriptions/XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/resourceGroups/templatetest

PS Azure:\> New-AzResourceGroupDeployment `
>>     -ResourceGroupName $resourceGroupName `
>>     -TemplateUri "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-vm-simple-windows/azuredeploy.json" `
>>     -adminUsername $adminUsername `
>>     -adminPassword $adminPassword `
>>     -dnsLabelPrefix $dnsLabelPrefix

DeploymentName          : azuredeploy
ResourceGroupName       : templatetest
ProvisioningState       : Succeeded
Timestamp               : 5/14/19 7:46:44 PM
Mode                    : Incremental
TemplateLink            :
                          Uri            : https://raw.githubusercontent.com/Azure/azure-quickstart-templates/maste
                          r/101-vm-simple-windows/azuredeploy.json
                          ContentVersion : <IP_ADDRESS>

Parameters              :
                          Name                Type                       Value
                          ==================  =========================  ==========
                          adminUsername       String                     azureuser
                          adminPassword       SecureString
                          dnsLabelPrefix      String                     micahtemplatetest
                          windowsOSVersion    String                     2016-Datacenter
                          location            String                     eastus

Outputs                 :
                          Name             Type                       Value
                          ===============  =========================  ==========
                          hostname         String                     micahtemplatetest.eastus.cloudapp.azure.com

Azure:/

Looks like the DNS name you picked is just invalid. Make sure to just put the name and nothing else. So for example, I picked micahtemplatetest as a dns name.

Hi Micah.  You are right.  I tried using a different DNS name and it worked.  I presumed it needed an FQDN.  Also when I loaded the JSON in Visual Studio Code it showed validation errors so I thought there was something wrong.  Thanks for your help!

@RichardKForester no problem :) Glad to hear you got it working!


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade" workflow

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-XK8ItpxnSow5
Commit ID: 5175c7678e32f33d1942920997850f72da69df9a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Quotation marks inside of attributes

If I have a template command that uses quotation marks inside of an HTML attribute, like
, I like for the outer quotation marks to be a single quote ' so that my text editor (which doesn't know about Go templates) highlights the block semi-correctly, but the plugin changes it to be a double quote ".

This is a default prettier behavior, and not specific to this plugin.
Take a look at this playground example:
https://prettier.io/playground/#N4Igxg9gdgLgprEAuEAeAFjAtgGwAQAmAhjEQLTwDOMAvAORUx0B8qA9JrsyADQgQAHGAEtolZKCIAnKRADuABWkJxKIjjlEAnuL4AjKUTABrODADKRLHAAywqHGQAzdZTj7DJs+YFH7Ac2QYKQBXdxA4LD04AgIYmyIofxCifzgAMQgpLBIRJOQQIhCYCF4QThwAdXRhKl8wOHMVWuEAN1qtArBKXRB7NykYBUN-HOdXcIArSgAPcwCcOABFEIh4cZw3Pl8pAYKKsoEpexhK4QIYdGQADgAGbdk3SsMBAqO4AdbHPgBHVfhhoJVIVKGQHDEYmUpHA-sJocNUmMkC5NuE3FhhEFQmiFst-o5kRM+KQ9GcLlckAAmYmGYQ4AIAYQgWCREUoAFYyiE3AAVIh6VQorYgVphACSUDisHMYGOQgAgpLzDAtIsNm4AL4aoA
This plugin just wraps around the default HTML formatter of prettier. Therefore, this issue won't ever be resolved.

Okay, my workaround has been to use backticks like
<a href="{{ thing `whatever` }}">hi

That highlights better than using double quotes.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62529

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/80294

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/84882

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98228

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98255


[backport] Improve installation guide of ChainerMN

Backport of #5656

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 832ad17beb5b8ef1c2f246becaec5d126489bbf9, target branch v5) succeeded!


org.xml.sax.SAXParseException - Content is not allowed in prolog with valid wsdl + xsd files

Hello,
I'm trying to validate my soap messages using the serviceProxy or soapProxy with a wsdl file + several xsd files. The WSDL und XSD files are valid and are used in our IBM Datapower Instances to validate SOAP-Messages. The same files can also be used in SoapUI for testing.
In Membrane, an org.xml.sax.SAXParseException - Content is not allowed in prolog error with one of the XSD is produced during Start-Up.
Membrane version: 5.5.4
SOAP-Specification:
vostra2-strafregister-v1-soap-specification-1.2.0.zip
Proxies.xml
proxies.xml.txt
LOG:
membrane-soap-error-log.txt
Thank you!

Hi @paulhyo,
thanks for reporting the issue. The file eCH-0051-common-2-10-0.xsd starts with a byte order mark. The BOM consists of the byte sequence EF BB BF that is sometimes inserted to indicate the encoding of a text file. The image shows the byte sequence of the file.

If you remove the BOM from the file it will work. Just open it in VSC and change the encoding at the bottom from "UTF-8 with BOM" to "UTF-8" and save. It is the only file in your zip archive with BOM.
Unfortunately the XML parser library can not deal with the BOM. We will strip the BOM before parsing in a future Membrane version.

@predic8 Membrane's GraphQL parser uses org.apache.commons.io.input.BOMInputStream for that purpose.

Thanks. I am writing a test right now. Maybe we can use the class also for XSDs and WSDLs.

@paulhyo thanks for reporting again.
#1341 fixes the issue.


Nice work!

Sorry for messaging this way, I couldn't find away to send you a message. I saw your post on another thread about welcoming collaboration and that sounds great!. my email is<EMAIL_ADDRESS>for further discussions. Thanks again.

Measured in CAD program. :)


Update server-metrics to 0.5.0

Change GC metrics https://github.com/metamx/server-metrics/releases/tag/server-metrics-0.3.0
Require java 8 (druid already does)
Add cpuacct cgroup monitor https://github.com/metamx/server-metrics/releases/tag/server-metrics-0.5.0
Update various dependencies https://github.com/metamx/server-metrics/pull/27

@drcrallen I think  #4480 should be updated instead of creating a new PR


TypeError: (0 , _test.defineConfig) is not a function

I used the playwright.service.config.ts file as mentioned in the article and my playwright version is 1.38.1.
The line import dotenv from 'dotenv'; was throwing errors so i used below line as alternative:
import { config } from 'dotenv';
config();
I also created a .env file named as playwrightTestingService.env and put the two variables in it (PLAYWRIGHT_SERVICE_ACCESS_TOKEN and PLAYWRIGHT_SERVICE_URL).
when i run the command npx playwright test --config=playwright.service.config.ts --workers=20 , I am getting TypeError: (0 , _test.defineConfig) is not a function
AB#1898417

Hi @maharrshi,
I wasn't able to reproduce this issue when using playwright version 1.38.1. Could you help with the following details

Modified playwright.service.config.ts file being used
Operating System
Node version

Regarding the dotenv issue, could you provide the error that was being thrown earlier?
Lastly, by default dotenv npm library searches for the file .env only. If you need to use another name for the env file, you'd need to set the path explicitly. ( Reference - https://github.com/motdotla/dotenv#path )
config({ path: 'playwrightTestingService.env' });

Hi @maharrshi, let me know if you had the chance to capture the above information for us to reproduce the issue.

Closing this issue for now, feel free to reopen if the issue persists.


avoid file format sniffing, for speed-up

we might want to explicitly read as format="newick" to save run-time: see https://github.com/biocore/scikit-bio/issues/1825

👍

@sjanssen2 @wasade @ebolyen is this PR good to merge for the coming release?

I'd say yes, but might be biased since it is my PR ;-)
I'd prefer a more general solution in skbio, though.


Style warnings in loop

When doing a fresh compile, 7 style warnings are generated:
 caught STYLE-WARNING:
;   The binding of SB-C::Y is not a REAL:
;    NIL
;   See also:
;     The SBCL Manual, Node "Handling of Types"

They don't affect the test results, but it would be nice to eliminate them.

Fixed in the unmerged commit for testing (#4).  The cause was the assumption that the array-dimension function would return exactly two values.  It could return 1, or it could return a list of any length and the compiler can't determine this.


Add total dead character fame to account info

Account.Stats.TotalFame
Thanks @Xythium for pointing this one out

Published in v9.3.0.


pm: device runtime: Fix enable() inconsistences

Leave the device in a consitent state
Zeroed usage count when enabling runtime pm

Personally I think its fine to have one squashed commit here. It'd be a bonus for adding a test case to ensure you can enable/disable and get the expected outcome.


Text field titles in 'Contact and Registration' forms are untranslated in Suomi view

Steps

Visit https://staging.apinf.io (version 0.39.0)
Change language by clicking on 'Suomi'
Go to 'Getting started' and click on  'Register' ('Rekisteroidy')
Scroll down and go to 'Contact Us'

Expected Result
All the text field titles in Contact and Registration forms must be in Suomi language
Actual Result
Text filed titles are untranslated in Suomi view
Screenshot

@baijat Verified it on nightly, it is reproduced

@bajiat The form has the translation. But it doesn't work as expected, an fixing it.

@bajiat , verified this resolved issue in https://staging.apinf.io version 0.40.0
Findings:

Text field titles in 'Contact Us' form are as expected in Suomi view  (screenshot 1)
Registration form is untranslated in Suomi view (eg. Page title , text field titles) (screenshot 2)

Screenshot 1:

Screenshot 2:


stats: fix stats name for prometheus

This commit replaces the illegal characters in stats name for matching the
regex required by prometheus, which is [a-zA-Z_:][a-zA-Z0-9_:]*.
Fixes #4568
The changes can be covered by the existing unit test PrometheusStatsFormatterTest.

Also, see my comment on the related issue. I think that there was a failure much earlier in tag extraction. The prometheus metric name shouldn't contain your cluster name at all; it is supposed to be a label on the metric, and labels are allowed to contain any character I believe (because they're quoted strings).

Yes. It seems there has a problem in extracting the value for label envoy_cluster_name. I will try to find out.

@ggreenway Updated PR per comments.
@alyssawilk Added unit tests as requested.
Please have a look.
The ci check_format failure looks irrelevant. It's about the order of header file "#include "server/http/admin.h"".

I'm not sure what's up with the mac failure.  Looks unrelated but it has failed 4 times thusfar...  Could you try a master merge and see if that fixes it?

From my investigation, merging master will fix this. I think it's fine to just merge this PR.


configurePlugins command for tsserver

Implements #18604

Add a new tsserver command, configurePlugins.
Add a new optional method to PluginModule, onConfigurationChanged. Plugin authors can implement this.
When configurePlugins is invoked, it will pass on the configuration object to any loaded plugin instances with a  matching name.
This configuration is meant to override the initial configuration passed in in create/PluginCreateInfo as well as any previous configurations passed in in configurePlugins.
The updated configuration will also be remembered by tsserver so that it can be passed in, in the create call, to any projects loaded in the future with the matching plugin. This is needed for consistency -- the caller of configurePlugins would have no way of knowing whether the plugin/project of interest has yet been loaded.

cc @mjbvz

@mjbvz Thanks! Just opened corresponding PR https://github.com/Microsoft/vscode/pull/61756 , let me know if that works.

Changes look good but we need test.

@sheetalkamat test added!


Pass GITHUB_TOKEN to install_kustomize.sh to avoid rate-limit

We are hitting rate-limt during post merge image build:
Github rate-limiter failed the request. Either authenticate or wait a couple of minutes.
It seems it is coming from [1] and can be fixed by passing the GITHUB_TOKEN there. So this patch does that to avoid build failures due to rate-limit.
[1] https://github.com/kubernetes-sigs/kustomize/blob/0fd385d7197026b92272dc8688ec66593be91fba/hack/install_kustomize.sh#L145

/test images

/test openstack-operator-build-deploy


Import supabase project

Auto Importing

[x] Ask for access token
[x] Chose an organization
[x] Create new or use existing project

Create new project

[x] Set name
[x] Set Database Password
[x] Set region

Use existing project

[x] Select from a list of projects

Manual Importing

[x] Enter Project URL
[x] Enter Project anon key

92faa0fca45896571e694ea215fa9b2089d4ebb5 closes this issue


Add support for slicing with subviews

Please don't merge this PR immediately. It needs some refinement, including updated documentation and more tests.
This is an implementation of #215, adding support for taking subviews while slicing. A few of the changes are:

The s! macro can take individual indices (to indicate subviews) in addition to ranges.
The s! macro returns an owned SliceInfo instance instead of just a reference, so the caller can easily pass it around between methods.
The various *slice*() methods now take a SliceInfo instance (or reference).
There's now a slice_into() method. Note that ideally we'd come up with a better name than slice_into because there's already an into_slice() method.
ArrayBase now has three additional methods *slice_axis*() that slice along a single axis.

The primary disadvantage of this change is that it's not easy to create a SliceInfo instance without the s! macro. If that's an important feature, it would be possible to do any (or all) of the following:

Add impl<'a> From<&'a [SliceOrIndex]> for SliceInfo<Vec<SliceOrIndex>, IxDyn>.
Add a macro to convert [SliceOrIndex; n] into SliceInfo<[SliceOrIndex; n], D>, where D is determined at compile time.
Add a function to convert [SliceOrIndex; n] into SliceInfo<[SliceOrIndex; n], D>, where the caller would have to specify D, and D would be checked at runtime.

Note that this PR is a breaking change.
Will you please let me know what you think?

I don't always have time during the week to give so much feedback, not if I want it to be well thought out.

I understand, no worries. :) Thanks for looking at it today!

I think it looks great.

Since you like the approach, I'll work on updating the documentation and adding more tests.

Minor note, we don't have to worry too much about Rust < 1.21. We have promised in our docs to jump to newer rust versions to advance the library, and Rust 1.21 brings the needs_drop function which will be a great help to us.

I successfully removed the T type parameter by using the approach you suggested (removing out_ndim and implementing impl<T: Borrow<[SliceOrIndex]>, D: Dimension> Borrow<SliceInfo<[SliceOrIndex], D>> for SliceInfo<T, D>).

Looks cool! The now we can make the final transition to &SliceInfo<D::SliceArg, DimOut>

@bluss I'm working on cleaning up this PR in preparation for merging. I have a few questions:

Should Si be renamed to something clearer, e.g. Slice?
Is the name slice_into() okay? It's quite similar to the name of the existing into_slice() method.
Are you interested in supporting usize ranges and indices? As a user, I think this would be very useful because most of my code works with usize values for lengths and indices, not isize. If so, how would you like to handle them? I see two options:

Cast usize to isize when creating the Si or SliceOrIndex object. The issue with this approach is that it doesn't work correctly if the value is > std::isize::MAX. (By the way, slicing in ndarray 0.10.12 is currently broken if the axis length is > std::isize::MAX, see below for an example.)let x = Array2::<u8>::zeros((std::isize::MAX as usize, 0));
x.slice(s![0..1, ..]);
println!("Succeeded!");
x.slice(s![-1.., ..]);
println!("Succeeded!");

let x = Array2::<u8>::zeros((std::isize::MAX as usize + 1, 0));
x.slice(s![0..1, ..]);
println!("Succeeded!");
x.slice(s![-1.., ..]);
// thread 'main' panicked at 'attempt to add with overflow'

The option I prefer is to have separate Si and SliceOrIndex types/variants for usize and isize. This will allow correct operation even when the axis length is > std::isize::MAX.

As first priority, try to incorporate Si into SliceOrIndex. Else it should have a longer name
slice_into seems like a problematic name, unsure
Yes it would be great to support usize as well. I'd be fine with having that in a separate PR. We don't have a range problem; axis length will never be greater than isize::MAX; Rust does not support objects larger than that IIUC.

What I've seen before is that it would need to implement all of isize, usize, and i32 -> SliceOrIndex conversions, if it should work with literals like 0 that are not typed (they fall back to i32).

I incorporated Si into SliceOrIndex.

One suggestion is to rename the existing into_slice method (as well as as_slice and as_slice_mut) to something more descriptive. Some possibilities are into_slice_standard, into_slice_std, or into_slice_std_order (to emphasize that the data must be in standard order); into_flat_slice (to emphasize that the data is flattened); or into_std_slice (to emphasize that the return value is the slice type from the standard library). These names would be sufficiently different from slice_into to avoid confusion.

axis length will never be greater than isize::MAX; Rust does not support objects larger than that IIUC

That's convenient! We can cast everything to isize, then. I can submit a separate PR once this one is done to add the conversions.

I think the current version of the implementation is pretty good, although I'm somewhat unsatisfied about the need to call .as_ref() (or some other method) when using .islice() with IxDyn arrays. What do you think about making only .islice() generic with a bound T: AsRef<D::SliceArg>? There's precedent for this in the standard library; see e.g. std::fs::File::open().

We can change islice like that later.
I think we've achieved a pretty good interface here. It may be hard for me to avoid tinkering with it after merging, I'd primarily see if there is a neater way to build the phantom dimension type.
For now, I'd put #[repr(C)] on the SliceInfo struct, should make the raw pointer cast we do even less problematic.

Naming of the slice methods. This may be too much of brainstorming, don't know if it works.

slice → slice_view
slice_mut → slice_view_mut
slice_into → slice
islice → slice_in_place

drawback: pretty breaking

We could also try slice_into → sliced, islice → slice_in_place  and the other renames, leaving plain slice and slice_mut as deprecated?

Regarding naming, I think I prefer your first suggestion:

slice → slice_view
slice_mut → slice_view_mut
slice_into → slice
islice → slice_in_place

For islice, if you choose slice_in_place, I would also rename map_inplace and mapv_inplace to map_in_place and mapv_in_place. Otherwise, you could use slice_inplace.
Another option is islice → slice_mut, although the transition would be even more confusing.
Another option is

slice → slice or slice_view
slice_mut → slice_mut or slice_view_mut
slice_into → slice_move
islice → slice_inplace

which makes it easy for users to update their code. The _move suffix isn't used anywhere in the standard library AFAICT, but it is the recommended suffix for the owned variant according to RFC 199 if the default is an immutable borrow.

Yet another option is

.slice() → .view().slice()
.slice_mut() → .view_mut().slice()
.slice_into() → .slice()
.islice() → .slice_inplace()

I think my favorite option so far is:

.slice() → .slice()
.slice_mut() → .slice_mut()
.slice_into() → .slice_move()
.islice() → .slice_inplace()

Let's go with that. One concern is that slice_move is the generic move one, including for taking an ArrayView and slicing it in a lifetime-preserving way. .sliced() seems good, but it's not distinct enough to be well understood I guess.

Can we keep into_subview?

Can we keep into_subview?

Sure; I just assumed that you'd want it to name it like .slice_move(). I'll change it back to .into_subview().

I also renamed .isubview() to .subview_inplace(). Is that okay?

@jturner314 Yeah I think that's a good call, subview_inplace seems good.

Should the third member of SliceOrIndex::Slice be called the "step size" or the "stride" in the documentation?

step size sounds good, it doesn't mix the concepts. It's a multiplicative stride I guess? If we have a row stride of 12 and slice with step size 2, the new stride is 24.

Thanks a lot for working on this cool feature. Please update PR  description and rebase & squash the commits so that we are ready to merge. I think it's ready, what do you think?

Oh that said, maybe I should look over if there are any non-breaking changes I can merge first.

I cleaned up the commit history and created a new ready-to-merge PR #377. I edited the history to try and make it as easy as possible to read (primarily by minimizing the size of the commit that adds SliceOrIndex, SliceInfo, etc.). I did make a few minor additional changes, the biggest one being moving do_slice and abs_index from dimension_trait.rs to dimension/mod.rs.


podAntiAffinity matchExpressions wrong Key

I noticed that the pods were allocated on the same node. After investigating, I noticed that the key for matchExpressions should be 'name' instead of 'app' because the name of the app is 'my-mongodb-svc' not 'my-mongodb'. Even thought I also tried with 'my-mongodb-svc' and 'app', but it didn't work. When I changed the key to 'name', it worked because the replicaSet has the name 'my-mongodb'.
affinity:
  podAntiAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
    - labelSelector:
        matchExpressions:
        - key: app #This should be **name** instead of app
          operator: In
          values:
          - my-mongodb

thanks :)

I'll refresh this lesson at some point and update the code or you can create a PR. Thanks!


Allow multiple keybindings to work

This is not a duplicate of

https://github.com/microsoft/vscode/issues/39888
I'm specifically asking to run multiple commands in sequence.
https://github.com/microsoft/vscode/issues/871
Unconditionally running multiple commands per keypress is already possible using the geddski.macros extension. Also, implementing this would not necessarily satisfy #871 since its up to the bound command to decide if execution should continue to other bindings.

Problem
Both yzhang.markdown-all-in-one and takumii.markdowntable define keybindings to overwrite the tab key. In both cases, the behavior is dependant on the content and the cursor position.
The yzhang.markdown-all-in-one binding allows for indenting list items. If the cursor is not in a list, a tab character is inserted instead.
The takumii.markdowntable binding moves the cursor between cells in a formatted table. If the cursor is not in a table, a tab character is inserted instead.
Both of these provide a "new" behavior in some cases and falls back to a "default" if the new behaviour is not applicable. The use cases for these two new behaviors are unrelated, but due to the way keybindings work in vscode, they are fully incompatible.
See these issues for more context

https://github.com/yzhang-gh/vscode-markdown/issues/1015
https://github.com/takumisoft68/vscode-markdown-table/issues/18

New Feature
Keybindings should be able to call a preventDefault function (or for compatibility purposes, an allowDefault or callNext function such that if the current keybinding determines it is ineffective control may be handed back to either the next matched keybinding if one (or more) exists or the default behavior.
Additionally, some way to order the execution of the bindings would likely be beneficial. This would not require a new GUI either, adding a new property to a keybinding definition "priority": 1 which can be used to define the execution order. (Though in this case, the order the keybindings are executed would not matter)
[
	{
		"key": "tab",
		"command": "markdowntable.nextCell",
		"when": "editorTextFocus && !editorReadonly && !editorTabMovesFocus && !inSnippetMode && !suggestWidgetMultipleSuggestions && !suggestWidgetVisible && editorLangId == 'markdown'",
		"priority": 1
	},
	{
		"key": "tab",
		"command": "markdown.extension.onTabKey",
		"when": "editorTextFocus && !editorReadonly && !editorTabMovesFocus && !inSnippetMode && !suggestWidgetMultipleSuggestions && !suggestWidgetVisible && editorLangId == 'markdown'",
		"priority": 2
	}
]

In this case, the higher priority command markdown.extension.onTabKey will execute first, falling back to markdowntable.nextCell, then finally the default action provided by VSCode to insert a tab character (or indentation with spaces).

Thanks for the clear explanation.


Simplify crypto status in message view

Fundamental insight: We won't be able to display multiple pieces of content at once with different crypto statuses. Instead, there will always be the primary content of an email, for which we show a crypto status icon in the header.
This is a WIP PR working towards this, ripping out the message container thingies, adding an icon to the message header, and working from there.

Note: This PR reverts one commit on master due to #1293, will rebase properly as soon as that is fixed

So um, stuff is sort of piling up on this one. New things so far, in logical order of commits:

refactored Message*Extractor a bit, moving from mixed return types (return + parameter) to only parameter returns
the concept of multiple view roots is ditched, which mostly means that MessageViewInfo now is simple and flat structure (affects display only at first)
there is some preliminary work towards detecting non-pgp encrypted/signed parts and displaying them more gracefully in MessageDecryptVerifier
OpenPgpResultAnnotation is now immutable and uses a builder pattern (and is called CryptoResultAnnotation)
rewrites (and tests) to MessageDecryptVerifier, moving towards primary part centered message structure. Parts which are not inside the 'primary' crypto part are now remembered as extra-attachments
those extra-attachments displayed in a specialized "this content is insecure" attachment view (LockedAttachmentView)
add support for encapsulated signed parts (two-step processing in MessageCryptoHelper, and propagates signature results upwards if applicable)
rewrite of the data flow of OpenPgpApi, moving to -Source and -Sink callback classes. major performance improvement, and MessageCryptoHelper no longer needs to handle any synchronization with the service and streams itself
support for progress reporting from OpenPgpApi, there is now a nice (?) progress bar displayed if encrypted data > 4096 bytes is processed
MessageCryptoHelper operation can now be cancelled - K9 no longer crashes when it finishes after the fragment is no longer active
MessageCryptoHelper is now detachable, and retained by MessageViewFragment through cofiguration changes

For some reason, github shows the commits in incorrect order, they are shown in a different order to me locally. I guess they are shown chronologically? Not sure what's going on there. Anyways some of the features are not done in there (hence WIP PR), but I will try to finalize some parts and make individual, less monstrous PRs from them.

Stuff left to be done here:

[ ] Keep decrypted data in memory instead of on disk, unless it's larger than a few kb or an attachment. This optimizes for the short text message scenario
[ ] Better handling of returned openpgp errors
[ ] Hande cancelled operations, offer a retry button
[ ] Nicer UI for partially available messages
[ ] Hide message content for insecure/error cases? There is some room for discussion here
[ ] Handling of mismatched from / signer uid
[ ] Link to key in info dialog

This PR is no longer WIP. It's probably missing some polish, but should be ready for architectural review. At one point I pulled all purely logic changes related to message extraction up, which is basically everything up to fddcb19 ("messageview: nicer handling of PendingIntent..."), but at a later point this separation was no longer possible.
Since the list above (previous comment), the following change have been added:

decrypted text parts smaller than some kb are kept in memory
"locked attachments", for unsigned/unencrypted parts
"Unsigned Text" view for unsigned text parts (mailing list footers)
better handling of partially available messages
mismatched user id handling
crypto error overlay "Display message anyway" mechanism
logic for displaying of special crypto states (errors) is moved into MessageCryptoPresenter
moved all loading into MessageLoaderHelper, ditching the MessagingController callbacks as a loading mechanism. works with state preservation.

mismatched user id stuff is in the now released beta (click, the OpenKeychain beta is commonly only a couple commits ahead of master)

Fixed most of the comments, and commented on the others. Thanks for the review! :+1:

I find it very hard to review pull requests as large as this. It's too late to influence the architecture. Pointing out every small issue found would take forever (both adding comments and getting the issues fixed).
I'm okay merging the PR because it doesn't make the code significantly worse than it is now. But it also doesn't make it much better. It adds a lot of functionality without significant test coverage.
Unfortunately the lack of tests also shows in the code. It's relatively tightly coupled and I'm guessing it will take us a long time to refactor that later. But we do need tests or this whole thing will become even more of a nightmare to maintain :(
That being said, I do like the functionality. PGP/MIME support seems to be on a good way :+1:

This PR has been around since mid April as a WIP PR - I got no comments on its architecture. I extracted all changes in the loading logic in May (#1405) to make it easier to review - I got no comments on that either. There is only so much I can do to make these PRs bite-size, the complexity of branch dependencies I can manage is limited, and putting something up for review currently means I can't really work on it for an unpredictable time span which may be several weeks long, even for medium-sized PRs (e.g. #1392). But I do have a schedule to keep.
There is noone to blame here, but I'm afraid the simple fact is that with limited review capacities and long round trip times, this is as good as it's going to get.

Please don't rewrite the history every time you update the branch/PR. It makes it hard to see what changed.
Let's add a label to our PRs when we want to clean up the history before a merge. Reviewers then need to indicate that they're done instead of merging the branch right away.

I believe the only thing missing for this PR to be merged is fixing the one string, and a rebase (sorry for that).

Yeah, I wasn't thinking there. So used to rewriting my PRs at this point to keep them clean, I forgot it's not a good idea after it has been reviewed. I'll keep that stuff in fixup commits in the future.


Use burningwave lib to export javac packages from module

Attempt to solve the problem of running the plugin with Java 17, but without forking to add JVM args.
Could try hiding this behind a setting as a start, in case it causes problems....

Note that Burningwave does not seem to support aarch64, so this would now work for folks with arm linux laptops and m1 macbooks etc.

The burningwave lib feels a bit like overkill for this, and forking the plugin is more flexible, closing this and going with #140

At least this little part worked fine with an aarch64 JDK.

Trying to get some more clues on how this works and when/if it might break https://github.com/burningwave/jvm-driver/issues/2

If I change exportCompilerPackages default to true then integration tests pass locally with corretto 17 after rebasing on https://github.com/spotify/fmt-maven-plugin/pull/145.

Went with forking. #140


Fix glify layer to handle machina owned portals.

Added entry to color mapping in glify-layer.js to handle machina owned portals instead of silently failing to render cached portals at all. Additionally fixed fallback to handle scenario of being returned an unknown team again in the future - will render as neutral.

Oh, it looks good, thanks for your contribution :+1:


Update overview.md

This change resolves #105 by changing locoated to located.

Thanks @JonZavialov !


"Fetching outdated packages and themes failed" console error when starting Atom

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Steps to Reproduce

Open atom and it appears

Expected behavior: [What you expect to happen]

Don't complain

Actual behavior: [What actually happens]

The console reported an error

Reproduces how often: [What percentage of the time does it reproduce?]

100%

Even though I used atom --safe

Versions

Additional Information
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>(disabled)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Thanks for the report - just to clarify, are you seeing any problem using Atom (can you check for package updates in Settings > Updates) or are you just seeing the console error?
Also, is this error new for you recently?

Sometimes it comes up, sometimes it doesn't

This is likely a bug in apm.
I had a dependency which lacked a master branch and that was tripping up apm.  This must have been from a recent change in apm because I'm on arch linux and update my dependencies pretty frequently.
Anyhoo the short term solution was for me to push a master branch to the dependency - it was a package I made for personal use, so this was a reasonable solution.
I still don't like that software often depends on the master branch existing because it's such a weird branch name - this isn't the first time I've come across such a bug.

Sometimes it comes up, sometimes it doesn't

@linjialiang I remember from another issue that you connect through a VPN?  Since this happens sometimes and isn't generally reproducible, it seems like thee issue could be related to how you connect to the internet.  Are you able to try a different network connection?

We really need better diagnostic information for this error message.

@rsese

It seems that you have not encountered this problem, that should be my side of the problem, I am win10

@rsese

The problem is that our network does not support the installation of atom plug-in. We have to use VPN. This will happen when I turn off the VPN interface

~/.atom/.prmrc
strict-ssl = false
http-proxy = http://<IP_ADDRESS>:1080
https-proxy = https://<IP_ADDRESS>:1080

I have the same issue on Debian. And it doesn't matter whether I start Atom from the console or from the start menu -- it still displays "Fetching outdated packages and themes failed" when I open settings and try to see if there are any updates to the installed packages. Even if I run in safe mode, it still cannot fetch outdated package information.
And I don't connect through a VPN or a proxy.
 We have to use VPN. This will happen when I turn off the VPN interface

~/.atom/.aprmrc
strict-ssl = false
http-proxy = http://<IP_ADDRESS>:1080
https-proxy = https://<IP_ADDRESS>:1080

I got the same error and I don't use any vpn. however, when I open any package's page from https://atom.io/packages with its direct link, sometimes website gives error. I think your api just break connection at first error or something else... so, that more than a vpn issue.


[SPARK-32640][SQL] Downgrade Janino to fix a correctness bug

What changes were proposed in this pull request?

This PR reverts https://github.com/apache/spark/pull/27860 to downgrade Janino, as the new version has a bug.
Why are the changes needed?

The symptom is about NaN comparison. For code below
if (double_value <= 0.0) {
  ...
} else {
  ...
}

If double_value is NaN, NaN <= 0.0 is false and we should go to the else branch. However, current Spark goes to the if branch and causes correctness issues like SPARK-32640.
One way to fix it is:
boolean cond = double_value <= 0.0;
if (cond) {
  ...
} else {
  ...
}

I'm not familiar with Janino so I don't know what's going on there.
Does this PR introduce any user-facing change?

Yes, fix correctness bugs.
How was this patch tested?

a new test

cc @rednaxelafx @kiszk @maropu @viirya @tgravescs

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32324/
Test PASSed.

Right, I had hit another bug in Janino 3.1.2 elsewhere with this code pattern:
int x;
if (cond) {
  x = ...
} else {
  long y = ...
  x = ...
}

(the actual code to trigger the problem is slightly more complicate but this example shows the gist)
This Janino bug is specific to the new stack map calculation logic, which is new in Janino 3.1.x. Going back to the 3..0.x releases gets around the problem.
With that issue and the issue mentioned in this PR, it looks like the conditional branch handling in Janino 3.1.x has degraded quite a bit. Let's avoid Janino 3.1.x until we can have more confidence in it.
I'd like to also suggest adding some codegen test cases specifically to test the underlying Java compiler we use at runtime, be it Janino or any other alternatives (e.g. javac). WDYT?

Test build #127700 has finished for PR 29495 at commit 0e2faf6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/127700/
Test PASSed.

late LGTM

(the actual code to trigger the problem is slightly more complicate but this example shows the gist)
This Janino bug is specific to the new stack map calculation logic, which is new in Janino 3.1.x. Going back to the 3..0.x releases gets around the problem.

@rednaxelafx Thanks for the explanation, Kris! Have you already filed this issue in the Janino community? If you've done it, I think the link to it helps for better traceability. Also, is it difficult to add tests for the issue you describe above? I think its better to add tests for that, too, if we can run into it the Spark side.

Hi @maropu san, I haven't gotten around to file the issue with Janino yet (I'd probably have to build the latest Janino to make sure the issue still exists in Janino master before filing the issue...).
I was suggesting to add a new set of tests in Spark specifically to test the underlying Java compiler, because there are certain code patterns that may hit compiler bugs and we should use this set of tests to:

demonstrate valid Java that's not used by Spark yet, and it fails compilation (for documentation purpose, i.e. don't use the specified code pattern in the test in Spark codegen)
demonstrate valid Java that's used by Spark codegen, and it should pass compilation (for compatibility verification)

For the bug I mentioned above, it is not used by Spark codegen yet and I had hit it elsewhere, so I hadn't thought about downgrading Janino in Spark just for that. But now thinking about it again, I think the (1) case here is pretty important too. As soon as the underlying compiler fixes the issue, the "expect failure" test cases will get notified and we'll know those patterns can be used in Spark.
WDYT?

Nice finding and thanks for fixing the bug. Late LGTM. I agree that downgrading the version is good resolution in current situation.
Downgrading this to 3.0.x re-brings the question though, as 3.0.x is deprecated and author won't care about it. Is migrating Janino to 3.1.x our eventual goal, or we'd like to stick with deprecated version line and deal with the version by ourselves once we hit some other issue?

For the bug I mentioned above, it is not used by Spark codegen yet and I had hit it elsewhere, so I hadn't thought about downgrading Janino in Spark just for that.

okay, I see. Thanks!

I was suggesting to add a new set of tests in Spark specifically to test the underlying Java compiler, because there are certain code patterns that may hit compiler bugs and we should use this set of tests to:

That sounds good to me because Spark heavily depends on Janino... and I think these kinds of tests always make Spark more robust. WDYT, the others?  Out of curiosity; how do we extract the common code patterns and any idea?

Out of curiosity; how do we extract the common code patterns and any idea?

I was thinking of starting out from two sources:

known issues that Spark had hit in the past (extracting from JIRA tickets)
some known problematic code patterns with Janino manually discovered

I can help with the latter.

late LGTM for downgrading Janino.
I agree with adding test cases for focusing on validation of any Janino for changing its version.

@HeartSaVioR I think eventually we should move to the officially supported Janino versions, after they fix bugs we report.

Nice, LGTM

I found an interesting regression in Janino 3.1.2.
We may need to check the compilation speed, too.

Thank you for reporting that too, @kiszk .

By Janino author, the performance regression is introduced in 3.0.13 - we are still affected by the regression.
https://github.com/janino-compiler/janino/issues/131#issuecomment-683939866

Oh, good catch!


minification is messing up node-fetch's detection of abort signals

I'm using nodemailer-mailgun-transport. When attempting to call transporter.sendMail, I'm getting:
TypeError: Expected signal to be an instanceof AbortSignal

The stack trace is kinda useless because it's minified. Also, because mailgun-js bundles all its deps with webpack, it's pretty difficult to find, but I'm pretty sure here's where the mailgun-js code gets involved: https://github.com/mailgun/mailgun-js/blob/28c71ded8b15dfa84d5933c9d458b834aa952d7a/lib/request.ts#L76
After investigating, I realized that node-fetch attempts to validate whether signal is an AbortSignal based on the name of the constructor.
In the latest stable version of node-fetch:
https://github.com/node-fetch/node-fetch/blob/v2.6.1/src/request.js#L42
And in the v3 beta it's still based on the name, but is implemented slightly differently:
https://github.com/node-fetch/node-fetch/blob/v3.0.0-beta.9/src/utils/is.js
In any case, the minification of mailgun-js is causing this issue.
Suggested solution
At the very least, don't minify. This would solve the problem. Also, you may have a reason to bundle, but that's pretty unusual so I'm curious why you're doing it. Can you avoid it? In my experience people handle bundling themselves for stuff like this.

Hold it. I just realized I have the wrong package... nodemailer-mailgun-transport uses https://npm.im/mailgun-js and this is https://npm.im/mailgun.js 🤦
Still, the minification and bundling this project is probably not great 😅

Scratch that last comment... nodemailer-mailgun-transport is using this package (https://npm.im/mailgun.js): https://github.com/orliesaurus/nodemailer-mailgun-transport/blob/9fb9efd35a6113aa9f2ab7d9225091987a09d9a1/package.json#L39
Sorry, the naming of this stuff is pretty confusing. Perhaps consider updating the repo name to mailgun.js to reduce confusion? 😅

Just realized why this was working a few weeks ago and suddenly stopped working. 8 days ago, nodemailer-mailgun-transport switched from the old mailgun-js to this mailgun.js: https://github.com/orliesaurus/nodemailer-mailgun-transport/commit/9c6596ac48f3371291a63e2cf700a87ba450067a
So yeah, anyway, I'm not sure why nobody else has reported this issue because from what I can tell, this shouldn't work for anyone using mailgun.js on the server.

Just stumbled upon this same issue and I can confirm mailgun.js appears to be currently unusable with nodemailer-mailgun-transport. Can also confirm the naming of this package is very confusing.

I am having the same issue

Related https://github.com/mailgun/mailgun-js/issues/101. The workarounds don't seem to be ideal though...

Experiencing the same with "vanilla" mailgun.js.

Experiencing the same with "vanilla" mailgun.js.

Me too. I've switched back to https://github.com/mailgun/mailgun-js-boland until this is resolved.

Experiencing the same with "vanilla" mailgun.js.

Me too. I've switched back to mailgun/mailgun-js-boland until this is resolved.

Is it faster/better than STMP? Came here to replace nodemailer SMTP transport with this.

Is it faster/better than SMTP? Came here to replace nodemailer SMTP transport with this.

I've been using it for a while, and, although it's no longer maintained, it's been working fine for sending emails, which is all I've used it for.
From the docs:

You can also use good old SMTP to send messages. But you will have to specify all advanced sending options via MIME headers

For anyone else who only really needs to send simple emails (like me), here's what I wrote to do that with the API directly:
type MailgunMessage = {
  to: string
  from: string
  subject: string
  text: string
  html: string
}

const auth = `${Buffer.from(`api:${mailgunSendingKey}`).toString('base64')}`

function sendEmail(message: MailgunMessage) {
  return fetch(`https://api.mailgun.net/v3/${mailgunDomain}/messages`, {
    method: 'post',
    body: new URLSearchParams(message),
    headers: {
      Authorization: `Basic ${auth}`,
    },
  })
}

Docs:

https://documentation.mailgun.com/en/latest/api-intro.html#authentication
https://documentation.mailgun.com/en/latest/api-sending.html#sending

Look mah, no dependencies!

Hello @kentcdodds
I updated the terser plugin configuration to exclude class names from the minification process.
This update should fix the issue.
The updated configuration will be used for builds start from version 3.5.7


After FFT & Winograd, what next?

Thanks @scott-gray @andravin for the awesome Winograd work. That really makes small conv kernel run super fast!
And the cuDNN team implement them so rapidly and nicely, really makes life much easier. Good job! @jdemouth
After these fancy ideas, I can't help thinking that what can we do to speed up training next?
Following the path of mathematics-based matrix multiplication optimization approach, with Winograd, we are likely to have reached to roof. On the top of Winograd, I know Le Gall & François did some great works around 2014, but no breakthrough improvement.
Another interesting thing is the lack of FP16x2 support on GP104, which we highly look forward to, but instead, we got the full throughput dp4a, very powerful int8 computation ability.
I think in theory 8-bit is enough to carry the information with quantization. But how could we make good use of dp4a in training, it would be interesting.
So I wonder if @scott-gray @andravin @jdemouth @hughperkins @bhack @soumith etc. could share any ideas about this?
Sorry for can't cc all you lovely guys in community, who care about and contribute to DL performance. And any ideas are warmly welcomed!
@soumith, if you think here it's not so proper to discuss this topic, pls help me to close it and sorry for bothering. ;)

Hi @nomi-wei , just a clarification: our fast convnet algorithms use Winograd's convolution algorithms. But the same Shmuel Winograd did co-author the Coppersmith-Winograd fast matrix multiplication algorithm, so the confusion is understandable (I probably should not even mention that Winograd also devise fast DFT algorithms ;-)

@andravin Ha-ha, my bad. Thanks for your clarification. It's really really helpful. ;-)
I didn't got the book you referenced, so I thought you might use winograd's famous mm method for this.  LoL. No wonder I still find it hard to understand your approach, after I learned these mm algorithms from scratch these few days.
Thanks again!
BTW, Andrew, I wonder if you're still working on improving this conv kernel stuff? If yes, that would be awesome.

I think in theory 8-bit is enough to carry the information with quantization.

googling for dp4a reaches a thread with Scott Gray in as first hit :-)  https://devtalk.nvidia.com/default/topic/934562/cuda-programming-and-performance/nvidia-pascal-geforce-gtx-1080-amp-gtx-1070/post/4889687/  So I would say he's aware of it :-)
I was actually pondering dabbling with ints way back in 2014 http://computer-go.org/pipermail/computer-go/2014-December/007105.html  ... but it's just one of many things that never survived contact with finite-hours-in-the-day :-)
Considering the effort involved in making gpus work, and work quickly, I would think the first thing to do might be to demonstrate using normal cpu code that you can get ok results?  You could just fire up torch, and create torch.ByteTensors.
A few questions which occur:

how will you deal with overflows?  It's one thing to have multiplications truncated to some maximum value, it's another thing for them to overflow into the opposite sign...
8-bits means there are 256 different values.  How will you deal with, well, gradients and stuff?

Hmmm, I'm simply reciting back to you the questions that were stated to me when I mentioned the idea myself :-)  http://computer-go.org/pipermail/computer-go/2014-December/007106.html


Write Python script to generate translation catalog (.pot file) from the XML class reference

This is the description of a task that would be necessary to properly solve godotengine/godot-docs#3162. It should be relatively easy to do for someone familiar with Python and XML parsing.
To allow translating our class reference (XML files in doc/classes/*.xml but also modules/*/doc_classes/*.xml), we need to generate a gettext translation catalog (.pot file) that includes the description strings from all XML files.
I can then define a new project for it on https://hosted.weblate.org/projects/godot-engine/ ("Godot Class Reference") to collect translations from the community, and we can look in a second step how to load them in the editor for offline docs, and in the online version of the class reference on localized docs websites.

To do this first step of extracting strings from the XML to generate a .pot file, I suggest using Python and taking inspiration/code from the existing scripts we have:

editor/translations/extract.py is used to extract translation strings from the C++ codebase where TTR() is used. It generates a .pot file, and the new script which has to be written should generate a similar output.
doc/tools/makerst.py and doc/tools/doc_status.py both use xml.etree.ElementTree to parse the docs XML and respectively generate the rST docs we use on the website, and a status report about the docs completion.

So basically a mix of the XML parsing and the .pot writing needs to be done.
The output file (probably doc/translations/classes.pot) should include the strings for all classes, ordered alphabetically and following the same order as in the XML itself.
For the extracted descriptions, the tab XML indentation should be stripped, but space indentation inside [codeblock] tags should be preserved. Double quotes should be escaped (\"), and newlines in the XML should be converted to \n in the msgid. gettext msgids ignore line breaks, so where line breaks are necessary, they need to be explicit (and translators will have to keep them in place too).
The msgids should be wrapped at 79 characters (use msgmerge for that, see extract.py).
The context comment should give the source file's location and the relevant line. Multi-line descriptions should be kept in a single msgid to make it easier to translate with the full context (and thus with explicit line breaks \n).
E.g. for Sprite.xml, the relevant section might start this way:
#: doc/classes/Sprite.xml:4
msgid "General-purpose sprite node."
msgstr ""

#: doc/classes/Sprite.xml:7
msgid ""
"A node that displays a 2D texture. The texture displayed can be a region "
"from a larger atlas texture, or a frame from a sprite sheet animation."
msgstr ""

#: doc/classes/Sprite.xml:16
msgid ""
"Returns a [Rect2] representing the Sprite's boundary in local coordinates. "
"Can be used to detect if the Sprite was clicked. Example:\n"
"[codeblock]\n"
"func _input(event):\n"
"    if event is InputEventMouseButton and event.pressed and event."
"button_index == BUTTON_LEFT:\n"
"        if get_rect().has_point(to_local(event.position)):\n"
"            print(\"A click!\")\n"
"[/codeblock]"
msgstr ""

I tag it "junior job" as it should be fairly easy to do, but it requires some familiarity with Python. Any volunteers is welcome to ask me for more details :)

To allow translating our class reference (XML files in doc/classes/*.xml but also modules/*/doc_classes/*.xml), we need to generate a gettext translation catalog (.pot file) that includes the description strings from all XML files.

BTW, while our current documentation workflow is designed so that modules can include their own docs in module folder, for the purpose of this translation effort, I want the all classes of official modules collated in the same classes.pot.
Providing a way for custom modules to ship with localized documentation would be nice, but it's out of scope for the initial implementation of localized docs. Even if it could be done relatively easily from the start, it adds complexity in the Weblate workflow as we'd have to multiply the number of .pot files and thus of translation projects.

BTW would it be possible to also extract the chunks of code on the docs? Most of them have comments that can also be translated.

BTW would it be possible to also extract the chunks of code on the docs? Most of them have comments that can also be translated.

If you mean code blocks in tutorials like in https://docs.godotengine.org/ja/latest/getting_started/step_by_step/signals.html#timer-example, that's not related to this issue, which is about the XML class reference.

I'm going to work on this if there are not problem.