[rom/e2e] fix boot_data_recovery exit_failure matching

Similar to boot_policy_rollback and boot_policy_bad_manifest, this also requires tweaks to exit_failure message so that it's not matched before exit_success message.
This is a fallout of #20592

Can you please trigger a nightly job before merging?

https://dev.azure.com/lowrisc/opentitan/_build/results?buildId=139649&view=results

Kokoro failed, but I'm merging anyway since this PR does not change RTL.


Initial pass at using Google Cloud Storage instead of cassandra.

@duftler, @ajordens
This doesnt have tests yet, but seems to work when I run it.
I'm not sure how to port the test because it is a live test (not a mock) so needs credentials to run.
Adam,
I'd like to refactor this to remove a lot of the copy/paste stuff.
I'm thinking about changinging the Support class to a templated base class, removing the actual storage mechanism from it, and injecting that back in with an interface. If that's possible, then it will concentrate the mechanism in one place and clarify what it needs to do and will make the behavior stuff more consistent and less brittle across different implementations. I'd move the feature implementation classes into front50-core (?) but and just keep the mechanism class and config class in the front50- components.
Does that make sense? I could do that after this PR.

Out of curiosity, did you try using an AmazonS3Client as is and just replace the endpoint URL and authentication keys?
In test cases using s3proxy, I did the following:
// See `S3ApplicationDAOSpec` and `S3TestHelper.s3ProxyUnavailable()`.
// I couldn't find a way to programatically spin up the s3proxy so these tests only run if someone first starts the proxy
def amazonS3 = new AmazonS3Client(new ClientConfiguration())
amazonS3.setEndpoint("http://<IP_ADDRESS>:9999")

As for authentication, you should be able to supply the GCS access and secret keys in lieu of the AWS access and secret equivalents. Not sure if the oauth2 credentials you're using in here are compatible.
FWIW S3Support initially started out as a wrapper around the periodic refresh behavior. This was necessary primarily because S3 was slow to return the contents of buckets with ~2k things in them. It's specifically optimized to make as few calls as possible to S3.
Maybe GCS isn't and the complexity of refreshing a cache would not be worth it.

On Sat, May 14, 2016 at 11:36 AM, Adam Jordens<EMAIL_ADDRESS>wrote:

Out of curiosity, did you try using an AmazonS3Client as is and just
replace the endpoint URL and authentication keys?
In test cases using s3proxy https://github.com/andrewgaul/s3proxy, I
did the following:

Interesting, but I dont understand how to use it. The docs talk about the
endpoint in terms of a host and port, not a base URL (GCS is
https://www.googleapis.com/storage/v1) Credentials are key/secret but we
use service accounts, which I think are a bit different.
And looking it over, isnt clear whether this works or is an interface I
need to implement. The GCS docs suggest that I can send S3 requests and
just use google credentials. But looking at the AWS java API has the same
issues; It isnt clear where or how to change the endpoint and credentials
dont seem to support our service accounts. I could be wrong, but that's my
impression looking at it. I'll ask around.

// I couldn't find a way to programatically spin up the s3proxy so these tests only run if someone first starts the proxy
def amazonS3 = new AmazonS3Client(new ClientConfiguration())
amazonS3.setEndpoint("http://<IP_ADDRESS>:9999")
As for authentication, you should
https://cloud.google.com/storage/docs/migrating#authentication be able
to supply the GCS access and secret keys in lieu of the AWS access and
secret equivalents. Not sure if the oauth2 credentials you're using in
here are compatible.
FWIW S3Support initially started out as a wrapper around the periodic
refresh behavior. This was necessary primarily because S3 was slow to
return the contents of buckets with ~2k things in them. It's specifically
optimized to make as few calls as possible to S3.
Maybe GCS isn't and the complexity of refreshing a cache would not be
worth it.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/spinnaker/front50/pull/90#issuecomment-219226740

def amazonS3 = new AmazonS3Client(new BasicAWSCredentials("ACCESS_KEY", "SECRET_KEY"), new ClientConfiguration())
amazonS3.setEndpoint("http://<IP_ADDRESS>:9999")

It still might not support a service account ... but sure would be nice if you could get credentials dedicated to it and try and use as-is ... without refactoring.


Updated metabase version due to security issue

https://discourse.metabase.com/t/log4j-zero-day-on-metabase/17915

Glad to see that critical CVE has been patched in Metabase 👍


Allow to disable proxy discovery in go client without magic

For now the only way to disable proxy discovery in go is to add numbers to your DNS record: https://github.com/ytsaurus/ytsaurus/blob/main/yt/go/yt/config.go#L261-L263
func NormalizeProxyURL(proxy string, tvmOnly bool, tvmOnlyPort int) ClusterURL {
// ...

	if strings.ContainsAny(proxy, "0123456789") {
		url.DisableDiscovery = true
	}
// ...

I had to patch /etc/hosts to get go mapreduce client working.
Also current behavior is very non-obvious. If you suddenly have numbers in DNS records, everything works for you through the balancer, even if you wanted to work with proxies directly.

Fixed in 54b321acfdc2948c97e07ddc88660123045b6937


[systemd] failed to get d-bus session:

output from zabbix agent
[systemd] failed to get d-bus session: Failed to connect to socket /run/dbus/system_bus_socket: Permission denied

Please provide agent logs - https://github.com/cavaliercoder/zabbix-module-systemd#debugging
and your SELinux configuration - https://github.com/cavaliercoder/zabbix-module-systemd#selinux.

I disabled SELinux and then got processes in zabbix, only for 6 services getting exclamation mark (Cannot open cpuacct.stat file/Cannot open memory.stat file) under monitor-latest data
[```
systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/irqbalance.service/memory.stat'
14852:20180821:220840.725 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/kdump.service/cpuacct.stat'
14853:20180821:220844.007 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/irqbalance.service/cpuacct.stat'
14853:20180821:220851.309 [systemd] cannot open metric file<EMAIL_ADDRESS>14852:20180821:221802.714 [systemd] cannot open metric file<EMAIL_ADDRESS>14853:20180821:221810.083 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/kdump.service/cpuacct.stat'
14854:20180821:221814.101 [systemd] cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/system.slice/irqbalance.service/cpuacct.stat'
14854:20180821:221821.358 [systemd] cannot open metric file<EMAIL_ADDRESS>14852:20180821:221829.482 [systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/kdump.service/memory.stat'
14854:20180821:221833.588 [systemd] cannot open metric file: '/sys/fs/cgroup/memory/system.slice/irqbalance.service/memory.stat'

See: https://github.com/cavaliercoder/zabbix-module-systemd/issues/12

sorry, don't follow, all above files doesn't exist on my system, not sure what should i do to get rid of above message-to disable those items ?

See https://github.com/cavaliercoder/zabbix-module-systemd/issues/12 => that's already reported issue. If you want to resolve it, then you need to.make your hand dirty, because this issue is still not resolved => you will need to code it or wait for resolution provided by someone else.

ok, thanks,last question:
in systems where SELinux is ON
how to add exception to get rid of
[systemd] failed to get d-bus session: Failed to connect to socket /run/dbus/system_bus_socket: Permission denied

stupid me, sorry didn't see SELinux link, will try and open new issue if face errors, thanks a lot for this template !!


Update Footer component files

@itsnitinr - this PR fixes #26 - with these changes the social media icons are displaying correctly in Chrome with ad-blockers on. Feel free to review and merge if you feel fit. Thank you for reviewing over my PR! 😃

Sorry! I tried submitting a separate pull request for some minor UI changes to the landing page and somehow it added into my footer PR. I'm still very new at this so I might be doing something incorrectly. Again, sorry for any mistakes!

Sorry! I tried submitting a separate pull request for some minor UI changes to the landing page and somehow it added into my footer PR. I'm still very new at this so I might be doing something incorrectly. Again, sorry for any mistakes!

I looked into it further and found that I should have been updating on different branches. Learned something new! Please let me know if I should go back and modify anything. Thank you!


 However, it is not.

 However, it is not.
This happened after I updated the certificates, and the SSL settings of the web server
www.ssllabs.com shows that my server has an A + rating
:link:

https://img.shields.io/website-up-down-green-red/https/dorokhin.moscow.svg?label=dorokhin.moscow
ssllabs report
** Screenshots **
Screenshot 1
Screenshot 1
:bulb: Possible Solution
Update your ssl client library.

How to fix:

Site .htaccess is https://github.com/BhadooMail/BhadooMail/blob/master/.htaccess
at AWS with SSL Rating A at ssllabs.com

or u can add
require("tls").DEFAULT_ECDH_CURVE = "auto"
to server.js

Check this https://site-status-php.herokuapp.com/?q=amazon.in or https://site-status-php.herokuapp.com/?q=amazon.com all shows down.
while https://site-status-php.herokuapp.com/?q=aws.amazon.com shows fine.

@dorokhin: how did u solve your problem?

@dorokhin: how did u solve your problem?

try my comment with server.js

it works with self-hosted version. but the shield.io version always shows down.

The production servers are now running Node 10.20.1 so this should be resolved.
Can anyone confirm?

I can't confirm this is fixed but I'm going to close it. If this isn't fixed, feel free to comment here and we'll reopen.

nice, it works for my page now :)

I can't confirm this is fixed but I'm going to close it. If this isn't fixed, feel free to comment here and we'll reopen.

it works!

Not working for Cloud flare Site
https://site-status.hashapp.ga/?q=big.driveindex.ga

Hi! Could you open a new issue, please?


Enable Undocked Regfree WinRT to work on Win8.1 and Win7

The detours library that enables undocked regfree winrt could in theory work down to Win7 - take a closer look to see if this is possible - for both Win8.1 and Win7.
Win8.1 currently errors with Error 0x8007109A – This operation is only valid in the context of an app container.
Win7 fails to load the component - possibly due to api set issues.

Windows 8.1
0x8007109A error is caused by the app container check that exists in windows 8.1 but not on later versions.
This can be fixed by, setting the linker option of your component that you're activating to /APPCONTAINER:NO
https://docs.microsoft.com/en-us/cpp/build/reference/appcontainer-windows-store-app?view=vs-2019
https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/windows-app-certification-kit-tests#appcontainercheck
Windows 7
Because the RoAPIs are missing on windows 7 and the project is based on detouring, it does not seem worthwhile to design a whole new version of the project just for win7 once you take into account that there is no customer demand for win7 support.


Thread Safety

Is the Parser thread-safe?
Can I build the parser into a static var and use it to parse inputs in different concurrent threads?
If not, is there any way to reduce the performance hit of having to build the parser (asking because I will be using it to parse data coming from request to a web API) ?

Yes it is thread safe. You should use it as you want. I solved Théâtre last thread safety issues a deux month ago search in closes issues.

to be complete here is the last issue  about thread safety https://github.com/b3b00/csly/issues/155
and the commit that fixed it : https://github.com/b3b00/csly/commit/0ec386a09dcaecae675079c75ac2afd945fc6227
I think your use case is fine as long as your syntax tree visitor is thead safe too.


Extension non compatible with magento 2.1.2

Cannot upgrade to 2.1.2 because of module requirements.

@sergy-gzh If you're willing to test this on Magento 2.1.x and confirm it still works, I'm sure a PR to update the composer.json file to target support for 2.0.x-2.1.x would be appreciated.

Any updates here? Don't get me wrong I love spending hours looking for block names.

@crantron I am not actively maintaining this module as I do not have very many occasions to use it regularly but you are welcome to test and submit a PR with the desired compatibility.

@crantron I recently became aware of this other module that seems to be a little bit more actively maintained so hopefully it serves your needs better. Note, I have not used it nor am I involved in its maintenance so I am not specifically endorsing it but it was shared with me in a thread on github by Magento so I hope it meets your needs. https://github.com/ho-nl/magento2-Ho_Templatehints

Sorry, I was mistaken, it was shared with my on a magento repo thread by https://github.com/paales
Here is the thread: https://github.com/magento/magento2/issues/571#issuecomment-263018785


fix: dont set status to exit for oom condition

Signed-off-by: zhuangqh<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
fix: dont set status to exit for oom condition
pouch would fail to stop or remove a oom container if it was set
to exited status
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
$ CID=$(pouch run -d busybox sh)
$ pouch exec -it $CID sh
$ run a oom program

// another terminal
$ pouch ps -a | grep $CID
// container is up
$ pouch inspect $CID | grep -i oom
// oomkilled is set to true

Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
CRI part using state.Error info string to identify oom status

LGTM

I think we must add a test case to cover the oom case. @zhuangqh @HusterWan
Can we reproduce the oom case by creating a TOMCAT container with JVM allocated with 100m, while the container memory limit is only 50m?

Actually, I am wondering if we could polish the PR description.

fix: dont set status to exit for oom condition. pouch would fail to stop or remove a oom container if it was set to exited status

The description above actually tells us almost nothing. Since you just repeated the error case.
You told us if A, then B. A=set to exited status, B=fail to stop or remove a oom container.
I think what matters is why A is not reasonable. In another word, we care about the reason of why A is wrong, not the result B if we do a wrong A.
WDYT? @zhuangqh

Actually, I am wondering if we could polish the PR description.

fix: dont set status to exit for oom condition. pouch would fail to stop or remove a oom container if it was set to exited status

The description above actually tells us almost nothing. Since you just repeated the error case.
You told us if A, then B. A=set to exited status, B=fail to stop or remove a oom container.
I think what matters is why A is not reasonable. In another word, we care about the reason of why A is wrong, not the result B if we do a wrong A.
WDYT? @zhuangqh

Actually, it is a horrible case that pouch cannot stop or remove a container which occurs oom. An oom container is stilling running as a normal container, what exits is the oom program.

I think we must add a test case to cover the oom case. @zhuangqh @HusterWan
Can we reproduce the oom case by creating a TOMCAT container with JVM allocated with 100m, while the container memory limit is only 50m?

sure, the simplest way to reproduce this issue is writing a c program and malloc a huge memory.

sure, the simplest way to reproduce this issue is writing a c program and malloc a huge memory.

It is worth adding a case to cover it via doing what you said. @zhuangqh


Setup a Zoom registration link for webinar

Could you create a Zoom registration link for the first webinar?

Done: https://zoom.us/webinar/register/WN_41bv9gKvRKynhA31OMYhww


[FLINK-2819] Add Windowed Join/CoGroup Operator Based on Tagged Union

Right now, this does everything in memory, so the JVM will blow if data
for one key becomes too large.

Subsumed by #1238


update gitignore to include folders/files that shouldn't be in repo

Dockerfile (lmk if i should delete)

Do you prefer Dockerfile inside the src/ directory?
I personally prefer it outside, inside the repository's root directory.

Also, I liked the pull request approach! Good idea.

Sounds good. Let me know if you have ideas on what I can work on to transition Mininode to ES6, on how to partition these tasks among us.


Translate Section 2: Hooks, useState, useReducer, useEffect, useRef and useImperativeHandle

Please feel free to ask to work on this issue and I'll assign it to you 😄
https://github.com/typescript-cheatsheets/react#hooks

Hey, can I get this one? :)

Of course @bnrosa !


Static-Site-Scaffold Tests

Closed by https://github.com/chromeos/static-site-scaffold-modules/commit/76eae6a60300d03c0133834091e2d7ac907f91ea


Publish checksums for .tar.gz archives

Motivation

I couldn't find any checksums along with the archives published at https://download.falco.org/?prefix=packages/bin/x86_64/. I think it's important to let users verify the integrity of the binaries they download.
Feature

I suggest to update the Falco release process to compute and publish checkums for all .tar.gz archives (as far as I can tell, the DEB and RPM binaries already have .asc files which are cryptographic signatures).
Alternatives

None
Additional context

None

thank you for reporting this, it makes a lot of sense!

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Thanks for handling this!


Generic types to generic

Types with generic types under generic, only for specialized types for other modules.
@MichaReiser Could you review this PR? And do you mind if I add you to member of this repository?

Zero commit is also welcome. Reviewing changes which can affect ruff behaviors or performance will be good enough.


update PGP key

Mine expired a couple days ago:
http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6EE18A8DC47977C2

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8563630-update-pgp-key?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

This is pretty easy to do isn't it?

Should be. It's probably a good time to move from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>too, though. No?

/me reviews https://www.gnupg.org/gph/en/manual/c14.html

@benhc123 Want to work on this one with me? Let's set up<EMAIL_ADDRESS>and make a key for that that both you and I have access to. Waddya say? :)

I've created the security user in Google Apps, but I'm having trouble delegating access to it to my main Gmail account, which is how I have the others set up.

Once security is configured at Google the next step is to configure it at Freshdesk. That's where I'll give you access, @benhc123.

I just tried delegation again and it went through. Maybe it took time for the new account to propagate within Google? :fried_shrimp:

Okay, I've configured<EMAIL_ADDRESS>in Freshdesk. I've also made a security team on GitHub and a security group at Freshdesk with @benhc123 @greggles @Changaco and myself.

@benhc123 Can I put you in charge of making a PGP key for<EMAIL_ADDRESS>

I'm looking at this. I'm writing up an IG doc as I go.

Is maintaining PGP worth it? Rarely do security researchers use PGP during disclosure.

GitHub discourages encrypted email for security disclosures:

Where is your PGP key? I want to use it when I submit a vulnerability.

If you absolutely believe encrypting the message is necessary, please read our instructions and caveats for PGP submissions.

Does gratipay use a web-based form for submitting issues? If so I think that github page applies. Otherwise, the first paragraph and basis of their philosophy disappears ;)

That said...I also think that encrypted submissions are kinda silly.

email encryption is a great idea for very high risk situations - the worst-case-scenario bug on gratipay is not yet as horrible as a worst-case-scenario bug on php.net or bankofamerica.com

it's also worthwhile to encrypt data that shouldn't be leaked eventually - since inboxes have a way of eventually getting cracked - but the nature of security issues means that they should be kept secret only for a short time.

encrypted emails do require key management (a pain in itself)

they make it harder to deal quickly with incoming submissions (find someone with the key)

But that's because they have a secure form on a website:
https://bounty.github.com/submit-a-vulnerability.html
As does Facebook: https://www.facebook.com/whitehat/report/.

Does gratipay use a web-based form for submitting issues? If so I think that github page applies. Otherwise, the first paragraph and basis of their philosophy disappears ;)

Right. ;-)


Improve health check with additional information

Is your feature request related to a problem? Please describe.
Im getting a health check error with no further information what's causing problem.
Describe the solution you'd like
A log snipped or reason code would help a lot.
Describe alternatives you've considered
Grabbing thru the logs by consulting the documentation first.

The point of the health check is to catch application deadlocks and terminal errors. Most likely, there won‘t be any structured error information. The last error is available via /api/state.

The point is.... Im getting an unsuccessful health check with no information about whats causing the issue.
evcc health [main  ] INFO 2023/05/24 10:03:08 evcc 0.117.4 [main  ] ERROR 2023/05/24 10:03:08 health check failed
while the error logs are clean and not reporting errors and /api/health is also fine.
curl -X GET http://localhost:8083/api/health
OK

BTW: Why do you mention /api/state ? I do not get any system health information with that call, or do I?
I still believe that enriching health output with details from log would help users a lot.

Sure.
Did a restart few minutes before creating logs to reduce log size. Ensured health check still reports error.
Pls find log attached.
evcc.log

Maybe a config dump is even more helpful.
config.txt

This does not look right?
Try min 6 .
Max 16, (or 12, 10 ..)
(Charging does not work below 6A according to the standard)
vehicles:
..
..
  minCurrent: 3
  maxCurrent: 6

Yes, doesnt make sense indeed. Changed it back to 6a min / 16a max.
Anyhow, that didnt solve the health check issue.


do not specify http_host on start OpenADRserver

This PR should solve the issue #30.
Changes:

Not pass http_host argument on call OpenADRServer. This solve the docker container wrong address resolution problem (localhost => ::1).
Use of server.run_async instead of web.AppRunner
Make sure client.stop() after tests

Wasn't the fix I committed today and referenced in #30 the same solution?

Ah I see this is for a different test case. Thanks! It looks good, I'll check it out tomorrow.

Thanks @cirochang, it looks good! I added my sign-off to the your commit and merged it in #32. It's now part of the main branch. I'll close this merge pull request.


undef method

hey,
does this look familiar?

/Users/james/.rvm/gems/ree-1.8.7-2011.12@global/gems/discotech-0.0.2/bin/discotech:15: undefined method `sample' for [:bold]:Array (NoMethodError)

Hey @imajes,
it turns out Ruby 1.8.7 could not disco.
... but now it can.
Disco time!


Several issues fixed.

These changes fix several issues.  Two additional variables can be set in the vagrant file (primary_dns and secondary_dns) which will statically set the primary and secondary dns servers on the vm's nic, which, if configured correctly, can allow the vm to successfully communicate with the domain controller if the vm was unable to without setting the nic's DNS settings.  Also fixed an issue in regards to renaming the machine while domain-joining it.  The only thing I was unable to get perfect is that when destroying the vm, after the vm is removed from the domain, it has to restart prior to actually destroying the vm, but the plugin does work now.

Despite what the check says, broken as it is, modified version of the vagrant-windows-domain plugin is perfectly functional and fixes a lot of issues with the plugin.  I highly recommend you commit the change.

I'd like to test this.
@whiggs which version of Vagrant were you using when you tested this? And which provider (VMWare Workstation?)

@chrisgannon6 Please feel free to test all you like.  When I was testing it,. I used the most up to date vagrant, version 2.1.5 (why would you use a not up-to-date version), and I used the vagrantfile provided in the development folder in the repository (which uses the virtualbox provider).  I hope this answered your questions.

Any update on merging this?

I have modified the plugin again and improved its performance.  I felt the plugin forced the vm being provisioned to restart unnecessarily several times, so I have removed the unnecessary restarts from the plugin to reduce the amount of time it takes to provision the vm.  I removed one of the two restarts when the vm is joined to the domain and I have removed all of the restarts performed after the vm is dis-joined from the domain (since this usually indicates the vm is being destroyed, the vm does not need to be restarted, it can just be destroyed).  It now works perfectly (at least I think it does).  Please feel free to test it yourselves, but please merge the changes and update the gem so that the plugin is readily available.  If you find a problem with it, then let me know so I can fix it, but if not, merge it.

Thanks @whiggs, these all sound like great changes.
I'm hesitant to merge anything with a broken build - i'm very much out of touch with Vagrant plugin development, but the build seems to be stuck in the early stages - it looks like there is a configuration issue removing/installing bundler.
Are you able to look at this before I merge it in (which I very much want to do)?

@mefellows I am pretty sure my modifications are not the reason behind the build failing, but rather, the .travis.yml configuration file.  Looking at the build errors, the build fails when running "gem uninstall bundler --all --executables" because (according to travis) "gem "bundler" cannot be uninstalled because it is a default gem."  I can attempt to modify the .travis.yml file for you to make it work, but that kind of defeats the purpose of having the .travis.yml file in the first place right?  In the end, its up to you.  You want to fix it, or do you want me to?

Ok.  Took quite a few tries, but the travis build configuration has been modified so that it passes the check,  Can you merge it now?

There we go.  Now it is really ready.


Re-implement #295 against latest master

Re-implemented #295 rather than resolve merge conflicts.

Docs Build status updates of commit f34999b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/language/type-model.md
:warning:Warning
View (qsharp-preview)
Details

articles/language/type-model.md

[Warning] 1 invalid cross reference(s) "microsoft.quantum.language.statements".

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

Docs Build status updates of commit faee801:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/language/type-model.md
:warning:Warning
View (qsharp-preview)
Details

articles/language/type-model.md

[Warning] 1 invalid cross reference(s) "microsoft.quantum.language.statements".

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

Docs Build status updates of commit 6217567:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 6ef5efa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 548e36d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 548e36d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit ddaccc2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit b4b443b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 18aa5bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 8f5bfcf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 462a931:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 8988ad0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 2f9a46f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit 2f9a46f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit ba8c528:
:clock10: Pending: waiting for processors (117 builds ahead of you)
:warning: Docs Build is busy, currently there are 117 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
AcrolinxScore
LowestCategoryScore
Issues
Scorecard
Processed

articles/language/type-model.md
79
56
111
link
:white_check_mark:

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

Docs Build status updates of commit ba8c528:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
AcrolinxScore
LowestCategoryScore
Issues
Scorecard
Processed

articles/language/type-model.md
79
56
111
link
:white_check_mark:

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
AcrolinxScore
LowestCategoryScore
Issues
Scorecard
Processed

articles/language/type-model.md
79
56
111
link
:white_check_mark:

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
AcrolinxScore
LowestCategoryScore
Issues
Scorecard
Processed

articles/language/type-model.md
79
56
111
link
:white_check_mark:

More info about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues

Docs Build status updates of commit 0781c88:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit ecd219a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit ecd219a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/language/type-model.md
:white_check_mark:Succeeded
View (qsharp-preview)

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


Better smoothing stability

Codecov Report

Merging #52 (5e26e09) into main (784db72) will decrease coverage by 4.65%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
- Coverage   92.12%   87.46%   -4.66%
==========================================
  Files          21       21
  Lines         813      806       -7
==========================================
- Hits          749      705      -44
- Misses         64      101      +37

Impacted Files
Coverage Δ

src/smoothing.jl
95.83% <100.00%> (-4.17%)
:arrow_down:

src/state_initialization.jl
74.62% <0.00%> (-23.91%)
:arrow_down:

src/perform_step.jl
73.94% <0.00%> (-19.39%)
:arrow_down:

src/ProbNumDiffEq.jl
87.50% <0.00%> (-6.25%)
:arrow_down:

src/caches.jl
97.67% <0.00%> (-2.33%)
:arrow_down:

src/solution.jl
93.67% <0.00%> (+1.17%)
:arrow_up:

src/filtering.jl
85.18% <0.00%> (+2.05%)
:arrow_up:

src/squarerootmatrix.jl
89.47% <0.00%> (+4.47%)
:arrow_up:

src/preconditioning.jl
100.00% <0.00%> (+4.54%)
:arrow_up:

... and 1 more

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 784db72...5e26e09. Read the comment docs.


Implement Crowdin for Section Translations

@fredrikved what is the plan with this PR? Just don't want it to diverge too much from main.

Waiting for clearance from Pris.
Will remerge when sections should be added to crowdin


TAB code

Hi, its possible insert TAB or another code into de barcode?
I need to print AAA TAB BBB, for example. It's possible?
Thanks

AAA \t BBB


Parent and child todo list issue

Hello!
I have testing your plugin and I like it! I found a little issue.
When you have a Parent list and a couple of child tasks if you mark both as done the Parent is marked as done, that's right. But if now you add a third Child, the Parent keeps been marked as done. Should be automatically be Undone... (IMHO)
The same feature should be if you have 3 Child tasks, 2 done and 1 undone. The Parent is Undone. Ok. But if you delete the Child that is Undone, the Parent should be Done...
Sorry for this mess of Child, Parents, done and undone tasks!! :)

This is a very nice issue, you found, but at the moment it requires too much work to do on algorithms.


Implement installers via electron-builder

Hey,
this might be totally wrong, as I'm a fist time node user. And so far I could only test win.
The installation of the exe seems to work fine, but there is no shortcut anywhere to be found. Uninstall also seems to work fine.
Would be very cool, if other people could build it for osx/linux and let the maintainer know if it works.
Cheers

The builder seems to work with my Ubuntu 14.04. But it doesn't meet with our CI process (You don't have to take care yet). I saw following behavior about installation.

The installer launches the app.
There are no shortcuts as you said.
The uninstaller also launches the app.

I'm also beginner for electron-builder, but it seems that some codes are necessary to handle shortcuts. So could you check below?

https://github.com/electron-userland/electron-builder#auto-update
Where is the actual app binary installed into?

Then, if you want to continue this PR, please check Mattermost CLA. http://www.mattermost.org/mattermost-contributor-agreement/

Sorry, I forgot to add the build folder. We would also need a background.png for osx I think? Not sure what to do there.
Yes, I'm aware of it not taking into account your ci setup right now.
3.) Yes uninstaller also opens the app, takes a few seconds then it closes and is uninstalled. That's whats happening with windows.
I'll try to look into the shortcuts again.
On windows it's installed to the userspace so C:\Users\razze\AppData\Local\mattermost for example.
CLA signed, thanks for pointing me towards it.

The problematic part about me doing the autoupdate stuff is, that I don't know if or how you will handle the server part. If I can assume, that we're using https://github.com/GitbookIO/nuts and heroku, I can probably come up with something.

Well it seems like you will need to do the server stuff. I don't have these data :)

Thanks. For now, we don't have to think about the update server. I think that the point of handling Squirrel event is create/remote shortcuts on the event. If there is no server, the updater merely fails. So I think that's not important matter. Of course, we will have to handle updater and server to provide auto-update.

Is it correct that this PR is against master? Or should it be dev?
Finally got it to work on windows, haven't tested any other OS. Implementing auto update should be trivial when we get a server. This work is heavily based on: https://github.com/electron/electron-api-demos
You might want to review this with whitespaces off:
https://github.com/mattermost/desktop/pull/138/files?w=0

Is it correct that this PR is against master? Or should it be dev?

Good question. master is okay.
JFYI, now there are two active branches, master and dev. They almost follows git-flow. However recently I feel that it's not simple for pull-requests. So the branching model will be a coming issue.

@yuya-oc well you might want to update contributing.md to help with the branch choice

Updated to use mongodb-js/electron-squirrel-startup
Fixed indent
Only build installer from 64bit
Small update for the copyright year

Just curious, what does your "works fine" mean? I have never seen any shortcuts, is it correct?
Environment:
Windows 10 x64
Node v4.2.2, npm 2.14.7 (maybe this is not matter)

Shortcuts work fine for me, but its under the Author name so in the folder Yuya Ochiai.
Enviroment is Win10 x64

I had overlooked the folder, thank you!


Importing spyder.plugins.editor segfaults

Description of your problem
What steps will reproduce the problem?

python -c "import spyder.plugins.editor"

What is the expected output? What do you see instead?
I get a segmentation fault. I would expect an import never to lead to a segmentation fault.
Please provide any additional information below
This is Debian bug 844601. Issue #4014 is related.
Versions and main components

Spyder Version: Current head, either master branch or 3.x branch. PR #4036 does not fix this issue.
Python Version: 3.6.0 or 3.5.2
Operating system: Debian Linux

The stack trace is the same as listed in #4014. The crash happens in QFontDatabase::addApplicationFont(QString const&), so the fix is probably similar.
Arguably, this issue is not as severe as #4014 because there is less reason for somebody to import spyder.plugins.editor.

@dalthviz could we add a test that tries to import each spyder file as @jitseshows? By recursively going trhough all python files in the spyder folder¿

@goanpeca, I think @dalthviz's PR on QtAwesome is enough for now.

yep


[gdal] Build error

Host Environment

OS: [Windows11 x64]
Compiler: mingw 8.1.0 64bit

To Reproduce
Steps to reproduce the behavior:
./vcpkg.exe install gdal --triplet=x64-mingw-dynamic
Failure logs
$ ./vcpkg.exe install gdal  --triplet=x64-mingw-dynamic
Computing installation plan...
The following packages will be built and installed:
    gdal[core,hdf5,netcdf,postgresql,supported-default-features]:x64-mingw-dynamic -> 3.4.3
Detecting compiler hash for triplet x64-mingw-dynamic...
Restored 0 packages from C:\Users\o\AppData\Local\vcpkg\archives in 170.8 us. Use --debug to see more details.
Installing 1/1 gdal:x64-mingw-dynamic...
Building gdal[core,hdf5,netcdf,postgresql,supported-default-features]:x64-mingw-dynamic...
-- Using community triplet x64-mingw-dynamic. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: G:\buildtmp\vcpkg\triplets\community\x64-mingw-dynamic.cmake
-- Using cached OSGeo-gdal-v3.4.3.tar.gz.
-- Cleaning sources at G:/buildtmp/vcpkg/buildtrees/gdal/src/v3.4.3-d31eaa7065.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source G:/buildtmp/vcpkg/downloads/OSGeo-gdal-v3.4.3.tar.gz
-- Applying patch 0001-Fix-debug-crt-flags.patch
-- Applying patch 0002-Fix-build.patch
-- Applying patch 0004-Fix-cfitsio.patch
-- Applying patch 0005-Fix-configure.patch
-- Applying patch 0006-Fix-mingw-dllexport.patch
-- Applying patch 0007-Control-tools.patch
-- Applying patch 0008-Fix-absl-string_view.patch
-- Applying patch 0009-atlbase.patch
-- Applying patch 0010-symprefix.patch
-- Using source at G:/buildtmp/vcpkg/buildtrees/gdal/src/v3.4.3-d31eaa7065.clean
-- Getting CMake variables for x64-mingw-dynamic
-- Using cached msys-gzip-1.11-1-x86_64.pkg.tar.zst.
-- Using cached msys-bash-5.1.008-1-x86_64.pkg.tar.zst.
-- Using cached msys-autoconf-2.71-3-any.pkg.tar.zst.
-- Using cached msys-diffutils-3.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-binutils-2.37-5-x86_64.pkg.tar.zst.
-- Using cached msys-libtool-2.4.6-9-x86_64.pkg.tar.xz.
-- Using cached msys-file-5.41-2-x86_64.pkg.tar.zst.
-- Using cached msys-zlib-1.2.11-1-x86_64.pkg.tar.xz.
-- Using cached msys-libbz2-1.0.8-3-x86_64.pkg.tar.zst.
-- Using cached msys-coreutils-8.32-2-x86_64.pkg.tar.zst.
-- Using cached msys-grep-3.0-2-x86_64.pkg.tar.xz.
-- Using cached msys-sed-4.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-libpcre-8.45-1-x86_64.pkg.tar.zst.
-- Using cached msys-m4-1.4.19-2-x86_64.pkg.tar.zst.
-- Using cached msys-automake-wrapper-11-4-any.pkg.tar.zst.
-- Using cached msys-gawk-5.1.0-2-x86_64.pkg.tar.zst.
-- Using cached msys-mpfr-4.1.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-gmp-6.2.1-1-x86_64.pkg.tar.zst.
-- Using cached msys-libreadline-8.1.001-1-x86_64.pkg.tar.zst.
-- Using cached msys-ncurses-6.2-2-x86_64.pkg.tar.zst.
-- Using cached msys-automake1.16-1.16.3-3-any.pkg.tar.zst.
-- Using cached msys-perl-5.32.1-2-x86_64.pkg.tar.zst.
-- Using cached msys-libcrypt-2.1-3-x86_64.pkg.tar.zst.
-- Using cached msys-pkg-config-0.29.2-4-x86_64.pkg.tar.zst.
-- Using cached msys-make-4.3-3-x86_64.pkg.tar.zst.
-- Using cached msys-findutils-4.8.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-libintl-0.21-1-x86_64.pkg.tar.zst.
-- Using cached msys-libiconv-1.16-2-x86_64.pkg.tar.zst.
-- Using cached msys-gcc-libs-11.2.0-3-x86_64.pkg.tar.zst.
-- Using cached msys-msys2-runtime-3.2.0-8-x86_64.pkg.tar.zst.
-- Using msys root at G:/buildtmp/vcpkg/downloads/tools/msys2/7e05e7aa09f1709f
-- Generating configure for x64-mingw-dynamic
-- Finished generating configure for x64-mingw-dynamic
-- Using cached msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst.
-- Using msys root at G:/buildtmp/vcpkg/downloads/tools/msys2/9a1ec3f33446b195
-- Configuring x64-mingw-dynamic-rel
-- Building x64-mingw-dynamic-rel
CMake Error at scripts/cmake/vcpkg_build_make.cmake:212 (message):
  libtool could not find a file being linked against!
Call Stack (most recent call first):
  scripts/cmake/vcpkg_install_make.cmake:26 (vcpkg_build_make)
  ports/gdal/portfile.cmake:326 (vcpkg_install_make)
  scripts/ports.cmake:146 (include)

error: building gdal:x64-mingw-dynamic failed with: BUILD_FAILED
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+gdal
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[gdal]+Build+error
Include '[gdal] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2022-05-05-67e17c1782801cf481be9ac0b3765dff3e4bdeb8
    vcpkg-scripts version: 93b38546e 2022-05-24 (13 hours ago)

I don't understand, why will I compile the i686 version here?

The folder G:/buildtmp/vcpkg/downloads/tools/msys2/7e05e7aa09f1709f is mingw64 tool chain.
G:/buildtmp/vcpkg/downloads/tools/msys2/9a1ec3f33446b195 is the incomplete mingw32.

What you call "mingw32" just serves to provide pkg-config on Windows.
Please provide:
buildtrees/gdal/build-x64-mingw-dynamic-rel-err.log
buildtrees/gdal/build-x64-mingw-dynamic-rel-out.log

What you call "mingw32" just serves to provide pkg-config on Windows.
Please provide:
buildtrees/gdal/build-x64-mingw-dynamic-rel-err.log
buildtrees/gdal/build-x64-mingw-dynamic-rel-out.log

buildtrees/gdal/build-x64-mingw-dynamic-rel-err.log
cpl_vsil_win32.cpp: In function 'const char* CPLGetWineVersion()':
cpl_vsil_win32.cpp:454:107: warning: cast between incompatible function types from 'FARPROC' {aka 'long long int (*)()'} to 'const char* (*)()' [-Wcast-function-type]
     pwine_get_version = reinterpret_cast<const char* (*)(void)>(GetProcAddress(hntdll, "wine_get_version"));
                                                                                ^
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_curl_streaming.cpp:32:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_curl_streaming.cpp:32:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_curl.cpp:31:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_curl.cpp:31:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_gs.cpp:33:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_gs.cpp:33:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_s3.cpp:37:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_s3.cpp:37:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_az.cpp:34:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_az.cpp:34:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_adls.cpp:34:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_adls.cpp:34:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_oss.cpp:33:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_oss.cpp:33:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_swift.cpp:34:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_swift.cpp:34:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_vsil_curl_class.h:35,
                 from cpl_vsil_webhdfs.cpp:33:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_aws.h:43,
                 from cpl_vsil_curl_class.h:34,
                 from cpl_vsil_webhdfs.cpp:33:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from cpl_azure.cpp:28:
cpl_azure.h:54:13: warning: declaration of 'BLOB' shadows a global declaration [-Wshadow]
             BLOB,
             ^~~~
In file included from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/combaseapi.h:153,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/objbase.h:14,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/ole2.h:17,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypes.h:12,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winscard.h:10,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/windows.h:97,
                 from C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/winsock2.h:23,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/system.h:406,
                 from G:/buildtmp/vcpkg/installed/x64-mingw-dynamic/include/curl/curl.h:35,
                 from cpl_azure.h:35,
                 from cpl_azure.cpp:28:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/wtypesbase.h:385:3: note: shadowed declaration is here
 } BLOB;
   ^~~~
In file included from ogrodsdatasource.cpp:34:
ods_formula.h:41: warning: "strcasecmp" redefined
 #  define strcasecmp stricmp

In file included from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_port.h:141,
                 from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_progress.h:33,
                 from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/ogr/ogrsf_frmts/ogrsf_frmts.h:34,
                 from ogr_ods.h:33,
                 from ogrodsdatasource.cpp:29:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/string.h:120: note: this is the location of the previous definition
 #define strcasecmp _stricmp

netcdfdataset.cpp: In function 'CPLErr NCDFGetSubGroups(int, int*, int**)':
netcdfdataset.cpp:11497:37: warning: unused parameter 'nGroupId' [-Wunused-parameter]
 static CPLErr NCDFGetSubGroups( int nGroupId, int *pnSubGroups,
                                 ~~~~^~~~~~~~
netcdfdataset.cpp: In function 'CPLErr NCDFGetGroupFullName(int, char**, bool)':
netcdfdataset.cpp:11520:41: warning: unused parameter 'nGroupId' [-Wunused-parameter]
 static CPLErr NCDFGetGroupFullName( int nGroupId, char **ppszFullName,
                                     ~~~~^~~~~~~~
netcdfdataset.cpp: In function 'bool NCDFIsUserDefinedType(int, int)':
netcdfdataset.cpp:12270:32: warning: unused parameter 'ncid' [-Wunused-parameter]
 bool NCDFIsUserDefinedType(int ncid, int type)
                            ~~~~^~~~
netcdfdataset.cpp:12270:42: warning: unused parameter 'type' [-Wunused-parameter]
 bool NCDFIsUserDefinedType(int ncid, int type)
                                      ~~~~^~~~
In file included from ods_formula.cpp:34:
ods_formula.h:41: warning: "strcasecmp" redefined
 #  define strcasecmp stricmp

In file included from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_port.h:141,
                 from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_conv.h:35,
                 from ods_formula.cpp:33:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/string.h:120: note: this is the location of the previous definition
 #define strcasecmp _stricmp

In file included from ods_formula_node.cpp:32:
ods_formula.h:41: warning: "strcasecmp" redefined
 #  define strcasecmp stricmp

In file included from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_port.h:141,
                 from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_conv.h:35,
                 from ods_formula_node.cpp:31:
C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/include/string.h:120: note: this is the location of the previous definition
 #define strcasecmp _stricmp

In file included from G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_conv.h:35,
                 from ogrosmlayer.cpp:41:
ogrosmlayer.cpp: In member function 'void OGROSMLayer::SetFieldsFromTags(OGRFeature*, GIntBig, bool, unsigned int, OSMTag*, OSMInfo*)':
G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_port.h:312:26: warning: format '%d' expects argument of type 'int', but argument 4 has type 'GIntBig' {aka 'long long int'} [-Wformat=]
 #define CPL_FRMT_GIB     "%" CPL_FRMT_GB_WITHOUT_PREFIX "d"
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ogrosmlayer.cpp:603:42: note: in expansion of macro 'CPL_FRMT_GIB'
             snprintf(szID, sizeof(szID), CPL_FRMT_GIB, nID );
                                          ^~~~~~~~~~~~
G:/buildtmp/vcpkg/buildtrees/gdal/x64-mingw-dynamic-dbg/port/cpl_port.h:312:26: warning: format '%d' expects argument of type 'int', but argument 4 has type 'GIntBig' {aka 'long long int'} [-Wformat=]
 #define CPL_FRMT_GIB     "%" CPL_FRMT_GB_WITHOUT_PREFIX "d"
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ogrosmlayer.cpp:614:42: note: in expansion of macro 'CPL_FRMT_GIB'
             snprintf(szID, sizeof(szID), CPL_FRMT_GIB, nID );
                                          ^~~~~~~~~~~~

build-x64-mingw-dynamic-dbg-err.log
build-x64-mingw-dynamic-dbg-out.log

So this is the full message that is taken as a build error:
*** Warning: linker path does not have real file for library -lz.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libz and none of the candidates passed a file format test
*** using a file magic. Last file checked: C:/Qt/Tools/mingw810_64/x86_64-w64-mingw32/lib/libz.a
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.

The vcpkg mingw build of zlib installs libzlib.dll.a, so the correct reference is -lzlib (or -lzlibd with debug postfix). -lz is wrong, and we need to find out where it comes from. (It probably goes unnoticed in most mingw installation which already provide a libz.dll.a or similar.)

to find out where it comes from.

It comes from gdal itself. PR is coming.

*** Warning: linker path does not have real file for library -lz.
The vcpkg mingw build of zlib installs libzlib.dll.a, so the correct reference is -lzlib (or -lzlibd with debug postfix). -lz is wrong, and we need to find out where it comes from. (It probably goes unnoticed in most mingw installation which already provide a libz.dll.a or similar.)

Thanks, I copied libzlib.dll.a as libz.dll.a, and then continued to compile, passed.
copy installed\x64-mingw-dynamic\lib\libzlib.dll.a installed\x64-mingw-dynamic\lib\libz.dll.a

@sotex What's result when you use the new 0005-Fix-configure.patch in https://github.com/microsoft/vcpkg/pull/24931?


Match the comment with #ifndef

Thank you for your contribution! PyTorch and Caffe2 are now officially merged with the PyTorch 1.0 prerelease. Please submit on https://github.com/pytorch/pytorch if this is still an issue over there.


Fix false negatives in NVD CPE matching

Ported from https://github.com/DependencyTrack/dependency-track/pull/3070

Sonar is complaining about missing coverage in VulnerableSoftwareRepository. That class is thoroughly exercised in the new CPE matching tests, however those live in a separate module so Sonar doesn't include it in the coverage metrics correctly.
I'd prefer not to write duplicate test code just to make this metric go up, but can do it anyway in case other team members wanted it.


deps: Bump com_github_curl -> 8.4.0

Commit Message: deps: Bump com_github_curl -> 8.4.0
Additional Description: CVE fix from https://github.com/curl/curl/releases/tag/curl-8_4_0
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

cc: @moderation & @phlax for the review

hopefully in future we don't need to do this from the virtue of https://github.com/envoyproxy/envoy/pull/29880

windows fail seems real:
//test/dependencies:curl_test                                            FAILED in 2 out of 2 in 0.3s
  Stats over 2 runs: max = 0.3s, min = 0.2s, avg = 0.3s, dev = 0.0s
  C:/build/tmp/execroot/envoy/bazel-out/x64_windows-opt/testlogs/test/dependencies/curl_test/test.log
  C:/build/tmp/execroot/envoy/bazel-out/x64_windows-opt/testlogs/test/dependencies/curl_test/test_attempts/attempt_1.log

https://dev.azure.com/cncf/envoy/_build/results?buildId=151981&view=logs&j=b840a642-5ff3-5357-2e4b-e06e40b0cffd&t=67965174-5100-5631-9dc0-68b9f0aacb53&l=12501
im in 2 minds about updating this prior to the 1.28 release - while its better for this to be updated its just doesnt leave much burn in time

yes, don't have to jeopardize upcoming v1.28 release for this. Meanwhile, if a new curl patch version arrives with the fix for above windows problem we can update or discard this PR based on dependabot.

/retest

Updated the curl_test.cc to ignore testing whether NTLM feature is enabled.

/retest

Hi @phlax, is this change safe to ship?


Frag equivalent of sql interpolator?

Hi, what is the equivalent Frag of writing sql"... $param"?
I thought it would be Frag("... ? ", IArray(param)), but that doesn't return any result rows, because the param is probably not passed correctly to the db.
I'm using sqlite.
def getReplyIds(parent_id: Long)(using con: DbCon): Vector[Long] = {

  // this works
  val frag = sql"select id from post where parent_id = ${parent_id}"

  // this doesn't work:
  // val frag = Frag("select id from post where parent_id = ?", params = IArray(parent_id))

  frag.query[Long].run()
}

For context, I'm experimenting with sqlc to generate Scala functions from raw sql queries: https://github.com/fdietze/sqlc-gen-from-template

Hi, Frag takes three arguments: https://github.com/AugustNagro/magnum/blob/master/magnum/src/main/scala/com/augustnagro/magnum/Frag.scala
You're missing the third writer: FragWriter argument (you do not want the default Frag.emptyWriter)
For an example on how to implement FragWriter, see for example https://github.com/AugustNagro/magnum/blob/master/magnum/src/main/scala/com/augustnagro/magnum/Spec.scala#L38

For reference, this is what I came up with:
def fragWriter(params: Seq[Any]): FragWriter = { (preparedStatement, startPos) =>
  var i = 0
  val n = params.size
  while (i < n) {
    val param = params(i)
    param match {
      case param: Int    => preparedStatement.setInt(startPos + i, param)
      case param: Long   => preparedStatement.setLong(startPos + i, param)
      case param: String => preparedStatement.setString(startPos + i, param)
      case param: Double => preparedStatement.setDouble(startPos + i, param)
    }
    i += 1
  }
  startPos + params.size
}


Feature/blui

For # PXBLUE-2533

Changes proposed in this Pull Request:

Rebrand to BLUI

I tested this within the themes demo & it works.  As soon as those small tweaks are in, we can publish a beta.


Update RxJava dependency / simplify support update

Hey there,
I've updated the RxJava deps.
Also extract a android support lib version number to update these libs with a one liner 👍
I've also tried to update okhttp and retrofit but currently this is impossible because of the com.github.alorma dependency (which is currently deprecated :/)

The deprecation is known and I'm in the middle of writing a lib from scratch, well I'm almost done. As soon as that's done, hoping for this weekend, I'll switch focus back this. I know it takes time but we're trying :)

Did you know how to fix this Travis error? I've searched for a file and it seems that Travis killed the app because it ran out of memory...?! But didn't find anything how to fix this.

I have looked at the Travis problem but have no clue how to fix it. Might just be as simple as updating the build tools. I'll look at that later.


Maxim number of followable users

The "Distributed cache service limits" sections states that "The total number of entities that can be followed by a single user on a distributed cache host with 16GB RAM assigned to the distributed cache service is 400,000.": is this the upper limit to the number of users a SharePoint user can follow? Is there any other limit related to the number of users a SharePoint user can follow?

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

ID: 81e0e611-8cbd-1b44-6e09-487b15307c6a
Version Independent ID: b00c5b8b-c735-6473-a492-b82ae4e8a02f
Content: Software boundaries and limits for SharePoint 2013
Content Source: SharePoint/SharePointServer/install/software-boundaries-and-limits.md
Product: sharepoint-server-itpro
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@LuigiBruno Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@MikePlumleyMSFT do you have insights on this?

The max you can set via the UI is 1000, which is also the default. You can set the value up to Int32.MaxValue in PowerShell, but I don't know what the consequences of setting a value that high would be sans performance issues.

The max you can set via the UI is 1000, which is also the default. You can set the value up to Int32.MaxValue in PowerShell, but I don't know what the consequences of setting a value that high would be sans performance issues.

Thank you @steward.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


ChatMessage doesn't get appended in the ChatContext

I have made a Voice Assistant using the kitt example
It can interact over voice as well as text messages.
Once the user ends the call/room, the assistant is designed to process all the messages and store them in a persistent database.
However, after the call ends, all the ChatMessaged pushed to the ChatContext using llm.chat() method while answering the text messages from the user are not present in the messages array.
The same happens if I push a System Message to the context while sending a system message to the llm after the function calls are finished.

Hi, friend. I was trying to run the same example but I can't. On my windows machine I always have this error:
{"message": "silero stream failed\nTraceback (most recent call last):\n  File "D:\!!!Trabajo\!!Natasquad\Repos\Live-Agent\env\lib\site-packages\livekit\plugins\silero\vad.py", line 148, in _run\n    await asyncio.shield(self._run_inference())\n  File "D:\!!!Trabajo\!!Natasquad\Repos\Live-Agent\env\lib\site-packages\livekit\plugins\silero\vad.py", line 171, in _run_inference\n    raw_prob = await asyncio.to_thread(\n  File "D:\!!!Trabajo\!!Natasquad\Repos\Live-Agent\env\lib\asyncio\threads.py", line 25, in to_thread\n    return await loop.run_in_executor(None, func_call)\n  File "D:\!!!Trabajo\!!Natasquad\Repos\Live-Agent\env\lib\concurrent\futures\thread.py", line 58, in run\n    result = self.fn(*self.args, **self.kwargs)\n  File "D:\!!!Trabajo\!!Natasquad\Repos\Live-Agent\env\lib\site-packages\livekit\plugins\silero\vad.py", line 172, in \n    lambda: self._model(tensor, self._sample_rate).item()\n  File "C:\Users\Reynold/.cache\torch\hub\snakers4_silero-vad_v4.0\utils_vad.py", line 65, in call\n    ort_outs = self.session.run(None, ort_inputs)\n  File "D:\!!!Trabajo\!!Natasquad\Repos\Live-Agent\env\lib\site-packages\onnxruntime\capi\onnxruntime_inference_collection.py", line 220, in run\n    return self._sess.run(output_names, input_feed, run_options)\nonnxruntime.capi.onnxruntime_pybind11_state.InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Unexpected input data type. Actual: (tensor(int32)) , expected: (tensor(int64))\n", "job_id": "AJ_juzTLFapA3Pq", "pid": 12844, "timestamp": "2024-07-02T20:29:42.814037+00:00"}
TL:DR
[ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Unexpected input data type. Actual: (tensor(int32)), expected: (tensor(int64))

Hi,
I seem to be getting something similar:
unhandled exception in the job entry <function entrypoint at 0x7fa47b98c4a0> | exc_info=Traceback (most recent call last):
  File "/home/appuser/myagent.py", line 13, in entrypoint
    initial_ctx = ChatContext().append(
                  ^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ChatContext' object has no attribute 'append' timestamp=2024-07-11T05:38:51.319684+00:00
unhandled exception in the job entry <function entrypoint at 0x7fa47b98c4a0>
Traceback (most recent call last):
  File "/home/appuser/myagent.py", line 13, in entrypoint
    initial_ctx = ChatContext().append(
                  ^^^^^^^^^^^^^^^^^^^^

Which is just running the minimal-agent.py example. When I looked further into the livekit.agents.llm module there does not appear to be an "append" attribute outlined:
class ChatContext(builtins.object)
 |  ChatContext(messages: 'list[ChatMessage]' = <factory>) -> None
 |
 |  ChatContext(messages: 'list[ChatMessage]' = <factory>)
 |
 |  Methods defined here:
 |
 |  eq(self, other)
 |      Return self==value.
 |
 |  init(self, messages: 'list[ChatMessage]' = <factory>) -> None
 |      Initialize self.  See help(type(self)) for accurate signature.
 |
 |  repr(self)
 |      Return repr(self).
 |
 |  copy(self)
 |
 |  ----------------------------------------------------------------------
 |  Data descriptors defined here:
 |
 |  dict
 |      dictionary for instance variables (if defined)
 |
 |  weakref
 |      list of weak references to the object (if defined)
 |
 |  ----------------------------------------------------------------------
 |  Data and other attributes defined here:
 |
 |  annotations = {'messages': 'list[ChatMessage]'}
 |
 |  dataclass_fields = {'messages': Field(name='messages',type='list[C...
 |
 |  dataclass_params = _DataclassParams(init=True,repr=True,eq=True,or...
 |
 |  hash = None
 |
 |  match_args = ('messages',)

Hey, it seems you were trying our updated examples without using our latest agents version. Please try again using livekit-agents v0.8.0


Jasmine-core and karma-jasmine-html-reporter` upgrade in package.json needed

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

Command (mark with an x)
- [ x ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
Angular CLI: 7.0.5
Repro steps
When i generate an angular project with the version on top of the cli.,
I get a version of jasmine-core and karma-jasmine-html-reporter that doesn't support the log
ERROR: 'Spec test b has no expectations.'
Example explained:
i have a test that i crafted in stackblitz here:
https://stackblitz.com/edit/testing-false-positiv?file=src%2Fapp%2Ftest-b%2Ftest-b.service.spec.ts
focus on the fact that one test expectation is not reached and the test-reporter is mentionning:
SPEC HAS NO EXPECTATIONS ...1a
So i went to angular-cli => created a project and added the same test in the new project as in stackblitz.
the output was:

No error is flagged.
Solution to see the error:
upgraded in package.json
jasmine-core to 3.0.0 and karma-jasmine-html-reporter to 1.1.0
Result:

Desired functionality
ng new should create an angular project with in package.json:
the versions for jasmine-core and karma-jasmine-html-reporter to activate this feature in the tests reporter (not mandatory to stick to the upgrade versions i picked)
*one of my friend is investigating Jest behavior with this No expectation test feature if available.
Mention any other details that might be useful
Next:
In the jasmine repo, an issue exists:
https://github.com/jasmine/jasmine/issues/1467
The jasmine member @slackersoft said:

I'd be happy to review a pull request that adds another option like 'stop execution on spec failure' called something like 'fail specs with no expectations'. Oddly, I think the easiest way to implement that will be to add an expectation failure to the spec with the appropriate message just before the Spec object marks itself complete and successful.

When the flag available, i hope devs will enable it (and maybe the cli will have it by default enable) to be able to detect false-positive tests that are hurting a lot (i saw a lot stuf around this happening in legacy tests of new teams i joined that's why i dived on the topic).
in the futur when the flag will be added to jasmine i'll open another issue to maybe enable by default in cli depending on cli team feedback.
medium<EMAIL_ADDRESS>

@hansl are you aware if internally within Google, Jasmine 3 is now supported?

i think the good call to do is:

move to Jest (NX did, i did :) )
if the cli continue to avoid jest => google team you need to rewrite karma or improve it (too slow) and have your own test framework (when ivy is done please :P)


Convert project to TypeScript

TypeScript is a superset of JavaScript and helps developers write less erroneous code as it provides compile time type-checking etc.
The initial version of the application was written in plain JS for speed but we should look into converting the project into a TypeScript one.

I think this issue should be closed too.

There is still work to be done in improving typescript errors, but that can be considered a separate task. Closing.


Getting key file import failure upon forking

We cloned this library a few days ago and were able to successfully build it, although we did have to manually copy "nuget.exe" into the .nuget folder.
We then tried, today, to fork the repo. We forked and cloned. When we tried to build from the new clone, we again got the nuget.exe error and again fixed it. Then, however, we got this error:
"Cannot import the following key file: DocuSignClient.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_6CA6AFBE065420C2  "
Based on SO, we used the sn command, but it wants a password:
c:\code\DocuSign-.NET-Client\DocuSign.Integrations.Client>sn -i DocuSignClient.p
fx VS_KEY_6CA6AFBE065420C2
Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.33440
Copyright (c) Microsoft Corporation.  All rights reserved.
Enter the password for the PKCS#12 key file:
Failed to parse the PKCS#12 blob in DocuSignClient.pfx -- The specified network
password is not correct.

Do we need to request a password from Docusign before we fork the repo? Or is forking not allowed at all?
 I just pushed an update to change from .pfx to .snk which should resolve your issue.
this was done so you can strong-name-sign your assembly and this way you can GAC it
Let me know if you still have an issue once you pull latest.

didn't hear anything new, so I Assume this is good now, closing....


Is there a way for importing Coop Worlds?

Is there a way for importing Coop Worlds?

I believe you can although it is not a very easy process: https://github.com/thijsvanloef/palworld-server-docker/issues/135#issuecomment-1912345210


prev issue 57 - 2: machine mode alignment

Separating previous issue #57 into multiple issues for better tracking

machine mode alignment
the machine mode CLIC space needs to be protected from S/U accesses with a PMP, they have their own (implementation defined) alignment constraints - it's probably worth requiring that in systems with S and/or U modes that:
a) the region containing all the hart's machine mode CLIC spaces can be mapped with one PMP, and
b) that there is a spare PMP available for this purpose

If PMPs are implemented, unless M-mode aperture is explicitly enabled for S and U mode, they cannot access it, so no PMP entry is required to isolate M-mode aperture.


Dart2js error when calling toString() on Null

The following program produces an error on dart2js
class A {}

main() {
  A? a = null;
  var x = a.toString();
}

Runtime error:
TypeError: C.JSNull_methods.toString$0 is not a function

Calling of Object methods on Null is not an error in Dart
Dart VM version: 2.9.0-13.0.dev (dev) (Fri May 29 15:59:05 2020 +0200) on "windows_x64"

There seems to be a tree-shaking issue here. If we print(x); (or just print(a.toString());), then the code runs properly.

This no longer reproduces.
X = {
    main: function() {
      C.JSNull_methods.toString$0(null);
    }
  };
...
  J.JSNull.prototype = {
    toString$0: function(receiver) {
      return "null";
    }
  };


Valid Webpack Alias Import Syntax

It seems that eslint-plugin-import is much more discriminate about what characters and what parts of a URI are used in an import statement than Webpack is.  Is there a complete list anywhere that I can assemble into a section for the readme?  Or a section of the code that might be relevant to discovering why the behavior is what it is that I can then create documentation for?
I have a test repository here that shows some of my confusion in App.jsx.  The README may shed some additional light on relevant files.

You can have a look at importType.js for the logic to differentiate import types, e.g. absolute, builtin, external, etc. One thing worth noting is that rules in eslint-plugin-import don't treat aliases starting with @ as internal imports.
Regarding you test project, seems you're missing resolve.extensions in webpack.config.js so it can't resolve .jsx files.


Dynamic vertex buffer getting overwritten by update after being submitted

Describe the bug
Dynamic vertex buffer is getting overwritten by update after being submitted and I'm not sure if its expected/wanted behavior.
To Reproduce
Steps to reproduce the behavior:

Create DynamicVertexBuffer and fill it with data
Submit it for render
Update vertices with other data
Submit it again
First vertices are overwritten by second submit

Expected behavior
I expected to see both of the submitted meshes at different positions
Repro
I modified example 01 to demonstrate the bug
Additional context

Debian 12 (bookworm) x86_64
X11 (i3wm)
tested with opengl and vulkan

This is expected behavior. You can't modify data until it's consumed (by bgfx::frame call).
You should not open issues like this, rather ask question in Discord and Discussions.

thanks for the clarification! I will definitely join the discord community :100:

Also check TransientVertex/IndexBuffers, it's better match for code in repro.
Transient buffers are when buffer life time is 1 frame. Dynamic buffers are more for things that last more than 1 frame but it's not completely static.


Add orchestration stack status support for VMware Cloud

This patch adds the ability to get the current status of the
orchestration stack (in case of VCD, this is a vApp). The status is
retrieved from the EMS on demand. Corresponding tests are used to
validate the behaviour.
The patch requires new version of fog-vcloud-director gem allowing
retrieval of specific vApp and providing additional statuses relevant
to vApps and VMs.
@miq-bot add_label providers/vmware/cloud, enhancement, gem changes

@agrare I've decided to split the vApp provisioning into several smaller pieces, starting with the status retrieval. I'll continue with the deployment (create) and termination (delete). We'll probably need to discuss how the update works in terms of VCD.

Sounds like a good plan @gberginc
This looks good to me :+1:

@miq-bot assign blomquisg

@gberginc Would you please fix the 2 Performance/Casecmp warnings from Rubocop.

@chessbyte I fixed casecmps and rebased again.
I wasn't sure whether I should update them as the code was written based on other providers.

@blomquisg @chessbyte is there anything else needed for this change to be accepted?

@bzwei can you give this a quick check?  Assign back to me when you're comfortable with it.

@bzwei The PR is updated with the suggested change. I hope the tests won't fail as I rebased on master again.

👍

@miq-bot assign @blomquisg


Validate client application_type

Fixes #97
This PR and its related issue are misnomers, because in reality redirect_uris are being validated, with rules that are primarily based on the value of application_type

Thanks. Looks good.


[TF2.3.0] Failed to Build libtensorflow_cc.so for C++ APIs with conda environment

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (CentOS Linux 7 (Core)):
TensorFlow installed from (source):
TensorFlow version: 2.3.0
Python version: 3.7.10
Installed using virtualenv? pip? conda?: conda
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 7.3.0
CUDA/cuDNN version: 10.1.243 (cuda), 7.6.5(cuDNN)
GPU model and memory: v100, 32g

Describe the problem
I'am tring to build TensorFlow’s C++ interface by this document (https://deepmd.readthedocs.io/en/latest/install-tf.2.3.html).
Provide the exact sequence of commands / steps that you executed before running into the problem
First, I create environment by

conda install bazel=3.1.0 cudatoolkit=10.1.243 cudnn=7.6.0=cuda10.1_0 python=3.8.8
conda install -c conda-forge cudatoolkit-dev=10.1.243 openmpi
conda install numpy

After configuration, I try to build by 'bazel build -c opt --verbose_failures //tensorflow:libtensorflow_cc.so'
The error is

ERROR: /mnt/gs18/scratch/users/gepei/tensorflow/tensorflow/cc/BUILD:629:1: Linking of rule '//tensorflow/cc:ops/functional_ops_gen_cc' failed (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command
(cd /mnt/ufs18/home-183/gepei/.cache/bazel/_bazel_gepei/515900c424239e830302083d92d41b3a/execroot/org_tensorflow &&
exec env -
LD_LIBRARY_PATH=/opt/software/binutils/2.30-GCCcore-7.3.0/lib:/opt/software/GCCcore/7.3.0/lib/gcc/x86_64-pc-linux-gnu/7.3.0:/opt/software/GCCcore/7.3.0/lib64:/opt/software/GCCcore/7.3.0/lib
PATH=/mnt/home/gepei/anaconda3/envs/tensorflow_GPU/bin:/opt/software/binutils/2.30-GCCcore-7.3.0/bin:/opt/software/GCCcore/7.3.0/bin:/mnt/home/gepei/anaconda3/condabin:/usr/lib64/qt-3.3/bin:/opt/software/core/lua/lua/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/hpcc/bin:/usr/lpp/mmfs/bin:/opt/ibutils/bin:/opt/puppetlabs/bin:/opt/dell/srvadmin/bin
PWD=/proc/self/cwd
external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc @bazel-out/k8-opt-exec-50AE0418/bin/tensorflow/cc/ops/functional_ops_gen_cc-2.params)
Execution platform: @local_execution_config_platform//:platform
bazel-out/k8-opt-exec-50AE0418/bin/_solib_local/_U_S_Stensorflow_Scc_Cops_Sfunctional_Uops_Ugen_Ucc___Utensorflow/libtensorflow_framework.so.2: undefined reference to `std::allocator::allocator()'
collect2: error: ld returned 1 exit status
Target //tensorflow:libtensorflow_cc.so failed to build
INFO: Elapsed time: 1427.425s, Critical Path: 388.90s
INFO: 5225 processes: 5225 local.
FAILED: Build did NOT complete successfully

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
The configuration is here.

You have bazel 3.1.0- (@non-git) installed.
Please specify the location of python. [Default is /mnt/home/gepei/anaconda3/envs/tensorflow_GPU/bin/python3]:
Found possible Python library paths:
/mnt/home/gepei/anaconda3/envs/tensorflow_GPU/lib/python3.8/site-packages
Please input the desired Python library path to use.  Default is [/mnt/home/gepei/anaconda3/envs/tensorflow_GPU/lib/python3.8/site-packages]
Do you wish to build TensorFlow with OpenCL SYCL support? [y/N]:
No OpenCL SYCL support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]:
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.
Do you wish to build TensorFlow with TensorRT support? [y/N]:
No TensorRT support will be enabled for TensorFlow.
Could not find any cuda.h matching version '' in any subdirectory:
''
'include'
'include/cuda'
'include/*-linux-gnu'
'extras/CUPTI/include'
'include/cuda/CUPTI'
of:
'/lib'
'/lib64'
'/opt/dell/srvadmin/lib64'
'/opt/dell/srvadmin/lib64/openmanage'
'/opt/ibutils/lib64'
'/opt/mellanox/hcoll/lib'
'/opt/mellanox/mxm/lib'
'/opt/mellanox/sharp/lib'
'/usr'
'/usr/lib64//bind9-export'
'/usr/lib64/atlas'
'/usr/lib64/dyninst'
'/usr/lib64/mysql'
'/usr/lib64/qt-3.3/lib'
Asking for detailed CUDA configuration...
Please specify the CUDA SDK version you want to use. [Leave empty to default to CUDA 10]:
Please specify the cuDNN version you want to use. [Leave empty to default to cuDNN 7]:
Please specify the locally installed NCCL version you want to use. [Leave empty to use http://github.com/nvidia/nccl]:
Please specify the comma-separated list of base paths to look for CUDA libraries and headers. [Leave empty to use the default]: /mnt/home/gepei/anaconda3/envs/tensorflow_GPU/pkgs/cuda-toolkit/,/mnt/home/gepei/anaconda3/envs/tensorflow_GPU/
Found CUDA 10.1 in:
/mnt/ufs18/home-183/gepei/anaconda3/envs/tensorflow_GPU/pkgs/cuda-toolkit/lib64
/mnt/ufs18/home-183/gepei/anaconda3/envs/tensorflow_GPU/pkgs/cuda-toolkit/include
Found cuDNN 7 in:
/mnt/ufs18/home-183/gepei/anaconda3/envs/tensorflow_GPU/lib
/mnt/ufs18/home-183/gepei/anaconda3/envs/tensorflow_GPU/include
Please specify a list of comma-separated CUDA compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus. Each capability can be specified as "x.y" or "compute_xy" to include both virtual and binary GPU code, or as "sm_xy" to only include the binary code.
Please note that each additional compute capability significantly increases your build time and binary size, and that TensorFlow only supports compute capabilities >= 3.5 [Default is: 7.0,7.0,7.0,7.0]:
Do you want to use clang as CUDA compiler? [y/N]:
nvcc will be used as CUDA compiler.
Please specify which gcc should be used by nvcc as the host compiler. [Default is /opt/software/GCCcore/7.3.0/bin/gcc]:
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native -Wno-sign-compare]:
Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]:
Not configuring the WORKSPACE for Android builds.
Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
--config=mkl         	# Build with MKL support.
--config=monolithic  	# Config for mostly static monolithic build.
--config=ngraph      	# Build with Intel nGraph support.
--config=numa        	# Build with NUMA support.
--config=dynamic_kernels	# (Experimental) Build kernels into separate shared objects.
--config=v2          	# Build TensorFlow 2.x instead of 1.x.
Preconfigured Bazel build configs to DISABLE default on features:
--config=noaws       	# Disable AWS S3 filesystem support.
--config=nogcp       	# Disable GCP support.
--config=nohdfs      	# Disable HDFS support.
--config=nonccl      	# Disable NVIDIA NCCL support.
Configuration finished

Here is the line 629 of /mnt/gs18/scratch/users/gepei/tensorflow/tensorflow/cc/BUILD
tf_gen_op_wrappers_cc(
    name = "functional_ops",
    include_internal_ops = 1,
    op_lib_names = [
        "functional_ops",
    ],
    pkg = "//tensorflow/core",
    visibility = ["//tensorflow:internal"],
)

Can someone help me with that? Thanks a lot.

Fixed by changing gcc from 7.3.0 to 7.5.0


DOM change when leaving a game is based on KickedFromGame event being sent to client.

Should more or less remove these lines:
https://github.com/DATx02-16-14/Hastings/blob/d82283d755abbdeb877599bb512c0ebe4ff20ec8/src/Server/Game.hs#L24-L27
And make sure that the client can update to the correct DOM without them.

Why? Is it a problem as it is?


Seems like it doesn't really spellcheck

Trying to use it in local repo with command:
spellchecker --generate-dictionary --files '**/*.tsx' --ignore '[a-z]+((d)|([A-Z0-9][a-z0-9]+))*([A-Z])?' '([A-Z][a-z0-9]+)((d)|([A-Z0-9][a-z0-9]+))*([A-Z])?' '[^a-zA-Z0-9-]+' '([\\w.]+)' '([\\w-]+)' '([\\w&]+)'

For example, I do an obvious mistake in one of the files - saccessfully, but as a result it prints only: no issues found. Am I doing it wrong?

Thanks for the issue! I wonder if one of the regexes is matching more words than it's supposed to. I'd suggest trying to remove the regexes from the --ignore parameter one at a time and seeing if that changes the output.
Also, is the repo on which you ran the command on the internet anywhere? If so, I can clone it and take a look.

You are right, need some more expertise with the regexp's.

Understood. Let me know if I can help with that. If this isn't an issue with the tool itself, I'll close this issue. Feel free to reopen it there turns out to be a bug :slightly_smiling_face: