Linkify issues on yolo

Description
We have issues on this page, but they're not clickable. This would be a quick meta feature, probably named rgh-linkify-yolo-issues
Screenshot

Example URLs
https://github.com/refined-github/yolo/blob/main/broken-features.csv

@fregante can you please provide some more information about the issue.

In the "issue describing bug" column there are some numbers like "6109". Each of those is a reference to an issue, for example #6109.
The feature should look something like:
for (const issueCell of select.all('td:nth-child(2)')) {
  wrap(cell.firstNode, <a href={getRghIssueUrl(cell.textContent)}>)
}

Ok can this implementation solve this issue ??
import React, { useEffect, useRef } from 'react';

const LinkifyIssues: React.FC = () => {
  const issueReferences = useRef<NodeListOf<HTMLTableDataCellElement>>(
    document.querySelectorAll('td:nth-child(2)')
  );

  useEffect(() => {
    issueReferences.current.forEach((issueCell) => {
      const issueNumber = issueCell.textContent;
      const issueLink = document.createElement('a');
      issueLink.href = `https://github.com/your-repo/issues/${issueNumber}`;
      issueLink.textContent = `#${issueNumber}`;
      issueCell.innerHTML = '';
      issueCell.appendChild(issueLink);
    });
  }, []);

  return null;
};

export default LinkifyIssues;
```

Ok can this implementation solve this issue ??
import React, { useEffect, useRef } from 'react';

const LinkifyIssues: React.FC = () => {
  const issueReferences = useRef<NodeListOf<HTMLTableDataCellElement>>(
    document.querySelectorAll('td:nth-child(2)')
  );

  useEffect(() => {
    issueReferences.current.forEach((issueCell) => {
      const issueNumber = issueCell.textContent;
      const issueLink = document.createElement('a');
      issueLink.href = `https://github.com/your-repo/issues/${issueNumber}`;
      issueLink.textContent = `#${issueNumber}`;
      issueCell.innerHTML = '';
      issueCell.appendChild(issueLink);
    });
  }, []);

  return null;
};

export default LinkifyIssues;

We don't have React here. The code I suggested is 90% of what you need

ok sir thank you
I already created a Pull request. There is some chance the code may be wrong if it is please let me know because this is my first contribution.
And thank you once again for explaining the issue


build(semantic-release): updated semantic-release process

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add compareRows failed log

Ⅰ. Describe what this PR did
add log
Easy to troubleshoot rollback failure reasons.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1375 into develop will increase coverage by 0.04%.
The diff coverage is 62.5%.

@@             Coverage Diff              @@
##             develop   #1375      +/-   ##
============================================
+ Coverage      45.76%   45.8%   +0.04%
- Complexity      1653    1655       +2
============================================
  Files            343     343
  Lines          12322   12337      +15
  Branches        1549    1556       +7
============================================
+ Hits            5639    5651      +12
+ Misses          6053    6051       -2
- Partials         630     635       +5

Impacted Files
Coverage Δ
Complexity Δ

.../java/io/seata/rm/datasource/DataCompareUtils.java
70.73% <62.5%> (-2.41%)
27 <1> (+2)

...server/store/file/FileTransactionStoreManager.java
47.03% <0%> (+1.04%)
19% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Treat 404 from a URL as missing file, not fatal error

Rebase of #223

Added a little test suite for loading from URLs into this PR, it should probably be a separate PR but oh well.


Basic Login via js api not working

var user = new Parse.User();
user.set("username", "my name");
user.set("password", "my pass");
user.set("email", "email@example.com");
// other fields can be set just like with Parse.Object
user.set("phone", "415-392-0202");
user.signUp(null, {
success: function(user) {
// Hooray! Let them use the app now.
},
error: function(user, error) {
// Show the error message somewhere and let the user try again.
alert("Error: " + error.code + " " + error.message);
}
});
Get error 403

Can you provide logs by running parse-server with VERBOSE=1

I'm using the express server so I can get https. How exactly do I pass that to it?

just set an environment variable VERBOSE=1 before you start parse server. if you start with node server.js that would be VERBOSE=1 node server.js

`var fs = require('fs'),
https = require('https');
var ssl = {
key: fs.readFileSync('./', 'utf8'),
cert: fs.readFileSync('./', 'utf8'),
ca: [fs.readFileSync('./', 'utf8'),
fs.readFileSync('./', 'utf8')]
};
var express = require('express');
var ParseServer = require('parse-server').ParseServer;
var databaseUri = ' ';
var port = process.env.PORT || 4337;
//var port = 443;
var api = new ParseServer({
databaseURI:  databaseUri,
cloud: __dirname + '/cloud/main.js',
serverURL: 'aa',
appId: 'aa,
'javascriptKey':'aa',
restAPIKey: 'a',
clientKey:'a',
facebookAppIds :['a'],
masterKey: 'a'
});
var app = express();
// Serve the Parse API on the /parse URL prefix
var mountPath = '/a';
app.use(mountPath, api);
app.use(express.static('public'));
// Parse Server plays nicely with the rest of your web routes
app.get('/', function(req, res) {
res.status(200).send('I dream of being a web site.');
});
app.listen(4338,function () { console.log('Server on port 4338'); });
https.createServer(ssl, app)
.listen(port, function() {
console.log('Server running on port ' + port + '.');
});`

I changed all my urls and keys to paste it in here. They are not actuall "a"

I need the server logs, when you're trying to do the login to identify the potential problem.

You mean the logs from the javascript call? Sure one sec

The logs the server is printing in the terminal/console when you run that.

Oh lol, I use the forever service. This ain't running in a console. One second, I will oblige.

There are no logs in the console.
 Request URL:https://:4337/FaithServer/users Request Method:POST Status Code:403 Forbidden Remote Address: :4337 Response Headers view source Access-Control-Allow-Headers:* Access-Control-Allow-Methods:GET,PUT,POST,DELETE,OPTIONS Access-Control-Allow-Origin:* Connection:keep-alive Content-Length:24 Date:Sun, 24 Apr 2016 17:50:00 GMT X-Powered-By:Express Request Headers view source Accept:*/* Accept-Encoding:gzip, deflate Accept-Language:en-US,en;q=0.8 Connection:keep-alive Content-Length:239 Content-Type:text/plain DNT:1 Host::4337 Origin:https://:4337 Referer:https://:4337/signup.html User-Agent:Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 Request Payload view source {username: "my name", password: "my pass", email<EMAIL_ADDRESS>phone: "415-392-0202",…} _ApplicationId : "a" _ClientVersion : "js1.6.14" _InstallationId : "bf757e4d-1ade-f921-030d-1192034d1356" email<EMAIL_ADDRESS>password : "my pass" phone : "415-392-0202" username : "my name"

Response is {"error":"unauthorized"}

However, our iphone app can accss/create users fine.

those are not the server logs when running with VERBOSE=1, I need the server logs, not the client logs

If that's an issue on the JS SDK so open the issue on the JS SDK repository

I understand, how do I start it with that parameter. Just node index.js VERBOSE=1
You have to understand I'm not a node programmer so the things you think are obvious aren't.

Where exactly is the js api? I'm using the one that used to be hosted on parsecdn. Is there another one?

https://github.com/ParsePlatform/Parse-SDK-JS/issues
Also did you set correctly serverURL in your SDK?

Yes, and I'm using that one, how do I turn on verbose mode? I don't think it's an sdk issue or there'd already be open issues.

It's posting to the correct url in the logs. It's not trying to go to parse.

you set VERBOSE=1 on your server, not on the client SDK

I know, where though? At what point  in the index.js above? Or does parse-server module parse command line args?

this is an environment variable. so, just set that environment variable and restart your server. If you don't know how to set an environment variable, I believe stack overflow or google can help you

Oh I know how to linux like a pro.

I don't even know node and I set all of this up.

Well, I set up an issue here: https://github.com/ParsePlatform/Parse-SDK-JS/issues/262
You can probably mark this as closed. Is there a way to force parse-server to always log verbose to a file?

run with VERBOSE=1 and forward the stdout/stderr streams to your log files.

Fairly unprofessional.

Setting env variables isn't a good solution for logging. Please add a feature to set a verbose log file. Thanks anyway.

What do you mean? If you're using forever everything is in the forever docs right on the README.md

And PR's are welcome, I belive there is also a verbose option, that you can set to true, when you create a new ParseServer.

I turned the forever off to run it in the console. I removed the element. So there is a parse server option "verbose"?

So to be clear, since it hasn't added anymore logging or the error is with jssdk,
var api = new ParseServer({   databaseURI:  databaseUri, verbose:true,

I'm not 100% sure if that flag enables the console logs, that's why you can enable the console logs by using VERBOSE=1 as an environment variable.

I did the env variable. Nothing additional came out of the console.

The error is 403 forbidden. Does that mean parse rejected the request ?

that mean the authentication failed. How did you do the environment variable?

[root@localhost ParseServer]#VERBOSE=1
[root@localhost ParseServer]# node index.js
â–€ â•¢â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘making app
Server on port 4338
Server running on port 4337.
`

that would be VERBOSE= 1node index.js
Also, that's a bad idea to run a server as root...

Parse JavaScript SDK v1.6.14

The forever service normally runs this as a separate user.

that would be VERBOSE= 1node index.js
^^ what are you saying ?

the command you should run should be :
VERBOSE=1 node index.js

Still no difference

Must be a javascript api issue. 1.6.14 ... Would it matter that I'm hosting the .js file and not on parsecdn?

I was trying to avoid having to set cross-domain stuff.

So I'm not sure what's wrong because that should start printing every requests/responses in the console.
That would mean your JS-SDK is not properly configured and is not going to your server.

going back to your logs you posted from the JS-SDK,

Request URL:https://:4337/Parse/users

For some reason that seem plain wrong...

well I removed the url...

I can pm you the site

[root@localhost ParseServer]# VERBOSE=1 node index.js
making app
Server on port 4338
Server running on port 4337.

well, that seems to be the issue... Did you double check your javascriptKey is valid? Also, because the server responds with 403, this is a SDK authentication issue.

Yes, the key and the appID match.
The error is odd:
ParseError {code: undefined, message: "unauthorized"}

I'm going to try removing the js key from index.js and just using the appid

Nope same problem. Even if I disable the jskey, clientkey, and restapikey.

what version of parse-server are you using? Any chance to get the logging working, otherwise it would mean that the requests don,t hit the proper server...

Whatever is the latest. This install is 2 weeks old. I ran npm update in the folder.

I tried with the masterkey. Same error.

Does other queries get logged when running your server with VERBOSE=1? That's what worries me about your setup as it seems that the client never reaches the proper server....

I can manually enter the url for the server mount in the browser and see nothing in the log

that doesn't make sense at all...

Welcome to the world of programming.

:)

why do you have 2 different port logged:
Server on port 4338
Server running on port 4337.

Your https server is listening on 4338 it seems and all your requests seem to go to 4337...

4337 is http (normal 80)
4338 is https (normally 443)

and if you do everything on HTTPS? would that change anything?

nothing changes no matter which port I select.

I disabled http for the purpose of testing now. Nothing changes.

I'm running centos btw, not ubuntu

Does any query make it through to your server?

yes, but they all return the same error message  ParseError {code: undefined, message: "unauthorized"}
I'm initing with the appid and jskey
Parse.initialize("appid","jsserver");
Parse.serverURL = 'https://:4337/Parse'

is your mount path correct? your replaced it with /a in your config, did you pass serverURL to be from the proper form? http://localhost:1234/Parse ?

yes, like I said. I copied this from our working iphone app exactly.

My configuration has been tested and supports a full app.

SO that's an issue with the JS SDK most likely, that's still not expected that no logs are being triggered on the server. Do you confirm that running with VERBOSE=1, the calls from the iOS app are getting logged?

I can not change the IOS app server as it is in production.

This is the dev server to set up the js work.

However, like I said, it's an exact clone.
Could it be express ?

and the iOS apps pointing to the dev server? This don't seem to be an issue on parse-server as you got it working with other SDK's.

You're starting to see why env variables are what I called unprofessional. You gotta command line it or pass it as a server option otherwise you'll run into this situation where an oddball config'd server doesn't play nice.

env variable are better than updating your source code to enable verbose logging...

no, lol. It should be a simple flag either way. Relying on OS specific things like env variables is very unprofessional.

this is an open source project, you're welcome to contribute to make it fit your needs.

Thanks for the help!

Please don't try that excuse. I've used parse for my clients for years. I'm having to do countless hours of free work now because of this "transition." We're all doing our part.
Check your ego at the door, mate. I'm just here to get this stuff out the door not compare dicks.

Thanks for this thoughtful response. But as you probably noticed, not only the login is not working for you but also all queries respond with an error. You also probably noticed that your iOS SDK is working correctly with your setup. So I doubt that the error is an issue with parse-server, but most likely an issue with the configuration / javascript SDK.
I'm not really sure what the error is, nor what the problem is. AFAIK, the VERBOSE flag should start spitting out logs and more precisely all request and response logs.
Yes verbose logging requires an environment variable, like express need an environment variable to enable DEBUG logging or the http module needs as well an environment variable to enable more logs.
Again, I can only encourage you to contribute, and if you haven't noticed, I'm not part of Facebook, but a guy like you, having clients relying on their parse instances to work and be transitioned.


partially parallelize

We explicitly do not want a fully factorized job list with one job per package.
Such an approach would

heavily depend on github workflows and
include generating workflow files from repos files with parsed package.xml (this leaving even more room for glue-code errors framework in the future.

Instead, it would help to split especially universe into <5 independent jobs to speed up the build by some hours.

Successfully implemented.
The implemented "staged" parallelism accelerates build times from 26+h to 12h.


v1.5.0 panic: unable to mmap memory: cannot allocate memory

my vps: CPU: 2 cores Memory: 4GiB, This problem will not occur when I fall back to<EMAIL_ADDRESS><EMAIL_ADDRESS>panic: unable to mmap memory: cannot allocate memory

goroutine 1 [running]:
github.com/tetratelabs/wazero/internal/wasm.NewMemoryInstance(0xc001190280)
        /root/go/pkg/mod/github.com/tetratelabs/wazero@v1.7.0/internal/wasm/memory.go:85 +0x1d7
github.com/tetratelabs/wazero/internal/wasm.(*ModuleInstance).buildMemory(0xc001070d00, 0xc001102a80)
        /root/go/pkg/mod/github.com/tetratelabs/wazero@v1.7.0/internal/wasm/module.go:658 +0x2d
github.com/tetratelabs/wazero/internal/wasm.(*Store).instantiate(0xc000074b40, {0x500c848, 0x8794120}, 0xc001102a80, {0x3e6ad13, 0x3}, 0xc001178840, {0x8794120, 0x0, 0x0})
        /root/go/pkg/mod/github.com/tetratelabs/wazero@v1.7.0/internal/wasm/store.go:366 +0x2c5
github.com/tetratelabs/wazero/internal/wasm.(*Store).Instantiate(0xc000074b40, {0x500c848, 0x8794120}, 0x0?, {0x3e6ad13?, 0x0?}, 0x0?, {0x8794120, 0x0, 0x0})
        /root/go/pkg/mod/github.com/tetratelabs/wazero@v1.7.0/internal/wasm/store.go:325 +0x5a
github.com/tetratelabs/wazero.(*runtime).InstantiateModule(0xc0011666f0, {0x500c848, 0x8794120}, {0x501d160, 0xc001168580}, {0x5034ec0, 0xc000b73950})
        /root/go/pkg/mod/github.com/tetratelabs/wazero@v1.7.0/runtime.go:312 +0x1e5
github.com/tetratelabs/wazero.(*runtime).InstantiateWithConfig(0xc0011666f0, {0x500c848, 0x8794120}, {0x7d71d70?, 0x553440?, 0xc000e9ff80?}, {0x5034ec0, 0xc000b73950})
        /root/go/pkg/mod/github.com/tetratelabs/wazero@v1.7.0/runtime.go:277 +0x74
github.com/wasilibs/go-re2/internal.init.0()
        /root/go/pkg/mod/github.com/wasilibs/go-re2@v1.5.0/internal/re2_wazero.go:157 +0x34d

Hi @yhy0 - thanks for the report. I realized that the current approach that mmap's a static amount of virtual memory for shared memory doesn't work on smaller machines. I have tried a change to dynamically size it based on total memory available to the process, could you see if it helps?
https://github.com/wasilibs/go-re2/commit/9f8aa894048abebc4f9d0fd48ce77415679ae5da

Everything seems fine now. 👍

Thanks for confirming! I have issued a patch release with the fix.

Hi @yhy0 - there have been some tweaks to the memory allocator in the latest main. Would you be able to try it to confirm your issue doesn't regress? Unfortunately I don't have good access to a system that reproduced the "cannot allocate memory" issue. Thank you.


Replace ethereum-cryptography dependency

Replace the ethereum-cryptography module usage by utilizing @noble/curves utilities.

@PhilippeR26

OK. I can quickly handle it.


Terraform Initialization Instructions

I'm having some trouble following these instructions.
When you setup the service principal you have the choice of setting up a password or a certificate. If you choose certificate then it isn't clear what this section means:
export ARM_CLIENT_SECRET=your_password
I added the location of my pem file, I'm not sure if that is correct.
In the JSON that was returned after I setup my service principal looked like this:
"fileWithCertAndPrivateKey": "/home/test/some_name.pem",
"name": "xxx",
"password": null,
So should I use null or the value from fileWithCertAndPrivateKey?
If feel like the section for:
subscription_id, client_id, client_secret, tenant_id
Needs more detail ... what are these values and how to you find them? The line for account show is helpful for the subscription Id and the tenant Id, but what about the other two?
If you look in the Terraform documentation, this is also not clear:
ARM_CLIENT_SECRET - The Client Secret associated with the Service Principal.
Also ... in the section of documentation for creating the environment variables there are no quotes around what you are supposed to enter.
Is it:
export ARM_SUBSCRIPTION_ID=your_subscription_id
or
export ARM_SUBSCRIPTION_ID="your_subscription_id"
Maybe it doesn't matter?
In this section, for the initialization script:
provider "azurerm" {
}
resource "azurerm_resource_group" "rg" {
name = "testResourceGroup"
location = "westus"
}
It isn't clear what this is doing. What is provider and what does that mean, what is a resource? I would assume azurerm is Azure Resource Manager ... but what is that? A terraform entity? Something to do with Azure?

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

ID: 78bafe84-4e50-785c-b4f6-e629127a80a9
Version Independent ID: 34e5924e-2d7e-3bf2-0992-78eb59463a6a
Content: Install and configure Terraform for use with Azure
Content Source: articles/virtual-machines/linux/terraform-install-configure.md
Service: virtual-machines-linux
GitHub Login: @echuvyrov
Microsoft Alias: echuvyrov

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

@jpconnock can you help assign this one correctly?
I am unable to assign to content author @echuvyrov

@MicahMcKittrick-MSFT - I can take it from here.
Hello @Tempest1000, sorry that you're having trouble following the doc. We document the creation of service principal in [this section](url
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/terraform-install-configure#set-up-terraform-access-to-azure) via the command [az ad sp create-for-rbac --role="Contributor" --scopes="/subscriptions/${SUBSCRIPTION_I] and the output of that command should have all the values you need to set in the next section, like this
export ARM_CLIENT_ID=your_appId
export ARM_CLIENT_SECRET=your_password
For your questions about the provider - the article assumes that you are already familiar with Terraform and shows you how to get started with it in Azure. This set of documents could be a good guide to learn more about the tool itself.
Let me know how I can be of further assistance,
Eugene

@Tempest1000 Thank you for the feedback. It looks like this issue has been answered, so I am going to close it now. If the answer provided is not enough or you have more feedback, please reopen this issue or create a new one. Thanks again!
#please-close


[hi] Localize /en/docs/reference/glossary/pod-disruption.md

Signed-off-by: Aayush<EMAIL_ADDRESS>Fixes: https://github.com/kubernetes/website/issues/37536
Please review and suggest any changes if needed.

/lgtm

@bishal7679 Does this pr need any more modifications? I think i have done all the changes mentioned above.

/cc @divya-mohan0209

@bishal7679 Does this pr need any more modifications? I think i have done all the changes mentioned above.

@Aayush987 apologies for the delay!


postal smtp incoming request slow and sometimes block

hi,
the incoming request through port 25 to server get connection time out from other servers.
it seems we are happening with DDOS attack in port 25. how can we monitor?
we check smtp-server logs in the log folder and we see many fails with 535 Invalid credential
we add csf firewall to server and add ips to black list but nothing change.

Unfortunately having port 25 open, as is required, means that people will try credentials and exploits that affect other mail server software.
Does your server have enough resources to deal with your expected traffic? Does your postal status show a lot of respawns or restarts?

hi thanks for your response.
how can we add another port like 2525 or 587 for sending?

yes postal status is correct and server resource usages is low.
but telnet domain 25
sometimes dose not response and sometimes is slow.

You can change which port is used in the config file postal.yml however this will mean you would have problems receiving bounces and any incoming messages unless you also open port 25 with another method like iptables.
There is #751 which may help but I'm not completely sure it would.

Thanks @willpower232.


id or _id (test 'Testing issue #48')

In the api documentation it states (emphasis added):

Put some new docs, providing the _ids:

and shows the code:
db.bulkDocs([
  {title : 'Lisa Says', _id: 'doc1'},
  {title : 'Space Oddity', _id: 'doc2'} //...

In test.basics.js for the 'Testing issue #48' test it shows:
var docs = [
  { 'id': '0' }, { 'id': '1' }, { 'id': '2' },
  { 'id': '3' }, { 'id': '4' }, { 'id': '5' }
];

The difference is that in the api documentation it states the id is an _id property, but in the docs it uses id without the leading underscore.
Question
Which form should we add into the d.ts file for v3.4.0?

_id
id
Both (might be tricky)

It is worth reiterating - we don't have to enforce either form, but the d.ts can guide developers by enforcing properties. For document operations that require an id we could stick to specifying that _id is required, or put both id and _id on the document interface and make them both optional - however that will then cause complications with intellisense resolving overloads, I think.
If _id is now the recommended way as of v3.4.0 then we can stick to that, and more advanced devs can probably tweak the d.ts to have id if they require it.

From IRC:
[18:34:44] <AndyBrown> nolanlawson: ... is that test mistakenly missing an underscore in front of id for the objects in the docs array?
[18:44:09] <nolanlawson> AndyBrown: yeah, that test is a mistake
[18:44:22] <nolanlawson> notice that it's not even verifying that the _ids its gets back are 1, 2, 3, 4
[18:44:44] <nolanlawson> it could say var docs = [{}, {}, {}, {}, {}, {}] and the test would still pass
[19:02:01] <AndyBrown> nolanlawson: that's what I figured once you had confirmed that documents use _id, and typescript using my d.ts was essentially telling me the same - which was a bonus.

Closing: as per nolanlawson's comment on IRC:

documents themselves always use _id. Responses to operations (aka "info" objects) always use id

i.e. - the confusion that led to this issue was due to pouchdb/pouchdb#3810 (the test documents should have used _id, or just renamed id to foo to prevent confusion with an actual document _id).


Rimworld Core folder somtimes causes desync or mismatch when connecting

@Parexy Do you have Any more information about this bug?


tensor.float16 support?

Dear Chris,
Due to my limited GPU memory, I was wondering if MinkowskiEngine support float16 computation? I am getting an error when making model as model.to(dtype=tensor.float16), then I am getting this error.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
f"Type mismatch input: {input_features.type()} != kernel: {kernel.type()}"
AssertionError: Type mismatch input: torch.cuda.FloatTensor != kernel: torch.cuda.HalfTensor
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Is that maybe because your pretrained model is in float32?
Thank you in advance.

Hi,
Currently, it is not supported. I will add support for it as soon as possible, but it should be sometime next week at the earliest.

Thanks a lot.


EVM-507 Integrate account-abstraction-invoker contract

Description

Add  https://github.com/0xPolygon/account-abstraction-invoker as a submodule to the edge
implement sendtx command just to test everything
Implement EVM-515 AA - E2E test

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[X] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[X] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[X] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[X] I have tested this code with the official test suite
[X] I have tested this code manually

Manual tests

$ make compile-core-contracts
$ make build
start cluster script from terminal $ ./scripts/cluster polybft
Deploy account-abstraction-invoker/contracts/AccountAbstractionInvoker.sol (send appropriate transaction and send it some of cluster nodes). Get INVOKER_ADDRESS of deployed contract
in second terminal execute aa relayer $./polygon-edge aarelayer --addr <IP_ADDRESS>:8198 --data-dir ./test-chain-1 --jsonrpc <IP_ADDRESS>:10002 --invoker-addr INVOKER_ADDRESS
in third terminal execute command which sends tx to relayer ./polygon-edge aarelayer sendtx --data-dir ./test-chain-2 --addr <IP_ADDRESS>:8198 --tx 0xc0ffee254729296a45a3885639AC7E10F9d54979:100:21000 --nonce 0 --invoker-addr INVOKER_ADDRESS

Would be great to provide a link to the EIP307 specification, which explains the way hash is calculated within Make3074Hash function.


fix(edge-proxy): [WEBS-000] fix condition to handle edge proxy

What problem does this PR solve?

It not call api edge-proxy because miss the condition

How does this PR solve it?

fix condition to handle edge proxy

TERMS & CONDITIONS: By pressing submit, I do hereby declare that my PR meets the following requirements of all code on Pomelo.:

The Definition of Done (However, if this PR is for a partial story, certain pieces of that may be deferred until the story is complete. Please complete all pieces related directly to this one PR.)
The Code-Review Guidelines
The UI Styleguide and Code Conventions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[feature] Output provenance as Sigstore bundle format

Is your feature request related to a problem? Please describe.
There is no support for offline verification currently. While a certificate is persisted in the DSSE signature, the Rekor entry proof is not, meaning the SLSA verifier must do an online lookup for the entry in Rekor.
Additionally, since all Sigstore clients now support the bundle format, this would allow SLSA clients to directly use Sigstore libraries to handle verification of the attestation signature (reducing code and simplifying maintenance), with the SLSA client handling verification of the attestation contents.
Describe the solution you'd like
Sigstore has defined a bundle format to store an attestation or signature along with verification metadata (certificate, signed timestamps, and Rekor log proofs). The generator should output a .sigstore.json bundle (the extension matches what other Sigstore clients output).
This was discussed in https://github.com/slsa-framework/slsa-github-generator/issues/716, but this issue was filed before the bundle format was created. This issue tracked persisting Rekor's inclusion proof as its own file.
Describe alternatives you've considered
An alternative would be to have a divergent format or save verification metadata as "detached" files, which complicates storage of that metadata for no benefit.

The "BYOB" (bazel, maven, gradle, nodejs) builders will use the "delegator" workflows, which will use our .github/actions/sign-attestations action to produce Sigstore bundles.

https://github.com/slsa-framework/slsa-github-generator/blob/afa0f38ec2bbdf5230c68444c7e964bb19e2b64b/.github/workflows/builder_maven_slsa3.yml#L84
https://github.com/slsa-framework/slsa-github-generator/blob/afa0f38ec2bbdf5230c68444c7e964bb19e2b64b/.github/workflows/delegator_generic_slsa3.yml#L278
https://github.com/slsa-framework/slsa-github-generator/blob/afa0f38ec2bbdf5230c68444c7e964bb19e2b64b/.github/actions/sign-attestations/src/main.ts#L44
Example maven e2e workflow run - https://github.com/slsa-framework/example-package/actions/runs/10135785683

The go builder and generic generator, still only produce the DSSE envelope.

https://github.com/slsa-framework/slsa-github-generator/blob/afa0f38ec2bbdf5230c68444c7e964bb19e2b64b/internal/builders/generic/main.go#L28
Example generic generator e2e workflow run - https://github.com/slsa-framework/example-package/actions/runs/10137367218

If there were a go library for producing Sigstore bundles, then we could easily integrate it within existing code for producing attestation envelopes. But it seems only the sigstore-js library can do that.
Otherwise, I think we might be able to use reuse our existing .github/actions/generate-attestations and .github/actions/sign-attestations actions in the generic and go workflows.

https://github.com/slsa-framework/slsa-github-generator/blob/afa0f38ec2bbdf5230c68444c7e964bb19e2b64b/.github/workflows/delegator_generic_slsa3.yml#L267-L281

^ This could also make it easier to get all the generators to start using the SLSA v1.0 format for provenance, and simplify the slsa-verifier code significantly.

I agree we should try to move the generic generator and go builder to use BYOB code and internal actions. Ideally we could eventually remove the Go code to consolidate on TypeScript (and bash to a lesser extent). It would be a significant effort since it's essentially a rewrite but fairly straightforward.
I don't think we can really eliminate the Go code from the container-based (docker) builder that @asraa and @rbehjati worked on though. I don't know if anyone's using it or if we should properly support it.

To give an update, sigstore-go now has bundle-producing functionality that I make use of in this PR to address this issue.

https://github.com/slsa-framework/slsa-github-generator/pull/3777

@ianlewis I also agree, but while attempting, I found that

if we used BYOB, not all the parameters that are available in the original workflow will work with BYOB. This means there would be breaking changes.
Directly using our .github/actions/generate-attestations and .github/actions/sign-attestations actions in the original workflow requires a lot of careful and extensive manual testing.

Directly using our .github/actions/generate-attestations and .github/actions/sign-attestations actions in the original workflow requires a lot of careful and extensive manual testing.

Could you elaborate more on what you mean here? My understanding is that they currently expect to be a builder and thus generate a subject hash from the artifacts themselves, whereas for the generic generator we would need it to take the subject as an input. What kind of additional testing do you think would be required?

@ianlewis I mean when I want to organize the actions, and their input and outputs. It took me a long while to demo a working conversion of the "generic-generator" that uses the "delegator".
I say it would be difficult to test because I think I would have to also include setup-generic and verfy-token in order to generate the SLSA_PREDICATE_FILE.

https://github.com/slsa-framework/slsa-github-generator/blob/3bcecb4ade4f265cff30488059a9dca39e26b360/.github/workflows/delegator_generic_slsa3.yml#L107

I hadn't tried it yet, so maybe it wouldn't have been so difficult. Github Actions workflows are generally not easy to debug, so I thought working with the go code would be a simpler to develop for.

Right. BYOB does need to be support generators. Should be a fairly straightforward conversion for the Go builder I think though.

Github Actions workflows are generally not easy to debug, so I thought working with the go code would be a simpler to develop for.

BTW, most of the TypeScript (aside from code that uses OIDC) should be able to be run locally if given the right environment variables and is similar to the Go code in that regard. Though not all of the actions are easy to invoke this way. I usually just set up some tests and run locally to debug before testing on GitHub Actions since the iteration loop is long there.


Probably missind headers for delete from arr*

Description
To develop, with the new coming change from Fetch API, the button on managing media to delete a media from doesn't work anymore.
It's actually deleting the request but not the movie inside radarr or sonarr.
Edit: Could be related but every 5secondes in my Chrome browser console I got this error with the endpoint of the media it's on, like a series on sonarr and movies on radarr see the screenshot.
Version
Develop
Steps to Reproduce

Click on Manage media inside a request
Click on delete from sonarr or radarr

Screenshots

Logs
No response
Platform
desktop
Device
PC - Windows
Operating System
Docker
Browser
Chrome 127
Additional Context
No response
Code of Conduct

[X] I agree to follow Jellyseerr's Code of Conduct

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


md-select multiple with check box window not closing in AngularJS v1.3.16

Dear all, here am using angular meterial design md-select multiple but this multi select window not closing when i was using the AngularJS v1.3.16 and it will work properly if i use  AngularJS v1.5.11.
so i need solve this issue what was wrong going on...thanks

Hi @subhashekkaluru , you're reporting an issue that has to do with https://github.com/angular/material, please report it there. Material2 needs at least Angular version 2.

thank u


Any disadvantages?

Hi, thanks for the great package. I don’t have any seo experience. So, I have to ask this question before investing in Flutter for web. Does this package have any disadvatages when compared to other seo packges or when compared to regular js web apps?

Hey. I would say it really depends on your situation. If webpage is the only thing you need I would probably go for the regular js web app as there's still quite a lot of unanswered "How does the googlebot actually work" questions which you can read more about here: https://github.com/flutter/flutter/issues/46789 but if you're planning to create Android/iOS/Web project and not aiming for 100% perfect SEO support at least not for now then I would advise you to give this package a try.
The only other SEO package I'm familiar with is https://pub.dev/packages/seo_renderer which I did work on (a bit) but for now I cannot say if it's better/worse. The issue with it is that the solution might be seen as cloaking which is black hat seo, so to solve it I created this package.
Currently I'm waiting for Google to index my example webpage https://krokyze.github.io/flutter_seo once i'll get some results I'll share the within README.

I think the main problem with Google bot is that it uses the same principle as a browser's "find on page" feature. One cannot search through the whole page only through a part which is visible on the screen at the moment.
As far as I can see your solution doesn't bring anything new to that

@Andreigr0 initially the main goal for this plugin was to tackle the issue which seo_renderer had. That the solution isn't potentially seen as black hat seo and is updating html doesn't matter if it's robot or not. You can try out the demo page https://seo.krokyze.dev/#/posts and check that "find on page" does actually work.
If you're thinking about content hidden behind the scroll that's infinite scroll issue, which is an issue for regular webpages too, you can read more about here how GoogleBot handles it: https://www.searchenginejournal.com/how-google-crawls-pages-with-infinite-scrolling/439008/

For whatever reasons Google didn't index the page while I was using Github default domain http://krokyze.github.io/flutter_seo
After setting up custom one seo.krokyze.dev and re-requesting indexing from Google they did it for only the list page, so I'm still trying to figure out what do I miss in the config.
But what I can confirm for now is that Google was able to index the content:

Hi! What happened to the demo? Is it still working? If i try out the searches from the previous comment's images I don't get these nice results.. Thanks!

Hi! What happened to the demo? Is it still working? If i try out the searches from the previous comment's images I don't get these nice results.. Thanks!

Hey, slowly (not enough time + validation within Google takes alot) exploring and trying to understand what am I missing as still only the landing page is indexed and none of the items. Few weeks ago I found out that possibly all of them are ignored because I was still using the hash in url. So I migrated to path url strategy and submitted the page for reindex, now waiting for some potential changes in results.
I still see the same search results as mentioned before:
https://www.google.com/search?q=site%3Aseo.krokyze.dev&ie=utf-8&oe=utf-8&aq=t
https://www.google.com/search?q=flutter+seo+green+papaya+salad&ie=utf-8&oe=utf-8&aq=t

Ohh sorry I messed up something (I don't know what :D), but now I get the same results.
Please let us know if there is any update with the reindexing, thank you again! :)

Did you try both html and wasm modes 🤔

Did you try html mode as used on Android instead of wasm 🤔

Not sure if I'm understanding the question but I'm using HTML mode for GoogleBot as the initial load is faster.

Not sure if I'm understanding the question but I'm using HTML mode for GoogleBot as the initial load is faster.

I just wondered if the flutter app being built in html mode would make any difference or not?
--web-renderer html

I also wonder if the following widget has any influence on text indexability?

I just wondered if the flutter app being built in html mode would make any difference or not?
--web-renderer html

It does affect the initial load of page as the CanvasKit is about 2MB extra in download size. It's in the tips https://github.com/krokyze/flutter_seo#force-html-renderer-for-bots
For example https://seo.krokyze.dev/posts initial load difference on Google Chrome is 2.4MB (CanvasKit) vs 806kB (HTML).

I also wonder if the following widget has any influence on text indexability?
https://api.flutter.dev/flutter/widgets/EditableText-class.html
Edit: Sorry I meant
https://api.flutter.dev/flutter/material/SelectableText-class.html

You might try using SelectableText and not Seo.text but last time I gave it a try it does hit quite on performance so I wouldn't advise to do it.

I try to search your web with bing & duckduckgo and they can find your page. but need specify text targeting.
https://duckduckgo.com/?va=v&t=ha&q=flutter+seo+green+papaya+salad+at+varius+vel+turpis&ia=web
https://www.bing.com/search?q=flutter+seo+green+papaya+salad+at+varius+vel+turpis&form=QBLH&sp=-1&lq=0&pq=flutter+seo+green+papaya+salad+at+varius+vel+turpis&sc=0-51&qs=n&sk=&cvid=E33494FFC5BF45E8A67F3B284D3CBF8B&ghsh=0&ghacc=0&ghpl=
on bing that's not on top but still in page one.
and can you try the meta seo library (https://pub.dev/packages/meta_seo)?
I think we can increase the score if we add metatag like decription & ogdescription.

hey @krokyze great package, brining SEO to Flutter web is like a dream.
Any ideia why it doesn't seem to work for all posts?
for example:
https://www.google.com/search?q=flutter+SEO+steak+tartare -> doesn't work
https://www.google.com/search?q=flutter+seo+green+papaya+salad -> works

hey @krokyze great package, bringing SEO to Flutter web is like a dream.
Any ideia why it doesn't seem to work for all posts? for example: https://www.google.com/search?q=flutter+SEO+steak+tartare -> doesn't work https://www.google.com/search?q=flutter+seo+green+papaya+salad -> works

Hey.
So the issue is that SEO will never know how to scroll a list in Flutter and as the "Steak Tartare" is at the bottom of the list it simply doesn't know about it. To overcome it I've tried adding https://seo.krokyze.dev/sitemap.xml which SEO should take into account and index each page but to be honest I'm not sure why it's ignoring it and haven't got time to try debugging it.

@krokyze thanks for replying, I thought about that, maybe didn't pick best example, let's say for example this one:
https://www.google.com/search?q=flutter+seo+chocolate+brownie which is the first post, also doesn't seem to work.
I'm trying to make sense of how this works as it works so well for post 3, but post 1 doesn't even show in google results, but I'm not SEO expert, don't even know if it's related to Flutter or if the same would happen with HTML website

@krokyze any updates on using sitemap.xml?
Also another way to let the bot know about all of the elements is to use Column inside a SingleChildScrollView instead of ListView.separated, because Column creates elements even if they are not currently in the visible part of the screen while ListView only renders those elements that are currently visible.
I understand that this might affect load time for the app which can also affect SEO score but if there are not a lot of elements or if they are fairly simple this might be a good approach.

@krokyze thanks for replying, I thought about that, maybe didn't pick best example, let's say for example this one:
https://www.google.com/search?q=flutter+seo+chocolate+brownie which is the first post, also doesn't seem to work.
I'm trying to make sense of how this works as it works so well for post 3, but post 1 doesn't even show in google results, but I'm not SEO expert, don't even know if it's related to Flutter or if the same would happen with HTML website

To be honest I'm no SEO expert too, but I do see the webpage in the results:

@krokyze any updates on using sitemap.xml?
Also another way to let the bot know about all of the elements is to use Column inside a SingleChildScrollView instead of ListView.separated, because Column creates elements even if they are not currently in the visible part of the screen while ListView only renders those elements that are currently visible. I understand that this might affect load time for the app which can also affect SEO score but if there are not a lot of elements or if they are fairly simple this might be a good approach.

I haven't had time to debug and try explore why GoogleBot does see the sitemap but haven't visited any of the posts.

Using Column, SingleChildScrollView I'm seeing as a hacky solution that might work for few but not for most so that's why I'm using ListView.separated.

@krokyze any updates on using sitemap.xml?
Also another way to let the bot know about all of the elements is to use Column inside a SingleChildScrollView instead of ListView.separated, because Column creates elements even if they are not currently in the visible part of the screen while ListView only renders those elements that are currently visible. I understand that this might affect load time for the app which can also affect SEO score but if there are not a lot of elements or if they are fairly simple this might be a good approach.

I haven't had time to debug and try explore why GoogleBot does see the sitemap but haven't visited any of the posts.
Using Column, SingleChildScrollView I'm seeing as a hacky solution that might work for few but not for most so that's why I'm using ListView.separated.

You are right, this is hacky, so the solution would probbably be to use sitemap somehow. As yourself I'm also not an expert for SEO, I just recently started learning about it. If you discover something usefull, please do share.

FYI looks like I've finally found the issue why Google didn't index most of the example pages. The issue was because of how Github Pages work and incorrect sitemap.xml. I'm guessing whole page will be indexed in few weeks.

hey @krokyze I used to dev with flutter, but searching for a SSR/SEO ready library to not go to react. Your library seems really interesting!
Btw, after a quick search, I would suppose that google is not taking into account your subpages as they are not reachable. Not because of the links that are enough, but maybe because of the container that is an flt-seo and not a standard div, section or else.
after crawling your website https://flutter-seo.netlify.app/posts with https://www.xml-sitemaps.com/ and other sitemap generators, all are not seeing your subpages. Is it because of that flt-seo or because of javascript execution requirements ?

Btw, after a quick search, I would suppose that google is not taking into account your subpages as they are not reachable. Not because of the links that are enough, but maybe because of the container that is an flt-seo and not a standard div, section or else.

Hey. Thanks for the tip, to be honest didn't knew Google would ignore them. Just did some reading and you might be true. Changed it to div now, let's see what Google says.

after crawling your website https://flutter-seo.netlify.app/posts with https://www.xml-sitemaps.com/ and other sitemap generators, all are not seeing your subpages. Is it because of that flt-seo or because of javascript execution requirements ?

Yep, you're correct.

After reading some articles about flutter and seo, I've discovered that hidden content would be banned by the indexers as the website is trying to display something to the indexer that isn't visible by a real user. It could be considered as "black hat technique"... "could", but not "will", as the user will still see the content through the flutter engine... Let's see how this will be considered

Hi, thanks for very promising package! From the conversation I am not sure if the indexing issue was eventually resolved or not. Were you able to index all the subpages or at least the visible ones?
Thanks

Hi, thanks for very promising package! From the conversation I am not sure if the indexing issue was eventually resolved or not. Were you able to index all the subpages or at least the visible ones? Thanks

Hey, I haven't really had the time to figure out why not all webpages are currently being indexed. The results seem quite random. For example, today it shows /, /posts, /posts/0, and /posts/32 as indexed.

When I resubmitted the sitemap.xml, it showed 64 pages as "Not indexed," but after a few days, the number randomly decreased.


[Event Hubs] Fix memory leak in EHBufferedProducerClient

Issue
First reported at https://github.com/Azure/azure-sdk-for-js/issues/25426, thanks to @pkraj0 for reporting the issue.
EventHubBufferedProducerClient leaks memory when there are no packets to send to event-hubs.
EventHubBufferedProducerClient

EventHubBufferedProducerClient is used to publish events to Event Hub
It does not publish events immediately. Instead, events are buffered so they can be efficiently batched and published when the batch is full or the maxWaitTimeInMs has elapsed with no new events enqueued.

Stress Testing
The test sends about 5000 events and stops for a long duration, revealing the memory blowing up.

Investigation
Studying the heap snapshots, and comparing them at various timestamps during the test run hinted at the issue.
The problem is at the BatchingPartitionChannel#_startPublishLoop and the AwaitableQueue#shift implementations.
BatchingPartitionChannel#_startPublishLoop

Starts the loop that creates batches and sends them to the Event Hub
Runs forever or until the abortSignal is invoked

AwaitableQueue#shift

Returns a Promise that will resolve with the next item in the queue.
If there are no items in the queue, the pending Promise stays forever.

Problem
BatchingPartitionChannel#_startPublishLoop relies on a while loop to run forever.

The root cause of the leak in the #_startPublishLoop is a race between two promises(AwaitableQueue#shift() and delay())
AwaitableQueue#shift() never settles because there is no activity.
Promise.race resolves as soon as one of the promises is fulfilled.
So these pending promises from AwaitableQueue#shift() keep accumulating because of the while loop causing the leak.

Solution
The fix is to abort the pending promises from AwaitableQueue#shift() once the race has been won by the other delay() promise.
What's in the PR?
@azure/core-util

Added a helper method racePromisesAndAbortLosers, an abstraction that leverages "Promise.race()" and aborts the losers of the race as soon as the first promise fulfills.
Changelog

@azure/event-hubs

Updated BatchingPartitionChannel#_startPublishLoop to use racePromisesAndAbortLosers instead of Promise.race.
Updated AwaitableQueue#shift() to return a promise that is cancellable so that the pending promise cancels once the first promise from Promise.race resolves .

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

So these pending promises from AwaitableQueue#shift() keep accumulating because of the while loop causing the leak.

In each loop iteration we only get the next one when there's an event; otherwise futureEvent is still the same one.  How could it cause the accumulation?
https://github.com/Azure/azure-sdk-for-js/blob/c1c67fab2360750aa2dbdca877dc2ede59d3a917/sdk/eventhub/event-hubs/src/batchingPartitionChannel.ts#L186-L188

In each loop iteration we only get the next one when there's an event; otherwise futureEvent is still the same one. How could it cause the accumulation?

I think because race creates a promise that it thens to all input promises, effectively creating a new promise for each input one. If one of the inputs doesn't settle, then all the promises created by thening to it will never settle.

I think because race creates a promise that it thens to all input promises, effectively creating a new promise for each input one. If one of the inputs doesn't settle, then all the promises created by thening to it will never settle.

Ah the new promise from race.  I think it settles when delay() resolved.  But perhaps the object is still kept alive by the futureEvent that has not resolved?

But perhaps the object is still kept alive by the futureEvent that has not resolved?

Yup, see this

found an issue related to this https://github.com/nodejs/node/issues/17469

In each loop iteration we only get the next one when there's an event; otherwise futureEvent is still the same one. How could it cause the accumulation?

When there is no activity, every time the delay resolves in the while loop (in promise.race), resolvers array grows with a new pending promise because of the AwaitableQueue#shift() call.
https://github.com/Azure/azure-sdk-for-js/blob/c1c67fab2360750aa2dbdca877dc2ede59d3a917/sdk/eventhub/event-hubs/src/impl/awaitableQueue.ts#L28-L34

/azp run js - event-hubs - tests

/azp run js - event-hubs - tests

/azp run js - event-hubs - tests


create input/output parameter category

There is a need for some parameters for a node to be both input and output parameters.  A web server, for example, may want to allow the port to be specified by the person deploying the web server, but clients of the web server will also need to know this port.  It would be possible to create two parameters: an input parameter (port-in) and an output parameter (port-out), but this is awkward.  Having a parameter that serves as both an input and output parameter makes clear how the parameter will be used without introducing unnecessary duplication.
As these parameters can also function as input parameters, they must be able to be modified when starting an application from the run dialog. (See slipstream/SlipStreamUI#402.)

I was thinking if it wouldn't make sense that all input parameters are directly also usable as output parameters, but this pointed me a simpler scenario where there are no input, output and input/output parameters, but only parameters, which might be editable on deployment. All parameters would then always be accessible as nodename.parametername.

What I do in that case is the following:
I create the parameter as an Input one and then I use ss-get --noblock input-param-name to retreive the value. If this is a password I generate a password and then I use ss-set -input-param-name password to update the parameter.
Since if a parameter is of type input or output change only it's visibility in the "Deploy ..." dialog (and in the Node of an Application) I would suggest to transform the dropdown menu Input/Output to a checkbox called for example editable to tell if the user can change it's value from the UI or not.


Failed test with images (runs in Markdown PHP 1.3 but not in Parsedown)

Hello. This is a small example of a little post with Images I've written which gets parsed OK when run in Markdown 1.3 (as shown in the demo page). When I try to parse it using Parsedown, the image references don't get rendered into the actual images:
Here is the link: http://pastie.org/pastes/8962289/text
(I've added it to pastie because when I try to write it here, github parses it and you can't see the original text.)

This is resolved now.


Sort settings.json on save

My proposal is to have a setting, which causes VSCode to sort the JSON entries of the currently edited settings.json file on save.
Detailed Breakdown

Enable by a boolean setting (checkbox)
Sort top-level JSON entries alphabetically by their keys in ascending order
Do this whenever a settings.json is saved (UI and direct JSON editing)

Further Ideas

Make a dropdown instead of a boolean setting which has the options "User", "Workspace", "Folder"
Add a second setting which determines whether this only happens on saving in the UI, "direct editing" or both.

Motivation
I think this feature would really improve the experience when editing the raw JSON.

I tried it but it didn't work. Also I want this to be automated rather than always executing a command.
This shou

@sofiabe1 and I plan to look into this

Correction: I meant ascending order instead of descending.

I came to report this same issue, I think it is good to keep common settings together

Does the "JSON: Sort Document" command in the command palette work for you?

It does for me, the formatting is changed,
Though I prefer if language specific settings "[html]" are kept at the bottom instead of moved to the beginning of the file, to give a sense of override

Hey @rzhao271, this issue might need further attention.
@evur, you can help us out by closing this issue if the problem no longer exists, or adding more information.

The richie5um2.vscode-sort-json extension could work, though I acknowledge that language-specific settings would end up stuck between uppercase and lowercase settings if the sort is case-sensitive, though.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Cannot run poxy on Ubuntu 24.04

Environment

Ubuntu 24.04
python 3.12.3
poxy 0.19.0

Describe the bug
poxy installs OK, but I cannot get it to run, with the error being: ModuleNotFoundError: No module named 'distutils'. I cannot find any successful way to install distutils on Ubuntu 24.04 - it seems it has been deprecated.
Am I doing something wrong, or does poxy need to be updated to remove a dependency on distutils?
Would really appreciate some pointers if I'm installing/running it incorrectly.
Additional information
I have successfully installed/run poxy on Ubuntu 20.04.
I tried replicating the setup that's working on 20.04 on 24.04:

Installed Miniconda
Set up conda virtual environment and ran pip install poxy
As far as I remember, this "just worked" on Ubuntu 20.04
I get the ModuleNotFoundError mentioned above on Ununtu 24.04

I tried creating a (non-Miniconda) python virtual environment (path at ~/.venv/docs):

~/.venv/docs/bin/pip install poxy works fine
Running ~/.venv/docs/bin/poxy results in the same ModuleNotFoundError.

Attempting to install distutils:
$ ~/.venv/docs/bin/pip install distutils
ERROR: Could not find a version that satisfies the requirement distutils (from versions: none)
ERROR: No matching distribution found for distutils

--bug-report

[ ] I have attached the zip file generated when using the --bug-report option
Not attached, I cannot get poxy to run to generate the bug report.

Am I doing something wrong, or does poxy need to be updated to remove a dependency on distutils?

Nope, you're not doing anything wrong. Looks like I need to do a pass over the dependencies. Thanks for letting me know :)

Looking into this now. Poxy uses setuptools+wheels for pypi packaging, and this issue suggests that having setuptools should satisfy that machinery. Can you try installing that instead?
Alternatively, it may be that some dependency I'm relying on transitively uses distutils, which would be a pain. I'd have to look into that.

Also, if there's a call stack accompanying the ModuleNotFoundError, please post it.

Also, if there's a call stack accompanying the ModuleNotFoundError, please post it.

Sorry, should have included that:
$ poxy
Traceback (most recent call last):
  File "/home/me/.local/bin/poxy", line 5, in <module>
    from poxy import main
  File "/home/me/.local/share/pipx/venvs/poxy/lib/python3.12/site-packages/poxy/__init__.py", line 7, in <module>
    from .main import main, main_blog_post
  File "/home/me/.local/share/pipx/venvs/poxy/lib/python3.12/site-packages/poxy/main.py", line 24, in <module>
    from .run import run
  File "/home/me/.local/share/pipx/venvs/poxy/lib/python3.12/site-packages/poxy/run.py", line 15, in <module>
    from distutils.dir_util import copy_tree
ModuleNotFoundError: No module named 'distutils'

Looking into this now. Poxy uses setuptools+wheels for pypi packaging, and this issue suggests that having setuptools should satisfy that machinery in python 3.12. Can you try installing that instead?
Alternatively, it may be that some dependency I'm relying on transitively uses distutils, which would be a pain. I'd have to look into that.

I have to say I'm a bit out of my depth with package management in python. However, I've attempted to install setuptools:
$ /home/me/.local/share/pipx/shared/bin/pip list
Package    Version
---------- -------
pip        24.3.1
setuptools 75.2.0

The result is still the same:
$ ~/.local/share/pipx/venvs/poxy/bin/poxy
Traceback (most recent call last):
  File "/home/me/.local/share/pipx/venvs/poxy/bin/poxy", line 5, in <module>
    from poxy import main
  File "/home/me/.local/share/pipx/venvs/poxy/lib/python3.12/site-packages/poxy/__init__.py", line 7, in <module>
    from .main import main, main_blog_post
  File "/home/me/.local/share/pipx/venvs/poxy/lib/python3.12/site-packages/poxy/main.py", line 24, in <module>
    from .run import run
  File "/home/me/.local/share/pipx/venvs/poxy/lib/python3.12/site-packages/poxy/run.py", line 15, in <module>
    from distutils.dir_util import copy_tree
ModuleNotFoundError: No module named 'distutils'

Ah! from distutils.dir_util import copy_tree is instructive. Looks like I'm using a version of copy_tree that's from the deprecated module, rather than using the one in shutil. Alrighty, that's easy fixed. I'll take care of that later today.

Should be fixed in 0.19.1. Thanks for the report 😄

Awesome - works fine now. Thanks for the quick turnaround.


CIP-0030 - Full API and wallet enumeration

I have suggestion regarding CIP-30. Right now it's confusing how to access Full API. It's accessible via window.cardano.{walletName}.getUtxos or window.cardano.getUtxos. If the second option is correct then I suggest to improve API to enumerate wallets becuase then wallet names mixes with API functions.

Ok, I just noticed that API is just returned by enable() method, so it's something like:
window.cardano.ccvault.enable().then(api => api.getUtxos())

I think that my confusion was caused by non-standard API of NamiWallet


Memory leak with parallel transcribe

Hey there, thank you for the project.
I have spotted a memory leak in the latest release (1.0.3). When transcribing sequentially, the memory behaves as expected. When however it is called in parallel, the memory usage keeps increasing until OOM, even if garbage collected manually.
I have built a minimal reproducible example. Notice also how "mem after gc" increases when you increase PARALLEL to 5 or 6.
wget "https://cdn.pixabay.com/download/audio/2024/07/23/audio_9f165cf892.mp3?filename=medieval-gamer-voice-donx27t-forget-to-subscribe-226581.mp3" -O test.mp3
import gc
from threading import Thread

from faster_whisper import WhisperModel
import psutil

PARALLEL = 4
THREADS = []
MODEL = WhisperModel('large-v2', device='auto', compute_type='int8', cpu_threads=4)

def get_rss():
    ''' Get current memory usage (RSS) in MB '''
    return int(psutil.Process().memory_info().rss / 1048576)

def transcribe():
    print(f'mem before {get_rss()}')
    segments, _info = MODEL.transcribe('test.mp3')
    _ = list(segments)
    print(f'mem after  {get_rss()}')

def sequential():
    print('sequential:')
    for _ in range(PARALLEL):
        transcribe()

def parallel():
    print('\nparallel:')
    for _ in range(PARALLEL):
        THREADS.append(Thread(target=transcribe))
        THREADS[-1].start()

def main():
    sequential()
    gc.collect()
    print(f'\nmem after gc {get_rss()}')
    parallel()

    for t in THREADS:
        t.join()

    gc.collect()
    print(f'\nmem after gc {get_rss()}')

if __name__ == '__main__':
    main()

Output:
sequential:
mem before 1761
mem after  2617
mem before 2617
mem after  2617
mem before 2617
mem after  2617
mem before 2617
mem after  2617

mem after gc 2617  # everything fine up until here

parallel:
mem before 2617
mem before 2617
mem before 2617
mem before 2617
mem after  2691
mem after  2691
mem after  2691
mem after  2691

mem after gc 2691  # leak

Edit:
There's another catch. When you run the same script multiple times, you will notice the outcome is very different sometimes for the final "mem after gc".
for run in {1..10}; do python test.py|tail -n1;done
mem after gc 2669
mem after gc 2670
mem after gc 2669
mem after gc 2671
mem after gc 2670
mem after gc 2670
mem after gc 4098  # !
mem after gc 2670
mem after gc 2669
mem after gc 2670

High Concurrency Exception


Fix a small typo in documentation

We are using oos instead of oss. Not a big deal tough as we are using the same wrong reference in the documentation. :)

@dadoonet when I saw the notification I thought it is some shitoberfest-like PR 😂


Investigate file upload definitions without request object

Some discovery documents do not specify a request type (e.g. Analytics).
 "response": {
  "$ref": "Upload"
 },
 "scopes": [
  "https://www.googleapis.com/auth/analytics",
  "https://www.googleapis.com/auth/analytics.edit"
 ],
 "supportsMediaUpload": true,
 "mediaUpload": {
  "accept": [
   "application/octet-stream"
  ],
  "maxSize": "1GB",
  "protocols": {
   "simple": {
    "multipart": true,
    "path": "/upload/analytics/v3/management/accounts/{accountId}/webproperties/{webPropertyId}/customDataSources/{customDataSourceId}/uploads"
   },
   "resumable": {
    "multipart": true,
    "path": "/resumable/upload/analytics/v3/management/accounts/{accountId}/webproperties/{webPropertyId}/customDataSources/{customDataSourceId}/uploads"
   }
  }
 }

It's not clear whether we should assume the request metadata should be the same as the response object ("Upload" in this case)

@chingor13, Can we update this to "type: process"?  This doesn't seem to be a use question.


Folder is locked when expand the folder in left hand side

Issues
If you expand a folder in File Manager using the left hand side
/ folder view area - the folder becomes locked so you can not rename the folder using Windows Explorer
The folder remains locked even if you change to look at another drive.
You have to exit File Manager in order to release the lock.
This locking behaviour doe not occur if you expand the folders in the right hand side (File list area) rather than the left hand side
Expected Behaviour / Change Request
I do not see a reason to lock the folder at all and at very least any folder locks should be released if you make the file least change to another drive
I might be wrong, but I do not recall this occuring with earlier versions of File Manager going back to Windows 3, NT, 2000 days
Please consider removing this folder lock - and preferabley other locks that occur in other situations
Environment
File Manager <IP_ADDRESS>
Windows 10

Odd! Can reproduce.

I think this is due to current directory handling:
00 00000089`2a442af0 00007ffa`7b73c5c4     ntdll!NtOpenFile
01 00000089`2a442af0 00007ffa`7b73c1c4     ntdll!RtlpCreateNewDirectoryReference+0x8c
02 00000089`2a442b90 00007ffa`773a8be8     ntdll!RtlSetCurrentDirectory_U+0xf4
03 00000089`2a442bf0 00007ff6`2fdece54     KERNELBASE!SetCurrentDirectoryW+0x28
04 00000089`2a442c10 00007ff6`2fd82ab4     Winfile!SetWindowDirectory+0x64 [c:\src\github\microsoft\winfile\src\wfutil.c @ 1082]
05 00000089`2a443c60 00007ff6`2fd7f280     Winfile!OpenOrEditSelection+0xc4 [c:\src\github\microsoft\winfile\src\wfcomman.c @ 630]
06 00000089`2a445540 00007ff6`2fdf2d44     Winfile!AppCommandProc+0x7d0 [c:\src\github\microsoft\winfile\src\wfcomman.c @ 964]
07 00000089`2a44b630 00007ffa`78271504     Winfile!FrameWndProc+0x11f4 [c:\src\github\microsoft\winfile\src\winfile.c @ 1031]

I see the same behavior on WinFile on NT 3.1.
Current directories in Windows are a bit of a frustrating mess.  The system allows a file open relative to an existing file handle when opening down the tree, but opening up the tree requires parsing strings.  That means each process current directory consists of a handle (used to open foo) and a path (used to open ..\foo.)  That in turn means that if a process has a current directory, it is not tolerant to that directory being renamed, or its path will become stale.  So, current directory handles are opened without FILE_SHARE_DELETE, ensuring that the string path is in sync with the handle, which creates the behavior here.
I haven't looked into what it would take to avoid changing current directories.  It is possible to construct fully qualified paths and always operate on them, avoiding the need to tell Win32 about any current directory.  Doing that implies firstly finding all of the code paths that aren't using fully qualified paths, then updating them to be fully qualified.


Add flag to prevent "dist" folder from being deleted during ng build

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x ] feature request

Versions.
@angular/cli: 1.0.0
node: 6.10.2
Same result as below for Windows or OSX
Repro steps.
I'm hooking up a Docker nginx container to the "dist" folder through a volume with the following command. Note that $(pwd) would represent the dist folder in this case (the working folder):
docker run -d -p 8080:80 -v $(pwd):/usr/share/nginx/html nginx:alpine
Hitting http://localhost:8080 works fine and the CLI sample app code/bundles in the dist folder work fine and are displayed in the browser.
However, if I run ng build again the dist folder seems to be deleted which then breaks the Docker container volume (since the original host folder that the container volume pointed to is now changed) and nginx will give a 404. I've sh'd into the nginx container and verified that the "html" folder isn't found (which means the "dist" folder isn't found probably due to the volume link breaking - that's what I suspect anyway). For devs wanting to work with "real" servers (nginx, Apache, HAproxy, etc.) to do updates to the CLI generated source code via Docker containers and volumes this presents a challenge.
The log given by the failure.
No failure in the CLI. The failure occurs with the Docker volume created between the nginx container and the dist folder on the host machine. Deleting the dist folder seems to be breaking the docker container volume link.
Desired functionality.
It would be nice to either leave the dist folder there and only delete the contents when performing a new "ng build" or to provide a flag that would allow us to leave the dist folder there for this type of scenario.
Mention any other details that might be useful.
Repo that runs this scenario plus several other containers can be found at https://github.com/DanWahlin/Angular-Docker-Microservices.
If you perform the steps listed in the readme it should fire up fine the first time. But, if you run an ng build again, the dist folder is deleted which seems to break the Docker volume link and nginx will then give a 404 since the original host folder was removed (at least I think that's why it's breaking).

Could we just have a flag for overwrite dist content and a proxy for live reload?

Wow ~ this ticket is describing exactly what I was going through the other day ! xD
I would second the motion of not deleting the dist and delete only its content or adding a flag to not delete it, and just overwrite since it makes adding volumes directly to it a lot trickier..

+1

I didn't get the message that the --delete-output-path flag was added for this scenario....thanks! Appreciate it.


About game stuttering after use

I obviously felt that the game was stuttering using the modifier, and it wasn't very obvious that one card after another, I don't know if you guys are the same

Thanks for the answer


Font names interpretation is changed in Scintilla v3.5.3

Till Scintilla v3.5.2, font names are interpreted as multi byte.
But, in v3.5.3, it was changed to UTF-8.
Therefore, Styles.c should be changed.
void Style_SetStyles(HWND hwnd,int iStyle,LPCWSTR lpszStyle)
{
   ... bla bla ...
  WideCharToMultiByte(CP_ACP,0,tch,-1,mch,COUNTOF(mch),NULL,NULL);

that line(4034) should be change to
  WideCharToMultiByte(CP_UTF8, 0, tch, -1, mch, COUNTOF(mch), NULL, NULL);

That is unrelated to Scintilla as far as I can tell.

No. It's definitly Scintilla related issue.
You'd better read following issues.
https://sourceforge.net/p/scintilla/bugs/1684/
https://groups.google.com/forum/#!topic/scintilla-interest/ti3PE4LDMNs/discussion

Well, I don't need to read anything. You can make a PR and provide proof that the current way fails and what the PR fixes.

Neil Hodgson wrote "This is likely due to a change in the interpretation of font names. Font names must now be in UTF-8.", not me.
And, current notepad2-mod store font name as ANSI.
Upper code changes from ANSI to UTF-8 in that part.

<IP_ADDRESS>0: font "맑은 Envy 고딕" is selected. But, system default font is shown.
(It's Korean font)

fixed ont: "맑은 Envy 고딕" is selected and shown.

But in both of your screenshots the selected font seems the same to me.
Anyway, please make a PR. I know there were some relevant changes in that Scintilla part, but from my tests things work fine on my machines. And your screenshots look fine; remember I don't speak Korean so they look fine at least.


dt with homemenu pause

So dt is calculated using os.time or whatever. When you use the home menu to pause out, dt is done properly. As in dt = 5 when you homemenu, you wait five seconds and then you go back to the game, dt = 10 now since it's using the OS time. I mean obviously this is expected by nature, but is it intended? I feel like there are situations where this might be wanted or unwanted. If it's intended, then I should make my own dt, say gt (gameTime). And have it go in the update like
if dt > .1 then   gt = gt + .1   dt = 0 end
Or is it unintended, and I shouldn't mess with my code lol. It's not a big deal, it just caused some funny bugs lol.

Mostly a design flaw, we didn't have to worry about that because LovePotion was 3dsx only not that long ago :P Should be a simple fix though

I kinda figured. But honestly in some cases that effect might be desired. I think I'll go ahead and modify my game code, unless your hard set on fixing it lol.


Placeholder Text Gets Truncated When Using Japanese Characters

Hello,
I've encountered an issue when setting the placeholder text in Japanese (e.g., "エリアを選択してください") using choices.js. The generated input element looks like this:
<input type="search" class="choices__input choices__input--cloned" autocomplete="off" autocapitalize="off" spellcheck="false" role="textbox" aria-autocomplete="list" aria-label="エリアを選択してください" placeholder="エリアを選択してください" style="min-width: 13ch; width: 1ch;">

The problem is that the min-width is set to 13ch, which causes the placeholder text to be truncated. It would be helpful if there was an option to set the width of the input[type=search] or to customize it in some way.
I'm not entirely sure how this is implemented, and I would appreciate any assistance or guidance on how to address this issue.
Thank you for your help!

"エリアを選択してください".length returns a length of 12 characters, and the ch unit assumes non-variable width fonts which is probably what is wrong.
Monkey patching instance.input.setWidth may be the best solution.
The original definition is this;
  setWidth(): void {
    // Resize input to contents or placeholder
    const { element } = this;
    element.style.minWidth = `${element.placeholder.length + 1}ch`;
    element.style.width = `${element.value.length + 1}ch`;
  }


Azure RedHat OpenShift 2022-09-04

Clone of #20463. I'm opening this PR because the Red Hat employee whose branch #20463 is based on is leaving.
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow. Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ]  new service onboarding
[x]  new API version
[ ]  update existing version for new feature
[ ]  update existing version to fix swagger quality issue in s360
[ ]  Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
September 7th

When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
September 20th

By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x]  I commit to follow the Breaking Change Policy of "no breaking changes"
[x]  I have reviewed the documentation for the workflow.
[ ]  Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: warning
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x]  Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service

Adding new API(s)

Adding a new API version

[x]  To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x]  Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x]  If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@leni-msft @raosuhas @rkmanda - I have to move this request to a new PR. Ross-bryan is leaving Red Hat so we can't continue using his branch.

@msyyc I'm not sure if you are seeing my responses, I cannot remove the ARMChangesRequested tag myself.

@msyyc I'm not sure if you are seeing my responses, I cannot remove the ARMChangesRequested tag myself.

Python pipeline has passed now. And you can ping assignee for other items.

@zizw123 can I get a response on this please? Note that I don't have permissions to remove ARMChangesRequested.

@zizw123 I have removed the 201 Created responses from the new resources: MachinePool, Secret, SyncIdentityProvider, and SyncSet. The one you commented on, OpenShiftCluster previously existed so would need a breaking change which we don't want to do in this version.

Hi @tianxchen-ms can I get this merged please? Once that happens, how long do you estimate it will take before this API is released. Can we test it through ARM before the full release? Thank you.

Hi @ventifus please fix ModelValidation error, and deploy the service before merged

@tianxchen-ms I have fixed the ModelValidation error.
Is it required to deploy the new API in our RP before this is merged? Can we deploy to canary or do we have to roll out to all global regions? What about the sovereign clouds?

@tianxchen-ms Tianxiang Chen FTE I have fixed the ModelValidation error.
Is it required to deploy the new API in our RP before this is merged? Can we deploy to canary or do we have to roll out to all global regions? What about the sovereign clouds?

Yes, the process is Swagger review -> ARM Sign-off -> Service development/rollout -> Swagger merge. Once merged, customer can access service by swagger, so you need to deploy at least canary.
//CC: @josefree

@tianxchen-ms We have deployed our service to Canary. We are ready to move ahead.

@ventifus please fix the conflict

@tianxchen-ms conflict fixed

@ventifus It seems there are new LintDiff errors, you need to fix them. And the tool didn't detect the deployment, could you tell me which region is deployed?

@tianxchen-ms we have deployed to eastus2euap, centraluseuap, westcentral, australiacentral, australiacentral2, australiaeast, australiasouth, centralindia, eastasia, southindia, japaneast, japanwest and koreacentral.
Seriously, when did ResourceNameRestriction make it into production lintdiff checks??? We spent weeks already trying to comply with that one and determined that it required a breaking change. We contacted the breaking change board and were advised to disregard that check. Please see PR history on that. We don't want any breaking changes at this time, please advise.

/azp run

@tianxchen-ms my team decided to implement the swagger pattern restrictions on new resources in order to avoid lint issues in the future. We are rolling out US sector regions right now, hopefully that will allow the readiness check to pass.

/azp run

/azp run

@ventifus I tested locally but failed to access. I found that you may forget to check in manifest, so tool cannot access service from ARM.

/azp run

/azp run

/azp run

Hi @tianxchen-ms we finally have ARM manifest rollout and checks are passing. We should be good for merging! Thank you.

/azp run


Decim invalid IV size

Hi!
My tests failed for Decim due to "Invalid IV length" error. IV is 16B by default, can it be changed somehow?
Thanks.
{
  "notes": "Configuration generated by poly-verif-egen",
  "seed": "1fe40505e131963c",
  "function_name": "DECIM",
  "stream_type": 1,
  "tv-size": 16,
  "tv-count": 65536,
  "stdout": true,
  "stream": {
    "type": "estream",
    "type_code": 1,
    "generator": "pcg32",
    "algorithm": "DECIM",
    "round": 6,
    "block-size": 16,
    "gen_inp": {
      "type": "false-stream",
      "scode": "0"
    },
    "gen_key": {
      "type": "hw_counter",
      "hw": 4,
      "scode": "hw4",
      "increase_hw": false,
      "randomize_start": false
    },
    "scode_inp": "0",
    "scode_key": "hw4",
    "scode_init": "e",
    "scode": "tpestream-aDECIM-r6-tv16-in0-khw4-rie",
    "init-frequency": "every-vector",
    "key-size": 16,
    "plaintext-type": {
      "type": "false-stream",
      "scode": "0"
    },
    "key-type": {
      "type": "hw_counter",
      "hw": 4,
      "scode": "hw4",
      "increase_hw": false,
      "randomize_start": false
    },
    "iv-type": {
      "type": "false-stream",
      "scode": "0"
    }
  }
}

Edit also wiki after merging PR.
https://github.com/crocs-muni/eacirc-streams/wiki/Project-eStream-(configuration)

https://github.com/crocs-muni/eacirc-streams/pull/28
Sorry, but you merged it before I fixed the typo...


Allow variables for certificate validity period

Though unlikely a cluster would not be upgraded within a year, I would like the option of setting certificate validity to something higher.
I am willing to provide a pull request if it is something you are willing to accept.

I wouldn't want to bubble this option up to Typhoon, so I'm going to pass. For those that are really motivated to set a longer expiration, having to fork and make the tweak is just enough of a little hurdle that it makes it clear they're deviating from good practice.
In future we'll be switching to rotating certs anyway.


With Nightly 2023.1.1-nightly.2023.2.1 the Restaurant example is not working

This task is automatically imported from the old Task Issue Board and it was originally created by Sylwia Brodacka.
Original issue is here.

There is a warning about EOF and no results shows
Comments:
(Sylwia Brodacka - Feb 1, 2023)

Caused by new API changes. (James Dunkerley - Feb 1, 2023)

**James Dunkerley** reports a new **STANDUP** for today (2023-02-01):
Progress: Repaired all examples except NASDAQReturns (will examine issue in the morning). Attempting to get video recording for PreppinData blog post. Backlog sorting. It should be finished by 2023-02-02.
Next Day: Next day I will be working on the #184369225 task. Resolve issue with NASDAQReturns. Demo. More Backlog and then onto DB/InMemory differences. (Enso Bot - Feb 1, 2023)

**James Dunkerley** reports a new **STANDUP** for today (2023-02-02):
Progress: Fixed the NASDAQReturns. Design session and planning on the dropdowns with Pawel - agreed plan on what to do next. More work on the tickets on Pivotal. It should be finished by 2023-02-02.
Next Day: Next day I will be working on the #184369225 task. Blog post, interview,  finish the pivotal ticket tidy. (Enso Bot - Feb 2, 2023)

Commits on https://github.com/enso-org/project-templates/

https://github.com/enso-org/project-templates/commit/16b49c44a5053e426630513a7d9181c3ae6affe3
https://github.com/enso-org/project-templates/commit/3cfcbe18ef77395e368477dd4f102a58d0e73424


Adjust registration and session links in navbar

Please comment if you'd like to be assigned, and let us know if you have any questions.
Description
These are two small, separate tasks involving links in the navbar. Please fix both of these in 1 PR.

The mobile navbar log out button displays regardless of the users session. This should only display if a user is signed in. However, it currently shows regardless of signed in status.
Users have to click the log in link or scroll to the bottom of the homepage to get to the sign up link. We want to add a link next to the log in link so that users can quickly sign up.

Acceptance criteria
Mobile navbar log out button

[ ] Log out is not displayed in the mobile hamburger menu when signed out (see exhibit 1)
[ ] Log out is displayed in the mobile hamburger menu when signed in

Sign up link on home page

[ ] Sign up link displays to the left of the log in link on home page navbar

[ ] On desktop (see exhibit 2)
[ ] On mobile (see exhibit 3)

[ ] Style of Sign up link matches Log in link
[ ] Sign up link does not display when user is logged in

Exhibit 1:

Exhibit 2:

Exhibit 3:

Hi @mononoken, Can I work on this?


Add special case for matching empty strings

Fixes #313
Adds tests for fix

Coverage increased (+0.05%) to 40.082% when pulling 8b0d7e08ccf3647bd30f8a8fd0898fc7195bb3a8 on zaowen:dolladollachills into e88fd99b3e1b9e1a70e4b844f55aeebf06cff235 on newsboat:master.


Display volume on digitized work detail page

ref #296

Codecov Report

Merging #469 (1ea3851) into develop (4937de8) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop     #469   +/-   ##
========================================
  Coverage    98.99%   98.99%
========================================
  Files          113      113
  Lines         5961     5968    +7
  Branches         8        8
========================================
+ Hits          5901     5908    +7
  Misses          60       60


Schema based validation part 1

MIssing:

[ ] docs
[ ] functional examples
[ ] runtime type check
[ ] experiment with using the schema as inversed object

from dataclasses import dataclass
from typing import List

from dynaconf import Dynaconf
from dynaconf import ExtraFields
from dynaconf import Field
from dynaconf import Schema
from dynaconf import Validator

"""
settings.json
{
    "random_thing": True,
    "ignored_from_json": True,
}
"""

email_expr = "(this.name + '@' + this.company + env.TLD) | lower"

@dataclass
class MySchema(Schema):
    city: str
    schema: int
    a_thing: List = Field(default_factory=list)
    random_thing: bool = False  # will come from settings.json
    computed: int = Field(default_factory=lambda: 40 + 2)
    name_upper: str = Field(default_expr="this.name.upper()")
    name_reversed: str = Field(default_expr="this.name | reverse")
    company: str = "Acme"
    email: str = Field(default_expr=email_expr, force_default=True)
    name: str = Field(
        validators=["this.name != 'Bruno' and env.IS_FOO == 'this_is_foo'"]
    )
    age: int = Field(18, validators=[Validator(gt=1, lt=16)])
    banana: str = Field(validators=[lambda this: this.city == "Rio"])

    class Config:
        extra_fields_policy = ExtraFields.ignore

settings = Dynaconf(
    settings_file="settings.json",
    envvar_prefix="DYNACONF_",
    environments=False,
    load_dotenv=False,
    name="Bruno2",
    city="Rio",
    banana=1,
    age=15,
    schema=1,
    abcd=10,  # this will be ignored, because it's not in the schema
    dynaconf_schema=MySchema,
    random_thing=False,  # Json wins
)

assert settings.name == "Bruno2"
assert "NAME" in settings
assert "name" in settings
assert settings.name_upper == "BRUNO2"
assert settings.name_reversed == "2onurB"
assert settings.company == "Acme"
assert settings.email ==<EMAIL_ADDRESS>assert settings.age == 15
assert settings.computed == 42
assert settings.random_thing is True

assert settings.load_dotenv_for_dynaconf is False

assert "ABCD" not in settings, settings.ABCD
assert "IGNORED" not in settings, settings.IGNORED
assert "IGNORED_FROM_JSON" not in settings, settings.IGNORED_FROM_JSON

replaced by #1107


Email notify on receiving payments to project

Just an idea, didnt find any other issue that mentions this.
Could be handy to have an email sent to account owner when another user supports/backs one of their projects. Also maybe include a summary of total no of users supporting the project with received information, like estimated payment totals as well prehaps.
Thanks.

I think this is useful for the first tip, and then maybe the 10th, 100th etc. The email could also include an explanation saying that tips are anonymous, so we can't reveal who the giver is.
Notifying on every single new tip... borderline spam IMO.

Could also send weekly summaries: https://github.com/gratipay/gratipay.com/issues/1022. Should we fold this into that?

Seeing the +1 from the OP on folding into #1022, reticketing this there.


Lexical toolbar z-index problem

Describe the Bug
When a select field is above the lexical editor, the lexical editor is partially hidden. This is true for 116.
Link to the code that reproduces this issue
No
Reproduction Steps
Create a select field with at least two options to pick from, above the lexical editor, and try to select one of those options.
Which area(s) are affected? (Select all that apply)
Not sure
Environment Info
116

Hey @stuckinsnow,
I believe this is a duplicate of #8728 which has a PR up by Ritsu.


[BUG]Sending messages from MME MIDI app to midi monitor causes Green Screen on the USB MIDI 2.0 driver and loopback device

Describe the bug
Sending messages from MME MIDI app to midi monitor causes Green Screen on the USB MIDI 2.0 driver and loopback device
This issue only occurs if the device is running with the USB MIDI 2.0 driver (UsbMidi2.sys) and loopback device (e.g. ProtoZOA)
To Reproduce

Load the attached firmware to the ProtoZOA.
Make sure the USB MIDI 2.0 driver (UsbMidi2.sys) is loaded.
Open midi.exe and monitor the ProtoZOA.
Open the Pocket MIDI 64bit(MME MIDI app) and choose MidiSrv enumerated ports for Output.
Output: ZOA-104 (iIF AC) O-1

From the "Views" menu, open "System Exclusive" window.
In the System Exclusive window, open the attached test data set, then, System Exclusive window shows sending data.

Click "Transmit" to send messages.

In the few seconds after starting data transmission, then Green Screen occurs.

Green screen shows "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED".
Expected behavior
No Green Screen.
Installer Name or Version
Windows.MIDI.Services.In-Box.Service.-.1.0.1-preview.7.24305.1438-x64.exe
Desktop (please complete the following information):

OS: Windows 11 24H2 build 26120.2222 (Insider Dev channel)

Device information, if this is with an external MIDI device:

ProtoZOA running with the attached firmware.
UUT_ZOA_104.zip

USB MIDI 2.0 class driver (USBMIDI2_<IP_ADDRESS>.x64.zip)

Application Information
MORSON Pocket MIDI (64bit MME MIDI app)
https://www.morson.jp/pocketmidi-webpage/

Tested this with a UMP USB device that loops the USB packet internally (not via MIDI DIN)
https://github.com/user-attachments/assets/6d48ed0d-5cff-4599-934d-6d61a96ce94d

I used Pocket MIDI and just was sending some pitchben message , then the app crashed the service too it seems
https://github.com/user-attachments/assets/287d04c3-aaf2-4ef7-ab6c-8ed8577161f2

This issue also appears to be a problem in USB MIDI 2 driver


nimble/bt5_scanner

This is not ready to MERGE. Still under tests, however, it is good to get comments on this.
Especially build flags are not yet sort out so it might not build is some configurations.

I am done reviewing the controller changes. Everything other than what I commented on looks good.

Thanks Will!

I only looked at the changes to the host; they look good to me.  All I saw was a few function renames (inserting "_cmd" into some function names), so please let me know if I missed something.

Chris, I overwrote previous pull request which contained host part with this one which contains only controller part. I did it because Szymon needs this patches to put his advertiser on top. Once that got merged I will create new pull with host part.

Changes look good.


Data preprocessing issues

Hello, I encounter the submitit.core.utils.UncompletedJobError: Job not requeued because: timed-out and not checkpointable. error when running the convert_h5_to_jpg.py code. How can I resolve this issue?

Hi @Lzl626,
Sorry for the late answer. The job requires more time. Try to increase the time limit parameter within submitit.


Page content list incomplete

Describe the issue
The list of sections (right side bar) of the page "https://docs.stacks.co/docs/build-apps/references/bns" is missing BNS and DID Standards.
Screenshots

confirmed. @kenrogers can you take a look here?

This issue is still important to me

Will take a look at this tomorrow and get it fixed.

This has been fixed with https://github.com/stacks-network/docs/commit/836e2815ebec55b754b947f7ee4f1d8de326e44d