Client.js vs Index.js

I'm not sure what the concept is behind having a client.js (as entry for dev and dist) and index.js (entry for base) in the webpack settings? Index.js uses a container and client uses components. Maybe you can shed light on how that's supposed to work? Thanks!

This has been changed in the latest version of the template and is client.js instead of index.js the entry in base.js might be a fragment, since the entry if overwritten by either base dev, dist or test config from what I can see.

but client.js doesn't use the default container then? Or am I missing something? client grabs component/App where as index grabs container/App

Uh, OK, this could be a problem in this gen then, when both files are available. will look into this.

seems to me that the issue comes from the base generator too as that's where client.js is created. Since it doesn't use Redux it doesn't point to a container. The index.js file which is added by THIS generator does point to a container correctly. But webpack sources client.js

I'm having trouble getting the hot loader working with the index.js entry.
I noticed the index.js file also doesn't have the AppContainer from react-hot-loader.
Should it use the AppContainer like in client.js?

client.js points to ./components/App
index.js points to './containers/App'
Myabe I'm missing something but it feels like there's something wrong

My main problem currently is that client.js doesn't user the provider/store and the expected architecture is unclear

Anyone found a solution?

@fabdrol Well, it seems a solution is to either change the entry point in ./conf/webpack/Dev ./conf/webpack/Dist ./conf/webpack/Test files to ./index.js, or... to ditch subgenerators altogether (not really a solution, just for my project they don't work anyway).
In any case subgens seem to be bound to /containers/App.js which loads everything else, if you want to use them, you need to include that file in one way or another.

Hey guys, I will update this as soon as I can find some spare time and some concentration. The whole base has been updated and there is quite a bit to adjust. Sorry for the delay.

Alright, this is fixed in 1.1.0 - feel free to re-open if problem persists.


Getting missing MSI headers when updating storage account encryption

Hi,
I'm trying to update a storage account encryption with the following code :
...
_, err := storageClient.Update(context.Background(), groupName, accountName, storage.AccountUpdateParameters{
		Kind: storage.Storage,
		AccountPropertiesUpdateParameters: &storage.AccountPropertiesUpdateParameters{
			Encryption: &storage.Encryption{
				KeySource: storage.MicrosoftKeyvault,
				KeyVaultProperties: &storage.KeyVaultProperties{
					KeyName:     &keyName,
					KeyVaultURI: &keyVaultURI,
					KeyVersion:  &keyVersion,
				},
				Services: &storage.EncryptionServices{
					Blob: &storage.EncryptionService{
						Enabled: &enabled,
					},
					File: &storage.EncryptionService{
						Enabled: &enabled,
					},
				},
			},
		},
	})
...

and I got the following error :
Update failed: storage.AccountsClient#Update: Failure responding to request: StatusCode=500 -- Original Error: autorest/azure: Service returned an error. Status=500 Code="MissingMsiHeaders" Message="MSI headers are missing from the request."

However this same code is working when I manually update the encryption in the Azure console.
I tried to use azure-sdk-for-go and go-autorest both in master and also go-autorest v11

Hello!  Sorry for the delay.  How are you creating the authorizer that's associated with storageClient?

authorizer, err := auth.NewAuthorizerFromEnvironment()

Hi,
we're setting :

AZURE_TENANT_ID
AZURE_CLIENT_ID
AZURE_CLIENT_SECRET
AZURE_SUBSCRIPTION_ID

that's all.
Thanks !

Hmm I can't repro this with a simple app.  Do you have a simplified repro handy?  Also what version of go-autorest are you using?

Hi,
I tried again using latest go-autorest (v10.11.0) and latest azure-sdk-for-go (v17.3.0).
And still have the issue with the following code snippet :
package main

import (
	"context"
	"fmt"
	"os"

	"github.com/Azure/azure-sdk-for-go/profiles/latest/storage/mgmt/storage"
	"github.com/Azure/go-autorest/autorest/azure/auth"
)

const (
	location    = "westus"
	groupName   = "RESOURCE_GROUP_NAME"  //put your resource group name
	accountName = "STORAGE_ACCOUNT_NAME" //put your storage account name
	provider    = "Microsoft.Storage"
)

var (
	storageClient storage.AccountsClient
)

func init() {
	authorizer, err := auth.NewAuthorizerFromEnvironment()
	if err != nil {
		fmt.Printf("%s: %s\n", "Error while getting authorizer from env", err)
		os.Exit(1)
	}
	subscriptionID := getEnvVarOrExit("AZURE_SUBSCRIPTION_ID")
	storageClient = storage.NewAccountsClient(subscriptionID)
	storageClient.Authorizer = authorizer
}

func main() {
	updateStorageAccount()
}

func updateStorageAccount() {
	keyName := "KEY_NAME"                            //put your key name
	keyVaultURI := "https://PUT_YOUR_KEYVAULT/"      // put your key vault
	keyVersion := "38ca204b37fe4085984c5f90a118a1e2" //put you key id
	enabled := true
	_, err := storageClient.Update(context.Background(), groupName, accountName, storage.AccountUpdateParameters{
		Kind: storage.Storage,
		AccountPropertiesUpdateParameters: &storage.AccountPropertiesUpdateParameters{
			Encryption: &storage.Encryption{
				KeySource: storage.MicrosoftKeyvault,
				KeyVaultProperties: &storage.KeyVaultProperties{
					KeyName:     &keyName,
					KeyVaultURI: &keyVaultURI,
					KeyVersion:  &keyVersion,
				},
				Services: &storage.EncryptionServices{
					Blob: &storage.EncryptionService{
						Enabled: &enabled,
					},
					File: &storage.EncryptionService{
						Enabled: &enabled,
					},
				},
			},
		},
	})
	if err != nil {
		fmt.Printf("%s: %s\n", "Error while updating storage account", err)
		os.Exit(1)
	}
}

// getEnvVarOrExit returns the value of specified environment variable or terminates if it's not defined.
func getEnvVarOrExit(varName string) string {
	value := os.Getenv(varName)
	if value == "" {
		fmt.Printf("Missing environment variable %s\n", varName)
		os.Exit(1)
	}
	return value
}

Thanks a lot I can repro this issue.  I suspect this has something to do with the Identity field in AccountUpdateParameters but the documentation doesn't specify how it should be set, nor is the response error documented.  :(
@blueww can you please help with this issue or route to somebody that can?  To summarize, when calling the update API we receive the following response.
Error while updating storage account: storage.AccountsClient#Update: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="MissingMsiHeaders" Message="Managed Service Identity (MSI) is not set for this account."

I don't see MissingMsiHeaders documented here.

@petitout
Have you follow all the steps in https://docs.microsoft.com/en-us/azure/storage/common/storage-service-encryption-customer-managed-keys before enabled Keyvault in Storage Account?
I have tried to set keyvault with the above doc, and it works.
Please note, if your account don't have identity, you need to update it by set the identity as following, and you need to give the account identity permission for the Keyvault:
                   ` updateParameters.Identity = new Identity();`

@blueww can we get the docs updated with the MissingMsiHeaders error code?

@petitout have you tried the steps recommended by @blueww and if so did it resolve your issue?

Hi @jhendrixMSFT and @blueww,
sorry for the delay.
I tried this : I went in the Azure web console and went to encryption configuration of the keyvault. I selected "Use my own key" , selected a key and saved (equivalent to step 3 in the doc @blueww pointed to). This worked fine.
Then I unselected "Use my own key" to use Microsoft.storage encryption and saved.
After that I was able to update the encryption type (to use a keyvault key) using my code snippet without any problem.
@blueww I couldn't identify any REST API that could be used as a pre-requesite of my code snippet. Are they any ?

@petitout
Good to know you find a way to make the feature work.
I am not the feature owner, so I might not be the best person to answer the feature questions.
(Our team owns storage SDK, but you question is more for feature itself instead of storage SDK.)
If you would like to know the rest API for the pre-requisite step, or any other questions for the feature, you might can open a question in https://docs.microsoft.com/en-us/azure/storage/common/storage-service-encryption-customer-managed-keys
Actually, What I get is how to do the pre steps from Powershell from the doc. So you might can also consider using Powershell to do the pre-requisite.

Sounds like this has been resolved so closing.  Please reopen as required.


Add GA dimension metric on number of slot requests

Will this send the metrics again if people follow the link from the email?

Yes @alan the new metric would be recorded again but this is a second dimension metric which gets recorded against page views so as there would be another page view we should also record the second metric as well. Plus it would be an edge case.


REAL trades being placed in --paper mode!

At first I thought it was a bit odd that paper mode suddenly required my API key etc...
I was "okay whatever, maybe they got in trouble with some exchanges for querying the API"...
Decided to test a strategy in --paper mode, paper mode was apparently active.
Suddenly my XMR get sold... I think, perhaps it is a simulated balance... Log into Kraken...
Sure enough my XMR had been sold...
./zenbot.sh trade kraken.XXMR-ZEUR --paper --order-type="taker"
is the command-line I used.
proof

Same thing happened to me on gdax.ETH-EUR

Confirmed on GDAX as well, performed actual trades.

help me.
why i set trade BTC-USDT ( BTC up bot buy, BTC down bot sell ) :(
what is set method ?

in a short test on my side #1405 should fix the issue.


Add captive portal blockage fingerprints for AT

Captive portal blockage fingerprints for Austria triggered by the Barracuda/NGFirewall middleboxes.
Example measurements:
https://explorer.ooni.io/measurement/20170814T120242Z_AS8447_g6CoCriPHXMWjXJHwZ9kjJmTusVWVPYEsOKOOhF1HLwrHR29hp?input=http:%2F%2Fwww.aleph.to
https://explorer.ooni.io/measurement/20180215T142531Z_AS31543_HutYcy6eALgop44KgGsXAsaF2i7v4feM6DP5vb2hST8nZdmWta?input=http:%2F%2Fanonymizer.secuser.com

Thanks! Added to #289


Sequential Proofs

The purpose of this issue is to track work on the development of sequential proofs for Cava circuits.
The first proof we consider is for a synthetic example of a circuit made with a counter which counts-by the current input values:
        _______
    ---| delay |------------
   |   |_______|            |
   |   ___                  |
    --| + ---------------------- out
 in --|___|

The countBy circuit takes the current 8-bit input (in) and the current state value represented by the register (delay) which is output in the current cycle as the output of the circuit, and this value is also the next state value for the delay. The adder is an 8-bit adder with no bit-growth i.e. it computes (a + b) mod 256.
Currently this circuit description is in the PR #367 in the file tests/Delay.v.
The implementation makes use of the loop combinator which implicitly places a register on the feedback path:
Section WithCava.
  Context {signal} `{Cava signal} `{Monad cava}.

  Definition countFork (i : signal (Vec Bit 8) * signal (Vec Bit 8))
                       : cava (signal (Vec Bit 8) * signal (Vec Bit 8)) :=
    newCount <- addN (fst i) (snd i) ;;
    ret (newCount, newCount).

  Definition countBy : signal (Vec Bit 8) -> cava (signal (Vec Bit 8))
    := loop countFork.

End WithCava.

We can test the circuit with some concrete values to confirm that it seems to work as intended:
Example countBy_ex1: sequential (countBy [b14; b7; b3; b250]) = [b14; b21; b24; b18].
Proof. reflexivity. Qed.

We can write a specification for the intended behaviour:
Fixpoint countBySpec' (state: N) (i : list (Bvector 8))
                      : list (Bvector 8) :=
  match i with
  | [] => []
  | x::xs => let newState := (Bv2N x + state) mod 256 in
             N2Bv_sized 8 newState :: countBySpec' newState xs
  end.

Definition countBySpec := countBySpec' 0.

Now the challenge is to prove that the implementation countBy has equivalent behaviour to the specification countBySpec:
Lemma countByCorrect: forall (i : list (Bvector 8)),
                      sequential (countBy i) = countBySpec i.

To make the proof work out it is fine to write the specification in a different way, or to change how the underlying semantics are expressed (e.g. computing the circuit "backwards" has been suggested) or making any other change that helps with the proof. Also, feel free to change the spec (e.g. to make it simpler): it's currently written in a mechanistic manner to mirror how the hardware is constructed.

Just to record some experimenting:
Following the pattern from #374, I tried defining a loop using a function from nat to simulate an infinite list. I wasn't able to get it working, though, because of trouble with interleaving the timestep argument and the monad. The timestep argument, with this type, has to be underneath the ident. However, the timestep needs to be exposed to any recursive definition because it's the decreasing argument. But because the subcircuit returns something wrapped in ident, it's necessary to have the ident in the single-step case, and these constraints aren't compatible as far as I can tell. Of course, I could use unIdent, but I think that violates the circuit graph principle, no?
Here's the definition without ident:
Definition seqFType t := nat -> combType t.

Fixpoint loopSeqF' {A B C : SignalType}
         (f : combType A * combType C -> combType B * combType C)
         (a : seqFType A) (t : nat) : combType B * combType C :=
  match t with
  | 0 => (defaultCombValue B, defaultCombValue C)
  | S t' =>
    let '(_, ct') := loopSeqF' f a t' in
    f (a t', ct')
  end.

Definition loopSeqF {A B C : SignalType}
         (f : combType A * combType C -> combType B * combType C)
         (a : seqFType A) : seqFType B * seqFType C :=
  let bc := loopSeqF' f a in
  (fun t => fst (bc t), fun t => snd (bc t)).

And here's as far as I got with ident included:
Fixpoint loopSeqF' {A B C : SignalType}
         (f : combType A * combType C -> ident (combType B * combType C))
         (a : seqFType A) (t : nat) : ident (combType B * combType C) :=
  match t with
  | 0 => ret (defaultCombValue B, defaultCombValue C)
  | S t' =>
    '(_, ct') <- loopSeqF' f a t' ;;
    f (a t', ct')
  end.

The version above typechecks but I can't make loopSeqF by calling it.

Great progress, I think we should continue to add sequential complexity #376

(For archival purposes / to remind myself later) In the meeting, we said it would be fine to use unIdent inside the loop.

Although it is possible to express a loop circuit who's output comes directly from the output of the register, this involves in internal combinational circuit using the enable input to control a multiplexor. However, I don't want the enable signal to be accessible to the internal logic (the f function): I only want it wired up under the hood to the clock enable input of registers (for the netlist interpretation, to yield good circuits).
I think we should have a variant of loopDelay as the primitive loop element which exposed both the output of f and the current state:
  loopDelayS : forall {A B C: SignalType},
               (signal A * signal C -> cava (signal B * signal C)) ->
               signal A ->
               cava (signal B * signal C);

i.e.
    ---------------------------- current state
   |
   |     _______
    ---| delay |-------------
   |   |_______|            |
   |   ___                  |
    --| + ---------------------- out
 in --|___|

Now loopDelay becomes a special case of loopDelayS and can be defined in Combinators.v.
This then allows us to make a countBy with enable which counts from 0 as the initial argument and does not need to burn logic to implement a multiplexor driven by an enable signal.

Closing this; we managed long ago in https://github.com/project-oak/silveroak/pull/561 to represent sequential circuits, and are now moving on to v2 with finer improvements, so I think there's no more need for a tracking issue.


feat(kzip): add subcommand and proto for metadata kzips

This lets us store the commit timestamp of the build in a CompilationUnit:
{
  "v_name": {
    "language": "kythe_build_metadata"
  },
  "details": [
    {
      "@type": "kythe.io/proto/kythe.proto.BuildMetadata",
      "commit_timestamp": "2020-06-05T06:15:09Z"
    }
  ]
}

I put the new BuildMetadata message in storage.proto, but maybe there's a better place?

I'm not sure why the build is failing - it works on my machine...
Here are the logs before it dies:
link: warning: package "github.com/golang/protobuf/ptypes/any" is provided by more than one rule:
    @com_github_golang_protobuf//ptypes/any:go_default_library
    @io_bazel_rules_go//proto/wkt:any_go_proto
Set "importmap" to different paths in each library.
This will be an error in the future.
link: warning: package "github.com/golang/protobuf/ptypes/duration" is provided by more than one rule:
    @com_github_golang_protobuf//ptypes/duration:go_default_library
    @io_bazel_rules_go//proto/wkt:duration_go_proto
Set "importmap" to different paths in each library.
This will be an error in the future.
link: warning: package "github.com/golang/protobuf/ptypes/timestamp" is provided by more than one rule:
    @com_github_golang_protobuf//ptypes/timestamp:go_default_library
    @io_bazel_rules_go//proto/wkt:timestamp_go_proto
Set "importmap" to different paths in each library.
This will be an error in the future.
link: warning: package "github.com/golang/protobuf/ptypes" is provided by more than one rule:
    @com_github_golang_protobuf//ptypes:go_default_library_gen
    @com_github_golang_protobuf//ptypes:go_default_library
Set "importmap" to different paths in each library.
This will be an error in the future.
panic: runtime error: index out of range [23] with length 0
goroutine 1 [running]:
cmd/link/internal/ld.decodetypeKind(...)
	/usr/local/go/src/cmd/link/internal/ld/decodesym.go:69
cmd/link/internal/ld.newtype(0xc000630180, 0xc002511010, 0xc0034c7800)
	/usr/local/go/src/cmd/link/internal/ld/dwarf.go:425 +0x2a32
cmd/link/internal/ld.defgotype(0xc000630180, 0xc002511010, 0x36)
	/usr/local/go/src/cmd/link/internal/ld/dwarf.go:420 +0x1c8
cmd/link/internal/ld.dwarfGenerateDebugInfo(0xc000630180)
	/usr/local/go/src/cmd/link/internal/ld/dwarf.go:1756 +0xa22
cmd/link/internal/ld.Main(0x89a320, 0x10, 0x20, 0x1, 0x7, 0x10, 0x6c35da, 0x1b, 0x6bf65d, 0x14, ...)
	/usr/local/go/src/cmd/link/internal/ld/main.go:219 +0xb96
main.main()
	/usr/local/go/src/cmd/link/main.go:68 +0x1bc
link: error running subcommand: exit status 2

The warning about proto packages being provided more than once is unfortunate, but I don't think this PR makes that worse than it already is.


Memory leak renders camera unresponsive over time

Left running overnight, the camera shows high memory usage, gets slow and sometimes streamer crashes.
Re-run manually in console displays errors with ioctl:
[root@thingino-t31n ~]# prudynt
[INFO:main.cpp]: PRUDYNT Video Daemon: Mar 12 2024 04:43:15_a278410b15
[INFO:main.cpp]: Starting Prudynt Video Server.
[INFO:IMP.cpp]: LIBIMP Version IMP-1.1.6
[INFO:IMP.cpp]: SYSUTILS Version: SYSUTILS-1.1.6
[INFO:IMP.cpp]: CPU Information: T31-N
[INFO:IMP.cpp]: Sensor: gc2053
---- FPGA board is ready ----
  Board UID : 30AB6E51
  Board HW ID : 72000460
  Board rev.  : 5DE5A975
  Board date  : 20190326
-----------------------------
ioctl error ret = -1
ioctl error ret = -1
ioctl error ret = -1
ioctl error ret = -1

I guess straigtening out getaway pid files fixed that.


Fix multiscreen webview tray popup 152 v210

First merge attempt into latest main - not tested yet !

@amadeo-alex Hi Alex, is there btw any way to contact you directly, via Email or anything ? I created this new PR based on your main (synced to my fork, and commits stashed into one).
I am a bit puzzled as my other fix (Alt-Escape to not close the Main Form) also shows up as a new change.
But looking at your main, it seems indeed that the code for that bugfix is not yet in main. I cannot currently test this again, as I am travelling and have no second screen. But it looks alright for me. Kindly have a look at it and if it feels ok, I delete my other PR (basing on 2.0.0) and mark this one as non-draft.
Or then, we'll wait until december until I am back home, but that would propably mean another PR, as main will most likely move ahead. Pls let me know what you think.
Best
Denis


Add Rancher Desktop landing page

Fixes https://github.com/rancher/rancher-docs/issues/938
Description
Adds a landing page for the Rancher Desktop integration.

Per discussion with Guna, we're proceeding to merge so stakeholders are able to preview the initial design/update. We'll continue to improve/iterate and address any feedback post-merge.


They are selling osiris as their own cheat

I know a cheat distributor that slightly changed the osiris menu and is selling it as its own cheat.
Their YouTube channel: https://www.youtube.com/channel/UCp0UM3c1ZzwpLBjdiOmIANQ/videos
They call it "Premium X"

osiris is open source cheat isnt it?

nothing daniel can do.

Permissions:  Commercial use
https://github.com/danielkrupinski/Osiris/blob/master/LICENSE


Question: user names and dots

I noticed while trying a recent version that the script says that usernames with dots are not allowed and therefor are being replaced with a comma.
In our current setup we have a lot of users with a dot in the name all working fine.
The log says the Gitlab doesn't allow this. Is this since version 12? Or did I miss something here?

I don't recall doing this deliberately, in which case it'll be an issue for Gitlab instead. A sure way to test this would be to just try and register as a normal user with a dot in.
After some searching it appears usernames can only contain. Alphanumeric characters by design, so this tool won't be able to change that. What may work is attempting to sign in as that user in advance to see what user name it creates. The tool could perhaps be adjusted to filter out characters but nothing else.

Hello Adam,
I have the same issue:
[warning] Dry run enabled: No changes will be persisted. [notice] Loading configuration. [notice] Loaded configuration. [notice] Validating configuration. [notice] Validated configuration. [notice] Retrieving directory users and groups. [notice] Establishing LDAP connection. [debug] LDAP: Enabling debug mode [debug] LDAP: Connecting [debug] LDAP: Setting options [debug] LDAP: Binding [notice] LDAP connection established. ldap_build_search_req ATTRS: cn cn displayName mail [notice] 101 directory user(s) found. [warning] User #1 [cn=y.vladimirov,ou=People,dc=awd-group,dc=tech]: Username "y.vladimirov" is incompatible with Gitlab, changed to "y,vladimirov".
And y.vladimirov is totaly accepted by the Gitlab with DOT. What we can do to fix it.

Hi @yasenv-code,
The issue is that Gitlab's API does not (or did not, it's been a while) accept non-alphanumeric usernames when creating a user via their exposed API function. That limitation applies to any external tool.
It would appear that usernames with dots in at all was itself an afterthought: https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7500
As this has been approximately 9 months the current Gitlab API may have resolved this by now. I don't have a sandbox I can try this on, but you're welcome to try it out yourself. What you'd need to do is checkout the current master, open "src/LdapSyncCommand.php" with your favourite text editor, then find this block at line 707:
// Make sure the username format is compatible with Gitlab later on
if (($ldapUserNameSlugified = $slugifyLdapUsername->slugify($ldapUserName)) !== $ldapUserName) {
    $this->logger->warning(sprintf("User #%d [%s]: Username \"%s\" is incompatible with Gitlab, changed to \"%s\".", $n, $ldapUserDn, $ldapUserName, $ldapUserNameSlugified));
    $ldapUserName = $ldapUserNameSlugified;
}

Simply comment out all of that as follows:
// Make sure the username format is compatible with Gitlab later on
/*
if (($ldapUserNameSlugified = $slugifyLdapUsername->slugify($ldapUserName)) !== $ldapUserName) {
    $this->logger->warning(sprintf("User #%d [%s]: Username \"%s\" is incompatible with Gitlab, changed to \"%s\".", $n, $ldapUserDn, $ldapUserName, $ldapUserNameSlugified));
    $ldapUserName = $ldapUserNameSlugified;
}
 */

When you run the sync command usernames will no longer be "slugified" at all.

Actually, on second thoughts it could be the Slugify component, specifically the regular expression involved. What you could try instead is changing that on line 586 from
"regexp"        => "/([^A-Za-z0-9]|-_\.)+/",

to
"regexp"        => "/([^A-Za-z0-9-_\.])+/",

Hello Adam, the regexp fix did the job. Now It imports all the players. I am stuck with another issue. But will open separate ticket.

Thanks for the feedback @yasenv-code, I'll commit that shortly.
@jsiegers you may be interested in this.


Cannot install cltorch on a system that previously ran it fine

First of all - amazing work.
I've encountered an error when installing this on a fresh system (exact same hardware, and most of the software was used before and worked fine - maybe slightly older versions)

[ 52%] Building CXX object src/lib/CMakeFiles/THCl.dir/THClTensorIndex.cpp.o
/home/vilius/cltorch/src/lib/THClTensorMath.cpp: In function ‘void THClTensor_minall_gpu(THClState*, THClTensor*, THClTensor*)’:
/home/vilius/cltorch/src/lib/THClTensorMath.cpp:268:19: error: ‘THInf’ was not declared in this scope
           (float) THInf, self->storage->wrapper)) {
                   ^
/home/vilius/cltorch/src/lib/THClTensorMath.cpp: In function ‘void THClTensor_maxall_gpu(THClState*, THClTensor*, THClTensor*)’:
/home/vilius/cltorch/src/lib/THClTensorMath.cpp:282:20: error: ‘THInf’ was not declared in this scope
           (float) -THInf, self->storage->wrapper)) {
                    ^
/home/vilius/cltorch/src/lib/THClTensorMath.cpp: In function ‘float THClTensor_minall(THClState*, THClTensor*)’:
/home/vilius/cltorch/src/lib/THClTensorMath.cpp:290:23: error: ‘THInf’ was not declared in this scope
   float val = (float) THInf;
                       ^
/home/vilius/cltorch/src/lib/THClTensorMath.cpp: In function ‘float THClTensor_maxall(THClState*, THClTensor*)’:
/home/vilius/cltorch/src/lib/THClTensorMath.cpp:312:24: error: ‘THInf’ was not declared in this scope
   float val = (float) -THInf;
                        ^
make[2]: *** [src/lib/CMakeFiles/THCl.dir/THClTensorMath.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [src/lib/CMakeFiles/THCl.dir/all] Error 2
make: *** [all] Error 2

Any ideas why this could be happening?

Spent last 3 days thinking this was driver/hardware issue, and didn't see the pull request. #65  fixed this.

Thanks!  Sorry about that.  Glad that you and kosmonautisk found out the issue and fixed it.  Thanks! :-)


Social share thumbnails missing

Previews from Social Share Preview chrome extension:

Also:

Why is there https://gafa.com prefix ?!

Ok, so it seems https://gafa.com is a custom domain registered by one of our users. And it seems Vercel just picks it up randomly out of all domains assigned to the app because we've incorrectly set paths to our og/twitter images. They should always be absolute URLs and we have set them as /thumbnail.png.

FIXED


[Question] Swap of axes (x / y / z) in the output boxes

Hello,
I have ran a traning experiments with 3d data which were given in .nii.gz format. with typical shape of 512 x 512 x 20 in X / Y and Z (slice) axes.
Looking at the predicted boxes, they seem to make sense when considered under the following format : [ zmin, ymin, zmax, ymax, xmin, xmax] whereas my understanding is that the results should be instead in the format : [ xmin, ymin, xmax, ymax, zmin, zmax]

Is it something expected from the code ?
Do you know what could be the origin of this swap of axes between X and Z ? Does the code expect the .nii.gz file to be formatted a specific way ?
Do you think that this could impact the performance of the code ? (ie. are there "slice / Z" specific processing applied that make it important to have the correct order of dimension during training / evaluation ?)

Thanks a lot for your help

At which point did you check the predicted boxes? The final result of the pkl file in the val_predictions folder should be in the original axes order, so given an image x,y,z, it will be in x_min, y_min, x_max, y_max, z_min, z_max
The same principle applied for different cases as well, given an z,y,x image it will produce z_min, y_min, z_max, y_max, x_min, x_max boxes in the end.
There are some notes: Internally nnDetection transposes data into the x,y,z format (assuming z is the axis with the highest spacing). All operations inside the neural network are axes independet, i.e. as long as it is configured correctly it doesn't matter where the z axis is => e.g. the docstrings were written at an earlier point and might be confusing since they assume x,y,z inputs

Thanks for your answer @mibaumgartner
We see them in the predicted boxes indeed in val_predictions. Investigating a little bit there seems to be a swap between the data in the folder "raw-splitted" and "raw_cropped", eg.:

in the folder "raw-splitted" data are in .nii.gz format and when loaded (with nibabel) correctly show a shape of 270 x 270 x 24
in the folder "raw-cropped" data are in npz format now show a shape of 4x 24 x 270 x 270 (i guess including the 3 input sequences + the segmentation)
in the folder "preprocessing" data are in npy format now show a shape of 3x 24 x 270 x 270

Once again if you do not think this swap could cause any issue with the training procedure I would not bother too much, but if you have an idea of where that can come from I would be interested to know !
Thanks again

Thank your for your detailed response @MMRohe,
the confusion arises from a rather awkward sitk convention and nnDetection uses sitk throughout it's whole pipeline. The produced box coordinated refer to the array obtained when load the image with Simple ITK and calling "GetArrayFromImage". That function inverts the axis order when compared to other readers such as nibabel which results in the inverted axis.
So to align the produced coordinates with your images when using nibabel you need to switch around the axis as you have specified in your first comment. Everything else inside nnDetection will work just fine :)


Caddy pushes in incorrect order

1. What version of Caddy are you using (caddy -version)?
master
2. What are you trying to do?
use server push
3.   What did you expect to see?
The server should first respond to the original request (200 header, push_promise and data) before sending all the push resources (200 header and data).
7. What did you see instead (give full error messages and/or log)?
The server first sends responses for the push resources (push_promise, 200 header and data) and only afterwards responds to the initial requet (both header and data).
This drastically decreases performance when pushing a lot of data as the client has to wait for all pushed resources before receiving the initial page.
8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
Serve 2 files, push one of them, watch with Wireshark.
Here are my logs: https://www.dropbox.com/sh/oucup2az15tmzhq/AACG45efML_zl7LhX7rXNarMa?dl=0
I am already trying to fix it.

The push_promise should be sent before the initial response so the order is correct in Caddy.

@twdkeule By the way, if you have in fact verified this claim:

The server first sends responses for the push resources (push_promise, 200 header and data) and only afterwards responds to the initial requet (both header and data). This drastically decreases performance when pushing a lot of data as the client has to wait for all pushed resources before receiving the initial page.

Then perhaps it is worth opening an issue with Go about this. I'm under the impression that Push() only sends PUSH_PROMISE frames, not necessarily pushing the data (content) of the promise immediately. I'd have to dig deeper, but from reading the spec and docs, it seems to be just a promise that the data will be sent; that the stream is reserved for future use.


Allow building against a single dynamic swift-syntax library

When SWIFTSYNTAX_BUILD_DYNAMIC_LIBRARY is specified, change swift-syntax dependencies to depend on a single _SwiftSyntaxDynamic product instead of separate products for each module.
This allows us to build SourceKit-LSP on Windows using SwiftPM without exceeding the maximum symbol limit and thus run SourceKit-LSP tests on Windows.
See https://github.com/swiftlang/sourcekit-lsp/pull/1754 and https://github.com/swiftlang/swift-syntax/pull/2879.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test macOS

@swift-ci Please test

@swift-ci Please test Windows


Big square at bottom-left

Software Versions

Python: 3.8.10 / 3.9.5
OS: Linux Mint 20.1 / Kubuntu 21.04
Kivy: v2.0.0 / v2.0.0
Kivy installation method: pip / pip

Describe the bug
A big square appears at bottom-left of nearest container when using widgets with on_mouse_pos-derived Behavior. It seems that square has the same color as non-hovered button (eg. color from canvas assigned via default_style() method.
Expected behavior
I didn't expect any weird squares at all.
To Reproduce
I've reduced my project to minimal working exapmple, but it is still quite big (80 loc .py + 40 loc .kv): extract files from kivy-stange-square.zip and run .py script.
Code and Logs and screenshots

Linux Mint
Kubuntu

I assume this is not a support request as this issue describes erroneous behavior of framework itself, and this is not the request for help in certain situation.
By "erroneous" I mean that this behavior is not stated in documentation (am I wrong?) and one, basing on previous experience, would not expect this "feature" to appear.

Its not erroneous - you are calling a method in __init__ and there you will get default values - pos of (0, 0) and size of (100, 100).
You could Clock.schedule_once(method, 1) there which would then have the values you were expecting.

Sorry, this is my bad indeed.


validation for agencies form

Codecov Report
Attention: Patch coverage is 7.69231% with 24 lines in your changes missing coverage. Please review.

Project coverage is 23.05%. Comparing base (b259ed1) to head (e7f8713).

Files
Patch %
Lines

...ce-web/src/components/App/Agencies/AgencyModal.tsx
6.66%
14 Missing :warning:

...mponents/Shared/Controlled/ControlledTextField.tsx
9.09%
8 Missing and 2 partials :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #24   +/-   ##
========================================
  Coverage    23.04%   23.05%
========================================
  Files           58       59    +1
  Lines          833      837    +4
  Branches       191      208   +17
========================================
+ Hits           192      193    +1
+ Misses         641      604   -37
- Partials         0       40   +40

Flag
Coverage Δ

compliance-web
23.05% <7.69%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Flextype Core: Entries - reduce the number of calls to the file system inside fetch methods.

There is possible issue with concurrency requests per page. [need to research]
fetch and fetchAll should be reviewed and should be reduced the number of calls to the file system, especially for fetchAll method. need to research. Possible solution is to store fetchAll result inside class property.

proposition: to load all entries db into the memory to work with all of them.

proposition: move media files from entries into it is own section, for e.g. file library

proposition: to have new type of entities - collection and single

possible issue is here \Twig\Loader\FilesystemLoader
need more time to investigate with AB and other tools

Not issue for now, will investigate this in future releases

Done.


Mac fixes

A previous fix to make close() occur later can cause socket reuse by servers to fail as previous sockets are left asynchronously open.
This change:

adds a callback to TCP server shutdown to signal that the server is completely shutdown
wait for that callback before destroying listeners in the server (and before destroying the server)
handles fallout

On my Mac, this fails on end2end test (C++) with assertion:
E0407 21:38:50.427261000<PHONE_NUMBER> sync_posix.c:74] assertion failed: err == 0 || err == ETIMEDOUT || err == EAGAIN

I still see several C tests failing also.
bins/opt/tcp_posix_test
bins/opt/chttp2_fullstack_uds_invoke_large_request_test
bins/opt/chttp2_socket_pair_invoke_large_request_test
bins/opt/chttp2_transport_end2end_test
Some security-related tests, though I know at least some are failing because I need to upgrade OpenSSL ...

I don't think the point is to fix all of the problems - this is just one of
the issues, and not even a 100% reproducible one.
On Tue, Apr 7, 2015 at 9:43 PM, Vijay Pai<EMAIL_ADDRESS>wrote:

I still see several C tests failing also.
bins/opt/tcp_posix_test
bins/opt/chttp2_fullstack_uds_invoke_large_request_test
bins/opt/chttp2_socket_pair_invoke_large_request_test
bins/opt/chttp2_transport_end2end_test
Some security-related tests, though I know at least some are failing
because I need to upgrade OpenSSL ...
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1222#issuecomment-90800718.

Ok, I see. Then this is very helpful as it removes about 90% of the failures in C and most of the ones in C++ as well.

Yeah, this is progress, not completion.
I've only been back a day :)
On Tue, Apr 7, 2015 at 9:58 PM Vijay Pai<EMAIL_ADDRESS>wrote:

Ok, I see. Then this is very helpful as it removes about 90% of the
failures in C and most of the ones in C++ as well.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1222#issuecomment-90801863.

And what a day it's been!
On Tue, Apr 7, 2015, 10:20 PM Craig Tiller<EMAIL_ADDRESS>wrote:

Yeah, this is progress, not completion.
I've only been back a day :)
On Tue, Apr 7, 2015 at 9:58 PM Vijay Pai<EMAIL_ADDRESS>wrote:

Ok, I see. Then this is very helpful as it removes about 90% of the
failures in C and most of the ones in C++ as well.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1222#issuecomment-90801863.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1222#issuecomment-90805692.


Travis: Re-enable 0.12 builds.

Jest doesn't currently work for Node v0.12. Once https://github.com/facebook/jest/issues/243 is fixed, then re-enable 0.12 in .travis.yml

Fixed in #240.


Component library

We should incorporate a customizable component library so we don't need to re-invent the wheel for common UI components and so that we can re-use these components for any future projects.

Completed first stage of moving existing code.


[Question]: Getting this error with The binary version of its metadata is 1.9.0, expected version is 1.7.1.

What is your question?
I have added android_alarm_manager_plus: ^4.0.3 to pubspec.yaml
and when I run flutter build apk, I am getting this error:
'''
/.pub-cache/hosted/pub.dev/android_alarm_manager_plus-4.0.3/android/src/main/kotlin/dev/fluttercommunity/plus/androidalarmmanager/AlarmBroadcastReceiver.kt: (27, 18): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
The class is loaded from /Users/peterkim/.gradle/caches/transforms-4/44f32ef92a48a9a2ea0a5cd6f6ead497/transformed/jetified-kotlin-stdlib-1.9.23.jar!/kotlin/Unit.class
'''
here is my build.gradle:
'''
buildscript {
ext.kotlin_version = '1.9.24'
repositories {
google()
jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:7.2.0'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
}

}
'''
can someone suggest how to fix this?
Checklist before submitting a question

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I am using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

Please check plugin's requirements first and update your project accordingly: https://github.com/fluttercommunity/plus_plugins/tree/main/packages/android_alarm_manager_plus#requirements
You need to update Android Gradle Plugin version in your project.

I did followed the requirement and still getting the message.
here are some details for my env:
flutter --version
Flutter 3.22.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 5dcb86f68f (7 days ago) • 2024-05-09 07:39:20 -0500
Engine • revision f6344b75dc
Tools • Dart 3.4.0 • DevTools 2.34.3

java --version
java 17.0.7 2023-04-18 LTS
Java(TM) SE Runtime Environment (build 17.0.7+8-LTS-224)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.7+8-LTS-224, mixed mode, sharing)

android/gradle/wrapper/gradle-wrapper.properties
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
# distributionUrl=https\://services.gradle.org/distributions/gradle-7.6.3-all.zip
distributionUrl=https\://services.gradle.org/distributions/gradle-8.7-all.zip

android/build.gradle
allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = "../build"
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(":app")
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

buildscript {
    ext.kotlin_version = '1.9.24'
    // repositories {
    //     google()
    //     mavenCentral()
    // }

    // dependencies {
    //     classpath 'com.android.tools.build:gradle:7.2.0'
    //     classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    // }
}

android/app/build.gradle
plugins {
    id "com.android.application"
    id "kotlin-android"
    // The Flutter Gradle Plugin must be applied after the Android and Kotlin Gradle plugins.
    id "dev.flutter.flutter-gradle-plugin"
}

def localProperties = new Properties()
def localPropertiesFile = rootProject.file("local.properties")
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader("UTF-8") { reader ->
        localProperties.load(reader)
    }
}

def flutterVersionCode = localProperties.getProperty("flutter.versionCode")
if (flutterVersionCode == null) {
    flutterVersionCode = "1"
}

def flutterVersionName = localProperties.getProperty("flutter.versionName")
if (flutterVersionName == null) {
    flutterVersionName = "1.0"
}

android {
    namespace = "com.example.oci_alarm_manager"
    compileSdk = flutter.compileSdkVersion
    ndkVersion = flutter.ndkVersion

    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId = "com.example.oci_alarm_manager"
        // You can update the following values to match your application needs.
        // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
        minSdkVersion flutter.minSdkVersion
        targetSdkVersion flutter.targetSdkVersion
        // minSdkVersion 21
        // targetSdkVersion 32
        versionCode = flutterVersionCode.toInteger()
        versionName = flutterVersionName
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig = signingConfigs.debug
        }
    }
}

flutter {
    source = "../.."
}

can you tell me what's missing?

//     classpath 'com.android.tools.build:gradle:7.2.0'

Which version of the Android Gradle Plugin you use instead of this commented line? It needs to be at least 8.3.0.

I have tried as suggested and still getting the same error:
allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = "../build"
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(":app")
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

buildscript {
    ext.kotlin_version = '1.9.24'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:8.3.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.24"
    }
}

hello am getting the same error, any solutions yet

hello again, i tried this and it worked for me:
i specified the kotlin version in the settings.gradle file, and i did not bother adding it again in the build.gradle file
from this:
plugins {
id "dev.flutter.flutter-plugin-loader" version "1.0.0"
id "com.android.application" version "7.3.0" apply false
id "org.jetbrains.kotlin.android" version "1.7.10" apply false
}
to this:
plugins {
id "dev.flutter.flutter-plugin-loader" version "1.0.0"
id "com.android.application" version "7.3.0" apply false
id "org.jetbrains.kotlin.android" version "1.9.10" apply false
}

It worked for me:
https://github.com/flutter-stripe/flutter_stripe/issues/1669


Update Radix Colors docs

Update docs with the recent 1.0.0 changes
Add Releases page
Move /docs/colors/getting-started/* to /docs/colors/overview/* similarly to how it's structured in the Primitives docs, as "Releases" page didn't make sense in "Getting Started"
Fix broken tabs
Prioritise vanilla CSS tabs

LGTM!


FI-2396-redirect-session

Summary
Adds a check for the root of the URL for the new session redirect event; if there is no basePath defined, the root will default to the existing location origin. This will break if the origin and the intended base path are different.
Testing Guidance
TBD

Yep the flicker is annoying, have been trying to find a workaround for the workaround but since there's a double reload I think it stays unless we come up with another solution here for the requests/routing.


Reword injectStripe explanation

injectStripe was pretty confusing to me when I first saw it. Hopefully these
clarifications make it easier for people to understand without having to dive
into the source (or gives them a better idea of what to look for if they do
look at the source).

Thanks, Jake!
lgtm


deepspeech2 modify for kunlun

PR types
Others
PR changes
Others
Describe
deepspeech2 modify for kunlun

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


Issue refactor

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
yes

License
Apache 2.0

What's in this PR?
Refactor issue module similarly to the notification module.
Checklist

[x] Implementation tested (with at least one cloud provider)
[x] Error handling code meets the guideline
[x] Logging code meets the guideline (TODO)

@colin014 I checked and it looked like notifications are only fetched once the user logged in. Any reason why we would fetch notifications prior to login?

CircleCI does not work. :\


Update podspec to support v6.5.0

Changelog
Fix
Crash on ios 13 & above , after dismissing campaign, and rotating device
Update
Build with Xcode 12.0

:tada: This PR is included in version 0.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


BUG: Fix for scipy.special seterr, geterr, errstate

What does this implement/fix?

This PR is an alternative to #20316. scipy.special.seterr, scipy.special.geterr, scipy.special.errstate currently do not work for ufuncs not implemented in the extension module _ufuncs (whose cython code is generated by _generate_pyx.py). This is because sf_error.c manages an error state in a static array, and currently each extension module has a separate copy of sf_error.c compiled in, when they actually all should be sharing this state. As identified by @izaid, a potential solution is to manage this state in a shared library. This PR differs from #20316 in that the shared library only manages the shared state and nothing else. I think it's best to go with the minimal set of changes for now in order to leave more options open for the future.

@rgommers, the failing job is trying to build a wheel on windows. Are we running against a fundamental limitation like mentioned here or is there some secret sauce to get this to work because the shared library is being used only by extension modules that live alongside it in the same folder?

I guess maybe something with delvewheel like here?

Yep, adding the path with delvewheel should work - it's also the recommended solution at https://mesonbuild.com/meson-python/reference/limitations.html#shared-libraries-on-windows. https://github.com/mesonbuild/meson-python/pull/551 may avoid the need for this in the future (I really need to test that).

I guess maybe something with delvewheel like here?

Yep, adding the path with delvewheel should work - it's also the recommended solution at https://mesonbuild.com/meson-python/reference/limitations.html#shared-libraries-on-windows. mesonbuild/meson-python#551 may avoid the need for this in the future (I really need to test that).

Cool. Thanks. I’m setting up windows in a virtual machine so I can work this out locally.

I found a solution which works locally on windows: extracting the contents of the wheel  to a temporary directory and taking lib_sf_error_state.dll out of the extracted wheel and putting it on the path delvewheel searches. Hopefully this works in the action too.

Nice! That did it. It looks like I also need to update https://github.com/scipy/scipy/blob/main/tools/wheels/repair_windows.sh

Nice! That did it. It looks like I also need to update https://github.com/scipy/scipy/blob/main/tools/wheels/repair_windows.sh

Fantastic news! Glad you were able to sort this out (relatively) quickly.

hmm that sounds like it might be related to gh-19627

hmm that sounds like it might be related to gh-19627

Yeah. New test that just needs tolerance bump
https://github.com/scipy/scipy/blob/53467c8f3cbd5af234625f9effb9a0fde88dfb8a/scipy/signal/tests/test_filter_design.py#L4252-L4257

@rgommers, let me know if this solution looks OK.

We don't need to wait for that meson-python PR. This is the way to preload the DLL on Windows, preloading this new shared library should fix things: https://github.com/scipy/scipy/blob/bb92c8014e21052e7dde67a76b28214dd1dcb94a/tools/openblas_support.py#L239-L274
Try adding that to special/__init__.py and see if the delvewheel stuff can then be removed?

Try adding that to special/__init__.py and see if the delvewheel stuff can then be removed?

Very nice. I'll try this out

Thanks @rgommers! I was not expecting this to be so difficult either. I'll get to work on the fix you suggested after finishing up the AMOS complex issues.

5. This isn't threadsafe (nor was the old global state); this needs handling when work starts on free-threaded CPython support (a.k.a. no-GIL).

Hopefully we'll have all of the ufuncs in one extension module then, and we won't need to worry about this anymore.

Huh. That worked locally on my Windows VM.

OK, I get this same error locally now
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\hostedtoolcache\windows\Python\3.11.8\x64\Lib\site-packages\delvewheel\_dll_utils.py", line 403, in get_all_needed
    raise FileNotFoundError(f'Unable to find library: {dll_name}')
FileNotFoundError: Unable to find library: libsf_error_state.dll
repairing D:\a\scipy\scipy\dist\scipy-1.14.0.dev0-cp311-cp311-win_amd64.whl
finding DLL dependencies
Processing d:\a\scipy\scipy\dist\scipy-1.14.0.dev0-cp311-cp311-win_amd64.whl

The initial call to delvewheel is failing because it can't find libsf_error_state.dll on its search path.

Ok, this seems to have worked. Thanks for the suggestion @rgommers!

And thanks @izaid as well for the help!


Feature/443 add certs to images

Closes https://github.com/opendevstack/ods-pipeline/issues/443
I see providing certs locally in a folder only as a alternative or even transitional solution for developers to be able to build the docker images (make build-and-push-images) locally. In case we ever install ods-pipeline within a network that requires certs, we probably need to extend the solution by e.g. supplying a url from where the certs can be imported, see for example in ods-core https://github.com/opendevstack/ods-core/blob/master/jenkins/agent-base/import_certs.sh

got superseded by https://github.com/opendevstack/ods-pipeline/pull/450 and https://github.com/opendevstack/ods-pipeline/pull/452

@michaelsauter I'm not sure whether this is the best approach to this, what is your opinion?

Not sure either. I think there are two factors to consider:

with #404, we will likely build on top of pre-built images
we will probably need to add certs in the images in the cluster, not just locally

Given the above, I wonder if a solution like the "import certs script" used in ods-core/Jenkins is better suited?

Due to our discussions earlier I'm closing this without merging, right @michaelsauter ?

Phew, I am unsure right now so let's keep it open for now. We can close when we have settled on a solution fitting with #404. I also realized that at the moment, our requirements do not state that ODS pipeline should work in such network conditions. We should add this.

decision from open office hours:
add an import_certs script (like done in other parts of ods) into the dockerfile wrappers (https://github.com/opendevstack/ods-pipeline/tree/master/deploy/ods-pipeline/charts/images/docker)
for that to work we need to introduce a url var to the scripts to the cluster

I suggest to close this, as #517 implements an alternative solution and has been merged. Agree @renedupont?


[SAC-42] Unify Spark ML and Dataframe operator into a uniform Spark Process

This PR is used to combine Spark ML and DF operation into the same Spark Process.
For example:
Give a Spark application with ML and DF job, they are recorded into a same Spark Process in Atlas.

CC @dongjoon-hyun to also take a review.

Thank you for pinging me, @jerryshao .

@jerryshao and @dongjoon-hyun  can you review the update code?

I will add test cases.

if no further comments, I would like to merge this PR. @jerryshao @dongjoon-hyun


Background layer switcher

This branch adds a background layer switcher control to the map according to #203.

A description on how to configure background layers and preview images is available from the updated documentation.

Hi Christian, I just returned from a 2 weeks holiday. Thanks for the review, I will look into the requested changes and provide some basic unit tests. Regarding your questions.

The switcher becomes automatically visible, as soon as 1 base layer is configured.
Positioning uses CSS (for now). This is obviously not one of the generic modules, as the behavior and placement of the button is custom.

@chrismayer All requested changes should have been addressed now.

Thanks for your ongoing effort on this @fschmenger! Regarding your comments:

The switcher currently is always visible and I haven't introduced any config option to disable it.

OK for me at least for the moment. Let's have a look how often it is requested not to have the BackgroundSwitchter tool. As a workaround the button could be hidden by CSS in a Wegue application.

Positioning uses CSS (for now). This is obviously not one of the generic modules, as the behavior and placement of the button is custom.

Thanks for clarification. This is totally OK and it should be tackled in a bigger view, how to place modules, et. al.
I'll merge now.


define retry arg for AsyncRetrying

Related to issue #839 that I made

@anthonyivn2 this must be something inside OpenAI endpoints right? closing this for now but feel free to open this or comment down below. Have this fixed with v0.2


[WIP] added citation validator

created a script (check_cite.py) that checks if all the software packages mentioned in the paper are also cited correctly. Checks for all of the packages in the bibfiles folder.
Tests and example files to follow soon

This includes unrelated changes, and have conflicts. I'm happy to show how to fix this with a rebase.


[5.5.x] use encryption key for serf

Uses install operation ID (as a simple UID) as an encryption key for the serf cluster to prevent unrelated nodes from joining the cluster.
Requires https://github.com/gravitational/planet/pull/605.
Fixes https://github.com/gravitational/gravity.e/issues/3372.
Design doc: https://docs.google.com/document/d/10VV-RrGdf7V3AKHAhCaCnuCuMBr2zDXKyaZjGi5Pahk/edit#.

Moved discussion regarding upgrade to the attached google doc.

Closing until further notice.


Pi/blueprint policy

This adds the blueprint policy command requested in #610
Someone double check my work on calculating the policy ID, please; I always get confused as to exactly how the script needs to be encoded before being hashed.

LGTM


allow assign to array element

We might be able to allow assign to array element, meaning replace image band. So:
$image[1] = $image[0];

would mean:
$image = $image[0]->bandjoin([$image[0], $image[3]]);

@jcupitt I've made some untested code that might work:
public function offsetSet($offset, $value): Image
{
    if($value instanceof Image) {
        $bands = $this->bandsplit();

        $offset = !is_null($offset) && $this->offsetExists($offset) ? $offset : $this->bands - 1;
        unset($bands[$offset]);

        return $value->bandjoin($bands);
    } else {
        throw new \InvalidArgumentException("Image::offsetSet function only accepts instance of Image");
    }
}

public function offsetUnset($offset): Image
{
    $offset = !is_null($offset) && $this->offsetExists($offset) ? $offset : $this->bands - 1;

    $begin = $this->extract_band(0, ['n' => $offset]);
    $end = $this->extract_band($offset, ['n' => $this->bands - 1]);

    return $begin->bandjoin($end);
}

This enhancement is impossible to implement in our current setting, it requires that our Image class is a fluent interface. So for example:
$image = Image::newFromFile('example.png');

// Invert image
$image->invert();

// Rotate 90 degrees clockwise.
$image->rot90();

// Buffer contains a rotated-inverted image
$buffer = $image->writeToBuffer('.png')

Instead of:
$image = Image::newFromFile('example.png');

// Invert image
$image = $image->invert();

// Rotate 90 degrees clockwise.
$image = $image->rot90();

// Buffer contains a rotated-inverted image
$buffer = $image->writeToBuffer('.png')

If we make a internal function to get the the underlying vips image resource then it should be possible. See for example:
/**
 * Our ArrayAccess interface ... we allow [] to get band.
 *
 * @param mixed $offset The index to set.
 * @param Image $value  The band to insert
 */
public function offsetSet($offset, $value)
{
    if($value instanceof Image) {
        $bands = self::bandsplit();

        if(self::offsetExists($offset)) {
            unset($bands[$offset]);
        }

        $this->image = $value->bandjoin($bands)->getImageResource();
    } else {
        throw new \InvalidArgumentException("Image::offsetSet function only accepts instance of Image");
    }
}

/**
 * Our ArrayAccess interface ... we allow [] to get band.
 *
 * @param mixed $offset The index to remove.
 */
public function offsetUnset($offset)
{
    if(self::offsetExists($offset)) {
        $begin = self::extract_band(0, ['n' => $offset]);
        $end = self::extract_band($offset, ['n' => $this->bands - 1]);

        $this->image = $begin->bandjoin($end)->getImageResource();
    }
}

/**
 * Get the underlying vips resource.
 *
 * @return resource The underlying vips image resource.
 *
 * @internal
 */
public function getImageResource() {
    return $this->image;
}

Then we are able to do this (untested):
require __DIR__ . '/vendor/autoload.php';
use Jcupitt\Vips;

$image = Vips\Image::newFromFile($argv[1]);

$image[1] = $image[0];
unset($image[2]);

$image->writeToFile($argv[2]);

Here's a branch which implements all this:
https://github.com/jcupitt/php-vips/tree/add-array-access
Plus docs and some tests. Any thoughts?

Looks good to me! Added some inline comments.

OK, I think I've fixed the stuff you found.
I made it throw an exception if you try to delete all bands, does that sound right?
I made a small performance improvement: it only expands constants to images if they are the first band. This way it can use bandjoin_const for a small speed-up on band append.

Throwing an exception if you try to delete all bands, sounds right to me. We could also add this to the test case (so $this->expectException(BadMethodCallException::class); here).
Just 1 minor comment: my name is misspelled in that commit. For the rest, it all seems to be good. :smile:

OK, done and merged to master. Thanks!
Let's leave it a day or two for any issues to shake out, then do 1.0.3.


GH-34: Minor improvements and fixes.

fixes #34

@pgev There are merge conflicts. Github not allowing to approve and merge.


TS7022 (circular reference) on simple assignments in a loop

🔎 Search Terms
TS7022, implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer, circular reference, circular type
🕗 Version & Regression Information

This is the behavior in every version (3.3.3+) I tried, and I reviewed the FAQ for entries about circular references

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.5.2#code/CYUwxgNghgTiAEYD2A7AzgF3hAlikAXPJjHgOYDcAUBCFhiJkSefAD7woCuEE8AvJx4RqVAGZIY8ABS0sOAfAAMFeAoA82PCAB0tFGQwALVTgDUZgJTwA3lXiJUmREdiLc+ANo4AutQc4YjIMzvxhLrDWNgC+9o7oWFAQaEgAwq5SgmAZ-vAhWIJJKemw1LFAA
💻 Code
declare const line: string;
let test: string | null = null;

for (let i = 0; i < line.length; i++) {
  const char = line[i];
  if (test === char) {}
  const alsoChar = char;
  test = alsoChar;
}

🙁 Actual behavior
The following error is triggered:
'alsoChar' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.(7022)
🙂 Expected behavior
No errors. char is clearly a string and alsoChar is just a copy of it, so there shouldn't be any type confusion and/or circularity. test isn't even read from, except in the empty if statement.
Additional information about the issue

Removing the empty if on line 6 fixes the error.
Replacing the if on line 6 by if (test !== char) {} also produces the error, but if (test! < char) {} doesn't.
Replacing line 2 by let test: string | undefined = undefined; also produces the error, but let test: string | undefined; doesn't.

This version also reproduces the issue:
declare const line: string;
let test: boolean | null = null;

for (let i = 0; i < line.length; i++) {
  const char = line[i];
  if (test !== char) {}
  const alsoChar = char === ""; // <- using a simple comparison
  test = alsoChar;
}

Same for this one:
declare const line: string;
let test: string | null = null;

for (let i = 0; i < line.length; i++) {
  const char = line[i];
  if (test !== char) {}
  const alsoChar = char[0]; // <- changing char to char[0]
  test = alsoChar;
}

But this one doesn't:
declare const line: string;
let test: string | null = null;

for (let i = 0; i < line.length; i++) {
  const char = line[i];
  if (test !== char) {}
  const alsoChar = char.charAt(0); // <- char.charAt(0) instead of char[0]
  test = alsoChar;
}

Another interesting point is that despite the error, the tooltip does show const alsoChar: string as expected. This is recent, though: v5.3.3 shows the type as any, whereas v5.4.5 shows it as string.

Please see #33191 and #42529. The behavior change in 5.4 is likely attributed to #56753. It is indeed somewhat interesting that the tooltip does show a type other than any.

I'm fixing the weird inconsistent quick info display here: https://github.com/microsoft/TypeScript/pull/59075

Please see #33191 and #42529. The behavior change in 5.4 is likely attributed to #56753. It is indeed somewhat interesting that the tooltip does show a type other than any.

Those issues look similar but I'm not sure the root cause is the same. The supposed circularity in my repro code is being caused by an empty if statement which is essentially dead code here. I assume it's narrowing something internally but given that it's not affecting the control flow at all (can be removed with zero consequences to the runtime), I don't see a good reason for this narrowing to be occurring. (Well, in the code that sparked the issue the if statement is not exactly dead code, but it's still unrelated to the variable that's getting the error.)

I'm fixing the weird inconsistent quick info display here: #59075

Doesn't that make it worse, though? The problem is in the extraneous error here, the tooltip has the correct type...

The supposed circularity in my repro code is being caused by an empty if statement which is essentially dead code here

It requests type of test which in turn depends on the type of alsoChat. That's how the circularity happens here. I agree that it's weird that some very similar cases work without running into circularity.

Doesn't that make it worse, though? The problem is in the extraneous error here, the tooltip has the correct type...

The tooltip has the correct type somewhat accidentally here. CheckMode.TypeOnly was introduced to suppress comparability errors when dealing with intermediate types created during control flow analysis. Those errors that were suppressed by that PR didn't affect the control flow analysis at all. So it was OK to suppress them.
An encountered circularity returns any type and that very much can propagate through the types computed during control flow analysis. That's why I think it wouldn't be good to suppress this error here in a similar way.
That said, this alternative patch doesn't change anything in the existing test suite and it "fixes" your particular circularity issue:
diff --git a/src/compiler/checker.ts b/src/compiler/checker.ts
index a965c51d22..640a0216c5 100644
--- a/src/compiler/checker.ts
+++ b/src/compiler/checker.ts
@@ -12055,6 +12055,9 @@ export function createTypeChecker(host: TypeCheckerHost): TypeChecker {
             if (isBindingElement(declaration) && checkMode === CheckMode.Contextual) {
                 return errorType;
             }
+            if (checkMode && checkMode & CheckMode.TypeOnly) {
+                return anyType;
+            }
             return reportCircularityError(symbol);
         }
         let type: Type;
@@ -12137,6 +12140,9 @@ export function createTypeChecker(host: TypeCheckerHost): TypeChecker {
             if (isBindingElement(declaration) && checkMode === CheckMode.Contextual) {
                 return type;
             }
+            if (checkMode && checkMode & CheckMode.TypeOnly) {
+                return anyType;
+            }
             return reportCircularityError(symbol);
         }
         return type;

But despite that, I think it's rather risky to allow this to propagate freely because the result propagates. Similarly, getTypeOfExpression sets NodeFlags.TypeCached on the node but in this scenario the type wouldn't actually be cached! That's just a different bug waiting to happen somewhere.
I also checked that it wouldn't have a perceivable bad impact on this scenario with an auto type:
declare const line: string;
let test;

for (let i = 0; i < line.length; i++) {
  const char = line[i];
  if (test === char) {}
  const alsoChar = char;
  test = alsoChar;
}

FWIW, I'm not saying that the circularity avoidance couldn't be improved for some of those cases. I feel like the change I proposed is good regardless of that.

#56753 is being superceded by #59183. This is a true circularity for basically the same reason as https://github.com/microsoft/TypeScript/issues/33191#issuecomment-1969952438.
See also https://github.com/Microsoft/TypeScript/wiki/FAQ#circularity-errors-may-occur-in-the-presence-of-circularities


ui: fix wrong feedback on vccuelist in stepmode

The vccuelist feedback (Side Fader) works fine in Crossfade-Mode but in Steps-Mode the feedback values goes crazy.

Makes perfect sense, thank you 👍


Bump base Alpine version and Java version

Bumps the base Alpine version to resolve some CVEs. Also bumps the minor Java version.

cc/ @llinder @jcchavezs

The readme clearly says to strip it out when calling the build script. From the scripts, I think that ends up as the java_version arg in the docker build, so the default in the Dockerfile does not apply. I have removed the suffix in the docker file and added a note about it for anyone that runs into this in the future.


Use a local server address

Hello,
Is it possible to configure the Mock server for a local address only (in 127.x.x.x), to avoid to expose Mock on network ?
Thanks,

Hi @Jnp95,
Thanks for your question.
I think this is more of a networking issue rather than something application specific. As a piece of software sMockin is only aware of the local ports (i.e H2 DB, admin & mock server) it's binds too.
You should be already able to access either admin or the mock server using the local IP addresses:
e.g
http://<IP_ADDRESS>:8000/templates/main.html

curl -i -X GET http://<IP_ADDRESS>:8001/helloworld

In terms of safe guarding access, this really comes down to configuring your local firewall (to block / expose these ports and set up any traffic rules) and potentially any HTTP servers (such as apache / nginx) you may have positioned as a gateway.


Updates Spring Boot and Gradle versions

Signed-off-by: Sean Sundberg<EMAIL_ADDRESS>

Addresses cloud-native-toolkit/planning#863


fix(db): inherit generics in valueChanges interface

Checklist

Issue number for this PR: #1214 (required)
Docs included?: not required
Test units included?: no
In a clean directory, npm install, npm run build, and npm test run successfully?: yes

Thanks @Maistho!


Memoryleak using Transformer when running pub serve

I'm currently running into a memory leak using pub serve.
The pubspec looks like this:
name: myapp
version: 0.0.1
description: Myapp.
dependencies:
  polymer: ^1.0.0
  polymer_elements: any
  web_components: ^0.12.0
  browser: any
  route_hierarchical: any
  protobuf: any
  uuid: any
  lawndart: any
  quiver: any
  reflectable: 0.2.0
transformers:
- web_components:
    entry_points:
    - web/index.html
#    - test/app_test.html
- reflectable:
    entry_points:
    - web/index.dart
#    - test/app_test.dart
- test/pub_serve:
    $include: test/**_test{.*,}.dart
- $dart2js:
    minify: false
    sourceMaps: true
    verbose: true
dev_dependencies:
  test: ^0.12.3
environment:
  sdk: ">=1.2.0 <2.0.0"
dependency_overrides:
  polymer:
    git:
      ref: behaviors
      url: https://github.com/dart-lang/polymer-dart.git
  polymer_interop:
    git:
      ref: 0.2.0-dev
      url: https://github.com/dart-lang/polymer_interop.git
  polymer_elements:
    git:
      ref: master
      url: https://github.com/dart-lang/polymer_elements.git
  reflectable:
    path: ../reflectable/reflectable

Im running this to prevent pub from taking all the memory available.
export DART_VM_OPTIONS=--observe
ulimit -Sv 4000000
pub serve --mode debug --hostname <IP_ADDRESS> --port 7080

I tried to find the reason using Observatory. The top classes from the allocation profile are

LinkEntry
_List
Context.

Seems to be the same issue I run into

Missing entry point: web/forms/selecting_many_items_using_checkboxes/index.dart
Exhausted heap space, trying to allocate 586272 bytes.
Exhausted heap space, trying to allocate 96 bytes.
in ShutdownIsolate: Unhandled exception:
Uncaught Error: Out of Memory
Stack Trace:
#0      _AllMatchesIterator.moveNext (dart:core-patch/regexp_patch.dart:268)
#1      _StringBase.replaceFirst (dart:core-patch/string_patch.dart:573)
#2      getErrorMessage (package:$pub/utils.dart:20)
#3      CrossIsolateException.serialize (package:$pub/serialize/exception.dart:45)
#4      serializeException (package:$pub/serialize/exception.dart:88)
#5      respond. (package:$pub/serialize.dart:164)
#6      _RootZone.runBinary (dart:async/zone.dart:1170)
#7      _Future._propagateToListeners.handleError (dart:async/future_impl.dart:529)
#8      _Future._propagateToListeners (dart:async/future_impl.dart:588)
#9      _Future._completeError (dart:async/future_impl.dart:384)
#10     _SyncCompleter._completeError (dart:async/future_impl.dart:56)
#11     _Completer.completeError (dart:async/future_impl.dart:27)
#12     TransformerImplementation.apply.<apply_async_body> (package:reflectable/src/transformer_implementation.dart:2008)
#13     _Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:670)
#14     _Future._propagateToListeners (dart:async/future_impl.dart)
#15     _Future._asyncComplete. (dart:async/future_impl.dart:376)
#16     _microtaskLoopEntry (dart:async/schedule_microtask.dart)
#17     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart)

#0      _rootHandleUncaughtError. (dart:async/zone.dart:894)
#1      _microtaskLoop (dart:async/schedule_microtask.dart:43)
#2      _microtaskLoopEntry (dart:async/schedule_microtask.dart:52)
#3      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)
#4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)
After about 10-20 reloads I get this exception.
name: polymer_dart_samples
description: Port of https://github.com/PolymerLabs/polymer-snippets
environment:
  sdk: '>=1.2.0 <2.0.0'
dependencies:
  polymer_elements:
    git: git@github.com:dart-lang/polymer_elements.git
  web_components: ^0.12.0
  polymer: ^0.17.0
transformers:
- web_components:
    entry_points:
    - web/forms/binding_a_boolean_field_to_a_checkbox/index.html
    - web/forms/binding_to_a_text_input/index.html
    - web/forms/binding_to_a_textarea/index.html
    - web/forms/implementing_simple_autocompletion/index.html
    - web/forms/implementing_simple_validation/index.html
    - web/forms/selecting_one_item_using_radio_buttons/index.html
    - web/forms/selecting_many_items_using_checkboxes/index.html
   # - web/events/using_custom_events/index.html
    - web/styling_elements/applying_styles_by_piercing_shadow_dom_boundaries/index.html
    - web/styling_elements/defining_styles_inside_a_polymer_element/index.html
    - web/styling_elements/programmatically_changing_the_styles_of_an_element/index.html
    - web/styling_elements/styling_distributed_nodes/index.html
    - web/styling_elements/using_host_context_to_theme_an_element/index.html
    - web/styling_elements/using_host_with_a_css_selector/index.html
    - web/styling_elements/using_host_with_pseudo_classes/index.html
    - web/layout_attributes/nesting_flex_layouts/index.html
    - web/layout_attributes/using_flex/index.html
    - web/layout_attributes/using_layout_attributes/index.html
    - web/polymer_elements/paper_toolbar/adding_a_menu_button/index.html
    - web/polymer_elements/paper_toolbar/adding_button_rows/index.html
    - web/polymer_elements/paper_toolbar/changing_the_toolbar_size/index.html
    - web/polymer_elements/paper_toolbar/using_paper_toolbar/index.html
- reflectable:
    entry_points:
    - web/forms/binding_a_boolean_field_to_a_checkbox/index.dart
    - web/forms/binding_to_a_text_input/index.dart
    - web/forms/binding_to_a_textarea/index.dart
    - web/forms/implementing_simple_autocompletion/index.dart
    - web/forms/implementing_simple_validation/index.dart
    - web/forms/selecting_one_item_using_radio_buttons/index.dart
    - web/forms/selecting_many_items_using_checkboxes/index.dart
    - web/styling_elements/applying_styles_by_piercing_shadow_dom_boundaries/index.dart
    - web/styling_elements/defining_styles_inside_a_polymer_element/index.dart
    - web/styling_elements/programmatically_changing_the_styles_of_an_element/index.dart
    - web/styling_elements/styling_distributed_nodes/index.dart
    - web/styling_elements/using_host_context_to_theme_an_element/index.dart
    - web/styling_elements/using_host_with_a_css_selector/index.dart
    - web/styling_elements/using_host_with_pseudo_classes/index.dart
    - web/layout_attributes/nesting_flex_layouts/index.dart
    - web/layout_attributes/using_flex/index.dart
    - web/layout_attributes/using_layout_attributes/index.dart
- $dart2js:
    $include: '**/*.bootstrap.initialize.dart'
dependency_overrides:
  polymer:
    git:
      ref: aea190df60e6c9d20078d89919443dea8e1b1997
      url: https://github.com/dart-lang/polymer-dart.git
  polymer_interop:
    git:
      ref: 0.2.0-dev
      url: https://github.com/dart-lang/polymer_interop.git
  reflectable: 0.2.0

Thanks for the bug report.
This might be some caching gone astray.
But from the provided information it is hard to say exactly where the problem is.
Are you able to provide the program itself that causes the leak so we can investigate further?

I had this a few times when I worked on https://github.com/bwu-dart-contributing/polymer-dart-patterns/tree/master/web/forms/implementing_simple_autocompletion
I haven't tried if simply reloading without changing anything leads to OOM.

I updated the link, I forgot to link to the right branch (0.17.0).

I don't think that reloading unchanged files causes this because the transformer is not running. I did a lot of reloads and nothing happens. If you want to trigger it even small changes to the code like add/removing a comment to a print statement will cause this behavior after some iterations.
If it's still necessary I will try to provide a stripped down example but that will take some time for preparation.

I tried to perform a small experiment: I ran pub serve in polymer-dart-patterns and loaded http://localhost:8080/layout_attributes/nesting_flex_layouts/index in dartium, and then did touch web/layout_attributes/nesting_flex_layouts/index.dart every 20 seconds. This causes pub serve to re-transform at each touch for a while (saying 'Build completed successfully' about 9 times, then just '[Info from Reflectable..]' without 'Build'), and then it stopped (no more output in the terminal, anyway). At the same time we have a growing process (ps shows 10GB, 19GB, 28GB).
I'll experiment a little more with that.

Looks similar to my experience. At first Dartium starts to time out and after a few more retries it crashes with OOM.

@eernstg This should be the issue I'm experiencing.
@zoechi Is the OOM in Dartium, too?

@wienczny I'm not sure what you mean by "in Dartium".
pub serve crashes with OOM and I use the reflectable transfomer only with Polymer 1.0.0-rc1 (client-side with Dartium).

@zoechi I was not sure whether the "it" from your post referred to pub or Dartium.

I found a similar issue. Might be related dart-lang/polymer-dart#401

I just landed a commit (8fbd26983a2e1b4faa7f005af1cbf6fb1271e5da) that changes the transformer in a tiny way syntactically, but it makes a difference in practice: The test scenario that I ran yesterday where pub serve serving 'http://localhost:8080/iron_validatable_behavior/index.html' to dartium could run 9 transformations before it started to fail now runs 150 transformations with no signs of trouble. The process still grows over time, but much less. The point is that we now use a single Resolvers instance rather than one per transformation.

Sounds great!


Update documentation with correction

the documentation for handling access through service principal had a small error

@vaerge : Thanks for your contribution! The author, @linda33wj, has been notified to review your proposed change.

Thanks for pointing this out. The issue has been fixed in separate PR and the current live doc is correct.
#please-close


jet: 0.3.21 -> 0.4.23

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/borkdude/jet/releases.
meta.description for jet is: CLI to transform between JSON, EDN, YAML and Transit, powered with a minimal query language
meta.homepage for jet is: https://github.com/borkdude/jet
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.23 with grep in /nix/store/c9ig53969amn5vigix7y6shlc58z3x4d-jet-0.4.23
found 0.4.23 in filename of file in /nix/store/c9ig53969amn5vigix7y6shlc58z3x4d-jet-0.4.23

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jet

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c9ig53969amn5vigix7y6shlc58z3x4d-jet-0.4.23 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jet https://github.com/r-ryantm/nixpkgs/archive/e5219c58d24680b7771ffe78837ffe87d7e8b8ed.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c9ig53969amn5vigix7y6shlc58z3x4d-jet-0.4.23
ls -la /nix/store/c9ig53969amn5vigix7y6shlc58z3x4d-jet-0.4.23/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

jet

Maintainer pings
cc @ericdallo for testing.

Result of nixpkgs-review pr 213963 run on aarch64-darwin 1

1 package built:

jet


DLR creation memory usage is linear in $\beta$ (should be $\log\beta$)

Description
This is a reposting of the triqs issue: TRIQS/triqs#917 showing that the memory usage building the DLR basis is linear in the inverse temperature $\beta$, preventing the use of DLR at low temperatures. This is probably caused by the current approach to select DLR Matsubara frequencies, since a dense Matsubara grid is used with an upper cutoff proportional to $\beta$.
See the memory scaling test here: TRIQS/triqs#917
Expected behavior: The peak memory usage should be $\log \beta$ for the DLR basis to be applicable in the low temperature regime.
Actual behavior: Peak memory usage is linear in $\beta$

Please see my response in the TRIQS repo. I'm going to label this as a feature request here, not a bug report.

Since this is really a cppdlr issue, let's discuss here. I am quoting your response in the corresponding TRIQS issue below:

Dear Jason,
I agree that there are many ways to handle this.
I think that since we have an upper bound on how many imaginary frequency points the DLR construction will select (given by the epsilon rank r of the real-frequency rank revealing QR) it is possible to construct a dyadic grid that terminates at the order Λ which is the current imaginary frequency cutoff. I have experimented with this in pydlr and it is working out well.
The idea is to put out panels on the positive Matsubara frequency indices where the first panel contains all r first Matsubara indices, the second panel contains every second index still keeping r points, the third panel takes every 4th index up to r points retained, etc. The number of panels is controlled by the upper cutoff Nmax=ceil(Λ) just as we are currently doing it. (Finally the index panels are also used for the negative frequency indices.)
Here is a code example that constructs the range of indices with panels with doubled spacing for each panel index when the flag dense_imfreq=False:
        if dense_imfreq:
            n = np.arange(-nmax, nmax+1)
        else:
            # -- Sparse starting grid in imaginary frequency
            r = self.rank
            n_panels = int(np.ceil(np.log2(nmax/r))) + 1 if nmax > r else 2
            n = np.zeros(r * n_panels)

            idx = 1
            for p in range(n_panels):
                d_idx = r * 2**p
                nn = np.arange(idx, idx + d_idx, 2**p)
                n[r*p:r*(p+1)] = nn
                idx += d_idx

            n = np.concatenate((1-n[::-1], n))

and here is the commit that implements this in pydlr jasonkaye/libdlr@ff40d13
Can I go on and implement this in cppdlr?
Best, Hugo

This is basically my suggestion (3) in my previous reply, and if it appears to be working, I am all in favor of implementing it, with some caveats. Given that this is a heuristic, and to avoid a proliferation of flags, for the time being I would try to do this by modifying the current code to give the user the option to pass in either an nmax, yielding the same behavior as now, or their own specified fine grid. This would first need to be an alternative constructor to imfreq_ops. Then, one would also need an alternative version of build_k_if. And then one would need to modify some more code in the imfreq_ops constructor slightly (extracting imaginary frequencies from pivots). This way, we maintain the current API, but also give the user the option to pass in a fine imaginary frequency grid of their choosing. Furthermore, you can make a function which generates your particular fine grid. Then we can decide later on if we want to make this more of the "default" in one way or another.
Also, it would be great if you could include a reasonably convincing test that this works as well as as the full fine imaginary frequency grid (e.g., giving just as small interpolation error for a few examples).
If that sounds reasonable to you and you want to go ahead and implement it, perhaps you can do it as a pull request and then we can look it over.
Thanks,
Jason

Hey guys, just stumbled over this issue, hope it is okay to comment "across the aisle":
I agree with @jasonkaye and @HugoStrand, I think strategy (3) should work nicely. For the IR basis, we found that you have considerable leeway in how you exactly choose the sampling frequencies without affecting the conditioning of the problem too much, as long as you make sure that the lowest couple of Matsubara frequencies are in your set. This is why we are fine with choosing the discrete sign changes of the highest-order basis function ...
In general, we find that the conditioning of the fitting problem in tau-space in 0.5 \sqrt\Lambda, while in Matsubara, you get 2 \sqrt\Lambda if you do it optimally, and you should still be within 4 \sqrt\Lambda or so if you don't exactly nail your frequency points.
As for strategies (1) and (2), what one finds empirically for many bases, for example the Fourier-transformed Chebyshev polynomials, is that for the lowest sampling frequencies, the "true" sign changes on the imaginary axis are extremely close to the Matsubara frequencies. So that is something you could think about. This might also explain why choosing Matsubara frequencies works reasonably well.

Hey @mwallerb!
Thank you for the input! I'll have a closer look at the prefactors on the coordination numbers of the transforms.
Regarding the sign changes in the Matsubara frequency representation of the Chebyshev polynomials, we saw the same trend when extending the Matsubara sparse sampling to Legendre polynomials, see Appendix B in https://doi.org/10.1103/PhysRevB.106.125153.
Cheers, Hugo

Thanks a lot, @HugoStrand - I missed this appendix in your paper!


Question: Is there a way to check if the dataset is lossless?

Hi @linjieli222
Since the dataset requires transferring large files, file corruption may occur due to network failures. Is there a way to check if the file I have received has been successfully downloaded without loss? (something like md5sum)

@liveseongho
Thanks for your great suggestion. We can provide such information for the compressed video dbs. Will update the corresponding md5sum numbers here once available.

Sorry about the delay. Below is the md5sum results for video_db/*.tar files:

how2.tar f618bc183352d3eaebd2cd4be2374767
tv.tar 6fad0fa4934a6ac7fd08b3ecef66afde
vatex.tar a75f964ae5a2a8456eb13e84eeaa5486
violin.tar a1218a0d81ef027daaab91ee3040e66b
vlep.tar 3e43f66b6aec75279341230ba2993844
yc2.tar c5224aa05c072ed8df9b0a7572adb13a

Thank you!!


New Templates with Projects Section (Issue #4)

I did my best to add a portfolio section to all the resume templates. Some of the css is a little off but I hope it can be worked on and merged.

Hello @sajattack
the PR breaks the layout of the templates, see screenshot.

Please do also not commit any unchanged files like person.jpg.

Can you be more specific about what is broken?

@sajattack  the complete layout is broken. Its now a 3-column grid and the icons overlap the borders of the shaddow-boxes.

@pubkey The 3 column-grid was intentional. I'll see what I can do about the icons.

@sajattack Please also do not adjust the existing templates, just add your changes as new ones. Then people can choose between different templates.

@salomonelli I don't really have the frontend expertise to design a whole template myself.

I meant by creating a new template, you just copy your content of e.g. left-right.vue into a new file called left-right-projects.vue. Then just follow the instructions on how to add left-right-projects.
Like this we can have two examples of a cv with projects and without. Also people can decide which one they rather like.

Not sure why the pdfs are conflicting

In /src/pages/home.vue insert the added templates like this:

      <router-link v-bind:to="'/resume/left-right-project'">

          left-right-project

      </router-link>

Could you please try to decrease the font-sizes?

Is it possible to add the template in the menu dynamically instead of writing a full html block for each template? Maybe it's also possible to create a templates.js file or somewhere else a list of all templates.

@mbndr PR is welcome

"Could you please try to decrease the font-sizes?" I didn't increase any font sizes. Why? @salomonelli

No comments on this for a while. Can you explain what you would like to see to have this merged @salomonelli ?

@sajattack Sorry, I am just like super busy :) I checked it once more, the only one that does not seem to fit is the side-bar-projects-template. Maybe you could decrease the font-size just for that one? The education part is cut off. Everything else works fine!

@salomonelli How do I generate the assets for the previews on the home page?

I am going to write a script that exports the pdfs also as pngs. At the moment you will need to do this manually.

@salomonelli Ok should be ready to merge now.

this is the oldest open pull request. Is anyone interested in updating the code for merge?

Updates have been merged into the project.


[MRG] Updated urls.

Closes https://github.com/mne-tools/mne-python/issues/2981

Did you test the code? I suspect there will be some MD5sums that need updating.

Yeah I tested it. The brainstorm data doesn't seem to have a hash.

is it the only dataset not having one?

Yep.

that's good enough for me.
@Eric89GXL if you feel like a hash would be nice to have. I'll let you take care of it.


[HOLD for payment 2024-11-28] Create expense button on empty Search page allows to create expense for non-migrated users

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

Version Number: v9.0.61-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Issue was repro when executing this PR: https://github.com/Expensify/App/pull/51979
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Go to staging.expensify.com/inbox
Sign in with a new Gmail account.
Create a Control workspace (not Collect).
Log in to staging.new.expensify.com with the same account.
Click FAB > Create submit (or any expense option).
Note that it shows Coming soon modal.
Go to Search.
Click Create expense on the empty state modal.

Expected Result:
Create expense button on the empty Search page will open Coming soon modal.
Actual Result:
Create expense button on the empty Search page allows user to create expense.
Workaround:
Unknown
Platforms:

[ ] Android: Standalone
[ ] Android: HybridApp
[x] Android: mWeb Chrome
[x] iOS: Standalone
[ ] iOS: HybridApp
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/703d5fc8-8a7e-4aef-8577-6a75c557eff9

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @adelekennedy / @adelekennedy

Clarifying in the main issue if the original contributor wants to take this over.

Looks like @ishpaul777 will take this over as a follow up to the PR that introduced this feature.
Removing a deploy blocker label since this is a new feature.

BugZero Checklist:

[x] [Contributor] Classify the bug:

Bug classification

Source of bug:

[ ] 1a. Result of the original design (eg. a case wasn't considered)
[ ] 1b. Mistake during implementation
[ ] 1c. Backend bug
[x] 1z. Other: A requirement for the new feature was missed in a case that wasn't considered.

Where bug was reported:

[ ] 2a. Reported on production
[x] 2b. Reported on staging (deploy blocker)
[ ] 2c. Reported on both staging and production
[ ] 2d. Reported on a PR
[ ] 2z. Other:

Who reported the bug:

[ ] 3a. Expensify user
[ ] 3b. Expensify employee
[ ] 3c. Contributor
[x] 3d. QA
[ ] 3z. Other:

[ ] [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: I think there isn’t an offending PR here, as a case wasn’t considered in the description and this issue is a part of #51804

[ ] [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A

[x] [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
N/A: It isn't an impactful bug

@adelekennedy looks like this is ready to pay?

Contributor: @suneox  paid $250 via Upwork
Contributor: @ishpaul777  owed $250 via Upwork

Hello.
I'm a full stack with experience in AI, blockchain and web development.
I hope to join your team.
Best regards.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/nishantvrastogi

Thanks for joining your team.
I'll try to implement your requirements with high quality within your timeline.

Thanks for your email.
I will try to implement your requirements with high quality within your
timeline.
Best regards
On Fri, Dec 6, 2024 at 3:59 AM melvin-bot[bot] @.***>
wrote:

✅ Contributor details stored successfully. Thank you for contributing to
Expensify!
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/52457#issuecomment-2522557484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNP4GVSIB5VMYFG5C7WZ6YL2EFRN3AVCNFSM6AAAAABRWCVNB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGU2TONBYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@adelekennedy Thank you! I’ve accepted an offer

@creativedev814, @RastogiNishant  Welcome to Expensify! First, please take some time to read through the guidelines on how to contribute to this project. This will help you understand the process and expectations for contributing effectively.

What should I do now?

Thank you, I will check it out.
On Fri, Dec 6, 2024 at 4:34 AM Cong Pham @.***> wrote:

@creativedev814 https://github.com/creativedev814, @RastogiNishant
https://github.com/RastogiNishant Welcome to Expensify! First, please
take some time to read through the guidelines
https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md
on how to contribute to this project. This will help you understand the
process and expectations for contributing effectively.
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/52457#issuecomment-2522646396,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNP4GVSMOU7TTW4JA6UU5VT2EFVTBAVCNFSM6AAAAABRWCVNB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGY2DMMZZGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Glad to hear it!
On Fri, Dec 6, 2024 at 2:26 PM adelekennedy @.***>
wrote:

Closed #52457 https://github.com/Expensify/App/issues/52457 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/52457#event-15564818052, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BNP4GVQIUYYM4IW72NZOXPT2EH27JAVCNFSM6AAAAABRWCVNB6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGU3DIOBRHAYDKMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I hope to join your team.
I have deep knowledge in web development, blockchain, AI and trading.
I hope to hear from you.
Best regards