Exported external package typings file 'redux-mock-store/index.d.ts' is not a module. Please contact the package author to update the package definition

I have downloaded redux-mock-store and it include a definition, when you attempt to use it provides the following error:
Exported external package typings file 'C:/Test/node_modules/redux-mock-store/index.d.ts' is not a module. Please contact the package author to update the package definition
We have implemented a manual typing for redux-mock-store, that worked fine for us:
/// <reference path="../../typings/globals/redux/index.d.ts"/>

declare module "redux-mock-store" {
    interface MockStore extends Redux.Store {
        getState(): any;
        getActions(): Array<any>;
        dispatch(action: any): any;
        clearActions(): void;
        subscribe(): any;
    }

    function configureStore(...args: any[]) : (...args: any[]) => MockStore;
    export = configureStore;
}

This index.d.ts is providing conflicts (even excluding node_modules folders), in our case we are manually deleting that file whenever we install the package.Could it be a good idea to remove the d.ts from redux-mock-store, review it and an updated on to the typings repository?

. @dylanparry implemented the TypeScript part of redux-mock-store, can you check with him on how to fix it?
I have never used TS in the past.

Hi. It looks like the API for Redux Mock Store has changed considerably since I wrote the index.d.ts file. For now it's probably best to either replace the file with the code that @brauliodiez has included above, or delete the file reference from the package.json until it can be updated correctly.

Same issue here, the typings file is broken.

May I make a fork and ask for pull request?

@brauliodiez Feel free to make a PR 👍
@dylanparry Thank you for the feedback

I have given a try and there is something wrong, if I place the file outside node_modules (as a typing) works fine, but inside node_modules I get the same error again, I will take look.

@brauliodiez Did you find out what the problem is there? Facing the same issue.

So after a bit of searching I came across this which seems to indicate we shouldn't be declaring a top level module for an external definition.
Bear in mind I'm pretty new to a lot of this so I may be missing something (or many things).
Changing to the following works for me:
`import {Store} from 'redux';
interface MockStore extends Store {
getState():any;
getActions():Array;
dispatch(action:any):any;
clearActions():void;
subscribe():any;
}
declare function configureStore(...args:any[]):(...args:any[]) => MockStore;
export = configureStore;`
i.e. the top level module has been removed and the function is a declare because "'declare' [is] now required for top level non-interface declarations " - Typescript - Known breaking changes between 0.8 and 0.9
Let me know what you think, I can create a PR if it's needed (and this is correct!).

You are right, we have checked and you version is working like a charm. @dylanparry , @arnaudbenard should @asgarddesigns raise a Pull Request includin the fix for the breaking change?

Anybody for this PR ?

Is everyone happy with this change?

Yes. Seems to work fine, so go with it.
On Wed, Jun 15, 2016 at 2:52 PM +0100, "Arnaud Bénard"<EMAIL_ADDRESS>wrote:
Is everyone happy with this change?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Done! Thanks everyone for the contribution 👍


[MRG] FIX Brain.remove labels()

Remove the hemi parameter, which was previously unused (even though it forced the user to set it). Labels are not stored by hemisphere, but by their name.

Coverage increased (+0.4%) to 78.362% when pulling 6affeab8a1f80c58b36bc1fbe7c6b3c4825265e7 on christianbrodbeck:fix/remove_labels into 86481141fc375086b950c75d419290d75e56155c on nipy:master.

Coverage increased (+0.4%) to 78.362% when pulling 6affeab8a1f80c58b36bc1fbe7c6b3c4825265e7 on christianbrodbeck:fix/remove_labels into 86481141fc375086b950c75d419290d75e56155c on nipy:master.

LGTM. @mwaskom can you look?

Code looks good to me. Are we still ignoring AppVeyor failures?

It seems unrelated


Trouble with the roomhandler when using ADDSERVER

Getting this error message when i work with the "ADDSERVER" command, adding a tls irc server.
heisenbridge          | Heisenbridge v1.5.0
heisenbridge          | Homeserver is publicly available at https://grimneko.de
heisenbridge          | ERROR:root:Ignoring exception from room handler. This should be fixed.
heisenbridge          | Traceback (most recent call last):
heisenbridge          |   File "/opt/heisenbridge/heisenbridge/main.py", line 150, in _on_mx_event
heisenbridge          |     await room.on_mx_event(event)
heisenbridge          |   File "/opt/heisenbridge/heisenbridge/room.py", line 85, in on_mx_event
heisenbridge          |     await handler(event)
heisenbridge          |   File "/opt/heisenbridge/heisenbridge/control_room.py", line 202, in on_mx_message
heisenbridge          |     await self.commands.trigger(command, tail)
heisenbridge          |   File "/opt/heisenbridge/heisenbridge/command_parse.py", line 95, in trigger
heisenbridge          |     await self.trigger_args(args, tail, allowed, forward)
heisenbridge          |   File "/opt/heisenbridge/heisenbridge/command_parse.py", line 79, in trigger_args
heisenbridge          |     await func(cmd_args)
heisenbridge          |   File "/opt/heisenbridge/heisenbridge/control_room.py", line 296, in cmd_servers
heisenbridge          |     proxy = f" through {server['proxy']}" if "proxy" in server and len(server["proxy"]) > 0 else ""
heisenbridge          | TypeError: object of type 'NoneType' has no len()

Indeed, the SERVERS command was broken for new servers since 1.4.0, fixed.
Fixed and thanks for reporting!


IPv6 zeroconf/Link-Local "suboptimal" in OOB config for DSR and anti lock out

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
The IPv6 Link-Local on LAN is not present when acquiring a prefix from WAN fails. Even though LAN is set to "Track Interface" and WAN has a valid IPv6 address (but somehow no prefix).
Zeroconf should always be initialized (unless disabled manually).
Also, the fe80::%iface addresses are missing from the firewall zones which also causes issues with zeroconf and DSR. Esp. because this prevents the web interface from being reachable via LL and unbound config defaulting to "Do not register IPv6 Link-Local addresses: false"
Additionally to provide a better user experience in DSR scenarios and lockout prevention AVAHI could be shipped and preconfigured to announce the web interface service to LAN and allow to find the opnsense again after missconfiguration. And regarding IPv4 it should be considered to always have an RFC 3927 present (as other routers like AVM Fritz!Box do) for the same reason (keeping an IPv4-LL even though a DHCPv4 one is configured is an optional "MAY" within RFC 3927 for accepting new connections and technically a "MUST NOT alter [remove]" for deconfiguring it once DHCP is present that OPNsense currently does not implement).
Furthermore OPNsense currently also doesn't properly handle IPv4-LL clients, as it should accept IPv4-LL source addresses with it's routable IPv4 as destination, as long as it's on the same link. Technically we don't need an IPv4-LL address ourselves for this, but having multiple addresses on the interface looks like a simpler and "cleaner" implementation than the implicit (also currently within OPNsense not working) behavior of section 3.3 from RFC 3927. Also, OPNsense doesn't join the <IP_ADDRESS> all routers multicast group nor reply or handle <IP_ADDRESS> (IGMPv3), but IPv4 is legacy anyway, so providing that as well as fixing that spam within the firewall log is probably irrelevant by now.
(Note: The mentioned AVM Fritz!Box is however ignoring the "pseudo-random number generation algorithm MUST be chosen" and always uses <IP_ADDRESS>)
To Reproduce
Steps to reproduce the behavior:

Boot iso (to get clean OOBE for reproducibility reasons)
Configure WAN and LAN interface (my testing instance has LAN vlan30, WAN vlan10)
Now a router on WAN should provide a prefix, but because of the default of "Override MTU: true" on WAN it didn't get one.
IPv6 configuration of LAN is skipped entirely, not even the Link-Local is initialized (see screenshot)

Expected behavior
Zeroconf should always be present on the interface, especially if IP configuration doesn't fully succeed.
Describe alternatives you considered
To not use zeroconf and to not rely on it being present for DSR.
Screenshots

Environment
OPNsense 23.7.4-amd64
FreeBSD 13.2-RELEASE-p3
OpenSSL 1.1.1v 1 Aug 2023
AMD Ryzen 7 3800X 8-Core Processor (1 cores, 1 threads)

Hi, I don’t fully understand. Could you back up your observations with ifconfig output to compare what is there and what is not?

These are quite a few requests for one issue, but one of them has indeed been on my personal "should address at some point" list for a long time: Track6 LAN interfaces missing IPv6 link-local addresses when the WAN is down.
@fichtner: When the WAN is down (no prefix available), track6 LAN interfaces obviously have no IPv6 GUA. But they also don't have a link-local address, which is unexpected. Worst case, the WAN being down could result in no access to the OPNsense Web GUI at all, because the LAN interfaces have no addresses.
There are workarounds (IP aliases), but I agree that every IPv6-enabled interface should always have a link-local address, unconditionally.

Exactly what @maurice-w says. The rest of this ticket is basically just to elaborate why having LL v6 is important and what we can/could do with it. I intended for the rest to be more of an elaboration of why it is important and how it fits into a bigger picture of "DSR and user experience".
And that is obv. more complex as it isn't "just one screw", but a bunch of screws that make the car...

I’ve seen the claim, but I’m unsure what’s stripping the LAN link-local. I don’t think it’s core code, but I could be wrong.
on other topics it helps to avoid or explain abbreviations to prevent misunderstandings or outright question marks.
cheers,
Franco

So during googling I stumbled upon this... https://forum.opnsense.org/index.php?topic=28030.msg137105#msg137105 ;)
I have a VM setup here that doesn't have IPv6 but tries to init it as per default configuration so I could observe this now. ifdisabled seems to prevent auto_linklocal from working. This changes when you add any IPv6 address. Looking at the code this 02b6085 should help, but also indicates that this used to be different before FreeBSD 13.
# opnsense-patch 02b6085

In any case thanks for the report!
Cheers,
Franco

Just wanted to confirm that this works for me. A track6 LAN interface now has a link-local address even if the WAN is down. Thanks @fichtner!


chore(server/conn): backport max_pending_accept_reset_streams()

NB: this commit is based on the 0.14.x release series.
the server::conn::http2 submodule provides types that are conditionally compiled when the backports feature is active, to facilitate upgrading to the 1.x release.
i've been working on upgrading the
linkerd2-proxy project to use hyper 1.0, but encountered a pertinent gap in Builder<E>'s interface when setting the backports and deprecated features.
this adds a max_pending_accept_reset_streams(..) method (added in #3201) to this builder, so that 0.14.x users relying on this functionality can prepare to upgrade to hyper 1.x safely.
this is effectively a backport of #3507, which restored this interface to the 1.0 release.
for more information, see:

https://github.com/hyperium/hyper/pull/3201
https://github.com/hyperium/hyper/pull/3507
https://github.com/hyperium/hyper/issues/3461
https://hyper.rs/guides/1/upgrading/

Submitted #3797 to fix that MSRV job.

Submitted #3797 to fix that MSRV job.

thank you! i'll rebase now


fix: typos in es_LA

fix: typos in es_LA

Hi! I appreciate your translation updates.
May you please add yourself in the Contributors table in the README.md?
Thanks!


Ther 22 flask application

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added
[x] Docs have been added / updated

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

merge docker-compose-flask-db-app in main

Please edit PR template.


NIFI-7743 Document Empty all queues option for Process Groups

Also:
-Edited "Configuring a Process Group" and related sections
-Updated screenshots as needed

+1 LGTM, did a full build and verified the docs were updated and look good. Thanks for the improvement! Merging to main


RPC Endpoint POC

Related to findings in #39 provide a POC that lifts smart constructors as RPC endpoints and allows some degree of composition.

 Initially we are gonna try the https://scalapb.github.io/grpc.html integration and see if the generated code matches and it's in the spirit of what we are trying to achieve with Freestyle. Scalapb already generates Server, clients and model definitions derived from proto buffers schemas. Proto buffers is one of the leading impl for client server RPC style communication and it's flexible in terms of versioning and lightweight payloads. Additionally ScalaPB supports Spark SQL which will open the door for sharing some of the concepts and infrastructure in the Spark module as well. This is an uber issue and hsould be broken down in smaller task to conduct the POC.

I'm interested in taking a stab at this one, but I will need time to get familiar with freestyle first.

I'd like to schedule some time for us to go over Freestyle and get a better idea of what you were thinking for this. I have some of my own ideas, and a few concerns on how to automate supporting gRPC (due to the nature of how ScalaPB works).

let's talk later today or next week when we are both available and I'll walk you through what we have so far

Superseded by https://github.com/frees-io/freestyle-rpc/issues/1


Any particular reason to spread denominators into Matrix A B and G?

I see in your README.md, the element in the matrix you give contains denominator.
For example in F(6x6,3x3) :
G =
⎡ 1      0     0  ⎤
⎢                    ⎥
⎢-2/9  -2/9   -2/9⎥
....
A, G and B matrix they all have denominators?
Is there any reason to make one matrix large and another matrix small?
For example, let's say the first row of G is G1 and first row of BT is BT1
Since they do pairwise product after multiplying a vector, we can make
G1' = G1 / x,  BT1' = BT1 * x
Changing row by x times large/smalleer doesn't affect the result.
So what's the idea behind the way you assign denominators to the three matrices?
Is that for precision?

The laplacian interpolation, which is basically used to compute the "inverse" matrix B given matrices A and G, creates some divisions. In signal processing, normally those divisions are moved to matrix G, which represents the filters, because filters are usually constant, and therefore the extra arithmetic is absorbed by the constants.
If the interpolation points are fractions, then matrix A will also will have these fractions (and powers thereof: A is a Vandermonde matrix of the interpolation points). We usually don't use fractional interpolation points until we exhaust the simple values (0, 1, -1, 2, -2), so the fractions in matrix A happen when we use (1/2, -1/2) for F(6,3) or F(4,5).
Anyway winCNN does not do anything smart about moving these fractions around. You might be able to increase numeric accuracy by scaling differently.


3.30.0: Adds new SDK versions and contract files

Pull Request Template
Description
This bumps the SDK version from 3.29.0 to 3.30.0. Please see the below changes in the GA public contract.

Also highlighted below are the preview contract changes.

For TTL expired documents what's expected on ChangeFeedMetadata? (ex: OperationType will be delete and TTLExpire=true). Please cover it code documentaion.
TimeToLiveExpired: How about 'IsTimeToLiveExpired'?

For TTL expired documents what's expected on ChangeFeedMetadata? (ex: OperationType will be delete and TTLExpire=true). Please cover it code documentaion.
TimeToLiveExpired: How about 'IsTimeToLiveExpired'?

@kirankumarkolli
AFAIK, yes, if the OperationType is 'deleted' then the TimeToLiveExpired will be 'true'.
Also, are you suggesting a refactor to change TimeToLiveExpired to 'IsTimeToLiveExpired'?

I have updated the contract to reflect the correct naming convention.


Make graph line thickness relative to the width of the according graph edge

Currently we have our graph lines thickness fixed by a number. Instead, we want the graph lines to have the thickness according to the underlying line width in the image. Every edge will have its own width.

Is it desirable to let the user decide which color the lines and the graph vertices will have? If so we could add this option in a menu item edit or view since those are changes a user wont do frequently.
Also we could add a slider which lets the user increase/decrease the vertices thickness.

Wait a sec. What does that even mean "relative to the overlapping graph lines"? What we really want is the following: NEFI measures the width of the structures it sees in the original input image. This is a number in pixel and stored as an edge attribute called "width". When it comes to drawing the edge, we want to grab this number to set the width of the drawing. When the graph is drawn onto of the original image, the edges coincide (in a perfect world).

When it comes to choosing the color, node size, etc, we need to ask ourselves whether we add value by doing so. If you ask me, the color does not matter. What matters is that the colors of the edges and the nodes are easily distinguishable for colorblind people. Similarly, i dont really care about the node size right now, but I can imagine that this could be a feature desirable in the future.

Ok good that you told us. We will make it so.

We also compute the variance. Maybe it's nice to also visualize this, perhaps via blurring?

How exactly would you show the variance? If i understood correct we need to show the same amount of blur along the complete edge. Then the edge would still look uniform.

If the standard deviation is x pixels and the width is y pixels, apply gaussian blur with radius x to the line of thickness y. Or something like that to give some visual indication of measurement error or whatever causes the variance.

Ok, we will first implement it according to Michael's sprecification.  By checking out the two different branches you can then later compare what type of edge rendering is better (we could possibly add a menu option two switch between those).

I changed the implementation to satisfy Michael's specification.

If the standard deviation is x pixels and the width is y pixels, apply gaussian blur with radius x to the line of thickness y. Or something like that to give some visual indication of measurement error or whatever causes the variance. Sharp edges have little variance, blurry edges don't have a reliable width.

Gaussian Blur always apllies to the whole image using a kernel size. So instead i simply interpolate the color transparency based on the edge's standard deviation:
def draw_edges(img, graph, col=(0, 0, 255)):
    """
    Draw network edges on the input image.

    Args:
        | *img* : Input image where edges are drawn
        | *graph* : Input graph containing the edges
    Kwargs:
        | *col* : colour for drawing

    Returns:
        Input image img with nodes drawn into it
    """
    edg_img = numpy.copy(img)
    for (x1, y1), (x2, y2) in graph.edges_iter():
        start = (y1, x1)
        end = (y2, x2)
        diam = graph[(x1, y1)][(x2, y2)]['width']
        # variance value computed during graph detection
        width_var = graph[(x1, y1)][(x2, y2)]['width_var']
        # compute edges standard deviation by applying sqrt(var(edge))
        standard_dev = numpy.sqrt(width_var)
        if diam == -1: diam = 2
        diam = int(round(diam))
        if diam > 255:
            print('Warning: edge diameter too large for display. Diameter has been reset.')
            diam = 255
        # access color triple
        (b, g, r) = col
        # set opacity based by standard deviation and some selected divider
        opacity = (standard_dev % 10) / 10
        # opacity must be in [0, 1]
        if opacity > 1.0:
            opacity = 1
        # set overlay in this case white
        overlay = (0, 0 ,0)
        # compute target color based on the transparency formula
        target_col = (b == 0 if 0 else (opacity * 255 + (1 - opacity) * b),
                      (g == 0 if 0 else opacity * 255 + (1 - opacity) * g),
                      (r == 0 if 0 else opacity * 255 + (1 - opacity) * r))
        # draw the line
        cv2.line(edg_img, start, end, target_col, diam)

    edg_img = cv2.addWeighted(img, 0.5, edg_img, 0.5, 0)
    return edg_img

I use the transparency formula from here. Since the opacity is in [0, 1] we need to calculate the modulo of from the standard deviation and 10. Now we get a number x  in [0, 10]. Dividing x by 10 gives us the opacity value between [0, 1]. This algorithm works based on the assumption that the standard deviation of the edges are around the same value.
Another option would be to let the user specify its custom divider value to bring the standard deviation into [0, 1]. In this case: opacity := standard_dev / DIVIDER
I would like to make the "blurry edges" feature available for the user by clicking the a checkbox "blurry edges" in the view menu.
You can try it out by checking out the edge_blur branch.

Note: i think we could make the calculation much more efficient by just using the variance instead of the standard deviation. We are just interested in the differences of the standard deviation's so the square from the variance shouldn't be much of a deal because of the modulo 10 / div 10.

You could draw the edge on a bitmap, blur the bitmap and overlay in on the image.
I agree about the variance vs the standard dev. In any case, I wouldn't use numpy.sqrt where math.sqrt will work. Have you tried extracting all variances and applying numpy.sqrt to the array of variances? It's an array method after all. But allocating the array probably eats any performance to be gained there.
edges_iter can return the edge data. That saves some dictionary lookups.
there is inconsistent bracing in the target_col computation. You could also do some common subexpression elimination there.
how can diam be -1 and why not write diam = max(diam,2)

(Just my 5 cents once again) Profile every file you want to optimize with line profiler to see what exactly eats up the cpu.
Here is a a quick howto:

sudo pip install line_profiler
open the algorithm file and insert "@profile" above the function definition you want to test
kernprof -l script_to_profile.py
process any big image
python3 -m line_profiler script_to_profile.py.lprof


Add rebase check and fix for new whitelist

Will need to merge https://github.com/ambiata/mafia/pull/148 first, but after that this should be good.
! @erikd-ambiata @charleso

👍


Note breaking errors with extraneous headers on caption upload

Which Cloudflare product does this pertain to?
Stream
Existing documentation URL(s)
https://developers.cloudflare.com/stream/uploading-videos/adding-captions/
Section that requires update
Add or Modify a Caption
What needs to change?
The curl example provided only calls out the explicit authorization header, but curl passes implicit headers with the -F option. Including those headers explicitly when using other methods than curl to attempt to upload captions (for example the requests library in python) will, at best, throw an HTTP 400 and an error code 10004 Decoding Error in the response. Code 10004 is not particularly specific, nor does searching for it turn up many helpful support results for captions specifically (most results from the CF forums or elsewhere are in relation to video uploads).
How should it change?
Clarifying that the authorization headers are the only headers that should be passed, regardless of any implicit headers that curl sends and/or providing resources for the CF error codes that users might encounter would reduce frustration.
Additional information
No response

Hey @HBBrenum! Thank you for the patience as I was just able to find time to respond. I work on the Stream team and trying to understand your report better to either fix our API or make sure we update our docs to clarify what we might have miscommunicated.
When I make a request to the captions API with extra headers, the API works as expected. Below I've added coconut: mango as a extra header (note that I've edited the verbose output from cURL for clarity but retained every header sent and received).
curl -X PUT 'https://api.cloudflare.com/client/v4/accounts/a67e14daa5f8dceeb91fe5449ba496eb/stream/644822f93dcddab3e9441587d184ca2f/captions/tr' -H 'Authorization:Bearer $KEY' -H 'coconut: mango' -F<EMAIL_ADDRESS>-v

> PUT /client/v4/accounts/a67e14daa5f8dceeb91fe5449ba496eb/stream/644822f93dcddab3e9441587d184ca2f/captions/tr HTTP/2
> Host: api.cloudflare.com
> user-agent: curl/7.81.0
> accept: */*
> authorization:Bearer $KEY
> coconut: mango
> content-length: 341
> content-type: multipart/form-data; boundary=------------------------79e17072d3916653
>

< HTTP/2 200
< date: Fri, 01 Jul 2022 04:57:25 GMT
< content-type: application/json; charset=UTF-8
< cf-ray: 723c8f88cb4b97f3-SJC
< set-cookie: __cflb=0H28vgHxwvgAQtjUGU4vq74ZFe3sNVUZaMyNVGZn96V; SameSite=Lax; path=/; expires=Fri, 01-Jul-22 07:27:26 GMT; HttpOnly
< vary: Accept-Encoding
< cf-cache-status: DYNAMIC
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< x-envoy-upstream-service-time: 357
< set-cookie: __cfruid=ea7468a07291429f358ddc25c2555d0788f84542-1656651445; path=/; domain=.api.cloudflare.com; HttpOnly; Secure; SameSite=None
< server: cloudflare
<
{
  "result": {
    "language": "tr",
    "label": "Türkçe"
  },
  "success": true,
  "errors": [],
  "messages": []
}

As you can see, adding the header coconut is fine.
However, if I try to set content-type, it is not:
curl -X PUT 'https://api.cloudflare.com/client/v4/accounts/a67e14daa5f8dceeb91fe5449ba496eb/stream/644822f93dcddab3e9441587d184ca2f/captions/tr' -H 'Authorization:Bearer $KEY' -H 'Content-Type: text/vtt' -F<EMAIL_ADDRESS>-v

> PUT /client/v4/accounts/a67e14daa5f8dceeb91fe5449ba496eb/stream/644822f93dcddab3e9441587d184ca2f/captions/tr HTTP/2
> Host: api.cloudflare.com
> user-agent: curl/7.81.0
> accept: */*
> authorization:Bearer $KEY
> content-length: 342
> content-type: text/vtt; boundary=------------------------795314ec39dbb78e
>

< HTTP/2 400
< date: Fri, 01 Jul 2022 05:50:50 GMT
< content-type: application/json; charset=UTF-8
< cf-ray: 723cddce2dd2643b-SJC
< set-cookie: __cflb=0H28vgHxwvgAQtjUGU4vq74ZFe3sNVUZbP8MasUPhY1; SameSite=Lax; path=/; expires=Fri, 01-Jul-22 08:20:51 GMT; HttpOnly
< vary: Accept-Encoding
< cf-cache-status: DYNAMIC
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< x-envoy-upstream-service-time: 8
< set-cookie: __cfruid=836842155ee90a5c4e44c653c70c9cbb047c7232-1656654650; path=/; domain=.api.cloudflare.com; HttpOnly; Secure; SameSite=None
< server: cloudflare
<
{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10004,
      "message": "Decoding Error"
    }
  ],
  "messages": null
}

This is because this endpoint expects data to be uploaded in form of multipart/form-data (RFC7578). By setting the content-type header, the request is no longer a valid multipart upload, which causes the Stream API to fail at decoding.
You mentioned that you use the python requests library to interact with the Stream API. Though I don't claim to be expert in Python, I've looked at the requests library documentation and found a multipart upload example: https://requests.readthedocs.io/en/latest/user/quickstart/#post-a-multipart-encoded-file. I would suggest to use a library to construct a multipart upload.
Going forward, one solution I'm bringing is to clarify this error condition make make it clear the type of upload we expect when we fail to parse. I have a pull request internally that makes an attempt to clarify when this error case it hit:
{
  "result": null,
  "success": false,
  "errors": [
    {
      "code": 10004,
      "message": "Decoding Error"
    }
  ],
  "messages": [
    {
      "code": 10004,
      "message": "Could not parse the multipart form upload. Please verify that this is a valid multipart upload with a key named 'file'."
    }
  ]
}

Do you think this would make it more clear and would have prevented this issue? Please feel free to correct me if I'm misunderstanding your report. I will comment again when my PR gets deployed into production.

Hi @renandincer thanks for the response! The trouble I ran into was with the content-type header. I thought that I was failing to upload with the requests library even when specifying multipart/form-data as the type, but I can't reproduce that result now.
I suppose the easiest resolution from my perspective, and the thing that, aside from the expanded error message, would have saved me the most time, is if the example curl command in the docs specifically called out the content-type: multipart/form-data header.

Closing now that this is fixed.


twist filter output wrong linear velocity

Bug
The linear value change sign if the angular value change sign.
need to rewrite line 69 to this:   double max_v = g_lateral_accel_limit / fabs(omega);
Specifications

Ubuntu version:16.04
ROS version:kinetic
Autoware branch:master

#1230 is opened about this bug


Automatic conversion from uncostrained type no longer works in Scala 3.1.1

Describe the bug
Scala environment: JVM
Scala version: 3.1.1
Iron version: 1.2.0
Reproduction steps
import io.github.iltotore.iron.*
import io.github.iltotore.iron.constraint.*
import io.github.iltotore.iron.numeric.constraint.*

def mult(x: Int > 0, y: Int > 0): Either[IllegalValueError[?], Int] =
  for
    a <- x
    b <- y
  yield a * b

def pow(z: Int): Either[IllegalValueError[?], Int] = mult(z, z)

pow(5)

The same is available as a Scastie here
Expected behavior
Up to Scala version 3.1.0 included
Right(25): scala.util.Either[io.github.iltotore.iron.constraint.IllegalValueError[_ >: scala.Nothing <: scala.Any], scala.Int]
Current behavior
With Scala version 3.1.1
the pow method fails to compile, with the following error:
cannot reduce inline match with
 scrutinee:  0 : (0 : Int)
 patterns :  case b @ _:Int if a.>(b)
             case b @ _:Int if a.==(b)
             case b @ _:Int if a.<(b)
             case b @ _:Int

Hello.
Scala 3.1.1 introduced some inline/type-inference bugs fixed in 3.1.2. Can you test Iron with this version ?
Your code works if we specify Int > 0 in your pow method. Since we cannot prove that Int is a Int > 0 at compile-time, Iron tries to use the compile-time value of z but Scala 3.1.0 restrained this behaviour to only fully inlined values.
Iron will receive a major release around this summer which will forbid this manipulation in profit of a more explicit fully safe refined type system.
To fix this issue, simply specify Int > 0 instead of Int for z in pow.
Also note since Iron 1.2.0, you can simplify your code into (Scastie):
import io.github.iltotore.iron.{*, given}
import io.github.iltotore.iron.constraint.{*, given}
import io.github.iltotore.iron.numeric.constraint.{*, given}

def mult(x: Int > 0, y: Int > 0): Raw[Int] = refined {
  x * y
}

def pow(z: Int > 0): Raw[Int] = mult(z, z)

pow(5)

Tried now on Scastie with 3.1.2 RC1 and the error seems to stay the same.
Specifying Int > 0 is of course doable, but this manipulation kept the code simpler, no need to propagate the constrain.

Specifying Int > 0 is of course doable, but this manipulation kept the code simpler, no need to propagate the constraint.

I dont think this explicitation is redundant and it ensures the algebraic consistency of the program/method without depending on the call itself (while your example might not work if z is unknown at runtime). In fact, forcing this explicitation makes refined types behaving like "normal" Scala types.
Anyway, I am still open to discussion and suggestions about this topic.

Thank you for all the replies, I see your point.


Android sample app wont even sync on latest Android Studio Iguana

Can't get the sample app to compile or even Gradle sync, opened the sample_app folder in Android Studio Iguana and no matter what jdk I select I get:
BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 61

Hi there,
This project was written a few years ago and I am no longer working on it.
I assume what you need is updating Gradle and the gradle plugin but I don't know if there's any migration required for it.
Alternatively, you could take the kotlin files and just create a new project from scratch.
Happy to review a PR if you want to update this.
Thank you


Issue with read\open of DXT3 file

Hello,
I am getting strange result when reading DXT3 files. DXT5 works very well.
Original file https://www.dropbox.com/s/hv6d5ru6dwemsyr/ui_team_logo.dds?dl=0
Original file look https://i.imgur.com/to9Vj9l.png
Lib read file like this https://i.imgur.com/1B2qbJM.png
That is not only for this single file, but for all DXT3 files that I have.
Also, other editors\viewers show such files without any issues.
Do you have an idea if it is possible to fix this?

I couldn't maintain this project as it was, so I've simplified it and used the Pfim library as a decoder, it does a much better job. You may want to use Pfim directly in your own project and use mine as an example of its use.


[PREVIEW, DO NOT MERGE] HHH-13022 Make OSGi integration work on JDK11

https://hibernate.atlassian.net//browse/HHH-13022
This is based on #2584, which should be merged first.
PLEASE DO NOT MERGE, I'm just opening this so we can discuss the current state of the code, and the remaining problems.
This is far from ideal, but it's the best I could do after several days spent investigating.
On the bright side, OSGi tests are now enabled regardless of the JDK version
On the dark side, making JAXB work in OSGi is really hell. It only works at the price of an ugly hack, and only when sticking to JAXB 2.2.11.
JAXB and OSGi
The first issue is that, for some reason, when we execute Hibernate ORM in Karaf, the JAXB APIs are loaded from some lib/ folder provided by Karaf. I don't know why exactly, but I suspect our OsgiClassLoader has something to do with this: as it is currently implemented, it looks up classes in the client's bundle context first, and only if not found there we look them up in the Hibernate ORM bundle context.
This is bad enough, but with the version currently included in Karaf, we can sort of make it work.
The second issue is that JAXB JARs do not work "out of the box". Just adding the runtime JAR as a bundle to our feature is not enough, the API classes will not detect it. Apparently it's because the JAXB JARs do not declare service implementations as OSGi requires (using blueprints, for example). Here are the solutions I could think of:

Use com.sun.xml.bind:jaxb-osgi, which is an OSGi bundle by the JAXB maintainers. Looks ideal? No it's not:

This bundle includes jaxb-xfc, which requires a lot of dependencies, among which package 'com.sun.source.tree' which is part of the Java compiler APIs and is not available by default in Karaf (I couldn't find the appropriate OSGi bundle).
I'm not even sure this OSGi bundle will work correctly if we solve the problem above, because the source code for this Maven artifact doesn't look like it does anything special to declare service implementations (no blueprints in particular). Maybe it will, but given the strange stuff we do in our classloader, I wouldn't bet on it.

Wrap the JAXB JARs ourselves, adding whatever OSGi configuration that is necessary.

Maybe we could create a clean bundle with all the correct configuration, but that would essentially mean re-building the jaxb-osgi artifact ourselves.
I was able to come up with a very simple wrapping. It's an ugly and probably fragile hack, but it works in Karaf with both JRE 8 and JRE 11. The hack consists in wrapping the JAXB runtime bundle, adding in particular an "Export-Package: META-INF.services" instruction to the manifest. Due to how resource loading works in Karaf, this ends up exposing the relevant META-INF/services/XXX file from the runtime bundle to the API classes, and the API classes end up instantiating the runtime as we would expect.

So once again, this is bad, but I was able to make it work, at least.
The third issue is that upgrading to JAXB 2.3 will probably be quite complex. I tried it, and faced the following challenges:

JAXB 2.3.1 requires javax.activation 1.2.0, which declares an OSGi dependency to package com.sun.activation.registries, which is not available by default in Karaf (I couldn't find the appropriate OSGi bundle).
JAXB 2.3.1 requires stax-ex 1.8, which declares an OSGi dependency to Java 9+, even though it should work just fine on Java 7 (it's built using JDK7)
... and that's only where I stopped, there may be more.

OK, thanks for the summary.
I think it would be worth opening a Karaf issue to ask for advice on how to solve this issue. We probably won't be the only one requiring a JAXB dependency. They might be more legitimate than us to ask for manifest fixes and so on.

A quick update. While working on reproducers to submit to the Karaf team for advice, I noticed that two weird pieces of code in particular was necessary to reproduce our problem. In both those places, we explicitly set the Thread Context Class Loader (TCCL) to a classloader of our own:

org.hibernate.osgi.OsgiPersistenceProviderService#getService:  @Override
  public Object getService(Bundle requestingBundle, ServiceRegistration registration) {
  	final OsgiClassLoader osgiClassLoader = new OsgiClassLoader();

  	// First, add the client bundle that's requesting the OSGi services.
  	osgiClassLoader.addBundle( requestingBundle );

  	// Then, automatically add hibernate-core and hibernate-entitymanager.  These are needed to load resources
  	// contained in those jars, such as em's persistence.xml schemas.
  	osgiClassLoader.addBundle( FrameworkUtil.getBundle( SessionFactory.class ) );
  	osgiClassLoader.addBundle( FrameworkUtil.getBundle( HibernateEntityManagerFactory.class ) );

  	// Some "boot time" code does still rely on TCCL.  "run time" code should all be using
  	// ClassLoaderService now.

  	final ClassLoader originalTccl = Thread.currentThread().getContextClassLoader();
  	Thread.currentThread().setContextClassLoader( osgiClassLoader );
  	try {
  		return new OsgiPersistenceProvider( osgiClassLoader, osgiJtaPlatform, osgiServiceUtil, requestingBundle );
  	}
  	finally {
  		Thread.currentThread().setContextClassLoader( originalTccl );
  	}
  }

org.hibernate.osgi.OsgiSessionFactoryService#getService:  @Override
  public Object getService(Bundle requestingBundle, ServiceRegistration registration) {
  	final OsgiClassLoader osgiClassLoader = new OsgiClassLoader();

  	// First, add the client bundle that's requesting the OSGi services.
  	osgiClassLoader.addBundle( requestingBundle );

  	// Then, automatically add hibernate-core.  These are needed to load resources
  	// contained in the core jar.
  	osgiClassLoader.addBundle( FrameworkUtil.getBundle(SessionFactory.class) );

  	// Some "boot time" code does still rely on TCCL.  "run time" code should all be using
  	// ClassLoaderService now.

  	final ClassLoader originalTccl = Thread.currentThread().getContextClassLoader();
  	Thread.currentThread().setContextClassLoader( osgiClassLoader );
  	try {
  		return buildSessionFactory( requestingBundle, osgiClassLoader );
  	}
  	finally {
  		Thread.currentThread().setContextClassLoader( originalTccl );
  	}
  }

Interestingly enough, if I remove these pieces of code, the OSGi tests now pass with JDK8 and JDK11, even if I do not add JAXB to our Karaf feature (it uses the Karaf-provided JAXB runtime). And no other tests fail. I added two commits to demonstrate this.
Also of interest: setting the TCCL in OsgiSessionFactoryService will have an effect during the whole duration of the bootstrapping process, but for OsgiPersistenceProviderService, it will only be effective in the OsgiPersistenceProvider constructor, which is dead simple and unlikely to trigger much class loading. OsgiPersistenceProvider itself, when it creates the EntityManagerFactory, does not set the TCCL. So there's something fishy here, at the very least an inconsistency between how we start in JPA and native mode.
I wonder if setting the TCCL is actually useful? I know it creates problems, but maybe it solves others? If it does, they are untested problems, though... I'll investigate a bit more, maybe try to ping Steve.

Superseded by #2589


Fix workflow definition history node data cannot be opened

Codecov Report

Merging #2760 into dev-1.3.0 will increase coverage by 0.99%.
The diff coverage is 35.35%.

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


Tests on new project dont pass

Description
if you create a new project using the method on the website, tests dont pass
CodeSandbox/Snack link
https://github.com/ofersadgat/gluestack-bug
Steps to reproduce

npm create gluestack
What would you like to build? Select "React Native app"
What is the name of your application? (i put my-app-ts)
cd my-app-ts
npm run test
Failure. "SyntaxError: Cannot use import statement outside a module"

gluestack-ui Version
latest
Platform

[ ] Expo
[X] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

@ofersadgat Thanks for reporting this. We'll have a look.

@surajahmed any updates on this?

hi @ofersadgat ,
We will update the tests and then push the new template.
The tests cases made previously are not compatible with the new version.

@akash3gtm can you comment on the thread when the new template with working tests has been pushed?


Is there a reason why Transform3 isn't implemented for Matrix4?

Currently, as far as I know the only way to transform a Point3 with a Matrix4 is:
Pt::from_vec((transform * pt.to_homogeneous()).truncate())

But there's a perfectly good API for objects which can transform points, Transform3.
This would be useful for procedural geometry generation applications, where you want to produce vertices for the same shape, translated and rotated to your desired location.

Related - https://github.com/bjz/cgmath/pull/302#issuecomment-211168768

Agreed.

The original reason, as mentioned in the thread that @kvark linked to, was that it requires additional interpretation of a matrix to treat it as an affine transformation vs a rotation. I think that I need to revise this stance though, for simplicity.

Related: #324

I'm guessing we would have to incorporate One (and Zero for completeness) into the trait hierarchy to avoid collisions. concat would then become mul.

Stuff like this hurts the usability of cgmath for me. I just want to be able to make quaternions, matrices, and vectors, and have them all play nice with each other in the expected ways.

Closing in favor of #349


Low efficiency in parsing Protobuf and a possible optimization

Affected Version
0.12+ [(In all versions that support protobuf-extension)
Description
Protobuf (protocol buffers) is known as a faster mechanism for serializing structured data. For higher efficiency in ingestion, we tried protobuf-extension and wrote a simple benchmark to compare it with Json. However, it turns out that protobuf is much slower.

After investigating the function parseBatch in class ProtobufInputRowParser, we found that the parser would first transform protobuf to Json(specifically, a String), and then use jsonParser to parse it. Despite of the huge transmission advantage of protobuf, this parsing mechanism would lead to slower ingestion due to the extra process.
In order to achieve faster ingestion, we optimized the function parseBatch by transforming the protobuf to a map directly:
DynamicMessage message = DynamicMessage.parseFrom(descriptor, ByteString.copyFrom(input));

Map<String, Object> record = CollectionUtils.mapKeys(message.getAllFields(), k -> k.getJsonName());

Then we wrote a benchmark to compare them. It turns out that the optimized one can reduce the ingestion time by about 80%. The result is shown below:

We also run the ProtobufInputRowParserTest to test if the parsing result is correct. It shows that if there is no need of setting JsonPathSpec (to rename the key or get a subset of the value), the result is correct.  We think that users can decide if they have such need and then choose a proper parsing method for higher efficiency.

Machine info:
1.7GHz Intel Core i7
16 GB 2133 MHz LPDDR3

you could make a PR


Export Dashboard - Data Sources Ordering Is Volatile

When using the export_dashboards command on the CLI, everything is working great but I noticed that sometimes the order of the datasources changes in the list with no updates. I'm attempting to use the export functionality to git version my dashboard definitions and a reordering of my datasources with no changes ends up causing noise in my diffs.
How to reproduce the bug

Create dashboard with multiple data sources
Export dashboard
Make a tweak to the dashboard but dont change anything in the data sources
Export again and diff the files

Step 3/4 might need to be repeated a couple times as I don't know that it happens every time.
Expected results
The export outputs should not be volatile, if I dont change a data source then there should be no diff when exporting multiple times. Exporting multiple times produces the same result always.
Actual results
I have 2 tables in my data sources list and they switched positions without any changes.
Screenshots
An example of a dashboard with 1 chart. Changing the chart name from "AOV" to "AOV - New" caused a huge diff between the original and new export.

Environment
(please complete the following information):

browser type and version:
superset version: superset version
python version: python --version
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I'm wondering if using a set in the export_dashboards method is causing the list reordering in inconsistent ways.
I'm happy to help implement a change! Let me know if you think thats the issue or if something else might be causing it.

@pnadolny13 I'm trying to get a little attention drawn back to the PR, so we can conclude this. Thanks for opening that, byt the way, and sorry it didn't get more eyes sooner. Are you able to rebase it, so it can trigger a fresh CI run and be mergeable?

its working as expected now if the issue has been resolved please close the issues

@Shazad-khan in which Superset version was this fixed?

I can reopen this if the problem persists, just let me know... let's try to get that PR through if it's the real fix.


stop translating when element is out of view

Hi.
Would it be possible to stop the element from translating when it moves out of view?
at the moment elements out of view are still translating as you scroll down your page.
Cheers,
Jack

Hey @jackiboy thanks for the issue.
We had a //TODO in the code to address this but removed it since it didn't seem necessary. The primary issue we struggled with is locating DOM elements when they are translated via translate3d(). We're not opposed to a solid implementation that handles pre-fetching positions for elements that move faster than scroll or post-fetching for elements that move slower.
It's a great issue, but a complicated one, but happy to work with someone on implementing a reasonable solution.

Hey @jackiboy, going to close this for the moment unless there's performance issues on your end.


I used nix-shell to install CMake to compile, but it failed and I don't know why QQ.(I use MacBook Pro M2 btw...

run nix-shell -p cmake cmake -B build cmake --build build and  then I got:
#include <IOKit/IOKitLib.h>
         ^~~~~~~~~~~~~~~~~~
1 error generated.
make[2]: *** [_deps/sdl2-build/CMakeFiles/SDL2-static.dir/build.make:552: _deps/sdl2-build/CMakeFiles/SDL2-static.dir/src/hidapi/SDL_hidapi.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:474: _deps/sdl2-build/CMakeFiles/SDL2-static.dir/all] Error 2

does it work on native macOS?

nix-shell works on my Arch machine, IOKit/IOKitLib.h seems like a macOS specific issue

{
  description = "I used nix-shell to install CMake to compile, but it failed and I don't know why QQ.(I use **MacBook Pro M2** btw...";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    flake-utils.url = "github:numtide/flake-utils";
  };

  outputs = { self, nixpkgs, flake-utils, ... }:
    flake-utils.lib.eachDefaultSystem (system:
      let
        pkgs = import nixpkgs { inherit system; };
      in
      {
        devShell = pkgs.mkShell {
          buildInputs = with pkgs;[
            cmake
            ninja
            llvmPackages.llvm
            mesa
          ] ++ lib.optionals (system == "aarch64-darwin") [
            darwin.apple_sdk.frameworks.Cocoa
            darwin.apple_sdk.frameworks.IOKit
            darwin.apple_sdk.frameworks.ForceFeedback
            darwin.apple_sdk.frameworks.AVFoundation
          ];
        };
      });
}


Fix import

nn.functional._functions.dropout was removed in v1

Thank you for pointing this out!
I found another alias for this name that isn't in a private/underscore namespace, and this is now fixed in master.


implemented vertical spacing for project updates on mobile design

Ensure vertical spacing between update cards found on project pages on mobile [v1.18.0 RELEASE]

Test Instructions

yarn dev
verify design on mobile

Check out a preview of your pull request here: https://app-servicecanadalabs-dev-pr-preview-3.azurewebsites.net


Windows issue: 0.33.5 - window becomes white on calling win.hide()

When calling BrowserWindow .hide(), the window becomes white under Windows 10 and 8.1 (haven't tested on anything else) with Electron 0.33.5.
The window then does not hide, simply remains white forever.

Oops, I removed a wrong line in https://github.com/atom/electron/pull/2950, will revert that.

Thanks! Awesome & quick work

:star2: Was wonder if I was doing something wrong :) Thanks for fixing it so quickly! :shipit:


Eliminate duplicate dependency spring-boot-starter-web

The project still builds.
All tests still run fine.

Thanks @catull  Merged.


New import interface

We recently had the issue of accessing data on the server, which was not easy through the Browser but trivial with a simple QFileDialog.
Which makes me think of the utility of the File System tab in the Browser, and I think it can be replaced by an Import and Load buttons in the Database tab.

View already exists in the Database tab, the Index action is never used and the Bookmark can be replaced by the shortcuts list we have at the left side of our FileDialog (called Favorites on MacOSX):

By using our OS's File Dialog (called native), we have easy access to our file system and new tools like on Mac, you have the Search tool, you can play with the file system (move files, create folder, rename).
It's pretty straightforward, robust and everything is already done.
The drawbacks I see: you cannot modify native FileDialog (I wanted to add a checkbox for saving persistently/non-persistently in the db but it's not possible), and I couldn't find a way to do multiple selection.
I also used this FileDialog in the view container button "open from ...". The almost-single-lined change I have done allows now to open DICOM folders (before we could only open files).
Note: when you select a folder containing several series, it loads all of them but just opens the first one.
I wanted your opinions on it before going further, even though it's almost done :), so you can test it!
The load button is not there, but you have the idea. As I said I did my test on Mac, so feedbacks on other OS are welcome.

You can use dialog.setFileMode(QFileDialog::ExistingFiles); instead of AnyFile for multiple selection.
You can look at https://github.com/LMMS/lmms/issues/90 where they developped their own dialogFile based on QFileDialog with usefull shortcuts.
I was looking at the connection to servers under Linux, but did not succeed for now :/.
Anyhow, i like the idea to remove the File system tab which is useless and to switch to an "import" button. :)

By the way, if you add dialog.setOption(QFileDialog::DontUseNativeDialog, false); on mac, do you have access to your favorites, servers, etc ?

With dialog.setFileMode(QFileDialog::ExistingFiles); I can't select files and folders.
I don't know how it works on Linux, but on Mac DialogFiles are the one you have in the Finder (file explorer), so you have all the shortcuts of your Finder. On Windows it's the same, I am pretty sure. Btw, the interface is the same as the one you have when you select a directory for the db in MUSIC, I also used native dialogs.
To answer your last comment, the key point here is to use native dialogs, to use what already exists and works well. And from this, if you can access your data with the file explorer, you can access it from the fileDialog.

As far as i tested, QFileDialog::DontUseNativeDialog do not seem to change anything on linux, it's never the native dialog. I'm going to test again today.

I searched a bit and this works on my side:
    // Try to select multiple files and directories at the same time in QFileDialog
    dialog.setFileMode(QFileDialog::Directory);

    QListView *l = dialog.findChild<QListView*>("listView");
    if (l)
    {
        l->setSelectionMode(QAbstractItemView::MultiSelection);
    }
    QTreeView *t = dialog.findChild<QTreeView*>();
    if (t)
    {
        t->setSelectionMode(QAbstractItemView::MultiSelection);
    }

You can choose multiple/single files or directories.

I add Load option.
Your solution @mathildemerle does not work for me, I cannot select multiple folders (btw, with your code, you cannot select files).

The Load button works well.
However, i can't use "CTRL-A" to select all my files in a DICOM directory, or open directly a directory.

I put this PR on "bug" label since it's not usable on my side for the moment.

Is this PR going to be updated some day or is it definitely abandoned ?

Well, i don't know, it was a good idea. Maybe the problem is going to be solved with Qt5?

It's not abandoned, I just need time to make it work.


[Question] Modify the default cluster-cidr of harvester

The default cluster-cidr network segment of the harvester cluster conflicts with our production environment. Is it possible to modify the method in the following way?
# git clone https://github.com/harvester/harvester-installer.git
# cd harvester-installer
# git checkout v1.1.2

# vim ./pkg/config/templates/rke2-90-harvester-server.yaml

...omitted...
cluster-cidr: <IP_ADDRESS>/16
service-cidr: <IP_ADDRESS>/16
cluster-dns: <IP_ADDRESS>
...omitted...

# make

# ls -al ./dist/artifacts/
total 5927012![image__9_](/uploads/3736b44268bd2d6c56e7b845d8e9f826/image__9_.png)
drwxr-xr-x. 2 root root        259 Jun  7 07:15 .
drwxr-xr-x. 3 root root         23 Jun  7 06:55 ..
-rw-r--r--. 1 root root<PHONE_NUMBER> Jun  7 07:15 harvester-cf6d3b7-dirty-amd64.iso
-rw-r--r--. 1 root root        675 Jun  7 07:15 harvester-cf6d3b7-dirty-amd64.sha512
-rw-r--r--. 1 root root   90024588 Jun  7 07:10 harvester-cf6d3b7-dirty-initrd-amd64
-rw-r--r--. 1 root root  622329856 Jun  7 07:14 harvester-cf6d3b7-dirty-rootfs-amd64.squashfs
-rw-r--r--. 1 root root   11448480 Apr 13 08:04 harvester-cf6d3b7-dirty-vmlinuz-amd64
-rw-r--r--. 1 root root       1897 Jun  7 07:15 image-lists.tar.gz

Could the official provide a more convenient and simple way to modify the harvester cluster-cidr configuration?

cc @guangbochen

When deploying the Harvester cluster using a repackaged image, we encountered the following issue. Is it possible that there are some configurations that need to be adjusted?
I have prepared three virtual machines, hk-harvester-master-0-{1~3}, for testing cluster deployment using repackaged iso. After the first node was deployed, the configuration of CIDR in the file /etc/rancher/rke2/config.yaml.d/90-harvester-server.yaml matched our expectations. However, upon adding the third node to the Harvester cluster, the status of the second node hk-harvester-master-0-2 that had joined the cluster became notready.
checking the logs of its RKE2 server, we have found the following error:
Jul 20 09:08:36 cngb-hmaster-c19-1 rke2[36897]: time="2023-07-20T09:08:36Z" level=fatal msg="starting kubernetes: preparing server: failed to validate server configuration: critical configuration value mismatch between servers"

Meanwhile, we discovered that the CIDR configuration for the file /etc/rancher/rke2/config.yaml.d/90-harvester-server.yaml on the hk-harvester-master-0-2 host had reverted back to its default settings, instead of the modified ones. To resolve this issue, we adjusted the file content to match that of hk-harvester-master-0-1, restarted the RKE2 server, and the node status returned to 'ready'.And we encountered a similar situation with the hk-harvester-master-0-3 host.

The default cluster-cidr is defined in harvester via the installer's rke2-template.
Currently, it does not support customization. For future enhancement, consider adding a new setting for it. However, upgrading from the existing cluster might be difficult as changing the cluster CIDR is a sensitive operation and can potentially disrupt your cluster and require to shutdown/restart all of your VMs and workloads.
Loop @bk201 and @markhillgit for some attention, thanks.

cc @innobead @forbesguthrie
We have a fixed CIRD for services, which might cause some users conflicts.

Any updates on this? It should be allowed to change the cluster-cidr on install, not necessary after an initial install.

Add require/doc label: to add doc in https://docs.harvesterhci.io/v1.3/install/harvester-configuration for new fields.

Re-opening issue for QA.


Problem in updating the operation-key of OKM’s /v1/update-operation-key API’s server and client

Updating operation-keys for the following endpoints creates a problem ,
Operation-name : /v1/update-operation-key
Serving uuid : okm-2-0-1-op-s-bm-010
Consuming uuid : okm-2-0-1-op-c-is-okm-2-0-1-000

Initial configuration :
Mode : Protection/reactive mode
OKM :
okm-2-0-1-op-s-bm-010 : /v1/update-operation-key : Operation key not yet provided
okm-2-0-1-op-c-is-okm-2-0-1-000: /v1/update-operation-key : Operation key not yet provided

Step1 : OKM set the operation-key of okm-2-0-1-op-s-bm-010 to “123456789”
Request :
url and operation-key will be formulated from
okm-2-0-1-op-c-is-okm-2-0-1-000: /v1/update-operation-key : Operation key not yet provided
requestBody :
{
Uuid : okm-2-0-1-op-s-bm-010 , new-operation-key : “123456789”
}
Consequence :
OKM :
okm-2-0-1-op-s-bm-010 : /v1/update-operation-key : “123456789”
okm-2-0-1-op-c-is-okm-2-0-1-000: /v1/update-operation-key : Operation key not yet provided

Step2 : OKM set the operation-key of okm-2-0-1-op-c-is-okm-2-0-1-000 to “123456789”
Request :
url and operation-key will be formulated from
okm-2-0-1-op-c-is-okm-2-0-1-000: /v1/update-operation-key : Operation key not yet provided
requestBody :
{
Uuid : okm-2-0-1-op-c-is-okm-2-0-1-000, new-operation-key : “123456789”
}
Consequence :
401 response code because the operation-key of the outdated operation-key

Note :
In the application , in order to avoid this problem for now , we gave a bad fix that , if there is an update in the server uuid(okm-2-0-1-op-s-bm-010) , the client uuid(okm-2-0-1-op-c-is-okm-2-0-1-000) will also be updated.

Closed as a new issue has been created https://github.com/openBackhaul/OperationKeyManagement/issues/265 for change in implementation


sap.ui.type.Float/Currency preserveDecimals

OpenUI5 version: 1.89.1
Hi,
the decision of overwriting the preserveDecimals format option in sap.ui.type.Float and sap.ui.type.Currency is going to be permanent?, because we have a bunch of apps using the decimals format option and I want to know if we need to change all of them or just wait a few versions.
Thanks!
Old working code:
<ObjectNumber number="{path: 'Adv', type: 'sap.ui.model.type.Float', formatOptions: { decimals: 2 }}" unit="{Currency}"/>

New:
<ObjectNumber number="{path: 'Adv', type: 'sap.ui.model.type.Float', formatOptions: { decimals: 2, preserveDecimals: false }}" unit="{Currency}"/>

At version 1.88:

At version 1.89:

Hi @pepealbuixech,
the newly introduced preserveDecimals set to true as default will stay. The wrong preserving of trailing zeroes as shown above is however fixed with https://github.com/SAP/openui5/commit/ce6172722b168f52b8be2140aae600fc05b0a409.
Regards,
Patric


Fix mergeStorageClassParams for vmimage clone

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

Currently, image's Spec.StorageClassParameters has a higher priority than image's harvesterhci.io/storageClassName  annotation.
Modifying storageclass does not work during vm clone.
Solution:

change the priority of image's Spec.StorageClassParameters and image's harvesterhci.io/storageClassName  annotation
Related Issue:
https://github.com/harvester/harvester/issues/4506
Test plan:

create a storageclass (name=any-replicas-1 replicas=1)
create a new vm image (name=image-test-r1 storageclass=any-replicas-1), the replicas should be 1
create a new vm image (name=image-test-r3 storageclass=harvester-longhorn), the replicas should be 3
clone the vm image image-test-r1 to create a new vm image   (name=image-test-r1-clone-r3 storageclass=harvester-longhorn), the replicas should be 3
clone the vm image image-test-r3 to create a new vm image   (name=image-test-r3-clone-r1 storageclass=any-replicas-1), the replicas should be 1

LGTM and expected that the clone image replica value has changed, Thanks.

@mergifyio backport v1.2

@mergifyio backport v1.1


feat: add page number command

Description
Adding add page number command to ILovePDF extension where you can
control the following:

To convert the PDF into facing page mode, where every two pages face each other.
To skip the first page since it's a cover page.
Decide the starting number
Decide the numbering format, font family, font size
Deciding what pages to number
Deciding the position of the numbering

Screencast
https://github.com/raycast/extensions/assets/41074872/a4249dc1-9641-402f-a675-774a0ec70209

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi again!
This command seems to be working as expected. However, there is a bit of a gap that could be avoided. Do you mind checking it out?

@mil3na Thanks for the feedback ^_^ . Fixed the issue.


Max: Bug fix on wrong aspect ratio and viewport not being maximized during context in review family

Changelog Description
This PR will fix the bug on wrong aspect ratio and viewport not being maximized when creating preview animation
Besides, the support of tga image format and the options for AA quality are implemented in this PR
Additional info
Should be tested in the Max version before 2024.
Testing notes:

Launch Max (2022, 2023) with OP
Create Review Instance with different review width and review height in the setting
Publish

@LiborBatek I have added the support of the tga image format for review and also anti-aliasing quality options in creator settings.
Also the aspect ratio should be fixed too, the resolution of the sequences wont be stretched by this case.

@LiborBatek Can you test the PR again? It is supposed that the aspect ratio should be correct and the image is cropped regarding to the ratio. Thanks!

@LiborBatek The view cropping wont happen when the aspect ratio of the review is the same with the render setting.
But the cropping does still happen when aspect ratio of the review and that of the render settings are different. This is to avoid any stretched images during rendering.

@BigRoy @antirotor does the code look okay for you?

Did one last test in max 2024 and even tho it produced the Review without any issues, when tried to re publish it again, the Publish Instance looses its context?
@moonyuet can u confirm too??
It seems that it is more likely an instance issue. Have you tried to create the new instances to publish it?

Did one last test in max 2024 and even tho it produced the Review without any issues, when tried to re publish it again, the Publish Instance looses its context?
@moonyuet can u confirm too??

It seems that the context

Did one last test in max 2024 and even tho it produced the Review without any issues, when tried to re publish it again, the Publish Instance looses its context?
@moonyuet can u confirm too??

It is more likely because the context data isn't updated correctly after the renaming. Let's create the new issue with separated PR.


Support syntax highlighting for all languages Prism supports

Feedback welcome and I'm happy to squash the commits if this is acceptable.

thank you! there was a small issue requiring the additional syntax plugins with Node.  The fix was applied https://github.com/Availity/metalsmith-prism/commit/b93719aa6efec302d28e65bef6b7f661965e3868.  Please let me know if everything is working as expected.

And thanks to you @robmcguinness for incorporating the changes and making them better so quick! I just tried 1.1.0 on my site and its working fine, the syntax highlighting for Ruby & Bash looks perfect.

:+1:


Search boxes show a bit of the background

Just noticed this in the corners:

Acceptance Criteria:

[ ] Cover weird triangles

:tada: This issue has been resolved in version 1.184.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use pinned versions of MSBuild for reference packages.

These versions of the packages are produced by source-build as reference packages and do not need to participate in version flow.

cc @JunTaoLuo

We need to consider the impact here. Is there a need to use the latest MSBuild versions to support features cc @rynowak @pranavkm. Also, is pinning the dependency to something older considered a breaking change here?

Our OmniSharpPlugin project depends on a compatible MSBuild with O#. I'm not confident reducing the version will be "ok"

I think our expanded reference assembly work covers this, so we shouldn't need these changes any more.  Sorry for the trouble, closing.


*: remove CompactionJobInfo re-exports

Signed-off-by: Rustin-Liu<EMAIL_ADDRESS>
What have you changed?
Remove CompactionJobInfo re-exports.
What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

cargo test --all --no-run
Does this PR affect documentation (docs) or should it be mentioned in the release notes?

Does this PR affect tidb-ansible?

Refer to a related PR or issue link (optional)
#6402
Benchmark result if necessary (optional)
Any examples? (optional)

@zhangjinpeng1987 @yiwu-arbug @brson  PTAL~

Please fix the conflicts.

Please fix the conflicts.

Fixed.

@brson  ping~

Nice work @Rustin-Liu .

/merge


Bluetooth driver

Hi,
There is still a lot of improvements we can do on this branch like for example:
We can pass Service ID and Characteristics ID requestForBluetoothDevices().
I can do this one but the bluetooth deviices I am using to test it has been already transferred on my client.
I will be grateful if someone can make this possible.
Thanks!

#8

Hi @bebo925 , do you have any schedule to merge this PR from @jcfrane for this bluetooth driver integration? You both are great for develop this awesome package, thanks

I got slammed at work, but I should have some time now with the current state of things.  I am hoping to get this merged soon.

Whats the status of this?

could you merge this and we will pay you.


fix(struct): renamed Error struct field into Failed

as @mumoshu suggested I have renamed the AffectedReleases.Error field to AffectedReleases.Failed to be more homogeneous with the other fields and to avoir conflits with other Error references.

@sgandon LGTM. Thanks a lot for fixing it 👍


Add path tracing overview to docs

@jdent02 May I suggest a separate PR for the commit "Move world settings to Blender world datablocks"?

Thanks! Really nice docs.


jMeter updated URLs

Description
This PR updates outdated dependency URLs in the jMeter installation script, and updates the jMeter version from 3.3 to 5.2.1.

:tada: This PR is included in version 3.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


add embeddings reusability in score fct + update readme accordingly

This is an improvement suggestion related to #13
This code update allows to easily reuse the embeddings.
The code is not 100% backward compatible as it does not use the store_embds anymore, but I made it such that people who were using the default value for store_embds won't see any difference.
I also updated the demo in the README to show how to use this update.

@ThibaultCastells Thanks for your help! It is much more handy in this case. Agree that this makes embeddings more easily reusable. Will proceed to merge!


[move source language] Record the source location of the last semicolon in a Sequence

Motivation
One of the tests from https://github.com/libra/libra/pull/2578 revealed a need to track the source location of the last semicolon in a Sequence, so that unreachable code errors can report the right location. This adds that information to the parser AST, and uses it in the expansion phase for the source location of the Exp_::Unit value that is used in the case where the final expression of  a sequence is missing.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Updated tests.

@bors-libra r=tnowacki

:pushpin: Commit e1f7f21 has been approved by tnowacki

:hourglass: Testing commit e1f7f2183f8672ce854f090c9bc3be8640aea4cc with merge 7500e87eb34d415902a56d54d3e1f7a2564d38e4...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tnowacki
Pushing 7500e87eb34d415902a56d54d3e1f7a2564d38e4 to master...


Wrong AJAX links

Please ensure:

[X] The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.

Description
Some links are AJAXed but GitHub returns the whole page, so the page will break immediately/once you make another navigation:

latest-tag-button: https://github.com/sindresorhus/refined-github/pull/4631#discussion_r682548229
To fix it, just remove the data-pjax attribute of the differences button

edit-files-faster:
https://user-images.githubusercontent.com/44045911/128181902-0a128898-53f5-4890-8f43-a2081501667b.mov
This is harder to fix because we need to find a way to disable the AJAX behavior

Screenshot
No response
Console errors
No response
Example URL
https://github.com/sindresorhus/refined-github
Browser(s) used
Chrome

Weird. Some links are automatically ajaxed, others need an attribute. The edit links don't have any attributes.
As for #4631 we can make sure it's using the right selector for that.

Some links are automatically ajaxed, others need an attribute. The edit links don't have any attributes.

I guess there are no "automatically ajaxed" things. Links in a container with [data-pjax] are all ajaxed, they don't need to have the attribute individually. The edit links are in this container:
<div role="grid" aria-labelledby="files" class="Details-content--hidden-not-important js-navigation-container js-active-navigation-container d-md-block" data-pjax>


Nested selectors can contain issues

Expected
.$(aaa) {
  .$(bbb) {
    ..
  };
}
// output .aaa .bbb

.$(aaa) .$(bbb) {
  ..
}
// output .aaa .bbb

Actual
.$(aaa) {
  .$(bbb) {
    ..
  };
}
// output .aaa.bbb

.$(aaa) .$(bbb) {
  ..
}
// output .aaa .bbb

Currently it renders to CssJs.selector(".aaa", [CssJs.selector(".bbb", [CssJs.color(CssJs.red)])])
Second selector should have a whitespace

There has been an exploration https://github.com/davesnx/styled-ppx/pull/404 about having a Resolver phase which is the way to go in order to handle the transformation on media-queries and selectors. Similar work has been done at native runtime: packages/emotion/native/Css.ml

Similar work has been done at native runtime: packages/emotion/native/Css.ml

Does it fix the issue (out of curiosity)?

It fixes the same issue but when you aren't using the ppx and running on native


Revert "Windows image should run sbomutil with windows archetype (#21…

…61)"
This reverts commit 33f8952ea1f3b5d674a309715bbd0c77fffc45e0.

/cc zmarano


How to move data or model from CPU to GPU?

Dear the developers of Jittor. I'm novice in Jittor and I used to adopt Pytorch in my deep learning project. When I wanna move my data or model from CPU to GPU, I always apply .to('cuda') operation. Is there any similar function in Jittor? If not, is there any explicit operation to move the data or models from CPU to GPU? Or I just need to specify the GPU (CUDA_VISIBLE_DEVICE=XXX) before running my script without explicit movement?
I'm looking forward to your reply. Thanks for your help.

Hello, using jt.flags.use_cuda=1 will put all arrays after this declaration to GPU.


Autoscrolling doesn't seen to work when dragging an item to the bottom of the list

Describe the bug
When dragging an item to the edge of the bottom screen, it doesn't seen to autoscroll. I don't know if it's an issue with the ref or which figuring out the parent component ref.
To Reproduce
I don't have a snack, but I'm figuring it's just a misconfiguration with how I'm implementing it. I'll dig through your code, but I have to admit, I'm not an expert at reanimated and most of the variables are reanimated values determining if it's the edge of the screen.
Platform & Dependencies
Please list any  applicable dependencies in addition to those below (react-navigation etc).

Platform: IOS & Android
React Native or Expo version: ^0.59.9
Reanimated version: ^1.7.0"
React Native Gesture Handler version: ^1.5.6

Additional context
Add any other context about the problem here.
Basically dragging an item to the end of the screen doesn't autoscroll to the next set of items. I can upload a generic video, but I prefer to just email you it (for privacy reasons).
Let me know.
Again, Thanks for your work.
Scott

I'm closing this. I tested this on a snack and it seems like the activation distance to autoscroll is just very small for what I'm using it for. It works though.


Have you test MobileVit on cifar-10?

Thanks for your wonderful work！
I prepare to try MobileVit on small dataset, such as MNIST, and I need adjust the network structure. Before this work, I want to know if MobileVit has a better performance than other networks on small dataset.
I notice "get_cifar10_dataset" in utils.py. Have you  tested MobileVit on cifar-10? If you have, could you please show me the accuracy and inference time result?

Ah... Sorry,I didn't test the performance of MobileVit on cifar-10.


Add Readme files on all the projects which was under the directory of 'Data Analysis'.

Description
The Projects under the directory of 'Data Analysis' had missing opening readme file . As now it has been updated, it contains important information about the project which can guide the user to view the insights from the analysis.
Fixes #1471
Type of change

[ ] Added a new machine learning frameworks, libraries or software.
[x] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

This is awesome, can you do the similar bulk update for the other folders as well, assigned you label 3

thank you sir  , ok i will do those updates too 😊.


Enabling scripted config files

While i totally understand the reasoning behind following restriction...

The React Cosmos config is a JSON file, so it can only host serializable values. This design decision is meant to discourage complex configuration, make it easy to embed config options into the UI, and enable visual config management in the future.

...I would love to see a way to allow JavaScript config files to be able to embed react-cosmos in enterprise environments.
In my specific use case we are normalizing building and testing across 50 independent projects in our company with a custom CLI tool. To be able to use react-cosmos in this environment I have to dynamically set the webpack configPath and rootPath inside the cosmos.config.json which is currently not possible.
I looked at the code part that is currently responsible for blocking JavaScript based config files and noticed that the JSON config gets loaded via the NodeJS require function which would automatically allow JavaScript configs that include a default export.
As I said at the very beginning, I can totally understand the intention of this restriction, yet I think the JavaScript ecosystem is way to versatile and complex to restrict tool configuration on simple JSON files. Further more popular tools like ESLint and Babel are going the hybrid approach as well to allow usage in any scenario.
I would love to hear your feedback on this proposal.

Hi @yhaering,
Besides the reasons you mentioned, the config needs to be serializable because it is injected into the React Cosmos UI. ESLint and Babel are server-side tools, but React Cosmos is both server and client side. Two separate configs could fix this, but it's still not ideal because some options are read in both the server and the client.
What if you generate your RC config before starting it? The generated config could be gitignored, or not, depending on your preference. Your cosmos script could look like this:
"scripts": {
  "cosmos": "scripts/generate-cosmos-config.js && cosmos --config ./path/to/generated/cosmos.config.json"

Thanks for the quick response.
I thought about generating the config file as well but would consider that a hacky last option ;)
Is it possible to start cosmos using a NodeJS API?
I played around with the startPlayground function but did not get it to work properly.

Is it possible to start cosmos using a NodeJS API?

Not really. The flow is pretty easy to follow, so it wouldn't be hard to expose an API. But the config is not received as an argument in the main function, but rather detected inside.

I thought about generating the config file as well but would consider that a hacky last option ;)

It's a hack, or a sophisticated config pipeline 😅
Hopefully this is good enough for you to get going.
I can't see something I could easily patch to make this easier for you at the moment, but I am keeping an open mind regarding:

Adding support for .js config module in the future. After all, the (computed) options need to serializable, not the file itself. That said, only a JSON file could be made editable via UI. And btw, the TypeScript config is also a JSON file ;).
Exposing a Node API that receives the config as an argument.

Thanks so much! :)
I will go with the highly sophisticated config pipeline approach for now.
Keep up the great work you are doing on this project!

Thank you, and good luck to you!

Came across this when searching for a js option and thought it would be a nice to have!
I've been trying to reduce the number of dotfiles in the root of one of our repos and it would be pretty sweet if we could join cosmos.config.json and cosmos.overrides.js into a single cosmos.config.js.
Just my two cents - keep up the great work!


/login update access_time, status

Upon calling /login endpoint update

access_time
status to active

This is a step for automation that I think many users might appreciate. We are used to put accounts in an inactive status after some time period has passed. When user logs in back into the solution, we want their account to become active again. These little changes are thus helpful and needed for our automation.
Ideally this should be behind some flag, just raising the PR as I got other devs asking to show an example solution.

Can this be re-opened on the develop branch? I'll then backport to master and release-v0.3_0.18 branches.

Nevermind, I see this was done mainly as an example. I'm not sure if the default behavior should be to do another disk I/O to change state into active. The other call - to update access time - should likely be added upstream.


IMU driver with new STIM300

Time estimate: 6 hrs
Deadline: TBA
Description of task: Last year we bought a STIM300 after we believed the old one was water damaged. Turns out the old one works and is now used for Beluga. This leaves the new one unused; we now plan to use it for the ASV. It thus needs to be configured and validated to be working with the stim300 driver repo.

Done. See PR #17 for the fix to the /dev volume that allows us to pass data to the container


LLaMA 3B configuration

Hello,
first I'd like to thank you for providing these weights! amazing work!
I want to know what is the configuration of LLaMA3B, specifically, what are the numbers of 1)layers, 2)heads, 3)dimension?

Hi @young-geng,
I created the architecture using lit-llama by lightning, but there was a problem, the dimension of the produced layer "mlp.gate_proj.weight" or "mlp.c_fc1.weight" is 8704, while in the chechpoint it's 8640.
I appreciate your help.

The 3B size is not a standard LLaMA size, so different libraries have the freedom to define their own architectures.


Added a static Image Background color

This gives all images a colored background which displays while they render. This is not a loading screen, but a true loading menu is somewhat difficult to implement, so this should make the site look a little better until then.
Related Issue: #5

looks good, but can we implement skeleton css here, i want them all to load at the same time 🤔

looks good, but can we implement skeleton css here, i want them all to load at the same time 🤔

Having a true skeleton would be the preferred option, only problem is that to do that well I might need to slightly restructure the image loading code. Should look the same on the front-end but might mean back-end has to be a little bit different, but I don't think it would cause any major problems. You'll be able to see for yourself if and when I finish the code 👍

Pull Request Invalid, new version coming soon (tm)

looks good, but can we implement skeleton css here, i want them all to load at the same time 🤔

Having a true skeleton would be the preferred option, only problem is that to do that well I might need to slightly restructure the image loading code. Should look the same on the front-end but might mean back-end has to be a little bit different, but I don't think it would cause any major problems. You'll be able to see for yourself if and when I finish the code 👍

maybe we can implement this cus, we can use a state here to define if image is all images are loaded or not, one solution could be to cache all image links in local storage and load them,


Web - Workspace - 404 error in the console appears when navigating to Workspace settings

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to URL https://staging.new.expensify.com/
Log with any account
Go to Settings -> Workspaces and etc

Expected Result:
No any errors in console
Actual Result:
404 error in the console appears when navigating to Workspace settings
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Windows / Chrome
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/0424e66b-9b86-4202-8b83-8232e5ab4d10
Expensify/Expensify Issue URL:
Issue reported by: Applause - internal Team
Slack conversation:
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

I'm not able to reproduce this, so I think we're missing part of the picture here. Judging by the logs, tt seems like this is more related to tasks than workspaces. What testing did you do before you encountered this issue @kbecciv ?

cc @thienlnam

@roryabraham Be honest, I don't remember what did I do before getting this error.

I think this is related to you creating a task (the API endpoint doesn't exist yet). We've merged some fixes so I imagine this will resolve in the coming days

Okay, should be resolved and not happening anymore


[Custom functions] Fix anchor tags

Fixes https://github.com/OfficeDev/office-js-docs-pr/issues/2222.
Includes typo fix and minor cleanup.

Docs Build status updates of commit 1343bdf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-json-autogeneration.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Setting active slide for carousel doesn't work with ngAnimate

Angular, animate - v1.4.7
Bootstrap - v0.14.2
Not a new issue see: https://github.com/angular-ui/bootstrap/issues/2235

http://plnkr.co/edit/OjmPa0FukOfqJ8JYlqo9?p=preview
You can see that when changing slides (first two buttons) that the carousel doesn't work. With active the slide shows up but you cannot change slides and without active everything disappears.  Changing active on its own does work.
However if you remove ngAnimate in my plnkr everything works.

There's one thing being done very wrong here - breaking the reference to the slides array is bad.
Forked the Plunker with those fixes here, but this needs a little looking into.

This should now be fixed in master, as can be seen here.


fix: isARM object comparison

What does this PR do?
Fix comparison of lam.architecture and Architecture.ARM_64.
Architecture.ARM_64 is an object and not ENUM.
Motivation
Currently, it fails to fetch ARM layers from Datadog causing runtime errors in Lambdas.
Testing Guidelines
Ran yarn test in v2.
Additional Notes
We can also check Lambdas architecture like this:
const isARM = lam.architecture.name === Architecture.ARM_64.name;
or
const isARM = lam.architecture.dockerPlatform === Architecture.ARM_64.dockerPlatform;
Not sure what you'd prefer;
Types of Changes

[X] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

[ ] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[ ] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

Hi @sabeslamidze, thanks for opening this and sorry for the delay in response
Could you explain more what you are seeing as the value of lam.architecture? On my side I see it typed as Architecture https://github.com/aws/aws-cdk/blob/74318c7d22bfc00de9e005f68a0a6aaa58c7db39/packages/%40aws-cdk/aws-lambda/lib/architecture.ts and the enum comparison works as expected

Hi @sabeslamidze, thanks for opening this and sorry for the delay in response
Could you explain more what you are seeing as the value of lam.architecture? On my side I see it typed as Architecture https://github.com/aws/aws-cdk/blob/74318c7d22bfc00de9e005f68a0a6aaa58c7db39/packages/%40aws-cdk/aws-lambda/lib/architecture.ts and the enum comparison works as expected

Hi @sfirrin ,
Looking at this code, two objects are compared with triple equals that will always result in False. Architecture.ARM_64 is not an Enum, it is an instance of Architecture class, according to the link you posted.

Hi @sabeslamidze, thanks for opening this and sorry for the delay in response
Could you explain more what you are seeing as the value of lam.architecture? On my side I see it typed as Architecture https://github.com/aws/aws-cdk/blob/74318c7d22bfc00de9e005f68a0a6aaa58c7db39/packages/%40aws-cdk/aws-lambda/lib/architecture.ts and the enum comparison works as expected

Hi @sfirrin ,
Looking at this code, two objects are compared with triple equals that will always result in False. Architecture.ARM_64 is not an Enum, it is an instance of Architecture class, according to the link you posted.

Btw, @sfirrin could you please confirm that Architecture.ARM_64 === Architecture.ARM_64 is True?

Ah, yes I was misreading that file, I see now you're right it's a class instance and not an enum
Looking some more, I think what we really want to compare here is the dockerPlatform as you mentioned in your original comment const isARM = lam.architecture.dockerPlatform === Architecture.ARM_64.dockerPlatform;. Could you update to that?

Thanks for the fix @sabeslamidze, it's been included as part of https://github.com/DataDog/datadog-cdk-constructs/releases/tag/v2-1.1.0 released just now


Enable batch

This add the extra code to enable the decision tree solution selection to handle batch gemms.

In tensile this is mostly coding to access the batch property from withing the dtree logic.
I did verify that this does work through by stepping through with a debugger.
I produced a model to verify that we get the type of results that are expected.
I have not done a side by side comparison of the new feature compared to the current solution selection through rocBLAS.

Change contents look good to me, just need to run clang-format so it passes static analysis


[Bug] Finder eyes blink incorrectly

Hey @neilsardesai, great work again on Mouse Finder! I love how it makes my Mac unique and appreciate the work you put into it. I recently built it from the Xcode file on Github and I'm dealing with an odd issue.
Once running, the blink animation zooms in and out instead of actually blinking. I'm not the best with Xcode so I can't quite figure out what is going on and I figured I'd open an issue to see if you had any ideas why this was happening or what I could do to solve it. Does anything come to mind?
Thanks again for your hard work! Love your stuff and can't wait to see what comes next!
If the attached video will not load please view it here: https://imgur.com/a/dGlZfu4
https://user-images.githubusercontent.com/20716142/156214123-3d04303e-3e6e-4092-ae91-4b8eb7b608da.mov

Hey Braxton, that’s def weird. Unfortunately I can’t reproduce this on my end. Are you also seeing this issue when you run the release build, rather than building it off of Xcode?

Hmm, dang, honestly I have no idea, since I can’t reproduce this on my end 🙁. I’m going to close this for now but if you can figure out what’s causing the issue, I’d be happy to review a PR. Alternatively, maybe you could tweak the code for your local build to just never have the eyes blink 👁👁

Go for it, I’ll follow up with you here if there is anything I notice or that comes to mind. May just need to turn off the blinking as a whole.
Thanks for your support & your great work! Be well!
On Mar 3, 2022, 18:08 -0600, Neil Sardesai @.***>, wrote:

Hmm, dang, honestly I have no idea, since I can’t reproduce this on my end 🙁. I’m going to close this for now but if you can figure out what’s causing the issue, I’d be happy to review a PR. Alternatively, maybe you could tweak the code for your local build to just never have the eyes blink 👁👁
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


code helper 100 cpu

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:22:50.650Z)
OS Version: Darwin x64 16.7.0
CPUs: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)
Memory (System): 16.00GB (3.98GB free)
Memory (Process): 200.14MB working set (0.00MB peak, 164.97MB private, 150.64MB shared)
Load (avg): 2, 2, 2
VM: 0%
Initial Startup: no
Screen Reader: no
Empty Workspace: yes
Timings:

Component
Task
Time (ms)

renderer
window.loadUrl() => begin to require(workbench.main.js)
163

renderer
require(workbench.main.js)
419

renderer
-> of which require() node_modules
140

renderer
create extension host => extensions onReady()
386

renderer
restore viewlet
203

renderer
restore editor view state
404

renderer
overall workbench load
496

main + renderer
start => extensions ready
995

main + renderer
start => workbench ready
1097

Additional Steps to Reproduce (if any):

Not to hijack this issue, but I had to do a CTRL + Backspace reload of Nux Mint to get code to stop chewing up the CPU. Just curious if it might be a similar issue in this case.

This issue has been closed because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.


ENH: Add qperf

looks nice!
two additional things would be needed before we merge:

docs
e2e tests :)


Add flatten options to parquet writer options

Move the options to flatten a input dictionary or
constant vector to the Parquet WriterOptions and
use values from the options.

@czentgr now that we have these options exposed, can we have a unit test that plays with these options and checks that the expected encodings were written?

@pedroerp right. Let me add tests for these options.

@pedroerp @majetideepak I've been playing with this.
Pedro when you say checks that the expected encodings were written you are referring to the Parquet encodings, correct? (I assumed so).
It turns out, for Parquet these options don't matter at all. At parquet level the encoding used is RLE_DICTIONARY (assuming the data can be written). The arrow parquet writer uses that by default unless it is turned off in the writer options of the arrow parquet writer.
The option can be turned off externally via the basic parquet::WriterOptions when they are set in getArrowParquetWriterOptions.
  if (!options.enableDictionary) {
    properties = properties->disable_dictionary();
  }

The hard coded default is true. That means even the plain vectors we create as a result of the flattening are that the data pages are RLE_DICTIONARY encoded.
The reason the two flatten options exist are:

The arrow::dictionary type does not support writing NULL values. This is a problem in using arrow and not parquet.
The constant vector REE (as arrow field type) encoding in the arrow schema is not handled (FieldToNode function in arrow). Hence we need to provide a plain vector so RLE_DICTIONARY is used instead.

Underneath, the encoding in parquet is the same if the data can be written with the option on or off:

dictionary without NULLs looks are encoded in parquet the same as flattened into plain vector with NULLs (encodingDictionary is true).
Constant vectors must be flattened as otherwise they cannot be written.

Given this, do we really need to expose both options? Only the flattenConstant option will result in a different parquet encoding down the line when REE is supported (a test can be added to expect to throw an error here if flattening is not used).
I have some tests made that can go into the ParquetWriterTests (which is a new test file that is created by other PRs).

@czentgr thanks for the details. Having a test to check that writing constants fail without flattening (since Arrow can't write REE to parquet), but works it we flatten seems reasonable to me.

@pedroerp @majetideepak Please take a look when you get a chance. As discussed this is exposing the flatten of a constant vector option when writing parquet and adds a test for it.

@majetideepak could you take another pass at this? Please flag it when it's accepted and I'll get it merged.

We decided to let this slip. Instead of externalizing the flatten option a better approach is to implement REE encoding to avoid having to flatten the dictionary in the first place.


weinre URL should be HTTPS when in secure mode

Hmm, we don't have any control over the weinre server - perhaps we could proxy it? gross :(


Move pre-commit-config to top-level directory

I think this was done already in https://github.com/CWorthy-ocean/C-Star/commit/e081da1b7e3426aabcd229d059ea1652302d878d


Update sql-database-elastic-scale-shard-map-management.md

Added explanation of immutability of mappings in response to customer inquiries

Hi @stuartozer, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (stuarto). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Stuart sent approval request to Sidney.

@sidneyh

Sidney approved.