[WIP] Make named pipe IPC opt-in

PR Summary
This PR makes the IPC named pipe listener, which currently always runs, opt-in.  This addresses issue #11599.
PR Context
Since about PowerShell 5.0, every PowerShell session has a running IPC (inter-process communication) listener that allowed other PowerShell sessions on a local machine (with appropriate privileges) to attach to it and debug running script.  One downside to this is on non-Windows platforms where the created named pipe used for the connection does not always get cleaned up after the session process terminates.  Another drawback is that an extra listener thread always runs in a PowerShell session, that is rarely used.
The fix is to make the IPC listener thread opt-in, through both a new -StartIPCListener pwsh.exe parameter and a new System.Management.Automation.Runspaces.Runspace.StartIPCListener() API.  This makes debugging running script on other PowerShell sessions less convenient but still doable.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[x] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[x] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

We discussed this some more and agree that opt-out would be less disruptive and still allow users not to have the listener running.  However, the original concern (#11599) was about named pipe files being littered on non-Windows platforms, if PowerShell is abruptly terminated (clicking on the terminal window close button rather than running exit command).  I did some investigation and dotNet puts the named pipe file in the users /tmp directory.  But it turns out that the CLR also creates three temporary files (two of which are used for debugging), and these files also get leaked.  So disabling PowerShell named pipe listener will not completely solve the problem.  The good news is that these files do get cleaned up on machine reboot, so those temporary files will not remain indefinitely.

Based on the current behavior, I agree that Opt-in is a better model as we are getting many reports of this failing very frequently in Ubuntu 22.04

Could pwsh on startup run in a separate thread a method that cleans up older pipes where the PID for that path has already exited? It would be annoying for this to become opt-in as I do fine it quite useful that Enter-PSHostProcess just works without having to respawn a new process.

@jborean93 I agree that the listener always running is pretty convenient, but it is good to get community input to verify that.  The system already cleans up these temporary files on machine reboot (maybe even user log in/out, but not sure), so I don't think it is necessary to have PowerShell add a redundant cleaning mechanism.  At this point I feel opt-out is the right thing to do (sorry if I wasn't clear).  This is similar to what dotNET CLR does now (via environment variable) and gives users the option to opt-out of the listener, and not have littered files causing false alerts, but by default the listener will continue to always run on session start.

Closing this PR due to change from opt-in to opt-out preference.

Is there a PR that implements the opt-out preference?


clean up removing bayes search

clean up remnants of bayes hyperparameter search

Codecov Report
Attention: Patch coverage is 83.33333% with 3 lines in your changes missing coverage. Please review.

Project coverage is 93.19%. Comparing base (800fd5b) to head (af32ac6).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

autoemulate/emulators/gaussian_process_mogp.py
0.00%
1 Missing :warning:

autoemulate/emulators/gaussian_process_sklearn.py
0.00%
1 Missing :warning:

autoemulate/emulators/neural_net_sk.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #272      +/-   ##
==========================================
+ Coverage   92.43%   93.19%   +0.76%
==========================================
  Files          62       62
  Lines        3635     3573      -62
==========================================
- Hits         3360     3330      -30
+ Misses        275      243      -32

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


🚀 Feature: Home Page Quick Start Card

🔖 Feature description
A Quick Start card on the home page can be helpful for new users to get up to speed on their companies internal developer portal.

https://github.com/backstage/backstage/assets/146387693/b7dff080-d490-465d-a478-6f48961c3e42
🎤 Context
Our team frequently receives questions about our new IDP and requests for help with onboarding. So, our product and design team created this Quick Start card to link users to the most important information when they first land on the IDP.
We thought this might be helpful for other Backstage adopters, but we want to get an opinion on this before submitting a PR contributing to the [@backstage/plugin-home](https://github.com/backstage/backstage/blob/master/plugins/home/api-report.md)
✌ Possible Implementation
The following displays all of the features of the card we have implemented on our end. We would contribute this as a basic QuickStart card, where a developer can pass in props to populate the card specifically for their company
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

friendly ping to @backstage/home-maintainers

Hello @nikolarAutodesk, thanks for opening this issue! Looks like a really good addition to the group of optional Homepage cards adopters can use for Backstage. I'll add a "help wanted" label to the issue so feel free to let us know if you are planning to work on it and we can assign you to the issue.

I'd like to work on this during KubeCon Contribfest

Thanks @nikolarAutodesk, I've assigned it to you 🚀

Hi @awanlin I am not sure what happened, but my PR did not automatically request a reviewer. Was there a process change? Do I need to request specific people?

closing this issue since the related PR has been merged: https://github.com/backstage/backstage/pull/27705


Cannot support NixOS

This hook will download .cache/pre-commit/repon0nie2em/py_env-python3.10/lib/python3.10/site-packages/clang_format/data/bin/clang-format for me. However, My OS is NixOS, which doesn't respect HFS so it must patchelf every program. Inspired by https://github.com/ntkme/sass-embedded-host-ruby/issues/116, I NIX_BINTOOLS=/nix/store/ngh5s155lcm1hwsakrfhla536x9g5v4z-binutils-wrapper-2.40 pre-commit run -a. It works for https://github.com/scop/pre-commit-shfmt, but cannot work for this hook. How to make it work?

You should ask your question here instead: https://github.com/ssciwr/clang-format-wheel.

sometimes you have to expect that nix is the problem and not everything else


Update Readme with Setup instructions

Update Readme with Setup instructions : Closes #90
Acceptance Criteria fulfillment

[x] Make Readme More attractive.
[x] Add Setup instructions

Proposed changes (screenshots)

 Before

 After

@ninadvyas the before after screenshots aren't showing up for me

@samad-yar-khan might be able to confirm if that's the same

@ninadvyas the before after screenshots aren't showing up for me
@samad-yar-khan might be able to confirm if that's the same for him

@jayantbh  they are showing for me

@jayantbh of the changes didn't see on your side you can check out on  https://github.com/ninadvyas/unwrapped
you can see the changes in readme file in my forked repository.

ok. Thanks for the feedback ill let you know after I fixed the changes @samad-yar-khan

Do you need anything else to be added @samad-yar-khan rather then the changes that you have mentioned??

Thanks for the contribution @ninadvyas 🚀


Spell error in the particle_system.py

line 19 and 20, domain is misspelled as domian, which lead to wrong domain size
self.domain_end = np.array([1.0, 1.0, 1.0])
self.domian_end = np.array(self.cfg.get_cfg("domainEnd"))

ah i got it wrong, domain size is correct because it uses “domian_end”
how can i delete this issue？😂


Extreme value search among one attribute and multiple nodes

Define an extreme value based on an attribute (e.g. wind) and it finds the corresponding extreme value among all nodes.
Previously, only an attribute-node pair was allowed for extreme value identification (e.g. wind-dena72).

@YoungFaithful


Offline Embedding ERROR

Hi, I used Prokka to predict protein sequences from metagenomic data and now want to use DHR for protein homologue prediction. However, when I tried to embed the protein sequences generated by Prokka, I encountered the following error and I'm not sure what went wrong. I would greatly appreciate your help in resolving this issue. Additionally, I have another question: Could you please explain how to use the two models, dhr_cencoder.pt and dhr_qencoder.pt?
python3 /home/xxx/00.Software/Dense-Homolog-Retrieval/do_embedding.py trainer.ur90_path=/home/xxx/10.meta-genome/01.sheep_gut/05.DHR/sheep_gut.faa   model.ckpt_path=/home/xxx/00.Software/Dense-Homolog-Retrieval/dhr_cencoder.pt  hydra.run.dir=./test
/home/xxx/00.Software/Dense-Homolog-Retrieval/do_embedding.py:40: UserWarning:
The version_base parameter is not specified.
Please specify a compatability version level, or None.
Will assume defaults for version 1.1
  @hydra.main(config_path="conf", config_name="pred_conf")
/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/hydra.py:119: UserWarning: Future Hydra versions will no longer change working directory at job runtime by default.
See https://hydra.cc/docs/1.2/upgrades/1.1_to_1.2/changes_to_job_working_dir/ for more information.
  ret = run_job(
Seed set to 1234
Error executing job with overrides: ['trainer.ur90_path=/home/xxx/10.meta-genome/01.sheep_gut/05.DHR/sheep_gut.faa', 'model.ckpt_path=/home/xxx/00.Software/Dense-Homolog-Retrieval/dhr_cencoder.pt']
Traceback (most recent call last):
  File "/home/xxx/00.Software/Dense-Homolog-Retrieval/do_embedding.py", line 80, in <module>
    main()
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/main.py", line 94, in decorated_main
    _run_hydra(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
    _run_app(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/utils.py", line 457, in _run_app
    run_and_report(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
    raise ex
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
    return func()
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
    lambda: hydra.run(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "/home/xxx/00.Software/Dense-Homolog-Retrieval/do_embedding.py", line 55, in main
    model = MyEncoder.load_from_checkpoint(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/pytorch_lightning/core/module.py", line 1552, in load_from_checkpoint
    loaded = _load_from_checkpoint(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/pytorch_lightning/core/saving.py", line 64, in _load_from_checkpoint
    checkpoint = _pl_migrate_checkpoint(
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/pytorch_lightning/utilities/migration/utils.py", line 142, in _pl_migrate_checkpoint
    old_version = _get_version(checkpoint)
  File "/home/xxx/miniconda3/envs/fastMSA/lib/python3.9/site-packages/pytorch_lightning/utilities/migration/utils.py", line 163, in _get_version
    return checkpoint["pytorch-lightning_version"]
TypeError: tuple indices must be integers or slices, not str

I have the same problem

The feeling is that the version of pytorch lightning written in the model is inconsistent with the version of pytorch lightning read in

Hello, thanks for trying. The yaml file to build the environment has been updated. The code base in main branch seems to corrupt with v1 branch, and I am currently cleanning it. Sorry for the inconvenience.

The codebase has been updated and please try to pull again. Thank you.


How to fix "file length is too long to create"?

Describe the bug
Can't download course, because file length is too long to create.
To Reproduce
Steps to reproduce the behavior:

udemy course url: https://www.udemy.com/course/phpmasterwfs/
Run the following command to reproduce the error.
See error

Expected behavior
I think download just started.
Screenshots

Python Environment (please complete the following information):

OS Platform: Windows 10
Python Version 3.7.4

Additional context
Add any other context about the problem here.

@Aragorn5534 you should be using --unsafe switch in front it will solve your problem

It helps. Thank you.


[OSCI]: add author skollryu md

Description
Add a markdown page for myself
Issues Resolved
N/A
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@ashwin-pc resolved. Please Check. Thanks


Enable usage of context path in EmbeddedJavalin

Came across this when embedding Javalin into a vaddin flow app, as far as I can tell there is nothing that interacts with jetting when removing the override like this.
Would save me a ton of time to be able to drop the common prefixes I'm having to add to every route.

Did you test this? Shouldn't context-paths be handled by whatever you are running Javalin on, not Javalin itself?

This has been released as part of 2.5.0 now: https://javalin.io/news/2019/01/04/javalin-2.5.0-released.html


Support for Control Replication in the Default Mapper

The default mapper needs to be updated to support control replication. This is a prerequisite for #765. Note that there are probably several interface changes to the mapping interface that will be required for this as well so that the mapper has the information that it needs to make the decisions that it wants to.

At this point people have had many years to work on the default mapper and I think we've settled on a good set of heuristics for it so in preparation for the control replication merge I am closing this issue.


Sync Mangadex v5 "My Lists" to neko categories

Essentially, I want my categories to be lists and my lists to be categories.

if this gets added in the future it would probably be a one time sync, and not a real time sync

So with the new custom lists that will go to production at some point. You will be able to group the library by your custom lists whatever they are named. So I won't be adding this specific syncing


Some new Google resources.

I have added 2 new Google resources to the list.

Hi @climent,
Thanks a lot for the new entries! :) 👍


Hover glow effect button Added

Fixes Issue
#1258
Changes proposed
Want to add Hover glow effect button
Screenshots

Checklist

[x] You've linked this PR to the correct issue.
[x] You have checked that the code is working correctly.
[x] You ⭐ the repository!

Video
https://github.com/Spyware007/Animating-Buttons/assets/114821855/726c3bcf-ea40-4d17-acaf-5fd3114000bd
Note to reviewers

Please check #1346


Active navlink according to the page

Describe the bug
On the navbar it's not showing the current page in which we are. On every page, it's showing home is the active navlink.
To Reproduce
Steps to reproduce the behavior:

Open index.html
Then click on any navbar link/item to open the respective page
When the new page is loaded then take a look on the navbar

Expected behavior
Navlink should be active according to the current page we are in. eg. - When we are in about page then "About us" should be active (i.e. underlined).
Screenshots

Hey, I would like to work on this issue.

@Anshpatwal Go ahed.


[microstream] Update common files for branch master

Update common files

It keeps trying this... not sure why...


Download / Local server?

Hi,
Old time OS/2 fan... is there anyway to download it and run it locally on a server ?

Hi @leonbollerup
Yes, you need to download a repository.
Then please use 'virtualenv' for Python 2.x
virtualenv ve
source ./ve/bin/activate
And install required packages (mostly Flask)
pip install -r requirements.txt
And run
python ./main.py


cors problem when querying over jsonld file with vc

No results for queries over jsonld resources with VC.

Explanation of the CORS problem:

when we load a .jsonld file
and that .jsonld file results in the browser loading a context file
and the server serving does not provide an appropriate CORS header (w3.org!)
then we get this error!

But...

we are requesting ntriples to the Solid server
in which case the Solid server translates the .jsonld file to ntriples
and avoid the CORS problem

So... what's happening here? Maybe some extra testcase info will help.

This happens on the https://pod.playground.solidlab.be/, logged in as<EMAIL_ADDRESS>
(The Accept header in the request is as intended)

Info: same exercise on https://css11.onto-deside.ilabt.imec.be works.
Is this an issue of the playground?

This happens on the https://pod.playground.solidlab.be/, logged in as<EMAIL_ADDRESS>
(The Accept header in the request is as intended)

What's the actual result when you're logged in? nquads or jsonld? Maybe the playground for some reason can't handle graphs?

On the Solid Playground, the returned content type is application/ld+json.
On our CSS it is application/n-quads.
Same code calling in both cases, same request headers etc...
Many details in illustrations below.
Questions:

why does the Solid Playground behave like this?
do we have to work around this from our side to be safe for portability to other Solid servers?

When logged in to CSS
Overview

Headers on the GET of products

When logged in to Solid Playground:
Overview

Headers on the GET of products

The only thing I can think of is that the playground for some reason doesn't support quads, and you could try accept: text/turtle before jsonld to see whether that solves it. turtle is a MUST for LDP, so we should at least assume every server can handle that one

More observations:
// original (goes wrong, returns application/ld+json)
Accept: "application/n-quads,application/trig;q=0.95,application/ld+json;q=0.9,application/n-triples;q=0.8,*/*;q=0.1"
// original modified: delta between q factors 0.1 (works, returns application/n-quads)
Accept: "application/n-quads,application/trig;q=0.9,application/ld+json;q=0.8,application/n-triples;q=0.7,*/*;q=0.1"
// original modified: delta between q factors 0.1 and replaced application/ld+json with text/turtle (works, returns application/n-quads)
Accept: "application/n-quads,application/trig;q=0.9,text/turtle;q=0.8,application/n-triples;q=0.6,*/*;q=0.1"

The problem is that in contrast with the CSS's (v7.0.2) on https://....onto-deside.ilabt.imec.be/, the CSS in the Solid Playground https://pod.playground.solidlab.be/ (v7.x.x) does not follow q factor priorities as expected with the q values in the original Accept header we were using.
This seems solved by changing the q factors so that they differ at least 0.1, see the second Accept header above.
I filed an issue for that in the CSS repo.
Finally, for the viewer I'll use the third Accept header, to be sure: we don't wont application/ld+json at all.


WSLg ignores ignores minimum size of X11 windows.

Windows build number:
10.0.19045.0
Your Distribution version:
Debian 12
Your WSL versions:
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.4170
Steps to reproduce:

Open any X11 GUI app, like glxgears.
Resize the window as small as it can get.

WSL logs:
No response
WSL dumps:
No response
Expected behavior:
Windows using X11 should not be resizable to a size smaller than their minimum size.
Actual behavior:
WSLg lets you resize any X11 window to any size, even 1x1 pixels.
Left: VSCode running on Windows at it's minimum size. Right: VSCode running on WSL with a size smaller than it's minimum size.

Left: VSCode running on Windows at it's minimum size. Right: WSL VSCode running on Wayland. It cannot be resized to be smaller than it's minimum size.

@Klemmbaustein you're accessing the X server via RDP session. That might influence the controls of the windows shown on your desktop.

@Klemmbaustein, for X11 application, the application specifies the minimum window side by WM_NORMAL_HINTS / WM_SIZE_HINTS in window property atom, would you please check if VSCode on X11 sets any? You can check via xprop command, thanks!


Vickel: Watch ariba[\W_]*+safety(?!.com)

Vickel requests the watch of the watch_keyword ariba[\W_]*+safety(?!\.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


Added the time string to the footer.

Added the time string to the footer

It is responsive across all devices.
It updates every 1.5 seconds .
Also displays AM & PM attiributes.

Thanks
Best Regards
Kapil

@Sayak-Bhunia issue number?

@Sayak-Bhunia issue number?

#22


Documentation tweak to Blocks in JavaScript Comparison

http://facebook.github.io/reason/javaScriptCompared.html#reason-and-javascript-blocks
Expected
IIFEs seem more conventional (hence the do proposal).
let res = () => {
  const x = 23;
  const y = 34;
  res = x + y;
};

Actual:
let res = undefined;
{
  const x = 23;
  const y = 34;
  res = x + y;
};

On second thought maybe the intent is to convey there's no stack operation LGTM.


Control of subscribe list | persist redis database

If i reset my whole redis database (and clear all) my old clients such as GCM will be can get new list?
Why should i care about take store strict data on redis server ? backup etc ?
Or no how can i check with client is my subscribed for X for example or no...?

So there's several questions here and please forgive me if I didn't understand something.
As far as your first question, I need more clarification.  You can do a snapshot of it with the BGSAVE command. Or are you trying to get it in a more human-readable form? This could just be accomplished with a script to fetch all the keys and stuff from Redis.
I also don't understand your question about "strict data." As far as backups, you can take snapshots of Redis and back them up. In fact, this is how persistent Redis works. This also means that everything you have must fit in RAM.
As far as the third question, we've developed an API to query which services a subscriber is subscribed to. We are working on pushing it upstream and you should see it soon.

Closing due to inactivity.
The /subscriptions endpoint has been created. (for the third question)


[Enhancement] limit messages returned from show restore and show backup returns a lot  messages in RestoreObjs

Search before asking

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

Description
No response
Solution
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

pick


Waypoint support global proxy image value

Please provide a description of this PR:

@hanxiaop: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test unit-tests

gencheck_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test unit-tests

gencheck_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test gencheck

unit-tests-arm64_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
7f9a60b5325368b17177e817cdb12d56f8ee29c0
link
true
/test unit-tests

unit-tests-arm64_istio
992d4b3f121a147467c8def62bd2cb75af1dcfd8
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
992d4b3f121a147467c8def62bd2cb75af1dcfd8
link
true
/test unit-tests-arm64

unit-tests_istio
992d4b3f121a147467c8def62bd2cb75af1dcfd8
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
992d4b3f121a147467c8def62bd2cb75af1dcfd8
link
true
/test unit-tests

unit-tests-arm64_istio
6e7c79cef356b0ccfbe3e7982154afd6e90d4b7e
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
6e7c79cef356b0ccfbe3e7982154afd6e90d4b7e
link
true
/test unit-tests-arm64

unit-tests_istio
6e7c79cef356b0ccfbe3e7982154afd6e90d4b7e
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Doesn't it already get the proxy image considering global values within go code in
	input := derivedInput{
		TemplateInput: mi,
		ProxyImage: inject.ProxyImage(
			cfg.Values.Struct(),
			proxyConfig.GetImage(),
			mi.Annotations,
		),

I'll check the logic. When I set hub, tag and values.global.proxy.image, the rendered waypoint image becomes hub/values.global.proxy.image/:tag, which is invalid image.

@hanxiaop: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
6e7c79cef356b0ccfbe3e7982154afd6e90d4b7e
link
true
/test unit-tests

gencheck_istio
82935fd2a464d290d32e580eb05d1b521a9fcc56
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu The issue I've mentioned above is caused by the code you provided, here we have:
https://github.com/istio/istio/blob/4029ebc0f0c0dbe25819498b3a501a05cdff2b5f/pkg/kube/inject/inject.go#L335-L337
which leads to the wrong ProxyImage value. The revised template in the PR fixes the issue if the global image value already have a slash.


Cannot build .net 4.6 solution

message: "D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(983,5): warning MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.6" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.

Relates to this forum thread.

Set an appSetting for your app MSBUILD_PATH = D:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe
#1624 @ahmelsayed

This should work now without requiring any app settings.

Nice

I've removed the appsettings but somehow the deploy scripts are cached. Is there a way to delete the current script and let it be regenerated? In the SCM portal there is only a way to download the script.

The files are cached in D:\home\site\deployments\tools, you can delete the files there from DebugConsole in the scm portal.

@ahmelsayed i've done that but script was still generated with
IF NOT DEFINED MSBUILD_PATH (
      SET MSBUILD_PATH=%WINDIR%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
)

@ahmelsayed i've tried again now with a new website from https://github.com/regisbsb/Dev14_Net46_Mvc5
but same result, @davidebbo said this site was fine but I can see that in the last tag it's still 4.0 not 14 the msbuild.
https://github.com/projectkudu/kudu/blob/S44/Kudu.Core/Infrastructure/PathUtility.cs vs
https://github.com/projectkudu/kudu/blob/master/Kudu.Core/Infrastructure/PathUtility.cs

https://github.com/projectkudu/kudu/issues/1659
still not deployed then..

I guess initially I thought that just having the new MSBuild on the box, but using the one in the framework folder would be enough. Apparently that's not correct so David made 1b85989027de7cb7f6789ddbe54d1ed5d6990c6d yesterday, which should fix this, but we are running into other issues with this change, so i'll need more time to sort that out. In the mean time setting MSBUILD_PATH should be a workaround

This should now work by default without setting MSBUILD_PATH.

I can confirm it works now without the MSBUILD_PATH. Thank you guys so much.


Discussion: do we want to continue using Jekyll?

Some of this was discussed previously on this PR.
As we go through the process of redesigning our site, it seems like another good opportunity to re-evaluate whether we want to:

Stick with Jekyll
Add a build step for the demo

Pros to switching to a JS-based site generator:

It would allow us to dog food ESLint in a more modern web application
It could open the door to more contributions from the community since the build tool would be in a language our users are a familiar with
We get to start using npm and its ecosystem for package management, making it easier to update/change packages and improve things in the future (i.e. things like switching out the code editor package, rewriting in another framework, etc. all become much easier to implement)
Increased performance for interactive elements (the demo, for instance, has a pretty long period of time to interaction)

Cons:

We would be adding the complexity of a build step (GitHub pages handles this for us now, since we're using Jekyll)
There will be time/effort needed up front to convert the existing site over to another site generator

Even if we do decide to stick with Jekyll, I would still be a proponent of bundling/building the JS we have, for the reasons listed above.
Note that both Babel and Vue.js have build steps, and it seems to be working for them! Vue.js's deployment strategy sounds pretty appealing to me:

The site is automatically deployed when commits land in master, via Netlify.

If we had a system like this in place, it seems like we wouldn't ever have to worry about running the build locally or for it getting out of sync (which I know were concerns before).
For reference, Babel and Prettier use Docusaurus, and Vue.js uses Hexo.
One very interesting benefit to Docusaurus is that it has the ability to create versioned docs out of the box.
I would be willing to work (even if it's just exploratory) on this!

For my personal opinion, I prefer VuePress, but I'm not opposed to using other CMS.

I don't have any strong feelings about our site generator. I'm fine with switching to another generator/adding a build step if it makes things easier.

I absolutely hate Jekyll - because Ruby on Windows is just a nightmare. But at the same time, I just don't see the point in adding complicity for what I perceive - minimal gains.

I'm still a big fan of Jekyll.  My site is running on Jekyll + Netlify and I
kind of love it. :)
For the demo, in particular, I think it might be worth splitting that out
into its own app with its own build system (and host at demo.eslint.org).
We definitely need to figure out how to deal with versioning the docs,
though. My biggest concern about switching to anything is that I wouldn't
want the documentation site to be dependent on people knowing React, Vue,
or any other client-side framework. I'm afraid that would make it harder
for more casual developers (and designers) to contribute meaningfully.
On Tue, Feb 5, 2019 at 5:29 AM Brandon Mills<EMAIL_ADDRESS>wrote:

I’ll admit to having been occasionally reluctant to work on the site
because I’d first have to get Jekyll working locally. I don’t see that by
itself as sufficient reason to switch, but it certainly makes the idea more
appealing. I didn’t know that Docusaurus gives versioned docs for free.
We’ve talked about ways to accomplish that before, and I’ve seen questions
e.g. on Stack Overflow where someone was trying to use a feature that was
in the docs but not their version. That could be a big win.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/eslint/eslint.github.io/issues/536#issuecomment-460637813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACWkp6OTCz2_-p1Sw5edS-xTqZUjMHrks5vKYcxgaJpZM4ah9X6
.

--

Nicholas C. Zakas
@slicknet
Author, Principles of Object-Oriented JavaScript http://amzn.to/29Pmfrm
Author, Understanding ECMAScript 6 http://amzn.to/29K1mIy

@mysticatea has his own demo site.

@g-plane Thank you for the mention.
I don't like Jekyll because that experience on Windows is terrible. I'm happy if we decide to use a JS-based site generator.
I have some plugins which are hosted with a JS-based site generator, VuePress.

https://vuejs.github.io/eslint-plugin-vue/
https://mysticatea.github.io/eslint-plugin-eslint-comments/
https://mysticatea.github.io/eslint-plugin-es/

Those sites have interactive examples to know how the rule reports code. For example https://vuejs.github.io/eslint-plugin-vue/rules/no-dupe-keys.html
The experience with VuePress is nice to me.
Basically, we don't need additional knowledge about Vue.js. We can write sites with Markdown files. Additionally, we can use Vue.js components to enhance Markdown files. This is additive.
As a result, we can write the interactive example very easily; only wrapping a code block by <eslint-code-block> tag in Markdown. <eslint-code-block> tag becomes an intaractive editor because it's a registered Vue.js component. For example:

<eslint-code-block :rules="{'vue/no-dupe-keys': ['error']}">

```vue
<!-- write example code here -->
\```

</eslint-code-block>

https://raw.githubusercontent.com/vuejs/eslint-plugin-vue/master/docs/rules/no-dupe-keys.md

And I have some online demo site.

Vue.js plugin's ... https://mysticatea.github.io/vue-eslint-demo/
TypeScript plugin's (WIP) ... https://mysticatea.github.io/typescript-eslint-demo/

Also, I have been maintaining some packages to help to build such documentation and online demo.

eslint4b ... An ESLint build that works in browsers
vue-eslint-editor ... An interactive editor that runs ESLint in VSCode editor

All of above documentations and online demos are built with eslint4b and vue-eslint-editor.

Very interesting, thanks for explaining. Given that Vue components are
additive and not required, then I'm not opposed to investigating Vuepress.
On Tue, Feb 5, 2019 at 9:02 PM Toru Nagashima<EMAIL_ADDRESS>wrote:

@g-plane https://github.com/g-plane Thank you for the mention.
I don't like Jekyll because that experience on Windows is terrible. I'm
happy if we decide to use a JS-based site generator.
I have some plugins which are hosted with a JS-based site generator,
VuePress https://vuepress.vuejs.org/.

https://vuejs.github.io/eslint-plugin-vue/
https://mysticatea.github.io/eslint-plugin-eslint-comments/
https://mysticatea.github.io/eslint-plugin-es/

Those sites have interactive examples to know how the rule reports code.
For example
https://vuejs.github.io/eslint-plugin-vue/rules/no-dupe-keys.html
The experience with VuePress https://vuepress.vuejs.org/ is nice to me.
Basically, we don't need additional knowledge about Vue.js. We can write
sites with Markdown files. Additionally, we can use Vue.js components to
enhance Markdown files. This is additive.
As a result, we can write the interactive example very easily; only
wrapping a code block by  tag in Markdown.
 tag becomes an intaractive editor because it's a
registered Vue.js component. For example:

\```

</eslint-code-block>

https://raw.githubusercontent.com/vuejs/eslint-plugin-vue/master/docs/rules/no-dupe-keys.md

And I have some online demo site.

   - Vue.js plugin's ... https://mysticatea.github.io/vue-eslint-demo/
   - TypeScript plugin's (WIP) ...
   https://mysticatea.github.io/typescript-eslint-demo/

Also, I have been maintaining some packages to help to build such
documentation and online demo.

   - eslint4b <https://www.npmjs.com/package/eslint4b> ... An ESLint
   build that works in browsers
   - vue-eslint-editor <https://www.npmjs.com/package/vue-eslint-editor>
   ... An interactive editor that runs ESLint in VSCode editor

All of above documentations and online demos are built with eslint4b
<https://www.npmjs.com/package/eslint4b> and vue-eslint-editor
<https://www.npmjs.com/package/vue-eslint-editor>.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/eslint/eslint.github.io/issues/536#issuecomment-460902003>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACWkpqagRwLE7FVSHVDIEfKmk2Ni2CPks5vKmHqgaJpZM4ah9X6>
.

--

Nicholas C. Zakas
@slicknet
Author, Principles of Object-Oriented JavaScript http://amzn.to/29Pmfrm
Author, Understanding ECMAScript 6 http://amzn.to/29K1mIy

For what it's worth, other popular static site generators like Gatsby and Docusaurus also allow you to create pages using Markdown as well.
@nzakas Would it possible to share how you've made working with Jekyll fit your workflow better?

Sure! I think for me the big thing was just installed Jekyll with bundler
to install and run it. We already point to the docs on how to do that in
the README:
https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/
I also found this helpful:
https://cloudcannon.com/tips/2017/12/08/speed-up-your-jekyll-builds/
Then I made a fast dev build that omitted everything I didn't usually need
during development.
I'm not sure what other problems people on Windows are referring to, but
let me know.
On Wed, Feb 6, 2019 at 1:45 PM Kai Cataldo<EMAIL_ADDRESS>wrote:

For what it's worth, other popular static site generators like Gatsby
https://www.gatsbyjs.org/docs/adding-markdown-pages/ and Docusaurus
https://docusaurus.io/docs/en/doc-markdown also allow you to create
pages using Markdown as well.
@nzakas https://github.com/nzakas Would it possible to share how you've
made working with Jekyll fit your workflow better?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eslint/eslint.github.io/issues/536#issuecomment-461199984,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACWku9OYicyP7TruFsPxNTzbjBtraa4ks5vK0zpgaJpZM4ah9X6
.

--

Nicholas C. Zakas
@slicknet
Author, Principles of Object-Oriented JavaScript http://amzn.to/29Pmfrm
Author, Understanding ECMAScript 6 http://amzn.to/29K1mIy

What's the progress?

I don't think we've assigned this as an action item to anyone at this
point. Does anyone want to volunteer to look at Vuepress and provide
feedback?
One thing I noticed when I checked it out is that it doesn't appear to have
blog functionality built-in. We rely on the ESLint blog a lot, so that's
important for us to consider. We could always run Jekyll just for the blog
and Vuepress for everything, but it would be nice to know if I missed
something here.
On Sat, Mar 2, 2019 at 8:07 PM Pig Fang<EMAIL_ADDRESS>wrote:

What's the progress?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eslint/eslint.github.io/issues/536#issuecomment-468986276,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACWkibFp_c8J-MVjXwVl7FwJyu9qnWiks5vS0qXgaJpZM4ah9X6
.

--

Nicholas C. Zakas
@slicknet
Author, Principles of Object-Oriented JavaScript http://amzn.to/29Pmfrm
Author, Understanding ECMAScript 6 http://amzn.to/29K1mIy

Currently, VuePress doesn't support blog officially, but there are implementations by community. And blog will be supported officially in their next major version.

We could always run Jekyll just for the blog and Vuepress for everything.

@nzakas It's a good idea!

I might have some time to look at this in the next few weeks. It sounds like there are a few of us interested in VuePress. I still think Docusaurus seems like a better option, for the following reasons:
Docusaurus builds the site from markdown files (with the ability to custom pages as React components for things like the demo), has the ability to create blogs, and supports Alogolia search out of the box. This Babel issue seems to indicate that migrating from Jekyll to Docusaurus is relatively painless.
It also looks like VuePress is currently in alpha and doesn't guarantee stability at the moment, and I'd also lean towards using something that is tried and true like Gatsby in the event we decide not to use Docusaurus.
As far as having a build/publish step goes, there are some solutions listed in the official docs. Also of note: if Netlify seems like a better option than setting up our own CI build step, they do offer a free plan for teams maintaining open source projects.
Looking forward to hearing what you all think!

I seem to have forgotten to list what I think is the most compelling reason to use Docusaurus - versioned docs! If we decided to go that route, I think we should start by creating versioned docs for releases going forward (we would have to decide if we want to run it on all releases, or limit it to major and minor releases) and leave the existing old major versioned docs in a more visible place. We could look into trying to somehow extracting old versions, but I'm not sure it's worth the effort at this point.

I seem to have forgotten to list what I think is the most compelling reason to use Docusaurus - versioned docs!

Yes!
Does Docusaurus also let us annotate when a particular feature (e.g., a rule option) is added somehow?

Does Docusaurus also let us annotate when a particular feature (e.g., a rule option) is added somehow?

It doesn't look like Docusaurus has that functionality built in. It looks like running the docusaurus-version command saves the current site into a versioned doc directory (see the Babel website's repo for an example).

Prettier’s website uses Docusaurus’s versioned docs: https://prettier.io/versions.html. What would likely happen is that the latest (“master”) version of the docs would be pulled from the ESLint repo at build time, but the old versions would live here in a versioned_docs directory.

I spent some time with Docusaurus and wanted to report my findings.
Docusaurus is a lot more opinionated than I had originally thought. I don't believe the limitations I've found need to be blockers, but they do make it more difficult to cut over the site as it is currently designed.

I didn't realize that Docusaurus uses React only as a rendering engine at build time, meaning that it can only generate static markup. It's possible to add interaction, but it's done by including a script tag in a page template (see https://github.com/babel/website/blob/master/website/pages/en/repl.js for an example).

Docusaurus handles the general layout and styles. It's possible to add your own custom CSS, but much of the layout and markup is generated by Docusaurus, limited the extent to which you can customize things.

Dropdowns are not supported in the navigation header.

The first two of these issues seem to be items the maintainers have on their roadmap, but I'm not sure of the timeline on that.
These limitations are an issue with the site as it is currently designed. That being said, I don't think they would be an issue for the newly designed site, as it happens to match the layout generated by Docusaurus.

In pursuing this, I would also like to revisit the idea of adding a build step to our site. We know it would be a prerequisite for any of the options we've discussed above, and separating that task out into its own separate task feels like a much easier way to do things. Besides unblocking us from using a different static site framework, I believe we would get the following immediate benefits:

When I first proposed this, we weren't pulling data from Open Collective's API. The build step could now automate running less, bundling the demo, and running the script we use to pull data from Open Collective.
We would get to dogfood ESLint in a more modern web application.
I believe this would make it more approachable and enjoyable for our community to contribute to the site (particularly the demo).

Here is how I propose we move to having a build step:

We could use the current repository, but GitHub pages has the unfortunate limitation of only allowing hosting from the master branch for a user or org site (one that ends in *.github.io). We could create a separate src branch, but that feels confusing and would require anyone working on the site to know that master is essentially a build artifact. If we were to create a new repository called eslint/website, we could treat the master branch as the source and publish to a second branch called gh-pages. This way, master is always the source of truth.
If we do create a new repository, we would have to update the release script to also copy documentation files into that repo in the interim.
We set up Travis (as described here) to run whenever a commit lands in master, running the build and publishing it to the gh-pages branch.
Update the build script to bundle the demo and the parser with Webpack, run less, and run the script that pulls from the Open Collective API.
Once we cut over completely to that repository for the website, we would have to update the release script once more to only generate docs in the new repository.

Now that the work for https://github.com/eslint/website/issues/576 is done, we are in a position to use any static site framework we'd like!
Have people's opinons changed? There have been mentions of Vuepress, Gatsby, and Docusaurus. I'm still of the mind that using Docusaurus is a win in the long run, since we get to take advantage of the community around that project and since the problem is trying to solve is open source documentation, but I'm definitely open to exploring other options.

Would love to continue moving this discussion forward.
What framework should we use?
I'm currently using Gatsby to build my personal website and no longer think it's a good idea for our use-case here. While I've really been enjoying using it, I think there's just too much overhead with having to understand React, how to correctly write components to work with server-side rendering,  GraphQL, and the framework itself. It's a really powerful, flexible tool that gives you a lot of options, but I don't think it meets our desire to have a website that is easy to contribute to. Docusaurus feels like a better option in this regard, but it also might be too rigid for our use case and would still have some of the same downsides Gatsby has regarding React and SSR.
I'm not sure how Vue-powered alternatives compare in this regard (maybe @mysticatea would have some insight), but @nzakas pointed me to Eleventy a while back, and it does seem like a framework with a much lower barrier to entry. It should also be fairly easy to convert, as it has a lot of flexibility in terms of what templating engines it allows.
Do we want to tie this to the site redesign?
I don't know if we have to tie this to the site redesign, particularly if we're cutting over to something like Eleventy where we might able reuse a lot of the existing codebase. If we were to cut over to something that would involve rewriting everything into Vue/React components, it might make more sense to do it all at once to minimize churn/throwaway work.
Thoughts?

I generally agree with your assessment.  It seems like Eleventy is the simplest and most straightforward port of what we have now.
I don’t think we should tie a platform change to a redesign. I’d still like to investigate hiring a designer to do a proper redesign, and I don’t see a reason to create a dependency on that for moving off of Jekyll.

I know we haven't necessarily decided to go this route, but I opened a PR cutting over the site to Eleventy to see how easy it would be here. It was pretty straightforward!
After going through this process, I like Eleventy. I think it has a low barrier to entry and seems to be quite flexible (down to being able to switch out templating engines). I kept things mostly the same for this PR for ease of conversion, but we don't have to stick with a lot of the constraints that Jekyll has if we decide to go this route.

The site has been migrated from Jekyll to Eleventy, so closing this issue.


node crash in TestFailedNodes

https://github.com/spacemeshos/go-spacemesh/runs/8220884884?check_suite_focus=true
i don't understand yet what has caused a crash {namespace="test-flpe", pod="smesher-16-0"}

same crash {namespace="test-opxs", pod="smesher-7-0"}

this was infra problem


Add BYTE_STREAM_SPLIT encoding

Apache Parquet does not have any encodings suitable for FP data and the available text compressors (zstd, gzip, etc) do not handle FP data very well.
It is possible to apply a simple data transformation named "stream splitting". Such could be "byte stream splitting" which creates K streams of length N where K is the number of bytes in the data type (4 for floats, 8 for doubles) and N is the number of elements in the sequence.
The transformed data compresses significantly better on average than the original data and for some cases there is a performance improvement in compression and decompression speed.
You can read a more detailed report here:
https://drive.google.com/file/d/1wfLQyO2G5nofYFkS7pVbUW0-oJkQqBvv/view
Reporter: Martin Radev / @martinradev
Assignee: Martin Radev / @martinradev
PRs and other links:

GitHub Pull Request #144
GitHub Pull Request #705
VOTE thread

Note: This issue was originally created as PARQUET-1622. Please see the migration documentation for further details.

Antoine Pitrou / @pitrou:
For posterity, here is the archive of the VOTE thread for this feature: https://lists.apache.org/thread/xs5qt2odm299pxgqb22mty2csc1so5yr

Martin Radev / @martinradev:
Thanks for the quick answer.
I do have a patch already available in my fork: https://github.com/martinradev/parquet-mr/commits/master
However, I have not previously committed to parquet-mr and I have not programmed in Java for some time now. Thus, I also do not know whether the quality of the patch is as high as it should be. It includes the implementation and various tests/

Gabor Szadovszky / @gszadovszky:
That's fine. I've just asked if you have a change to know if the parquet-format release is urgent. I'll look through your change offline however, the best way to do a full review is to comment on a pull request.
I'll initiate a parquet-format release after we released parquet-mr. (There is no real connection between the two but I would not like to distract the community's attention from the parquet-mr release...)

Martin Radev / @martinradev:
@gszadovszky How should we handle that the new encoding is part parquet-format 2.8.0 and parquet-mr has a dependency on 2.7.0.
Should I bump up the version of parquet-format in parquet-mr?

Gang Wu / @wgtmac:
The issue raised by @mapleFU above may also exist in the parquet-mr.
cc [~xinlishang] @ggershinsky

Xuwei Fu / @mapleFU:
@gszadovszky @martinradev
Hi all, I meet a problem here: https://github.com/apache/arrow/issues/15173
Would you mind take a look? Seems we don't have "non-null value count" here.

Gabor Szadovszky / @gszadovszky:
parquet-format 2.8.0 is not released yet. To start a PR to parquet-mr master you will need the parquet-format 2.8.0 released and the parquet-mr to be depending on it.
For longer feature developments we use feature branches. On a feature branch, you may use a workaround that installs the current parquet-format master as a snapshot and depend on it. But if your change would not require several loops of development I don't think it worth the additional efforts.
Usually, parquet-format releases can be done in a week or two. Are you planning to initiate a PR to parquet-mr soon?


Update some tabs and links in billing.md

Description of the change: Updated some URLs and tab names to reflect the changes made to the Account Details section of the app
Reason for the change: Some information was outdated following the recent launch
Link to original source: https://sendgrid.com/docs/ui/account-and-settings/billing/

Closes #

Hello @katieporter,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Multiple tooltips appear for each dataset in timeseries when too much points are displayed

Probably linked to https://github.com/chartjs/Chart.js/pull/5578.
Another option would be to use decimation, eg https://github.com/AlbinoDrought/chartjs-plugin-downsample, or to reduce the time range.

As a workaround we can now configure the time span so that when a lot of data has to be displayed the user can reduce it and mitigate this effect.


Doesn't work on Chrome stable v69

Tested on latest Chrome stable v69.0.3497.81.
Doesn't work even after fallowing https://github.com/beaufortfrancois/picture-in-picture-chrome-extension/issues/7 recommendation and enabled flags
#enable-experimental-web-platform-features
#enable-surfaces-for-videos
#enable-picture-in-picture

What is the error you're seeing in the JavaScript console?

@beaufortfrancois, after multiple retries and browser restarts, in works now. The only required flag in Chrome v69 is #enable-surfaces-for-videos (leaving all else on default), without it doesn't work (extension is missing anything like tooltip saying the reason why not working).
The confusing part is when #enable-picture-in-picture enabled, the extension icon hover will show "Picture-in-Picture NOT supported". Perhaps needed another tooltip since might be confused with Picture-in-Picture feature.

Does not work even after restarting browser multiple times and enabling #enable-surfaces-for-videos flag on stable v69.0.3497.81

met the same same situation, and enabled all the 3 features, reload browser and doesn't work .
Then after a while, it just works somehow.
@beaufortfrancois where to check the error log by the way.

Can you provide steps to reproduce?
Which platform are you on?
Which URL are you trying?

I tried youtube.com, Chrome build on latest Win10 64-bit Pro.

It used to work only in youtube.com, no other website, neither in embedded YouTube.

Hi everyone! I have the same issue on youtube.com, extention doesn't work.
macOS 10.13.6
Chrome Version 69.0.3497.81 (Official Build) (64-bit)
Extension v.1.1 from Chrome Store
Flags enabled:
#enable-experimental-web-platform-features
#enable-surfaces-for-videos
#enable-picture-in-picture

After your reply, I was trying to check the extension console and after then opened extension page: chrome://extensions/?id=hkgfoiooedgoejojocmhlaklaeopbecg I see the inactive background page:

After click by this link and will open console window  and extension will work fine.
Thanks for the idea!
FYI @mounirlamouri @peria


arch & runtime flavor notice on Installing ASP.NET 5 On Windows

In this page Installing ASP.NET 5 On Windows, it will be better to add some notcie about dnvm upgrade will install dnx-clr-win-x<IP_ADDRESS>-beta7 only.  If you need install all the other 3 runtimes, you'll have to install it manually.  That is

dnvm install 1.0.0-beta7 -arch x86 -r coreclr
dnvm install 1.0.0-beta7 -arch x64 -r coreclr
dnvm install 1.0.0-beta7 -arch x86
dnvm install 1.0.0-beta7 -arch x64

@TomArcher can you try to reproduce on a clean VM. I just test
dnvm list
lists all 4 versions as installed.

If you use the installer you will get all four runtimes. It's only when you use dnvm that you just get the default DNX.


702 syntax warnings

Extended program check issues:
functin module SU20_MAINTAIN_SNGL could not be found - method zif_abapgit_object~exists( ) of class lcl_object_auth
exception ICM_NOT_AUTHORIZED is not defined in the interface of the function module ICM_GET_INFO2 - method is_local_system of class lcl_http.
Exception CX_CLIF_SCAN_ERROR is neither caught nor is it declared in the RAISING clause of INIT_SCANNER (class lcl_oo_class_new)

merged, closing


[BACKEND] Fix bug in ForOpDeadArgElimination.

Suppose we have a loop which yields an operand which lives outside the
loop, i.e. is loop-invariant.  Moreover, suppose the same operand in
iter_args is never used.
%init = ...
%x = ...
%y = for iter_args(%unused = %init) {
  yield %x
}
return %y

Previously, we would declare that operand 0 of the yield is "dead" and
replace it with yield %init.  This is obviously not correct.
The way this happened was:

ForOpDeadArgElimination iterates over the forOp's results, in this
case just [%y].
We notice that %y is used, so it's not dead.  We call markLive(%x),
where %x is the yielded value that corresponds to %y.
%x is not defined in the loop body, so markLive skips it.
Therefore at the end of the function, operand 0 of the yield is
considered dead.  We change it to yield %init, so it can be removed
from the loop entirely in a later pass.

In this patch, we add a special case that says that a yield which
returns a value from outside the loop isn't dead.
Fixes https://github.com/openai/triton/issues/2672

Thank you for the review!


Striked out text misaligned

Slide 1.5 (33)
iPhone 6s 11.1.2
https://reddit.com/r/JailbreakSwap/comments/8xo3fy/usmd_h_iphone_6s_64gb_gold_on_ios_91_tmobile_only/

That is all in UIKit, don't know if it's possible to debug or fix this

Fixed with the new text library!


v0.1 refactor

I propose we create a 0.0 release of GPfit and then perform a pretty wholesale refactor of the code. Here is the list of changes I would like to make:

[x] General code tightening (more concise code, less unnecessary whitespace)
[x] Py3 only (e.g. delete __future__ imports)
[x] Delete legacy Matlab code
[x] Better variable naming

[x] Appropriate use of case (rename upper case and mixed case vars unless global)

[x] Better function naming

[x] Rename get_params
[x] Rename ba_init

[x] Better class naming

[x] Rename FitCS

[x] Code restructuring

[x] MA, SMA, ISMA should all be in one module
[x] Reduce confusing overlap of naming of fit.py and fit_constraintset.py
[x] Separate FitCS and XfoilFit (move to xfoil.py)
[x] Group lse_scaled and lse_implicit into one module
~Fit should be a class not a function~
~Eliminate plot_fit.py and print_fit.py (they should be class methods)~

[x] Remove examples/tests redundancy

[x] Better naming of the examples too

#98
~Write the Getting Started docs page~

There is a little overlap with #73 but would be good to include those items too!
@bqpd @whoburg any objections or things you want to add?

Those look good to me! I might just add "write the Getting Started docs page"?

Good call. The docs need a lot of love but that seems like an appropriate piece to include in this effort.

The cleaner the API the shorter that page will be, too!

@pgkirsch this sounds fantastic! What are your thoughts on using a code formatter like black to accomplish some of the earlier bullets?

Thanks @whoburg! black seems cool, I'll give it a go.

@whoburg I ran black on the code. It certainly brings nice uniformity and saves time spent mindlessly formatting code.
There are a few things I don't love though.
For instance, I'm not a fan of its policy on whitespace around *, /, ** operators. I believe PEP allows a = x*y + z**2 and I've always thought that looks nicer and more concise than a = x * y + z ** 2.
It also does makes some weird changes like:
-Vdd = random_sample(1000,) + 1
# ...
+Vdd = (
+    random_sample(
+        1000,
+    )
+    + 1
+)

Sure, that original line probably isn't great style and the black change can be fixed by assigning x = random_sample and doing Vdd = x + 1 but it still feels odd to enforce a change that seems to make the code less readable.
Lastly, rather than making the code more concise, it increased the total lines of code in the main directory very slightly from 906 to 941 (despite allowing lines up 88 chars long).
Anyway don't mean to complain too much, it's clearly a powerful tool and I'm on board with continuing to use it. I just wanted to flag a few minor things that gave me pause.
(cc @bqpd)

Yeah the best use I've seen of black is to pretty-print long data entries for adding quick tests: just copy-paste in one line, then run black to line-break etc.

(also it would've been super useful back when we were first linting everything!)

Good discussion @pgkirsch and @bqpd, I'm all for whatever is most pleasing and efficient to use, whether that includes a code formatter or not. Completely up to you.

Good discussion @pgkirsch and @bqpd, I'm all for whatever is most pleasing and efficient to use, whether that includes a code formatter or not. Completely up to you, no strong feelings here.

Just coming back here to say that I've fully come around on black and would support using it not only in gpfit but also in gpkit, maybe once the great pylint refactor of 2024 is merged 👀


card h-100 on Safari strange behavior

Hello,
When creating a card in bootstrap 4 and adding this to the card class "h-100", works well on chrome but creates a massive white gap at the bottom of the card in both safari and Internet explorer(both latest versions as of today).
All you have to do to test this bug is create a card some text in it and the h-100 to the class "card"
Any tips to go around this please?
Thank you,

which version is this on?

is this present in 4.5?

Let me check now, I will come back to you asap.

necesita compartir un ejemplo de los problemas o agregar el empinado para reproducir este error ...

yes, could you make a codepen with the code that causes it?

I am making one now, please give me some time because my page is really big and I need to filter out all the vue.js and PHP.

I am making one now, please give me some time because my page is really big and I need to filter out all the vue.js and PHP.

only need
create a view instance and emty control
put the html code related o recreate
card h-100 and send all capture or code posible...

Bug reports must include a live demo of the issue. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and Operating System details.
This is an automated reply


Feature/#40

Current coverage is 90.3% (diff: 25.0%)

Merging #42 into master will decrease coverage by 0.5%

@@             master        #42   diff @@
==========================================
  Files            62         63     +1
  Lines           714        713     -1
  Methods           0          0
  Messages          0          0
  Branches         60         59     -1
==========================================
- Hits            649        644     -5
- Misses           40         45     +5
+ Partials         25         24     -1

Powered by Codecov. Last update fc6f3a7...839b4da


Update zoc to 7.14.5

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Thank you for the contribution. It was merged directly as 218515d94824b433b83e55f41e380bd84cf7b60b. Your contribution is still credited to you.


Hosting

Lets also host it on Github Pages. It'll be easier to make changes after hosting.
Just tell me how to and I'll do it.

is this issue completed?

Yeah! Thanks for reminding :grin:.


Consider using an established code style convention

https://github.com/airbnb/javascript; or
https://github.com/gajus/eslint-config-canonical

As it is, it is hard to contribute to the code base, because it feels completely alien to JavaScript ecosystem.

No, your coding style, on the contrary, feel completely alien to me.


Added functionality to operate on persistent (text file) data with harness.py file

Wrote code (harness.py) to read data from text file (customers.json) which can be used as interim persistent storage.
The following functions are now supported:
a) LIST_ALL
b) RETRIEVE
c) UPDATE
d) ADD
e) DELETE
*Need to test each of these functionalities by comparing with actual data in "customers.json" file

I could not test the functionalities as my VM is not working properly. Kindly test ASAP.

I will test them

Not using it anymore


Schlegel2016

FBrf0234450
Some extra detail added for larval Hugin neurons, including synapsing broad categories (PI IPCs, selves, interneurons).
Specific neurons all seem to be in ontology
Now also added larval antennal nerve and abdominal sensory neurons.
Added input from interneurons and sensory neurons (generic) in description/comments, but specifics not given in paper.
Subclasses not made for neurons identified by numbers (skids?)

Closing as all useful data in ontology now


No mention of Azure Logic Apps

[Enter feedback here]
I didn't saw any mention of Azure Logic Apps a an option either to migrate o implement a new service. it is consider inside one of the other options?

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

ID: 510808e8-db5d-6b07-9a04-6edb743a2dfc
Version Independent ID: 20d098aa-ef31-cb26-d677-765cfc9a7164
Content: Choosing an Azure compute service - Azure Architecture Center
Content Source: docs/guide/technology-choices/compute-decision-tree.md
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#330952

Closing this issue as a note under the "Understanding the hosting model" addresses this.


How to get the CLIC datasets?

Great job on your work! I was wondering if you could help me obtain the 2022 CLIC datasets mentioned in your paper, as I couldn't locate them on the homepage (http://compression.cc/). Thank you in advance for your assistance.

You can get the dataset from http://compression.cc/tasks/.
See Perceptual metrics part.

您的邮件已收到哦我会及时处理哒~

You can get the dataset from http://compression.cc/tasks/. See Perceptual metrics part.

Thank you for your response. However, I noticed that the dataset you provided (https://storage.googleapis.com/clic2021_public/perceptual/clic_2021_perceptual_valid.zip) is labeled as the validation set and consists of 2733 images. I would like to confirm whether this is the dataset used in your paper.

Yes


the cook from tr 5, if you shoot him, flies down and hangs in a standing animation

He not work

well this is because he was only killed in a cutscene, not like a normal enemy so I think this is OG behaviour. Closing