Bugs in data flow overload threats

Threats DF.O.CCDFSFC.3 and DF.O.CCDFSTC.3 model potential attacks on a service by a client that normally sends data to or receives data from the service. The threats model the possibility that a malicious or compromised client could send or request excessively large volumes of data.
The threat patterns assume the malicious or compromised client is the source/destination of the data flow. The effect is an overload in the data exchange between the client and service. However, data can flow via intermediaries, so the service may be forwarding data to/from another process. This is modelled by two secondary threats DF.O.CCDS2FC.0 and DF.O.CCDS2TC.0, which propagate the overload in one data exchange to the next exchange carrying the same data flow. Two more secondary threats P.O.CCDFSTS.0 and P.O.CCDFSFS.0 then cause an overload at the final service which is the ultimate destination/source.
There are several assumptions here, at least some of which are questionable.

The first pair of threats assumes only a client which is the source/destination of the data flow can launch such an attack - a malicious service or intermediary cannot be the cause of an overload in the data flow.
The second pair of propagation threats assume data flows in the same direction (client-to-service or service-to-client) at every step on the path between source and destination.
The last pair of threats assume that an excessive data flow passing through an intermediary does not overload the intermediary, since it doesn't process the data but only forwards it.

Any malicious or compromised client obviously can launch an attack to overload its service with excessive requests, irrespective of whether those requests or their responses convey a potentially large volume of data. This is covered by a separate threat P.O.CCCS.3 that doesn't involve flows of data. Ideally, threats that do involve flows of data would not duplicate the effect of the more general threat.
That said, an overload at the target service does not propagate beyond that service to affect other processes - that is only possible if the overload is expressed via an excessive data flow forwarded by the target service from/to other processes. Duplication should therefore be avoided by suppressing the service overload threat P.O.CCCS.3 where there is an equivalent data flow overload threat.
Evidently, a data flow overload can arise if any client (not necessarily the data flow source or destination) sends or requests an excessively large volume of data. It can also arise if a malicious or compromised service sends an excessive amount of data in response to a legitimate request. The primary threats DF.O.CCDFSFC.3 and DF.O.CCDFSTC.3 should be replaced by others that cover attacks by services that send data as well as by clients, where the malicious or compromised process may be an intermediary.
An excessive demand for data should propagate via a series of client-service connections. This propagation should cease on reaching a service that waits for data from another client rather than forwarding the request to another service. Excessive demand should not cause process overload at an intermediary - this should only happen if the excessive data request reaches the source of the data flow.
An excess of data should propagate via intermediaries, irrespective of whether the data flows client-to-service or service-to-client. If the attack comes from a process sending a lot of data, then the excess of data should affect every step between the cause and the data flow destination. The excessive data flow could cause a process overload at an intermediary that waits for requests from other clients rather than forwarding the data to another service, or at the destination process.

Seems like the best principles would be as follows.
A client could send data to a service, or request data from a service. A malicious client could therefore send too many requests, or too much data. A malicious service cannot send too many requests, but can send too much data in response to a request.
An intermediary could act as either a client or a service.
Attacks launched or propagating from client to service can be blocked by firewall policies to manage the rate of communication or use of bandwidth. Attacks launched or propagating from service to client cannot.
Excessive data requests and excessive data transfer are two distinct forms of attack.
Excessive requests for data should not overload a recipient service unless the service is the source of the data (since then it must perform computation in responding to the request).
If a client sends so many data requests to an intermediary that they overload the service interface, it should be treated as a case of P.O.CCCS.3, causing a non-propagating overload. Ideally, P.O.CCCS.3 should be modified so it doesn't arise when the service is the source of data, since in that case the overload is also non-propagating and P.O.CCCS.3 would be a duplicate threat.
If an intermediary acting as a service receives excessive requests from its client, and the intermediary forwards those requests to another service, it will forward the excessive requests - so the excessive request attack propagates in a client-to-service direction from the intermediary.
If an intermediary acting as a service receives excessive requests from its client, and the intermediary gets data from another client, it must wait for data to arrive before responding to any requests. This means the excessive request attack is not propagated in the service-to-client direction. There should be no effect on the intermediary, since it should not expensive (in storage or computation) to queue requests, or to assume previous requests expire if unfulfilled when a new request arrives.
If a client sends too much data to a service which is the destination for the data, the service will become overloaded by the need to process and/or store the data. This means P.O.CCCS.3 should be altered so it also doesn't apply when the service is the destination, since once again, it would then be a duplicate threat.
If a client sends too much data to an intermediary, and it acts as a client to forward the data to another service, then the excessive data attack propagates and the intermediary is not otherwise affected. If the volume is sufficient to overload the service interface, it should be treated as a case of P.O.CCCS.3 and would not then be propagated.
If a client sends too much data to an intermediary, and the intermediary forwards the data to another client, then it must store the excessive data while waiting for a data request from its client. In that case, the intermediary's storage capacity may be overloaded. This would lead to a loss of availability, but probably not of the whole intermediary process. The most likely response would be to stop accepting requests from the client, or accept the requests but discard the data which amounts to the same thing. Thus there would be a loss of availability in the inbound client channel only. The excessive data attack would not be propagated.
If a service sends too much data in response to a client request, and the client is the destination for the data, the client will become overloaded as it performs computation on and/or stores the data.
If a service sends too much data in response to a request from an intermediary, and the intermediary acting as a client forwards the data to another service, the excessive data attack propagates and the intermediary is not affected.
If a service sends too much data in response to a request from an intermediary, and the intermediary acting as a service forwards the data to its own client, it must store the excessive data while waiting for a data request from its client. As with the excessive data attack from a client, the outcome would be that the intermediary stops accepting more data, i.e., it shuts down the client channel to the service. The excessive data attack would not be propagated.

P.O.CCCS.3 is not currently sensitive to the network path over which excessive requests are sent, so it requires significant changes to include the possibility of control via a firewall policy.
P.O.DoS.3 is not specific to a malicious or impersonated client - the attack comes from anyone with access to a network from which the service can be accessed. However, an untrustworthy client only exists if an attacker can access the service as the client. This means either they are the (malicious) client, they compromised the client, or they can impersonate the client to the service. In all these cases they must have access to the service, so they can also cause P.O.DoS.3.
Conclusion - we don't really need P.O.CCCS.3, as it duplicates the attack captured (in a more general form) by P.O.DoS.3.

There is an issue with data relays. If a relay is not of type DB, then it simply forwards data, but it is considered to be a source and destination for flows of that data. The purpose of the relay (in system-modeller usage terms) is to 'pin' the flow of data so it goes through the relay and not via some shorter path that may exist between communicating processes.
To fix this, we need excessive request or excessive data attacks to propagate between different data flows to/from a relay. In doing this, the same restrictions apply as before, i.e., excessive requests and data received from a client only propagate to a service, while excessive data received from a service can propagate to clients or services of the relay.
Although the relay propagates these attacks from one data flow to another, both must be flowing in the same direction through the relay, i.e., both input flows or both output flows.

Summary of issues that need to be addressed:

[ ] Data relays (serving data stored elsewhere) should be made equivalent to an implicit relay (intermediary because it is on the shortest path).
[ ] DB services should not be able to act as transparent relays. They process queries, and it should be assumed they do this to determine what data request to forward.
[ ] A malicious data destination client can request an excessive amount of data. An intermediary client can do so only if the data flow does not have end-to-end cyrptographically protection - if present this is assumed also to protect data requests.
[ ] The request will propagate in a client-to-service fashion until it reaches the data source service which will become overloaded. If it first reaches an intermediary service that is not a client of the adjacent data source, the attack will propagate no further.
[ ] A data source client or service can send an excessive amount of data. The excessive data flow will propagate in a process-to-process fashion until it reaches the data destination, which will become overloaded. If it first reaches an intermediary service that is not a client of the adjacent data destination, the attack will propagate no further but the data flow will become unavailable.
[ ] An intermediary client or service can inject excessive amounts of data, unless end-to-end cryptographic protection is used.

In addition to threats modelling excessive data requests and data flows flow, the following must be reconciled:

[ ] P.O.CCCS.3 should be suppressed where the target is the source or destination of a data flow via the untrustworthy client, since in such cases the data flow overload threat would have the same effect.
[ ] P.O.CCCS.3 should not be suppressed where the target is an intermediary, since in that case the target would not become overloaded by simply forwarding excessive data flows or requests.


Exposures bins - patient table, 2016

This purpose of this issue is to obtain bin values for the following variables (patient table, 2016): EstResidentialDensity, EstHouseholdIncome, AvgDailyPM2.5Exposure_2, AvgDailyPM2.5Exposure_qcut, MaxDailyOzoneExposure_2, MaxDailyOzoneExposure_2_qcut. This is for a JACI manuscript I am developing with Dave Peden. Target submission date is December 4, 2020.

Let's find another venue for tracking tasks like this.


User cannot create an EKS cluster when the security group and subnets are specified

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Create a hosted EKS cluster
Give in the subnet and security group.
Cluster fails to come up with error: Waiting for API to be available; InvalidParameterException: Specified subnets must belong to cluster's vpc vpc-0a5f5c40d7990ec10 { RespMetadata: { StatusCode: 400, RequestID: "670bff0f-0eaf-447c-8aa6-c0b39d227014" }, ClusterName: "sowmya-eks-1", Message_: "Specified subnets must belong to cluster's vpc vpc-<>", NodegroupName: "sowmya-ng1" }

Expected Result:
User entered subnet and security groups should be used and cluster should come up successfully
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head commit id: ca3f705a4
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Hosted EKS
Kubernetes version (use kubectl version):

1.17

Verified on master-head - commit id: 6aef36313

Create a hosted EKS cluster
Give in the subnet and security group.
Cluster comes up successfully
Security group set on Rancher reflects as Additional security groups in EKS
Subnets set on rancher reflect under Subnets in EKS console.


Unsupported Tarball

Whenever I add FlakeHub dependencies to my flake config, If i run nix flake update, my config starts spitting out errors saying:

Upgrading to 2.18.1 should take care of that immediately: https://flakehub.com/docs#i-got-error-unsupported-tarball-input-attribute-rev-or--error-unsupported-tarball-input-attribute-lastmodified-what-do-these-errors-mean


Helpful error for when you don't provide a location.

Coverage decreased (-0.8%) to 60.577% when pulling da3a54f74fcc77da0bd4eaee717eba2d180aa2e2 on no-location into 457e7ad3bfe53e480633fb3fd8a8015e5b0d1e14 on master.


Randomly seeing red "xERROR"

Prerequisites

[x] I have read and understand the CONTRIBUTING guide
[x] I looked for duplicate issues before submitting this one

Description

This randomly happens, but I'm pretty sure it only happens in git repo's (thought I'm not 100% sure of that).
Environment

Oh my Posh version: 3.30.1
Theme: avit
Operating System: Windows 10
Shell: pwsh 7.0.3
Terminal: Windows Terminal

This shows when the last command output wasn't 0, meaning there was an issue with the previous command. This by design :-)

ah, thanks for clarifying.  keep up the awesome work :)

What might be a good idea for this theme is that I remove the error string and only show the red cross. That'll look better 😬


LGSVL Simulator change (part 1)

Add Borregas map

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Guodong Rong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

These might needs to be made as docker volume it you would like to contribute to Apollo, @xiaoxq @ycool Your thoughts?

These might needs to be made as docker volume it you would like to contribute to Apollo, @xiaoxq @ycool Your thoughts?

Thank you! These files are relatively small and I feel OK to check in directly :)

Could you sign the CLA so that we can merge the PR. Thanks!

Could you sign the CLA so that we can merge the PR. Thanks!

I clicked "details" beside license/cla, and clicked the button saying "sign in github to sign cla". Then it brings me back to this page, and nothing seems happened. :(
Can you guide me how to sign it correctly?

I click "details" beside license/cla now, it shows "You have signed the CLA for ApolloAuto/apollo". But this page still shows "Contributor License Agreement is not signed yet". Why?


Add collaborators to this repo

Comment below to be added as a collaborator
We will all be using this repository today. Even though it's public right now, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API. Once you comment, we will add you as a collaborator.
You'll start to receive a lot of emails. (❗) You can slow these down immediately by clicking the Unwatch button at the top of the page and selecting either the Participating and @mentions or Ignore option.

Hi

Hello 👋

Hello!

Hello

Hello

Hello

🚀👨🏼💻

Howdy 🙋♂

Hallå!

Hi there!

Hows it goin'?

Hello

Hi! :)


get IOError down to 24 bytes (#1355)

resolves #1355 shaving off 2 bytes from IOError struct
Modifications:
This one had a bit of a curveball.  Replacing StaticString shaves off one byte.  The other extra byte is saved by switching the order that the enum and Int32 properties are declared.  Seems like a compiler bug to me.
For example:
struct Good {
    enum FailureDescription {
        case function(String)
        case reason(String)
    }

    let reason: FailureDescription
    let errnoCode: Int32
}

struct Bad {
    enum FailureDescription {
        case function(String)
        case reason(String)
    }

    let errnoCode: Int32
    let reason: FailureDescription
}

print(MemoryLayout<Good>.size)
print(MemoryLayout<Bad>.size)

// 24
// 25

I'm curious now why that might be.
Result:
New condition:
print(MemoryLayout<IOError>.size) // 24

Hmm, I wonder where the enum discriminator went in the “good” case. The only excuse for shrinking this by one byte when FailureDescription is clearly 20 bytes wide is because the enum discriminator got stuffed somewhere in the Good case that it did not in the Bad, but I can’t really see why that optimisation wasn’t available in both cases.

First of all, thanks very much for this PR @realdoug ! As @Lukasa points out this is public API breaking right now. That's my mistake, I didn't quite appreciate how much we exported in our API here but I have a proposal how we can fix it all and remain API stable: Internally we just stop using the enum case that uses the StaticString and we can convert
public let reason: FailureDescription

to
private let failureDescription: String

public var reason: FailureDescription {
    return .reason(self.failureDescription
}

we should then also deprecate this init
public init(errnoCode: Int32, function: StaticString)

and rewrite it as
@available(*, deprecated, renamed: "init(errnoCode:reason:)")
public init(errnoCode: Int32, function: StaticString) {
    self.failureDescription = "\(function)"
}

Gotcha.  I figured you may want to paper over it somehow.  Pushed a new version w/ updates @Lukasa @weissi Int32 + String results in the correct 20 bytes.
It's worth noting that this implementation loses the information distinguishing between reason/function.  Perhaps that's ok, though if so, the enum & the computed var that returns it should be deprecated as well, right?
Alternatively, I could add a private Bool and conditionally return the correct FailureDescription value.  Or perhaps the correct solution is both: use a private bool and deprecate both the enum and the computed prop that returns it, and add a non-deprecated public accessor which returns a string.

Also, the deprecation causes many tests to emit warnings, which need to be cleaned up, but I wanted to validate the approach first.

@realdoug nice once! Great job! The information loss is okay, the old one was just there because in Swift before 5.0, Strings were very bad so StaticString made sense.
Regarding the warnings, can’t we just make NIO use reason:  everywhere instead of function:  ? I think that could be done with a big ol’ find&replace :).
We might want to add one single test which tests that the old function: still works. You can just deprecate the tests (you’ll find examples) then it won’t complain about it using deprecated functionality

@swift-nio-bot test this please

CI passed, that failure is a spurious perf test. So it’s all good from ky PoV apart from the copyright years

ah my bad @weissi copyright year is fixed now.

@swift-nio-bot test this please

@swift-nio-bot test this please

@swift-nio-bot test this please

@swift-nio-bot test this please

@swift-nio-bot test this please

Awesome!

Awesome!


Easy way to disable on small screens?

In my case the thumbnail images of 300px are already filling a phone screen, so the popup function is no advantage and probably a worse user experience.

The only immediate solution that comes to my mind is to not initialize the lightbox library when the screen is too small. That can be handled by your code that calls the imagelightbox. Know how to do it?

I could do with some help on that. I've never managed to get my head around javascript apart from making modifications to existing code.

I have a seperate JS file with a few jQuery bits in and have added this, which seems to work.
$(document).ready(function() {
    if ( $(window).width() > 600) {
        $( function() {
            $( '.lightBox a' ).imageLightbox();
        });
    }
});

Nice to hear that.


ARM64 Support: Pi

Love the container!
Was wondering if you had any plans for ARM64 images?

that will be great

The latest image is now multi-arch!


Public Use

Will you publish the tool here so that everyone can use it? With a guide  maybe?

Hey @bonxz
yep - still working on this. The project is just in its early stages. Leave me a star - there is more to come.
Cheers!

Nice. Would also like to test everything when it is approximately ready and could then give feedback. Would also be nice if you could put screenshots here, as it looks more or less ready

Hey @bonxz ,
I've just started to release distributions on every push to main. Yesterday I've released 1.0.1 which contains a node distribution. You should be able to set this up on your machine.
Here is a short instruction:
download the (compressed) tarball (here)and unpack it.
Run it with node
node dist/main.js --dataPath "./"
this should have created a config.json file in your project root.
You need to set this file up like this:
{
  "DISCORD": {
    "CLIENT_ID": "Discord Application OAuth2 Client ID",
    "CLIENT_SECRET": "Discord Application OAuth2 Secret"
  },
  "BASE_URL": "http://localhost:8080",
  "TOKEN_SECRET": "Some Secret Value",
  "PORT": 8080,
  "DATABASE": "database.db",
  "WEBAPP": {
    "COMPANY": {
      "NAME": "Your Company Name",
      "SERVER": "Your Server"
    }
  }
}

You will need a discord application (https://discord.com/developers/applications) and setup OAuth2 for this app
From there you can get your CLIENT_ID and CLIENT_SECRET. You will also need to register your local Redirect URL in there, just type http://localhost:8080/api/login/callback
After that restart your node application (node dist/main.js --dataPath "./") and everything should hopefully be working.
If there are any issues, feel free to ask :) glad if I can help and get some first feedback.
Beware... this is still early stages and the state is reaaaally messy still :)
Have a nice weekend

So I got the server up and running. I have also registered my Discord bot but when I try to log in via Discord it tells me that the OAuth redirect url is wrong.

What exactly should I enter in the URL?

Hey @bonxz
in the discord OAuth2 config I've got

You won't need the port 4200 as I only need this for local angular development. So that should seem fine.
Did you put the correct BASE_URL in your config.json ? It must be "http://localhost:8080", because the server will suffix this with /api/login/callback. So there should be no additional forward slashes or anything.
see https://github.com/cbartel/nw-company-tool/blob/753d579be11eac3d11667cfcc17b282eed18f3b5/server/src/service/discord.service.ts#L11)
You should also be able to see your redirect url in the URL when you are on the discord page (the page from your screenshot).
Hope this puts you in the right direction.

Okay I got it working. Somehow it didn't want to accept the callback url at first.
So I like the project very much. You have done a good job.
From the design it is so wanted that the window is on the left and not in the middle?
And I don't know if it's possible but maybe you can even show the avatar of the users next to the name via the Discord login.
I would still wish if you could also enter the Gearscore in the list.
Will there also be a war planning so in the way that you can log on / log off there. So that you can plan approximately in a war what you have everything with you and what you can still need with the people who are registered.
Optimal would be then even more values such as armor weight (light, medium, heavy) and what weapons you play.
I am curious what you still have planned for features. So far it helps me and my company to create a better overview in any case.

Hi Bonxz,
glad to hear it works!
Thank you very much for your feedback.
Regarding the positioning of the frontend components: I might rework the whole frontend as it is just a placeholder in the current state. I might even switch from angular material components to prime-ng, but I'm not quite sure yet. I think a centered box would look better, yes.
Showing the discord avatar is a good idea - I will have a look how and if I can get the discord image from the discord api.
Gearscore, favorite weapons, armor wight - good points :) will take that into account aswell.
I will mostly work on this tool on weekends.. unfortunately I am planning to work on more technical features first, as the basic app flow (in the PoC state as it is currently) runs quite well :)
For the next weeks I have planned the following things:

complete the user detail view (if you click on a character in the company table)
enable developers to write plugins/modules for this tool. I would love to use this features myself, so I don't create such a huge codebase and can split up functionality in smaller chunks
documentation on how to setup your own instance of nw-company-tool. Including an example on how to do this with a domain, a droplet (from digitalocean), nginx (with https) and pm2

Cheers :)

Yes don't stress about the updates. So far, everything is working very well. The following planned features also sound good. 👍🏼

I've updated the projects README with information about how to setup the tool. Closing this issue.


ALVR loses connection and is unable to regain it.

Description
ALVR after some time of playing completely freezes and the headset is unable to reconnect. The logs will say this on each attempt at reconnecting:
09:19:55.238679810 | [INFO] | ClientConnected
09:19:55.238867391 | [INFO] | Serial Number: 1WMGH000XX0000
09:19:55.238873562 | [INFO] | Model Number: Miramar
09:19:55.238877439 | [INFO] | Render Target: 2688 1440
09:19:55.238881928 | [INFO] | Seconds from Vsync to Photons: 0.005000
09:19:55.238885294 | [INFO] | Refresh Rate: 90
09:19:55.243840698 | [INFO] | Setting new IPD to: 0.063232
09:25:08.329056906 | [INFO] | ClientDisconnected
09:25:08.355546495 | [INFO] | Client disconnected. Cause: At alvr/sockets/src/control_socket.rs:32

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environement
Hardware
hw-probe
Audio:
pipewire
Installation
ALVR Version:
Latest nightly, 2022.01.25
SteamVR Version:
1.21.6
Install Type:

[ ] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[x] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
Arch Linux

This might be a network issue. Make sure your computer is connected via Ethernet to your Router/AP and that your Quest has a 5 GHz WiFi connection. It's not advised to use a shared Router/AP for this application.

It is connected directly with usb to my computer, and the logs show the client tries to connect but immediately disconnects as shown in the log snippet I attached to the issue.

Are you using a USBC to Ethernet adapter on the Quest or just using a regular USBC cable plugged into the USB port of your PC? If it's the latter, I don't think that's a supported method.

It is the latter one and it is mentioned on the wiki, and as I said I do not think the actual connectivity is the issue. Especially as when the "disconnect" happens it just has the stream completely freeze but the client does not disconnect. When restarting the app it stays on "Searching for server" with those messages appearing in the log. A full SteamVR restart is required for it to start working again.

Apologies, I was unaware of the USB method.
Does SteamVR show any errors or does it continue working as expected, just disconnected from the Headset?

SteamVR does not display any errors, tracking is lost as expected due to the client being disconnected.

By looking at the source code, it seems like something goes wrong with receiving the packets at ControlSocketReceiver::recv.


Malloy as a library doesn't work

Hello,
I'm trying to use the npm package and follow the documentation but I've got an error at the execution.
import { Runtime } from "@malloydata/malloy";
import { DuckDBConnection } from "@malloydata/db-duckdb";

const connection = new DuckDBConnection("duckdb-example");
const runtime = new Runtime(connection);

runtime.loadModel("source: flights is table('duckdb:data/flights.parquet')")

const runner = runtime.loadQuery("query: flights->{group_by: flight_num}")
runner.run() // <- executes query, returns JSON of results

(base) nabil in ~/project/monplein/prototype2 on main ● ● λ node index.mjs
/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:75
                    throw new MalloyError(`Error(s) compiling model:\n${errText}`, errors);
                          ^

MalloyError: Error(s) compiling model:
FILE: internal://internal.malloy
line 1: Undefined source 'flights'
  | query: flights->{group_by: flight_num}
  |        ^
    at Malloy.compile (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:75:27)
    at ModelMaterializer._materialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1283:27)
    at ModelMaterializer.rematerialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1464:34)
    at ModelMaterializer.materialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1459:25)
    at QueryMaterializer._materialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1494:32)
    at QueryMaterializer.rematerialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1464:34)
    at QueryMaterializer.materialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1459:25)
    at PreparedResultMaterializer._materialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1745:32)
    at PreparedResultMaterializer.rematerialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1464:34)
    at PreparedResultMaterializer.materialize (/Users/nabil/project/monplein/prototype2/node_modules/@malloydata/malloy/dist/malloy.js:1459:25) {
  log: [
    {
      at: {
        url: 'internal://internal.malloy',
        range: {
          start: { line: 0, character: 7 },
          end: { line: 0, character: 14 }
        }
      },
      message: "Undefined source 'flights'"
    }
  ]
}

Node.js v18.8.0

It appears that documentation is incorrect. Here's an updated version:
import { Runtime } from "@malloydata/malloy";
import { DuckDBConnection } from "@malloydata/db-duckdb";

const connection = new DuckDBConnection("duckdb-example");
const runtime = new Runtime(connection);

const runner = runtime
  .loadModel("source: flights is table('duckdb:data/flights.parquet')")
  .loadQuery("query: flights->{group_by: flight_num}")
runner.run() // <- executes query, returns JSON of results

Ah actually I found where that snippet was. It was incorrect, and has since been updated: https://github.com/looker-open-source/malloy/commit/4435680508647933e69cf3d6f1d0099a53f9ca53. Sorry for the confusion.

Thanks, I forgot to specify where I found the code.
Is the npm page of malloy will be updated ?
Now I have a segfault but it's an another error.
(base) nabil in ~/project/monplein/prototype2 on main ● ● λ node index.mjs
[1]    91358 segmentation fault  node index.mjs

I believe we will be updating the NPM page soon @whscullin?
The segfault looks like https://github.com/looker-open-source/malloy/issues/798

Thanks for the clarification. Now it works as attended.

I've updated the npm packages so the docs on npmjs.com are now up to date, as well.


[desktop_webview_window] is it possiable support runJavascriptReturningResult

I want to catch html from webview on windows destop.
is it possible support :
https://pub.dev/documentation/webview_flutter/latest/webview_flutter/WebViewController/runJavascriptReturningResult.html
or is there have other solution ?

https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-1.0.1020.30#executescript
According the document, the answer should be yes.
But this plugin haven't implement this yet.

Is it possible add this function?


font.com request gives 404

I'm using your suggested configuration like so:
import WebFont from 'webfontloader'

WebFont.load({
	monotype: {
		projectId: 'xxxxxx-xxxx-xxxxxx-xxxx-xxxxxxxxxxx',
		loadAllFonts: true,
	}
})

And the browser is making a request to https://fast.fonts.net/jsapi/xxxxxx-xxxx-xxxxxx-xxxx-xxxxxxxxxxx.js that always gives a 404.
The sample code for the project which I download from fonts.com (which is not using webfontloader) works like a charm so the fonts.com project-id itself seems to work.
Is there something additional configurations to fonts.com I need to do in order to use webfontloader that is not documented here?
(Adding domains etc. seems to have been a thing in the past because fonts.com marks those guides as legacy now.)

I'm having the same issue.


DbContext Injection per request

Hi!
I'm trying to inject a DbContext in validator class like in code below:
public class MyCommandValidator : AbstractValidator<MyCommand>
{
        private readonly MyDbContext _dbContext;

        // Inject dbContext per request
        public MyCommandValidator(MyDbContext dbContext)
        {
            // Pass just once here, cause of singleton cache:
            _dbContext = dbContext;

            // More rules here...

            // _dbContext is disposed at second time:
            RuleFor(p => p.Email).Must(email => !_dbContext.Customers.Any(p => p.Email == email));
        }
    }

    public class AutofacValidatorFactory : ValidatorFactoryBase
    {
        public override IValidator CreateInstance(Type validatorType)
        {
            // Pass just once per type:
            return DependencyResolver.Current.GetService(validatorType) as IValidator;
        }
    }
```

There's any way to disable or override the cache like asked in here without touch source code? http://stackoverflow.com/questions/30572472/how-to-prevent-fluentvalidation-from-caching-the-validator-class

Thanks!

I wouldn't recommend doing it like this - validators are designed to be instantiated just once, rather than by request.
Rather than injecting the DbContext directly, a better approach would be to inject a Func which would then be invoked to retrieve a request-specific DbContext. This way, the lifecycles of the validator and the context aren't tied to gether, so the validator can still be a singleton, and the DbContext can be per-request.
Hope that makes sense

Thanks for the answer @JeremySkinner!
Yep, it really makes sense!
I've already tried to inject the Func via Autofac, but it shows the exception on second time validation:
var builder = new ContainerBuilder();

builder.RegisterType<MyDbContext>().InstancePerRequest();
builder.Register<Func<MyDbContext>>(c =>
{
    var scope = c.Resolve<ILifetimeScope>();
    return () => scope.Resolve<MyDbContext>();
});

Additional information: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.

Maybe something wrong with my config. I will try more and tell you here!
But anyway, I think that when implenting a custom IValidatorFactory, the lifetime control of validators should be responsability of this custom implementation. Don't you agree?
Thank you again!

Hi @JeremySkinner,
I've changed the Func registration and it's working now.
builder.RegisterType<CeciexContext>().InstancePerRequest();
builder.Register<Func<CeciexContext>>(c =>
        () => DependencyResolver.Current.GetService<CeciexContext>());

Thank you!


Importing all wallets into final build and increasing the build size.

Hello,
So, in code while doing this import, it should only import these three wallets. But yarn analysing final build is showing blocto wallet, torus wallet and all others and increasing the app size a lot. Is there any way to reduct the final build size of apps using this wallet adapter?
import {
  getPhantomWallet,
  getSolflareWallet,
  getSolletWallet,
} from "@solana/wallet-adapter-wallets";

Can you say more about your project environment and build setup? If your transpiler is set up for tree shaking, this shouldn't happen.

I'm new to react or js. So, can't answer that. Basically I cloned this repo and did
yarn install
yarn build

Then the build size in 13MB. I added GENERATE_SOURCEMAP=false in build scripts to remove source map to reduce the size to 3MB.
Then I followed this to analyse the build. Attached analyse screenshot.

Do you suggest I need to do yarn eject to configure those things as mentioned in that repo? Any doc or blogpost how I can set tree shaking for this kinda project to get going?

Thanks for the additional detail, I'll look into this.

This is fixed by https://github.com/solana-labs/wallet-adapter/commit/6d9c3a7e23c7dc7bad2234e828400571634fdc8b and has been published as a minor (breaking change) release to the affected packages.
The change that broke tree shaking was for https://github.com/solana-labs/wallet-adapter/issues/4 but I think the starter projects provide reasonable ways to get transpiling of modules working now.

Thanks will try. Dunno why github not giving mails/notifs.

Hello @jordansexton, I've removed node modules, changed the version of this package to 0.10.0 in package.json of the repo I've used. But still build consists all these wallets. Am I doing this right?

Can you mention more about what your project structure / build toolchain looks like? The build now exports esnext modules, so tree shaking should work out of the box for most build systems.

I've cloning this repo - https://github.com/exiled-apes/candy-machine-mint, changing version of wallet adapter from 0.9.0 to 0.10.0 and then doing
yarn install
yarn build

And then doing yarn analyze as mentioned above.

Cool, thank you for providing those steps. I'll do the same tomorrow and check it out.

So I repeated this. Here's an interesting result:

I'm seeing the dependencies of the torus and blocto wallet adapters, for example, but @solana/wallet-adapter-* is missing from the node_modules shown.
 on the right, I see:

This is showing a src directory with .ts/.tsx files, not the JS files that are actually used in the build -- it must be using the sourcemap.
If I search the generated build/static/js directory for "blocto", I see the Blocto SDK is being included -- but the blocto package with the adapter is not. Same with "torus".
This indicates to me that the sub-dependencies of the adapters are being included, but the tree shaking is working for the adapters. I'll see what can be done to fix this.

So I repeated this. Here's an interesting result:

I'm seeing the dependencies of the torus and blocto wallet adapters, for example, but @solana/wallet-adapter-* is missing from the node_modules shown.
 on the right, I see:

This is showing a src directory with .ts/.tsx files, not the JS files that are actually used in the build -- it must be using the sourcemap.
If I search the generated build/static/js directory for "blocto", I see the Blocto SDK is being included -- but the blocto package with the adapter is not. Same with "torus".
This indicates to me that the sub-dependencies of the adapters are being included, but the tree shaking is working for the adapters. I'll see what can be done to fix this.

This has been implemented by converting the core and wallet packages to ESM with sideEffects: false to improve tree shaking. Adapters like Torus, Blocto, and Sollet still require loading third party deps, but these will only be included if used in your application.

Published:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>


suggestion for the protocol - make 12 the minimum number of witnesses rather than the exact number

The whitepaper explains that the choice of 12 witnesses is somewhat arbitrary.

The above means that each unit must list its witnesses so that they can be compared. We require that the number of witnesses is exactly 12. This number 12 was selected because:

it is sufficiently large to protect against the occasional failures of a few witnesses (they might prove dishonest, or be hacked, or go offline for a long time, or lose their private keys and go offline forever);

it is sufficiently small that humans can keep track of all the witnesses to know who is who and change the list when necessary;

the one allowed mutation is sufficiently small compared with the 11 unchanged witnesses.

So, the reasons for it being large are to protect the overall reliability of the network, the reasons to keep it small are to make it easier for humans to understand and come to a consensus on who the witnesses should be.
It seems that 12 is already deemed an acceptable minimum for network reliability, and can be a minimum enforced by the protocol.
Why not let the maximum be set by humans?

First, what's the point?
Second, how would it look like? what would the 1-mutation rule be like? how the majority would be defined?
No doubt, more flexibility means more complexity, greater attack surface.  It must be justified.

@tonyofbyteball yes that's fair.
the point is to try and make the system of witnesses naturally more decentralised by making the pool of witnesses larger.
personally i think a lot of the difficulty changing witnesses currently comes from the wallet UI rather than the protocol (see linked issue), but this issue is a summary of discussions that have been happening in slack.

As I understand it... This at first may sound like a way to allow a wallet to improve protection as needed, but it could actually also allow for a detrimental concentration of poorly selected witnesses along a particular chain. Seeing as the network as a whole allows an unlimited number of witness, having this 12+1 limit per wallet keeps things flexible and evolving, yet modulated; so witness influence (or possible collusion) is kept consistently inconsequential across the network. The current witness and finality rules are simple, elegant and deliver mutually safe chains.

@SY-MEDIA you are correct in theory, but please also see https://github.com/byteball/byteball/issues/175

Since there is a 1-permutation rule, would you not (across the whole network) already have your wish anyway?   A particular user sees only their list of 11 + 1 , but if many users (perhaps by industry, geographic region, brand, celebrity, local tx performance, sports team, etc.) have their own preferred '+1' then the result across the whole network is that there is no upper limit of transaction order witnesses providing their view of the order of events on the DAG.


Add tilt support

This PR fixes #33
Works for me with Kamvas Pro 16

Thank you very much. I can't try it with my tablet, but LGTM.


only take RTT samples for retransmittable packets

see https://github.com/quicwg/base-drafts/pull/2078

Turns out that we're already doing this, since we're only saving retransmittable packets to the packetHistory:
https://github.com/lucas-clemente/quic-go/blob/3d2d45d53ff9d48b29d8a44c88555ab67912be03/internal/ackhandler/sent_packet_handler.go#L133-L136
If no packet is saved, we won't take an RTT sample:
https://github.com/lucas-clemente/quic-go/blob/3d2d45d53ff9d48b29d8a44c88555ab67912be03/internal/ackhandler/sent_packet_handler.go#L290-L299


What version of jongo for mongo driver version? Compat chart?

We are currently on Jongo 0.4, mongo driver 2.13. We are looking to move to the Mongo 2.14 or 3.2 driver. Which version of Jongo should we be using? Is there a compatibility chart somewhere?

Sorry for the late response.
We have a CI job to test Jongo against multiple driver versions and Mongo 2.6/3+ : https://jongo.ci.cloudbees.com/job/jongo-test-mongo-versions
Here is the results of the last execution :
Running tests against java driver 3.0.1 and MongoDB 2.6
3.0.1 SUCCESS
Running tests against java driver 3.0.2 and MongoDB 2.6
3.0.2 SUCCESS
Running tests against java driver 3.0.3 and MongoDB 2.6
3.0.3 SUCCESS
Running tests against java driver 3.0.4 and MongoDB 2.6
3.0.4 SUCCESS
Running tests against java driver 3.0.5-SNAPSHOT and MongoDB 2.6
3.0.5-SNAPSHOT SUCCESS
Running tests against java driver 3.1.0 and MongoDB 2.6
3.1.0 SUCCESS
Running tests against java driver 3.1.0-rc0 and MongoDB 2.6
3.1.0-rc0 SUCCESS
Running tests against java driver 3.1.1 and MongoDB 2.6
3.1.1 SUCCESS
Running tests against java driver 3.2.0 and MongoDB 2.6
3.2.0 SUCCESS
Running tests against java driver 3.2.0-rc0 and MongoDB 2.6
3.2.0-rc0 SUCCESS
Running tests against java driver 3.2.1 and MongoDB 2.6
3.2.1 SUCCESS
Running tests against java driver 3.2.2 and MongoDB 2.6
3.2.2 SUCCESS
Running tests against java driver 3.3.0-SNAPSHOT and MongoDB 2.6
3.3.0-SNAPSHOT SUCCESS
-------------------------------
Running tests against java driver 3.0.1 and MongoDB 3.0
3.0.1 SUCCESS
Running tests against java driver 3.0.2 and MongoDB 3.0
3.0.2 SUCCESS
Running tests against java driver 3.0.3 and MongoDB 3.0
3.0.3 SUCCESS
Running tests against java driver 3.0.4 and MongoDB 3.0
3.0.4 SUCCESS
Running tests against java driver 3.0.5-SNAPSHOT and MongoDB 3.0
3.0.5-SNAPSHOT SUCCESS
Running tests against java driver 3.1.0 and MongoDB 3.0
3.1.0 SUCCESS
Running tests against java driver 3.1.0-rc0 and MongoDB 3.0
3.1.0-rc0 SUCCESS
Running tests against java driver 3.1.1 and MongoDB 3.0
3.1.1 SUCCESS
Running tests against java driver 3.2.0 and MongoDB 3.0
3.2.0 SUCCESS
Running tests against java driver 3.2.0-rc0 and MongoDB 3.0
3.2.0-rc0 SUCCESS
Running tests against java driver 3.2.1 and MongoDB 3.0
3.2.1 SUCCESS
Running tests against java driver 3.2.2 and MongoDB 3.0
3.2.2 SUCCESS
Running tests against java driver 3.3.0-SNAPSHOT and MongoDB 3.0
3.3.0-SNAPSHOT SUCCESS

I'm going to run theses tests against the versions you are targeting

Thanks, might be good to have a simplified chart on the main README as well. thanks!


Support unencrypted email usage during development only.

Context:

Rauthy forces TLS connections right now. It tries "real" TLS first and will try again with a downgrade to STARTTLS, if this fails. It will never allow plaintext, because it should really never be used in a real deployment.

This works great and, indeed, real production / staging deployments should always be encrypted, but would it be possible to support plaintext only during development? The can be 100% tied to DEV_MODE to prevent any accidental configuration mishaps.
Use case:
Running Rauthy via docker compose with "throw away" containers and local SMTP via something like MailHog, or MailDev allows for a tighter feedback loop during development. This includes testing user registration flows / API key setups / magic links and data storage.
Expected result:
When DEV_MODE is set to true in Rauthy config, it should be possible to configure Rauthy to use local SMTP (even if non-encrypted)
Actual result:
Rauthy attempts to connect a few times and fails and then the container exits.

That's not a big deal actually. I will not tie it to DEV_MODE, because this does quite a bit more stuff with DB migrations and so on under the hood which might not be what you want in that case.
As I am thinking about it, this could actually come in handy in some deployment scenarios. For instance if someone is not using the container image but maybe the binary directly on the host. In this case the unencrypted localhost relay would be safe in production.
I could add a new config var which will try an unencrypted connection to an SMTP relay running on your localhost port 25 by default without any further configuration. Would that fit your need?

I implemented this in #246 .
Do you have a local Rust dev setup and are you able to start the current main branch locally for testing? That would speed up things quite a bit, because I would not need to run the whole nightly-container pipeline otherwise, which takes almost 1 hour to complete on the current machine.
I added just recipes just maildev-start and just maildev-stop for local testing and updated the E-Mail section in the config quite a bit:
#####################################
############# E-MAIL ################
#####################################

# Will be used as the prefix for the E-Mail subject for each E-Mail
# that will be sent out to a client.
# This can be used to further customize your deployment.
# default: "Rauthy IAM"
EMAIL_SUB_PREFIX="Rauthy IAM"

# Rauthy will force TLS and try a downgrade to STARTTLS, if
# TLS fails. It will never allow an unencrypted connection.
# You might want to set `SMTP_DANGER_INSECURE=true` if you
# need this for local dev.
#SMTP_URL=
#SMTP_USERNAME=
#SMTP_PASSWORD=
# Format: "Rauthy<EMAIL_ADDRESS>#SMTP_FROM=

# The number of retries that should be done for connecting to
# the given SMTP_URL.
# When these retries are exceeded without success, Rauthy will
# panic and exit, so no E-Mail can get lost silently because of
# a missing SMTP connection.
# default: 3
SMTP_CONNECT_RETRIES=3

# You can set this to `true` to allow an unencrypted and
# unauthenticated SMTP connection to an SMTP relay on your localhost
# or for development purposes.
# When set to `true`, `SMTP_USERNAME` and `SMTP_PASSWORD` will be
# ignored and you can modify the target port with
# `SMTP_DANGER_INSECURE_PORT`.
# default: false
SMTP_DANGER_INSECURE=true

# The port for an insecure SMTP relay.
# This will most likely be used for testing only.
# It will only be taken into account if `SMTP_DANGER_INSECURE=true` is set.
# default: 1025
#SMTP_DANGER_INSECURE_PORT=1025

It is working like expected so far. I started with allowing it on localhost only, but that would not work when using docker compose obviously, so now there is SMTP_DANGER_INSECURE=true, properly named with DANGER, because it would basically allow an insecure connection to any host.
This is merged into the current main branch and if you could test this in your site directly, it would be nice.
I explained a bit in the CONTRIBUTING.md how to get it running in local dev mode.

Nvm about the local Rust setup on your side. I have some free resources on a machine on the side and just started a nightly pipeline. I ~45 - 60 minutes, you can test with a nightly container image directly.

If you want to use a local SMTP relay for testing E-Mails, there are just recipes for maildev:

Just FYI there's a cool Rust alternative for this as well, which reached v1.0 just a week ago: https://github.com/tweedegolf/mailcrab/

Just FYI there's a cool Rust alternative for this as well, which reached v1.0 just a week ago: https://github.com/tweedegolf/mailcrab/

Oh that's really cool. I did not know about this.
Will change the recipes with the next release because I like keeping everything Rust only.

You can use the new nightly images for testing the changes:
ghcr.io/sebadob/rauthy:0.20.2-20240118

ghcr.io/sebadob/rauthy:0.20.2-20240118-lite

Thanks so much for the super fast turn around and the comprehensive additions!
I believe everything should be sorted for cases where you want to run the binary directly or when you run the docker image directly on the host (using the host network)
One last quality of life improvement is to allow docker compose internal DNS resolution to work. Here's what I mean by this. In docker-compose.yml
 maildev:
      image: maildev/maildev
      ports:
        - "1080:1080"
        - "1025:1025"

  rauthy:
    image: ghcr.io/sebadob/rauthy:0.20.2-20240118
    ports:
       - '8080:8080'
       - '9090:9090'
    volumes:
      - ./rauthy/data/:/app/data
    environment:
      - SMTP_URL=maildev
      - SMTP_DANGER_INSECURE=true
    depends_on:
      - maildev

SMTP_DANGER_INSECURE and SMTP_URL are sort of incompatible here because I want to use maildev as the URL (which docker compose would resolve to the maildev container.
If I was running everything on the same host network I wouldn't have this problem. But... it's nice to have things isolated from each other unless it's actually needed.
In other words, when I set  SMTP_DANGER_INSECURE to true, the "host" (as in the url host) for SMTP seems to not use the SMTP_URL option if I'm reading this correctly and seems set to a fixed value of localhost
https://github.com/sebadob/rauthy/blob/main/rauthy-models/src/email.rs#L547-L574
Can this respect the SMTP_URL and maybe have that default to localhost if that's needed. That way I can set the SMTP_URL  to maildev or mailcrab or whatever local SMTP server I have as a named service in docker compose and it would resolve to that. Note the the SMTP port stuff is not related here. That part seems OK, this just about the host part of the url.
Thanks again!

Oh yeah, that's my bad. The first version was restricted to localhost only, but then I wanted to change it to make it work with docker compose and other hosts too.
But, I simply forgot to switch the hardcoded localhost to the SMTP_URL. My bad, sorry. I will build a new nightly with the change, then it should be fine.

You can check again with the new nightly, which respects the SMTP_URL for insecure relays:
ghcr.io/sebadob/rauthy:0.20.2-20240119

ghcr.io/sebadob/rauthy:0.20.2-20240119-lite

Magic, thanks a ton!
This is fully resolved on my end and the issue can be closed (I'll leave that to you)


Update dev-dependencies to satisfy npm audit

Time to stop supporting older versions of node... ;-)

@JacoKoster sorry I didn't give you any ACK, I saw it and I thought 🤔 "Not sure about forcing a major release dropping node support because of dev dependencies"

@ziluvatar How do you want to proceed? Shall i make it mergeable again?

I think just leave it as is for now. At the very moment we drop v4 support I/you can resolve the conflicts and merge.

Closing this as stale. When we decide to drop specific node version support with a major update we'll address dev deps.


Adding support to mapping Persistent Volume Claim

The idea is support mapping Persistent Volume Claim when you upgrade or install using myvalues.yaml

/assign @pmuir

/ok-to-test
/approve


feat: SRG validation as default query

Introduction
resolves #107
This branch already uses the changes introduced in #124
Technical solution after this PR

A default query has been integrated to automatically fetch validation results from Dynatrace.
Each entry in the validation results table now includes a direct link that opens the Site Reliability Guardian (SRG) view.

When there are no validation results to display, an empty screen will now appear promoting the Site Reliability Guardian.

:heavy_check_mark: Common checklist

[x] Added tests for new functionality and regression tests for bug fixes
[x] Screenshots of before and after attached (for UI changes)
[x] Added or updated documentation (if applicable)
[x] Helpful resources linked (if applicable)

Note: Merged the Branch https://github.com/blasget/backstage-plugin/tree/CA-11418-Define-custom-DQL-queries-within-catalog-info into this one, so both have the same changes now. Will close one PR later on.


LlavaNext Model cannot be started

System Info
image: ghcr.io/huggingface/text-generation-inference:sha-40213c9
model: https://huggingface.co/llava-hf/llava-v1.6-34b-hf
Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
...
17T07:25:20.920584343Z [rank0]:   File "/opt/conda/lib/python3.10/site-packages/text_generation_server/utils/weights.py", line 112, in get_sharded

17T07:25:20.920592356Z [rank0]:     filename, tensor_name = self.get_filename(tensor_name)

17T07:25:20.920599543Z

17T07:25:20.920606030Z [rank0]:   File "/opt/conda/lib/python3.10/site-packages/text_generation_server/utils/weights.py", line 63, in get_filename

17T07:25:20.920613791Z [rank0]:     raise RuntimeError(f"weight {tensor_name} does not exist")

17T07:25:20.920621329Z

17T07:25:20.920627955Z [rank0]: RuntimeError: weight language_model.suffix.weight does not exist

Expected behavior
working on sha-eade737 but broken on sha-40213c9.  Is cuda-graph not yet supported for llavanext? Both images will report errors if cuda-graph is enabled or the input image is not a square picture.

same issue， have you resolved?  @paulcx

same issue， have you resolved?  @paulcx

No, I haven't.


Check for nullptr when unloading model

Ensure that model state pointer is not null when unloading model to prevent segfault on failed load

@divyegala Could I trouble you for a quick look at this one? It's a very small change which ensures a graceful exit for model load failure at a specific point.


some games missing

I tried to keep an overview of what I have with
lgogdownloader --list-details --language all --platform all --ignore-dlc-count .

recently that stopped working correctly.
Now I have some entries twice, e.g.
gamename: alien_nations
        path: /alien_nations/setup_alien_nations_2.05_hotfix_(21104).exe
        path: /alien_nations/setup_alien_nations_2.05_hotfix_(french)_(21104).exe
        path: /alien_nations/setup_alien_nations_2.05_hotfix_(german)_(21104).exe
        path: /alien_nations/extras/alien_nations_manual.zip
        path: /alien_nations/extras/alien_nations_wallpaper.zip
        path: /alien_nations/extras/alien_nations_soundtrack.zip
gamename: alien_nations
        path: /alien_nations/setup_alien_nations_2.05_hotfix_(21104).exe
        path: /alien_nations/setup_alien_nations_2.05_hotfix_(french)_(21104).exe
        path: /alien_nations/setup_alien_nations_2.05_hotfix_(german)_(21104).exe
        path: /alien_nations/extras/alien_nations_manual.zip
        path: /alien_nations/extras/alien_nations_wallpaper.zip
        path: /alien_nations/extras/alien_nations_soundtrack.zip

but others are missing, e.g. dark_queen_of_krynn or all heroes of might and magic games.
I guess it could be a bug on the server side, but on the GOG webpage the games are listed correctly. The count is correct, i.e. 24 are duplicate and 24 are missing.

Does --list show the missing games?

I just tried --list and got 14 less games than I have, of which another 35 were listed duplicately, so 49 games were missing completely.

I have a rather large collection (> 2000 games), perhaps that's why other people don't see this issue? Is there a bug report I can file at GOG about this, what should I say there?

Lets see if the json response from server has duplicates before lgogdownloader tries to parse it.
Are there duplicates in the output of this:
curl --cookie ~/.config/lgogdownloader/cookies.txt  "https://www.gog.com/account/getFilteredProducts?hiddenFlag=0&isUpdated=0&mediaType=1&sortBy=title&system=&page=1" -o - | json_pp | grep slug
json_pp should be part of perl or libjson-pp-perl package

That particular command gives me 100 different games (but of course, I have 20 more pages...). So I tried:
for i in $(seq 1 22); do curl --cookie ~/.config/lgogdownloader/cookies.txt "https://www.gog.com/account/getFilteredProducts?hiddenFlag=0&isUpdated=0&mediaType=1&sortBy=title&system=&page="$i -o -  | json_pp | grep slug > $i.txt; done

and see
$ cat *txt | wc -l
    2175
$ cat *txt | sort -u | wc -l
    2175

so this looks ok. Is lgogdownloader downloading them all directly after one another, or are there perhaps pauses in between that makes GOG re-sort them?

lgogdownloader should download them directly after one another unless --wait is used.
The result makes me think that something goes wrong when lgogdownloader is parsing the json reponse.
Enable debug info printing by building lgogdownloader with cmake .. -DCMAKE_CXX_FLAGS="-DDEBUG=1"
This makes it print the json response to stderr.
Redirect stderr output to file and see if there are duplicates
$ ./lgogdownloader --list 2> debug.txt
$ grep "\"slug\"" debug.txt | sort

Right now this looks good:
# grep "\"slug\"" debug.txt | sort | wc -l
    2171
# grep "\"slug\"" debug.txt | sort -u | wc -l
    2171

Comparing it with the curl output from above: the grep above was not good enough and also matched the four metal slug games "url" entries, so it matches the curl output.

So it gets valid info but something goes wrong with it later.
Try adding this after line 275 in src/website.cpp
std::cerr << "game.name = " << game.name << std::endl;

and check if the amount of games matches the previous output from curl
$ lgogdownloader --list 2> debug.txt
$ grep "game\.name" debug.txt | sort -u | wc -l

I checked this out too with my library; my GOG library on https://www.gog.com/account says that I have 1855 games.
OS: CentOS Linux release 8.1.1911 (Core), Boost 1.66
curl:
$ for i in $(seq 1 19); do curl --cookie ~/.config/lgogdownloader/cookies.txt "https://www.gog.com/account/getFilteredProducts?hiddenFlag=0&isUpdated=0&mediaType=1&sortBy=title&system=&page="$i -o -  | json_pp | grep slug > $i.txt; done
$ cat *.txt | wc -l
1959
$ cat *txt | sort -u | wc -l
1866

lgogdownloader (debug build):
$ lgogdownloader --version
LGOGDownloader 3.5.0a7648d
$ lgogdownloader --list 2> debug.txt
$ grep "\"slug\"" debug.txt | sort | wc -l
1855
$ grep "\"slug\"" debug.txt | sort -u | wc -l
1855

the patched debug executable is currently running, will add this information, as it is finished.

Something went wrong:
diff --git a/src/website.cpp b/src/website.cpp
index a83fe44..46b9f17 100644
--- a/src/website.cpp
+++ b/src/website.cpp
@@ -273,6 +273,7 @@ std::vector<gameItem> Website::getGames()
                     }
                 }
                 games.push_back(game);
+               std::cerr << "game.name = " << game.name << std::endl;
             }
         }
         i++;

and then:
lgogdownloader --list 2> debug2.txt

gives me only ~80kB:
Getting game names (1/22) 1 / 100
...
Getting game names (22/22) 71 / 71

I forgot that the progress info printing on line 174 manipulates the cursor position.
You should either change line 174 to use std::cout instead of std::cerr and use the previous command to redirect stderr to file
lgogdownloader --list 2> debug.txt

or use std::cout for the debug info printing on line 275 and redirect stdout to file
lgogdownloader --list > debug.txt

Hm, looks good:
# grep "game\.name" debug3.txt | sort -u | wc -l
    2171

It's currently working again, let's assume it was server-side.


code is not editable

Once i run a code in editor it runs...but after that when i need to run other code old code doesn't edit

Thanks, @sudhir512kj. What browser were you using and which URL were you visiting?

I am using Mozilla Firefox latest version in ubuntu 16.04 .. i was trying .net on browser

@jonsequitur did you get my problem and its solution

This looks like the same issue as #17.

@jonsequitur

yes i think you are right... @jonsequitur that looks same like this issue...so what is the solution for this


Out of the box, hitting the main endpoint with https:// redirects to http:// endpoints

I've configured a separate load balancer to handle https://.  But when trying to login and clicking any links in the UI, the app is specifying http:// endpoints.  Since I've blocked port 80 access on my 3rd party load balancer, the app doesn't work other than the main page.
Is there a way to make the redirects/links relative so they don't specify http?

May need to add some sort of rewrite to force https://
My Cachet page seems to be behaving the same way, however my domain is HSTS preloaded so it forces https at the browser level.
What type of load balancer are you utilizing? Haproxy or something?

@djdefi I'm using an amazon ELB.  So unfortunately, not much rewrite-ability.

It may be something that can be added to the docker image / nginx config there. I have seen some other docker images have a flag to specify when using HTTPS or something similar.

@ryanwalls If you are using a load balancer probably you need configure you trustedproxies, you can do it on config/trustedproxies.php

Also expressing interest in this. It's pretty important to be able to use https in front of cachet.

@jessesanford did the suggestion that @joecohens gave above help?

Master has been updated in #43 to utilize an external nginx container, which allows you to modify the nginx configuration. Hopefully this will help to get around this issue.

Closing this as nginx config is now external.


Missing chapters/content

We will need the chapters/content on the following:

saving mechanisms in SpaDES
internal module plotting using using Plots and Plot
SpaDES.experiment -- with words of caution about seeds. a commented draft exists in the LandR chapter, but a separate chapter is needed
documentation -- metadata (sort of covered, but best practices etc) + module manuals + model/workflow manuals (point to LandR example and bookdown, maybe Quarto?)
sourceURL and extractURL.

see also #28


Add affilbox.cz CNAME tracker

Found on top4football.com
https://affil.top4football.com/t3.js (=> cz.affilbox.cz)
affilbox.cz is blocked by both EP and AGTPF: https://www.affilbox.cz/ (apparently Czech affiliate provider)

These two domains only.


Add Text To Speech

Add text to speech on responses, handling the silent flag too. Probably using Google API's.

The native Android one should be able to handle this, something like
public static void speakResponse(String response) {
     TextToSpeech tts = new TextToSpeech(MainActivity.this, null);
     tts.setLanguage(Locale.US);
     tts.speak(response, TextToSpeech.QUEUE_ADD, null);
}

Yeah, that's what I was thinking of. I wanted to explore open source alternatives first but I don't think I'll find anything as good.

Now implemented.


chore: route for isSignedIn

Fixes #65
Short description of what this resolves:
route for checking if a user is signed in or not using isSignedIn.
Checklist

[x] My branch is up-to-date with the Upstream master branch.
[x] The acceptance, integration, unit tests and linter pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

please resolve conflicts @Utkarsh1504

@iamdevvalecha resolved


Improve Setup Wizard

Fix language and translation throughout Setup Wizard
Fix #252 double modal issue
Fix settings tab not looking for URL hash
Fix undefined JS functions in Setup Wizard
Fix setup prompt appearing in Setup Wizard
Remove automatic setup for public sites
Remove unused setup template
Change setup step 1 modal to explicitly describe what happens, required attribute
Move <script> tag JS to external file and load on Setup Wizard

Addresses #408

@jeffreylees - Added you here for a review of the documentation that I changed. All in-line, let me know if it's hard to read or if you'd rather see it in-place on a demo site.

👍 from docs in Slack for "Standard"


Localize infographics API

API call: /api/infographics-data
This requires:

Localizing each widget
Add language parameter in API
I think there is no need we'll save per newsflash data for all languages in cache. That means that after extracting data from cache, we'll use a relevant dictionary to send the data in the wanted language. @ziv17 FYI

Seems like the last time anyone touched babel in this repo was 3 years ago.
For those who are not familiar (such as myself), I think this blog post is exceptionally useful:
https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-xiii-i18n-and-l10n

@ziv17 performed an amazing work here. Closing this one.


Tetra Compat

The Blacksmith class does not work with the Tetra Mod
https://www.curseforge.com/minecraft/mc-mods/tetra
It does not apply any Boni due to Tetra not relying on a crafting Table and the Swords not beeing recognized due to not allowing sharpness in an Anvil.

fixed this in
https://github.com/LimonBlaze/origins-classes-forge/pull/17

Fixed in commit-94b6b59


Women Who Code

Description
Project proposal
Why

https://www.womenwhocode.com/
https://en.wikipedia.org/wiki/Women_Who_Code
https://www.womenwhocode.com/donate

We need more women in programming. This is a non-profit that encourages and helps with that.

Code of Conduct
By submitting this pull request, I confirm I've read and complied with the CoC 🖖

The CI flow could not re-run for PRs that are more than a month ago. Therefore, I ask for comments from those who haven't voted yet.
@defi-er Do you agree to this? Please react by 👍 or reply to this comment.

The CI flow could not re-run for PRs that are more than a month ago. However, I will merge this proposal because all the committee members have approved this.


add config block

This PR resolves #10
if the config block is not specified, queries do not filter any data since the condition in the query is WHERE true .
Therefore, it does not cause any breaking change.

Very good idea for cost saving!
I will try that and create a new release
Thanks @tanukifk


Publish in https://open-vsx.org/

It would be great if we could also have this extension published in https://open-vsx.org/, so that IDE editors like vscodium, theia, etc. can also use it

Thanks for opening an issue. I'll bring this up with the team to see if this is feasible and maintainable. Will report back.
how-to-publish-an-extension

Hey, is there some progress? I would love to use this plugin in Codium!

It takes two minutes two complete. Please get on this.


Develop and Implement Code Naming Standard

@jmbeisner - wondering if we should adhere to PEP 8 and then just call out exceptions - like the number of characters / line. Thoughts?

I'd be down with PEP 8. We might have to update some of our indentations. And yeah, definitely don't want to stick to 79 chars/line.

Closing for now. This organically has developed. Will revisit if needed.


AMD Adrenalin Context Menu Desktop

I was on 1.8.x before and there was an AMD Adrenalin: Software context menu on the desktop, now it is gone with 1.9.5. I read up on adding new context menu items but I have no idea how to link a program. Any help is appreciated.

Can you double check that after disabling NS, the AMD Adrenaline option does appear in the Windows default context menu? I've had issues with that program in particular disappearing from the desktop context menu, which would be the fault of the app and not the context menu

Thank you for your reply. It does appear once I disable NS.


display only 1 guide (the active one)

This is a suggestion:
Add another gif in the https://atom.io/packages/indent-guide-improved displaying only 1 guide (1 vertical line) instead of all guides.
When a file contains a lot of indentation, it is visually nicer to display just one guide than a crowded set of guides. I think people who like clean code will appreciate this. No code modification is required (a checkbox in the settings would also be perfect for people not to change their atom stylesheet!).
This is an example that works well with javascript files. The key is width:0px.
.indent-guide-improved {
  width:0px;
  &.indent-guide-stack {
    &.indent-guide-active {
      background-color: rgba(255, 255, 255, 0.2);
      width:1px;
      margin-left: 3px;
    }
  }
}

Thanks a lot for this! It's almost perfect for me. The project I'm working on has indent size set to 4 and your styling is really helpful. However, because indentation is not 2, the guides show in the middle of the element tags instead of at the start of it. I think it's because Atom reads indent in sets of 2 but if there's anyway of styling this as well that would be perfect. Cheers!

@fonziemedia:  for 4 spaces (python, etc) you may play with the margin-left property.
This should work fine:
margin-left: -1em;

Perfect! Thanks a lot for your help!


fix: type error in drop down

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #51364

Quick question - do we want to leave the linked issue open so we can address the type generation issue?

Quick question - do we want to leave the linked issue open so we can address the type generation issue?

No need, it should be closed.
Oliver generated the types in one of his old PRs, the component was used before the types were added, which cased the confusion.

Awesome, thanks for clarifying!


Add new Token SOLADA To the list

[ ] I will not ping the Discord about this pull request.

Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR
At minimum each entry should have

Token Address: DAhyNwD9bsMkcgXHzCvVCVimkpeRwc6bv9i47UuuQAo3
Token Name: SolADA
Token Symbol: SDA
Logo : https://1.bp.blogspot.com/-i0y17yXzNEs/YLCZ2wnk2GI/AAAAAAAAerU/uM0IXaQ7WvcPYFpVoQWisfjtszXFcpWMQCLcBGAsYHQ/s1024/SolADA%2BToken.png
Link to the official homepage of token: http://solada.unaux.com/
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

website doesnt exsists

Hello sir.
The link is active you can check again please
http://solada.unaux.com/?i=1


[GIT PULL] liburing/io_uring_for_each_cqe: Pull load acquire out of for loop

I thought it was a bit odd that the macro repedatly does the atomic load. While when using it one can amortize the atomic store following the loop, I don't really see why one wouldn't want to do the same for the load, like is already being done in io_uring_peek_batch_cqe(). Maybe I'm missing smth.
This pulls the load out of the loop into a local. Not sure if this is acceptable. I gave it a long ugly name to avoid name collisions, but still. Maybe making a new macro would be better.

git request-pull output:
The following changes since commit 206650ff72b6ea4d76921f9c91ebfffd9902e6a0:

  test/fixed-hugepage: skip test on -ENOMEM (2024-09-27 10:27:10 -0600)

are available in the Git repository at:

  https://github.com/CPestka/liburing for_each_cqe

for you to fetch changes up to cb02d22dba0c6005c877c14a2cd2574a4b95462c:

  liburing: Pull load_acquire out of for loop to amortize cost (2024-09-29 14:43:43 +0200)

----------------------------------------------------------------
CPestka (1):
      liburing: Pull load_acquire out of for loop to amortize cost

 src/include/liburing.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar<EMAIL_ADDRESS>
The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
<EMAIL_ADDRESS>
Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe<EMAIL_ADDRESS>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

I think this is fine to do, it'll iterate anything that was already available by the time of starting the loop.

It's changing behaviour in a nasty way, we can't have this version.

Oh. Yeah, that is nasty. Having two initializations in the for loop instead does not work either here -,-
Guess this does not work with this macro. Do You think it is worth it to add another macro that does this or do you want to keep it to one?

Ah indeed, thanks Pavel. I'll revert it.

Do You think it is worth it to add another macro that does this or do you want to keep it to one?

One would be ideal, I don't think there's any issue with only loading it upfront rather than repeatedly in the loop. There was never any guarantee on how CQEs are found, it only really guarantees that CQEs that were available at the time of the call will be iterated. Eg the app does a wait_nr(N) and then iterates. And depending on ring setup mode, there's no way that events will show up DURING the loop, unless old school setup is done (eg signal notifications for task_work).

One would be ideal, I don't think there's any issue with only loading it upfront rather than repeatedly in the loop. There was never any guarantee on how CQEs are found

Agree, that should be fine, it depends on timings anyway and might happen that we get a new batch only after finishing "for each".

Oh. Yeah, that is nasty. Having two initializations in the for loop instead does not work either here -,-
Guess this does not work with this macro. Do You think it is worth it to add another macro that does this or do you want to keep it to one?

Idea 1:
for (int cached_tail = ({ head = ring.head; load_acquire((ring.tail) }, ...)

Do we require compilers to support statement expressions in liburing?
Idea 2:
struct iter {
 int head, tail;
};

for (struct iter it = {..., ...}, ...)

In which case you don't even need to pass head, so it might even be a separate helper or just a dummy parameter

I like idea 1, as it doesn't require a new helper for this.

Not particularly a problem, you can always gracefully ignore an argument.

In terms of compiler support, that kind of construct has been used in the kernel for 20+ years, so I don't think we have to worry about that.

That's if we follow kernel requirements, we're not doing msvc, but I was still thinking about cases where the user might want some niche compiler. Maybe some heterogeneous computing like cuda, or when BPF was in discussion I was thinking making the header shareable with libbpf program (not sure if it supports it).

Not particularly a problem, you can always gracefully ignore an argument.

Sure, but then folks would need to opt-in.

I don't understand, the user should never use the value of head variable after the loop, so it's basically
#define for_each(ring, head, cqe)  for_each_no_head(ring, cqe)

I hear your point on more esoteric compilers. How about this, and please stay close to the eye wash station:

Or we can do whatever option and see if anyone complaints. Though it reminds me someone tried to compile it as a strict C.

diff --git a/src/include/liburing.h b/src/include/liburing.h
index 3ad061d18dfb..512edd50d5cc 100644
--- a/src/include/liburing.h
+++ b/src/include/liburing.h
@@ -310,10 +310,11 @@ int __io_uring_get_cqe(struct io_uring *ring,
 	 * io_uring_smp_load_acquire() enforces the order of tail	\
 	 * and CQE reads.						\
 	 */								\
-	for (head = *(ring)->cq.khead;					\
-	     (cqe = (head != io_uring_smp_load_acquire((ring)->cq.ktail) ? \
-		&(ring)->cq.cqes[io_uring_cqe_index(ring, head, (ring)->cq.ring_mask)] : NULL)); \
-	     head++)							\
+	for (__u32 __HEAD__ = (head) = *(ring)->cq.khead,		\
+	     __tail__ = io_uring_smp_load_acquire((ring)->cq.ktail);	\
+	     (cqe = ((head) != __tail__ ?				\
+	     &(ring)->cq.cqes[io_uring_cqe_index(ring, __HEAD__, (ring)->cq.ring_mask)] : NULL)); \
+	     (head) = ++__HEAD__)

 /*
  * Must be called after io_uring_for_each_cqe()

which should result in identical code as to just getting rid of passing in a head iterator to begin with.

Any would do IMHO. nit: I don't think you need to assign head.

Just trying to avoid needing to do another helper... We have to assign head or some compilers will (rightfully) complain that head is only ever being written, never read. Because I'd much rather just get rid of head entirely, but imho preferable to live with the existing version over having two versions of this.


[FEATURE] Is there any plan to support for other multimodal models from China?

Is there any plan to support for other multimodal models from China?
such as erniebot, Tongyi Qianwen, Tencent Hunyuan, SparkDesk, etc.

@EZevan it'd be great to support any of these models. Would you be able to make a PR?


Error when installing plugin.

npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t<EMAIL_ADDRESS>npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
I have installed the platform helper separately so I now it is there.

how did you install Git Client?


Use a requests Session

Today I had to override requests default timeout and had to do some monkeypatch (http://blog.mathieu-leplatre.info/handling-requests-timeout-in-python.html). Isolating and exposing the session is easier to customize their behaviour.

Coverage increased (+0.002%) to 99.686% when pulling ec867bd984e65d911afb693ea48aae59c9944466 on resumov:request-session into a569714b38aadbecb74086aea9c092200a02c774 on pagarme:master.

Coverage increased (+0.002%) to 99.686% when pulling ec867bd984e65d911afb693ea48aae59c9944466 on resumov:request-session into a569714b38aadbecb74086aea9c092200a02c774 on pagarme:master.


About the re-implementation of Layernorm

Hi @lucidrains ,
Thanks for the implementation of Uniformer.
After checking the code, I found that you have re-implemented the layernorm operation in the following.
https://github.com/lucidrains/uniformer-pytorch/blob/78397000e647fd4035a7fa2bede999d59d4c3ded/uniformer_pytorch/uniformer_pytorch.py#L13-L23
I wonder if there are any differences between your re-implementation and the official code provided by PyTorch (i.e., torch.nn.Layernorm(dim)  ).
Looking forward to your reply. Thx.

 Thanks for the reply.


New PR to update FAQ per changes from Alpa

@alkohli @ronmiab

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Updated collaboration link

Resolves issue #357

@Priyaaa1 You can check it

@ayush-848 mention the issue you resolved.

@ayush-848 mention the issue you resolved.

#357

@ayush-848 the task you did is not of level 1, if there is gssoc label you'll get 1 point

@ayush-848 the task you did is not of level 1, if there is gssoc label you'll get 1 point

Oh, ok


psensor: add -Wno-error due to increasing compiler strictness

ZHF: #172160
Description of changes
This Hydra failure:
https://hydra.nixos.org/log/iq8zqmw7yclgwpvr8i8clwf2sh67jb0i-psensor-1.2.1.drv
...appears to be the result of the package shipping with -Werror and
gcc accreting ever-increasing quantities of warnings as time
progresses.  Let's not treat the compiler warnings as errors.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

The ZHF announcement PR says: "Please ping @NixOS/nixos-release-managers on the PR and add the 0.kind: build failure label to the pull request. If you're unable to because you're not a member of the NixOS org please ping @dasJ, @tomberek, @jonringer, @Mic92"
I am unable to add this build label, so I therefore am issuing this ping.

Result of nixpkgs-review pr 172177 run on x86_64-linux 1

1 package built:

psensor


Couldn't request the voting rights

I try to request voting rights by got failed transaction

I think this is due to a bug that was introduced recently while i was adding styles to the commitVote container. i'm gonna push some changes right now. lemme know if you still have an issue after

It works perfectly now!

awesome, glad it's working now. closing this, but feel free to keep opening issues and asking questions. this project needs a lot of work and im grateful for feedback


added pause event for mobile scroll operation as per w3c protocol

Following PR is the changes around issue link as mentioned below,
https://github.com/karatelabs/karate/issues/1893

@babusekaran @ptrthomas ^^
Please review this PR against issue, https://github.com/karatelabs/karate/issues/1893

@bipin-k  Thanks! LGTM✔

merged with thanks !


adding the code for 3 sum closest in cpp

code for 3 sum closest problem
in which we find the sum of three elements closest to given target.

Thanks for the contribution!


dynamic metadatas

to allow shareable urls to come with their own preview we need to change approach:

app/[demoname]/page.tsx -- displaying the  and dynamic metadata (server-side)
app/layout.tsx or app/[demoname]/layout.tsx (not sure yet) -- with the nav

see also:

https://nextjs.org/docs/app/building-your-application/optimizing/metadata#dynamic-image-generation
https://nextjs.org/docs/app/api-reference/file-conventions/metadata/opengraph-image

done


fix(rust): use jemallocator for linux gnu, mimalloc for everything else

This is aligned with swc, see https://github.com/swc-project/swc/blob/ad8e6a006c35977d70b719e67b5a45244c017ca1/crates/swc_node_base/Cargo.toml#LL16C1-L20C81
Summary
This may fix CI crashing on linux machines

🤖 Generated by Copilot at 0318b14
This pull request updates the memory allocator settings for different target platforms in the rspack project. It replaces the mimalloc-rust crate with the jemallocator crate for some Linux targets, to improve performance and compatibility. It also removes some unnecessary dependencies and adds some configuration attributes in various Cargo.toml and src files.

Walkthrough

🤖 Generated by Copilot at 0318b14

Add jemallocator crate as a dependency to use jemalloc as the global allocator for some Linux targets (link)
Remove rspack_tracing dependency from the benchmarking crate and refine target-specific dependencies for mimalloc-rust and jemallocator based on performance and compatibility (link)
Remove unused use mimalloc_rust::GlobalMiMalloc statements from the benchmarking crate and the benchmarking tests (link, link)
Set jemalloc as the global allocator for Linux targets with gnu environment and either x86_64 or aarch64 architecture using #[global_allocator] and static GLOBAL in the benchmarking crate, the benchmarking tests, and the Node.js binding crate (Cargo.toml link, link, link; main.rs link, link; lib.rs link)
Update #[cfg] attributes for mimalloc-rust to set mimalloc as the global allocator for non-Linux targets in the benchmarking crate, the benchmarking tests, and the Node.js binding crate (Cargo.toml link, link, link; main.rs link, link; lib.rs link)
Remove unnecessary mimalloc-rust dependency from the build script crate (link)

I retried the linux tests 5 times and nothing crashed, I think this is safe to merge.

Note: Merge after v0.2.0


Delegate logicfields to a kts script

For the longest time I wanted to use kotlin scripting engine for something and this is a good use case, additionally a few days ago a user called scastiel on reddit posted a detailed blog of his implementation of this element  which is really helpful as this feature (specificlly ide support) is very poorly documented, something that prevented me from dedicating too much time into it


How to generate a new audio using trained model

Hi,
I have trained your model on VCTK and when I run evaluate I do not see any number or new files. I am interested to generate new audio using the trained model. Can you tell me the command needed to do it. Thanks!

Has anybody figured this out?


Fix break that was missed during a merge

Description
Fix break that was missed during a merge
Check List

[ ] ~New functionality includes testing~
[ ] ~New functionality has been documented~
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1707 (bf602ca) into main (782b042) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1707      +/-   ##
============================================
- Coverage     62.85%   62.83%   -0.02%
+ Complexity     3259     3258       -1
============================================
  Files           253      253
  Lines         18082    18082
  Branches       3242     3242
============================================
- Hits          11365    11362       -3
- Misses         5063     5066       +3
  Partials       1654     1654

Impacted Files
Coverage Δ

...security/auditlog/sink/InternalOpenSearchSink.java
69.23% <0.00%> (-11.54%)
:arrow_down:

Continue to review full report at Codecov.

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


Add terraform code for AWS account and use nixops from local machine

This is actually 2 parts:

transfer the terraform management of the AWS account from https://github.com/input-output-hk/mantis-iele-ops as this is a legacy project now
try to get nixops running from my local machine. This was sort of working but not very reliably. I really want to get rid of the nixops machine and the glue code required for deploying from a remote machine however using OSX was tricky. I want @gilligan to take a look

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] $(nix-build default.nix -A pkgsLocal.updateMaterialized) to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] $(nix-shell shell.nix --run fix-stylish-haskell) to fix any formatting issues

If you changed any Purescript files:

[ ] $(nix-shell shell.nix --run fix-purty) to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

Apart from adding account management I have also included an upgraded version of nixops. This is because you should actually be able to deploy the nixops stuff from your local machine however it's not quite working yet. The work to fix it will be in another PR when I work it out.

Apart from adding account management I have also included an upgraded version of nixops. This is because you should actually be able to deploy the nixops stuff from your local machine however it's not quite working yet. The work to fix it will be in another PR when I work it out.


Installing on Laravel 10.3 x is giving some error

Error
Class "WeProDev\LaraNav\Enum\NavLocationEnum" not found
 // laranav.nav     'nav' => [         // laranav.nav.SIDE_NAV         NavLocationEnum::SIDE_NAV->value => [             [                'title' => 'Dashboard',                 'type' => NavLinkTypeEnum::ROUTE->value,                 'url' => 'lp.dashboard.panel',                 'active' => true,

Hi @bipsdevs
Thanks for your feedback, I'll have a look and let you know.
Do you have laranav.php in your config file?! did you installed laranav in your local, can you try this command?
composer require weprodev/laranav