[BUG] rancher webhook fails on RKE1 clusters

Rancher Server Setup

Rancher version: v2.7-1712bf9f7116e25711fd76b99d7ce5672c2d4a23-head
Installation option (Docker install/Helm Chart): Docker single node with v2.7-head as the image

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: RKE1 v1.25.6 and RKE1 v1.24.10
Cluster Type (Local/Downstream): downstream RKE1 cluster on Harvester v1.1.1

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:
user: Admin

Describe the bug

When you deploy out an RKE1 cluster on Harvester v1.1.1 Rancher webhook goes into a fail state. This happens on k8s v1.24.10 and v1.25.6 in RKE1
To Reproduce

Import Harvester v1.1.1 into Rancher v2.7-head
Create cloud credentials
Deploy RKE1 cluster onto Harvester
Wait for  cluster to go active
Click explore
Check pods and installed apps in all namespaces for rancher-webhook
Result

Expected Result

rancher-webhook should work
Screenshots

Additional context

The Harvester cluster was a 3 node virtualized kvm/libvirt setup done through ipxe-examples on v1.1.1. The Rancher cluster was a single node docker deploy on openSUSE Leap 15.4.

This also happens for me after upgrading from Rancher 2.6.4 to 2.7.1 and then upgrading downstream clusters to 1.25.6.

Upgrade Rancher from 2.6.4 to 2.7.1
Upgrade downstream cluster from 1.22 to 1.23 --> no problem. rancher-webhook doesn't even exist, nor does the rancher-webhook-tls secret.
Upgrade downstream cluster from 1.23 to 1.24 or 1.25 --> rancher-webhook pod gets created in cattle-system and is stuck in containerCreating mode due to rancher-webhook-tls not existing. All the failed helm-operation- pods @noahgildersleeve mentioned are also present in my case.

○ → kubectl get pods -n cattle-system
NAME                                   READY   STATUS              RESTARTS        AGE
cattle-cluster-agent-7f4767c9f-svvqq   1/1     Running             3 (5m31s ago)   5m51s
cattle-cluster-agent-7f4767c9f-vwtrn   1/1     Running             3 (5m32s ago)   5m52s
cattle-node-agent-2c6rz                1/1     Running             0               13m
cattle-node-agent-tfnbk                1/1     Running             0               14m
helm-operation-2fx2v                   1/2     Error               0               8m18s
helm-operation-b6tck                   1/2     Error               0               9m34s
helm-operation-dfcrj                   1/2     Error               0               9m40s
helm-operation-prsxr                   1/2     Error               0               9m23s
helm-operation-prsxt                   1/2     Error               0               9m29s
helm-operation-vgqwq                   1/2     Error               0               4m9s
kube-api-auth-kqjmc                    1/1     Running             0               14m
rancher-webhook-6fb4f54478-xbfqj       0/1     ContainerCreating   0               5m54s

kubectl describe pod -n cattle-system rancher-webhook-6fb4f54478-xbfqj

  Warning  FailedMount       2m32s                kubelet            Unable to attach or mount volumes: unmounted volumes=[tls], unattached volumes=[tls kube-api-access-bbxjb]: timed out waiting for the condition
  Warning  FailedMount       24s (x9 over 4m34s)  kubelet            MountVolume.SetUp failed for volume "tls" : secret "rancher-webhook-tls" not found
  Warning  FailedMount       14s                  kubelet            Unable to attach or mount volumes: unmounted volumes=[tls], unattached volumes=[kube-api-access-bbxjb tls]: timed out waiting for the condition


macOS: remove redundant system libraries link

This became redundant after https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2413.

Dankjewel!


Get logs API return 500 not 404 when log not exists

If job is killed when waiting resource. Not log is generated. Currently, API will return 500. Need to return 404.

Test case:

Start a job, make it in waiting status.
All API to get the job logs. Make sure the API return 400 instead of 500. And UI shows correct


Automatically trace deleted from jaeger in memory in every 25s

Requirement - what kind of business use case are you trying to solve?
Trying with limiting number of traces in in-memory. I am using jaegertracing/all-in-one image. Limiting maximum number of traces using MEMORY_MAX_TRACES environment variable. In my test I am testing max trace is 20

Problem - what in Jaeger blocks you from solving the requirement?
I have generated 10 traces. all the traces are displayed in jaeger ui. Observing, in every 25seconds, one of trace is getting deleted and disappeared from Jaeger ui.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Any open questions to address
Why traces deleted every 25 sec. Is there any thing I am missing.

{"level":"debug","ts":1560992074.8679144,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":480}
{"level":"debug","ts":1560992074.8688984,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"42bd3bf2a58089dc","span-id":"42bd3bf2a58089dc"}
{"level":"debug","ts":1560992082.867254,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":801}
{"level":"debug","ts":1560992082.8686414,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"4de3bc16bc13ecb1","span-id":"4de3bc16bc13ecb1"}
{"level":"debug","ts":1560992082.8687825,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"7c6838b653f8b85a","span-id":"7c6838b653f8b85a"}
{"level":"debug","ts":1560992083.869301,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992083.8720343,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"286fec6f264c4aad","span-id":"286fec6f264c4aad"}
{"level":"debug","ts":1560992084.8662515,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992084.8676286,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"2807324975f96f27","span-id":"2807324975f96f27"}
{"level":"debug","ts":1560992085.86622,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992085.8670275,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"501118478869f4e","span-id":"501118478869f4e"}
{"level":"debug","ts":1560992112.866112,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992112.866933,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"238f39fd42961f5f","span-id":"238f39fd42961f5f"}
{"level":"debug","ts":1560992114.866202,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":801}
{"level":"debug","ts":1560992114.8668005,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"63d8ed1d4d615134","span-id":"63d8ed1d4d615134"}
{"level":"debug","ts":1560992114.8669047,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"68ee1927c4768759","span-id":"68ee1927c4768759"}
{"level":"debug","ts":1560992115.866195,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992115.8671951,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"29b43c9d3b30fa4","span-id":"29b43c9d3b30fa4"}
{"level":"debug","ts":1560992160.8661075,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992160.8672228,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"36317ae7569e6806","span-id":"36317ae7569e6806"}
{"level":"debug","ts":1560992161.8670542,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":480}
{"level":"debug","ts":1560992161.8681276,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"6d3242d7bb17cc70","span-id":"6d3242d7bb17cc70"}
{"level":"debug","ts":1560992178.8660352,"caller":"processors/thrift_processor.go:113","msg":"Span(s) received by the agent","bytes-received":478}
{"level":"debug","ts":1560992178.86679,"caller":"app/span_processor.go:117","msg":"Span written to the storage by the collector","trace-id":"a694265d9543df","span-id":"a694265d9543df"}

Note that jaeger-query also generates traces which probably affects your limit.

Thanks! That is the issue.
Is there any configuration which will limit max traces per service?

There is not.

This does not appear to be an issue with Jaeger. I am closing this.
Feel free to reopen/comment if there are other issues.


Using the pattern created by the 2 qumode and 3 qumode squeeze gates, add an n-qumode squeeze gate

The idea is to prevent needing to add a 4 qumode, 5, qumode, 6 qumode, etc. squeeze gate.
See #131

From Daniel Dong who first asked for the 3 qumode squeeze gate:

I think there's an limit to qiskit's HighLevelSynthesis, where it has a limit between a 12 and 15 qubit custom circuit
in that case, there's little point to adding a squeeze gate for an arbitrary number of qumodes as, at 5 qubits, we're already limited to a maximum of 2 qubits per qumode (edited)


Recipe for runway connectors

Same as the other one-way connectors but this time with feathers.

So I did, it should be fixed now. Glad you spotted that !


Python3 compatibility

Is it possible to make compatible with python3?
I keep running into errors due to the hashing and message printing.

@Qguess How did you done with what?
In my and CI's Python3 environment, a test program(scripts/test.py) executed correctly with passed all tests, so I think the code is not wrong.

Just used python2.7 I don't understand how can you take ecdsa public key and use the two pairings to solve for private key.
On Jul. 16, 2019 01:38, Shiho Midorikawa<EMAIL_ADDRESS>wrote:
@Qguesshttps://github.com/Qguess How did you done with what?
In my and CI's Python3 environment, a test program(scripts/test.py) executed correctly with passed all tests, so I think the code is not wrong.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/elliptic-shiho/ecpy/issues/11?email_source=notifications&email_token=AMNUTCMUEGYGHYCUL7UKKX3P7S73DA5CNFSM4ICCXLLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ6S6VA#issuecomment-511520596, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMNUTCPB3D4PRM5OSYXVNULP7S73DANCNFSM4ICCXLLA.


Update learning-bus-user.md

Removed a course that no longer exists

Removed a course that no longer exists on Microsoft Learn.
#sign-off


No static method getMainExecutor

Hi,
l have trouble running a specific app which worked on earlier flutter versions.
On emulator I'm getting the following error:
`Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
lib\main.dart:1
√  Built build\app\outputs\flutter-apk\app-debug.apk.
W/FlutterActivityAndFragmentDelegate(17314): A splash screen was provided to Flutter, but this is deprecated. See flutter.dev/go/android-splash-migration for migration steps.
E/AndroidRuntime(17314): FATAL EXCEPTION: main
E/AndroidRuntime(17314): Process: XXX, PID: 17314
**E/AndroidRuntime(17314): java.lang.NoSuchMethodError: No static method getMainExecutor(Landroid/content/Context;)Ljava/util/concurrent/Executor; in class Landroidx/core/content/ContextCompat; or its super classes (declaration of 'androidx.core.content.ContextCompat' appears in /data/app/~~9BJxuN7z5AmQPo8xmEEe_Q==/XXX-iz5CrEQ1CIST6D0OKQzgww==/base.apk)**
E/AndroidRuntime(17314): 	at io.flutter.embedding.android.FlutterView.onAttachedToWindow(FlutterView.java:483)
E/AndroidRuntime(17314): 	at android.view.View.dispatchAttachedToWindow(View.java:20753)
E/AndroidRuntime(17314): 	at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3490)
4
E/AndroidRuntime(17314): 	at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3497)
E/AndroidRuntime(17314): 	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2613)
E/AndroidRuntime(17314): 	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2126)
E/AndroidRuntime(17314): 	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:8653)
E/AndroidRuntime(17314): 	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1037)
E/AndroidRuntime(17314): 	at android.view.Choreographer.doCallbacks(Choreographer.java:845)
E/AndroidRuntime(17314): 	at android.view.Choreographer.doFrame(Choreographer.java:780)
E/AndroidRuntime(17314): 	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1022)
E/AndroidRuntime(17314): 	at android.os.Handler.handleCallback(Handler.java:938)
`

On physical device I'm getting:
Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:51292/8dGuTc40nXk=/
Flutter doctor output:
`[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19044.1645], locale en-US)
    • Flutter version 2.10.5 at C:\flutter
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision 5464c5bac7 (3 weeks ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\admin\AppData\Local\Android\Sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = C:\Users\admin\AppData\Local\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • CHROME_EXECUTABLE = C:\Work\chrome_debug.bat

[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.0.2)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.0.31919.166
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2021.1)
    • Android Studio at C:\Program Files\Android\Android Studio1
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)

[!] Android Studio (version 4.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    X Unable to determine bundled Java version.
    • Try updating or re-installing Android Studio.

[√] VS Code (version 1.66.2)
    • VS Code at C:\Users\admin\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.38.1

[√] Connected device (5 available)
    • M2101K9AG (mobile)           • fd22dae3      • android-arm64  • Android 11 (API 30)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 12 (API 31) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [Version 10.0.19044.1645]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 100.0.4896.127
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 101.0.1210.32

[√] HTTP Host Availability
    • All required HTTP hosts are available`

@tigrenok00
The error **E/AndroidRuntime(17314): java.lang.NoSuchMethodError: No static method getMainExecutor(Landroid/content/Context;)Ljava/util/concurrent/Executor; in class Landroidx/core/content/ContextCompat; or its super classes (declaration of 'androidx.core.content.ContextCompat' appears in /data/app/~~9BJxuN7z5AmQPo8xmEEe_Q==/XXX-iz5CrEQ1CIST6D0OKQzgww==/base.apk)** seems to be coming from third party plugin which you might be using, but I can't tell which plugin since you didn't provide much info.
I suggest you to take a look at plugins you are using and check which plugin might be throwing the error and accordingly reach out to dedicated plugin repo, or you may also ask the same on support channels like StackOverflow.
Closing from here.


bump to 019

Current dependencies on/for this PR:

main

PR #65   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 6, 6:50 PM EST: @willseltzer merged this pull request with Graphite.


Add -UserAgent parameter to Start-BitsTransfer

Summary of the new feature / enhancement
BITS has many advantages over the Invoke-WebRequest cmdlet, but there doesn't seem to be any way to set a custom User-Agent header, like Invoke-WebRequest has (-UserAgent).
This means that whenever I'm downloading a file from a server where I need to change my User-Agent (e.g. some software distribution sites provide the file directly for well-known user agents like Wget, but show a website with download button for other user agents), I have to use Invoke-WebRequest instead of Start-BitsTransfer.
Would it be possible to add a similar parameter to Start-BitsTransfer?
Proposed technical implementation details (optional)
No response

Start-BitsTransfer is not in the repo. Please use Windows Feedback tool and other channels to request new feature.


Exception when use RedissonRedLock + RedissonMultiLock

I'm trying to introduce RedLock algorithm in my project, I have 3 Redis nodes, and I need to lock several keys in each thread. Here is my implementation:
// config1 for node #1, config2 for node #2, config3 for node #3, all of them are using single server.
RedissonClient redission1 = Redisson.create(config1);
RedissonClient redission2 = Redisson.create(config2);
RedissonClient redission3 = Redisson.create(config3);
RLock key11 = redission1.getLock("key1");
RLock key12 = redission1.getLock("key2");
RLock multiLock1 = new RedissonMultiLock(key11, key12);
RLock key21 = redission2.getLock("key1");
RLock key22 = redission2.getLock("key2");
RLock multiLock2 = new RedissonMultiLock(key21, key22);
RLock key31 = redission3.getLock("key1");
RLock key32 = redission3.getLock("key2");
RLock multiLock3 = new RedissonMultiLock(key31, key32);
RLock redLock = new RedissonRedLock(multiLock1, multiLock2, multiLock3);
redLock.tryLock(lockAcquireTimeoutMs, lockExpiryMs, TimeUnit.MILLISECONDS);
Expected behavior
no exception
Actual behavior
Got exception with message: ""org.redisson.RedissonMultiLock cannot be cast to org.redisson.RedissonLock""
Steps to reproduce or test case
the root cause is this code in method tryLock(long waitTime, long leaseTime, TimeUnit unit) of class RedissonMultiLock.java:
RFuture future = ((RedissonLock)rLock).expireAsync(unit.toMillis(leaseTime), TimeUnit.MILLISECONDS);
It trys to cast rLock to RedissonLock, but in my case the rLock is RedissonMultiLock. By this implementation, RedissonMultiLock actually can not group any RLock types but RedissonLock.
Redis version
Redisson version
3.10.7
Redisson configuration

The RedLock is a subset of multi lock, it is unusual to see them blended together. I can't stop wondering what your intension is to "group" those different locks originated from the same node before used in RedLock? I am asking because in the sense of multi lock the schematics of (A + B) + (C + D) + (E + F) isn't the same as A + B + C + D + E + F.

Hello jack, it is not (A + B) + (C + D) + (E + F), but (A1 + B1) + (A2 + B2) + (A3 + B3).
Let's say A1, A2, A3 is for key A, but against different nodes. Same for B1, B2, B3.
In my understanding, RedLock used multiple nodes for fault tolerance reason, when the majority of nodes are up, I can acquire the lock successfully. So I acquire the lock for key A against node1, node2 and node3, if I acquired two such as A1 and A2, but A3 result in failure, I can still consider the lock of key A is required.

In my case, I need to acquire the lock of both key A and key B, for fault tolerance reason, i created 3 independt Redis nodes, they are not in a cluster.

Hello jack, it is not (A + B) + (C + D) + (E + F), but (A1 + B1) + (A2 + B2) + (A3 + B3).
Let's say A1, A2, A3 is for key A, but against different nodes. Same for B1, B2, B3.

Won't this be two RedLocks, one for A1, A2, A3 and another for B1, B2, B3?

But I need to acquire both key A and B simultaneously, they can't be separated from each other, that's why I use RedissonMultiLock.

Basically, the As and Bs are two fault tolerant Locks backed by RedLock algrithm. If you want two RedLocks executed in parellel, you can just use the async methods and combine the future.


@observable: Support observable getters like polymer @published

Originally opened as dart-lang/sdk#14111
This issue was originally filed by<EMAIL_ADDRESS>
I'm not sure why this ended up in polymer instead of observe, but it's just as useful for non polymer apps.  The method ObservableMixin._observed is almost identical to polymer/src/declaration _getProperties.
See https://code.google.com/p/dart/issues/detail?id=13937.

 Comment by madsager

Added Area-Library, Library-Observe, Triaged labels.

 Comment by jmesserly

Added NotPlanned label.

 Comment by jmesserly

Hi Erik,
I'm not sure I understand the issue. Here's my understanding -- correct me if I got it wrong.
@published creates a relationship between an HTML attribute and a property.
Therefore, it wouldn't make sense at the package:observe layer of the system, because there's no dart:html knowledge at that level.
Likewise it's not a Custom Elements feature--because not all custom elements are observable.
So we need to put it in a package that unifies observe, templates, and custom elements features. package:polymer fits the bill nicely :)
But more than that, it's part of Polymer's "opinionated framework".
www.polymer-project.org/polymer.html#published-properties
We do need better support for getters/computed fields -- but that is covered by another bug.

Removed Area-Library label.
Added Area-Polymer, NeedsInfo labels.

This comment was originally written by<EMAIL_ADDRESS>
Hey John,
Sorry, I forgot to get back to you. I was referring to supporting getters/computed fields. I must have missed the other bug.

 Comment by jmesserly

awesome! yeah, would love to see computedfields get better

Added Duplicate label.
Marked as being merged into dart-lang/observe#40.

 Comment by anders-sandholm

Removed Library-Observe label.
Added Pkg-Observe label.


Question

@bevacqua Thanks for the amazing work done.
Use Function() as a "no-op".

function (cb) {
  setTimeout(cb || Function(), 2000);
}

why not use if-else and do not call setTimeout at all ?

Say you have an external API method with a opts, done? signature. That method internally calls many other functions, some of which are asynchronous as well. If you set done = done || Function() or some such at the entry point, you won't have to check whether a callback is being passed in the internal functions.


Stop using global variables in favor of context.

Hello! I'm trying to write an integration test between two projects that use knative.dev/pkg for building reconcilers.
Generally, it's working fine, but I'm facing a problem because I need to start two "sharedmain" projects, one for each one,
and they use different namespaces/configuration. The problem is that when we use static info like system.Namespace() it makes really hard to compose such runtime.
So I guess my question is: would it be welcome changes to stop using global variables in favor of context.Context? We can make it backward-compatible by automatically adding default values into the context when not found.

start two "sharedmain"

That's not really how the package is meant to be consumed. If you need to run different controllers in the same process you would just use a single sharedmain and merge the list of controllers.

would it be welcome changes to stop using global variables in favor of context.Context?

At this point I don't think we would want to introduce such a change - the use of the system.Namespace() and some other functions are fundamental assumptions at this point. Even in tests.

That's not really how the package is meant to be consumed. If you need to run different controllers in the same process you would just use a single sharedmain and merge the list of controllers.

Even if I use a single sharedmain, I still can't run controllers in multiple namespaces.. and the only limitation here is the fact that we are using an env var, which it's not thread safe to update.

At this point I don't think we would want to introduce such a change - the use of the system.Namespace() and some other functions are fundamental assumptions at this point. Even in tests.

I've checked, and most (if not all) functions that use system.Namespace() already receives context.Context. In terms of tests, it would help tests, since you wouldn't require a os.Setenv(system.NamespaceEnvKey, "knative-testing") anymore. And would enable to test the integration of controllers running in different namespaces.

Yeah I understand you needs. I don't think we'd want to make the changes to accommodate this.
As a workaround you could launch your different controllers in two child processes.

Here's an example on how to launch these processes in a golang test
https://go.dev/talks/2014/testing.slide#23

Going to close this out - thanks for reaching out prior.


logging-effect-1.3.0 benchmark fails to compile

In Stackage Nightly, cc @ocharles :
Building benchmark 'benchmark-logging-effect' for logging-effect-1.3.0..
[1 of 1] Compiling Main             ( Benchmark.hs, dist/build/benchmark-logging-effect/benchmark-logging-effect-tmp/Main.o )

Benchmark.hs:20:96: error:
    • Couldn't match type ‘prettyprinter-<IP_ADDRESS>:Data.Text.Prettyprint.Doc.Internal.Doc
                             ann3’
                     with ‘PP.Doc’
      NB: ‘PP.Doc’
            is defined in ‘Text.PrettyPrint.Leijen.Text’
                in package ‘wl-pprint-text-<IP_ADDRESS>’
          ‘prettyprinter-<IP_ADDRESS>:Data.Text.Prettyprint.Doc.Internal.Doc’
            is defined in ‘Data.Text.Prettyprint.Doc.Internal’
                in package ‘prettyprinter-<IP_ADDRESS>’
        arising from a functional dependency between:
          constraint ‘LoggingEffect.MonadLog
                        (LoggingEffect.WithSeverity PP.Doc)
                        (LoggingEffect.LoggingT
                           (LoggingEffect.WithSeverity
                              (prettyprinter-<IP_ADDRESS>:Data.Text.Prettyprint.Doc.Internal.Doc
                                 ann3))
                           IO)’
            arising from a use of ‘loggingEffectLog’
          instance ‘LoggingEffect.MonadLog
                      message (LoggingEffect.LoggingT message m)’
            at <no location info>
    • In the first argument of ‘LoggingEffect.runLoggingT’, namely
        ‘loggingEffectLog’
      In the first argument of ‘nfIO’, namely
        ‘(LoggingEffect.runLoggingT
            loggingEffectLog loggingEffectStdoutHandler)’
      In the second argument of ‘bench’, namely
        ‘(nfIO
            (LoggingEffect.runLoggingT
               loggingEffectLog loggingEffectStdoutHandler))’
   |
20 | main = defaultMain [ bgroup "log10k" [ bench "logging-effect" (nfIO (LoggingEffect.runLoggingT loggingEffectLog loggingEffectStdoutHandler))
   |                                                                                ^^^^^^^^^^^^^^^^
:
:
:

Not sure if this is a Stackage issue or not?

http://hdiff.luite.com/cgit/logging-effect/diff?id=1.3.0&id2=1.2.6
The prettyprinter was changed, but it wasn't updated in the benchmarks afaics.

Ah yes, I should have filed in the upstream project then.

I would love a PR! I will try and prep a fix but it might take me a bit of time (work is crazy right now)

@ocharles there is no extreme rush - just wanted to make sure it doesn't go forgotten that's all.
(Earlier I mistook it as a potential import ambiguity - that is why I filed it here cautiously by mistake.)

I believe this is released and fixed now. Anything I need to do?

Thanks!


Refactor Cfd constructor to improve readability

I found this hard to read so I refactored it a bit to use early returns

I've basically done the same thing in #1308 :)

Happy to use your refactoring then :)


IconButton does not implement button theme

The IconButton element does not support the button theme customization.
I was expecting, as mentioned by the documentation, that the button theme will be applied to the IconButton component when the className is constructed but it is not. It seems that only theme.toggle, theme.inverse, theme.primary, theme.accent and theme.neutral are considered.
const classes = classnames([theme.toggle], {
        [theme[level]]: neutral,
        [theme.inverse]: inverse,
      }, className);

Is this normal?

We got the same problem and are now using inverse, primary or accent. The documentation is wrong here in my opinion because it says for the button theme property: "Used for the root element in any button."


stats bug

Describe the bug
some of the stats aren't syncing up with my in game stats
Profile/Location
A link to the profile which the bug occurred with, if applicable (e.g. https://sky.shiiyu.moe/stats/Minikloon/Banana)
Additional Info
If applicable, what pet/weapon/armor you are using and where you are in Skyblock.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS:  Windows 10
Version 1.19.4

pretty sure there was a problem with health and other things affected by skyblock levels. i think there is a pull request open to fix it it just hasnt been merge yet

pretty sure there was a problem with health and other things affected by skyblock levels. i think there is a pull request open to fix it it just hasnt been merge yet

Yeah, there's PR. Sadly it's not possible to fully sync stats due to API limitations

#1696


chanmc nerfed finally

https://github.com/user-attachments/assets/bc4aa571-30d4-483e-a27a-859bbb2c6eb9

Missing configuration.


880 Project access user level permissions

Targets #880

Description

We needed a role named project-manager. The user with this role should be able to see the project management menu in the dashboard.
Checklist:

[x] I have performed a self-review of my own code.

Merging as all the changes requested have been made.


Setting upper/lower angular parameters on HingeJoint3D in GDScript doesn't work

Godot version
4.0
System information
Windows 10
Issue description
When setting the upper/lower angular limits on the HingeJoint3D using GDScript, the parameters default to 180°, -180°
Steps to reproduce

Add a HingeJoint3D node to the scene
Assign the rigidbodies
Set the upper and lower angular limits with code

$HingeJoint3D.set("angular_limit/upper", 5)
$HingeJoint3D.set("angular_limit/lower", -5)

Minimal reproduction project
N/A

It seems that values can be set in the editor, but not via code.
The following code displays that values have been set, but the remote inspector still displays the default values for upper and lower limit:
func _ready():
	set("angular_limit/upper", 5)
	set("angular_limit/lower", -5)
	print("Upper angular limit: %f" % get("angular_limit/upper"))
	print("Lower angular limit: %f" % get("angular_limit/lower"))

this bug is still present in 4.2.1

both Object's "set()" method and HingeJoint3D's "set_param()" method make the limit default to 180/-180
has anyone found a workaround?

Just use Mathf.DegToRad. This is example in C#:
HingeJoint3D.Set("angular_limit/upper", Mathf.DegToRad(5));


Does this loop forever? :)

https://github.com/nblumhardt/serilog-blazor/blob/e0f1ba4f8015571570d9a94eee95d10444c61c03/SerilogBlazorDemo.Server/Diagnostics/SerilogClientLoggingMiddleware.cs#L55

Would appear that it did! :-) ... Just YOLO-committed a fix, thanks.


I get errors when i try to run tsc conf.ts

Hi I am struggling to resolve these errors when trying to do tsc or tsc conf.ts so that i can generate a conf.js file and run protractor test.

Error:
<>:testTypescript sarthakgupta$ tsc
node_modules/blocking-proxy/built/lib/blockingproxy.d.ts:1:23 - error TS2688: Cannot find
type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/blockingproxy.d.ts:2:23 - error TS2307: Cannot find
module 'http'.
2 import * as http from 'http';
~~~~~~
node_modules/blocking-proxy/built/lib/webdriver_commands.d.ts:1:23 - error TS2688: Cannot
find type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/webdriver_commands.d.ts:5:25 - error TS2307: Cannot
find module 'events'.
5 import * as events from 'events';
~~~~~~~~
node_modules/blocking-proxy/built/lib/webdriver_logger.d.ts:1:23 - error TS2688: Cannot find type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/webdriver_logger.d.ts:2:25 - error TS2307: Cannot find module 'stream'.
2 import * as stream from 'stream';
~~~~~~~~
node_modules/blocking-proxy/built/lib/webdriver_proxy.d.ts:1:23 - error TS2688: Cannot find type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/webdriver_proxy.d.ts:2:23 - error TS2307: Cannot fin
Sarthaks-MacBook-Air:testTypescript sarthakgupta$ tsc
node_modules/blocking-proxy/built/lib/blockingproxy.d.ts:1:23 - error TS2688: Cannot find
type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/blockingproxy.d.ts:2:23 - error TS2307: Cannot find
module 'http'.
2 import * as http from 'http';
~~~~~~
node_modules/blocking-proxy/built/lib/webdriver_commands.d.ts:1:23 - error TS2688: Cannot
find type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/webdriver_commands.d.ts:5:25 - error TS2307: Cannot
find module 'events'.
5 import * as events from 'events';
~~~~~~~~
node_modules/blocking-proxy/built/lib/webdriver_logger.d.ts:1:23 - error TS2688: Cannot find type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/webdriver_logger.d.ts:2:25 - error TS2307: Cannot find module 'stream'.
2 import * as stream from 'stream';
~~~~~~~~
node_modules/blocking-proxy/built/lib/webdriver_proxy.d.ts:1:23 - error TS2688: Cannot find type definition file for 'node'.
1 ///
~~~~
node_modules/blocking-proxy/built/lib/webdriver_proxy.d.ts:2:23 - error TS2307: Cannot find module 'http'.
2 import * as http from 'http';
~~~~~~
node_modules/protractor/built/runner.d.ts:1:23 - error TS2688: Cannot find type definition file for 'node'.
1 ///
~~~~
node_modules/protractor/built/runner.d.ts:3:30 - error TS2307: Cannot find module 'events'.
3 import { EventEmitter } from 'events';
~~~~~~~~
Found 10 errors.

Bug report

Node Version: v11.10.0
Protractor Version: 5.4.2
Angular Version: ``
Browser(s): Chrome
Operating System and Version MacOs 10.13.6
Your protractor configuration file
import {Config} from 'protractor';

export let config: Config = {
directConnect: true,
capabilities: {
'browserName': 'chrome'
},
framework: 'jasmine',
specs: ['tests/regressionTests.spec.js'],
seleniumAddress: 'http://localhost:4444/wd/hub',
noGlobals: true
};

A relevant example test
Output from running the test
Steps to reproduce the bug
The URL you are running your tests against (if relevant)

package.json file:
{
"name": "backbase-assignment",
"version": "1.0.0",
"description": "test",
"author": "Sarthak Gupta",
"scripts": {
"tsc": "tsc",
"pretest": "npm run tsc",
"test": "protractor tmp/conf.js",
"debug": "node --inspect-brk ./node_modules/.bin/protractor asyncAwait/conf.js"
},
"devDependencies": {
"@types/jasmine": "^2.5.41",
"@types/jasminewd2": "^2.0.6",
"ts-node": "^3.0.2"
},
"dependencies": {
"protractor": "5.4.2",
"typescript": "~2.0.0",
"jasmine": "^2.4.1"
}
}
tsconfig.json file:
{
"compilerOptions": {
"target": "es5",
"module": "commonjs",
"moduleResolution": "node",
"sourceMap": true,
"declaration": true,
"removeComments": false,
"noImplicitAny": true,
"outDir": "built/"
},
"exclude": [
"node_modules"
]
}

I tried to do the below after looking at some other posts
npm install @types/node --save
npm install typescript --save-dev
npm install ts-node --save-dev
It starts to work now. But i still don't know why and how? I can see I have also mentioned these dependencies in package.json so they should already be present in node_modules after doing package.json? and thats not happening.

I faced the same problem. It worked after uninstalling unwanted plugins in vscode.
Could you please list down the plugins which you are using?

Its a type definition error:
npm install @types/node --save-dev
is enough.
Beware that we use --save-dev as its not a runtime dependency.


Broken examples

Probably because of a substitution?
see for example, new passed files of get_range_help.R in inst/examples

Closing it, we have solved this last time, if it happens again we can open a new one.


Accentuated letters and other non-English letters are letters

I have noticed in this post that Official release by Abörted Hitler Cöck, 2011-12-23 triggers the AB acronym AcousticBrainz because of ö not being seen as a Letter by JavaScript (it's clearly a lowercase Letter O with trema accent).
I discovered that \b, \w and \W are only working with pure ASCII letters (English).
As JavaScript RegExpr does not know \p{L}/\P{L} syntax for Letter / non-Letter Unicode categories, I had to copy a full list of character ranges from https://github.com/slevithan/xregexp/blob/master/tools/output/categories.js#L40 .
@Freso, do you have a way to test it on Discourse?
The code is becoming way much more complex.
But international compatibility should be important…
Maybe there is a more simple way… I don't know.

If anybody wants to pick this up, take a look how it is done in the original discourse-linkify-words repo. (essentially, instead of using \b and `\w' we explicitly list the boundary characters).

Thanks @danielhollas,
It seems the plugin changed quite much, as we come from an common/head_tag.html file to a javascripts/discourse-linkify/lib/utilities.js.es6 file now.
We had to modify the plugin because of #1 and #2. :)
Is it below code?
https://github.com/discourse/discourse-linkify-words/blob/91fd7d44820e01504c548860e1a47664514e291e/javascripts/discourse-linkify/lib/utilities.js.es6#L33-L34

@jesus2099 I believe the current version of discoure-linkify should handle the issues in #1 and #2.
Yes, I've refactored the code quite a bit to make it in line with current Discourse theme approach. Incidentally, the code is now much easier to modify for the purposes of your version. Essentially, it should suffice to just modify a couple things here:
https://github.com/discourse/discourse-linkify-words/blob/91fd7d44820e01504c548860e1a47664514e291e/javascripts/discourse-linkify/initializers/initialize-discourse-linkify.js.es6#L31
So in principle it might be worthwhile to just merge with upstream and reapply the modifications, instead of pulling individual pieces. I am happy to submit a PR for that if you'd agree with that idea.

I agree it could be great to align back to your source before re-fixing, if even still needed.
I don't know where are our specific stuff (the words we highlight) but @Freso, as you maintain this, what do you think of above proposal?

@jesus2099 the word list is maintained in the theme component settings in the Discourse Admin interface and that shouldn't break with the update.

I would be happy with a PR of a merge with the updates from the source repository of this codebase. :)

@Freso @jesus2099 Great! I'll cook up a PR. Next week is going to be busy so probably the one after that. Thanks!

Apparently #6 will fix this with Unicode property escapes category \p{Letter}.
I put this in draft and will close it once I can see #6 in action.


x/playground: falsely detects a deadlock when running Cmd.StderrPipe example code

What version of Go are you using (go version)?
The playground
Does this issue reproduce with the latest release?
Works on latest released web site
What did you do?
Clicked "Run" on the example for Cmd.StderrPipe
What did you expect to see?
It runs
What did you see instead?
fatal error: all goroutines are asleep - deadlock!

goroutine 1 [IO wait]:
internal/poll.runtime_pollWait(0x7efd408c4ee8, 0x72, 0x505300)
	/usr/local/go-faketime/src/runtime/netpoll.go:220 +0x55
internal/poll.(*pollDesc).wait(0xc000104198, 0x72, 0xc00011c001, 0x200, 0x200)
	/usr/local/go-faketime/src/internal/poll/fd_poll_runtime.go:87 +0x45
internal/poll.(*pollDesc).waitRead(...)
	/usr/local/go-faketime/src/internal/poll/fd_poll_runtime.go:92
internal/poll.(*FD).Read(0xc000104180, 0xc00011c000, 0x200, 0x200, 0x0, 0x0, 0x0)
	/usr/local/go-faketime/src/internal/poll/fd_unix.go:159 +0x1b1
os.(*File).read(...)
	/usr/local/go-faketime/src/os/file_posix.go:31
os.(*File).Read(0xc000102018, 0xc00011c000, 0x200, 0x200, 0xc00011c000, 0x0, 0x0)
	/usr/local/go-faketime/src/os/file.go:116 +0x71
bytes.(*Buffer).ReadFrom(0xc000068e88, 0x505200, 0xc000102018, 0x505200, 0x4eb2f0, 0x0)
	/usr/local/go-faketime/src/bytes/buffer.go:204 +0xb1
io/ioutil.readAll(0x505200, 0xc000102018, 0x200, 0x0, 0x0, 0x0, 0x0, 0x0)
	/usr/local/go-faketime/src/io/ioutil/ioutil.go:36 +0xe5
io/ioutil.ReadAll(...)
	/usr/local/go-faketime/src/io/ioutil/ioutil.go:45
main.main()
	/tmp/sandbox971301426/prog.go:21 +0x1ca

Program exited.

This is a bug in the faketime logic. It's now being run in a sandbox that allows interaction with external processes, but the deadlock detector assumes that's not the case, that wakeups can only come up from inside the program. Here the wakeup will come from outside the program.

/cc @andybons @toothrot per owners.

CC @aclements

This doesn't strictly have to come from another process.
e.g., https://play.golang.org/p/YLeam5VkpRZ
This hits the same checkdead throw. Though in this case this is arguably helpful, since the standard behavior would be to hang forever.
Note https://play.golang.org/p/TFCeA6hhJX8 does not fail. This is because there is now a M really running in a syscall, while the original example is fully blocked in netpoll.

The fundamental problem here is that findrunnable immediately stops the M if nothing is ready.
The assumption here (correct me if I'm wrong), is that at this point if none of the netpoll FDs are ready, then only a timer/sleep could be preventing forward progress, and checkdead will jump time to restart progress.
Unfortunately, that simply isn't true in this expanded environment. Situations I can think of where this assumption breaks down:

Waiting on an FD written by a child process (this original bug).
Waiting on a kernel-written FD (timerfd comes to mind).
Waiting on a socket that doesn't have synchronous responses (e.g., some netlink sockets, (maybe) loopback inet sockets).
(Plus probably more)

There are a few options I see:

If netpoll is waiting on an FD, try to jump time, but if there is no jump to be made, just wait like a normal Go program. I feel like this is the best approach, but the behavior will be a bit unpredictable. (e.g., this would make the os.Pipe hang actually turn back into a hang instead of a checkdead throw.

Drop time jumps from netpoll entirely if there are FDs. This is more predictable, but will make some programs that used to work now timeout on the playground, since their sleeps don't necessarily time jump. (This is effectively a partial removal of faketime altogether, which is also an option, but presumably unacceptable).

Make faketime a feature of the sandbox rather than the Go runtime, so it affects all programs equally, and could be removed from the runtime. This is likely quite difficult to make work with arbitrary Linux programs, but something to consider.

(3) is mostly listed as a bit of a strawman, but unless we have some sandbox-wide mechanism, there will always be cases we can't cover. If a subprocess is depending on timing of its input on some level, then faketime in the main Go program is likely to break that interaction.

As long as there is an overall wall time limit on the playground execution, we should probably just implement time as real time there and rip out nearly all the fake time code. We could still make the time when the program begins be reported as the magic date so that caching doesn't look funny.

Is it actually viable to run the playground in real time? I would love to drop faketime. Based on #30439 I thought there were reasons we couldn't just drop it, including the present tool.

AIUI, there is a 5s timeout on playground execution. I'd also love to see faketime gone, but I imagine that would break lots of programs with non-trivial amounts of sleep.

We could instrument the playground to record what fraction of executions use more than 5s of sleep.
Or we could decide those are simply not supported anymore.
I'm honestly OK with either - the playground is for test cases and the like. Hardly any of those need 5s of sleep.

(And the ones that really do need 5s of sleep may not work right with fake time anyway.)


Let -h/--help display also mvnd specific options

The default line length of 80 is really ugly. The client uses JLine, so we do have the terminal width and we should send it to the daemon to properly format the help.  We could add a getTerminalWidth method to the ClientOutput for that and it could be sent as a system property to the daemon (an internal property such as mvnd.terminalWidth).  I'll work on that bit if you want.
Also, we should add a way to document the command line options such as --start, --stop and --status somehow as they seem to be missing from the help.

@ppalaga The default line length of 80 is really ugly.

I agree, and it is even less: 74. I just took the format used by the the stock mvn --help.

The client uses JLine, so we do have the terminal width and we should send it to the daemon to properly format the help. We could add a getTerminalWidth method to the ClientOutput for that and it could be sent as a system property to the daemon (an internal property such as mvnd.terminalWidth). I'll work on that bit if you want.

+1, that would be awesome.

Also, we should add a way to document the command line options such as --start, --stop and --status somehow as they seem to be missing from the help.

Yes, that's not so hard. I plan to work on that.

Is this good to merge then?

@ppalaga I'm working on the terminal width, but if you want to merge before, that's fine with me.


[2.0.1-cherrypick] [#7007]transform params to SPRING_DATASOURCE_XXX

PR #7007
ISSUE #7005

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.1-prepare@36fd0c8). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.0.1-prepare    #7067   +/-   ##
================================================
  Coverage                 ?   32.63%
  Complexity               ?     1604
================================================
  Files                    ?      433
  Lines                    ?    14482
  Branches                 ?     1437
================================================
  Hits                     ?     4726
  Misses                   ?     9293
  Partials                 ?      463

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 36fd0c8...c14cd81. Read the comment docs.


Pressing alt destroys unsaved changes and entire tabs and undo buffer

Atom 0.208.0 on Linux Mint 17.1 Cinnamon

Go to a directory in the shell.
Launch atom from the shell.
Open a file.
Go down a couple screens in the file and type some rubbish without saving.
Press alt.
Observe that the menu is now visible, the unsaved changes in the file are destroyed, the undo buffer is cleared, and the cursor position resets to the first line in the file.

The above steps on an unsaved tab will actually destroy its contents and close it.
Screenshots (sorry, upload doesn't seem to be working for me today):

Enter some rubbish in the buffer: https://img.bi/#/QvT4bXP!exmmkclbatacdtDfbcfaECGqJaWnnajdWyrzicur
Tap alt and see the menu: https://img.bi/#/nbZT9ww!cyeabHOkhxqCozesEnozCaQdgpkwBsziDejKbbBw

I did not observe any errors in the dev console.

Are you able to reproduce in safe mode? atom --safe

@thomasjo, no, the issue does not repro in safemode.

OK, that means it's almost surely caused by a community package. Can you please provide a list of installed packages; apm list --installed (or apm list -i)

I'm a little perplexed as I tested disabling each package (except for the theme, which I switched) but the issue still occurred on each. Here's what I have installed:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Closing this out as it appears to be a third party package problem.
If you open the keybinding resolver using ctrl-. you should be able to see what commands are running when you press alt and that may show which package could be causing this behavior.
Please comment after trying this if this still appears to be a core Atom issue and we can reopen this.

@kevinsawicki I tried again today and I'm sorry for posting earlier (but happy it's resolved), it was the hidpi plugin. As soon as I disabled that, things started working fine. Thanks for the help!


Deal with the case that the app already exists

That app creates a new application everytime you try do it, but the best way to do it is to verify if the app already exists!

Fixing this issue made me realize I was declaring static variables that shouldn't be static. That happened cause Python static declarations are made like this:

Fixing this right now.

Fixed! I had to override the __new__ method, so it looks if a app with the same name already exists before allocating a memory space for it. This link explains the override.

In this version, I'm just looking to apps I have created at that session of the code. I'm working on a version that calls the API in order to discover if the app already exists on the luis you're consuming!


Remove the object-path dependency

Remove the object-path dependency form format package.

Done with https://github.com/fluentfixture/fluentfixture/commit/5ca4334a3aa535d07478f0be193d50102a0d60a5


Support Python 3.13

Guppylang no longer depends on pytket (which determines maximum supported python version), so the guppy constraint should just become ">=3.10".


SignalR JavaScript API

I love these API browsers! Are there plans to add the API documentation for the SignalR client to the new JavaScrip API browser? I think it will be especially necessary to have that when .NET Core 2.1 RTM is released because its jQuery dependency has been removed and there will likely be a lot of changes.

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

ID: 699693b0-9b5d-f166-5519-13cc2908fa1d
Version Independent ID: a0d3294f-1dbe-1fec-1f43-177a66811e30
Content: Release Notes - March 2018
Content Source: teamblog/release-notes-march-2018.md
Service: unspecified
GitHub Login: @dend
Microsoft Alias: danielfe

Yes! We are currently working on onboarding those to docs.microsoft.com.

@stamminator Thanks again for your question.
I'm closing this issue as resolved.
Please feel free to re-open if/as needed with additional blog feedback.


Add SveteKit example (bis)

Nice👌. How about we add some tests to ensure the demo will work moving forward?

One last issue beside that I still have, when I start the prod build I get the following message:
[14:47:46.617][/examples/svelte-kit][pnpm run test:preview][stderr] The following Vite config options will be overridden by SvelteKit:
  - build.outDir

The e2e test fails because of this message, but everything is actually generated as it should be.

The following Vite config options will be overridden by SvelteKit

That should be easy to fix. Let me try.

The following Vite config options will be overridden by SvelteKit

That should be easy to fix. Let me try.

Done.
The CI is still failing on Windows; does SvelteKit support Windows? The CI logs suggest that it doesn't.
Otherwise the CI is green!
To make TypeScript happy I checked .svelte-kit/types/ into the repository. Is that a recommended approach, or should we generate the types before running the tests?

To make TypeScript happy I checked .svelte-kit/types/ into the repository. Is that a recommended approach, or should we generate the types before running the tests?

I modified it so that it generates them before the tests.

Neat 👍.
Let me make a final review tomorrow.

I've done some changes, most notably I've rebased the example on top of a more minimalistic SvelteKit boilerplate.
I actually prefer the one you chose, but the long term strategy is to regularly rebase the example on top of an official SvelteKit boilerplate — using the minimal one reduces maintainability cost.
Let me know what you think. From my side the PR is now ready to be merged.
I'll create that little boilerplate generator script npm init telefunc@latest --svelte-kit that copy-pastes examples/svelte-kit sometime this/next week.

I actually prefer the one you chose, but the long term strategy is to regularly rebase the example on top of an official SvelteKit boilerplate — using the minimal one reduces maintainability cost.

That's a good move.

Let me know what you think. From my side the PR is now ready to be merged.

LGTM :rocket:

Thanks for the review of the review :-). Looking forward to see the SvelteKit-Telefunc combo in the wild.


Endpoints 20H1 & 22H2

There is no page set up that talks about endpoints for version 20H1. The applies section of the previous or next release near to them does not say that applies to 20H1 and 20H2 for example.
Does 20H2 and Win 11 endpoint links applies for 20H1 and 22H2?

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

ID: 1ba43b5f-dd62-9634-fe8b-c10755456df8
Version Independent ID: 1ba43b5f-dd62-9634-fe8b-c10755456df8
Content: Connection endpoints for Windows 10 Enterprise, version 21H2 - Windows Privacy
Content Source: windows/privacy/manage-windows-21h2-endpoints.md
Product: windows-client
Technology: itpro-privacy
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Main

Not merging this PR because WEBAPP_PORT isn't needed when running in Docker, and I'd prefer not to include IDE-specific files in the repo. Please feel free to submit other improvements or bug fixes, though.


Nick: Watch gbinsta.net

Nick requests the watch of the watch_keyword gbinsta\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

gbinsta\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


DBZ-766 Implement PgOutput logical decoder for Postgres 10+

https://issues.jboss.org/browse/DBZ-766
@gunnarmorling @jpechane, this PR is very much still a WIP but I wanted to go ahead and get my work out in the open with you guys so you could go ahead and begin digesting the changes and potentially offering some feedback on some choices I've made which I'd like to find better alternatives for.
That said there are a few caveats:

The dbz_publication right now gets created automatically still using for all tables.  We obviously want to change this for the long-term but for the sake of having a PoC I left it as is.  It should be simple enough to hook into the PostgresSchema and build the publication based on the list of filtered tables should the publication not yet exist during connector startup.

Since the pgoutput logical replication stream does not indicate a column's optionality state and we discussed simply setting all columns as optional, a number of tests were modified to alter the optionality of the built schema based on whether this decoder was being used or one of the others.  I'm not sure if either of you have an opinion on that, but just wanted to point it out.

The PgOutputMessageDecoder maintains some schema map-based lookup state that I have not yet integrated with the actual PostgresSchema.  I felt since this was isolated to this particular decoder, it made more sense to keep it in the decoder until we were sure this satisfies all our needs.
There are 2 maps maintained by the decoder, relationIdMetadata and tableIdByRelationId.  The former map acts as a RELATION message cache so when relation messages are received they'll be stored in this map and as an INSERT, UPDATE, or DELETE operation comes over the stream for that relation-id, the entry will be consumed.  In theory this former map should always be empty over the complete duration of the replication connection.  The latter map is used to maintain the lookup between a relation-id provided by the pgoutput decoder stream and a schema TableId.  This is the part that we discussed integrating with PostgresSchema long-term.

There are also a few other things I want to point out here that you guys may have better suggestions on how to do these things that are cleaner and more appropriate.

Inside ColumnMetaData I ended up doing some type modifier calculations with the PostgresType.  I'd like to somehow consolidate this better with TypeMetadataImpl and PostgresType.  The reason I did it slightly different for now was that we only delegate length/scale calls to the postgres TypeInfo inside PostgresType for specific OIDs.  I wanted to better understand why this limitation exists in the first place so rather than impact other decoders, I exposed a slight one-off for this PoC.

I have some code dupe from RecordsStreamProducer in the PgOutputMessageDecoder which I don't particularly like.  I need to spend some time trying to find a better way to handle this, any insight or suggestion here would be very welcomed.

The PgOutputMessageDecoder several constructor arguments that are only applicable to it and not the other implementations.  I'm wondering if we could come up with a better way to feed these into the decoders?   I was thinking perhaps a MessageDecoderContext object.  I'm a much bigger fan of parameter objects rather than a long list of passed arguments.  Other ideas?

Look forward to hearing your feedback.

Great news, thanks a lot, @Naros!
@jpechane, could you take a look at this one? I'll do too, but a first pass from you would be much appreciated. Thanks!

@jpechane I'm working on fetching the optional state out-of-band and once I have that done I'll push the changes, which should obsolete your comments about JdbcConnection and TestHelper.  That should allow me to hopefully revert all the optionality changes made to tests.

I'm a much bigger fan of parameter objects rather than a long list of passed arguments.

+1

This also needs a rebase to the latest master.

@Naros I've looked at the failed tests

OutboxEventRouterIT is prone to start race condition, I propose to add one record that will be snpashotted and wait for it, should solve the problem
io.debezium.connector.postgresql.connection.ReplicationConnectionIT.testHowRelationMessagesAreReceived() is tough nut to crack. I've not found anything problematic in the code but when I run the test roughly 30 times locally I got 2 times the same failure as was on Jenkins so there is definitely something wrong

@jpechane Applied the snapshot check to the few methods that were prone to the race condition in commit  https://github.com/debezium/debezium/pull/956/commits/6b1cee5c02f6e462c9b0df196a83442641485336 and that seems to have solved that problem as well; great suggestion!

@Naros We are done, thanks! Please just squas everything into a single commit and I'll merge it. When I tried squasing myself I ended up with a commit authored by Gunnar which is not exactly correct in this case :-)

I've rebased against master again and implemented some small changes to work with changes that were merged as a part of https://github.com/debezium/debezium/pull/976.  This should be all set now.

@Naros Merged, great piece of work, thanks!


Why is it impossible to use pinch to zoom ?

I'm using turbo-android and I'd like to allow users to zoom-in some images.
How can I do that ?
I've checked the viewport: <meta content="width=device-width, initial-scale=1, user-scalable=1" name="viewport">
Tried to use webView.settings.setSupportZoom(true) without success.

We use the following viewport attributes in the HEY app when we conditionally enable page zoom:
width=device-width, initial-scale=1, maximum-scale=2.5

Additionally, on the Android side, we set:
webView.settings.builtInZoomControls = true
webView.settings.displayZoomControls = false

Thanks a lot. indeed it's working now.


Install clippy and rustup in nightly_lints

In the nightly lints example the clippy and rustup components were not added like in the rest of the examples. This adds the installation so everything runs.

That was a ridiculous mistake, thank you very much!


Glauth Backend and Fallback Servers env variable name and flag name inconsistent

Glauth can be configured to take fall back end backend servers via env variable or command line flag.
While the Environment variable is in Plural, the command line flag is in singular which might lead to confusion.
GLAUTH_BACKEND_SERVERS vs --backend-server
GLAUTH_FALLBACK_SERVERS vs --fallback-server
https://github.com/owncloud/ocis/blob/f9e1b7be9499c51497cb45252cf9874f746a4b98/glauth/pkg/flagset/flagset.go#L209
https://github.com/owncloud/ocis/blob/f9e1b7be9499c51497cb45252cf9874f746a4b98/glauth/pkg/flagset/flagset.go#L212
https://github.com/owncloud/ocis/blob/f9e1b7be9499c51497cb45252cf9874f746a4b98/glauth/pkg/flagset/flagset.go#L268
https://github.com/owncloud/ocis/blob/f9e1b7be9499c51497cb45252cf9874f746a4b98/glauth/pkg/flagset/flagset.go#L271

glauth service was removed from ocis, therefore no longer valid


Kaun Banega Crorepati web added #2406

Title and Issue number

Kaun Banega Crorepati Web Added #2406
Close #2406

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

@MohitGupta121
Kindly merge it. (No images folder exist)


issue creating web app with sandbox subscription

The issue text was copied to the clipboard.  Please paste it into this window.

Does this occur consistently?
Repro steps:

Action: appService.CreateWebApp
Error type: AuthorizationFailed
Error Message: The client<EMAIL_ADDRESS>with object id '706f193a-e0b1-4ab9-94d1-e99847081f67' does not have authorization to perform action 'Microsoft.Web/serverfarms/read' over scope '/subscriptions/ad6d4767-abfb-4459-938a-55a306750cfa/resourceGroups/appsvc_linux_centralus/providers/Microsoft.Web/serverfarms/appsvc_linux_centralus' or the scope is invalid. If access was recently granted, please refresh your credentials.
Version: 0.17.0
OS: darwin
OS Release: 19.5.0
Product: Visual Studio Code
Product Version: 1.45.1
Language: en

Call Stack
extension.bundle.js:225:3583434
retryCallback extension.bundle.js:225:116429
retryCallback extension.bundle.js:157:31051
extension.bundle.js:157:32664
handleRedirect extension.bundle.js:171:7747
extension.bundle.js:157:29836
Request._callback extension.bundle.js:1:584810
Request.r._callback.r.callback.r.callback extension.bundle.js:201:4468
Request.emit events.js:203:13
Request.<anonymous> extension.bundle.js:201:17577
Request.emit events.js:208:15
IncomingMessage.<anonymous> extension.bundle.js:201:16367
Object.onceWrapper events.js:291:20
IncomingMessage.emit events.js:208:15
endReadableNT _stream_readable.js:1168:12
processTicksAndRejections task_queues.js:77:11

Dupe of https://github.com/microsoft/vscode-azureappservice/issues/1490. As a workaround, try "Advanced" create - which should give you more options that might work for your subscription


New release 0.1.6

The HISTORY.rst is different from PyPI because I constantly forget ReStructuredText is not Markdown.

PyPI

:scream: oh my