What's new in .NET 7 Preview 5 [WIP]

What's new in .NET 7 Preview 5
This issue is for teams to highlight work for the community that will release .NET 7 Preview 5
To add content, use a new conversation entry. The entry should include the team name and feature title as the first line as shown in the template below.
## Team Name: Feature title

[link to the tracking issue or epic item for the work]

Tell the story of the feature and anything the community should pay particular attention
to be successful using the feature.

Preview 1: https://github.com/dotnet/core/issues/7106
Preview 2: https://github.com/dotnet/core/issues/7107
Preview 3: https://github.com/dotnet/core/issues/7108
Preview 4: https://github.com/dotnet/core/issues/7378
Preview 5: https://github.com/dotnet/core/issues/7441
Preview 6: https://github.com/dotnet/core/issues/7454
Preview 7: https://github.com/dotnet/core/issues/7455

Higher performance reflection invoke by @steveharter

Observability
Expose performant ActivityEvent and ActivityLink tags enumerator methods https://github.com/dotnet/runtime/issues/68056
The exposed methods can be used in the perf critical scenarios to enumerate the Tags objects without any extra allocations and with fast items access.
namespace System.Diagnostics
{
    partial struct ActivityLink
    {
        public Activity.Enumerator<KeyValuePair<string, object?>> EnumerateTagObjects();
    }

    partial struct ActivityEvent
    {
        public Activity.Enumerator<KeyValuePair<string, object?>> EnumerateTagObjects();
    }
}

in preview 5 we can create blazor and maui projects with .net 7 target!?
and when is maui released!?

System.IO.Stream
Add Stream ReadExactly and ReadAtLeast https://github.com/dotnet/runtime/issues/16598
One of the most common mistakes when using Stream.Read() is that the programmer doesn't realize that Read() may return less data than what is available in the Stream and less data than the buffer being passed in. And even for programmers who are aware of this, having to write the same loop every single time they want to read from a Stream is annoying.
To help this situation, we have added new methods to the base System.IO.Stream class:
namespace System.IO;

public partial class Stream
{
    public void ReadExactly(Span<byte> buffer);
    public void ReadExactly(byte[] buffer, int offset, int count);

    public ValueTask ReadExactlyAsync(Memory<byte> buffer, CancellationToken cancellationToken = default);
    public ValueTask ReadExactlyAsync(byte[] buffer, int offset, int count, CancellationToken cancellationToken = default);

    public int ReadAtLeast(Span<byte> buffer, int minimumBytes, bool throwOnEndOfStream = true);
    public ValueTask<int> ReadAtLeastAsync(Memory<byte> buffer, int minimumBytes, bool throwOnEndOfStream = true, CancellationToken cancellationToken = default);
}

The new ReadExactly methods are guaranteed to read exactly the number of bytes requested. If the Stream ends before the requested bytes have been read an EndOfStreamException is thrown.
Example
using FileStream f = File.Open("readme.md");
byte[] buffer = new byte[100];

f.ReadExactly(buffer); // guaranteed to read 100 bytes from the file

The new ReadAtLeast methods will read at least the number of bytes requested. It can read more if more data is readily available, up to the size of the buffer. If the Stream ends before the requested bytes have been read an EndOfStreamException is thrown. You can opt out of throwing an exception, however that means ReadAtLeast will read less than the requested bytes if the Stream ends.
Example
using FileStream f = File.Open("readme.md");
byte[] buffer = new byte[100];

int bytesRead = f.ReadAtLeast(buffer, 10);
// 10 <= bytesRead <= 100

New analyzer and fixer for Regex source generator - @joperezr
https://github.com/dotnet/runtime/pull/69872/

CodeGen
Community PRs
@singleaccretion made 23 PR contributions  during Preview 5 with some highlighted items below:

Improve the redundant branch optimization to handle more side effects PR#68447
PUTARG_STK/x86: mark push [mem] candidates reg optional PR#68641
Copy propagate on LCL_FLDs PR#68592

@Sandreenko completed allowing StoreLclVar src to be IND/FLD PR#59315.
@hez2010 fixed CircleInConvex test in PR#68475.
See contributions from @anthonycanino, @aromaa and @ta264 in the below sections.
Arm64

Arm64: Have CpBlkUnroll and InitBlkUnroll use SIMD registers  uses SIMD registers for initialization of copy a block of memory less than 128 bytes. Some performance wins are shown here.

PR#68363 consolidated 'msub' and 'madd' logic.

Loop Optimization

PR#67930 Handle more scenarios for loop cloning  now supports to operate on loops that go backwards or forwards with the increment of > 1. The performance wins can be seen here.

PR#68588 Hoist the nullchecks for 'this' object moves the nullchecks on an object outside the loop. Performance wins can be seen here.

x86/x64 Optimizations
There were a number of optimizations targetted for x86/x64 platforms:

PR#67182 Emit shlx, sarx, shrx on x64  optimized mov+shl, sar or shr to shlx, sarx or shrx on x64.
PR#68091 enabled UMOD optimization for x64.
@anthonycanino added X86Serialize hardware intrinsic in PR#68677.
@aromaa optimizec bswap+mov to movbe in PR#66965.
@ta264 fixed linux-x86 compilation for clr.alljits subset in PR#68046.

Modernize JIT
As more and more community contributors participate in the JIT code base, it is increasingly getting important to restructure our code and modernize it in order to allow our contributors to easily ramp up and rapidly develop code.
This release we did a lot of work on the internals of the JIT, cleaning up the JIT’s intermediate representation and removing limitations as a result of old design decisions. In many cases this work resulted in less memory usage and higher throughput of the JIT itself, while in other cases it resulted in better code quality. Some of these changes were:

Delete CLS_VAR PR#68524
Delete GT_ARGPLACE PR#68140
Delete GT_PUTARG_TYPE PR#68748

The above allowed us to remove an old limitation in the JIT’s inliner when inlining functions with parameters of byte/sbyte/short/ushort type, resulting in better code quality:

Allow the inliner to substitute for small arguments PR#69068

As .NET has become a more and more popular platform for writing high-performance code the coding style has changed. One area where the JIT was lacking was in its understanding of unsafe code involving reads and writes of structs and struct fields. @SingleAccretion contributed great changes in this area by switching the JIT’s internal model to a more general “physical” model. This paves the way for the JIT to better reason about unsafe code using features like struct reinterpretation.

Physical value numbering PR#68712
Implement constant-folding for VNF_BitCast PR#68979

Other minor cleanups were also made to simplify the JIT IR:

Remove GTF_LATE_ARG PR#68617
Substitute GT_RET_EXPR in inline candidate arguments PR#69117
Remove stores as operands of calls in LIR PR#68460

General Optimizations
A few general JIT optimizations were done in below PRs:

PR#68105 enabled multiple nested "no GC" region requests.
PR#69034 removed "promoted parameter" tailcall limitation.

I think we may also want to mention that crossgen2 now has been published with NativeAOT?
/cc: @agocke

An interesting question -- it does demonstrate that we're shipping programs using NativeAOT, but crossgen is also effectively private surface area, so I'm not sure if it would be helpful to most blog readers

System.Reflection performance improvements when invoking members
The overhead of using reflection to invoke a member (whether a method, constructor or a property getter\setter) has been substantially reduced when the invoke is done several times on the same member. Typical gains are 3-4x faster.
See https://github.com/dotnet/runtime/pull/67917 for more information.
Using the BenchmarkDotNet package:
using BenchmarkDotNet.Attributes;
using BenchmarkDotNet.Running;
using System.Reflection;

namespace ReflectionBenchmarks
{
    internal class Program
    {
        static void Main(string[] args)
        {
            BenchmarkRunner.Run<InvokeTest>();
        }
    }

    public class InvokeTest
    {
        private MethodInfo? _method;
        private object[] _args = new object[1] { 42 };

        [GlobalSetup]
        public void Setup()
        {
            _method = typeof(InvokeTest).GetMethod(nameof(InvokeMe), BindingFlags.Public | BindingFlags.Static)!;
        }

        [Benchmark]
        // This went from ~116ns to ~39ns or 3x (66%) faster.
        public void InvokeSimpleMethod() => _method!.Invoke(obj: null, new object[] { 42 });

        [Benchmark]
        // This went from ~106ns to ~26ns or 4x (75%) faster.
        public void InvokeSimpleMethodWithCachedArgs() => _method!.Invoke(obj: null, _args);

        public static int InvokeMe(int i) => i;
    }
}

Observability
Expose performant ActivityEvent and ActivityLink tags enumerator methods dotnet/runtime#68056
The exposed methods can be used in the perf critical scenarios to enumerate the Tags objects without any extra allocations and with fast items access.
namespace System.Diagnostics
{
    public partial struct ActivityLink
    {
        public Activity.Enumerator<KeyValuePair<string, object?>> EnumerateTagObjects();
    }

    public partial struct ActivityEvent
    {
        public Activity.Enumerator<KeyValuePair<string, object?>> EnumerateTagObjects();
    }
}

Can you please provide some sample code for the above?

@AngelosP one minor erratum concerning the IAsyncEnumerable example:
// It now works and no longer throws NotSupportedException
JsonSerializer.Serialize(new MyPoco { Data = ... }, MyContext.MyPoco);

The above is not support and will always throw, since IAsyncEnumerable requires one of the async serialization methods. For the sake of correctness it should probably read:
// It now works and no longer throws NotSupportedException
await JsonSerializer.SerializeAsync(new MyPoco { Data = ... }, MyContext.MyPoco);

.NET 7 GA is available. Closing these pre-release issues.


Ninja response files

This PR adds support for @response files for llbuild ninja.
Changes:

rspfile and rspfile_content rule attributes support
${in_newline} parameter support
simple test for response file deletion when a rule succeeded and response file content

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Errata vs original wayback-machine-downloader, Sub-Directory Target, Spaces in Filenames, and Port Number in the Archive Address.

A couple of issues have cropped so far that have kept me from using this tool as I'd really like to:

When I input a target URL like,
example.com/documents/
rather than pull everything in the target directory, in this case /documents/ (including the many sub-directories in that I'd like to get), instead it still just tries to pull the entire site at the root (example.com)

Also, the files that are saved end up with "%20" replacing the spaces in the original filenames which makes it a huge hassle if the website you're working with has thousands of files with spaces that would then need to be manually renamed back to their original names be fileable/sortable/non-duplicating vs earlier backups.

Also, some pages on Wayback Machine are backed up with a port number in the URL (for some reason) such as www.example.com:80 which kicks back the following error when otherwise running:
NotADirectoryError: [WinError 267] The directory name is invalid: 'C:\Archive\www.example.com:80'

A couple of issues have cropped so far that have kept me from using this tool as I'd really like to:

When I input a target URL like,
example.com/documents/
rather than pull everything in the target directory, in this case /documents/ (including the many sub-directories in that I'd like to get), instead it still just tries to pull the entire site at the root (example.com)

Also, the files that are saved end up with "%20" replacing the spaces in the original filenames which makes it a huge hassle if the website you're working with has thousands of files with spaces that would then need to be manually renamed back to their original names be fileable/sortable/non-duplicating vs earlier backups.

Also, some pages on Wayback Machine are backed up with a port number in the URL (for some reason) such as www.example.com:80 which kicks back the following error when otherwise running:
NotADirectoryError: [WinError 267] The directory name is invalid: 'C:\Archive\www.example.com:80'

2 and 3 i will have a look soon. for your first one - did you use current or full download?

fixed 2 and 3 with the new release. i also clarified the current path-structure in readme. have to overthink if it makes sense to use the requested url/path as "root" for all timestamps. my intention on the path is, that there is always the root of the query as startpoint inside the output containing then the queried path.


DaemonSet Pods scheduling doc is a bit stale

This is a Bug Report

Problem:
The "How Daemon Pods are scheduled" section at https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled is a bit stale and difficult to understand. The section in its current form seems to be the result of many additions and removals while the ScheduleDaemonSetPods feature went through its various release states.
There are various problems:

An unsolicited reference to a ScheduleDaemonSetPods feature. To my concern, this feature is GA, and enabled by default.
It is mentioned that: "... DaemonSet pods are created and scheduled by the DaemonSet controller instead...", then some problems of this approach are listed, and suddenly, the ScheduleDaemonSetPods bumps into the conversation. My general impression after reading this part was that, on the latest K8s, the DS controller schedules the Pod, but I can somehow configure it to be scheduled by the default scheduler. Very confusing.

By looking through the code I realize that as of K8s 1.17 (when the  ScheduleDaemonSetPods became stable), all DaemonSet Pods are modified with a node affinity and the default scheduler schedules them. In no case does the DS controller set the spec.nodeName. Does this hold?
Proposed Solution:
I propose that:

We go through the "How Daemon Pods are scheduled" section & uncover the meaning of every single sentence
Settle on the technical details wrt DaemonSet and what the state is now
Rewrite it making clear what the current state is.

I can contribute if you agree that this restructure is needed.
Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled

I think this duplicates a much older issue @gregth
You are welcome to work on the DaemonSet docs; the older issue is already triaged as accepted. Feel free to contribute!
Some of these details about scheduling might belong within https://kubernetes.io/docs/concepts/scheduling-eviction/ - have a think about this (I haven't looked recently, so maybe there is nothing to move). You can move content and replace the original with a link to its new home.
/remove-kind bug
/triage duplicate
/language en

If DaemonSets Pods don't have special scheduling, maybe a section about how DaemonSets are scheduled is no longer needed.

@sftim that makes sence.
But since this section existed for a long time, and users may still look for it or reference it, we may gently shrink it to a few lines, stating the absolutely necessary information: the DS controller creates the Pod with affinity that matches the node where the Pod shall run, then scheduler takes over and assigns the Pod to the node, if other conditions permit, etc.

Sure, that works.

@sftim Per our discussion, I sent a PR: https://github.com/kubernetes/website/pull/39392


Sound off option

Would be great to have a sound off option.
Looked at the docs and GitHub without any luck.
✌

Although for Brightcove Player, in this case will be the same for Video.js: http://docs.brightcove.com/en/video-cloud/brightcove-player/guides/volume-control.html
-Matt

Yup, you probably wanted muted().
You can either call muted() on the player, or supply it as an html attribute on the video element:
<video muted controls class="video-js"></video>

Hope that helps. (Thanks @mboles!)

Thanks!


Support Expression build in AstBuilder

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

run starrocks_be_unittest

run starrocks_be_unittest

Any test case for this PR?

There is currently no independent UT, and all code has no logical entry. I will change the Parser entry in all UTs to the new Parser in the next PR that opens the new Parser. At that point, the new Parser can use all existing tests


test PR do not merge

Signed-off-by: Drew Erny<EMAIL_ADDRESS>
- What I did
- How I did it
- How to test it
- Description for the changelog

@dperny this one still needed, or can we close?


Administratively close complaints by request

Requested by Jim C. Multiple lists are expected.

New script for administratively closing complaints
begin
    declare
        @adminId uniqueidentifier,
        @comment nvarchar(4000);

    declare @complaintsToClose table (
        id int
    );

    insert into @complaintsToClose
    values
        -- list all complaint IDs here
        (7519),
        (7287);

    select @adminId = Id
    from AspNetUsers
    where Email =<EMAIL_ADDRESS>
    select @comment = 'This complaint is being administratively closed. ' +
                      'If EPD recieves another compaint regarding this ' +
                      'issue, we will treat it as a new complaint.'

    insert into ComplaintTransitions
        (Id,
         Comment,
         ComplaintId,
         CreatedById,
         CreatedDate,
         DateTransferred,
         TransferredByUserId,
         TransitionType)
    select newid(),
           @comment,
           Id,
           @adminId,
           sysdatetime(),
           sysdatetime(),
           @adminId,
           4 -- Closed
    from Complaints
    where ComplaintClosed = 0
      and Deleted = 0
      and Id in (select id from @complaintsToClose);

    update c
    set ReviewById          = @adminId,
        ReviewComments      = @comment,
        ComplaintClosed     = 1,
        DateComplaintClosed = sysdatetime(),
        Status              = 4 -- AdministrativelyClosed
    from Complaints c
    where ComplaintClosed = 0
      and Deleted = 0
      and Id in (select id from @complaintsToClose);

    select Id,
           ComplaintClosed,
           CreatedDate,
           DateComplaintClosed,
           ReviewById,
           ReviewComments,
           Status,
           UpdatedById,
           UpdatedDate
    from Complaints
    where Id in (select id from @complaintsToClose);

    select ComplaintId,
           Comment,
           CreatedById,
           CreatedDate,
           DateTransferred,
           TransferredByUserId,
           TransitionType
    from ComplaintTransitions
    where ComplaintId in (select id from @complaintsToClose)
      and TransitionType = 4;
end;

Received spreadsheet for WPB complaint IDs to close

Added stored procedure admin.CloseComplaintsTableType to administratively close complaints. How to use the SP:
begin
    declare @complaints as admin.CloseComplaintsTableType;

    insert into @complaints
        (Id, ReviewComment)
    values
        (999998, 'Administratively closed with this review comment.'),
        (999999, 'Administratively closed with another review comment.');

    exec admin.CloseComplaints @complaints;
end;

Final set of complaints submitted and processed.


Updated stripes to v5

Update stripes to v5

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-plugin-find-package-title/job/PR-21/1/

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-plugin-find-package-title/job/PR-21/2/

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-plugin-find-package-title/job/PR-21/3/


UsesOnlineServices should not require @tag prefix

Open settings, search for
usesOnlineServices notice no results
Search for
@tag:usesOnlineServices notice there are results
I do not understand why is it neccessery to explicitly specify the @tag. The downsides of this are:

less discoverable by users
not consistent with the rest of our settings story where we behave a bit like google -> whatever you type we try to be smart and give results back. We require no explicit need to specify the name / description, we just search across both

In the extnesions view it is a different story since the searching is done by the marketplace and we can not be smart as for settings. Being consistent with extensions view does not make sense to me here.
Tag feels like an implementation detail to me.
fyi @kieferrm @roblourens

I think this is a different use case than normal searching. Typically we give our best guess as to what the user wants. Here, the user wants an exact set of settings, no more and no less. So I think having different syntax is justified.
The user will probably never type out that full string. Right now they will find it under the ... menu. In the future we could also have intellisense like we do for the extensions viewlet.

My point is that the user shuold easily discover this by typing
"online service", "do not send data" and similar queries.
Also why are online services special that they deserve an entry in this menu. If we add it for all the settings people search for that menu will soon be cluttered.

I think online services are special because they are a well defined set of settings that users have already expressed interest in modifying as a single block. There aren't many other tags we can think of, so clutter doesn't seem like a big issue at the moment. If we do end up adding a lot, we can take the extensions search approach of hiding all the different tags behind the autosuggest widget and only showing the most general settings in the dropdown.
Natural language queries are nice, but not ideal for something so concretely defined. For instance, Google can be as fast as they are because if results are missing, nobody knows, and if results don't really make sense for the given query, people can mostly figure out that that isn't what they were looking for. However, if we provide an incomplete set of results, people will know, and they'll go on to say its a conspiracy to steal their data or something. And if we present results that aren't relevant, people won't know, and settings like (contrived example): Send data to local Tensorflow service for online training will show up in searches even though they aren't online services, leaving people confused as to whether that setting actually sends data online or just has a weirdly worded description.
Regardless, I think the plan is to augment all the online service descriptions with something along the lines of "This is an online service which sends data to https://...." anyways, which will make it easier to naturally search for these settings with "online service" or "send data" or similar, but even with that it would be nice to provide users a concrete set of settings so that they know the search term isn't missing out on any, and they know every result is actually a setting controlling some component of uploading data.

And another point is that we can't rely on natural language search to return good results, specifically in this case, because a user who cares about these settings has probably disabled it 😁

@isidorn has still a valid argument, i.e. that I should also be able to find these settings using NLS. I.e. we should make sure that they are returned (potentially among other things) from the bing service. At the same time, we also should have a way to show they user a well-defined set of settings that are exclusively about online services.

@kieferrm We'd get that from adding a "This is an online which sends data to ..." right?

@JacksonKearl, yes, we need to update the descriptions of the settings accordingly, or we need to define alt words for the settings keys to the NL search service.

Tag feels like an implementation detail to me

We needed a way to have a well defined set of settings and also a way for extensions to contribute to this set. We went with tags.
Now, whether we want to support a generic tag based search or only support search for specific tags is up for discussion. A generic tag based search is indeed useful, if there are a host of tags to work with. Else we can skip the @tag: and just go with @usesOnlineServices similar to @modified

Also why are online services special that they deserve an entry in this menu.

Like @kieferrm said, this was to have a way to show the well-defined set of settings to aid discovery for users who want to have a fine grained control over features that make network requests without them explicitly asking for it. The new settings editor is still in preview. If we do go with having the search box provide suggestions, then a menu entry will not be needed as much.

we need to update the descriptions of the settings accordingly

We can definitely do this for the settings we own, it gets tricky to enforce on this on extensions.

or we need to define alt words for the settings keys to the NL search service.

@roblourens tags could be used as alt words directly. The NLS is smart enough to split the words based on camel casing right?

Core Settings descriptions are updated with https://github.com/Microsoft/vscode/commit/3b82258154ab7a6c60065a3e8a8ac36a3ccbe091

Hi
Tải Outlook for iOShttps://aka.ms/o0ukef

From: Ramya Rao<EMAIL_ADDRESS>Sent: Thursday, August 2, 2018 5:00:52 AM
To: Microsoft/vscode
Cc: Subscribed
Subject: Re: [Microsoft/vscode] UsesOnlineServices should not require @tag prefix (#55374)
Core Settings descriptions are updated with 3b82258https://github.com/Microsoft/vscode/commit/3b82258154ab7a6c60065a3e8a8ac36a3ccbe091
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/55374#issuecomment-409738451, or mute the threadhttps://github.com/notifications/unsubscribe-auth/An083b6M58tNnDgJoTdGfarXOBCWt-pvks5uMiUUgaJpZM4Vmmno.

For the July update, we wont be adding the option to show the settings for online services in the menu. It will continue to appear in Insiders, but wont in Stable with https://github.com/Microsoft/vscode/commit/582cd9547d435735e583be540d0ba0c8262880c8


CDN-in-a-Box now uses Snapshots instead of legacy CRConfig

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue

Switches the Traffic Monitor init script from using a legacy, undocumented endpoint to a standard one, and updated documentation accordingly.
Which Traffic Control components are affected by this PR?

CDN in a Box
Documentation

What is the best way to verify this PR?
Build and run CDN-in-a-Box
CDN-in-a-Box has no tests.
The following criteria are ALL met by this PR

[x] I have explained why tests are unnecessary
[x] This PR includes documentation
[x] An update to CHANGELOG.md is not necessary
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3884/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3890/
Test PASSed.


Update hail to 0.2.100 in dataproc helper

Not merging immediately, as this will need a (manual) rebuild of the Dataproc image before deployment.


Added spanish translation files for client and server side

@gschlager shall we merge this, pending changes? It pre-dates Crowdin integration. 🙂

No, we can't merge it. Translations have to go through Crowdin. All changes would be overwritten by tomorrow's update.
@criadoperez Thanks for the PR, but we accept translation updates only through Crowdin.

Ok, no problem. Thanks for the Crowdin link. I'll continue there.

Thank you! ☺


Error in cv2.line function

"D:\Python Programs\venv\Scripts\python.exe" "D:/Python Programs/draw_in_air.py"
Traceback (most recent call last):
File "D:\Python Programs\draw_in_air.py", line 73, in
mask = cv2.line(mask, (a,b), (x,y), (0, 0, 255), 6)
cv2.error: OpenCV(4.5.2) :-1: error: (-5:Bad argument) in function 'line'

Overload resolution failed:

Can't parse 'pt1'. Sequence item with index 0 has a wrong type
Can't parse 'pt1'. Sequence item with index 0 has a wrong type

getting above error even after copy pasting the code.
there is one observation- if values of a,b,x and y are integer then it don't show this error but then code doesn't work as expected and if values of a,b,x and y are float then i am getting above error

Same problem here..how to solve it..any ideas??

Same problem here..how to solve it..any ideas??

you can type cast these values of pt1 and pt2 to int then it will work I'll soon update the code


how to broadcast message with tcp server?

first,retty is very nice, but we have some a small problem,
how to broadcast message with tcp server? or exclude specific id?
and
how to find any client context with tcp server?
or
can be clone any inbound or outbound handlers to hashmap?
maybe we need socket handle map or uuid map?

for game server ,we need find client context for close\write\boardcast\check, so,maybe we need some trait or function.

Thanks for the feedback. Let me add a broadcast or chat server to show how to use it.

https://github.com/retty-io/retty/releases/tag/v0.10.0 is released to change pipeline.finalize and PipelineFactoryFn to return Arc.
examples/chat_tcp_server.rs shows how to do the broadcast message to other peers.


Adding the  to the DOM

Hi, any specific reason I have to add the canvas element to the DOM to be able to convert it to PNG? I'm getting an error on the following line.
More of a inquiry than an issue, since I can live without it, but it would come in handy if possible i.e.
Thanks

that just caches the class as a property on the canvas element... maybe it's conflicting w/ a native property. what's the full source code of what you're trying to do so i can replicate?


feat: add styling for jsx using twind

usage:
import { install } from "x/tw.ts";
import { defineConfig } from "@twind/core";

// create a twind config
const twindConfig = defineConfig({
  presets: [presetAutoPrefix(), presetTailwind()],
});

// install the twind connfig
install(twindConfig)

// use
const app = new cheetah();

app.get('/', (c) => jsx(c,
styled h3 component
))

app.serve() // your element should be styled!

testing is a bit inefficient
there is probably a way to test for styling without using DOMParser :p

@not-ivy you forgot to run deno task check.

squash and merge please 😄

@not-ivy could you please move the updated jsx function to the root and name the file render.ts & the function render plus leave the original test suite as is and create a separate one (render.test.ts) inside the test directory?
I'll then deprecate the old implementation.


Update build-windows.md, remove linux lib deps installation line.

Removes misinformation, as this is already on the dogecoin/docs/build-unix.md page. Installing these linux libraries from aptitude can, and will interfere with the libraries that are cross-compiled from /dogecoin/depends/packages m4's using gcc/mingw.

its a good idea to use aptitude to install the required linux dependencies (but newer versions) just before cross compiling those same deps with the mingw toolchain?

quite simply, it is not a step in cross compiling the codebase for windows on WSL/Linux, and yes I was referring to Qt having been problematic with things of that nature in the past, and we've all seen Qt bugs go away and then resurface in future versions. Also, experienced users don't need these instructions, and know how to specify paths anyway, but inexperienced users do not, so I made this PR for the greater good. cheers!
ps: nice to see a very active maintainer here, and I appreciate your vigilance.

@patricklodder i can help bump some deps versions and linux cross compile updates for building with mingw under ubuntu.. i know much of codebase needs updating, but i can do lil pieces at a time here n there if ya need some help


Updating Dfareporting.php

Adding an updated DCM API service definition to address #803.

These files are auto-generated, so this change will not take.

Does that mean it won't be updated to support the DCM API v2.3? Or does it mean that the update to the new API version will happen automatically before the sunset date on february 29?

It means it'll be updated when the script is manually run to update all the APIs. It's not a great solution, but it's all we have right now.
For those who need it sooner can implement the changes in this pull request.

Thanks for the info. Will the API update be available before the sunset date? Also will it be available in the v1 branch?

@bshaffer When will you manually run the script to update all the APIs? I don't really wanna fork and apply the changes myself.

these have been updated for v1-master (see #834), and the PR for master is here: #835
I won't be merging these changes into master because they break BC. I will need to tag a stable release (2.0.0) first, and then I can merge them in. This will probably be in a week or two. So if you need this, just pull down my personal fork and use that.

this has now been merged into the master branch


Ticks for plots need to be hourly

Overview
Currently the ticks are very precise, let's make this hourly so that it's easier for user to see. No more that 15 number of ticks!

Proposed Solution
The function _compute_tick_labels currently determine the tick marks for the qc plot pointed out in https://github.com/uw-ssec/offshore-geodesy/issues/175#issuecomment-1777992065
https://github.com/uw-ssec/offshore-geodesy/blob/d0f2bd01e387c287aa2b78eaaab007a82337a013/src/gnatss/ops/qc.py#L47-L75
Currently this implementation get's the minimum and maximum of the data timestamp, then the step for each tick is determined by dividing the difference by n_ticks.
This issue propose a change to have the tick steps by hourly if the difference b/w min and max is more than 1 hour, or be minutes if the difference is less than an hour with n_ticks no more than the specified n_ticks.


Strange formatting on Budget scf

I don't yet know if this is related to the latest release or because I toggled on some new settings, but I wanted to report seeing what appears to be a styling bug in the Budget view:

I'm on version 2.22.0, and have the following settings toggled on in the Budget settings:

Make the Categories Dropdown Larger
Stealing From Future Alert
Stripped Budget Rows
To Be Budgeted Warning
Warn When Target Balance is Not Reached
Budget Rows Progress Bars > Pacing on name column and goals on budgeted column
Category Solo Mode and Toggle Master Categories > Enable Category Solo Mode

Finally, here's a settings export:
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":true},{"key":"AdjustableColumnWidths","value":false},{"key":"AutoDistributeSplits","value":false},{"key":"AutoEnableRunningBalance","value":false},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"both"},{"key":"BudgetQuickSwitch","value":false},{"key":"BudgetSpendingGoal","value":false},{"key":"BulkManagePayees","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"CategorySoloMode","value":"cat-solo-mode"},{"key":"ChangeEnterBehavior","value":false},{"key":"ChangeMemoEnterBehavior","value":false},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseSideMenu","value":true},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomFlagNames","value":false},{"key":"DateOfMoney","value":false},{"key":"DaysOfBuffering","value":false},{"key":"DaysOfBufferingDate","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DeselectTransactionsOnSave","value":false},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":false},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":false},{"key":"FilterCategories","value":false},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideClosedAccounts","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":true},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":false},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LinkToInflows","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"0"},{"key":"NotesAsMarkdown","value":false},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResizeInspector","value":false},{"key":"ResizeSidebar","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"0"},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":false},{"key":"ShowCategoryBalance","value":true},{"key":"ShowIntercom","value":true},{"key":"SpareChange","value":false},{"key":"SplitKeyboardShortcut","value":true},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"StripedBudgetRows","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":true},{"key":"ToBeBudgetedWarning","value":true},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"ToolkitReports","value":false},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":false},{"key":"l10n","value":"0"}]

That's the progress bar.

OK,  but when I expand a category, it's also pretty much straight down the middle of the progress bar?

Is it correct that this is a styling bug that I'm seeing it when the category groups are all collapsed, or is it just and aesthetic difference of opinion?
I'll do some more toggling of features to narrow it down.

It's the middle of the month therefore you're seeing it in the middle of the category area. It's not a styling bug. It's not a bug. I have seen times when the line in the category name doesn't line up with the sub-categories and that is a bug related to font styling (bold vs non-bold).

oooOOOOoooh. That is the overall monthly progress bar, not progress of spending per category. If I'm hearing you right, on the 20th, it will be 2/3 of the width along. Apologies.

You've got it. It's the amount of time that has passed since the beginning of the time period (month). No need to apologize.


Feature/package with readme

README.md has just updated!

Remove all npms
Specify node version

Thanks for the reviews! merging it now :)


As a Partner I want to have the portal advertise my logo ..so that I market my involvement/my organisation and other related projects etc

original id#87

Needs clarification, is this related with #92? Where do you want the logo?


Reapplying lost edits.

These corrections were accepted previously but appear to have been lost due to careless merging.
Specifically:

The style of the text must be consistent with footnote 13, or that footnote makes no sense. (This point may also need correction later on, I haven't read that far.)
"respectively" means the lists must be in the same order. Changed "<, >, and =" to ">, <, and =" to match "respectively, greater than, less than, or equal to" as in the original text.
Inserted missing paragraph break that was in the original text.

Please make the edits in 'content' directory instead. The html files in root directory will be overwritten by render_all.sh. You can add more commits to this pull request, I think.

If it's auto-generated does it belong in the repository in the first place? Does the xuanji.appspot.com website pull from the repository directly or something? Or does that have to be updated manually?
Anyway I applied the edits to the file in the contents directory as requested. I'm not sure what to do about the file in the root directory, since those edits now seem pointless. Should I leave it? Should I apply another commit to reverse the changes? Can you cherry pick it out or something?

Good point. We should negotiate with @zodiac about what to do with the generated files. Ignoring these would lessen confusion. For now, the site is updated manually by him.
It's fine to leave both commits in. Thanks!

I shall gitignore the generated files - should have done it long ago.


fix millisecond timeout in tb_peek_event

Timeout for tb_peek_event did not work correctly, this should fix it.

I mainly fixed this for jermbox, so the submodule there should also be updated if this is accepted.


Don't allow undo of changes to project extents or geolocation.

Letting something like "undo all" revert your changes to geolocation, etc. could be very unexpected.

Thanks. I wasn't sure if it was simply because applying a changeset that changes these properties will put the in-memory representation of the iModel into an inconsistent state (it will). We will need to address that as some point (probably sooner, now that you're allowing people to create, push, and pull such changesets).


Change the TTL to 60 for Register EDU and SVC CNAME Records

Context
Change to the default TTL to 60 for all register CNAMES
Changes proposed in this pull request
TTL Changed to 60
Guidance to review

Azure portal dns zone CNAME records to display TTL value of 60

Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[ ] Do we need to send any updates to DQT as part of the work in this PR?
[ ] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 Register - Create DNS zone in Azure DNS via terraform and migrate


rpmsgsocket: add rpmsgsocket test case

Summary
rpmsgsocket: add rpmsgsocket test case
Impact
Testing

Test case of https://github.com/apache/incubator-nuttx/pull/2964


Fix invalid constant type & multiple frame support

Constants of type Number can't contain more than one decimal point as in 0.5.5

Added support for receiving more than one frame at a time

Merged into the stretch branch instead.


Single Service for Search Live Tests

Some of this seems fairly clunky/ugly and I'd like to clean it up some. But I also wanted to get some feedback about the general approach before rolling it out further. So far I have only updated the synonym maps live tests. Some things I don't love:

now have to have every individual test delete every synonym map (or whatever) it creates. This can vary by test so I don't think there is good way to automate it, but it's tedious and error prone.

Alternatively, they could all get random names and the thes can be less strict about checking the number of existing [created things], but that also seems less than ideal (especially when testing the APIs that are explicitly for listing things)

The global resource group and search service code all seems pretty cluttered. I have some ideas to improve but wanted to make sure there wasn't just already some similar or existing things that could be (re-)used from somewhere.

cc @johanste @scbedd @lmazuel

Closing, was decided service-per-test is actually not a problem/burden. Since it is also faster and simpler, there is no reason to merge this.

Well, this is a mess now. Will make a new PR


Is iPhone XS Max supported?

Hi,
This is an amazing project. I was looking for something like this for a while.
Is iPhone XS Max supported? There is a workaround, but it's not so efficient, as it is placing an iPhoneX (much smaller) into the iPhoneXS Max background. Too much space wasted.
Is there a proper way of supporting this? Officially we need 6.5" (XS MAX) and 5.5" (8 Plus). The rest is scaled down automatically anyway.
I hope this project is still maintained.
Thanks,
Houman

The way is done at the moment is that iPhone X screenshots are used for both iPhone X and Xr. The iPhone Xr has the same resolution as the iPhone Xs Max.

I think there is a problem. I took the exported files and dragged them to the 6.5" tab and was told the dimensions were wrong. It wants 1242x2688. I cannot get the template to produce that size?

 I didn't see a reason to use different iPhone X frames. They all look similar enough for the purpose of App Store screenshots. The template, however, does spit out all the necessary sizes for the XS and XR / XS Max. It might be good to have the template create an XS Max folder (even though the XR shots are the same size). Might clear up some confusion. I'll consider adding that to the template. Gonna close this out for now. Thanks.

Note that I have just had a rejection from app store because I used iPhone X frame in the 6.5" screenshots. They said "Specifically, your 6.5-inch iPhone screenshots do not display the app in the correct device frame."
Would be great to get the latest device frames added!

@jarrodbell I've added iPhone XS Max frames in the latest version. Thanks!


updated powermate (1.2.4,3.2015.08)

https://github.com/caskroom/homebrew-cask/issues/17380#issuecomment-173411458

Thank you for the contribution. It needed some fixes, so they were made in 0635ab0e70d2ae7b4b334a6734dd5c20aaa1e7b6. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Highlighted cell movement bug with frozen rows/columns

Describe the bug
If some rows and/or columns are frozen, then moving the highlighted cell using arrow keys causes the correct cell to be selected but the sheet view doesn't auto scroll.
To Reproduce
Steps to reproduce the behavior:

Open a sheet with frozen rows (say 2)
Scroll down a lot and select a cell in say row 30
Now press up arrow to move upwards
See error

Expected behavior
The non-frozen view should scroll when the highlighted cell is beyond the viewing range.
Screenshots

Notice the disparity between cell selected and the sheet view.

@zyc9012 / @gazedreamily  can you help here?


Do not print traceback when exiting with Ctrl+C

There is no need of showing the traceback when exiting the server with Ctrl+C
I know that this is a demo server and not for production use but if someone which is new to Python run it and see the traceback can be confusing.

I think a traceback is probably appropriate here, since its a learning exercise...
I don't want to hide anything from a beginner. I'd rather a beginner was confused and looked it up, than hide it from them.


cleanup unused variables and change Clab.WithRuntime(...) to use *runtime.RuntimeConfig

the Clab bound options where not used any more. Hence I've deleted them.
changed Clab.WithRuntime from (name string, d bool, dur time.Duration, gracefulShutdown bool) to (name string, rtconfig *runtime.RuntimeConfig).

now when I see the full PR I am not sure it is a good idea to import runtime package for cmd package

I think the values are still used, they just moved to runtimeConfig
I think it's ok, as long as runtime and clab do not import cmd, it should be cycle free

Also the debug variable, is just consumed in one case by the docker runtime.
https://github.com/srl-labs/containerlab/blob/fa9c2dae742526716c09de7e2f96a2c142fcdde8/runtime/docker/docker.go#L221-L226
And even this can be left out, since this is omitted via the debug level, which even used the global debug var.
To be honest that flag is not really needed atm.

Also the debug variable, is just consumed in one case by the docker runtime.

the debug is used not only in docker, it is also used in ignite
https://github.com/srl-labs/containerlab/blob/4caa86f05137210a07dce9f588689712683ef244/runtime/ignite/iginite.go#L239

but the rest looks ok to me
Building the binary with -race doesn't detect any issues with passing runtime config as a pointer, so should be ok as well


about page navbar glitch fixes

#45

https://github.com/ceadoor/cea.ac.in/pull/46/commits/1a2096818a7d7d341fa1dfef8c027c9709f3f845


Identical CardId for the same card

Hi,
I have question regards identifying cards that have already been registered. Right now for the same TEST cards(identical card number, expiry date, ccv) registerCard method return different CardIds. Is it only for test cards? If no, how to determine that card has already been registered?

Hi @StasevichVitaliy and thanks for your question !
On our side, each registration of a card is a new card object, with a different CardId.
Why ? Because, at the moment, you can (and you have to) register the same card (ie. same card number) for each currency you want to use this ward with.
Example:
Card 1234XXXXXXXX7890 - EUR = CardID 1
Card 1234XXXXXXXX7890 - GBP = CardID 2
Card 1234XXXXXXXX7890 - EUR = CardID 3 (weird, but possible)
If you wanna find if a card has been registered, please use our Fingerprint feature: https://docs.mangopay.com/endpoints/v2.01/cards#e952_list-cards-for-a-fingerprint
Card 1 / 2 and 3 has the same Fingerprint value, even if Object ID is different.
Mickaël

@mickaelpois thanks a lot


Multiple IHostedSerivces or BackgroundService implementations

Could you provide an example that uses multiple IHostedServices or BackgroundService implementations?
I cant seem to find much about it and when I try it, I am constantly only hitting the first registered service.
I have tried implementing it via BackgroundService and putting the code in ExecuteAsync and I have tried implementing IHostedService directly and putting the long running code in StartAsync.
I think the issue is return Task.CompletedTask; is never called.
For example I have two Kafka consumers implemented as BackgroundServices
The code looks identical in both aside from the topic and an OnMessage methods
    protected override Task ExecuteAsync(CancellationToken stoppingToken)
    {
        var kafkaEndpoint = _kafkaConfig.Endpoint;

        var kafkaTopic = "PhoenixEventStore";

        var consumerConfig = new Dictionary<string, object>
        {
            { "group.id", "consumer1" },
            { "bootstrap.servers", kafkaEndpoint },
            { "auto.offset.reset", "earliest" }
        };

        using (var consumer = new Consumer<Null, string>(consumerConfig, null, new StringDeserializer(Encoding.UTF8)))
        {
            consumer.OnMessage += (obj, msg) =>
            {
                Log.Information($"Consumer1 Received {msg.Value}");
            };

            consumer.OnPartitionEOF += (_, end) =>
            {
                Log.Information($"Consumer1 Reached end of topic {end.Topic} partition {end.Partition}.");
            };

            consumer.OnError += (_, error) =>
            {
                Log.Error($"Consumer1 Error: {error}");
            };

            consumer.Subscribe(new List<string>() { kafkaTopic });

            while (!stoppingToken.IsCancellationRequested)
            {
                consumer.Poll(TimeSpan.FromSeconds(10));
            }

            //consider setting value that check whether the consumer has stopped polling.
        }
        return Task.CompletedTask;
    }

Since both services are long running the Task.Complete is never hit. However if I comment out the while loop both services ExecuteAsync are hit instead of just the first one registered.
Thanks!

Hello @shanemontgomery ... You'll get a faster answer if you open your question on Stack Overflow or ask on a support chat, such as Slack or Gitter.

Thanks for contacting us.
We don’t have the resources to invest in this area, so we are closing the issue. Should your request generate enough  👍 responses, we’ll reconsider.


[fix] Export with resolved uri to coco, yolo, voc

How are we gonna solve the problem with presigned URL lifetime here?

How are we gonna solve the problem with presigned URL lifetime here?

task.data['$resolved$'] is only for COCO/YOLO/and other export formats for image (and other media) downloading. After export this key $resolved$ will be removed.


Image issue

How can i deploy the image on the shopify store through url?
I have implemented the graphql query it is working fine but in the local code how can i send the url like-https://explosion-globe-giant-mm.trycloudflare.com/uploads/gemstone/image_1706105049048.png
the above url is using authentication and host as well so how can i use this?

Hm i'm not sure what you mean. But it seems like you're trying to upload a file from your app to shopify store.
In that case take a look at Uploading files to shopify using graphql

Hm i'm not sure what you mean. But it seems like you're trying to upload a file from your app to shopify store.
In that case take a look at Uploading files to shopify using graphql

Thanks

Hello @Mini-Sylar ,
I want to upload the image in the web/uploads folder and it is uploadig successfully so how can i access this image in the frontend vue file. if i am using the-https://waves-louise-unlikely-galleries.trycloudflare.com/uploads/imageName.it is not working.
Could you please help me out on this?

By web/uploads folder i'm assuming you mean the one on your app and not shopify's CDN
In that case here's how I would handle it
Step 1
let's assume I have a folder in my web directory called uploads. I can serve resources direcly using:
├── web
│   ├── index.js
│   ├── uploads
│   │      ├── team_img_1.jpg
# ....Your existing code
app.use(shopify.cspHeaders());

// Serve images from the "uploads" directory
app.use("/api/images", express.static("uploads"));

Step 2
I then setup an action in my store (e.g counter.js from the template) to fetch from uploads directory:

import { useAuthenticatedFetch } from '../helpers/useAuthenticatedFetch'
const useFetch = useAuthenticatedFetch()
# Other existing code
const fetchImages = async (image) => {
    try {
      const response = await useFetch(`/api/images/${image}`)
      if (!response.ok) {
        throw new Error(`Failed to fetch image: ${response.status}`)
      }
      const blob = await response.blob()
      return URL.createObjectURL(blob)
    } catch (error) {
      console.error(`Failed to fetch image: ${error.message}`)
      return null
    }
  }

 return { /*others*/, fetchImages }

Step 3
Then it's as simple as calling my action in my vue file
<template>
 <div class="fetch-image">
        <button @click.prevent="fetchImage('team_img_1.jpg')">Fetch Image</button>
 </div>
 <img :src="image" />
</template>

<script setup>
// useToast and other stuff

const fetchImage = async (imageName) => {
  await appBridge.dispatch(Loading.Action.START)
  useToast('Fetching image')
  try {
    const response = await useProductCounterStore().fetchImages(imageName)
    image.value = response
    await appBridge.dispatch(Loading.Action.STOP)
  } catch (error) {
    await appBridge.dispatch(Loading.Action.STOP)
  }
}
</script>

Screenshot

Final Image

OK,Thank You so much ,I will implement this and Let you know if it is needed.


Removed redundant else statement

Description
The else statement is not needed because the return statement will always
break out of the enclosing function. Removing the else will reduce
nesting and make the code more readable.
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7d1c9ab) 95.07% compared to head (27484d8) 94.83%.
Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #461      +/-   ##
==========================================
- Coverage   95.07%   94.83%   -0.24%
==========================================
  Files          34       36       +2
  Lines        1096     1181      +85
==========================================
+ Hits         1042     1120      +78
- Misses         54       61       +7

Files
Coverage Δ

ols/src/query_helpers/docs_summarizer.py
92.50% <100.00%> (ø)

... and 1 file with indirect coverage changes

/lgtm

/approve


Add project  description

@melloware @gastaldi WDYT?

Weird this didn't merge into master.  It looks like you merged from one of your branches to one of your branches.

Weird this didn't merge into master. It looks like you merged from one of your branches to one of your branches.

I only opened a patch but yeah i merged this in my fork version then opened this PR


Update for dry-configurable settings separation

The main change here is that we stop relying on Dry::Configurable::Config internal implementation details by using the new #configured? API introduced in https://github.com/dry-rb/dry-configurable/pull/143.
While we're here, we make one other small tweak to improve dry-configurable compatibility: use dry-configurable's class-level #finalize instead of Config#finalize directly, which will mean that we'll continue to have correct behaviour if dry-configurable ever moves any additional logic to this class-level method.

Since this is a fairly rote PR, I intend to merge it in a day or so (i.e. next time I'm working on this) to get ready for releasing both dry-configurable and dry-system.


Support mongodb without transaction support

Codecov Report

Merging #6 into master will increase coverage by 0.87%.
The diff coverage is 84.21%.

@@             Coverage Diff              @@
##             master       #6      +/-   ##
============================================
+ Coverage     68.04%   68.92%   +0.87%
- Complexity       92      108      +16
============================================
  Files            23       25       +2
  Lines           363      399      +36
  Branches         24       27       +3
============================================
+ Hits            247      275      +28
- Misses          108      115       +7
- Partials          8        9       +1

Impacted Files
Coverage Δ
Complexity Δ

...main/java/com/monjam/core/database/DbTemplate.java
100% <100%> (ø)
11 <7> (?)

...c/main/java/com/monjam/core/command/DbMigrate.java
100% <100%> (ø)
10 <1> (+1)
:arrow_up:

...va/com/monjam/core/history/DbMigrationHistory.java
100% <100%> (ø)
6 <4> (ø)
:arrow_down:

...ore/src/main/java/com/monjam/core/api/Context.java
91.66% <100%> (+11.66%)
5 <2> (+2)
:arrow_up:

...src/main/java/com/monjam/core/command/Command.java
92% <100%> (+2%)
6 <3> (+2)
:arrow_up:

.../main/java/com/monjam/core/command/DbRollback.java
92.59% <50%> (-7.41%)
9 <1> (ø)

...a/com/monjam/core/database/LegacyDbCollection.java
63.63% <63.63%> (ø)
4 <4> (?)

.../com/monjam/core/database/SessionDbCollection.java
75% <75%> (ø)
5 <5> (?)

... and 1 more

Continue to review full report at Codecov.

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


Known Issue: Notify not working as expected

Will fix notify not working as expected in the near future. But for my purposes it's working for what I need to do with it.

fixed


Image attributes

See
7e38491cec5309c1f31663b36be4feda7f97e991 delete attribute also form annotations on x
98641c99309e683c7a581f42824fb51cf8204684 track changes also for delete-btn
a4f5ba8b92f12b4c21b2e7871afdcf83db8a2c1c bbox uses attribute tool to track changes
b6910c61bf851182c0dc66ebc025e5b297aae932 simple attributes filter
9782ca6639853eab6a34e176aed3cb49f3e428b4 added export option
0b52c8deeb40e81a0e6be45e8eb57f2000863412 tool framework ftw 🙈
e94bac59649613deb689e837d961fa6062c899ad initial attributes verison, violates tools design
22f39529a928174ec23a47f96be625b33539a09a added attributes skeleton


Gesture-Controlled-Virtual-Mouse

💥 Proposal
Gesture Controlled Virtual Mouse makes human computer interaction simple by making use of Hand Gestures and Voice Commands. The computer requires almost no direct contact. All i/o operations can be virtually controlled by using static and dynamic hand gestures along with a voice assistant. This project makes use of the state-of-art Machine Learning and Computer Vision algorithms to recognize hand gestures and voice commands, which works smoothly without any additional hardware requirements. It leverages models such as CNN implemented by MediaPipe running on top of pybind11. It consists of two modules: One which works direct on hands by making use of MediaPipe Hand detection, and other which makes use of Gloves of any uniform color. Currently it works on Windows platform.

@Killer2OP   - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


How to remove youtube-dlg

I am using Ubuntu Mate.
I downloaded youtube-dlg_0.4-1~webupd8~zesty4_all.deb from http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/pool/main/y/youtube-dlg/
Then double clicked the file and thus install it.
When I needed to remove it, I opened synaptic and remove the youtube-dlg package.
Still some of the element is remaining and it is conflicting with my youtube-dl program which I installed using apt-get install youtube-dl
How to completely remove it?

@blueray453 what is the output of which youtube-dl ?

Still some of the element is remaining and it is conflicting with my youtube-dl
What elements conflict with youtube-dl?


Investigate using Vault and HSM to sign Fabric transactions

Please look into:

Vault -- what it does, how it works with both Soft hsm and actual cloud HSM, how it compares to hosted services like Azure Key Vault
How to use Vault and HSM to sign Fabric transactions.

We'll eventually link these up with Cactus Fabric connector.

@brioux You can have a look at this fabric sample https://github.com/hyperledger/fabric-samples/tree/main/asset-transfer-basic/application-typescript-hsm , I will also see how we can use HSM with cactus vault key chain.

Ok thanks @Zzocker I'll check on this today.

@Zzocker I have finished integrating HSM.  see my fork of blockchain-carbon-accounting. Waiting on @sichen1234 to finalized the pull request.
I don't see a peer programming call scheduled. We can discuss whenever you're free.

Can resist HSM integration later. Focusing on WebSocket based identity provider for client side fabric security


fix: not work with Nova v3.12.0

@ref https://github.com/laravel/nova/pull/1000

Uhm this will break for those not using the latest version of nova, can you update the composer.json to add a constrain?

Uhm this will break for those not using the latest version of nova, can you update the composer.json to add a constrain?

Okay.

Thanks


Check for git repository before git commands

When we are attempting to fetch the version info from the git repository, first check if we're actually in one, otherwise spurious errors messages get printed.

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


CI: Reference github-settings repository

Codecov Report

Merging #138 (efe6b63) into main (cec88fc) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head efe6b63 differs from pull request most recent head 7877b0d. Consider uploading reports for the commit 7877b0d to get more accurate results

@@           Coverage Diff           @@
##             main     #138   +/-   ##
=======================================
  Coverage   97.37%   97.37%
=======================================
  Files          17       17
  Lines        1297     1297
=======================================
  Hits         1263     1263
  Misses         34       34

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


Missing additional login return data from the Notion auth provider

Discussed in https://github.com/orgs/supabase/discussions/12278

Originally posted by madebyisaacr February  9, 2023
When using Notion as an auth provider, Notion returns a lot of additional information when a user signs in. From this data, access_token is available as supabase.auth.getSession().data.session.provider_token, but I can't find a way to retrieve any of the other return data.
Is it possible to access any of the data Notion returns in Supabase? Being able to use some of these properties like bot_id, workspace_name, workspace_icon would be very helpful for the app I'm making.
A screenshot from Notion developer docs showing the return information:

@saltcod Thanks for transferring this issue, do you think there's any solution or workaround for this?


Create new, empty repo to facilitate collaboration on the "notebook state" problem

Hi folks,
In yesterday's server meeting, I proposed creating a new repo to explore solutions to the issue raised here: Proposal: Restore Notebook execution progress when a browser page is reload
We've seen a lot of interest on this issue from people representing different organizations. I'd like to focus this energy to a single place on Github so we can easily collaborate. This work will likely be larger than a single PR and require some explorative work. For that reason, I'd like to focus this work in a separate repo.
I'll open a vote in our private council repo. @jupyter-server/jupyter-server-council
In the meantime, what should we call this repo if it gets created?

Pinging folks who've been involved in the conversations: @matthewwiese @skukhtichev and @parul100495

In the meantime, what should we call this repo if it gets created?

How about: jupyter-server/jupyter_message_replay ?

@Zsailer jupyter-server/jupyter_message_replay is succinct enough for me!

The name looks good to me as well.

/polls 'message_replay' 'kernel_playback' 'message_recovery'

The Server Team voted in favor of creating a new repo for this work 🚀! (8 Yes, 7 Abstain).
Let's create the repo during the meeting.

How about "serverside-notebook-state"? "message replay" is one possible solution, but not the only one.

@ivanov true. The problem is a bit broader than the notebook too—e.g. kernel state (say for a console, not a notebook document) needs restoration too.

@Zsailer Could you add a placeholder README to the jupyter-server/message_replay repo? GitHub won't let me fork it and open a PR with the extension cookiecutter template because the repository is empty

Thank you @blink1073!

For anyone following along, here's the link: https://github.com/jupyter-server/message_replay


Error: Connection to leader lost

Error: Connection to leader lost
at Multilevel._clearRequests (/var/www/videomail/staging/source/node_modules/level-party/node_modules/multileveldown/leveldown.js:122:38)
at /var/www/videomail/staging/source/node_modules/level-party/node_modules/multileveldown/leveldown.js:104:10
at f (/var/www/videomail/staging/source/node_modules/once/once.js:17:25)
at onclose (/var/www/videomail/staging/source/node_modules/level-party/node_modules/multileveldown/node_modules/end-of-stream/index.js:43:45)
at emitNone (events.js:72:20)
at emit (events.js:166:7)
at Encoder.destroy (/var/www/videomail/staging/source/node_modules/level-party/node_modules/multileveldown/node_modules/pbs/encoder.js:24:10)
at Duplexify._destroy (/var/www/videomail/staging/source/node_modules/level-party/node_modules/multileveldown/node_modules/duplexify/index.js:187:66)
at /var/www/videomail/staging/source/node_modules/level-party /node_modules/multileveldown/node_modules/duplexify/index.js:174:10
at doNTCallback0 (node.js:408:9)
at process._tickCallback (node.js:337:13)

Not sure what I can do here. Probably a bug in multileveldown?

Any change the error message Error: Connection to leader lost could be improved, mentioning which one leader got lost exactly?

Can you reproduce this error?
/m
On Tue 30 Jun 2015 at 10:44 Michael Heuberger<EMAIL_ADDRESS>wrote:

Any change the error message Error: Connection to leader lost could be
improved, mentioning which one leader got lost exactly?
—
Reply to this email directly or view it on GitHub
https://github.com/substack/level-party/issues/8#issuecomment-117058747.

That's difficult to reproduce. Both hosting parties are complex apps.
Any chance you could improve the error message and add a debug option for now?

Still happening here and really would like to see tips/hints how I can debug this best? cc @mafintosh

@binarykitchen Is this still an issue, or can it be closed?

Same problem.
When i close and reopen it, some times can not open without any error information.
And i found MANIFEST-xxxx file which record in CURRENT  is lost.
I think some thing relate to https://github.com/google/leveldb/issues/79
In the end, is use https://github.com/Level/leveldown#leveldownrepairlocation-callback method to fix the dir, then levelDB can be open again.
But i am sure some data were lost cause the method create a dir named lost.

@GeekBerry which version of level-party are you on?


Adding several publication ready figures [Figure 2, Supplementary Figs 2 and 3]

Sorry for the long PR - it generates all figures (main and supplementary) for the first results subsection. I also needed to calculate all pairwise correlations between cells in order to plot pairwise correlation density curves.
Main figure

Supplementary Figures

Please feel free to continue discussions in each thread, but I will merge for now!


can you provide pre-built images for main branch

Both gpt-neox 1.0 and 2.0 are based on torch 1.8. Can you provide pre-built images for main branch, which based on torch 1.13

We've updated our Dockerfile to be based on the NGC PyTorch container, which provides torch 2.3.0
Does this resolve your issue, or do you need 1.13 specifically?


Userid is coming as 0, 1, 2 etc

Hi Folks,
Thanks for creating this wonderful gem.
I am trying to use this gem and almost all my needs are working well.
However, I noticed that the user_id is coming as nil, 0, 1, 2, 3.... etc
See below:
> Impression.last
  Impression Load (1.6ms)  SELECT  "impressions".* FROM "impressions" ORDER BY
"impressions"."id" DESC LIMIT $1 /*application:Foo*/  [["LIMIT", 1]]
=> #<Impression id: 2256, impressionable_type: "EditablePage", impressionable_id: 39,
user_id: 5, controller_name: "blog_posts", action_name: "show", view_name: nil,
request_hash: "fdcb03fdfd...", ip_address: "1xx.xx.xx.76", session_hash: "293e851aec2260bec0b556cf68080e04",
message: "Getting foo blog post", referrer: "https://example.com/blog/?page=1",
params: {"slug"=>"foo"}, created_at: "2022-04-07 11:49:33", updated_at: "2022-04-07 11:49:33">

How I am adding
def show
  @blog_post = BlogPost.find_by(slug: params[:slug])
  impressionist(@blog_post, "Hitting<EMAIL_ADDRESS>  ...
end

Anything I am missing here?
After changing the migration to create ImpressionTable, I am getting following error:
PG::InvalidTextRepresentation: ERROR: invalid input syntax for type uuid: "0" :
INSERT INTO "impressions" ("impressionable_type", "impressionable_id", "controller_name",
"action_name", "request_hash", "ip_address", "session_hash", "message", "params",
"created_at", "updated_at") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11)
RETURNING "id" /*application:Foo,controller:blog_posts,action:show*/

Hey dont know if this is still helpful, as it seems for me you are working with uuids as primary ids.
I just changed in the migration table the user_id and the impressionable_id to strings like:
t.string :impressionable_id
t.string :user_id
that worked for me


React.DOM -> react-dom package

Hey @joshwnj, I'm upgrading react to v16 in x-team/auto and this is currently a blocker

@kasprownik we should also upgrade auto-ui to use React v16 in that case, right?


net/http: ReadRequest can stack overflow due to recursion with very large headers

http.ReadRequest can stack overflow due to recursion when given a request with a very large header (~8-10MB depending on the architecture). A http.Server which overrides the default max header of 1MB by setting Server.MaxHeaderBytes to a much larger value could also be vulnerable in the same way.
According to the new security policy (#44918), this will be fixed as a PUBLIC track issue.
Credit to Guido Vranken who reported the crash as part of the Ethereum 2.0 bounty program.
/cc @golang/security

@gopherbot please consider this for backport to 1.16.4 and 1.15.12, it's a security issue.

The x/net fix still needs to be pulled into the main Go repo as done in CL 314596, reopening for that (and adding release-blocker so it's not missed).

The x/net fix has been pulled into the main repo for Go 1.17 as part of CL 316251. Closing as fixed.


ERROR: Twiddle: fetch failed to get commit 29a0b6f234, please file an issue at https://github.com/Ward9250/Twiddle.jl/issues

In julia 0.5.2, I got the following when running Pkg.update()
INFO: Upgrading Twiddle: v0.3.1 => v0.4.0
INFO: Rolling back TexExtensions from v0.1.0 to v0.0.3
INFO: Rolling back StatsBase from v0.17.0 to v0.16.1
INFO: Rolling back SpecialFunctions from v0.2.0 to v0.1.1
INFO: Rolling back install of ScikitLearn
INFO: Rolling back Requests from v0.5.0 to v0.4.1
INFO: Rolling back PyCall from v1.14.0 to v1.13.0
INFO: Rolling back install of Parameters
INFO: Rolling back PairwiseListMatrices from v0.5.1 to v0.4.0
INFO: Rolling back install of NamedArrays
INFO: Rolling back NaNMath from v0.2.6 to v0.2.5
INFO: Rolling back JSON from v0.13.0 to v0.12.0
INFO: Rolling back IntervalSets from v0.1.1 to v0.0.5
INFO: Rolling back HttpParser from v0.3.0 to v0.2.0
INFO: Rolling back FileIO from v0.5.1 to v0.4.1
INFO: Rolling back FTPClient from v0.2.1 to v0.1.1
INFO: Rolling back EzXML from v0.4.4 to v0.4.3
INFO: Rolling back DataStructures from v0.6.0 to v0.5.3
INFO: Rolling back DataFramesMeta from v0.2.0 to v0.1.3
INFO: Rolling back Colors from v0.7.4 to v0.7.3
INFO: Rolling back ColorTypes from v0.5.2 to v0.5.1
INFO: Rolling back BioSymbols from v1.1.1 to v1.1.0
INFO: Rolling back BioSequences from v0.6.3 to v0.6.2
INFO: Rolling back BioCore from v1.2.0 to v1.1.0
INFO: Rolling back AxisArrays from v0.1.4 to v0.1.3
INFO: Rolling back Automa from v0.3.0 to v0.2.4
ERROR: Twiddle: fetch failed to get commit 29a0b6f234, please file an issue at https://github.com/Ward9250/Twiddle.jl/issues
 in edit(::Function, ::String, ::Base.Pkg.Types.VersionSet, ::Vararg{Base.Pkg.Types.VersionSet,N}) at ./pkg/entry.jl:30
 in (::Base.Pkg.Entry.##2#5{String,Base.Pkg.Types.VersionSet})() at ./task.jl:360
 in macro expansion at ./task.jl:327 [inlined]
 in add(::String, ::Base.Pkg.Types.VersionSet) at ./pkg/entry.jl:51
 in (::Base.Pkg.Dir.##2#3{Array{Any,1},Base.Pkg.Entry.#add,Tuple{String}})() at ./pkg/dir.jl:31
 in cd(::Base.Pkg.Dir.##2#3{Array{Any,1},Base.Pkg.Entry.#add,Tuple{String}}, ::String) at ./file.jl:59
 in add(::String) at ./pkg/pkg.jl:100
 in eval_user_input(::Any, ::Base.REPL.REPLBackend) at ./REPL.jl:64
 in macro expansion at ./REPL.jl:95 [inlined]
 in (::Base.REPL.##3#4{Base.REPL.REPLBackend})() at ./event.jl:68

Hmmm that's very odd, what happens if you Pkg.rm("Twiddle"); Pkg.add("Twiddle") ?

julia> Pkg.rm("Twiddle")
INFO: Removing Twiddle (unregistered)

julia> Pkg.add("Twiddle")
INFO: Upgrading Automa: v0.2.4 => v0.3.0
INFO: Upgrading AxisArrays: v0.1.3 => v0.1.4
INFO: Upgrading BioCore: v1.1.0 => v1.2.0
INFO: Upgrading BioSequences: v0.6.2 => v0.6.3
INFO: Upgrading BioSymbols: v1.1.0 => v1.1.1
INFO: Upgrading ColorTypes: v0.5.1 => v0.5.2
INFO: Upgrading Colors: v0.7.3 => v0.7.4
INFO: Upgrading DataFramesMeta: v0.1.3 => v0.2.0
INFO: Upgrading DataStructures: v0.5.3 => v0.6.0
INFO: Upgrading EzXML: v0.4.3 => v0.4.4
INFO: Upgrading FTPClient: v0.1.1 => v0.2.1
INFO: Upgrading FileIO: v0.4.1 => v0.5.1
INFO: Upgrading HttpParser: v0.2.0 => v0.3.0
INFO: Upgrading IntervalSets: v0.0.5 => v0.1.1
INFO: Upgrading JSON: v0.12.0 => v0.13.0
INFO: Upgrading NaNMath: v0.2.5 => v0.2.6
INFO: Installing NamedArrays v0.6.1
INFO: Upgrading PairwiseListMatrices: v0.4.0 => v0.5.1
INFO: Upgrading PyCall: v1.13.0 => v1.14.0
INFO: Upgrading Requests: v0.4.1 => v0.5.0
INFO: Upgrading SpecialFunctions: v0.1.1 => v0.2.0
INFO: Upgrading StatsBase: v0.16.1 => v0.17.0
INFO: Upgrading TexExtensions: v0.0.3 => v0.1.0
INFO: Installing Twiddle v0.4.0
INFO: Rolling back TexExtensions from v0.1.0 to v0.0.3
INFO: Rolling back StatsBase from v0.17.0 to v0.16.1
INFO: Rolling back SpecialFunctions from v0.2.0 to v0.1.1
INFO: Rolling back Requests from v0.5.0 to v0.4.1
INFO: Rolling back PyCall from v1.14.0 to v1.13.0
INFO: Rolling back PairwiseListMatrices from v0.5.1 to v0.4.0
INFO: Rolling back install of NamedArrays
INFO: Rolling back NaNMath from v0.2.6 to v0.2.5
INFO: Rolling back JSON from v0.13.0 to v0.12.0
INFO: Rolling back IntervalSets from v0.1.1 to v0.0.5
INFO: Rolling back HttpParser from v0.3.0 to v0.2.0
INFO: Rolling back FileIO from v0.5.1 to v0.4.1
INFO: Rolling back FTPClient from v0.2.1 to v0.1.1
INFO: Rolling back EzXML from v0.4.4 to v0.4.3
INFO: Rolling back DataStructures from v0.6.0 to v0.5.3
INFO: Rolling back DataFramesMeta from v0.2.0 to v0.1.3
INFO: Rolling back Colors from v0.7.4 to v0.7.3
INFO: Rolling back ColorTypes from v0.5.2 to v0.5.1
INFO: Rolling back BioSymbols from v1.1.1 to v1.1.0
INFO: Rolling back BioSequences from v0.6.3 to v0.6.2
INFO: Rolling back BioCore from v1.2.0 to v1.1.0
INFO: Rolling back AxisArrays from v0.1.4 to v0.1.3
INFO: Rolling back Automa from v0.3.0 to v0.2.4
ERROR: Twiddle: fetch failed to get commit 29a0b6f234, please file an issue at https://github.com/Ward9250/Twiddle.jl/issues
 in edit(::Function, ::String, ::Base.Pkg.Types.VersionSet, ::Vararg{Base.Pkg.Types.VersionSet,N}) at ./pkg/entry.jl:30
 in (::Base.Pkg.Entry.##2#5{String,Base.Pkg.Types.VersionSet})() at ./task.jl:360
 in macro expansion at ./task.jl:327 [inlined]
 in add(::String, ::Base.Pkg.Types.VersionSet) at ./pkg/entry.jl:51
 in (::Base.Pkg.Dir.##2#3{Array{Any,1},Base.Pkg.Entry.#add,Tuple{String}})() at ./pkg/dir.jl:31
 in cd(::Base.Pkg.Dir.##2#3{Array{Any,1},Base.Pkg.Entry.#add,Tuple{String}}, ::String) at ./file.jl:59
 in add(::String) at ./pkg/pkg.jl:100
 in eval_user_input(::Any, ::Base.REPL.REPLBackend) at ./REPL.jl:64
 in macro expansion at ./REPL.jl:95 [inlined]
 in (::Base.REPL.##3#4{Base.REPL.REPLBackend})() at ./event.jl:68

julia> Pkg.rm("Twiddle")
INFO: Removing Twiddle (unregistered)

julia> Pkg.rm("Twiddle")
INFO: Package Twiddle is not installed

julia> Pkg.add("Twiddle")
INFO: Installing Twiddle v0.4.0
INFO: Package database updated

It installs fine for me. I also don't know why your Pkg is upgrading a load of packages that have nothing to do with Twiddle during the install, only then to roll them back! Commit 29a0b6f234 is the 0.4 release commit, on both Github and METADATA.jl.
Being unable to reproduce the issue, I don't really know what to suggest other than perhaps blasting your julia package library location with rm in the shell and doing Pkg.init in julia again, and install your packages afresh.

Remove  ~/.julia folder and install all again works! Strange!
Thanks


add CodeRoad

Name of the extension you are adding
CodeRoad
Why do you think this extension is awesome?
Uses VSCode in a novel way to play coding tutorials like a game.
Make sure that:

[X] Screenshot/GIF included (to demonstrate the plugin functionality)

[X] ToC updated

Any idea why the build failed?
LInks seem similar to other existing projects.
Some 404s, but unrelated to this PR.


Project can't be build on macos

The project can't be build on macos. Is it because a native linux os is required ? Is there a workaround ?
make
git clone --depth 1 https://github.com/opencontainers/runc.git "/Users/dabou/Code/go-workspace/src/github.com/genuinetools/img/cross/src/github.com/opencontainers/runc"
Cloning into '/Users/dabou/Code/go-workspace/src/github.com/genuinetools/img/cross/src/github.com/opencontainers/runc'...
remote: Counting objects: 728, done.
remote: Compressing objects: 100% (619/619), done.
remote: Total 728 (delta 137), reused 367 (delta 82), pack-reused 0
Receiving objects: 100% (728/728), 1.18 MiB | 1.76 MiB/s, done.
Resolving deltas: 100% (137/137), done.
GOPATH=/Users/dabou/Code/go-workspace/src/github.com/genuinetools/img/cross /Applications/Xcode.app/Contents/Developer/usr/bin/make -C "/Users/dabou/Code/go-workspace/src/github.com/genuinetools/img/cross/src/github.com/opencontainers/runc" static BUILDTAGS="seccomp apparmor"
CGO_ENABLED=1 go build  -tags "seccomp apparmor netgo osusergo cgo static_build" -installsuffix netgo -ldflags "-w -extldflags -static -X main.gitCommit="21ac0862f2c695f7ecb55346401932a9ad8cc8d6" -X main.version=1.0.0-rc5+dev " -o runc .
# github.com/opencontainers/runc/libcontainer/nsenter
nsexec.c:3:10: fatal error: 'endian.h' file not found
# github.com/opencontainers/runc/libcontainer/configs
libcontainer/configs/config.go:128:11: undefined: Cgroup
# github.com/opencontainers/runc/libcontainer/utils
libcontainer/utils/utils_unix.go:39:62: undefined: unix.SOCK_CLOEXEC
make[1]: *** [static] Error 2
make: *** [/Users/dabou/Code/go-workspace/src/github.com/genuinetools/img/cross/src/github.com/opencontainers/runc/runc] Error 2

Nope it says this in the readme it's a Linux binary just like you can't run lxc on mac


Current state of catcher_2

Hello,
This is just a quick question about the fork from the original catcher package.
What was the motivation that you forked catcher && Are you planning to maintain this package for a extended time ?
Greeting.

Thank you for raising this question. As a developer who actively uses catcher2, I'd like to share my understanding of why someone would fork the original cacher package and their plans for maintaining it.
The original catcher package had not been maintained for a long time, which presented challenges for many developers like myself, especially regarding essential updates for security and compatibility. The advent of catcher2 has addressed these issues, providing us with a more stable and secure solution.
The motivation behind forking and creating catcher2 was to ensure ongoing support and improvements for this tool, making sure it meets both current and future development needs. Judging by their active updates and engagement, I believe the maintainers are committed to the long-term upkeep of this project.
Moreover, as part of the community, it’s evident that the maintainers encourage feedback and contributions. This not only improves the quality of the package but also strengthens community bonds. I am personally very grateful for their efforts and believe that, over time, catcher2 will continue to be enhanced and refined.
I hope this answer helps you understand the motivation behind the fork and the plans for future maintenance. If you have any suggestions or thoughts about catcher2, I’m sure the maintainers would warmly welcome your participation and feedback.

Hello,
I forked it because upstream was not updated for quite a while and there were a few obvious bugs.
Most prominently, it was incompatible with Flutter 3.13 and also still used deprecated zones instead of the new onError callbacks.
All these things have been fixed in my fork.

Ah, another response in the same minute :)
Also, thank you for the kind words! Yes, as long as I am still around, I will try my best to keep updating it to ensure compatibility with the newest updates and also standards.
I welcome any feedback, suggestions, bug reports and - of course - PRs!
Also, even though I am pretty sure everything still works correctly, I don't own any Apple devices and hence cannot test new changes on them.
Feedback or even testers and additional maintainers in that regard would be greatly appreciated.
However, as you might have noticed, catcher_2 works without any native code as of now.
Because of this, I am very positive that compatibility will be ensured to a high degree. But one can never be sure...
But as already said - thank you @calcitem for your kind words! :)
I will close this issue to keep my issue list clean. But if you have any further questions, I will be pleased to answer them to my very best of my abilities.


Bug Report/Question: FPS drops to ~30 when entering

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
Windows 10 x64
What version of the game are you using? Look in the bottom left corner of the main menu.
KE 1.6.2, manually built using source from the release page
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Just enter the Options Menu
Please describe your issue. Provide extensive detail and images if possible.
I just downloaded KE 1.6.2 from the GitHub release page and built it from scratch and it runs fine, but as soon as I enter the options menu my FPS drops to ~30FPS, is this a known bug or something or is my PC weird?

get a better pc


Error -  No matching export in "node_modules/solid-js/web/dist/dev.js" for import "isDev"

Getting the following error. Followed instruction to install the extension, npm package and added to vite plugins.
✘ [ERROR] No matching export in "node_modules/solid-js/web/dist/dev.js" for import "isDev"
node_modules/@solid-primitives/utils/dist/index.js:3:9:
  3 │ export { isDev, isServer } from 'solid-js/web';
    ╵          ~~~~~

commenting out the plugin in vite.config removes the error and project compiles.
Many thanks for help!

You probably need to update solid-js version. isDev export was added in 1.6.12 I think.

Many thanks! it works now 🙏


Node-API lost coloring/formatting of error messages

https://github.com/prisma/prisma/pull/8286/checks?check_run_id=3080909038 vs https://github.com/prisma/prisma/pull/8286/checks?check_run_id=3080909177

I have tried to reproduce this and could not.