ESM files deployed to NPM package contain import references to CommonJS sibbling JS files (missing .module suffix))

<EMAIL_ADDRESS>import { snapshot, subscribe, getVersion } from './vanilla';
export * from './vanilla';

...should point to<EMAIL_ADDRESS>...but instead point to<EMAIL_ADDRESS>Same issue with<EMAIL_ADDRESS>import { subscribe, snapshot, proxy } from './vanilla';

FYI, to work around this problem, I use @rollup/plugin-replace in my build process with the following configuration:
{
  include: /.+valtio.+/,
  delimiters: ['', ''],
  "'./vanilla'": "'./vanilla.module'"
}

Ah, actually, when I use Preact WMR's development server, vanilla.module.js imported by index.module.js (via import ... from 'valtio') is not equal to the one imported by utils.module.js (via import ... from 'valtio/utils'), causing the proxy to be corrupted!
So my final fix is in fact to replace import ... from ''./vanilla' to import ... from ''valtio/vanilla' in both index.module.js and utils.module.js. Thanks to the package.json exports, this works fine.

Thanks for reporting.
This is causing by #112. So, unpkg follows "module" in package.json but not "exports"...
I somehow thought *.module.js is better (maybe because of types, but we are now copying them), but probably esm/*.js would solve it.

Thank you for your prompt reply. I look forward to testing the fix, once merged and published.
I am hitting an interesting Preact WMR "bug" (maybe a "feature", I'm not sure), where the export map is correctly used by the Rollup-based production build system, but at development time some module caching seems to be involved which results in breaking the proxy functionality:
This happens when I import devtools() from valtio/util, which in turn invokes subscribe() from ./vanilla:
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/utils.ts#L64
=>
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/vanilla.ts#L188-L192
...and when I import proxy() from valtio (but crucially: transitively via ./vanilla)
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/index.ts#L1
=>
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/vanilla.ts#L40
Because of how Preact WMR loads modules, it seems the two ./vanilla are not the same modules in memory. Consequently, the LISTENERS Symbol prop is somehow undefined:
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/vanilla.ts#L103-L105
subscribe() would normally reveal that proxyObject[LISTENERS] is falsy instead of a Set():
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/vanilla.ts#L193-L199
...but Preact WMR removes process.env.NODE_ENV in its preprocessing phase, so I discovered this bug further down the call chain, when this line of code crashed:
https://github.com/pmndrs/valtio/blob/8e625551783f2e6364670faf59411fe2b926793d/src/vanilla.ts#L213
So, my workaround is to replace ./vanilla imports in Valtio's node_modules dist (./index and ./utils) with valtio/vanilla. This totally fixes the bug, I assume because Preact WMR's development server module cache indexer takes into account the export map correctly with valtio/vanilla symbolic references, resolving to a common ./vanilla module.
I reported a similar issue with Twind (which has since been fixed), but I think the situation was slightly different because each "sub package" is declared in the top-level export map AND has its own package.json (subfolder). See:
<EMAIL_ADDRESS>e.g.:
<EMAIL_ADDRESS>I will post an issue in Preact WMR's tracker once I have a repro pattern, but in the meantime I am going to CC the main developers, just in case they have an idea: @marvinhagemeister @developit and @JoviDeCroock

So, my workaround is to replace ./vanilla imports in Valtio's node_modules dist (./index and ./utils) with valtio/vanilla.

This actually makes sense, but then it doesn't solve the original unpkg issue, does it? maybe it does. I wish we had a way to check it without publishing it.

I think relative import references are a big no-no from one "sub package" to another (hypothetical example: ../vanilla/index.mjs from ./esm/utils/index.mjs), WHEN each "sub package" actually defines its own package.json in its own subfolder (e.g. valtio/core, valtio/vanilla, valtio/utils, valtio/react export map + consistent physical and logical organisation of "sub packages").
However valtio currently only defines an export map, without individual "sub packages". Perhaps this is the missing piece for better integration in the various modern systems like Preact WMR, SnowPack/SkyPack, Vite, etc.?
I'm not sure, but I should be able to try out the theory by hacking node_modules/valtio directly in my Preact WMR project (i.e. I can add package.json for each "sub package", try different export maps, and tweak Valtio's ESM import statements). I don't have the bandwidth to experiment right now, but I will get to it :)

it doesn't solve the original unpkg issue

I'm not sure what you mean by that. I provided Unpkg links in my comments purely to display the raw contents of Valtio dist files, just as they appear in local node_modules. Unpkg just mirrors the NPM registry, unlike SkyPack etc. which are CDNs that feature "smart" ESM support and transparent multi-package bundling.

I'm not sure what you mean by that.

Oops, I was confused with something. So, the original issue and the behavior with Preact WMR are different things.
The original issue should be resolved by #139.
The behavior you mentioned about Preact WMR sounds conflicting with #112 / #110.
(but, it's not certain if #112 really fixed #110.)
We may need some help on this.
Let me merge #139 as it should be a good fix.

yes I agree with your analysis.
one step at a time :)
👍

I can confirm that strictly-speaking, the fix works, thank you :)
However, the module caching problem persists with Preact WMR (as expected), and I wonder whether this affects other "modern" build systems as well.
So, I continue to patch Valtio via my package.json postinstall script, replacing relative import references to absolute ones, as per Valtio's export map (e.g. ./vanilla to valtio/vanilla).
Otherwise, this:

@danielweck You are absolutely right. #112 was a wrong fix. It didn't fix #110.
I don't know how to fix #110, but let me revert #112.


Refactor chapter 11 - Advanced Risk Minimization

Tidied up and converted code from arbitrary plotting libraries to ggplot2, along with updating the script to adapt to the changes of new images and their locations.
The scope of changes: Chapter 11: Advanced Risk Minimization

[x] Chapter 11.01: Risk Minimizers
[x] Chapter 11.02: Pseudo-Residuals
[x] Chapter 11.03: L2 Loss
[x] Chapter 11.04: L1 Loss
[x] Chapter 11.05: Advanced Regression Losses
[x] Chapter 11.06: 0-1 Loss
[x] Chapter 11.07: Bernoulli Loss
[x] Chapter 11.08: Brier Score
[x] Chapter 11.09: Advanced Classification Losses
[x] Chapter 11.10: Maximum Likelihood Estimation vs Empirical Risk Minimization I
[x] Chapter 11.11: Maximum Likelihood Estimation vs Empirical Risk Minimization II

 Migrate R code to mlr3 and ggplot; update nomenclature

 Migrate R code and tidy up for chapter 11: Advanced Risk Minimizer


The HashiCorp Vault Secret resolution only returns a Secret or Null

As a developer, it's easy to get stuck here because if the access token to the Vault lacks permissions or is incorrect, it either returns a Secret or nothing.
https://github.com/eclipse-edc/Connector/blob/258a31190a9c837606c2e327fe4dd5e54f3f1921/extensions/common/vault/vault-hashicorp/src/main/java/org/eclipse/edc/vault/hashicorp/HashicorpVault.java#L42
In the case of a 403 error, it would also be helpful to pass along this message so that you can handle the respective errors afterward.
What are your thoughts on this?

The vault implementation should send a message to the Monitor indicating the type of problem but continue to return null or the value.

I will provide a PR for this. @ndr-brt

I will provide a PR for this. @ndr-brt


Count total requests and errors for http endpoints

Hi!
I really dig the sample nozzle, thank you so much! Saved me a ton of time to start pumping data into StatsD. I felt like i was working just a bit too hard to paint a simple dashboard and added two basic metrics for all http endpoints. Total requests and errors. Is this something you would be interested in having in the sample?

Has bug, counts everything twice!


bugfix: it will cause memory overflow when client reconnect frequently.

Ⅰ. Describe what this PR did

remove channel from identified channels map if expired;
optimize ChannelManager class code style.

Ⅱ. Does this pull request fix one issue?
fix https://github.com/seata/seata/issues/2531

Codecov Report

Merging #2439 into develop will decrease coverage by 0.08%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop    #2439      +/-   ##
=============================================
- Coverage      51.74%   51.66%   -0.09%
+ Complexity      2667     2666       -1
=============================================
  Files            518      518
  Lines          16805    16831      +26
  Branches        2031     2035       +4
=============================================
- Hits            8696     8695       -1
- Misses          7293     7320      +27
  Partials         816      816

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/io/seata/core/rpc/ChannelManager.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...re/src/main/java/io/seata/core/rpc/RpcContext.java
43.24% <0%> (-1.21%)
21 <0> (ø)

...very/registry/zk/ZookeeperRegisterServiceImpl.java
60.93% <0%> (-0.79%)
25% <0%> (ø)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 5 committers have signed the CLA.:white_check_mark: xingfudeshi:x: l81893521:x: zjinlei:x: objcoding:x: jsbxyyxYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 5 committers have signed the CLA.:white_check_mark: xingfudeshi:x: zjinlei:x: objcoding:x: jsbxyyx:x: l81893521You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #2439 (eed08a5) into develop (1811109) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop    #2439      +/-   ##
=============================================
- Coverage      50.81%   50.74%   -0.07%
+ Complexity      2813     2812       -1
=============================================
  Files            558      558
  Lines          17927    17949      +22
  Branches        2124     2126       +2
=============================================
- Hits            9110     9109       -1
- Misses          7952     7974      +22
- Partials         865      866       +1

Impacted Files
Coverage Δ

...rc/main/java/io/seata/core/rpc/ChannelManager.java
0.00% <0.00%> (ø)

...re/src/main/java/io/seata/core/rpc/RpcContext.java
39.47% <0.00%> (-1.07%)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
54.63% <0.00%> (-0.52%)
:arrow_down:


Initial WebRTC support

This PR is the result of the joint effort of me and @brandonmakin during last GSoC.
Sadly, due to build issues and size, non-HTML5 support (on which @brandonmakin worked hard last summer) will be delegated to a GDNative plugin (and which will soon be available here https://github.com/godotengine/webrtc-native/ ).
This PR do not yet include the high level multiplayer peer (which might be added to this PR in a future commit as soon as we stabilize it a bit).
This will, of course, all come in 3.2.

up to you, @akien-mga

Looks good to me, but @karroffel might want to check the GDNative changes and @eska014 have a look at the JS integration.

There's one little change I need to push (will do later today), to allow compiling with module_gdnative_enabled=no. Plus I have to remove the google demo stun server leftover from JS :-/

@eska014 have a look at: https://github.com/godotengine/godot/pull/26792/files#diff-8cd4b6695db965b42410d87a3c6069d9 , maybe we can reuse it for XMLHTTPRequests too? I saw you had something similar using an array.

Thanks!


Continuous Scan

Hi all,
The library is working very well but I got one problem.
If the user scans a certain QR-Code the barcodeResult-method starts a new activity. But if the QR-Code does not contain the right informations, the app should keep scanning.
If I scan a random QR-Code and then move on to a QR-Code that contains the Information the App needs, nothing happens. So the app somehow stopps scanning. Even when I use barcodeView.decodeContinuous(callback) in my onCreate-method.
What would be a good approach for that?
Thanks.

I can't figure it out, maybe I'm too stupid for that

Sorry for the late reply.
decodeContinuous should continue scanning, as in this example: https://github.com/journeyapps/zxing-android-embedded/blob/master/sample/src/main/java/example/zxing/ContinuousCaptureActivity.java
Alternatively, if the barcode is not what you want, just call decodeSingle(callback) again.

Thanks, I just mady a silly mistake and got confused...


Fix button appearance in Firefox

Fix diagonal button borders not being antialiased in Firefox on OS X using a hack with transform: scale (Bugzilla link)
Fix off-by-pixel button height in Firefox by hardcoding line-height.

:+1:


Fix #2171 deployments should be part of the index automatically (back…

…ward compatibility)

can i haz tests?

LGTM!


[New Port Request] OpenCppCoverage (tool)

Name: OpenCppCoverage
Description: OpenCppCoverage is an open-source code coverage tool for C++ under Windows.
Source repository URL: https://github.com/OpenCppCoverage/OpenCppCoverage

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Improve MKL FFTW detection

MKL provides a full FFTW interface; this PR makes sure it can be used.

Codecov Report

Merging #36 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #36   +/-   ##
=======================================
  Coverage   94.86%   94.86%
=======================================
  Files          40       40
  Lines        3580     3580
=======================================
  Hits         3396     3396
  Misses        184      184

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 598cf2b...e220915. Read the comment docs.


Relax requirement on telemetry library

I noticed that these telemetry version restrictions are probably more strict than they should be, because telemetry 1.1.0 has been released, and it's showing as not possible to upgrade because of these version specs limiting it to 1.0.*.
I didn't make updates in the Rebar configs because I'm not familiar with how that works. I just updated the Mix configs.

Looks like all the rebar ones are already ~> 1.0?

FYI I don't have merge permissions, in case you were waiting on me to press the button. 😅


Update electric_storage.jl and doc strings

Update default degradation parameters per updated parameters.
Also update several doc strings for input descriptions.

I piggy backed on this PR to include a very minor update to the wind doc string https://github.com/NREL/REopt.jl/pull/106/commits/3acc26a6ce0e1578c484801e14ee464ac132f9cd

@rathod-b Looks good, thanks for these updates: A few comments beyond the in-line ones:

The docs for the degradation model still need to be updated; there are TODOs in the code but we might want that as an open issue just so we don't forget it.
It would be good to make a more robust collection of tests.  We can use the new file  degradation_tests.json for this since it's not currently used.  We should include a test case for replacement (which we already have, but please add an assertion for the number of replacements or a new degradation-specific measure) and a test case for augmentation (which we don't have yet).

Let me know if you want help with any of these. Thanks! Alex

Hi Alex, thanks for your comments on the PR! Its been a while and I am picking this back up. I have removed the many TODOs from the code documentation which were initially added as reminders for me. If you see any more of them, do let me know.
I have also updated the replacement strategy testset to validate some degradation specific parameters to ensure the results make sense and DVs arent switching between 0 and 1 as they were when we were testing this back in Fall 2022. Let me know if there are any comments on that.
Lastly, I have an open question for you. At present, we add the SOC incentive to the objective function in run_reopt.jl without any consideration for BESS degradation. I was wondering if we wanted to handle that programmatically, or handle it via a warning to a user and have then set the add_soc_incentive to false when running degradation?

@rathod-b Looks good, thanks for these updates: A few comments beyond the in-line ones:

The docs for the degradation model still need to be updated; there are TODOs in the code but we might want that as an open issue just so we don't forget it.
It would be good to make a more robust collection of tests.  We can use the new file  degradation_tests.json for this since it's not currently used.  We should include a test case for replacement (which we already have, but please add an assertion for the number of replacements or a new degradation-specific measure) and a test case for augmentation (which we don't have yet).

Let me know if you want help with any of these. Thanks! Alex

Hi Alex, thanks for your comments on the PR! Its been a while and I am picking this back up. I have removed the many TODOs from the code documentation which were initially added as reminders for me. If you see any more of them, do let me know.
I have also updated the replacement strategy testset to validate some degradation specific parameters to ensure the results make sense and DVs arent switching between 0 and 1 as they were when we were testing this back in Fall 2022. Let me know if there are any comments on that.
Lastly, I have an open question for you. At present, we add the SOC incentive to the objective function in run_reopt.jl without any consideration for BESS degradation. I was wondering if we wanted to handle that programmatically, or handle it via a warning to a user and have then set the add_soc_incentive to false when running degradation?

I could also use some help in fixing the rendering of a formula in documentation. Line 145 in electric_storage.jl has the broken formula for residual value.

@rathod-b Looks good, thanks for these updates: A few comments beyond the in-line ones:

The docs for the degradation model still need to be updated; there are TODOs in the code but we might want that as an open issue just so we don't forget it.
It would be good to make a more robust collection of tests.  We can use the new file  degradation_tests.json for this since it's not currently used.  We should include a test case for replacement (which we already have, but please add an assertion for the number of replacements or a new degradation-specific measure) and a test case for augmentation (which we don't have yet).

Let me know if you want help with any of these. Thanks! Alex

Hi Alex, thanks for your comments on the PR! Its been a while and I am picking this back up. I have removed the many TODOs from the code documentation which were initially added as reminders for me. If you see any more of them, do let me know.
I have also updated the replacement strategy testset to validate some degradation specific parameters to ensure the results make sense and DVs arent switching between 0 and 1 as they were when we were testing this back in Fall 2022. Let me know if there are any comments on that.
Lastly, I have an open question for you. At present, we add the SOC incentive to the objective function in run_reopt.jl without any consideration for BESS degradation. I was wondering if we wanted to handle that programmatically, or handle it via a warning to a user and have then set the add_soc_incentive to false when running degradation?

I could also use some help in fixing the rendering of a formula in documentation. Line 145 in electric_storage.jl has the broken formula for residual value.

Lastly, I have an open question for you. At present, we add the SOC incentive to the objective function in run_reopt.jl without any consideration for BESS degradation. I was wondering if we wanted to handle that programmatically, or handle it via a warning to a user and have then set the add_soc_incentive to false when running degradation?

A warning should be fine here - these different objectives can be handled by the solver.

Relevant changes from this PR were merged into develop via #443. This PR is being closed.


test(sdk): attestation integration test.

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

Project coverage is 89.25%. Comparing base (8301f23) to head (f86a7c6).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #746      +/-   ##
==========================================
- Coverage   89.54%   89.25%   -0.30%
==========================================
  Files         104      104
  Lines        4411     4422      +11
==========================================
- Hits         3950     3947       -3
- Misses        299      312      +13
- Partials      162      163       +1

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


Add a way to disable logscale

Please add a way to influence graph generation. The timing information is displayed in log scale, which is inappropriate for my data

Thanks for the suggestion.
In fact, I think I might just remove the log-scaling entirely. That's what caused your earlier issue. I'm not sure the use-cases for it are sufficiently compelling to make it worth the maintenance effort at this point.
As I'm sure you've guessed, the plot generation hasn't received a lot of attention yet. So far, you seem to be the only person using the plot generation in any meaningful way. Would you mind adding your input on that to #107?


Add replication role detection from runtime Redis information

Make the role aware of the runtime-assigned replication roles of existing Redis instances to avoid forcing role changes to instances (which might cause downtime).
Do it by sourcing data from the INFO Redis command through a fact script, then using that information to determine whether an already running instance is a master or a slave. Then, if the option is enabled, ignore the manually assigned role in favor of the detected role. That fact script can also possibly replace the existing redis one, which is really not that useful, since a) you likely already have the data it contains from the inventory b) it doesn't support/can't distinguish more than once instance.
Hopefully is enough to fix #22 without requiring any weird configuration generation.
Tests are pending - I'm posting this for some feedback before going further.

@DavidWittman I did some work to try and solve the problems that #25 couldn't, by attempting to merge rewritten configuration with our managed config at daemon startup time, with some other assorted fixes. Please check it out if you can.

I fixed systemd quoting issues (as #30) by rebasing some commits.

It seems Ansible 1.9 doesn't support the systemd module :(


DocumentDB: Select query failed when cross partition

When I use DocumentDbRepository.findAll() method to select all entities, exception occurs:
{"message":"Cross partition query is required but disabled. Please set x-ms-documentdb-query-enablecrosspartition to true, specify x-ms-documentdb-partitionkey, or revise your query to avoid this exception."}
As docs says, the CosmosDB saves data and index them with partition keys. And when running query, the REST API requires specific the partition key or enable crosspartitionkey flag. But in the lib, it set the options to null, make the call failed.
In my thought, there should be two methods:

findAll() to enable setEnableCrossPartitionQuery(true)
Another method to select entities with specific partition key.

If the collection doesn't set a partition key, the CRD operation can work properly, But once the partition key specified, all the CRD request required partition key.


Add breadcrumbList to home, libraries

#143

How about this? :)

I just place it to / and /libraries/.
It's not available in like the page /libraries/XXXX or others now,
because I don't have good idea where to place the breadcrumbList.

Any suggestion? :)

@qas612820704 sorry for the late review, would you mind to fix the conflicts first? Thanks.

I rebased it to latest master branch.
Is conflict resolved?

Looks so! @qas612820704 for library, I think you can just put it above the library name.
We also need to add it to about & api page :)

library page

api page

about page

@PeterDaveHello,
While I adding features,
I saw that templates/api.html indents  by tab unlike other pages use space.
Should I fix this? (Replace tabs to spaces)

@qas612820704 Nice catch! Feel free to send another PR to fix it, thanks!

OKey : )

@PeterDaveHello one more thing, mind to add this feature also on each library version?

Hi @qas612820704
Can we have more space between the breadcrumbList and the library name?

I also wonder if we can hide the "home" item or put it another space? (no idea yet)

What do you think?

@PeterDaveHello, conflict fixed!

Closing as duplicate.


[OFFICIAL/AEW] AEW WrestleDream 2024 LiVe StreamS Free On TV Channel 13 OCT 2024

It's time to watch AEW WrestleDream 2024 as this latest All Elite Wrestling PPV follows in the footsteps of last month's stellar duo of All In and All Out. Having won the AEW World Championship at All In and retained that prize at All Out, Bryan Danielson once again headlines a stacked card, this time as he defends his gold against former Blackpool Combat Club cohort Jon Moxley.
🔴🌍📺📱👉GO LIVE==►► CLICK HERE TO STREAMING
🔴🌍📺📱👉STREAMING==►► CLICK HERE TO WATCH LIVE
🔴🌍📺📱👉GO LIVE==►► CLICK HERE TO STREAMING
🔴🌍📺📱👉STREAMING==►► CLICK HERE TO WATCH LIVE
Make sure you know how to watch AEW WrestleDream 2024 from anywhere with PPV and a VPN if required.
AEW WrestleDream 2024 start time
Date: Saturday, October 12
Time: The main broadcast starts at 8 p.m. ET / 5 p.m. PT and Oct 13 at 1 a.m. BST / 11 a.m. AEDT. The Zero Hour pre-show begins on YouTube 90 minutes before the PPV start time.
Watch in the U.S.: PPV.com / YouTube / Triller TV
Elsewhere: DAZN / PPV.com
Watch anywhere — try NordVPN 100% risk free
While Danielson vs. Moxley is the headline attraction of AEW WrestleDream 2024, the full card has come together nicely with plenty of other great match-ups that could well steal the show when all is said and done at Washington's Tacoma Dome.
Given the history of AEW delivering big whenever the company is on Pay-Per-View, and in the aftermatch of the excellent All In and All Out, anticipation is extremely high for another great show with WrestleDream. Some of the build to the PPV may have been questionable, but the wrestling on offer, as always, is sure to be fantastic.
Ready for what should be one of the biggest AEW events of 2024? Below, there's every piece of information you need on how to watch AEW WrestleDream live streams from anywhere in the world.
How to watch AEW WrestleDream 2024 live streams from anywhere on Earth
Traveling abroad? Can't watch AEW WrestleDream live streams with your usual app or streamer? Good news: with a virtual private network, or VPN, you can appear to be surfing the web from your hometown (or anywhere else), and access the streaming services of your choice.
The software allows your devices to appear to be back in your home country regardless of where in the world you are. So ideal for wrestling fans away on vacation or on business. Our favorite is NordVPN. It's the best on the market:
Image
Exclusive deal
There's a good reason you've heard of NordVPN. We specialize in testing and reviewing VPN services and NordVPN is the one we rate best. It's outstanding at unblocking streaming services, it's fast and it has top-level security features too. With over 5,000 servers, across 60 countries, and at a great price too, it's easy to recommend.
Get over 70% off NordVPN with this deal
How to watch AEW WrestleDream 2024 live streams in the U.S.
As with all AEW PPVs up to this point, All Out can be streamed via PPV.com, YouTube or TrillerTV (formerly known as FITE TV) for $50 USD.
Those apps can be found on Roku, Fire TV, Apple TV, and mobile devices, as well as on their website.
Love TV? Sign up to the weekly How To Watch newsletter
How to watch AEW WrestleDream 2024 live streams in the UK, Canada and beyond are cheaper
Wrestling fans in Canada, Australia, New Zealand, the U.K., and Ireland can tune in to AEW All Out on PPV.com.
TrillerTV and YouTube are also selling AEW WrestleDream 2024 live streams around the world in other territories. Prices vary. For example, it's $25 in South Africa, Australia, the U.K. and many other places.
If you're away from home use a VPN to access your usual streaming service from anywhere.
AEW WrestleDream 2024 card
AEW WrestleDream heads to Tacoma, Washington
(Image credit: AEW)
Zero Hour Pre-Show Tag Team Match: MxM Collection (Mansoor, Mason Madden) vs. The Acclaimed (Anthony Bowens, Max Caster)
Zero Hour Pre-Show Singles Match: Anna Jay vs. Harley Cameron
Zero Hour Pre-Show ROH TV Championship Match: Atlantis Jr. (c) vs. Brian Cage
ROH World Championship Match: Mark Briscoe (c) vs. Chris Jericho
Singles Match: Darby Allin vs. Brody King
2 Out Of 3 Falls Match: Hologram vs. The Beast Mortos
AEW TNT Championship Match: Jack Perry (c) vs. Katsuyori Shibata
Singles Match: Jay White vs. Adam Page
AEW Tag Team Championship Match: The Young Bucks (Matthew Jackson, Nicholas Jackson) vs. Private Party (Zay, Quen)
AEW International Championship Match: Will Ospreay (c) vs. Ricochet vs. Konosuke Takeshita
AEW Women's Championship Match: Mariah May (c) vs. Willow Nightingale
AEW World Championship Match: Bryan Danielson (c) vs. Jon Moxley
AEW WrestleDream 2024 preview
Having defeated Swerve Strickland to become AEW World Champion at All In this summer, Bryan Danielson defends that title in heated fashion at WrestleDream. After being attacked by now-former-friend Jon Moxley after Bryan's All Out win over Jack Perry, the American Dragon was suffocated with a plastic bag. While Danielson has revenge on his mind, the veteran's full-time in-ring career is on the line should he come up short against Mox.
In other WrestleDream title matches, Mariah May puts her AEW Women's Championship on the line against Willow Nightingale, with this set in motion following Nightingale winning a four-way bout on AEW Dynamite; Will Ospreay defends the AEW International Championship in a triple-threat match against the high-flying Ricochet and the ever-impressive Konosuke Takeshita; The Young Bucks face off against Private Party with the Jacksons' AEW Tag Team Championships up for grabs; fellow Elite man AEW TNT Champion Jack Perry does battle with the legendary Katsuyori Shibata; Chris Jericho has the chance to become a two-time ROH World Champion as he faces current champ, Mark Briscoe. Away from those title matches, AEW WrestleDream 2024 also offers up a trio of hotly anticipated singles matches; the erratic 'Hangman' Adam Page facing former Bullet Club buddy 'Switchblade' Jay White; long-time friends and long-time rivals Darby Allin and Brody King going to war once again; and the electric Hologram locking quite literal horns with The Beast Mortos on a 2 Out of 3 Falls Match.
Of course, one hot topic of conversation/speculation ahead of WrestleDream is what surprise names could potentially make an appearance. Some fans are fully expecting Shane McMahon to turn up at WrestleDream, while Bobby Lashley is another name on plenty of lips - particularly with Swerve Strickland, who's been courted by Bobby's BFF MVP lately, set for an in-ring segment at the PPV.
Where the WrestleDream Zero Hour is concerned, that pre-show currently has three matches confirmed for it, as MxM Collection takes on The Acclaimed, Anna Jay and Harley Cameron go one-on-one, and Atlantis Jr. defends his ROH TV Championship against the powerful Brian Cage.

Closed due to irrelevant content.


⚠ Samsung has degraded performance

In bad4266, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2476 ms

Resolved: Samsung performance has improved in d865f49.


Running project

How to run project?
I want to run it locally.
how to do it?

I will add documentation on this as soon as i can.

That's OK.
but if possible, tell me what to do for now!

Is it possible to launch with Docker? I wanna fix the #95 issue

I don't really use Docker for development of Matnbaz and the Docker files are old, I doubt if they are compatible with the current state of the project.
I'll try to add documentation on how to run the project locally soon, now that most of the features are implemented.

https://github.com/matnbaz/matnbaz/wiki/Running-locally


Introduce Issue Forms

Summary
In a effort to reduce the amount of issues by mistake or with insufficient information, we're introducing Issue forms (In beta on Github at the moment). With this now users need to fill a form to submit a issue.
This should reduce the amount of issues created without enough information.
Test period
First we need to test if the new form issues are going to work smoothly. If everything works fine, I will update the links inside the app to point to the new forms.

@idmarjr queres fazer merge disso aqui?


Extremely low UI refresh performance.

VSCode Version: 1.12.0
OS Version: MacOS Sierra 10.12.4
Resolution: 2560x1440 @ 60Hz . with the editor at full screen size.  When resized to ~half of the screen, the UI issue below does not occur.

Steps to Reproduce:

Open vsc with no open files or with many open files
Open integrated terminal
Resize integrated terminal and experience the unresponsive UI refresh.
Open a few files
Enable split editor and resize the different columns to experience the unresponsive UI refresh.

@yangwen2 Do you by any chance start code with --disable-gpu?

The issue occurs sans the --disable-gpu option.  I just tried it with disable gpu and there is tremendous frame dropping effect (flashing black frames) when resizing the panes.  However the lagginess does seem to go away in that mode.  The perceived smoother fps may be due to actual frame dropping going on.

@yangwen2 did this happen with 1.11? can you share a video how this looks for you?

Issue did not occur with 1.11
https://gfycat.com/ElderlyGreenDarklingbeetle

@yangwen2 can you open another of the panels (e.g. "Output"), then restart VS Code and then see if the same slow performance can be seen? I am trying to find out if this could be a regression from the integrated terminal or not.

It's still slow with the Output panel.  Dragging the boundary between the split editors also exhibit this UI issue.  However, it's not nearly as laggy as resizing the terminal
settings.json:
{     "window.zoomLevel": 0,     "typescript.check.tscVersion": false,     "editor.cursorStyle": "block",     "editor.cursorBlinking": "solid",     "vsicons.projectDetection.autoReload": true,     "git.confirmSync": false,     "workbench.colorCustomizations": {         "activityBar.foreground": "#c8cace",         "activityBarBadge.background": "#da291c",         "statusBar.background": "#2185C5",         "tab.activeBackground": "#385666",         "tab.inactiveForeground": "#D1D1D1",         "editor.selectionBackground": "#29404A",         "editorCursor.foreground": "#FFEE00",         "editor.lineHighlightBackground": "#37424A",         "contrastActiveBorder": "#FFEE00",         "editor.selectionBackground": "#393D66",         "input.foreground": "#fff",         "editorLineNumber.foreground": "#999",         "editor."     },     "workbench.colorTheme": "Atom One Dark",     "workbench.iconTheme": "vscode-icons",     "files.exclude": { 	"**/.git": true, 	"**/.DS_Store": true, 	"**/*.js.map": true, 	"**/*.js": {"when": "$(basename).ts"} }, "tslint.enable": true, "tslint.autoFixOnSave": true, "terminal.integrated.shellArgs.osx": ["-l"] }

@yangwen2 does it reproduce when all editors are closed?

With all editors closed, terminal, output panels no longer exhibit laggy UI when resizing, even whilst at full screen.

@yangwen2 ok good to know. I think what would help is to get a performance profile when you resize. This is possible from within VS Code by using the profiler tools:
To create a CPU profile using developer tools in VS Code:

select Help > Toggle Developer Tools
click on Profiles
click the start button
do whatever you need to do to get the CPU spin high
wait for some time (10-20 seconds should be enough)
stop the profiling
click the save button and attach the output file to this issue

VSC_Issue25924.txt

@yangwen2 thanks for the prompt reply!
@alexandrudima not sure if anything pops to your mind that could possibly make resizing slower between 1.11 and 1.12 when editors are open. To me this seems to be a duplicate of https://github.com/Microsoft/vscode/issues/16845 and not a 1.12 regression (e.g. Electron related).


Fix macro hygine issues

Description
This PR:

Adds #![no_implicit_prelude] in macro tests. This ensures that:

We don't use anything we are not supposed to use
Traits are called unambiguously

Adds #[automatically_derived] and #[doc(hidden)] where missing
Replace Span::call_site() with Span::mixed_site()

Fixes #1633
Checklist

[ ] I have run cargo make pr-flow
[ ] I have reviewed my own code
[ ] I have added tests

Not sure why mixed_site is needed on Token!s, but it can't hurt :)

I did a find and replace for call_site()), which should've covered most (if not all cases). It doesn't really matter though
I'm going to merge this. If it causes any problems, we can always revert it


[SPARK-15660][CORE] RDD and Dataset should show the consistent values for variance/stdev.

What changes were proposed in this pull request?
In Spark-11490, variance/stdev are redefined as the sample variance/stdev instead of population ones. This PR addresses the only remaining legacy in RDD. This may cause breaking changes, but we had better be consistent in Spark 2.0 if possible. This PR also popVariance and popStdev functions.
Before
scala> val ds = spark.createDataset(Seq(1.0, 2.0, 3.0))
ds: org.apache.spark.sql.Dataset[Double] = [value: double]

scala> ds.describe().show()
+-------+-----+
|summary|value|
+-------+-----+
|  count|    3|
|   mean|  2.0|
| stddev|  1.0|
|    min|  1.0|
|    max|  3.0|
+-------+-----+

scala> ds.rdd.stdev
res1: Double = 0.816496580927726

After
scala> ds.rdd.stdev
res0: Double = 1.0

How was this patch tested?
Pass the updated Jenkins tests.

Test build #59637 has started for PR 13403 at commit 3fe0cb6.

Test build #59637 has finished for PR 13403 at commit 3fe0cb6.

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

Merged build finished. Test PASSed.

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

hm I think we probably don't want to change the behavior of this to not surprise people ...

Thank you for review again @rxin.
Actually, I fully understand and expect your decision.
The reason why I making this issue is I think we need explicit discussions and the conclusion for this issue.
I worried that Spark shows this inconsistency forever implicitly. As we know, if we do not this in Spark 2.0, this will happen on Spark 3.0 or maybe never because of the same reason.

Hi, @rxin .
I updated the example more practically by using SparkSession.createDataset().rdd.stdev.
If we must preserve the current behavior for backward compatibility, what about adding notes somewhere about the inconsistency for new users?

Yeah I find this surprising too. As far as I know, databases tend to treat stddev as the sample stddev -- except Hive for some reason, AFAIK. I've never quite understood the theoretical motivation for that. Maybe the idea is that the aggregate is typically over some projection, or subset, of all data. But to me, the default should logically be population stdev, since there's no inherent reason to believe the result set is not the entire population of interest.
For RDDs, it seems even clearer that the behavior should be population stddev.
For Datasets, maybe it's less surprising to do what databases usually do.
It does bear documentation for sure, but maybe not changing the behavior.

Thank you for review, @srowen .

Rebased.

Test build #59793 has started for PR 13403 at commit 0715f08.

Test build #59793 has finished for PR 13403 at commit 0715f08.

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

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

Merged build finished. Test PASSed.

Test build #59979 has started for PR 13403 at commit ffff801.

Test build #59979 has finished for PR 13403 at commit ffff801.

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

Merged build finished. Test PASSed.

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

Test build #60026 has started for PR 13403 at commit ae5fb7a.

Test build #60026 has finished for PR 13403 at commit ae5fb7a.

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

Merged build finished. Test PASSed.

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

Test build #60195 has started for PR 13403 at commit f999c8c.

Test build #60195 has finished for PR 13403 at commit f999c8c.

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

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

Merged build finished. Test PASSed.

What about just adding an explicit note on old StatCounter.stdev?
http://spark.apache.org/docs/2.0.0-preview/api/scala/index.html#org.apache.spark.util.StatCounter
MLLIB stat.Statistics is also consistent with Dataset.
scala> import org.apache.spark.mllib.linalg.Vectors
scala> import org.apache.spark.mllib.stat.{MultivariateStatisticalSummary, Statistics}
scala> Statistics.colStats(sc.parallelize(Seq(Vectors.dense(1.0),Vectors.dense(2.0),Vectors.dense(3.0)))).variance
res10: org.apache.spark.mllib.linalg.Vector = [1.0]

Although we can not change old API, I think it's a good idea to add popVariance and popStdev clearly.
If everything in this PR is now allowed, what about just adding an explicit note on old StatCounter.variance and StatCounter.stdev?
http://spark.apache.org/docs/2.0.0-preview/api/scala/index.html#org.apache.spark.util.StatCounter

Test build #60496 has started for PR 13403 at commit a3baf4f.

Test build #60496 has finished for PR 13403 at commit a3baf4f.

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

Merged build finished. Test PASSed.

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

Test build #60715 has started for PR 13403 at commit e41561e.

Test build #60716 has started for PR 13403 at commit 602e236.

Hi, @rxin and @srowen .
Now, I update this PR like the following.

Update the documentation of legacy Scala/Java API more clearly
Add popVariance/popStdev functions explicitly

Could you give me some feedback?

Test build #60715 has finished for PR 13403 at commit e41561e.

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

Merged build finished. Test PASSed.

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

Test build #60716 has finished for PR 13403 at commit 602e236.

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

Merged build finished. Test PASSed.

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

Thank you so much for your review, @srowen !
I updated the PR according to your comments.

Test build #60771 has started for PR 13403 at commit 15938b3.

Test build #60771 has finished for PR 13403 at commit 15938b3.

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

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

Merged build finished. Test PASSed.

CC @mengxr @jkbradley I'd kinda like to have this for 2.0.0 for completeness.

Ping~

Test build #60938 has started for PR 13403 at commit 4f0fc8a.

Thank you, @srowen .
I updated the PR according to one of your advices.
For the other advice, I tried like the following. It looks good, but a little bit inconsistent with the remaining parts of the codes.
   /** Compute the population variance of this RDD's elements. */
-  def variance(): Double = self.withScope {
-    stats().variance
-  }
+  def variance(): Double = popVariance

   /** Compute the population standard deviation of this RDD's elements. */
-  def stdev(): Double = self.withScope {
-    stats().stdev
-  }
+  def stdev(): Double = popStdev

It's because the functions of DoubleRDDFunctions.scala and JavaDoubleRDD.scala simply forwards to their correspondents. May I keep the corrent logic for this?

OK, I suppose it's either down the over, or over then down in the API. Either way is consistent with something.

Test build #60946 has started for PR 13403 at commit aeb4888.

@dongjoon-hyun @srowen I made a comment just before @dongjoon-hyun updated the PR:
I think it should be approximate equality but with a very small tolerance, e.g. 1e-14. Both calls trigger reduce jobs and we don't have guarantees on the ordering or reduce operations, which might lead to small numerical errors. Maybe it doesn't apply to the test case here, but it is still a best practice to not test strict equality of floating-point numbers.

Hi, @srowen .
Now, I fixed them all. Sorry for missing those.

Oh, thank you, @mengxr !
I'll update again.

Thank you for reviewing this PR, @mengxr and @srowen !

Test build #60948 has started for PR 13403 at commit cb10b9c.

Hi, @mengxr .
I updated them to use accurate values and small tolerances, too.
-    assert(abs(2.0 - rdd.sampleVariance) < 0.01)
-    assert(abs(1.41 - rdd.sampleStdev) < 0.01)
+    assert(abs(2.0 - rdd.sampleVariance) < 1e-14)
+    assert(abs(Math.sqrt(2.0) - rdd.sampleStdev) < 1e-14)

Test build #60950 has started for PR 13403 at commit 3a6396e.

Test build #60946 has finished for PR 13403 at commit aeb4888.

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

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

Merged build finished. Test PASSed.

Test build #60938 has finished for PR 13403 at commit 4f0fc8a.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #60948 has finished for PR 13403 at commit cb10b9c.

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

Merged build finished. Test PASSed.

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

Test build #60950 has finished for PR 13403 at commit 3a6396e.

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

Merged build finished. Test PASSed.

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

Thank you, @srowen .

Test build #61018 has started for PR 13403 at commit a98633b.

Test build #61018 has finished for PR 13403 at commit a98633b.

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

Merged build finished. Test PASSed.

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

Test build #61106 has started for PR 13403 at commit bb12a7f.

Test build #61106 has finished for PR 13403 at commit bb12a7f.

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

Merged build finished. Test PASSed.

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

Merged to master

Thank you for everything, @srowen , @mengxr , @rxin .


[local-volume] Added more information about storageClassName for local-volumes

I slightly modified the text in the top level README.md to make it more clear about how to use the storage class name with local-volumes.
I updated the bootstrapper README.md to make it more explicit about the storageClassName that will be set for a local-pv that is discovered by providing an example.

/assign @msau42

@msau42 - I moved the example up to the top-level README, and I utilized actual local PV.
Please let me know if you suggest any further changes.

@msau42 - I update this PR to address your comments.

/lgtm
Thanks!

/assign @wongma7 - PTAL

/lgtm
/area local-volume


gcompress,gcfg,gparse,gjson,gredis模块测试用例编写

Codecov Report

Merging #178 into master will increase coverage by 2.06%.
The diff coverage is 90.65%.

@@            Coverage Diff             @@
##           master     #178      +/-   ##
==========================================
+ Coverage   62.07%   64.14%   +2.06%
==========================================
  Files         195      195
  Lines       16843    16849       +6
==========================================
+ Hits        10455    10807     +352
+ Misses       5678     5361     -317
+ Partials      710      681      -29

Impacted Files
Coverage Δ

g/encoding/gjson/gjson.go
88.62% <88.23%> (+16.16%)
:arrow_up:

g/encoding/gjson/gjson_api_new_load.go
92.45% <92%> (+11.68%)
:arrow_up:

g/os/gcfg/gcfg.go
92.27% <92.2%> (+45.17%)
:arrow_up:

g/os/gcache/gcache_mem_cache_lru.go
80.95% <0%> (-7.15%)
:arrow_down:

g/os/gspath/gspath_cache.go
84.78% <0%> (-4.35%)
:arrow_down:

g/container/gtree/gtree_redblacktree.go
59.14% <0%> (-1.43%)
:arrow_down:

g/container/gtree/gtree_avltree.go
56.2% <0%> (-1.27%)
:arrow_down:

g/container/garray/garray_normal_int.go
69.88% <0%> (-1.17%)
:arrow_down:

g/database/gredis/gredis_config.go
100% <0%> (+18.18%)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 55f5e6d...d305d25. Read the comment docs.


Link to ES6 object does not work

Following code do this. You can add car to the list of cars. You can change manufacturer name. When I have defined items in state as ES6 classes then I cannot change the manufacturer name. With literal objects everything works fine. Is this bug or I do something wrong?
import React from 'react';
import ReactDOM from 'react-dom';
import Link from 'valuelink';
import { Input } from 'valuelink/tags';

class CarModel {
    constructor() {
        this.manufacturer = 'default';
    }
}

class Car extends React.Component {
    render() {
        let carLink = this.props.carLink;
        let val = carLink.value.manufacturer;
        return (

<Input type="text" valueLink={ carLink.at('manufacturer') } /> { val }

        )
    }
}

class CarList extends React.Component {
    constructor(props) {
        super(props);

        this.state = {
            cars: []
        };
    }

    handleAdd() {
        let cars = this.state.cars;
        cars.push(new CarModel());

        this.setState({ cars })
    }

    render() {
        let cars = Link.state(this, 'cars').map((car, i) => (
            <Car key={ i } carLink={ car } />
        ));

        return (

{ cars }

                <button onClick={ this.handleAdd.bind(this) }>Add Car</button>

        )
    }
}

ReactDOM.render(
    <CarList />,
    document.getElementById('root')
);

Is this bug or I do something wrong?

It's the feature. When carLink.at('manufacturer') is updated, it assumes that carLink is the plain object or array because it needs to know how to properly clone it. That's how nested link update is done: it creates the copies of the parent chain so that setState or other state management libraries could detect that direct state member is changed using the shallow comparison.
Therefore, no classes as state members are supported. As this is not the way to go in a large application, we're at Verizon/Volicon are not using NestedLink alone, but as a part of NestedReact. Which replaces React's state with observable and serializable classes. https://github.com/Volicon/NestedReact
Here is an example. In order to get ES6 classes syntax you need to use "rc" version. It will be released soon.
https://github.com/Volicon/NestedReact/tree/develop/examples/checklistTree

As an alternative, it is possible to create the fork of NestedLink to support immutable classes.
The easiest way to go is to add your own "helper". Put it in the default option to the switch. Here:
https://github.com/Volicon/NestedLink/blob/master/valuelink.ts#L298
Helper is a combination of clone, map, and remove functions. That's what NestedLink must know how to do for your classes in order to operate properly. clone is essential. Others are needed only if you want to use corresponding operations in your classes.
I would just forward these operations to the object in your helper, and created the base class with such an operation. Generic "clone" operation can be implemented in the base class like this:
clone(){
    const copy = new this.constructor();
    Object.assign( copy, this );
}

ok. Thank you.


cargo build fails on Rust 1.79.0

error: lint `or_patterns_back_compat` has been renamed to `rust_2021_incompatible_or_patterns`
  --> src/lib.rs:24:2
   |
24 |     or_patterns_back_compat,
   |     ^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `rust_2021_incompatible_or_patterns`
   |
note: the lint level is defined here
  --> src/lib.rs:7:2
   |
7  |     warnings
   |     ^^^^^^^^
   = note: `#[deny(renamed_and_removed_lints)]` implied by `#[deny(warnings)]`

error: could not compile `captur` (lib) due to 1 previous error

Thanks for the report!
I have some strict linting on this project that really needs to be updated. This should be an easy fix to warn during build, and only error out in CI.

Alright, this is fixed as part of #6 , but I have some other cleanup that I want to do before pushing out a new release. I'll close this issue once the new release is published.
Thanks again for the report!

Awesome, thanks for the quick response!

https://github.com/MitMaro/captur/releases/tag/1.0.0 has been created and published to crates.io


Allow for filepaths to include

When playing with omlmd I tried to push a file which contained a ":" and oras choked on it. I belive that you should check if the file exists and only split off the last : looking for options, not the first colon.

@tarilabs akin to our discussion above, I think we should allow maximally one :, and then if there is another one (and the filepath does not exist) an error should be raised. So your last example above (the newly failing test) should raise that error I think.

@vsoch we could transform the already existing test case on main, failing with this PR, as a failure case. If I understand that correctly, I agree.
I do not concur we should allow maximally one :, as it seems to me in case of Win you want to allow C:\file:mime and in other cases we want to allow my:file:containing:columns:mime.
Let me know how could I help on this PR ! Thanks for the early feedback

@tarilabs akin to our discussion above, I think we should allow maximally one :, and then if there is another one (and the filepath does not exist) an error should be raised. So your last example above (the newly failing test) should raise that error I think.

Again just driveby commenting with limited context so feel free to disregard but...
why would you allow one colon but not more than one colon?  what if a filename has two? what if the red has one and a content type?
if the plan is to delegitimize certain filenames to avoid ambiguity with filenames with embedded content types then why allow embedded colons at all?
Special case for just Dan's case seems strange to me, it should either allow colons in general or not all imo
also, is there any security ramifications? is this ever used in untrusted scenarios? just thinking about the case where a content type could be spoofed by having files named file and file:wrongtype on disk at the time of the call

why would you allow one colon but not more than one colon? what if a filename has two? (eg machineid:hash-type:hash) what if the ref has one and a content type (eg hash-type:hash:content-type)?

More than one colon is fine if the file is found to exist. It's the cases where you've parsed a mimetype and there is an extra colon not associated with a file that should raise an error. That's likely a mistake.

More than one colon is fine if the file is found to exist. It's the cases where you've parsed a mimetype and there is an extra colon not associated with a file that should raise an error. That's likely a mistake.

But if the file doesn't exist it ultimately raises an error anyway right? I guess the question is should, missing;file:type and missing:file:type both ultimately lead to FileNotFoundError or should missing:file:type return a ValueError instead.
Another complication is mime types can support parameters, and the values of parameters can have colons (e.g, just making something up,  prolly not be real, ref="file.mp4:video/mpeg4; aspect_ratio=16:9") .
So perhaps this code should be validating the content type against the spec as well, and the kind of error returned perhaps should depend on if the content type is valid.

Another complication is mime types can support parameters, and the values of parameters can have colons (e.g, just making something up, prolly not be real, ref="file.mp4:video/mpeg4; aspect_ratio=16:9") .

Is that applicable here? 🤔

... If defined, the value MUST comply with RFC 6838, including the naming requirements in its section 4.2, ...
(source)

it seems to me it's only the media-type itself, not the parameters typically found in content-type.
wdyt?

If the path starts with a colon, fail right away.
If there are one or more colons, split by the colon, just once (as the PR does here)
Then assume the first part is a media type, the second part is a file.
If the file does not exist, error.
If the media type is empty, also error.

We can discuss those more complex cases when they actually appear. I don't think it makes sense to solve a problem that doesn't exist yet.

Another complication is mime types can support parameters, and the values of parameters can have colons (e.g, just making something up, prolly not be real, ref="file.mp4:video/mpeg4; aspect_ratio=16:9") .

Is that applicable here? 🤔

I think the main use case for parameters is legacy text files (e.g. ISO-8859-1 or Windows-1252 instead of utf-8), maybe not applicable, or worth supporting...no idea.
Complications with parameters aside, I guess my main point, though, was, this merge request is focusing on validating the filename and doing I/O calls to make heuristic decisions, but it might be worthwhile to validate the media type too. Knowing if the media type is valid or invalid is useful in its own right, and can also potentially inform the heuristics as well.

Complications with parameters aside, I guess my main point, though, was, this merge request is focusing on validating the filename and doing I/O calls to make heuristic decisions, but it might be worthwhile to validate the media type too. Knowing if the media type is valid or invalid is useful in its own right, and can also potentially inform the heuristics as well.

Totally agree! It's out of scope for this PR, but it would be great to open an issue (if you don't want to work on it) or PR directly to tackle it.

If the path starts with a colon, fail right away.

okay, but note files can legitimately start with colons, may be none that will ever go through these functions, i'm don't know.  (but I have some in my home dir right now for instance)

2. If there are one or more colons, split by the colon, just _once_ (as the PR does here)

makes sense to me

3. Then assume the first part is a media type, the second part is a file.

assume you mean that the other way around, but makes sense

4. If the file does not exist, error.

makes sense

5. If the media type is empty, also error.

I still think it probably makes sense to do more validation than just "is empty" since the docs say the format is a hard requirement. I wouldn't be surprised if there is some regex already crafted out there that validates to spec.

We can discuss those more complex cases when they actually appear. I don't think it makes sense to solve a problem that doesn't exist yet.

yea sorry not trying to derail things for cases that don't matter. maybe i'm pushing for over engineering here...

We can move the "starts with" to be later, and yes other order is what I meant. Apologies - I keep switching state between deep programming and trying to be articulate - doesn't always work super well.
And generally whatever you think is best practice I am happy to review.

And generally whatever you think is best practice I am happy to review.

So I don't want to invest the time to build and test this right now, but my suggestion would be something like this, (though maybe slightly different if you and @tarilabs decide media type parameters aren't worthy of supporting)
 def split_path_and_content(ref: str) -> PathAndOptionalContent:
     """
     Parse a string containing a path and an optional content

     Examples
     --------
     <path>:<content-type>
     path/to/config:application/vnd.oci.image.config.v1+json
     /dev/null:application/vnd.oci.image.config.v1+json
     C:\\myconfig:application/vnd.oci.image.config.v1+json

     Or,
     <path>
     /dev/null
     C:\\myconfig

     :param ref: the manifest reference to parse (examples above)
     :type ref: str
     : return: A Tuple of the path in the reference, and the content-type if one found,
               otherwise None.
     """
-    if ":" not in ref:
-        return PathAndOptionalContent(ref, None)
-
-    if pathlib.Path(ref).drive:
-        # Running on Windows and Path has Windows drive letter in it, it definitely has
-        # one colon and could have two or feasibly more, e.g.
-        # C:\test.tar
-        # C:\test.tar:application/vnd.oci.image.layer.v1.tar
-        # C:\test.tar:application/vnd.oci.image.layer.v1.tar:somethingelse
-        #
-        # This regex matches two colons in the string and returns everything before
-        # the second colon as the "path" group and everything after the second colon
-        # as the "context" group.
-        # i.e.
-        # (C:\test.tar):(application/vnd.oci.image.layer.v1.tar)
-        # (C:\test.tar):(application/vnd.oci.image.layer.v1.tar:somethingelse)
-        # But C:\test.tar along will not match and we just return it as is.
-        path_and_content = re.search(r"(?P<path>.*?:.*?):(?P<content>.*)", ref)
-        if path_and_content:
-            return PathAndOptionalContent(
-                path_and_content.group("path"), path_and_content.group("content")
-            )
-        return PathAndOptionalContent(ref, None)
-    else:
-        path_content_list = ref.split(":", 1)
-        return PathAndOptionalContent(path_content_list[0], path_content_list[1])
+
+    # RFC 6838 Section 4.2: Media Type Syntax
+    # https://tools.ietf.org/html/rfc6838#section-4.2
+    #
+    # Media types are defined as:
+    #
+    # type-name = restricted-name
+    # subtype-name = restricted-name
+    # restricted-name = restricted-name-first *126restricted-name-chars
+    # restricted-name-first  = ALPHA / DIGIT
+    # restricted-name-chars  = ALPHA / DIGIT / "!" / "#" / "$" / "&" / "-" / "^" / "_"
+    #
+    # So valid characters are letters, digits, and the symbols: ! # $ & - ^ _
+    # Additionally, parameters can be added, which are not specified in detail in RFC 6838.
+    # For parameters, we'll accept any token or quoted string after a semi
+
+    RESTRICTED_NAME_FIRST = r"(?:[A-Za-z0-9])"
+    RESTRICTED_NAME_CHARS = r"[A-Za-z0-9!#$&\-\^_]"
+    RESTRICTED_NAME = rf"{RESTRICTED_NAME_FIRST}{RESTRICTED_NAME_CHARS}{{0,126}}"
+    QUOTED_STRING = r'"(?:\\.|[^"\\])*"'
+    VALUE = rf"(?:{RESTRICTED_NAME}|{QUOTED_STRING})"
+    PARAMETER = rf"(?:;\s*{RESTRICTED_NAME}\s*=\s*{VALUE})"
+    MEDIA_TYPE = rf"{RESTRICTED_NAME}/{RESTRICTED_NAME}(?:{PARAMETER})*"
+
+    media_type_regex = re.compile(rf"{MEDIA_TYPE}\Z")
+
+    if not ref:
+        raise ValueError("Invalid manifest reference")
+
+    path = pathlib.Path(ref)
+    drive = path.drive
+
+    path_candidate = ref
+    content_candidate = ''
+    search_start = len(drive)
+    search_end = len(ref)
+    while search_end >= 0:
+        search_end = ref.rfind(':', search_start, search_end)
+
+        if search_end >= 0:
+            path_candidate = ref[:search_end]
+            content_candidate = ref[search_end + 1:]
+
+        if os.path.exists(path_candidate):
+            if content_candidate:
+                if media_type_regex.fullmatch(content_candidate):
+                    return PathAndOptionalContent(path_candidate, content_candidate)
+                else:
+                    raise ValueError(f"Invalid media type '{content_candidate}'.")
+            else:
+                return PathAndOptionalContent(path_candidate, None)
+
+    raise FileNotFoundError(f"Filename '{ref}' does not exist.")

decide media type parameters aren't worthy of supporting

To clarify, I don't think is a decision here, I simply believe the OCI spec I've liked is not supporting params. Did you have a chance to look at the source spec I've linked in https://github.com/oras-project/oras-py/pull/161#issuecomment-2400235237 and would you reach the same conclusion?

decide media type parameters aren't worthy of supporting

To clarify, I don't think is a decision here, I simply believe the OCI spec I've liked is not supporting params. Did you have a chance to look at the source spec I've linked in #161 (comment) and would you reach the same conclusion?

my reading of the source you pointed me to says the media type must follow rfc 6838. It then directs the reader to section 4.2, with language like "including section 4.2", not "limited to section 4.2".  I mean the parameter bit is the very next section, 4.3, and it's a clear continuation of 4.2, so I don't know why it wouldn't be part of things, but that's just my hot take.

thank you @vsoch @rhatdan


The system directory contains Chinese characters , The project doesn't work .

The system directory contains Chinese characters , The project doesn't work .
example:
D:\项目代码\github\vite-app\src\components
error:

normal example:
D:\github\vite-vue
there won't be any problem
System Info

vite version: ^2.0.0-beta.7
Operating System: windows 10
Node version: v14.15.3
Package manager (npm/yarn/pnpm) and version: npm 6.14.9

As a developer, it's better not to use the Chinese directory, sometimes the characters will be garbled

As a developer, it's better not to use the Chinese directory, sometimes the characters will be garbled

As a developer, it's better not to use the Chinese directory, sometimes the characters will be garbled

I know, this may affect some other users

As a developer, it's better not to use the Chinese directory, sometimes the characters will be garbled

I know, this may affect some other users

But there is no denying that this is a bug,
in beta.31, It became /@fs/项目代码\github\vite-app

But there is no denying that this is a bug,
in beta.31, It became /@fs/项目代码\github\vite-app


PlotlyAPI: use res.text() if request failed

Closes #380

@tarzzz This a 1-line PR. Please, would you review it?

💃 ..


✨ feat: implement URL encoding and new cookieAttributes prop

Drops cookieDomain in favor of a more flexible prop cookieAttributes
URL encoding/decoding for setting and parsing the cookie
New e2e tests to test entire journeys

Pull Request Checklist

[x] I have read and accept the Contributor License Agreement

I really like that! That needs to be released as a new major version

Awesome! Please keep in mind to trigger a new FOSS evaluation before pushing the new bundled release to npm. 😄


Voltage, Phases and Current look strange

Describe the bug
In the Charge Details view, voltage is 1 or 2, Phases does not show anything and Current is 0. This is a DC charging session. Is that correct?
Screenshots

Operating environment (please complete the following information):

OS: Ubuntu 18.04.1
Version v1.13

Well, it's displayed as it is reported by the API. There are definitely some quirks. For example, some firmwares always report 2 phase charging regardless of whether that's really true or not.


jwt: Reject requests with HTTP headers present in claim to headers

Title: Reject requests with HTTP headers present in claim to headers
Description: I would like to optionally block requests that contain HTTP headers which are also present in the claim-to-header JWT configuration. This ensures that headers used to carry JWT claims cannot be tampered with by downstream clients.  My current workaround is to remove these headers with HeaderMutation.
Note that the filter overrides the header value if present but if the rule is optional (contain allow_missing: {}) then it will also allow the header to be forwarded.
Proposed:
Implement a new JwtRequirement option to fail requests containing headers specified in the claim-to-header configuration. When this requirement is enabled, incoming request with a header that matches a claim-to-header mapping should be rejected with an appropriate HTTP error code.
...
http_filters:
  - name: envoy.extensions.filters.http.jwt_authn
    typed_config:
      "@type": type.googleapis.com/envoy.extensions.filters.http.jwt_authn.v3.JwtAuthentication
      providers:
        firebase:
          claim_to_headers:
          - claim_name: user_id
            header_name: x-firebase-uid
          - claim_name: firebase.sign_in_provider
            header_name: x-firebase-provider
      rules:
      - match:
          prefix: "/"
        requires:
          requires_all:
            requirements:
              - provider_name: firebase
              - strict_claim_to_headers: {} # block requests with matching headers to a matching rule.
...

cc @yanavlasov

also cc @tyxia


[security] Istio CA needs to support different cert TTL for different workloads

In some cases, users may want to have different cert TTL for different workloads. For example, the workloads on VMs may want to have longer TTL than K8s ones, for legacy reasons, limitations on network, or long workload downtime.

Hey,
I don't know if it helps others but I ended up signing my own 1yr cert against the istio CA to work around this.
https://gist.github.com/Stono/fe83ea90e912f878bf5e49cdd403cbbc

Hi Stono, in your case you don't have a node agent to provision/rotate certs for your device, it makes sense to have a long lived cert.
I think for this issue, we want to support the use case that node agent provisions certs for the workloads. So maybe the node agents will get certs living for days/weeks (not too long, because node agents are still able able to talk to CA)
In the next step, we may support calling Istio CA to provision certs for a normal user using a command line tool. Maybe that will save you some manual work.


NODE-1134: using pino as debug logger

We need pino, pino-debug and pino-pretty to kind of mimic the previous result:
before:

after:


install failed

log:
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.

Unfortunately, an error has occurred:
	timed out waiting for the condition

This error is likely caused by:
	- The kubelet is not running
	- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
	- 'systemctl status kubelet'
	- 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
Here is one example how you may list all Kubernetes containers running in docker:
	- 'docker ps -a | grep kube | grep -v pause'
	Once you have found the failing container, you can inspect its logs with:
	- 'docker logs CONTAINERID'
	[WARNING HTTPProxy]: Connection to "https://<IP_ADDRESS>" uses proxy "http://<IP_ADDRESS>:22222". If that is not intended, adjust your proxy settings
	[WARNING HTTPProxyCIDR]: connection to "<IP_ADDRESS>/16" uses proxy "http://<IP_ADDRESS>:22222". This may lead to malfunctional cluster setup. Make sure that Pod and Services IP ranges specified correctly as exceptions in proxy configuration
	[WARNING HTTPProxyCIDR]: connection to "<IP_ADDRESS>/16" uses proxy "http://<IP_ADDRESS>:22222". This may lead to malfunctional cluster setup. Make sure that Pod and Services IP ranges specified correctly as exceptions in proxy configuration
	[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
/bin/kubeadm [init --config=/etc/kubernetes/kubeadm.conf] err: exit status 1 4m26.70353459s
Resetting kubeadm...
/bin/kubeadm [reset --force --cri-socket=unix:///run/containerd/containerd.sock]
[preflight] running pre-flight checks
[reset] Reading configuration from the cluster...
[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[reset] stopping the kubelet service
[reset] unmounting mounted directories in "/var/lib/kubelet"
[reset] deleting contents of stateful directories: [/var/lib/etcd /var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]
[reset] deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually.
For example:
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

 If that is not intended, adjust your proxy settings

It seems in the log that you have set up HTTPProxy:
[WARNING HTTPProxy]: Connection to "https://<IP_ADDRESS>" uses proxy "http://<IP_ADDRESS>:22222". If that is not intended, adjust your proxy settings.

And your Kubelet error shows that it can't connect (TCP refuse) to the API server:
Mar 19 18:58:21 kubesphere kubelet[7246]: E0319 18:58:21.746162    7246 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://<IP_ADDRESS>:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: connection refused

Can you please share your proxy environment configuration:
env | grep -i _proxy= | sort

NO_PROXY must contain the ip ranges defined with --kubernetes-infrastructure-cidr --kubernetes-pod-network-cidr and --kubernetes-service-cidr. For the default values this would be the following:
export NO_PROXY="<IP_ADDRESS>/20,<IP_ADDRESS>/16,<IP_ADDRESS>/16,.kubernetes,.kubernetes.default,.kubernetes.default.svc,.kubernetes.default.svc.cluster.local"

Please modify NO_PROXY for you network configuration accordingly.

why pull k8s image???
dial tcp <IP_ADDRESS>:443: i/o timeout
Mar 21 11:06:12 localhost kubelet: E0321 11:06:12.212869    6572 pod_workers.go:190] Error syncing pod 6f947a25aaf142618e41c0a9b56040f4 ("kube-controller-manager-kubesphere_kube-system(6f947a25aaf142618e41c0a9b56040f4)"), skipping: failed to "CreatePodSandbox" for "kube-controller-manager-kubesphere_kube-system(6f947a25aaf142618e41c0a9b56040f4)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-controller-manager-kubesphere_kube-system(6f947a25aaf142618e41c0a9b56040f4)\" failed: rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to resolve image \"k8s.gcr.io/pause:3.1\": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout"
Mar 21 11:06:12 localhost kubelet: E0321 11:06:12.213333    6572 remote_runtime.go:96] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Mar 21 11:06:12 localhost kubelet: E0321 11:06:12.213375    6572 kuberuntime_sandbox.go:68] CreatePodSandbox for pod "kube-apiserver-kubesphere_kube-system(dcc44bcb9fab97d23ea76d9175babe47)" failed: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Mar 21 11:06:12 localhost kubelet: E0321 11:06:12.213388    6572 kuberuntime_manager.go:662] createPodSandbox for pod "kube-apiserver-kubesphere_kube-system(dcc44bcb9fab97d23ea76d9175babe47)" failed: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Mar 21 11:06:12 localhost kubelet: E0321 11:06:12.213455    6572 pod_workers.go:190] Error syncing pod dcc44bcb9fab97d23ea76d9175babe47 ("kube-apiserver-kubesphere_kube-system(dcc44bcb9fab97d23ea76d9175babe47)"), skipping: failed to "CreatePodSandbox" for "kube-apiserver-kubesphere_kube-system(dcc44bcb9fab97d23ea76d9175babe47)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-apiserver-kubesphere_kube-system(dcc44bcb9fab97d23ea76d9175babe47)\" failed: rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to resolve image \"k8s.gcr.io/pause:3.1\": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout"
[root@kubesphere kubelet.service.d]#

]# crictl images
IMAGE                             TAG                 IMAGE ID            SIZE
docker.io/banzaicloud/coredns     1.2.6               f59dcacceff45       12.2MB
docker.io/banzaicloud/etcd        3.2.24              3cab8e1b9802c       63.4MB
docker.io/banzaicloud/hyperkube   v1.13.3             68b0696339174       180MB
docker.io/banzaicloud/pause       3.1                 da86e6ba6ca19       326kB

The kubelet uses the hard coded pause container during the initialization of pods. https://github.com/kubernetes/kubernetes/search?q=PodSandboxImage&unscoped_q=PodSandboxImage

https://github.com/banzaicloud/pke/issues/14 will address this.
Please note later on weave network will be installed, that will add two more images.
# crictl images
IMAGE                                 TAG                 IMAGE ID            SIZE
docker.io/banzaicloud/auto-approver   0.1.0               085ce11431983       16MB
docker.io/banzaicloud/coredns         1.2.6               f59dcacceff45       12.2MB
docker.io/banzaicloud/etcd            3.2.24              3cab8e1b9802c       63.4MB
docker.io/banzaicloud/hyperkube       v1.13.3             68b0696339174       180MB
docker.io/banzaicloud/pause           3.1                 da86e6ba6ca19       326kB
docker.io/weaveworks/weave-kube       2.5.1               1f394ae9e2260       40.5MB
docker.io/weaveworks/weave-npc        2.5.1               789b7f4960344       13.5MB

@pennpeng Created release 0.2.1 with the fix.
Please give it a try!

same problem
[root@kubesphere kubernetes]# systemctl status kubelet -l
● kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/etc/systemd/system/kubelet.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─0-containerd.conf, 10-kubeadm.conf
   Active: active (running) since Fri 2019-03-22 17:43:30 CST; 1min 55s ago
     Docs: https://kubernetes.io/docs/
 Main PID: 10504 (kubelet)
    Tasks: 19
   Memory: 30.3M
   CGroup: /system.slice/kubelet.service
           └─10504 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --anonymous-auth=false --authorization-mode=Webhook --client-ca-file=/etc/kubernetes/pki/ca.crt --event-qps=0 --feature-gates=RotateKubeletServerCertificate=true --protect-kernel-defaults=true --read-only-port=0 --rotate-certificates=true --streaming-connection-idle-timeout=5m --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256 --container-runtime=remote --container-runtime-endpoint=unix:///run/containerd/containerd.sock

Mar 22 17:45:25 kubesphere kubelet[10504]: E0322 17:45:25.956897   10504 pod_workers.go:190] Error syncing pod 304f9e65b941638069f0ef000250eccd ("kube-scheduler-kubesphere_kube-system(304f9e65b941638069f0ef000250eccd)"), skipping: failed to "CreatePodSandbox" for "kube-scheduler-kubesphere_kube-system(304f9e65b941638069f0ef000250eccd)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-scheduler-kubesphere_kube-system(304f9e65b941638069f0ef000250eccd)\" failed: rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to resolve image \"k8s.gcr.io/pause:3.1\": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout"
Mar 22 17:45:25 kubesphere kubelet[10504]: E0322 17:45:25.956904   10504 pod_workers.go:190] Error syncing pod 26a4d4d11a44d508fcc89c82c268853e ("etcd-kubesphere_kube-system(26a4d4d11a44d508fcc89c82c268853e)"), skipping: failed to "CreatePodSandbox" for "etcd-kubesphere_kube-system(26a4d4d11a44d508fcc89c82c268853e)" with CreatePodSandboxError: "CreatePodSandbox for pod \"etcd-kubesphere_kube-system(26a4d4d11a44d508fcc89c82c268853e)\" failed: rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to resolve image \"k8s.gcr.io/pause:3.1\": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout"
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.038783   10504 kubelet.go:2266] node "kubesphere" not found
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.041989   10504 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://<IP_ADDRESS>:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: connection refused
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.042844   10504 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://<IP_ADDRESS>:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dkubesphere&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: connection refused
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.043997   10504 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:453: Failed to list *v1.Node: Get https://<IP_ADDRESS>:6443/api/v1/nodes?fieldSelector=metadata.name%3Dkubesphere&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: connection refused
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.139062   10504 kubelet.go:2266] node "kubesphere" not found
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.146355   10504 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.239273   10504 kubelet.go:2266] node "kubesphere" not found
Mar 22 17:45:26 kubesphere kubelet[10504]: E0322 17:45:26.339515   10504 kubelet.go:2266] node "kubesphere" not found
[root@kubesphere kubernetes]# pke version
kubeadm version: struct { cmd.ClientVersion "json:\"clientVersion\"" }{ClientVersion:cmd.ClientVersion{GitVersion:"0.2.1", GitCommit:"8027e50", GitTreeState:"", BuildDate:"2019-03-21T15:31:28Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}}
[root@kubesphere kubernetes]#

and the crictl has no tag options,i can't retag docker.io/banzaicloud/pause to k8s......

It seems kube-apiserver exited with error.
List kube-apiserver and look for CONTAINER ID.
$ crictl ps -a -l name=kube-apiserver -n 1
CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
05ab01a60ec81       f59dcacceff45       3 minutes ago       Running             coredns             0                   c03e7623ba8d9

Get container logs for kube-apiserver. Use CONTAINER ID from previous command.
crictl logs 05ab01a60ec81

And paste the logs here.

there are no image:"k8s.gcr.io/pause:3.1\
[root@kubesphere ~]#  crictl ps -a -l name=kube-apiserver -n 1
CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
[root@kubesphere ~]#  crictl ps -a -l name=kube-apiserver -n 1
CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
[root@kubesphere ~]#  crictl ps -a -l name=kube-apiserver -n 1
CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
[root@kubesphere ~]#  crictl ps -a -l name=kube-apiserver -n 1
CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID
[root@kubesphere ~]#

Please do a clean install from scratch (no containerd installed on host machine).
Use 0.2.1 version:
curl -v https://banzaicloud.com/downloads/pke/pke-0.2.1 -o /usr/local/bin/pke

and verify the right PKE version is being used:
chmod +x /usr/local/bin/pke
/usr/local/bin/pke version -o yaml
clientVersion:
  buildDate: "2019-03-21T15:31:28Z"
  compiler: gc
  gitCommit: 8027e50
  gitTreeState: ""
  gitVersion: 0.2.1
  goVersion: go1.12.1
  platform: linux/amd64

gitVersion must be 0.2.1.

@pennpeng are you still experiencing this issue?

Closing due to inactivity.


[anaconda] Python (Pip) Security Update for pyarrow (GHSA-5wvp-7f3h-6wmm)

Dev container name:
anaconda
Description:
This PR patches the following vulnerability:
GHSA-5wvp-7f3h-6wmm - related to the pyarrow package;
This vulnerability comes from the continuumio/anaconda3 image used upstream for the anaconda devcontainer.
Changelog:
Updated Dockerfile & locked version for following package :

pyarrow - minimum package version set to 14.0.1.

Other changes to support primary change :

Updated tests to verify pyarrow minimum version 14.0.1 to fix GHSA-5wvp-7f3h-6wmm.

Checklist:
Checked that applied changes work as expected.

@microsoft-github-policy-service agree company="GitHub"

@microsoft-github-policy-service agree company="GitHub"

@microsoft-github-policy-service agree company="GitHub"

@microsoft-github-policy-service agree company="GitHub"
On Wed, Dec 13, 2023 at 11:58 AM microsoft-github-policy-service[bot] <
@.***> wrote:

@bhupendra-vaishnav https://github.com/bhupendra-vaishnav please read
the following Contributor License Agreement(CLA). If you agree with the
CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of
intellectual property rights to my Submissions and I am not making
Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work
for my employer (or my employer has intellectual property rights in my
Submissions by contract or applicable law). I have permission from my
employer to make Submissions and enter into this Agreement on behalf of my
employer. By signing below, the defined term “You” includes me and my
employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the
party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its
affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is
effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable
or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft
and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or
distributing code or other content to any
Project, including but not limited to communication on electronic
mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf
of, the Project for the purpose of
discussing and improving that Project, but excluding communication
that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material
Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement
before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now
or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions
is entirely Your original work.
Should You wish to Submit materials that are not Your original work,
You may Submit them separately
to the Project if You (a) retain all copyright and license information
that was in the materials as You
received them, (b) in the description accompanying Your Submission,
include the phrase “Submission
containing materials of a third party:” followed by the names of the
third party and any licenses or other
restrictions of which You are aware, and (c) follow any other
instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include
Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a
contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your
employer has intellectual
property rights in Your Submission by contract or applicable law, You
must secure permission from Your
employer to make the Submission before signing this Agreement. In that
case, the term “You” in this
Agreement will refer to You and the employer collectively. If You
change employers in the future and
desire to Submit additional Submissions for the new employer, then You
agree to sign a new Agreement
and secure permission from the new employer before Submitting those
Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly
display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all
of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or
the combination of the
Submission with the Project to which it was Submitted to make, have
made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the
Project.
Other Rights Reserved. Each party reserves all rights not
expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without
limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are
legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your
original work (except as You may
have disclosed under Section 3). You represent that You have secured
permission from Your employer to
make the Submission in cases where Your Submission is made in the
course of Your work for Your
employer or Your employer has intellectual property rights in Your
Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You
represent and warrant that You
have the necessary authority to bind the listed employer to the
obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless
You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE
WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED
UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO,
ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of
any facts or circumstances of which
You later become aware that would make Your representations in this
Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to
Projects and information about
contributions may be maintained indefinitely and disclosed publicly,
including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the
laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal
courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in
which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County,
Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire
agreement between the parties, and
supersedes any and all prior agreements, understandings or
communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may
be assigned by Microsoft.

—
Reply to this email directly, view it on GitHub
https://github.com/devcontainers/images/pull/893#issuecomment-1854539271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLSKHRQRTJFRXAHZQG7FNDYJH3FBAVCNFSM6AAAAABATUZUSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGUZTSMRXGE
.
You are receiving this because you were mentioned.Message ID:
@.***>