Feat(web-react): Introduce BreadcrumbsItem component

and refactor Breadcrumbs to use it

refs #DS-835

Description
Refactoring of Breadcrumbs to simplify the usage of the component by adding the new BreadcrumbsItem subcomponent to render items more easily.
Additional context
There is a concept of the two slots for icons - iconStart and iconEnd.
Also, the arrows were switched from the original implementation. Now the default arrow is on the end for better manipulation in coditions.
Issue reference
https://jira.lmc.cz/browse/DS-835

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Follow the PR Title/Commit Message Convention.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

coverage: 96.46%. remained the same when pulling c5061acd58de08d0a9609969574b02d3ff52660f on feat/DS-835-breadcrumbs-item into 4e1b5ebd2a3989261d4b1f04735a5025d6ee696d on main.

@crishpeen So, to finish this, we must discuss the usage of the slots for icons; 💁♂ @adamkudrna and @pavelklibani

@crishpeen Thank you very much for your suggestions and also for implementing them on this issue. However, I have discovered some inconsistencies between custom breadcrumbs demos. So, please, do a final check for me, that everything is correct. Many thanks. :-)

how about a storybook demo?

You are right. Story added.


Label zoom rooms on Thurs+Friday schedule

Something we should a little more clear are the zoom rooms. Instead of using "Zoom" or "Zoom (as above), could we use Zoom room number, i.e. "Zoom 1" ? They are listed in the minute by minute here: https://docs.google.com/spreadsheets/d/1BRCCVjyUiWGI2s8os8-F5gY4mB9U6f70j9XCs_yiX2w/edit#gid=452609008

It looks like Marzyeh already did this for Thursday yesterday (https://github.com/acm-chil/acm-chil-website/commit/305ff814493a6808749422dbf35386c1dcea4b60), but the numbering doesn't match what's in the spreadsheet (the tutorials are 1A, 1B, 1C instead of 1, 2, 3).
I think this numbering system makes more sense so I will copy it for Friday (to address #74 also), but the spreadsheet should probably be updated. (I don't want to touch the spreadsheet in case I mess it up)


JAM Services for Ethereum Optimistic Rollups and Ethereum

JAM’s mission as a rollup host can be extended from validating Polkadot rollups to validating Ethereum optimistic rollups (ORUs) as well as Ethereum itself.
We outline a design for a JAM Service to validating ORUs + Ethereum using a similar approach to Polkadot rollups anticipated in the CoreChains service. The design involves verifying state witnesses against account balances, nonces, code, and storage, and then using this state to re-execute block transactions, all within the service's refine operation; then, these validated ETH L1+L2 blocks are stored on-chain in service's accumulate operation.
This JAM service is readily implementable with already available tools that fits seamlessly into JAM’s refine-accumulate service architecture:
(a) Geth’s Consensus API, which outputs state witnesses for Ethereum and its dominant ORU ecosystems (OP Stack and Arbitrum Nitro), and
(b) Rust-based EVM interpreter revm that should be compilable to PolkaVM with polkatool.
This allows Ethereum+ETH L2 ORU users to benefit from JAM’s high computational and storage throughput. The JAM service enables rollup operators to choose JAM Services over other rollup service providers or to enhance their use of Ethereum for improved Web3 user experience, ultimately to provide validity proofs faster.
Furthermore, Ethereum itself can be validated by the same JAM service, providing additional verification for ORU L2 commitments posted to Ethereum across all Ethereum forks.
This is an attempt to accommodate feedback from everyone on #127.

Is there a reason why there's an RFC to do exactly what Hyperbridge is being designed to do?
https://blog.polytope.technology/introducing-hyperbridge-interoperability-coprocessor#full-node-level-security

Afaik, there is still zero relationship with the JAM changes here, becuase the accumulate is exactly the parachain accumulate.
There maybe ORs whose blocks some somewhat unordered, which seemingly motivates this being a JAM service, not just a parachain.  It's odd if that's true, since ORs have a stagering intershard latency problem.  It anyways would not stop hyperbridge from waiting until the OR sequences, or maybe pre-processing with an artificial ordering, and reimposing the OR sequence later.

@rphmeier @burdges  The cost of this Succinct Labs SP1 solution actually finalize your ORU with ZK proofs" appears economically viable to me, with claims of $1K-3K/mo fixed proving costs and very reasonable costs per transaction.
If this rsp is production-level, we can certainly have JAM DA hold Succinct (and other prover networks) generate ZK finality proofs, verified in refine and stitched together in accumulate at ETH finalized checkpoints.  How would you see it differently?  Is it "vapourware" to you?

I've forgotten why they're reinventing snowfork there, maybe it gives lower latency than the delay method used by snowfork.  Anyways, I'd guess the ETH bridges wind up merged eventually after everyone agrees upon which tech to use, just because running them gets expensive, and treasury won't pay for two ETH bridges.
There is no independent reason for a DA layer here, because the only data in the ETH bridge is the validator keys.  ETH needs some trick like a SNARK or sampling to track the polkadot validators and prove thewir signatures.
All the OR blocks do end up in polkadot's availability, but that's because they're turnned into parachain blocks.

Closed to rework in a SP1 proof centric way.


Hover is annoying

Type: Bug
Whenever you write the 'query' word, the hover appears in the screen and it doesn't dissappear when you write a parameter as it happens for other words. It's quite annoying.
VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx   (8 x 2096)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
9.89GB (2.13GB free)

Process Argv
--crash-reporter-id 37fff3b1-4e5c-4041-84ea-d6c7555c502c

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

composer-php-vscode
DEV
1.31.12740

phptools-vscode
DEV
1.31.12740

profiler-php-vscode
DEV
1.31.12740

LiveServer
rit
5.7.9

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewvextcfv2:30681851
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
2i9eh265:30646982
6233i204:30672705
azdwalk:30687957
pythonms35:30686772

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.76.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I know i can deactivate it, but i guess that's not the behaviour it should have

See? The two hovers get over one another, that's why i'm saying this shouldn't be the behaviour

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Dots instancing compatible Graphics Tools shaders

Describe the problem
When using Entities Graphics, the Standard shader can't be used as it isn't dots instancing compatible.
Describe the solution you'd like
Make the shaders in graphics tools Dots instancing compatible.
<EMAIL_ADDRESS>Describe alternatives you've considered
Use a different shader.
Additional context

Hi @Merichbier ,  please open this issue in the Graphics Tools repository here:
https://github.com/microsoft/MixedReality-GraphicsTools-Unity/issues


Add the ability to specify the config file path via environment manager

This should make it possible to easily run hubibot inside of TrueNAS as an app via the "Launch Docker Image" flow which allows specifying environment variables and mount paths to datasets.
Note: I am not sure how to test this because when I run docker build I end up getting an error about permissions to /home/hubibot/.local due to the pip install command in the Dockerfile. I've never built a docker container so I'm likely running into some user error issues.

I had tried testing this change by building my own docker image but I ran into a permission issue. I've filed https://github.com/vdbg/hubibot/issues/51 with details about the problem.

code change looks good. Could you update README.md to document the env var support and some of its potential uses?

I put a quick update in the README.md. Once we get this into the latest docker image I'll verify that it works and take a screenshot of the configuration screen showing exactly what to set in TrueNAS.

all set, let me know if you want me to add anything else

looks good thx for making these changes


Storybook a11y tests with Storybook Test Runner

This PR adds testing using Storybook Test Runner and axe-playwright to the React component library. See Storybook's Accessibility tests page for background information.
This new test run requires a running Storybook instance. With Storybook running locally at localhost:6006, run npm run storybook-test to see its output.
Unlike in #368, I am unable to get the Select component to throw the error "ARIA hidden element must not be focusable or contain focusable elements." I'm unsure why this is so far. I've tried adding a manual delay to the postVisit step to see if it has something to do with the test runner hitting the page before the hidden element is rendered, and this didn't have any effect. More exploration required.
Two genuine errors are being surfaced by this test suite: The stories Button/Icon and Button/PlaceholderIconButton are both failing "Ensures buttons have discernible text". These will get addressed in a future PR.

For now, I'm not adding the test run to any GitHub Actions workflow since the tests are failing.

Two genuine errors are being surfaced by this test suite: The stories Button/Icon and Button/PlaceholderIconButton are both failing "Ensures buttons have discernible text". These will get addressed in a future PR.

This is because there's no aria-label or aria-labelledby prop, right? In the docs, we flag that if users are using icon-only buttons, they need to pass one of those labels to make them accessible. Is the fix simply to add placeholder aria-labels to those stories, or are you contemplating a change to the component itself to bake in that label in those use-cases?

Two genuine errors are being surfaced by this test suite: The stories Button/Icon and Button/PlaceholderIconButton are both failing "Ensures buttons have discernible text". These will get addressed in a future PR.

This is because there's no aria-label or aria-labelledby prop, right? In the docs, we flag that if users are using icon-only buttons, they need to pass one of those labels to make them accessible. Is the fix simply to add placeholder aria-labels to those stories, or are you contemplating a change to the component itself to bake in that label in those use-cases?

Right, there is no discernible text from the button contents, aria-label, aria-labelledby, or any field within the SVG that would suffice.
I think adding an aria-label prop to those stories is the simplest, with explanatory text in the docs.
I don't think we can do anything further to bake more logic into the component due to the nature of the problem. Check out the article Accessible Icon Buttons for background info. IMO, there's no perfect way to satisfy this rule in all cases using logic in the component, and we can't control what folks will be using in the children slot, so the best we can do is educate them.


Where can I get more details about the security features for Apollo?

Dear Apollo developers, I see Apollo is building new security features presented here, including intrusion detection, car firewall and secure OTA kits, but I do not find the implementation of these features except secure OTA in the latest version of Apollo's code base. Is there any plan to integrate the intrusion detection and firewall feature into the current Apollo code base? Or where can I find the relevant source code or documentations for these features? Thanks for your information!

@hongkedavid many of security features are not in the open source platform, but available in solutions that we built for our partners.

@jinghaomiao Got it. Thanks for your information!

@jinghaomiao I see. Thanks!


Will like to change the GUI

Functionality is working pretty well. I will make some adjustments to the ui

Hello @HanslettTheDev, are you going to proceed with ui changes or suggest any? Otherwise, I will close this issue.

YOU CAN CLOSE IT BUT I WILL STILL MAKE THE NEEDED CHANges
On Tue, May 17, 2022, 10:25 PM Ilias Charitos @.***>
wrote:

Hello @HanslettTheDev https://github.com/HanslettTheDev, are you going
to proceed with ui changes or suggest any? Otherwise, I will close this
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/ilias4780/fpl_statistics_ui_app/issues/7#issuecomment-1129331820,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APILY6QLEOGVZVRJ6D7N3CTVKQFEVANCNFSM5RXPJ5KQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok, thank you!

Hello mate,
No problem at all, feel free to meddle with it.
Kind regards,
Ilias
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Hanslett @.>
Sent: Saturday, March 26, 2022 6:40:56 PM
To: ilias4780/fpl_statistics_ui_app @.>
Cc: Subscribed @.***>
Subject: [ilias4780/fpl_statistics_ui_app] Will like to change the GUI (Issue #7)
Functionality is working pretty well. I will make some adjustments to the ui
—
Reply to this email directly, view it on GitHubhttps://github.com/ilias4780/fpl_statistics_ui_app/issues/7, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANDD6FAVLD3PLAF2BXMCCVDVB5K3RANCNFSM5RXPJ5KQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Problem about the number of files that have been downloaded

When I downloaded more than 1000 files, I found that the number of files became to 1000 / 1000
I changed the code in main.js :
	rpc.subscribe('tellStopped', [0, 10], function(data) { 		scope.$apply(function() { 			utils.mergeMap(data[0], scope.stopped, scope.getCtx); 		}); 	});
It became to 10/10
But the code is:
	rpc.subscribe('tellStopped', [0, 999999], function(data) { 		scope.$apply(function() { 			utils.mergeMap(data[0], scope.stopped, scope.getCtx); 		}); 	});
It's still 1000 / 1000
how can it show the correct files number

acitive:2, waiting:1800,stopped:200,  total:2002
acitive:2, waiting:1000,stopped:1000,  total:2002
acitive:2, waiting:800,stopped:1000,  total:1802
acitive:2, waiting:400,stopped:1000,  total:1402
acitive:2, waiting:0,stopped:1000,  total:1002
acitive:0, waiting:0,stopped:1000,  total:1000

I have modified the code in settings.js:
  "max-download-result": {     val: 999999,     desc: "Set maximum number of download result kept in memory. The download results are completed/error/removed downloads. The download results are stored in FIFO queue and it can store at most NUM download results. When queue is full and new download result is created, oldest download result is removed from the front of the queue and new one is pushed to the back. Setting big number in this option may result high memory consumption after thousands of downloads. Specifying 0 means no download result is kept. Default: 999999"   },
BUT it didn't work, so I thought I could change the code of aria2：

I add a new code into the aria2 start program：
 --max-download-result=999999
the max download result number exceeded 1000

Now can someone tell me if the code in settings.js is just illustrative?If so, I'm afraid I've taken the time to put useful Settings into the launcher I wrote myself


[Feature Request]: string validation with regex

It was requested a few times on reddit and also stays in my TODO/WORKLOG.
Syntax
#[nutype(
    validate(
        regex = "^\w+@\w(\.\w)+$"
    )
)]
pub struct Username(String);

Alternative syntax could be with // like in scripting languages:
regex = /^\w+@\w(\.\w)+$/

If you're reading this, please share your opinion.
Crates

regex
lazy-regex - seems to be based on top of regex. Can be very helpful, since the regex is check at compile time

Concerns
Will it play well with potential support of Arbitrary?
I think rand_regex can be helpful here.

Alternative syntax could be with // like in scripting languages:
If you're reading this, pleasure share your opinion.

As a user, I would prefer something more like the first option:
#[nutype(
    validate(
        regex = r#"^\w+@\w(\.\w)+$"#
    )
)]
pub struct Username(String);

This is because I'd rather keep magic in macros to a minimum, keeping the code as "rust-like" as possible. I think this is easier for the library as well: just accept a string here and leave it up to the user to create.

Alternative syntax could be with // like in scripting languages:
regex = /^\w+@\w(\.\w)+$/

If you're reading this, pleasure share your opinion.

I'd prefer seeing macro input the same as regex crate's input. So, definitely a string literal.

lazy-regex - seems to be based on top of regex. Can be very helpful, since the regex is check at compile time

No need to increase number of dependencies for that. Regex may be trivially validated by proc macro expanding it.
It would also be nice to accept not only string literals, but constants and constant expressions too. Sometimes we do want to keep regex description separately and reuse in multiple places, despite the fact that in such cases we won't be able to validate them in compile-time.

@tyranron @jssblck Thanks to your contribution.
Ok, so we agree we don't want regex = /abc/, but rather
regex = "abc" and regex = r#"abc"# (both are just normal strings  from the rustacean point of view).

No need to increase number of dependencies for that. Regex may be trivially validated by proc macro expanding it.

This is a good point. A tricky part is: if the regex is validated at the moment of expanding it means:

regex dependency is needed at compile time
regex versions by at compile time and runtime may diverge, which may result into oopsy behaviour (e.g. when something compiles but then suddenly crashes at runtime).

It would also be nice to accept not only string literals, but constants and constant expressions too

I agree, though don't have any clear idea yet on that. Shell the constant by of type &'static str or Regex or something else ?
For example I often use Regex in pair with once_cell (earlier it was lazy_static) to do something like this:
static SOCKET_REGEX: Lazy<Regex> = Lazy::new(|| {
    Regex::new(
        r#"(?x)
        [^\d](\d{1,3}\.\d{1,3}.\d{1,3}.\d{1,3}:\d{2,5})[^\d]
    "#,
    )
    .unwrap()
});

In this case doing something like
#[nutype(
    validate(regex = SOCKET_REGEX)
)]
pub struct Socket(String);

is tricky, cause nutype has no chance to know the type of SOCKET_REGEX at the moment of macro expanding.
What are yours development habits?

A tricky part is: if the regex is validated at the moment of expanding it means:
* `regex` dependency is needed at compile time

* `regex` versions by at compile time and runtime may diverge, which may result into _oopsy_ behaviour (e.g. when something compiles but then suddenly crashes at runtime).

No, it's quite trivial, imho. regex dependency is needed in both at compile time and at runtime, so you use the same version in both nutype and nutype_macros crates, which is trivially controllable. In nutype_macros crate, you use it for validating string literals. In nutype crate you keep its re-export, so in proc macro expansion you use something like:
static __NUTYPE_REGEX: ::nutype::once_cell::sync::Lazy<::nutype::regex::Regex> =
    ::nutype::once_cell::sync::Lazy::new(|| {
        :nutype::regex::Regex::new(#regex_lit).unwrap()
    })

I agree, though don't have any clear idea yet on that. Shell the constant by of type &'static str or Regex or something else ?

First, I was thinking just about any expression returning &'static str.

#[nutype(
    validate(regex = SOCKET_REGEX)
)]
pub struct Socket(String);

But being able to feed there Regex or Lazy<Regex> is a very nice idea!

is tricky, cause nutype has no chance to know the type of SOCKET_REGEX at the moment of macro expanding.

This is easily solvable by some additional type-level glue in nutype crate, which will aid the macro expansion with return-type polymorphism:
// in `nutype` crate

pub trait IntoRegex: Sized {
    fn into_regex(self) -> Lazy<Regex>
}

impl IntoRegex for &str {
    fn into_regex(self) -> Lazy<Regex> {
        Lazy::new(|| Regex::new(self).unwrap())
    }
}

impl IntoRegex for Regex {
    fn into_regex(self) -> Lazy<Self> {
        Lazy::new(|| self)
    }
}

impl IntoRegex for Lazy<Regex> {
    fn into_regex(self) -> Self {
        self
    }
}

and expand it like:
static __NUTYPE_REGEX: ::nutype::once_cell::sync::Lazy<::nutype::regex::Regex> =
    ::nutype::glue::IntoRegex::into_regex(#whatever)

No, it's quite trivial, imho. regex dependency is needed in both at compile time and at runtime, so you use the same version in both nutype and nutype_macros crates, which is trivially controllable.

I am not convinced that it will always be true. There can be the following deps tree:

App

regex version A
nutype

nutype_macros

regex version B

However, maybe it's good enough to go, assume that in most cases regex version will be the same and in case of differences, the differences won't cause any problems (hopefully), cause regex syntax is very stable.

This is easily solvable by some additional type-level glue
Good point, I forgot that we can play that trick.

Although, some users may not use once_cell so it may require one more extra feature flag.
@tyranron @jssblck What do you think would be a proper error variant when a regex is violated?
My initial idea was to have an error variant per validator. At this point Invalid is already used custom validator with.
I feel like Invalid could be a good name, but then it breaks this 1-1 match between validators and error variants.

@greyblake RegexMismatch/ed?

InvalidFormat?
On Mon, Feb 20, 2023, 12:48 Kai Ren @.***> wrote:

@greyblake https://github.com/greyblake RegexMismatch/ed?
—
Reply to this email directly, view it on GitHub
https://github.com/greyblake/nutype/issues/5#issuecomment-1436842480,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3W2BMEPQGZORFAFGOG4DWYNKZ7ANCNFSM6AAAAAAU3FJ5Q4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@jssblck @tyranron Addressed in https://github.com/greyblake/nutype/pull/24.
Hopefully I will release v0.2.0 next week with this included.

@jssblck @tyranron   FYI the feature is available in 0.2.0.


Add codegen/build-clients.sh script, update codegen/apis submodule

Problem
We're getting ready to release v1.0.0 of the Go SDK. Before we do that, we need to make sure we're generating our control and data plane client code from the proper specifications. When the go-pinecone repo was originally set up, the apis submodule was created and points to a private, Go-specific cut of the OpenAPI and proto files from about 4 months ago.
Since then we're made changes to how we approach client generation, and where our upstream spec files live.
Solution

Add new codegen/ folder to hold both the apis submodule and the build-clients.sh script.
Update .gitmodules to move apis -> codegen/apis.
Add a build-clients.sh script. Originally, just gen called a few shell commands for generating from OpenAPI and protos. The new script handles generation in a fashion similar to our other repos, and allows specifying a specific API version.
Update client.go / client_test.go to handle some changes to underlying types.

My approach was based on the work @jhamon has done in other repos to align our code generation pipelines.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[X] Infrastructure change (CI configs, etc)
[ ] Non-code change (docs, etc)
[ ] None of the above: (explain here)

Test Plan
There weren't changes needed to the actual SDK interface. Make sure CI runs and our unit & integration tests are passing as expected.

Is the version being set in X-Pinecone-Api-Version header for control plane actions? For some other languages, I had to augment the generated code by writing the version number somewhere (see python and ts) and then setting up that custom header.

Good question, I was going to implement the header in a follow up PR, but given what you mentioned I should probably just do it here. Thanks for the heads up, I had wrongly assumed the version number was written in as part of the spec build process and wasn't considering it.

The generated java included the version number, but still required some effort to hook it up into headers properly. So it's worth double checking that is being done correctly after this refactoring.

Added a generate_version_file() function to the build-clients.sh script. This outputs whichever API version was used to generate the code into a Go file as a constant, which is then imported and used for sending the X-Pinecone-Api-Version with requests.


Custom dev server no longer reconnects

Describe the bug
When using the latest beta version of Vite (3.0.0-beta.10) and the latest plugin-react (2.0.0-beta.1), after you npm run dev then stop the server and restart it again, the polling in the browser never reconnects with the following errors:
client.ts:297          GET http://localhost:24678/ net::ERR_FAILED 426
waitForSuccessfulPing @ client.ts:297
await in waitForSuccessfulPing (async)
(anonymous) @ client.ts:104
localhost/:1 Access to fetch at 'http://localhost:24678/' from origin 'http://localhost:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I assume it might be related to this change.
You can easily reproduce it via the playground/ssr-react example.
Reproduction
N/A
System Info
System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Max
    Memory: 722.75 MB / 64.00 GB
    Shell: 5.1.16 - /usr/local/bin/bash
  Binaries:
    Node: 17.9.0 - ~/.nvm/versions/node/v17.9.0/bin/node
    npm: 8.5.5 - ~/.nvm/versions/node/v17.9.0/bin/npm
  Browsers:
    Chrome: 103.0.5060.114
    Safari: 15.5
  npmPackages:
    @vitejs/plugin-react: 2.0.0-beta.1 => 2.0.0-beta.1

### Used Package Manager

npm

### Logs

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to [vuejs/core](https://github.com/vuejs/core) instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

Adding an hmr.clientPort of 5173 seems to fix it, but then results in a separate issue where the page itself randomly reloads while the server is running.


start ball at random location

It would be nice if the ball started at a rando mlocation. Otherwise, the players will notice that they need to move the pads to the same places every game...

I was thinking about instead having  ball_velocity_y be random instead. But the only problem is anything over 1 is too fast, and I can't seem to get it to work with decimals. If I set ball_velocity_y to a decimal the ball gets stuck on the walls.

Just added it along with random direction


Make TaskEither a Monoid

The added functions are a combination of the Monoid definitions from Task and Either.

Thanks @mlegenhausen


cmd/link: remove dependencies on cmd/internal/obj

cmd/internal/obj is for writing Go object files, whereas cmd/link only reads Go object files.  We should remove cmd/link's dependencies on cmd/internal/obj by moving legitimately shared constants/types into separate packages.
See also #14782.

Yes please.
On Thu, Apr 7, 2016 at 3:09 PM, Matthew Dempsky<EMAIL_ADDRESS>wrote:

cmd/internal/obj is for writing Go object files, whereas cmd/link only
reads Go object files. We should remove cmd/link's dependencies on
cmd/internal/obj by moving legitimately shared constants/types into
separate packages.
See also #14782 https://github.com/golang/go/issues/14782.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/15165

Concur. I even wonder about de-coupling the constants used for LSym.Type between cmd/internal/obj and the linker -- the latter uses far more. The code to read them from object files could map from the obj.Type to the ld.Type. Or something -- currently the constant definitions in obj "know" way too much about the guts of the linker. (It doesn't help that the linker depends on the order these constants sort in)


Fix typo

It works. However the deploy fails because we didn't migrate https://github.com/kubic-project/velum/pull/104 to https://github.com/kubic-project/caasp-container-manifests. I can take a look at it.

https://github.com/kubic-project/terraform/commit/00515174d73a96a174bd35be1207703542412a8a introduced a problem in which we never really wait for the port to be there.
However, and when https://github.com/kubic-project/velum/pull/104/commits/5224276eef306de95d9323e5202098548ff4309b hits https://github.com/kubic-project/caasp-container-manifests we won't need to wait for a port but for a unix socket (just to keep it in mind).
This is why the until isn't working as expected on provision-dashboard.sh:
$ netstat -lnt | awk '$6 == "LISTEN" && $4 ~ ".THISDOESNTEXIST"'
$ echo $?
0


Fails to save & load dictionaries & corpora with extended character set

bm25s.BM25 save and load methods crash as they generate / load json files with non-ASCII characters.
This can be fixed with something like:
bm25s.BM25.save method:
  with open(vocab_path, "wt", encoding='utf-8') as f:
      json.dump(self.vocab_dict, f, ensure_ascii=False)

and bm25s.BM25.load:
        if load_vocab:
            vocab_path = save_dir / vocab_name
            with open(vocab_path, "r",encoding='utf-8') as f:
                vocab_dict: dict = json_functions.loads(f.read())
        else:
            vocab_dict = None

Also saving & loading corpus should be handle accordingly.

Thank you. can you make a PR + test cases in tests/core? I will merge it once the test pass.

Here's a test template:
import unittest

import numpy as np

import bm25s

class TestClassNameForYourCase(unittest.TestCase):   # TODO: write a meaningful name
    def setUp(self):
        np.random.seed(42)
        self.k = 5
        self.scores = np.random.uniform(-10, 10, 2000)
        self.expected_scores = np.sort(self.scores)[-self.k:][::-1]
        self.expected_indices = np.argsort(self.scores)[-self.k:][::-1]

    def test_your_function_here(self):  # TODO: write a meaningful name
        result_scores, result_indices = topk(self.scores, self.k, backend="numpy", sorted=True)
        self.check_results(result_scores, result_indices, sorted=True)

if __name__ == '__main__':
    unittest.main()

Here you go.

import unittest

import numpy as np

import bm25s

class TestClassNameForYourCase(unittest.TestCase):   # TODO: write a meaningful name
    def setUp(self):

        self.text =["Thanks for your great work!"] # this works fine
        self.text = ['שלום חברים'] # this crashes!

        # create a vocabulary
        tokens = [ t.split() for t in self.text ]
        unique_tokens = set([item for sublist in tokens for item in sublist])
        vocab_token2id = {token: i for i, token in enumerate(unique_tokens)}

        # create a tokenized corpus
        token_ids = [ [vocab_token2id[token] for token in text_tokens if token in vocab_token2id] for text_tokens in tokens ]
        corpus_tokens = bm25s.tokenization.Tokenized(ids=token_ids, vocab=vocab_token2id)

        # create a retriever
        self.retriever = bm25s.BM25()
        self.retriever.index(corpus_tokens)

    def test_your_function_here(self):  # TODO: write a meaningful name
        # both of these fail: UnicodeEncodeError: 'charmap' codec can't encode characters in position 2-6: character maps to <undefined>
        self.retriever.save('test_bm25s', corpus=self.text)
        self.retriever.load('test_bm25s', load_corpus=True)

if __name__ == '__main__':
    unittest.main()

This looks good! Looking forward reviewing your PR

Hi @xhluca, is the issue resolved? Had faced the same. In case not, please make the changes, I would be delighted to use your library.

I have not had the bandwidth to make those changes myself, I will take a stab once I have the time. If it's something you urgently need, feel free to create a PR and I'm glad to review it.

@xhluca I have created a PR as per the changes after testing it with Non ASCII chars, please review it. Thanks.

Fixed in latest pr


Add files via upload

Sencha Electron products

What are these files for? Could you add a bit more context to this PR?

Icons for Sencha's products using Electron

@adwankar any reason you don't just add these to your existing PR here? https://github.com/electron/electron.atom.io/pull/528

Closing this out. @adwankar please go ahead and update the other PR: https://github.com/electron/electron.atom.io/pull/528


Would it be a way to show local images ?

Hello @KmolYuan
I'm looking for a way to include static assets locally like img, gifs ...
I don't see any example where it's possible, not in the sources, but perhaps I just didn't seek enough ?
So is there a way ?

Images can be inserted by img key or Markdown syntax in doc key.
# single
img:
  src: path/to/local-image.png
# multiple (placed horizontally)
img:
- src: img1.png
- src: img2.gif

Okay, I think it is caused by my server asset folder settings; the root files are ignored but files in subfolders work.
I will try to fix this.

It is indeed working fine in any sub folder
as long as the subfolder is already existing when the server is ran.
Thank you it's already all I need to go on.


Add attempt count to queue model

Overview
Add attempt count to queue model to enable retries in async platform.

Two possible code concerns, and a general concern as to whether this belongs as part of the raw dispatch object or as part of the JSON body (where relevant).
The retry count is fine here either way as the async platform is currently the only consumer of this library, but it feels to me like this is a detail specific to the consumers of this project not this project itself?


Debian - segmentation fault  dotnet new console

Hi, just followed the official guide to install dotnet on debian.
Install went fine, but when I tried to launch the tutorial example, I get :
`
$ dotnet new console -o hwapp
Getting ready...
[1]    18216 segmentation fault  dotnet new console -o hwapp
`

Can you run an strace and upload the log file (logfile below) somewhere?
strace -f -o logfile dotnet new console -o hwapp

Here you go :
$ dotnet --info
.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     debian
 OS Version:
 OS Platform: Linux
 RID:         debian-x64
 Base Path:   /usr/share/dotnet/sdk/2.0.0/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

The strace also returns a segmentation fault :

$ strace -f -o logfile dotnet new console -o hwapp
Getting ready...
[1]    1297 segmentation fault  strace -f -o logfile dotnet new console -o hwapp

Hi, any news on this ? Anything else I can do to help debug?

@livarcocc is this the one people have been working around by disabling the first run experience?

Looks like this one: https://github.com/dotnet/core/issues/649#issuecomment-330445968
@livarcocc do you have an issue tracking fixing this in the cli?

export DOTNET_CLI_TELEMETRY_OPTOUT=1
removed the segmentation fault for me

👍

should I close the issue or you want it left open until a real fix has been issued?

Lets leave it open until @livarcocc confirms that there is an issue somewhere tracking the fix. Once we have that, this can be closed. Thanks @ierpe!

@Petermarcu @steveharter can you help debug this and understand why the telemetry code is causing a seg fault? If this were in native code, I would expect a stack trace somewhere. But we will investigate.

Could this be an incompatibility via libcurl? See https://github.com/dotnet/core/issues/963#issuecomment-330842070 and https://github.com/dotnet/corefx/issues/8951#issuecomment-299793545

@Petermarcu you're welcome!
@omajid For info my version of libcurl is : libcurl 7.55.1

@livarcocc I'm installing fresh debian now, will report back tomorrow.

I couldn't repro. I used debian stretch. One difference is that dotnet --info reports the RID as Linux-x64 instead of debian-x64.
dotnet --info
.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     debian
 OS Version:  9
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /usr/share/dotnet/sdk/2.0.0/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

@ierpe what is the contents of your /etc/apt/sources.list.d/dotnetdev.list file? I have:
deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-debian-stretch-prod stretch main

the same issue @Mac
the official guide says:
dotnet new console -o hwapp
cd hwapp

I checked the dotnet help (dotnet core sdk 2.0)
~ dotnet help new
.NET Initializer

Usage: dotnet new [options]

Options:
  -h|--help             Show help information
  -l|--lang <LANGUAGE>  Language of project [C#|F#]
  -t|--type <TYPE>      Type of project
➜  source mkdir dotnet

all the guide shuold be update to :
mkdir -p hwapp
cd hwapp
dotnet new -t console

@steveharter /etc/apt/sources.list.d/dotnetdev.list file :
deb [arch=amd64] https://packages.microsoft.com/repos/microsoft-debian-stretch-prod stretch main

FWIW here's my Debian Stretch environment (no repro, clean install)

$ curl -V
curl 7.52.1 (x86_64-pc-linux-gnu) libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

$ openssl
OpenSSL> version
OpenSSL 1.1.0f  25 May 2017

$ cat /proc/version
Linux version 4.9.0-3-amd64<EMAIL_ADDRESS>(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19)

$ cat /etc/*-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

@icedfish

the same issue @mac

So you're also getting the seg fault during dotnet new console?
Does export DOTNET_CLI_TELEMETRY_OPTOUT=1 prevent the seg fault?

@ierpe have you tried to debug the seg fault, or look at any dumps in order to determine the crashing module\stack? I can send you gdb instructions.

@icedfish

I checked the dotnet help (dotnet core sdk 2.0)

Can you confirm this? What does dotnet --version say? What does dotnet --info say?

~ dotnet help new
.NET Initializer

Usage: dotnet new [options]

Options:
  -h|--help             Show help information
  -l|--lang <LANGUAGE>  Language of project [C#|F#]
  -t|--type <TYPE>      Type of project
➜  source mkdir dotnet

That looks like the older 1.0 Preview SDK. -t does not work with the 1.x or 2.x SDKs.

@steveharter nope I haven't, don't know how actually...

@ierpe probably the easiest way is to catch the seg fault with gdb if you can. You'll likely need to be root to install that. So
su
apt-get install gdb
exit

and then run dotnet:
gdb --args dotnet new console
run

after seg fault
backtrace

hopefully you get a crashing module (libcurl?) and stack.

@omajid sorry , I checked my system, find that I used to install the old 1.0RC SDK before install the new 2.0 sdk.
after uninstall the old version by the cli script
and reinstalled the sdk 2.0, It's ok now.
But it's really puzzle, the the 2.0 sdk not remove the old sdk automaticlly or even notify me the incompact.....

@steveharter is that what you wanted ?

$ gdb --args dotnet new console
GNU gdb (Debian 7.12-6) <IP_ADDRESS>61007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from dotnet...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/dotnet new console
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7f0ea6576700 (LWP 11703)]
[New Thread 0x7f0e9ffff700 (LWP 11704)]
[New Thread 0x7f0ea5d75700 (LWP 11705)]
[New Thread 0x7f0ea5574700 (LWP 11706)]
[New Thread 0x7f0ea4d73700 (LWP 11707)]
[New Thread 0x7f0e9f7fe700 (LWP 11708)]
[New Thread 0x7f0e2e140700 (LWP 11709)]
[Thread 0x7f0e2e140700 (LWP 11709) exited]
[New Thread 0x7f0e2e140700 (LWP 11710)]
[New Thread 0x7f0ea41b9700 (LWP 11711)]
[New Thread 0x7f0e2d93f700 (LWP 11712)]
[New Thread 0x7f0e2d13e700 (LWP 11713)]
[New Thread 0x7f0ea4178700 (LWP 11714)]
[New Thread 0x7f0e07ffd700 (LWP 11715)]
[New Thread 0x7f0e077fc700 (LWP 11716)]
[New Thread 0x7f0deed59700 (LWP 11717)]
[New Thread 0x7f0dee558700 (LWP 11718)]
[Thread 0x7f0dee558700 (LWP 11718) exited]

Thread 16 "dotnet" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f0deed59700 (LWP 11717)]
0x00007f0e2c67dd6d in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(gdb) backtrace
#0  0x00007f0e2c67dd6d in ?? ()
   from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#1  0x00007f0e2c678c8b in X509_verify_cert ()
   from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x00007f0e31168e06 in ?? ()
#3  0x00007f0deed57e50 in ?? ()
#4  0x6c00fa377b77ae7b in ?? ()
#5  0x0000000007bcbd60 in ?? ()
#6  0x00007f0ea83f5488 in ?? ()
   from /usr/share/dotnet/shared/Microsoft.NETCore.App/2.0.0/libcoreclr.so
#7  0x00007f0deed58688 in ?? ()
#8  0x00007f0e312a2580 in ?? ()
#9  0x00007f0e312a2580 in ?? ()
#10 0x00007f0deed57e50 in ?? ()
#11 0x00007f0e31168e06 in ?? ()
#12 0x00007f0deed57ee0 in ?? ()
#13 0x00007f0e312a2580 in ?? ()
#14 0x00007f0e083b6760 in ?? ()
#15 0x0000000000000001 in ?? ()
#16 0x00007f0e080de958 in ?? ()
#17 0x00007f0e08634f90 in ?? ()
#18 0x00007f0e08634f20 in ?? ()
#19 0x00007f0e083b6760 in ?? ()
---Type <return> to continue, or q <return> to quit---
#20 0x00007f0de40ff270 in ?? ()
#21 0x00007f0deed57f50 in ?? ()
#22 0x00007f0e30f7ce57 in ?? ()
#23 0x00007f0deed57ef0 in ?? ()
#24 0x00007f0e08634f20 in ?? ()
#25 0x00007f0e080de958 in ?? ()
#26 0x0000000000000000 in ?? ()

@ierpe yes thanks. It is likely crashing when calling into OpenSsl.
Can you run a couple commands please:
$ openssl version
and
 ls /usr/lib/x86_64-linux-gnu/libssl.so.*
You should get back
OpenSSL 1.1.0f  25 May 2017
and
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.2  /usr/lib/x86_64-linux-gnu/libssl.so.1.1
If not, and you're getting the 1.0.0 version you can give this a try:
apt-get remove ssl1.0.0
apt-get install ssl1.0.2

@steveharter

$ openssl version
OpenSSL 1.1.0f  25 May 2017

$ ls /usr/lib/x86_64-linux-gnu/libssl.so.*
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
/usr/lib/x86_64-linux-gnu/libssl.so.1.1

@ierpe since you have the 1.0.0 version, that is likely conflicting and has been a problem for others. You can remove that by doing an apt-get remove ssl1.0.0
Typically the 1.0.0 version is there due to an upgrade to stretch or buster, and not a clean install. It could have come from another app's dependency as well.
cc @bartonjs is there an issue to address this in some manner? Like if 1.0.2 is there use that first. Thanks

@steveharter removing ssl1.0.0 fixed it for me, thanks for the support!

@steveharter The reason I had 1.0.0 version was that spotify-client depends on it and I had manually installed it. Please refer to my post in #649

I have multiple apps that depend on version 1.0.0 and others that depend on 1.0.2.
What do I do?


screen is swiping in iphone xs when moving the slider

[X ] I have searched existing issues
[ X] I am using the latest multi slider version

I upload some video that explain what is happen.
Link:
https://streamable.com/4s1po

Did you try to place the component further away from the bottom? Pretty sure that area is restricted by Apple for their gestures


fix ceph group_vars (else ansible ceph deployment fails)

Without uncommenting these 4 variables, the ansible-ceph deployment failed
Note: the (very active) ansible-ceph roles dependencies were downloaded around the 10.may (18h CEST), when I initially started the setup.

Note: In latest master of this repos ( since commit https://github.com/ClusterHQ/flocker-ceph-vagrant/commit/3623f3e6a319a15890eee259d1bc5b6b63ba10f3 )  a older ansible-ceph version from end of april is used, which does not require the change in this PR!

@lhoss should we leave this open?

you can close it, as the current version of the repos works (and so should the latest ansible-ceph AFAIR)


Peer Feedback  from Group 9

Hello group 10,
Great Job! We (Jacob, Santiago, Yuyan from group 9) all enjoy reviewing your World Happiness Report Explorer app. It is very organized and informative. If I were a policy analyst working for the government, I will find the app is super useful for helping me identify how happiness scores change over time for our country while comparing with the rest of the world. If I saw a country had a much better performance than our county, I can even explore which factors make such difference(e.g. GDP, family, life expectancy). In this way, I think it can point me to right direction for my further research and even future advocacy.
What we like:

As I mentioned, we like the overall layout of your app. Everything is so clear and organized. The structure of the dashboard allow us to easily and quickly understand the app.
We also like the way that the drop-downs and sliders interact with the plots. As I select more features, more plots will show up! So cool!
The overall plot types are very efficient! We can always easily compare the happiness score over time for two countries. The line plots are very suitable and in line with the purpose of the app.
The app takes just one screen, we like it as there is no scrolling needed.

What we suggest: (we might be wrong)

We found that there are so many options in the countries, we like it. But we would suggest to add another filter, such as continent. For the purpose of this dashboard, if I really want to compare one county with some other countries together(as benchmark), then I cannot do that. All I can do is select them one by one and then drop them one by one. Also I select more than 5 countries, the app becomes overwhelming quickly.
We also noticed that for the contribution plots, there is no y-axis scales for the plots on the right hand side. Initially, I assume they have the same scale as the plots on the left. But after careful comparison, I do not think this is how it works, at least from an audience perspective. Because the white grid lines are not aligned. Maybe it worth to add the scales of the y-axis for all plots to avoid confusion.
I am using the mac laptop with full screen. I found out that if I select all the contribution plots, the titles and the axes of those plots will all overlap together. Maybe it's because there are so many plots on the same screen. Maybe try to combine two relatively unimportant factor together.
Maybe add a card or some other plot types in the app. Currently they are all line charts.(But still very clear!)

Overall, we think your group did a amazing job in designing the dashboard! Hope our suggestions can help in your Milestone4. Have a great weekend!

Thanks Group 9!
We have addressed this feedback in #34, #30


Exclude the generated files from linting

It takes a long time

Coverage decreased (-23.5%) to 4.097% when pulling a0faa58efcdac75c720188d49b88c742e8f19215 on matthchr:feature/exclude-generated-files-lint into 64ab538860b7458e8f64862f3e36263538d3fceb on Azure:master.


rustywind: 0.17.0 -> 0.18.0

Diff: https://github.com/avencera/rustywind/compare/v0.17.0...v0.18.0
Changelog: https://github.com/avencera/rustywind/blob/v0.18.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

https://github.com/avencera/rustywind/pull/77 added a dependency on the ureq crate, which transitively pulls in ring. The random number generator in ring requires linking to the Security framework on macOS, so that needs to be added.

nice catch!


Add Google Analytics code to the website

Since the grant has started officially, one of the things I'd like to do is to have a clearer idea of what visitors do, where they come from, and where we lose them; I'd like to add Google Analytics code to the site and have it working for at least a month. In principle, I'd use my own code, but if there's some official Google account I could use, and whose results I can access, that would be fine.
In principle, I would remove it once I finish the grant, but I can leave it there if it helps, or change it to another one.
Any ideas for/against?

I don't know if this something desired.
Users like me frown upon google analytics (or any other type of tracers).  I presume our users are the type that will at least run adblockers, resulting in severely skewed results.
Wouldn't webserver logs provide all the needed info? E.g. what docs pages are popular?

They might, but I don't have access to the server. For the time being
there's just the breakdown of visited pages, but I need a deeper analysis:
how many pages visited per session, landing page, that kind of things.
I could include it temporarily, during the study, and eliminate it once I
get an idea of what's going on.

Not vetoing anything (or in the position to do :) ), just a heads up that privacy aware users don't know if their info is used correctly or not.
Looking forward to your work!

Someone in a privacy list I participate has suggested this one
https://matomo.org/
It's got a 30-day free trial period. Could be enough for the purpose of
this. Would that be OK?

I am very much against using a proprietary or 3rd party service to track all users of the site. If it were a self-hosted system (so all data doesn't get shared with Google or another service), I don't mind.

Just anecdotical, but my adblocker (ublock origin) blocks that domain by default :).

@nxadm One of the many blocking plugins I use in Firefox also takes it out. But I don't expect everyone to have a privacy-centric setup in their browsers. These people also shouldn't be tracked by 3rd parties by using our docs. Especially not by 3rd parties that are known to abuse this data for corporate profit.

@Tyil Yes, on top my pihole block that as well. My post should not be read as "it's ok, it's blocked" but as "it's pretty useless because it's blocked".

So we would have to go with something self-hosted, right?

If you want to track users, that's the way I would suggest you go, yes.

Self hosting would be a lot more work than the cloud solutions which are generally adding a few lines of javascript into the HTML. This literally takes a few minutes rather than the few hours of self-hosting setup and probably maintenance time.
If people are offering to do the work of self hosting then that's good but not sure its worth it for a few weeks of run time.
You could offer a "opt out" link for people quite easily with Google Analytics and probably with other services like Matomo for anyone objecting to the privacy issues who isn't already running privacy enhancing brower plugins.

That would be really be helpful and something I can personally do without
depending on other people and their installation policies on production
servers. It would really be just temporary and it would go for the greater
good of improving Perl6's documentation.

@stmuk I actually set up Matomo to see how much effort it is. Though I did use docker for it, the effort is minimal, certainly not "a few hours".
I still maintain we should have privacy by default on the docs, not "all your privacy is void unless you find this hidden button to give you privacy from this moment onwards".
@JJ A self-hosted Matomo is easy to setup and seems to give everyone what they want. I'm voting for this solution.

To the title:
⚠ No. ⚠
Adblockers get rid of this stuff, and for a good reason. Let's not spit in face of our users even if we have good intentions (a large number of them have face shields anyway).

Wouldn't webserver logs provide all the needed info? E.g. what docs pages are popular?

They might, but I don't have access to the server

Then you should just ask around on #perl6 and I'm sure you'll be provided with access.
As for self-hosted matomo… uhhhh… I don't know. Looking at their website (which I had to temporarily whitelist in my adblocker…):

Browser addons blocking the Matomo (Piwik) Tracking Javascript (NoScript, DoNotTrack, etc.) If you use browsers addons such as Adblock, Adblock plus, NoScript, Ghostery or others, the Matomo Javascript code is not executed in your browser. Try to use a different browser that does not have these extensions, or disable these browser extensions and try again.

So IMO we should not waste any effort in this fight with users. Look at apache logs (or whatever), and you'll get half of the info you want. As a user I think the other half you shouldn't have.

I still maintain we should have privacy by default on the docs, not "all your privacy is void unless you find this hidden button to give you privacy from this moment onwards".

Correct.

OK. I'll try to obtain some logs and see how I can work with them to extract the information I need. I'm closing this now.

@JJ You can still use Matomo in that scenario. Fire up a VM, container, or whatever you like, and load up the logs into that.
But there's plenty of other ways one can parse the logs. I've heard Perl is great at parsing text ;)


libcalico-go should improve error handle when use list+watch resource mode to reduce load on apiserver

we use an old version before https://github.com/projectcalico/libcalico-go/pull/1484 that list resource with consistent read;  it will read from etcd directly;
we use felixconfig change some param,  too many list pod make our apiserver over load and oom ;
we study the master source code,  even though list + watch read from cache (rv=0) after  https://github.com/projectcalico/libcalico-go/pull/1484;  but I think some items should improve also;

allowBookMark Should add like https://github.com/projectcalico/libcalico-go/pull/1484 TODO
felixconfig change param should restart Felix Should Doc annotation; It is too rish in BigCluster;  When update config restart Should add random wait time reduce cluster load;
golang use http2 default, so list + watch retry will not LB to another apiserver instance;  (over load with more retry)
(1)  libcalico-go should use backoff when handle error like k8s goclient informer, eg: 429, service unavaliable;
(2)  client config Burst add to 100,  client will send more request when some error;
(3)  RVTooLarge error should handle like RV too small like https://github.com/projectcalico/calico/pull/6045
data encode use application/vnd.kubernetes.protobuf will faster 10x  like kube-scheduler and kube-controller
I am not sure is it necessary to load all Pod in Felix,  program NetworkPolicy ?

@caseydavenport @fasaxc

Thanks for the tips, yes, it'd be good to get some of those done (they've been on the backlog for a while but it's hard to prioritise them vs more serious bugs).
You should use Typha if your APi server is getting overloaded.  That reduces the load because only Typha has a watch; felix just connects to Typha instead.

Thanks for the tips, yes, it'd be good to get some of those done (they've been on the backlog for a while but it's hard to prioritise them vs more serious bugs).
You should use Typha if your APi server is getting overloaded. That reduces the load because only Typha has a watch; felix just connects to Typha instead.

explain about apiserver overload ,   it is one of cluster instance  overload because retry will always happen on One TCP Connection due to HTTP2;
The process maybe :

one instance maybe overload oom because too many request;
all broken client reconnect to instance2,  overload ,  retry , oom;
the apiserver broken one by one ,  until all cluster ~~~~

If request LB to every instance ,  The server cap is enough;   But  http2 retry on One Instance will broken this One first;
I think it is same as Typha ,  will overload one by one ....
you are right that maybe have more serious Todo;  I think calico is good enough,  But this Process just maybe happen on BigCluster ,  it is more important than  all small cluster;  expect more attention;  (smile)

How many nodes do you have? Small clusters run 3 x Typha. If you have 100 nodes you'll have 3 connections to API server, not 100. 30x reduction in load.

you are right;   But I think  it just overload  from apiserver  to Typha Server Instance ....

Sorry, I don't understand; Typha won't get overloaded, it's designed to handle hundreds of Felix connections.

Please upgrade Calico and Kubernetes to the latest versions and then start using Typha.  If that doesn't solve your problem we'll be in a much better position to investigate.

we will try it when have an opportunity;
I think main is  HTTP2  multi stream on One TCP Connection ,  L4 lb about connection has no affect about stream requests;
kube-apiserver use --goaway-chance  random close http2 connection to make connection more blance ,  even though same connection != same http request ,  but have an change to reblance connection;
It is same as other Servers use HTTP2  list + watch mode ....

Watch bookmarks is the main one that would really help, I think. It's just very tricky to plumb through libcalico-go without breaking anything else. There are several layers with very subtle error handling that need to be dealt with.

Get data with encode with protobuf from apiserver
Encode from json to protobuf breaking nothing when get data from apiserver also;
just:
config, _ := clientcmd.BuildConfigFromFlags("", *kubeconfig)
config.ContentType = "application/vnd.kubernetes.protobuf"

I'd love to give that a go if it has such a big impact; I worry about subtle breakages/incompatibilities with all our custom CRDs and so on but maybe it just works and gives a big win.
Why don't you put up a PR and we can run it through our CI tests.

Looks like protobuf only supported for some resources: https://kubernetes.io/docs/reference/using-api/api-concepts/#alternate-representations-of-resources.  That makes me more confident that it's a good idea: only a few resources to check and no CRD changes to worry about.

I'd love to give that a go if it has such a big impact; I worry about subtle breakages/incompatibilities with all our custom CRDs and so on but maybe it just works and gives a big win.
Why don't you put up a PR and we can run it through our CI tests.

maybe I can have a try ......

I think Typha is an better design (send batch msg to other component with TCP Conn) after study source code  to reduce apiserver load ....

Typha and Felix share the libcalico-go code, any improvement to one also improves the other (but simply switching to Typha should reduce load a lot just by virtual of having 100x fewer connections to your API servers).

Typha and Felix share the libcalico-go code, any improvement to one also improves the other (but simply switching to Typha should reduce load a lot just by virtual of having 100x fewer connections to your API servers).

yes

@gaopeiliang are you sure we don't use protobuf?  I asked on Kubernetes slack and they said client-go uses it by default

Breadcrumb numbers aren't revisions, they're not in sync between typhas.  Clients start from scratch with the new typha connection.  Recent versions of typha support compressed snapshots and they share them between clients.  Much faster than the API server.

Breadcrumb numbers aren't revisions, they're not in sync between typhas. Clients start from scratch with the new typha connection. Recent versions of typha support compressed snapshots and they share them between clients. Much faster than the API server.

en ,,  I think the obj in breadcrumb, like pod update obj  is versioned;    if  client scratch from diff typha instance that unsync ,  client maybe receive repeate breadcrumb, and repeate update obj ?  like pod obj version from 10 -> 7 -> 8 -> 9 -> 10

Calico is designed to be memoryless, it would apply state 10, then state 7, then state 8, then 9, then 10 again.  Not ideal but this is also very rare in practice because Typha is generally a couple of orders of magnitude faster than its clients.


Update documentation website basics

[x] Remove example pages and blog posts
[x] Replace logos
[ ] Remove Docusaurus references and images

@Fashander I added the third point because we do have some Docusaurus images on https://docs.ferretdb.io


Calculating the distance

Hi,
May I ask you to explain this line of the code, for which reason you are using those numbers.
Distance= -593.97*average**(3) + 1506.8*average**(2) - 1373.1*average + 522.06
Thanks.

Hello,
This equation converts the values from the disparity map to a distance.
We use here a polynomial equation of order 3 as explained in your PDF since it represents the best fit for converting disparity in stereo to distance. How we established the coefficients is described somewhere in the youtube comments or also in the discussion part of the youtube channel.
Hope this helps.
Have a nice day/evening!


adds an annoying console.log

DO NOT MERGE THIS PR

Closing this PR since it was just an example for the purposes of onboarding new teammates


PLNSRVCE-363: preliminary e2e-test integration (will get verification once openshift/release is updated to consume)

the true verification of this will be once I update openshift/release for jvm-build-service a la https://github.com/openshift/release/blob/33aac19fbdcee42298798dc0f69d8873e55e50c2/ci-operator/config/redhat-appstudio/application-service/redhat-appstudio-application-service-main.yaml#L1-L3 and https://github.com/openshift/release/blob/33aac19fbdcee42298798dc0f69d8873e55e50c2/ci-operator/config/redhat-appstudio/application-service/redhat-appstudio-application-service-main.yaml#L21-L60
so quite possibly if the rehearsals in that upcoming openshift/release PR fail, I'll need to come back here and make updates
But minimally, this PR will verify

that the initial openshift/release bootstrapping done via https://github.com/openshift/release/pull/29191 produced the consequences we want
that these change do not affect the existing CI

FYI
@stuartwdouglas
@mmorhun
@psturc
@Michkov
Of course, if anybody in Europe is still online and sees something very obvious before I merge this, let me know and I'll update :-)

ok nothing broke so merging


Fix memory update to -1

- What I did
Close  #22516
- How I did it
If memory parameter is not changed by update command set is  as '-1'
- How to verify it
docker create --name test -m 50m busybox:latest
docker inspect -f '{{.HostConfig.Memory}}' test
# 52428800
docker update -m -1 test
docker inspect -f '{{.HostConfig.Memory}}' test
# -1

docker run -it -d --name test2 -m 50m busybox:latest
docker stats test2
# Shows 50m memory limit
docker update -m -1 test2
docker stats test2
# Shows no memory limits (host memory)

- Description for the changelog
Remove memory constraints after creating/running container with update command
Possibility to set memory to '-1' which removes memory constraints
Signed-off-by: boynux<EMAIL_ADDRESS>

ping @hqhq

There is a bug in my pull request I'm trying to fix that.

Pull request is ready for review, and I'm not sure why windowsTP5 is failing!
Ping @hqhq @runcom

I think it makes more sense to use docker update --memory -1 <id> to unset memory limit to unlimited, because it's the way to reflect cgroup api.

@hqhq yes, seems more legit. I can update my changes accordingly. I guess that's would a bit easier as well.

ping @hqhq I'm done with your suggested changes, and I think gccgo failure is not related to my changes.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-memory-update" git@github.com:boynux/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@boynux Thanks, but docs need to be updated as well.

@hqhq sure, actually I wanted to ask this question. Where are the docs please?

@boynux It's not working in my box:
$ docker update -m -1 d3cc5496e730
Error response from daemon: Cannot update container d3cc5496e730be54b9c109a5216fa92aa5ec7ed3c2382266850e6eda0947b71b: rpc error: code = 2 desc = "failed to write<PHONE_NUMBER> to memory.limit_in_bytes: write /sys/fs/cgroup/memory/docker/d3cc5496e730be54b9c109a5216fa92aa5ec7ed3c2382266850e6eda0947b71b/memory.limit_in_bytes: invalid argument\n"

I guess your change is not complete.

@hqhq  Regarding your test, that's interesting, the integration tests does exactly what you did and it passes the test (false-positive?). I also tried that several times with no issues. Would you please provide the create/run command for your container as well.
I'll check again to see if something is missing.

@boynux The integration test updates a stopped container, and my test is update a running container, just use:
$ docker run -ti --rm -n test -m 300M ubuntu bash
[switch to another terminal]
$ docker update -m -1 test

@boynux do you still have time to work on this?

Sorry I was very busy last week and this week too. I partially implemented
the run part but not ready to submit.
I don't promise this week but definitely next week I'm able to finish the
work. If there is schedule to release this this week then I'd suggest
someone picks up the last part otherwise I'll finish that by next week. (I
don't promise but if I find some time free this week I'll try to finish
that).
On Mon, May 23, 2016, 10:40 PM Alexander Morozov<EMAIL_ADDRESS>wrote:

@boynux https://github.com/boynux do you still have time to work on
this?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-221089326

ping @boynux have you had time to look into this?

I fixed the issue and I'll push my changes today.
On Thu, Jun 2, 2016, 1:55 AM Sebastiaan van Stijn<EMAIL_ADDRESS>wrote:

ping @boynux https://github.com/boynux have you had time to look into
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-223159284, or mute
the thread
https://github.com/notifications/unsubscribe/ABoR-L3h34hKJnm0fbbv7tp0Xkm5OUjpks5qHhwJgaJpZM4IZgNP
.

@boynux when you push your changes, can you also squash your commits, so that we have a single commit in this PR?

Sure, once all tests passed I'll do that. OK?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-223284148, or mute
the thread
https://github.com/notifications/unsubscribe/ABoR-JsOjCRj0XZPkaCrNItNH_cxNOBeks5qHtRJgaJpZM4IZgNP
.

@boynux tests are passed :)

@LK4D4 but review comments weren't addressed yet if I see correctly

@thaJeztah yeah, my comment was related to squash proposal

I'm working on the tests.

@thaJeztah tests passed, and commits squashed. Ready for review :)

I'm getting an error when testing this, but I'm running on Docker for Mac currently, perhaps someone else can test?
docker update -m -1 foo
Error response from daemon: Cannot update container dba001ad9f71e6707547e4b7df51126acb667242cfba374d2aa844aea5a3a01e: rpc error:
code = 2 desc = "failed to write<PHONE_NUMBER> to memory.limit_in_bytes: write /sys/fs/cgroup/memory/docker/dba001ad9f71e6707547e4b7df51126acb667242cfba374d2aa844aea5a3a01e/memory.limit_in_bytes: invalid argument\n"

LGTM :angel: but a little concern about the error on Docker for Mac :sweat:
/cc @justincormack

Actually, may be a "proxy" issue on Docker for Mac (@justincormack?)

OK, it looks like I found the difference; it looks like this fails if the container is running; I did docker run to create the container, not docker create; stopping the container allows you to update the memory;
# docker run --name test -m 50m -dit busybox
58f3bfefe0a90719a309822763c0966e690e0f7e4825a46fc1dd312b27d16816

# docker update -m -1 test
Error response from daemon: Cannot update container 58f3bfefe0a90719a309822763c0966e690e0f7e4825a46fc1dd312b27d16816: rpc error: code = 2 desc = "failed to write<PHONE_NUMBER> to memory.limit_in_bytes: write /sys/fs/cgroup/memory/docker/58f3bfefe0a90719a309822763c0966e690e0f7e4825a46fc1dd312b27d16816/memory.limit_in_bytes: invalid argument\n"

# docker stop test
test

# docker update -m -1 test
test

# docker inspect -f '{{.HostConfig.Memory}}' test
-1

@thaJeztah: Is that cgroup complaining about '-1'?
this test is doing the same: https://github.com/docker/docker/pull/22578/files#diff-221c6fb9a0aa122469c32da1609729deR230
Do you think it's Mac related or I missed something?

@boynux interesting; my second test was actually on Docker Toolbox (boot2docker) to exclude it being an issue in Docker for Mac

@thaJeztah Now I'm confused, let me do another round of manual testing, maybe there is something wrong with the test itself or Kernel.
According to @hqhq:

docker update --memory -1  to unset memory limit to unlimited, because it's the way to reflect cgroup api.

So I assume that error has something to do with cgroups (I'm not sure though)

It's possible it's related to kernel version; both Docker for Mac and boot2docker are on a recent kernel (I'll check the versions later on)

With kernel 4.4.0 I had no problem to execute docker update -m -1
Any idea?

Just checked; Docker for Mac; Kernel Version: 4.4.12, and my Boot2Docker version is on 4.4.8. Not sure why it fails, I'll have a look if I can find someone else to test

Actually, attempting to start the container after it's updated to -1 fails as well
Error response from daemon: rpc error: code = 2 desc = "oci runtime error: process_linux.go:286: setting cgroup config for ready process caused \"failed to write 104857600 to memory.memsw.limit_in_bytes: write /sys/fs/cgroup/memory/docker/e09f4e68a306d967d15f9db15c6e89304c583a1a52fd904a10dcf685e20f5d4e/memory.memsw.limit_in_bytes: invalid argument\""
Error: failed to start containers: test

And stop/start works here :|

Wait a moment memory.memsw.limit_in_bytes isn't it SWAP?

oh! hm, interesting

Fresh bundle and build, kernel cgroup swap enabled, everything works normal :(
I think it has something to do with Docker on Mac, probably Kernel issue or something.
I can't test it further because I have no Mac, it'd be great if you help to find out the root cause.

Yes, indeed; it's a default install of both Docker for Mac and Docker Toolbox / Boot2Docker, so other people may run into the same issue :cry:
I asked @justincormack if he had any thoughts on what may be causing this (but it's evening here, so may be until tomorrow that he'll be looking)

@thaJeztah Did you find anything regarding the issue? Is there something that I can do?

btw, I'll update the branch to latest master!

@boynux pls, rebase. thanks!

Sure 😃
On Fri, Jul 29, 2016, 1:33 AM Alexander Morozov<EMAIL_ADDRESS>wrote:

@boynux https://github.com/boynux pls, rebase. thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-236055628, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABoR-NwZZyAnE3SmYiiUaPGyZdi20Pvwks5qaTxVgaJpZM4IZgNP
.

@LK4D4 "janky" fails and seems to be incompatibility in cgroup! Any suggestion?

@boynux whoa, that's bad. Is it like new kernel stuff?

@boynux @LK4D4 oh! that's the exact error I got when testing on Docker for Mac; https://github.com/docker/docker/pull/22578#issuecomment-224264869
Also not sure if there's a relation, but; https://github.com/docker/docker/issues/25099
@justincormack any ideas?

@LK4D4 Well, I'm not sure that related to new Kernel changes. I'll investigate more.
@hqhq do you have any idea?

@boynux  since you are here, could you please also fix update --memory-swap -1?  I think --memory-swap has the same problem with memory

On Docker for mac, it seems to just be related to the swap limit, if I set unlimited swap limit then I can change the memory limit from 40m to -1 fine, if there is a swap limit it will fail, which seems reasonable. I guess this is just not true in some kernels.
So I think https://github.com/docker/docker/pull/25461 should provide a reasonable error message in this case.

@boynux Failure in janky is because Docker will set swap memory as twice of memory by default, with swap memory limited, you can not set memory unlimited. You need to set swap memory unlimited first as suggested by @coolljt0725 .

Ok, got it. I'll try to fix it then.
Thanks for help

Now it's getting more interesting, for some reason (Docker updates or Kernel?) I started to get the mentioned error on my machine too (not for swap memory but for memory limit itself). The funny thing is I get something like this (this is copied from previous comments):
Error response from daemon: Cannot update container 58f3bfefe0a90719a309822763c0966e690e0f7e4825a46fc1dd312b27d16816: rpc error: code = 2 desc = "failed to write<PHONE_NUMBER> to memory.limit_in_bytes: write /sys/fs/cgroup/memory/docker/58f3bfefe0a90719a309822763c0966e690e0f7e4825a46fc1dd312b27d16816/memory.limit_in_bytes: invalid argument"

And when I do this:
# echo "-1" | tee sys/fs/cgroup/memory/docker/58f3bfefe0a90719a309822763c0966e690e0f7e4825a46fc1dd312b27d16816/memory.limit_in_bytes
-1

It works with no errors!!! So right now I'm investigating to understand what causes this behaviour.
Any thoughts?

Ping

Any update @boynux, or do you need more input / assistance?

Yes, I can confirm the swap is not the only issue, I'm still having
troubles to set memory to -1 with recent master rebase! Any input / idea
would be great
On Thu, Sep 15, 2016, 5:34 PM Sebastiaan van Stijn<EMAIL_ADDRESS>wrote:

Any update @boynux https://github.com/boynux, or do you need more input
/ assistance?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-247363373, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABoR-G7bKGM-V-F5cZkVnUTi2D1cJkINks5qqWWCgaJpZM4IZgNP
.

@boynux set swap memory to -1 and then set memory to -1 still doesn't work ?  what's the issue?

@boynux can you rebase? Can take another look and see if we can resolve.

I've rebased the master against my fork. Unfortunately my tests are broken now (which used to work :( )

Wow! All test passed! What's going on here?

I couldn't test the swap option, the memory one works for me.
LGTM if someone can check the swap update.
re-ping @coolljt0725, @justincormack

sorry for late response,  missing some note from github _:)
This doesn't work for me, I need to unset the memory.memsw.limit_in_bytes before docker update -m -1 xxx.
[root@fedora docker]# docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
64e9cbd26239        busybox             "sh"                31 seconds ago      Up 30 seconds                           agitated_boyd
[root@fedora docker]# cd 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b/
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.limit_in_bytes
209715200
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.memsw.limit_in_bytes
419430400
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# docker update -m -1 64e9cbd26239
Error response from daemon: Cannot update container 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b: rpc error: code = 2 desc = failed to write -1 to memory.limit_in_bytes: write /sys/fs/cgroup/memory/docker/64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b/memory.limit_in_bytes: invalid argument
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# echo -1 > memory.memsw.limit_in_bytes
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# docker update -m -1 64e9cbd26239
64e9cbd26239
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# docker version
Client:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.6.3
 Git commit:   43922d0
 Built:        Tue Oct 18 08:46:30 2016
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.6.3
 Git commit:   43922d0
 Built:        Tue Oct 18 08:46:30 2016
 OS/Arch:      linux/amd64
 Experimental: true
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.memsw.limit_in_bytes
9223372036854771712
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.limit_in_bytes
9223372036854771712

Before unset the memory limit, we need to unset the --memory-swap first if the system has enable the memory swap limit because docker will set the memory swap limit to double the memory limit by default.
@mlaventure  maybe your system doesn't enable memory swap limit or am I missing something?

I'll write a test for that. It would be easier to test it that way.
On Tue, Oct 18, 2016, 11:08 AM Lei Jitang<EMAIL_ADDRESS>wrote:

sorry for late response, missing some note from github _:)
This doesn't work for me, I need to unset the memory.memsw.limit_in_bytes
before docker update -m -1 xxx.
[root@fedora docker]# docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
64e9cbd26239        busybox             "sh"                31 seconds ago      Up 30 seconds                           agitated_boyd
[root@fedora docker]# cd 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b/
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.limit_in_bytes
209715200
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.memsw.limit_in_bytes
419430400
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# docker update -m -1 64e9cbd26239
Error response from daemon: Cannot update container 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b: rpc error: code = 2 desc = failed to write -1 to memory.limit_in_bytes: write /sys/fs/cgroup/memory/docker/64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b/memory.limit_in_bytes: invalid argument
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# echo -1 > memory.memsw.limit_in_bytes
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# docker update -m -1 64e9cbd26239
64e9cbd26239
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# docker version
Client:
Version:      1.13.0-dev
API version:  1.25
Go version:   go1.6.3
Git commit:   43922d0
Built:        Tue Oct 18 08:46:30 2016
OS/Arch:      linux/amd64
Experimental: true
Server:
Version:      1.13.0-dev
API version:  1.25
Go version:   go1.6.3
Git commit:   43922d0
Built:        Tue Oct 18 08:46:30 2016
OS/Arch:      linux/amd64
Experimental: true
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.memsw.limit_in_bytes
9223372036854771712
[root@fedora 64e9cbd26239c17b669e3529f7f017370336d051b7cb6c2738cadc2cb724f64b]# cat memory.limit_in_bytes
9223372036854771712
Before unset the memory limit, we need to unset the --memory-swap first
if the system has enable the memory swap limit because docker will set the
memory swap limit to double the memory limit by default.
@mlaventure https://github.com/mlaventure maybe your system doesn't
enable memory swap limit or am I missing something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-254450329, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABoR-Kbvs7CuXOOMV2JiQdn5oUyXYiM_ks5q1IyagaJpZM4IZgNP
.

@coolljt0725 correct, memsw isn't enable on my system :)

@coolljt0725 Your test suggests to also update containerd to reset swap? or it's sufficient to do it here? I'm not sure containerd does this in the correct order

@coolljt0725 @mlaventure I found the issue, this commit in RunC solves the problem (with some tweaks on Docker side)
So the issue is RunC simply ignores swap changes when it's -1 I just check to see if memory is set to -1 and then silently set swap mem to -1 too. So it passes Kernel validation.
Now what is the process to commit these changes into RunC? Should I do a PR and relate it to this ticket?
RunC Changes: https://github.com/boynux/runc/commit/41afa949dacfb41d2375c4cfdb58251eed928b98

@boynux yes, you will need to open a PR in the runc repo (https://github.com/opencontainers/runc). Once merge, we then need to update containerd to use the new version, then vendor containerd here :sweat_smile:

Ok, cool. The I will submit a PR for RenC, once merged I'll update here.
Thanks
On Wed, Oct 19, 2016, 1:55 AM Kenfe-Mickaël Laventure <
<EMAIL_ADDRESS>wrote:

@boynux https://github.com/boynux yes, you will need to open a PR in
the runc repo (https://github.com/opencontainers/runc). Once merge, we
then need to update containerd to use the new version, then vendor
containerd here 😅
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/22578#issuecomment-254672680, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABoR-JIswO5fqXxqTyGJIGWQkMVmo0wKks5q1VyLgaJpZM4IZgNP
.

@hqhq Can you review RunC pull request please.

I'm going to close this for now, because we need the changes in RunC, but ping me when that is merged, then we can reopen


Disconnected at 7200 seconds

We are currently using vertica-python to connect from a windows machine to vertica (hosted on linux). We are consistently getting our long running queries disconnected at 7200 seconds. We see:
https://github.com/vertica/vertica-python/blob/74d426fae75b0fe221e65a1ed20eff6889970ce9/vertica_python/vertica/connection.py#L451
It looks like the keepalive is set...what could be causing this? 7200 I know is the keepalive time.
Is this also going to work for windows? Do we also need https://docs.python.org/3/library/socket.html#socket.socket.ioctl with SIO_KEEPALIVE_VALS for socket to remain open?

vertica-python provides connection_timeout as a connection parameter to control socket operations timeout (see README), queries can be affected by this. Please check if you have set connection_timeout first.

Close this issue because it has not had recent activity.


If I'm a user, I want to have a status message telling me that there is an issue with the Socrata API (or that the API has blank data) so that I'm not completely confused when the dashboard doesn't return permit data.

[ ] Ernie to give Sophia and flag a variable on if the APIs are returning anything other than 200 OR returning an empty set.
[ ] @phiden to check that global flag and then flash an error message over the entire dashboard.

Run the API to see if its even working.
If it is, pass 1.
If the county did a bad import, pass -1.
If Socrata is down, the HTTP result code. (404, 500, etc)

https://github.com/codeforamerica/mdc-feedback/pull/234


Messages show as being published yet do not appear in MQTT

Title is self-descripting. I am trying to publish messages to MQTT, it connects successfully and appears to publish successfully however nothing appears when subscribed to the MQTT topic.
I am fairly new to AWS IoT so I am guessing I am missing something simple. Could this be a permission issue, and if so how can I tell? Any advice would be helpful, thanks!

Turns out messages where just being sent too quickly... Seems to work fine with a delay.


rafthttp: fix wrong return in pipeline.handle

pipeline.handle is a long-living one, and should continue to receive
next message to send out when current message fails to send. So it
should continue instead of return here.
This bug is introduced at https://github.com/coreos/etcd/pull/3666
I met this when starting one slow follower.

LGTM.
A test case would be better though.

test added

merge it due to previous LGTM and low risk.

@yichengq I do not really understand the test. It is supposed to test that the pipeline can still accept new messages even if it encountered failures/errors previously. But your test description seems to be wrong. If it was wrong, can you please revert this commit?

@xiang90 You are right. will revert and resend.


Angularjs throws “Unexpected strict mode reserved word” which causes application to crash

I am currently developing an application for mobile phones using angularJS and cordova 3.2.
Some of my players report, that the application is not starting on their devices. This devices are listed below.

optimus p880 (Android Version 4.0.3)
Lifetab von Medion (Adroid Version 4.0.3)
Sony Ericsson Xperia mini pro ( Android 4.0.4)

So it seems somehow connected to that Android Version 4.0.3/4.
Not starting means, that the cordova application is starting, but that angularjs crashes before it is initiated, because all the elements where an ng-cloak class is attached (which in my case is set for the complete root window) remain hidden. So the user does not see anything.
The problem is, that I don't have any of this devices to test it, but one player did send me the logs of his device, saying
Uncaught SyntaxError: Unexpected strict mode reserved word

With the line number and the file name I could determine, that the problem is caused by the code below (its from the angular.js v1.2.16 file in line 3878). The problem seems to apply in the statement throw err;
(#3878)
function createInternalInjector(cache, factory) {

  function getService(serviceName) {
    if (cache.hasOwnProperty(serviceName)) {
      if (cache[serviceName] === INSTANTIATING) {
        throw $injectorMinErr('cdep', 'Circular dependency found: {0}', path.join(' <- '));
      }
      return cache[serviceName];
    } else {
      try {
        path.unshift(serviceName);
        cache[serviceName] = INSTANTIATING;
        return cache[serviceName] = factory(serviceName);
      } catch (err) {
        if (cache[serviceName] === INSTANTIATING) {
          delete cache[serviceName];
        }
        throw err; /*** THE ERROR APPLIES HERE! **/
      } finally {
        path.shift();
      }
    }
  }

I cannot really say, what happens here. The applications works fine on other devices and other android versions.
Has anyone of you an idea how I could fix that issue for the players?
(I duplicated this issue from StackOverflow. )

I am shooting darts in dark here, but can it be related to https://github.com/angular/angular.js/pull/7768 ?

Long time no activity. I assume it's resolved.


@types/lodash 4.14.74 isn't compatible with TypeScript 2.7.1, update to later version

Typedoc has dependency on @types/lodash and this version of lodash's .d.ts file doesn't meet all the constraints checked by the latest version of TypeScript 2.7.1.  This causes packages consuming typedoc doc package to fail builds if they try to update to TypeScript 2.7.1.  In other words packages using typedoc are blocked from getting the latest features of TypeScript and stuck on 2.6.x
See:
"@types/lodash": "4.14.74",
https://github.com/TypeStrong/typedoc/blob/master/package.json#L36
There are more details and example video here:
Referenced Issue: https://github.com/alexjoverm/typescript-library-starter/issues/172
There are many later version of @type/lodash available that likely have fixed this issue.  Since it's such a popular library I'm sure someone else ran into this.
I think fix would be to simply update the dependency of @types/lodash to a later version which has the fix tested against TS 2.7.1 then publish new 0.9.1 version of this package so consuming projects will be unblocked.

Either way, this should be fixed now with the v0.10.0 release. We can reopen if it is still a problem.

I'm also seeing this issue.  I've had to lock in to<EMAIL_ADDRESS>for typedoc to run.  Because of this, when I try and upgrade to version 0.10.0 of typedoc I get the following failure:
Using TypeScript 2.7.1 from /Users/landonpoch/source/csl/node_modules/typescript/lib Error: /Users/landonpoch/source/csl/node_modules/@types/lodash/index.d.ts(12650)  Type 'T' does not satisfy the constraint 'object'.
If I upgrade lodash to the latest then the project will compile but the docs won't generate:
Using TypeScript 2.7.1 from /Users/landonpoch/source/csl/node_modules/typescript/lib /Users/landonpoch/source/csl/node_modules/typedoc/dist/lib/models/types/array.js:37         var elementTypeStr = this.elementType.toString(); TypeError: Cannot read property 'toString' of undefined
This means I can't upgrade to TS 1.7 in my project yet if I want to keep using typedoc.

@landonpoch alexjoverm/typescript-library-starter#172 seems to indicate that their errors were fixed with updating TypeDoc and doing a fresh install. Have you tried clearing your node_modules directory and reinstalling?

@aciccarello - I have indeed done a rm -rf node_modules after an upgrade to 0.10.0 in package.json.  Still seeing issues with typedoc and lodash types.

@landonpoch Okay. Do you have a repo where I can reproduce the issue?

@aciccarello - I have tried creating a simple project that can reproduce the issue and I haven't been successful yet.  This may actually be a different issue as I'm only seeing it in one of the repositories that we are using typedoc with.  I'm going to try to do some more digging but I agree that this shouldn't be opened until I can find good reproducible steps for you.

@aciccarello - Steps to reproduce:

Use the latest for typedoc, typescript, lodash and @types/lodash
Make sure your tsconfig.json has "strictNullChecks": false
Run typedoc with --includeDeclarations flag

That should do it.  I did some digging by trying to debug typedoc but I'm not all that familiar with the code.  However, from what I could see there was an issue getting the type parameter name for the lodash zip function.  This is what was causing the this.elementType reference to be undefined in the ArrayType class.  No idea why strictNullChecks triggers the issue, but that's what was causing it.

Closed via #692

I'm still seeing this issue.  Here's the relevant portion of my tree in the repro project that I have:
<EMAIL_ADDRESS>/Users/landonpoch/test/repro
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>/Users/landonpoch/test/repro
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└──<EMAIL_ADDRESS>Does typedoc need to be using the latest lodash types for this to work?  Maybe I just have a wrong version of one of those packages listed above?  Please let me know.  Again, I only see the issue if I haven't enabled strict null checks.

I noticed there was also a version bump of typedoc.  So I updated that:
<EMAIL_ADDRESS>/Users/landonpoch/test/repro2
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Looks like it's still failing.
`
Using TypeScript 2.7.2 from
.../repro2/node_modules/typedoc/node_modules/typescript/lib
.../repro2/node_modules/typedoc/dist/lib/models/types/array.js:37
var elementTypeStr = this.elementType.toString();
`

On my environment I installed<EMAIL_ADDRESS><EMAIL_ADDRESS>and I've got this same issue too.
The error:
var elementTypeStr = this.elementType.toString();
                                              ^
TypeError: Cannot read property 'toString' of undefined
at ArrayType.toString (...\node_modules\typedoc\dist\lib\models\types\array.js:37:47)

when I'm trying to recompile my documentation with using  includeDeclarations: true option.
I was trying restore my node_modules and I was trying to install the latest version of lodash and all of ways are without success.
 I believe that should fix it. Typedoc bundles its own version of typescript so the version you installed does not affect it.

@aciccarello thanks a lot for this tip! I didn't know that the<EMAIL_ADDRESS>has been released ! So now I can recompiling my documentation with using includeDeclarations: true option. Now I have to check if it's making my documentation proper but it is not your problem now :) So about inserted the typescript version into typedoc bundle - it was very smart solution ! Thanks a lot once again !


kdb: 3.1.0 -> 3.2.0

Motivation for this change
Bumping along with others...
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Whoops, dupe: #59552


Keybind command+ä / command+ö not working

In other programs I use command+ö for previous tab and command+ä for next tab.
That keybind does not work with this plugin.
I've tried ctrl/alt/option/⌘ . None of them work with +ö / +ä.
If I use "normal" keys (I tried to find shortcuts that were not used)
Previous tab: command+.  (dot)
Next tab: command+y
it works..
If I use command ö (remove the +) it works if I press command, wait, then ö. I don't want this though
fyi: I use a Swedish keyboard layout.

Got it, Mousetrap supports this, but we need to add custom mapping for umlauts. Would you be able to provide me with the key and keycode on your keyboard layout?