router: add support for virtual cluster based on virtual host headers

Commit Message: add support for virtual cluster based on virtual host headers
Additional Description: Currently virtual cluster is determined based on downstream headers. But we have a usecase to generate stats based on the headers added in virtual host. This PR enables that.
Risk Level: Low
Testing: Added integration test
Docs Changes: N/A
Release Notes: Added

/retest

/assign-from envoyproxy/senior-maintainers
for new feature review

LGTM from me. I will also ask someone else to review who is more familiar with this functionality.


module overrides load_balancers configuration for self managed node group ASGs

Description
Since the new module version v18.x doesn't support attaching classic load balancers to ASGs. We have to separately attach load balancers using the aws_autoscaling_attachment terraform resource.
However, for terraform-aws-eks managed ASGs, every time we run a terraform apply, the module removes this association leading to the load balancers being removed from ASGs, causing an outage.

[x] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
This is relevant for self managed node group ASGs.
Versions

Module version [Required]:

Terraform version:
<1.1.3

Provider version(s):
v18.18.x

Reproduction Code [Required]
Create a new alb_attachment.tf
resource "aws_autoscaling_attachment" "test" {
  count                                  = length(module.eks.self_managed_node_groups_autoscaling_group_names)
  autoscaling_group_name                 = module.eks.self_managed_node_groups_autoscaling_group_names[count.index]
  elb                                    = "elb-arn"
}

Steps to reproduce the behavior:

Add the above  configuration to your eks module usage.
Run terraform apply.
Run terraform plan.
Notice the module try to remove the previously created ELB->ASG association.

Using Workspaces

Cache cleared.

See steps above for reproducing this issue.
Expected behavior
Module should ignore changes to ELB associations with ASG since it's no longer managing this part of the configuration.
Actual behavior
Module overrides externally added config for ELB-> ASG association.

Created a PR to resolve this issue.
https://github.com/terraform-aws-modules/terraform-aws-eks/pull/2218

I will post the question I left on the PR here as well - I'm curious, do you not utilize the AWS load balancer controller for ingress?

I will post the question I left on the PR here as well - I'm curious, do you not utilize the AWS load balancer controller for ingress?

We do. But some of the clusters do not have load balancer controllers so we have to attach long-lived load balancers deployed separately using terraform.

see comment here https://github.com/terraform-aws-modules/terraform-aws-eks/pull/2218#issuecomment-1238650527


Update Table partitions doc re: how to avoid in-between spans for scans of partitioned tables

In versions of CRDB < 21.1, to avoid the latency hit of scanning spans that are in between partitions, you must either:

use an enum type and a not null constraint
add a check constraint and a not null (if you aren't using enums for some reason)

This is necessary because in versions < 21.1, the optimizer
doesn't know that there are no other possible values for the
tenancy unless you define the possible values strictly as
described above.
This will not be necessary for v21.1+ clusters that use the new multi-region features.
Note: I have not carefully read the Define table partitions doc, so some or all of this info may be there (or implied).  It does seem to be implied, but in a rather subtle way, by

: Enumerate all possible values for each partition. List partitioning is a good choice when the number of possible values is small.

Also, the limitation that you can't use ENUMs appears to be fixed (see linked CRDB ticket from the doc).
See also:

cockroachdb/docs#9205
cockroachdb/docs#9207

@ericharmeling I pulled this into my world but I'm kinda treating it as backlog since it is technically multi-region but not "new cool multi-region" - I noticed you have some other partitioning docs, so let me know if this should come over to you / SQL Docs - world instead

Just a small correction:
Prior to 21.1, it was not possible to use an enum column as the partitioning column. In 20.2, this gives the error "partitioning by enum values is not supported". So only option 2 would be available to users.
In 21.1, if not using the new multi-region patterns, either of the options you listed would work.

I believe this is still relevant, since many clusters still use partitioning.


How to mount multiple tiddlywikis instead of 1 with 2.1

Could someone provide some examples for the new tree syntax on how to mount 2 tiddlywikis? Before that it was super easy with
{
  "tree": {
       "Testrunde": ".\\tiddlywiki\\wiki\\story\\testrunde",
       "Testrunde2": ".\\tiddlywiki\\wiki\\story\\testrunde2"
  },
  "bindInfo": {
		"bindWildcard": true
  },
  "putsaver": {
    "backupDirectory": "../backups"
  },
  "$schema": "./settings.schema.json"
}

This syntax is not supported in 2.1 anymore it fails loading with
{
  Testrunde: '.\\tiddlywiki\\wiki\\story\\testrunde',
  Template: '.\\tiddlywiki\\wiki\\template\\testrunde'
}
 APP 2019-08-25 12:03:33 Uncaught error in the request handler: property item must be a TreePath
 APP 2019-08-25 12:03:33 Uncaught error in the request handler: Cannot read property 'find' of undefined
 APP 2019-08-25 12:03:33 TypeError: Cannot read property 'find' of undefined
                             at treeWalker (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\src\server-types.ts:724:26)
                             at Object.resolvePath (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\src\server-types.ts:771:15)
                             at a.project (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\src\tiddlyserver.ts:77:16)
                             at a._tryNext (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:139:209)
                             at a._next (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:139:111)
                             at a.next (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:40:64)
                             at a._subscribe (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:57:497)
                             at a.b._trySubscribe (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:45:371)
                             at a.b.subscribe (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:45:197)
                             at b.call (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:138:254)
                             at b.subscribe (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:45:135)
                             at b.call (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:106:24)
                             at b.subscribe (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\lib\Rx.min.js:45:135)
                             at Object.handleTiddlyServerRoute (C:\Users\Kevin\Dropbox\Tools\tiddlyserver\src\tiddlyserver.ts:126:5)
                             at C:\Users\Kevin\Dropbox\Tools\tiddlyserver\src\server.ts:390:9
                             at processTicksAndRejections (internal/process/task_queues.js:85:5)

Working solution:
{
  "tree": {
	"$element" : "group",
	"indexPath" : "group1",
	"$children" :
	{
	  "Testrunde1": {
	    "$element":"folder",
        "path": ".\\tiddlywiki\\wiki\\story\\testrunde"
	  },
	  "Testrunde2": {
	    "$element":"folder",
        "path": ".\\tiddlywiki\\wiki\\template\\testrunde"
	  }
	}
  },
  "bindInfo": {
		"bindWildcard": true
  },
  "putsaver": {
    "backupDirectory": "../backups"
  },
  "$schema": "./settings.schema.json"
}

However, the documentation should be updated to reflect this. I am able to figure this out, but others should not have to understand the Settings documentation which is correct but technical.

Your first example was supposed to work as well so this is a bug. I will
fix this as soon as I can.
On Sun, Aug 25, 2019 at 6:10 AM Kevin Streicher<EMAIL_ADDRESS>wrote:

Working solution:
{
"tree": {
"$element" : "group",
"indexPath" : "group1",
"$children" :
{
"Testrunde1": {
"$element":"folder",
"path": ".\tiddlywiki\wiki\story\testrunde"
},
"Testrunde2": {
"$element":"folder",
"path": ".\tiddlywiki\wiki\template\testrunde"
}
}
},
"bindInfo": {
"bindWildcard": true
},
"putsaver": {
"backupDirectory": "../backups"
},
"$schema": "./settings.schema.json"
}
However, the documentation should be updated to reflect this. I am able to
figure this out, but others should not have to understand the Settings
documentation which is correct but technical.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Arlen22/TiddlyServer/issues/70?email_source=notifications&email_token=AADLMQHVA3SCAER2AUPMUM3QGJLBFA5CNFSM4IPIS5W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CQO3I#issuecomment-524617581,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADLMQFGXKTNWTEMZ2GX4HTQGJLBFANCNFSM4IPIS5WQ
.

I just tested it and it is fixed in the revision I posted at https://github.com/Arlen22/TiddlyServer/issues/67.


Python FDK does not filter data

Using RTK 2.3.0, ITK 5.3.0rc3  wrappings with python 3.9 on MacOs.
FDK reconstruction seems to not filter the data prior to back-projection.
This is the case both in Spyder or by direct execution of the script in command line (python testfdk.py).
Anaconda python. Pb occurs when script launched within an env. or not.
Steps to reproduce :
import itk as itk
from itk import RTK as rtk
import matplotlib.pyplot as plt

geo = rtk.ThreeDCircularProjectionGeometry.New()
for i in range(360) :
    geo.AddProjection(1000,1500,i)

imtype = itk.Image[itk.F,3]

cst = rtk.ConstantImageSource[imtype].New(Constant=0.,Size=[256,3,360],Origin=[-127.5,-1.,0.])
proj = rtk.SheppLoganPhantomFilter[imtype,imtype].New()
proj.SetGeometry(geo)
proj.SetInput(cst)
proj.SetPhantomScale(80)

csttomo = rtk.ConstantImageSource[imtype].New(Constant=0.,Size=[256,1,256],Spacing=1.,Origin=[-127.5,0,-127.5])

fdk = rtk.FDKConeBeamReconstructionFilter[imtype].New()
fdk.SetGeometry(geo)
fdk.SetInput(0,csttomo.GetOutput())
fdk.SetInput(1,proj.GetOutput())

fdk.Update()
recons = fdk.GetOutput()

itk.imwrite(recons,'recons.mha')

I don't seem to be able to reproduce on Linux. Which RTK package did you use, the one on pypi?

Nope. I downloaded the Wheels from last action on master here.

I can reproduce it on linux and it's an FFT issue
import itk as itk
from itk import RTK as rtk

geo = rtk.ThreeDCircularProjectionGeometry.New()
for i in range(360) :
    geo.AddProjection(1000,1500,i)
imtype = itk.Image[itk.F,3]
cst = rtk.ConstantImageSource[imtype].New(Constant=0.,Size=[256,3,360],Origin=[-127.5,-1.,0.])
proj = rtk.SheppLoganPhantomFilter[imtype,imtype].New()
proj.SetGeometry(geo)
proj.SetInput(cst)
proj.SetPhantomScale(80)

ramp = rtk.FFTRampImageFilter[imtype, imtype, itk.D].New()
ramp.SetInput(0,proj.GetOutput())

ramp.UpdateLargestPossibleRegion()
recons = ramp.GetOutput()

itk.imwrite(recons,'ramp.mha')

I'm guessing that compiling new RTK packages with new ITK code but using an "old" ITK release causes a problem due to, e.g., InsightSoftwareConsortium/ITK#3156. I'll ask if we can get new ITK wheels...

Locally recompiling the wrappings from ITK and RTK fixes the issue. If I add after the imports the line
itk.VnlFFTImageFilterInitFactory.RegisterFactories()

it seems to fix the issue... So there is nothing else to fix the issue than compiling locally, using this workaround or wait for a new ITK release.

New packages provided in  InsightSoftwareConsortium/ITK#3156 show that the issue is not solved.

itk.VnlFFTImageFilterInitFactory.RegisterFactories()

does not help.


Install script

Automate the install of the adafruit libraries and configuring the program on the rpi

Initial script has been created need to adjust so it installs the systemd files so it enables itself on startup


WIP Develop: Cloud Run deploiement

Pull Request Test Coverage Report for Build 637

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.2%) to 77.985%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/app.controller.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/check/utils.ts
1
56.25%

Totals

Change from base Build 614:
0.2%

Covered Lines:
1226

Relevant Lines:
1558

💛  - Coveralls


the number picture is 235,but label failed and number is None

Need more info, fill the issue form and logs would be helpful
Describe the issue
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.


photo-index: index photos by sources too

Ignore first three commits as they are being reviewed separately.

jenkins: test this


Remove ssd overprovisioning

In the scheduler, the ssd overprovisioning should be removed.

Done in https://github.com/threefoldtech/terraform-provider-grid/pull/249


Meta update part 2

Preview build: https://dash-docs--41.org.readthedocs.build/projects/core/en/41/

Closing in favor of #42


fixed type issues with preact

Thanks for the contribution!
Does the changed one also compatible with React?

Tested in my local machine and these 2 types seem to be equal. Thanks!


Decentralized capital pricing tool: Scoping study

Project Abstract
Prior related W3F Grant: Token economics survey (2022)
A scoping study for: A Blockchain capital pricing workbook template and documentation.
Together the workbook and user guide are intended to demonstrate how to:

design a (hypothetical) blockchain token with known (theoretical) equilibrium relations,
build a workbook model of the equilibrium token dynamics, and
construct a capital pricing model for the token.

The target audience is blockchain developers, analysts and users. The tool implementation is blockchain agnostic.
Description:
Design a hypothetical token with a known pricing relation to observable variables that influence the token value dynamics.
The token use case and design will strive to be consistent with the constraints and requirements described by Cong, Lin William, Ye Li, and Neng Wang. “Tokenomics: Dynamic Adoption and Valuation.” The Review of Financial Studies 34, no. 3 (August 2020): 1105–1155..
Implement a capital pricing workbook for the so-designed token/coin. The capital pricing framework will be the Black Zero-Beta capital asset pricing model (CAPM).
Grant level

[x] Level 2:  Up to $30,000, 3 approvals

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI), or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).

The main reasons for this are: in general, we are always careful when it comes to funding token-related work, and this application isn't necessarily polkadot specific, whereas the staking application is very focused on our ecosystem.

Thanks for the feedback. Apologies for the ambiguity - this does assume familiarity with the CLW paper or at least its annotated entry in Token economics survey (2022).
I understand the reluctance to be seen funding a particular token.
Just to be clear this is not implementing a token that will be launched. It is a scoping study to establish the work that would be required to implement a user/developer tool that will expose the risks of a particular token - that token could already exist in the Dotsama ecosystem, or it could be in development.
The template targets a fairly common use case among parachains and on-demand parachains.
I'll add the following clarifications if they cause you to revise your current assessment. Let me know if you do change your mind:

The framework is appropriate for Substrate parachain tokens that:

have a fixed supply
are not used to fund collating or staking, e.g. on-demand chains, solo chains, permissioned and permissionless chains
are expected to have network effects from user adoption
are focused on a particular use case rather than being a fiat replacement.

Two use cases I hesitated to put forward are, first, as a parachain pre-launch development tool:

can you identify the productivity benefit that is driving your token value?
can you measure those things? Directly? Indirectly?
do you and your users understand the 'best-estimate' timeframes required for your expected network effects to materialize?
do you and your users understand the range of token values suggested by your data? These tokens are not the-skys-the-limit. They have a limited value range.

Second, a tool for users to evaluate an existing token. If it helps I could add an item regarding selecting an existing token in the ecosystem to illustrate this use case - but won't this be controversial? It will appear to be targeting a team.

I'm personally also much more interested in your other application.

That is on me. This tool provides similar functionality but at a broader/higher level. Rather than just asking: Is staking working as they say? This tool will be asking (within the constraints of a model): Is this token working as expected?

I would still be much more interested in your other application

Is this an either-or choice?
If so the other application is more important - right now there is zero help for developers creating a token economy - yet all the tools are provided to do so.
This is a recipe for disasters ... like the Acala stablecoin.

We usually support only one application at a time per person/team unless it's a bigger team.

Understood. Please evaluate this application as the higher priority - IMO. If it gets declined we can move on.

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/referendum-234-data-availability-retroactive-funding-and-on-chain-invoices/3421/37

@taqtiqa-mark thank you for your application. Is this application a research or development one? I notice that the application is not compliant with any of the two templates that we have (software development or research). Please select one and make the adjustments to comply with the template. Give special attention to the milestone deliveries table. Let me know when I can take another look at this application.

@taqtiqa-mark thank you for your application. Is this application a research or development one?

Development.

I notice that the application is not compliant with any of the two templates

Correct - per the discussion above @Noc2 and 'the team' are assessing if this type or tool is in the scope of the grant program.  If it is I'll provide the additional detail taking into account any feedback.

I just saw that you requested my review here. I took another look at your previous grant and the delivery, and to be honest, I don't see a clear benefit regarding this project for the Polkadot ecosystem ....

@Noc2 , I Just wanted to clarify a couple of things. By persisting I'm not discounting your objections. And I have taken time reviewing other grants, in areas I am expert, to try to understand what you consider the community needs:

Especially since the grants program primarily supports the development of a PoC or something similar and not production-ready software.

or somehow picking up this work and actually implementing a unique token design based on it.

Yes that is one use case, which I describe as pre-launch.  I do point out the validation use case, which I describe as post-launch. I believe there is some interest in the post-launch use case. But PoC for this use case maybe out of scope?

But I also shared the application with @jonasW3F, who might be in a better position to judge it. And I also pinged the rest of the team again.

Thanks, I'll make a couple of more revisions. Then if the application is still does not persuade the team we can safely say this line of tooling is categorically out of scope.  That is important because the published proof of token dynamics is one of the simplest and least risky - things get exponentially more difficult, and more risky, from there.

@taqtiqa-mark As I commented here, the deliverables table is still not compliant with our template. If you want to go forward with this application, please adjust it, so we can mark it as ready to review by the committee.

Hi I'll respond inline:

Hi @taqtiqa-mark

thanks for your interest in working on this for the ecosytem. I share @Noc2 concern that this might not be suitable for a Web3 Grant as one of your main goals is to come up with a pricing model of Parachain token.

For calrity the pricing model has already been developed in the published paper cited.  I certainly am not "coming up with a pricing model of Parachain token".

The other goals will certainly also be very much related to overall market dynamics.

That statement on market dynamics isn't clear to me.  But I think I understand the reservations: the W3F doesn't want to be seen to be promoting a particular token model.

We generally abstain from giving any guidelines about the financial aspects around DOT or parachains.

Understood, I very much share that reservation (see below).  Hence this proposal was generic.

I do, however, think that it might be a valuable contribution to the ecosystem, so my guess would be that the Treasury is a better place to ask for funding.

I'll certainly consider that.

On a personal note: as you certainly are confident that your contribution will be valuable, there are many new projects out there that are very interested in getting help with their token design.

I bear that in mind.

I do, however, appreciate your broader perspective of coming up with open guidelines for the ecosystem. Again, this sounds more suited for the Treasury.

Yes, an open tutorial is certainly the primary motivation.

As a sidenote. I read your delivery of Milestone 3 from the last grant. I already expressed my concern of relevance at the time. After having reviewed your manuscript, I feel confirmed in my initial estimate:

I think you're being selective here.  You inital estimates was:

... rigorous (academic) token economic research is mostly absent.

We now know that is a profound misconception. One I shared in.  But I was more optimisitc than you and that optimism has been bourne out more than I'd expected - the Sockin papers are particularly encouraging - and possibly, in my mind, explains the SEC more aggressive stance.  Their staff can't be excused the level of irnorance I had.
And now we can point to this paper in the ecosystem showing this research is very rigorous and has been well known for several years in the form of discussion papers, and published in the most prominant journals for going on three years.

the only reference to anything related Polkadot is Table 4 that simply categorizes the parachain tokens into three rather obvious types.

Again your prior expectation was:

I'd not expect much other tokens than utility tokens that pay for transaction fees, are used in governance for voting and/or might be used for staking. Other token types are virtually absent as they'd constitute clear securities.

I'll need to think about how to phrase things in the paper so that it is clearer what those authors are saying - that your understanding (stated above) is very near back to front.
The difficulty here is the economic definition of a security vs the legal definition.  The courts haven't paid to much attention to the economic definitions - preferring to 'look behind the curtain'.
All of the analysis done applies to the Polkadot ecosystem. Unfortunately, there was only the Equillibirum token/chain that contained any material that could be identified as being in the framework reviewed here.  It is valuable to know that fact.

Other than that, the document just lists a few economic concepts, in my opinion misses making the reader aware of the relevance between each them,

That is a fair point.  The relevance between them is set out in the 1,200+ pages of Lunqvist and Sargeant.  I'll make this explicit.

and summarizes 6 (relevant) papers. Here, again, the reader is not educated about the relevance of the studies to the specific application in Polkadot.

Yes that is correct.  To do so would be "to come up with a pricing model of Parachain token"  and would be to provide "guidelines about the financial aspects around DOT or parachains"

I doubt that giving this document to any parachain team has them learn something about their token economics.

This is a problem.
For example, I introduce the term 'breakable token' that is understandable to a lay reader. That is it is not the formal economic charaterization.  I do make clear which token 'features' or 'functions' make a token breakable.
It does appear you are trying to get me to say, in this scoping review, that token X is best modelled, or most closely resembels a 'breakable' token, or token Y has characterisitics that are consistent with an 'effervescent' token.
Can you elaborate how what you are asking is different from asking me "to come up with a pricing model of Parachain token"  and to provide "guidelines about the financial aspects around DOT or parachains".
It may help to use a hypothetical chain/token.  And to describe, or mock-up, some concrete artifact you had expected to see that is not present.

You might argue that applying the theories from the papers to the parachain tokens is out of scope of the delivery.

It very clearly is out of scope.  Ironically, for the very reasons you object to this proposal. To do so would be "to come up with a pricing model of Parachain token" for some particular team  and to provide "guidelines about the financial aspects around DOT or parachains".
I did address explicitly in the paper why that is not done - I do not know what a developer (team) has in their mind's eye for their token.  The subtle details matter greatly.

But, I would still have loved to see some tangible implications for practitioners in the last (now fully delivered) grant.

As I said I'm happy to try to do that.
Can you indicate what you have in mind that is not a backdoor way "to come up with a pricing model of Parachain token"  and to provide "guidelines about the financial aspects around DOT or parachains"?

Also in this grant proposal, I'd love to see some upfront work giving a glimpse on the usefulness of the final study.

Regarding the details of the previous grant mentioned above please open issues against the previous grant addressing the detail and artifacts you believe I should have delivered.  I'll do my best to address those shortcomings - within the constraints that we seem to agree on: they should not be a backdoor way "to come up with a pricing model of Parachain token"  and are not to provide "guidelines about the financial aspects around DOT or parachains".
I don't propose to revise this application further.  I'll await reject/accept decision then we can move on.

@taqtiqa-mark As I commented here, the deliverables table is still not compliant with our template.

Yes, as indicated previously by @Noc and now @jonasW3F there is concern this topic is out of scope of the program. Unless that changes it appears we are headed to rejecting the PR as out of scope.  Then we can move on.

If you want to go forward with this application, please adjust it, so we can mark it as ready to review by the committee.

IIUC, we have to clear the first hurdle of establishing the topic is within scope.

In light of the experience with the grant Token economics survey (2022). Specifically, the attempt, on the brink of accepting Milestone 3, to bring within scope material that was clearly defined as out of scope, and the attempt to provide guidance to block chain teams. Details here:
https://github.com/taqtiqa-mark/tokenomics-survey-2022/issues/4
And given the complexity and subtlety of the analysis that is the subject of this application, prior experience dictates it is prudent to withdraw this application.

Hi @taqtiqa-mark. I respect your decision to withdraw your applications. But could you elaborate what you mean by

bring within scope material that was clearly defined as out of scope

? Are you referring to the ongoing grant, or the application?

Are you referring to the ongoing grant, or the application?

The current grant, which was all but signed off until this application was discussed.


Cluster Issuer is not found

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
A clear and concise description of what the bug is.
I  created a Issuer of cloudflare ,but not found in k8s

edgar.zhao@edgarzhao-2 ~/data/strikingly/eosx_deploy/cert-manager/eosscan # cat cloudflare_ssl_dns.yaml
apiVersion: cert-manager.io/v1alpha2
kind: Issuer
metadata:
  name: letsencrypt-prod-cloudflare
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email<EMAIL_ADDRESS>    privateKeySecretRef:
      name: letsencrypt-prod-cloudflare
    solvers:
    - selector: {}
      dns01:
        cloudflare:
          email<EMAIL_ADDRESS>          apiKeySecretRef:
            name: cloudflare-credentials
            key: secret-access-key

edgar.zhao@edgarzhao-2 ~/data/strikingly/eosx_deploy/cert-manager/eosscan # kubectl create -f cloudflare_ssl_dns.yaml
issuer.cert-manager.io/letsencrypt-prod-cloudflare created
edgar.zhao@edgarzhao-2 ~/data/strikingly/eosx_deploy/cert-manager/eosscan # kubectl get Issuer --all-namespaces
No resources found.

Expected behaviour:
A concise description of what you expected to happen.
Steps to reproduce the bug:
Steps to reproduce the bug should be clear and easily reproducible to help people
gain an understanding of the problem.
Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.10.2):

1.12.10-gke.17

Cloud-provider/provisioner (e.g. GKE, kops AWS, etc):
cert-manager version (e.g. v0.4.0):
Install method (e.g. helm or static manifests):

helm install \
  --name cert-manager \
  --namespace cert-manager \
  --set ingressShim.defaultIssuerKind=ClusterIssuer \
  --set ingressShim.defaultIssuerName=letsencrypt-prod \
  --set webhook.enabled=false \
  --version v0.12.0-beta.1 \
  jetstack/cert-manager

/kind bug

I have a similar problem with a cloudflare cluster issuer.
I have created the two cluser issuers, if I run
kubectl get clusterissuer
I can see both
But even if I specify to use the cloudflare one by using the ingress annotation, the other one is used, as if the cloudflare one was completely ignored.
I have also tried removing the other one, and nothing works, as it's like if the cloudflare issuer does not exist.
I've tried to put multiple solvers - http01 and dns01, with all the possible combination of selectors, and I cannot make the cloudflare one working.
Even specifying it as a unique resolver does not work, it's as if I do not have any resolver set up.
I'm using version 0.11.0 of Cert Manager.

Same here on a GKE cluster (master 1.12.10-gke.17, nodes 1.12.8-gke.10`).
How could we troubleshoot this? I found no documentation anywhere on the doc website.

After investigating this, turns out my ClusterIssuer had already been there. However, this is what my environment looked like before I had to manually delete the old cert-manager CRDs to be able to see it listed. Please see https://github.com/kubernetes/kubernetes/65818#issuecomment-557520865

What is most likely being seen in all cases is having multiple grouos of CRDs installed in a cluster (we changed the group from certmanager.k8s.io to cert-manager.io. These resources have aliases for use with kubectl. When multiple CRDs of different groups are installed that use the same short names kubectl may be referencing the resource with the wrong group.
If you try kubectl get cert-manager.io.Issuers --all-namespace you should see the resources available.
To fix this, delete the old CRDs from your cluster.
kubectl delete -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.10/deploy/manifests/00-crds.yaml

I'm having issue with letsencrypt prod, the tls-secret that it creates should not have tls.crt empty, ca.crt shows empty too in working clusters so I think that may be fine. However, the empty tls.crt field is definitively the one causing Nginx to use fake certificate.
Cert-manager:
helm install
cert-manager
--namespace ingress-public
--version v0.13.0
jetstack/cert-manager
cluster-issuer.yaml
apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
name: letsencrypt-prod
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
email<EMAIL_ADDRESS>privateKeySecretRef:
name: letsencrypt-prod
solvers:
- http01:
ingress:
class: nginx
The app is having issues because cert is invalid/fake. Help needed!

@Raghubalam, I'm seeing the same thing.

This link has
Spec:   Issuer Ref:     Group:  cert-manager.io     Kind:   ClusterIssuer     Name:   **letsencrypt-production**
whereas we have
Spec:   Issuer Ref:     Group:  cert-manager.io     Kind:   ClusterIssuer     Name:   **letsencrypt-prod**
...to the experts, would this matter? Also @Raghubalam you have "cert-manager.io/v1alpha2" and I'm using "cert-manager.io/v1beta1". I'm really new to this (Kubernetes), but I need to get this cert issue figured out.


Update Composer dependencies (2023-03-31-00-12)

Visual regression test passed!
View the visual regression test report


[DOC] more detailed doc for CorpusBPTTBatchify

Description
The document for CorpusBPTTBatchify does not explicitly mention the size of the tuple which could be confusing to end users. This PR updates the documentation to provide more details on the data format.
Checklist
Essentials

[X] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[X] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[X] Code is well-documented

Changes
Comments

Job PR-888/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-888/1/index.html


Plz invite me

I am @charles0830 .
I want join and contribute here

Hello Charles, you have already joined the org. Thank you for being a member. Closing this issue


[Task] Define app memory limit

What should be done
Define is the Docker Compose file the app memory limit in the Docker Compose file with the same memory limit defined by the Lenra server.
Technical recommandation
    deploy:
      resources:
        limits:
          memory: 256M
        reservations:
          memory: 128M

Waiting for this PR to make it simpler


Error message from GCOV

At the link stage, the linker generates the following error messages :

This is relevant to the GCOV. The *.gcda data have to be deleted at the link stage. But CMake doesn't delete.
Need to delete explicitly.

Adding the following setting to the test/CMakeLists.txt may solve this problem.
    # Delete the gcov data file before linking. Otherwise, we will get many errors.
    add_custom_command(
        TARGET ${TEST_EXECUTABLE_NAME} PRE_LINK
        COMMAND find . -name "*.gcda" -delete
        COMMENT "Deleting *.gcda files in ${CMAKE_BINARY_DIR}"
        WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
        VERBATIM)

This setting explicitly deletes all the *.gcda file under the build subdirectory.

Done


Support for using functions in bash prompt

Hi,
Would you like to extend the clr_ functions to wrap escape sequences in \[ - \] pairs?

Can you give an example?

When you inlcude colour parts in your PS1 variable, the character coding should be included in \[ and \]:
PS1=$'${debian_chroot:+($debian_chroot)}\[\033[01;31m\]\h\[\033[00m\] \D{%F %T} \[\033[01;34m\]\w\n\$ \[\033[00m\]'

If you don't do it, and your typed command wraps line, you will see the downside of it.

Sole purpose of this lib is to define words for numbers.
For the special case of prompt, you can use constants.

The constants are a bit cumbersome to use, at least if I use this repo. I prefer constants, which contains \033[01;31m, not just 31


Unpin XGBoost version

fix #1536

Unpinning XGBoost issues:

build_docs failing:

Workers failing to return in cost_benefit_matrix.ipynb, which causes the build docs to time-out
Changing -j auto in Makefile and OMP_NUM_THREADS in circleci config do not fix the issue
Doc build for Pull Request passes, as seen here
Changing version back to 1.2.0 allows the docs to pass, and we don't run into this worker issue

Next Steps:

Make sure to set xgb_parameters.update({"use_label_encoder": False, "eval_metric": "logloss"}) to remove warning messages for newer XGBoost version
Check runtime differences between 1.3.0 vs 1.2.0 versions

Closing PR for now, will move issue to icebox and revisit later once we look into removing build_docs or XGBoost has new releases.

Unpinning XGBoost issues:

build_docs failing:

Workers failing to return in cost_benefit_matrix.ipynb, which causes the build docs to time-out
Changing -j auto in Makefile and OMP_NUM_THREADS in circleci config do not fix the issue
Doc build for Pull Request passes, as seen here
Changing version back to 1.2.0 allows the docs to pass, and we don't run into this worker issue

Next Steps:

Make sure to set xgb_parameters.update({"use_label_encoder": False, "eval_metric": "logloss"}) to remove warning messages for newer XGBoost version
Check runtime differences between 1.3.0 vs 1.2.0 versions

Closing PR for now, will move issue to icebox and revisit later once we look into removing build_docs or XGBoost has new releases.


fix metadata to use a string instead of a bool

using a bool here is only supported > 11.12.0, and breaks the cookbook for earlier chefs.
fix for https://github.com/opscode-cookbooks/build-essential/issues/56

tested successfully on 11.6.0, where the bool version failed.

As I commented on #56 (and created a PR for this exact change), I'm :+1: on this.


dubbo最佳实践案例申请，全自动开源框架Emsite

望dubbo团队快速完成到apache顶级项目的升级，申请做dubbo的最佳使用示范项目：https://gitee.com/hackempire/emsite-parent

Hi, welcome!
Would you please update the title and description using English? Dubbo is a global community and we would like the issue to be seen by people all over the world.
Questions like this are expected to be asked in the mailing list, you can subscribe and ask there.

Thanks for a wonderful integration framework.
But I guess the "best practices" were some principals from many production biz system, those contained experience of using dubbo to design, development, testing, deployment and maintainance.

thanks for ur best wish, let's close this issue for now.


Maybe get a list of changed files using git diff and pass them to the script?

          Not sure we need all that but I tend to minimize the number of external calls in build processes in favor of things that can be retrieved internally to avoid issues. Let's keep an eye on it. If it becomes an issue, we can use something like the code below:

    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Diff
        shell: bash
        run: |
          git fetch origin ${{ github.base_ref }}

          base_sha=$(git rev-parse origin/${{ github.base_ref }})
          head_sha=$(git rev-parse ${{ github.sha }})

          changed_files=($(git diff --name-only $base_sha $head_sha))

          echo "Changed files:"
          for file in "${changed_files[@]}"; do
              echo "$file"
          done

Originally posted by @caponetto in https://github.com/opendatahub-io/notebooks/pull/558#discussion_r1638245768

Looks like I can leave out git fetch and git rev-parse. See the FromRef usage in blog
run: "& .github/workflows/create-test-matrix.ps1 -FromRef '${{ github.base_ref }}'"

https://purple.telstra.com/blog/github-action-test-matrices-part2


Add --debug flag

Now that styledocco fails gracefully, the stack trace is hidden making bug reports harder to trace.  The --debug flag will enable users to show the stack trace if they wish.

+1 :+1:


binary rewards in readme, but not in the code

Hello!
I'm wondering if there is any good reason for assigning rewards as: 1 - 0.9 * (self.step_count / self.max_steps)
(this line)?
The readme says that the rewards are 0 or 1, so I think either readme or the code should be fixed to avoid confusion.
To me, the binary rewards seem more reasonable as the discount factor in the return computations already takes care of  encouraging the agent to reach the goal faster.
Also, assuming that the agent doesn't know for how many steps it was running, it will have a hard time predicting the reward (and consequently value) if the reward depends on step_count. Such reward makes the environment even more partially-observable.
I think it needlessly makes the problem harder.
Anyway, thank you for this beautiful environment!

Hello, I think you're probably correct but we wanted to give an incentive in the environment's reward to reach the goal faster, no matter the discount factor.


R samples always running on macOS!

The R samples on the web page are also running for a quick test on my CRAN R interpreter on macOS Catalina!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dde63717-000d-d97c-0898-36c005d8541f
Version Independent ID: 4c63fc76-7fac-4e58-cca7-e8476cb1248f
Content: Getting started with R Tutorial - Visual Studio
Content Source: docs/rtvs/getting-started-with-r.md
Product: visual-studio-dev15
Technology: vs-rtvs
GitHub Login: @kraigb
Microsoft Alias: kraigb

@hindermath Thanks for the note. It seems that you're just commenting on having a success here, and aren't running into an issue, correct?
Either way, though, because support for R was dropped from Visual Studio 2019, the RTVS documentation that you refer to here is no longer actively maintained, and for that reason I'm closing this issue. Thanks.


Can't find fitboundUpdate

Hi,
I just installed latest version of this library  "react-mapbox-gl": "^4.8.6" and tried to detect if a zoom event was caused by a user interaction by using fitboundUpdate introduced in PR https://github.com/alex3165/react-mapbox-gl/pull/711.
But fitboundUpdate is always undefined on the fired event:
onZoomEnd = (
    map: MapboxGL.Map,
    event: React.SyntheticEvent<any>
  ) => {
    //@ts-ignore
    if (!event.fitboundUpdate) {
      alert("Zoom caused by user interaction")
    }
  };

This should work based on the documentation change from PR https://github.com/alex3165/react-mapbox-gl/pull/711
Do you know what I did wrong?
Thanks.

The problem was that we were calling map.fitBounds from our code and we were not sending a fitboundUpdate option.


Depend on mockito-core only.

kotlintest only uses stuff from mockito-core. Otherwise e.g.
when you use maven-enforcer-plugin and define a rule which
forbids duplicate classes there is a clash because mockito-all
defines some matchers itself.

:+1:


🚀 Feature: Add an option to run all tests, including skipped ones

Feature Request Checklist

[x] I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
[x] I have searched for related issues and issues with the faq label, but none matched my issue.
[ ] I want to provide a PR to resolve this

Overview
It would be nice to have an option that could make Mocha run all tests, even skipped ones.
At my company, we skip flaky tests in our CI build to avoid blocking developers, but we'd like to set up a "quarantined" tests build that runs all tests. This allows us to check when flaky tests are no longer flaky and can be safely introduced back into the blocking tests pool.
Suggested Solution
mocha --includeSkipped
Alternatives
Sed all my test files before running Mocha, which isn't particularly sound.
Additional Info
No response

Hmm, but how would Mocha / a project's testing infrastructure know which tests are skipped for flakiness vs. other reasons?
This feels to me like a project-specific preference that would be better solved in project-land. For example, you could write your own function that calls it or it.skip depending on some process.env.RUN_FLAKY_TESTS:
function myIt(title, callback) {
  if (process.env.RUN_FLAKY_TESTS) {
    it(title, callback);
  } else {
    it.skip(title, callback);
  }
}

Am I missing some nuance to the request?

Mocha doesn't need to know why a test is skipped. Under this model, the user asked for all tests to be run, so interpreting the results becomes the user's problem.
Your workaround is fair; it just feels weird that Mocha supports marking a test as skipped, but doesn't support other ways of interacting with it. If I wanted a test to never run, the logical thing to do would be to delete the test entirely.

If I wanted a test to never run, the logical thing to do would be to delete the test entirely.

Not necessarily. Folks sometimes try to keep skipped tests around to make sure they stay valid for static analysis such as linting or type-checking. A test might be skipped for a time-sensitive reason such as an external service not being ready yet or dropping support for something at a known time.
Anyway, per #5027, we're not looking to add a lot of new features. I'm going to go ahead and close this as a pretty specific use case. Thanks for filing + discussing! 🤎

OK, fair enough. Thanks for considering it.


Rebase from pokadot-js/extension-master

Rebase from pokadot-js/extension-master

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Sign validation request when using aws-sigv4 (#130)

Signed-off-by: Robin Roestenburg<EMAIL_ADDRESS>Description
Fixes #130 by having the opensearch-aws-sigv4 gem pass the signing headers to the request to verify / validate the OpenSearch distribution.
When you do not use the AWS v4 signing, the behaviour of the opensearch-ruby gem is unchanged. The verify_open_search method is called without passing any headers (as before).
Issues Resolved
Closes #130.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I think the only change needed is overriding open_search_validation_request method:
def open_search_validation_request
  method = 'GET'
  path = '/'
  signature = sigv4_signer.sign_request(http_method: method, url: signature_url(path, {}))
  @transport.perform_request(method, path, {}, nil, signature.headers)
end

Though maybe I'm missing sometlhing.

This also need a rebase. Each gem now has its own changelog inside its respective folder.

I think the only change needed is overriding open_search_validation_request method since the verification logic is virtually identical to the base client

@nhtruong yes, I think you are right. I have adjusted the code (and rebased onto the latest version).


wrong method

13:50:39 | ERROR    | 120 - my_Session | Неизвестная ошибка при авторизации: Telegram says: [400 BOT_METHOD_INVALID] - The method can't be used by bots (caused by "messages.RequestWebView")

should i use phone number instead of token?
i wish the russian text's was in english

should i use phone number instead of token?

yes

i wish the russian text's was in english
there's no such method yet, use translator


autocorrect: 2.8.5 -> 2.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for autocorrect is: A linter and formatter for help you improve copywriting, to correct spaces, punctuations between CJK (Chinese, Japanese, Korean)
meta.homepage for autocorrect is: https://huacnlee.github.io/autocorrect
meta.changelog for autocorrect is: https://github.com/huacnlee/autocorrect/releases/tag/v2.8.5
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.8.5 with grep in /nix/store/28pk30a5ngh44ws6350h8481acl8blxa-autocorrect-2.8.5
found 2.8.5 in filename of file in /nix/store/28pk30a5ngh44ws6350h8481acl8blxa-autocorrect-2.8.5

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
autocorrect

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/28pk30a5ngh44ws6350h8481acl8blxa-autocorrect-2.8.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A autocorrect https://github.com/r-ryantm/nixpkgs/archive/eb168c2d6b9aaaf481ed9ab5842481652bc9842d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/eb168c2d6b9aaaf481ed9ab5842481652bc9842d#autocorrect

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/28pk30a5ngh44ws6350h8481acl8blxa-autocorrect-2.8.5
ls -la /nix/store/28pk30a5ngh44ws6350h8481acl8blxa-autocorrect-2.8.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

autocorrect

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for autocorrect is: A linter and formatter for help you improve copywriting, to correct spaces, punctuations between CJK (Chinese, Japanese, Korean)
meta.homepage for autocorrect is: https://huacnlee.github.io/autocorrect
meta.changelog for autocorrect is: https://github.com/huacnlee/autocorrect/releases/tag/v2.9.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.9.0 with grep in /nix/store/w4na46ymknzcs6m0ajjw7hzp0lcfp7mq-autocorrect-2.9.0
found 2.9.0 in filename of file in /nix/store/w4na46ymknzcs6m0ajjw7hzp0lcfp7mq-autocorrect-2.9.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
autocorrect

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w4na46ymknzcs6m0ajjw7hzp0lcfp7mq-autocorrect-2.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A autocorrect https://github.com/r-ryantm/nixpkgs/archive/1f61158764f7af206179fc3b6014fa4a4253614b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1f61158764f7af206179fc3b6014fa4a4253614b#autocorrect

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w4na46ymknzcs6m0ajjw7hzp0lcfp7mq-autocorrect-2.9.0
ls -la /nix/store/w4na46ymknzcs6m0ajjw7hzp0lcfp7mq-autocorrect-2.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

autocorrect

Maintainer pings


Adding a minimum version for Open MPI

Version 1.7 of Open MPI causes problems in HPX. This change
adds Open MPI as a highly suggested software package with
the minimum version being 1.8

@diehlpk Does this address what you meant?

@aserio Yes, sounds good.

LGTM


Error mapping models with jdk 11.0.11 update

Yesterday oracle jdk 11.0.11 was released and mapping stopped working with the following error (model mapper version 2.3.9):
...
Caused by: org.modelmapper.MappingException: ModelMapper mapping errors:

1) Error mapping a.b.c.ModelA to a.b.c.ModelB

1 error
	at org.modelmapper.internal.Errors.throwMappingExceptionIfErrorsExist(Errors.java:380)
	at org.modelmapper.internal.MappingEngineImpl.map(MappingEngineImpl.java:81)
	at org.modelmapper.ModelMapper.mapInternal(ModelMapper.java:573)
	at org.modelmapper.ModelMapper.map(ModelMapper.java:495)
	... 254 common frames omitted
Caused by: java.lang.ClassCastException: null

MM configuration:
// ... here are some custom converters
modelMapper.getConfiguration().setFieldMatchingEnabled(true).setMatchingStrategy(MatchingStrategies.STRICT).setFieldAccessLevel(
            Configuration.AccessLevel.PRIVATE).setUseOSGiClassLoaderBridging(true);

Rolling back to jdk 11.0.10 resolved the issue. Tried updating the library to 2.4.0 but it made no changes.

Can you provide reproducible code or more detailed information? Thanks.

Sure, will do once I have the time to investigate this further.

This is issue is reproducing for us also.
org.modelmapper.internal.Errors.throwMappingExceptionIfErrorsExist(Errors.java:380) [modelmapper-2.3.9.jar!/:na]\n\tat org.modelmapper.internal.MappingEngineImpl.map(MappingEngineImpl.java:81) [modelmapper-2.3.9.jar!
Caused by: java.lang.ClassCastException: null

This will get resolved after restarting the server in our case and will get reproduced again after code is there in live for some time.

Hey guys, any update on this one ? we have the exact same weird behavior with adopOpenJDK 11.0.11+9 in production.
Rollling back to previous LTS version fix mapping behavior...As it is critical for our company, how can we help ?

@GabrielCORDIER please provide a failing test case if you can. I don't have an allocation to work on this issue myself and honestly don't know when I will since this is not a high priority for us.

I managed find a simple example to generate the same exception, the exception is thrown after a couple hunderd iterations.
This was tested using modelmapper version  2.3.9 and openjdk version 11.0.11
import org.modelmapper.ModelMapper;

import java.util.Map;
import java.util.Set;

public final class ModelMapperFactory {
    static class Baz {
        public void setStrings(Set<String> strings) {}
    }

    static class Foo {
        public Map<String, String> getStringToStringMap() { return Map.of() }
    }

    static class Bar {
        public void setBaz(Baz baz) {}
    }

    public static void createInstance() {
        ModelMapper mapper = new ModelMapper();

        mapper.createTypeMap(Foo.class, Bar.class).addMappings(m -> m.skip(Bar::setBaz));
    }

    public static void main(String[] args) {
        while(true) {
            createInstance();
        }
    }
}

I can reproduce this issue now, thanks @PimW for the reproducible code.
Currently, I have no idea about the root cause, I guessed it's side effect caused by JDK-8255544.

It looks like it's caused by the change of JIT compiler optimization in JDK-8257594. But the root cause hadn't been found.
I'm trying to fix the issue by #611. Can anyone in this thread check if the issue was fixed or not by the pull request?

Minimum reproducible code created: https://github.com/chhsiao90/jdk-8257594-bug
Already submit a bug report to oracle.

https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8266615

It looks like it's caused by the change of JIT compiler optimization in JDK-8257594. But the root cause hadn't been found.
I'm trying to fix the issue by #611. Can anyone in this thread check if the issue was fixed or not by the pull request?

Hi, I've checked this fix and it is working in my case.
Thank You!

@chhsiao90 I confirm the issue here doesn't reproduce on the latest master version.

FYI: The bug from java side was fixed in 11.0.13.

Is this fixed? I am still getting the error with 2.4.3 and OpenJDK Runtime Environment 18.9 (build 11.0.11+9)
This only occurs after about thousands of iterations. Any solution for this?

Got the same error with model mapper 2.4.3 and OpenJDK Runtime Environment 18.9 (build 11.0.11+9),
Getting the error  Caused by: java.lang.ClassCastException: null only after multiple iterations (around 1000). Anyone having the same issue even after the version upgrade?

We are facing the very similar behaviour on production since last couple of days.  We are using java-11-amazon-corretto. We had no change in jdk since long.  The issue is intermittent and exists only in some of the containers of the same service.
Can anybody tell what can be the probable issue and resolution?


Update links in documentation

Two of the links in the end are a copy-paste of the one above. This commit fixes it.

Sorry about that!

Thanks, @tdutrion!


UV: Safe Exposure Times only shown in hours

Can we view the UV safe exposure time in minutes when it is less than 1 hour? Right now, I see '0 h' which is less helpful than '15 m'.

Hi,
this function has been added to the newly released version.
Thank you, bye
Renato

Thank you!


Add PHP CS Fixer and run it in CI

Questions
Answers

Description?
Add PHP CS Fixer and run it in CI

Type?
new feature

BC breaks?
no

Deprecations?
no

Fixed ticket?

How to test?

Possible impacts?

Thank you for review @okom3pom


Integrate Doug's work on Thread.

Note that ktfmt formatted many files that were not targetted by this PR.

Thanks!


FancyZones incorrect after undocking/redocking with external monitors

Microsoft PowerToys version
0.70.0
Installation method
GitHub
Running as admin
No
Area(s) with issue?
FancyZones
Steps to reproduce
I have a Dell Precision laptop with an external dual USB-C dock that has three monitors attached. I leave my laptop closed when connected to the dock so the only displays are the external monitors. I have two horizontal monitors and one vertical monitor. I have these zones configured for each monitor using the zone editor to reflect what I want on each screen. I unplug my laptop from the dock, disconnecting all three monitors (and a USB keyboard and mouse) at the same time. When I plug the laptop back into the dock, the zones are incorrect. When I open the zone editor it shows the correct zones for each monitor. But when I shift+drag a window to snap it to a zone, all three monitors show the configured zone layout of the primary display.
It doesn't happen every time, but it's been enough that I have stopped using FancyZones altogether. Until this is fixed it's not worth the risk
✔ Expected Behavior
All monitors to display their configured zones as per the editor
❌ Actual Behavior
When shift+dragging a window to a zone, all monitors show the zone layout configured for the primary monitor
Other Software
No response

Hi, @timartin1495
Thanks for reporting. Could you attach /bugreport?
@SeraphimaZykova FYI

PowerToysReport_2023-07-07-08-06-49.zip

This is from immediately after plugging back into the dock and the zones being incorrect

I will update today and update here if anything changes. Thanks!

No issues since I've updated to 0.71. Thank you!

Of course I had to say something. Now it's happening again

PowerToysReport_2023-07-21-07-28-46.zip

This time when I opened the editor it had reset the saved layout for the screens. I was able to change it back to my custom preferred layout and it immediately worked again. Previous times it showed one layout but only let me snap to the default.
Also in case it's important, the monitor that I have the custom layout for in portrait orientation. The other two monitors I leave as the default layout because they are both landscape.

/dup https://github.com/microsoft/PowerToys/issues/24656


contribution vue form Validation Library

What problem does this feature solve?
my think vue.js  ecology  lack  form Validation Library
although exist  plenty of  form Validation Library ,yet  None of them are particularly good.
They can only do simple validation Complex and not for vue components support custom validation  fail style.
my contribution is VccValidate
docs (https://dev-zl.github.io/VccValidate/#/)
npm (https://www.npmjs.com/package/vcc-validate)
What does the proposed API look like?
docs (https://dev-zl.github.io/VccValidate/#/)

That's great 👍
You could propose it to https://github.com/vuejs/awesome-vue


[WIP] Enable and fix tests for Let's Encrypt & Coolblue EV

This adds a PKCS7 & DER to PEM converter.
The PKCS7 one took a while to figure out... but it works great!
Currently using it on a OhDear! like application in the last few months and it seems to be working like intended, not having any certificate that has an unresolvable chain anymore.
Fixes #5

Also fixes #6, did not notice the Coolblue cert generating that error locally because I was not on the lowest phpseclib, it was fixed in 2.0.5 apparently.

Thank you very much!


No module named 'imgui_bundle._imgui_bundle.imgui'; 'imgui_bundle._imgui_bundle' is not a package

This is a bit of a weird usecase, but I'm testing out using imgui_bundle with UPBGE, a game engine integrated into Blender (However, I think this problem would be present for Blender addons as well). Basically, Blender retains the loaded library, and when trying to re-import imgui_bundle a second time after stopping and starting the engine runtime (in Blender-embedded mode) it fails to import imgui_bundle._imgui_bundle.imgui correctly.
It works fine in standalone player or export, so this probably has something to do with retaining state while the same process is open. Anyways, the simple fix I found was to just use a try-catch statement at the top of imgui_bundle/__init__.py to wrap the imports.
# Part of ImGui Bundle - MIT License - Copyright (c) 2022-2023 Pascal Thomet - https://github.com/pthom/imgui_bundle
try:
    from imgui_bundle._imgui_bundle import imgui as imgui  # type: ignore
    from imgui_bundle._imgui_bundle import hello_imgui as hello_imgui
    from imgui_bundle._imgui_bundle import implot as implot
    from imgui_bundle._imgui_bundle import imgui_color_text_edit as imgui_color_text_edit
    from imgui_bundle._imgui_bundle import imgui_node_editor as imgui_node_editor
    from imgui_bundle._imgui_bundle import imgui_knobs as imgui_knobs
    from imgui_bundle._imgui_bundle import im_file_dialog as im_file_dialog
    from imgui_bundle._imgui_bundle import imspinner as imspinner
    from imgui_bundle._imgui_bundle import imgui_md as imgui_md
    from imgui_bundle._imgui_bundle import immvision as immvision
    from imgui_bundle._imgui_bundle import imguizmo as imguizmo
    from imgui_bundle._imgui_bundle import imgui_tex_inspect as imgui_tex_inspect
    from imgui_bundle._imgui_bundle import imgui_toggle as imgui_toggle
    from imgui_bundle._imgui_bundle import portable_file_dialogs as portable_file_dialogs
    from imgui_bundle._imgui_bundle import imgui_command_palette as imgui_command_palette
    from imgui_bundle._imgui_bundle import im_cool_bar as im_cool_bar
    from imgui_bundle import immapp as immapp
    from imgui_bundle.immapp import icons_fontawesome as icons_fontawesome

    from imgui_bundle._imgui_bundle import __version__, compilation_time

    from imgui_bundle._imgui_bundle.imgui import ImVec2, ImVec4, ImColor, FLT_MIN, FLT_MAX  # type: ignore
    from imgui_bundle.im_col32 import IM_COL32
except ImportError:
    pass
# Glfw setup:

I'm not sure if this would break anything, and maybe there is a more correct way to do this. In my tests however, it seems to work fine and it successfully imports the module.

Hi,
Could you try to put this try/except inside the user code, i.e. near the first occurring import of imgui_bundle.
It seems awkward to silently swallow error like this. I could not push in production.

I was able to move the try/except logic to the user code, it's not particularly elegant but it works fine. I'm still not sure what the root cause of this issue is, but I think the fix is good enough for now. It's not as simple as wrapping the import in a try-except since the init.py module is called at the beginning of module initialization, so catching the error externally doesn't end up importing the module. I had to make a workaround.


docs: improve cp command in step 4 of README

Added a small improvement in Step 4 of the README, specifying exactly how to copy the KDE color scheme file to the local config.

Oh whoops. Thanks!


Stuck on "Loading..."

Moved from https://github.com/macarthur-lab/gnomad_browser/issues/92
Originally created by @sds02 on Thu, 25 Jan 2018 18:05:10 GMT

When I tried looking for ARID1B, BRCA1 or any gene for that matter, it got stuck. Says "Loading....". I tried Chrome and Safari. I then disconnected from the wifi of my building and connected to hotspot from my phone and it started working! My concern is that I have never had such issues with gnomAD (the original version) while using the wifi from my building so I don't know what's happening with the new version!

Moved from https://github.com/macarthur-lab/gnomad_browser/issues/92#issuecomment-365312532
Originally created by @mattsolo1 on Tue, 13 Feb 2018 16:02:55 GMT

Thanks for trying it out again! Would you mind opening the developer tools console in your browser and taking a screenshot of what you see? For example in chrome, this is View > Developer > Javascript console

Moved from https://github.com/macarthur-lab/gnomad_browser/issues/92#issuecomment-362620762
Originally created by @mattsolo1 on Fri, 02 Feb 2018 15:40:31 GMT

Hello, I think we've addressed this issue. Would you mind trying again?

Moved from https://github.com/macarthur-lab/gnomad_browser/issues/92#issuecomment-364563369
Originally created by @sds02 on Fri, 09 Feb 2018 20:54:06 GMT

Hi! So, I tried again and it's still stuck on "Loading...". Checked my wifi connection and all websites including the old gnomad browser are working just fine.

The gene and region pages now show an error message if there's a problem fetching data instead of continuing to show "Loading...".


No chef-automate binary in fresh machine

  On a brand new vagrant instance the cookbook fails because it's trying to run 'chef-automate' when it doesn't exist.

================================================================================
         Recipe Compile Error in /tmp/kitchen/cache/cookbooks/wbg_a006ba_managed_automate2_server/recipes/default.rb
         ================================================================================

         Errno::ENOENT
         -------------
         No such file or directory - /tmp/kitchen/cache/chef-automate

         Cookbook Trace:
         ---------------
           /tmp/kitchen/cache/cookbooks/managed-automate2/recipes/default.rb:22:in ``'
           /tmp/kitchen/cache/cookbooks/managed-automate2/recipes/default.rb:22:in `from_file'
           /tmp/kitchen/cache/cookbooks/wbg_a006ba_managed_automate2_server/recipes/default.rb:17:in `from_file'

         Relevant File Content:
         ----------------------
         /tmp/kitchen/cache/cookbooks/managed-automate2/recipes/default.rb:

          15:
          16:  # is Automate already installed?
          17:  installed = false
          18:  upgrade = false
          19:  restore = false
          20:
          21:  # is Automate installed?
          22>> versions = `#{chefautomate} version`.split
          23:  if versions[5].nil?
          24:    currentversion = -1
          25:  else
          26:    installed = true
          27:    currentversion = versions[5]
          28:  end
          29:
          30:  # if we have an upgrade URL or we have an upgrade file and a directory, it's an upgrade
          31:  if node['ma2']['upgrade']['url'] || (node['ma2']['upgrade']['file'] && node['ma2']['upgrade']['dir'])

         System Info:
         ------------
         chef_version=13.8.5
         platform=centos
         platform_version=7.4.1708
         ruby=ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux]
         program_name=chef-client worker: ppid=13441;start=00:06:47;
         executable=/opt/chef/bin/chef-client

         Running handlers:
       [2018-12-06T00:06:52+00:00] ERROR: Running exception handlers
         Running handlers complete
       [2018-12-06T00:06:52+00:00] ERROR: Exception handlers complete
         Chef Client failed. 7 resources updated in 04 seconds
       [2018-12-06T00:06:52+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
       [2018-12-06T00:06:52+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
       [2018-12-06T00:06:52+00:00] ERROR: No such file or directory - /tmp/kitchen/cache/chef-automate
       [2018-12-06T00:06:52+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

I'll chalk this up as a documentation bug. You're supposed to use the airgap_bundle recipe to download the chef-automate command (and the .AIB) and put those in place so you can use them with the default recipe. It's meant to be air-gapped, so we can't have it reaching out to the Internet.


KAFKA Manager <IP_ADDRESS> SASL_PLAINTEXT can't get the Latest Offset and Leader Size for each topic & Consumers can not get LogSize and lag

I am having Kafka Manager 1.3.37 and Kafka server kafka_2.12-<IP_ADDRESS>. We have enabled SASL_PLAINTEXT since then we don't see the topic offset on the kafka manager.
Is it a known issue or limitation with Kafka?

You need to pass in the jaas conf.


Unmarshal partitions

Great that the partition table is parsed! However, we should probably

filter out null/zero partition entries,
respect partition_entry_lba and num_partition_entries. We can't necessarily assume that the partition entry table is a fixed size. The table may be 128 entries on Windows and 256 entries on Linux, for example. We also can't be sure the table follows directly after the header - it may be at a different LBA, and depending on the sector size the header is padded with varying number of zero bytes
https://github.com/PizieDust/ocaml-gpt/blob/e2c6f75c1bc92a955b317fcb0b889ac2f2c6406d/lib/gpt.ml#L327-L342

As we discussed we would need to do the unmarshaling in stages - either by making a state machine out of Gpt.unmarshal or we remove the partitions field from Gpt.t and have separate Gpt.unmarshal_header and Gpt.unmarshal_partition_entries.

In the end it made sense to keep partitions in Gpt.t as e.g. the partitions_crc32 field depends on the partition table (or at least its checksum).


The basic mechanics need implementing

So we need:

[ ] The start of the game
[ ] The end of the game
[ ] Randomly generated planetmos map
[ ] Villages/Towns
[ ] Proc-gen weapons? :godmode:
[ ] Respawn mechanic
[ ] Leveling up + evolution (...trees?)
[ ] Skills
[ ] Unlockable Passives + Skills
[ ] Unique unlockable passives + skills for each species

[https://tgstation13.org/wiki/Wizard](https://tgstation13.org/wiki/Wizard this page has spells you can make


Adding permissions

Added encryption to dbSettings and rcon so passwords are not stored plaintext in the database.
Commit https://github.com/Stormyy/b3cod4x/commit/69fe9d5e5b7510326d4f07e1a4ced17d569a7141.
If you are going to update you have to change the mysql field dbSettings (table b3servers) from json to text. This because i json is not fully supported by laravel and this can't be done with migrations.

Currently creating claim process where you have to claim a ingame player. You will have the same rights as in the b3server. Will commit these changes soon. The changes include a custom cod4x plugin

Added in v1.0


Refactor

Hi, this is probably overkill but was a fun little exercise this evening to make some changes which I'd have made or requested to this library if I'd have been reviewing this code internally prior to putting it to use.
I'm offering not in the spirit of "hey that code is wrong", but rather just taking the compact little module you wrote and trying to show how I might tweak it to to be more idiomatic, so please feel free to ignore or include any of these changes at will
The main things I'd hope you'd takeaway would be: 1) try to always handle errors and avoid panics (I'm looking at the string type assertion here) , 2) always use gofmt on your code (in fact configure your editor to automatically run gofmt on save as it just removes any debate about how to format stuff from within your team, and 3) in general try to avoid using the generic interface{} type - almost always you should prefer a concrete type, a.k.a type safety is great.
hope you continue to enjoy writing Go etc.
cheers
Sam

Thanks for this. I appreciate all the effort you put into it.
My gut reaction was "I don't like these changes".... but that was my mind in "Node.js" mode. After reflecting on it, I think the idiomatic approach with error handling makes more sense from a community adoption perspective. After all, that's the "Go" way.
Good catch on the generic interface. If this were only a JSON parser, the generic interface would be necessary, but in this case it absolutely isn't (since everything will always be a string).
The one I have a hard time with is gofmt, which is something that has come up in another Go project I have (which is not a library, just an app people use). I absolutely can't stand the formatting.
Anyhow, that's my long winded way of saying thank you.
Oh, and extra kudos for adding the extra tests/missing Clear test.

Ah, no problem was a fun palate cleanser. The error handling in Go certainly bothered me at first too, but now I just feel weird if it's not there. Interestingly I think Go 2 is planned to have some new syntax for error handling that will eliminate some of the repetition. It's not finalised yet but interested to see how that develops.
Gofmt may not be your favourite but particularly when working in a team it's great to have a tool that just takes away any nit-picky debate about formatting meaning you can just concentrate on the actual logic.


Adding a type factory to the Select widget

https://t.me/aiogram_dialog/28587

/closes #124

@vlkorsakov Need same for Radio/Multiselect


chore(main): release alma9-systemd 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-03-03)
Features

alma9-systemd: add a dockerfile for building an alma9 image with systemd support (#13) (9cf1c2e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mateusz-uminski/dockerfiles/releases/tag/alma9-systemd-v0.1.0 :sunflower:


Ok v2

😻

whoever did the gradle mixin args must be so smart and cool and sexy

https://github.com/zPeanut/Hydrogen/blob/05ea2bf35970d782ae0472eda593153930ccef49/build.gradle#L1
It should be self explanatory


charts: Add ReservedCodeCacheSize and jdk.nio.maxCachedBufferSize to presto JVM options

As recommended by the presto deployment documentation.

/retest

/retest

/retest

/retest

/retest

/retest


IPAM: Adds AWS ENI IPv6 Prefix Delegation Support

Previously, ENI prefix delegation support was limited to IPv4.
This PR updates existing structs, methods, etc. to support IPv6
prefix delegation. The overall implementation follows the existing
approach taken for IPv4 prefix delegation.
Although AWS assigns a /80 prefix to an ENI, 64 addresses are the
maximum number of allocatable addresses. This restriction can be user
configurable in the future if needed.
Fixes: #19251
Fixes: #18405
Adds "aws-enable-ipv6-prefix-delegation" configuration flag to enable IPv6 prefix delegation support for ENI IPAM mode in AWS.

Includes commit 3b20d9cd3a91fc7232ccf2812343bc028054b252 from #31145. When #31145 is merged, I will rebase to remove this commit so ignore this commit from your review.

@danehans The main commit here is quite long, would it be possible to break this down into a couple smaller commits to make the changes easier to review/understand?

@danehans The main commit here is quite long, would it be possible to break this down into a couple smaller commits to make the changes easier to review/understand?

@tommyp1ckles thanks for reviewing the PR. I originally broke the PR into ~4 commits but the Check if build works for every commit CI job was failing. Let me know if you have any suggestions on the best way to break the PR up into multiple commits that will pass this job.

Some example PRs from recent large-size change sets:
https://github.com/cilium/cilium/pull/32336/commits
https://github.com/cilium/cilium/pull/32125/commits
In these case I believe the reviewers also held some conversations to explain the changes to the reviewers.

To verify the e2e functionality of this PR, perform the following steps:
Create an EC2 cluster:
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
  name: cilium
  region: us-west-2
kubernetesNetworkConfig:
  ipFamily: IPv6
addons:
  - name: vpc-cni
  - name: coredns
  - name: kube-proxy
iam:
  withOIDC: true
managedNodeGroups:
- name: ng-1
  desiredCapacity: 2
  instanceType: t3a.small
  ssh:
    allow: true
  # privateNetworking: true
  # taint nodes so that application pods are
  # not scheduled/executed until Cilium is deployed.
  # Alternatively, see the note below.
  taints:
   - key: "node.cilium.io/agent-not-ready"
     value: "true"
     effect: "NoExecute"

Note: withOIDC: true is required for IPv6 based on the eksctl docs and I disabled privateNetworking to verify the kernel version of instances using SSH.
Patch VPC CNI:
kubectl -n kube-system patch daemonset aws-node --type='strategic' -p='{"spec":{"template":{"spec":{"nodeSelector":{"io.cilium/aws-node-enabled":"true"}}}}}'

Before installing Cilium, a few dependencies must be met. First, create an IAM policy doc required for the operator to function:
$ cat eni-policy.json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "ec2:DescribeNetworkInterfaces",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:ModifyNetworkInterfaceAttribute",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:AssignPrivateIpAddresses",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:AttachNetworkInterface",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:DescribeTags",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:CreateTags",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "ec2:CreateNetworkInterface",
      "Resource": "*"
    }
  ]
}

Create an IAM policy using the above policy document:
aws iam create-policy --policy-name CiliumENIPolicy --policy-document file://eni-policy.json

Attach the IAM policy to the node instance role created by eksctl. First, extract the node role from the node group:
aws eks describe-nodegroup --cluster-name cilium --nodegroup-name ng-1 | jq -r '.nodegroup.nodeRole'

Attach the IAM policy to the node group:
aws iam attach-role-policy --role-name eksctl-cilium-no-NodeInstanceRole-XmmjKuDUfvxd --policy-arn arn:aws:iam::552234177002:policy/CiliumENIPolicy

Next, the Cilium ipv6NativeRoutingCIDR configuration flag must be set to IPv6 network of the AWS VPC. Get the VPC ID and save it as an environment variable:
export VPC_ID=$(aws ec2 describe-vpcs --filters "Name=tag:alpha.eksctl.io/cluster-name,Values=cilium" --query "Vpcs[].VpcId" --output text)

Get the IPv6 CIDR for the VPC and save it as an environment variable:
export VPC_CIDR=$(aws ec2 describe-vpcs --vpc-ids $VPC_ID --query "Vpcs[].Ipv6CidrBlockAssociationSet[].Ipv6CidrBlock" --output text)

Build and push images:
agent build/tag/push:
ARCH=amd64 DOCKER_DEV_ACCOUNT=docker.io/danehans DOCKER_IMAGE_TAG=ipv6-pd-latest make dev-docker-image

aws-operator build/tag/push:
ARCH=amd64 DOCKER_DEV_ACCOUNT=docker.io/danehans DOCKER_IMAGE_TAG=ipv6-pd-latest make docker-operator-aws-image

Due to the following Cilium daemon error, set the VPC IPv6 CIDR range for each node:
`level=fatal msg="Cannot autocomplete node addresses" error="IPv6 allocation CIDR is not configured. Please specify --ipv6-range" subsys=daemon`

Annotate each node with network.cilium.io/ipv6-pod-cidr=$VPC_CIDR.
Wait for Cilium to be ready:
cilium status --wait

I used my CiliumCon IPv6 demo to verify functionality. Note that the kernel version for instance t3a.small does not support BIG TCP.

/test

@tommyp1ckles Once this has been approved and merged in, can you advise how frequently you release new minor versions? We're trying to gauge how far off this feature is from being GA. TIA

Heads up that https://github.com/cilium/cilium/pull/31145 will need to be also added back into this effort if someone revives this PR.

@joestringer I talked to @danehans and he is not going to be able to move forward with this PR. Do you think a maintainer could take over his work ?

Hello! Is the work ever going to merged in the future?

@joestringer I talked to @danehans and he is not going to be able to move forward with this PR. Do you think a maintainer could take over his work ?

@joestringer is there anything you or one of cilium's maintainer could do ?

Cilium relies on the contributions from volunteers in the community to implement functionality that they find important. I would encourage contributors to chat with one another, collaborate on what they see as the solutions, and make proposals to move this forward step by step. Personally I don't have the bandwidth to tackle this at the moment.

Hi, I'm going to be working on this in a few months, I could do some PR on @danehans repo

What work does the @danehans need to be acceptable? The above review looks to be mostly minor requests?

I believe https://github.com/cilium/cilium/pull/32352#discussion_r1617183868 is the biggest concern which I think will need some serious engineering work to get resolved.


Feature request: option to reuse first creator for contact

the contact is required. And its likely to be the same person as the data owner. So an option could be a check box that says
[] use first creator for contact
and if checked, uses whatever is in creator 1's object to populate it.
this would be similar to "use billing address for shipping address", which most people are used to.

Done, via ability to import from the current data package as well as any other data package.


Source maps include full local path names, not shown in original folders

When I bundle with this command - watchify main.js -t reactify -o bundle.js -v -d the source file names appear in devtools with the file name including the full local file path and they are not shown in their nested folders.
This causes a few problems with many files as it is hard to see which file you are looking at.
I have posted a SO question which includes some screenshots that might help explain what I mean.
Is there a solution to this or am I doing something wrong?
Thanks
(If cross posting or linking etc. is frowned upon let me know and I will remedy- i am new to issues on github)

I had someone answer this on the  SO question.
It was a browserify option that fixed the issue- adding --full-paths=false to the comman worked. This is the final command that worked for me.
watchify main.js -t reactify -o bundle.js -v -d --full-paths=false

@davepile You're probably using an old version of watchify. Prior to 2.5.0, fullPaths was required for the caching to work, thus the CLI automatically added it. If you update to a newer version, you won't have to set --full-paths to false, since that's already the default.

@zertosh - I have watchify 2.5.1 installed globally and in the project


fix coveralls reporting

fixes #128

Changes Unknown when pulling 01c9987725149e3c522d4a5bb2a05d9ba62ad640 on ryan-williams:coveralls into ** on HadoopGenomics:master**.

Thanks for fixing this @ryan-williams!


Problem with layout

Hello I'm having a hard time getting started. Basically to get a simple appbar and a docked leftnav what's the code? Right now my problem is that I have an 8px margin on my appbar I can't get rid of, and my leftnav is above the rest of the screen, not beside like a regular side menu... Thanks!
My code is as follows

              <LeftNav
                disableSwipeToOpen={true}
                docked={true}
              />

              <AppBar title="Test"/>

                  <RaisedButton primary={true} label="Tap"/>

                  <DatePicker hintText="Portrait Dialog"/>

                  <DatePicker
                      hintText="Landscape Dialog"
                      mode="landscape"/>

ok my mistake I assumed the LeftNav component worked like the Drawer component in React Native, but that's not the case. It's just an overlay. And I though the library had a responsive layout but that's not the case.


Cannot setequality

Hi Jaiq,
I want to filter grid when first load but it's not work filter grid with null value, any suggestion?
SetEquality("ApprovalDate",  null);
    protected override bool OnViewSubmit()
    {
        if (!base.OnViewSubmit())
            return false;

        SetEquality("UserID", Authorization.UserDefinition.UserId);
        SetEquality("ApprovalDate",  null);

        return true;
    }

SetEquality doesn't work with null values. Null and empty string is simply ignored. As leaving a searchbox with empty value doesn't filter.
Try this:
((ListRequest)this.View.Params).Criteria &= new Criteria("ApprovalDate").IsNull()

It works thanks Jaiq.
Regards
Rudianto


Test: transition of "auto attach" feature to new js-debug JavaScript terminal

Refs: https://github.com/microsoft/vscode/issues/88599

[ ] anyOS: @joaomoreno
[x] anyOS: @stevencl

Complexity: 3
Authors: @connor4312, @weinand

VS Code's legacy Node.js debugging supports an "auto attach" feature, which makes the VS Code debugger automatically attach to node.js programs if they were launched from the integrated terminal in debug mode (for details see https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_auto-attach-feature).
The new JavaScript debugger supports an even more elegant auto-attach: node.js programs do not have to be launched in debug mode in order to have the debugger auto attach to it (this is js-debug's new "Node.js Debug Terminal").
To provide a smooth transition experience for existing "auto-attach" users to the new js-debug functionality, we've added code that automatically transitions the "auto-attach" settings to the new settings when the user switches from the current node.js debugger to js-debug.
How to verify:

make sure to use the old node.js debugger in VS Code
have a simple long running test program, e.g. test.js:var i = 0;
setInterval(() => {
  console.log('hello world ' + i++);
}, 1000);

set a breakpoint on the console.log
enable "Auto Attach" via F1
run the program from the integrated terminal via node --debug test.js

VS Code should automatically attach to the program and stop on the breakpoint

now switch to the new js-debug
launch the program again from the integrated terminal but now via node test.js

VS Code should automatically attach to the program and stop on the breakpoint (but now in the new debugger)
Now verify more cases:

enable "Auto Attach" in the old node.js setup
switch to the new js-debug
stop VS Code
start VS Code
verify that the "Auto Attach" shows up in the status bar
verify that js-debug has not yet been activated
run node test.js from the integrated terminal
verify that the new debugger attaches automatically

TBD..
@connor4312 please correct anything that I got wrong and add more tests for corner cases you are aware of

@weinand I believe it's node --inspect test.js, instead of --debug. I've updated your instructions.


Broken link to RFC in App.vue for Vue template

Describe the bug
I've just initialized a Vue app with Vite and found that the link to RFC for <script setup> in App.vue is broken.
Should it be https://github.com/vuejs/rfcs/blob/master/active-rfcs/0040-script-setup.md?
Reproduction
https://github.com/vitejs/vite/blob/main/packages/create-app/template-vue/src/App.vue#L10
System Info
No response

Used Package Manager
yarn
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 https://github.com/vuejs/vue-next instead.
[ ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Would you open a PR for that? :slightly_smiling_face:

Of course!


Parser improvements

Fixes match parsing to include optional comma at the end of match arm body.
Parses unit (()) properly now
Fixed parsing, and added resolution and typechecking for alias.

Depends on #19 so that needs to get merged first.

Haven't checked it too thoroughly, but also seems good. Flags with aliases we can add once we have proper signatures etc.

I was going to add flags next, but it seems to be involved deeply with the parser and since you're rewriting the lexer which will move parts of the parser, I'll wait for it to settle a little bit. For now, I'll rebase once #19 is accepted and add the error for flags.

I'm closing this in favour of #29
This one became a mess after my previous PR was merged and I wasn't able to resolve it easily.


Update legobeat/l7-devenv

Repo URL:
https://github.com/legobeat/l7-devenv
Checklist:

[X] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[X] The lines end with a .. This is to conform to awesome-list linting and requirements.
[X] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[X] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else. No .. for Neovim.
[X] The description doesn't contain emojis.
[X] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[X] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

In the recently merged PR there was a wrong URL address.

Thanks for the PR!


Update object categories in Cocopen class init

       self.class_dict = {"device": 1,
                        "ethernet": 2,
                        "phone": 3,
                        "power": 4,
                        "hdmi": 5,
                        "coaxial": 6}
        self.categories = [{"supercategory": "device", "id": self.class_dict["device"], "name": "device"},
                                {"supercategory": "cable", "id": self.class_dict["ethernet"], "name": "ethernet"},
                                {"supercategory": "cable", "id": self.class_dict["phone"], "name": "phone"},
                                {"supercategory": "cable", "id": self.class_dict["power"], "name": "power"},
                                {"supercategory": "cable", "id": self.class_dict["hdmi"], "name": "hdmi"},
                                {"supercategory": "cable", "id": self.class_dict["coaxial"], "name": "coaxial"}]

These categories correspond to data on labelbox. For our current submission, we should only deal with single wire images. We should rename the folder on azure from "single-wire" to "wire" and assign the folder name to the category id. A reach improvement would be to collect images of single devices and set up auto-labeling for them so that we can demonstrate the functionality of this method on more than one object type.

Updated object categories in the config/parameters.yml file. Created a new function, generate_supercategories(self) which reads the object categories in config/parameters.yml and generates the super categories dictionary automatically. Note: this method does not include any subcategories. We are also now reading class_dict directly as class_dict=self.parameters["categories"].


Warning: Document size exceeded configured limit

Hi,
Since the update the system fills the context window very fast, while creating a very small file. With the original version the research finished around 250-300k file size (I'm running it on a single 4090), now it finishes at 20k.
Ollama is up-to-date, I tried with qwen2.5-7b-q6_K (6Gb) and phi3.5:3.8b-mini-instruct-q8_0  (4Gb), the issue appears with both. Ollama also offloads to CPU and claims 30GB memory for phi3.5:8b. It was not the case before.
The n_ctx and context_length parameters are untouched and I did create the customizing model with ollama -f.
Anyone having the same issue? Any solutions?
Thanks a lot.

On a 4090, depending on the LLM you're running, you should be able to reliably support at least 80k token context size. I've been able to run 131k token context on my 3090 on smaller models too.

Thank you. I found the reason, it's not an issue, only a contraint configured in the system_config.py: the default for max_document_size is set to 12000 character.

I have a laptop 4070, the model ask me for 80 Gib of system memory with the specified context  length in the Readme? I tried reducing it still got the same error. Is it linked?

@alex-crr the modelfile is created only for configuring a model to run with ollama with the ollama create modelname -f modelfile command

Yeah that system_config thing was because of an accidental merge I made which is fixed now redownload the github main for the original working version, that other new APIs version is now in a separate branch.


Split the the output generated by Css Mirroring into common, nativeDi…

…r and flippedDir subparts.

Thanks Monam!


js-sdk fix linter warnings from set operations

See https://github.com/momentohq/client-sdk-javascript/pull/171#discussion_r1073579719