Need ability to reuse configmaps between multiple helm chart releases

I see that you can mark a resource to not be deleted after uninstalling a release.  However, I'm still not able to reuse the configmap.  I would like to have a configmap be used over and over again by many helm releases at the same time.
The problem that I run into is that once the configmap is created, if I install another helm release, then it fails because the configmap already exists.  On install I would like the ability to successfully install if a configmap already exists.  It could update it or simply just ignore the error.

@k8vance88 so if I'm understanding this correctly, you are doing the following:
$ helm install mychart --name foo
$ helm delete foo
$ helm install mychart --name foo

Is this correct?

If so, there are two ways to make this work:

Option 1: deleting the old release using `--purge`:

$ helm install mychart --name foo
$ helm delete foo --purge
$ helm install mychart --name foo

Option 2: upgrading the old release:

$ helm install mychart --name foo
$ helm delete foo --purge
$ helm upgrade foo mychart

Does this help solve your issue, or am I mis-interpreting your issue? Please let me know! :)

Actually we are thinking you may install the chart more than once.  Where both versions are running at the same time independently.

Ah, gotcha. Thank you for clarifying!
This sounds like an interesting feature. I would love to hear more about this in the form of a design document! That way we can talk in more detail about the design decisions required to make this work as  well as any proposed changes to Helm that may or may not be breaking changes in the API.

Do you have a design doc template?

We don't have a template, but a good practice is to describe the following, each in their own section:

Abstract: a short (~200 word) description of the technical issue being addressed.
Specification: The technical specification should describe the syntax and semantics of the feature. The specification should be detailed enough to give users (and maintainers) a reference to better understand the feature.
Motivation: Clearly explains why the existing workflow is inadequate to address the problem that the proposal solves.
Rationale: The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other tools related to Helm.
Backwards Compatibility: If this feature introduces backwards incompatibilities, it must include a section describing these incompatibilities and their severity. The proposal must explain how the author proposes to deal with these incompatibilities.

Abstract:
Ability to have installed multiple instances of the same Helm chart (at the same time) such that all instances (releases) share the same configmaps.
Specification:
The helm chart developer would mark resources as sharable.  The helm chart install would then update rather than create the resource. A sharable resource would only be deleted (upon deletion of a helm release) if no other helm release was using it (or if no other instance of the same helm chart is installed).
Add new annotation for helm chart developer to mark a resource as sharable:
helm.sh/resource-policy: sharable
Example:
apiVersion: v1
kind: ConfigMap
metadata:
name: my-sharable-configmap
annotations:
"helm.sh/resource-policy”: sharable
Motivation:
Currently, if I try to install two of the same helm charts with the same config map, the 2nd deployment fails because the shared configmap already exists. I could solve this issue by giving each configmap a unique name per release. However, the duplication is unnecessary because the configmaps would be identical.  It's unknown how many releases a user will deploy at the same time (could be tens to hundreds).
Rationale:
The nature of some helm chart deployments is such that many instances of the same chart will be deployed at the same time.  Helm chart installation does not allow for multiple instances of the same chart to be installed if the helm chart has resources that are not uniquely named.
One workaround would be to create the configmap as a pre-req to installing the helm chart(s), but that creates extra steps and is error prone for the user (and isn't the helm chart supposed to deploy everything for you).  Another workaround that has been considered is to create a job that will create the shared resources.  The job would also need to be deleted after the helm install. This approach is less than ideal because it takes time to run the job and is a performance hit on the helm chart installation.
Backwards Compatibility:
Backwards compatibility should not be an issue because the annotation would be new.  Also, behavior will only change if user has added the annotation.  If the chart developer introduces a new version of their helm chart and updates a shared configmap, then the helm chart developer should change the name of the new configmap so that older installations of the configmap will continue to use the older version.

Just ran into this limitation. In my case I was trying to modify the TCP services ConfigMap that the nginx ingress controller watches to configure TCP ingress to services.

/remove-lifecycle stale

Another possible use case:  A large project has charts used by multiple apps placed in common directory.  One of these  common charts might contain a configMap, defined once, but referenced by all instances of apps that require that common chart.

The use case I'm running into now is shared ClusterRoles with per-chart ClusterRoleBindings.
So have e.g. 10 Ingress controllers with 1 ClusterRole and 10 ClusterRoleBindings.
How about we make e.g. the release tag a list rather than a string (for example, I don't exactly know how Helm keys itself to it's generated objects).
Each release would add/pop itself on/off the list.
Once it is empty, the object would be up for deletion.
Sharing would thus be either implied or dependent on @k8vance88 's sharable annotation

Interesting workaround/ugly haxorz: https://github.com/helm/helm/issues/2680#issuecomment-408212936

is there any solution being addressed to this issue??

The nginx ingress feature alone would be a huge win. Another use case is to add alert rules to prometheus, I'm sure there are others where a shared configmap where helm does an upsert would be very nice.

We haven't seen any movement from the community on this proposal, so I'm going ahead and closing this due to inactivity. As of https://github.com/helm/helm/pull/7649, resources cannot be shared/upgraded by multiple releases anyways, which prevents cases like helm delete releaseA deleting a configmap releaseB relied upon.

@k8vance88 Did you find any hack around for this use case?

Abstract:
Ability to have installed multiple instances of the same Helm chart (at the same time) such that all instances (releases) share the same configmaps.
Specification:
The helm chart developer would mark resources as sharable. The helm chart install would then update rather than create the resource. A sharable resource would only be deleted (upon deletion of a helm release) if no other helm release was using it (or if no other instance of the same helm chart is installed).
Add new annotation for helm chart developer to mark a resource as sharable:
helm.sh/resource-policy: sharable
Example:
apiVersion: v1
kind: ConfigMap
metadata:
name: my-sharable-configmap
annotations:
"helm.sh/resource-policy”: sharable
Motivation:
Currently, if I try to install two of the same helm charts with the same config map, the 2nd deployment fails because the shared configmap already exists. I could solve this issue by giving each configmap a unique name per release. However, the duplication is unnecessary because the configmaps would be identical. It's unknown how many releases a user will deploy at the same time (could be tens to hundreds).
Rationale:
The nature of some helm chart deployments is such that many instances of the same chart will be deployed at the same time. Helm chart installation does not allow for multiple instances of the same chart to be installed if the helm chart has resources that are not uniquely named.
One workaround would be to create the configmap as a pre-req to installing the helm chart(s), but that creates extra steps and is error prone for the user (and isn't the helm chart supposed to deploy everything for you). Another workaround that has been considered is to create a job that will create the shared resources. The job would also need to be deleted after the helm install. This approach is less than ideal because it takes time to run the job and is a performance hit on the helm chart installation.
Backwards Compatibility:
Backwards compatibility should not be an issue because the annotation would be new. Also, behavior will only change if user has added the annotation. If the chart developer introduces a new version of their helm chart and updates a shared configmap, then the helm chart developer should change the name of the new configmap so that older installations of the configmap will continue to use the older version.

@k8vance88 Did you find any hack around for this use case?

@Kaali09, not a great solution. but we deleted the config maps using a job hook that ran during uninstall.

@k8vance88 I know this is a closed issue but how did you manage to contact the k8s api using a job hook?

@k8vance88 I know this is a closed issue but how did you manage to contact the k8s api using a job hook?


Unit Testing for ShapedRecipeBuilder

Automatically converted from #26

Please see this comment as to why this was closed.


Your model trained with 4 GPU(12gb) machine does not perform well.

Your model trained with 4 GPU(12gb) machine does not perform well. Can you provide a set of parameters suitable for 4-gpu (12gb)?

Dup #108


fix: do not ignore errors

Description
Issue https://github.com/asyncapi/cli/issues/1475 gives an example where an invalid external reference is ignored, and all other documents are skipped. Instead of silently failing, this PR proposes to let the error propagate.
Related issue(s)
Fixes https://github.com/asyncapi/cli/issues/1475

I do not normally do try...catches only for the sake of error-swallowing, so I surely did it for some reason, but I honestly do not remember for what exactly.
Either that use case has already been taken care of, or I will see the same edge case and process it in another way.
@souvikns, this PR looks good to me, but can you please do this simple review only so I'm not reviewing my own code?
Also, should the title be fix: remove obsolete try...catch ?

/rtm


[question] Why not check that arguments are used?

I expected "bar" is defined but never used in this code, but got nothing.
function foo (bar) {
  return true
}
foo()

I've found it's because of this setting. But I couldn't find the reason.
"no-unused-vars": [2, { "vars": "all", "args": "none" }],

https://github.com/feross/eslint-config-standard/blob/master/eslintrc.json#L104
http://eslint.org/docs/rules/no-unused-vars.html#args
I think it should be { "args": "all" } or { "args": "after-used" }.
It seems this change was made in this commit.
https://github.com/feross/standard/commit/72765c25507bb1b459dddaa6a8f57f28b180e5a9#diff-da50a6bc6687fde49b3a83e1f9ad2c4fR97
Is there still any reason that it doesn't check arguments?

The reason was, for me at least, that express (the web framework) requires a certain number of arguments to a middleware for it to be considered an error handling middleware:
app.use(function(err, req, res, next) {
  // logic
})

In principle this rule is decent, and could help catch errors. But it might be too late to stick this in there, unless we add
Here's a test run on the top ~400 packages that use standard based on npm dependency count:
# tests 427
# pass  301
# fail  126

with this setting:
    "no-unused-vars": [2, { "vars": "all", "args": "after-used" }]

So, maybe this will have to wait until there's a standard-strict or a future major version.

Makes sense. Thanks for response!


Delete subscription not working

Describe the bug
A clear and concise description of what the bug is.
Have you read the Contributing Guidelines?
Yes
To Reproduce
Steps to reproduce the behavior:

Enable subscriptions in resolver
Subscribe to deletedOne or deletedMany
Trigger a deleteOne or deleteMany mutation

Expected behavior
The subscription should trigger if an object was deleted.
Screenshots
n/a
Desktop (please complete the following information):

Node Version: 14.14.0
Nestjs-query Version: 1.1.2

Additional context
The other subscriptions, like updated and created are working fine, but deleted not.

I can confirm this, AuthFilter is lost for delete subscriptions. Mentioned 13 days ago at #45. @TriPSs please merge.

This is fixed thanks to @windose ❤  Released in version v1.1.3


Regression: tests settigns do not show up when opening AxoCover after a solution is loaded

It happens only when AxoCover is loaded at the first time. If it has been loaded once, it will work.
Workaround: Can be resolved by simply closing and reopening the solution.

Fixed it.


fix: reference to link in model

The link in the custom control is referenced incorrectly and is therefore not displayed.
It has been replaced with the correct 'this' reference.

Thanks, again


Pagination

why there is no navigation through pages, it is not convenient when all comm displayed? (sorry for my English)

Hi, We have started the new comments module 2.0 with the following features:

pagination
moderation
and other small changes

do you have a beta version ?)

Please, consider possibility of translating module without global language
settings and possibility for comment author to change/delete the comment.
It is fine to give that rights to administration role but it really should
be on author level too. Soft delete is OK. I will contribute if I develop
those features myself.
23.11.2016. 13.05, "Igor Chepurnoy"<EMAIL_ADDRESS>је
написао/ла:

Hi, We have started the new comments module 2.0 with the following
features:

pagination
moderation
and other small changes

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/yii2mod/yii2-comments/issues/36#issuecomment-262496536,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEv4-xGMyRkIns0CpIWevegcZ-XZmQSIks5rBCv-gaJpZM4K6Ecr
.

@eolitich

do you have a beta version?

No, we don't have enough time.

@Gawran  Thanks for your feedback.

Resolved in release https://github.com/yii2mod/yii2-comments/releases/tag/1.9


Let Registry constructor argument override default types

With the addition systen, the constructor argument and the register method do the same and there is no way to get rid of Coin and MsgSend.

This requires adding Coin to defaultRegistryTypes.

Just to be sure: You mean these two methods here?
  public constructor(customTypes: Iterable<[string, GeneratedType]> = []) {
    const { cosmosCoin, cosmosMsgSend } = defaultTypeUrls;
    this.types = new Map<string, GeneratedType>([
      [cosmosCoin, Coin],
      [cosmosMsgSend, MsgSend],
      ...customTypes,
    ]);
  }

  public register(typeUrl: string, type: GeneratedType): void {
    this.types.set(typeUrl, type);
  }

So the result should look like that?
public constructor(customTypes: Iterable<[string, GeneratedType]> = []) {
    this.types = new Map<string, GeneratedType>([
      ...customTypes,
    ]);
  }

  public register(typeUrl: string, type: GeneratedType): void {
    this.types.set(typeUrl, type);
  }

The old types
      [cosmosCoin, Coin],
      [cosmosMsgSend, MsgSend],

could remain in the registry when no constructor argument is set. Then new Registry() is non-breaking. For this to happen we need to turn the default = [] to an optional. Once the constructor argument is set, it overrides the defaults instead of appending.


Do not change color of selected file in file explorer

Filename color should not be changing color when selected in the file explorer. This happens when folders are selected as well.
Filename text turns white when selected for both error warnings and git modifications. This makes sense to avoid conflicts with colorful highlights, but for people who use neutral highlighting, the color change is distracting as well as quite confusing. This should be a choice for users to make.
How it appears when selecting:

Without changing color it should look like this:

/duplicate of #53998


GCP Cloud Services - Custom KSA Names in Targets

Hi!
You could make the google cloud targets also have the configuration to use KSA, resolved in #1372?
Thanks!

Hi @apenen, thanks for raising this issue. Sounds like a logical improvement, we'll keep it on our radar.
Feel free to join our Slack if you haven't already, we'd love to know more about your use case.

Thanks!


Add ability to template the name of a step in a Factotum DAG

This would allow us to have generic DAGs which we can then personalise so that the webhooks have more meaningful information.
cc/ @ungn

This function needs to be altered from following the stack calls:
https://github.com/snowplow/factotum/blob/master/src/factotum/parser/mod.rs#L129-L132
We just need to call templater::decorate_str on the task name eagerly from what I can see.

@jbeemster, the title suggests name in the DAG's steps. Could the name of the DAG itself be templated as well?
"schema": "iglu:com.snowplowanalytics.factotum/factfile/jsonschema/1-0-0",
"data": {
    "name": "{{...}}",          <-- DAG name
    "tasks": [
        {
            "name": "{{...}}",  <-- DAG step name

Hi @ihortom I already did that in this ticket: https://github.com/snowplow/factotum/issues/117
TLDR; yes!


docs: use "remember-me" everywhere

I'm not sure I see it hyphenated like that very often. What prompted this change?

Since remember-me seemed to be the most commonly used in the source code comments, I adapted it.
It is easy to search.

I like the hyphen or quotes:

remember-me token
"remember me" token

We could also use a noun adjunct:

remembrance token
persistence token

I guess I didn't remember I had hyphenated it anywhere lol
We can hyphenate, that's fine.


std.format: Tweak format string docs

Add grammar links and headings.
Add example for positional format spec, move existing paragraph.
Document %u format char.
Make array examples runnable.

While I'm normally quite happy, when people try to improve Phobos, for me, this PR is a little bit inconvenient. Since about a month I'm reworking std.format completely. I started with splitting the module in several sub modules, refactored most of it and since last weekend I'm reworking the docs. There are four functions left:  formatValue is in review state (#7911), formattedWrite in preparation, the other two (unformatValue and formattedRead I will probably postpone a little bit, because I need to better understand the read part which I treated up to now a stepmotherly, before doing so.
After that I planned to rework the module docs, like this PR does, but on a much more thorough base (there is much more undocumented stuff and there are more things, that need to be corrected). A lot of this rework, I have already done locally (weeks ago), but not added yet, because I can't do everything at once and always have to wait until the changes are reviewed.
So forgive me, asking you to revoke this PR. Would you mind me?

@ntrel What are your thoughts on @berni44 's comments?

ping @ntrel

If @berni44 has incompatible changes then it's ok with me to close this. I'd like to know when they're submitted. BTW this has ddoc problem anyway where $(DL is not expanded for some reason. I couldn't work out why.

I'd like to know when they're submitted.

Partly they are already submitted see #7919. The followup #7935 is currently in review process, and when this is merged, I think, there will about three or four more to follow until the docs are completed. My goal is to get this finished before next stable is branched off. Looks like we are well in our schedule.

It seems like @berni44 is on top of this. @ntrel thanks anyway for your work and sorry for not being able to merge this.


Fix issue #122

I think this should fix it, but I can't run the bot because i don't have the api url and key.

If I could get the api url and key it would make testing stuff easier, but idk if the api is owner only or something


Support for Kubernetes v1.20

How to categorize this PR?

/area open-source usability
/kind enhancement
/priority normal
/merge keep-commits
/exp intermediate
/topology garden seed shoot
What this PR does / why we need it:
Support for Kubernetes v1.20
Which issue(s) this PR fixes:
Part of #3260
Special notes for your reviewer:

I didn't vendor new k8s.io/* Golang sources yet - @timebertt plans to update to kubernetes-v1.19 as part of #3109.
⚠ This PR only contains the Gardener part for supporting 1.20 - there will/must be follow-up PRs for each extension repository where individual support gets added.

Release note:

Gardener can now support shoot clusters with Kubernetes version 1.20. In order to allow creation/update of 1.20 clusters you will have to update the version of your provider extension(s) to a version that supports 1.20 as well. Please consult the respective releases and notes in the provider extension's repository.

Apart from the failed verify step, it looks very good to me. I played with the PR locally extensively (seed bootstrap for v1.20; hibernation and wake up with v1.20; dynamic volume provisioning with CSI; worker pool with CRI; switch between IPVS and IPTables; worker with suse-chost) and it worked as expected.
/lgtm

@ialidzhikov I've pushed a new commit 588143d which fixes the verify step, PTAL.

I played with the PR locally extensively (seed bootstrap for v1.20; hibernation and wake up with v1.20; dynamic volume provisioning with CSI; worker pool with CRI; switch between IPVS and IPTables; worker with suse-chost) and it worked as expected.

That's awesome, thank you very much for your time and efforts and extensive testing, highly appreciated. 👏

Thanks for your reviews, guys! I'm going ahead merging this now and marking the respective PRs on the provider extensions as ready for review.


Add Phrase configuration file

Tell Phrase what our strings files look like. This is read by Phrase when it
imports from GitHub.

Current dependencies on/for this PR:

main

PR #1052   👈

This comment was auto-generated by Graphite.


fix: endpoint configuration issue

Resolve endpoint configuration issue by removing EXHORT_DEV_MODE environment parameter.

Codecov Report
Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (44fc91e) 75.63% compared to head (3e4da04) 85.31%.
Report is 4 commits behind head on master.

Files
Patch %
Lines

src/exhortServices.ts
20.00%
4 Missing :warning:

src/redhatTelemetry.ts
50.00%
4 Missing :warning:

src/config.ts
95.34%
0 Missing and 2 partials :warning:

src/stackAnalysis.ts
95.65%
0 Missing and 2 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #672      +/-   ##
==========================================
+ Coverage   75.63%   85.31%   +9.68%
==========================================
  Files          10       12       +2
  Lines         238      286      +48
  Branches       37       39       +2
==========================================
+ Hits          180      244      +64
+ Misses         51       35      -16
  Partials        7        7

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


Environment images are not available for job runs after update

Describe the bug
Environment images are not available for job runs after update
To Reproduce
Steps to reproduce the behavior:

Create a cron job
Update Orchest
Environment image is deleted
Build is not triggered for environments referenced in cron jobs
When a job triggers a pipeline run, the run fails because no environment image is available

Expected behavior
The job should succeed in running after an update.
Environment

OS: Linux server
Browser: Chrome
Version: 2021.06.1
Environment: prod, cloud.

Depending on how we approach this issue, it is probably good to be aware of #310.


Input required on how to require authentication for non-WFP users for specific data layers

In the context of Cambodia, data collected through mobile forms (Kobo toolbox) should not be accessible to the general public. There's a need to explore potential solutions which can 1) securely authenticate PRISM Cambodia users within government, 2) be compatible with WFP's own requirements on user authentication, 3) not require a WFP login.

@wadhwamatic closing for now, if 4 is true we might need to revisit the logic a bit. For now it seemed that all the forms we were looking at had a Province field.


Fix fix16_mat3_t alignment to 4 bytes instead of 64

fix16_mat3_t being aligned to 64 bytes is just wasteful, revert that to 4 bytes.

@razor85 I was going to merge this, but with a 16-byte alignment. For some reason, it was auto merged. I'm exactly sure why.
I'll go ahead and fix this manually.

16-byte is still pretty bad, mainly when doing operations with the DSP (wasting space). Why did you choose that?

The reason is for cache alignment (16-byte cache line).
Is the issue here that you have a contiguous set of matrices, and you
calculate the pointer to the next matrix by adding 36 (or 9) to the pointer?
On Sat, Sep 25, 2021 at 11:18 AM Romulo Fernandes @.***>
wrote:

16-byte is still pretty bad, mainly when doing operations with the DSP
(wasting space). Why did you choose that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ijacquez/libyaul/pull/73#issuecomment-927162799, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACFIQI4VQIAMH7OKUNSANDUDYG6XANCNFSM42VOHR5Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Yes but inside the DSP so its just a MC0 access. Also when doing DMA there.
Sent from Yahoo Mail for iPhone
On Sunday, September 26, 2021, 10:28 AM, Israel Jacquez @.***> wrote:
The reason is for cache alignment (16-byte cache line).
Is the issue here that you have a contiguous set of matrices, and you
calculate the pointer to the next matrix by adding 36 (or 9) to the pointer?
On Sat, Sep 25, 2021 at 11:18 AM Romulo Fernandes @.***>
wrote:

16-byte is still pretty bad, mainly when doing operations with the DSP
(wasting space). Why did you choose that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ijacquez/libyaul/pull/73#issuecomment-927162799, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACFIQI4VQIAMH7OKUNSANDUDYG6XANCNFSM42VOHR5Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Got it. The more common use case would be dealing with matrices on the CPU.
Would this be useful?
#define MATRIX_SIZE (9 * sizeof(fix16_t))
#define MATRIX_COUNT 10
static fix16_t _matrices[(MATRIX_SIZE * MATRIX_COUNT] __aligned(4);

// Access matrix X:
fix16_mat3_t * const matrix = &_matrices[X * MATRIX_SIZE];

I guess another solution would be to make 16-byte alignment the special
case...
On Sun, Sep 26, 2021 at 12:33 PM Romulo Fernandes @.***>
wrote:

Yes but inside the DSP so its just a MC0 access. Also when doing DMA there.
Sent from Yahoo Mail for iPhone
On Sunday, September 26, 2021, 10:28 AM, Israel Jacquez @.***> wrote:
The reason is for cache alignment (16-byte cache line).
Is the issue here that you have a contiguous set of matrices, and you
calculate the pointer to the next matrix by adding 36 (or 9) to the
pointer?
On Sat, Sep 25, 2021 at 11:18 AM Romulo Fernandes @.***>
wrote:

16-byte is still pretty bad, mainly when doing operations with the DSP
(wasting space). Why did you choose that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ijacquez/libyaul/pull/73#issuecomment-927162799, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AACFIQI4VQIAMH7OKUNSANDUDYG6XANCNFSM42VOHR5Q
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ijacquez/libyaul/pull/73#issuecomment-927358226, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACFIQPP6EOR6C32CKGQXHTUD5YOZANCNFSM42VOHR5Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Got it. The more common use case would be dealing with matrices on the CPU.
Would this be useful?
#define MATRIX_SIZE  (9 * sizeof(fix16_t))
#define MATRIX_COUNT 10

static fix16_t _matrices[MATRIX_SIZE * MATRIX_COUNT] __aligned(4);

// Access matrix X:
fix16_mat3_t * const matrix = &_matrices[X * MATRIX_SIZE];

I guess another solution would be to make 16-byte alignment the special case...

I just went ahead with the 4-byte alignment like you suggested.

Thanks! The other trick wouldn’t work because the alignment would still make it bigger than needed
Sent from Yahoo Mail for iPhone
On Wednesday, September 29, 2021, 2:38 AM, Israel Jacquez @.***> wrote:
I just went ahead with the 4-byte alignment like you suggested.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Husky throws an error if ganache-core is a dependency in a project

Expected Behavior
Expect Husky not to throw an error on Git commands.

Your Environment

Version used: 2.10.2
Operating System and version: MacOS Catalina 10.15.3 (19D76)

I'm seeing the exact same problem. The issue is that you are including husky in your shrinkwrap file.

Are there any plans to fix this?

Yes! I'll try to get it done next week.

I can confirm that 2.11.0-beta.0 fixes this

Hey @davidmurdoch, this happened once again, and<EMAIL_ADDRESS>pulls its dev dependencies, including husky, once again.

Thanks, @alcuadrado! It should already be fixed in the latest alpha release that I'm smoke testing now.

I just tried the alpha release, and it doesn't include husky, nor compiles any native dependency 🎉
When can we expect this to be released as non-alpha nor beta?

Thanks for giving it a try @alcuadrado! What version of node did you install with?
And for release to beta, maybe today, and if that goes well, stable should be released by end of week, maybe even sooner.

Awesome news!
I tried it with node v10.22.1 and npm v6.14.6

Fixed (again) in https://github.com/trufflesuite/ganache-core/releases/tag/v2.13.0-beta.0 and https://github.com/trufflesuite/ganache-cli/releases/tag/v6.11.1-beta.1


Update setup.py to remove setuptools deprecation

Running python setup.py install outputs the following warning:
/home/john/anaconda3/envs/py39/lib/python3.9/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.

This is fixed in master now.


28 refactoring

Those fixes add fill_data_gaps() into data_to_csv_file(), so it will be processing any data coming from DB.
Also, added function to retrieve the list of measurements from current DB.

Coverage remained the same at 96.951% when pulling 4bd1006bf3f4fa2ea8a5d82b08cde2ccc7ce619a on 28_refactoring into 5f319749469b6d03c4924750dc06da392a637fd6 on development.


update dd-strategies notebook

updates the ibmq-dd-strategies notebook to (1) present our newer dd strategies, (2) target ibm_brisbane instead of perth (which has been retired), and (3) use qiskit-ibm-runtime's local service instead of qiskit-ibm-provider (which has been deprecated). This final change means we no longer require an ibm token for our notebook test
also updates qiskit-superstaq's example-requirements to require qiskit-ibm-runtime instead of qiskit-ibm-provider. the latter is still used in the ibmq-dd notebook, however this is currently excluded from the notebook check and also relies on outdated devices and strategies and so needs to be updated anyway

This is mainly a style preferential comment so the current default works as well and this can be ignored, but it might make it everso less cramped if we added a cell above that was:

oh that's nice, done :)

@bharat-thotakura thanks for the review! i ended up changing the notebook a little further - it occurred to me that there was no reason to include qiskit's transpilation at all, when the purpose of the notebook is just to compare superstaq's different strategies (the other dd notebook is supposed to be the one comparing to qiskit proper)


not streaming video file from mega?

@kaczmarkiewiczp
I have installed last version. I streamed in the past videos from mega, I believe with this version.
Was not using it for a time. Tried several days lately and it gets stuck in wainting but no streaming starts.
Any hint?
Changes in mega?
Thanks
CT

Do you still experience this problem? I could not reproduce, it works as intended (on 2019-07-16).

Yes, I still experience this problem. Should you wish me to do any test... I am ready.
CT

Just for clarification: Are you opening the file by tapping the entry in the list? Or via ⋮ > Open As > Video?
Tapping an entry always downloads it first before trying to open it - which can take a while depending on your internet connection, network congestion and the cloud provider (mega).
I guess rcloneExplorer could try to be smarter by implementing a file size and/or extension mapping mechanism for (large) video files.
Can you try to play it via  ⋮ > Open As > Video?

@x0b
ahhhh
I have been using it with open as etc. that works nicely. I believed that that was not streaming....
I was expecting it to stream directly tapping on the entry...
Perhaps a note somewhere explaining the situation would help others... or a swith in the behaviours... could you not programm tapping making as current open as? it would be more intuitive... And then, ithe other options could be "download and open as"....
Probably the change does not merit the effort ... if not within an update for another reason
So, streaming works nicely, but I was misunderstanding it.
Big thanks!

No problem.
However, your response prompted me to look a bit closer. It turns out, that .mkv files on mega remotes are returned as application/octet-stream (possibly as a result of rclone failing to correctly guess the file type).
When everything works as it should, rclone already recognizes both audio and video files and streams them directly. However, this did not work automatically on mega remotes with some file types. Unrecognized mimeTypes will now also be queried against the Android Database.
This change should land in the next version. Until then, Open As > Video should work just as well.

Thanks again!


Support 128 cores

thank you for this cool utility @fasterthanlime ! I use it locally to monitor SSH coding on a super fast box w/256GB Ram / 64 Cores.
Here is what I changed:

[ ] color from green -> red  clear -> solid to indicate core usage
[ ] sort core layout based on usage
[ ] squares

Todo

[ ] make squares scale in regards to core count

This is a cool change! I recommend maintaining your own fork with any changes though - this repository has to stay the way it was left at the end of the video, so it can serve as a reference.
I'm happy to link to your fork in the README - you can submit a PR for that. I'm going to close this PR and will approve one that edits the README to link to your fork!


Add a CLI tool for code generation

Hi folks. One of the @mravinale's ideas is to have a tiny CLI tool bundled in the seed project.
In this PR you will see the first draft of that CLI. Based on Yeoman, I added the necessary scaffolding stuff to start working out in new generators. I've included one in order to play a little bit and I also believe is useful.
Installation and usage is also documented (please read in the diff).
For demoing purposes here is a video: https://www.screencast.com/t/JGNiwoueQ5
Please feel free to comment about anything. Even about the component template. Shoot!
@mravinale @juampick

Please take another look @juampick. Specially this last commit https://github.com/MakingSense/mern-seed/pull/10/commits/f897e58f787f1d470ea9fd8e4e4d5d114b332393 where I implemented what we talked about.
Side though: optional parameters as the name represents, are optional. With my changes if anyone uses --stateless --container it will only take into account one of them. Is like not optional. I have different ways to solve it but I wanted to use the simplicity of using flags, because are nice shortcuts. If you think I should use a user dialog in order to pick a type let me know and I can do the change but it will be an extra step the dev will need to fill.

I understand @matiasbeckerle your concern but I think it's nice for now.. as a 1st approach! congratz


Manuscript Edit Suggestions

line 19, 20: We here describe a procedure -> Here, we
line 35: , all of science -> , to all of science
line 30: firs -> first
line 43, 44:  for dependence-testing motivating -> for dependence-testing, motivating
line 125, 126: and therefore faces > and therefore it faces
line 160: only close in x, not y -> only close in x, and not in y
line 179, 180: n=100, but dimensionality -> n=100, but with dimensionality
line 336: for each brain region g, we -> for each brain region, g, we
line 357: map encoding which -> map encoding, which
line 359: succeeded -> succeed (match the tense with the rest of sentence)

@cshen6 can you correct these?
@zmousavi thank you!

ok, will correct.
Once done I will push change and close this one


Bump carbon.multitenancy.version to 4.10.2

$Subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2522756452

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2522756452
Status: success


Optionally encrypt tokens and secrets at rest using pgcrypto

If pgcrypto is installed on the Postgres database we should allow to use it to encrypt all tokens and secrets. That way if a data breach occurs we won't need to refresh all the tokens and secrets unless the encryption key itself has leaked.

I'm not familiar with pgcrypto but it doesn't seem to provide anything we can't do already within Go. Is there advantage to using a database side implementation?

Sometimes, yes. There are security advantages for offloading the encryption to the database server. See http://stackoverflow.com/questions/9326264/is-there-some-security-advantage-to-using-pgcrypto-instead-of-partition-level-en
Also there are practical use cases for pgcrypto which may or may never apply here.
If you need the unencrypted value in a stored procedure it's easier to just pass the encryption key as a parameter to the stored procedure instead of SELECTing the value, decrypting it and then passing it over the wire to the stored procedure.
pgcrypto can also help increasing resource utilization of the database server and offload encryption and decryption from the busy OAuth server. That means better that dex will scale better as long as your database is up for the task.
If we implement this feature, we probably want to have the database compare the token/secret to the value in the database so we'll need stored procedures. In that case see point number 1.
There are disadvantages though. Lookups on secrets cannot be indexed or constrained.
You can workaround this issue by storing the hash of the secret as well. See http://stackoverflow.com/questions/27997514/postgresql-primary-key-constraint-on-encrypted-data-using-pgcrypto-extension
Preferably using bcrypt which is supported by pgcrypto.
Since we're sending the encryption key to the database, TLS connections are a must which will slow down request throughput. However, since we're dealing with sensitive data here I argue that this must be required by dex anyway in order to avoid leakage of secrets over the wire in case someone is listening (To the NSA agent who is probably reading this: Yo! What's up man?). So in this very specific case, it's a no brainer.
If you don't seperate you're authorization tables from the rest if your data you may not want to use database-side encryption since it will reduce the database throughput. This is why pgcrypto is optional.
We should create a new issue about optional client side encryption for cases like this.
I recommend seperating the databases anyway for security reasons. In case of the aforementioned data breach, you'll only get a list of usernames and that's it.
We should probably edit the documentation to provide the recommendations above.
So, what say you?

dex already encrypt keys using AES-GCM and passwords using bcrypt before sending them to the backend storet. The Go code already does what you're describing, so it seems odd to move this logic to the database since that's what you're worried about being breached.

Are there any specific architectural arguments you are concerned about?
I specified the advantages and disadvantages and it's up for the user to decide if he requires the functionality or not.

Hmm now that I read http://dba.stackexchange.com/questions/24370/how-to-use-aes-encryption-in-postgresql#answer-24379 I'm not so sure anymore.

Are there any specific architectural arguments you are concerned about?

Yes. Again, we already implement the encryption features you're asking for (we just do it in the Go code), and database side crypto doesn't seem like a good mechanism for securing against a database breach.

Well, I think I'll close this issue unitl I find a better argument for using pgcrypto.


[ImgsedBridge] Switch to imginn.com and fix stories

Imgsed is now Imginn, so witched to the new URL
Stories API has changed, so we need to use the uid instead of the username

My test environment is blocked by Cloudflare : can anyone test if the change make the bridge work again ?


Automated releases

Set up automated releases and snapshots, possibly with Travis CI and Bintray, or whatever seems practical.

Hi, is there any progress on this issue? I am gonna need it soon released with "recent" changes including Scala 2.12 support. Is there anything I can do to make it resolved and released soon? If so, please give me as many details as possible, I'd look at it.
I am interested in:

available latest snapshot in maven repo
released stable 2.1.0 with Scala 2.12

Thanks

Sorry I kind of missed this. The current progress is that I registered an account on Sonatype ;)
To get current versions Jitpack seems to work.
If you'd still like to work on setting this up, I can give you the necessary privileges.

Thanks for the update, however, I'm sorry, I have already workaround it.

Releasing is described in section Releasing.
It is almost fully automated, there is one more step needed to automatically push artifacts from bintray to maven central. Solution is to execute API call at the end of travis build to perform sync.
Work In Progress :)

Releases are automatically pushed to bintray, only sync to maven central must be performed manually but is well described in Releasing and is almost instant.
On the other hand automating it is very complicated and releases are not performed frequently.
In my opinion it is not worth automating it for now.
Closing and in case of returning need for it please open a new issue.


[usm] fix revive issues for HTTP

What does this PR do?
Fixes revive linter warning for the package pkg/network/protocols/http2

Motivation
Pass the revive lint issues for the HTTP protocol package.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge

/merge -c


Replace sephereon/PEX presentation definitions with web5 js VCs implementation

This PR addresses #25

explicitly types our offering's get requiredClaims

I believe the issue is because PresentationDefinitionV2 is a type alias in web5-js; see here.
So I'm guessing the TypeScript compiler is replacing the type reference w/ @sphereon/pex-models, but that's not what is defined as the OfferingData.requiredClaims type from here
So yeah... it's an odd ball out, in that it's the only get() method with an explicit return type, but I guess that's okay.
The other option is, we could change web5-js's presentation-exchange.ts to not do a type alias, and just directly export the sphereon type, so change this (how it currently is)...
import type { PresentationDefinitionV2 as PexPresDefV2 } from '@sphereon/pex-models';

//...

export type PresentationDefinitionV2 = PexPresDefV2

to this...
import type { PresentationDefinitionV2 } from '@sphereon/pex-models';
export type { PresentationDefinitionV2 } from '@sphereon/pex-models';

If we keep it as-is, then I would classify this as technical debt, albeit it's an extremely small amount of debt. The other option is, I think we should include a comment above the get requiredClaims() accessor explaining what's going on here (maybe with a link to this comment).

This is merged in now  - https://github.com/TBD54566975/web5-js/pull/336

Would it make sense to only verify those claims that satisfy the PD?

Yeah, I think so! @jiyoontbd can you think of an instance where we need to verify claims which are not defined in the Offering? That is, the Offering has N-number of claim requirements, and the RFQ has (N+M)-number of requirements, and we need to verify all N+M of them?


added dockerfile path and build context

DOCKERFILE_PATH was added to Makefile.common in #5635
This PR changes that to be passed to the -f flag and adds a new variable DOCKERBUILD_CONTEXT which specifies the build context for the docker build.
more info:
https://docs.docker.com/engine/reference/commandline/build/#build-with-path
cc  @simonpasquier  @SuperQ
Signed-off-by: Hrishikesh Barman<EMAIL_ADDRESS>

ping @SuperQ


ERROR

PocketMine-MP Crash Dump Mon Feb 17 16:35:36 UTC 2020
Error: Call to a member function getSafeSpawn() on null
File: plugins/OneInTheQuiver-master/src/oitq/OITQTask
Line: 68
Type: Error
THIS CRASH WAS CAUSED BY A PLUGIN
BAD PLUGIN: OneInTheQuiver v2.0.1
Code:
[59] 		if(count($this->plugin->gameData) < 2){
[60] 			$this->countdown = 31;
[61] 			$this->plugin->gameStatus = self::WAITING;
[62] 		}
[63]
[64] 		/** @var Player $p */
[65] 		foreach($this->plugin->gameData as $gameData){
[66] 			$gameData["player"]->sendPopup("Starting in " . $this->countdown);
[67] 			if($this->countdown === 0){
[68] 				$gameData["player"]->teleport($this->plugin->map->getSafeSpawn());
[69] 				$this->plugin->sendKit($gameData["player"]);
[70] 				$this->plugin->gameStatus = self::GAME;
[71] 			}
[72] 		}
[73] 	}
[74]
[75] 	private function handleGame(){
[76] 		$this->game--;
[77] 		if($this->game === 0 || count($this->plugin->gameData) < 1){
[78] 			$this->plugin->getServer()->broadcastMessage("Game ended, no one won!");
Backtrace:
#0 plugins/OneInTheQuiver-master/src/oitq/OITQTask(46): oitq\OITQTask->handleCountdown()
#1 src/pocketmine/scheduler/TaskHandler(159): oitq\OITQTask->onRun(integer 3341)
#2 src/pocketmine/scheduler/TaskScheduler(199): pocketmine\scheduler\TaskHandler->run(integer 3341)
#3 src/pocketmine/plugin/PluginManager(682): pocketmine\scheduler\TaskScheduler->mainThreadHeartbeat(integer 3341)
#4 src/pocketmine/Server(2570): pocketmine\plugin\PluginManager->tickSchedulers(integer 3341)
#5 src/pocketmine/Server(2346): pocketmine\Server->tick()
#6 src/pocketmine/Server(2203): pocketmine\Server->tickProcessor()
#7 src/pocketmine/Server(1785): pocketmine\Server->start()
#8 src/pocketmine/PocketMine(272): pocketmine\Server->__construct(object BaseClassLoader, object pocketmine\utils\MainLogger, string[26] /home/unwichtig/Thebridge/, string[34] /home/unwichtig/Thebridge/plugins/)
#9 src/pocketmine/PocketMine(295): pocketmine\server()
#10 (1): require(string[81] phar:///home/unwichtig/Thebridge/PocketMine-MP.phar/src/pocketmine/PocketMine.ph)

The level that is in the config is not loaded.

how do you set the spawns?

Presently, there's no way to do that, it just randomly selects, I'll probably change that in the future.

Okay


highlighting in slides defaults to dracula and ignores global settings

Code highlighting in slides defaults to dracula and ignores the global settings in highlight_style:
Changing this line works, but I do not know how to make it use highlight_style:
https://github.com/gcushen/hugo-academic/blob/35563bb498869908e7e2d3202df2106b9378f982/layouts/slides/baseof.html#L24

The slides feature uses the Reveal theming system rather than the Academic theming system. The default Reveal theme is dark whereas the Academic one is light. As such, the user may not wish to apply the same Highlight theme to both their website and slides.
Open to feedback on this...

Or it could simply be on a slide-basis, as one can already choose the reveal theme locally:
+++
title = ""

[slides]
theme = "white"
highlight_style = "github"
+++
``

Thanks for the feedback. I agree, since we allow the theme to be changed on a per-slide basis, let's also allow the code highlighting style to be changed on a per-slide basis so that a light themed slide can have a complementary light themed code highlighting.


collectionview is stuttering

The collectionview i'm using is almost op copy off the code as presented on the website.
Now i've come to test the APK generated on my tablet which is quite powerfull. The images are admittedly high-res yet black and white, still when sliding the slide seems to stutter. As the image is not or repeatedly redrawn, or at least it appears so. Given the images are not displayed full size i assumed the image would not consume as much resources as when displaying higher resolution.
What is the way to go for testing here ? Is the stuttering a known issue ?

We are using picasso for image loading. If you load very large images these images could get evicted from the cash when a new smaller version is requested.

@oxitech239 Regarding testing, you can use Android SDK platform-tools to measure UI performance:
https://developer.android.com/training/testing/performance.html

Superb, thanks, i'll see what i can make from this. I planned on including multiple image resolutions anyway.
What is picasso ?

The image size is about 2400x1500 pixels

Picasso is a library for image loading: http://square.github.io/picasso/

Note also that on Android the CollectionView is implemented as a RecyclerView which means the cells are getting reused and the content is recreated as the data comes in to view.

Thanks, i assume this may explain the 'stutter' or recreate/redraw of the images

Closing as "resolved".


04: OK vs NOT OK distinction is confusing

This distinction could be confusing to new users. Since they probably don't know what OK is supposed to look like, it's asking them to make a choice which they don't have the information to make. It should instead be clear about the output that they should use to determine whether it's ok or not ok.

:+1:

+1 on this being confusing - going through these exercises at Node School SF, where thankfully there are awesome mentors.


Docker compose quay is not working with docker-compose version 1.25

[ ] Verify that it is working for Docker Compose version v2.14.1
[ ] Add a check in the Makefile

@seepgoel any progress on this one?


Added code for longest common substring and updated the readme file

Issue #425
Added code for longest common substring using DP and updated the readme file.

@raksha009 @rudrakshi99 @tarun26091999 @plazzy99
I request the mentors to please review my pull request.

Resolve conflict

@plazzy99 @tarun26091999
I have resolved the merge conflicts, please do check.


K8s ingress with istio without sidecar

Is it possible to use k8s ingress with ingress gateway for an application without injecting sidecar into the applicationor the namespace where the ingress is created? I mean is it possible to just use istio ingress gateway just like any other ingress controller like nginx ingress controller?
I have gateway svc as loadbalancer and has a domain name and static ip attached to it from the metallb load balancer
Environment:
k8s version: 1.15.5
istio version : 1.4.0
on prem

In order to save resources, we are using istio ingressgateway without sidecar in out development cluster for a while, it works well.
without sidecar, istio just act as a ingress gateway, no service mesh here.
we only enable istio-injection in our production environment.

Yes, this is supported. See https://istio.io/latest/docs/tasks/traffic-management/ingress/kubernetes-ingress/ for more info. Sidecar is only needed for service to service features, mtls, server side telemetry, auth, etc. But you can do basic Ingress without it

@howardjohn I went ahead and try your suggestion to test out the use of istio with k8s ingress, for basic ingress it works fine, but if my service only accept a HTTPS connection, it seems that I have no way to configure the ingress this way. I have tried using the tls option of ingress, but the tls only terminated at the ingress, so the connection to the service is still HTTP. Would you have any idea how I might configure this just using istio and k8s ingress? Or i need to setup nginx and use nginx ingress controller afterall...
Any help is much appreciated. Thanks in advanced.

Connection to the upstream service is NOT part of the Ingress spec. You can use destination rule to configure this.

My reason of wanting to use istio without the sidecar is the same as @ryan4yin, to save resource for some of my services. If I opt to use destination rule, then i would have to inject the sidecar back in, right? @howardjohn If I just want to connect to the backend service via k8s ingress via https with istio, can I set up as https://istio.io/latest/docs/tasks/traffic-management/ingress/kubernetes-ingress/ suggest, and let istio do the tls termination, and then deploy nginx ingress controller for the https connection from ingress to backend service? Do you think this would be an overkill?

No. You do not need a sidecar for Ingress, even with destinationrule. Also, if your only goal is to not use sidecars, you can still use Gateway/VirtualService, you don't need Ingress

Do you think this would be an overkill?

Yes

@howardjohn Thanks for the tip, just to clarify when you say Ingress, you mean the k8s Ingress (https://kubernetes.io/docs/concepts/services-networking/ingress/) right?
So now my current setup is basically like this:
public network --> gateway (with tls SIMPLE for a wildcard domain) --> virtual service (for reverse proxy to specific backend service) + destinationRule (for make sure it connect to backend service via 443 with tls)
For the above setup, do i not need a sidecar?
I tried removing the sidecar injection before, but i faces some occasional upstream connect error or disconnect/reset before headers. error, that is why I thought the sidecar is a must.

Yes, no sidecar is required for that.
On Mon, Aug 9, 2021 at 10:41 AM rklhui @.***> wrote:

@howardjohn https://github.com/howardjohn Thanks for the tip, just to
clarify when you say Ingress, you mean the k8s Ingress (
https://kubernetes.io/docs/concepts/services-networking/ingress/) right?
So now my current setup is basically like this:
public network --> gateway (with tls SIMPLE for a wildcard domain) -->
virtual service (for reverse proxy to specific backend service) +
destinationRule (for make sure it connect to backend service via 443 with
tls)
For the above setup, do i not need a sidecar?
I tried removing the sidecar injection before, but i faces some occasional upstream
connect error or disconnect/reset before headers. error, that is why I
thought the sidecar is a must.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/24750#issuecomment-895412724, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIQEKI3EYWXX5OFOITT4AHNRANCNFSM4OA3DDQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@rklhui I'm facing a similar issue with the same architecture setup : Use the Istio Ingress Gateway to route request to pod that listen in https.
@howardjohn Have you some recommendation/requirement about the certificate configuration on the backend ?
Have you solve you problem ? Could you show me the DestinationRule ?

In order to save resources, we are using istio ingressgateway without sidecar in out development cluster for a while, it works well.
without sidecar, istio just act as an ingress gateway, no service mesh here.
we only enable istio-injection in our production environment.

@ryan4yin What is the thinking behind you enabled sidecar in production instead of going without sidecar, same as in your development cluster?

@manojtr just as I said before:
without sidecar, istio just act as an ingress gateway, no service mesh here.

sidecar is useful while you need service mesh.
for example, if service A need to call Service B:
graph LR
  Client --> LoadBalancer --> igw[Istio Gateway]
  subgraph Kubernetes
    igw --> s_a[Service A] --> s_b[Service B]
  end

with Service A's Sidecar, you can do a lot of L7 operations  on the traffic from A to B, such as traffic split:
graph LR
  Client --> LoadBalancer --> igw[Istio Gateway]
  subgraph Kubernetes
    igw --> s_a[Service A] -- 90%  --> s_b1[Service B v1]
    s_a[Service A]    -- 10% -->  s_b2[Service B v2]
  end

and others like http status_code/latency monitoring, fault injection, etc...

Hi,
If I need to setup DestinationRule to enable least requests load balancing policy for the upstream service, without sidecar running on the pod, how does istio be able to track the number of active requests on each pod?


Use Organization Build Release Github Action

Questions
Answers

Description?
Use Organization Build Release Github Action

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?

How to test?
CI should be green

Thank you @atomiix


Missing LICENSE file

While you've stated that the project is licensed under MIT in the Cargo.toml,
adding a discrete LICENSE file would be worth it too.

License file has been added :)


upgrading react components for use with v15 or v0.14

Allows usage of yako addon components for usage with modern versions of React

Coverage remained the same at 87.209% when pulling 57e3571804f5a05cf9a3b7a3a09a3c43d95bcde3 on hasPatrickC:react-upgrade into 3ad2594e3c2eb8e8043b89be257af2f5a773b88d on alfredkam:master.


Internal deployment process needs clear documentation

Team members should have a central (notion) source of proper deployment and integration.

@jessopb like this one? https://www.notion.so/lbry/How-To-Release-cfb38925465148e583ee8d2c35f8c44a
or if not this? what are you thinking? Notice the spee.ch section is empty (we need to up date it)

closing for #811


POL-449: Convert resource type to lowercase for comparisons

Description
Microsoft is not consistent with the case of its resource types; work around this by converting to lower case when|
comparing types from various sources across Microsoft.
Issues Resolved
https://jira.flexera.com/browse/POL-449
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

          1 Error

:no_entry_sign:
Please add a 'default_frequency' property field and value. compliance/azure/azure_untagged_resources/untagged_resources.pt

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger


Add Asite (US Gov.) connector

When submitting a connector, please check the following conditions for your PR to ensure a smooth certification process.

[ ] I attest that the connector works and I verified by deploying and testing all the operations.
[ ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[ ] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[ ] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@natalie-pienkowska Can you please approve this PR as it is asking for 2 approving reviews.

@sriyen-msft Could you give tell me when Our connector will merge in master branch?


Create a standard tus client model

Create a state machine model for tus uploads
Use https://github.com/pfusik/cito to build core logic for tus client
Add JS implementations around core logic to complete tus client

First attempt at a state transition chart:

Rounded boxes are states
Circles show the invocation of public methods (from library user) or private methods (from client itself)

Public interface for controlling uploads:

createUpload
resumeUpload
createOrResumeUpload
pauseUpload

Maybe, XState helps here? Checking their tutorial and that they can invoke services, I thought, it could be a good thing to use?

XState is a promising library for JavaScript, thanks for sharing! This issue is also intended to look into ways how we can build state machines that are shared across different programming languages. That could allow reusing the state machines in our JavaScript, Python, Swift and Java clients without the need of re-implementing the same logic everywhere. However, I am not sure if such a tooling exists yet.


feat(release): use github releases instead of CHANGELOG

You need to set environment variable GITHUB_AUTHTOKEN as your github token.
Closes #2124

ping @eddiemonge


Blog Post for KIC 2.2

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Issue to track the creation of the Gateway API Milestone 1 blog post
Proposed Solution
No response
Additional information
No response
Acceptance Criteria

[x] Blog post written and edited
[x] Blog is staged on https://konghq.com/blog/
[x] Reviewed by docs/writing/pmm team

blog post now complete https://konghq.com/blog/kong-ingress-controller-2-2/


Notes for 2021-01-14

Thanks for considering @terrajobst!

Thanks for considering @terrajobst!

One more question though, I see it's aiming at .NET libraries - How about products built with .NET that are OSS? What if they are related to Azure? Might be out-of-scope but has same issues.

One more question though, I see it's aiming at .NET libraries - How about products built with .NET that are OSS? What if they are related to Azure? Might be out-of-scope but has same issues.

How about products built with .NET that are OSS?

That's fair, I believe we certainly have a bias towards libraries in this working group, largely because libraries are bit harder because they become part of somebody else's app. Products or service offerings are a bit easier to control but I believe it's also likely that they have other issues. Maybe it's just me, but I tend to think of "ecosystem" more as "sets of libraries you can use to build apps" rather than "a bunch of offerings you can use" because the latter makes it no longer developer technology specific (i.e. the Node ecosystem vs. the .NET ecosystem) but platform specific (i.e. the Windows ecosystem vs. the macOS ecosystem).

How about products built with .NET that are OSS?

That's fair, I believe we certainly have a bias towards libraries in this working group, largely because libraries are bit harder because they become part of somebody else's app. Products or service offerings are a bit easier to control but I believe it's also likely that they have other issues. Maybe it's just me, but I tend to think of "ecosystem" more as "sets of libraries you can use to build apps" rather than "a bunch of offerings you can use" because the latter makes it no longer developer technology specific (i.e. the Node ecosystem vs. the .NET ecosystem) but platform specific (i.e. the Windows ecosystem vs. the macOS ecosystem).

In my case it is always about Docker images that people can use in their platforms but never a "product product" but I see what you mean and it's fine.
Thanks for sharing!

In my case it is always about Docker images that people can use in their platforms but never a "product product" but I see what you mean and it's fine.
Thanks for sharing!

Curious what others think here @clairernovotny @sbwalker

Curious what others think here @clairernovotny @sbwalker

Just to give context - I maintain https://promitor.io/ & https://k8s-event-grid-bridge.tomkerkhove.be/ which both extend Azure With .NET.

Just to give context - I maintain https://promitor.io/ & https://k8s-event-grid-bridge.tomkerkhove.be/ which both extend Azure With .NET.

@terrajobst I agree with @tomkerkhove that the survey should not focus solely on "libraries". I personally have never created an open source "library"... projects such as DotNetNuke and Oqtane are comprehensive frameworks that are much broader in scope than libraries. However they still suffer from the same .NET open source challenges.

@terrajobst I agree with @tomkerkhove that the survey should not focus solely on "libraries". I personally have never created an open source "library"... projects such as DotNetNuke and Oqtane are comprehensive frameworks that are much broader in scope than libraries. However they still suffer from the same .NET open source challenges.


Update branding to 5.0.0-alpha1

This is blocked until we branch for preview8

Entity Framework 5 ??

@ErikEJ Don't read anything into this. It doesn't mean the next release will be 5.


No code yet sent/published by the herta bot

There's a new code by the way on the livestream today 2.1, it did not send yet nor the previous one (the recent)
(recent previous one)
SB87P52BTVQ3
2.1
#1 - 3SRN6L3AADLK
#2 - YTRN743TSUL7
#3 - 2S8N6M3ATV6T

The bot sent the codes into my server so the scraping works just fine. Looking at the logs it seems like it has some issues resolving the guild ids. Can you send me the server id of the server you are in so I can double check it?

The bot sent the codes into my server so the scraping works just fine. Looking at the logs it seems like it has some issues resolving the guild ids. Can you send me the server id of the server you are in so I can double check it?

Sorry for the late response, I see, no worries
Here is the channel ID for the bot assigned to send the message:<PHONE_NUMBER>797142578
Server ID:<PHONE_NUMBER>77953300

Looks like something is really off. It looks like the codes were sent and after there is an error regarding no alert channel being set. Sadly I cannot inspect the config file holding the Information because of the deployment environment. I'll try to attach the bot to a DB instance instead of using a file. It should be also more scalable in the future.

I see it was sent, but there is an error despite the fact that the channel and alert are set, and I have already activated permissions for almost all possible permissions. Let me know or update me if it's fixed no rush and if there's anything I need to do, such as reactivating the slash commands to set it up again

I changed the code to use a Db and did some improvements in general. Let me know if the bot now works for you as expected.

I changed the code to use a Db and did some improvements in general. Let me know if the bot now works for you as expected.

Alright, should I do the / slash commands again or no need? And since there are no new codes yet, but there might be later due to the new update, we'll see

Try the slash commands again. You should actually get a bunch of new codes because the bot "forgot" which were already sent.

Try the slash commands again. You should actually get a bunch of new codes because the bot "forgot" which were already sent.

I see and yup also thanks, did few hours/mins ago and it finally shows up now, It's fully working


Multiline doc comments in enums are copied to following variants

Input C/C++ Header
enum Test {
  /**
   * hello world
   */
  A,
  B,

  C,
}

Bindgen Invocation
$ bindgen input.h

Actual Results
/* automatically generated by rust-bindgen */

/// hello world
pub const Test_A: Test = 0;
/// hello world
pub const Test_B: Test = 1;
/// hello world
pub const Test_C: Test = 2;
pub type Test = u32;

Expected Results
The doc comment should not be duplicated (carried forward), like so:
/// hello world
pub const Test_A: Test = 0;
pub const Test_B: Test = 1;
pub const Test_C: Test = 2;
pub type Test = u32;

Hmm. Is this a clang bug?

Might be.

Poking around with the clang.cindex Python bindings, it does look like this is a libclang bug.
from clang.cindex import *
h = TranslationUnit.from_source('input.h')
for x in h.cursor.walk_preorder():
    print(x.type, x.displayname, x.brief_comment)

CursorKind.TRANSLATION_UNIT input.h None
CursorKind.ENUM_DECL Test None
CursorKind.ENUM_CONSTANT_DECL A hello world
CursorKind.ENUM_CONSTANT_DECL B hello world
CursorKind.ENUM_CONSTANT_DECL C hello world

Time to file a bug in LLVM's bug tracker, I guess.

Thanks a lot for investigating and looking into it! Sorry I didn't find time to do it myself.

https://bugs.llvm.org/show_bug.cgi?id=39705


Plugin does not format "merge into" correctly for Hive SQL

it does not correctly format below.
merge into table USING (
SELECT  *
FROM table 2)
Thanks

Thanks for your feedback. I will try to fix it in the next version.


Releases?

Hey are you guys still keeping up with releases?  I'm wanting to make a consistently updated Dockerfile (and helm chart) repository for oauth2_proxy, but I'm realizing that all of the other ones appear to be old because the last release was almost a year ago.
Are the maintainers planning on tagging any releases after 2.1?
Thanks!

+1 for this... would really like to see some more frequent releases. There's also a lot of PR's open that need looking at.

Thanks @jehiah 👍

@tanuck no problem; it's been a long time coming =)


Tt ma ticket 15 no birth cert

Users no longer need to provide a full birth certificate or naturalisation
certificate as supporting documents in the following CNI countries
(NOTE: this is not all CNI countries):

Albania, Algeria, Angola, Armenia, Austria, Azerbaijan, Bahrain, Belarus,
Bolivia, Bosnia & Herzegovina, Bulgaria, Chile, Croatia, Cuba, Denmark,
Dominican Republic, El Salvador, Estonia, Ethiopia, Georgia, Greece, Guatemala,
Honduras, Hungary, Iceland, Kazakhstan, Kosovo, Kuwait, Kyrgyzstan, Latvia,
Lithuania, Luxembourg, Macedonia, Mexico, Moldova, Montenegro, Nepal, Norway,
Panama, Poland, Romania, Russia, Serbia, Slovenia, Spain, Sudan, Sweden, Tajikistan,
Tunisia, Turkmenistan, Ukraine, Uzbekistan, Venezuela, Democratic Republic of Congo

Note to the reviewer: this leaves us with 4 "standard" phrases:

List without birth cert
List without birth cert in a country with notary public
List with birth cert
List with birth cert in a country with notary public

I have considered interpolating the two variables above, but the whole outcome is within a precalculate block already, which is miles long, so adding another two blocks above the current one would seem out of context.
I have also considered having a list that requires birth certificate (CNI countries - countries that don't need birth cert), but I decided to leave it as it is in this PR as this is what FCO gave us, so most likely they will send updates in the same form in future.
Any suggestions how to improve this PR are very welcome

When you mention interpolation, do you mean something like:
# In marriage-abroad.rb
precalculate :birth_certificate_requirement do
  if resident_of == 'ceremony_country' && %w(germany italy japan spain).exclude?(ceremony_country)
    if no_birth_cert_requirement.exclude?(ceremony_country)
      Phraselist.new(:birth_certificate_requirement)
    end
  end
end

# In marriage-abroad.yml
birth_certificate_requirement: |
  - your [full birth certificate](/order-copy-birth-death-marriage-certificate/) or [naturalisation certificate](/get-replacement-citizenship-certificate)

required_supporting_documents: |
  You’ll need to provide supporting documents, including:

  - your passport
  %{birth_certificate_requirement}
  - proof of residence, such as a residence certificate - check with the %{embassy_or_consulate_ceremony_country} to find out what you need
  - equivalent documents for your partner

required_supporting_documents_incl_birth_cert_notary_public: |
  You’ll need to provide supporting documents, including:

  - your passport
  %{birth_certificate_requirement}
  - proof of residence, such as a residence certificate - check with the %{embassy_or_consulate_ceremony_country} or notary public to find out what you need
  - equivalent documents for your partner

If so, I agree that I'm not sure it's worth doing. While it removes some duplication from the phrase lists, it adds some duplication to the Smart Answer.
I can't really think of any other ways to improve what you've got so this all looks good to me.

The latest commit looks good to me, @tadas, although I'd prefer the update of marriage-abroad-files.yml to be separate, i.e. move the "Update checksums for regression tests" commit after "Unify countries that require 3 day residency and don't need birth certs".


Implement Orama search (again)

Staging Site
This is a continuation of #104

For some reason hitting enter/return doesn't trigger a navigation. I think this might be a bug with the orama search box
https://github.com/user-attachments/assets/8d900c89-5659-49bd-8b0e-653434521989

on it!

I looked into the keyboard issue further, and it's only when using tabs that hitting "enter" doesn't trigger a navigation. If I use arrow keys it works fine
https://github.com/user-attachments/assets/80e7615a-214e-441b-9a3b-f3bb440435d3

Hey @brookslybrand, how're doing? I'm Rodrigo from Orama.
We have upgraded our Searchbox version with a HOTFIX. Would you mind to apply this diff to your branch?
Thanks!
diff --git a/package.json b/package.json
index c6de7c0..dfc4b7d 100644
--- a/package.json
+++ b/package.json
@@ -22,7 +22,7 @@
   "dependencies": {
     "@docsearch/css": "^3.6.0",
     "@docsearch/react": "^3.6.0",
-    "@orama/searchbox": "^1.0.0-rc50",
+    "@orama/searchbox": "^1.0.0-rc52",
     "@oramacloud/client": "^1.3.6",
     "@remix-run/node": "2.8.1",
     "@remix-run/react": "2.8.1",

Thanks @rjborba! I never saw your message, but wanted to let you know I did upgrade and that version is working. Thanks!

It seems like the focus trap for the modal is not working in Safari for some reason. I can't recreate this issue on Chrome
https://github.com/user-attachments/assets/ac05973e-301a-4f17-a5e2-f570cd076219

Thanks for sharing @brookslybrand! We're going to take a look!

Awesome, thank you @rjborba!
Another little one: when I use the arrow keys, it doesn't automatically scroll when I get past the 3rd item. It'll scroll if I do an up arrow key, but it'd be ideal if it scrolls to whatever I'm focused on so I don't lose my place.
Also, and I'm not sure if this is something I can easily customize, the focus color (at least for light mode) is pretty hard to distinguish. I am slightly color deficient, so it may be more pronounced for me
https://github.com/user-attachments/assets/958b291f-0cd7-45eb-9f51-fc66d97192b4

Awesome, thank you @rjborba!
Another little one: when I use the arrow keys, it doesn't automatically scroll when I get past the 3rd item. It'll scroll if I do an up arrow key, but it'd be ideal if it scrolls to whatever I'm focused on so I don't lose my place.
Also, and I'm not sure if this is something I can easily customize, the focus color (at least for light mode) is pretty hard to distinguish. I am slightly color deficient, so it may be more pronounced for me
no-scroll.mov

@brookslybrand all very relevant observations. We will be releasing a version addressing all these bullets as well.
I will drop a message as soon as we have it. Thanks! :)

@brookslybrand Hi! Quick update so you guys can be up and running

Another little one: when I use the arrow keys, it doesn't automatically scroll when I get past the 3rd item. It'll scroll if I do
an up arrow key, but it'd be ideal if it scrolls to whatever I'm focused on so I don't lose my place.

The scroll issue is fixed. We're going to publish a new version ASAP. I'll drop a message when we do it.

It seems like the focus trap for the modal is not working in Safari for some reason. I can't recreate this issue on Chrome

This one is actually a limitation with Safari:
"By default tab-access is disabled in safari. To enable it, check "Preferences > Advanced > Press tab to highlight each item on a page"

It looks like there ins't much we can do about it. I'll look into it a bit further to be sure.

Also, and I'm not sure if this is something I can easily customize, the focus color (at least for light mode) is pretty hard to distinguish. I am slightly color deficient, so it may be more pronounced for me

About this stying-related question, we work with css vars which you can override with whatever you need.
In this case, the token --background-color-fourth is used on the background of selected item. You can replace it with whatever you think is suitable!
diff --git a/app/modules/orama-search.tsx b/app/modules/orama-search.tsx
index ba5b4d4..69d61c5 100644
--- a/app/modules/orama-search.tsx
+++ b/app/modules/orama-search.tsx
@@ -40,6 +40,14 @@ export function SearchModalProvider({
             onClose={() => setShowSearchModal(false)}
             colorScheme={colorScheme}
             theme="secondary"
+            themeConfig={{
+              light: {
+                "--background-color-fourth": "red"
+              },
+              dark: {
+                "--background-color-fourth": "green"
+              }
+            }}
             resultsMap={{
               description: "content",
             }}

As I said before, we're going to publish a new version fixing the scroll. Meanwhile please feel free to raise any question/bug. Thanks!

Hey @brookslybrand!
We just published a new version of our SearchBox.
Please upgrade yours to 1.0.0-rc53
diff --git a/package.json b/package.json
index f6f9a1d..da94486 100644
--- a/package.json
+++ b/package.json
@@ -22,7 +22,7 @@
   "dependencies": {
     "@docsearch/css": "^3.6.0",
     "@docsearch/react": "^3.6.1",
-    "@orama/searchbox": "^1.0.0-rc52",
+    "@orama/searchbox": "^1.0.0-rc53",
     "@oramacloud/client": "^1.3.6",
     "@remix-run/node": "2.8.1",
     "@remix-run/react": "2.8.1",

Is has a fix related to scroll to view for result elements.

Awesome, thank you @rjborba for the fix, instructions, and explanation!
I've pushed the latest. Going to work on an A/B testing strategy next


RFC6331: Moving DIGEST-MD5 to Historic

Dear @msimerson,
In first, I wish you a Happy New Year!
20 November 2008: CRAM-MD5 to Historic:

https://tools.ietf.org/html/draft-ietf-sasl-crammd5-to-historic-00

29 June 2017: CRAM-MD5 to Historic:

https://tools.ietf.org/html/draft-zeilenga-luis140219-crammd5-to-historic-00

July 2011: RFC6331: Moving DIGEST-MD5 to Historic:

https://tools.ietf.org/html/rfc6331

I add same about SCRAM-MD5.
There are now:

July 2010: RFC5802: Salted Challenge Response Authentication Mechanism (SCRAM): SASL and GSS-API Mechanisms: https://tools.ietf.org/html/rfc5802 (SCRAM-SHA-1 and SCRAM-SHA-1-PLUS)
July 2010: RFC5803: Lightweight Directory Access Protocol (LDAP) Schema for Storing Salted: Challenge Response Authentication Mechanism (SCRAM) Secrets: https://tools.ietf.org/html/rfc5803
November 2015: RFC7677: SCRAM-SHA-256 and SCRAM-SHA-256-PLUS: Simple Authentication and Security Layer (SASL) Mechanisms: https://tools.ietf.org/html/rfc7677

Soon:

SCRAM-SHA-512(-PLUS): https://tools.ietf.org/html/draft-melnikov-scram-sha-512
SCRAM-SHA3-512(-PLUS): https://tools.ietf.org/html/draft-melnikov-scram-sha3-512

@msimerson: Already solved?

https://github.com/msimerson/Mail-Toaster/search?q=md5
https://github.com/msimerson/Mail-Toaster/search?q=scram


Manifest merger failed : Attribute application@supportsRtl

Maybe it's possible for the library to omit supportsRtl ?
Error:Execution failed for task ':app:processDebugManifest'.
> Manifest merger failed : Attribute application@supportsRtl value=(false) from AndroidManifest.xml:13:9-36
	is also present at [io.supercharge:shimmerlayout:0.5.0] AndroidManifest.xml:11:18-44 value=(true).
	Suggestion: add 'tools:replace="android:supportsRtl"' to <application> element at AndroidManifest.xml:7:5-33:19 to override.

It will be fixed in the next release which I am about to release in the weekend.

@abiemann the supportsRtl was removed from the manifest.


[chore] Fixed a dead link for machine id man page

Fixes #
Changes
This is fixing a CI error here https://github.com/open-telemetry/semantic-conventions/actions/runs/11861560247/job/33059139725?pr=1574
@lmolkova ^^
Please provide a brief description of the changes here.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist

[ ] CONTRIBUTING.md guidelines followed.
[ ] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[ ] schema-next.yaml updated with changes to existing conventions.

hi @gyliu513! it looks like you need to also update it in the yaml file

@trask which yaml file you are mentioning, can you point that out? Thanks!

oh, looks like it's in 3 places: https://github.com/search?q=repo%3Aopen-telemetry%2Fsemantic-conventions+freedesktop&type=code

@trask done, thanks!


Dates must not be null

On loading the message activity, I get an error : "Dates must not be null"

@Oirere-Jr You should pass the valid createdAt inside the getCreatedAt() method implementation


Change visibility of UrlMatchesRedirect

Xamarin.Auth Issue
Feature description
Please consider marking UrlMatchesRedirect protected so classes implementing WebRedirectAuthenticator can have custom URL matching e.g in case the query string contains the relevant information

PR has been created and reviewed, just pending merge


SNS: do not duplicate subscriptions

Hi.
This is apparently is a bug. If I try to create 2 subscriptions between a topic and an endpoint, Amazon will create only a single one and on the 2nd call will return the ARN of the 1st one.
Though, I couldn't any description of it in the docs (event stackoverflow didn't help.) But the experiments show that this is the behavior they have.

Thanks for the contribution and welcome to the community!


无法找到模块“html-to-json-parser”的声明文件

import { JSONType } from 'html-to-json-parser'
无法找到模块“html-to-json-parser”的声明文件。“c:/code/demo-vue-quill/node_modules/html-to-json-parser/dist/index.modern.js”隐式拥有 "any" 类型。
There are types at 'c:/code/demo-vue-quill/node_modules/html-to-json-parser/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'html-to-json-parser' library may need to update its package.json or typings.ts(7016)

Hi @MiniJude, Thank you for reaching me out!
I need more clarification on this issue (e.g, environment where you running, type in pkg.json, is it client or server side script, main language of the project)
Thanks
Yousuf Kalim

Hi @MiniJude, Thank you for reaching me out!
I need more clarification on this issue (e.g, environment where you running, type in pkg.json, is it client or server side script, main language of the project)
Thanks Yousuf Kalim

thank you for your reply!
node -v v18.16.0
and this is my package.json file:
// package.json
{
  "name": "vue-quill-demo",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vue-tsc && vite build",
    "preview": "vite preview"
  },
  "dependencies": {
    "@vueup/vue-quill": "^1.1.1",
    "@vueuse/core": "^10.1.2",
    "html-to-json-parser": "^1.1.0",
    "katex": "^0.16.7",
    "less": "^4.1.3",
    "quill-blot-formatter": "^1.0.5",
    "quill-image-uploader": "^1.3.0",
    "vue": "^3.2.47"
  },
  "devDependencies": {
    "@types/katex": "^0.16.0",
    "@vitejs/plugin-vue": "^4.1.0",
    "typescript": "^5.0.2",
    "vite": "^4.3.2",
    "vue-tsc": "^1.4.2"
  }
}

probably related : TypeError: (0 , html_to_json_parser_1.default) is not a function - cannot import HTMLParser

I am closing this issue as I have just updated the library to version 2.0.0, where I fixed the issue by moving the function from default export to normal export.
Please update the library and follow the Readme.md for revised implementation.
Thank You

I am having the same issue on 2.0.1:

Could not find a declaration file for module 'html-to-json-parser'<EMAIL_ADDRESS>implicitly has an 'any' type.
There are types at '/Users/Nienke/Sites/dokugaku/services/work-processor/node_modules/html-to-json-parser/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'html-to-json-parser' library may need to update its package.json or typings.ts(7016)

package.json
"exports": "./index.js",
"type": "module",
"engines": {
  "node": ">=16"
},

tsconfig.json
{
  "extends"<EMAIL_ADDRESS>  "compilerOptions": {
    "lib": ["ES2021"],
    "outDir": "./dist",
    "rootDir": "./src",
    "module": "node16",
    "moduleResolution": "node16"
  },
  "exclude": ["node_modules"],
  "include": ["src"]
}

@repo/typescript-config/base.json
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Default",
  "compilerOptions": {
    "declaration": true,
    "declarationMap": true,
    "esModuleInterop": true,
    "incremental": false,
    "isolatedModules": true,
    "lib": ["es2022", "DOM", "DOM.Iterable"],
    "module": "NodeNext",
    "moduleDetection": "force",
    "moduleResolution": "NodeNext",
    "noUncheckedIndexedAccess": true,
    "resolveJsonModule": true,
    "skipLibCheck": true,
    "strict": true,
    "target": "ES2022"
  }
}


Fix invalid CSS in dfnpanels.css

Add missing unit to border-radius.

Context: I'm seeing spec build failures [0] for [1] (which itself fixes an unrelated spec build failure), and this looked possibly to be the culprit? Not sure since this line is 2 months old though...
[0] https://github.com/WICG/turtledove/actions/runs/7173660187/job/19533486675?pr=949
[1] https://github.com/WICG/turtledove/pull/949

Reported as #2733

It's meant to be px, yeah. I've made the change; I'm just rebasing tests real quick and then I'll cut a new release. Sorry about that.


Update CODEOWNERS for current codebase and teams

Should catch more automated code review requests for relevant teams.

Related (but more ambitious in fixing dual responsibility):

https://github.com/godotengine/godot/pull/89486

Oops, I missed that. Sorry for duplicating the work. I'll review that PR and see how to merge the two.

Superseded by #89486.


Android 14 foreground service type required

Description
Android 14 requires us to set a foreground service type of connectedDevice.
With that, we must have the BLUETOOTH_CONNECT permission or call UsbManager.requestPermission() to allow our services to enter the foreground.

Closed with #1860


Added info / tooltip for add role and import role dialogs in the UI

Description
This PR added info / tooltip for add role and import role dialogs in the UI.

Fixes: #4835

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
Add Role Dialog =>
Before Changes:

After Changes:

Import Role Dialog =>
Before Changes:

After Changes:

How Has This Been Tested?

Manually tested the Add Role and Import Role from UI

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. [S]


When I print a receipt with images I get an error, please help.

When I print a receipt with images I get an error, please help.
Once the receipt is printed normally, as it should, then there is an error
Bug description
The media.width.pixel field of the printer profile is not set. The center flag will have no effect.
Steps to reproduce
from escpos.printer import Network
from PIL import Image
import datetime
class Printer:
def init(self):
try:
self.printer = Network('<IP_ADDRESS>')
except Exception as e:
print(f"Ошибка в функции init : {e}")
def print_receipt_canteen(self, employee_username: str, menu: str) -> None:
    date, time = datetime.datetime.now().strftime("%d.%m.%Y"), datetime.datetime.now().strftime("%H:%M:%S")
    self.printer._raw(b"\x1b\x61\x01")  # Center-align text
    self.printer._raw(b"\x1b\x45\x01")  # Set bold text
    self.printer.image("media/images/logotip.bmp", impl="bitImageRaster")  # Add logo
    text = f'\n\n{" СТОЛОВАЯ ".center(len(" СТОЛОВАЯ ") + 24, "*")}\n' \
           f'\n{"ФИО:".ljust(14)}{employee_username.center(25)}' \
           f'\n{"Дата:".ljust(14)}{date.center(25)}' \
           f'\n{"Время:".ljust(14)}{time.center(25)}\n\n' \
           f'\n{"Меню:".ljust(14)}{menu.center(25)}\n\n' \
           f'{"-" * 40}\n\n'.encode("cp1251")
    self.printer._raw(text)
    image_path = f"media/images/{menu}.png"
    img = Image.open(image_path)
    new_width = 300
    new_height = 300
    img = img.resize((new_width, new_height))
    resized_image_path = f"media/images/resized_{menu}.png"
    img.save(resized_image_path)
    self.printer.image(resized_image_path, impl="bitImageRaster")
    self.printer.cut()

Xprinter: Manufacturer Model XP-A160H
python-escpos version: 3.0a99
python version:** 3.10
operating system: Debian 10

Please verify you python-escpos version. To my knowledge there is no release 1.9

Please verify you python-escpos version. To my knowledge there is no release 1.9

Installed python-escpos==3.0a9 same error

How did you install that version? If it is really a version 1.9, then I guess that you have installed a fork and not this project.

How did you install that version? If it is really a version 1.9, then I guess that you have installed a fork and not this project.

In the requirements.txt file python-escpos==3.0a9

How did you install that version? If it is really a version 1.9, then I guess that you have installed a fork and not this project.

I set the desired width in pixels, the error disappeared, but after printing gunicorn restarts
class Printer:
def init(self):
try:
self.printer = Network('<IP_ADDRESS>')
self.printer.profile.profile_data["media"]["width"]["pixels"] = 576
except Exception as e:
print(f"Ошибка в функции init : {e}")

Could you please give the traceback of the error? (Or did I miss it?)

Could you please give the traceback of the error? (Or did I miss it?)

After setting the width value in pixels, the error disappeared, but the problem with printing images remained the same, printing without images is successful, but I would like to print a receipt with images

I have read your issue again, but unfortunately I do not understand, which issue with printing images remains now?

Thanks for your help, the problem turned out to be not with Python-escpos, I apologize..


Added time dilation caculator

Wow, you're working on a really old version! We've switched to a new system - your code should go into it's own file under the src folder. This just makes everything neater.
Whenever you're ready, you can submit a new pull request.


Prevent ttyd from restarting the program on exit

Hi, I'm using ttyd to launch /bin/bash inside a container. When exiting bash (either by entering exit or C-d), ttyd automatically clears the terminal and relaunch bash.
How can I make it so that bash doesn't restart and the screen output remains untouched?
Here's the command I use:
ttyd -p 8080 bash

More info:
[root@0494e00e4ad4 app]# ttyd --version
ttyd version 1.6.0

Installed form the Fedora32 package:
ttyd.x86_64                        1.6.0-1.fc32                     @updates      ```

I have the same problem/request.

possible, but it's hardcoded:
https://github.com/tsl0922/ttyd/blob/master/html/src/components/terminal/index.tsx#L203

Added a client option (on master) to disable it, usage: ttyd -t disableReconnect=true bash.


Use uniform property to specify tenant-id, client-id, client-secret.

Closing it. Use this issue instead: https://github.com/Azure/azure-sdk-for-java/issues/19696


Upgrade libraries dependabot missed

I'm not sure why, but every so often Dependabot seems to lose track of some libraries (TypeScript seems to be affected relatively often). This bumps the versions of Jest and TypeScript because Dependabot didn't.

Removed TypeScript upgrade because TypeDoc is having issues with the new version for now: https://github.com/TypeStrong/typedoc/issues/1589
Once that gets released I'll create a new PR for that.


bazeldnf: Update to v0.5.9

What this PR does / why we need it:
Update bazeldnf to v0.5.9-rc2.
Needed for s390x support, see https://github.com/kubevirt/kubevirt/pull/10490.
Special notes for your reviewer:
Once it's been verified that the update doesn't break anything, I will make sure that the final v0.5.9 release is tagged and pick it up before removing the draft status from this PR.
Release note:
NONE

/test all

bazeldnf v0.5.9 has been tagged, so this can be considered for merging now.

@xpivarc it looks like all the checks passed, what is still missing to get this merged? Thanks!

@xpivarc it looks like all the checks passed, what is still missing to get this merged? Thanks!

Hi @andreabolognani - your PR is part of a batch that is being tested for a batch merge - https://prow.ci.kubevirt.io/?type=batch&pull=11106


Fix sidebar HTML entity encoding.

Browsers & devices needs the ampersand encoded as & to pass validation.

I don't think that's true. We are using utf-8 which makes the ampersand just fine.

Agreed with @XhmikosR, which issue are you trying to fix ?

Yup, surprisingly, a naked & is fine (and don't even think it's related to utf-8, just general HTML5 parsing) https://validator.w3.org/nu/?doc=https%3A%2F%2Fgetbootstrap.com%2Fdocs%2F4.0%2Fgetting-started%2Fintroduction%2F

My guess is @bardiharborow was trying to implement the vnu.jar integration and thought this was causing issues :)
Here are the current HTML errors (minus the missing src for img): https://gist.github.com/XhmikosR/9e417efb51b3b7b86c8502c8bb36b7a0
Most of those come from jekyll_toc and from the remaining ones, most of them must be by design.

It appears that my understanding came from Section 5.3.2 in the HTML4 spec, where it says:

Authors should use "&" (ASCII decimal 38) instead of "&" to avoid confusion with the beginning of a character reference (entity reference open delimiter).

I cannot find an equivalent section in the HTML5 spec, and in fact I'm beginning to suspect that entity references have been generally depreciated. You learn something new every day I guess.