fstat st_blocks is wrong, results in failure of many IO functions

Your Windows build number:  Build 16299.129

What you're doing and what's happening:
I am working on a 512 bytes sectored filesystem (Windows and Linux).
Download bytes testfiles here: bytes_testfiles.zip
Copy into Win32 "C:/testdir" (adjust if necessary)

stat /mnt/c/testdir/504_bytes_testfile
stat /mnt/c/testdir/505_bytes_testfile

The 504_bytes_testfile returns a block size of 0, but the 505_bytes_testfile returns a block size of 1.

What's wrong / what should be happening instead:
On Real Linux(tm), the blocks size for both files is always 1.

How to reproduce on Real Linux(tm):

Creating the 512 bytes sectored partition
Plug in a HDD that has free space. Then open gparted to initialize that empty drive unformatted.
Assuming that the new partition device is located at /dev/sdb1 ...

mkfs -t ntfs -s 512 -c 512 /dev/sdb1
mkdir /mnt/test
mount /dev/sdb1 /mnt/test
cd /mnt/test

Place the 504 and 505 bytes testfiles into /mnt/test
execute the stat commands as described above on them

stat /mnt/test/504_bytes_testfile
stat /mnt/test/505_bytes_testfile

Strace of the failing command, if applicable:  is this required? please post if yes.

Helpful links: https://linux.die.net/man/2/fstat
Funny related issue of wxWidgets: https://github.com/wxWidgets/wxWidgets/commit/a03ece4880d68743f0a40710f00b82da223c870f
This causes issues in many Linux IO libraries. pls fix, pls fast
Code::Blocks build scripts do not work otherwise.

@quiret - You mention this behavior "causes issues in many Linux IO libraries."  Could you elaborate?

Hope we get a well defined answer to which libraries/packages depend on the behaviour. But even if we don't, it seems the open question here is whether DrvFs is striving for ntfs-3g equivalence, or whether you point at the man page (which is authoritative in the same way that Wikipedia is authoritative) and say, nah, DrvFs is Right™. ntfs-3g has been around for a long time and they didn't choose how it behaves for their health. They presumably did it that way because it makes ntfs-3g fit into the Linux ecosystem better.

This was marked by-design which is pretty much a flow chart terminus. If there exists in the wild an example of a specific scenario that breaks on WSL but works on on Real Linux with ntfs-3g or say a NFS/SMB mount that would be worth opening a new issue. "Breaks" (contrast: reports a different number up for interpretation) is a pretty high bar but it might exist.


Scaling Avatar

How to Scale Ultimate XR avatar ?
I'm having problem with scaling ,I tried changing scale to 2 and also changed "Eye Base height" and "eye forward offset". but nothing worked. Please guide us in scaling UXR Avatar.

Thanks for the feedback. I have just commited some changes that fix the body and arm IK not working correctly when the avatar has scaling values. It should work correctly now.

Please test it and let us know if it fixed the issue on your side as well. As you mentioned, make sure that the "Eye Base Height" and "Eye Forward Offset" in your UxrAvatarController component fit the new scaled avatar.

we are currently working on it .But after scaling the avatar how to make changes in  UXR Hand Integration and Align to Avatar  because Hand Integration is not working correctly.


Comment rendering

🚀 Pull Request
Description
Relates to https://github.com/SciTools/iris/issues/3840 and the issue https://github.com/SciTools/iris/issues/4657.
The docstrings layout is inconsistent especially the indentations.

dot.py latest | this PR
nimrod_load_rules.py latest | this PR
pp.py latest | this PR

Changes made as per the official numpdoc strings guide, see https://numpydoc.readthedocs.io/en/latest/format.html#docstring-standard and https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html
I also updated the docstring guidance on the docs and the pull request guidance

docstrings.rst latest | this PR
contributing_pull_request_checklist.rst latest | this PR

For help with the docstring formatting I used pydocstyle http://www.pydocstyle.org/en/stable/usage.html via the command:
pip install pydocstyle
pydocstyle --convention=numpy pp.py --add-ignore=D200,D405,D407,D411,D205,D400,D105,D102,D401 # D205 D400 D105 D102 D401

I chose to ignore some for now.  We have an option to make this part of our pre-commit checks in future.

Consult Iris pull request check list

We're getting 403 errors from GitHub that are breaking the linkcheck, and it doesn't seem to resolve on a rerun?


Update offsets (1.0 backport)

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

Comparison is base (ec75587) 78.71% compared to head (ef8083b) 43.95%.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-1.0     #555       +/-   ##
================================================
- Coverage        78.71%   43.95%   -34.76%
================================================
  Files               61       59        -2
  Lines             5036     4914      -122
================================================
- Hits              3964     2160     -1804
- Misses             861     2623     +1762
+ Partials           211      131       -80

Flag
Coverage Δ

integration-test
?

unittests
43.95% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks @grcevski , I think that for a 1.0.3 it's OK just like this :-) But as you wish.

Yeah actually if we cut a new release soon, it doesn't really matter :)


Azure Bastion login via cli with aad does throw error message

PS C:\Users\chpinoto> az network bastion ssh -n cptddns -g cptddns --target-resource-id /subscriptions/my-sub-id/resourceGroups/cptddns/providers/Microsoft.Compute/virtualMachines/cpddnsvmhub --auth-type AAD
Command group 'network bastion' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
The command failed with an unexpected error. Here is the traceback:
'Profile' object has no attribute 'get_msal_token'
Traceback (most recent call last):
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 657, in execute
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 720, in _run_jobs_serially
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 691, in _run_job
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 328, in call
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/network/custom.py", line 7802, in ssh_bastion_host
File "C:\Users\chpinoto.azure\cliextensions\ssh\azext_ssh\custom.py", line 58, in _get_and_write_certificate
_, certificate = profile.get_msal_token(scopes, data)
AttributeError: 'Profile' object has no attribute 'get_msal_token'
PS C:\Users\chpinoto> az version
{
"azure-cli": "2.30.0",
"azure-cli-core": "2.30.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {
"account": "0.2.1",
"ad": "0.1.0",
"alias": "0.5.2",
"application-insights": "0.1.13",
"azure-devops": "0.18.0",
"cli-translator": "0.3.0",
"costmanagement": "0.1.1",
"interactive": "0.4.4",
"internet-analyzer": "0.1.0rc6",
"kusto": "0.3.0",
"log-analytics": "0.2.2",
"portal": "0.1.1",
"resource-graph": "1.1.0",
"sentinel": "0.1.0",
"ssh": "0.1.5",
"storage-blob-preview": "0.5.0",
"storagesync": "0.1.0"
}
}
Some guidance how to fix this to get the bastion native client working on my Windows OS.
Thanks

network

Fixed in https://github.com/Azure/azure-cli/pull/20648


fixed a documentation gap, switched to docker-compose

Hi folks,
I've noticed that the docker-compose command isn't complete, I thought it might be relevant to fix both in the README.md filed, and documentation.

Hi Shon,
The syntax depends on the docker compose version as you can see from the official documentation.
If you want to use V1 you can alias "docker compose" to "docker-compose" on your local environment to solve the issue locally.
Thanks

Hi Shon,
The syntax depends on the docker compose version as you can see from the official documentation. If you want to use V1 you can alias "docker compose" to "docker-compose" on your local environment to solve the issue locally.
Thanks

Hi Shon,
The syntax depends on the docker compose version as you can see from the official documentation.
If you want to use V1 you can alias "docker compose" to "docker-compose" on your local environment to solve the issue locally.
Thanks

Hi folks,
I've noticed that the docker-compose command isn't complete, I thought it might be relevant to fix both in the README.md filed, and documentation.

Hi Shon,
The syntax depends on the docker compose version as you can see from the official documentation.
If you want to use V1 you can alias "docker compose" to "docker-compose" on your local environment to solve the issue locally.
Thanks


upgrade to go 1.10 / alpine 3.7

Also make use of the go 1.10 build & test cache (https://golang.org/cmd/go/#hdr-Build_and_test_caching)

Not 100% sure the changes for the build cache are correct (I think the additions are fine, just not sure about changing/removing older optimizations)

LGTM, thanks!


brew cleanup doesn't clean ~/Library/Caches/Homebrew

I noticed brew keeps a copy of the files it downloads in  ~/Library/Caches/Homebrew , and the "brew doctor" command doesn't clean it.
For example:

[damians@iMac ~]$ brew cleanup
Removing: /usr/local/Cellar/ffmpeg/3.4.1... (248 files, 50.9MB)
Removing: /usr/local/Cellar/x264/r2795... (11 files, 3.2MB)
==> This operation has freed approximately 54.1MB of disk space.

And in the Cache folder there are still:

[damians@iMac ~]$ ls ~/Library/Caches/Homebrew
ffmpeg-3.4.1_1.high_sierra.bottle.tar.gz  x264-r2854.high_sierra.bottle.tar.gz

man brew will show you the -s flag for cleanup.
Even then, cleanup doesn't always get everything.

The cleanup section of brew’s man page (emphasis mine):

For all installed or specific formulae, remove  any older  versions from the cellar. In addition, old downloads from the Homebrew download-cache are deleted.
If --prune=days is specified, remove all cache files older  than days.
If --dry-run or -n is passed, show what would be removed, but do not actually remove anything.
If -s is passed, scrub the cache, removing  downloads  for  even the latest  versions  of  formulae. Note downloads for any installed formulae will still not be deleted.  If  you  want  to delete those too: rm -rf $(brew --cache)

This is expected behaviour. If you want to remove everything, run the suggested rm command.

Thanks for the answer. What's the use of keeping already installed formulae downloads files around?

In case something goes wrong and you have to reinstall.

Closing issue as solved (clarified).

@galad87 In future always, always, always fill out the issue template, please.


HDDS-10233. Apache Release Manager Guide

What changes were proposed in this pull request?
Port Release Manager Guide from https://cwiki.apache.org/confluence/display/OZONE/Ozone+Release+Guideline
Enable syntax highlighting for bash examples.
https://issues.apache.org/jira/browse/HDDS-10233
How was this patch tested?
:eyes:

@errose28 Thank you for the explaination. Looks good to me to use Github as the standard.

Thanks @errose28, @symious for the reviews so far.
I fully support further reviewing and improving the contents of this guide (and other pages to be ported).  I also have a couple of items in mind for that.  However, I suggest making improvements over the original content in follow-up PR(s).  Both Confluence Wiki and Git can show history of changes, but we cannot diff between states in CWiki and Git.  All content added here will be seen as one initial commit for this page.
For the same reason, I don't think we should keep the CWiki page as is (or even improved in the future).  Keeping both pages alive will be a pain.  Especially if we start making improvements to the website content in follow-up PRs (or even in this PR).  I would add a warning at the top of the cwiki page to direct readers to the specific page on the new website.  The site may be in progress, but the same is true for cwiki.  I don't see any problem exposing the staged website to the audience of the cwiki.
Summary of the process I suggest:

port contents as is (adapt formatting from cwiki to mdx)
edit original page to link to the website
improve in follow-up PRs

This applies to pages that are 1:1 ported from cwiki or other "remote" source.  For pages curated from various sources, we should combine steps 1 and 3, since the content will be new anyway.

LGTM with the no-change switch.

I have applied (most) suggested changes to avoid having to duplicate review effort in follow-up PRs.  Also made a couple of trivial formatting tweaks.
Review items with more generic ideas (e.g. using Title Case, rearranging/combining parts, or completely revamping sections) I still would like to address in follow-up PR.

Thanks @errose28, @symious for the review.

@errose28 I don't see the new content in the staging site.  Publisher workflow ran fine, asf-site-v2 branch has the content.  Am I missing something?

Added note about the new location.  Linked to this PR and the source file.  Will add link to the rendered version after it becomes available in the staging site.

Yeah I checked last night and also did not see the new content deployed but it looks good now. Maybe some slowdown in processing on the ASF infra side. In that past it had been published about a minute after merging.


Uncaught Error: Cannot find module

phaser-es6-webpack-1.0\src\main.js"
at webpackMissingModule (_math-scale.js:18)
at Object. (_math-scale.js:18)
at webpack_require (bootstrap 8158fcd1685397aac32a:54)
at webpackJsonpCallback (bootstrap 8158fcd1685397aac32a:25)
at bundle.js:1

hi there i've get that error when try to run development server using npm run dev , am i missing any file?. thanks

Hi. Have you modified the project after cloning it?

not yet ,  just cloning your repo and try to run, but that errors appears

here is the errors in command bash when i run npm run dev

Could you make a fresh install in another location?
What is that "!!ES6" in the path?

closed for inactivity


merge: dev to master

fix: replace fancy chars with dots

:tada: This PR is included in version 0.132.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


More spamchrting tools

What feature do you want to get added on the base engine?
I want a spamcharting feature that can change the distance of duplicates.

To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor and 6K+ support.

You already have one.
The Shift by # Steps Stepper

It's mainly for when you have to duplicate it over a certain distance because the step shifter shifts all the notes in a section.

The step shifter also determines the distance of each duplicate

But since there is nothing that's used to select certain notes, it's hard to actually shift the notes you want to shift.

Yeah, I can't really add that because it's kinda.......
d i f f i c u l t

What about using some of the code from CDEV Engine?

wait cdev added that-

Yeah. I saw a video for the showcase and it show that feature along with moving them.

Good news is that I will be adding it

ok ive actually reconsidered, since if you select note spam and move it it automatically turns into stacked 16th notes

Can't you code something that can override that like maybe changing some of the code from cdev to keep it at no snap?

Can't you code something that can override that like maybe changing some of the code from cdev to keep it at no snap?

I was gonna consider adding smth like only making it snap the first note (and holding SHIFT removes the snap) then moving the notes based off that note's strum time but didn't really get to see how that would work

right now, I don't feel like adding more tools for spamcharting, I might add more later if I don't ever forget, but otherwise I don't feel like adding more rn


can't save image

hi
i have problem with uploading
my code:
if($request->hasFile('logo')) {
            $logo_name = $web->subdomain .'.' . $request->file('logo')->extension();
            $web->logo = $request->file('logo')->storeAs(
                'upload/logo', $logo_name
            );

            $logo = Image::make($request->file('logo'))->resize(256, null, function ($const) {
                $const->aspectRatio();
            })->save('upload/logo/256/'. $logo_name);
        }

i get this error

NotWritableException in Image.php line 143: Can't write image data to path (upload/logo/256/aleki.jpeg)

Seems like permission problem. Did you check the folder's permission for writing?

I had the same problem, even I have given  the permission. But I found the reason in the source code. If you don't have the directory(path), you can't save the file to disk.
I change part of the src code like bellow:
$pathInfo = pathinfo($path);         $data = $this->encode($pathInfo['extension'], $quality);         if(!\File::exists($pathInfo['dirname'])){             \File::makeDirectory($pathInfo['dirname']);         }
the original code is
`/**
* Saves encoded image in filesystem
*
* @param  string  $path
* @param  integer $quality
* @return \Intervention\Image\Image
*/
public function save($path = null, $quality = null)
{
$path = is_null($path) ? $this->basePath() : $path;
    if (is_null($path)) {
        throw new Exception\NotWritableException(
            "Can't write to undefined path."
        );
    }

    $data = $this->encode(pathinfo($path, PATHINFO_EXTENSION), $quality);
    $saved = @file_put_contents($path, $data);

    if ($saved === false) {
        throw new Exception\NotWritableException(
            "Can't write image data to path ({$path})"
        );
    }

    // set new file info
    $this->setFileInfoFromPath($path);

    return $this;
}`

Maybe this is a good suggestion. :)


Direct sampling contour default value for the MC sample should be calculated based on alpha

Currently, we have  the DirectSamplingContour uses a Monte Carlo sample size of 1E6 as standard value. This is not good as it can lead to too low sample size if low alpha values are used.
Currently:
def init(self, model, alpha, n=100000, deg_step=5, sample=None):
Instead by default n should be calculated as n = 100 / alpha.

Implemented.


Add nbqa-ruff for doc notebooks

Closes https://github.com/pymc-labs/pymc-marketing/issues/554
I suggest we use nbqa-ruff (https://github.com/nbQA-dev/nbQA) in the pre-commit hooks. I left out clv/dev notebooks as they have many ruff-errors to fix, and we can do it on a separate issue (BTW, what do we want to do with these dev notebooks ?)

📚 Documentation preview 📚: https://pymc-marketing--561.org.readthedocs.build/en/561/

No, they are experimental 😄


Factor out into a standard PostgreSQL extension

Our interfaces and core functionality are stable and well-defined enough at this point that we can cleanly formulate our API in terms of the extension API. The main areas of work here are:
Syntax - Grammar is not extensible so we lose CREATE CONTINUOUS VIEW et all. They become SELECT pipelinedb.create_cv('...') etc.
Syscache lookups - We'll need to write fast lookup support around our catalog tables since they won't be native catalogs anymore.
Planner/executor - CQ node types will need to be handled via hooks instead of natively.
Dump/restore - We'll need to make dump/restore work with vanilla pg_dump/pg_restore
This refactor should probably happen in a few phases:

Phase 0: get the diff against upstream Postgres down to an absolute minimum
Phase 1: factor PipelineDB out as an extension of itself
Phase 2: stabilize the extension against upstream Postgres, possibly landing some changes upstream where necessary

Woah!

We should start breaking this into incremental additions, and aim to time the final step with PG 9.7, which will probably be out in Q12017. Ideally we can incrementally release this rework in our own releases before then.

According the Postgres roadmap, 10/9.7 is scheduled for a Q3 release next year. Is the Q1 2017 timeline above a typo?

@derekjn Is this likely to land Q1 this year or is it realistically going to be further out towards the second half of the year? I'm just to get a sense of things for our deployment plans.
Cheers.

Hey @samgaw! Second half of the year would be more realistic for planning purposes. Are you currently using PipelineDB or are you waiting for the extension refactor?

@derekjn We've been running it in the lab for a few months. The hold off on deployment has been waiting for either the refactor or the 9.6 merge; but if the merge comes first the end result is the same for us so I've really no preference either way.

@derekjn Would this allow for combining CitusDB and PipelineDB functionality in a single PG deployment?

@derekjn Would this allow for combining CitusDB and PipelineDB functionality in a single PG deployment?

@mbulgakov17 probably not in any useful way. The PipelineDB core runs on a single server, so if you were running a CitusDB across multiple nodes and wanted to run PipelineDB on them as well, you'd probably end up with some kind of operational mess.

@mbulgakov17 If it helps we have them separate and syndicate to both CitusDB and PipelineDB through a queue (kafka and rabbitmq).
In theory logical decoding (e.g. bottle) from pipelinedb -> citus would be the ideal choice but I'm not sure how well that would work and what the decoding looks like for streams/views. Luckily accurate consistency with stats is not a major requirement for us.

Thank you for sharing, @agentgt

Wondering if having pipelinedb act as a proxy in front of postgresql wouldn't be an easier path and more flexible on the pipelinedb end (you could keep the same code syntax for the end users).
Doing so would allow you to decorellate the DB backend from the code logic and probably have an easier code to manage. On the end user side, we could have the storage done in, let's say and RDS Postgres instance and the pipelinedb proxy run on a docker image for example.
Thoughts?

@aerostitch it's definitely a cool idea in theory, but wouldn't really be feasible in practice. You could make something work this way and get correct results, but the performance wouldn't even be remotely comparable to what PipelineDB currently provides, to the point where it would likely be pointless to use. It would be so expensive that you'd most likely be better off just storing all of your granular data in a warehouse and running on-demand queries on it.
I see two approaches you could take for this:

Cache all aggregate data at the PipelineDB layer and just write out updates to the storage layer to avoid read-writes for incremental updates. But this is basically equivalent to how PipelineDB already works. You can actually do this already with PipelineDB if you want, by just tailing output streams and writing output rows to some external datastore.

Don't cache aggregate data and incur the cost of a read-write for each incremental update. Not only would this involve a lot of round trips between PipelineDB and the storage layer, but you'd be incurring all of the overhead of generating raw SQL queries and planning them before execution on the storage end. Currently PipelineDB bypasses all of that by co-locating compute and storage, and running incremental updates without any planner overhead.

I definitely like what you've outlined though, it's very elegant but unfortunately would be impossible to make such a setup perform at the level that users have come to expect of PipelineDB.

Thanks for the answer @derekjn .
Yeah solution 1 was more what I was thinking and would basically be a big cache with a query language on top of it :)
The use case would have been to be able to have an equivalent of a distributed cache that we could spread on different nodes of a kubernetes cluster for example and having the storage safe in a non-ephemeral environment (we keep only 60mins of datapoints).
But I do understand your concern about performance on large scale data.

Wondering if you aim to refactor this in the same three phases as noted above? The PostgreSQL 10 beta is out and there's enough changes that I think an easier refactor strategy would be to start with a new blank extension and slowly port over code from PipelineDB into that?
I think the first step can be to get a few simple aggregates to work end-to-end, including support for output streams etc. Once that is stable, porting other aggregates should be fairly straight-forward?

@usmanm I think that approach is worth experimenting with now that PG 10beta is out, because it if is going to be faster, it's going to be much faster. We'll evaluate this approach and report back here over the next week or so.

@usmanm I did some prototyping with the direct-to-extension approach, and I think it's going to work pretty well. The biggest complication is that it's non-trivial to port modules that use PipelineDB-specific things that aren't available in PG core. Examples of such things are DestTupleTable, DestCombiner, custom syscache entries, etc.
It is necessary to replace these components with standard primitives no matter how we do this, so I think the best way to go about finishing the refactor will be a two step process:

Standardize everything in the PipelineDB tree.
Port the standardized tree directly to an extension.

The main advantage of this approach is that I don't believe that any upstream merging is necessary. As you suggested, once everything is standardized it's actually fairly smooth to port all modules directly as an extension. But as I mentioned the standardization has to happen at some point anyways, so it seems more practical to do it in its own stage rather than simultaneously while porting.

Resolved in extension repo.


Support find singleBatch and validate getMore parameters

Description
Closes #2005.

After all, supporting the list defined in https://github.com/FerretDB/FerretDB/issues/2005 was easier than creating additional issues. So this PR closes the issue.
Readiness checklist

[ ] I added/updated unit tests.
[x] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[x] I updated user documentation.
[ ] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

@chilagrow Please do https://github.com/FerretDB/FerretDB/pull/2855/files#r1235077008 and https://github.com/FerretDB/FerretDB/pull/2855/files#r1235078804 in the next PR


Flat theme: include listing of locales above frontend header

Hi! We are using the Helpy Flat UI theme and I noticed that it could be more convenient for the user to directly be able to switch locales from the header and that all locales are listed side-to-side instead of a dropdown. Somewhat like this:

By looking through the codebase, I found out that files /app/themes/flat/views/layouts/_header.html.erb and /app/themes/flat/views/layouts/_above_header.html.erb already exist, but they seem not to be used at all. Should the header layout be included in /app/themes/flat/views/layouts/flat.html.erb or have I understood something incorrectly? It seems to me that the header is currently outputted from lines https://github.com/helpyio/helpy/blob/634145490bc8a14fe5750c8ac05537bf9117eac6/app/themes/flat/views/layouts/flat.html.erb#L54-L73
instead of using the header layout.
I'm happy to make a PR about this.

@l3ku I would probably do this by inserting some javascript into your design.  You can accomplish this by going to settings > design then scroll down to the footer js.  Add a script like this:

This will run on every page of the helpcenter and add the locale links accordingly.  You can additional styling as you see fit, or use a regex to match the exact URL of the page the user is on (probably unnecessary).


The plugin ignores configuration in certain scenario

Adding the attached file using apply from: 'common.txt' in build.gradle causes the plugin to download LATEST-EAP-SNAPSHOT with sources regarding of the configuration.
common.txt
Environment:
org.jetbrains.intellij" version "0.0.35"
Java 6
IntelliJ IDE 13

Are you sure that this is the problem of plugin and not misconfiguration of you build.gradle?

I have the following configuration:
intellij {
    version '13.1.6'
    pluginName 'MyPlugin'
    intellij.downloadSources false
    intellij.updateSinceUntilBuild false
    intellij.instrumentCode true
    intellij.type 'IU'
    systemProperty 'idea.is.internal', 'false'
}

What can be misconfigured?

I don't see any apply from in your configuration

I am not sure if it was an actual problem. I am unable to reproduce it so far after computer restart :/


launch.json: setting protocol:inspector results in bogus error

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:34:09.706Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

debugger-for-chrome
msj
3.1.7

Steps to Reproduce:

launch.json:

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "chrome",
			"request": "launch",
			"name": "Launch Chrome against localhost",
			"protocol": "inspector"
		}
	]
}

this results in the following error on the type property:
The debug type is not recognized. Make sure that you have
a corresponding debug extension installed and that it is
enabled..

if you typo inspector then the type error goes away.
Reproduces without extensions: N/A

@Spongman I do not really understand what you mean by "if you typo inspector then the type error goes away", but I guess that you've meant to say "if you remove the 'protocol' attribute, then the type error goes away".
@aeschli @isidorn this is a really annoying case of misleading error reporting:
the "chrome" debug type does not support a "protocol" attribute. But the "node" debug type would support that attribute.
We need a way to mark the "type" attribute as a "schema defining" attribute. So that the error reporting does not report the "type" attribute as wrong but flag the "protocol" attribute as unknown.

by "typo" i mean "mis-spell", eg:
"protocol" : "Qnspector"

aha, I understand.
Yes an unknown attribute (in any schema) will result in the same (correct) behaviour as a removed attribute.

This is currently not supported by the JSON schema as far as I know and would be a feature request.
@aeschl is there some workaround for this currentlyi (to give the type proparty some sort of weight)


Check for valid IPs before choosing one

Today, Dapr runtime chooses the first valid IPv4 address that is not localhost loopback. This is used for sidecar-to-sidecar communication. There is no guarantee that the chosen IP is reachable even within the host itself. Add validation before choosing the IP.
Options for validation (not exclusive):

Check if IsGlobalUnicast() is true.
Check if IP can be pinged.
Check if IP can be connected to (if side car is already listening to HTTP or GRPC port).

See https://golang.org/src/net/ip.go
See https://github.com/dapr/dapr/blob/ce7430e49491d3e6040ace869336d794f83c862e/pkg/runtime/runtime.go#L512

Related to issue #1046

Correction: this is not used for sidecar to sidecar communication, it's used for Actors to announce their host names to the placement service.
Also why is this P0?

Correction: this is not used for sidecar to sidecar communication PER SE, it's used for Actors to announce their host names to the placement service, and thus is used for actor proxying communication.
Also why is this P0?

Updated description to make it clear that his IP is used for Actor proxying communication after being announced to placement service.
Removed P0 since this will be a team discussion.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_78e0a3bc-3463-49ef-a0cd-8e96c3b27b86/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_78e0a3bc-3463-49ef-a0cd-8e96c3b27b86.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


feat(tasks): cancel pending task

Undropping a table (#324) requires us to cancel the queued tasks that would perform the drop. For this we need to add a cancel_task function to the TaskQueue trait. For now, we should only be able to cancel pending tasks.
Cancelling running tasks requires a more complex design and also a decision if we even want to support that. Being able to cancel running tasks, can leave things in unknown states. Conversely, it enables us to stop misbehaving tasks. Given the involved complexity, we should leave this out for now and address it in a follow up issue.

#517 implements a specific solution used for undropping tables


Bashellite does not have an option to specify a config file on command-line

Now that bashellite uses a configuration file located in /etc/bashellite, it is hard to test changes to repo filters without affecting a live install.

Fixed by PR #40


Add support to use BOARD mode

Add support to use BOARD mode. BCM mode should be default. Mode could be at the beginning of the program (as in RPi.GPIO) or for each device separately (led = LED(7, mode=BOARD)).

Duplicate of #467.
This has been debated back-and-forth. We distinctly only supported a single numbering system in the beginning, to keep things simple. Your best bet is to use a port label or the pinout command line tool.

If you were to support both ways, but one would be default, it would not be more complicated.
In addition, I am interested in how to support the older versions of Raspberry Pi, which have a different labeling without changes.

But any resources people make will vary - some using one numbering system, some using another.
GPIO Zero works with any Pi model, as BCM pin numbers work wherever they're located on the board. And the pinout tool will show you an accurate pinout diagram for the Pi you're on.


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Starting work on this task. I'll be adding information to contact me.

Contact info completed and added to the resume

Add links to social networks

Add links to my social networks, phone number, email, etc. To make it easier for the community to contact me and get to know each other better.

Contact info completed and added to the resume


Support MQTT 5 protocol

Folks, we love your work, please help support MQTT 5 protocol,
Cheers,

For the reference this has a very good implementation of MQTT V5.

Support MQTT 5 protocol And Cluster. May refer to https://github.com/wind-c/comqtt .

Support MQTT 5 protocol And Cluster. May refer to https://github.com/wind-c/comqtt .

would be great for us users if a way could be found to have those updates in comqtt merged back here to this project

@torntrousers I will definitely be having a deeper look at @wind-c 's implementation of some of these features. I am very impressed what they have accomplished.
For mochi-co/mqtt it's important to consider the purpose of the library - which was (originally) to provide a minimalist, high performance embeddable library. We've aimed for the smallest, simplest amount of code possible in order to achieve these goals, so when it comes to features like clustering, there's a lot to consider.
I do think it would be nice to add these features, but they need to be balanced against maintainability and performance - and there's a few areas nin the existing codebase we need to improve first (like #101) :)

For sure, all good for me and thats why we use this project.


Expose signer

This PR introduces a significant enhancement to the hardhat-deploy repository by exposing the signer functionality for various purposes. This change has been made to enhance the usability and flexibility of the library in different scenarios.
Motivation:
The motivation behind this PR is to address several use cases where direct access to the signer is necessary, including but not limited to:
Custom Signings: Developers often require the ability to perform custom signings for specific transactions or interactions with smart contracts. By exposing the signer, users can now implement their custom signing logic easily.
Integration with External Wallets: This change facilitates integration with external wallets, allowing users to seamlessly use their preferred wallet providers within hardhat-deploy workflows.
Advanced Smart Contract Interactions: Some advanced use cases, such as multi-signature wallets or complex smart contract interactions, require direct access to the signer. This PR enables these use cases without extensive workarounds.

you want access to the signer that hardhat-deploy figure from the accounts names it allow you to setup, right ?
because otherwise, hardhat itself provide access to signer

you want access to the signer that hardhat-deploy figure from the accounts names it allow you to setup, right ?
because otherwise, hardhat itself provide access to signer

@wighawag Yeah, I need signer (EOA/trezor/ledger/...) to pass as an argument to protocol-kit of @safe-global (ref: etherAdapter). Hardhat itself does not support trezorSigner.

Thanks @huyhuynh3103
available in v0.11.39


Pull Request from Capston-1-desktopAndMobile branch to Master

Project Requirements are as follows

Should follow these design guidelines, including:

Colors.
Typography: font face, size and weight (we suggest using Lato as it is a free font similar to the one used in the original design).
Layout: composition and space between elements.

The pages should look almost identical to the original design. Small adjustments like text or image changes are acceptable.
You should build only these 2 pages: (The home and the about page)
Each of these pages should have versions for 2 different screen sizes: (Mobile max 768px and for others min 768px).
Interactions:

Links

The home page should have a link in the menu to the about page.
The logo in the header links to the home page.

Mobile menu:

When the user clicks (or taps) the hamburger button on the header, the mobile menu appears over the page.
There are no guidelines for the mobile menu in the docs, but you should implement it so it is consistent with the design (colors, typography, spacings, etc.).
The mobile menu should have a close (X) button that closes the menu.

Dynamic page:

The section "Featured speakers" should be created dynamically in JavaScript.
You should use a JavaScript variable with the data about the speakers and use it when the page loads to create the HTML for this section dynamically.

Video description of the Project.

for more information please visit the requirements page

Video description of the project has been added in the PR description.


Add Verification Manual VM8

This PR adds VM8, with good step by step explanations, how to provide full simulation of
the Parametric Calculation of Point-to-Point Distances.
VM8:
1st commit:  code almost done with idea how to modify mapdl.ndist at the main script

Hi Alex(@akaszynski) and German(@germa89),
may I ask someone of you to review VM8 when it will be comfortable for you?
p.s.
I have changed a bit of pandas data frame. If you like it, I can add it to ansys -> mapdl -> core ->misc.py  as the function that can be useful for all docs.
Thank you in advance!

Hi @RomanIlchenko1308
Please do not include any style in the dataframe, I believe we are better moving towards a theme definition of the table style.
Therefore, after getting the pandas dataframe, just call df.style. See this:
# Create and fill the output dataframe with pandas.
df2 = pd.DataFrame(main_columns, index=row_names)

# Apply style settings for the dataframe.
df2.style

It should look like:

Please check:
https://github.com/pyansys/pyansys-sphinx-theme/pull/17

Thank u German for your feedback!
About data frame code
I will leave it until I have not merged the data frame PR #848.
When I finish that, I will create new PR with New branch and I will go through all VMs and substitute the print f output tables with pandas data frame.
I will finish PR of VM10 during a few hours, and I'll be back to check all your suggestions and apply them.
Thank you again for your feedback!

You haven't address (almost) any of the changes I proposed you. Hiding the sphinx tag, removing the extra files and the pandas dataframe configuration code is needed for me to approve this PR.

Hi @germa89,
As we have discussed, yesterday, I would like to summarize the work done:

I have left the # sphinx_gallery_thumbnail_path = '_static/vm8_setup.png' in the topic Start MAPDL.
I have modified a script with decorators @property.
Where I have some doubts it is about extra files, here I would like to ask you to give me a hand with it?

Thank you in advance!

Hi @germa89
I have removed style settings, just left the df2.style.format("{:.2f}") to obtain 2 decimals.
The VM8 is ready to be reviewed.
Thank you in advance sir and great work with CSS and HTML settings for web pages!!! Thank you!


Feat support unity packages

Changes

...

Checklist

[ ] Read the contribution guide and accept the code of conduct
[ ] Readme (updated or not needed)
[ ] Tests (added, updated or not needed)

whoops, accidentally made on of the draft PRs from my fork into this project instead. Sorry about that 😅


feat: add morpho assets

This PR adds some Morpho assets that were requested.

PR-Codex overview
This PR adds new Morpho assets to the packages/environment/src/assets/ethereum.ts file, enhancing the asset listing under the ERC_4626 type for various protocols.
Detailed summary

Added multiple new assets with the MORPHO protocol, including:

gtUSDACore, gtDAICore, Re7FRAX, Re7USDA, gtWETH, bbETH, gtLRTcore, Re7WETH, MCwETH, USUALUSDC+, steakUSDC, gtUSDC, steakUSDT, bbUSDT, gtUSDT, USDC RWA, Re7USDT, reUSDC, fxUSDC, sbMorphoUSDC, MC.eUSDC, apUSDC, bbUSDC, Re7USDC.

Each asset includes details such as symbol, name, id, type, protocol, releases, decimals, underlying, and priceFeed.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

https://app.shortcut.com/enzyme/story/8879/potential-biz-case-cooperation-with-morpho-add-lending-pools-in-the-ui


bug: icons alignment in footer

social icons are not properly aligned in footer of Home Page.

@DivyanshiNarang Assigned.
Make sure to join the discord server of all contributors - https://discord.gg/fgMHHP4Kcq

If it's still not done, can you please assign me this task!


Update deps minus rollup and babel and remove del.

My plan was to drop gulp completely, but I'm not sure if/when I'll get the time to do it so this was easier  for now.

Thanks 👍 @XhmikosR


PCBS and Parquet support ANSI year month interval type [databricks]

Closes #2814

Parquet support ANSI year month interval type
PCBS support ANSI year month interval type

Signed-off-by: Chong Gao<EMAIL_ADDRESS>

build

build

build

Should re-target branch-22.06, convert it to draft.

build

@razajafri  Help review, thanks.

LGTM

@res-life why are we choosing to write scalatest when as a convention we write python tests? It makes sense to do scala tests for situations where writing a python test isn't possible e.g. writing a unit test for a private method or may be you have to inject variables into a class before testing. We also use python tests in environments where it's not possible for us to run scala tests.

@razajafri
Currently Pyspark does not have year month type, please see
https://github.com/apache/spark/blob/branch-3.3/python/pyspark/sql/types.py
Day time type is supported in
SPARK-37279 Support DayTimeIntervalType in createDataFrame, collect and Python UDF
Is waiting the Spark to support year month type.


Refactor progress, composition, focus events

This is a work item for #685.
progress:

[ ] https://developer.mozilla.org/en-US/docs/Web/Events/abort_(ProgressEvent)
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/error_(ProgressEvent)
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/load_(ProgressEvent)
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/loadend
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/loadstart
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/progress

focus:

[ ] https://developer.mozilla.org/en-US/docs/Web/Events/blur
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/focus
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/focusin
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/focusout

composition

[ ] https://developer.mozilla.org/en-US/docs/Web/Events/compositionend
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/compositionstart
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/compositionupdate

AC:

all pages migrated and reviewed
BCD updated

@chrisdavidmills I am as usual confused about the proper targets for the progress events. I'm pretty sure XMLHttpRequest is one target, so I've migrated them under there: https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest#Events.
I've also added a live example and all the other stuff that was missing from these terrible old pages.
It seems as though they are also on FileReader (see https://searchfox.org/mozilla-central/search?q=ProgressEvent&path=).
The docs pages themselves suggest they are also on image and video elements, but although I can get events on those elements with names like loadstart, load, progress, they don't seem to be actual ProgressEvent objects (they don't have the loaded or total properties). Do you know what the story is here?

@wbamberg you sure do pick the fun ones ;-)
So, the FIle API definitely uses proper ProgressEvents for event objects: https://www.w3.org/TR/FileAPI/#event-summary
As for images and video, is it not just that they inherit from HTMLElement: https://html.spec.whatwg.org/multipage/dom.html#htmlelement
Which implements the GlobalEventHandlers mixin: https://html.spec.whatwg.org/multipage/webappapis.html#globaleventhandlers
?

As for images and video, is it not just that they inherit from HTMLElement: https://html.spec.whatwg.org/multipage/dom.html#htmlelement

Which implements the GlobalEventHandlers mixin: https://html.spec.whatwg.org/multipage/webappapis.html#globaleventhandlers

Oh thank you, that does make sense (I think). Except that these are just Event objects, so the documentation is consistently wrong here (as it suggests that listening to, say progress on a video will get you a ProgressEvent).
But also! Your link points to https://html.spec.whatwg.org/multipage/media.html#event-media-progress, which seems to be telling me that these events are fired only on media elements (https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement, presumably) - and AFAIK this does not include image elements, so the existing docs are wrong there, too?
So it seems like what we should do here is: write pages for the relevant events under https://html.spec.whatwg.org/multipage/media.html#event-media-progress (specifically, I guess, loadstart, progress, abort, error) and hang them off HTMLMediaElement?

I've added:

pages for these events on FileReader: https://developer.mozilla.org/en-US/docs/Web/API/FileReader#Events along with a live example for most of them.

pages for loadstart, progress, abort, error on HTMLMediaElement: https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement#Events along with a live example for some of them.

Good approach Will — I think this works well, and I really like the live examples.
I've looked through the pages and they generally seem pretty decent. the FileReader events section is missing the opening paragraph about using addEventListener, and I wonder whether the live examples need a note to say that you could also use on... handler properties instead of addEventListener()?

@chrisdavidmills , I reckon these pages are ready for a look.
progress events
This is as noted in https://github.com/mdn/sprints/issues/1101#issuecomment-470346536. I added the paragraph in FileReader#Events as you asked, but didn't add a note to the live samples - I could, but it seemed like hammering the point.
focus events

Element: https://developer.mozilla.org/en-US/docs/Web/API/Element#Focus_events
Window: https://developer.mozilla.org/en-US/docs/Web/API/Window#Focus_events

As far as I can tell Window is not a target for focusin or focusout, contra the docs.
composition events

Element: https://developer.mozilla.org/en-US/docs/Web/API/Element#Composition_events

Interestingly these do not seem to have a corresponding on- property. I managed to get a live sample but I don't know how to trigger it except on macOS. I'd be happy to make it multiplatform but I don't know how. We could use a guide to working with input method editors for this stuff, as they are hard to understand without that context.

Hi @wbamberg ! Some feedback for you (these largely look really good):
FileReader events

The pages for onloadend/onloadstart/onprogress seem to be missing.

Element focus events

The pages for onfocusin/onfocusout seem to be missing
These still have the old-style compat tables. I'm assuming you are waiting to submit the BCD before updating them?
The event pages for these (and the Window events) seem to have two extra columns in the blue boxes — "Sync/Async" and "Composed" — which I've not seen before. How many event pages have you come across that have these? Should we add these for other event pages; I guess you're keeping them because it is not a good idea to arbitrarily delete information that might be useful, which I think is a good call for now. But we'll need to think about this for the future maintenance work.

Window focus events

In the window.focus page you still mention window.focusin, even though it doesn't exist.

Composition events

Yup, some events do not have corresponding event handlers. It is rare, but I've seen it before.
The example is is a difficult one. I think composition events might be easier to fire on mobile browsers, e.g. through an IME, but I'm no exxpert here. If we did want to write something more cross-platform, it might be worth asking one of the engineers in this area, like Masayuki.
I struggled to get these events firing even on Mac. I think you really mean Opt when you say Alt? Maybe say Opt/Alt, as I'm sure a large number of mac folk know it as Opt. Also, maybe write in some more specific insrtructions, e.g. focus the input element. then press Opt/Alt + `, then press a, or some other printable key (most seem to work?).

Thanks Chris.

FileReader events

The pages for onloadend/onloadstart/onprogress seem to be missing.

I'm not proposing to add these pages where they don't exist as I feel it's out of scope for refactoring the existing event ref pages. I can if you like though, but of course it will make everything take longer.

Element focus events

The pages for onfocusin/onfocusout seem to be missing

Yup, as above.

These still have the old-style compat tables. I'm assuming you are waiting to submit the BCD before updating them?

Yes.

The event pages for these (and the Window events) seem to have two extra columns in the blue boxes — "Sync/Async" and "Composed" — which I've not seen before. How many event pages have you come across that have these? Should we add these for other event pages; I guess you're keeping them because it is not a good idea to arbitrarily delete information that might be useful, which I think is a good call for now. But we'll need to think about this for the future maintenance work.

Yes, basically this (especially "Composed" - although we ought to explain somewhere that that means, since it is very non-obvious to me) seemed useful, and I don't think it's a good idea removing potentially useful entries without having thought about what this box should contain.
I don't really want to go back adding these rows to all the other tables at this stage. In general I think it's not realistic or a sensible use of our time to expect this degree of consistency out of the Wiki. If we want to keep these boxes, and we want a high degree of consistency, then in the medium term one approach could be to keep the data in mdn/data and build it using a macro. Long term we should fold it into an overall structured content plan.

Window focus events

In the window.focus page you still mention window.focusin, even though it doesn't exist.

Oops. Removed.

Composition events

The example is is a difficult one. I think composition events might be easier to fire on mobile browsers, e.g. through an IME, but I'm no exxpert here. If we did want to write something more cross-platform, it might be worth asking one of the engineers in this area, like Masayuki.

We could ask. I don't have contacts there though. I don't think we should block this work for that.

I struggled to get these events firing even on Mac. I think you really mean Opt when you say Alt? Maybe say Opt/Alt, as I'm sure a large number of mac folk know it as Opt. Also, maybe write in some more specific insrtructions, e.g. focus the input element. then press Opt/Alt + `, then press a, or some other printable key (most seem to work?).

Thanks, I've tried improving the instructions. I didn't say "some other printable key" since I think giving very specific instructions is likely to be more helpful.

I'm not proposing to add these pages where they don't exist as I feel it's out of scope for refactoring the existing event ref pages. I can if you like though, but of course it will make everything take longer.

Nah, that's fine. As we agreed in that other thread with @a2sheppy , we are gonna leave creating new pages for now, to make the scope of work more manageable.

I don't really want to go back adding these rows to all the other tables at this stage. In general I think it's not realistic or a sensible use of our time to expect this degree of consistency out of the Wiki. If we want to keep these boxes, and we want a high degree of consistency, then in the medium term one approach could be to keep the data in mdn/data and build it using a macro. Long term we should fold it into an overall structured content plan.

That's perfectly fine, and makes sense.

We could ask. I don't have contacts there though. I don't think we should block this work for that.

I'm in favour of leaving this for now, as we have enough to do already. This could be part of a future maintenance run.

Thanks, I've tried improving the instructions. I didn't say "some other printable key" since I think giving very specific instructions is likely to be more helpful.

This is much better. I just increased the height of the live examples to avoid a vertical scrollbar on Firefox; I'm happy with this now.
So I think one looks done. Happy to close if you are. Oh, wait, do we have BCD in place for these?

do we have BCD in place for these?

I have a PR for it: https://github.com/mdn/browser-compat-data/pull/3585. It would I guess be great to get it reviewed before tomorrow's push. If you don't have time I could ask someone else though.

do we have BCD in place for these?

I have a PR for it: https://github.com/mdn/browser-compat-data/pull/3585. It would I guess be great to get it reviewed before tomorrow's push. If you don't have time I could ask someone else though.

I forgot to update BCD for focus events. I have just filed https://github.com/mdn/browser-compat-data/pull/3650 for that.

BCD is updated and deployed, pages are refreshed. Closing.


Recursively defined type fails to be applied

module RecDeps

let rec add_n_t (n:nat) : Type =
    if n = 0 then int
    else int -> add_n_t (n-1)

let f (ff : add_n_t 2) : int = ff 3 4

Gives:
RecDeps.fst(7,36-7,37): (Error 173) Too many arguments to function of type RecDeps.add_n_t 2; got 2 arguments, remaining type is if 2 - 1 = 0 then Prims.int else _: Prims.int -> Prims.Tot (RecDeps.add_n_t (2 - 1 - 1))

This is caused by the normalizer not reducing 2 - 1 = 0 when HNF is on. It should descend into the 2 - 1 when the head (=) is a primop.
This dirty patch makes it work. I'll test for regressions and get it merged later.
diff --git a/src/typechecker/FStar.TypeChecker.Normalize.fs b/src/typechecker/FStar.TypeChecker.Normalize.fs
index 687a8f9f3c..6facfd73e7 100644
--- a/src/typechecker/FStar.TypeChecker.Normalize.fs
+++ b/src/typechecker/FStar.TypeChecker.Normalize.fs
@@ -2395,11 +2395,24 @@ and rebuild (cfg:cfg) (env:env) (stack:stack) (t:term) : term =
         log cfg (fun () -> BU.print1 "Rebuilding with arg %s\n" (Print.term_to_string tm));
         // this needs to be tail recursive for reducing large terms

+        let is_primop_app (t:term) : bool =
+          match (SS.compress t).n with
+          | Tm_app (h, _) ->
+           begin match (U.un_uinst h).n with
+            | Tm_fvar fv -> begin match find_prim_step cfg fv with
+                            | Some _ -> true
+                            | None -> false
+                            end
+            | _ -> false
+           end
+          | _ -> false
+        in
+
         // GM: This is basically saying "if exclude iota, don't memoize".
         // what's up with that?
         // GM: I actually get a regression if I just keep the second branch.
         if not cfg.steps.iota
-        then if cfg.steps.hnf
+        then if cfg.steps.hnf && not (is_primop_app t)
              then let arg = closure_as_term cfg env_arg tm in
                   let t = extend_app t (arg, aq) None r in
                   rebuild cfg env_arg stack t
@@ -2407,7 +2420,7 @@ and rebuild (cfg:cfg) (env:env) (stack:stack) (t:term) : term =
                   norm cfg env_arg stack tm
         else begin match !m with
           | None ->
-            if cfg.steps.hnf
+            if cfg.steps.hnf && not (is_primop_app t)
             then let arg = closure_as_term cfg env_arg tm in
                  let t = extend_app t (arg, aq) None r in
                  rebuild cfg env_arg stack t


[WebtoolsE2E] [Multiple docs] The .NET Aspire Orchestrator Support dialog screenshot needs to be updated because the Aspire Version displayed.

Describe the issue or suggestion
Issue description
In Tutorial: Add .NET Aspire to an existing .NET app docs, we need to update some instructions.
Issue1:
For Add .NET Aspire to the Store web app section, document shows no Aspire Version in .Net Orchestrator Support dialog.

EXPECTED:
The Aspire Version displayed in the .NET Aspire Orchestrator Support dialog.

Associated WorkItem - 341261

This issue has been fixed, and I can no longer to reproduce it.


Add missing spec_helper require to process/constants_spec

This was a FIXME statement marked by @nanobowers in the Natalie project

It might be nice to have a CI check/small Ruby script to catch this kind of things.

@eregon I wrote a small script to find these, and it looks like there are 130 **/*_spec.rb files that should have a require_relative "....../spec_helper" added to them.  It should not be much trouble to add a mode to fix these files.
If a check script is added to the CI, would it live in this repo or somewhere else (mspec)?

If a check script is added to the CI, would it live in this repo or somewhere else (mspec)?

https://github.com/ruby/mspec/tree/master/tool is the right place for that.


examples: add gtk4 femtovg example

This has been requested a few times in the matrix channel, should be stable enough to upstream now

The code looks good but the screenshot doesn't :) would you mind fixing that?

Whoops, that was https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6050


Link to travis-ci.com tests

as shown in the text above, we should link to the travis-ci.com instead of travis-ci.org tests!

I believe this is no longer necessary since we have switched to GitHub Actions @apeltzer?

True - an ancient issue of the forefathers and foremothers so to say 😂