Creating kernel extensions that are not part of other nuget packages

This is related to dotnet/try#395
Adding extensions to nuget packages like XPlot in the interactive-extensions/dotnet/cs has been implemented and the use case for that is when you want to extend the kernel with respect to a particlay nuget package. This scenario makes perfect sense.
However, there is another set of scenarios where a user might just want to extend  the kernel and not be specific to any library, for example, adding a magic command for %%time. (I think this is similar to the tools in F# cc @KevinRansom ).If I write such an extension, how do I distribute it? The most obvious answer is via a nuget package. But what would be the structure of that nuget package?
MyKernelExtension
    2.0.0
          lib/netstandard2.0/MyKernelExtension.dll

OR
MyKernelExtension
   2.0.0
          interactive-extensions/dotnet/cs/MyKernelExtension.dll

For the first case, we will have to add a functionality to #r nuget to look for IKernelExtension types in each metadata reference that it is adding and load them. While this approach looks appealing it will potentially make #r nuget slower.
In the second case, since there is no "lib" folder, how will we find the path to the nuget package on disk ?(Currently we use the metadata reference to find the base path to the nuget package C:\Users\.nuget\packages\Xplot\2.0.0\lib\standard2.0\Xplot.dll is used to find the path C:\Users\.nuget\packages\Xplot\2.0.0\ and search for extensions in it)

A third approach that I can think of is that for loading "stand-alone" extensions(ones that are not related to any specific library, like the magic commands), we use the #extend directive or potentially a %%load_ext magic command so the user would do
%%load_ext MyKernelExtension

This would download the extension nuget package and then look for the IKernelExtension types in the metadata references and add them. This would make it a cleaner way to write such extensions and users know explicitly that this nuget package is for the purpose of a KernelExtension.
This will also help us clearly specify that :

If the extension is part of some other nuget package, then you should follow this convention(interactive-extensions\dotnet\cs) and just do #r to consume it.
Else if the extension is not related to any other library, use %%load_ext to use it.

Closing this, as both extension types (library enhancement and extension-only packages) are implemented.
We don't believe loading an extension by means other than NuGet is needed at this time.


Real Time Chat Application using socket.io

Issue Type:

[ ] Bug Report
[x] Feature Request
[ ] Documentaion

Describe the bug
Real Time Chat Application using socket.io and node js with UI in Html CSS and Java Script . As This repository is for  JS project , so it should something like a Real Time Chat application which have a beautiful UI and allow multiple users at a Same Time . This project will enhance the repo and node js skills

A clear and concise description of what the bug is.

Possible solution

Describe the solution you thought of.
So In this I am Going to develop a Real Time Chat application from which we can have a chatting experience as same as WhatsApp with beautiful UI , Apart from this It will also support multiple users at same time . Users should enter there name and start chatting , without entering they cannot start there chatting .

Screenshots

If applicable, add screenshots to help explain your problem.

Okay

Hye Myself Pawan Sharma GSSOC 22 . I have open This request and I want to contribute to it . plz assign this to me


[Accessibility] [Screen Reader] Fix the Connect Service dialog to be read by the screen reader

Fixes ADO Issue: #64726
Describe the issue
If users select Add Language Understanding (LUIS) and dialog get open but the screen reader does not announce open dialog information, then it would be difficult for users to understand after the dialog was opened or not.
Actual behavior:
After selection of Add Language Understanding (LUIS) control dialog gets open but open dialog information does not provide by the screen reader.
Expected behavior:
After selection of Add Language Understanding (LUIS) control dialog gets open but open dialog information does not provide by the screen reader.
Repro Steps:

Open Bot Framework Emulator installed on the system.
Bot Framework Emulator Application with Welcome screen opens.
Navigate on the welcome screen and select Create a New BOT configuration link.
New BOT Configuration dialog opens.
Navigate on the dialog and enter inputs in edit fields then select the save and connect button.
Navigate to BOT Explorer on the left pane and select it.
Bot Explorer Pane opens, navigate to + icon on services section and select it.
Menu for services opens, navigate to the "Add Language Understanding (LUIS)" menu item and select it.
Add Language Understanding (LUIS) dialog opens, navigate on the dialog.
Verify the screen provide open dialog information or not.

Changes included in the PR

Added a focusable div element to allow the screen reader to announce the dialog content

Screenshots
Test cases executed successfully

Coverage remained the same at 67.76% when pulling 57d37918572edd54719c0552d8c294452a2deba0 on southworks:external/southworks/fix/luis-dialog/dialog-content-announcement into 3310e57c55425b845a313a227a1eac849002aafa on microsoft:main.


Allow NotificationActionButton to accept href

Much like how <Button /> can accept an href prop, I would like to be able to pass href to <NotificationActionButton /> that way I can render a high-contrast hyperlink within an <InlineNotification />.
My workarounds are either:

Use <InlineNotification lowContrast /> so that links appear more visibly.
navigate the page via on:click on the current <NotificationActionButton />.

I can contribute a PR if this proposal is accepted.

As a whole, I don't seem any harm in allowing the close button to be an anchor link with the button styles.
Could you clarify how the href would improve hyperlink text rendering if it only applies to the button?

that way I can render a high-contrast hyperlink within an <InlineNotification />

At the time of posting, I didn't notice that <NotificationActionButton> is really <Button> that accepts everything <Button> accepts as $$restProps, which includes href.
The issue I should have highlighted involves colour contrast. After some brief research, I learned that the colour blue is problematic when applied to text on dark backgrounds. Reference: https://www.uxmatters.com/mt/archives/2007/01/applying-color-theory-to-digital-displays.php
Consider this example: https://svelte.dev/repl/1ef79fc3dc284347abc77ebe8c3ff430?version=3.54.0

When compared with React version of <Link />, I noticed it has a different blue colour (reference) that is closer to WCAG AAA, see sample. It may have to do with using white.css with a normal dark <InlineNotification>, so the <Link> uses it's light-themed blue colour.


Subset update_or_create error

Describe the bug
An exception is thrown when using the subset update_or_create function.
TypeError: unsupported operand type(s) for ** or pow(): 'bool' and 'dict'
Looks like it's missing a comma:
return self.update(subset=subset, private=private ** kwargs)
Version
TM1py 1.5.0

Thanks for the catch! It's fixed


Create Python3-Dice_rolling-clashofclane.py

hey @Aman22sharma please merge my pull request.

please @Aman22sharma merge my pull request.


Update references to consensus spec

It might be worth updating the consensus-specs link to so that they both point to their respective master branches.

I don't think it good to point to master branch unless there are no tagged versions. We have a bunch of references to the consensus spec, e.g. in the README
https://github.com/ChainSafe/lodestar/blob/3f3a207643f6c35ae4b3cfe683cd167cfe70a2c3/README.md?plain=1#L8
All those references are kinda outdated as we already test against v1.4.0 (which has no major release yet) but could at least update to v1.3.0
https://github.com/ChainSafe/lodestar/blob/3f3a207643f6c35ae4b3cfe683cd167cfe70a2c3/packages/beacon-node/test/spec/specTestVersioning.ts#L18
Originally posted by @nflaig in https://github.com/ChainSafe/lodestar/issues/6126#issuecomment-1824524736

Yeah the problem with pointing to master is that a lot of references in our code point to a specific tagged version of the consensus-specs for greater accuracy. We should be more proactive with updating these references though, outside of hard forks or another significant milestones (~1/year at this rate).

I'll track this for around January. We should aim to do this sometime around each hard fork. Given that January/February we will be starting the transition to Deneb, we should update then.


1.12.2 not supported

1.12.2 shows "Outdated server" on connect and does not show the version in the server list.

My guess'd be that the server doesn't accept 1.12.2 clients.

@jamierocks The ping in the server list also shows a red cross, which should be fully handled by Waterfall itself.

This is handled by BungeeCord not Waterfall though

If the server doesn't accept 1.12.2 clients, bungee nor waterfall is going to help you.
Unless you can provide some more info, I'm closing this.


Use setup.cfg over setup.py

This breaks distutils support which might be wanted in some scenarios when bootstrapping, so I am -1.

Can you detail such use cases? The way I know distutils is not planned to be supported going ahead (@pganssle can confirm this). It certainly did not cause issues for virtualenv. Even in cases where you don't have access to setuptools, you can just use the wheel we'll publish.

I agree distutils should not be used by anyone, but there are some scenarios where we might not have setuptools. Distributions like arch prefer to build from source than using distributed wheels. Using distributed wheels is not even an option when the package is not pure.
I would be slightly inclined the other way if this provided any kind of improvement other than just storing the metadata in a nicer way.

Let's agree to disagree on this too, I'll not push on it if you feel so strongly about it.

Bootstrapping python envrionments from scratch is already a pain, I don't want to make it even harder :smile:.

Bootstrapping python envrionments from scratch is already a pain, I don't want to make it even harder 😄.

If you're worried about this IMHO we should be removing setuptools dependency entirely, and use distutils only. Otherwise, we're telling a blatant lie to ourself: that we fallback to distutils and it works. In the current CI we never test this, so we have exactly 0 confidence in this. We'll never know if we use a flag that doesn't work with distutils, until we release and someone gets back to us complaining.

Bootstrapping python envrionments from scratch is already a pain, I don't want to make it even harder 😄.

Didn't we introduce the no isolation build for this? I'd expect one would resolve to bootstrap this project the same way. Install our build dependencies from pyproject.toml and then start building this package.

@gaborbernat I also was thinking to use setup.cfg instead of setup.py, but I assumed that the context here is that @FFY00 is an Arch Linux maintainer involved in packaging Python, and all these Linux distros have weird rules about what tools need to be built from source.
They'll have to solve the problem of "Python doesn't have distutils in it anymore" at some point after this PR is merged and we start the process of removing distutils from Python in favor of setuptools, but I think the point here is that, at least at the moment, it would presumably be convenient if at least some version of build could be built without any dependencies (including setuptools).
I think this is a pretty simple package, though. Depending on the needs of the Linux distro packaging community, possibly the best thing to do in the long term would be to keep a hard setuptools dependency for building the sdist, but customize include additional information in the sdist that would allow for a zero-dependency wheel-building or installation step.
That said, I don't know how important it is to be able to do a zero-dependency build of this package. Actually using the package requires the pep517 library, which is built with flit, and flit has run-time dependencies on a few packages that have hard build-time dependencies on setuptools, so I don't think that "bootstrap build so that you can build setuptools" will be a feasible strategy right now anyway.
Presumably @FFY00 has more information here. If a hard requirement on setuptools is actually going to be a problem for distro packagers, then I think it's reasonable to keep this compatible with distutils while distro packagers figure out what their setup will look like in a post-distutils world. If there's no immediate practical value to this, I'm inclined to ditch setup.py entirely now as we explore options that will ease the burden on distro packagers.

then I think it's reasonable to keep this compatible with distutils

If we do this we might as well use for now distutils as the primary... and add setuptools as fallback once https://github.com/pypa/setuptools/pull/2143 lands. I'm ok with not using setuptools for this if bootstrapping is an issue, but then we should drop setuptools entirely, and test only with distutils. In the current form, the fallback to distutils is a wish at best, and not guaranteed to work.

If we do this we might as well use for now distutils as the primary... and add setuptools as fallback once pypa/setuptools#2143 lands. I'm ok with not using setuptools for this if bootstrapping is an issue, but then we should drop setuptools entirely, and test only with distutils. In the current form, the fallback to distutils is a wish at best, and not guaranteed to work.

I disagree strongly with this. If we keep distutils support at all, we should just test that whatever feature of build it's important to use it for works if you build it with distutils, but distutils doesn't support stuff like python_requires, and generally speaking has a ton of bugs in it that wouldn't be acceptable either for people installing from sdist or for us when building the wheel. The kind of people who care about building this with distutils will probably not care about at least some of those problems (like python_requires), and will have specific workarounds for others. The vast majority of people should be either building with setuptools or (even more preferable) consuming a wheel built with setuptools.

Fair enough, but long story short if we claim distutils support we should validate that subset, or drop supporting it.

I personally the way things stand to vote for removing support for it unless @FFY00 can describe an actual use case where without is not possible.

and all these Linux distros have weird rules about what tools need to be built from source

For arch is simple, everything should build from sources. There are some exceptions for cases where this is not possible, like proprietary tools.
I am not going to dive into how to bootstrap the dependency tree for Linux distributions since there are several different workflows that can be chosen. It is possible to build this project with setuptools instead of distutils when bootstrapping, but it might impact the amount of effort needed, depending on the particular workflow.
I am not opposed to drop support for distutils, I just don't think having a slightly nicer way to declare metadata is compelling enough.
@pganssle btw, pep517 needs flit_core, not flit. flit_core has no runtime dependencies and can build itself.
Anyway, I am -1 on this. I don't really think we should remove it, but I have no issue if it is removed. In arch, we can bootstrap using setuptools.

I think we should remove it until someone has an actual use case where using setuptools is not possible, or alternatively keep it but then add tests to validate it actually works.

I re-triggered the tests, codecov is now fixed.

I really don't have enough insight into how much more difficult this would make the lives of distro maintainers, so it's hard for me to have a strong opinion on it.
One way to "split the baby" is to use setuptools unconditionally, but also not migrate everything to setup.cfg, so that if distro maintainers want to patch the sdist to make it easier to bootstrap with distutils, it's a simpler change for them. Of course, that would be "best effort". That might be worse than doing nothing, though.
I also think that if we do want to switch to declarative metadata, we'll want to switch to PEP 621 in ~a few months (or whenever support for PEP 621 lands in setuptools), so I'm not as gung-ho about setup.cfg as I would have been a few months ago.
Sorry I can't be more definitive, I just don't feel like I have enough information.

If @gaborbernat is super keen on making this change, I am willing to accept it.

If @gaborbernat is super keen on making this change, I am willing to accept it.

The alternative of testing distutils is painful and troublesome enough that I would not worry about supporting distutils until someone comes and presented a case where it's impossible to provision setuptools instead. I'd expect all distributions by now figured out how to inject setuptools given it's popularity, so I'd not expect this to be a problem. And @FFY00 just confirmed this for Arch. So I yes let's merge this if someone is willing to approve it.


Add Flox to installation options

I've test out installing localsend with Flox, and it worked.
It currently doesn't have a webpage where you can view the package, but these are the commands I ran to make it work.
$ flox init
✨ Created environment 'tmp.jAEYbDjIqo' (aarch64-darwin)

Next:
  $ flox search <package>    <- Search for a package
  $ flox install <package>   <- Install a package into an environment
  $ flox activate            <- Enter the environment
  $ flox edit                <- Add environment variables and shell hooks

$ flox install localsend
✅ 'localsend' installed to environment 'tmp.jAEYbDjIqo'
$ flox activate
✅ You are now using the environment 'tmp.jAEYbDjIqo'.
To stop using this environment, type 'exit'

flox [tmp.jAEYbDjIqo] $ localsend
flutter: dynamic_color: Accent color detected.
...

Hi, according to https://github.com/flox/flox, Flox is using Nixpkgs as repository for its packages. Since you also cannot provide the exact URL of the LocalSend package on Flox, I think that adding Flox seem to be redundant. Nix is already mentioned there (it should be added to macOS too)

This makes sense, I'll close the PR to not clutter the list. 😊


Understanding loss landscape

I understood that in the loss landscape visualization the z-axis is NLL. I'm curious what the x-axis and y-axis mean. Of course, we can see in loss_landscapes.py how the x and y values participate in the calculation, but I don't have an intuitive understanding of it.
    xs = np.linspace(x_min, x_max, n_x)
    ys = np.linspace(y_min, y_max, n_y)
    ratio_grid = np.stack(np.meshgrid(xs, ys), axis=0).transpose((1, 2, 0))
    print(ratio_grid)
    metrics_grid = {}
    for ratio in ratio_grid.reshape([-1, 2]):
        print(ratio)
        ws = copy.deepcopy(ws0)
        gs = [{k: r * bs[k] for k in bs} for r, bs in zip(ratio, bases)]
        gs = {k: torch.sum(torch.stack([g[k] for g in gs]), dim=0) + ws[k] for k in gs[0]}
        print(gs)
        model.load_state_dict(gs)

        print("Grid: ", ratio, end=", ")
        *metrics, cal_diag = tests.test(model, n_ff, dataset, transform=transform,
                                        cutoffs=cutoffs, bins=bins, verbose=verbose, period=period, gpu=gpu)
        l1, l2 = norm.l1(model, gpu).item(), norm.l2(model, gpu).item()
        metrics_grid[tuple(ratio)] = (l1, l2, *metrics)

    return metrics_grid

Thank you sincerely.

Hi @SonHyegang, thank you for reaching out and raising a great question. Sorry for the late reply; this week was pretty hectic for me.
Essentially, we utilize two randomly initialized neural networks as the bases, or simply x- or y- axes, for the visualizations of the loss landscape. In other words, intuitively speaking, the boundaries of these visualizations can be correspond to the random initializations of the neural networks. Likewise, the training trajectories of the neural network can be conceptualized as paths from these boundaries to the center of the visualization. I hope this helps you.


[BUG] Instability after power failure

Describe the bug

After recovering from a cluster power failure, longhorn pods are frequently OOM killed, and high load average on nodes causes nodes to be not ready.
Support bundle for troubleshooting
Generating a support bundle via the UI got stuck at 16%, but was able to copy what looks like a complete zip from the support bundle pod.

Environment

Longhorn version: 1.7.2
Impacted volume (PV): I've scaled down some workloads attempting to improve stability. As far as I can tell, volumes still attached seem to be okay.
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s v1.31.2+k3s1

Number of control plane nodes in the cluster: 1
Number of worker nodes in the cluster: 7

Node config

OS type and version: debian 12
Kernel version: 6.1.0-28-amd64, 6.1.21-v8+
CPU per node: 4 nodes - 4 core amd64, 4 nodes - Raspberry PI 4 arm64
Memory per node: amd nodes 16GB, arm64 nodes 8GB
Disk type (e.g. SSD/NVMe/HDD): SSD
Network bandwidth between the nodes (Gbps): 1Gbps

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): baremetal
Number of Longhorn volumes in the cluster: 32

Additional context

Workaround and Mitigation

@a01fe Which pods experienced the OOM?
cc @mantissahz (community coordinator)

Did the Longhorn pods have high memory usage?

Not before power failures last week during a storm. Now there lots of these in each node's logs:
Dec 15 21:15:16 k3ss01 kernel: Out of memory: Killed process 1854636 (longhorn) total-vm:1993060kB, anon-rss:19824kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:248kB oom_score_adj:999
Dec 15 21:15:16 k3ss01 kernel: Out of memory: Killed process 1854544 (longhorn) total-vm:1992804kB, anon-rss:17336kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:248kB oom_score_adj:999
Dec 15 21:15:16 k3ss01 kernel: Out of memory: Killed process 1954374 (longhorn) total-vm:2066792kB, anon-rss:18208kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:252kB oom_score_adj:999
Dec 15 21:15:16 k3ss01 kernel: Out of memory: Killed process 2056802 (longhorn) total-vm:2066792kB, anon-rss:19444kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:268kB oom_score_adj:999
Dec 15 21:15:16 k3ss01 kernel: Out of memory: Killed process 11709 (longhorn) total-vm:2279860kB, anon-rss:19488kB, file-rss:4kB, shmem-rss:0kB, UID:0 pgtables:384kB oom_score_adj:999
Dec 15 21:15:16 k3ss01 kernel: Out of memory: Killed process 7410 (longhorn-instan) total-vm:9518844kB, anon-rss:3324324kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:10088kB oom_score_adj:999

Can you provide the pods' CPU and Memory metrics over time?

I had scaled down prometheus along with other non-essential workloads to see it would help with stability. I'll scale it back up and and try to get this.

Which pods experienced the OOM?

longhorn-manager:
$ kubectl get -n longhorn-system pod -o json | jq '.items[] | .status.containerStatuses[] | select(.lastState.terminated.reason == "OOMKilled") | .image'
"docker.io/longhornio/longhorn-manager:v1.7.2"
"docker.io/longhornio/longhorn-manager:v1.7.2"
"docker.io/longhornio/longhorn-manager:v1.7.2"
"docker.io/longhornio/longhorn-manager:v1.7.2"

What are your workloads? Any steps to reproduce the case?

At this point, I haven't found any steps to not reproduce the problem 😹 I've scaled back as many non-essential workloads as I can, and I still wind up with nodes with load averages > 150.
I'm not sure if this was the case before the "event", but I've noticed that there are lots of "Pending" lhb resources.
$ kubectl get lhb -n longhorn-system | grep Pending | wc -l
    3697

Is this normal?

longhorn-manager seems impossible to use too much memory. Are you using RWX volumes?

Looking through the volumes.yaml, all 31 volumes are accessMode: rwo  No RWX, anyway.
One interesting thing is that there are 4,422 backups in backups.yaml.  Also there is a lot of logging in the longhorn-manager logs about this kind of failure:
2024-12-14T12:52:16.635079681-08:00 time="2024-12-14T20:52:16Z" level=warning msg="Failed to get the snapshot daily-ba-98b8345e-33e2-4f4b-ae43-aab13ff8671c in volume pvc-facc4660-55ff-42b6-bc5d-c00ad44bf7e2 when syncing backup status" func="controller.(*BackupController).syncBackupStatusWithSnapshotCreationTimeAndVolumeSize" file="backup_controller.go:901" controller=longhorn-backup error="<nil>" node=k3sa02
2024-12-14T12:52:16.636694412-08:00 time="2024-12-14T20:52:16Z" level=warning msg="Waiting to enable the backup monitor for backup backup-0e76a120bcaa4a0c" func="controller.(*BackupController).reconcile" file="backup_controller.go:414" backup=backup-0e76a120bcaa4a0c controller=longhorn-backup error="failed to get the snapshot daily-ba-98b8345e-33e2-4f4b-ae43-aab13ff8671c before enabling backup monitor: snapshot.longhorn.io \"daily-ba-98b8345e-33e2-4f4b-ae43-aab13ff8671c\" not found" node=k3sa02

I'm not using RWX volumes.
Here's memory usage on one amd64 node, other amd64 nodes look similar.

Memory usage on an arm64 node:

longhorn-manager memory usage:

instance-manager memory usage:

Would you pick up a random longhorn-manager and export its pprof heap result?:

Forward the pprof port for the longhorn manager:

kubectl -n longhorn-system port-forward <longhorn manager pod name> 6060:6060

Get the heap profiling file:

wget -O heap.out "http://localhost:6060/debug/pprof/heap"

Upload the profiling result to this ticket. Of course, you can directly check it as well

go tool pprof heap.out
(pprof) web

Here's one about an hour after restarting all the nodes.
heap.out.tar.gz

Here's another from a longhorn-manager pod using 7G.
heap-4v5fd.out.tar.gz
NAME                     CPU(cores)   MEMORY(bytes)
longhorn-manager-4v5fd   355m         7052Mi
longhorn-manager-77cdj   59m          2997Mi
longhorn-manager-hgtzw   171m         766Mi
longhorn-manager-qvbc4   27m          2733Mi
longhorn-manager-s8lnm   36m          1625Mi
longhorn-manager-sq9vq   56m          1519Mi
longhorn-manager-srjlz   49m          1267Mi
longhorn-manager-zqbtf   53m          1414Mi

Sure looks like a repeated GRPC call that is accumulating buffer space and not completing, likely related to the backup monitor that is unable to start.  In the source for longhorn/longhorn-manager, synced to tags/v1.7.2,
ith longhorn/longhorn-manager synced to tags/v1.7.2, do

/repos/Longhorn/longhorn-manager$ go tool pprof --source_path=. <path-to-9978>/heap.out>
File: longhorn-manager
Type: inuse_space
Time: Dec 17, 2024 at 6:49pm (MST)
Entering interactive mode (type "help" for commands, "o" for options)
(pprof) top
Showing nodes accounting for 493.20MB, 80.00% of 616.50MB total
Dropped 422 nodes (cum <= 3.08MB)
Showing top 10 nodes out of 113
      flat  flat%   sum%        cum   cum%
  193.92MB 31.46% 31.46%   193.92MB 31.46%  bufio.NewReaderSize (inline)
  185.65MB 30.11% 61.57%   185.65MB 30.11%  google.golang.org/grpc/internal/transport.newBufWriter (inline)
   35.10MB  5.69% 67.26%    35.60MB  5.78%  sigs.k8s.io/json/internal/golang/encoding/json.(*decodeState).literalStore
   26.01MB  4.22% 71.48%    26.01MB  4.22%  runtime.malg
   12.51MB  2.03% 73.51%    12.51MB  2.03%  reflect.mapassign0
    9.50MB  1.54% 75.05%   402.08MB 65.22%  google.golang.org/grpc/internal/transport.newHTTP2Client
    8.51MB  1.38% 76.43%     8.51MB  1.38%  reflect.unsafe_NewArray
    8.50MB  1.38% 77.81%     8.50MB  1.38%  google.golang.org/grpc/internal/buffer.NewUnbounded
       7MB  1.14% 78.95%     9.50MB  1.54%  context.(*cancelCtx).propagateCancel
    6.50MB  1.05% 80.00%    15.50MB  2.51%  context.withCancel (inline)

And the top two have only grown in the later pprof, up to a combined 1.5 GB
~/repos/Longhorn/longhorn-manager$ go tool pprof --source_path=. <path-to-9978>/heap-4v5fd.out

(pprof) top
Showing nodes accounting for 2440.20MB, 85.21% of 2863.92MB total
Dropped 400 nodes (cum <= 14.32MB)
Showing top 10 nodes out of 102
      flat  flat%   sum%        cum   cum%
  779.84MB 27.23% 27.23%   779.84MB 27.23%  google.golang.org/grpc/internal/transport.newBufWriter
  774.67MB 27.05% 54.28%   774.67MB 27.05%  bufio.NewReaderSize
  331.14MB 11.56% 65.84%   331.14MB 11.56%  runtime.malg
  121.01MB  4.23% 70.07%   121.01MB  4.23%  google.golang.org/grpc/internal/buffer.NewUnbounded (inline)
  109.01MB  3.81% 73.87%   109.01MB  3.81%  google.golang.org/grpc/internal/transport.(*controlBuffer).get
   84.01MB  2.93% 76.81%   205.02MB  7.16%  google.golang.org/grpc/internal/grpcsync.NewCallbackSerializer
   81.51MB  2.85% 79.65%    81.51MB  2.85%  context.(*cancelCtx).Done
   68.51MB  2.39% 82.04%   142.51MB  4.98%  context.withCancel
   52.01MB  1.82% 83.86%    77.01MB  2.69%  context.(*cancelCtx).propagateCancel
   38.51MB  1.34% 85.21%    38.51MB  1.34%  golang.org/x/net/http2/hpack.(*headerFieldTable).addEntry

So it seems clear that there is a leaked GRPC connection in the backup monitoring code, which needs some more poking around.
However, the reason so many efforts are made is because so many backups are pending.  Out of the 4,422, the breakdown by state looks like:
grep state: backups.yaml | sort | uniq -c
    682       state: Completed
     21       state: Error
      1       state: "null"
   3718       state: Pending

And all the pending ones have a message like this:
      messages:
        info: Failed to get the Snapshot daily-ba-d559efa4-d1d2-41b9-8d71-2292a2957b7c
      newlyUploadDataSize: "null"
      ownerID: k3ss01
      progress: 0
      reUploadedDataSize: "null"
      replicaAddress: "null"
      size: "null"
      snapshotCreatedAt: "null"
      snapshotName: "null"
      state: Pending
      url: "null"

Where notes about its absence are the only reference to "daily-ba-d559efa4-d1d2-41b9-8d71-2292a2957b7c".  It is not in snapshots.yaml.  That backup and those in similar conditions might as well be deleted because they will never complete.  That will, in turn, lessen the load on memory and CPU as there are fewer backups to try to ask about.  After the cleanup, it may be necessary to restart the longhorn-manager pods to recover the memory.
What happened to snapshot daily-ba-d559efa4-d1d2-41b9-8d71-2292a2957b7c and the others missing?  I don't know.  For the subset I have checked, there are no logs to explain that - only that they are not found.  So that would be the workaround: to delete the Pending backups.  Hopefully the recurring jobs can resume successfully.

I've had a script running for a few days looping through pending backups and kubectl delete lhb/xxx them, but it's deleting 10-ish per day, at this rate it'll take months to finish! Is there a better way to delete the pending backups? Also, I'm wondering if it would help to get rid of recurring jobs until I get things cleaned up. Is there way to disable recurring jobs without deleting them all?

@james-munson Assigned the ticket to you. Thank you.

I'm not sure why the deletion would be so slow.  Two possibilities spring to mind:

The repeated check for backup monitoring is still using a lot of the CPU.
There is non-trivial work to delete an incremental backup.  See, for instance, the description in https://github.com/longhorn/longhorn/issues/2339#issuecomment-802364652, which still applies, as far as the work to be done.

It probably would be a good idea to stop the ongoing load of the recurring backup job until it catches up.  Are any daily backups succeeding?  One might also consider creating a full backup as a safeguard for some or all volumes, depending on the volume size.  See https://longhorn.io/docs/1.7.2/snapshots-and-backups/backup-and-restore/create-a-backup/#full-backup
FYI, I will be out over the Holidays, so attention to this issue may be sporadic until the New Year.


GovukAppConfig silences OpenTelemetry log output when running a rake task

https://github.com/alphagov/govuk_app_config/pull/307 removes OpenTelemetry initialisation in the console to avoid flooding the console with OpenTelemetry startup messages.
This PR adds the additional behaviour that when OpenTelemetry is configured (ie we are not on a console), we do a second check to see whether we're in a rake task and silence OpenTelemetry log messages so that Rake tasks with simple text output are not swamped with OpenTelemetry startup messages.
Since we're already assuming Rails.const_defined? is available, we use it to check for Rake, then call Rake.application.top_level tasks, which returns an empty array if running in rails, but a list of tasks if running through rake.

It looks like we could configure it not to log anything (but I'm not sure what else it logs - could be important stuff)
OpenTelemetry::SDK.configure do |c|
  c.logger = Logger.new(File::NULL)
end

https://www.rubydoc.info/gems/opentelemetry-sdk/OpenTelemetry/SDK

@robinjam / @theseanything I've updated this PR to try James's suggestion, will try it on a branch of email-alert-api to confirm it works as expected, then if that goes okay I'll tag you both in as reviewers.

@theseanything Since you approved I've moved the changed code into lib/govuk_app_config/govuk_open_telemetry.rb instead of it being in the railtie (so that the OpenTelemetry::SDK config code is all in one block). That still okay?


PMID:12234926 cold shock

cold shock and recovery at high temperature
def based on PECO:0000285: Cells were cold shocked followed by recovery at a temperature range higher than normal for standard pombe growth.

PECO:0000323


Rename packages

Starting with a simple renaming of packages from seedu.address to seedu.clinkedin.

Codecov Report
Base: 55.73% // Head: 55.76% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (36c45c9) compared to base (4c6d285).
Patch coverage: 40.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #105      +/-   ##
============================================
+ Coverage     55.73%   55.76%   +0.02%
  Complexity      496      496
============================================
  Files           102      102
  Lines          2065     2064       -1
  Branches        231      231
============================================
  Hits           1151     1151
+ Misses          824      823       -1
  Partials         90       90

Impacted Files
Coverage Δ

src/main/java/seedu/clinkedin/AppParameters.java
75.00% <ø> (ø)

src/main/java/seedu/clinkedin/Main.java
0.00% <ø> (ø)

src/main/java/seedu/clinkedin/MainApp.java
0.00% <0.00%> (ø)

...main/java/seedu/clinkedin/commons/core/Config.java
68.18% <ø> (ø)

...java/seedu/clinkedin/commons/core/GuiSettings.java
69.23% <ø> (ø)

.../java/seedu/clinkedin/commons/core/LogsCenter.java
78.37% <ø> (ø)

...in/java/seedu/clinkedin/commons/core/Messages.java
0.00% <ø> (ø)

...ain/java/seedu/clinkedin/commons/core/Version.java
82.50% <ø> (ø)

...java/seedu/clinkedin/commons/core/index/Index.java
100.00% <ø> (ø)

...in/commons/exceptions/DataConversionException.java
100.00% <ø> (ø)

... and 92 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


translate warn deprecated

I want to translate with agruments.
there's message warned that function translate(text,params) was just deprecated.

I've the same issue


cmd/go: provide an option to print toolchain switch

Sometimes we want to trace how and where go picks up the target toolchain.
(is it from module cache? or is it from one of my PATH that may have a symlink?)
Either a debug environment variable or a flag (-x or -v) to enable tool switch activity logging can be helpful.

cc @bcmills @matloob

I think the existing -x flag is the right fit — it should emit a comment when we switch toolchains.

@bcmills , @hyangah  - I would like to work on this feature change.
Currently I did a small local setup on this go.mod file. Which are those go commands we can show the information about switch.

module change-tc

go 1.21.1

toolchain go1.21.4

by local go env modifies as below

set<EMAIL_ADDRESS>set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set<EMAIL_ADDRESS>

Note :  Current relevant go [...] -x shows the updated toolchain location.

Are we refering situations mentioned - https://go.dev/doc/toolchain - Go toolchain switches, especially after it has been been switched , not during second and subsequent.

Can we fix this issue - cmd/go: go env GOMOD tries to download newer toolchain #61455 along with this. It has to make an appropriate switch here?

I did try to address for "toolchain not available" issue and switching to go version executing this command or local available go in PATH.
Please let me know if I can raise a CL for this.

C:\Users\R\golang\analyse-bugs>cat go.mod
module example.com/analyze-bugs

go 1.23

C:\Users\R\golang\analyse-bugs>"C:\Program Files\Go\bin\go" run .
go: downloading go1.23 (windows/amd64)
go: download go1.23 for windows/amd64: toolchain not available

C:\Users\R\golang\analyse-bugs>go run .
go: downloading go1.23 (windows/amd64)
go: download go1.23 for windows/amd64: toolchain not available
Switching to your local go version executing this command: devel go1.22-5f08b44799 Mon Nov 13 14:11:13 2023 +0000 windows/amd64
Swithing Go line in go.mod file to : go 1.22 ------ go.mod ------
module example.com/analyze-bugs

go 1.22
====================
Go.mod file is switched to go 1.22 . Kindly re-execute the relevant commands
C:\Users\R\golang\analyse-bugs>go run .
Hello World

sure I will send a separate CL for this one.

@bcmills @hyangah - here is the CL for this - https://go-review.googlesource.com/c/go/+/548437
I have few questions currently toolchain switch is called at the very base of pretty every go command.

It must be called early in startup - See https://go.dev/doc/toolchain#select -

If we use x where it is not a valid flag, it shows x is not valid flag but will show the toolchain switch message , for example : go help mod -x. Technically toolchain switch currently happens for all commands if needed and then execute the command as subprocess or syscall.exec.

Kindly suggest.

@matloob @rsc and I discussed this today.
Requires more thought about the right way to implement this. It's a non-trivial change.
Pushed the milestone to 1.24 because we want to get it right.
Abandoned my CL since we shouldn't parse the -x flag before toolchain switching.

Probably GODEBUG=toolchaintrace=1 to get toolchain switch tracing.


Remove sdk package and move base plugins into plugins dir.

A basic refactor with this one, that removes the central SDK package, and moves each of the plugin definitions into their plugin packages.

I like the refactor it makes the code base more modular.


Use standard Python gitignore file

Created from https://github.com/github/gitignore/blob/main/Python.gitignore

Hey, you write awesome PR descriptions. However, you don't include those descriptions in the commits, so when I go to squash merge, the default is an empty commit... do you mind updating your commits to include the descriptions?
Easy enough to do with a git commit --amend to edit a commit's description followed by force-pushing the new updated commit.


MCA

Hello,
There are 3 problems.
first : With iris dataset, I have this problem :

I don't know why this method doesn't work.
Second : The method to_sklearn doesn't work. It's normal, MCA doesn't exist in sklearn.
thirds : problem with to_sql method :

Regards,
Alexandre

Hi Alexandre,

It is normal, we need to update the doc on inverse_transform
The 'to_sklearn' is not available for this type of models AND this function is deprecated. memModels are much more portable and easy to use.
memModels are not yet available for MCA.

If you need to export MCA to memModel, please create a new issue to ask for this feature.
I'll transform this issue to a "doc" issue.
Badr


add load kube config from dict

sometimes the kubeconfig is not stored in a file,may be in db or something.So I think we need a method to load kubeconfig from dict, like client-go https://godoc.org/k8s.io/client-go/tools/clientcmd#RESTConfigFromKubeConfig

/cc @yliaog

Codecov Report

Merging #42 into master will decrease coverage by 1.41%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
- Coverage   93.59%   92.18%   -1.42%
==========================================
  Files          11       13       +2
  Lines         859     1190     +331
==========================================
+ Hits          804     1097     +293
- Misses         55       93      +38

Impacted Files
Coverage Δ

config/kube_config_test.py
94.48% <100%> (+2.02%)
:arrow_up:

config/kube_config.py
84.71% <87.5%> (-7.16%)
:arrow_down:

watch/watch.py
100% <0%> (ø)
:arrow_up:

config/exec_provider_test.py
98.38% <0%> (ø)

config/exec_provider.py
82.6% <0%> (ø)

watch/watch_test.py
98.13% <0%> (+0.17%)
:arrow_up:

config/dateutil.py
93.33% <0%> (+4.44%)
:arrow_up:

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 6f02e73...9ed66c5. Read the comment docs.

ping @roycaihw


Simple table normalization strips all table symbols

Hi, great project!
I use markdig in a project to normalize incoming Markdown files and to gather metadata about the document. Now some of these documents include tables and I noticed that they are not rendered at all (I use a JS renderer for markdown, but that one works just fine). As it turns out, markdig seems to strip all table symbols in the normalization step.
I have a reproduction, which closely resembles the actual code used: https://github.com/ricardoboss/markdig-table-normalization
The gist of it is this:
Program.cs
var markdownPipeline = new MarkdownPipelineBuilder()
    .UsePipeTables()
    .Build();

var content = File.ReadAllText("test.md");
var document = Markdown.Parse(content, markdownPipeline);
var builder = new StringBuilder();
var writer = new StringWriter(builder);
var renderer = new NormalizeRenderer(writer);
renderer.Render(document);

Console.Write(builder.ToString());

test.md
| Col | Col 2 | Col 3 |
|:----|:-----:|------:|
| left | center | right |
| spaaaaaaaaacer | spaaaaaaaaacer | spaaaaaaaaacer |

And I expected the output to be same or somewhat formatted, but the actual output is this:
ColCol 2Col 3leftcenterrightspaaaaaaaaacerspaaaaaaaaacerspaaaaaaaaacer

I think you are just missing a pipeline.Setup(renderer) call to add the renderer for tables

https://github.com/xoofx/markdig/issues/155 doesn't list tables yet, so it might simply not be implemented at this point.

Duplicate of #155


Documentation & Tutorial missing

Describe the bug
Neither documentation nor tutorial on https://wpfui.lepo.co/
I'm sorry for bringing this up via GitHub issue.
Unfortunately the documentation & tutorial is missing since quite some time now.

They’re incomplete, but not missing for me. Try clearing your browser cache, maybe…

Interesting, so it only works on Chrome on my side. I can live with that.

CTRL + SHIFT + R or: Clear site data


Bump PyO3 version

There has been another new PyO3 release recently that among other things
fixed a bug when building on 32bit systems. It is good to get this fix
before we release retworkx again. This commit bumps the dependency
version to keep retworkx up-to-date with new PyO3 versions.

Coverage remained the same at 84.972% when pulling bb7fb728405e470ded2148cdb2a8a09987f05e41 on mtreinish:bump-pyo3-again into 98a2704b6306c466f30921551b24598253d40952 on Qiskit:master.


Update libraries identified as insecure (1.4)

libraries identified by the output of #1910 need to be updated.

Collated feedback from vulnerability scan:

logback (1.1.7)

logback-core (1.1.7)

spring-core (4.2.5)
jackson-core ( 2.7.0)

jackson-datatype-jdk8 (2.7.0)
jackson-datatype-jsr310 (2.4.0)

mariadb-java-client (1.3.2)

@rovat @kamransaleem - just updated a load of libraries - be on the lookout for regressions pls.


'Verify' method incorrect call

So I found the following error, when the library was spitting out the following error.
UnauthorizedError: "--[SECRET]--" is not a valid algorithm.
  Supported algorithms are:
  "HS256", "HS384", "HS512", "RS256", "RS384", "RS512" and "none".

index.js 50:5
var valid;
  try {
    valid = jws.verify(jwtString, secretOrPublicKey);
  }
  catch (e) {
    return callback(e);
  }

verify-stream.js 44:28
function jwsVerify(jwsSig, algorithm, secretOrKey) {
  if (!algorithm) {
    var err = new Error("Missing algorithm parameter for jws.verify");
    err.code = "MISSING_ALGORITHM";
    throw err;
  }
  jwsSig = toString(jwsSig);
  var signature = signatureFromJWS(jwsSig);
  var securedInput = securedInputFromJWS(jwsSig);
  var algo = jwa(algorithm);
  return algo.verify(securedInput, signature, secretOrKey);
}

As you can see, the parameters are incorrectly supplied. Which leads to the secret being used as the algorithm and the secret itself stays undefined.
I can either make a pull request to fix this, or it can be solved by someone else. Just let me know.

I'm very sorry for the false issue. I just looked at the package config and was using and older version. (got the versions from the authorization repo, I think it should be updated to avoid these kinds of situations though).


Add "pattern to match" setting for JME parts

It's been long enough, and I haven't thought of a better syntax for the JME pattern matcher, so I might as well make it available to the general user.
There should be a "pattern to match" setting for JME parts, along the same line as the string restrictions. If the student's answer doesn't match the pattern, they get a fraction of the total credit, and a message in the feedback.

My current thinking is that each JME part should have a list of patterns. For each pattern, the author specifies if the student's answer must, or must not, match the pattern. If the condition is not satisfied, a penalty is applied and a feedback message supplied by the author is shown to the student.
This should completely replace the string restrictions.

It's more complicated than that: you might have a sequence of patterns, and if you don't match the first one then there's no point matching the others.
So I think that idea is an over-reach for this feature. Really I want a separate system for identifying mal-rules.
We did some thinking and came up with the following list of problems where you're bothered about the form of the student's answer, so pattern-matching is necessary:

Expand brackets. Expression must not have ? * (? + ?`+) anywhere.
Put a complex number in modulus-argument form, r*e^(i theta)
Put a complex number in Cartesian form, a + ib.
Factorise an expression: must be of the form ? * ?`+ (assuming that is possible). "Fully factorise" would involve checking each factor is irreducible, which is hard. Also need to check that no factor is equivalent to 1.
Write in the form 2^n (or e^n or similar)
Write as a polynomial in x/y/whatever with integer/fraction/numerical coefficients.
A single fraction: must match ?/?, where top and bottom do not contain fractions.
Complete the square: write in the form (x+?)^2+?
Don't use decimals anywhere (need a way of matching on how a number literal was originally written, not just its parsed value)
Write a formula, isolating a variable, e.g. y = ?. For this, it would be handy to pick out a captured part of the answer, and mark that, instead of the whole thing.
The equation of a line, either in the form y=mx+c or y-y1 = m(x-x1)
Perform polynomial division, producing an expression of the form polynomial + remainder/divisor
Rationalise the denominator of a surd: ? / ?, where the bottom doesn't contain any square roots.
Write as a (integer or rational) multiple of pi
Cancel common factors on top and bottom of a fraction. Not sure how to check for this, without knowing something about the common factor.
Rewrite in terms of sin and cos (or some other functions).
Rewrite as partial fractions. Probably need to know what the denominators are going to be, or compare product of denominators to denominator on LHS, and check none of them is 1 (and no numerator is 0).

For a few of these cases, you want to check that certain bits are not 0 or 1. Would it be feasible to use numerical comparison for that, in a `where clause? For example, ?;x / ? where compare(x,1)<>0`

Done in Numbas v4.0.


Error when deleting a container: The specified container does not exist but container.deleted is None

I'm trying to delete containers and everything is going pretty well. In particular, I first check and see if container.deleted is None then I make a call using .delete_container. The reason for checking first is that I just simply want to skip a container if it's already deleted and don't make any call to the client. The thing is for some containers, even though the container.deleted is None (meaning the container is not deleted yet and should exist?), when I try to delete the container I get the following error: The specified container does not exist.:
The specified container does not exist.
RequestId:<the-request-id>
Time:2023-11-10T23:30:20.0036591Z
ErrorCode:ContainerNotFound
Content: <?xml version="1.0" encoding="utf-8"?><Error>ContainerNotFound<Message>The specified container does not exist.
RequestId:<the-request-id>
Time:2023-11-10T23:30:20.0036591Z</Message></Error>

I wonder if there's any other way than checking container.deleted to see if the container does or does not exist before making the call? The idea is to make this deletion process a bit faster, specially when dealing with a large number of deletions, and there's no point in making a call to the client if a container has been already deleted.

@phosseini - Thanks for your feedback. This repo houses many different client libraries for azure, is this issue about azure-storage-blob? Would you mind filling out the issue template information so we can tag the right people to help?
Package Name:
Package Version:
Operating System:
Python Version:
Preemptively tagging @vincenttran-msft @jalauzon-msft for storage questions.


Example benchmark config gets incorrectly minified

Ccing @neubig @pfliu-nlp
On our dev and prod server, the benchmark submit drawer shows an incorrectly minified benchmark config. The root cause is webpack (used by create react app) auto-minifies JS files by removing any whitespaces before serving to production. I didn't catch this bug as I've been developing locally...
I initially thought about switching to JSON, but then we must remove all comments as they are not allowed in JSON. There is also no easy way to exclude a file from minification without ejecting create-react-app (which is not recommended especially given we don't have a dedicated frontend team at the moment. Here are some reasons).
I'm thinking if it'd be better to fetch the config file from the CLI repo and parse it. This way it's guaranteed to be in a pretty format, and a bonus is we don't need to maintain two config files (one in web and one in CLI). Open to comments and suggestions!

Thanks for creating this issue! I think what you proposed works. (You probably already thought about this) Another slightly simpler option is to store this file as a .txt or as a string in the code (we don't need raw-loader if we go with this). But we don't get syntax highlighting if we store it as plain text.


Percentage In Progress Bar

Would you be willing to accept a patch replacing
BAR_TEMPLATE = '%s[%s%s] %i/%i - %s\r'

with
BAR_TEMPLATE = '%s[%s%s] %i\% - %s\r'

So that
[################################] 3728/3728 - 00:00:00

becomes
 [################################] 100% - 00:00:00

?

I was also just missing this feature. Hard to implement?


Add network-health-max-time-since-msg-sent flag

Closing in favor of https://github.com/ava-labs/avash/pull/141


Add ColoredLabel

Add ColoredLabel
Project URL
https://github.com/Luccifer/ColoredLabel
Category
Text
Description
A simple lib that can help to add onto the ImageView a/(an?) UILabel which will change it's color state depending on the colors and dark/light summarization of image under it
Why it should be included to awesome-ios (mandatory)
It's awesome to be able to use such functionality and it was not (such like this) presented in awesome list before.
Checklist

[ ] Has 50 GitHub stargazers or more
[ ] Only one project/change is in this pull request
[x] Isn't an archived project
[ ] Has more than one contributor
[ ] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 12 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

499
301
https://github.com/arikis/Overdrive redirects tohttps://github.com/saidsikira/Overdrive

531
404
https://github.com/rob-nash/Records

610
301
https://github.com/alexdrone/Dispatch redirects tohttps://github.com/alexdrone/DispatchStore

943
301
https://github.com/kean/Yalta redirects tohttps://github.com/kean/Align

1179
403
https://developer.apple.com/metal/

1289
301
https://github.com/JustHTTP/Just redirects tohttps://github.com/dduan/Just

2055
301
https://github.com/alaphao/LLSpinner redirects tohttps://github.com/alephao/LLSpinner

2255
404
https://github.com/rob-nash/Sheet

2571
404
https://github.com/rob-nash/Rotary

3015
301
https://github.com/tumblr/SwiftCompilationPerformanceReporter redirects tohttps://github.com/TumblrArchive/SwiftCompilationPerformanceReporter

3103
403
https://developer.apple.com/testflight/

3202
403
https://developer.apple.com/swift/blog/

  Generated by :no_entry_sign: Danger

@Luccifer We cannot merge your PR yet until you fill all of the contribution guideline requirements. Feel free to open PR once it is ready.
Please check our CONTRIBUTION GUIDELINES


Support twitch VOD in addition to youtube videos

imho not relevant anymore. YT is king for guides.


increase sidebar hl contrast in solarized

Fixes the Solarized/Solarized Dark themes to increase contrast between items in the Debug sidebar window. Non-selected item text is changed to the base01 color in Solarized (see here).
Example below, where the selected request is inside "My Folder".
Old:

New:

Default for reference:

Closes #5594

Thank you @noahmpauls 👍

@noahmpauls you can claim a free tshirt for this PR contribution - find more at https://konghq.com/community/open-source-contribution


Add deprecation notice

As outlined in #2 and commented on in #3, the application no longer works due to the OMDBAPI becoming a paid service.
This PR adds a deprecation notice at the top of the README to alert potential users that, at least for right now, the application is no longer functional.
/cc @mayankchd

Thanks a lot!


Confluence "Children Macro" Sort Order

When exporting to Confluence the "children" macro is added at the bottom of each page. The script doesn't specify any order explicitly and it seems "sort by title" is the default choice.
When using section numbers this starts to look weird as soon as you get to chapter 10 :-)
The other sort options are "creation" and "modification".
Given the way the script works, pages should get created in the same order they appear inside the document that is being exported. So maybe explicitly sorting by "creation" would be better?
The alternatives are "leave it as it is" and "make it configurable".

so, let's give "creation" a try...
or start to number like 01, 02, 03 :-)


你好我又遇到问题了 = =

上次remove-lock之后能正常启动dashboard了，codis-admin管理的也基本正常，但是想要用codis-fe打开维护页面却失败了，显示无法访问，不知道是不是哪里配置错了
dashboard.toml
##################################################
#                                                #
#                  Codis-Dashboard               #
#                                                #
##################################################

# Set Coordinator, only accept "zookeeper" & "etcd".
coordinator_name = "zookeeper"
coordinator_addr = "<IP_ADDRESS>:2181"

# Set Codis Product Name/Auth.
product_name = "codis-demo"
product_auth = ""

# Set bind address for admin(rpc), tcp only.
admin_addr = "<IP_ADDRESS>:18080"

# Set quorum value for sentinel, default is 2.
sentinel_quorum = 2

proxy.toml
##################################################
#                                                #
#                  Codis-Proxy                   #
#                                                #
##################################################

# Set Codis Product Name/Auth.
product_name = "codis-demo"
product_auth = ""

# Set bind address for admin(rpc), tcp only.
admin_addr = "<IP_ADDRESS>:11080"

# Set bind address for proxy, proto_type can be "tcp", "tcp4", "tcp6", "unix" or "unixpacket".
proto_type = "tcp4"
proxy_addr = "<IP_ADDRESS>:19000"

# Set jodis address & session timeout, only accept "zookeeper" & "etcd".
jodis_name = ""
jodis_addr = ""
jodis_timeout = "20s"
jodis_compatible = false

# Set datacenter of proxy.
proxy_datacenter = ""

# Set max number of alive sessions.
proxy_max_clients = 1000

# Set max offheap memory size. (0 to disable)
proxy_max_offheap_size = "1024mb"

# Set heap placeholder to reduce GC frequency.
proxy_heap_placeholder = "256mb"

# Proxy will ping backend redis in a predefined interval. (0 to disable)
backend_ping_period = "5s"

# Set backend recv buffer size & timeout.
backend_recv_bufsize = "128kb"
backend_recv_timeout = "50s"

# Set backend send buffer & timeout.
backend_send_bufsize = "128kb"
backend_send_timeout = "50s"

# Set backend pipeline buffer size.
backend_max_pipeline = 1024

# Set backend tcp keepalive period. (0 to disable)
backend_keepalive_period = "75s"

# If there is no request from client for a long time, the connection will be closed. (0 to disable)
# Set session recv buffer size & timeout.
session_recv_bufsize = "128kb"
session_recv_timeout = "30m"

# Set session send buffer size & timeout.

启动命令是？
On Monday, October 31, 2016, adamchen233<EMAIL_ADDRESS>wrote:

上次remove-lock之后能正常启动dashboard了，codis-admin管理的也基本正常，但是想要用codis-
fe打开维护页面却失败了，显示无法访问，不知道是不是哪里配置错了
dashboard.toml
`##################################################
Codis-Dashboard
##################################################
Set Coordinator, only accept "zookeeper" & "etcd".
coordinator_name = "zookeeper"
coordinator_addr = "<IP_ADDRESS>:2181"
Set Codis Product Name/Auth.
product_name = "codis-demo"
product_auth = ""
Set bind address for admin(rpc), tcp only.
admin_addr = "<IP_ADDRESS>:18080"
Set quorum value for sentinel, default is 2.
sentinel_quorum = 2
proxy.toml
##################################################
Codis-Proxy
##################################################
Set Codis Product Name/Auth.
product_name = "codis-demo"
product_auth = ""
Set bind address for admin(rpc), tcp only.
admin_addr = "<IP_ADDRESS>:11080"
Set bind address for proxy, proto_type can be "tcp", "tcp4", "tcp6",
"unix" or "unixpacket".
proto_type = "tcp4"
proxy_addr = "<IP_ADDRESS>:19000"
Set jodis address & session timeout, only accept "zookeeper" & "etcd".
jodis_name = ""
jodis_addr = ""
jodis_timeout = "20s"
jodis_compatible = false
Set datacenter of proxy.
proxy_datacenter = ""
Set max number of alive sessions.
proxy_max_clients = 1000
Set max offheap memory size. (0 to disable)
proxy_max_offheap_size = "1024mb"
Set heap placeholder to reduce GC frequency.
proxy_heap_placeholder = "256mb"
Proxy will ping backend redis in a predefined interval. (0 to disable)
backend_ping_period = "5s"
Set backend recv buffer size & timeout.
backend_recv_bufsize = "128kb"
backend_recv_timeout = "50s"
Set backend send buffer & timeout.
backend_send_bufsize = "128kb"
backend_send_timeout = "50s"
Set backend pipeline buffer size.
backend_max_pipeline = 1024
Set backend tcp keepalive period. (0 to disable)
backend_keepalive_period = "75s"
If there is no request from client for a long time, the connection will be
closed. (0 to disable) Set session recv buffer size & timeout.
session_recv_bufsize = "128kb"
session_recv_timeout = "30m"
Set session send buffer size & timeout.
`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CodisLabs/codis/issues/1015, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAsHpVMozwla0dMyLBOI2kWPjvsn1Xofks5q5UNQgaJpZM4Kkk80
.

nohup ./bin/codis-fe --ncpu=4 --log=fe.log --log-level=WARN
--dashboard-list=codis.json --listen=<IP_ADDRESS>:8080 &
or
nohup ./bin/codis-fe --ncpu=4 --log=fe.log --log-level=WARN
--dashboard-list=codis.json --listen=<IP_ADDRESS>:8080 &
在内网其他机子上访问<IP_ADDRESS>:8080

fe就是个反向代理。你确认一下 assets 路径对吗？
On Monday, October 31, 2016, adamchen233<EMAIL_ADDRESS>wrote:

nohup ./bin/codis-fe --ncpu=4 --log=fe.log --log-level=WARN
--dashboard-list=codis.json --listen=<IP_ADDRESS>:8080 &
or
nohup ./bin/codis-fe --ncpu=4 --log=fe.log --log-level=WARN
--dashboard-list=codis.json --listen=<IP_ADDRESS>:8080 &
在内网其他机子上访问<IP_ADDRESS>:8080
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CodisLabs/codis/issues/1015#issuecomment-257196107,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAsHpeEibNpkXNsiMpvakx9aROU__ejZks5q5USkgaJpZM4Kkk80
.

codis.json是
[
    {
        "name": "codis-demo",
        "dashboard": "<IP_ADDRESS>:18080"
    }
]

在fe.log里
2016/10/31 09:31:45 main.go:102: [WARN] set ncpu = 4
2016/10/31 09:31:45 main.go:105: [WARN] set listen = <IP_ADDRESS>:8080
2016/10/31 09:31:45 main.go:117: [WARN] set assets = /root/work/src/github.com/CodisLabs/codis/bin/assets
2016/10/31 09:31:45 main.go:132: [WARN] set --dashboard-list = codis.json

/root/work/src/github.com/CodisLabs/codis/bin/assets这个路径是对的，里面有index.html等东西= =

对不起！！！是防火墙的问题，我傻逼了，画面明明之前已经改过防火墙啦= =，打搅了😂
2016年10月31日 上午9:28，"spinlock9"<EMAIL_ADDRESS>
启动命令是？
On Monday, October 31, 2016, adamchen233<EMAIL_ADDRESS>wrote:

上次remove-lock之后能正常启动dashboard了，codis-admin管理的也基本正常，但是想要用codis-
fe打开维护页面却失败了，显示无法访问，不知道是不是哪里配置错了
dashboard.toml
`##################################################
Codis-Dashboard
##################################################
Set Coordinator, only accept "zookeeper" & "etcd".
coordinator_name = "zookeeper"
coordinator_addr = "<IP_ADDRESS>:2181"
Set Codis Product Name/Auth.
product_name = "codis-demo"
product_auth = ""
Set bind address for admin(rpc), tcp only.
admin_addr = "<IP_ADDRESS>:18080"
Set quorum value for sentinel, default is 2.
sentinel_quorum = 2
proxy.toml
##################################################
Codis-Proxy
##################################################
Set Codis Product Name/Auth.
product_name = "codis-demo"
product_auth = ""
Set bind address for admin(rpc), tcp only.
admin_addr = "<IP_ADDRESS>:11080"
Set bind address for proxy, proto_type can be "tcp", "tcp4", "tcp6",
"unix" or "unixpacket".
proto_type = "tcp4"
proxy_addr = "<IP_ADDRESS>:19000"
Set jodis address & session timeout, only accept "zookeeper" & "etcd".
jodis_name = ""
jodis_addr = ""
jodis_timeout = "20s"
jodis_compatible = false
Set datacenter of proxy.
proxy_datacenter = ""
Set max number of alive sessions.
proxy_max_clients = 1000
Set max offheap memory size. (0 to disable)
proxy_max_offheap_size = "1024mb"
Set heap placeholder to reduce GC frequency.
proxy_heap_placeholder = "256mb"
Proxy will ping backend redis in a predefined interval. (0 to disable)
backend_ping_period = "5s"
Set backend recv buffer size & timeout.
backend_recv_bufsize = "128kb"
backend_recv_timeout = "50s"
Set backend send buffer & timeout.
backend_send_bufsize = "128kb"
backend_send_timeout = "50s"
Set backend pipeline buffer size.
backend_max_pipeline = 1024
Set backend tcp keepalive period. (0 to disable)
backend_keepalive_period = "75s"
If there is no request from client for a long time, the connection will
be
closed. (0 to disable) Set session recv buffer size & timeout.
session_recv_bufsize = "128kb"
session_recv_timeout = "30m"
Set session send buffer size & timeout.
`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CodisLabs/codis/issues/1015, or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAsHpVMozwla0dMyLBOI2kWPjvsn1Xofks5q5UNQgaJpZM4Kkk80>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CodisLabs/codis/issues/1015#issuecomment-257195908,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOeDrSX_kGQNL1vCZxqZXoGPYVfT0Yawks5q5UQngaJpZM4Kkk80
.


Check the Transaction History status in the following case

Describe the task
Check the Transaction History status in the following case
To reproduce the behavior
Steps:

Go to the send token screen
Select token = USDT (Astar), Destination Chain = Statemint
Input valid data for the remaining fields
Click on the Transfer button
Approve the transaction
Observe:

Status of the transaction history
USDT (Astar) balance
Status of the transaction on explorer

Actual:

The transaction status was displayed as follows: In Progressing -> Completed -> Failed
USDT (Astar) balance not change
Status of the transaction on Explorer is Success

Notes:

Check with address: 5CqUd153pVTUe3K12TJnpFzkpXGBhU3Z9SqqH5u2ifZ6u1x2
Extrinsic: https://astar.subscan.io/extrinsic/0x5a21008b3396d20cc890f6f5474040f90bd2399464deffcb6b0c2456043ca662

Expect:

Check the reason for the transaction failure
Exchange more and define transaction status display on SubWallet and Explorer

[ ] Show incorrect transaction status of the redeem transaction
Steps:

Stake 1 DOT (Acala) successfully
Perform fast unstake
Observe the transaction history displayed and compare status of this transaction on explorer

Actual: Show incorrect status

Expect: Show correct status

Do not reproduce this behavior on the current version (v1.2.28) => Close this issue


Multi arch docker file

Clear and concise description of the problem
It would be amazing if you could build a multi arch docker container. I prefer to have pre built dockers as I'm sure to have them updated without check each github for updates.
It can be built on arm64 (rpi 4) as I have it running right now without any issues, but it would be amazing to have it pre-built by default if possible.
Thank you for developing it, I've been looking for a nice looking bookmark manager for a while now. It's great.
Suggested solution
add different arch in the dockerfile before build and push
Alternative
No response
Additional context
No response
Validations

[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@phampyk great idea! I've added docker multi-arch builds to the build and push github action in this repository. Unfortunately prisma (one of the core libraries used in Briefkasten), doesn't support armv7. Meaning we can't support the Raspberry Pi 3B+, only rpi 4 and newer (arm64).
In short, the docker hub image ndom91/briefkasten is now built for both amd64/arm64 :partying_face:


How to spin off a sibling container?

Question
What is the recommended / sanctioned way to configure docker/jenkins so that it can spin off a build in a sibling container? I have gone through all the documentation that I could find, and read through all the issues, and still end up at: Impossible. This does not work, unless I use not recommended or unsafe workarounds.
Since this is a very fundamental functionality of Jenkins, I must overlook something simple. Would anyone knowledgable be so glad and point me to the right piece of documentation?
What I did
Bind-mount

When I use a bind mount, I get Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock.
Jenkins runs with the default 1000:1000.
User 1000 outside of the container is part of the docker group (GID 999) and can access the docker daemon just fine.
Inside the container, /etc/groups lists GID 101 under docker, and GID 999 is named ping.
Ugly workarounds include:

Force GID 999 when starting Jenkins, instead of the default 1000.  On other hosts, the docker GID might be different. On the Mac, for example, docker.sock is owned by root:root.
Lowering the restrictions of /var/run/docker.sock. Ugly because it is unsafe.
Building my own dockerfile. Ugly because such a fundamental function should work out of the box.

Access via TCP

Opening the docker daemon to allow access from <IP_ADDRESS>. Ugly because the entire world can connect to my docker daemon now.
Doing the above, but protecting the socket with certificates. This works for every container that I tried, but not for Jenkins. The problem is the Truststore that I have to provide: It contains the docker sockets certificate. Every other SSL connection now fails (e.g. to Github), because the regular Java truststore entries are missing.

And that's it, I found no other suggestions.
My environment is docker-ci on Ubuntu 18.04.2 LTS.

I came upon this thread in looking for a solution to this problem...which I then solved.
Here's code inside a "script" tag in an otherwise declarative Jenkins pipeline:
...
JENKINSUID = sh ( script: 'id -u jenkins', returnStdout: true ).trim()
DOCKERGID = sh ( script: 'stat -c %g /var/run/docker.sock', returnStdout: true ).trim()
JENKINSGID = sh ( script: 'id -g jenkins', returnStdout: true ).trim()
docker.image('maven:3.6.2-jdk-8').inside("--user=${JENKINSUID}:${JENKINSGID} --group-add ${DOCKERGID} -v /var/run/docker.sock:/var/run/docker.sock -v /usr/bin/docker:/usr/bin/docker") {
// This should work:
sh "docker ps"
}
I based this on this:  https://stackoverflow.com/questions/47854463/got-permission-denied-while-trying-to-connect-to-the-docker-daemon-socket-at-uni
...except that I removed the need for an entirely new docker container.


More robust oriented bounding box computations

The OrientedBoundingBox::fromPoints method implements an eigenvector-based approach for computing the oriented bounding box of the given set of points, as decribed in "Collision queries using oriented bounding boxes" by Stefan Gottschalk (PDF file).
This approach is prone to distortions - roughly: When there is a "dense" set of points that do not contribute to the actual extremes, then thes points will cause a suboptimal eigenvector to be computed. This can be observed, for example, in these cases:

An oriented bounding box of a cube-shaped set of points: The bounding box is not tightly fitting

An oriented bounding box that was computed from the corners of the first bounding box - this fits perfectly:

When adding a few more of the original points, the oriented bounding box becomes worse:

This happens although these inner points should not affect the bounding box. This phenomenon is also described in the original thesis:

Approaches for improving the robustness are described in the thesis as well. The most important one is to compute the bounding box not based on all points, but only based on the points of the convex hull of the original points. The idea here is that only the "extreme" points should contribute to the eigenvector computation.
I tried this out, with the quickhull3d library. It does improve the result in some cases - for example, the case 3. from the list above does no longer cause any problems. But still, depending on the exact arrangement of the points, the convex hull may not solve the issue. For example, when computing the convex hull of the cube-shaped set of points, then the hull contains some triangles that are not exactly the "cube faces", but only inserted due to inaccuracies. Depending on where exactly these points are, they may still distort the eigenvectors.
I tried to go one step further, and applied the MeshoptSimplifier.simplify method of the meshoptimizer library to the convex hull, with the goal to get rid of the triangles that are only caused by these inaccuracies. But even when the (optimized) convex hull is a perfect cube, the approach does not necessarily yield good (or even "not bad") oriented bounding boxes:

The thesis specifically mentions an approach for computing the covariance matrix (that serves as the basis for computing the eigenvectors) based on triangles (and not only based on vertices/points). But....

the implementation becomes a bit more complex
it still requires the computation of the convex hull
it might still require the optimization/simplification of the convex hull
and it's still not clear whether that would solve the issue and yield "good" bounding boxes more reliably

I did some experiments for computing the bounding box with https://github.com/Esri/dito.ts . The results are summarizes in https://github.com/CesiumGS/3d-tiles-tools/pull/79#issuecomment-1798923857 .
The tl;dr is: The method is noticably slower, but gives better results in nearly all cases.
The implementation in dito.ts was ported from the original C/C++-based implementation. It uses some vector math (really simple things, add/subtract/dot/length) that is implemented based on raw arrays. Iff this method should be supported by CesiumJS, then one could consider to implement it based on the existing Cartesian* classes.

Just establishing a connection to https://github.com/CesiumGS/cesium/issues/4785 here...

@javagl Would you call these duplicates? I'd be in favor of consolidating these issues.


Streaming File Uploads

Specific Demand
The current FileEngine exposes two ways to read a file: Reading the file to a string or reading the file to a byte array. Both of these methods perform poorly with large files. In addition to poor performance, you cannot provide updates to the user based on file upload progress.
Implement Suggestion
We should expose a third API that returns the size of the file (depending on the platform) and a stream with the file data
Related to https://github.com/DioxusLabs/dioxus/pull/1181

Reminder on file size visibility: https://github.com/DioxusLabs/dioxus/pull/2323
And for the stream part, in my own web only project with file uploads, I use: web_file: web_sys::File and with https://github.com/MattiasBuelens/wasm-streams :
    let mut stream = ReadableStream::from_raw(web_file.stream());
    let reader = stream.get_byob_reader();
    let mut reader = ChunkedReader::new(reader, MAX_ALLOWED_SIZE_CHUNK_PADDED);

    while let Some(res) = reader.read_chunk().await {


DEX - help button to trigger guidelines

What would you like to be added:
From DEX page, we would like to add a CTA to show DEX guidelines page. Currently, it's only displayed on initial install of app. This will allow users to view content in case they missed out.
/needs design
/assign @jtlntno-cake
Why is this needed:

Acceptance Criteria: In DEX screen, user able to access DEX guidelines page
Android:

[ ] DEX > click i > Guideline should display

iOS:

[ ] DEX > click i > Guideline should display


:memo: feat(docs-beta): Build out more of the tutorial

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #85

PR #86   👈

This comment was auto-generated by Graphite.


Grouping quick open entries is broken

open linkedList.ts
trigger quick outline
type : to group by symbol kind
:bug: groups are repeated, no grouping happening

There are two comparators: one that compares by matches and one that first compares the item kind and then the matches. The issue is that we never use the latter comparator.... 🤦♂


[Improvement][Task Plugin] Improvement Kubeflow task plugin

Purpose of the pull request
related: #12166
Brief change log

check new phase in status:conditions
add example in doc

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #12928 (5b4e205) into dev (c916c60) will decrease coverage by 0.13%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##                dev   #12928      +/-   ##
============================================
- Coverage     39.44%   39.31%   -0.14%
  Complexity     4244     4244
============================================
  Files          1052     1061       +9
  Lines         39857    40018     +161
  Branches       4586     4586
============================================
+ Hits          15723    15732       +9
- Misses        22356    22506     +150
- Partials       1778     1780       +2

Impacted Files
Coverage Δ

...lphinscheduler/plugin/kubeflow/KubeflowHelper.java
81.39% <40.00%> (-5.45%)
:arrow_down:

...dolphinscheduler/plugin/kubeflow/KubeflowTask.java
90.16% <100.00%> (+0.16%)
:arrow_up:

...erver/master/processor/queue/TaskEventService.java
69.64% <0.00%> (-10.72%)
:arrow_down:

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
42.55% <0.00%> (-2.13%)
:arrow_down:

...hinscheduler/plugin/alert/script/ScriptSender.java
70.58% <0.00%> (-1.64%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.38% <0.00%> (-1.39%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
51.19% <0.00%> (-1.20%)
:arrow_down:

...eduler/api/service/impl/DataSourceServiceImpl.java
50.75% <0.00%> (-1.02%)
:arrow_down:

...cheduler/plugin/alert/dingtalk/DingTalkSender.java
34.13% <0.00%> (-0.78%)
:arrow_down:

... and 33 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

thanks all


Support for disabling title missing?

According to the highcharts API disabling the title is possible by setting it to null.
I tried options.setTitle(new Title(null)); and options.setTitle(null); with no effect. What's the trick?
Wicket: 6.21.0
Wicked-Charts: 2.0.0
Btw, keep up the great work!

Btw, the same seems to apply to Axis.

Ay, it's setTitle("");! A bit ambiguous, but works.


Added flag to disable build name validation on ios

Added --validate-build-name flag to the flutter build ios/ipa commands.
Version names with pre-release suffixes such as 1.0.0-beta or 1.2.3-alpha were previously being truncated to 1.0.0 and 1.2.3, in accordance with Apple's documentation on CFBundleShortVersionString.
This flag allows the developer to bypass this validation.
Fixes #63768
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

So Flutter has two different flags --build-name and --build-number. --build-name is used to set CFBundleShortVersionString and --build-number is used to set CFBundleVersion.
So for --build-name/CFBundleShortVersionString, both the archived documentation and current documentation are clear that it should only be "three period-separated integers". So I don't think it makes sense to allow just any value to be set as this PR does.
Also, this PR doesn't seem to actually address issue https://github.com/flutter/flutter/issues/63768.
In issue https://github.com/flutter/flutter/issues/63768, they reported that --build-number/CFBundleVersion should allow a suffix that allows either d, a, b, or fc followed by a number of 1-255. And according to this archived documentation for CFBundleVersion, it seems true. However, if we look at current documentation, it does not mention allowing a suffix and explicitly states only "numeric characters (0-9) and periods" are allowed. It's not clear to me if the App Store/Xcode will reject, ignore, or accept the suffix.
If we wanted to allow the suffix as the archived documentation says, I think we should probably update the below function to only allow just a suffix of d, a, b, or fc (followed by a number of 1-255) rather than just any string.
https://github.com/flutter/flutter/blob/9a72e1c699f2b277b85110c89cbbb851f4de6935/packages/flutter_tools/lib/src/build_info.dart#L456-L491
Again, I'm not certain that we should allow it at all, though. @jmagman Any thoughts?

I'm not certain that we should allow it at all, though.

I agree, I don't see why we should allow developers to punch a hole through the validation logic, against the (non-archived) documented formatting published by Apple, potentially to be disallowed by the App Store.  If you want to set a particular special version that would potentially be rejected by the App Store I suggest digging into your ios/Runner.xcworkspace and setting the CURRENT_PROJECT_VERSION build setting there yourself, and CFBundleVersion and CFBundleShortVersionString in the project, which should override Flutter's attempts to parse the version from the pubspec.


Rename testgen vote -> is_nil to nil

addressing clippy's suggestion as below from PR #759

warning: methods called is_* usually take self by reference or no self; consider choosing a less ambiguous name

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Updated CHANGELOG.md

Codecov Report

Merging #760 (b7f70fc) into master (6d04471) will decrease coverage by 0.0%.
The diff coverage is 92.8%.

@@           Coverage Diff            @@
##           master    #760     +/-   ##
========================================
- Coverage    50.6%   50.6%   -0.1%
========================================
  Files         197     197
  Lines       13575   13570      -5
  Branches     3249    3249
========================================
- Hits         6877    6872      -5
  Misses       6336    6336
  Partials      362     362

Impacted Files
Coverage Δ

testgen/src/vote.rs
80.1% <66.6%> (ø)

light-client/src/operations/voting_power.rs
88.5% <100.0%> (ø)

light-client/tests/model_based.rs
87.8% <100.0%> (ø)

rpc/tests/kvstore_fixtures.rs
97.4% <100.0%> (-0.1%)
:arrow_down:

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 6d04471...b7f70fc. Read the comment docs.


Test suite limit optimization

          Hi @ASaiAnudeep Thanks for making a progress here. Could we enhance this to accommodate more than 10 test suites? If so, this plugin would truly shine.

Thank You!
Originally posted by @KosalaiV in https://github.com/test-results-reporter/reporter/issues/144#issuecomment-1975797183

@KosalaiV  , I've added a new input called max_suites, which is set to a default value of 10, allowing you to adjust the limit on the number of suites.
{
  "name": "slack",
  "inputs": {
    "url": "<slack-incoming-webhook-url>",
    "max_suites": 20
  }
}

I will update the docs in sometime.


2019-12-09 GUARD-325 Failed-Orders-Sync

Summary
One of our customers faced Etsy's order's deserialization issue.
Newtonsoft.Json.JsonReaderException: JSON integer<PHONE_NUMBER> is too large or small for an Int32. Path 'results[1].Transactions[0].image_listing_id', line 1, position 64978.
Etsy's documentation contains mistake - https://www.etsy.com/developers/documentation/reference/transaction, it declares that this field should be int.

Since the Etsy documentation is correct, are we should that a "long" will be large enough? We don't have to just make it a string?
Long data range should be enough to store possible imageId values. I see that for listings ids Etsy uses the same type.

Long data range should be enough to store possible imageId values. I see that for listings ids Etsy uses the same type.

Sounds good. The PR looks good. See no way to approve it now, since I commented earlier:(


Add test of deterministic and non deterministic provider's methods

The PR is aiming to solve #741 for all the providers (not only OscarMovie)
E.g. it was detected that Mbti has same issue.
It retrieves all the declared public methods from provider with zero arg and invokes them several times.
The result is expected to be not the same at least for some of the invocations.
As an exception there Deterministic annotation added to mark methods which are expected to return same value for any number of invocations.

DOH, needs a spotlessapply

Codecov Report

Merging #743 (a8ce391) into main (d1992a1) will increase coverage by 0.03%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #743      +/-   ##
============================================
+ Coverage     92.80%   92.84%   +0.03%
- Complexity     2590     2592       +2
============================================
  Files           281      281
  Lines          5126     5126
  Branches        530      530
============================================
+ Hits           4757     4759       +2
+ Misses          241      240       -1
+ Partials        128      127       -1

Impacted Files
Coverage Δ

...ain/java/net/datafaker/providers/base/Address.java
97.14% <ø> (ø)

.../main/java/net/datafaker/providers/base/Drone.java
100.00% <ø> (ø)

...in/java/net/datafaker/providers/base/Locality.java
64.81% <ø> (ø)

...c/main/java/net/datafaker/providers/base/Mbti.java
100.00% <100.00%> (ø)

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Images and math in tab headings broken in 2.0.0

Describe the bug
Placing images and math in tab headings/titles does not work in version 2.0.0.
To Reproduce / Expected behavior
I'm not sure if it is (was) a deliberate feature, but prior to 2.0.0 one could have tabs like what is shown here. The Sphinx code generating this is of the form
.. tabs::

   .. tab:: |linux| :math:`\,\,` Linux

      Tab 1 text...

   .. tab:: |windows| :math:`\,\,` Windows

      Tab 2 text

where |linux| and |windows| are images defined as
.. |linux| image:: /_static/linux.png
   :height: 35px

.. |windows| image:: /_static/windows.png
   :height: 35px

I use :math: simply to produce some whitespace between the images and the titles.
With sphinx-tabs 2.0.0 we get the following:

Neither the image nor the math is rendered. It's as though the RST-text isn't getting parsed but just used raw, as is.
Environment

Python 3.9.1
Sphinx 3.4.1
Linux Mint 20

I'm not sure if this is just intentionally not supported. Images in tab headings is non-trivial.


TCE v0.10.0 is throwing error when deploying Management Cluster using NSX ALB v20.1.7

Bug Report
TCE TKG v0.10.0 is throwing error when deploying Management Cluster using NSX ALB v20.1.7 as load balancer.
Expected Behavior
Management cluster should be able to complete step: Generate cluster configuration
Steps to Reproduce the Bug
on vSphere 7u2 environment start deployment of management cluster using the below config and it throws error at "Generate cluster configuration" step.
Screenshots or additional information and context
✘ [0320 13:26:09.53627]: init.go:85] unable to set up management cluster, : unable to build management cluster configuration: unable to get template: - load: name crd not found in module static.lib.yaml in  03_customizations/02_avi/add_akoo.yaml:5 | #@ load("static.lib.yaml", "crd","service")
Environment Details

Build version (tanzu version): v0.10.0
Deployment (Managed/Unmanaged cluster): Management Cluster
Infrastructure Provider (Docker/AWS/Azure/vSphere): vSphere
Operating System (client): Linux (ubuntu)

Diagnostics and log bundle
✘ [0320 13:26:09.53627]: init.go:85] unable to set up management cluster, : unable to build management cluster configuration: unable to get template: - load: name crd not found in module static.lib.yaml in  03_customizations/02_avi/add_akoo.yaml:5 | #@ load("static.lib.yaml", "crd","service")

See https://github.com/vmware-tanzu/community-edition/issues/3189 for a workaround.
Waiting for someone with more expertise in this area to triage, but this is likely a duplicate of that one.

Looks like this was fixed in tanzu-framework with https://github.com/vmware-tanzu/tanzu-framework/pull/1044
That change is part of the tanzu-framework v0.11.2 release that TCE is using in the upcoming TCE v0.11.0 release, so this should be resolved then.

@stmcginnis assigning this to you to validate once we have our first rc :+1:

@stmcginnis on second though, now that we have a pinned framework version, can you verify this at your earliest and we can close it out? Appreciate it!


Safer file management

Currently the script allows the destruction of existing files without confirmation. This is potentially very risky.
Please consider some safer file management. Happy to do some PR's if needed

That's a good point. I can add that feature, but I won't be able to get to it til next week. If you want to submit a PR for it, that'd be great. Otherwise I'll jump on it next week.

Cool. I should be freed up around Monday arvo (EST), I will try to get some PR's in order.

Sounds great! 👍

Fixed by PR #6


Not every autogenerated virtual services needs to be public / exposed to the world

Hi,
right now, keptn creats Istios virtual services automatically when you onboard a service. The things is, the hosts entry will also be filled by a FQDN which is not necessary for most of the services. Most of the time actually only one service needs to be exposed to the world.
A short example from a Redis pod which is only used from the other pods within the same namespace.
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  creationTimestamp: null
  name: redis
spec:
  gateways:
  - public-gateway.istio-system
  - mesh
  hosts:
  - redis.staging.<domain>.de
  - redis
  http:
  - route:
    - destination:
        host: redis.staging.svc.cluster.local

My proposal would be, to add a flag while onboarding the service.
keptn onboard service redis --project=project --chart=keptn/redis/charts/ --image=redis --public=false
Kind regards,
Stephan

To re-iterate on what Stephan has posted, this is the result of onboarding carts and carts-db in the dev stage:
$ kubectl get services -n sockshop-dev
NAME       TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)     AGE
carts      ClusterIP   <IP_ADDRESS>     <none>        80/TCP      59m
carts-db   ClusterIP   <IP_ADDRESS>   <none>        27017/TCP   60m

$ kubectl get vs -n sockshop-dev
NAME       GATEWAYS                             HOSTS                                                  AGE
carts      [public-gateway.istio-system mesh]   [carts.sockshop-dev.<IP_ADDRESS>.xip.io carts]         58m
carts-db   [public-gateway.istio-system mesh]   [carts-db.sockshop-dev.<IP_ADDRESS>.xip.io carts-db]   60m

The virtual-service for carts-db could also benefit from this, as right now it is publicly exposed.
For an implementation, it should be enough to not use the gateway public-gateway.istio-system, but instead just use mesh, right?

I think you could actually remove both.
public-gateway.istio-system and
redis.staging.<domain>.de .
As soon as you remove one of them it is not public anymore. It's on you.

You are correct, we should also remove the hostname, just in case.

Long-Term plan is to deal with VirtualServices (vs. Kubernetes services) a little differently, and give the user more control about this.
Right now, I'll keep this open as a known issue for 0.6.x and 0.7.x


SynchronousAdapter.name must return a string, not func

overview
opentrons.hardware_control.adapters.SynchronousAdapter inherits from threading.Thread. Addtionally, conceptually, it also sort-of inherits from opentrons.hardware_control.API through it's own delegation mechanism.
Both Thread and API have a name attribute.
Thread.name returns a string, and the PyCharm debugger relies on this.
However, SynchronousAdapter.name returns API.name, which returns (e.g.) TempDeck.name which results in a method object, not a string. This crashes PyCharm, and makes the OT2 protocol undebuggable, which is a bit of a big deal.
A simple fix is to add
        if attr_name == 'name':
            return super(SynchronousAdapter, self).name

at the top of SynchronousAdapter.__getattribute__ (I've tested same with some judicious hacks).
current behavior
See above.
steps to reproduce
See above.
expected behavior
All OT2 protocols should be debuggable in the simulator.

A different, perhaps more elegant, fix would be change from SynchronousAdapter 'is-a' Thread to SynchronousAdapter 'has-a' thread, which would intrinsically avoid this conflict and any others that might be lurking.

The following is a protocol which is not debuggable because of this bug:

from opentrons.protocol_api import ProtocolContext

metadata = {
    'protocolName': 'Test Test Test',
    'author': 'Robert Atkinson<EMAIL_ADDRESS>    'apiLevel': '2.0'
}

def run(protocol_context: ProtocolContext):
    temp_module = protocol_context.load_module('tempdeck', location=11)

After some digging, it looks like this class is not being a well-behaved sub-class of threading.Thread. We'll keep an eye on this and likely try to move away from this multiple-inheritance thing that's going on

After #4870 SynchronousAdapter doesn't inherit from Thread anymore


Start issuer/verifier AcaPy with debugging enabled

The goal is to be able to debug the AcaPy running in the load testing setup by attaching a debugger to it.

https://github.com/My-DIGI-ID/aries-cloudagent-loadgenerator/commit/7948a67aff7ba53f58da54417d84f1ab651b621b


Fix return type for _write

The documentation doesn't say anything about what it should return, so I assume it should return void.
https://nodejs.org/dist/latest-v10.x/docs/api/stream.html#stream_writable_write_chunk_encoding_callback_1

CLA is signed

Taking a look at the test failures now.

Thanks a lot for the PR! It looks great but unfortunately I can't merge it because 5a988d12 already made that change a few days ago. Really sorry we didn't get to it sooner, but thanks again for the contribution.


Update dependencies to allow Ramsey/Uuid version 4

Is there any possibility of a new tagged release that allows ramsey/uuid 3 or 4, and not simply 3?
PHP, and your dependencies have moved on since the last tagged release.

same issue here

same here

Same here.

Any news about this pull request? I can't run open census with the latest laravel/lumen due to this restriction


devenv shell exits when any command returns an error

After opening a devenv shell, I typed a command wrong which returned an error to the shell. devenv dropped me out of the nix shell and back to my regular zsh prompt.  Typing devenv shell or direnv allow reopens the shell.
Session transcript with minimal reproducible error:
bjk in 🌐 beast in ~/projects/devenvtest on ☁  (us-east-1) took 1m37s
❯ direnv allow

bjk in 🌐 beast in ~/projects/devenvtest on ☁  (us-east-1)
❯ direnv allow
direnv: loading ~/projects/devenvtest/.envrc
Building shell ...
Entering shell ...

deadnix 0.1.8
cachix 1.0.1
statix 0.5.6
vulnix 1.10.1
go version go1.19.3 linux/amd64
pre-commit-hooks.nix: hooks up to date
hello from devenv
git version 2.38.1
<< In the devenv shell here>>
(devenv) bjk@beast:~/projects/devenvtest$ false
<< devenv shell has exited here>>
bjk in 🌐 beast in ~/projects/devenvtest on ☁  (us-east-1) took 4s
❯ devenv --version
https://devenv.sh (version 0.1): Fast, Declarative, Reproducible, and Composable Developer Environments

Versions:
nix (Nix) 2.11.0
direnv 2.32.1

Hey, thanks for spotting this! I pushed a fix to master, could you install and try if it works?

Looks like it works great, thanks for the quick fix!
On Fri, Nov 11, 2022 at 2:05 PM Domen Kožar @.***>
wrote:

Hey, thanks for spotting this! I pushed a fix to master, could you install
and try if it works?
—
Reply to this email directly, view it on GitHub
https://github.com/cachix/devenv/issues/21#issuecomment-1312080226, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAJE5HN5ES35K6H4X7GXSDWH2KJJANCNFSM6AAAAAAR52LNVA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--

Brian Ketelsen
bketelsen  gmail  com

Release 0.2 with this fix.


Used the placeholder to insert the branch instruction.

Used the placeholder and calculated the length between the branch inst and target label using the long branch if necessary.

the changes had been redesigned and added to the #566


ci docker caching

Is your feature request related to a problem? Please describe.
during CI we build every time. ideally we should be smart about caching
Describe the solution you'd like
circleci has rich caching features which should be used between builds

turns out this requires a different plan on circle ci