ADD: repositories

Coverage remained the same at 98.391% when pulling 970b2722bd95645ee4d42248bbffebeae886f269 on doc/repos into 30bec0b748ebd04f9d739c2478393b9ef03b928b on develop.

Codecov Report

Merging #8 into develop will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           develop     #8   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files            4      4
  Lines          296    296
  Branches        46     46
======================================
  Hits           296    296

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 30bec0b...eb3e1ef. Read the comment docs.


Upgrade fails from 1.5.0 to 1.5.2

I get this notification:
2022-11-01T22:35:01+08:00 𝒊  New version of agc available. Current version is '1.5.0'. The latest version is '1.5.2'. Please consider upgrading to the latest version by following https://aws.github.io/amazon-genomics-cli/docs/getting-started/installation/
I install the new version by following:
https://aws.github.io/amazon-genomics-cli/docs/getting-started/installation/
I check the version:
$ agc --version
agc version: 1.5.0

It's still the old version and I keep receiving the notification in new terminal windows.

Hello Omar,
Thanks for reaching out! I was able to download the amazon-genomics-cli-1.5.2.zip and successfully install the 1.5.2 release on my Mac.
Can you elaborate more on which binary you downloaded and the operating system you used?
Thank you.

Ohh got it now, I had just copy pasted the command on the page:
aws s3api get-object --bucket healthai-public-assets-us-east-1 --key amazon-genomics-cli/nightly-build/amazon-genomics-cli.zip amazon-genomics-cli.zip
which gave me the nightly build.
Once I specified the version, as below it worked fine.
wget https://github.com/aws/amazon-genomics-cli/releases/download/v1.5.2/amazon-genomics-cli-1.5.2.zip


[question] Type Props for basic JSX elements

Are there any packages that define the list of props that a react JSX element can take?
We would like to type our components as exact, but it's a pain to manually list all of these.

These should also be listed in the props sections of $JSXIntrinsics definitions in https://github.com/facebook/flow/blob/60e640c2287c2e7b9d0f261e4c8a617763005f1e/lib/react-dom.js#L246
A few questions for the friendly maintainers (cc @samwgoldman):

Are there any plans on this on the roadmap?
Is this something you would accept PRs for or do you prefer flow react-dom bindings to remain unopinionated about props of JSX intrinsics?

Essentially a duplicate of https://github.com/facebook/flow/issues/3773

Duplicate of #3773


start guidelines

See #19

Thanks Will!  I'm very appreciative of the time spent thinking about documentation.  It's not something I've had the luxury to do.  @mcguffk, I might leave the the ball in your court to review this since you were part of that discussion.  @taylorr4, since you'll likely be supporting whatever standards we create, I'm guessing you might want to weigh in as well.


upstream_rq_total is not consistent during H1 and H2 circuit breaking

For the HTTP/1 connection pool, we increment upstream_rq_total even if the request ends up being circuit broken. For the HTTP/2 connection pool we do not.
This is confusing and we should fix this to be consistent, one way or the other.
cc @danielhochman @junr03

I can do this, I was just touching nearby code. I'll get @snowp to help me if I need backup.


[release-1.25] Service LB seems redirecting traffic to other nodes, even externalTrafficPolicy is Local

Backport:

#6633

Validated on master branch using commit id a2521856f56b2ad6d14797108e73bf8a9fab9a9f from release-1.25 branch
Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
SLES SP4
Cluster Configuration:
Two node: One server one agent
Config.yaml:
cat /etc/rancher/k3s/config,yaml
write-kubeconfig-mode: 644
token: <REDACTED>
selinux: true
cluster-init: true
disable:
  - traefik
  - local-storage

Steps to reproduce the issue  and validate the fix

Copy config.yaml
Install k3s

curl -fL https://get.k3s.io | INSTALL_K3S_COMMIT=a2521856f56b2ad6d14797108e73bf8a9fab9a9f sh -s - server

Deploy the yaml shared in the issue
nginx.yaml

apiVersion: v1
kind: Namespace
metadata:
  name: front-nginx
---
apiVersion: v1
kind: Service
metadata:
  namespace: front-nginx
  name: nginx
spec:
  type: LoadBalancer
  selector:
    app: nginx
  externalTrafficPolicy: Local
  ports:
    - protocol: TCP
      port: 80
      appProtocol: http
---
apiVersion: apps/v1
kind: Deployment
metadata:
  namespace: front-nginx
  name: nginx
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 1
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
        - name: nginx
          image: nginx:1.23.2-alpine
          ports:
            - containerPort: 80

> kubectl get nodes
NAME               STATUS   ROLES                       AGE     VERSION
ip-172-31-15-110   Ready    <none>                      7m46s   v1.25.6+k3s-a2521856
ip-172-31-7-169    Ready    control-plane,etcd,master   11m     v1.25.6+k3s-a2521856

> kubectl get pods -o wide -A
NAMESPACE     NAME                              READY   STATUS    RESTARTS   AGE     IP          NODE               NOMINATED NODE   READINESS GATES
front-nginx   nginx-cdbbc86c6-htfmk             1/1     Running   0          2m23s   <IP_ADDRESS>   ip-172-31-15-110   <none>           <none>
kube-system   coredns-597584b69b-md4z7          1/1     Running   0          9m21s   <IP_ADDRESS>   ip-172-31-7-169    <none>           <none>
kube-system   metrics-server-5f9f776df5-2xjvl   1/1     Running   0          9m21s   <IP_ADDRESS>   ip-172-31-7-169    <none>           <none>
kube-system   svclb-nginx-b1e790d6-t2gm7        1/1     Running   0          2m23s   <IP_ADDRESS>   ip-172-31-15-110   <none>           <none>
kube-system   svclb-nginx-b1e790d6-wm7qw        1/1     Running   0          2m23s   <IP_ADDRESS>   ip-172-31-7-169    <none>           <none>

To reproduce: k3s version v1.25.6+k3s1
Access 80/tcp of both nodes and note request from both nodes are successful
curl http://SERVERIP
<!DOCTYPE html>

<title>Welcome to nginx!</title>

Welcome to nginx!

Validate when externalTrafficPolicy: Local is not set, Service LB should redirect traffic to both nodes
curl http://SERVERIP
<!DOCTYPE html>

<title>Welcome to nginx!</title>


Update sort.c

Added counting sort algorithm

congratulations on your hactoberfest contribution. if you like this repo then give it a star. Happy hacking..


Inject canonical tag on mkdocs as we do with Sphinx

In Sphinx if a user has a custom domain we setup the canonical tag for the user (we also have some docs for that feature https://docs.readthedocs.io/en/latest/canonical.html)
In Sphinx we do that here https://github.com/rtfd/readthedocs.org/blob/9b2b17c0fc603267b4b20f5923862c2db82602da/readthedocs/doc_builder/templates/doc_builder/conf.py.tmpl#L95-L95
On mkdocs we don't do that, but it's possible using the site_url setting https://www.mkdocs.org/user-guide/configuration/#site_url
We can do that here
https://github.com/rtfd/readthedocs.org/blob/9b2b17c0fc603267b4b20f5923862c2db82602da/readthedocs/doc_builder/backends/mkdocs.py#L107-L107
Ref https://github.com/rtfd/readthedocs.org/issues/3137

@stsewd I would like to take this issue up.
I didn't find the way to get the canonical url of the project, is it present in the keyword arguments that append_conf receive, i.e. __?

That comes from the project model, but this issue has the Needed: design decision label, we need to wait to be approved before writing some code

Just adding that looks like the site_url option have been there for a long time, nothing relevant on the changelog https://www.mkdocs.org/about/release-notes/#other-changes-and-additions-to-version-0160

Just btw MKdocs just yesterday added support for Environment variables in version 1.2.0, all you have to do is make a variable with the final URL available for the build :)

https://www.mkdocs.org/about/release-notes/#support-added-for-environment-variables-in-the-configuration-file-1954

As mentioned by @astrojuanlu, we can use environment variables in .mkdocs.yml and that would be valuable in general to users.
However, then this needs to be fixed: https://github.com/readthedocs/readthedocs.org/issues/8529


[5.5] SwiftPM complains about @main in non main.swift file when integrated driver is not enabled

This is the 5.5 cherry-pick of https://github.com/apple/swift-package-manager/pull/3546.  This fix has been in the main branch for 12 days.
One of several different code paths in BuildPlan.swift are taken depending on whether the integrated Swift driver is enabled, whether explicit modules are enabled, whether there is a single source file in the module, etc.
In the non-integrated-driver case, the code path for adding a -parse-as-library when necessary wasn't taken. This moves that code to a more central place, and extends a unit test to test both single and multiple file Swift targets, which seems to trigger the difference in code paths.
Separately, there should be a JIRA to eliminate the code duplication in BuildPlan.swift, because it leads to this kind of bug.
rdar://78080245

@swift-ci please test


Error formatting 3 files in trio

Using an install of black master (fa159bb3576b0d8a79) running on Debian testing's python 3.6, trying to format the trio source code, it fails on 3 different files. Reproduction script:
$ git clone git@github.com:python-trio/trio.git
$ cd trio
$ git checkout 24cf95a62e9c6b683f7f875201dc2649a33230d8
$ black trio

Errors in the output:
error: cannot format trio/tests/test_socket.py: 18
error: cannot format trio/tests/test_highlevel_open_tcp_stream.py: INTERNAL ERROR: Black produced invalid code: invalid syntax (<unknown>, line 298). Please report a bug on https://github.com/ambv/black/issues.  This invalid output might be helpful: /tmp/blk_usla4iw_.log
error: cannot format trio/_core/tests/test_run.py: INTERNAL ERROR: Black produced code that is not equivalent to the source.  Please report a bug on https://github.com/ambv/black/issues.  This diff might be helpful: /tmp/blk_8btywbcq.log

Here are the log files:
blk_8btywbcq.log
blk_usla4iw_.log

Thanks for reporting, I noticed this too, hence no release yet. There are three problems:

Trailing comma gets put in a wrong place if there's a trailing comment. Example:

    assert scenario.connect_times == {
        "<IP_ADDRESS>": 0,
        "<IP_ADDRESS>": 0.300,
        # <IP_ADDRESS> was never even started
        ,
    }

When # yapf: disable was found in trio/_core/tests/test_run.py, Black decided to discard that content entirely. 🤣

Or should I say, 18. This is again a # yapf: disable-related bug. This time it's when you disable twice in a row. Black doesn't support statement-level format disabling and it gets confused by this.

async def test_getaddrinfo(monkeygai):
    check(res, [
        (tsocket.AF_INET,  # <IP_ADDRESS> is ipv4
         tsocket.SOCK_STREAM,
         tsocket.IPPROTO_TCP,
         "",
         ("<IP_ADDRESS>", 12345)),
    ])  # yapf: disable

    check(res, [
        (tsocket.AF_INET6,
         tsocket.SOCK_DGRAM,
         tsocket.IPPROTO_UDP,
         "",
         ("::1", 12345, 0, 0)),
    ])  # yapf: disable

I'll fix all three this weekend.

Thanks for reporting, all this is fixed in 18.4a0!


Problem with zoomToBoundingBox()

I have problem to use zoomToBoundingBox(). According to what I've read somewhere here, I've created my own MapView class to call zoomToBoundingBox() in onLayout(). Here is my code:
public class MyMapView extends MapView {

    public void setBoundingBox(BoundingBoxE6 boundingBox) {
        this.boundingBox = boundingBox;
    }

    private BoundingBoxE6 boundingBox = null;

    ...

    @Override
    protected void onLayout(boolean arg0, int arg1, int arg2, int arg3, int arg4) {
        super.onLayout(arg0, arg1, arg2, arg3, arg4);

        // Now that we have laid out the map view,
        // zoom to any bounding box
        if (this.boundingBox != null) {
            this.zoomToBoundingBox(this.boundingBox);
        }
    }
}

So, In my fragment I initialize the boundingBox:
@Override
public void onResume() {
    super.onResume();

    final BoundingBoxE6 boundingBox = new BoundingBoxE6( ... );
    // this gives ``N:44899816; E:5020385; S:44899001; W:5019482``

    mMapView.setBoundingBox(boundingBox);

    mMapView.invalidate();
}

So, the calculated bounding box should obviously cause to get a max zoom level but it doesn't.
First, problem in calculation; onLayout() is called after onResume() and I explored the code of zoomToBoundingBox() and here are the results on each data calculated:
zoomLevel = 0
maxZoomLatitudeSpan = 55.08
requiredLatitudeZoom = 14.0  // I have a big doubt on this result!
maxZoomLongitudeSpan = 472.07
requiredLongitudeZoom = 17.0  // hum well, better but not best expected value
So zoomToBoundingBox() will choose a zoom level of 14.0 why? Anyway,  requiredLongitudeZoom of 17.0 is not the best result. As you can see here (http://imgur.com/ZEnX2Za), the max level of 18.0 is possible.

So how should I use zoomToBoundingBox() ?

Couple of notes.

extending MapView isn't necessary in this case
in OnResume of your activity,   create your bounding box, then call zoomToBoundingBox.

That should get you going...
if you set the bounding box on a map view that restricts the user from panning the map outside of that bounds.

Hi spyhunter99,
I tested the MapView extend solution after searching on Internet because using it in onResume() didn't work. I get the same result in fact.
And I suppose that problem comes from requiredLatitudeZoom calculation with a result of 14.0 which doesn't correspond to an expected value.
About the restriction, maybe you are talking about setBoundingBox(), because using zoomToBoundingBox() doesn't prevent to pan the map and I really really hope that it shouldn't!

Correct, I was referring to setBoundingBox because I thought I saw that in
your sample code.
On Thu, Jan 7, 2016 at 2:42 AM, Alain<EMAIL_ADDRESS>wrote:

Hi spyhunter99,
I tested the MapView extend solution after searching on Internet because
using it in onResume() didn't work. I get the same result in fact.
And I suppose that problem comes from requiredLatitudeZoom calculation
with a result of 14.0 which doesn't correspond to an expected value.
About the restriction, maybe you are talking about setBoundingBox(),
because using zoomToBoundingBox() doesn't prevent to pan the map and I
really really hope that it shouldn't!
—
Reply to this email directly or view it on GitHub
https://github.com/osmdroid/osmdroid/issues/236#issuecomment-169587150.

Ok my problem really with zoomToBoundingBox().

Hello,
I wakeup this thread because I still cannot get zoomToBoundingBox working when I call it from onResume().
When I call it later (via a dcated button for example) with the exact same values, it works well.

try calling it after a delayed started. I think there's a few related issues to this
#264 #142
Also try this
MapView.addOnFirstLayoutListener(new OnFirstLayoutListener() { ...});

Hello, I tried to implement MapView.addOnFirstLayoutListener(new OnFirstLayoutListener() { ...}); and it seems to be the right place to call zoomToBoundingBox().
Thanks a lot

Hello,
I tried to call zoomToBoundingBox() in MapView.addOnFirstLayoutListener(new OnFirstLayoutListener() { ...}); but that doesn't solve all problems.
The view is well centered (but calling it with animate=true doesn't work at all #264 but the zoom level is not ok. Below is the code:
mMapView.addOnFirstLayoutListener(new MapView.OnFirstLayoutListener() {

        @Override
        public void onFirstLayout(View v, int left, int top, int right, int bottom) {

            final BoundingBoxE6 boundingBox = new BoundingBoxE6(44899816, 5020385,44899001,5019482);
            mMapView.zoomToBoundingBox(boundingBox, false);
            mMapView.invalidate();
    }
}

If I put the same code in an onClickListener(), it perfectly works:

Here is some debug message to explain what I try to do when I get the problem:
Here I open the fragment map with a given bounding box

D/MyApp: Fragment_agmap: onCreateView
I/OsmDroid: Using tile source specified in layout attributes: org.osmdroid.tileprovider.tilesource.XYTileSource@7118d91
I/OsmDroid: Using tile source: Mapnik
I/OsmDroid: sdcard state: mounted
I/OsmDroid: sdcard state: mounted
I/OsmDroid: sdcard state: mounted
V/MyApp: PauseHandler: onResume
D/MyApp: bounding box N:44899816; E:5020385; S:44899001; W:5019482
I/OsmDroid: rescale tile cache from 0 to 14
I/OsmDroid: Finished rescale in 2ms
I/OsmDroid: Tile cache increased from 9 to 20
D/cr_Ime: [ImeAdapter.java:587] detach

Here I click a button to zoom out to a bigger box.

I/MyApp: btFullItinerary clicked
D/MyApp: bounding box N:44900127; E:5021498; S:44899001; W:5019482
I/OsmDroid: rescale tile cache from 14 to 18
I/OsmDroid: Finished rescale in 104ms
I/art: Background partial concurrent mark sweep GC freed 23788(2MB) AllocSpace objects, 5(15MB) LOS objects, 20% free, 60MB/76MB, paused 4.119ms total 192.565ms
D/cr_Ime: [ImeAdapter.java:587] detach

Here I click a button to zoom in to the original box

I/MyApp: btFullItinerary clicked
D/MyApp: bounding box N:44899816; E:5020385; S:44899001; W:5019482

I confirm that the initial zoomToBoundingBox() works only for certain bounding boxes, even if called from onFirstLayout(). The problem seems to be somewhere inside the calculation of maxZoomLatitudeSpan, maxZoomLongitudeSpan: their computed values differ depending on the initial zoom level and bounding box (with all the other parameters being the same, including the size of the view).
I suspect that this has something to do with the initial boundingBox() which appears to be very large, possibly introducing errors in the Projection() calculation? But this is just a guess.

Great info! It may be enough for a unit test
On Oct 28, 2016 6:31 PM, "Szymon Tomasz Stefanek"<EMAIL_ADDRESS>wrote:

I confirm that the initial zoomToBoundingBox() works only for certain
bounding boxes, even if called from onFirstLayout(). The problem seems to
be somewhere inside the calculation of maxZoomLatitudeSpan,
maxZoomLongitudeSpan: their computed values differ depending on the initial
zoom level and bounding box (with all the other parameters being the same,
including the size of the view).
I suspect that this has something to do with the initial boundingBox()
which appears to be very large, possibly introducing errors in the
Projection() calculation? But this is just a guess.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/236#issuecomment-257044143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4kGeLEwqhf42CEjbgx6i5jlJSHcJdbks5q4neLgaJpZM4G_nqA
.

Investigating more. I believe that the calculation of maxZoom*Span should not depend on the current bounding box (in map coordinates) but only on the view size and the maximum zoom level.
Calculations involving the current bounding box carry an error depending on the currently set zoom size and center coordinates. If I'm not wrong, if the current level of detail is set to 1 then the current map size is tileSize << 1 (512 in my case) and the average horizontal error in integer pixel coordinate mapping is something in the order of half a degree (in the middle of the map). The error grows pretty fast as the coordinates approach the upper/lower edge of the map.
A "hackish" workaround for this issue is to first set the map zoom to a "reasonable" level (I used 14), center it somewhere in the middle and then call zoomToBoundingBox().

I just made a quick sample that centers the map on the vatican, then varied the startup zoom level and compared the results. Interesting to say the list
start zoom levels 18-4 yielded zoom 13
start zoom 3 yielded 14
start zoom 2 yielded 15
start zoom 1-0 yielded 10
The expected zoom was actually 15. Something is definitely wrong. Rerunning the same test with a button click now...

Last update for tonight. Same results from a button onclick listener. Also of note, if i click the button a second time, we get the correct result (zoom=15). I don't think startup has anything to do with it. It's a calculation problem

Hmmm...when you click the button a second time you have already set "reasonable" initial conditions with the first click.
More guessing: my feeling that this bug is caused by the error introduced by boundingBox() grows steadily. boundingBox() shouldn't be used here. If there is really no way around it then a hack is to first set a high zoom level and a point close to coordinates (0,0), so the error introduced is low. However, it's a hack. It should be possible to calculate the maximum lat/long span with only the view size, tile size and maximum zoom level as input.

simplest solution may be to just call zoomToBoundingBox twice.
        final BoundingBox boundingBox = new BoundingBox(41.906802,12.445436,41.900073,12.457852 );
        mMapView.zoomToBoundingBox(boundingBox, false);
        mMapView.zoomToBoundingBox(boundingBox, false);
        mMapView.invalidate();

this works for me on all zoom levels that i've tested. Always goes to the expected zoom level (15)

An iterative solution :)
...a bit hacky... but it works :D

a real solution to this has been committed by @monsieurtanuki. Thanks for the bug report. This one has been open way too long


Update Readme.md

@Git-Dev-Admin-010

Hi

how to make money on linux
Le lundi 24 octobre 2022, Git-Dev-admin-010 @.***> a
écrit :

Hi
—
Reply to this email directly, view it on GitHub
https://github.com/btccom/btcpool-ABANDONED/pull/508#issuecomment-1289499948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPJ7EVUR47OAYSPKR7EZKDWE3P4JANCNFSM6AAAAAARNJCSEQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Compatible with Django 1.9

Is this project updated for 1.9?

Try it?

Hello @aaugustin! Thanks for awesome work on django-debug-toolbar.
Unfortunately this doesn't work for me with Django 1.9.7. I'm using Python 3.5 and Django 1.9.7.
What is strange when I include into INSTALLED_APPS = Base.INSTALLED_APPS + ('debug_toolbar',)
I've got hanging app. Django just freeze forever. When I cancel (Ctrl+C) the django process I got this stacktrace:
    _setup()
  File "/usr/local/lib/python3.5/site-packages/configurations/__init__.py", line 17, in _setup
    django.setup()
  File "/usr/local/lib/python3.5/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/local/lib/python3.5/site-packages/django/apps/registry.py", line 71, in populate
    with self._lock:

It's maybe problem related to django-configurations. Feel free to ask whatever you need to find root cause of this problem. But without debug_toolbar it works fine, so probably this is combination of this issue.

Uh, annoying. Are you using the "explicit setup" described in the installation instructions?

No, I'm not using that.

There's a good chance the explicit setup will resolve the problem that causes this traceback, regardless of the version of Django being use.
Apps such as django-configurations are incompatible with the magic setup.

Hi, I currently use debug-toolbar with django 1.9.7 and Python 3.5 without any issues and manual configurations so it might be collisions with another addons.

Django debug toolbar is incompatible with Django 1.9 in the automatic mode, because it hangs here:
def patch_root_urlconf():
    from django.conf.urls import include, url
    from django.core.urlresolvers import clear_url_caches, reverse, NoReverseMatch
    import debug_toolbar
    try:
        reverse('djdt:render_panel')
    except NoReverseMatch:
        urlconf_module = import_module(settings.ROOT_URLCONF)
        urlconf_module.urlpatterns = [
            url(r'^__debug__/', include(debug_toolbar.urls)),
        ] + urlconf_module.urlpatterns
        clear_url_caches()

On the line reverse('djdt:render_panel').
I'm reverting back to manual setup, but this problem requires attention.

I think the debug toolbar should drop the automagic setup.

I think the debug toolbar should drop the automagic setup.

If this suggestion is serious, I have created PR to do so.

Well... Let's say 80% serious.
I actually believe that the automagic setup isn't a tractable concept.
But I'm not eager to take responsibility for removing it and deal with frustrated users.

What about using a deprecation path, similar to Django's strategy? We could deprecate the automatic setup for the next release with a loud warning, and remove in the following (or later) release.

I personally agree. Because with Django 1.10 automatic setup definitely doesn't work. I suppose because of new style middleware?

The toolbar is not working for me in Django 1.9, even with the explicit setup. There are no errors in my application, but the toolbar does not show up.

Have problems with automatic setup, but doesn't crash with it.


Update tests to use async/await instead of looking at Tasks directly

The current stable version of the Unity Test Framework (UTF) does not support async tests. This is the main reason that no tests use await in them.
However, since around Unity 2021.3, task cancellation no longer works synchronously (I've reported an issue to Unity), and we have to use workarounds to make the tests pass. This is not optimal, as it's no longer testing the actual behaviour you would see when running in Unity.
The only way I can think of to mitigate this it to start using the UTF prerelease version, which does support async tests. This way all tests could be written using await, no direct Task inspection would be required, and the workarounds could be removed.
Even if the issue in Unity is fixed, this would be the best thing to do. The only downside is having to use a prerelease version of UTF, and the effort that will have to be put into rewriting most of the tests.

Based on work in #198, it's not obvious to me that some direct Task inspection is still required for checking that a task has not completed.
The new methods AwaitFailureExceptionForUnity and AwaitTaskCompletionForUnity seem to be a good solution to await tasks or errors, and we can also assert that they complete (later) within the same frame.


Links work on iPhone X but not iPhone 6s

App links work on an iPhone X. They don't work on iPhone 6s running iOS 14.01.
The link won't open the app. I can long-press the link, but it doesn't give the app as an option like it does on the iPhone X.

Branch works when I add cordova-plugin-deeplinks
Adding that plugin says:
"iOS project Code Sign Entitlements now set to: My App/Resources/My App.entitlements
Entitlements file is in reference section."

I looked and there's a file. Apparently branch doesn't create this file. The docs say you must add it yourself when using Capacitor, but I'm not using Capacitor.


Replace badges in README.md with cooler badges

Current badges in the README by shields.io can be replaced.
We can use the flat-square style on shields.io while generating badges for the repository for this.

Hey @osBins, Can i work on this issue?

Sure! Assigning the issue to you.

Thanks a lot. I'm looking forward to it :)


Change licence to MPL 2.0

This will allow people to use SciD in proprietary applications, while preventing them from releasing proprietary versions of the library itself.

It has been pointed out that this would prevent code from being moved from SciD to Phobos, so let's not do this now.


Release 0.8.0

Version 0.8.0 announces a few changes. The release is scheduled for early October, and the milestone is available here: https://github.com/vincent-herlemont/native_db/milestone/1
The purpose of this issue is to list the various changes that will be included.

Done


List of Supported Languages for Syntax Highlighting is out of date

I have just noticed that not all languages given in the documentation do render correctly but some that are not given actually do. I assume there have been some updates in the rogue library that have been integrated but not made their way into the documentation.
For example, when writing:
```ps1
some-powershell-command "some string" #comment
```

This should look like
some-powershell-command "some string" #comment

But actually looks like
some-powershell-command "some string" #comment

However, using powershell instead of ps1 as language identifier works like a charm.
The current list of identifiers and supported languages by rogue can be found here.
Sidenote: Interestingly, Github supports the union of identifiers for those examples, I've tested.

That's a good idea. I've filed a ticket to discuss as a team before we could open it up as a Help Wanted ticket: https://mattermost.atlassian.net/browse/MM-22249

@cwarnermm I could grab this one.
@hmhealey I want to make sure I'm following this correctly, but looking through everything it appears that the definitions moved from the syntax_highlighting.tsx file over to the constants.jsx file, but that you're still only able to use highlighting for the languages in that list?
Then I guess the next question would be do we want to include the aliases in the documentation as well? For example for MarkDown you can use MarkDown but also md and mkd. Do we want to maybe convert that section to a table listing the languages and all of the available aliases? Or is that a little too messy/unwieldy?

Thanks, @ewwollesen! I've assigned you to this ticket.

@cwarnermm How do you feel about something like this instead of how the languages are listed currently? It seems potentially more useful, but on the other hand it's kind of big so I don't know.

Thanks! @ewwollesen - A table-based approach is likely easier to read and scan quickly. This approach also lends itself well to listing many aliases, where necessary. Let's go with this approach!


Further improve release script

Change script to:

[ ] Add commit author to the changelog/release notes
[ ]  Do actions for current fork/repository instead of main repository.
[ ] Ask before publishing a new release/npm version.
[x] Handle case when snyk-snapshot.json isn't updated.
[ ] Make it work properly on Windows (see: #564)
[ ] Other?

Did you do the snyk one?

Did you do the snyk one?

Yes.

[ ] Handle case when snyk-snapshot.json isn't updated.

[X] Better error output
[X] Switch all shelljs.exec to async

[ ] Make it work properly on Windows (see: #564)

I believe the script fails on Windows if there are more than 1 change. At least that's what I think was happening to me the other day.

[ ] npm 2FA

[ ] Automatically update performance-budget/connections.ini (see: https://github.com/sonarwhal/sonarwhal/pull/798/files#r166410722)

[ ] Rollback Git(Hub) changes (latest commit(s), tags, etc. if something goes wrong


Glridb 504 improve validation for contacts and agencies

Improved error logging (server side) and error handling (ui side)

Awesome. Thanks!


Colour Picker: Add a section to save some favourite colours

The new colour picker is great, but one thing lost from the old one is being able to quickly select certain colours without having to manually put them in every time. Being able to set a list of maybe 8 colours would be particularly useful for things like #5890 or the Screen Markers plugin.

Alternatively, a "recent colors" section would probably satisfy this without needing as much UX design.

Yeah that'd get the job done too, preferrably remembered between sessions


Feature request : view missing episodes in TvShows

Hi
Can you please add some way to identify what are missing episodes in TvShows ?
This feature could be provided by contextual menu at tvshow or season level.
Missings could be find by comparing files from local (real) and files from remote data (theorical).
Thanks
Louis

The same feature for missing seasons, please:)

also add in the main-tree the local existing and in tvdb.com existing seasons/episodes like this:

have included that into the V3 branch


fix bf16 cast on disktensors

the cast in #2698 won't work because we need to bitcast to uint16 from the uint8 disktensor on-disk (before realizing to Device.DEFAULT) - because bitcast between different sizes isn't supported.
more regression tests in 0e36de09752f73c10d922c3256c04aceafa11b38 (test_disktensor was edited in the same PR with a typo, otherwise this would've been caught earlier).
I understand these changes are doing the bf16 cast in a different place than the original cleanup. The reason why I'm limiting the hack to disk-only is to have control over the uint8->uint16 in-disk bitcast.

I don't get what's wrong now. I don't think you need these hacks in the linearizer.
It's okay if a backend doesn't support a dtype, we have to be robust to this in a generic way.

I will never merge hacks that look like this, adding if statements to multiple places.

If a disk tensor is bfloat16, and you do .to('cpu') on it, that should just fail. CPU doesn't support BF16

I'll reopen and come back to this

That sounded promising, are you still working on a fix @Qazalin ?


Add Microsoft.Office.Interop.Excel reference

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Add the following reference to Tabular Editor so that T.E. can communicate with Excel.
Microsoft.Office.Interop.Excel
This would be helpful for exporting data/metadata to Excel (instead of a text file) as well as reading metadata from an Excel file.

Add the following at the top of your script:
#r "Microsoft.Office.Interop.Excel"

// ... your script here ...

More information: https://github.com/otykier/TabularEditor/wiki/Advanced-Scripting#net-references

ah amazing, thanks!


Remove crossgen'ed IL assemblies and then rename NI assemblies to the same as the corresponding IL images.

This is to make sure:

The dependency existence check by powershell.exe will pass for all TPAs.
CoreCLR by default will load the NI images even though it's using names of the IL images.

When the legacy APIs like "GetAssemblies" are back, we probably want to retire PSALC (to what extent is still unknown) and solely depend on the CoreCLR default load context, and this is the way to make sure the CoreCLR default load context will load the NI images produced in our post-build.

Hi @daxian-dbw, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Dongbo Wang). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@mirichmo could you please review this? It's tightly related to the new dotnet.core package adoption. This alternative is also suggested by the CoreCLR team.

The comment is updated to make it easy to understand.


Make installed system use kernel from the ISO

This massively reduces install time, as now compiling the kernel on the device is not required.

Reviewed, looks good.
SHA256 of the iso is 7976066e7288e00f9b7348a0bb7ec16ec09fd5d0b71f11a536cf9b2146d46c25
Testing now

Tested, the install is now much quicker. The largest thing that needs to be compiled now seems to be mesa, but this should be solved by updating nixpkgs.


Unable to install ZLS 0.11.0 for Zig version 0.11.0

Can someone please tell me how to install ZLS manually? Doing it through this extension always fails.
It downloads the ZIG tarball and installs it. Then it downloads the ZLS tarball and upon installing it:-
TypeError: Cannot read properties of undefined (reading 'status')
Source: Zig Language

macOS Sonoma
System installed Python 3.11.6
Version: 1.86.0-insider
Commit: 271fb7fbd599b49a1482ea7284a50b3229317f96
Date: 2024-01-19T05:46:59.001Z
Electron: 27.2.1
ElectronBuildId: 26149897
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.3.0

That's strange, would you be able to install a modified version of the extension to get a more accurate error message?
Steps:
git clone https://github.com/ziglang/vscode-zig.git --depth 1 --single-branch
git apply patch
npm install
npx vsce package
code --install-extension vscode-zig-0.5.1.vsix

patch:
diff --git a/src/zls.ts b/src/zls.ts
index b6fe42d..5a77334 100644
--- a/src/zls.ts
+++ b/src/zls.ts
@@ -216,7 +216,7 @@ async function installVersion(context: ExtensionContext, version: SemVer) {
             })).data;
         } catch (err) {
             // Missing prebuilt binary is reported as AccessDenied
-            if (err.response.status == 403) {
+            if (err.response != undefined && err.response.status == 403) {
                 window.showErrorMessage(`A prebuilt ZLS ${version} binary is not available for your system. You can build it yourself with https://github.com/zigtools/zls#from-source`);
                 return;
             }

And if not, you can manually install ZLS by downloading https://zigtools-releases.nyc3.digitaloceanspaces.com/zls/0.11.0/aarch64-macos/zls, making it executable with chmod and setting zig.zls.path to it.


About the portal > Logging in (French Subheading)

Discrepancy on https://staging.covid-hcportal.cdssandbox.xyz/fr/about/create-an-account
Not the same as Figma screens: https://www.figma.com/file/znPqLTQQDcUkaNjdDcShiz/Exposure-Notification-Health-Portal?node-id=8362%3A440
In Figma:
FR: "Vous n'avez pas de téléphone mobile?"
In staging:
FR: "Pas de téléphone mobile?"

Pull Request for this issue has been created - https://github.com/cds-snc/covid-alert-portal/pull/733

Merged in stage and production.


Staking Exploit

Following an audit of your PoSV2 code changes looking for flaws and exploits, I found a small one, small enough not to bother exploiting myself. I see you have added an 8% payment of stake rewards to a developer fund. In the block validation code you only check that the coinstake transaction has a vout to the dev address. The payment could be for zero and the block would still pass validation. You may want to tighten up on this, at least checking for a non-zero payment or perhaps something that is at least over a % threshold. Otherwise people can easily boost their stakes with the dev fund losing out. You may as well make the development fund % configurable since you've in effect made it a voluntary payment from a protocol perspective as things stand.

Thanks for taking the time to review our code, it is always appreciated.
Yes you are correct, we were only checking for the existence of the dev vout address and that the total sum of the stake reward matched.
In our initial thoughts on how to handle the dev payment, there was a desire to make the amount configurable. Ultimately we settled on sending a fixed amount.
While we may revisit making it a configurable amount in a future release, we take your point to tighten up this oversight in the short term.
Cheers.

Issue resolved, but as change is minor as well as consensus-breaking, coded and withdrawn, will be included in next required soft-fork/consensus-breaking update.


Error with latest angular2 rc app running with systemjs

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1
What steps will reproduce the problem?

Open http://systemjs.craigsmenu.com/ to verify that the site works. (It may take up to 15s to load)
Try use PhantomJS to open the site.
It does not render properly. See details below.

Which operating system are you using?
Mac
Did you use binary PhantomJS or did you compile it from source?
Binary
Please provide any additional information below.

The script I used is:
var page = require('webpage').create();
page.open('http://systemjs.craigsmenu.com/', function(status) {
    console.log("status is: " + status);
    if (status === "success") {
        console.log("success");
        setTimeout(function() {
            console.log("screenshot");
            page.render('screenshot.png');
            phantom.exit();

        }, 10000);
    }
    else {
        console.log("not success");
        phantom.exit();
    }
});

The command I ran is phantomjs ./craigsmenu.js
I do not get a proper snapshot.png and the console shows error:
MBP:nld-crawler-js gordon$ ./phantomjs/bin/phantomjs ./craigsmenu.js
status is: success
success
Error: eval@[native code]
        invoke@http://systemjs.craigsmenu.com/node_modules/zone.js/dist/zone.js:323:34
        run@http://systemjs.craigsmenu.com/node_modules/zone.js/dist/zone.js:216:50
        http://systemjs.craigsmenu.com/node_modules/zone.js/dist/zone.js:571:61
        invokeTask@http://systemjs.craigsmenu.com/node_modules/zone.js/dist/zone.js:356:43
        runTask@http://systemjs.craigsmenu.com/node_modules/zone.js/dist/zone.js:256:58
        drainMicroTaskQueue@http://systemjs.craigsmenu.com/node_modules/zone.js/dist/zone.js:474:43
        g@http://systemjs.craigsmenu.com/node_modules/core-js/client/shim.min.js:8:19360
        http://systemjs.craigsmenu.com/node_modules/core-js/client/shim.min.js:8:19482
        k@http://systemjs.craigsmenu.com/node_modules/core-js/client/shim.min.js:8:14322
        Evaluating http://systemjs.craigsmenu.com/app
        Error loading http://systemjs.craigsmenu.com/app

  http://systemjs.craigsmenu.com/:17
screenshot
MBP:nld-crawler-js gordon$

+1

I am afraid that Angular2 is not supported yet due to a modern JS (ES2015) features.

Thank you @Vitallium . Any plan to support it soon?

Could you please try again with 2.5 binary? Thanks!

Where do I get 2.5 binary? http://phantomjs.org/

@sunshineo here

I cannot run it
MBP:phantom gordon$ ./bin/phantomjs ./craigsmenu.js
dyld: Library not loaded: /usr/local/opt/webp/lib/libwebp.6.dylib
  Referenced from: /Users/gordon/Downloads/phantom/./bin/phantomjs
  Reason: image not found
Abort trap: 6
MBP:phantom gordon

@sunshineo you must install webp libraries. For example, in Ubuntu: sudo apt install webp

@Vitallium I'm on Mac. I downloaded from https://storage.googleapis.com/downloads.webmproject.org/releases/webp/index.html but cannot figure out how to install.

Just use HomeBrew to install it. This is the easiest way.

I did
brew install webp

It still complains
dyld: Library not loaded: /usr/local/opt/webp/lib/libwebp.6.dylib

Ironically, I have:
/usr/local/opt/webp/lib/libwebp.7.dylib
/usr/local/opt/webp/lib/libwebp.3.dylib
not libwebp.6.dylib .


Moving a VM between projects attempts a full disk copy, even when there's not sufficient available space.

Required information

Distribution: Ubuntu
Distribution version: 22.04.4
The output of "lxc info":

jsimpso@alcazar:~$ lxc info
config:
  core.https_address: '[::]:8443'
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- snapshot_schedule_aliases
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
- usedby_consistency
- custom_block_volumes
- clustering_failure_domains
- resources_gpu_mdev
- console_vga_type
- projects_limits_disk
- network_type_macvlan
- network_type_sriov
- container_syscall_intercept_bpf_devices
- network_type_ovn
- projects_networks
- projects_networks_restricted_uplinks
- custom_volume_backup
- backup_override_name
- storage_rsync_compression
- network_type_physical
- network_ovn_external_subnets
- network_ovn_nat
- network_ovn_external_routes_remove
- tpm_device_type
- storage_zfs_clone_copy_rebase
- gpu_mdev
- resources_pci_iommu
- resources_network_usb
- resources_disk_address
- network_physical_ovn_ingress_mode
- network_ovn_dhcp
- network_physical_routes_anycast
- projects_limits_instances
- network_state_vlan
- instance_nic_bridged_port_isolation
- instance_bulk_state_change
- network_gvrp
- instance_pool_move
- gpu_sriov
- pci_device_type
- storage_volume_state
- network_acl
- migration_stateful
- disk_state_quota
- storage_ceph_features
- projects_compression
- projects_images_remote_cache_expiry
- certificate_project
- network_ovn_acl
- projects_images_auto_update
- projects_restricted_cluster_target
- images_default_architecture
- network_ovn_acl_defaults
- gpu_mig
- project_usage
- network_bridge_acl
- warnings
- projects_restricted_backups_and_snapshots
- clustering_join_token
- clustering_description
- server_trusted_proxy
- clustering_update_cert
- storage_api_project
- server_instance_driver_operational
- server_supported_storage_drivers
- event_lifecycle_requestor_address
- resources_gpu_usb
- clustering_evacuation
- network_ovn_nat_address
- network_bgp
- network_forward
- custom_volume_refresh
- network_counters_errors_dropped
- metrics
- image_source_project
- clustering_config
- network_peer
- linux_sysctl
- network_dns
- ovn_nic_acceleration
- certificate_self_renewal
- instance_project_move
- storage_volume_project_move
- cloud_init
- network_dns_nat
- database_leader
- instance_all_projects
- clustering_groups
- ceph_rbd_du
- instance_get_full
- qemu_metrics
- gpu_mig_uuid
- event_project
- clustering_evacuation_live
- instance_allow_inconsistent_copy
- network_state_ovn
- storage_volume_api_filtering
- image_restrictions
- storage_zfs_export
- network_dns_records
- storage_zfs_reserve_space
- network_acl_log
- storage_zfs_blocksize
- metrics_cpu_seconds
- instance_snapshot_never
- certificate_token
- instance_nic_routed_neighbor_probe
- event_hub
- agent_nic_config
- projects_restricted_intercept
- metrics_authentication
- images_target_project
- cluster_migration_inconsistent_copy
- cluster_ovn_chassis
- container_syscall_intercept_sched_setscheduler
- storage_lvm_thinpool_metadata_size
- storage_volume_state_total
- instance_file_head
- instances_nic_host_name
- image_copy_profile
- container_syscall_intercept_sysinfo
- clustering_evacuation_mode
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  - <IP_ADDRESS>:8443
  - '[fd42:8de0:bb24:3ce3::1]:8443'
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
<snip>
    -----END CERTIFICATE-----
  certificate_fingerprint: 9539a5c67e0fcdf9813278c22264dcb5906a8e7f8b98229fb76afdd6beddaecd
  driver: lxc | qemu
  driver_version: 4.0.12 | 6.1.1
  firewall: nftables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    idmapped_mounts: "true"
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.15.0-33-generic
  lxc_features:
    cgroup2: "true"
    core_scheduling: "true"
    devpts_fd: "true"
    idmapped_mounts_v2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_allow_deny_syntax: "true"
    seccomp_notify: "true"
    seccomp_proxy_send_notify_fd: "true"
  os_name: Ubuntu
  os_version: "20.04"
  project: maas
  server: lxd
  server_clustered: false
  server_event_mode: full-mesh
  server_name: alcazar
  server_pid: 1352
  server_version: "5.1"
  storage: dir
  storage_version: "1"
  storage_supported_drivers:
  - name: lvm
    version: 2.03.07(2) (2019-11-30) / 1.02.167 (2019-11-30) / 4.45.0
    remote: false
  - name: zfs
    version: 2.1.2-1ubuntu3
    remote: false
  - name: ceph
    version: 15.2.16
    remote: true
  - name: btrfs
    version: 5.4.1
    remote: false
  - name: cephfs
    version: 15.2.16
    remote: true
  - name: dir
    version: "1"
    remote: false

Issue description
In a circumstance where the size of a VM's disk is larger than the amount of available space in the LXD storage backend, trying to move that VM between projects results in LXD trying to make a full copy of the VM and failing:
jsimpso@alcazar:~$ lxc storage list
+---------+--------+------------------------------------------------+-------------+---------+---------+
|  NAME   | DRIVER |                     SOURCE                     | DESCRIPTION | USED BY |  STATE  |
+---------+--------+------------------------------------------------+-------------+---------+---------+
| default | dir    | /var/snap/lxd/common/lxd/storage-pools/default |             | 6       | CREATED |
+---------+--------+------------------------------------------------+-------------+---------+---------+

jsimpso@alcazar:~$ df -h /var/snap/lxd/common/lxd/storage-pools/default
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2       110G   99G  4.7G  96% /

jsimpso@alcazar:~$ sudo ls -lh /var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/maas_alpha/root.img
-rw-r--r-- 1 root root 56G Jun 22 11:17 /var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/maas_alpha/root.img

jsimpso@alcazar:~$ lxc move alpha alpha --project maas --target-project default
Error: Migration operation failure: Create instance from copy: Failed to run: nice -n19 dd if=/var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/maas_alpha/root.img of=/var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/alpha/root.img bs=16M conv=nocreat iflag=direct oflag=direct: dd: error writing '/var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/alpha/root.img': No space left on device
652+0 records in
651+0 records out
10921967616 bytes (11 GB, 10 GiB) copied, 78.3542 s, 139 MB/s

If other VMs are attempting to write to that storage backend when it fills up, they appear to stall, and LXD loses communication with them. Once the qemu process has been killed, LXD can re-launch the VM as expected.
Steps to reproduce

Have two projects present so that we have something to move between
jsimpso@alcazar:~$ lxc project list
+----------------+--------+----------+-----------------+----------+-------------------------+---------+
|      NAME      | IMAGES | PROFILES | STORAGE VOLUMES | NETWORKS |       DESCRIPTION       | USED BY |
+----------------+--------+----------+-----------------+----------+-------------------------+---------+
| default        | YES    | YES      | YES             | YES      | Default LXD project     | 3       |
+----------------+--------+----------+-----------------+----------+-------------------------+---------+
| maas (current) | NO     | YES      | NO              | NO       | Project managed by MAAS | 5       |
+----------------+--------+----------+-----------------+----------+-------------------------+---------+

Having a storage backend with relatively little storage will make for easier testing, I tested with a 120GB disk.

Initialise a few VMs, give one a bigger disk:
lxc init ubuntu/jammy alpha --vm
ize=60GB
lxc start alpha
lxc launch ubuntu/jammy beta --vm
lxc launch ubuntu/jammy gamma --vm
lxc launch ubuntu/jammy delta --vm

Grow the VM disk:
lxc exec alpha -- dd if=/dev/zero of=anchor.file bs=1M count=50000 status=progress

You should now have a VM whose disk is larger than the amount of available store in the backend:
jsimpso@alcazar:~$ df -h /var/snap/lxd/common/lxd/storage-pools/default
 Filesystem      Size  Used Avail Use% Mounted on
 /dev/sda2       110G   61G   43G  59% /

 jsimpso@alcazar:~$ sudo ls -lh /var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/maas_alpha/root.img
 -rw-r--r-- 1 root root 56G Jun 22 09:00 /var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/maas_alpha/root.img

Open a connection to each running VM (lxd exec <vm> bash)

On two VMs, start slowly writing to disk. Then, move the large VM between projects:
root@beta:~# dd if=/dev/zero of=anchor.file bs=1 count=5000000000000 status=progress
root@delta:~# dd if=/dev/zero of=anchor.file bs=1 count=5000000000000 status=progress
jsimpso@alcazar:~$ lxc move alpha alpha --project maas --target-project default

During the move, the two VMs attempting to write to disk fully unresponsive, but the last one continues to respond to input.
We can then see that the qemu process is still running, but LXD has lost contact with it:
jsimpso@alcazar:~$ lxc move alpha alpha --project maas --target-project default
Error: Migration operation failure: Create instance from copy: Failed to run: nice -n19 dd if=/var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/maas_alpha/root.img of=/var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/alpha/root.img bs=16M conv=nocreat iflag=direct oflag=direct: dd: error writing '/var/snap/lxd/common/lxd/storage-pools/default/virtual-machines/alpha/root.img': No space left on device
652+0 records in
651+0 records out
10921967616 bytes (11 GB, 10 GiB) copied, 78.3542 s, 139 MB/s

jsimpso@alcazar:~$ lxc ls
+-------+---------+-------------------------+------+-----------------+-----------+
| NAME  |  STATE  |          IPV4           | IPV6 |      TYPE       | SNAPSHOTS |
+-------+---------+-------------------------+------+-----------------+-----------+
| alpha | STOPPED |                         |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
| beta  | STOPPED |                         |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
| delta | STOPPED |                         |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
| gamma | RUNNING | <IP_ADDRESS> (enp5s0) |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+

jsimpso@alcazar:~$ lxc start beta
Error: Failed cleaning config drive mount path "/var/snap/lxd/common/lxd/devices/maas_beta/config.mount": Failed unmounting "/var/snap/lxd/common/lxd/devices/maas_beta/config.mount": Failed to unmount '/var/snap/lxd/common/lxd/devices/maas_beta/config.mount': device or resource busy
Try `lxc info --show-log beta` for more info
jsimpso@alcazar:~$ lxc info --show-log beta
Name: beta
Status: STOPPED
Type: virtual-machine
Architecture: x86_64
Created: 2022/06/22 11:11 AWST
Last Used: 2022/06/22 11:11 AWST
Error: open /var/snap/lxd/common/lxd/logs/maas_beta/qemu.log: no such file or directory

jsimpso@alcazar:~$ ps aux |  grep beta
root        9911  0.0  0.0  79904  3424 ?        Ssl  11:11   0:00 /snap/lxd/23037/bin/virtiofsd --fd=3 -o source=/var/snap/lxd/common/lxd/devices/maas_beta/config.mount
lxd         9927 19.4  7.6 1934532 614632 ?      Sl   11:11   2:27 /snap/lxd/23037/bin/qemu-system-x86_64 -S -name beta -uuid 159e794b-17e6-4658-869e-73f996996395 -daemonize -cpu host,hv_passthrough -nographic -serial chardev:console -nodefaults -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=allow,resourcecontrol=deny -readconfig /var/snap/lxd/common/lxd/logs/maas_beta/qemu.conf -spice unix=on,disable-ticketing=on,addr=/var/snap/lxd/common/lxd/logs/maas_beta/qemu.spice -pidfile /var/snap/lxd/common/lxd/logs/maas_beta/qemu.pid -D /var/snap/lxd/common/lxd/logs/maas_beta/qemu.log -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -runas lxd
root        9930  0.0  0.1 1211832 13584 ?       Sl   11:11   0:00 /snap/lxd/23037/bin/virtiofsd --fd=3 -o source=/var/snap/lxd/common/lxd/devices/maas_beta/config.mount
jsimpso    10698  0.0  0.2 1384848 17496 pts/1   Sl+  11:14   0:00 lxc exec beta bash

Killing the process returns the console:
jsimpso@alcazar:~$ sudo kill 9927
jsimpso@alcazar:~$
----
root@beta:~# dd if=/dev/zero of=anchor.file bs=1 count=5000000000000 status=progress
16908336 bytes (17 MB, 16 MiB) copied, 61 s, 277 kB/sError: read vsock vm(4294967295):1873106686->vm(31):8443: connection reset by peer
jsimpso@alcazar:~$

And the VM can be started up again:
jsimpso@alcazar:~$ lxc ls
+-------+---------+-------------------------+------+-----------------+-----------+
| NAME  |  STATE  |          IPV4           | IPV6 |      TYPE       | SNAPSHOTS |
+-------+---------+-------------------------+------+-----------------+-----------+
| alpha | STOPPED |                         |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
| beta  | RUNNING |                         |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
| delta | STOPPED |                         |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
| gamma | RUNNING | <IP_ADDRESS> (enp5s0) |      | VIRTUAL-MACHINE | 0         |
+-------+---------+-------------------------+------+-----------------+-----------+
jsimpso@alcazar:~$

So the fact that LXD attempts the migration is normal. We never try to guess the disk space and instead just go ahead and if we're going to hit ENOSPC, then that's going to be our cue that there isn't enough space.
The reason for that is that different storage backends store things very very differently. You can easily do cat /dev/null > out.img or the like on a VM stored on a dir storage backend, make it go to 100GiB, then move it to a project that uses a zfs storage pool and ZFS will happily store that in something like 500MiB thanks to the default inline compression.
Now, these days a project move shouldn't actually cause any data to be copied, so we'd need to check on current LXD to see what's going on there. It's also obviously problematic if QEMU just crashes or stops responding in such a situation when it itself isn't supposed to be writing anything to disk.

Yeah seems like the target project flag is confusing the same pool move detection somehow.

Right, so I've taken a look at whats going on here, and the behaviour is that when using instances on the dir pool the storage subsystem invokes CreateInstanceFromCopy, this then detects that the source and target are in the same pool and switches to "same-pool mode" which then invokes CreateVolumeFromCopy on the storage driver.
In the case of a storage driver that supports optimized copies (snapshots) this is very quick and doesn't take much disk space as the copy is just a snapshot of the source instance (and then in the case of ZFS, the source instance volumes are kept around but hidden as they are still referenced by the new instance's name).
In the case of the dir storage driver however, CreateVolumeFromCopy invokes genericVFSCopyVolume which uses the dd command to copy the VM's root disk device.
Basically the problem here is that there isn't a "move" concept in the storage subsystem (https://github.com/lxc/lxd/blob/632b3839b3388cc89df0ffe96d7c7c9134f00a7b/lxd/storage/pool_interface.go#L39-L145) and so the lxc move is just a lxc copy followed by a lxc delete (effectively).
We can see this where its implemented in the server side:
https://github.com/lxc/lxd/blob/632b3839b3388cc89df0ffe96d7c7c9134f00a7b/lxd/instance_post.go#L486-L553
So I'm going to put this down as a feature & maybe, as its not a bug per-se.


Subdivision does not copy links correctly.

When Subdiviing a file with one heading into a Folder with the heading and the file in it, links such as [[Latin Vulgate]] is copied into the new note as \[\[Latin Vulgate]]
Seems like this is an error when the new copy is created.
On a side note, I noticed that the new file has different creation dates as well. Might be better to do a move instead atleast when the delete option is enabled as I don't want to lose all the history I have with the first file. My use case is coverting a file into a folder with the original file as its folder note. Both my folder and the folder notes have the same names.

Hi, @moonbrew
I think I've fixed the link error in 9b45480, please try the latest version.
For the second note, for now the new folder is just created from the original file. So in your use case, maybe you can disable the original file deletion and index file creation, then manually move the original file into the folder newly created.


Chrome Stalling when requesting a lot of images at the same time

I've used your plugin from a long time now without any problem.
Not sure if this is the correct place to post this, please forgive me.
I have encountered this strange issue recently with a site that you can see here: https://dot-agency.it/spctrm/.
https://www.dropbox.com/s/satj2yaphw2j8oe/spectrum_problem.png?dl=0
In the screenshot at the link you can see that even with the cache enabled sometimes chrome takes even 2s to give me the file. The behaviour it's very randomatic, very hard to replicate if you have a fast computer almost impossible.
Do you think it's related to lazysizes? anyone encountered something like that before?
Thanks a lot!

This site does not use lazysizes but it uses some jquery lazyloading plugin.


Page numbers are coming back as -1 in synced notes.

I'm seeing -1 for page numbers in the notes I've created so far, in both the front matter and the in the note itself. I tried making notes for two different epubs. They both have -1 for page numbers. In KOReader itself, the books do show page numbers.

Sadly KOReader doesn't save the page by itself but it's only inserted in the string proposed as note.
eg.
["text"] = "Pagina **14** Nobody needs willpower not to eat a chocolate bar when there isn’t one around @ 2022-01-21 22:40:15\
\
this is the text I add as a note",

The first row is what KOReader put as a default note, the word "Page" translated in the language you are using KOReader, the number of the page, the highlighted text, the '@' symbol and the datetime.
If you remove this default I can't get the right page number so you should append your note to that (don't worry, my plugin already take the text after the default one)
I can look at it just to be sure... mybe I can find some convoluted way to get the page.


Create page for token request

For the endpoint like OpenShift's /oauth/token/request, the User can be redirected to SSO with the IdP.
Once they login via the IdP, they are redirected back to a page that simply says "Display Token":

Then, upon clicking, they are provided with the token and some utility commands using the token:

Closed via https://github.com/smart-spectral-matching/ssm-service-catalog/pull/4


Support for Spring cloud SchemaRegistryClient

Feature request
Spring uses org.springframework.cloud.stream.schema.registry.client.SchemaRegistryClient for its Avro conversion
We can use GlueClient to make calls to get schema.
Also AWSSchemaRegistryClient wraps requests related to the schema management, which is easy to use without needing to worry about underlying errors and logic.
On the other hand spring's interface need few more things which is challenging to get either via GlueClient or AWSSchemaRegistryClient. With combination of both and making extra calls to ensure, we get what we need.
What we have achieved so far:
@Component
public class GlueSchemaRegistryClient implements SchemaRegistryClient {
    private static final Logger LOG = LoggerFactory.getLogger(GlueSchemaRegistryClient.class);

    private final GlueClient glueClient;
    private final AWSSchemaRegistryClient awsSchemaRegistryClient;
    private final String registryName;

    public GlueSchemaRegistryClient(GlueClient glueClient, AWSSchemaRegistryClient awsSchemaRegistryClient, GlueSchemaRegistryConfiguration glueSchemaRegistryConfiguration) {
        this.glueClient = glueClient;
        this.awsSchemaRegistryClient = awsSchemaRegistryClient;
        this.registryName = glueSchemaRegistryConfiguration.getRegistryName();
    }

    @Override
    public SchemaRegistrationResponse register(String subject, String format, String schema) {
        UUID schemaId = awsSchemaRegistryClient.createSchema(subject, format.toUpperCase(), schema, Collections.emptyMap());
        GetSchemaVersionResponse schemaVersionResponse = awsSchemaRegistryClient.getSchemaVersionResponse(schemaId.toString());

        SchemaRegistrationResponse response = new SchemaRegistrationResponse();
        response.setId(7); // TODO: Setting some random id, need to check if needed or not
        response.setSchemaReference(new SchemaReference(subject, schemaVersionResponse.versionNumber().intValue(), format));
        return response;
    }

    @Override
    public String fetch(SchemaReference schemaReference) {
        GetSchemaVersionResponse getSchemaVersionResponse = glueClient.getSchemaVersion(GetSchemaVersionRequest.builder()
                .schemaId(SchemaId.builder()
                        .registryName(registryName)
                        .schemaName(schemaReference.getSubject())
                        .build())
                .schemaVersionNumber(SchemaVersionNumber.builder()
                        .versionNumber((long) schemaReference.getVersion())
                        .build())
                .build());

        return getSchemaVersionResponse.schemaDefinition();
    }

    @Override
    public String fetch(int id) {
        LOG.error("Shouldn't get called for non-cached client");
        throw new UnsupportedOperationException("Not supported by glue, also not needed as non-cached class");
    }

}

But this can be done efficiently if AWSSchemaRegistryClient exposes 2 APIs
1. GetSchemaVersionResponse createSchema(String schemaName, DataFormat format, String schemaDefinition);
2. GetSchemaVersionResponse getSchemaVersion(String schemaName, Long versionNumber);

cc: @harshadnawathe @DivyaUppu

any feedback, views, idea on this?


Added wallet key pools, lookahead and improved the code structe

Looking OK. Though please check the comments. I'll do another review round later.

I think besides the look-ahead issue this is looking better and better.

I think is good to go, unless you're waiting for someone else's review.

Looks good. I left some extra comments but all quite nitpicky and safe to ignore.

Thanks. I will fix these in the next PR.


Performance Increase for startup and object creation

Improvement of the startup and creating a quicker startup and type creation to ensure it can provide a quick base for bots.
Describe the solution you'd like
Unnecessary performance killers should be removed, and startup should be made more efficient. Possible startup methods should be improved or entirely removed and replaced.
Describe alternatives you've considered
An alternative method for startup and replacement of the metadata_check which triggers the on_ready function.
Additional context
Performance decreased heavily since the start and startup can take up to 4-6 seconds compared to the 1-2 seconds before.

why assign me when i barely do shit for the team

why assign me when i barely do shit for the team

Sssh it alright pats

I do less than you so shut @Nxybi

I do less than you so shut @Nxybi

at least you have done something smh

at least you have done something smh
wdym? you've done so much, all I've done is add... maybe 25? lines of code to Frostbyte

Removing help wanted tag - github keeps screaming at me

Rewrote WS and event handling for better performance in #25. The issue can be seen as solved and closed


Issue with new feature of tags

Hello ^^.
I have upgraded the theme to experiment with this new feature (I have set the count to 20) and now I have a "big" problem. Let me show some screenshots:

First tags:

Middle tags:

Final tag:

And now, they are shown in a weird orden (I think it is reverse alphabetical order in each 'level').


feat: cloud ids

closes #512
Landing zone v2 subpackage.
Depends on client-landing-zone package.
Package to create Cloud Intrusion Detection System (IDS) resources inside the network host project. This is required for PBMM.
Warning! It requires the alpha CRD cloudidsendpoint  loaded in the config controller.

perhaps indicate in the readme that this package also depends on an updated client-setup package; maybe mention the minimum version that should be used.

@stephanemillaire-ssc I will create another small PR to implement your request


e.show is not a function

Refs: https://github.com/microsoft/vscode/issues/91335

Take the watch view and drop it into the panel
Drag the watch view and drop it into the Extensions viewlet icon in activity bar
Extensions viewlet gets broken -> there is an error in the developer tools console 🐛

Reload does not fix the issue -> it would be great if we fix this issue this milestone.
Call stack
RR e.show is not a function: TypeError: e.show is not a function
    at file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6372:803
    at Array.map (<anonymous>)
    at ae.onDidAddViewDescriptors (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6372:794)
    at ae.create (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5635:380)
    at ae.create (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6368:434)
    at t.create (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3399:1008)
    at e.showComposite (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5147:974)
    at e.doOpenComposite (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5146:870)
    at e.openComposite (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5146:402)
    at e.doOpenViewlet (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5716:343)
    at e.openViewlet (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5715:675)
    at t.CompositeDragAndDrop.openComposite (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5680:434)
    at t.CompositeDragAndDrop.drop (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5665:155)
    at Object.onDrop (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5652:843)
    at HTMLLIElement.<anonymous> (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5538:528)

fyi @sandy081, fixed by adding flag to container descriptor that rejects adding views. necessary for extensions viewlet.


feat: added time_stamp flag

currently default filename is "$UNIX_TIMESTAMP-wayshot.$EXTENSION" . This pr adds flag --time_stamp to use human read-able timestamp instead of seconds from UNIX_EPOCH .

@Decodetalkers I'm wondering if we should make this the default, UNIX_TIME time isn't a great naming convention. What do you think?
CC: @AndreasBackx Hi apologies for pinging but would like some of your input if possible -- would changing our naming scheme from wayshot-UNIX_TIME.encoding to wayshot-HUMANIZED_TIME.encoding be considered a breaking change?

@Shinyzenith if you mean an ISO8601 timestamp, then yes. If you mean like "1 day ago", then I'd definitely say no.
Also would make the former the default. I'd also make it wayshot-TIME.EXT so they're grouped if sorted by name. It's technically a breaking change, though we're in 0.x so I think this is fine.
I'm away from a PC, though I'd let people override the name how they want and avoid any further name customisations. Though I think we already have this, cannot check rn.

yes user can provide output file name . if no name is provided it saves file in $UNIX_TIMESTAMP-wayshot.$EXTENSION format which is a bit confusing hence this flag.

@Shinyzenith if you mean an ISO8601 timestamp, then yes. If you mean like "1 day ago", then I'd definitely say no.

Yes I am indeed referring to ISO8601 although this PR isn't formatted with respect to it. I will request that change if everyone agrees on this feature req.

Also would make the former the default. I'd also make it wayshot-TIME.EXT so they're grouped if sorted by name. It's technically a breaking change, though we're in 0.x so I think this is fine.

Please correct me if I am mistaken but at the moment we already do wayshot-TIME.EXT.
PS: I don't think changing the naming conventions after we hit 1.x would be acceptable so this will only be entertained for the 0.x period but I will still try to keep it to a low frequency.
We won't hit 1.x until the screencopy protocol either gets accepted in ext namespace of wayland-protocols or zwlr is stabilized to wlr. I think we are fine for now

@Decodetalkers Can I get an ack for you to make wayshot-ISO8601_ENCODED_TIME.EXT the new default?

@Shinyzenith made the requested changes please review.

np problem does this look fine ?

 np problem does this look fine ?

CC: @AndreasBackx

Apologies for the late reply! (In the future, feel free to ping me on Discord as well.)
And again further apologies, I noticed that my format DD-MM-YY HH:MM:SS was not what I intended. I also posted 2024-12-31 23:59:59 which would be YYYY-MM-DD HH:MM:SS. The problem with using wayshot-DD-MM-YYYY HH:MM:SS.ext is that when sorted alphabetically, it's not sorted by time (which is very much desired imo). Doing YYYY-MM-SS does have this benefit which is why I was advocating for it.
Also, now that I see it, should we use wayshot-2024_03_08-01_01_43.png instead? This would have the additional benefit that when using this from the terminal, you don't have to quote it.
So do you peeps agree wayshot-YYYY_MM_DD-HH_MM_SS.ext would be ideal?

wayshot-YYYY_MM_DD-HH_MM_SS.ext

I think I would go ahead with this due solely due to the _. Quoting files in terminals can be a huge mess.

@Shinyzenith
@AndreasBackx
done

I think default would be best. @rachancheet do you agree? If yes we can do so and land the merge.

agreed. What should i rename the flag ??

@rachancheet it should be removed your new function should be the body of the old default function.

Done. @AndreasBackx Thanks for the guidance

Hi, I resolved the merge conflicts.


Conman template: wrong execpath

Value:
SERVER execpath="/usr/share/conman/exec"
Is not adapted to new path of conman.

Solved by @bouriquet

PR #115


Question for ASP.NET 6.0 builder.service.AddDbContext support

Hello, I want to ask, does this support the builder service on ASP.NET 6.0?
if not will it be possible to support it on the options? Because it throw error
'SqlServerDbContextOptionsBuilder' does not contain a definition for 'UseRowNumberForPaging' and no accessible extension method 'UseRowNumberForPaging' accepting a first argument of type 'SqlServerDbContextOptionsBuilder' could be found (are you missing a using directive or an assembly reference?)

try {
    string host = "localhost";
    string user = "sa";
    string pass = "12345";
    string port = "1433";
    string db   = "AdventureWorks2008R2";
    builder.Services.AddDbContext<AppDBContext>(
        opt => opt.UseSqlServer(@"Server="+host+","+port+";Database="+db+";User Id="+user+";Password="+pass,
     i => i.UseRowNumberForPaging()) // This result on error
    );
} catch(Exception e) {
    Console.WriteLine(e.ToString());
}

Test Code/Project that can be used to test is https://github.com/benyaminl/dotnet-core-playground
Any suggestion/help appreciated. Thank you

Ouch dumb. Sorry. I need to import EntityFrameworkCore.UseRowNumberForPaging;
Closed. Sorry.


Key Generation not working

When i try to generate key it does not work. Image in description. Python requirements installed. I use Python 3.12.2.

I tried to use VPN in 3 different locations but it is not working.
I can confirm that creating Account works but not key generation.

Use github actions


Raw, unaltered input in post

I'm using KaTeX for rendering math equations.
I found, that on multi-line input Ghost is "altering" the input, so KaTeX is unable to render the equation.
Say, I have the following equation, KaTeX will only render if it's unaltered:
$$
\begin{aligned}
   a&=b+c \\
   d+e&=f
\end{aligned}
$$

But, on page it look like:

$$

\begin{aligned}

a&=b+c \

d+e&=f

\end{aligned}

$$

The
 tag is not a problem, but altering ampersand and slashes with
 tag are.
Is it possible to have "raw" tag, which won't change the input ( is not an option here)? Or is it available right now?

@m0nhawk anything wrapped in HTML tags will be output as-is, so you could use a
 or , eg:
# KaTeX example

$$
\begin{aligned}
   a&=b+c \\
   d+e&=f
\end{aligned}
$$

More markdown...

Inserting the KaTeX code without wrapping in HTML isn't supported as there is no support in CommonMark for "raw" output like that.
There will likely be more options in the future once our full mobiledoc editor lands where you could add a raw/html card, or there may be a way to add custom markdown-it extensions such as markdown-it-katex.
Closing this issue as it's not a bug. In the future please direct any support requests to our Slack channel, our GitHub repo is not the right place for these type of issues - our support guide was linked in the GitHub notification above the issue creation form as well as the default issue text and it has details about what issues you should raise here and which issues should be handled elsewhere. (Many projects have their own support guidelines and GitHub highlights them for you, please read them before opening issues 😄)


Weird compile error on MNIST example only when copying out of repo?

Describe the bug
I copy pasted everything out of the MNIST src into my own project because I wanted to try making a test NN.
It does not like one of the types in data.rs yet it compiles fine in the project itself?
  --> TicTacToeMaster\src\data.rs:29:42
   |
29 |             .map(|tensor| tensor.reshape([1,784]))
   |                                  ------- ^^^^^^^ expected struct `Shape`, found array `[{integer}; 2]`
   |                                  |
   |                                  arguments to this function are incorrect
   |
   = note: expected struct `Shape<_>`
               found array `[{integer}; 2]`
note: associated function defined here
  --> C:\Users\itscrabs\.cargo\registry\src\github.com-1ecc6299db9ec823\burn-tensor-0.2.3\src\tensor\base.rs:31:12
   |
31 |     pub fn reshape<const D2: usize>(&self, shape: Shape<D2>) -> Tensor<B, D2> {
   |            ^^^^^^^
help: try wrapping the expression in `burn::tensor::Shape`
   |
29 |             .map(|tensor| tensor.reshape(burn::tensor::Shape { dims: [1,784] }))
   |                                          +++++++++++++++++++++++++++         +

For more information about this error, try `rustc --explain E0308`.
error: could not compile `TicTacToeMaster` due to previous error

To Reproduce
Steps to reproduce the behavior:

Create new cargo project
Copy everything in examples/mnist to the project
add serde and burn to Cargo,toml
cargo run
See error

Expected behavior
Example to run
Additional context
I'm not so great with GitHub but just forcing it into the correct Burn shape using new() seems to fix it:
at examples/mnist/data.rs: line 29 should become:
.map(|tensor| tensor.reshape(burn::tensor::Shape::new([1,784])))

Ho my bad, this is just the new API on the main branch, but the version on crates.io is a bit outdated. Using the struct Shape will work on all versions. I just added a generic parameter to accept everything that implements Into<Shape>  (Including array) to reduce boilerplate code.


Xrdp crashes when connecting

xrdp version
<IP_ADDRESS>
Detailed xrdp version, build options
PASTE HERE

Operating system & version
ALT Server 10.2
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
Xotg
What desktop environment do you use?
Mate
Environment xrdp running on
Ge force 210
What's your client?

Area(s) with issue?
Authentication, Graphic glitches
Steps to reproduce
I installed xrdp, then installed mate-session, connected the thin client to the server, entered the username and password, connected, a picture appeared and the system crashed
✔ Expected Behavior
I expected to see the system working
❌ Actual Behavior
The connection was lost and the error trans_write_copy_s failed was received, and the error Sending [ITU T.125] DisconnectedProviderUltimatum fail was received
Anything else?
No response

@POdUShkA1812 - can you provide the xrdp.log and xrdp-sesman.log files from your connection attempt please?

xrdp.log
xrdp-sesman.log

I can't see any problems at all in there.

Is the xrdp-sesman.log complete?
What does "the system crashed" mean?
Can you reconnect? What happens when you try?

I didn’t really understand the question about how to open the xrdp-sesman file.
I'm trying to connect to the server, the connection occurs and after 10 seconds it breaks.
When I try to connect again, I get the same error, and sometimes the message appears: can not connect on session bus

The file is in /var/log/xrdp-sesman.log
Can you log in on the server console normally?

No further input - closing.


Avoid extension host communication if possible

Run with --logExtensionHostCommunication or with code change for LOG_EXTENSION_HOST_COMMUNICATION

Create an empty folder
Create a text file
Enable auto save
Type one character

Observe, as part of saving the extension host is invited to participate in saving, but this is a text file and there are no extensions that I have installed for formatting text files, nor do I have enabled the format on save setting.

The $participateInSave is used to trigger the onWillSave-event - it is unrelated to formatting. I can now go in and wait for the first and last subscribers to this event and send IPC messages to enalbe/disable the main-side-listener but I doubt that will make a difference (apart from complexity). So @alexandrudima what is the cost of an empty IPC message? Do we really wanna go all in here, do the same with onDidSave, onDidChangeTextDocument etc?

The $participateInSave is used to trigger the onWillSave-event

Aha! Then we should leave it in. From its name I thought this message was about save participants (i.e. it was not called $acceptOnWillSave)


Integrating KeyVault with AKS fails to work following this tutorial due to a security issue with KubeNet

See here for information on the issue.
From that page:

Introduction
AAD Pod Identity is disabled by default on clusters with Kubenet network plugin. The NMI pods will fail to run with error AAD Pod Identity is not supported for Kubenet.
Why this change?
Kubenet network plugin is susceptible to ARP spoofing. This makes it possible for pods to impersonate as a pod with access to an identity. Using CAP_NET_RAW capability the attacker pod could then request token as a pod it’s impersonating.

Following this tutorial, the AAD Pod Identity fails to work (the NMI Pod go into a crash loop on startup) and thus things never actually work.
Ideally someone needs to update the steps in this document to include a safe and secure work around for this issue.
This is a very complicated subject and a lot of people who just want to run a few containers with K8S as a managed service might not have the knowledge to work around this safely themselves.
EDIT: This might be 'avoided' by using the suggested version of 1.16.X mentioned in the tutorial... but that simply avoids the issue by leaving the users open to the security vulnerability as mentioned above 1.19.X is much more up to date (and thus has AAD Pod Identity Disabled for security reasons) and ideally the tutorial should be updated to support this.

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

ID: eee999c1-32dd-d014-40df-8027adee1258
Version Independent ID: 19a29c09-79f8-580a-841f-873e2801da56
Content: Integrate Azure Key Vault with Kubernetes
Content Source: articles/key-vault/general/key-vault-integrate-kubernetes.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@markmcgookin
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.


"memory allocation" error

Diffing a 13kb C++ source file results in a memory allocation of<PHONE_NUMBER>854775800 bytes failed error.  My laptop doesn't have 9,223 petabytes of memory, so this keeps it from working.
Release 0.53 onward fails like this.  Version 0.52 works.
The latest release tested is Difftastic 0.55.0 (7fda26d 2024-01-30, built with rustc 1.65.0).
Unfortunately, the source is proprietary.  I'll see if it can be reproduced with something that can be shared.

How many lines are in the files, and roughly how many lines are in common (e.g. how big is a patch created by GNU diff)?
You're probably hitting the scaling limitations of the textual diffing logic, which uses O(N^2) memory with dynamic programming (the Myers Diff algorithm). I know that GNU diff / BSD diff have tricks to handle larger files well, at the cost of a less optimal diff (more lines shown as changed). I think difftastic needs to have similar heuristics for large text diffs.

I can reproduce with "Difftastic 0.55.0 (built with rustc 1.75.0)" (latest homebrew version) with these files:

a.txt (14 lines)
b.txt (315 lines)

GNU diff's output is 306 lines.

@simonmichael are you sure that's the same issue? I can't reproduce with your files.
$ /bin/time -v difft a.txt b.txt >/dev/null
	Command being timed: "difft a.txt b.txt"
	User time (seconds): 0.02
	System time (seconds): 0.01
	Percent of CPU this job got: 93%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.04
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 26312
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 0
	Minor (reclaiming a frame) page faults: 338
	Voluntary context switches: 0
	Involuntary context switches: 4
	Swaps: 0
	File system inputs: 0
	File system outputs: 0
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0

That memory amount seems sensible.

Indeed. Unfortunately, today I'm not able to reproduce it either! I do expect to see it again eventually, I'll update here in that case.

Apologies for the delay in getting some files for this.
Here's a repro (with different files than the initial message in this report) using 'Difftastic 0.56.1 (d9d6401 2024-03-05, built with rustc 1.65.0)':
wget https://raw.githubusercontent.com/llvm/llvm-project/5d6304f01742a0a7c628fe6850e921c745eaea08/compiler-rt/lib/asan/asan_allocator.cpp -O a
wget https://raw.githubusercontent.com/llvm/llvm-project/9e68b7e0e04f89cd3810102016ddf34fd3a33b3d/compiler-rt/lib/asan/asan_allocator.cpp -O b
./difft a b
b --- 1/10 --- Text
16 16
17 17 #include "asan_allocator.h"
18 18
19 .. #include "asan_internal.h"
20 19 #include "asan_mapping.h"
21 20 #include "asan_poisoning.h"
22 21 #include "asan_report.h"

b --- 2/10 --- Text
25 24 #include "lsan/lsan_common.h"
26 25 #include "sanitizer_common/sanitizer_allocator_checks.h"
27 26 #include "sanitizer_common/sanitizer_allocator_interface.h"
28 .. #include "sanitizer_common/sanitizer_common.h"
29 27 #include "sanitizer_common/sanitizer_errno.h"
30 28 #include "sanitizer_common/sanitizer_flags.h"
31 29 #include "sanitizer_common/sanitizer_internal_defs.h"

b --- 3/10 --- Text
memory allocation of<PHONE_NUMBER>854775803 bytes failed
aborted (core dumped)


ConnectIDFactoryImpl can't be used with passive diagnostic port

ConnectionIDFactoryImpl can't be used with passive ConnectionIDFactoryImpl because it announces changes to the rest of the system

#876


[Compose] Support Jetpack Navigation on Android

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

Comparison is base (9c64892) 74.00% compared to head (6a8e2fd) 74.00%.

Files
Patch %
Lines

.../kotlin/kt/mobius/compose/ComposeMobiusLoop.jvm.kt
60.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #188   +/-   ##
=======================================
  Coverage   74.00%   74.00%
=======================================
  Files           7        8    +1
  Lines         100      100
  Branches       22       22
=======================================
  Hits           74       74
  Misses         14       14
  Partials       12       12

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


"change" event not consistent

Hello,
When using palettes, the change event behavior is, in my opinion, not consistent.
Let me explain:

When moving the color, the change event is not triggered.
When you use the palette to directly select a color, the change event is triggered.

Why is it triggered in one case and not the other ?

Moreover why is this event triggered when the  value is still being edited (I'm not that familiar with the expected "change" event behavior, if this is the expected behavior, then it makes sense).

When you cancel the edition, the color is set back to the previous value, but no "change" event is triggered.
If you previously used the "change" event to manipulate an element's color, you can't set it back to the original value without using spectrum's own event (not practical when you want to stay color picker agnostic).
I believe you should stick to either:

"change" event is only triggered when the color is actually selected (you can still listen to the move event to update an element "live").
"change" event is triggered each time the temporary color is changed (including moving on the color pad and when discarding the selection).

ps: if you want to reproduce the behavior, you can use the doc's websites:
https://bgrins.github.io/spectrum/
The first color picker at the top has the expected behavior (and relies on spectrum, move and hide events, not on the "change" event).
https://bgrins.github.io/spectrum/#options-showPalette
The palette demonstration color picker uses the "change" event and illustrates the event's incoherency:
Try to click on a palette element and then cancel: the doc's border has been updated even if the edition was canceled.
Thanks for your attention, don't hesitate if you need more info.
Cheers,
Benjamin

@bgrins , is there any solution for this?


Got the message Could not set dlopen hook Unsupported JVM

Team,
While trying to attach async-profiler to the java process we encountered the below listed error
[ERROR] Could not set dlopen hook. Unsupported JVM?
Command used: ./profiler.sh -e cpu -d 300  -o collapsed -f /opt/async-profiler-2.8-linux-x64/jdk_312_cpu_collapsed.txt
We were able to attach to the process successfully a day before, but suddenly got this message.
async-profiler runs on the host whereas the java process runs inside the container
Thanks
Sattish.

What OS image does the container run? Is it Alpine Linux?
Did you successfully attach to the same process before, or you restarted the process since then?
Can it be the case that you loaded different versions of async-profiler in the same process?
(you can check it by calling cat /proc/<pid>/maps | grep asyncProfiler)

HI Andrei,
Thanks for your response. We use ubuntu Trusty. I was successful in
attaching to the process initially. We noticed this error only after we
installed gprofiler a continuous profiling tool.
When i went through their documentation we found that they were using
async-profiler internally to gather cpu profiles for java stack. After
stopping the gprofiler we didn't notice the error.
Please close the ticket. Sorry for the discommode.
On Thu, Jun 16, 2022 at 6:56 PM Andrei Pangin @.***>
wrote:

What OS image does the container run? Is it Alpine Linux?
Did you successfully attach to the same process before, or you
restarted the process since then?
Can it be the case that you loaded different versions of async-profiler in
the same process?
(you can check it by calling cat /proc//maps | grep asyncProfiler)
—
Reply to this email directly, view it on GitHub
https://github.com/jvm-profiling-tools/async-profiler/issues/610#issuecomment-1157660487,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABY2VGJXQ65X2M3HPFL7YL3VPMTQHANCNFSM5YZ3B4SA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
with regards,
Sattish
9940080070

gProfiler's latest version is v2.8.1 so if @sattishv had used older versions of async-profiler before, then yes, multiple versions were loaded in the process (however, we never found it to be a problem)

I'm getting this error on Arch Linux (https://aur.archlinux.org/packages/async-profiler).
14:17 darkstar api-tester ❯ cat /proc/44038/maps | grep asyncProfiler

14:17 darkstar api-tester 1 ❯ async-profiler -d 30 -f output.html 44038
[ERROR] Could not set dlopen hook. Unsupported JVM?

14:17 darkstar api-tester 200 ❯ cat /proc/44038/maps | grep asyncProfiler
7f2e14061000-7f2e14066000 r--p 00000000 fe:00 6298755                    /opt/async-profiler/build/libasyncProfiler.so
7f2e14066000-7f2e1409c000 r-xp 00005000 fe:00 6298755                    /opt/async-profiler/build/libasyncProfiler.so
7f2e1409c000-7f2e140a8000 r--p 0003b000 fe:00 6298755                    /opt/async-profiler/build/libasyncProfiler.so
7f2e140a8000-7f2e140a9000 r--p 00046000 fe:00 6298755                    /opt/async-profiler/build/libasyncProfiler.so
7f2e140a9000-7f2e140aa000 rw-p 00047000 fe:00 6298755                    /opt/async-profiler/build/libasyncProfiler.so

@joca-bt The problem is understood. I'm working on a fix.

The fix has been pushed

Dear @apangin ,
We found this issue in aws linux, and use version 2.9, could u please kindly help to look into it? Thanks!
bash-4.2# /opt/debug/async-profiler/profiler.sh -e itimer -d 30 -f /tmp/hello.html 1
[ERROR] Could not set dlopen hook. Unsupported JVM?
bash-4.2# /usr/java/jdk-11/bin/java --version
openjdk 11.0.10 2021-01-19 LTS
OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build 11.0.10+9-LTS)
OpenJDK 64-Bit Server VM Corretto-<IP_ADDRESS>.1 (build 11.0.10+9-LTS, mixed mode)
bash-4.2# uname -a
Linux decision-rule-saas-takin-7676b8d8c7-jwhxf 5.4.204-113.362.amzn2.x86_64 #1 SMP Wed Jul 13 21:34:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
bash-4.2# cat /proc/1/maps | grep asyncProfiler
7fc6fb976000-7fc6fb9be000 r-xp 00000000 103:01 165074609                 /opt/debug/async-profiler/build/libasyncProfiler.so
7fc6fb9be000-7fc6fbbbe000 ---p 00048000 103:01 165074609                 /opt/debug/async-profiler/build/libasyncProfiler.so
7fc6fbbbe000-7fc6fbbc0000 rw-p 00048000 103:01 165074609                 /opt/debug/async-profiler/build/libasyncProfiler.so

Thanks,
Roy

This is a known issue that has been fixed in #761.

@RoySunnySean007 Yes you can build an up-to-date version from sources or take early access binaries from here:
async-profiler-3.0-ea-linux-x64.tar.gz

Thanks @apangin !