Why Not add more Models parameters  from Controllers and  Let ControllerName and ActionName more easy get in View?

Why Not add more Models parameters  from Controllers
In HomeController.cs
return View(Index,userinfo,msglist,...); //userinfo is a model,msglist are  models
maybe a limit for count of the models parameters ( Max best most is 8 too much model limit is meaningless)
and in Home/Index.cshtml
Model1,Model2,Model3,Model4,Model5,Model6,Model7,Model8  if(Model1.HasValue) {  <a asp-for='Name' value='Model1.Name'>.... }
Let ControllerName and ActionName more easy get in View?
In Index.cshtml
\<h2\>@:this.ControllerName / @:this.ActionName \</h2\>
another problem is why not let route system more easy use?
i know currently the route system of asp.net mvc is very strong!
but its still little complex !
im a noob and i just hope MVC framework more easy to use and more and more popular !
i think if (u,me,we,all asp.net mvc ) want to grow,need study good(merit) from competitor.
discard the dross and select the essence !

You can already easily pass in however much data you want to the view using ViewData/ViewBag:
ViewData["model1"] = model1;
ViewData["model2"] = model2;
...
ViewBag.Model1 = model1;
ViewBag.Model2 = model2;

And you can read these just as easily from the view.
To get the controller name and action name from the view you can access RouteData values and read the "controller" and "action" keys.
The reason these aren't first-class items is that they are not very common patterns.


Avoid process reference error

Seems the typo in code. Similar issue was fixed here: #726
Exception output:
Uncaught (in promise) ReferenceError: process is not defined
    at warning (react-utils.js:75)
    at warnOnce (react-utils.js:92)
    at checkIfStyleSheetIsImported (react-utils.js:132)
    at XYPlot.componentDidMount (xy-plot.js:165)
    at eval (ReactCompositeComponent.js:262)
    at measureLifeCyclePerf (ReactCompositeComponent.js:73)
    at eval (ReactCompositeComponent.js:261)
    at CallbackQueue.notifyAll (CallbackQueue.js:74)
    at ReactReconcileTransaction.close (ReactReconcileTransaction.js:78)
    at ReactReconcileTransaction.closeAll (Transaction.js:207)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

thanks!


Revert calculation of humidity and temperature for DHT11.

Code review: http://codeflow/Client/CodeFlow2010.application?server=http://codeflow/Services/DiscoveryService.svc&review=jordanrh-dea1fc4e32ef45198e4bd64b3aacf981

Hi @jordanrh1, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Jordan Rhee). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Unable to deploy to an Opeshift 3.5 cluster using FMP 3.5.34

Description
When running the integration tests of this project (which use Arquillian Cube) on an Openshift 3.5 cluster, I am getting the following error
java.lang.RuntimeException: io.fabric8.kubernetes.clnt.v3_1.KubernetesClientException: Failure executing: POST at: https://osemaster.spring-boot.osepool.centralci.eng.rdu2.redhat.com:8443/oapi/v1/namespaces/gandrian/deploymentconfigs. Message: DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1". Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1", metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}).
Caused by: io.fabric8.kubernetes.clnt.v3_1.KubernetesClientException: Failure executing: POST at: https://osemaster.spring-boot.osepool.centralci.eng.rdu2.redhat.com:8443/oapi/v1/namespaces/gandrian/deploymentconfigs. Message: DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1". Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1", metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={})

The odd things is that when I the tests are run on an Openshift 3.7 cluster, everything works as expected.
Furthermore, when I change the version of f-m-p to 3.5.30 everything works just fine on both Openshift 3.5 and 3.7
Info

f-m-p version : 3.5.34
Maven version (mvn -v) : 3.5.2

Kubernetes / OpenShift setup and version : Openshift 3.5
If it's a bug, how to reproduce : Run mvn clean verify -Popenshift,openshift-it on the sb-1.5.10 branch of the aforementioned project:
Sample project : https://github.com/snowdrop/spring-boot-http-booster/tree/sb-1.5.10

Notes
You can easily switch versions of fmp in the sample project by setting the fabric8-maven-plugin.version Maven property

In case it's not very clear, the easiest way to reproduce the problem is to make this single modification to the sample project:
Add the following lines in pom.xml

3.5.34

Hi @geoand
I am not sure but this may be a problem because of you are using latest fmp with latest model and client on previous Openshift.
New openshift generates api version like For DeploymentConfig: apps.openshift.io/v1
So latest fmp may be generating things like that and not supported on previous Openshift version.
You can try this thing if it works.
You can also set the apiVersion of the resource like in the case of SecurityContextConstraints :

SecuirtyContextConstraints scc = new SecurityContextConstraintsBuilder()
		.withApiVersion("v1")
		.withNewMetadata().withName("scc").endMetadata()
		.withAllowPrivilegedContainer(true)
		.withNewRunAsUser()
		.withType("RunAsAny")
		.endRunAsUser()
		.build();

Ideally, this should be a problem, I am not sure just my initial suspect.
Thanks

Hello @piyush1594,
I just wanted to add that doing the following:
mvn clean package fabric8:deploy -Dfabric8-maven-plugin.version=3.5.34 -DskipTests=true -Popenshift

also results in the following:
 Message: DeploymentConfig in version "v1" cannot be handled as a DeploymentConfig: no kind "DeploymentConfig" is registered for version "apps.openshift.io/v1"
About the fix you propose, where would such a change be applied?

My best understanding of the problem is the following:
FMP 3.5.34 generates a DeploymentConfig using apiVersion apps.openshift.io/v1 which is not something that Openshift 3.5 understands.
FMP 3.5.30 generated a DeploymentConfig using apiVersion v1 which was correctly understood by Openshift 3.5.
This raises the question whether Openshift 3.5 is meant to be supported by FMP 3.5.34 or not?
If it is meant to be supported then I guess FMP much determine the version of Openshift that is to be used before creating the DeploymentConfig

Hey @geoand
I just checked locally building a sample project.
FMP 3.5.34 generates Deployment Config with apiVersion apps.openshift.io/v1
FMP 3.5.30 generates Deployment Config with apiVersion v1
If this is the case, then ideally it is breaking the compatibility with previous Openshift version.
@hrishin @rohanKanojia Need your input into this.

@piyush1594 Thanks for confirming!
Is there any documentation on what versions of Kubernetes/Openshift are meant to be supported with each FMP version?

@geoand
I don't think we have a documentation for this. We need to start doing this. We need to create matrix table which should inform about a particular fmp version is compatible with following OpenShift or Kubernetes version.
Our documentation is here : https://maven.fabric8.io/
Thanks

Hey @geoand
Can we close this issue as we have added matrix table? You can find the matrix table on the website here https://maven.fabric8.io/#compatibility-with-OpenShift-and-Kubernetes
and on GitHub here https://github.com/fabric8io/fabric8-maven-plugin/blob/master/README.md
Thanks

Hi @piyush1594
I really like it! Thank you very much for this!
Feel free to close the issue :)

Thanks @geoand


Error: Cannot find module 'sync-exec'

I messed up the dependencies and devDependencies in my last PR. Sorry for that. This PR resolves this bug.
In detail, the bug was, that sync-exec was only registered under devDependencies, thus it would not be installed when installing this package using npm install or so.

@gleero: Is there any reason not to merge this PR?
When you do, please also increase the version number, otherwise the module version that can be installed via NPM still remains unusable with the latest Node version.

How can I help to get this PR merged?

I'm afraid this can only be done by @gleero.

I reminded @gleero on Twitter about it a few hours ago. It might help a bit. Lets see. In the meantime I'm using your forked version.

Thanks, @gleero.
Please keep in mind that you have to increase the version number to make this change available to everyone using this package.

Thanks @gleero!


Optimise image

Latest image was done by using python/ubuntu. The size of this image is around 1.5 GB. The idea now is to use an optimised version of the container with alpine for example and to reduce the size of the image.
https://github.com/AlvaroRodriguezGallardo/src-brokering/blob/5936cd36a1daa00126b1cbec34870a38be1c2246/example-fn/Dockerfile#L3
Alpine OS is not using the standard glibc so several packages will not work as usual.
Create a new branch, named: example-fn-optimised and create there all the files, etc.

Done!

Great. Now alpine will reduce the size of the image.


Add start and end event listener icons to diagram

Is your feature request related to a problem? Please describe.
Listeners provide implicit functionals which may affect to execution of process but they does not displayed on diagram. It makes debugging and undestanding of diagram a little harder.
Describe the solution you'd like
I think it would be useful if we can see which activities have configured start/end listeners as icon on activity in modeler UI.
Describe alternatives you've considered
None

Hi @voidkor ,
there is a plugin available for this feature: https://github.com/umb/camunda-modeler-property-info-plugin.
Hope this helps, Ingo

Hi @ingorichtsmeier ,
it works fine! Thank you!


Link question

Is this supposed to be Copy PolicyDefinitions folder to \contoso.com\SYSVOL\contoso.com\policies\PolicyDefinitions or Copy PolicyDefinitions folder to \contoso.com\SYSVOL\contoso.com\policies\PolicyDefinitions.
Supposed to be \ or \ before the first contoso.com.  Another Microsoft doc shows it as \.
It doesn't say it here, but the other document says that it should be our domain name\SYSVOL.  Is this correct?

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

ID: ad012591-5c74-f1cd-d3a2-443768e8ceee
Version Independent ID: 918ea4bc-0849-3745-5d9d-a21a973bcd3b
Content: Enroll a Windows 10 device automatically using Group Policy - Windows Client Management
Content Source: windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

Hello @rconiv - Thank you for your query. Please note that information mentioned in step 5 Copy PolicyDefinitions folder to \SYSVOL\contoso.com\policies\PolicyDefinitions is correct. You need to copy the PolicyDefinitions folder to \SYSVOL\contoso.com\policies\PolicyDefinitions. Adding \ before the domain is to give the path idea for the end-user. SYSVOL paths areas:

\SYSVOL
\SYSVOL\domain
\SYSVOL\staging\domain
\SYSVOL\staging areas
\SYSVOL\domain\Policies
\SYSVOL\domain\scripts
\SYSVOL\SYSVOL

Visit https://support.microsoft.com/en-us/topic/04fc119e-295f-a556-9d7c-616796e96d5d to get more idea how the SYSVOL folder works and what needs to be taken into consideration.
Thanks.
Imran.
@e0i - FYI&A Pleaes.

Hello @rconiv - Thank you for your query. Please note that information mentioned in step 5 Copy PolicyDefinitions folder to \SYSVOL\contoso.com\policies\PolicyDefinitions is correct. You need to copy the PolicyDefinitions folder to \SYSVOL\contoso.com\policies\PolicyDefinitions. Adding \ before the domain is to give the path idea for the end-user. SYSVOL paths areas:

\SYSVOL
\SYSVOL\domain
\SYSVOL\staging\domain
\SYSVOL\staging areas
\SYSVOL\domain\Policies
\SYSVOL\domain\scripts
\SYSVOL\SYSVOL

Visit https://support.microsoft.com/en-us/topic/04fc119e-295f-a556-9d7c-616796e96d5d to get more idea how the SYSVOL folder works and what needs to be taken into consideration.
Thanks.
Imran.
@e0i - FYI&A Pleaes.


Client Allocation Request for: friday

Client Allocation Questions
Core Information

Name: friday
Website / Social Media: https://shopping.friday.tw/
Region: Asia excl. Greater China
DataCap Requested: 15TiB
Addresses to be Notarized: f1jyahrlkqntzt7oxszl7kkferax4x7jswz5rex3a
Notary Requested: ozhtdong

@rizzojafeth Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Thanks for your application. I have some questions about you and your company:
1.What's your name? What's your position?
2.What's your company's business? Do you have any other social media link?
3.Could you show me your company's business license?
4.How many miners do you want to store your data to? How much data for each miner?
5.Will you record your allocation decision in public? Which platform will you use?
6.What method/tool will you use to inspect miners? Which aspect of miners will you inspect?

1.Qi Jing. I’m the chairman of Friday.
2. In 2014, friday shopping was published, with the innovative integration of the concept of "curation", starting from the lifestyle, exclusive sales of specialty products, and introducing expert recommendations to create a new shopping experience. In 2017, it merged with GoHappy Shopping, a subsidiary of Far East E-commerce, to deepen the operation of the friday shopping brand, and integrate the advantages of the group-combined with the largest retail channel under the department store sales line, hoping to create the most complete retail channel system for O2O in Taiwan. In the same year, friday shopping won the Visionary Five-Star Service Award First prize in the online shopping category.
Friday shopping adheres to the concept of "concern people" and officially launched the gold membership service in April 2019. friDay shopping shouts "Benefits every time，great life!", combining consumer feedback with unique products, health, entertainment, and convenience , security and other services, all-round upgrading of membership rights, operating a membership system, deepening the relationship between members, and creating an iron powder economy.
In 2020, friDay shopping starts from "let's shopping for a better life", and together with FarEasTone Telecom Group. We will use considerate and innovative services to make technology simpler, help people live in the present more conveniently and smartly, and become a good partner in people's digital life.
3.OK, I will.
4.I think 2 miners are enough.
5.Github can help us inspect miners.
6.We’ll use filfox. We would like to find out reliable miners.

Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network

bafy2bzaceb6olx2yepr4ihhumipt4o5y2jctl5xdp3up2oaul632epfmttjdg

Address

f1jyahrlkqntzt7oxszl7kkferax4x7jswz5rex3a

Datacap Allocated

NaNB

Signer Address

f1lwpw2bcv66pla3lpkcuzquw37pbx7ur4m6zvq2a

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb6olx2yepr4ihhumipt4o5y2jctl5xdp3up2oaul632epfmttjdg


fix(merlin): Fix incorrect formatting of chart values

Motivation
In #254, a new schema was introduced due to the refactored Helm chart. However, there were some tiny errors with the formatting of the values file. In addition https://github.com/caraml-dev/merlin/pull/389 which has been merged to the main branch of Merlin requires a new config field to be introduced in its Helm chart values file for the API server to start up correctly. This PR fixes those issues.
Note: This PR will be merged to get a new Helm chart published for Merlin, which will then be used to update the Merlin CICD workflow, before I'll come back to this repo to update the default Merlin image used.
Modification

charts/merlin/values.yaml - Correction of an incorrect field name and misalignment of a config block
charts/merlin/templates/_helpers.tpl - Addition of the ArtifactServiceType config field

Checklist

[x] Chart version bumped
[x] README.md updated

Thanks for the quick review! 🚀


Backport a version switcher fix for mobile

Closes GH-140
https://github.com/pydata/pydata-sphinx-theme/pull/1342

+1
Let's try this.


Please open a security advisory

I believe I may have found what looks like a security vulnerability in sagetv.
Please open a security advisory so we can discuss privately.
https://github.com/google/sagetv/security/advisories

I think you need to open the advisory yourself, and then it will become visible to me.

I think you need to open the advisory yourself, and then it will become visible to me.

I can't. An admin on the repository needs to do it.

I can't. An admin on the repository needs to do it.

OK, opened one (let me know if you can't find it, I'm not sure if the link is obfuscated so I shouldn't post it here)

OK, opened one (let me know if you can't find it, I'm not sure if the link is obfuscated so I shouldn't post it here)

Got it, you can post links in the public. The contents of advisories is private and only accessible to those who are added to the advisory.

Got it, you can post links in the public. The contents of advisories is private and only accessible to those who are added to the advisory.


Adding support for ChefSpec platform family

When running tests with ChefSpec I load the build-essentials recipe and a number of warnings appear stating that the node's platform is not supported. The node is the chefspec generated node from Fauxhai.
The node currently does not have a platform family. It is set to nil with ChefSpec 4.0.1 version. I have proposed a pull request to set the platform_family to chefspec for a ChefSpec node. This pull request would support the platform family so that tests do not generate a lot of extraneous error messages.

I'm going to close this out since the real solution is to set the platform in Chefspec.  If you run as Ubuntu (which I thought was the default...) you shouldn't have this problem.


Does not work on MacOS X Cellar Elixir v1.0.2

Tried to use this Elixir autocompletion and linter, but it could not work.
I have this in my Sublime Text v3 User Settings:
"env":
{
"PATH": "/usr/local/Cellar/elixir/1.0.2/bin"
},

I had a faulty Nodejs plugin in sublime which messed with the loading of the PATH when sublime was launching.  Check your Sublime Console when you start sublime, ensure PATH modification is being loaded correctly.


Makefile: use defined variables in 'test-with-kind'

Change commands and parts of parameters to use defined variables

In order to prevent erorrs of running e2e tests, this commit maintains
the prefix and tag of loaded images as 'intel/' and 'devel'
This commit also fixes the error of running 'make test-with-kind' in
Jenkinsfile.

Signed-off-by: Hyeongju Johannes Lee<EMAIL_ADDRESS>

Codecov Report

Merging #861 (e0d23b4) into main (e7cc7b4) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head e0d23b4 differs from pull request most recent head 2d7f363. Consider uploading reports for the commit 2d7f363 to get more accurate results

@@           Coverage Diff           @@
##             main     #861   +/-   ##
=======================================
  Coverage   55.00%   55.00%
=======================================
  Files          39       39
  Lines        3667     3667
=======================================
  Hits         2017     2017
  Misses       1535     1535
  Partials      115      115

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 e7cc7b4...2d7f363. Read the comment docs.

Please wait until the test with Jenkinsfile is finished successfully.!

@hj-johannes-lee looks like ’kubectl’ binary needs to be installed in ’Jenkinsfile’

@mythi @bart0sh I guess I changed everything as you suggested, and the test with Jenkinsfile is also finished succesfully.! Could you take a look lastly?


[SPARK-45577][PYTHON] Fix UserDefinedPythonTableFunctionAnalyzeRunner to pass folded values from named arguments

What changes were proposed in this pull request?
Fix UserDefinedPythonTableFunctionAnalyzeRunner to pass folded values from named arguments.
Why are the changes needed?
In the analysis in Python for Python UDTF, the folded values are not passed from named arguments.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Modified the related tests.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @dtenedor

The failed tests seem not to be related to this PR.

Thanks! merging to master.


entry: send( ctx => ({/.../})) generates TypeError

Description

In the machine configuration object the following generates an error:
          entry: [
            log(
              (ctx) =>
                `Sending command to ui machine with purpose: ${JSON.stringify(
                  ctx.changes.purpose,
                )}`,
            ),
            send(
           // function expression that returns event
              (ctx) => ({
                type: 'GENERATE_UI',
                payload: { purpose: ctx.changes.purpose },
              }),
              {
                // options
                id: 'generate_ui',
                to: 'ui-server',
                delay: 10,
              },
            ),
          ],

Configure the send action creeator with an event object instead (and fix the value of the payload)... no error.
Expected Result

No error
Actual Result

TypeError: can't access property "indexOf", r.event.type is undefined
    sn StateChartAction.js:86
    React 25
    430 index.tsx:14
    i (index):1
    104 main.2b5d9a5b.chunk.js:1
    i (index):1
    a (index):1
    e (index):1
    <anonymous> main.2b5d9a5b.chunk.js:1

Reproduction

CodeSandbox template (JavaScript)
CodeSandbox template (TypeScript)
⚛ CodeSandbox template (React)
⚛ CodeSandbox template (React + TypeScript)
💚 CodeSandbox template (Vue + Composition API)
XState Visualizer

Additional context

xstate: "^4.11.0"

Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the time to set up the repro, even if exact steps are given.

@Andarist thank you for your prompt reply. Your point is fair and I will do my best to get something up and running.
In the meantime, have you seen this type of error code before? It comes from the online viz with my pasted code base.
Sent with GitHawk

The visualizer is running on an older version of XState, which could be the source of this error.

Ah!! That explains soooo much.
I was looking for a way to run the visualizer locally. Is that possible?  Is it on github so that I might also see how I might help... if helpful (I did do a first pass look and did not find anything).
Regarding the version online, is there legacy code that will break with an upgrade?
Sent with GitHawk

I'm currently working on the new visualizer, which is expected to be completed by the end of the month. It is a complete overhaul of the existing visualizer which is why we can't incrementally update the current one.

@davidkpiano Thank you alround.  It's a great tool.  Clearly differentiating.   On a separate, but viz-related topic, is there a way to have one machine reference another machine specified in a different gist? So, ~ imports of gists?

@davidkpiano Thank you alround. It's a great tool. Clearly differentiating. On a separate, but viz-related topic, is there a way to have one machine reference another machine specified in a different gist? So, ~ imports of gists?

There will be! Sneak preview: see the parent link?

Truly cool.


Get-RunspaceData "An error occurred while sending the request."

Expected Behavior
Sort more than 50-100 at the time.
Current Behavior
It does works for the first 50-100 JAVs after that this error pops out:
Get-RunspaceData: C:\Users\X\Documents\PowerShell\Modules\Javinizer\2.5.7\Public\Invoke-JVParallel.ps1:561
Line |
561 |                      Get-RunspaceData
|                      ~~~~~~~~~~~~~~~~
| Exception calling "EndInvoke" with "1" argument(s): "The running command stopped because the
| preference variable "ErrorActionPreference" or common parameter is set to Stop: [GIRO-62]
| [Set-JVMovie] Error occurred when creating thumbnail image file [\Z\censored\sorted\GIRO-62
| [Giga] - Armored Heroine Bondage Broken Nifty Domination ANGELA Kayama Yoshisakura (2015)\fanart.jpg]:
| Exception calling "DownloadFile" with "2" argument(s): "An error occurred while sending the request.""
Steps to Reproduce (for bugs)
Run with the standard command: Javinizer -Path "SOURCE" -DestinationPath "DESTINATION"
Note: I run the powershell on Windows 10, but the path and destination path are on UNRaid connected via network.
Your Environment

Module version used: 2.5.7 - cli
Operating System and PowerShell version: Windows 10, PowerShell 7.1.4

Is this a consistent issue?

How many scraper threads are you running?
What scrapers are you using?

It's always consistent when I try to add more than 50 JAVs at the time.
Using default options so 3.
JAVLibrary, R18, DMM

A little update, so apparently the number on queued jobs doesn't matter, any number cause this problem, but it's kinda random, my guess is that the problem is related to where the videos are stored (UNRAID) I couldn't find a fix, but just running the command again and again if it fails, works.

Also getting a new error that doesn't interrupt the sorting, and honestly I don't know why I'm getting it and what it should affect:
Write-Error: C:\Users\X\Documents\PowerShell\Modules\Javinizer\2.5.7\Public\Invoke-JVParallel.ps1:561
Line |
561 |                      Get-RunspaceData
|                      ~~~~~~~~~~~~~~~~
| Cannot index into a null array.

Also getting a new error that doesn't interrupt the sorting, and honestly I don't know why I'm getting it and what it should affect:
Write-Error: C:\Users\X\Documents\PowerShell\Modules\Javinizer\2.5.7\Public\Invoke-JVParallel.ps1:561
Line |
561 | Get-RunspaceData
| ~~~~~~~~~~~~~~~~
| Cannot index into a null array.

I'm aware of this issue, but I'm not quite sure how exactly it's reproduced as of right now. I  haven't noticed it breaking any of the current features so I think it's safe to say to ignore it.


ReadGroup produces unexpected result with aggregate

I’m seeing some unexpected (to me) behavior when benchmarking ReadGroup with count as the aggregate. It seems to do the grouping correctly but will leave one row per original series in its output.
Example: I have two tag keys

t0 cardinality 2
t1 cardinality 5

And then I call ReadGroup, and group by t0 with an aggregate count:
Table: keys: [_start, _stop, t0]
                   _start:time                      _stop:time               t0:string                      _time:time                  _value:int           _field:string     _measurement:string               t1:string
------------------------------  ------------------------------  ----------------------  ------------------------------  --------------------------  ----------------------  ----------------------  ----------------------
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=0)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=1)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=0)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=0)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=0)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=4)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=0)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=3)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=0)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=2)

Table: keys: [_start, _stop, t0]
                   _start:time                      _stop:time               t0:string                      _time:time                  _value:int           _field:string     _measurement:string               t1:string
------------------------------  ------------------------------  ----------------------  ------------------------------  --------------------------  ----------------------  ----------------------  ----------------------
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=1)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=3)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=1)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=0)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=1)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=2)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=1)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=1)
2019-11-25T00:00:00.000000000Z  2019-11-26T00:00:00.000000000Z         a-%!d(string=1)  2019-11-25T00:00:00.000000000Z                          24                      f0                      m0         b-%!d(string=4)

The aggregate function seems to be applied per input series rather than per output series. Certainly Flux expects the latter.

@wolfcm FYI the e2e tests in https://github.com/influxdata/flux/pull/2843 appear to exercise this flaw. Or at least, some flaw in the push down. I can't tell because I don't know how to view the diff in influxdb e2e tests.
To see the failure happen you need to comment out the feature flag tests for the rule as I don't think there is any way to flip on feature flags in e2e tests (yet). Will check into that next week.

Closed via https://github.com/influxdata/influxdb/pull/18342.
ReadGroup still aggregates per series, but now the query planner adds an extra re-aggregation step on the query side when pushing down grouped aggregates to storage.

You fixed https://github.com/influxdata/influxdb/issues/18304, but I think this issue should remain open. I expect that we'll want to fix storage to aggregate per output series at some point, since it will be a big win for performance, and this issue should only close when we do that work.


array (numoy) operations support

Hello all,
Thanks a lot of this library, I was planning to implement something similar for a project of mine when I found this and it is very useful.
I am trying to use it with ndarrays from numpy and found few shortcomings with workarounds, I am not sure if there are better workarounds or tips for this:

ndarray slicing:
It is great that the library can handle and uses numpy arrays in the backend. However, slicing can be problematic. E.g: I have a 2d array A of size [M,N] and use A_fxp = Fxp(A). This works wonders and as I understand A is stored as ndarray inside the Fxp object. Now If I slice this as C = A_fxp[0] it generates an ndarray of size N. I thought this would generate a Fxp object with the same proprieties as A_fxp containing the vector of length N. My workaround: C = Fxp(A_fxp[0], like=A_fxp) which is not so bad for me but might cause issues when using functions with no control over slicing inside them. Is there a better way to do this currently?

Updating the values of ndarray inside Fxp object:
Updating a value numpy ndarray inside of Fxp object does not accept Fxp object. in the same example above (A = [M,N] and use A_fxp = Fxp(A)). x = Fxp(4). A_fxp[0,0] =  x does not work. My Workaround: A_fxp[0,0] =  x(). Again, this is not bad but I think it would be better if it casts the Fxp object to allow the update.

Performace:
E.g.: Using the same array A = [M,N],

A_fxp = Fxp(A)
for i in range(M):
    for j in range(N):
         for x in range(10000): # a lot of iterations
             A_fxp[j,j] = A_fxp[j,j] + some_variable

This is very slow. I am not sure what is going in the background. Does the object update (evaluate) the whole array to make sure rounding is correct for every time an update to one value takes place?

Hello MaenMallah,
First of all, thank you for the feedback.
ndarray slicing:
Yes, you're right. In the slicing that operation should return a Fxp object. It should be include that in next release.
Updating the values of ndarray inside Fxp object:
Yes, the cast should be supported here. In that case you should be carefull if A and x have different characteristics; for i.e in your expample format of A_fxp depends of values of A (best format was found), and format of x will be likely different. It should be also included in next release.
Performance:
Yes... very slow! I've checked it and when you change one or more values, all array is update and stored again. In that process, the rounding is performed again and overflow checked again. It's pretty sure there is a better way to do it. I'll try to figure it out.

Hello @MaenMallah ,
All the points now are supported in version 0.3.7.
I get a better performance in the slice settings.
Please check if the issue is solved for you.

Hello @francof2a,
Thanks a lot of addressing them this fast. I will test and let you know. Sorry I didn't answer earlier, I just noticed your early answer. Please keep the good work going.

Hello @francof2a,
When I tested slicing I got the following error:
y[0]
Traceback (most recent call last):
File "", line 1, in
y[0]
File "C:\ProgramData\Anaconda3\lib\site-packages\fxpmath\objects.py", line 761, in getitem
return Fxp(self.get_val()[index], like=self)
File "C:\ProgramData\Anaconda3\lib\site-packages\fxpmath\objects.py", line 131, in init
self.set_val(val)
File "C:\ProgramData\Anaconda3\lib\site-packages\fxpmath\objects.py", line 330, in set_val
val_max =  (1 << self.n_word) - 1
TypeError: unsupported operand type(s) for <<: 'int' and 'NoneType'
I tired initializing y with a list and numpy array and both threw errors.

Could you please paste whole code? I couldn't reproduce that error.

Hello @francof2a, I tried replicating this on a different machine and it worked fine. I am not sure what was wrong with my first setup. I will test again there and notify if this is working as expected.

Hello @MaenMallah ,
do you have any news about this issue? If not, please, let me close the issue.


zephyr: unable to build simple example targeting the nucleo_f767zi board with libc wasi

I am trying to build the product-mini/platforms/zephyr/simple example targeting the nucleo_f767zi board with WAMR_BUILD_LIBC_WASI so that a WASM module compiled for wasi can execute on the board itself.
This is the command I am trying to use to build:
ZEPHYR_BASE=~/zephyrproject/zephyr west build -b nucleo_f767zi . -p always -- -DWAMR_BUILD_TARGET=THUMBV7 -DWAMR_BUILD_LIBC_WASI=1

However, the code is unable to build without errors:
-- Zephyr version: 3.5.99 (/home/ron/zephyrproject/zephyr), build: zephyr-v3.5.0-2399-gc94cd30cecbf
[30/177] Building C object CMakeFiles/app.dir/home/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c.obj             FAILED: CMakeFiles/app.dir/home/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c.obj
ccache /home/ron/zephyr-sdk-0.16.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DBH_FREE=wasm_runtime_free -DBH_MALLOC=wasm_runtime_malloc -DBH_PLATFORM_ZEPHYR -DBUILD_TARGET=\"
THUMBV7\" -DBUILD_TARGET_THUMB -DCORE_CM7 -DHSE_VALUE=8000000 -DKERNEL -DPICOLIBC_LONG_LONG_PRINTF_SCANF -DSTM32F767xx -DUSE_FULL_LL_DRIVER -DUSE_HAL_DRIVER -DWASM_DISABLE_H
W_BOUND_CHECK=0 -DWASM_DISABLE_STACK_HW_BOUND_CHECK=0 -DWASM_DISABLE_WAKEUP_BLOCKING_OP=0 -DWASM_ENABLE_AOT=1 -DWASM_ENABLE_BULK_MEMORY=1 -DWASM_ENABLE_FAST_INTERP=0 -DWASM_
ENABLE_GLOBAL_HEAP_POOL=1 -DWASM_ENABLE_INTERP=1 -DWASM_ENABLE_LIBC_BUILTIN=1 -DWASM_ENABLE_LIBC_WASI=1 -DWASM_ENABLE_MINI_LOADER=0 -DWASM_ENABLE_MODULE_INST_CONTEXT=1 -DWASM_ENABLE_MULTI_MODULE=0 -DWASM_ENABLE_SHARED_MEMORY=0 -DWASM_GLOBAL_HEAP_SIZE=131072 -D_FORTIFY_SOURCE=1 -D_POSIX_C_SOURCE=200809 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_ST
ART -D__ZEPHYR__=1 -I/home/ron/Development/wasm-micro-runtime/core/iwasm/interpreter -I/home/ron/Development/wasm-micro-runtime/core/iwasm/aot -I/home/ron/Development/wasm-m
icro-runtime/core/iwasm/libraries/libc-builtin -I/home/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/include -I/home/ron/Deve
lopment/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src -I/home/ron/Development/wasm-micro-runtime/product-mini/platforms/zephyr/simple/../
../../../core/iwasm/include -I/home/ron/Development/wasm-micro-runtime/core/shared/platform/zephyr -I/home/ron/Development/wasm-micro-runtime/core/shared/platform/zephyr/../
include -I/home/ron/Development/wasm-micro-runtime/core/shared/mem-alloc -I/home/ron/Development/wasm-micro-runtime/core/iwasm/common -I/home/ron/Development/wasm-micro-runt
ime/core/shared/utils -I/home/ron/zephyrproject/zephyr/include -I/home/ron/Development/wasm-micro-runtime/product-mini/platforms/zephyr/simple/build/zephyr/include/generated
 -I/home/ron/zephyrproject/zephyr/soc/arm/st_stm32/stm32f7 -I/home/ron/zephyrproject/zephyr/drivers -I/home/ron/zephyrproject/zephyr/soc/arm/st_stm32/common -I/home/ron/zeph
yrproject/modules/hal/cmsis/CMSIS/Core/Include -I/home/ron/zephyrproject/zephyr/modules/cmsis/. -I/home/ron/zephyrproject/modules/hal/stm32/stm32cube/stm32f7xx/soc -I/home/r
on/zephyrproject/modules/hal/stm32/stm32cube/stm32f7xx/drivers/include -I/home/ron/zephyrproject/modules/hal/stm32/stm32cube/stm32f7xx/drivers/include/Legacy -I/home/ron/zep
hyrproject/modules/hal/stm32/stm32cube/common_ll/include -isystem /home/ron/zephyrproject/zephyr/lib/libc/common/include -std=gnu99 -ffunction-sections -fdata-sections
                                    -Wall -Wno-unused-parameter -Wno-pedantic -mthumb -fno-strict-aliasing -Os -imacros /home/ron/Development/wasm-micro-runtime/product-mini
/platforms/zephyr/simple/build/zephyr/include/generated/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m7 -mthumb -mabi
=aapcs -mfp16-format=ieee -mtp=soft --sysroot=/home/ron/zephyr-sdk-0.16.4/arm-zephyr-eabi/arm-zephyr-eabi -imacros /home/ron/zephyrproject/zephyr/include/zephyr/toolchain/ze
phyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit
-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=/home/ron/Devel
opment/wasm-micro-runtime/product-mini/platforms/zephyr/simple=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/ron/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/ron/ze
phyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections --specs=picolibc.specs -std=c99 -MD -MT CMakeFiles/app.dir/home/ron/Development/wasm-micro-runtime/core/iwasm/lib
raries/libc-wasi/sandboxed-system-primitives/src/posix.c.obj -MF CMakeFiles/app.dir/home/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-p
rimitives/src/posix.c.obj.d -o CMakeFiles/app.dir/home/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c.obj -c /home
/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c
/home/ron/Development/wasm-micro-runtime/core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c:18:10: fatal error: libc_errno.h: No such file or directory
   18 | #include "libc_errno.h"
      |          ^~~~~~~~~~~~~~
compilation terminated.
....

Any ideas? Thanks in advance!

If I try to execute my WASM code compiled targeting wasi I get the following log from the board:
Connected to /dev/ttyACM0. Press Ctrl-C to exit.
*** Booting Zephyr OS build zephyr-v3.5.0-2399-gc94cd30cecbf ***
WASM module instantiate failed: allocate memory failed
elapsed: 14

If I compile iwasm for Linux, and I set WAMR_BUILD_LIBC_WASI 0 then I get the following error:
$ ./iwasm ../../../app-samples/hello-world-tinygo/test.wasm
[16:13:34:719 - 7FCAE7617B80]: warning: failed to link import function (wasi_snapshot_preview1, fd_write)
Exception: lookup the entry point symbol (like main, _main, __main_argc_argv) failed

If I compile iwasm with WAMR_BUILD_LIBC_WASI 1 then the code executes as I expect:
$ ./iwasm ../../../app-samples/hello-world-tinygo/test.wasm
Hello world!

@deadprogram thanks for reporting! I've been working on the zephyr support and will look into this!

Hello @hasheddan any updates on this by any chance? :smile_cat:

:wave: :smiley_cat:

@deadprogram thank you for the ping and my apologies on the delay here! I have just opened #3086 to address the primary issue you encountered here, but am also investigating additional rough spots regarding WASI support with Zephyr. Feel free to try out the patch and report any further problems you encounter!

Hello, I have the same issue with build to qemu_cortex_a53 :(
I am running the latest wamr version (I've just pulled from main branch)

Is there any update on this issue?  I'm having similar problems building with WAMR_BUILD_LIBC_WASI 1 on Zephyr.  I'm still targeting WASI preview 1 so I'm on the release/1.3.x branch.


Clean Up Unnecessary Commented Code

Ticket no longer needed. Work will be completed in Code Clean Up-PI 6 #2375


Add support for typesystem

This could be connected to the work that @loradd is doing for symbol resolution

Within the context of releasing Kolasu 1.6 we should identify possible changes to the API that could be necessary to later enable the implementation of the typesystem. Adding APIs is not necessarily something we should do before releasing 1.6.
I would think that annotations could be something useful to add for storing the computer types.
@loradd do you have thoughts about this?


fix: handle missing package.json file when checking for version

Which problem is this PR solving?

In some cases (typically, AWS lambda; but can potentially happen in other cases) the package.json file may be missing at runtime for a certain module. Currently OTEL crashes in this case, unnecessarily.
See discussion - https://github.com/open-telemetry/opentelemetry-js/issues/2193

Short description of the changes

In case the module's version is missing (due to a missing package.json file), we patch the module/file if and only if the supported versions contain a wildcard (*). Until now, an exception was thrown, crashing the app.
Added tests that cover these scenarios/

@Rauno56 👍

@nozik You'll need to rebase the PR (or give us access to your fork so we can do it for you)

@vmarchaud done

@obecny Done


add: functional API wrapper

@pugio has often talked about having a nice functional wrapper (ala ruby) in a python context. My first attempt at this failed because I was trying to stick to the existing type system. Let's see if we can do better by just making a wrapper object.
constructors

[x] __init__
[x] copy
[x] wrap
[x] fromkeys

contents

[x] __repr__
[x] __len__
[x] __contains__
[x] __iter__
[x] __eq__
[x] keys
[x] values
[x] items
[x] attr
[x] count
[ ] get

select

[ ] first
[ ] last
[ ] take
[ ] drop
[ ] uniq
[ ] filter
[ ] index

apply

[ ] map
[ ] reduce
[ ] each
[ ] group

format

[ ] sort
[ ] reverse
[ ] compact
[ ] flatten
[ ] zip
[ ] join

add

[ ] push
[ ] append
[ ] concat
[ ] extend
[ ] insert
[ ] setdefault
[ ] __add__
[ ] __iadd__

remove

[ ] pop
[ ] popitem
[ ] delete
[ ] remove
[ ] clear

modify

[ ] update
[ ] __imul__
[ ] __rmul__

Upon reflection, this is definitely me getting nerd sniped. I don't actually have a concrete use case for this, but it's a lot of fun to work on.

Closed via 792046ee93bb3e85bc9fedf8cc622d57d417bf9a


css imported from a node module is not served correctly with vite dev

Describe the bug
My html links to a stylesheet provided by a node module:
<link rel="stylesheet"<EMAIL_ADDRESS>
The server started by vite dev does not serve this file correctly, see steps below. vite build however correctly bundles this into the output. I would expect that vite dev behaves the same as vite build followed by vite preview.
Reproduction
https://github.com/andreashuber69/vite-dev-bug-repro
Steps to reproduce
git clone https://github.com/andreashuber69/vite-dev-bug-repro.git
cd vite-dev-bug-repro
npm install
npm run dev

The above steps will open a browser. If you inspect via the browser dev tools, you will see that the referenced stylesheet @picocss/pico/css/pico.min.css is not served correctly (the browser instead shows the contents of index.html).
If you however run the following commands...
npm run build
npm run preview

... the referenced stylesheet is correctly bundled and served.
System Info
System:
    OS: Linux 6.6 Pop!_OS 22.04 LTS
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 22.65 GB / 31.20 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.11.1 - /usr/local/bin/node
    npm: 10.2.4 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
  npmPackages:
    vite: ^5.1.4 => 5.1.5

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

are you using docker in this much memory only
Try it without reproducing

are you using docker in this much memory only Try it without reproducing

I'm not sure I follow. I'm not using docker. Did you try to reproduce it with the "Steps to reproduce"?

This inconsistency may be reasonably a bug, but if you're looking for a workaround, I think you can use more explicit path or side effect import, something like this:
https://stackblitz.com/edit/github-adr9cy?file=index.html
<link rel="stylesheet"<EMAIL_ADDRESS>
<script type="module">
  import<EMAIL_ADDRESS></script>

Duplicate of #12260


add new privacy policy link on top banner

Description
New GDPR privacy policy link
Benefits
Users can enjoy reading the updated policy
Possible Drawbacks
We may lose users if they don't accept the privacy policy
Testing
Tested successfully in sandbox

Merged as the test failures unrelated to the current changes.


Installation cannot continue after the installer reboot

The installation cannot continue after the installer reboot.
Test Version: 11.6.2 12.0.1
The log at the second boot

It seems that I meet the same problem when installing macOS Ventura. Have you solved that?

Try using the new EFI

Try using the new EFI

2.1.0 ? This is the version I was using before.

Try using the new EFI

2.1.0 ? This is the version I was using before.

What CPU you using? intel 10th or intel 8th?

Try using the new EFI

2.1.0 ? This is the version I was using before.

What CPU you using? intel 10th or intel 8th?

What if I'm using the 10th CPU? Intel i5-10210U, thx

Try using the new EFI

2.1.0 ? This is the version I was using before.

What CPU you using? intel 10th or intel 8th?

What if I'm using the 10th CPU? Intel i5-10210U, thx

Nothing wrong. It's just that I haven't tested the work on the eighth generation, that's why I'm asking. Most likely you have a problem with your installer. Try to use some other one.

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing?
Message ID: @.***>

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing? Message ID: @.***>

As far as I know, not everyone has this problem. Unfortunately, I have not yet been able to understand why it occurs. If you find a solution on the forums, you can offer it.

Try using the new EFI

2.1.0 ? This is the version I was using before.

Most likely you have a problem with your installer. Try to use some other one.

I got confused in the comments)

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing? Message ID: @.***>

You can roll back to big sur. Everything works fine on this OC.

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing? Message ID: @.***>

As far as I know, not everyone has this problem. Unfortunately, I have not yet been able to understand why it occurs. If you find a solution on the forums, you can offer it.

Accroding to this blog, it is the new shutdown method on Monterey that results in the annoying problem.
https://hpglw.com/3a0d9306.html
And this one gives a suggestion —— using the new VoodooPS2Controller.kext, add kbd_fixdisable=1 to boot-args. I don't know whether it will work or not.
https://zhuanlan.zhihu.com/p/581274059

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing? Message ID: @.***>

You can roll back to big sur. Everything works fine on this OC.

Exactly. Thank you for your work. 👍

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing? Message ID: @.***>

As far as I know, not everyone has this problem. Unfortunately, I have not yet been able to understand why it occurs. If you find a solution on the forums, you can offer it.

Accroding to this blog, it is the new shutdown method on Monterey that results in the annoying problem. https://hpglw.com/3a0d9306.html
And this one gives a suggestion —— using the new VoodooPS2Controller.kext, add kbd_fixdisable=1 to boot-args. I don't know whether it will work or not. https://zhuanlan.zhihu.com/p/581274059

Unfortunately, I won't be able to check this in the near future, but thank you for a possible solution to this problem.

OK. By the way, when I reboot on Monterey, the keyboard doesn't work on OpenCore picker. The F2 and F12 key cannot work, either. So I have to use a mouse instead. Is that a common failing? Message ID: @.***>

You can roll back to big sur. Everything works fine on this OC.

Exactly. Thank you for your work. 👍

😉

Try using the new EFI

2.1.0 ? This is the version I was using before.

What CPU you using? intel 10th or intel 8th?

My CPU is also i5-10210u, but I keep having the problems. I can't complete the installation.

It seems that I meet the same problem when installing macOS Ventura. Have you solved that?

Have you solved the installation problem?

It seems that I meet the same problem when installing macOS Ventura. Have you solved that?

Have you solved the installation problem?

Not yet. Due to so many problems, I rolled back to Big Sur. I think all is fine on Big Sur.

It seems that I meet the same problem when installing macOS Ventura. Have you solved that?

Have you solved the installation problem?

Not yet. Due to so many problems, I rolled back to Big Sur. I think all is fine on Big Sur.

I also tested Big Sur, but the same error occurs. There are some answers that say it's a BIOS problem.

It seems that I meet the same problem when installing macOS Ventura. Have you solved that?

Have you solved the installation problem?

Not yet. Due to so many problems, I rolled back to Big Sur. I think all is fine on Big Sur.

I also tested Big Sur, but the same error occured. There are some answers that say it's a BIOS problem.

I know what you mean. Maybe there is still some problems. You can complete the Big Sur installation by using this CLOVER EFI.
https://st7530.lanzout.com/icebg0hcjzze

Thank you for your work.

Thank you for your work. :relaxed:

@FluffyCuteOwO Using the latest EFI (2.2.0, pre-released), I can now complete the Ventura installation normally. The keyboard problem has also been solved. THANKS!

@FluffyCuteOwO Using the latest EFI (2.2.0, pre-released), I can now complete the Ventura installation normally. The keyboard problem has also been solved. THANKS!

you are welcome


Fix build warnings of chars and make_strings_column

Fixes #1724
There are many warnings when building jni now because cudf deprecated cudf::make_strings_column with typed offsets and cudf::strings_column_view::chars.
This PR replace those api usage with non-deprecated apis.

build

Please provide more PR description.

@ttnghia Thanks for review, updated description.


Packer throwing error while provisioning goss during cicd.

When trying to use Goss provision as below in template.json  for Packer , I am getting the below error: Any thoughts / suggestions- how to fix it. TIA
Code:

{
  "variables": {
    "aws_access_key": "",
    "aws_secret_key": "",
    "token": ""
  },
  "builders": [
    {
      "type": "amazon-ebs",
      "access_key": "{{user `aws_access_key`}}",
      "secret_key": "{{user `aws_secret_key`}}",
      "token": "{{user `token`}}",
      "region": "us-east-1",
      "source_ami_filter": {
        "filters": {
          "virtualization-type": "hvm",
          "name": "amzn2-ami-hvm-2.0.*.1-x86_64-ebs",
          "root-device-type": "ebs"
        },
        "owners": [
          "amazon"
        ],
        "most_recent": true
      },
      "instance_type": "t2.micro",
      "ssh_username": "{{user `ssh_username`}}",
      "ami_name": "packer-example {{timestamp}}",
    "tags":{
    "Name": "nginx-ami-packer - {{timestamp}}"
    }
    }
  ],
  "provisioners": [
    {
      "type": "shell",
      "script": "nginx.sh"
    },
    {
      "type": "goss",
      "tests": [
        "goss/goss.yaml"
      ]
    }
  ]
}

Error:
Tor-Ranopriyo-MBP13:packer-ami ranopriyoneogy$ packer build -var-file=vars.json template.json
Error: Failed to initialize build "amazon-ebs"

error initializing provisioner 'goss': Unknown provisioner goss

==> Wait completed after 375 microseconds

==> Builds finished but no artifacts were created.

Closing this issue - Fixed it by installing correct version of packer-provisioner-goss from https://github.com/YaleUniversity/packer-provisioner-goss/releases/tag/v3.0.2 . Thanks


UP status incorrectly given to anything in 2.0-alpha.2

What did you do?
Misconfigured Prometheus 2.0-aplha.2 such that it attempts to scrape a host does not exist. It was then marked as UP even though it should not have been.
What did you expect to see?
Items marked appropriately in the /status page (UP iff they're up and DOWN iff they're down)
What did you see instead? Under which circumstances?
Everything is marked as UP regardless of whether that's actually true or not.  You can replicate easily by using a host name that isn't reachable. You can use the config below.

Prometheus version:

prometheus, version 2.0.0-alpha.2 (branch: HEAD, revision: ab0ce4a8d9858956b37b545cfb84bb4edb5d7776)
build user<EMAIL_ADDRESS>build date:       20170525-21:21:28
go version:       go1.8

Prometheus configuration file:

scrape_configs:
- job_name: "up-test"
  static_configs:
  - targets: ['does.not.exist']

This was fixed.

How to build dev 2.0 . I just build a 1.7 version.


Add support for versions for official Arch packages

Hi, thanks for this contribution. Would be great to get this merged.
Would you be willing to add tests using the project's new testing framework?

If anyone would like to adopt this PR, please feel free to do so: grab the branch, add more commits addressing the comments, and open a new PR referencing this one.


Install CMake Config, raise minimum required version to v3.0

Raise minimum CMake version to 3.0
Install a Config module to make the tools findable by CMake find_package()
Use find_package() for the headers

Implement a fallback for older versions of the header

Minor cleanups throughout the build scripts

I'd say it closes #2662 since it does install a Config file, but there's still a lot of cleanup possible.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The Android build failed with the following message:
FAILED: source/libSPIRV-Tools-shared.so
208
: && CMAKE_C_COMPILER -fPIC -fexceptions -frtti -fpic -Wno-psabi --sysroot=/opt/android-ndk-r15c/platforms/android-14/arch-arm -funwind-tables -finline-limit=64 -fsigned-char -no-canonical-prefixes -march=armv7-a -mfloat-abi=softfp -mfpu=neon -fdata-sections -ffunction-sections -Wa,--noexecstack  -mthumb -fomit-frame-pointer -fno-strict-aliasing -O3 -DNDEBUG  -Wl,--fix-cortex-a8 -Wl,--no-undefined -Wl,-allow-shlib-undefined -Wl,--gc-sections -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,libSPIRV-Tools-shared.so -o source/libSPIRV-Tools-shared.so source/CMakeFiles/SPIRV-Tools-shared.dir/util/bit_vector.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/util/parse_number.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/util/string_utils.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/assembly_grammar.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/binary.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/diagnostic.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/disassemble.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/enum_string_mapping.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/ext_inst.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/extensions.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/libspirv.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/name_mapper.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/opcode.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/operand.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/parsed_operand.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/print.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/software_version.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/spirv_endian.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/spirv_fuzzer_options.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/spirv_optimizer_options.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/spirv_reducer_options.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/spirv_target_env.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/spirv_validator_options.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/table.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/text.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/text_handler.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_adjacency.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_annotation.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_arithmetics.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_atomics.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_barriers.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_bitwise.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_builtins.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_capability.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_cfg.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_composites.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_constants.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_conversion.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_datarules.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_debug.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_decorations.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_derivatives.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_extensions.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_execution_limitations.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_function.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_id.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_image.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_interfaces.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_instruction.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_layout.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_literals.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_logicals.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_memory.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_memory_semantics.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_misc.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_mode_setting.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_non_uniform.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_primitives.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_scopes.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_small_type_uses.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validate_type.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/basic_block.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/construct.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/function.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/instruction.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/val/validation_state.cpp.o source/CMakeFiles/SPIRV-Tools-shared.dir/util/timer.cpp.o -L/libs/armeabi-v7a  "/opt/android-ndk-r15c/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi-v7a/libgnustl_static.a" "/opt/android-ndk-r15c/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi-v7a/libsupc++.a" -lm && :
209
/bin/sh: 1: CMAKE_C_COMPILER: not found

I see the failure on Android and made a few stabs on fixing it, but this error confuses me. It's probably related to one of the linker overrides in the android toolchain file misbehaving, but in order to be able to debug this I need to install the Android NDK first.

Update: I installed the NDK on my machine and tried to reproduce the failure on CI-android. So Everything Works On My Machine :tm: .
So I'll have to try out a few more things to track that issue down.

There is a bunch of things going on in this CL, would it make sense to break it apart? Make a Cl which splits out the various Find scripts. Make a CL to bump the version of CMake. Make a CL to do the install things? May make it easier to track down why the Android bot is unhappy.

@mmha Any update on this PR?

This has gone stale.  Android build is still failing, and no update in over a year.


New endpoint: resolve HGNC aliases and previous IDs

Statement of problem
Genes in HGNC can be identified by:

current HGNC ID
symbol
alias
prior symbols

Provide alias and prior IDs based on the current HGNC ID.
Solution
It appears that information on previous symbols and aliases for HGNC genes is available in UBKG as terms of differing semantic types. For example, the previous symbol corresponds to the name of a term node with relationship type NS.
The UBKG API will need a new endpoint that organizes HGNC information by type.

Sample Cypher query for HGNC HGNC:7178:
match(t:Term)<-[r]-(c:Code) where type(r) in ['PT','ACR','SYN','NS'] AND c.CodeID='HGNC HGNC:7178' RETURN c.CODE AS Code, CASE type(r) WHEN 'PT' THEN 'name' WHEN 'ACR' THEN 'symbol' WHEN 'NS' THEN 'previous' WHEN 'SYN' THEN 'alias' ELSE type(r) END AS type, t.name AS value ORDER BY type(r)

result:
[
  {
    "Code": "HGNC:7178",
    "type": "symbol",
    "value": "MMRN1"
  },
  {
    "Code": "HGNC:7178",
    "type": "previous",
    "value": "MMRN"
  },
  {
    "Code": "HGNC:7178",
    "type": "name",
    "value": "multimerin 1"
  },
  {
    "Code": "HGNC:7178",
    "type": "alias",
    "value": "EMILIN4"
  },
  {
    "Code": "HGNC:7178",
    "type": "alias",
    "value": "GPIa*"
  },
  {
    "Code": "HGNC:7178",
    "type": "alias",
    "value": "ECM"
  }
]

https://github.com/x-atlas-consortia/ubkg-api/issues/45


Python error thrown with az role assignment create

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az role assignment create
Errors:
The command failed with an unexpected error. Here is the traceback:
'RoleAssignmentsOperations' object has no attribute 'config'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 658, in execute
    raise ex
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 692, in _run_job
    result = cmd_copy(params)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/lib/python3/dist-packages/azure/cli/command_modules/role/custom.py", line 166, in create_role_assignment
    return _create_role_assignment(cmd.cli_ctx, role, object_id, resource_group_name, scope, resolve_assignee=False,
  File "/usr/lib/python3/dist-packages/azure/cli/command_modules/role/custom.py", line 183, in _create_role_assignment
    assignments_client.config.subscription_id)
AttributeError: 'RoleAssignmentsOperations' object has no attribute 'config'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az role assignment create --role {} --assignee {} --scope {}

Expected Behavior
Environment Summary
Linux-5.15.15-1rodete1-amd64-x86_64-with-glibc2.33, Debian GNU/Linux rodete
Python 3.9.9
Installer: DEB

azure-cli 2.32.0 *

Extensions:
azure-devops 0.22.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

uninstalled and then reinstalled using this method and it works now

@jiasli for awareness

See https://github.com/Azure/azure-cli/issues/19640

Been seen the same behavior while running az login in a PowerShell session
az login --service-principal --username $Env:spnClientID --password $Env:spnClientSecret --tenant $Env:spnTenantId

Issues in the last day or so with similar behavior:
https://github.com/Azure/azure-cli/issues/21306
https://github.com/Azure/azure-cli/issues/21331
https://github.com/Azure/azure-cli/issues/21332
https://github.com/Azure/azure-cli/issues/21333
Possibly some systemic issue with the latest Azure CLI release?

Thanks for clarifying @jiasli!

See #19640
I searched for Debian GNU/Linux rodete but didn't get too much useful info. May I know what system this is?

@jiasli  yep:
$ uname -a
Linux bionj1 5.15.15-1rodete1-amd64 #1 SMP Debian 5.15.15-1rodete1 (2022-01-20) x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux rodete
Release:	rodete
Codename:	rodete

$ arch
x86_64

I have a patch for this at https://github.com/Azure/azure-cli/issues/22231#issuecomment-1113136152


[IMPROVEMENT] ctrl+f search result full width switch

I would like to be able to spot ctrl+f search results more easily by seeing them colored in full width, rather than only part matching search being colored.

duplicate #74


Task5

Issue: #6
Executed the given commands

Hey @Ishu0112
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @Ishu0112
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Fix InvalidPathException using BSP on Windows.

Fix invalid windows path produced by URL#getFile in mill.bsp.ModuleUtils#getMillBuildClasspath, fixing #1091 and #1021

Looks reasonable. I'd would be great, to also have a test case for that.

Yes. Paths can be capricious between opération systems.

Looks reasonable. I'd would be great, to also have a test case for that.

Yes. Paths can be capricious between opération systems.

Looks reasonable. I'd would be great, to also have a test case for that.

Yes. Paths can be capricious between operating systems. Maybe this test and change should be applied to the oslib.

Are you going to create a PR for oslib?

Looks reasonable. I'd would be great, to also have a test case for that.

Yes. Paths can be capricious between operating systems. Maybe this test and change should be applied to the oslib.

Are you going to create a PR for oslib?

Looks reasonable. I'd would be great, to also have a test case for that.

Yes. Paths can be capricious between operating systems. Maybe this test and change should be applied to the oslib.

@Iltotore Are you going to create a PR for oslib?

If you think it is better than pushing changes here, yes.

Looks reasonable. I'd would be great, to also have a test case for that.

Yes. Paths can be capricious between operating systems. Maybe this test and change should be applied to the oslib.

@Iltotore Are you going to create a PR for oslib?

If you think it is better than pushing changes here, yes.

It's a misbehavior there and should be fixed there.

It's a misbehavior there and should be fixed there.

Superseded by https://github.com/com-lihaoyi/mill/pull/1285 and also by upstream PR https://github.com/com-lihaoyi/os-lib/pull/53.

@Iltotore Thank you for your work on this topic! Although we fixed the issue now without any of your commits, your work is highly appreciated.


feat(FMP-415): when amount changes, predict fees

Current dependencies on/for this PR:

main

PR #77   👈

This comment was auto-generated by Graphite.


Add (No) Code of Conduct

https://nocodeofconduct.com

is this to please github (because code of conduct is mandatory or like that) ?

Fortunately it's not mandatory, it's just to make it clear that we only care about what (really) matters.


Better surface parser failures

Type of Issue
Select the type of issue:

[ ] Bug report (to report a bug)
[ ] Feature request (to request an additional feature)
[x] Tracker (I am just using this as a tracker)
[ ] Refactor request
[ ] Documentation Ask

Description
From conversation with @kavyasrinet: let's figure out a better way to surface and track parser failures.
Previous proposed solution was to have engineers directly write to ground truth using Autocomplete. Problem is that our grammar changes quickly, so the onboarding cost is not sustainable. It is also not sustainable to have a few people routinely add commands from issues to ground truth.
Another idea is to decide on a set of important commands. The problem with our lists of "high pri" commands now is that for everything deemed high pri, we already have it in ground truth. A more scalable approach might be to

Consider space of possible commands, instead of checking for exact matches. eg. "follow the X" might be essential for anything in the world that is X.
Do not add every failed command from an issue to ground truth, only if it is within the space of commands we really need in ground truth.
Alternatively, we don't add commands to ground truth from model issue trackers, and instead add them to model unit test. Test is not blocking but provides signal into how current model is doing.

Checklist
TBD, will add subtasks once this is clear

[ ] Come up with a scalable approach for handling model failures.
[ ] Implement solution

cc @anuragprat1k , @aszlam


Document that redirects are not supports when interlock is configured for TLS passthrough

File: ee/ucp/interlock/usage/redirects.md
There is currently a limitation where redirects do not work if a service is configured for TLS passthrough in interlock proxy.
This limitation should be noted in the documentation.
A support case indicated that this is currently an existing feature request tracked by reference number FIELD-280

https://docker.atlassian.net/browse/FIELD-280

@trapier @dani-docker @euanh PTAL at this issue.

@traci-morrison this issue report is accurate.   There is a KB on the issue at https://success.docker.com/article/interlock-support-for-http-redirect-to-tls-passthrough

Yes, this report is accurate.   There is a fix in master, and all things going well it will be in the next Interlock release.

WIP: https://github.com/docker/docker.github.io/pull/10048

Completed in https://github.com/docker/docker.github.io/pull/10048.