Page based reminders

Hi, nice plugin.
I had a feature request - for the reminders dialog to be opened when a certain page was opened. These could be specified in the same format as the date reminders i.e. (@[[Page linked to reminder]]). This could be in addition to a reminder being linked to a date or time.

Could you tell me how use page-based reminder feature?
I have no idea to use the feature.

So you know the way reminders are linked to dates? They pop up when the date/time has come. In a similar way, this would open when you open a certain page.
Example use case - you have a page on walking dogs, which you look at before you walk the dog. This time you remember, you have to go to the shop on the way too to get dog food. So you add a page-linked reminder in the format
- [ ] Buy dog food on next walk (@[[Dog walking]])

which will show the reminder when you next open the page Dog walking.
If I'm still not making sense, when I have time I will just open a pull req and show you what I mean.

Thank you for your explanation!
But I write the TODO item (dog food) to Dog walking page in that case.
How does it help more than plain TODO item?

I think there would be a few benefits:

You are more likely to see important information if it pops up otherwise if you are casually scrolling you will look over it
If you have a lot of information on that page, having the reminders pop up is more efficient than looking for them
You can put these todos anywhere e.g. you could write all your todos in your daily note but also link them to pages
You might have a lot of todos e.g. for a project but a few things you need to urgently do - this is easier than dividing the tasks up with a header, then making it stand out etc. the urgent todos could otherwise get lost in the rest

And you could turn it on and off which would make it a choice if people didn't want to be annoyed if they needed to look through stuff quickly but would be useful when working through things so you do not forget and it is comprehensive.

Thanks for providing the benefits.  And sorry for the late reply.
I've been using this plugin for a long time, but I still didn't think I needed this feature.
I don't want to implement this feature to keep the implementation of this plugin simple.
If there are many others with the same request, I will consider support again.

This might actually be a nice feature, just for customizability. >.<


ArrayMap, make put return the inserted index

A bit of a low hanging fruit but I can't PR it. If you're using ArrayMap as a backing mechanism in an Adapter it saves time for very very hurrdurr cases where you want to notify where an element was inserted or updated and pass it around to the observer.
ArrayMap.java L~84:
public int put (K key, V value) {
    if (size == keys.length) resize(Math.max(8, (int)(size * 1.75f)));
    int index = indexOfKey(key);
    if (index == -1) index = size++;
    keys[index] = key;
    values[index] = value;
    return index;
}

Thank you, Nathan.


Get temperature or / and air pressure from raspberry

/pi temp for temperature;
/pi pressure for air pressure;
/pi env for both;

Wait until my pitons project finished it's first API.


dream_web.py gone from the code?

I just did a 'git pull' and the python scripts\dream_web.py no longer works as described in the instructions. I tried dream.py --web and it does load a page, but the CSS and JS aren't found. Is there something wonky going on with my setup or is there a new method I need to use for the GUI?

Nice catch on the instructions being stale; I'll submit a PR updating those.
Re: "the CSS and JS aren't found", that's probably this issue; you could try the fix in that PR.

Thanks @bakkot - Adding the .lower() to the code fixed the paths.

@arothmanmusic would you be up for trying out this change instead? I like that fix better but I'm not in a position to test if it works, and it sounds like you are.

@bakkot I've swapped that line and restarted the server. Seems to work just as well that way as it did the other!

Should be fixed on main between https://github.com/lstein/stable-diffusion/pull/198 and https://github.com/lstein/stable-diffusion/pull/192. Thanks for the report.


Astrocraft and Citadel do not startup together

Mod Name
Astrocraft
Mod Homepage
https://modrinth.com/mod/astrocraft
Minecraft version
1.20.1
Describe the bug
when installing citadel with astrocraft, the game crashes when initializing game.
Steps to reproduce

add astrocraft for fabric in the mods folder
add citadel for forge in the mods folder
start the game
...

Logs
https://gist.github.com/vinnyg0621/735e5d3188c9b396314519330a7ada8a
Additional context
i have alex's mobs and caves in my mods folder too, which that mod is required for

Caused by: org.spongepowered.asm.mixin.injection.throwables.InjectionError: Critical injection failure: Redirector modifyTwilightColor(Lnet/minecraft/client/multiplayer/ClientLevel;F)F in astrocraft.mixins.json:MixinWorldRenderer from mod astrocraft failed injection check, (0/1) succeeded. Scanned 1 target(s). Using refmap astrocraft-refmap.json

This is a redirect conflict between the two mods, and is outside our control. I suggest asking the mod's devs if it's possible to use a chainable injector instead, such as ModifyExpressionValue or WrapOperation.


New version: HandBrake.HandBrake version 1.9.0

Created by 🥟 Dumplings in workflow run #9960.

Log
Updated: 1.8.2 → 1.9.0
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

current version 1.9.0 is incorrect see: https://github.com/microsoft/winget-pkgs/blob/master/manifests/h/HandBrake/HandBrake/1.9.0/HandBrake.HandBrake.installer.yaml#L15C17-L15C74
so this PR would help fix it.
@stephengillie

Hi @spectopo and @lm-gh,
Changes made by this PR would overwrite those made in https://github.com/microsoft/winget-pkgs/pull/195526. So for this PR to proceed, it must be modified to include changes already merged in that PR.


GH-35916 [Java][arrow-jdbc] Add extra fields to JdbcFieldInfo

Rationale for this change
Existing info is not enough to make completely accurate conversion decisions.
What changes are included in this PR?
Include the type name reported by the database and the max number of characters as part of the JdbcFieldInfo.

Closes: #35916

I tried to find all common fields across ResultSetMetaData and getColumns. These were the only 2 missing.

I think you do need more fields, though. For example: in Postgres, you need it to figure out the timestamp precision (https://github.com/apache/arrow-adbc/blob/main/java/driver/jdbc/src/main/java/org/apache/arrow/adbc/driver/jdbc/adapter/JdbcToArrowTypeConverters.java). Or to figure out the precision/scale for NUMERIC/decimal.

Both of those are already part of JdbcFieldInfo.
The remaining pieces of info seem to be harder to get in a standardized way.
For example, there's a bunch of extra columns from the getColumns ResultSet that don't have a respective ResultSetMetaData method call.
There's also a few ResultSetMetaData method calls that don't have a respective column in a getColumns row, but instead would be found as columns in a getTypeInfo.


[Feature] Support W8A16 Int8 inside FusedMoE

Checklist

[x] 1. If the issue you raised is not a feature but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[x] 2. Please use English, otherwise it will be closed.

Motivation
vllm now supports W8A16 Int8 inside FusedMoE. see #7415
So, after vllm new version released. sglang will support too?
Related resources
No response

In the short term, yes. In the long term, we will maintain it ourselves.


Update storage-ref-azcopy-copy.md

This appears to be changed, in the cli --preserve-s2s-access-tier

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

@EasyAsABC123 Thanks for bringing this to our attention. @zezha-msft can you pls confirm the API change? If this has been changed, it would deviate from the name pattern given to the other S2 switches.

No the flag did not change. It's --s2s-preserve-access-tier.

Thank you @zezha-msft. @EasyAsABC123 can you pls tell us where you are seeing this flag appear as "preserve-s2s-access-tier"? The current version of AzCopy should be showing the flag as "s2s-preserve-access-tier".

#please-close


feat: Check NetworkManager gameobject for NI and NBs

This hopefully makes it apparent to newcomers that wonder why NetworkManager isn't working correctly that they can't put NetworkIdentities on NetworkManager objects. Same thing applies for NetworkBehaviours on NetworkManager objects.
This idea started out by MrGadget or James in the Discord mentioning about the fact people were stacking NetworkBehaviours on the Network Manager game object and complaining why it wasn't working, which is a really bad practice. We should instead detect this, alert the user with an error so they don't come into the Discord really upset and/or lashing out at us because they put all their network logic on the same game object as Network Manager, instead of others. I also added in a check to ensure if you have two network managers that it alerts you preemptively to avoid the shock of the "duplicate network manager, will be destroyed" warning.
I originally wanted to try to block the Scene from playback mode so it's a show-stopper error, but it seems Exceptions thrown in either OnValidate or PostProcessScene are not major show-stoppers.
Tested and working. As for maintainability, it copy-pasted a chunk from the function below it, so it'll be pretty easy to update. Yeah yeah, the code contained inside PR will survive the next 10 years.

@SoftwareGuy good idea if it helps people.
but why so complicated? a simple GetComponent check in Awake would make this in two lines of code :)

Hm, to be honest I haven't tried that - I'll take a look and see if that'll work as I envision it to work. I'm not 100% sure if Awake will fire, because the problem is that the NetworkIdentity nerfs the GameObject before NetworkManager even gets a chance to initialize AFAIK. So that's why I did it in PostSceneProcess; it's known to fire rather than Russian roulette.

Going to check that this weekend, will let you know how it goes. It may be OK to switch to Awake, but I am wondering if that'll fire before NetworkIdentity wakes up and disables the object.
Hold fire for now - definitely will check Awake and if that works with testing, I'll move it around.

@SoftwareGuy please reopen with the Awake check later :)


example:forms, can't create or delete anything!

@jrc-github Any detail information?
A bug report with no detail information has no sense and is not useful for the maintainer team to look into and fix it.

sorry,  i made a mistake.   I changed db session's control flow of flask_admin, but i forgot this.


Fix node labels at Python 3

Fixes the apply of custom labels on cluster nodes if Python 3 is used (#2843).
https://github.com/kubernetes-incubator/kubespray/issues/2843#issuecomment-395572952

@ant31 we signed cla.

/check-cla

Looks like the commit have been made with a different account/email address.

@avatarlab Please fix your commit email address.

/check-cla

/lifecycle stale

Fixed in PR#3415
/close


Cannot install Pecl http extension

Describe the bug

Cannot install pecl http extension 3.2.4 (http://pecl.php.net/package/pecl_http)
Version

[ ] I have checked releases, and the bug exists in the latest patch version of v1 or v2.
[X] v2
[ ] v1

Runners

[X] GitHub Hosted
[ ] Self Hosted

Operating systems

Ubuntu 18.04
PHP versions

PHP 7.4.13
To Reproduce

Workflow is available online at https://github.com/llaville/php-compatinfo-db/blob/master/.github/workflows/php-tests.yaml
Expected behavior

Extension http and its dependencies raphf and propro installed
Screenshots/Logs

Logs available at https://github.com/llaville/php-compatinfo-db/runs/1713249088#step:3:65

Additional context

I'm be able to install http pecl extension 3.2.4 on my docker environment, Ubuntu 18.04, PHP 7.4.14 with all its dependencies (raphf 2.0.1, propro 2.1.0, and librairies as explained at https://mdref.m6w6.name/http), in my project : see comment at https://github.com/llaville/php-compatinfo-db/issues/63#issuecomment-761535682
I've also tried to install it locally with act 0.2.17 without success: see comment at https://github.com/llaville/php-compatinfo-db/issues/63#issuecomment-760091985
Are you willing to submit a PR?

No skill to do it, sorry !

To install from packages.
specify extensions in this order raphf, propro, http
    strategy:
      fail-fast: false
      matrix:
        php: ['7.4', '8.0']
    steps:
      - name: Setup PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: ${{ matrix.php }}
          extensions: raphf, propro, http

Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/489948004/workflow
To install using PECL:
Install libcurl4-openssl-dev -y before running setup-php and suffix pecl_http with appropriate versions of PHP 7.4 and PHP 8.0.
    strategy:
      fail-fast: false
      matrix:
        include:
          - php: '7.4'
            extensions: 'pecl_http-3.2.4'
          - php: '8.0'
            extensions: 'pecl_http-4.0.0'
    steps:
      - run: sudo apt-fast install libcurl4-openssl-dev -y
      - name: Setup PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: ${{ matrix.php }}
          extensions: ${{ matrix.extensions }}

Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/489958829/workflow

To install from packages.
specify extensions in this order raphf, propro, http
    strategy:
      fail-fast: false
      matrix:
        php: ['7.4', '8.0']
    steps:
      - name: Setup PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: ${{ matrix.php }}
          extensions: raphf, propro, http

Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/489948004/workflow
To install using PECL:
Install libcurl4-openssl-dev -y before running setup-php and suffix pecl_http with appropriate versions of PHP 7.4 and PHP 8.0.
    strategy:
      fail-fast: false
      matrix:
        include:
          - php: '7.4'
            extensions: 'pecl_http-3.2.4'
          - php: '8.0'
            extensions: 'pecl_http-4.0.0'
    steps:
      - run: sudo apt-fast install libcurl4-openssl-dev -y
      - name: Setup PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: ${{ matrix.php }}
          extensions: ${{ matrix.extensions }}

Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/489958829/workflow


Getting /records at a particular entry

Its not clear to me from the spec, is/will there be a way to get /records tied to a specific entry?
The use case would be a client wanting to use the data at a given snapshot and not have the data change when a new entry is added.

@pmackay there is only one /record for an entry; the one identified by the given primary key of the entry.  For example, the /record for the country register entry
{"country": "GM"; "name": "Gambia, The"}

is /record/GM.
This follows from the definition of a record.

Sure, but how to get all records via /records endpoint at a specific point in the entry list?

I'm not sure I understand the question.
Do you mean "how do I get a list of all records as it was at a particular point in time, identified by number of entries in the register?" That's not something we currently support; if you wanted it you'd have to download the register and make your own index.
If I have understood you correctly, and if there is interest in this functionality, I'd be interested in hearing use-cases. Can you give examples of where you might use it?
(ping @michaelabroschomb)

how do I get a list of all records as it was at a particular point in time, identified by number of entries in the register?

Yes. Another way of looking at it is similar to the way one can reference a particular commit/release/tag of a project on Github with a URL. Currently the /records endpoint seems to be the git equivalent of HEAD.
To make up a contrived example, say the register of food-premises-types was going to be used directly by a council in a form for requesting a food premises license. At some point, a new entry might be added to handle food delivery by drone (insert own futuristic example here). Councils however might not want to immediately have their form include this new type without doing an internal review about their policy for drone delivery. But they do like to call the register API directly rather than downloading data cos its easier for their webforms. So having an endpoint that returns a snapshot rather than always the latest would be helpful.

What is the use-case for this scenario?

@psd I had hoped the above comment suggested one. Here's another couple of ideas:
Councils might want to use a register of commonly used waste containers or bulky items they will collect. If they want to:

build web forms that dynamically query the register directly (rather than having to download and separately store a copy)
control the list such that if the register changes, their lists dont automatically change, because they want to verify the change first

is that a use case you would consider valid and worth supporting?

Ah, that's clearer. I think you're asking for versioning of enumerated types.
Hiding changes made to register data is something we do not support in the register, they're definitely the concern of the client.
I'm in the process of expanding the versioning and extensibility section to explain this and some of the other evolutions which register data and the register API may make and which clients must be resilliant to.


feat: adjust principal recipients in location page

:tada: This PR is included in version 1.1.0-develop.27 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Determine desired and correct "service" discovery mode behavior

The hostname scheme used for the service gateway discovery mode appears incorrect. The Service DNS specification uses a single hostname that points to the Service IP, or Pod IPs in headless mode. KIC 3.0 uses multiple hostnames, prepending a Pod IP subdomain to the Service hostname.
While the Pod hostname spec does use IP subdomains, the Service spec does not.
The original goal of this feature was to support TLS, with the (mostly correct) expectation that users would not have certificates with Pod IP SANs available. We should clarify which hostnames we expect in practice and why. While we can reliably expect that the short Service name (without the .cluster.local or whatever cluster domain suffix) will resolve, users with certificate issuance systems will possibly use arbitrary hostnames.
The currently working mode (pod) expects proxy instances to present a certificate matching the Pod hostname. Because each replica must mount the same certificate, it likely requires a wildcard SAN to match any IP subdomain. This is not ideal: Pod hostnames use a <IP>.<Namespace>.pod.cluster.local format, so a valid certificate for any proxy Pod would also be valid for any other Pod in the same namespace.
Presenting a certificate valid for the full Service hostname (no wildcard) is not overly broad, but does not really fit with the current discovery implementation. There are no Service-based hostnames that point to a specific endpoint only, so there's no way we can construct a list of hostnames that covers every replica. We would likely need to build the list of IPs to contact (as in the ip strategy), loop over those, and dynamically build a client with local DNS overrides for each, so that we can remap <service>.<namespace>.svc.cluster.local hostnames to a each endpoint IP in order. This also satisfies the arbitrary hostname case.
Rough acceptance:

[ ] The service discovery mode uses the hostname format from https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-aaaa-records when connecting to Pods.
[ ] Users can provide their own hostname for admin service TLS validation.
[ ] The controller can still update every Pod in DB-less mode, even when given only a single hostname.
[ ] (Optional, recommended) We can properly test discovery in integration testing, overcoming the hurdle of not running in the cluster but wanting to use cluster-internal IPs. Suggested, though unexplored options for bridging that gap include Inlets, kt-connect, and Telepresence.

Dunno really how best to phrase those, but whatever.

FWIW, I initially wrote this as a response to https://github.com/Kong/kubernetes-ingress-controller/issues/3934 before determining it needed a new issue. The original writeup had some examples that are omitted above.

pod does resolve fine on GKE with kube-dns:
$ kubectl version
Client Version: v1.28.4
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.24.15-gke.1700

$ kubectl get po -owide
NAME                                   READY   STATUS    RESTARTS   AGE     IP           NODE                                                  NOMINATED NODE   READINESS GATES
ana-kong-6ccbdcb7cc-6dxhp              1/1     Running   0          5m59s   <IP_ADDRESS>   gke-traines-test-2023-12-default-pool-cb07533f-cxw4   <none>           <none>
ana-kong-controller-655794c769-g5rc7   1/1     Running   0          5m58s   <IP_ADDRESS>   gke-traines-test-2023-12-default-pool-cb07533f-cxw4   <none>           <none>

$ kubectl get po -oyaml | grep -A1 DNS_STRATEGY
      - name: CONTROLLER_GATEWAY_DISCOVERY_DNS_STRATEGY
        value: pod

2023-12-01T22:15:07Z	info	setup	Retrying kong admin api client call after error	{"v": 0, "retries": "2/60", "error": "making HTTP request: Get \"https://10-104-0-6.default.pod:8444/\": dial tcp <IP_ADDRESS>:8444: connect: connection refused"}
2023-12-01T22:15:11Z	info	Successfully synced configuration to Kong	{"url": "https://10-104-0-6.default.pod:8444", "update_strategy": "InMemory", "v": 0}

Though not shown, adding actual configuration, scaling/restarting, and non-default namespaces all worked fine.
The service strategy does not work:
2023-12-01T22:31:06Z	info	setup	Retrying kong admin api client call after error	{"v": 0, "retries": "24/60", "error": "making HTTP request: Get \"https://10-104-2-7.ana-kong-admin.other.svc:8444/\": dial tcp: lookup 10-104-2-7.ana-kong-admin.other.svc on <IP_ADDRESS>:53: no such host"}

This address format looks unusual, however. While the Pod DNS spec does indicate that it includes the IP prefix, the Service DNS spec does not, and instead says that you should only see a single NAME.NAMESPACE.svc.cluster.local A record, which returns the ClusterIP if available or the Pod IPs if not (if headless). GKE DNS does return those:
root@cool:/# dig kana-kong-admin.default.svc.cluster.local +short
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

The format with IP subdomains is of unclear origin. Is it something extra CoreDNS provides? This format is still in use, but I'm no longer sure where it should work. Although we mentioned CoreDNS, service does not work with CoreDNS (on KIND) either, so this address format does not appear to be something extra it offers out of the box.

Review of the tunneling options
General notes

The integration test suite hardcodes the use of discovery or not discovery. We may want to make this switchable, though it's at the cost of yet another integration run if we do use it.
KTF apparently hardcodes the use of an HTTP admin API. It should not do this.

https://github.com/Kong/kubernetes-ingress-controller/pull/5295 has a mostly working PoC. Something weird is broken with Postgres and it hacks away the problems above.
Inlets
The OSS options and their feature set isn't quite clear. It seems that the server and management app have MIT licensed options, but the client has only paid options? Also not clear if it offers a simple network device and route manipulation option for transparent L3 routing, which is what we want. Docs suggest it requires a TCP proxy with a listen on the client host, so you would have to connect to that instead of Pod IPs.
kt-connect
Very not product-ized and likely to remain that way given Alibaba Cloud's market. However, it is GPLv3. This shouldn't matter as it's being used to manipulate the environment and would not ever be imported into Go packages, but that may still create an extra wrinkle.
Somewhat hampered by basically all issue discussion being in Chinese.
Telepresence
Somewhat product-ized. The original feature set (what we need) was available via a standalone application, but Ambassador have recently made the readily available binaries require an account regardless of whether you'd need one to push paid features.
No-account installs
The binaries from the GitHub releases page do not have this limitation, but are not distributed via package managers (namely Homebrew) or Actions (they're hardcoded to the nag version).
The actions fortunately aren't necessary (simply downloading the binary and running telepresence helm install and telepresence connect works fine), but local dev is kinda limited. I thought go install would work, but
go install<EMAIL_ADDRESS>go<EMAIL_ADDRESS>(in github.com/telepresenceio/telepresence/v2@v2.17.0):
	The go.mod file for the module providing named packages contains one or
	more replace directives. It must not contain directives that would cause
	it to be interpreted differently than if it were the main module.

and I can't see what else I should install instead, if anything is available. I suppose we could detect OS and pull binaries from the release page somehow via the Makefile.
KTF chicken egg problems
Telepresence cannot install its egress point without a running cluster. The integration test harness generally wants to create its own cluster from scratch and start running tests immediately. We can use kind-action or similar to set one up in advance (and subsequent addons, such as metallb, are generally fine with this), but it may miss some settings.
A somewhat comedic option is to integrate Telepresence into KTF. There is, AFAIK, no reason we can't make an addon wrapper to function as a pseudo-CLI replacement, which would allow it to run as part of a KTF environment create and solve the distribution problem (no Go install? no problem!) in one go.

Another KIND user mentioned https://sshuttle.readthedocs.io/en/stable/usage.html#usage as an option. It looks like it satisfies the client-side criteria (just exposes IP ranges).

go install<EMAIL_ADDRESS>go<EMAIL_ADDRESS>(in github.com/telepresenceio/telepresence/v2@v2.17.0):
	The go.mod file for the module providing named packages contains one or
	more replace directives. It must not contain directives that would cause
	it to be interpreted differently than if it were the main module.

and I can't see what else I should install instead, if anything is available. I suppose we could detect OS and pull binaries from the release page somehow via the Makefile.

You won't be able to use go install with a module that uses a replace. That's basically what the error says.

As for the service matter: the origin of those addresses is from the linked article https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-aaaa-records-1

Any Pods exposed by a Service have the following DNS resolution available:
pod-ip-address.service-name.my-namespace.svc.cluster-domain.example

Which is known to not work on GKE's kube-dns. Some more findings on this one: https://github.com/Kong/kubernetes-ingress-controller/issues/4065#issuecomment-1560958169

Have you considered mirrord? It's MIT license

Have you considered mirrord? It's MIT license

This tool as far as I remember when I used it last time is meant to wrap the running binary by starting mirrord with the wrapped binary as CLI param. When trying to run this on Mac I remember hitting some problems like seg faults but I don't have the logs from those tests unfortunately.
As a side effect this approach will also make debugging practically impossible ( at least I'm not aware of a method of making it work this way ).
BTW: I've just found an issue that I created a couple of months ago for integration tests using GD: https://github.com/Kong/kubernetes-ingress-controller/issues/3631


redis client with premium tier: must support clustering ?

Documentation is somewhat confusing here. It states "At the present time not all clients support Redis clustering", then "You can connect to your cache using the same endpoints, ports, and keys that you use when connecting to a cache that does not have clustering enabled. Redis manages the clustering on the backend so you don't have to manage it from your client". So it's not clear if you must use a client library that supports clustering or not (with the Premium tier).

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

ID: 71a6ea88-8013-21fa-2f71-ff7cb5e7afc7
Version Independent ID: c1ee6186-916a-4f0e-2179-f8366e4afb5c
Content: How to configure Redis clustering for a Premium Azure Redis Cache
Content Source: articles/redis-cache/cache-how-to-premium-clustering.md
Service: cache
Product: unspecified
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

@gunzip Thank you for your feedback! We have assigned this issue to the author to investigate further and take the right course of action.

We just want customers to connect to the main port and then the client will automatically download the cluster configuration along with other port numbers, if it supports clustering.  The Redis clustering protocol requires that each client connect to each shard directly in clustering mode. If the client doesn't support clustering, I'm pretty sure you will see a lot of MOVED redirection exceptions


Error: Cannot send value to non-payable function

I am attempting to deposit ETH to be converted into W-ETH.  When I am in the deposit section of Maker Market I am given the error:
Error: Cannot send value to non-payable function
I am using metamask on my mac and have more ETH available than what I am attempting to deposit.
Thanks in advance.

I'm having exactly the same issue...

Thanks for reporting, this should be a quick fix. I believe what's happening is that the ABI encoding for the Eth wrapper is not marked "payable" because it was built with an old compiler where functions were payable by default. But a recent web3.js version is now helpfully ensuring we don't send ETH to "non-payable" functions.

Awesome...thanks for the quick resolution.

I just logged back into maker market to test the resolution and I am still being given the same error.  It looks like the issue has not been resolved.  Please advised.
Thanks.

On Fri, Feb 10, 2017 at 1:12 PM Mariano Conti<EMAIL_ADDRESS>wrote:
Closed #175 https://github.com/makerdao/maker-market/issues/175 via
2c495c5
https://github.com/makerdao/maker-market/commit/2c495c5e6e0dc6e79a9fbb56abc975fca13dd2b7
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/makerdao/maker-market/issues/175#event-957791646, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYfPYNJblCcS78p7XYoeP78P-xgoT9qRks5rbLatgaJpZM4L89ne
.
I just logged in and the same error still is taking place.
Please advise.
Thank you.


Auto-deploy the project

Hi,
Can we auto-deploy the project after generating the code instead of downloading it? Does Jhipster have an auto-deployment feature?

I don't understand what you mean with 'auto deploy'.
How did you use JHipster Lite?

locally ?
https://lite.jhipster.tech ?

Where do you want to deploy ?

AWS ? GAE ? Azure ? Heroku ? Etc.

Hi,
I have deployed Jhipster on GCP VM.
Now whenever I create a new project with required patches or modules, I have to manually download the project and run it.
With Auto-deployment I meant, Is there any way I can directly deploy the project somewhere after applying the patches or modules instead of downloading it?

The "download" button is mainly here for the instance deployed here (we should probably remove that from the local instance...). When starting locally (./mvnw) you can set your project folder in the folder path to get all the already applied configuration to your project and directly update in on your local disk.
I don't really see a point in having a deploy button in the interface since JHlite goal is not to generate full applications, this is not a no-code platform. The goal here is to generate some infrastructure code when building a business application.
For me, updates should go though a normal CI / CD pipeline, that mean:

Create a branch;
Make the update;
Push it;
Review it;
Merge it and that will be deployed.

(You can do that without branches and push to trunk the that will be the same :))

Closing this one, following the last comment


Add option to generate all undefined as null or undefined.

We believe we have an issue when generating from Python to TypeScript.
For some reason, the API may return T | null but the type generated using openapi-typescript is T | undefined
Can we have an option to modify the output to allow both T | null | undefined?

Running in the same issue


Merge Testing into Feature

Before I finalize the changes to my rngSeed_inScenarioTable feature branch, I need to merge updates that other developers have done to the testing branch into my feature branch

For reasons I don't understand, the modifications I made, which are showing up when I look in my branch directly, are not showing up in the PR merge view at all.  Hence, the PR is simply just going to merge the updates to testing into my feature branch as if it is still the same as testing was when I created it.  Obviously I don't want to do that, so I'll close this PR and recreate it.


uv installed on 3.9 version, but make venv on 3.7 version

Input:
python3.9 -m uv venv venv

Output:
Using Python 3.7.17 interpreter at: /usr/bin/python3
Creating virtualenv at: venv
Activate with: source venv/bin/activate

I would recommend instead: uv venv --python python3.9.

We could hint to UV to use the correct version as we do for virtual environments, I would expect this command to work as well.
https://github.com/astral-sh/uv/blob/65518c9c585648267721a6effc090cb2f18e12dc/python/uv/__main__.py#L29-L31

Perhaps, take a look at https://github.com/astral-sh/uv/issues/2058 too.


First set of Functional tests for EF.Relational.Design

@divega @bricelam Would appreciate some feedback this approach to functional tests for RevEng.
Have tried to avoid Mocks (per Diego's comments) but found I needed to use them in one place (may be able to remove later by making the outputting of files into a service).
Tests are not by any means exhaustive. Will add more once the general approach is considered OK.
Note: changed the generator to receive the actual provider instance and leave the looking up of this provider in the assembly to the Commands code.

Part of https://github.com/aspnet/EntityFramework/issues/1669

These still feel like unit tests to me; TestDatabaseMetadataModelProvider feels like a mock. I think for functional tests, it would good to hit a database and/or compile code. The rest of the coverage can probably be done in unit tests. The two big functional scenarios I see are:

Create various database objects, verify SqlServerMetadataModelProvider outputs a correct model
Create various models, generate code, verify code, compile code, verify model

@bricelam @lajones have you guys talked about how to move forward with this?

@divega @bricelam Will do - wanted to do it F2F.

@lajones, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;


Release Google.Cloud.Location version 2.2.0

Changes in this release:
New features
This library now targets netstandard2.0 instead of netstandard2.1. This should be compatible with existing libraries that depend on it, but will allow new libraries to also target netstandard2.0.

Created release for Google.Cloud.Location-2.2.0


Taking entries out of sub-menus

Hello! I would like to take things like "Move to New Window" and "Close Tabs to the Left/Right" out of their sub-menus and into the main tab context menu. That doesn't seem to be possible, currently - if I disable the sub-menu by editing the tab-content.css file, the entire sub-menu disappears, including its contents, which isn't what I want to do.
Is what I want feasible? If yes, how could I do it? Perhaps you could also add support for it?

Unfortunately I cannot make structural changes with CSS. That would be possible with JavaScript, but is out of scope of this project. You'd first need a way to load UserChrome.js scripts. That was easy before Firefox 57 and is now harder to achieve.
There are different approaches. I know it works, but the source I have is written in german. I think this will help you:
https://github.com/Endor8/userChrome.js
Still you need to know how to code JavaScript.
CSS actually is for styling, but also can hide items and under certail circumstances can change the order of items that are on the same level.


update readme with the docs edits

@tylerl0706,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


TR not listen on 53 port

I'm submitting a ...

[x] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[x] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

After install TR not run any service on 53 ports and NS for CDN not available
Expected / new behavior:

bind DNS on 53
Minimal reproduction of the problem with instructions:

TR 4.0.x
Anything else:

Click for related logs output

INFO  2020-06-19T17:31:46.152 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json; timeout is 15000
WARN  2020-06-19T17:31:46.165 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http Request to https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json Status 401
INFO  2020-06-19T17:31:46.640 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:47.640 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:48.641 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:49.641 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:50.641 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:51.642 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:52.642 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:53.642 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:54.643 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:55.643 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:55.995 [localhost-startStop-1] com.comcast.cdn.traffic_control.traffic_router.core.util.PeriodicResourceUpdater - Waiting for valid: /opt/traffic_router/db/cr-config.json
WARN  2020-06-19T17:31:56.104 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:31:56.617 [pool-3-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.monitor.TrafficMonitorWatcher - Loading properties from /opt/traffic_router/conf/traffic_monitor.properties
WARN  2020-06-19T17:31:56.620 [AsyncHttpClient-Reaper] com.comcast.cdn.traffic_control.traffic_router.core.util.PeriodicResourceUpdater - Failed request http://tm.myawesomecdn.com:80/publish/CrConfig?json: java.net.ConnectException: https://tm.myawesomecdn.com:443/publish/CrConfig?json
java.net.ConnectException: https://tm.myawesomecdn.com:443/publish/CrConfig?json
	at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:104)
	at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427)
	at org.jboss.netty.channel.DefaultChannelFuture.notifyListeners(DefaultChannelFuture.java:418)
	at org.jboss.netty.channel.DefaultChannelFuture.setFailure(DefaultChannelFuture.java:380)
	at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$1.operationComplete(NioClientSocketPipelineSink.java:115)
	at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427)
	at org.jboss.netty.channel.DefaultChannelFuture.notifyListeners(DefaultChannelFuture.java:413)
	at org.jboss.netty.channel.DefaultChannelFuture.setSuccess(DefaultChannelFuture.java:362)
	at org.jboss.netty.channel.AbstractChannel$ChannelCloseFuture.setClosed(AbstractChannel.java:355)
	at org.jboss.netty.channel.AbstractChannel.setClosed(AbstractChannel.java:185)
	at org.jboss.netty.channel.socket.nio.AbstractNioChannel.setClosed(AbstractNioChannel.java:197)
	at org.jboss.netty.channel.socket.nio.NioSocketChannel.setClosed(NioSocketChannel.java:84)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.close(AbstractNioWorker.java:357)
	at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:58)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)
	at org.jboss.netty.handler.ssl.SslHandler.closeOutboundAndChannel(SslHandler.java:1426)
	at org.jboss.netty.handler.ssl.SslHandler.handleDownstream(SslHandler.java:590)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
	at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
	at org.jboss.netty.handler.codec.http.HttpClientCodec.handleDownstream(HttpClientCodec.java:97)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:109)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
	at org.jboss.netty.channel.Channels.close(Channels.java:812)
	at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:197)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.finishChannel(NettyAsyncHttpProvider.java:1116)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.closeChannel(NettyAsyncHttpProvider.java:1102)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.abort(NettyAsyncHttpProvider.java:1335)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.access$800(NettyAsyncHttpProvider.java:158)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.expire(NettyAsyncHttpProvider.java:1782)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$ReaperFuture.run(NettyAsyncHttpProvider.java:1803)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.channels.ClosedChannelException
	... 37 more
INFO  2020-06-19T17:31:56.643 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:57.644 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:58.644 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:31:59.644 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:00.645 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:01.645 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:02.645 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:03.645 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:04.646 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:05.646 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:32:06.104 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:32:06.646 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:07.646 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:08.647 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:09.647 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:10.647 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:11.648 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:12.648 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:13.648 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:14.648 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:15.649 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:32:16.105 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:32:16.166 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: https://ops.myawesomecdn.com/api/1.3/user/login; timeout is 15000
INFO  2020-06-19T17:32:16.223 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json; timeout is 15000
WARN  2020-06-19T17:32:16.236 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http Request to https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json Status 401
INFO  2020-06-19T17:32:16.649 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:17.649 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:18.649 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:19.650 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:20.650 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:21.650 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:22.651 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:23.651 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:24.651 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:25.651 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:32:26.105 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:32:26.652 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:27.652 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:28.652 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:29.653 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:30.653 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:31.653 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:32.653 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:33.654 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:34.654 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:35.654 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:32:36.105 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:32:36.655 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:37.655 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:38.655 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:39.656 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:40.656 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:41.656 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:42.657 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:43.657 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:44.657 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:45.657 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:32:46.106 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:32:46.237 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: https://ops.myawesomecdn.com/api/1.3/user/login; timeout is 15000
INFO  2020-06-19T17:32:46.291 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json; timeout is 15000
WARN  2020-06-19T17:32:46.304 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http Request to https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json Status 401
INFO  2020-06-19T17:32:46.658 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:47.658 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:48.658 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:49.659 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:50.659 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:51.659 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:52.660 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:53.660 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:54.660 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:55.661 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:55.995 [localhost-startStop-1] com.comcast.cdn.traffic_control.traffic_router.core.util.PeriodicResourceUpdater - Waiting for valid: /opt/traffic_router/db/cr-config.json
WARN  2020-06-19T17:32:56.106 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:32:56.620 [pool-3-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.monitor.TrafficMonitorWatcher - Loading properties from /opt/traffic_router/conf/traffic_monitor.properties
INFO  2020-06-19T17:32:56.661 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:57.661 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:58.661 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:32:59.662 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:00.662 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:01.662 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:02.663 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:03.663 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:04.663 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:05.664 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:33:06.107 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:33:06.664 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:07.664 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:08.665 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:09.665 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:10.665 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:11.666 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:12.666 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:13.666 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:14.667 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:15.667 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:33:16.107 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:33:16.305 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: https://ops.myawesomecdn.com/api/1.3/user/login; timeout is 15000
INFO  2020-06-19T17:33:16.361 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json; timeout is 15000
WARN  2020-06-19T17:33:16.376 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http Request to https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json Status 401
INFO  2020-06-19T17:33:16.667 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:17.668 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:18.668 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:19.668 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:20.669 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:21.669 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:22.669 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:23.669 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:24.670 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:25.670 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:33:26.107 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:33:26.670 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:27.671 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:28.671 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:29.671 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:30.672 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:31.672 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:32.672 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:33.673 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:34.673 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:35.673 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
WARN  2020-06-19T17:33:36.108 [pool-1-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.AbstractResourceWatcher - [SteeringWatcher] Waiting for configuration to be processed, unable to download from 'https://ops.myawesomecdn.com/internal/api/1.3/steering.json'
INFO  2020-06-19T17:33:36.673 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:37.674 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:38.674 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:39.674 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:40.674 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4
INFO  2020-06-19T17:33:41.675 [New I/O worker #5] com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - Waiting for https certificates to support new config abd66c4

TR likely isn't listening on port 53 yet because it is not starting up successfully to due issues in your environment. This issue means it can't connect to your Traffic Monitor to GET the CrConfig:
WARN  2020-06-19T17:31:56.620 [AsyncHttpClient-Reaper] com.comcast.cdn.traffic_control.traffic_router.core.util.PeriodicResourceUpdater - Failed request http://tm.myawesomecdn.com:80/publish/CrConfig?json: java.net.ConnectException: https://tm.myawesomecdn.com:443/publish/CrConfig?json

There are likely errors in the TM error log that indicate why it's not serving TR the CrConfig. Additionally, this error indicates that something is wrong, either with TO or your TR credentials:
WARN  2020-06-19T17:31:46.165 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http Request to https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json Status 401

Make sure your TR user has valid credentials in traffic_ops.properties.

@cheluskin - these types of questions can be answer faster here fyi - https://traffic-control-cdn.slack.com/


When using the Dart Plugin within Eclipse there should be an automatic way to install/update Dartium

This issue was originally filed by<EMAIL_ADDRESS>
Currently, you need to follow a few links, download a .zip file and manually copy the files within the eclipse directory. Error prone  and annoying.

This issue has been moved to dart-lang/eclipse3#49.


import unittest

Resolves undefined names in legacy tests

If some other file has imported unittest before this file is run then the global is set up and all is good at runtime.  However this is an implicit condition and not an explicit condition and we all know about what the Zen of Python says about that.  So it may work today but not tomorrow if the order of execution changes.

ok, but as the decorator is not used, maybe the good fix was just prunning unittest.skip


add coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1d20684). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   92.63%
=========================================
  Files             ?       11
  Lines             ?      190
  Branches          ?        0
=========================================
  Hits              ?      176
  Misses            ?       14
  Partials          ?        0

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 1d20684...c557c94. Read the comment docs.


Maybe rename the project?

Hi there! I think this is a great project (docker should have this sort of thing built in for all the money my org pays them...). My issue is more that the project name is close enough to Dokku (something I maintain), which is a self-hosted PaaS for docker.
I know naming is hard and you might be attached to this name already, but I would appreciate it if you would change the project name so that they aren't potentially confused by folks. It'll also help with discoverability for you since it won't be treated a misspelling of Dokku.
Feel free to ignore this issue if you would rather not rename. Good luck on this endeavor otherwise!

No worries, just thought I'd mention it. Thanks for considering it.
Closing now since there isn't much I can do :)


Oauth2-proxy as ExtAuth

Description:
I'm assessing whether we can move away from our current Ingress/Auth Ambassador Edge-Stack in favor of Envoy Gateway or others. We heavily rely on JWT & OIDC filtering at the moment and EG unfortunately has a less than optimal implementation of a combination of both compared to AES. I therefore try to use oauth2-proxy as ExtAuth in a SecurityPolicy.
This is my extAuth spec, successfully calling the endpoint of oauth2-proxy that should either return 202 or 401.
extAuth:
    failOpen: false
    headersToExtAuth:
    - Cookie
    - X-Auth-Request-User
    - X-Auth-Request-Groups
    - X-Auth-Request-Email
    - X-Auth-Request-Preferred-Username
    - X-Forwarded-Proto
    - X-Forwarded-Host
    - X-Forwarded-Uri
    - X-Auth-Request-Access-Token
    http:
      backendRefs:
      - group: ""
        kind: Service
        name: oauth2-proxy
        port: 80
      path: /oauth2/auth
  targetRefs:
  - group: gateway.networking.k8s.io
    kind: Gateway
    name: gateway1

My envoy actually reports this 202 code correctly, however, still considers it as ext_authz_denied.
{
  "start_time": "2024-10-29T15:10:29.515Z",
  "method": "GET",
  "x-envoy-origin-path": "/",
  "protocol": "HTTP/2",
  "response_code": "202",
  "response_flags": "UAEX",
  "response_code_details": "ext_authz_denied",
  "connection_termination_details": "-",
  "upstream_transport_failure_reason": "-",
  "bytes_received": "0",
  "bytes_sent": "13",
  "upstream_host": "-",
  "upstream_cluster": "httproute/dummy-app/dummy-app/rule/0",
  "route_name": "httproute/dummy-app/dummy-app/rule/0/match/0/*"
}

I'm not sure how this makes sense, what kind of response would the envoy proxy expect in order to let my request through?

yah that def looks odd, unsure if its superficial or not, hoping someone can try out https://gateway.envoyproxy.io/docs/tasks/security/ext-auth/#http-external-authorization-service and see if the results are similar or different

I dug a bit deeper into the code - it looks like Envoy expects http status OK/200, whereas oauth2-proxy returns Authenticated/202. Neither one or the other seem to be able to configure the expected/sent code.
Does anyone have an idea on how else to achieve these two components to successfully talk to each other?

cc @denniskniep

@zeisich you might want to look in envoy-oidc-authserver? We are heavily using it at few of our customers.
Lacks a bit of documentation unfortunately, but I think you might be able to figure it out looking at example deployment.
https://github.com/shelmangroup/envoy-oidc-authserver/tree/main/run/k8s/manifests
more features of the configurations can be found looking at this configuration.
https://github.com/shelmangroup/envoy-oidc-authserver/blob/main/run/config/providers.yaml
Super handy feature is pre/post auth authorization policies using rego from Open Policy Agent, which opens many possibilities. One example is that you're able to bypass oidc-auth-flow if Authorization header is sent and passes your policy validation.

Thanks, @lsjostro , I'll give it a try!

thanks for sharing a working solution @sando38


mesa: Build swrast gallium driver along with vc4

when running -ctestimage target, it fails because of errors it finds in
Xorg logs
| Log:
/mnt/a/yoe/build/tmp/work/raspberrypi3-yoe-linux-gnueabi/core-image-sato/1.0-r0/target_logs/Xorg.0.log
| -----------------------
| Central error: [    14.760] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
Therefore we enable swrast gallium drivers to make xorg happy
Signed-off-by: Khem Raj<EMAIL_ADDRESS>

Thanks @kraj . Merged to master.


Chef 17: Update all dependencies with bundle update

Signed-off-by: Neha Pansare<EMAIL_ADDRESS>Description
Bundle update to update update Gemfile.lock and omnibus/Gemfile.lock
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

https://buildkite.com/chef/chef-chef-main-omnibus-adhoc/builds/963


Pressing Capslock may break keyboard access for few seconds

When I press Capslock three times repeatedly I can't access keyboard for 3-5 secons. That issue also happening randomly if I type quickly.

I cannot reproduce this issue on my test machines. 3-5 seconds can never be the case. Considering you are somehow able to press 3 times in the span of one clock cycle of the CPU (practically impossible), the max lag you could notice is of 80 * 3 = 240 milliseconds. If you take the average, 80ms is the lag that is actually induced in order for the system to properly handle the keypress event and set the LED.
What I did to reproduce? Kept spamming random keys on my keyboard while toggling caps lock key. The behaviour was exactly like it is supposed to be; normal.
My take on this is, Dexts run in the user space rather than running in kernel space, so, a high system load can lead to delayed interrupts sometimes, which, has nothing to do with this driver.

It happens every time I try it doesn't happen without dext. May be it doesn't happen in your system because caps lock led is working on you. But every time I try to press 3 times capslock I can't type its not happening randomly. That is not a big issue for me but when I typing something quickly it happens exactly the same way. And its definitely longer than 240ms.

Please see https://github.com/black-dragon74/ROG-HID/issues/4#issuecomment-670781447

This issue also fixed with v1.3 thanks


Variables Menu - Right Pane

Add a Variables menu pane to the right side of the screen

Can you add a screenshot to this PR please


[Feat]: footer of contactus page

What feature?
in the footer of contactus page the logo of the os communitysite is somedown we can move it up so that webpage looks good.
Show us the magic with screenshots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

please assign me this issue @Vaishnavi-Patil2211


feat(backend-core): Organization memberships

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/clerk-expo
[x] @clerk/backend-core
[ ] @clerk/clerk-sdk-node
[ ] @clerk/edge
[ ] build/tooling/chore

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

This PR adds support for organization membership related operations in our backend-core package. It also adds resources for OrganizationMembership and OrganizationMembershipPublicUserData.
More specifically:

Added a method to fetch all organization memberships for a given organization. The method signature is organizations.getOrganizationMembershipList(params).
Added a method to create organization memberships. The signature is organizations.createOrganizationMembership(params).
Added a method to update an organization membership. The signature is organizations.updateOrganizationMembership(params).
Added a method to delete an organization membership. The signature is organizations.deleteOrganizationMembership(params).

Can we maybe add the 'index.ts' change so that the rest of the SDKs have access to the Org methods ?

@igneel64 Sure thing, I was planning to do it after we add all endpoints, but I guess there's no point in delaying it.


UploadListener is not called

I have set up OneUpUploaderBundle with two upload libraries.
I used FineUploader library and Blueimp library on 2 different Symfony test projects.
Both instances upload files to the endpoint without issues.
However, upload listeners are not called and are displayed in Symfony3 Profiler Events section Not Called Listeners in both test projects!
I have read all pull requests and issues on this projects Github page, still no suggestions worked! Additionally I have searched StackOverflow trough and trough, but did not found anything to fix my problem.
More detailed explanaton and exact code used can be found on StackOverflow:

OneUpUploaderBundle with Fine Uploader question
OneUpUploaderBundle with Blueimp question

Please advise.
Thank You for your time and knowledge.

Probably my issue is related: https://github.com/1up-lab/OneupUploaderBundle/issues/253
In my case listeners are also not called so it's break thing connected with chunk (but not only). In my case is environment related because it's cannot be reproduced on other. Unfortunately I can't find reason.

Yes, I am using PHP v7.0.8 (newest as of time of writing) on Windows 10 Pro.
For development i am using PHP built in server.
I have not tested it yet in production with Apache server.

If you still have this issue check my #253.Perhaps it is the same problem

@Rikijs In case you just switched over to php7, have you set the values of post_max_size and upload_max_filesize to big enough values in your php.ini file?

This issue was caused by misconfiguration of services.yml. Instead of oneup_uploader.post_persist.gallery instead of ...default_uploader works. Curiously .default_uploader was only auto complete item that PHPStorm offered. In the meantime events are still shown in Event Dispather Not Called Listeners section, though I can confirm that events now fire as codein them executes and saves info about files to database.


verilog: support for hierarchcial connections

References from [System]Verilog sources to internal module wires are now supported. Special autowires are automatically created and later resolved by the hierarchy pass, which turns them into appropriately dimensions wires with the hierconn attribute already supported downstream by the flatten pass. Because the hierarchy pass resolves modules from the top down, modules with automatic hierarchical connections are re-processed using a similar strategy to the one used to support SystemVerilog interfaces.
Fixes #647

I'm a concerned about adding more virtual members to RTLIL::Module which is strictly specific to Verilog, since this creates more complexity for non-Verilog frontends.

I went this route because it parallels the existing implementation of interfaces. We could use dynamic_cast instead, but note this would require including ast.h in hierarchy.cc. I agree that existing strategy is problematic given that these methods could pollute other frontends, although I'd hope the base this-is-not-supported implementation on RTLIL::Module would suffice for most (all?) other frontends.

Is it really necessary for the caller to specify hierconns here, i.e. can't the reprocess function figure this out on its own?

It is not necessary to pass that list. We could expose lookup_hierconn (likely to be renamed resolve_hierconn_auto) so it could be used in ast.cc

Should there really be separate reprocess_module and reprocess_with_hierconns entry points?

I'm not very familiar with the existing implementation of interfaces, although based on the what I have encountered working on sv2v and the limited existing test coverage, it may be in need of some attention. Mostly I was concerned with convoluting (and breaking) the implementations of both features. I would be happy to combine these functions. Either way, I wouldn't necessarily expect these automatic hierarchical connections to work if they refer to data within interface instances.

I'm a concerned about adding more virtual members to RTLIL::Module which is strictly specific to Verilog, since this creates more complexity for non-Verilog frontends.

I went this route because it parallels the existing implementation of interfaces. We could use dynamic_cast instead, but note this would require including ast.h in hierarchy.cc. I agree that existing strategy is problematic given that these methods could pollute other frontends, although I'd hope the base this-is-not-supported implementation on RTLIL::Module would suffice for most (all?) other frontends.

Is it really necessary for the caller to specify hierconns here, i.e. can't the reprocess function figure this out on its own?

It is not necessary to pass that list. We could expose lookup_hierconn (likely to be renamed resolve_hierconn_auto) so it could be used in ast.cc

Should there really be separate reprocess_module and reprocess_with_hierconns entry points?

I'm not very familiar with the existing implementation of interfaces, although based on the what I have encountered working on sv2v and the limited existing test coverage, it may be in need of some attention. Mostly I was concerned with convoluting (and breaking) the implementations of both features. I would be happy to combine these functions. Either way, I wouldn't necessarily expect these automatic hierarchical connections to work if they refer to data within interface instances.

@whitequark Do you have any reservations regarding my suggestions above? If not, I'd be happy to take another pass at this PR.

@zachjs Your suggestions all sound reasonable to me. I believe the implementation of interfaces was not done with long term evolution of internal APIs in mind; I think it would be prudent to take more care of this now.


Build multiple arch/platforms at once?

nw-builder has an option
platforms: ["win32", "linux64", "linux32", "osx64"],

so I can run it once and build all required targets.
How can I achieve this?

Try build --concurrent.

So if I don't want to build 2 unnecessary targets I should run build 4 times in my case?

If I could do something like --win32 --linux64 --linux32 --osx64 I would be happy.

Added in nwjs-builder-phoenix 1.14.0. e.g. build --tasks win-x86,win-x64,mac-x64 ..

Cool! Thank you!


add metadata to KVM domain (Issue 6695 fix)

Description
This PR...
Fixes: #6695

Types of changes

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

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Hi @Jehan-h20220012, could you please add a more descriptive title and message?
You need to pass this setting when starting a VM. You can try adding it to the VM's details or do some research on how it would be better. The main part of the Domain's XML is generated from here. when the setting is enabled you need to append the required metadata to the XML.
https://libvirt.org/formatdomain.html#general-metadata

@slavkap Thank you, I will look into it and will let know if any help needed.

@Jehan-h20220012 what @slavkap said and can you add test description as well, please? good luck.

@Jehan-h20220012 is this still relevant? are you still looking at this? (cc @slavkap )

@Jehan-h20220012 is this still relevant? are you still looking at this? (cc @slavkap )

I have no updates on it and this issue might have been resolved by some other PRs.

@slavkap @shwstppr should we postpone or try to get this in 4.19?

@DaanHoogland I don't think this is ready yet. PR just adds the global config but I don't see its value being queried. Or maybe I'm missing something

No @shwstppr , let's abandon this and reboot when there is call for it.