Urgent / Critical Problem with 'christitus.com/win' Web Re-direct !!

First notice by the author of this issue ticket
I noticed something odd with an Issue Ticket recently.. it was reporting a problem with Numlock Toggle Tweak (Disable/Enable Numlock on Startup). ( here's a link to that issue )
Of course, when I saw this I said to myself "Well this is weird, this has been reported and fixed by Chris him self.. A WEEK AGO!"
then I looked into the Git Logs trying to find anything out of the ordinary.. nothing weird to see.
tried running WinUtil, and first thought ".. Old Version Maybe?", and indeed.. I was getting an older version (version 24.06.11) instead of the latest version found on GitHub (version 24.06.20, at the time of writing).
Screenshots (evidence to reference)

Additional Info
By looking at this.. it isn't something one person will have, as the issue I've referenced above is by another person, who's probably getting an older version (a version containing the Numlock Bug Issue).
This is a CRITICAL Issue, should be resolved as soon as possible. @ChrisTitusTech

Note for anyone reading this
Please try running WinUtil through the Admin PowerShell Terminal, command: irm christitus.com/win | iex, click the Gear Icon on the top-right corner (Next to the X Icon), and click the About Drop-down Item, see the Version Field, is it up-to-date to the one shown on GitHub Repo? (link to version line in 'winutil.ps1' file)

Looked into the HTTP Requests themselves, and it turns out it was permanently set to re-direct to the winutil.ps1 24.06.11 GitHub Release, here's a link to it
Screenshots

I thaught that this was intentional, because PRs now are made directly to the main branch and the Releases are autocreated when compiling. But I don't remember him actually talking/writing about the way he does the redirects now.

I thaught that this was intentional, because PRs now are made directly to the main branch and the Releases are autocreated when compiling. He once said, that dev users should use the raw link (old method), which is the same as the release version. These would not be Full Version Releases then, therefore the delay in changing the redirect. But I don't remember him actually talking/writing about the way he does/wants to do the redirects nowadays.

The reason behind delaying a release is fair enough, but wouldn't be better if the releases were made manual only?
Of course I don't really know what Chris plan for the "deployment/release model", but testing the changes on the main branch, and reviewing what has changed as well is by far the best thing to do, even though there might be Human error in the process.. and the obvious time sinking it might take.
Just a humble & possible solution that might help
Now I don't know if the idea I'm proposing will work or not.. so take it with a grain of salt 😅
I've thought of a system that might satisfy every need there is.. but at the cost of an extra request (or two) made to GitHub, that being.. just don't download the winutil.ps1 file directly :/
What I mean by that is to have a File in the repo, lets call it winutil_launcher.ps1 for example, and this's the file the User will request, inside that script file you'll have a few lines of code, which figures out what's the latest stable release of WInUtil (like version 24.06.20), with again.. Release being Manual Only.
Now despite being a simple system.. its quite flexible one, I mean if we want, we could implement the a previous idea of mine ( fully explained in issue #2060 ), by making a new file, lets call it winutil_launcher_dev.ps1, which will do:

check if git is installed

Installed? -> Proceed to the next step
Not Installed? -> Try Installing it using Invoke-WebRequest, Chocolatey Package Manager, or WinGet Package Manager (or even an entirely different approach to solving this problem)

do a Shallow Clone of winutil repo into the Temp Folder
[Optional/Recommend Doing] Check & Set Execution Policy, and the Language Mode (if possible)
run the Compile.ps1 script on the Client Computer, then run winutil.ps1 if the Compilation was successful.
Enjoy your Dev Build, which has been Built From Source Code, meaning no Backdoor to speak of, Jai Tan 😉

This of course.. for the Dev Branch, designed for people who want the latest changes/commits (and therefore, the most unstable), aim at testers using Virtual Machines (or just people want to see what's being worked on, and report any issues if encountered), or devs who want to live on the Bleed-Edge 🎸 🩸 , both cases are totally fine IMHO
And most importantly my fellow contributors.. Say Goodbye to Compiled Files (winutil.ps1) in PRs 🕶 😄
Because there'll be no need to ship with winutil.ps1 in the repo, and have Git ignore it completely (using .gitignore file).

Downsides of it is extra time to get the winutil.ps1 file (from GitHub Releases, using their REST API), this is sadly un-avoidable, as more request you make, the after depending on the previous to finish (block requests), the longer you'll have to wait.. this will depend on how close you're to the server (Geolocation relative to the server, at least the closest one), and is your internet stable or not (request might fail, and you'll have to request again, adding more wait time)

I don't have extensive knowledge about cloud environments, but I believe that eliminating the need for client-side setup would significantly enhance the user experience. WinUtil is designed to be modular, and requiring local installation and compilation would undermine the purpose of an invoked script. Ideally, we could implement a trigger that compiles WinUtil using a cloud-based solution like Cloudflare Workers, thereby reducing the burden on the client.
Also if we are using solutions like Workers we could also use them to identify the newest release and use that one for regular users.
Those changes would remove the regional issues that people have (eg. India) because the client does not have to reach github anymore.
Upsides:

Devs compile the newest version without the need of any setup/Client ressources.
Github Domain Blocking won't be a big problem anymore
better Management of Releases
Less API reqests to GitHub

Downsides:

Potential additional costs (Cloudflare is known for generous pricing)
Could reduce/increase loading time, but Cloudflare is known to be fast.

Another different idea I proposed in a issue (I don't exactly remember when) would be to implement a model like Microsoft with the winget repo where new commits are automatically generated and marked as pre release
Then the compilation of a new stable release could be triggered manually

Another idea - have a winutildev github where people can do PR's on and that is a testing ground then when it is tested and good it gets transfered to the main winutil page for stable release.

Another idea - have a winutildev github where people can do PR's on and that is a testing ground then when it is tested and good it gets transfered to the main winutil page for stable release.

That would be similar to the old method of using a testbranch. I don't know how well liked that would be thinking about we "just" switched from an idea like that.
I personally would also prefer to have a project on one repository, to keep maintainability and reduce confusion.

Another idea - have a winutildev github where people can do PR's on and that is a testing ground then when it is tested and good it gets transfered to the main winutil page for stable release.

That would be similar to the old method of using a testbranch. I don't know how well liked that would be thinking about we "just" switched from a similar setup.
I personally would also prefer to have a project on one repository, to keep maintainability and reduce confusion.
But it does also have its ups, so I think the best way would be to merge ideas from this issue to come up with a solution.
I propose following combination of Ideas:

The solution from Marerich is in my opinion almost a must have at this point.
We could combine that with a Cloudflare worker, to always get the newest release/prerelease and link it to the url (christitus.com/win & christitus.com/windev), so that this doesn't have to be done manually and users can use WinUtil even with the blocked GitHub url in some countries.
Pre-Releases will still get released automatically at compilation
Full releases have to be done manually

Nice summary @MyDrift-user 👍
All the points you provided are well done, and of course, even if we couldn't do the Cloudflare part, we could do a workaround to achieve a similar result.

If we want to fix that, we'll have to make it so the user never actually has to make a request to github himself, which is as you said difficult without another provider/temp. hoster/...
The Idea I had with the worker is following:

user makes request to domain
cloudflare worker gets newest release/prerelease and hosts it himself.
user gets access to that "self" hosted file, not having to make a request himself to github.com/githubusercontent.com

The Idea came because I once heard (or thaught i heard) Chris talking about his website, that is apparently also hosted on cloudflare using cloudflare pages, so the domain would already be linked to cloudflare making that the easiest setup when needing another provider than GitHub.
That was also just a random idea I had, but I'm not a Web Dev either ...

I would actually argue, that using a CDN like Cloudflare is not really necessary at all.
Chris already hosts his own website (the hosting provider really doesn't matter) and winutil itself (at least at the moment) is quite small, so nothing would prevent a script or GitHub Action to run, that simply copies winutil onto the Webserver so that it could be queried from there.
Of course like this, Chris's Webserver would need to handle the load and the traffic of the users downloading the script which directly correlates to potentially higher prices (which are not necessary when fetching from GitHub)

I would actually argue, that using a CDN like Cloudflare is not really necessary at all.
Chris already hosts his own website (the hosting provider really doesn't matter) and winutil itself (at least at the moment) is quite small, so nothing would prevent a script or GitHub Action to run, that simply copies winutil onto the Webserver so that it could be queried from there.
Of course like this, Chris's Webserver would need to handle the load and the traffic of the users downloading the script which directly correlates to potentially higher prices (which are not necessary when fetching from GitHub)

Well the handling and responsibility of making it work is quite daunting, as according to Chris, every day, more than 10 thousand requests are made to christitus.com/win.. which will make changing things a bit difficult + depending on what web service Chris uses for hosting, DDOS attacks will be annoying to handle (not if, but when they happen)

Edit: the discussion drifted from "how to fix an url" over, "how to setup the releases better" to "how to fully revamp the whole script distribution".
I think those are all valid points that can be discussed, but it should probably be done in separate threads (e.g. separate discussion topics) and not all jumbled together in this issue

True 😂
Overall, I had fun discussing the different ideas and possible solutions to use to make the Distribution process more streamlined and better on both the Devs and Users.. but it's better to discuss it in a separate issue ticket (we shouldn't drift further from the main topic at hand).

@og-mrk @Marterich @MyDrift-user Great suggestions all!
I really like the latest release and pre-release approach with a manual full release.
Website is actually hosted on cloudflare using github... which is pretty much how winutil is handled hehe. So I don't have a "host" per se because it is distributed like a netlify static site using Cloudflare CDNs that are copied from the website repo. This makes my website have no attack surface and fast.
Winutil link from christitus.com/win is because I'm lazy and wanted a smaller url to type. I love the idea of just linking this to latest and dev making another windev url.
Thank you!

@ChrisTitusTech Take a look at #2060 Regarding the dev url (together with pre-releases) there @og-mrk and I discussed this a bit more in detail already :)

@Marterich merged this in and I really like it. One thing I need a bit of clarity on is there a global "pre-release" tag like there is on latest?
I switched the christitus.com/win link to push to latest, but I wanted to make a christitus.com/windev link to the "latest pre-release"

@Marterich merged this in and I really like it. One thing I need a bit of clarity on is there a global "pre-release" tag like there is on latest? I switched the christitus.com/win link to push to latest, but I wanted to make a christitus.com/windev link to the "latest pre-release"

Yes there is. I think this is what you mean.

@Marterich merged this in and I really like it. One thing I need a bit of clarity on is there a global "pre-release" tag like there is on latest? I switched the christitus.com/win link to push to latest, but I wanted to make a christitus.com/windev link to the "latest pre-release"

@ChrisTitusTech Annoyingly I think not really.

HTML site that queries the Latest dev Release via JS
   <!DOCTYPE html>
<html>
<head>
    <script>
        // Function to fetch the latest release tag from the GitHub API
        async function getLatestRelease() {
            try {
                const response = await fetch('https://api.github.com/repos/ChrisTitusTech/winutil/releases');
                const releases = await response.json();
                const preRelease = releases.find(release => release.prerelease);
                return preRelease.tag_name;
            } catch (error) {
                console.error('Error fetching release data:', error);
                return null;
            }
        }

        // Function to redirect to the latest pre-release version
        async function redirectToLatestPreRelease() {
            const latestRelease = await getLatestRelease();
            if (latestRelease) {
                const url = `https://raw.githubusercontent.com/ChrisTitusTech/winutil/${latestRelease}/winutil.ps1`;
                window.location.href = url;
            } else {
                console.error('Unable to determine latest pre-release version.');
            }
        }

        // Call the redirect function when the page loads
        window.onload = redirectToLatestPreRelease;
    </script>
</head>
<body>
    Redirecting to the latest pre-release version...
</body>
</html>

This will still not solve the issue because afaik there's no option in PS to Download and Run a Website including JS
Idea 1:
Create a job that periodically downloads the script onto your webserver or create a Github Action that uploads the file via FTP
Idea 2:
Check if you can set your DNS Entries via API. That way you could create a GitHub Action that dynamically updates the CloudFlare DNS Record.
Idea 3:
I'll see if it's possible to create a small PowerShell Script that can be embedded as text which will act as a loader to fetch the newest Version. I'll update the commend if I manage to create it :)

Edit: Create the following static page on your windev link. If this is invoked via irm https:/[...] | iex it'll query the newest pre-release, and run it.

Very cool and works super fast.
If there is no network the dev still gets a error because we are using write-error:
Get-LatestRelease : Error fetching release data: The remote name could not be resolved: 'api.github.com'
At C:\Users\SOMEONE\Desktop\test.ps1:15 char:22
+     $latestRelease = Get-LatestRelease
+                      ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-LatestRelease

These don't really help in this case, so I would personally suggest a write-host maybe with -ForegroundColor Red to keep it clean, it still see the most important infos if there is an issue.

@MyDrift-user Even though I think this is really a case that should pretty much never occur, I updated my code snippet in the comment.
Also, I added logic to pull the latest full release if no pre-releases should exist.

The Solution would be to just take the newest release no matter what kind it is. (I don't mean the tag "latest")
$preRelease = $releases | Select-Object -First 1

@ChrisTitusTech @MyDrift-user
I created a linked PR that initializes the file at the base of the repo and describes what link needs to be done to get https://christitus.com/windev to work


Fix production build

Fix production build with electron and webpack
I started fixing this issue here https://github.com/guildspeak/guildspeak-desktop/tree/fix/build

fixed in https://github.com/guildspeak/guildspeak-desktop/commit/09a1778f93c44e08c6691bc912471ffacdb3aef2


Document how to implement mixin commands

Got excited and documented all the commands.
Closes #216
Preview available at https://deploy-preview-221--porter.netlify.com/mixin-commands/

@jeremyrickard Let me know how this matched up to what you had to implement for the kubernetes mixin.

That checks out pretty well. Couple of small comments inline

Good catch, fixed!

CI is stuck but the doc changes are in. Merging with my mega root. 💪


Can't make a pre-selection

I have a user profile with his mobile number and want to show the ( flag +XX ) next to it.
but I'm not able to get the country object before the selection
can you help me with that please..

Nice Thanks it's working fine now  👍🏻


Cell render with asynchronous modal window

It hurts me when I want to derive my own view and use the asynchronous modal:
TD::set('email')->loadModalAsync('oneAsyncModal', 'saveUser', 'id', 'email');

This approach involves only plain text output. If I want to call my own render, then it completely replaces the window call. This is because the loadModalAsync method is a private add-on for render. The only way out now is to use macros #785
I think we can change the method loadModalAsync completely removing the last argument
TD::set('email')
    ->loadModalAsync('oneAsyncModal', 'saveUser', 'id')
    ->render(function (Repository $repository){
        return $repository->get('email');
    })

This can cause conflicts, so it’s good to rename the method, and leave depricated for the current one.
TD::set('email')
    ->toggleAsync('oneAsyncModal', 'saveUser', 'id')
    ->render(function (Repository $repository){
        return $repository->get('email');
    })

Yeah i think this is much better


Adjust DataTable to respect the :keys order

Closes #150.
Sidenote: Table.to_rows_with_info/2 always returns all columns in info, but I think info is more about the table itself, rather than the specific rows. @josevalim wdyt?

Yeah, we shouldn’t prune “info”.


#2014 Support k0s

Add support for k0s #2014

Thanks! Small nitpick on the changelog and ready to go!

Done for the changelog


Configurable precision for fields

Currently, distances are rounded to the nearest 10th of a mile using parseFloat().toFixed(1)
Rather than dictate the precision, move this to a configuration option with a sensible default, and apply across all fields.

This has been fixed at f081f2834dda1c54e92fa313b7d98c58e3418d8f


Update docfx.json

Add contrib to exclude.

Docs Build status updates of commit 5980208:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

sharepoint/docfx.json
:x:Error

Details

sharepoint/docfx.json

Line 45, Column 6: [Error: json-syntax-error] After parsing a value an unexpected character was encountered: ".

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

sharepoint/docfx.json
:white_check_mark:Succeeded

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

@JohanFreelancer9

@yogkumgit  This is probably better suited for @traya1 's review

Agree with @get-itips.


Invite users button is broken

Clicking it makes it pop up and immediately close the window again

Is happening again on staging


MoprhoMetriX not working for Mac Os < 11.0.0

Software can be installed, but cannot open. Issue due to PyQt6 framework. Using Mac Os Catalina (10.15.7), intel chip. Tried opening software through terminal and this was the error message: Sorry, "MorphoMetriX" cannot be run on this version of macOS. Qt requires macOS 11.0.0 or later, you have macOS 10.15.7.

PySide6 versions 6.4.3+ dropped support for Mac OS Catalina 10.X, will downgrade future versions to 6.4.3.

Version 2.2.0 should solve this issue.


Support for use without import 'bdsm'

Not all projects support ES6. Anyway to get it to work without import 'bdsm'
by using a script tag?

You can use BDSM by including it using a script tag after installing it from npm
<script src="../node_modules/bdsm/dist/bdsm.js"></script>
Or you can use unpkg which serves npm packages over CDN
<script<EMAIL_ADDRESS>


containerservice: adding support for Custom Headers

Fixes https://github.com/Azure/AKS/issues/2757
Unblocks https://github.com/hashicorp/terraform-provider-azurerm/issues/6793
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

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

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

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

Change to data plane APIs
Adding new properties
All removals

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

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

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

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

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@tombuildsstuff - thanks for the energy on this topic (and for the PR).
I'll be honest: We don't love the way we're using headers to configure feature enablement right now. It has a lot of flaws, not the least of which as you've pointed out is that it's not "officially documented" in the REST API. It also doesn't work with ARM templates, you can't always easily see what feature's you turned on after the fact, and so on (there are a lot of flaws).
I'm not sure if you've noticed but we've recently starting publishing -preview APIs alongside the standard ones. One of the reasons for that is we're trying to tackle this problem more holistically by letting preview features get placed into the -preview API in a way that solves a lot of the above problems:

It allows users to set and get feature enablement via all interfaces equally well (ARM templates, SDKs, CLI, etc)
It gives us a more clear out if that feature never makes it to GA, as opposed to the ambiguous world of headers today.

Unfortunately that means we really would like to be moving in the opposite direction here: Less headers, less support (and use) of headers, until we can eventually stop supporting them altogether (that's probably a ways off but it's the goal). Adding the headers explicitly to the API doesn't solve any of their other problems and also commits us to supporting the pattern for longer than we'd like.

@matthchr I understand the desire to move away from this - but as these are supported today they should be documented in the Swagger? Future API versions can opt to remove this field once it's no longer used, but as this API Version supports this field it should be documented, as it's optional and isn't returned from the API - removing this isn't a breaking change.
cc @JeffreyRichter since I've seen this a few times and I'm wondering if there's some guidance missing from the ARM docs here?

@tombuildsstuff , this PR is pending for your action to move on. Either get breaking change approval or revert those changes that caused breaking.  Another action is to fix CI check failures.

@raych1 this PR is waiting on the SDK/ARM Team to decide how to proceed: https://github.com/Azure/azure-rest-api-specs/pull/18232#issuecomment-1068300285
If the API no longer supports these fields as of today then that's fine and we can close this PR, since this PR is no longer up to date - but if the API still accepts these values then the Swagger should be updated to account for this, even if the intention is to deprecate/remove support for this in a future API Version (which can be done when there's no remaining features using this method).

If the API no longer supports these fields as of today then that's fine and we can close this PR, since this PR is no longer up to date - but if the API still accepts these values then the Swagger should be updated to account for this, even if the intention is to deprecate/remove support for this in a future API Version (which can be done when there's no remaining features using this method).

As of today all 4 possible usages for these headers are deprecated. No new usages are being added. It is true that existing APIs will continue accepting the headers for the k8s versions listed above until they go out of support, but given their deprecated status we believe it doesn't make sense to add them to the stable Swagger at this time. Headers for all of the
@tombuildsstuff, thanks for this PR. I'm going to close it given the above status. We really appreciate the conversation that it drove here as well as internally. Please feel free to respond if you strongly disagree and we can continue the discussion. Note that https://github.com/hashicorp/terraform-provider-azurerm/issues/6793 lists a bunch of headers for various features (Gen2 Vms, Ephemeral OS, containerd, Ubuntu 18.04). None of the headers for those features are supported anymore anyway (they all don't do anything)

If the API no longer supports these fields as of today then that's fine and we can close this PR, since this PR is no longer up to date - but if the API still accepts these values then the Swagger should be updated to account for this, even if the intention is to deprecate/remove support for this in a future API Version (which can be done when there's no remaining features using this method).

As of today all 4 possible usages for these headers are deprecated. No new usages are being added. It is true that existing APIs will continue accepting the headers for the k8s versions listed above until they go out of support, but given their deprecated status we believe it doesn't make sense to add them to the stable Swagger at this time. Headers for all of the
@tombuildsstuff, thanks for this PR. I'm going to close it given the above status. We really appreciate the conversation that it drove here as well as internally. Please feel free to respond if you strongly disagree and we can continue the discussion. Note that hashicorp/terraform-provider-azurerm#6793 lists a bunch of headers for various features (Gen2 Vms, Ephemeral OS, containerd, Ubuntu 18.04). None of the headers for those features are supported anymore anyway (they all don't do anything)

@matthchr
Maybe it is not the right place, but I would love to know what happend to first point:
Using GPU VHD images
Will these images be discontinued?

@matthchr - existing APIs still support these, even if deprecated, so they are valid, people are using them, and should be represented in swagger

Using GPU VHD images

we're focusing on optimizing the vanilla images for latency. the behavior is very nearly identical today. the main other difference is the nvidia device plugin. that is relatively easy to deploy as an end-user, or if there's demand we can expose that via normal APIs separately.
for bonus points: with an expanding range of skus, we need to pivot driver version based on GPU model, which defeats the purpose of the preinstalled drivers, and actually added latency in some cases :/

When will the GPU VHD image functionality be supplanted by the so called vanilla images? And by that point will all the GPU VHD images be phased out completely i.e. users will not be able to use or set them in the headers anymore?


python311Packages.pyunifiprotect: 4.10.2 -> 4.10.3

Diff: https://github.com/briis/pyunifiprotect/compare/refs/tags/v4.10.2...v4.10.3
Changelog: https://github.com/AngellusMortis/pyunifiprotect/releases/tag/v4.10.3
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 237211 run on x86_64-linux 1

7 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
python310Packages.pyunifiprotect.dist
python311Packages.pyunifiprotect
python311Packages.pyunifiprotect.dist
unifi-protect-backup
unifi-protect-backup.dist


Compilation Error: Sketch uses 1839173 bytes (140%) of program storage space.

When I compile I get the following error:
"Arduino: 1.8.13 (Windows 10), Board: "TTGO T1, Default 4MB with spiffs (1.2MB APP/1.5MB SPIFFS), 240MHz (WiFi/BT), QIO, 80MHz, 4MB (32Mb), 921600, None"
Sketch uses 1839173 bytes (140%) of program storage space. Maximum is 1310720 bytes.text section exceeds available space in board
Global variables use 116472 bytes (35%) of dynamic memory, leaving 211208 bytes for local variables. Maximum is 327680 bytes.
Sketch too big; see http://www.arduino.cc/en/Guide/Troubleshooting#size for tips on reducing it.
Error compiling for board TTGO T1."
Has anyone else had the same problem ? and how did you fix it.  I would be happy to lose some of the extensive range of features but I don't know where to start doing that.

Looks like you have way to much Global variables set.
Make sure to define more static and const types.
Make sure to omit the use of String types.
Whenever you use statements like Serial prints that show values, try to do it like this:
Serial.print(F(“Temperature value:”)); // The F() function places the static value in STATIC MEMORY
Serial.println(integerValueTemperature); // This “embeds” the String and Integer value in a single message
Serial.flush(); // This flushes the information before continuing (just a best practise)
Try to reuse larger variables and do what is advised; check the Sketch too big URL.
Regards,
Eric

On 30 Dec 2020, at 23:35, nickw56<EMAIL_ADDRESS>wrote:
When I compile I get the following error:
"Arduino: 1.8.13 (Windows 10), Board: "TTGO T1, Default 4MB with spiffs (1.2MB APP/1.5MB SPIFFS), 240MHz (WiFi/BT), QIO, 80MHz, 4MB (32Mb), 921600, None"
Sketch uses 1839173 bytes (140%) of program storage space. Maximum is 1310720 bytes.text section exceeds available space in board
Global variables use 116472 bytes (35%) of dynamic memory, leaving 211208 bytes for local variables. Maximum is 327680 bytes.
Sketch too big; see http://www.arduino.cc/en/Guide/Troubleshooting#size http://www.arduino.cc/en/Guide/Troubleshooting#size for tips on reducing it.
Error compiling for board TTGO T1."
Has anyone else had the same problem ? and how did you fix it. I would be happy to lose some of the extensive range of features but I don't know where to start doing that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/wfdudley/T-watch-2020/issues/16, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCG53QTFJICOC7NRUEQRADSXOTJLANCNFSM4VOZBSPA.
[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/wfdudley/T-watch-2020/issues/16", "url": "https://github.com/wfdudley/T-watch-2020/issues/16", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Your partitioning is wrong.  You need to use the special partitioning for the T-watch-2020, which is:
2x6.5 MB APP, 1.5MB SPIFFS
I am fully aware of all the things genotix has mentioned, but thank you for the suggestions.

Thanks for your reply.  Where/how do I change this ?  In my Arduino IDE/tools/partioning scheme there is no option that matches this and I can't see an option to add a new scheme.
Apologies if I am missing something obvious - I am a 64 year old novice so your patience and assistance is much appreciated.

I just did a completely fresh install of Arduino and "all the fixin's" to
see how this worked.
Once I installed the esp32 support package, and selected "TTGO T-watch"
from the "espArduino" in the "Tools/Board:" dropdown menu,
the proper partition scheme was automatically set.  I didn't have to touch
this option.
Bill Dudley
This email is free of malware because I run Linux.
On Thu, Dec 31, 2020 at 5:17 AM nickw56<EMAIL_ADDRESS>wrote:

Thanks for your reply. Where/how do I change this ? In my Arduino
IDE/tools/partioning scheme there is no option that matches this and I
can't see an option to add a new scheme.
Apologies if I am missing something obvious - I am a 64 year old novice so
your patience and assistance is much appreciated.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/wfdudley/T-watch-2020/issues/16#issuecomment-752914721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI4VYU7R7F6EF32Z2JOKWMTSXRFRZANCNFSM4VOZBSPA
.

Hi Bill
I got it working using one of the Huge App scheme.  It's absolutely the best T-watch version I have tried so far.  If I encounter any further issues I will try re-installing the Arduino IDE and see if that gives me the scheme you reccommended.
In the meantime- many thanks and all the best for 2021
Nick


fix: fix attach / provision bug

What type of PR is this?
/kind bug

What this PR does / why we need it:

modify csi-attacher and csi-provisioner timeout and crd provisioner polling timeout to avoid errors from mismatch in timeouts
use deepcopied version of cri to feed cloud provisioner to avoid unwanted updates
fix other minor bugs

Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build 988140338

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.2%) to 53.243%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/provisioner/crdprovisioner.go
0
6
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/provisioner/crdprovisioner.go
2
0%

Totals

Change from base Build 987756943:
0.2%

Covered Lines:
2512

Relevant Lines:
4718

💛  - Coveralls


⚠ Bofrost.at has degraded performance

In c725e2d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2199 ms

Resolved: Bofrost.at performance has improved in 4c042ec.


ipvlan: clean up leftover  in setupBaseDevice()

commit c3adaec9dc06a68 removed IPVLAN code, clean up setupBaseDevice().
found this through https://github.com/cilium/cilium/issues/20603
don't think IPVLAN leftover code is related to that issue. clean it up
Signed-off-by: Vincent Li<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Thanks for contributing!

Fixes: #issue-number
clean up IPVLAN leftover code  in setupBaseDevice()

/test

/test
Job 'Cilium-PR-K8s-1.24-kernel-net-next' failed:
Click to show.

seems related to https://github.com/cilium/cilium/issues/13236, not related to this PR @tklauser

/test-1.24-net-next

Marked for backport to v1.12 because #20453 was also backported and there's merge conflicts when backporting #20734.


WIP: Fixed oddities caused by change to Goldmark renderer

Fixes #1891

Preview : https://deploy-preview-1898--competent-brattain-de2d6d.netlify.com/

/assign @sarahmaddox
I have fixed most of the formatting issues, except 2 files, in which the numbered lists are broken after shortcode. I will fix that in a separate PR.

@sarahmaddox
This PR is ready to be reviewed.

Well done and thank you for the sterling work @janeman98!
/lgtm
/approve

Thanks @sarahmaddox !


Navbar CSS and JS

Now that the navbar has been modularized, the CSS needs to be more explicitly defined and less susceptible to inheritance, such as bootstrap versions, hydroshare_core.css,

Discussed with @martinseul and we are closing this issue.


Fix #130

closes #130

Codecov Report

Merging #229 (9dca9a0) into master (a78a53d) will decrease coverage by 0.32%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #229      +/-   ##
============================================
- Coverage     66.68%   66.35%   -0.33%
  Complexity      564      564
============================================
  Files            96       96
  Lines          2026     2036      +10
  Branches        208      208
============================================
  Hits           1351     1351
- Misses          603      613      +10
  Partials         72       72

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/LoginScreen.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/SetUpScreen.java
0.00% <0.00%> (ø)

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 a78a53d...9dca9a0. Read the comment docs.


Developing an InstanSegModel class

Somewhat related to #17, I made an implementation of a python class which has similar syntax/usage to Cellpose and Stardist. Ideally, this would mean that you can use InstanSeg like this:
nuclei_mod_is = InstanSegModel("fluorescence_nuclei_and_cells", gpu=True)
image = "cells_000.tif"
label_image = nuclei_mod_is.predict(image, pixel_size=0.5, normalize=True)

I've tested a bunch of the features, as well as implementing usage on generic numpy arrays (rather than relying on AICSImage, which may not be able to handle all image types)

This looks really good! Thanks for proposing it. I think a lot of the same ideas are implemented now in the InstanSeg class, hopefully covering all the use cases you were aiming for (ideally more)

Great! Yeah I was going to close this as most of this got implemented.


[SUGGESTION] Numbers obfuscation

Description
I suggest add a second way to obfuscate numbers. You know what we can obfuscate numbers by their transform in to math expression (like 1 = 0 + 0 + 0 + 1 or something like this)
Short example of transform:
40000 === (-0x33a4+0x47b*0x3+0x4d43+(0xcd*-0x29+-0xbf0+0x53d5)+(-0x3ede+-0x9*-0xd3+-0xf*-0x64d)+(-0x2c0a+-0x5d*0x6c+0x7a56))// true

But this is easy to check (transofrm back) in to number.
You should just input this value in to console (or create regexp for auto replace this, right?)

What if we do some better (stronger but harder) for numbers?
Code examples
I suggest something like this:
// original code
const number = 1000;
console.log(number);

// obfuscated code

const global = [...,
-0x7 * 0x2ea + 0x1838 + 0xb * 0x2 // === 1000
, ...] // this is array with all words, numbers etc
// ...
const number = getFromGlobal("0x99") // I just input any random offset, this function would return value (-0x7 * 0x2ea + 0x1838 + 0xb * 0x2) === 1000 and this is END.
console.log(number); // return 1000
// ...

This is very simple and ... mb fast choice.
Second is better but maybe slow?
// obfuscated code

// note:
// 1. We transofrm 1000 in to -0x7 * 0x2ea + 0x1838 + 0xb * 0x2
// 2. We move "-0x7", "0x2ea" and etc in to global array.
// 3. We call (get) values by

const global = [
...,
-0x7,  0x2ea, 0x1838, 0xb, 0x2,
...
] // this is array with all words, numbers etc
// ...

const number = getFromGlobal("0x99") * getFromGlobal("0x100") + getFromGlobal("0x101") * getFromGlobal("0x102")
// this expression the same like if we input -0x7 * 0x2ea + 0x1838 + 0xb * 0x2.
// We also can don't input -0x7 in to global array, move WITHOUT minus symbol (0x7) and then call -getFromGlobal("0x99") === -0x7 // true
console.log(number); // return 1000
// ...

Differents between first and second ways.
First way
Minuses

too simple
too pure (I mean dumb)
you can find in global array completed number value (I mean value: 1000)

Pluses

simple (lol)
fast (mb)
don't hard

Second way
Minuses

slow (mb, but not too slow, a bit slow I suppouse)
mb harder like first way (I mean for write code)

Pluses

you can't saw completed number in to array (i.e while debug or etc), this is BIG-BIG PLUS.
you can't create simple regexp for transform all number expression in to completed numbers.

Example what you see in global array with first way:
[
...
// you CAN find value "1000".
1000, // === -0x7 * 0x2ea + 0x1838 + 0xb * 0x2
...
]

Example what you see in global array with second way:
[
...
// you CAN'T find value "1000".
7, // ===  0x7 || -7 === -0x7
746, // === 0x2ea
746, // === 0x2ea
6200, // === 0x1838
11, // === 0xb
2, // === 0x2
...
]

A bit suggestion
In my example I use offsets like 0x99,..., 0x101. I think we should NOT insert values in to array with offset + 1 (like from 99 to 101). We should set random offset for every value, string, number and etc. All empty values we should fill by random numbers, strings and etc. On my mind.

Hmm. I check latest obfuscate and don't sure. Did you already do this things?
const _0x3dd1af = -parseInt(_0x3e77f1('0x1df', 'Iwf!')) * parseInt(_0x3e77f1('0x1d4', 'T3Yn')) + -parseInt(_0x3e77f1(0x1eb, 'Mj)N')) + parseInt(_0x3e77f1('0x1d7', '4L!V')) + -parseInt(_0x3e77f1('0x1c6', 'w&3F')) + parseInt(_0x3e77f1('0x1c3', '9Hee')) * parseInt(_0x3e77f1('0x1c1', 'VfXV')) + -parseInt(_0x3e77f1(0x1db, '#fX[')) * -parseInt(_0x3e77f1('0x1d2', 'Qc1o')) + parseInt(_0x3e77f1('0x1e9', 'mLtg')) * parseInt(_0x3e77f1('0x1d8', 'jGz^'));

const _0x3dd1af = -parseInt(_0x3e77f1('0x1df', 'Iwf!')) * parseInt(_0x3e77f1('0x1d4', 'T3Yn')) + -parseInt(_0x3e77f1(0x1eb, 'Mj)N')) + parseInt(_0x3e77f1('0x1d7', '4L!V')) + -parseInt(_0x3e77f1('0x1c6', 'w&3F')) + parseInt(_0x3e77f1('0x1c3', '9Hee')) * parseInt(_0x3e77f1('0x1c1', 'VfXV')) + -parseInt(_0x3e77f1(0x1db, '#fX[')) * -parseInt(_0x3e77f1('0x1d2', 'Qc1o')) + parseInt(_0x3e77f1('0x1e9', 'mLtg')) * parseInt(_0x3e77f1('0x1d8', 'jGz^'));

Hi. This is a new rotateStringArray mechanisn

I think it will slow down the code, so you need to obfuscate only tiny part of all number literals. Maybe add threshold field to config also.
Adding some letters after number also will be useful, same to new stringArrayRotation. parseInt("1234blablabla") == 1234
Also I think it should go after numbers to expression transformation.


DELIA-41812: Network Plugin Issues

Reason for change: Modify ping and trace endpoint validation and return trace output as a list
Test Procedure: Build arris xi6 and test based on README.md
Risks: Low
Signed-off-by<EMAIL_ADDRESS>Signed-off-by<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Mariusz Strozynski seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Question: What exactly is cached in onDemandEntries?

[x] I have searched the issues of this repository and believe that this is not a duplicate.

According to the docs a page is cached for 25sec in development by default. However, when you change something on the API-side or even in the JSX of a page, the page will update (both by HMR and when calling manually using F5).
So I'm curious, what exactly is cached here, what exactly do you specify with maxInactiveAge?
Your Environment

Tech
Version

next
5.0.0

node
9.5.0

OS
Win10

When you don't access the page for x time it will be removed from webpack compilation till you ask for it again through accessing it.
The x time is maxInactiveAge


Submit VCell <IP_ADDRESS>

id: vcell
version: <IP_ADDRESS>
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_VCell/aa8a4a44ae637b7245beb9adc46f3100fc0d052e/biosimulators.json
specificationsPatch:
version: <IP_ADDRESS>
image:
url: ghcr.io/biosimulators/biosimulators_vcell/vcell:<IP_ADDRESS>
validateImage: true
commitSimulator: true

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

The validation/submission of your simulator failed.
- 422 Client Error: Unprocessable Entity for url: https://api.github.com/repos/biosimulators/Biosimulators/issues/144/comments

The complete log of your validation/submission job, including further information about the failure, is available here.
Once you have fixed the problem, edit the first block of this issue to re-initiate this validation.
The BioSimulators Team is happy to help. Questions and feedback can be directed to the BioSimulators Team by posting comments to this issues that reference the GitHub team @biosimulators/biosimulators (without the backticks).

I'll have to look into why the GitHub API isn't accepting this.
Here's the test results: https://github.com/biosimulators/Biosimulators/suites/2310305992/artifacts/48497166.

I am wondering if it is related to the failures created by GitHub file permission issue/error thrown by jsbml library when trying to initialize log4j appenders. Akhil will try a patch to the library.
Ion
Sent from my iPhone, please excuse any typos.
On Mar 21, 2021, at 18:36, Jonathan Karr @.***> wrote:

*** Attention: This is an external email. Use caution responding, opening attachments or clicking on links. ***
I'll have to look into why the GitHub API isn't accepting this.
Here's the test results: https://github.com/biosimulators/Biosimulators/suites/2310305992/artifacts/48497166https://urldefense.com/v3/__https://github.com/biosimulators/Biosimulators/suites/2310305992/artifacts/48497166__;!!N0rdg9Wr!7j3CW_njrpi30FNSpwNKQcZnde-sinPXJvrGYf8Kxz-Yur-SEAr8T4AcqfHekA$.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/biosimulators/Biosimulators/issues/144*issuecomment-803672115__;Iw!!N0rdg9Wr!7j3CW_njrpi30FNSpwNKQcZnde-sinPXJvrGYf8Kxz-Yur-SEAr8T4Ar4jeU1g$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABYODNT2X4PW2P66RYIR3ELTEZYFFANCNFSM4ZR75B4A__;!!N0rdg9Wr!7j3CW_njrpi30FNSpwNKQcZnde-sinPXJvrGYf8Kxz-Yur-SEAr8T4BOHp4_bw$.

I don't think these are related. I would guess the error is due to one of two things:

The message body is too long for GitHub.
The message body contains an invalid character that must be escaped.

When I have time, I can figure out what's going on.
In case of errors like this, the results are always saved as an "artifact" file. A link to this file is available from the bottom of the run (e.g., https://github.com/biosimulators/Biosimulators/actions/runs/674101685). I should be able to determine the link and post it to the GitHub issue.


KAFKA-8513: Add kafka-streams-application-reset.bat for Windows platform

For improving Windows support, this PR adds a batch file correponding to bin/kafka-streams-application-reset.sh.
I Ran the added batch file and confirmed it worked on Windows 10 as follows:
PS C:\kafka-trunk> .\bin\windows\kafka-streams-application-reset.bat --application-id streams-pipe --input-topics streams-plaintext-input --to-earliest

(snip)

Reset-offsets for input topics [streams-plaintext-input]
Following input topics offsets will be reset to (for consumer group streams-pipe)
Topic: streams-plaintext-input Partition: 0 Offset: 0
Done.
Deleting all internal/auto-created topics for application streams-pipe
Done.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Overall LGTM.
Call for second review @guozhangwang @bbejeck @ewencp

Thanks for the PR @sekikn!


Adds ability to set last reconciliation date to MockPumpManager

This allows for being able to more easily test stale pump data.  (You'll need to delete any pump data first)

It looks like once set, it can't be unset?

@ps2 yeah, good catch.  I'll add something to make it possible.


test_inspect_cfg access violation

The test suite sporadically fails on 64 bit Windows in: numba/tests/test_dispatcher.py
The backtrace is like:
======================================================================
ERROR: test_inspect_cfg (numba.tests.test_dispatcher.TestDispatcherMethods)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "<path_to_env>numba\tests\test_dispatcher.py", line 511, in test_inspect_cfg
    cfgs = foo.inspect_cfg()
  File "<path_to_env>numba\dispatcher.py", line 376, in inspect_cfg
    for sig in self.signatures)
  File "<path_to_env>numba\dispatcher.py", line 376, in <genexpr>
    for sig in self.signatures)
  File "<path_to_env>numba\dispatcher.py", line 373, in inspect_cfg
    return lib.get_function_cfg(fname)
  File "<path_to_env>numba\targets\codegen.py", line 302, in get_function_cfg
    dot = ll.get_function_cfg(fn)
  File "<path_to_env>llvmlite\binding\analysis.py", line 28, in get_function_cfg
    ffi.lib.LLVMPY_WriteCFG(func, dotstr, show_inst)
WindowsError: exception: access violation reading 0x000000000000000E

----------------------------------------------------------------------
Ran 6643 tests in 267.821s

FAILED (errors=1, skipped=84, expected failures=6)

Slightly suspicious this has the same root cause as: https://github.com/numba/numba/issues/2436

Not the same root cause, seems to be an issue solely on 64bit windows.

Just ran into this issue with Linux builds of Numba 0.38.0 on Python 3.5. Not sure if it is the same error, but it does trace back to test_inspect_cfg.
Fatal Python error: Segmentation fault

Current thread 0x00007f8d0d26e700 (most recent call first):
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/llvmlite/binding/ffi.py", line 107 in __call__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/llvmlite/binding/analysis.py", line 28 in get_function_cfg
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/targets/codegen.py", line 298 in get_function_cfg
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/dispatcher.py", line 403 in inspect_cfg
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/dispatcher.py", line 406 in <genexpr>
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/dispatcher.py", line 406 in inspect_cfg
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/tests/test_dispatcher.py", line 566 in test_inspect_cfg
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/case.py", line 605 in run
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/case.py", line 653 in __call__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/suite.py", line 122 in run
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/suite.py", line 84 in __call__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/suite.py", line 122 in run
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/suite.py", line 84 in __call__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/suite.py", line 122 in run
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/suite.py", line 84 in __call__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/runner.py", line 176 in run
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/main.py", line 256 in runTests
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/testing/main.py", line 211 in run_tests_real
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/testing/main.py", line 226 in runTests
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/unittest/main.py", line 95 in __init__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/testing/main.py", line 127 in __init__
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/testing/__init__.py", line 70 in run_tests
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/runtests.py", line 23 in _main
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/site-packages/numba/runtests.py", line 116 in <module>
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/runpy.py", line 85 in _run_code
  File "/home/conda/feedstock_root/build_artifacts/numba_1525055584125/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.5/runpy.py", line 193 in _run_module_as_main
/home/conda/feedstock_root/build_artifacts/numba_1525055584125/test_tmp/run_test.sh: line 7:   884 Segmentation fault      (core dumped)

xref: https://github.com/conda-forge/numba-feedstock/pull/7
ref: https://circleci.com/gh/conda-forge/numba-feedstock/111

Thanks for reporting @jakirkham.
@sklam there's a couple of 0.38 fails on the build farm from the latest build I did when trying conda recipe changes, windows 64bit and usually Py35 but the odd Py36 (not that Python version should matter).

We also see Windows 64-bit Python 3.5 failures, but the log is probably to vague to be helpful. Maybe there is a segfault. Unclear where though. If you have suggestions, would be happy to try them.
xref: https://github.com/conda-forge/numba-feedstock/pull/7
ref: https://ci.appveyor.com/project/conda-forge/numba-feedstock/build/1.0.10/job/dq4jkmea4wao4ci5

@jakirkham I think the issue you are seeing is possibly because the numba-feedstock build is consuming artifacts from the llvmlite one which in turn consumes artifacts from llvmdev, and the llvmdev feedstock isn't patched like the Anaconda distro/wheel ones. Comparing: https://github.com/conda-forge/llvmdev-feedstock/blob/master/recipe/meta.yaml#L16-L17, vs. https://github.com/numba/llvmlite/blob/master/conda-recipes/llvmdev/meta.yaml#L15-L22, it is the twine patch https://github.com/numba/llvmlite/blob/master/conda-recipes/twine_cfg_undefined_behavior.patch which applies to llvm 6.0.0 that is with view of preventing the segfault in test_inspect_cfg (bug is reported upstream https://bugs.llvm.org/show_bug.cgi?id=37019).

Closing.


Deploy to gh-pages

:leaves:

See it at http://open-austin.github.io/austingreenmap/. Terrible tho.


about unofficial-iconv

错误信息：
CMake 路径：cmake.exe
正在使用 CMake 生成构建目录……
-- Selecting Windows SDK version 10.0.17763.0 to target Windows 10.0.17134.
-- cotire 1.8.0 loaded.
CMake Error at vcpkg/scripts/buildsystems/vcpkg.cmake:266 (_find_package):
Could not find a package configuration file provided by "unofficial-iconv"
with any of the following names:
unofficial-iconvConfig.cmake
unofficial-iconv-config.cmake

Add the installation prefix of "unofficial-iconv" to CMAKE_PREFIX_PATH or
set "unofficial-iconv_DIR" to a directory containing one of the above
files.  If "unofficial-iconv" provides a separate development package or
SDK, be sure it has been installed.
Call Stack (most recent call first):
CMakeLists.txt:28 (find_package)
-- Configuring incomplete, errors occurred!
See also "./build/Debug/CMakeFiles/CMakeOutput.log".
CMake 生成失败

ps: while running generate.ps1

prepare.ps1 运行成功了吗

似乎有报错，我重新执行一遍试试看

ok 重新安装依赖库后生成正常


Is there any test for 'no changes' to compilation?

Based on the docs/examples, we'd ALWAYS have to get the css and then write it out, but that's not the best use of a cache...e.g., if we're running the compiler for every less sheet on our page and then have to write out every css file on each page load, that's a lot of time wasted.
In both lessphp & less.php the cachedCompile() method returns a compiled date so you can determine if the cache/output was updated.  I don't see anything like that being set or availble with the $parser->cache.

There is no direct method, but using the public API you can accomplish the functionality you need. I've created an example in the example directory.
Does it cover what you need?

Thanks, that works for me!


Should we have a conda package?

I don't know. I am dumb, but I want to help.

http://conda.pydata.org/docs/using/pkgs.html

well, I followed the newbie conda tutorial and it looks like their build tool is broken. here's my bug report on their end.


[STORM-1232] port backtype.storm.scheduler.DefaultScheduler to java

Now the DefaultScheduler code is dependent on java EvenScheduler. This may cause compilation errors. I'll fix it later.

Thanks @abhishekagarwal87 for your review. Comments addressed.

Since resolving conflicts merge cause some issues, I have created a new PR(https://github.com/apache/storm/pull/1108). Please take a look.

The new PR also fixed the dependence issue.


Documentation fixes: grammar, spelling and code

This PR fixes several nitpicks in the documentation related to either spelling/grammar or code style.
Let me know if I took too many liberties when changing the code examples, and I'll make changes accordingly. I couldn't find any information in the contributing guidelines about a JavaScript style guide, so I assumed that you would be using a generic style.

Thanks!


Add "IPv4+IPv6" protocol value for IPSEC mobile VPN

[ x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[ x] I have searched the existing issues and I am convinced that mine is new.

IPv6 is becoming more important day by day as more and more mobile users are using connections with DS-Lite or pure IPv6.
In order to setup a mobile tunnel that works with IPv4 and IPv6 in OPNsense you have to specify the interface as "any".
This approach might have undesired side effects in a configuration with several WAN interfaces that are used for IPSEC.
It would be nice to have a "clean" way to configure the mobile user connection for both IPv4 and IPv6.
I have created a patch, that allows setting the protocol to "any" when editing the mobile user connection.
The generated StrongSwan configuration will then contain something like
left = <IP_ADDRESS>,2001:1:2:3:4::1
which works fine for us in production use.
I am aware this will only work for IKEv2, maybe there should be some kind of warning if using protocol=any with IKEv1.
opnsense_ipsec.patch.txt

@goodomens42 we don't accept patches inside issues, for discussion and feature merges we advise to use the normal GitHub PR process (https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests)

@goodomens42 Based on your patch, I've created a PR: see #5166


[SPARK-36886][PYTHON] Inline type hints for python/pyspark/sql/context.py

What changes were proposed in this pull request?
Inline type hints for python/pyspark/sql/context.py from Inline type hints for python/pyspark/sql/context.pyi.
Why are the changes needed?
Currently, there is type hint stub files python/pyspark/sql/context.pyi to show the expected types for functions, but we can also take advantage of static type checking within the functions by inlining the type hints.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing test.

Test build #143846 has started for PR 34185 at commit 2016bba.

Test build #143846 has finished for PR 34185 at commit 2016bba.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48359/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48359/

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

can you make Jenkins happy (https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/143902/)?

Test build #143903 has started for PR 34185 at commit 97529b3.

Test build #143903 has finished for PR 34185 at commit 97529b3.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

I think the problem is the versions of mypy and other linter tools are different in GitHub Actions and Jenkins. we would first have to figure out to make both old and new versions happy.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48421/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48421/

Test build #143916 has finished for PR 34185 at commit 2016bba.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #143933 has started for PR 34185 at commit b3dc524.

Test build #143959 has started for PR 34185 at commit 8b0a314.

Test build #143959 has finished for PR 34185 at commit 8b0a314.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

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

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48453/

Test build #143990 has finished for PR 34185 at commit 8b0a314.

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

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48453/

Test build #144006 has finished for PR 34185 at commit f9d45cb.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48483/

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

cc @HyukjinKwon,  can you take a look, pls?

Test build #144080 has started for PR 34185 at commit 23ebe1b.

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

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48558/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48678/

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

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48678/

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

cc @xinrong-databricks @itholic @ueshin FYI

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48772/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48772/

Test build #144339 has started for PR 34185 at commit 3e9b99f.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48818/

thank you!


It would be nice to add the possibility of money between worlds to the plugin

At the moment, players need to be in the same world to transfer money. It would be great if you could transfer money if the players are in the same group at the moment.
Also, add the ability to transfer money if the players are in different groups, but with an additional option:
/pay [Player] [Amount] [Group]

Hi,
The main idea of this plugin is to separate economy between worlds without installing more servers.
I will check if I can do something to detect, if or not, the players are in the same group and not the same world.
You can grab all the code and make an alternative of mine if you like. I've not much time to make new feature at the moment.


Update rapids-cmake to require cmake 3.23.1

This moves rapids-cmake to require CMake 3.23.1 or newer.
Along with that we are able to do the following improvements:

Use CMake's FindGTest as it now provides all the targets we require
Simplify install_lib_dir logic
Simplify logic around version values that are all zeroes

Due to https://gitlab.kitware.com/cmake/cmake/-/merge_requests/7523 We will need to change the get_gtest logic or maybe require 3.23.4+

Dropped the changes to thrust as those are now captured in: https://github.com/rapidsai/rapids-cmake/pull/231

@robertmaynard do you want me to review this now, or do you want to just wait for 3.24? We've been waiting on a CMake upgrade for a while anyway so I'm not opposed, but I thought we were expecting to see 3.24 in time for our 22.10 release anyway.

@robertmaynard do you want me to review this now, or do you want to just wait for 3.24? We've been waiting on a CMake upgrade for a while anyway so I'm not opposed, but I thought we were expecting to see 3.24 in time for our 22.10 release anyway.

My thought was we could roll out these changes now, and verify that all consumers are still building correctly. That will give us time to have 3.24 released and conda packages provided. After that we can make another PR to bump the minimum required and update components with 3.24 improvements.

That's fine with me. But just FYI... https://github.com/conda-forge/cmake-feedstock/pull/165 :smile:

I'll review this afternoon

@gpucibot merge


bug: [dashboard] attempt to perform arithmetic on field 'width' (a nil value) when setting the header

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2 release
Operating system/version
macOS 15.1.1
Describe the bug
When trying to set the header dynamically, sometimes it fails with the following error.
Error detected while processing UIEnter Autocommands for "*":
Error executing lua callback: ...epro/data/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:417: attempt to perform arithmetic on field 'width' (a nil value)
stack traceback:
        ...epro/data/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:417: in function 'format'
        ...epro/data/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:567: in function 'render'
        ...epro/data/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:654: in function 'update'
        ...epro/data/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:209: in function 'open'
        ...epro/data/nvim/lazy/snacks.nvim/lua/snacks/dashboard.lua:1039: in function 'setup'
        ...ri/.repro/data/nvim/lazy/snacks.nvim/lua/snacks/init.lua:126: in function <...ri/.repro/data/nvim/lazy/snacks.nvim/lua/snacks/init.lua:123>
Press ENTER or type command to continue

Steps To Reproduce

Use the minimal provided init.lua
Try to open neovim multiple times, it doesn't need to be quickly after each other, but one of them should fail with the error above.

Expected Behavior
To not fail
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
	spec = {
		{
			"folke/snacks.nvim",
			config = function()
				local function wrap_text(input_table, width)
					local wrapped_lines = {}

					for _, line in ipairs(input_table) do
						if line == "" then
							table.insert(wrapped_lines, "")
						else
							local line_start = 1
							while line_start <= #line do
								local line_end = math.min(line_start + width - 1, #line)

								if line_end < #line then
									local space_pos = line:sub(line_start, line_end):find(" [^ ]*$")
									if space_pos then
										line_end = line_start + space_pos - 1
									end
								end

								local segment = line:sub(line_start, line_end):gsub("^%s*", "")
								if segment ~= "" then
									table.insert(wrapped_lines, segment)
								end

								line_start = line_end + 1
							end
						end
					end

					return table.concat(wrapped_lines, "\n")
				end

				local random_quote = function()
					local quotes = {
						-- Copied from startify https://github.com/mhinz/vim-startify/blob/4e089dffdad46f3f5593f34362d530e8fe823dcf/autoload/startify/fortune.vim#L85-L239
						{
							"Debugging is twice as hard as writing the code in the first place.  },
						{
							"Adapting old programs to fit new machines usually means adapting new machines to behave like old ones.",
							"",
							"- Alan Perlis",
						},
						{
							"Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.",
							"",
							"- Alan Perlis",
						},
						{
							"It is easier to change the specification to fit the program than vice versa.",
							"",
							"- Alan Perlis",
						},
						{
							"Simplicity does not precede complexity, but follows it.",
							"",
							"- Alan Perlis",
						},
						{ "Optimization hinders evolution.", "", "- Alan Perlis" },
						{
							"Recursion is the root of computation since it trades description for time.",
							"",
							"- Alan Perlis",
						},
						{
							"It is better to have 100 functions operate on one data structure than 10 functions on 10 data structures.",
							"",
							"- Alan Perlis",
						},
						{
							"There is nothing quite so useless as doing with great efficiency something that should not be done at all.",
							"",
							"- Peter Drucker",
						},
						{
							"If you don't fail at least 90% of the time, you're not aiming high enough.",
							"",
							"- Alan Kay",
						},
						{
							"I think a lot of new programmers like to use advanced data structures and advanced language features as a way of demonstrating their ability. I call it the lion-tamer syndrome. Such demonstrations are impressive, but unless they actually translate into real wins for the project, avoid them.",
							"",
							"- Glyn Williams",
						},
						{
							"Quality, functionality & schedule. You get to pick only two, btw if you gonna pick functionality & schedule, I'm outta here, so every other quality Engineer because I don't want to deliver shit.",
							"You gotta have quality, so you actually picking between functionality & schedule",
							"",
							"— Bryan Cantrill",
						},
						{
							"The power of code to make toil go away has always fascinated me, perhaps more than the power of code to make things.",
							"",
							"— Rebecca Murphey",
						},
						{
							"Influence is all about giving people your ideas and letting them run with it as their own.",
							"",
							"— Kris Nova",
						},
					}
					math.randomseed(os.time())

					return quotes[math.random(#quotes)]
				end

				require("snacks").setup({
					dashboard = {
						preset = {
							header = wrap_text(random_quote(), 60),
						},
						sections = {
							{ section = "header" },
						},
					},
				})
			end,
		},
		-- add any other plugins here
	},
})

Thank you for the repro. Fixed!


refactor hnsw search path

This is part of effort for #61

extract code to search one step in hnsw into a separate method.
make searchBaseLayerST return NeighborSet directly without converting it into a std vector.
Add operator> to Neighbor, allow NeighborSet::insert to accept an optional pq to collect any nodes that was evicted from the NeighborSet for later use.

/kind improvement

LGTM

/lgtm


281 Scaling of commuter migration/mobility data

Implements scaling for the commuter mobility data.

The Scaling is based on the center point of each county. This method is efficient, but also sometimes inaccurate.
In order to have the input file (center points) also for the test cases, it was added to the constructor
Since no scaling of commuter mobility was done before, the comparison values of the unit tests had to be adjusted as well.

Merge Request - GuideLine Checklist
Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.
Checks by code author:

[x] There is at least one issue associated with the pull request.
[x] The branch follows the naming conventions as defined in the git workflow.
[x] New code adheres with the coding guidelines
[ ] Tests for new functionality has been added
[x] A local test was succesful
[x] There is appropriate documentation of your work. (use doxygen style comments)
[ ] If new third party software is used, did you pay attention to its license? Please remember to add it to the wiki after successful merging.
[ ] If new mathematical methods or epidemiological terms are used, has the glossary been updated ? Did you provide further documentation ?
is present or referenced. Please provide your references.
[ ] The following questions are addressed in the documentation*:  Developers (what did you do?, how can it be maintained?), For users (how to use your work?), For admins (how to install and configure your work?)
For documentation: Please write or update the Readme in the current working directory!

Checks by code reviewer(s):

[ ] Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
[ ] The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
[ ] There are appropriate unit tests and they pass.
[ ] The git history is clean and linearized for the merge request.
[ ] Coverage report for new code is acceptable.

Closes #281

Codecov Report

Merging #291 (22fd400) into main (8b25d83) will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #291      +/-   ##
==========================================
+ Coverage   91.23%   91.36%   +0.13%
==========================================
  Files          77       79       +2
  Lines        4721     4854     +133
==========================================
+ Hits         4307     4435     +128
- Misses        414      419       +5

Impacted Files
Coverage Δ

cpp/memilio/utils/custom_index_array.h
97.76% <0.00%> (-1.40%)
:arrow_down:

cpp/models/abm/location.cpp
99.03% <0.00%> (-0.97%)
:arrow_down:

cpp/models/abm/time.h
100.00% <0.00%> (ø)

cpp/models/abm/world.h
100.00% <0.00%> (ø)

cpp/models/abm/person.h
100.00% <0.00%> (ø)

cpp/models/abm/household.h
100.00% <0.00%> (ø)

cpp/models/abm/parameters.h
100.00% <0.00%> (ø)

cpp/models/abm/simulation.h
100.00% <0.00%> (ø)

cpp/memilio/utils/stl_util.h
100.00% <0.00%> (ø)

cpp/models/abm/household.cpp
100.00% <0.00%> (ø)

... and 11 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 8b25d83...22fd400. Read the comment docs.


Cherry-pick bugfix to branch-2.1

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #4114
Problem Summary(Required) ：

The type of memory_limitation_per_thread_for_schema_change is int32 and upper limit is 2GB.
When memory_limitation_per_thread_for_schema_change is set to more than 4GB, the memory limitation of schema change will overflow and maybe set to 0.
Change the type of memory limitation to uint64

run starrocks_fe_unittest

run starrocks_be_unittest

run all

run starrocks_be_unittest

run starrocks_be_unittest

run starrocks_be_unittest


libc 0.3: Change prototypes for exec* function to match headers

Yes, this makes the prototypes harder to use. And less intuitive.
But this makes them match headers, and thus now we can properly test them. This fixes https://github.com/rust-lang/libc/issues/1272
This is breaking change

I rebased multiple times, and now the PR is ready for review

@JohnTitor did you realize that this change is backwards-incompatible, and causes downstream crates' builds to fail?

these commits are in main branch, and not in libc-0.2 branch. so I assume it is fine from libc point of vue ?
see v0.3 Roadmap.

Ahh, that makes sense.  Thanks, @semarie .


Initalize vs Initialize

Hi!
When starting a receiver, the command given is initalize_receiver, but the word is spelled with two 'i's, initialize.
PS: This is an awesome project!

Thank you! Will correct it.


Atom Package / Theme Repo Search does not work (1/24/2016 3:22PM)

Gives error 500. Same in the editor.
https://atom.io/themes/search?utf8=✓&q=theme

@gyf304 thanks for reporting - these kind of errors usually fix themselves in a few hours.  If it still persists, please re-open the issue on https://github/atom/atom.io.  Thanks!


Windows manager

Currently IVoyager has kind of a windows system as well as panku console.
Maybe expose Editor windows subsystem or extend it?

IVoyager relies on IVDraggableControl