end of concrete_solve

After seeing how these tutorials turned out, I took it upon myself to figure out how to make it so that DiffEq code could use adjoints with literally no change and is safe. Turns out it works. This PR removes concrete_solve and makes it so that it's all solve usage, since concrete_solve is now deprecated in DiffEqBase v6.36. The manifest might need an update, and my computer is the absolute worst case right now for that so I just directly edited the rendered results.
@vaibhavdixit02

Thanks! I imagine using solve should change the results too, do you want me to rerun this?

@cpfiffer we would have the same problem and it might need to be run multiple times for it to look good. Also, something's broken in OrdinaryDiffEq that prevents the run of the zygote backend problems. I will put in a fix in some time

Also, something's broken in OrdinaryDiffEq that prevents the run of the zygote backend problems.

What do you mean?

Can we just set a seed? It's incredibly expensive and time consuming to run this thing and I'm not interested in running and rerunning it every time we update something to see if it's mixing well. There are too many other tutorials to keep track of and they should all mostly work whenever they're run.

FWIW, the Turing.jl v0.13 update only broke the first example which is pretty quick, so it would be good to isolate that out and find out what happened in the latest release.

I mean more that I should be able to rerun this notebook locally and it should mix the same as the markdown file, and if that's not the case, something needs to be modified. I thought @Vaibhavdixit02's comment was that if I run this twice, one might be fine and the other might be garbage.

The chains sometimes do wonky stuff, but that's something that should get fixed instead of glossed over. One thing that could help is starting at the MAP estimate.
BTW @Vaibhavdixit02 , why did you change the default parameters of the LV equation? That might've made it a bit less stable of an example.

why did you change the default parameters of the LV equation?

I didn't, I thought you wanted to run it with these values since they are off from the mean of the distributions purposefully.

p = [2.2, 1.0, 2.0, 0.4] aren't the parameters I started on. It's a somewhat odd parameter set because it doesn't capture the cyclic nature of the solution very well.

@cpfiffer it should be good to go now

Thanks, folks!

@Vaibhavdixit02 I think you pushed the wrong version: https://github.com/TuringLang/TuringTutorials/blob/master/10_BayesianDiffEq.ipynb
(Having this as notebooks is a major PITA)

Yeah, just noticed that. I too hate having these as notebooks.

I think you pushed the wrong version:

Do you mean because of the incomplete runs?

There's a bunch of undefined errors in the notebook.

There's a bunch of errors from using an old OrdinaryDiffEq version, the first cell changes the parameters but didn't update the plot and the updated parameters are only used in the first example, so the other examples need to be re-ran. Etc.

@cpfiffer that should work with the new release of OrdinaryDiffEq

updated parameters are only used in the first example, so the other examples need to be re-ran. Etc.

They will be reran for deployment is what I understood?

We haven't set up a GitHub action to do it, so I typically rerun them on my machine and then push the updated markdown files to the repo. Super low-tech.

You should be good to go for that @cpfiffer, I saw that it runs quite a lot faster on your end so didn't run the entire notebook again purposefully

Cool, works for me. I'm running it now and I'll post here if there's issues.

Alright, yes, it should work when it re-runs, so 🤞


[CSBindings] Overload variable shouldn't be delayed by its application

When inference is determining bindings of a type variable that represents
an overload set (e.g. member or operator reference), let's not consider
it as delayed due to presence of ApplicableFunction constraint since
argument/result type inference depends on overload set but not vice versa.
Resolves: rdar://78917861

@swift-ci please test


refactor test framework

From @hongsudt on December 19, 2016 18:48

submit multiple schemas in one call
apply retry logic for 500 series error code

Copied from original issue: informatics-isi-edu/chaise#885

@hongsudt  I have added the retry logic and pushed it to master in this branch.
I couldn't implement the submit multiple schemas in one call as the API is not complete.


Get a error llike unknown args: ['--listen']

Similar bug exists in latest ComfyUI, but more severe when ComfyUI-RVC.
main.py: error: unrecognized arguments: --listen --gpu-only

Then ComfyUI no longer works.
Comfy-RVC does a good job in this regard. ComfyUI can work normally, but it will still prompt the following information:
unknown args: ['--listen']

I don't understand why this occurs. Is it because the wrong main.py is used due to the addition of sys.path, or is it for other reasons? I hope you can answer my questions

This is printed by the config.py file I copied from mainline rvc repo, it can be safely ignored.

This is printed by the config.py file I copied from mainline rvc repo, it can be safely ignored.

Thanks for your answer.


clarified getting started Compose topics based on user feedback

Added info based on issue #269 submitted by @itudoben
cc @dnephin
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

LGTM, merging


Fix getting FrameworkName from TargetFrameworkAttribute on Mono

The Mono implementation looked at FrameworkDisplayName which is something like .NET Portable Subset, but the Windows/COM implementation got the framework identifier as .NETPortable,Version=v4.5,Profile=Profile259.
Changed the Mono implementation to get the first constructor argument of the attribute, which contains what we want.
/cc @JeremyKuhne now that the Mono bug is fixed, I noticed this while testing.

LGTM. @ValMenn - Added issue #119 so we can generate and consume updated packages.

Looks good.


correct java main method signature, otherwise performance can't be ru…

…n in IDE

@shidongwa Thanks, merged.


[DOC] Information on mapping claims must in the top of the document

Information on mapping claims are currently in the bottom of the page. I think it should be take to upper level. Its easy for user t understand the concept and do the claim mapping.
Better  if you can explain Requested Claim and Mandatory Claim via a simple example
[1]https://docs.wso2.com/display/IS540/Configuring+Claims+for+a+Service+Provider

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Single configuration for all functions (best practise for typescript functions)

Which Category is your question related to?
Lambda
Amplify CLI Version
4.31.1
What AWS Services are you utilizing?
Lambda, Lambda Layer
Provide additional details e.g. code snippets
I would like to use typescript for every function in my project and from what I saw I would have to setup typescript for each function separately, also I would have to  install the same packages for each function because they don't share node_modules or package.json and it bothers me because it looks like maintainability nightmare to me.
I looked at shared layers but I don't think it is what I am looking for. Is there any other possibility to keep everything together or what would be the best practise in that case?

Hi @tetrash
I think to support typescript for functions , you have to manually add dependencies as you were saying the functions don't share package.json and node_modules. AFAIK I don't think layers  will help in this case as typescript dependencies will be needed at compile time and layers modules will be available to lambda functions at runtime.
you can post this question on amplify discord community for a quick response and other better suggestions: https://discord.com/channels/705853757799399426/735987884355485696

@akshbhu thanks, I'll try it


Added a document processor to ensure that ner tags are well-formed.

The meat here is cc.factorie.app.nlp.ner.WellFormedNer which takes a ChainNer (it is easily adaptable to StackedChainNer) and processes a document by annotating it exactly as it's instance of ChainNer would, except that it only permits licit transitions as defined by the label domain (see cc.factorie.app.nlp.ner.SpanEncoding).
This exists primarily to make things easy for cc.factorie.app.nlp.ner.NerChunkAnnotator, and should, in general, process a document before it.

Cool, looks good, will merge once tests pass
On Thu, Oct 22, 2015 at 12:14 PM Jack Sullivan<EMAIL_ADDRESS>wrote:

The meat here is cc.factorie.app.nlp.ner.WellFormedNer which takes a
ChainNer (it is easily adaptable to StackedChainNer) and processes a
document by annotating it exactly as it's instance of ChainNer would,
except that it only permits licit transitions as defined by the label
domain (see cc.factorie.app.nlp.ner.SpanEncoding).
This exists primarily to make things easy for
cc.factorie.app.nlp.ner.NerChunkAnnotator, and should, in general,
process a document before it.
You can view, comment on, or merge this pull request online at:
https://github.com/factorie/factorie/pull/331
Commit Summary

Added a document processer to ensure that ner tags are well-formed.

File Changes

M src/main/scala/cc/factorie/app/chain/ChainModel.scala
https://github.com/factorie/factorie/pull/331/files#diff-0 (2)
M
src/main/scala/cc/factorie/app/nlp/DocumentAnnotatorPipeline.scala
https://github.com/factorie/factorie/pull/331/files#diff-1 (4)
M src/main/scala/cc/factorie/app/nlp/ner/ChainNer.scala
https://github.com/factorie/factorie/pull/331/files#diff-2 (13)
M src/main/scala/cc/factorie/app/nlp/ner/NERChunkAnnotator.scala
https://github.com/factorie/factorie/pull/331/files#diff-3 (9)
M src/main/scala/cc/factorie/app/nlp/ner/NerTag.scala
https://github.com/factorie/factorie/pull/331/files#diff-4 (88)
A src/main/scala/cc/factorie/app/nlp/ner/WellFormedNer.scala
https://github.com/factorie/factorie/pull/331/files#diff-5 (48)

Patch Links:

https://github.com/factorie/factorie/pull/331.patch
https://github.com/factorie/factorie/pull/331.diff

—
Reply to this email directly or view it on GitHub
https://github.com/factorie/factorie/pull/331.


Interactive shell will be broken in release 2.0.34

Describe the bug
A clear and concise description of what the bug is.
Over the weekend, one of the interactive shell’s dependency, prompt_toolkits released a breaking change. Unfortunately, the interactive shell module doesn’t cap the dependency (This PR is to address it on dev: https://github.com/Azure/azure-cli/pull/6485)
To Reproduce
Steps to reproduce the behavior.
Install Azure CLI from source code, or install PyPI package tomorrow (6/5) after release.  The Interactive Shell will break.
Expected behavior
A clear and concise description of what you expected to happen.
See above.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
PIP install
Additional context
Add any other context about the problem here.

Workaround:
Option 1. In the virtual environment force install prompt_toolkis==1.0.15
Option 2. Install Azure CLI from other package management system


Default canvas history page to 1 when changing between all and user transactions

When the toggle history button is pressed the table should default to the first page of whatever table is requested.
This is a super easy addition:

onChange of the toggle should simply also include setCurrentPage(1)

This was addressed by @gshorer97 in 1b6bacd3e91379e30fad2bd75a27210a819b59c8 . Closing


[opentelemetry-collector] Add conditional to override mounting ConfigMap

Hi all,
Sample from templates below show current requirements to have configuration mounted using the well defined naming schema needs configMap.create to be set to true.
    volumeMounts:
      {{- if .Values.configMap.create }}
      - mountPath: /conf
        name: {{ include "opentelemetry-collector.lowercase_chartname" . }}-configmap
      {{- end }}
volumes:
  {{- if .Values.configMap.create }}
  - name: {{ include "opentelemetry-collector.lowercase_chartname" . }}-configmap
    configMap:
      name: {{ include "opentelemetry-collector.fullname" . }}{{ .configmapSuffix }}
      items:
        - key: relay
          path: relay.yaml
  {{- end }}

In the scenario where opentelemetry-collector is deployed as a subchart with a custom configuration, users will need to specify the name of the custom configuration using the extraVolumes and extraVolumeMounts fields. This process can be streamlined by enabling conditional override capability.
For instance, we can enable override via configMap.mount and couple it with configMap.create using an OR condition. This approach will facilitate mounting the configuration using the existing naming convention if:

configMap.create is set to true
configMap.mount is set to true
both options set to true

Potential Solution
    volumeMounts:
      {{- if or .Values.configMap.create .Values.configMap.mount }}
      - mountPath: /conf
        name: {{ include "opentelemetry-collector.lowercase_chartname" . }}-configmap
      {{- end }}
volumes:
  {{- if or .Values.configMap.create .Values.configMap.mount }}
  - name: {{ include "opentelemetry-collector.lowercase_chartname" . }}-configmap
    configMap:
      name: {{ include "opentelemetry-collector.fullname" . }}{{ .configmapSuffix }}
      items:
        - key: relay
          path: relay.yaml
  {{- end }}

@chunter0 What's confusing to me is that the name of the confmap/mount isn't change based on whether "create" or "mount" is used. When would a user use "mount" instead of "create"? It seems they do the same thing.
Can you provide a subchart example where this feature would be used?

Mount isn't coupled with creation of the ConfigMap because as a user we would like to own the template in the parent chart for ConfigMap creation.
Current
As a user we're currently using the naming schema and have to get the ConfigMap mounted using extraVolumes. This is sub-optimal because this has to be specified in the parent chart and the data type is an array. If a user of the parent wants to specify another volume they will have to pass in their volumes as well as the parent chart defaults.
Parent Chart
apiVersion: v2
dependencies:
- alias: telemetryCollector
  condition: telemetryCollector.enabled
  name: opentelemetry-collector
  repository: https://open-telemetry.github.io/opentelemetry-helm-charts
  version: 0.74.0
name: parent

This example is how the parent mounts the config under the well known naming schema
extraVolumes:
- name: telemetry-configmap
  configMap:
    name: {{ telemetryCollector.fullnameOverride }}-config
    items:
      - key: relay
        path: relay.yaml

Another example if a user of the parent chart wants to add another volume, as we can see from the values below they would need to redefine the entire extraVolumes field to avoid removing the parent chart ConfigMap
extraVolumes:
- name: telemetry-configmap
  configMap:
    name: {{ telemetryCollector.fullnameOverride }}-config
    items:
      - key: relay
        path: relay.yaml
- name: user-defined

@TylerHelmuth

So this is a situation when using the chart as a subchart AND supplying your own configuration file with the same name as the one the collector would have created? So instead of
configMap:
  create: false
extraVolumes:
- name: telemetry-configmap
  configMap:
    name: {{ telemetryCollector.fullnameOverride }}-config
    items:
      - key: relay
        path: relay.yaml

you'd do
configMap:
  create: false
  mount: true

Exactly @TylerHelmuth

@chunter0 ok I'm understanding now. This feels ok to add, but potentially confusing.  We'll want to add comments to the section that make it very clear how this field should be used.

IMO this feels brittle – it requires the parent to name the configmap exactly what the subchart expects for its naming convention. I think it would be cleaner if you instead provided something like existingName: "somrandomcm" which would control this feature. This would let the user specify a name and mount the configmap simultaneously.

@jaronoff97 You're thinking instead of having a boolean control this behavior you'd want something like this
configMap:
  existingName: "some-name"

And the chart templates mount based off that field?

yes, that's what I had in mind – it allows the user some more flexibility in terms of their naming conventions while achieving the same goal.

@jaronoff97 I like that approach

How does this this look

yep just commented, sorry was out on vacation.


No icon on Plasma Linux

Actual behavior:
Hello @thedoublejay ,
as I told you on TG a while back, there is no icon on Plasma Linux. I don't know if that is a Plasma issue or one in your appimage.
This is what it looks like: https://i.imgur.com/MDWIBV9.png
Expected behavior:
Have the actual icon available on the top left of the wallet, but also in the task manager.
How to reproduce it (as minimally and precisely as possible):
Start the wallet on Linux, maybe KDE Plasma is required for this, maybe X11 as well, not sure exactly but somehow I doubt it.
What are your environment parameters?

DeFi Wallet Version: 2.5.2
Operating System (OS): Arch Linux AMD64
Current free storage capacity: More than enough

Anything else we need to know?
It's low priority, but I think it would look much better to potential users.

Hi @John-Gee , may I know what icon do you mean?

@izzycsy
If you look at the screenshot I posted, you'll see the default X11 icon instead of the DeFiChain one.

Hi @John-Gee , thanks for elaborating, will inform the team. Thank you.

Sure thing, thank you!

Hi @John-Gee , update v2.6.0 is out, this is a mandatory update.
Please read through the release notes before updating. This comment is to notify you about the update.

Hi @John-Gee , update v2.6.1 is out.
Please read through the release notes before updating. This comment is to notify you about the update.

Hi @John-Gee , update v2.6.2 is out.
Please read through the release notes before updating. This comment is to notify you about the update.

Also on ubuntu 21.4 the defi wallet app  not appear icon.

Hi @John-Gee @angelocastiglione , update v2.6.3 is out.
Please read through the release notes before updating. This comment is to notify you about the update.

Hi @John-Gee @angelocastiglione  update v2.7.0 is out, this is a mandatory update. Kindly backup wallet before updating.
 Please read through the release notes before updating. This comment is to notify you about the update.

Hi @John-Gee @angelocastiglione , update v2.7.1 is out, this is a mandatory update. Kindly backup wallet before updating.
 Please read through the release notes before updating. This comment is to notify you about the update.


visibilityOf/presenceOf/etc. gives wrong result for disabled inputs

Bug report

Node Version: 10.9.0
Protractor Version: 6.0.0
Angular Version: 7.2.10
Browser(s): Chrome
Operating System and Version Window 10

When using expected conditions on a disabled input the following EC:s gives you false even though the element is really there (verified visually):
presenceOf
visibilityOf
elementToBeClickable
Also textToBePresentInElementValue doesn't match even though it should
Same code worked fine before upgrading.
Steps to reproduce:

Add a disabled input to any page you're testing

<input class="field" value="test" disabled />

Add an expected condition

await browser.wait(ExpectedConditions.visibilityOf(element(by.css('.field'))), 30000);

No Profit. Will fail even though element is visible.

Edit: I might add that textToBePresentInElementValue doens't work, but element.getAttribute('value') does. So it doesn't seem related to getting the actual value.

@cnishina: Would you mind take a look at this?

@kyliau @alan-agius4 : I noticed you guys have started to make commits in this repo! That's awesome. When we did a POC to try to move to Protractor 6 this is what stopped us. Please take a look whenever you have the chance and thanks for you contributions.

Hi @JonWallsten, protractor version 6, is deprecated.
Unless you are already on Protractor version 6 you shouldn’t try to use it.

@alan-agius4 I'm aware. We did this POC last year. But I doubt this bug has been fixed since. Hence the mention on you guys. I can try to recreate the behavior in 7.x.x and update the bug. If I recall correctly this was the major thing stopping us from proceed with the await/async upgrade. I tried to figure out myself what was happening, but got lost in the Protractor source code.

This is still an issue, I have experienced. It was working few weeks ago until I updated to latest protractor version 7.0.0

As far as I'm aware this issue was with 6 due to a alpha version of selenium driver used. Protractor 7 uses the same stable selenium driver as 5.x and appears to be mainly a code clean-up

I found root cause was test failed due to failed test when running multiple instance causing selector not found and second instance not opening  the page


[Analytics] Add usage example for a SaaS customer to adopt Analytics Engine

As we grow Analytics Engine usage we're going to want to provide in-depth examples of how customers can benefit. This commit adds the first of those examples, which gives a basic summary of how and why a customer running a software-as-a-service platform would use us. We should be able to use this example as a direct reference with some customers.

Can this be merged?


support button initialize

This PR has a field due to Its size, ChatGPT pull request should have size of 2048 Token.


"android.power_rails" Stdlib SQL implementation does not match the docs.

For Android power rails, the raw value stored in the counters table is the cumulative energy consumed since boot. This is measured in micro Joules or uWS (micro watt seconds) as denoted in the track name and the trace proto spec: https://cs.android.com/android/platform/superproject/main/+/main:external/perfetto/protos/perfetto/trace/power/power_rails.proto;l=46
the android_power_rails_counters table simply contains the raw value from the counters table without converting it from energy to power. The android.power_rails implementation however documents that this value is in microwatts:

Power rails counter value in micro watts.

https://cs.android.com/android/platform/superproject/main/+/main:external/perfetto/src/trace_processor/perfetto_sql/stdlib/android/power_rails.sql
Either the implementation or doc should probably be updated so that they match.

Power rails counter value in micro watts.

Yeah I think this is a typo, there is a missing "seconds" here. Will take a look tomorrow.


API Privacy

Review which parts of the API should be public.
Make all the readwrite stuff private?

Current public/private control is not as fine-grained as I'd like (hence why the detail module exists).

There has been some review already (though also see #43).


[IRGen] Fix crashes involving ObjC generic params

Sema allows you to pass type-pinning parameters into an extension of an Objective-C generic class, but IRGen did not properly handle erasing these types to existential types in runtime metadata. This commit corrects that mistake.
Fixes rdar://80708693.

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 6572a19b6706f4573d422bff6784cf2f6a15cf05

Force-pushed an expungement of the original implementation (although I kept the changes correcting the isTypeErasedGenericClass()/usesObjCGenericModel() split, since that was just silly).

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 70d120bc7146c589b8e23289c321f817c0743a00

@swift-ci please test linux platform

Build failed
Swift Test Linux Platform
Git Sha - 70d120bc7146c589b8e23289c321f817c0743a00

The Linux failure is unrelated and apparently caused by a recent change to SwiftPM to use Swift Collections.

@swift-ci please test linux platform


Unique molecule ID taking into account tautomerism

We are looking into generating a unique molecular ID that will give different IDs if two molecules are different tautomeric forms.
Features should be:

fast: we potentially want to apply it at large scale
consistent mol → ID: we should be able to recompute an ID from a given molecule (can't be random neither auto increment)
stable across python/rdkit and datamol versions: a unique ID should still be the same in a couple of years.
differentiate tautomeric forms

An elegant way would to use a non-standard inchi that would include a hydrogen layer /f. See https://en.wikipedia.org/wiki/International_Chemical_Identifier for details.
Here is a proof of concept that it works:
import datamol as dm

from rdkit import Chem

# SMILES: "N=C(N)O"
inchi3 = "InChI=1/CH4N2O/c2-1(3)4/h(H4,2,3,4)/f/h2,4H,3H2/b2-1?"

# SMILES
inchi4 = "InChI=1/CH4N2O/c2-1(3)4/h(H4,2,3,4)/f/h2-3H2"

mol3 = dm.from_inchi(inchi3)
mol4 = dm.from_inchi(inchi4)

print(dm.to_smiles(mol3))  # N=C(N)O
print(dm.to_smiles(mol4))  # NC(N)=O

# generated inchi and inchikey remain the same since the hydrogen layer has been removed

print(dm.to_inchi(mol3))  # 'InChI=1S/CH4N2O/c2-1(3)4/h(H4,2,3,4)'
print(dm.to_inchi(mol4))  # 'InChI=1S/CH4N2O/c2-1(3)4/h(H4,2,3,4)'

print(dm.to_inchikey(mol3))  # 'XSQUKJJJFZCRTK-UHFFFAOYSA-N'
print(dm.to_inchikey(mol4))  # 'XSQUKJJJFZCRTK-UHFFFAOYSA-N'

# when computing the inchikey directly from the non-standard inchi with the hydrogen layer
# those are different

print(Chem.inchi.InchiToInchiKey(inchi3))  # XSQUKJJJFZCRTK-ZIALIONUNA-N
print(Chem.inchi.InchiToInchiKey(inchi4))  # XSQUKJJJFZCRTK-UBUOBULFNA-N

But currently I haven't found a way to actually generate that hydrogen layer with rdkit. It seems to me that rdkit can only read the hydrogen layer and not generate it. I think this is purposely, so people stick to the standard inchi since using /f is non-standard.
To make it work we would have to find a way to compute the hydrogen layer, append it to the inchi and then use Chem.inchi.InchiToInchiKey(inchi3) to compute the inchikey from the inchi.

This is just a proposal, feel free to throw alternative ideas.
ping @maclandrol @craigmichaelm @zhu0619

It seems like you can control the option to take into account moving hydrogens to generate a non-standard inchi and inchikey with Chem.inchi.MolToInchiKey(mol3, options="/FixedH") (note the /FixedH from https://www.inchi-trust.org/technical-faq-2/#15.24).


feat: add mypy typing support

Hey, nice implementation of snowflake IDs! 🙌
Thought I'd throw in some mypy support.

Renamed the import of datetime to dt to fix datetime() property scope conflict
Added mypy dependency with types-requests
Enabled strict mypy rule
Excluded tests folder from mypy type-checking
Added py.typed file to indicate that typing is enabled on this project for consumers
Replaced pytest.ini with equivalent pyproject.toml rules

If this is useful, I'm also happy to add in some pre-commit hooks and GitHub workflows?
May also be a good idea to have some linting in place as well - I'm happy to set up ruff in a separate PR if interested?

Nice work! Please give me some more time to review.


Separate Killmails from Requests

Right now the information from a killmail has a 1-to-1 relationship with the information about a request (sidenote: Killmail info is like the time of loss, where, who. Request info is payout, modifiers, division). Splitting the concept of a request would also mean changing a division would no longer be a thing, and would mean you could apply to multiple divisions at once.
Problems to solve include:

[ ] What information to share across divisions and how to share it.
[ ] How to migrate existing requests (probably an Alembic migration from hell).

Dupe of #46


Update dependencies

Description
Changes proposed in this pull request:

Update Spring boot version
Update PostgreSQL driver version

Related issue(s)

See also https://github.com/kyma-incubator/compass/pull/1990

/hold cancel


README: Update all contents to match project

Parent issue: #36

UI.png needs to be 726 x 593px (width x height)


Hi, I see that your wip logo is gone. Can you train the soundstream (loss drops normally) and achieve good results?

Hi, I see that your wip logo is gone. Can you train the soundstream (loss drops normally) and achieve good results?

Hey, I'll be having a look at this next week. I'll let you know how I get on! At this stage I believe @lucidrains is predominantly focused on setting up the architectures.

FYI I've tried training it with a single batch to overfit but it didn't. I am also casually checking the code and I'll share if I find something.

yea people are successfully training it now


switch from rollup to esbuild

builds were getting extremely slow. there were two reasons:

rollup can get slow on large codebases
we were doing TS typechecking as part of bundling

This commit makes two changes to fix that:

switches to esbuild, a new experimental bundler written in Go
which is orders of magnitude faster than rollup
move typechecking out of band so it doesn't block compilation, but just emits warnings separately

Instructions for how to test:
https://github.com/geoffreylitt/wildcard/blob/3c16fe83d84e1a23f757b4099501833ee999298f/docs/devenv.md
Basically, in two terminal tabs:

yarn run dev
yarn run tsc

This addresses #28

todo: I should move esbuild to the dev dependencies section


Adding myself to projects and removing Sam from owners

Follow up for #100 also adding myself and @cent5 to projects to make sure we have current owners.

(need a /merge command)

/merge


README: add more details about whys and what fors

See discussion on #1

Thanks for the approval. What's the process for merging here?

Well, it looks like you need to fix conflicts first :(

rebased and ready to go


I have run black on the cli module and fixed a tiny bug with a formatting argument not being interpolated when reporting missing dependencies.

Does this resolve #1349?

This is hard to review. If you're going to black things, can you make that a separate commit so that the semantic changes can be seen and evaluated separately?
I would suggest something like:
git rebase -i upstream/master^
# set `master` to `e`
black <files>
git commit -a -m 'STY: black'
git rebase --continue
# resolve all conflicts in favor of 1a2a299

@effigies sorry about that, I separated it in two commits
@tsalo, yes, I made a reference to resolve that issue. Thanks pointing it out.

Hello @oesteban! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file fmriprep/cli/run.py:

Line 123:17: E113 unexpected indentation
Line 123:100: E501 line too long (105 > 99 characters)

I'm going to assume that the black call was semantically neutral.

I just called black fmriprep/cli and then fixed a couple of pep8 errors it introduced (apparently it likes to have trailing commas after list elements and other semantically neutral stuff). So yes, semantically neutral.


Add support for connectOrCreate

Problem

Suggested solution

Alternatives

Additional context

shall we mark this as closed?

ah yes!


ERROR TypeError: b.className.replace is not a function     at e.resetAnimation (wow.min.js:2)

ERROR TypeError: b.className.replace is not a function
at e.resetAnimation (wow.min.js:2)
when i used material checbox

Hi @oveshparasara
Could you provide a minimum info about your setup?

ng version?, cli version?
npm or yarn version?
wowjs version ( library has been tested with wowjs-1.1.3)
repro steps, or even better, repro project
full stackstrace and when does it appear?

Thanks

WOW - v1.1.2
node : v9.4.0
Angular CLI: 1.7.4
OS: linux x64
Angular: 5.2.10
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
@angular/cdk: 5.1.1
@angular/cli: 1.7.4
@angular/material-moment-adapter: 6.0.0
@angular/material: 5.1.1
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.10.0
npm 5.6.0
when check on material checkbox then throw  ERROR TypeError: b.className.replace is not a function
at e.resetAnimation (wow.min.js:2)

Hi,
Do you have a  repository I can fork to reproduce the error?

I'm having same problem. When i checked on material checkbox this error appear, Someone gives the answer here https://github.com/matthieua/WOW/issues/185#issuecomment-319997317 but the problem is how do i change that line on production in angular 7.
Thanks

Hi @sanoj-v ,
Unfortunately, there is nothing i can do. As the link you provided shows, this is an issue on WOW.js (not on this library ngx-wow , which  is simply its wrapper for Angular).
It seems a PR has already been created with the proposed fix (see https://github.com/matthieua/WOW/pull/239) , but it hasn't been merged yet...


Disabled and Readonly not working in inline mode

Describe the bug
disabled=true is not working when inline is set to true
To Reproduce
<Datepicker
    v-model="date"
    :disabled="true"
    :inline="true"
  />

Expected behavior
Disabled state, where you can not select a date
temp fix
:class="[{ 'opacity-50 pointer-events-none': disabled }]"

Maybe the same with "readonly"
So disabled - everything gray like a disabled date, nothing clickable
and with readonly="true", nothing clickable but keep the styling?

Hmm, I didn't even think about it 😄 . Will fix it

Fixed in v2.4.3


Avoid storing the list of members of a Poet round in the proof

Motivation
Currently, the Poet proof is stored in the following structure, along with a potentially huge list of all members of the respective poet round: https://github.com/spacemeshos/go-spacemesh/blob/5c7f4867ccbe1750b31862e9a4d5576621ebb3d3/common/types/activation.go#L343-L349
It is excessive (the proof is big). It should be enough to only store the merkle proof proving the sequential work. It should be the responsibility of the NiPoST to prove the NiPostChallenge it references is actually a member of the PoET.
Proposal
The proposed changes are to:

avoid storing a list of members in a poet proof,
store a merkle proof proving membership in NiPoST,
modify NiPoST validation as follows.

Updated structures:
type NIPost struct {
	// A proof that the challenge for the PoET, which is
	// constructed from fields in the activation transaction,
	// is a member of the Poet's proof.
	// Proof.ProvenLeaves contains the challenge.
	// Proof.Root must match the Poet's POSW statement.
	Proof poetShared.MerkleProof

	// Post is the proof that the prover data is still stored (or was recomputed) at
	// the time he learned the challenge constructed from the PoET.

	// The proof should be verified upon the metadata during the syntactic validation,
	// while the metadata should be verified during the contextual validation.
	PostMetadata *PostMetadata
}

// PoetProof is the full PoET service proof of elapsed time. It includes the leaf count and the actual PoSW.
type PoetProof struct {
	poetShared.MerkleProof
	LeafCount      uint64
}

A node should store PoetProof along with the statement in a key-value store. The Statement will be later used to verify if the nipost challenge of an ATX is actually a member of a PoSW it references. For example:
type PoetProofWithStatement {
	PoetProof
	// The input to Poet's POSW.
	// It's the root of a merkle tree built from all of the members
	// that are included in the proof.
	Statement []byte
}

Validation of a PoET in nipost builder

Construct a merkle tree from the list of poet round's members.
The root of the merkle tree is the PoET proof's statement.
Validate the PoET's merkle proof (POSW) with the statement
Save PoetProof in DB.

When a PoetProof is already saved in DB we consider it validated.
Validation of NiPoST in ATX handler

verify NIPost.Proof
obtain (from DB/fetch) PoetProof by its ref (NIPost.PostMetadata.Challenge)
a. if poet proof needs to be fetched, validate it against NIPost.Proof.Root, which is (should be) the POSW statement
b. otherwise verify if NIPost.Proof.Root == proof.Statement - this check proves the "elapsed time" part
verify NIPost.Post the same way as it is done now - this check proves that the smesher still held data after "elapsed time"

just two important limits from yesterday call:

merkle path should be limited to some small'ish number based on the total number of members that poet can accept
poet should limit total number of members, to ~100000, so then path should be max 17 i think


Make FSTPostingsFormat load FSTs off-heap

Description
FSTs supports to load offheap for a while. As we were trying to use FSTPostingsFormat for some fields we realized heap usage bumped.
Upon further investigation we realized the FSTPostingsFormat does not load FSTs offheap. This PR addresses that.

@Tony-X have you tried passing all Lucene unit tests using this Codec?  I think you can add -Dtests.codec=... to force all tests to use it.

@mikemccand hey Mike, I did not make a new Codec for this. IIRC, FSTPostingsFormat will be exercised by the RandomCodec. Also there is TestFSTPostingsFormat extends BasePostingsFormatTestCase that tested this PostingsFormat.
Oh wait, I see that the test target support -Dtests.postingsformat to override posting format. So I ran ./gradlew test -Dtests.postingsformat=FST50  and all tests passed.
Since the successful output doesn't provide randomization info, I also ran with an non-existent postings format ./gradlew test -Dtests.postingsformat=FST5x and it failed, which means the override is happening.
`

Thanks for the CHANGES entry - I'll push shortly

Thanks @msokolov !

I think this was mistakingly not backported to 9.x?  (I only caught this because I was seeing merge conflicts trying to backport #12803 and saw this.  I'll backport shortly -- I think this is low risk for the pending 9.9.0 release: this has baked in main for a couple months, and this is a very rarely used experimental postings format.


Create meaningful names for SCION apps

Following up on https://github.com/netsec-ethz/netsec-scion/issues/61, as SCION apps are (will be) installed into /usr/bin thus globally available on the end users' systems, they should

have meaningful names
do not clash with already released products

E.g. netcat or ssh is something that has to be renamed as we cannot blindly install a binary named netcat into any system which we expect to be still functional afterwards :)

webapp becomes scionviz?

I'd still argue viz means completely nothing to me, but this is already much much better than webapp :)

Just some suggestions:

scionlab-hud
scionlab-dashboard
scionlab-control-panel
myScionlab
iScionlab :balloon:

scionlab-viewer?

iScionlab is growing on me :1st_place_medal:

scionlab-dashboard +1

dashboard sounds good ... descriptive.
Was trying to find a good word that starts with SL, but there are not that
many. SLICK has some good meanings, the acronym expansion is ScionLab
Investigator and CheKer.
On Thu, Oct 3, 2019 at 4:09 PM Mateusz Kowalski<EMAIL_ADDRESS>wrote:

scionlab-dashboard +1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/netsec-ethz/scion-apps/issues/108?email_source=notifications&email_token=AB6SLGOL2KM2ILYVWOCMXW3QMX4IVA5CNFSM4I32Y4B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAIKOBQ#issuecomment-537962246,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6SLGIRRJ3AVE5332V6VVLQMX4IVANCNFSM4I32Y4BQ
.

sled SCIONLab Experiments Dashboard

Having only just recently been exposed to the "webapp", I think SCIONLab Experiments Dashboard sounds very fitting and I would immediately understand the purpose. 👍

In the meantime, all demo applications are built and installed with a mostly reasonable binary name (scion-netcat, scion-sshd, etc).
We can still keep this open, as the "webapp" name is still there. I'll edit the title of this issue to only refer to renaming webapp. At the moment, nobody is really maintaining webapp though, and I'm not sure what will happen with it.


Permify Fails to Launch with PostgreSQL Without Specific Environment Variables

Description:
When running Permify with PostgreSQL, the application fails to properly start if the following environment variables are not set:
PERMIFY_DATABASE_MAX_OPEN_CONNECTIONS=100
PERMIFY_DATABASE_MAX_IDLE_CONNECTIONS=20
PERMIFY_DATABASE_MAX_CONNECTION_LIFETIME=300s
PERMIFY_DATABASE_MAX_CONNECTION_IDLE_TIME=60s
Suggested Solution:
To resolve this issue, default values should be added to internal/config. This would ensure that the application can start correctly even if these specific environment variables are not explicitly set by the user.
Impact:
Without these default settings, users must manually set these environment variables to avoid startup failures, which could lead to operational disruptions and increased setup complexity.
Next Steps:

[ ] Add default values for the above-mentioned environment variables to internal/config.
[ ] Test to ensure that the application starts correctly with and without these environment variables set by the user.

Hi @tolgaOzen, I have created a draft PR for this. Could you please check it and let me know if I need to make any more changes? Thanks!


[Bug]: Failed to launch the browser process

Minimal, reproducible example
const puppeteer = require('puppeteer');
const browser = await puppeteer.launch({ headless: 'new' });

Error string
Error: Failed to launch the browser process!
Bug behavior

[ ] Flaky
[ ] PDF

Background
Trying to open a page, code works fine on local (Windows 11, Node 20) but doesn't work on my VPS (Ubuntu 22, Node 18).
Expectation
Launch the browser
Reality
/home/container/node_modules/@puppeteer/browsers/lib/cjs/launch.js:259
                reject(new Error([
                       ^
Error: Failed to launch the browser process!
/home/container/.cache/puppeteer/chrome/linux-114.0.5735.133/chrome-linux64/chrome: 1: Syntax error: "(" unexpected
TROUBLESHOOTING: https://pptr.dev/troubleshooting
    at Interface.onClose (/home/container/node_modules/@puppeteer/browsers/lib/cjs/launch.js:259:24)
    at Interface.emit (node:events:525:35)
    at Interface.close (node:internal/readline/interface:533:10)
    at Socket.onend (node:internal/readline/interface:259:10)
    at Socket.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Puppeteer configuration
No response
Puppeteer version
v20.8.0
Node version
v18.16.1
Package manager
npm
Package manager version
8.5.1
Operating system
Linux

tried using puppeteer-core with the browser that puppeteer installed, reinstallig everything and literally everything I could think of but I still can't figure it out.

It looks like a mismatch in cpu architectures between the binary and the server. What kind of cpu do you have? E.g., https://github.com/puppeteer/puppeteer/issues/9384 we do not currently have arm64 binaries for Linux (but we hope to have it soon).

It looks like a mismatch in cpu architectures between the binary and the server. What kind of cpu do you have? E.g., https://github.com/puppeteer/puppeteer/issues/9384 we do not currently have arm64 binaries for Linux (but we hope to have it soon).

the server is using an ampere cpu, i forgot to post an update but the issue was that i need a gui. don't really know how i'll get it but i'll figure it out eventually 👍

I was getting the same error message, but was able to solve it by installing Nodejs with Volta instead of using the version that was installed with the snap package manager.
Here's a bit more info... I'm migrating from an x86 AWS EC2 instance to an ARM instance using Ubuntu 22. At first Puppeteer failed to install Chrome so I installed chromium-browser with apt. However, the snap package manager actually ended up installing it for some reason (something to do with it being a "transitional package"). Then set the "executablePath" for Puppeteer to the package-manager-installed version of Chromium, but kept getting the "Failed to launch the browser" error. I tried a LOT of different things that didn't work out.
Eventually I launched a fresh ARM EC2 instance and started from scratch but ended up using Volta to install Nodejs and it worked right away. I didn't realize the first machine had used snap to install Nodejs until I was comparing everything I could between the two servers and compared the output from the command "snap list".
So in the end I

installed volta: curl https://get.volta.sh | bash
used volta to install nodejs and yarn: volta install node && volta install yarn
installed puppeteer with yarn: PUPPETEER_SKIP_DOWNLOAD=1 yarn add puppeteer
installed chromium with apt/snap: apt install chromium-browser
set the puppeteer launch option "executablePath" to the package-manager-installed chromium


Passing extra information to a partial template instantiation

I'd like to know whether there's any best practice about passing extra arguments to a partial template. Let's assume I have a partial template like this:
<button class='btn btn-default btn-sm' type='button'>

</button>

I'd like to be able to use a single template to produce a button with glyphicon-chevron-right and glyphicon-chevron-left. However, as far as I can tell:

I can't create complex variables in templates (ie. a map containing current . and direction key);
I can't pass more than one argument to {{ template "foo" bar }} call;
I can't add new keys to ..

Any other way to get this functionality? Currently I'm simply defining two separate templates, but that's clumsy.

Ran into this issue today as well - wasn't sure if my understanding of Go template was bad, or if there's no good way. I would have spent less time getting stuck if documentation mentioned that there's no good way. I was trying to migrate a Jekyll theme, and Jekyll has a way to pass multiple parameters to its "includes" call.

It seems the best solution so far has been the .Scratch feature that @bep recently added.

@spf13 wow, thank you for a quick reply! @bep that's great!
For everyone else, here's the relevant pull request:
https://github.com/spf13/hugo/pull/746
Hopefully the documentation page reflects the change soon:
http://gohugo.io/extras/scratch

I don't think we'll gonna provide anything "smarter" than Scratch anything soon, unless provided by the Go templates -- so close this. Hate open issues :-)

Oh, and until 0.13 gets out in the open -- the latest docs can be read nicely at https://github.com/spf13/hugo/blob/master/docs/content/extras/scratch.md

0.15 introduces a map that can be used for this https://github.com/spf13/hugo/pull/1463
See dict function http://gohugo.io/templates/functions/#dict


Missing "script/runner", undocumented dependency on rails?

When I try to use this gem in a plain old ruby project, runner tasks fail with:
bundler: command not found: script/runner
Install missing gem executables with `bundle install`

I know this is exists in rails projects, but the readme didn't make it seem like Rails was a hard requirement. I'm just trying to run a script on a schedule and this gem seemed perfect.
schedule.rb:
set :output, "./checker.log"
every 1.minutes do
  runner "Checker.run"
end

I installed whenever using the instructions, added to my Gemfile and ran bundle exec wheneverize ., then whenever --update-crontab

try to use bundler: bundle exec whenever --update-crontab

try to use bundler: bundle exec whenever --update-crontab

Won't help. Experienced the very same issue in a plain ruby project. Whenever expects rails script to be present for runner tasks, otherwise it relies on the presence of script/runner:
https://github.com/javan/whenever/blob/e916b58f29ea4da76de9ddc5aca8c85a5f29f897/lib/whenever/setup.rb#L16-L23
Unfortunately, this script is missing and Whenever doesn't provide any option to create it. Having generator for such script or instructions in README or Wiki would be great.
I've solved this issue for myself by switching to rake tasks as my scenario allows them.
Another possible solution is to setup runner manually in config/schedule.rb, for example:
set :runner_command, 'ruby -r ./some/lib/dependency -e'
job_type :runner, 'cd :path && :bundle_command :runner_command ":task" :output'


remove spurious \

When in markdown one needs https:\// but when included in a code snippet you don't need the additional \

@simonzoopla : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@simonzoopla : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the formatting fix; thanks @simonzoopla.

Verified the formatting fix; thanks @simonzoopla.


release->master mergeback

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/213/ : SUCCESS in 7s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/219/ : SUCCESS in 3s

Sonar scan result

No issue found. Congratulations!

More detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-public-demos-gate-PR92
To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'.

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/214/ : SUCCESS in 7s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-merge-compliance-check/79/ : SUCCESS in 9s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-sonarqube-scan-zuul-gate/77/ : SUCCESS in 40s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-fossa-scanning-zuul/40/ : FAILURE in 6s (non-voting)


Add 'about' link to FAQ in menu (replacing the link to Great Firewall)

Blocked on #65

https://github.com/dhowe/ChinaEye/pull/67


Update getting started documentation

Need to add more on the getting started / details on:

Creating processing components
The build command
Creating routes by config

Done


Expand the Defects4J benchmark to be the complete version 2

Currently it contains 75 bugs out of the 835 as I was able to quickly grab 75 through SequenceR's metadata

I have updated the list but currently missing are the line numbers for most of the bugs. A subset of this data can come from https://github.com/program-repair/defects4j-dissection

This comment may help to resolve the issue.


need help

Hello, I only saw 4134 AMPs in the code. Where are the 8225 AMPs of CAMP mentioned in the paper? Can we use it?

You can get it from AMPdb_data.csv


Is phoenix or chimera better for german?

Hi @CyberTimon,
Thanks for your attention. For German, we recommend Chimera. Its backbone is LLaMA, which has native support for German.
Best,
Zhihong

Yes, the dataset we used contains German instruction data. We will also expand the dataset in the future. :-)
Best,
Zhihong

Thank you very much! The model works very well.


Dsday24 speakers

can I get you both to cast an eye over this please - it's holding information only at the moment until we have something more concrete

This is now only awaiting the session info for the content panel as it feels slightly different, and for the closing keynote :)


Dramatically improved the UI style.

Here is a rewritten UI.

Thanks for the PR, but 2048 is in maintenance mode. World-changing PRs aren't needed at this point.


Could you possibly add an option to remove textures completely and replace them with the smooth plastic ones

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
Could you possibly add an option to remove textures completely and replace them with the smooth plastic ones. Also is there a way I can have high render distance but low graphic quality and finally is there a fast flag you could use to remove grass on Roblox's new terrain?

Yeah, that's already planned to be added, if the functionality for it even exists until then.
To address those last two requests, see if this flag config works for you. This will force the quality to be as low as possible regardless of render distance, and set grass to never render.
{
   "DFIntDebugFRMQualityLevelOverride": "1",
   "FIntFRMMaxGrassDistance": "0",
   "FIntFRMMinGrassDistance": "0"
}

Copy and paste this JSON config and import it into the flag editor, and it should work. Let me know if you have any issues.

Thanks alot for your support I really appreciate it
On Thu, Feb 22, 2024 at 12:06 AM pizzaboxer @.***>
wrote:

Yeah, that's already planned to be added, if the functionality for it even
exists until then.
To address those last two requests, see if this flag config works for you.
This will force the quality to be as low as possible regardless of render
distance, and set grass to never render.
{
"DFIntDebugFRMQualityLevelOverride": "1",
"FIntFRMMaxGrassDistance": "0",
"FIntFRMMinGrassDistance": "0"
}
Copy and paste this JSON config and import it into the flag editor, and it
should work. Let me know if you have any issues.
—
Reply to this email directly, view it on GitHub
https://github.com/pizzaboxer/bloxstrap/issues/1319#issuecomment-1958422422,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BC7HNB6WI2OZPVTSFWIA7FTYU2DXVAVCNFSM6AAAAABDTPWP2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYGQZDENBSGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add support for anything renderable as children rather than just strings.

Hi all,
We recently upgraded to v5.0.3 and ran across the following error:

The error is due to only children of type string being supported rather than anything renderable. This PR contains a failing test with a example of using JS expressions within children.
From React docs https://facebook.github.io/react/docs/jsx-in-depth.html#children-in-jsx

In JSX expressions that contain both an opening tag and a closing tag, the content between those tags is passed as a special prop: props.children. There are several different ways to pass children [...]

Where children can typically be anything that can be rendered: numbers, strings, elements or an array (or fragment) containing these types (from PropTypes.children)
With the current API, I would expect children of these various types to be supported. However for example, <title> requires the children to be strings.
To summarize by examples:
const title = 'The Title';

// Works
<Helmet>
  <title>Title: The Title</title>
</Helmet>

// Works
<Helmet>
  <title>{'Title: The Title'}</title>
</Helmet>

// Works
<Helmet>
  <title>{'Title: ' + title}</title>
</Helmet>

// Doesn't Work
<Helmet>
  <title>Title: {title}</title>
</Helmet>

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

@kchunterdeluxe Could you sign the CLA please?  So we can give you credit for the unit test.  Thanks!

@cwelch5, CLA signed


[US] List View - Column-based ordering (ascending/descending on column header click)

As an application user, I want to be able to filter the columns of the tables, so that I can customize the filter experience.

MoSCoW
Risk
Story Points

Should
Low
4

Acceptance Criteria
Risks

Performance concerns if the data volume is large
Complexity if different column require different filtering logic

Pre-requisites

[x] Meet with the stakeholder to clarify the requirements
[ ] Complete the requirements of this US

Tasks

[x] Determine the kind of column-filtering for the existing tables
[x] Remove the dropdown for ordering
[x] add new table with new columns for ordering

Note
Table View: Looks and Feels

https://github.com/WillTrem/UInnovate/assets/92006009/c7c3ad5e-7475-4af5-8eed-2f6ebb82a5e1

Looks good! Signing off!


Fix(cx-1485): ensure android dark mode can overridden inapp

The type of this PR is: Bugfix

This PR resolves CX-1485
Description
Stops forcing of dark mode on users. This allows us to override the user's dark mode choice.
BEFORE
https://user-images.githubusercontent.com/18648835/119120134-35ddfc80-ba2c-11eb-8110-ceb0ef482766.mp4
AFTER
https://user-images.githubusercontent.com/18648835/119120385-8190a600-ba2c-11eb-9588-ef01d3ee58dd.mp4

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

This is interesting, it must be that your phone OEM custom android build is handling dark mode differently than stock android. On my phone, I have Darkmode enabled but I don't get it that way

Until later dark mode 🦇 ! Thanks!


Deleting preprocess output post segment creation

If the preprocessed output dir is defined, we will delete it after segment creation succeeds.

Codecov Report

Merging #4591 into master will increase coverage by 0.22%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4591      +/-   ##
============================================
+ Coverage     64.23%   64.45%   +0.22%
  Complexity       32       32
============================================
  Files          1072     1072
  Lines         55702    55702
  Branches       8131     8131
============================================
+ Hits          35778    35903     +125
+ Misses        17276    17148     -128
- Partials       2648     2651       +3

Impacted Files
Coverage Δ
Complexity Δ

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-25%)
0% <0%> (ø)

...elix/core/relocation/RealtimeSegmentRelocator.java
22.5% <0%> (-22.5%)
0% <0%> (ø)

...ache/pinot/common/utils/TarGzCompressionUtils.java
68.23% <0%> (-12.95%)
0% <0%> (ø)

...thandler/SingleConnectionBrokerRequestHandler.java
79.54% <0%> (-9.1%)
0% <0%> (ø)

...impl/dictionary/DoubleOnHeapMutableDictionary.java
65.21% <0%> (-8.7%)
0% <0%> (ø)

...n/java/org/apache/pinot/core/transport/Server.java
59.25% <0%> (-7.41%)
0% <0%> (ø)

.../apache/pinot/common/config/RealtimeTagConfig.java
93.33% <0%> (-6.67%)
0% <0%> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
82.6% <0%> (-6.53%)
0% <0%> (ø)

...impl/dictionary/FloatOffHeapMutableDictionary.java
83.92% <0%> (-5.36%)
0% <0%> (ø)

...troller/helix/core/retention/RetentionManager.java
75% <0%> (-4.17%)
0% <0%> (ø)

... and 28 more

Continue to review full report at Codecov.

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


Show selected collection in matrix

From @zzottel on December 5, 2013 16:46
If I choose to view only one collection, there is no visual indication that I'm not seeing the whole stream.
This is the case in several themes I tested, so I hope there's a possibility to fix that for them all in a template or something?
Copied from original issue: friendica/red#224

From @zzottel on December 6, 2013 15:51
Fixed, thanks.


[shopware-6-client] Handle sorting by multiple fields

Acceptance criteria:

[ ] ShopwareParams allows adding an array of Sort interface
[ ] query param converters (main and store-API) are aligned with the extended ShopwareParams interface
[ ] Sortings within the request are separated by comma ","

example request body:
"sort": "-level,-name",

piece of JSON above presents sorting part that sets the sorting on two fields: level and name, both in descending order

ShopwareParams accepted has been extended, and since now it accepts sort objects in an array as well like
await getCategories({
      sort: [
        {
          field: 'level',
          desc: true
        },
        {
          field: 'name',
          desc: true
        }
      ]
    })


[RFC] Users Documentation

Is your feature request related to a problem? Please describe.
No documentation for Users API
Describe the solution you'd like
Documentation for Users API

Just missing documentation on 'update'


vector style for polygon with hatch

Hi to all,
there is a manner to define, for a vector polygon,  a style with hatching pattern?
For line there is a strokeDashstyle that permit to print different line type. I want fill polygons on vector layer with some type of hatching pattern rather than coloring it in a uniform way.
Thanks.
Giuseppe

https://docs.geoserver.org/stable/en/user/styling/sld/cookbook/polygons.html#hatching-fill

Hi,
thanks for the response.
I apologize, but I did not understand correctly. I have a geojson layer.
It is not possible for this layer to define a style (with hatch) following the mapfish json style version 2?
In the posted link there is a refer to a sld syntax for hatched style.
Thanks.
Giuseppe

AFAIK, you can use directly the SLD styling in mapfish print.

How do you apply the SLD styling to a geojson in mapfish?

Like that:
https://github.com/mapfish/mapfish-print/blob/68161f4a34326736c64cdaa27bf9500fca762320/core/src/test/resources/org/mapfish/print/processor/setstyle/basic/request.json
or:
https://github.com/mapfish/mapfish-print/blob/68161f4a34326736c64cdaa27bf9500fca762320/core/src/test/resources/org/mapfish/print/processor/map/center_osm_fixedscale_dpi/requestData.json#L11

Thanks for this! I tried inserting the SLD string but formatting was not right. Got it working now!

how to apply hatched polygon on vector feature of ol instead  of whole layer for mapfish-print


extract subset load balancer metadata matches from request

Per #2334, the idea is to allow metadata matches (used to select subsets via the subset load balancer) to be computed from request data. Specifically, the intent is to match request header values against a regular expression and allow matched groups to be used as metadata values.
Configuration
One question is how to encode this configuration. Two proposals have been made.

Encode the regexes and metadata mappings in a structure parallel to the existing metadata_match field of RouteAction.
Use the regexes already encoded in the regex field of RouteMatch and introduce an additional field to allow mapping matched groups to metadata.

Option 1 allows headers to be optionally matched and converted into match criteria for the purposes of load balancing. Several optional headers could be defined and the resulting match criteria (if any) applied to routing. This option may cause the same header to be matched against multiple regular expressions (one to match the route, and one to extract metadata values).
Option 2 requires producing a route for each valid combination of headers. N optional, independent headers that produce match criteria would require 2^N routes. For a given route regexes are only matched once.
In either case, care will have to be taken to make sure the match criteria delivered to the subset load balancer are correctly sorted.
Security Considerations
My analysis is that any configuration using dynamically generated match criteria for the subset load balancer can be written using static match criteria, given a sufficient number of routes. There may be need to limit the length of header values or extract match criteria to avoid large memory allocations in the request path (existing header limits may be sufficient). Allowing arbitrary matches might allow an attacker to craft special requests to probe for metadata matches that were not meant to be exposed (e.g. internal-use versions, etc.)

@zuercher @ufodone what do you think of something like https://github.com/envoyproxy/envoy/pull/3254 as a workaround? This would at least — for now — allow us to do this from a filter. And even with regex support, some more advanced use cases would need to be able to do this from a filter.
So I am curious on your thoughts of using RequestInfo.setDynamicMetadata() to tag a request and then construct MetadataMatchCriteria from that.

@rgs1 I'll have to look into the details a bit more but at first glance I think I could use to to fulfill my use case.  I'd originally wanted to avoid writing a custom filter so that a vanilla envoy executable could be used but that's probably less important now as the deployment of such instances will be more contained than I'd originally thought.
I'd been planning on using a LUA filter so I suppose that it would be fairly easy to expose RequestInfo.setDynamicMetadata() to the LUA filter and that would eliminate my need to build a C++ filter (although I may eventually find that I want a C++ one for performance reasons anyway).

I am in need of this feature as part of our envoy migration from V1 to V2 API. As in V1 we were routing based on cluster_header
https://www.envoyproxy.io/docs/envoy/latest/api-v1/route_config/route.html?highlight=cluster_header
Now in V2 API we are in need to provide dynamic value for metadata match criteria.
Do we have any timeline when this fix will be available ?

@sahanaha cluster header is supported in v2 here: https://github.com/envoyproxy/envoy/blob/master/api/envoy/api/v2/route/route.proto#L326

@mattklein123
Thanks for the response.
Do we also support dynamic value in metadata match criteria ? In my use case I need to match ":path" in route metadata_match, something like below...
                   "route": {
                          "cluster": "some_service",
                          "metadata_match": {
                            "filter_metadata": {
                              "envoy.lb": {
                                "url":      ":path",
                                "type":   "dev"
                              }
                            }
                          }
                          }

I tried the above configuration but it did not work.

@sahanaha sorry do you just need to match on the path header? Can you describe what you are trying to accomplish exactly?

@mattklein123
Yes, idea here is to dynamically match the :Path value in route metadata with the host metadata ex:
"route": {
"cluster": "some_service",
"metadata_match": {
"filter_metadata": {
"envoy.lb": {
"url":      ":path",               //match the dynamic value with below EDS response
"type":   "dev"
}
}
}
}
and my host metadata from EDS response would be something like below..
{
   "version_info": "0",
   "resources": [
   {
     "@type": "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment",
     "cluster_name": "some_service",
     "endpoints": [
     {
      "lb_endpoints": [
      {
       "endpoint": {
        "address": {
         "socket_address": {
          "address": "host_ip1",
          "port_value": 80
         }
        }
       },
       "metadata": {
        "filter_metadata": {
          "envoy.lb" : {
“url” : "/v1/heartbeat”,                           //match the URL with :path & route it.
           "type": "dev"
         }
        }
       }
      },
      {
       "endpoint": {
        "address": {
         "socket_address": {
          "address": "host_ip3",
          "port_value": 80
         }
        }
       },
       "metadata": {
        "filter_metadata": {
          "envoy.lb" : {
“url” : "/v1/heartbeat123”,                      //match the URL with :path & route it.
           "type": "test"
         }
        }
       }
      }
 ]

}
   ]
  }
 ]
}
So that I just define a single metadata_match in route configuration, as you see metadata value for url is different for each host, however I want to configure a single route match_criteria where url value is dynamic.

@sahanaha sorry don't know off the top of my head. @zuercher is this is the same issue as the original issue?

@sahanaha we achieve this with a filter, by doing something like:
ProtobufWkt::Struct keyval;
ProtobufWkt::Value val;

const auto* header_entry = headers.get(header);
auto header_value = std::string(header_entry->value().getStringView());

val.set_string_value(header_value);
(*keyval.mutable_fields())["url"] = val;  // url is the key from your example

callbacks.requestInfo().setDynamicMetadata("envoy.lb", keyval);

However, it would be nice to be able to express this via config.

@rgs1
Thanks! I will work on adding the above mentioned filter to suite my requirement.
Do we have any ETA to achieve dynamic metadata matching via config ?

@rgs1
I have 2 questions..
#1 with the above filter example you have given how does my route metadata_match configuration looks like ? Should  I remove metadata_match config from route ?
#2 can we achieve setting dynamic metadata value with LUA filter ?
I was just exploring the LUA filter. I see that we can extract the ":path" value from the header. Is there any way that we can set :path value extracted from LUA filter into the metadata_match  ?
"route": {
"cluster": "some_service",
"metadata_match": {
"filter_metadata": {
"envoy.lb": {
"url" : "/v1/heartbeat",    // Not sure how to set "url" from the :path value in LUA filter below
"type": "dev"
}
}
}
}
"http_filters": [
{
"name": "envoy.lua",
"config": {
"inline_code": "
function envoy_on_request(request_handle)
headers = request_handle:headers()
request_handle:logTrace(headers:get(":path"))  //this extracts the value which I need for "url"
end"
}
},
{
"name": "envoy.router",
"config": {}
}
],
If it's possible then how does my route metadata_match looks like ? I did not find much help in the document.

@sahanaha:

that's correct, you don't need metadata_match per route anymore because the dynamic metadata that's set by the filter is matched directly against the endpoints' metadata. If you look at https://github.com/envoyproxy/envoy/commit/2d2506761a3c9d03594619f7c6cc8596ddb59950, you'll see that the request's metadata overrides the route's metadata (if any).

i haven't played with LUA filters, but if the requestInfo object is reachable and you can call setDynamicMetadata, you are good to go...

@sahanaha
Unfortunately the LUA filter included with Envoy doesn't expose access to the dynamic meta data feature that was added.  Would be great if it was...
I had the same use case, and hacked this together by modifying lua_filter.cc/h (this is a rough outline).
`//Expose requestInfo in Decoder/Encoder callbacks
RequestInfo::RequestInfo& getRequestInfo() override { return callbacks->requestInfo(); }
//Add to lua exported functions
{"dynamicMetadata", static_luaDynamicMetadata}};
//Impelment the lua call with something like
int StreamHandleWrapper::luaDynamicMetadata(lua_State* state) {
ASSERT(state_ == State::Running);
const char* key = luaL_checkstring(state, 2);
const char* value = luaL_checkstring(state, 3);
ENVOY_LOG(info, "Dynamic metadata key={} value={} ", key, value);
auto keyval = MessageUtil::keyValueStruct(key, value);
callbacks_.getRequestInfo().setDynamicMetadata("envoy.lb", keyval);
return 0;
}`
You then can just add the following line to your LUA script
request_handle:dynamicMetadata("somekey", "somevalue");
Hope that helps.  I have dreams of contributing something like that back, but time is lacking, and we haven't decided if we're going this route or not.

@moss94 stealing your idea, I have a WIP in here: https://github.com/dio/envoy/commit/293fcaccf4dbcac62c3fc59bf916c2636ba51454
I put the API as follows
function envoy_on_request(request_handle)
  request_handle:requestInfo():dynamicMetadata():set("envoy.lb", "foo", "bar")
  request_handle:requestInfo():dynamicMetadata():get("envoy.lb")["foo"]
end

As exhibited in the test file here. Not sure if we should default to "envoy.lb" key whenever possible.

@moss94
I modified the lua_filter.cc/h files as you suggested…
file lua_filter.h
// added the following line in FilterCallbacks
class FilterCallbacks {
…
virtual RequestInfo::RequestInfo& getRequestInfo();
..
}
//added to lua exported functions
{"dynamicMetadata", static_luaDynamicMetadata}};
// declared the following for luaDynamicMetadata
DECLARE_LUA_FUNCTION(StreamHandleWrapper, luaDynamicMetadata);
// added the following in DecoderCallbacks  and EncoderCallbacks
RequestInfo::RequestInfo& getRequestInfo() override { return callbacks_->requestInfo(); }
file lua_filter.cc
// contains the implementation of luaDynamicMetadata
int StreamHandleWrapper::luaDynamicMetadata(lua_State* state) {
ASSERT(state_ == State::Running);
const char* key = luaL_checkstring(state, 2);
const char* value = luaL_checkstring(state, 3);
ENVOY_LOG(info, "Dynamic metadata key={} value={} ", key, value);
auto keyval = MessageUtil::keyValueStruct(key, value);
callbacks_.getRequestInfo().setDynamicMetadata("envoy.lb", keyval);
return 0;
}
I am getting the following linking error when I build envoy with   ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.dev'
ERROR: /source/source/exe/BUILD:21:1: Linking of rule '//source/exe:envoy-static' failed (Exit 1): envoy_cc_wrapper failed: error executing command
(cd /build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/execroot/ci &&
exec env -
PWD=/proc/self/cwd
/build/tmp/_bazel_bazel/436badd4919a15958fa3800a4e21074a/external/local_config_cc/extra_tools/envoy_cc_wrapper -o bazel-out/k8-fastbuild/bin/source/exe/envoy-static -pthread '-Wl,--hash-style=gnu' -static-libstdc++ -static-libgcc<EMAIL_ADDRESS>-pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread -pthread '-fuse-ld=gold' -B/usr/bin -Wl,-S<EMAIL_ADDRESS>/usr/bin/ld.gold: error: external/envoy/ci/prebuilt/thirdparty_build/lib/libnghttp2.a:1:1: invalid character
bazel-out/k8-fastbuild/bin/source/extensions/filters/http/lua/_objs/config/source/extensions/filters/http/lua/config.pic.o:source/extensions/filters/http/lua/config.cc:function Envoy::Extensions::HttpFilters::Lua::FilterCallbacks::FilterCallbacks(): error: undefined reference to 'vtable for Envoy::Extensions::HttpFilters::Lua::FilterCallbacks'
/usr/bin/ld.gold: the vtable symbol may be undefined because the class is missing its key function
bazel-out/k8-fastbuild/bin/source/extensions/filters/http/lua/_objs/lua_filter_lib/source/extensions/filters/http/lua/lua_filter.pic.o:source/extensions/filters/http/lua/lua_filter.cc:typeinfo for Envoy::Extensions::HttpFilters::Lua::Filter::DecoderCallbacks: error: undefined reference to 'typeinfo for Envoy::Extensions::HttpFilters::Lua::FilterCallbacks'
bazel-out/k8-fastbuild/bin/source/extensions/filters/http/lua/_objs/lua_filter_lib/source/extensions/filters/http/lua/lua_filter.pic.o:source/extensions/filters/http/lua/lua_filter.cc:typeinfo for Envoy::Extensions::HttpFilters::Lua::Filter::EncoderCallbacks: error: undefined reference to 'typeinfo for Envoy::Extensions::HttpFilters::Lua::FilterCallbacks'
bazel-out/k8-fastbuild/bin/source/common/http/http2/_objs/codec_lib/source/common/http/http2/codec_impl.pic.o:source/common/http/http2/codec_impl.cc:function Envoy::Http::Http2::ConnectionImpl::sendPendingFrames(): error: undefined reference to 'nghttp2_session_send'
bazel-out/k8-fastbuild/bin/source/common/http/http2/_objs/codec_lib/source/common/http/http2/codec_impl.pic.o:source/common/http/http2/codec_impl.cc:function Envoy::Http::Http2::ConnectionImpl::sendPendingFrames(): error: undefined reference to 'nghttp2_strerror'
bazel-out/k8-fastbuild/bin/source/common/http/http2/_objs/codec_lib/source/common/http/http2/codec_impl.pic.o:source/common/http/http2/codec_impl.cc:function Envoy::Http::Http2::ConnectionImpl::StreamImpl::submitTrailers(Envoy::Http::HeaderMap const&): error: undefined reference to 'nghttp2_submit_trailer'
bazel-out/k8-fastbuild/bin/source/common/http/http2/_objs/codec_lib/source/common/http/http2/codec_impl.pic.o:source/common/http/http2/codec_impl.cc:function Envoy::Http::Http2::ConnectionImpl::StreamImpl::readDisable(bool): error: undefined reference to 'nghttp2_session_consume'
bazel-out/k8-fastbuild/bin/source/common/http/http2/_objs/codec_lib/source/common/http/http2/codec_impl.pic.o:source/common/http/http2/codec_impl.cc:function Envoy::Http::Http2::ConnectionImpl::ClientStreamImpl::submitHeaders(std::vector<nghttp2_nv, std::allocator<nghttp2_nv> > const&, nghttp2_data_provider*): error: undefined reference to 'nghttp2_submit_request'
Is there anything else I am missing here ? I am new to envoy code , kindly help!

@sahanaha
Looks like I left out the interface pure virtual in FitlerCallbacks in lua_filter.h
virtual RequestInfo::RequestInfo& getRequestInfo() PURE;

FYI: @ggreenway and I are currently working on implementing this in a HTTP filter, by utilizing the changes from https://github.com/envoyproxy/envoy/pull/3254. We're planning on supporting regex matching a header and constructing metadata from the regex capture groups.

@bmetzdorf @ggreenway @sahanaha let me see if we can clean & publish our internal filter so you can see the interface/config constructs that we are using. We'd be super interested in collaborating, perhaps we can get a general enough filter merged.
cc: @derekargueta

@rgs1 That would be great if you have something built already.
Here's what we were thinking roughly, for configuration:
  message Dest {
    // Defaults to "envoy.lb"
    string namespace = 1;
    string key = 2 [(validate.rules).string.min_bytes = 1];
    uint32 value_regex_group_number = 3;
  }
  message Rule {
    string header_name = 1 [(validate.rules).string.min_bytes = 1];
    string regex = 2 [(validate.rules).string.min_bytes = 1];
    repeated Dest dest = 3 [(validate.rules).repeated .min_items = 1];
  };

  repeated Rule rules = 1 [(validate.rules).repeated .min_items = 1];

@ggreenway we are not that far away then. This what ours look like currently:
package pinterest.config.filter.http;

enum ValueType {
  STRING = 0;
  NUMBER = 1;
}

message MetadataKeyValuePair {
  // The namespace. If this is empty, the filter's namespace will be used.
  string metadata_namespace = 1;

  // The key — must be present.
  string key = 2;

  // The value — may be absent.
  string value = 3;

  // The type.
  ValueType type = 4;
}

message HeaderToMetadataRule {
    // The header from which to extract a value.
    string header = 1;

    // The metadata key with which the extracted value will be paired.
    MetadataKeyValuePair on_header_present = 2;

    // If the header is not present — and this is set — insert this key/value pair instead.
    MetadataKeyValuePair on_header_missing = 3;

    // Whether or not to remove the header after it's been copied to metadata. By allowing the
    // configuration to express header removal, we easily prevent internal metadata from leaking.
    bool remove = 4;
}

message HeaderToMetadataConfig {
    repeated HeaderToMetadataRule request_rules = 1;
    repeated HeaderToMetadataRule response_rules = 2;
}

A couple of notes:

we don't currently use regexes, just direct matches. Easy to fix.
we support this both ways, for requests and responses via a StreamFilter.
we also support — very important for us — adding metadata when a header is missing (on_header_missing).

Let me know what you think of this approach. I'll try to push a clean branch today.

@bmetzdorf @ggreenway this is what we are using: https://github.com/envoyproxy/envoy/pull/3633, lmk what you think — thanks!

@moss94
Thanks for sharing your solution. This works fine for my requirement, will continue with this until the original FIX is available in envoy.

@sahanaha fyi, here are the draft docs for the header-to-metadata filter (#3633), lmk what you think. thanks!

@rgs1
The document looks good! Thanks!
I was just trying to map it with my requirement of ":path"  value matching.
Please check if the below configuration is correct
{
"http_filters": [
{
"name": "envoy.filters.http.header_to_metadata",
"config": {
"request_rules": [
{
"header": ":path",                  —> I guess the value
of ":path" will be extracted here
"on_header_present": {
"metadata_namespace": "envoy.lb",
"key": "url",
"type": "STRING"
},
"remove": false
}
]
}
}
]
}
The corresponding upstream cluster configuration will be ..
{
"clusters": [
{
"name": "versioned-cluster",
"type": "EDS",
"lb_policy": "ROUND_ROBIN",
"lb_subset_config": {
"fallback_policy": "DEFAULT_SUBSET",
"default_subset": {
"fallback" : "true"                       —> fallback to
default subset with key "fallback" and value "true"
},
"subset_selectors": [
{
"keys": [
"url"                —> the subsets will be formed
based on the  ":path" value extracted in http_filter
]
}
]
}
}
]
}
Thanks
Sahana
On Thu, Jun 21, 2018 at 2:19 AM, Raúl Gutiérrez Segalés <
<EMAIL_ADDRESS>wrote:

@sahanaha https://github.com/sahanaha fyi, here are the draft docs for
the header-to-metadata filter (#3633
https://github.com/envoyproxy/envoy/pull/3633), lmk what you think.
thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/2436#issuecomment-398891850,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmIodb06QqlFYJgJ9Lov5kIK1Ia78lH6ks5t-rVrgaJpZM4RqYif
.

@sahanaha yeah, that should work. LMK if otherwise.

Hi,
Hope I can ask one more question...
I have a scenario where same IP address is part of multiple subsets based on metadata match criteria..
EDS response:
"lb_endpoints": [
{
"endpoint": {
"address": {
"socket_address": {
"address": "<IP_ADDRESS>",
"port_value": 16503
}
}
},
"metadata": {
"filter_metadata": {
"envoy.lb" : {
"url" : "/v3/Mllib-try1"
}
}
}
},
{
"endpoint": {
"address": {
"socket_address": {
"address": "<IP_ADDRESS>",
"port_value": 16503
}
}
},
"metadata": {
"filter_metadata": {
"envoy.lb" : {
"url" : "/v3/Mllib-try1"
}
}
}
},
{
"endpoint": {
"address": {
"socket_address": {
"address": "<IP_ADDRESS>",               --> IP address is same as url: "/v3/Mllib-try1"
"port_value": 16503
}
}
},
"metadata": {
"filter_metadata": {
"envoy.lb" : {
"url" : "/v3/Mllib-try2"
}
}
}
},
{
"endpoint": {
"address": {
"socket_address": {
"address": "<IP_ADDRESS>",         IP address is same as url "/v3/Mllib-try1"
"port_value": 16503
}
}
},
"metadata": {
"filter_metadata": {
"envoy.lb" : {
"url" : "/v3/Mllib-try2"
}
}
}
},
I was hoping to see 2 subset creation, one for "/v3/Mllib-try1" and another for "/v3/Mllib-try2". However in the envoy trace I see that only subset was created for url= "/v3/Mllib-try1" and then second one was eliminated (probably because it has the same IP as the first one)
As per the below document same host can be part of multiple subsets (e7 host is part of 3 subsets)
https://github.com/envoyproxy/envoy/blob/master/source/docs/subset_load_balancer.md
Is there any way that we can still create subsets when the IP address is duplicated ?

@sahanaha I think you'll need two recent PRs:
https://github.com/envoyproxy/envoy/pull/3814 (merged)
https://github.com/envoyproxy/envoy/pull/3840 (waiting for review)

@sahanaha you've got the same IP and port... that won't work, since they are both the same endpoint. Or did you just forget to update the port in your example?

@rgs1
In my scenario I do end up getting same IP and Port in multiple subsets. Is
there any workaround solution for this problem ?
On Tue, Jul 17, 2018 at 7:06 AM, Raúl Gutiérrez Segalés <
<EMAIL_ADDRESS>wrote:

@sahanaha https://github.com/sahanaha you've got the same IP and
port... that won't work, since they are both the same endpoint. Or did you
just forget to update the port in your example?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/2436#issuecomment-405431332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmIodbOs3BzfXfy7IU0fzfjmOIAf8xOsks5uHT-QgaJpZM4RqYif
.

@sahanaha so an endpoint (ip+port) can be in multiple subsets, but the endpoint should only appear ones in EDS (with all the corresponding metadata that would cause it to be in multiple subsets) — does that make sense?

@rgs1
Yes, it makes sense, Thanks!.
Let me see how I can fit my requirement into this.

Hi,
I still have some issues fitting our requirement in the V2 envoy. Let me just start with a background of our requirement…

Lets assume I have 3 endpoints in a cluster (ip:port) and multiple URLs (you can assume URLs as some data/file which resides inside the mentioned ip:port) assigned to each endpoint.
The number of URLs assigned to each endpoint grows during runtime and the same URL can be part of multiple endpoints (we duplicate it in multiple endpoints as a backup)
As shown in the diagram Endpoint 1 contains URL1, URL2 and URL2 is also part of Endpoint 2.
When users sends request to ENVOY, we will be having URL1 or URL2 ….. URLn as part of the http request. We fetch this information via dynamic metadata matching and then route the request to corresponding Endpoint which contains the respective URL number.
The issue here is.. the number of URLs grows during runtime and is not fixed, hence we can not configure the exact metadata key names in subset_selectors.
We could think of 2 possible ways of solving this..

create each metadata key for every URL in the EDS response. for example …

Endpoint 1 {
ip: "<IP_ADDRESS>"
port: 1600
}
metadata {
"key1" : "URL 1",
"key2" : "URL 2"      —> URLs can grow more than 10,000 and with that our metadata key count.
}
similarly …
Endpoint 2 {
ip: "<IP_ADDRESS>"
port: 1600
}
metadata {
"key2" : "URL 2",
"key3" : "URL 3"
}
However in this approach we don’t know how many number of keys gets generated during runtime. This could be in 10,000. It will be a huge number to statically configure in the envoy config subset_selector. Also we might have to put a threshold on number of keys will can grow but we will be loosing the other URLs which crosses beyond this threshold.

Second approach is to create one cluster for each URL, example if I have URL1, URL2, URL3 ……. URLn, we will be construction that many clusters each having the corresponding endpoint.

In this approach we can solve the issue of having a duplicate IP:port (as the ip:port can be same in multiple clusters) however the main disadvantage is that the cluster number grows with respect to number of URLs… ie if number of URLs are 10,000 we will end up creating 10,000 cluster entries.
Do you have any suggestions to overcome this situation ? What is the best approach which we can take in V2 envoy to fit our requirement ? Any help on this will be greatly appreciated .

Hi Team,
Is there any update on my requirement question which I posted above ?

in multi-tenant scene, instances of a service may have different label, we could config roure configuration for every instance to match header, however the config is troublesome because the tenat is  too much and the match is linear not a LB rule, and we should update the config in ever instance's life-cycle. so if exist a way to config it easy?

Belatedly closing this because I think the header-to-metadata filter fulfilled the origin feature request.


Update AnimeDatabase.swift

Added "Bleach" 👍

You opened the PR in your own fork, you should open it here 😄


Trådfri: service light.turn_on doesn't work with maximum brightness

Home Assistant release (hass --version):
0.57.1
Python release (python3 --version):
Python 3.6.0
Component/platform:
tradfri
Description of problem:
Service light.turn_on doesn't turn Trådfri light bulb on if the brightness is set to 255.
Looks like a regression as it worked on 0.56.
Expected:
Light bulb is turned on with maximum brightness
Problem-relevant configuration.yaml entries and steps to reproduce:
Nothing special in configuration.
Steps to reproduce:

Open Services in web front-end
Choose light.turn_on
Service data:

{
"entity_id": "light.tradfri_bulb_e27_ws_opal_980lm",
"brightness": 255
}

Press Call service
Nothing happens.

Works fine with "brightness": 254

Proposed solution here:
https://github.com/home-assistant/home-assistant/pull/10359


[Linux] IJulia install error

Hey there,
I've just installed julia from the official binaries for Linux and wanted to add the IJulia kernel to jupyter. When following the installation instructions from here, the installation fails.
Reproduction Steps:
Start julia:
julia
Install IJulia:
using Pkg; Pkg.add("IJulia")
Resulting Output:
   Cloning default registries into `~/.julia`
   Cloning registry from "https://github.com/JuliaRegistries/General.git"
ERROR: Git repository not found at 'https://github.com/JuliaRegistries/General.git'
Stacktrace:
 [1] pkgerror(::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:113
 [2] #clone#4(::String, ::Base.Iterators.Pairs{Symbol,LibGit2.CachedCredentials,Tuple{Symbol},NamedTuple{(:credentials,),Tuple{LibGit2.CachedCredentials}}}, ::typeof(Pkg.GitTools.clone), ::String, ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/GitTools.jl:129
 [3] #clone at ./none:0 [inlined]
 [4] (::Pkg.Types.var"#124#126"{Pkg.Types.RegistrySpec,String})(::LibGit2.CachedCredentials) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1029
 [5] shred!(::Pkg.Types.var"#124#126"{Pkg.Types.RegistrySpec,String}, ::LibGit2.CachedCredentials) at ./secretbuffer.jl:184
 [6] clone_or_cp_registries(::Pkg.Types.Context, ::Array{Pkg.Types.RegistrySpec,1}, ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1028
 [7] clone_or_cp_registries at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1013 [inlined] (repeats 2 times)
 [8] clone_default_registries() at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:963
 [9] find_registered!(::Pkg.Types.EnvCache, ::Array{String,1}, ::Array{Base.UUID,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1244
 [10] registry_resolve!(::Pkg.Types.EnvCache, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:880
 [11] #add#25(::Bool, ::Pkg.BinaryPlatforms.Linux, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.add), ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:95
 [12] add(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:72
 [13] #add#24 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:69 [inlined]
 [14] add at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:69 [inlined]
 [15] #add#21 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:67 [inlined]
 [16] add at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:67 [inlined]
 [17] #add#20(::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.add), ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:66
 [18] add(::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:66
 [19] top-level scope at REPL[1]:1
caused by [exception 1]
GitError(Code:EINVALIDSPEC, Class:Net, malformed URL 'http://proxy.host:port')
Stacktrace:
 [1] macro expansion at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/LibGit2/src/error.jl:101 [inlined]
 [2] clone(::String, ::String, ::LibGit2.CloneOptions) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/LibGit2/src/repository.jl:459
 [3] #clone#131(::String, ::Bool, ::Ptr{Nothing}, ::LibGit2.CachedCredentials, ::Dict{Symbol,Tuple{Ptr{Nothing},Any}}, ::typeof(LibGit2.clone), ::String, ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/LibGit2/src/LibGit2.jl:580
 [4] #clone at ./none:0 [inlined]
 [5] #clone#4(::String, ::Base.Iterators.Pairs{Symbol,LibGit2.CachedCredentials,Tuple{Symbol},NamedTuple{(:credentials,),Tuple{LibGit2.CachedCredentials}}}, ::typeof(Pkg.GitTools.clone), ::String, ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/GitTools.jl:123
 [6] #clone at ./none:0 [inlined]
 [7] (::Pkg.Types.var"#124#126"{Pkg.Types.RegistrySpec,String})(::LibGit2.CachedCredentials) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1029
 [8] shred!(::Pkg.Types.var"#124#126"{Pkg.Types.RegistrySpec,String}, ::LibGit2.CachedCredentials) at ./secretbuffer.jl:184
 [9] clone_or_cp_registries(::Pkg.Types.Context, ::Array{Pkg.Types.RegistrySpec,1}, ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1028
 [10] clone_or_cp_registries at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1013 [inlined] (repeats 2 times)
 [11] clone_default_registries() at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:963
 [12] find_registered!(::Pkg.Types.EnvCache, ::Array{String,1}, ::Array{Base.UUID,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1244
 [13] registry_resolve!(::Pkg.Types.EnvCache, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:880
 [14] #add#25(::Bool, ::Pkg.BinaryPlatforms.Linux, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.add), ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:95
 [15] add(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:72
 [16] #add#24 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:69 [inlined]
 [17] add at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:69 [inlined]
 [18] #add#21 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:67 [inlined]
 [19] add at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:67 [inlined]
 [20] #add#20(::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.add), ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:66
 [21] add(::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:66
 [22] top-level scope at REPL[1]:1

System Specifications:
Julia: Version 1.3.1 (2019-12-30)
Sytem: Linux 5.5.9-arch1-2
If something is missing please do tell. Thanks in advance!

Your output includes this:
GitError(Code:EINVALIDSPEC, Class:Net, malformed URL 'http://proxy.host:port')

This implies that you have a misconfigured proxy server. Check your ~/.gitconfig file to see if it specifies a proxy, or if you have an http_proxy environment variable set.

This was indeed the issue. Thanks alot!


[AIRFLOW-6504] K8sExec: Allow specifying configmap for Airflow Local Setting

Currently airflow.cfg file can be passed via ConfigMap using airflow_configmap under [kubernetes] section setting.
We want to be able to specify airflow_local_settings.py via configmap too so that the Kubernetes Worker has this file. We need airflow_local_settings.py to specify pod_mutation_hook.
Without that currently, if we are using KubernetesExecutor and have a task with KubernetesPodOperator, it will inherit and change Pod using pod_mutation_hook
Astronomer specific use-case: We need this to move pods launched via K8sExec and K8sPodOperator to dynamic-node-pool

Issue link: https://issues.apache.org/jira/browse/AIRFLOW-6504

[x] Description above provides context of the change
[x] Commit message/PR title starts with [AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID*
[x] Unit tests coverage for changes (not needed for documentation changes)
[x] Commits follow "How to write a good git commit message"
[x] Relevant documentation is updated including usage instructions.
[x] I will engage committers as explained in Contribution Workflow Example.

* For document-only changes commit message can start with [AIRFLOW-XXXX].

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

Created PR on airflow repo at https://github.com/apache/airflow/pull/7097


Retrieve company information

Feature: Implement CRUD for the company
Branch-name: retrieve-company-information
By: Rubina Thapa
Date: 2024-04-07
Time: 12:04 PM
Epic: Company
Task:  Retrieve a company's details by its ID,
Description:  It retrieves a company's details by its ID, returning a ResponseEntity containing a CompanyResponseDto using a controller method annotated with @GetMapping.


[Log In] Styles refactoring

Environment: Windows 10 Pro 22H2 Google Chrome Version 122.0.6261.112 (Official Build) (64-bit)
Reproducible: always
Preconditions

Site https://zero-waste-staging.onrender.com/uk is opened

Steps to reproduce

Go to 'Log In' tab

Actual result

Heading has small size
Placeholder is missed in the textfields
'Sign Up' link is present
Space is different in regards 'Увійти/Log In' button

Expected result

Heading should have size h1
Placeholder should be added into the textfields
'Sign Up' link should be removed from the page
Space should be similar in regards 'Увійти/Log In' button

User story and test case links
"User story #838
Test case"

The issue creation has been agreed with technical expert

Done