alarm on live reload seems to be executed in a different context, causing issues

I am getting this kind of error
Error: Some functionality, such as asynchronous I/O (fetch, Cache API, KV), timeouts (setTimeout, setInterval), and generating random values (crypto.getRandomValues, crypto.subtle.generateKey), can only be performed while handling a request.
    at assertInRequest (/home/wighawag/dev/wighawag/tools/ethereum-events-worker/node_modules/.pnpm/@miniflare+shared@2.5.1/node_modules/@miniflare/shared/src/context.ts:29:11)
    at /home/wighawag/dev/wighawag/tools/ethereum-events-worker/node_modules/.pnpm/@miniflare+core@2.5.1/node_modules/@miniflare/core/src/standards/timers.ts:15:28
    at /home/wighawag/dev/wighawag/tools/ethereum-events-worker/node_modules/.pnpm/@ethersproject+providers@5.6.8/node_modules/@ethersproject/providers/src.ts/json-rpc-provider.ts:135:9
    at new Promise (<anonymous>)
    at timer (/home/wighawag/dev/wighawag/tools/ethereum-events-worker/node_modules/.pnpm/@ethersproject+providers@5.6.8/node_modules/@ethersproject/providers/src.ts/json-rpc-provider.ts:134:12)
    at StaticJsonRpcProvider.<anonymous> (/home/wighawag/dev/wighawag/tools/ethereum-events-worker/node_modules/.pnpm/@ethersproject+providers@5.6.8/node_modules/@ethersproject/providers/src.ts/json-rpc-provider.ts:420:15)
    at Generator.next (<anonymous>)
    at /home/wighawag/dev/wighawag/tools/ethereum-events-worker/dist/index.mjs:27135:67
    at new Promise (<anonymous>)
    at __awaiter3 (/home/wighawag/dev/wighawag/tools/ethereum-events-worker/dist/index.mjs:27117:10)

It happens when I update code and then when the alarm get triggered, I get that error in the alarm handler

I did not encounter this issue for a while now, so not sure what caused the issues and I did not record the commit where it happened
the repo is https://github.com/conquest-eth/do-ethereum-events
and this is the state of the repo 13 days ago :  https://github.com/conquest-eth/do-ethereum-events/tree/513ed0108ff13ed2d0bad60098e1af03c12dc6a0
Not sure if it this will help, but if I encounter again I ll post it


CallInfo API

CallInfo is API to listen a call state like 'ringing', 'offhook', 'idle', it's supported only on Android.
CallInfo.addEventListener('change', state => {
   ...
})

Also I'm going to add 'incoming/outgoing' and 'phone number' information.
How do you think it is a good idea to continue working on this PR? Or it's better to extract it into a separate repo? I would be glad to maintain this feature in react-native.

Thanks for this PR! Given that it's completely isolated, I think it would actually make a lot of sense as a 3rd party extension.
It seems like there's already https://www.npmjs.com/package/react-native-call-receiver# but the github page is gone.

@javache ok thanks, will do an extension


Dropdown published with wrong js file

Maybe I am wrong, but I have found that the dropdown.js file installed with "npm install ng-semantic --save" present in ng-semantic/dropdown and ng-semantic/bundles/ng-semantic.js is the transpiled version of  master/demo/app/components/dropdown.ts. Hence, the component will not work.

Yea, sm-dropdown is not ready yet, let me fix it.

@Eduardo-M-Cavalcanti I think this is fixed with new version?


no property autocomplete in JSX(related with an empty space)

VSCode Version: Version 1.19.1 (1.19.1) 0759f77bb8d86658bc935a10a64f6182c5a1eeba

OS Version: macOS, 10.12.6

Steps to Reproduce:
TypeScript React, and https://twitter.com/jiyinyiyong/status/946642303950626817
Reproduces without extensions: Yes.

Any update on this? The Ctrl-Space works and provides the correct autocomplete options for props with associated type. Would be nice if I didn't have to do that each time.

@kevinmlong Have the same problem, but wonder about: "... autocomplete options for props ...". Is VS Code capable to autocomplete my custom propTypes from an imported component?


Add variable to disable default cloud posse tags

Thanks for this open source module, I'm planning to use it to setup CloudTrail logs for auditing.
I'm making this PR because in my project we have our own tag naming schema and that does not play well together with Cloud Posse's scheme. I understand if this change isn't really interesting for you, but I think it's a nice addition for people, like me, that want to use your modules without having extra tags being created on the resources.
I'm happy to accommodate any change you recommend, let me know.

ping @aknysh @vadim-hleif: could one of you please let me know if this PR is in any way interesting for you? I would like to use other modules in your organisation but first I need to know you are open to such PRs.


add "for package creators section" on README.md

add some instructions for package creators
It requires password to download packages .  but I dont know
rsync -avz --progress --delete packages@packages.red-data-tools.org:public/debian/ repositories/debian
<EMAIL_ADDRESS>password:

Thanks.
We manage SSH public keys for<EMAIL_ADDRESS>in https://github.com/red-data-tools/packages.red-data-tools.org/blob/master/ansible/files/home/packages/.ssh/authorized_keys .


inetutils: use platforms.unix per feedback that works w/Darwin too.

https://github.com/NixOS/nixpkgs/pull/39773#discussion_r185143821

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: inetutils
Partial log (click to expand)
/nix/store/63qdryfhbm0aa93xbxdz8vj05qvfp9bw-inetutils-1.9.4

Success on x86_64-linux (full log)
Attempted: inetutils
Partial log (click to expand)
/nix/store/8ar7rjhirsclyf10qx3syzw6yfk6vp57-inetutils-1.9.4

Failure on x86_64-darwin (full log)
Attempted: inetutils
Partial log (click to expand)
void    logwtmp(const char *, const char *, const char *) __OSX_AVAILABLE_BUT_DEPRECATED(__MAC_10_0,__MAC_10_5,__IPHONE_2_0,__IPHONE_2_0);
        ^
3 warnings and 9 errors generated.
make[2]: *** [Makefile:1695: rlogind.o] Error 1
make[2]: Leaving directory '/private/tmp/nix-build-inetutils-1.9.4.drv-0/inetutils-1.9.4/src'
make[1]: *** [Makefile:1491: all-recursive] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-inetutils-1.9.4.drv-0/inetutils-1.9.4'
make: *** [Makefile:1428: all] Error 2
builder for '/nix/store/d344gr9kiwnajv99x79wwna01qsim315-inetutils-1.9.4.drv' failed with exit code 2
error: build of '/nix/store/d344gr9kiwnajv99x79wwna01qsim315-inetutils-1.9.4.drv' failed

Err, @matthewbauer -- thoughts?

Closing in favor of #39790.


:bug: fix elseif syntax in recipes

Minor fix needed to make the package work correctly.
Adding the package works as expected with:
] add https://github.com/EcoJulia/SimpleSDMLayers.jl#master

However, it fails to load correctly and returns:
julia> using SimpleSDMLayers
[ Info: Recompiling stale cache file /home/gdansereau/.julia/compiled/v1.1/SimpleSDMLayers/DPfL7.ji for SimpleSDMLayers [2c645270-77db-11e9-22c3-0f302a89c64c]
ERROR: LoadError: LoadError: syntax: use "elseif" instead of "else if"
Stacktrace:
 [1] include at ./boot.jl:326 [inlined]
 [2] include_relative(::Module, ::String) at ./loading.jl:1038
 [3] include at ./sysimg.jl:29 [inlined]
 [4] include(::String) at /home/gdansereau/.julia/packages/SimpleSDMLayers/JJhvi/src/SimpleSDMLayers.jl:1
 [5] top-level scope at none:0
 [6] include at ./boot.jl:326 [inlined]
 [7] include_relative(::Module, ::String) at ./loading.jl:1038
 [8] include(::Module, ::String) at ./sysimg.jl:29
 [9] top-level scope at none:2
 [10] eval at ./boot.jl:328 [inlined]
 [11] eval(::Expr) at ./client.jl:404
 [12] top-level scope at ./none:3
in expression starting at /home/gdansereau/.julia/packages/SimpleSDMLayers/JJhvi/src/recipes/recipes.jl:8
in expression starting at /home/gdansereau/.julia/packages/SimpleSDMLayers/JJhvi/src/SimpleSDMLayers.jl:27
ERROR: Failed to precompile SimpleSDMLayers [2c645270-77db-11e9-22c3-0f302a89c64c] to /home/gdansereau/.julia/compiled/v1.1/SimpleSDMLayers/DPfL7.ji.
Stacktrace:
 [1] compilecache(::Base.PkgId, ::String) at ./loading.jl:1197
 [2] _require(::Base.PkgId) at ./loading.jl:960
 [3] require(::Base.PkgId) at ./loading.jl:858
 [4] require(::Module, ::Symbol) at ./loading.jl:853

Fixing the elseif in src/recipes/recipes.jl fixed the problem for me. I've tested it using
] add https://github.com/EcoJulia/SimpleSDMLayers.jl#fix-elseif

@mkborregaard Travis activated!


WAL Atomiticy

As pointed out by someone in Discord, we do not guarantee atomicity for WAL, in the case of txn commit.

Very worth looking forward to


Mitigate the long provisioning latency for Azure multicloud connections

This is because Azure VPN gateway provisioning can take ~20 minutes. @divega is in communication with the team that runs this service about plans to fix this.

Following up on this.

Hi team !
As ex MS FTE, interested to look into this project ;)
Is it expected in the example (https://paragliderproject.io/examples/multicloud.html) that "glide rule add gcp vm-c --ping default.azure.vm-a" would automatically trigger VPN GW creation on both Azure and GCP ?
In my dev container, it is not triggering any Azure - GCP connectivity even after 20 minutes.
Thanks !

Just rebuilt my dev container, deleted all resources and now, adding the rule seems to be working fine to create connectivity between GCP and Azure.
Anyway, will continue to follow this project! seems very interesting and if any help is needed, reach out to me !

@alexandreweiss glad that it worked.

Triage: We need to keep following up on this, not necessarily something that is going to get resolved soon though.

Sure, happy to help anytime. More networking specialist than coder ;) The provisionning time, at least in Azure, as always been around ... the only improvement i saw in the last year is the linux VMs spinning that is like 30 sec. But for Gateways like ER, VPN, vWan : there is always lot of stuff made inside the OS so takes quite longer time


JDK 21 compatibility, version bumps and cleanup

analog update to https://github.com/apache/netbeans-mavenutils-archetype-netbeans-platform-app-archetype/pull/13

LGTM


Npm run format

Updating everything with npm run format. This will give us some better consistency with line spacing and styling

Nice fix!


Use separate RG for K8S persistent volumes

Commit 2541caf013b50ba1b2ac7f740b9efbedf13686d3:

Creates separate resource group for storage needs.
Creates separate tfstate file for the resource group.
Switches 'azure-disk-retain' -storage class to use the above resource group
Creates an Azure rolebinding so that our cluster can access the resource group.

By this commit, persistent volumes created to the separate resource group are not destroyed even if terraform destroy is performed in the root module. However, in the current script the "abandoned" volumes are not reused, so if one wants to collect the information in them, it has to be done manually.
Closes #66

With commit fa1b6d7 using the separate resource group is opt-in.  This can be enabled via a variable use_separate_storage_rg set as true.


Support script migration

Codecov Report

Merging #8 into master will increase coverage by 4.08%.
The diff coverage is 82.97%.

@@             Coverage Diff              @@
##             master       #8      +/-   ##
============================================
+ Coverage     67.61%   71.69%   +4.08%
- Complexity      128      172      +44
============================================
  Files            26       33       +7
  Lines           457      583     +126
  Branches         33       37       +4
============================================
+ Hits            309      418     +109
- Misses          138      154      +16
- Partials         10       11       +1

Impacted Files
Coverage Δ
Complexity Δ

...com/monjam/core/resolve/JavaMigrationResolver.java
92% <ø> (ø)
5 <0> (ø)
:arrow_down:

...c/main/java/com/monjam/gradle/MonjamExtension.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../main/java/com/monjam/core/command/DbRollback.java
100% <100%> (+7.4%)
10 <6> (+1)
:arrow_up:

...in/java/com/monjam/core/resolve/MigrationInfo.java
100% <100%> (ø)
4 <2> (+1)
:arrow_up:

...om/monjam/core/executor/NoopMigrationExecutor.java
100% <100%> (ø)
3 <3> (?)

...main/java/com/monjam/core/database/DbTemplate.java
100% <100%> (ø)
12 <1> (+1)
:arrow_up:

...c/main/java/com/monjam/core/command/DbMigrate.java
100% <100%> (ø)
10 <7> (ø)
:arrow_down:

...a/com/monjam/core/resolve/MigrationInfoHelper.java
83.33% <100%> (+1.51%)
5 <0> (+1)
:arrow_up:

...com/monjam/core/resolve/NoopResolvedMigration.java
100% <100%> (ø)
4 <4> (?)

...onjam/core/resolve/CompositeMigrationResolver.java
100% <100%> (ø)
7 <7> (?)

... and 18 more

Continue to review full report at Codecov.

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


Comments

Is it possible to get comments for a video?

youtube_explode_dart has such a feature, so I think it's possible.

I am still working on a solution, but I have a start. You can make a request like this to get the comments:
POST /youtubei/v1/next?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8 HTTP/1.1
Host: www.youtube.com

{
  "context": {
    "client": {"clientName": "WEB","clientVersion": "2.20210820.01.00"}
  },
  "continuation": "Eg0SC3E1VW5UNElrNktVGAYyDyINIgtxNVVuVDRJazZLVQ=="
}

and you can get continuation like this:
package main

import (
   "encoding/base64"
   "fmt"
   p "google.golang.org/protobuf/testing/protopack"
)

func main() {
   m := p.Message{
      p.Tag{2, p.BytesType}, p.LengthPrefix{
         p.Tag{2, p.BytesType}, p.String("q5UnT4Ik6KU"),
      },
      p.Tag{3, p.VarintType}, p.Varint(6),
      p.Tag{6, p.BytesType}, p.LengthPrefix{
         p.Tag{4, p.BytesType}, p.LengthPrefix{
            p.Tag{4, p.BytesType}, p.String("q5UnT4Ik6KU"),
         },
      },
   }
   s := base64.StdEncoding.EncodeToString(m.Marshal())
   fmt.Println(s)
}

alternatively, before the above request, you can make another request like this:

POST /youtubei/v1/next?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8 HTTP/1.1
Host: www.youtube.com

{
  "context": {
    "client": {"clientName": "WEB","clientVersion": "2.20210820.01.00"}
  },
  "videoID": "q5UnT4Ik6KU"
}

and the continuation value will be in the response.

Getting the key from the video ID looks like magic. I'm sure you're not here for my praise, but..  this is really impressive. I just tried it on a random video and it works.

Thanks. To be fair, a couple of people did it already in Python [1] and Crystal [2], so I just translated the code to Go. However doing so was quite difficult, as I only found one implementation for Protobuf Wire in the standard library [3], and the functions arent exported, so I would have had to vendor them. After much looking, I found the Protopack package [4], which does exactly what is needed here. I overlooked it at first, because the Protobuf module is huge, and since it was under the testing folder, I didnt think it was anything.
I am still working on the code, as I think you can improve it by defining a Protobuf struct instead, with field tags instead [5]:
// A struct corresponding to a TimeStamp protocol buffer.
// The tag strings define the protocol buffer field numbers;
// they follow the convention outlined by the reflect package.
struct {
	microsec  uint64 `protobuf:"1"`
	serverIP6 uint64 `protobuf:"2"`
}

I just havent figured out how to do that yet.

https://github.com/user234683/youtube-local/blob/master/youtube/comments.py
https://github.com/iv-org/invidious/blob/master/src/invidious/comments.cr
https://github.com/golang/go/blob/master/src/runtime/pprof/protobuf.go
https://pkg.go.dev/google.golang.org/protobuf/testing/protopack
https://golang.org/ref/spec#Struct_types

Since no one currently knows what the field names are anyway, I think I will just stick with the current implementation. I did wrap it up in a function though:
package proto

import (
   "encoding/base64"
   p "google.golang.org/protobuf/testing/protopack"
)

func continuation(videoID string) string {
   m := p.Message{
      p.Tag{2, p.BytesType}, p.LengthPrefix{
         p.Tag{2, p.BytesType}, p.String(videoID),
      },
      p.Tag{3, p.VarintType}, p.Varint(6),
      p.Tag{6, p.BytesType}, p.LengthPrefix{
         p.Tag{4, p.BytesType}, p.LengthPrefix{
            p.Tag{4, p.BytesType}, p.String(videoID),
         },
      },
   }
   b := m.Marshal()
   return base64.StdEncoding.EncodeToString(b)
}

I found a better package for encoding:
package proto

import (
   "encoding/base64"
   "github.com/philpearl/plenc"
)

type continuation struct {
   A struct {
      VideoID string `plenc:"2"`
   } `plenc:"2"`
   B uint32 `plenc:"3"`
   C struct {
      D struct {
         VideoID string `plenc:"4"`
      } `plenc:"4"`
   } `plenc:"6"`
}

func newContinuation(videoID string) continuation {
   var con continuation
   con.A.VideoID = videoID
   con.B = 6
   con.C.D.VideoID = videoID
   return con
}

func (c continuation) encode() (string, error) {
   b, err := plenc.Marshal(nil, c)
   if err != nil {
      return "", err
   }
   return base64.StdEncoding.EncodeToString(b), nil
}

https://github.com/pytube/pytube/issues/910


Implement native Yarn Modern support

This is a feature request for github-action.
What would you like
github-action should provide full native support for Yarn Modern (version 2 and later) usage.
Why is this needed
Yarn Classic (version 1) entered maintenance mode in January 2022, so github-action should provide full support for the follow-on version Yarn Modern (aka Yarn Berry - current version is 3.x 4.x).
Due to the fact that Yarn Classic is still widely used, Yarn Classic and Yarn Modern both need to be supported. Yarn Classic support cannot yet be dropped.
Yarn Modern is currently dealt with through the use of github-action options. These are workarounds because the action does not recognize Yarn Modern and therefore does not change the commands it calls internally. For workaround usage see:

README > Yarn Modern
README > Yarn Modern - Plug'n'Play

Missing features and possible solutions
Module API call for Yarn Plug'n'Play (pnp)
The call to the Cypress Module API to invoke cypress run fails in a Yarn Plug'n'Play (pnp) environment. It does not find cypress.
For comparison: at the CLI level, for Yarn Classic and Yarn Modern, yarn node script.js works with all variations. In contrast node script.js works with only with Yarn Classic, Yarn Modern node-modules and Yarn Modern pnpm. It does not work with Yarn Modern pnp.
npx replacement by yarn
Internally  github-action uses npx to execute cypress commands such as cypress cache list and cypress verify.
This does not work correctly with the Yarn Plug'n'Play default mode of Yarn Modern because there is no node_modules directory available in this configuration. npx will then separately download the arbitrary latest version of Cypress to work with, producing results which are not tied to the yarn.lock file.
With Yarn Modern configured for pnpm any npx commands fail completely. Since npx is currently hard-wired into github-action it is incompatible with this mode.
The Yarn Modern CLI run command offers the option --binaries-only so npx can be replaced by yarn run --binaries-only or yarn run -B in Yarn Modern environments. An equivalent option is not available for Yarn Classic, so npx should continue to be used in this case to avoid issues with Yarn Classic environments where cypress has been used as the name of a script in package.json. See issue https://github.com/cypress-io/github-action/issues/941 where this conflict became apparent.
yarn install command
Yarn Classic dependencies are correctly installed by github-action using yarn --frozen-lockfile, however the option --frozen-lockfile is deprecated in the Yarn Modern CLI install. For correct usage with Yarn Modern, the option --frozen-lockfile should be removed. (See also the detailed discussion in https://github.com/cypress-io/github-action/pull/611). This issue is currently worked around by using the custom install-command github-action option for Yarn Modern configurations.
Suggestion summary

Yarn Version / Mode
Installation
npx
Module API

Yarn Classic
no change
no change
no change

Yarn Modern node-modules
yarn (drop --frozen-lockfile)
yarn run -B
yarn node

Yarn Modern pnp
ditto
ditto
ditto

Yarn Modern pnpm
ditto
ditto
ditto

This means that the action needs to differentiate between Yarn Classic (version 1) and Yarn Modern (version 2 and later) and needs to change the logic correspondingly. Since the three nodeLinker variants of Yarn Modern (node-modules, pnp and pnpm) can be handled the same, there is no need to differentiate between them.
Currently the action checks for the presence of yarn.lock to recognize Yarn projects. yarn.lock is used by both Yarn Classic and Yarn Modern.

There are multiple issues with Cypress compatibility with Yarn Plug'n'Play, especially for component testing - see https://github.com/cypress-io/cypress-documentation/issues/5394


How are android apps like Whatslog able to get online status?

On Android there are apps like Whatslog that will monitor a whatsapp contact online status. They don't need any permission except storage permission.
https://play.google.com/store/apps/details?id=com.whatslog.log&hl=en
How can they do that without having to scan a QR code from whatsapp web?

After checking the api with mitmproxy, I think they do it server-side.


Keyboard layout changes it self.

Windows Terminal version
1.13.11432.0
Windows build number
10.0.22000.0 Microsoft Windows NT 10.0.22000.0
Other Software
No response
Steps to reproduce
launching a python script
Expected Behavior
When i try to luch a python application inside the CLI
it add me a United States English Qwerty to the windows keyboard layouts.
Currently i have  2 layouts
English United States French
German German

Actual Behavior
add a english layout

What shell are you launching your python script from/?
Does this happen for all python scripts?
Does this happen when you launch other child processes from that shell? (e.g. running pwsh from cmd or something)

What shell are you launching your python script from/?
Does this happen for all python scripts?
Does this happen when you launch other child processes from that shell? (e.g. running pwsh from cmd or something)

Windows Powershell
Just tested, yes
No

ps: forget to say. The new English US Qwerty is hidden in the windows Language and region, i must manually add it and delete again .

Does this happen for all python scripts

Just tested, no, only my script, so i need to dig inside and its nothing related to terminal

Yea, I'd reckon that's the root cause here. Either something you're doing, or something one of your dependencies is doing. Not sure there's anything more I know to try and help debug. Sorry about that!


Ideas for improving Stable Cascade's fine details.

I wish you lots of success with this fantastic new release! It's an incredible achievement for prompt coherence and complex hands and feet! I am stunned to see overlapping hands holding a flower, and seeing all the correct fingers. This new technology is amazing and you should be very proud. Amazingly good job by everyone involved!
Since this is a research project, I am curious. The model is very good already. But humans tend to look a bit like plastic due to the super smooth skin. Do you think that the "soft, smooth-skinned, airbrushed" look of skin will be curable via further finetuning? Or is that some kind of limitation of the small, internal latent space? Or maybe even the training data or dimensions?
I would guess that it is fixable via further refinement of the stages that add the final details (Stage B seems to be the fine details stage?).
Alternatively, users can of course add a typical "detailer" stage after the final image stage, to get crisp details. But I guess that such a tweak wouldn't be needed if Stable Cascade can be slightly revised to become better at details.

they are currently working on a DiT model that has a lot more effort being put into it. This is a research artifact. The new transformer model has thousands of nodes.
This model (Cascade) is bottlenecked by the VQGAN, and its reconstructive stage that reduces the latents to 4 channels. The base model (stage C) has 16 channels, that's a fair amount of information reduction.

they are currently working on a DiT model that has a lot more effort being put into it. This is a research artifact. The new transformer model has thousands of nodes.

For anyone else wondering:
https://huggingface.co/docs/transformers/en/model_doc/dit
Sounds good that they're making a new DiT with thousands of nodes, if I understood you correctly. Sounds like that would be great for details.
But what do you mean that Stable Cascade is "a research artifact"? The team worked with the Würstchen developers to evolve that architecture and seemed very proud on Twitter about this new network. They have also confirmed that Stable Cascade will become a commercial product when this development is done.

This model (Cascade) is bottlenecked by the VQGAN, and its reconstructive stage that reduces the latents to 4 channels. The base model (stage C) has 16 channels, that's a fair amount of information reduction.

Hmm. Yeah, the Stage C has 16 (I remember reading 13 but I guess that was wrong) channels in a 24x24 grid. That's required to compress all of the prompt information into such a small grid.
It then gets enlarged (decompressed) by Stage B. But even though that enlargement reduces the channels from 16 to 4, it's still a much larger latent image after decompression/enlargement0, so it makes sense to reduce the information density (channels).
What do you mean that it's bottlenecked by the adversarial network btw? Do you mean that the adversarial network wasn't good enough at determining which images were detailed vs blurry?
I could believe that. Because the results, while the composition is good, are all pretty blurry. Sort of like "sharp edges, blurry textures". It definitely needs some work.
I'd guess Stage B (the enlargement) is the biggest culprit for this blurred effect.
Do you know if Stage A (the VAE decoder) is responsible for fine details/further enlargement too?

Following up on this - as usual, fine tuning the B-stages (much like madebyollin's work on Stage-A) (even the lite variant) produces noticeably finer detail than the released variants. I am somewhat actively perplexed as to why but it seems that the B-stage maybe could've used re-training without the CLIP/Tenc needs as well as its effectively not using them and a waste of VRAM.
A simple 1k steps of UHD images using a modified version of the train_b.py script, batch size of 1, AdamW (on 4090). I'd be curious to see if anyone else can confirm similar findings.

i think it's because text-conditional guidance improves FID and CLIP scores a bit during the initial toy model experimentation stages just after they validate architectures using ImageNet or CIFAR etc
you see this in the DeepFloyd architecture. the stage II model is needlessly text-conditioned and uses the T5 embeds.
the SDXL refiner makes use of the single OpenCLIP-G model, and only trained on the final 200 steps of the schedule! when this kind of guidance isn't even used by the model.. though it does have substantial impact with the aesthetic scores holding back floodgates of watermarks and other poor quality results. it's just that the prompt itself doesn't.
again the Cascade arch passes the text guidance needlessly into the stage B. but also, Wurstschen v2 didn't do that. it used two separate conditionings for stage C and B! with OpenCLIP-H for stage C and OpenCLIP-G for stage B. @pcuencas do you have insight for us as to why this choice maybe made?


Can't build images

Output of docker version:
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:38:55 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:38:55 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 3
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 22
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.2.0-36-generic
Operating System: Ubuntu 15.10
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 9.645 GiB
Name: cassandra
ID: 6G7E:OCPA:S4R4:OXSE:JPDL:6JGP:7O63:Z66Q:O37J:Z2LL:EFQD:L5U3
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:

Create Dockerbuild file according to the whalesay tutorial
Run docker build -t docker-whale .

Describe the results you received:
Step 1 : FROM docker/whalesay:latest
---> 6b362a9f73eb
Step 2 : RUN apt-get -y update && apt-get install -y fortunes
invalid id:
Describe the results you expected:
I would expect the image to build
Additional information you deem important (e.g. issue happens only occasionally):
running as /usr/bin/docker daemon -H fd:// --iptables=False --bridge=none
Output of docker network ls:
NETWORK ID          NAME                DRIVER
6ead2e77435f        VPN                 bridge
bfbc07928f6e        VPN_THROTTLED       bridge
84227598b5bb        host                host
6b0c79764525        none                null

(note there is not a network called bridge, perhaps because  I never ran docker without --bridge=none)

can you show the Dockerfile

@jkirkby91 I don't think the docker file is related in this case (you can see the steps it's running), possibly the --bridge=none in this case, but I haven't tried to reproduce yet.

Ok, confirmed; if the daemon has never been started before, and it's started with --bridge=none, then the default bridge network is not created.
To reproduce;
start a fresh machine (I used ubuntu 15.10 as the original report), and install the static binaries;
curl https://get.docker.com/builds/Linux/x86_64/docker-1.11.1.tgz > docker.tgz
tar -xvf docker.tgz
mv docker/* /usr/bin/

start daemon with --bridge=none
/usr/bin/docker daemon --debug --iptables=False --bridge=none &

notice that there's no "bridge" network
docker network ls
NETWORK ID          NAME                DRIVER
0486f8db5140        host                host
06c99cbfbafc        none                null

Do a build (using the "whales" image, but shouldn't matter what;
FROM docker/whalesay:latest
RUN apt-get -y update && apt-get install -y fortunes
CMD /usr/games/fortune -a | cowsay

Watch the build failing:
docker build -t docker-whale .
Sending build context to Docker daemon 2.048 kB
Step 1 : FROM docker/whalesay:latest
 ---> 6b362a9f73eb
Step 2 : RUN apt-get -y update && apt-get install -y fortunes
invalid id:

logs
DEBU[0007] Calling POST /v1.23/build?buildargs=%7B%7D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&rm=1&shmsize=0&t=docker-whale&ulimits=null
DEBU[0007] [BUILDER] Cache miss: [/bin/sh -c apt-get -y update && apt-get install -y fortunes]
DEBU[0007] [BUILDER] Command to be executed: [/bin/sh -c apt-get -y update && apt-get install -y fortunes]
ERRO[0007] Couldn't run auplink before unmount /var/lib/docker/tmp/docker-aufs-union442469909: exec: "auplink": executable file not found in $PATH
ERRO[0007] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/a52bbe882845fa702ae53675e13f66268fd293484864cc2c5fe14b7e82c4141a-init: exec: "auplink": executable file not found in $PATH
DEBU[0007] container mounted via layerStore: /var/lib/docker/aufs/mnt/a52bbe882845fa702ae53675e13f66268fd293484864cc2c5fe14b7e82c4141a
ERRO[0007] Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/a52bbe882845fa702ae53675e13f66268fd293484864cc2c5fe14b7e82c4141a: exec: "auplink": executable file not found in $PATH

Note that starting the daemon without --bridge=none creates the bridge network, but build is still failing, due to --iptables=false (and no iptables rules being present); this should not be a problem if you manually created those rules.

Marking this as bug, although I'm not sure what the expected outcome should be with --bridge=none, as this would tell docker to not create a bridge, thus  telling it to not create a bridge network
ping @mavenugo

I don't see any problem with not having a default network. Some users, as me, don't want a bridge created nor a default network. Currently I am forced to have a docker specific bridge, so I can have a docker specific bridge network so I can build images. I will never launch a container inside that network, so this really only needlessly occupies a subnet that is never used, other than building images.
Ideally, one would be able to build an image using the host's network. Is there any reason for this not to be possible ?

Ideally, one would be able to build an image using the host's network

see the discussion on https://github.com/docker/docker/issues/10324 and https://github.com/docker/docker/pull/20987

@thaJeztah ok, I +1'd there.
However, I'm worrying that the "fix" for this specific bug is to always create a default network. In my opinion this should not be the case. Instead:

--bridge=none specified -> no bridge, no default bridge network (sounds obvious)
no --bridge specified -> docker0 bridge, educated random subnet, default bridge network on this subnet
--bridge=existing_bridge -> default bridge network on existing bridge's subnet

For the first case, if a bridge existed in the past but this current run of the daemon is with --bridge=none, then don't create the bridge pre-defined network (it won't work anyway, as there is no bridge. If users  create a bridge for docker to use afterwards, then they must create a bridge network as well if they wish to use it).

Is this still an issue?

Let me close this ticket for now, as it looks like it went stale.


VP0 gacks under sieve pbft with non deterministic results returned

Description:  VP0 stopped logging, started dumping numbers out till it was ctrl-c'd
Steps to repro:

Setup a CA and set of 4 VPs using pbft sieve using privacy and security
Login your user
Do a secure deploy using a version of Chaincode_02 that injects non-deterministic values

Results:
vp0 crashes
Expected results:
vp0 should handle the error gracefully
non-deterministic-values given to sieve 4 of 4.txt
non-deterministic-values given to sieve 3 of 4.txt
non-deterministic-values given to sieve 2 of 4.txt
non-deterministic-values given to sieve 1 of 4.txt
chaincode_nondeter_example02.zip
Cool, relevant movie quote:

11:15 Restate my assumptions:

Mathematics is the language of nature.
Everything around us can be represented and understood through numbers.
If you graph the numbers of any system, patterns emerge. Therefore, there are patterns everywhere in nature.

Evidence: The cycling of disease epidemics;the wax and wane of caribou populations; sun spot cycles; the rise and fall of the Nile. So, what about the stock market? The universe of numbers that represents the global economy. Millions of hands at work, billions of minds. A vast network, screaming with life. An organism. A natural organism. My hypothesis: Within the stock market, there is a pattern as well... Right in front of me... hiding behind the numbers. Always has been.

Can you please provide a full log, or at least the log section before that large array of numbers?

Sorry guys, spent the day running into bugs, will have to look at this tomorrow.

How does the attached chaincode inject nondeterministic values?

It's got some errors, I can't repro the issue on current code...  closing as no repro

Wait!  Murali helped me, who knew there is an int63?  Or is that another name for a signed int64?
In any case, I was able to capture the logs using redirect and append at the end of the commandline, and I've got a solid repro, works every time.  I'm adding the logs and the ndt (in honor of Neil deGrasse Tyson) code that causes it, and the deploy, just for kicks!
Logs:
Poop.  The files are 70 meg each, github allows only 10 meg files, lets see how much compression we get with winzip.  26.4MB, still too big, lets see if winrar does any better...

Great, github won't take .rar files.
And it won't take multi-file zips... ok, here goes rar files inside zip files.
vp0.part1.zip
vp0.part2.zip
vp0.part3.zip
vp1.part1.zip
vp1.part2.zip
vp1.part3.zip
vp2.part1.zip
vp2.part2.zip
vp2.part3.zip
Non-deterministic chaincode example02:
nond2.zip
Deploy payload that causes crash (Always repros):
{
  "jsonrpc": "2.0",
  "method": "deploy",
  "params": {
    "type": 1,
    "chaincodeID":{
        "path":"github.com/hyperledger/fabric/examples/chaincode/go/ndt"
    },
    "ctorMsg": {
        "function":"init",
        "args":["a", "1000", "b", "2000"]
    },
    "secureContext": "lukas"
  },
  "id": 1
}

I opened only vp0 but it looks like part1/2/3 all contain the same log ???  timestamp of first line is 19:59:49.708 for all 3.
In any case, the problem is an errant logger.Debug call  at https://github.com/hyperledger/fabric/blob/master/core/ledger/ledger.go#L157 which prints out the whole transaction.
after that logger.Debug call finishes, I see that the peer is still up.
So, no crash and the sieve check for non-determinism happens at line 835 in the log.
Let's try to re-run with a lesser core_logging_level ?

Hmmm, no, they're segmented by winrar and the filenames are automatically named after the original files by winzip.  Possibly if you unzipped them all in the same directory, whatever unrar program is smart enough to recognize the pieces are related and gives you the complete file as it unrars all the parts and stitches them together?
Will rerun with lesser logging level on Mon, or sooner if I can manage to come in this weekend.

Here goes with warning level logging and today's code:
Lots of "This indicates a bug" in the logs
vp0log.txt
vp1log.txt
vp2log.txt
vp3log.txt

Spent some time with @RicHernandez2 to re-configure his network and re-run his scenario.
I don't see the "indicates a bug" messages anymore and the system stays up after the deploy/invoke of the test chaincode.
I do see an error message on the query but this looks like some coding issue in the chaincode itself.
In any case, I've asked Ric to re-run with a commit containing PR #1325

folks, what's the status on this one? can it be closed?

@corecode @vukolic i'm closing this as it is stale and the last comment from @tuand27613 suggested it is no longer an issue.


Guanyu/dockerfiles

Created 2 bash scripts for starting and setting up 3 nodes with docker containers
Created 2 bash scripts for starting and setting up multiple nodes with docker containers
Support testing on local machine

run the following cmd to start 4 nodes in containers
docker build -t node . ./launch_containers.sh 4      ./setup_containers.sh 4

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.132%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3079

Relevant Lines:
4801

💛  - Coveralls


fix narrowing warnings

Signed-off-by: Daniela Engert<EMAIL_ADDRESS>

@cstratopoulos Yes, I think that is a good idea

Merged in 163, thank you!

Thanks, Vinnie - the narrowing warning is gone now 😄


migrate to python 3.8

currently this library depends on 2.7. There will be a couple of changes needed to the existing code, I'll describe them specifically here if needed when I dig into it

okay so turns out the reason why this is written the way that it is, is because this is a jython library not a python library. Jython is Python 2.7, not 3. This also explains why the library uses setuptools etc and not poetry.
I'm not totally sure what the options are here. Python checks currently running in metadig-engine use a couple functions from this library, so jettisoning jython all together would be a big refactor for many checks. However, down the road, depending on jython could cause us problems since it won't allow us to do a whole lot of python analysis-type things (numpy is not available for jython, for example).
Thoughts @mbjones?

I agree with your assessment of the relative difficulty. Getting rid of Jython is a good long-term goal. But there are also complications of trying to pass data through less reliable mechanisms -- the approach we are using in Java to R is also pretty convoluted. Let's discuss alternatives on our next design call.


feat: add dynamic fields methods support

Fixes #117

Please @ragingdave, can you merge this PR?

After some thought, as this package is not locked on any version of Nova, the implementation in #124 is safer.

I would have to agree that 124 appears safer as well. Closing this, and will have a look at 124 some time later today


dependency vulnerability within superagent 3.8.3

could you please update the dependencies of superagent 3.8.3
Prototype Pollution
Vulnerable module: extend
Introduced through<EMAIL_ADDRESS>Detailed paths
Vulnerable module: extend
Introduced through<EMAIL_ADDRESS>Detailed paths
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Remediation: Your dependencies are out of date, otherwise you would be using a newer extend than<EMAIL_ADDRESS>Try reinstalling your dependencies. If the problem persists, one of your dependencies may be bundling outdated modules.
Overview
extend is a port of the classic extend() method from jQuery.
Affected versions of this package are vulnerable to Prototype Pollution. Utilities function can be tricked into modifying the prototype of "Object" when the attacker control part of the structure passed to these function. This can let an attacker add or modify existing property that will exist on all object.
Remediation
Upgrade extend to versions 2.0.2, 3.0.2 or higher.
https://snyk.io/vuln/npm:extend:20180424

Superagent uses ^3.0.0 so it picks up the fixed version of extend whenever available. If you run npm update you'll get the fixed version.

It is very unlikely to be a problem, because extend is only used for merging of the query string, and we don't do anything interesting with query string's prototype.


update protocol to https for domains that support it

a few of the links listed in the README use http when the domains support https, so this PR updates those domains to use https.

Thank you very much for raising the PR


feat(image): Using a common image for stress-ng commands

Signed-off-by: Udit Gaurav<EMAIL_ADDRESS>

What this PR does / why we need it:

This is for using a uniform image for stress-ng commands

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes # https://github.com/litmuschaos/litmus/issues/1459
Checklist

[x] Does this PR have a corresponding GitHub issue?
[x] Have you included relevant README for the chaoslib/experiment with details?
[x] Have you added debug messages where necessary?
[x] Have you added task comments where necessary?
[x] Have you tested the changes for possible failure conditions?
[x] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[x] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[x] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[x] Can you suggest the minimal resource requirements for the litmusbook execution?
[x] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[x] Has the litmusbooks been linted?

Special notes for your reviewer:

@uditgaurav Can you please attach the logs?


Ability to type in a formula in the Offer-X window

When offering gp in a trade, it would be useful to have the ability to type in a formula such as "85.2M * 8".

Duplicate of #9967


Update main to 3.30.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@gillins both 3.30 and 3.28 are facing the same issue. It seems pyqt5 could not be found. I tried to debug this yesterday in a VM machine but it was crashing (my vm is probably not good enough). Any ideas?

The only relevant change I saw was in windows virtual machine that is used. do you think we need to rerender pyqt?
Didn't saw any relevant changes upstream either.

I saw the same issue with that PPC PR, but didn't investigate. Something must have changed recently. I'll do a bit of digging when I get a moment.

Maybe pyqt needs to be rerendered?

No idea. I'll try and add some messages to the output to see what is going wrong first.

This is my bad because there are 2 copies of PyQt5-5.15.*.dist-info/METADATA. One for 5.15.9 from pyqtwebkit (I had to merge this later version to fix OSX arm64) and one for 5.15.7 from pyqt (migration to 5.15.9 is stalled here: https://github.com/conda-forge/pyqt-feedstock/pull/129).
I'll see if I can do a workaround.


Pearson correlation pixel by pixel correlation

It should be possible to calculate Pearson correlation on pixel by pixel basis on time/lat/lon datasets

Done.

You might be interested in an recursive implementation of the pearson correlation coefficient. E.g. https://github.com/TUW-GEO/pytesmo/blob/master/pytesmo/metrics.py#L410 to speed things up. You could do it time slice by time slice instead of reading each timeseries using isel


Updated to service fabric 3.3.664 and added implementation of CreateNonIServiceProxy

The changes to the interface on pull request https://github.com/microsoft/service-fabric-services-and-actors-dotnet/pull/131/ is not compatible. Updated nuget packages and implemented interface with a NotSupportedException.

 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.:x: PixelByProxy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

LGTM, please sign the agreement so we can take the PR and release a new version.

Thanks , we need this too  👍

Working on getting company approval for CLA.

All set. Thanks!


refactored DispatchQueue extensions

There's no functionality difference, the change is cosmetic.

Thanks for the PR! However, this is, in fact, functionally different, as it will return the same queue for each QoS level, not generate a new one like the original code. Since the intent here is to let the system manage what queues it gives us, this would fundamentally alter the behavior of this API. For that reason we won't be merging it. Cheers! :beers:


Installing after build fails with a permission error

Description
On Arch Linux building Atom from source with the --install flag fails with a permission error.
Steps to Reproduce

git clone git://github.com/atom/atom.git
cd atom
git checkout 1.19-releases
script/build --install

Expected behavior:
Build ends without errors and atom 1.19.0-beta1 is installed.
Actual behavior:
Build fails with:
Installing "atom-beta-1.19.0-beta1-amd64" at "/usr/local/share/atom-beta"
Error: EACCES: permission denied, unlink '/usr/local/share/atom-beta/LICENSE'
  at Error (native)
  at Object.fs.unlinkSync (fs.js:1103:18)
  at copyFileSync (/home/moritz/code/atom/atom/script/node_modules/fs-extra/lib/copy-sync/copy-file-sync.js:13:10)
  at copySync (/home/moritz/code/atom/atom/script/node_modules/fs-extra/lib/copy-sync/copy-sync.js:32:7)
  at /home/moritz/code/atom/atom/script/node_modules/fs-extra/lib/copy-sync/copy-sync.js:40:7
  at Array.forEach (native)
  at Object.copySync (/home/moritz/code/atom/atom/script/node_modules/fs-extra/lib/copy-sync/copy-sync.js:37:14)
  at module.exports (/home/moritz/code/atom/atom/script/lib/install-application.js:62:8)
  at dumpSymbols.then.then.then.then.packagedAppPath (/home/moritz/code/atom/atom/script/build:111:7)

Reproduces how often:
Always
Versions
Atom: 1.19.0-beta1
OS: Arch Linux
Additional Information
I tried running the build script as root with sudo script/build --install but then the build failed with an error similar to #7134.
Workaround::
Run script/build without the --install flag and then run:
packagedAppPath=$(echo ~/code/atom/atom/out/atom-*)
sudo node -e "require('./script/lib/install-application')('$packagedAppPath', '')"

Same issue on Manjaro 4.14 while building atom 1.26

Error: EACCES: permission denied, mkdir '/usr/local/share/applications'
at Object.fs.mkdirSync (fs.js:902:18)
at Object.mkdirsSync (/home/owen/github/atom/script/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:29:9)
at module.exports (/home/owen/github/atom/script/lib/install-application.js:76:8)
at binariesPromise.then.then.then.then.packagedAppPath (/home/owen/github/atom/script/build:132:7)
at :null:null
Is there a way to manually install? I don't feel running sudo build --install is the right thing to do.


add logscale support

Following the "logscale commit" on torch/gnuplot, here is the adaptation to use it with torch/optim (useful to display the loss)

Thanks Guilhem!


WIP - Refactor controller-manager to use native ctrl-runtime components

How to categorize this PR?

/area dev-productivity
/kind technical-debt
What this PR does / why we need it:
This PR refactors the entire gardener-controller-manager to use a single controller-runtime Manager and transforms all controllers to use controller-runtime's controllers and watches instead of using informers directly.
Which issue(s) this PR fixes:
Needs #4320 first, then works towards #4251
Special notes for your reviewer:

The distinction between "client" and "cached client" (i.e. the CachedRuntimeClients feature gate) is mostly gone. There is one place left where a comment indicated that no caching shall be used for a certain request, but other than that, it's all cached now.
The logging setup code is WIP, because #4320 already contains the new Zap-based logging code and I did not want to replicate it here. That's why for now the setup is just minimal. This must be changed before this can be merged, though.
To improve logging consistency, each reconciler uses the same logger as its controller. This is because controller-runtime does some nice naming stuff for the logs that I did not want to replicate in our codebase. The downside is that there is a reconciler.logger = c.GetLogger() line for each reconciler.
For approving CSRs, I did not find a way to achieve it with controller-runtime clients. That's why the controller-manager still constructs an oldschool Kubernetes client.
In general, a lot of logic in event handlers was bravely removed (i.e. checking whether generations have changed), assuming it's all performance optimizations that would not be required if the Reconcile() is fast enough. This made writing event handlers for the controller watches much easier. Functional predicates (like namespace restrictions) were kept of course.
In cases where a single controller in the old codebase had multiple queues, the code has been restructured to have 1 queue = 1 reconciler = 1 controller. For example the controller/seed/'s AddToManager() function adds 3 controllers. The file structure has not been changed though.

Release note:

Breaking: The configuration key `server` in the `GardenerControllerManagerConfiguration` has been split into `healthServer` and `metricsServer`. Note that both cannot be listening on the same port.
Breaking: The `CachedRuntimeClients` feature gate has been removed from the `GardenerControllerManagerConfiguration`, clients are now always cached.

Hey @timuthy, this is a follow up to the #4320 -- PTAL if and when you have time. Needs the other PR for its pkg/logger/ first though.

Converted back to draft until https://github.com/gardener/gardener/pull/4320 is merged and this PR is updated.

This PR will not be continued/merged as is. It will be reworked and reopened as a new PR, once someone has capacity to take over.
/close


MSI installer

Add an MSI installer that will unpack files in Program Files and create a task in the scheduler to autorun the web interface.
It is advisable to add an uninstaller.

Duplicate of #1


Unknown provider when using minified version

When I use the minified version I get a Unpr error. The run function is missing the "$rootScope" annotaion  in the dist files.

Hi,
It works fine form me. I have updated demo website with minified version..
Please download latest files and check.

Hi,
It seems that the problem comes from Bower, when I install the module with it the minified version doesn’t work and I get the previous error.
I don't have any idea how Bower works, you may want to check it because the dist files works perfectly when I clone it directly from Github.
thanks

Hi,
There was an issue with minified version of angular-falsh. I had fixed it but forgot to update bower and npm..
Thanks for pointing this out I have fixed this. Please check..

Hi,
It works perfectly now, good job.


adding Oracle to table

Adding Oracle to table

/lgtm

preview https://deploy-preview-3353--competent-brattain-de2d6d.netlify.app/docs/started/installing-kubeflow/

@zijianjoy @chensun special request - would one of you please approve this so that we don't have to cherry pick this for the kubeflow docs ?  thanks!

/lgtm
/approve
Thank you for the update!


Use and benchmark SnoopPrecompile.jl

Investigate the use of SnoopPrecompile.jl for the ODINN.jl package. So far I have already implemented it in the #invert branch, but I still haven't properly assessed if there is any benefit in terms of performance. I should also check more in detail how to correctly use, since it was just a quick test.

This package is now deprecated. To be migrated to PrecompileTools.jl: https://julialang.github.io/PrecompileTools.jl/stable/


feat: runtime validation with typia

This PR replaces zod for Schema validation in certain packages to use typia instead. Typia is faster and is AOT, which should yield better performance and interop with existing Typescript types.
The biggest difference is going to be running from compiled code instead from source. You will have to start npm run watch or npm run build in order to make sure all local packages are compiled. That, however, should help to make sure that whatever we test locally while developing, is what end users of the library are going to see.

Going to close due to https://twitter.com/grabbou/status/1781423500097401023


fix: start to delete flannel pods to workaround issue scenario

What this PR does / why we need it:
To workaround the issue scenario: https://github.com/flannel-io/flannel/issues/1721 where the pods will get stuck to create the containers. It is sorted out by re-creating the flannel pods.
Which issue(s) this PR fixes:
Fixes # [sc-68370]
Special notes for your reviewer:
Testgrid: https://testgrid.kurl.sh/run/flannel_k8s_upgrade_feb_8_workaround
Steps to reproduce
https://staging.kurl.sh/47129cf -> https://staging.kurl.sh/1a98e97
Does this PR introduce a user-facing change?
Fixes issue scenario faced where the containers are not created after k8s upgrades because flannel issues.

Does this PR require documentation?
NONE

It will be called each time the Kurl script is run. Not only when
kubernetes is being upgraded. Also please take into account multi node
clusters. We will have to restart flannel after it has been upgraded on all
nodes
Sent via Superhuman iOS @.***>
On Wed, Feb 8 2023 at 1:08 PM, Camila Macedo @.***>
wrote:

@.**** commented on this pull request.
In addons/flannel/template/base/install.sh
https://github.com/replicatedhq/kURL/pull/4057#discussion_r1100681020:

@@ -253,6 +253,13 @@ function flannel_kubeadm() {
}

function flannel_already_applied() {

We will remove the flannel pods to let it be re-created

in order to workaround the issue scenario described in

https://github.com/flannel-io/flannel/issues/1721

log "Deleting pods from kube-flannel namespace"
kubectl delete --all pods --namespace=kube-flannel

This code implementation will only be called when the package is installed
already.
So, should not it only be called in the upgrade?
—
Reply to this email directly, view it on GitHub
https://github.com/replicatedhq/kURL/pull/4057#discussion_r1100681020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC2U54B3P57YOEYP3XPQTDWWQDLFANCNFSM6AAAAAAUVVUHNU
.
You are receiving this because your review was requested.Message ID:
@.***>


Add contributor page (no view yet)

Issue
#78
Overview (Required)
Add remote/local logic to get contributors.
For displaying contributors, I will let @srym or others do it. (I will do it if no one does this)
https://github.com/DroidKaigi/conference-app-2017/compare/master...shiraji:78_add_contributor_page?expand=1#diff-4cbabe00489cf45da36d6482d4379adbR77
Links
N/A
Screenshot
N/A

@shiraji Commented. Thank you for contribution! Almost perfect!

Do you want me to rebase the commits? @konifar

LGTM! 💯

Thanks for tackling this task!


Add moose submodule to VTB

What is this for?

thermochimica for now.
it also makes sense for checking meshing scripts

Use the https remote. There's no need to use SSH

Job VTB Documentation on 08334fc wanted to post the following:
View the site here
This comment will be updated on new commits.


Virtual scroll alignment

The top scroll bar disappears behind the header.
Does not align at zero.
Bottom stops correctly at 499.

@peterennis  I'm unable to reproduce this. If you would, please reopen with steps to reproduce in the docs repo.


Error using chrome.storage.sync

I am using the following code :
chrome.storage.sync.get('Shops', function(retVal) {
 console.log(retVal);
});

But I get this error:
gopher://xxx/_generated_background_page.html
Rest of the app (which does not call chrome.storage.sync works perfectly fine). I am using AngularJS.

chrome.storage.sync doesn't work. chrome.storage.local should work, and for syncing with drive you should use drive's JS API directly.


[WIP] fix: Fixed errors getting during using wsgen after uploading zip or using endpoint

Checklist

[X] I have read the Contribution & Best practices Guide.
[X] My branch is up-to-date with the Upstream development branch.
[X] I have added necessary documentation (if appropriate)

Fixes #2143

Not needed


form.submit with validate array does not work

Laravel Precognition Plugin Version
0.3.1
Laravel Version
10.0
Plugin
Vue
Description
I would like to add which fields on the form should be validated on submit. I would expect that populating the optional validate property with an array of paths would do this.
e.g.
@change="form.validate('assets.0.address.zipcode' )"
works
but this doesn't:
const submit = () => {
    form.submit({
        validate: ['assets.0.address.zipcode', 'assets.0.address.number'],
    });
};

Steps To Reproduce
add the code as mentioned in the description to your form
change the name(s) in the array of thevalidate property
See that it validates the whole form, instead of just the given names ('assets.0.address.zipcode', 'assets.0.address.number')

@cliff-paqt it is not possible to do this as a "submit" request is not a precognition request.
You would need to handle this on the back end yourself.

@cliff-paqt have you found any solution?

We went with the proposed soltution from timacdonald, but we set an object on the headers, specifying which part it should validate.
 formConfig = {
            headers: { part: validationPart },
        };

where you can add formConfig als a parameter on form.submit
The backend then uses a custom shouldValidate function to check which part it should validate.

We went with the proposed soltution from timacdonald, but we set an object on the headers, specifying which part it should validate.
 formConfig = {
            headers: { part: validationPart },
        };

where you can add formConfig als a parameter on form.submit
The backend then uses a custom shouldValidate function to check which part it should validate.

Thank you, I almost undestand your solution. Could you kindly post a little example of validationPart and shouldValidate, please?

validationPart is just a string that is passed to the composable handling the eventual submit.
the shouldValidate on the backend should check if the headers exist for your error rule

Just a reminder that the framework does not do anything fancy with submissions, so there are security implications from limiting validation for plain submissions that are not handled and it is not recommended.
That being said, you are free to do whatever you need in your own applications 👍


pnpm interactivity bug

Heyo! 😊
I've came up with a weird bug that I'm not 100% sure how to fix. I've switched to pnpm in a solid-start small project I was starting and cape up to this.

Clicking on the button does nothing and I can find this in the console.

Steps to reproduce

Run npm create jd-app@latest (created with Tailwind and tRPC)
Create a Counter component, see it working fine
Switch to pnpm
Counter component no longer works

PS: Noticed that there are no issue templates, but that you do have them on https://github.com/solidjs/solid. I'm open to helping with these, just got a question, do you want to have these on all repos or just on some? Because if you want them to be on all repos, we could move the issue templates into https://github.com/solidjs/.github

Update your deps. Related issue.

Can confirm that it fixed it, thanks @AlexErrant!


How to get the callback when the video has been played?

How to get the callback when the video has been played?

Play complete

You can attach a listener to the VideoPlayerController, and check controller.value.isPlaying:
bool started = false;
controller.addListener((){
  final playing = controller.value.isPlaying;

  if(!started && playing){
    started = true;
    return;
  }

  if(started && !playing){
    print("stopped playing");
    return;
  }
});

@a250059653 you can detect video completion likes this
  @override
  void initState() {
    super.initState();
    _controller = VideoPlayerController.network('URL')
      ..initialize().then((_) {
        setState(() {});
        _controller.play();
        _controller.addListener(() {
          final isCompleted =
              _controller.value.position == _controller.value.duration;
          if (isCompleted) {
            print('video ended do something now');

          }
        });
      });
  }

In the future please try asking support questions on one of the forums at https://flutter.dev/community
Closing as this is neither a feature request nor a bug.


social media icons in about page

The icons are not identical in shape and size I would like to change it.

Hello, I would like to work on this issue.

hey, Please assign this issue to me.


Ensure computations don't crash the server

We've observed that the multishot computation crashes the server. Error message:
error: Server promise rejection { Error: demo2 reports undefined features, but demo1 reports 3 features.
    at opts.userResults.forEach (/coins/coinstac/packages/coinstac-common/node_modules/laplacian-noise-ridge-regression/src/remote.js:21:15)
    at Array.forEach (native)
    at Object.assertUserDatas (/coins/coinstac/packages/coinstac-common/node_modules/laplacian-noise-ridge-regression/src/remote.js:14:22)
    at Object.run (/coins/coinstac/packages/coinstac-common/node_modules/laplacian-noise-ridge-regression/src/remote.js:56:10)
    at JavascriptComputation.fn (/coins/coinstac/packages/coinstac-common/node_modules/laplacian-noise-ridge-regression/src/index.js:54:36)
    at JavascriptComputation.run (/coins/coinstac/packages/coinstac-common/src/models/computation/javascript-computation.js:20:33)
    at tryNext.then.then.then (/coins/coinstac/packages/coinstac-common/src/models/pipeline/pipeline.js:138:31)
From previous event:
    at runQueue.(anonymous function).runQueue.(anonymous function).then (/coins/coinstac/packages/coinstac-common/src/models/pipeline/runner/pool/pipeline-runner-pool.js:554:23)
    at tryOnImmediate (timers.js:543:15)
    at processImmediate [as _immediateCallback] (timers.js:523:5)
From previous event:
    at RemotePipelineRunnerPool.triggerRunner (/coins/coinstac/packages/coinstac-common/src/models/pipeline/runner/pool/pipeline-runner-pool.js:552:6)
    at RemotePipelineRunnerPool.handleResultChange (/coins/coinstac/packages/coinstac-common/src/models/pipeline/runner/pool/pipeline-runner-pool.js:304:10)
    at DBListener.listener.on (/coins/coinstac/packages/coinstac-common/src/models/pipeline/runner/pool/pipeline-runner-pool.js:407:24)
    at emitOne (events.js:96:13)
    at DBListener.emit (events.js:188:7)
    at Changes.DBListener.changes.pouchy.changes.on.info (/coins/coinstac/packages/coinstac-common/src/models/db-listener.js:30:14)
    at emitOne (events.js:96:13)
    at Changes.emit (events.js:188:7)
    at tryCatchInChangeListener (/coins/coinstac/packages/coinstac-common/node_modules/pouchdb-core/lib/index.js:41:10)
    at Object.Changes.opts.onChange (/coins/coinstac/packages/coinstac-common/node_modules/pouchdb-core/lib/index.js:79:5)
    at Changes.<anonymous> (/coins/coinstac/packages/coinstac-server-core/node_modules/pouchdb-utils/lib/index.js:409:14)
    at emitOne (events.js:96:13)
    at Changes.emit (events.js:188:7)
    at tryCatchInChangeListener (/coins/coinstac/packages/coinstac-common/node_modules/pouchdb-core/lib/index.js:41:10)
    at Object.Changes.opts.onChange (/coins/coinstac/packages/coinstac-common/node_modules/pouchdb-core/lib/index.js:79:5)
    at onGetWinningDoc (/coins/coinstac/packages/coinstac-server-core/node_modules/pouchdb-adapter-leveldb-core/lib/index.js:1319:20)
    at onGetMetadata (/coins/coinstac/packages/coinstac-server-core/node_modules/pouchdb-adapter-leveldb-core/lib/index.js:1337:18)
    at /coins/coinstac/packages/coinstac-server-core/node_modules/pouchdb-adapter-leveldb-core/lib/index.js:1361:9
    at /coins/coinstac/packages/coinstac-server-core/node_modules/sublevel-pouchdb/lib/shell.js:87:12
    at /coins/coinstac/packages/coinstac-server-core/node_modules/sublevel-pouchdb/lib/nut.js:103:19 isRunError: true } _bitField=18087936, isRunError=true, _rejectionHandler0=undefined, _promise0=undefined, _receiver0=undefined, _parent=undefined, _promisesCreated=0, _length=1
info: Shutting down server…

This appears to come for a branch in remote.js.

For debugging purposes, I’ll add the database state. We're running multishot ridge regression with two users, demo1 and demo2. It should go for 200 iterations, then stop.
demo1’s local result’s data:
{
   "biasedX": [
       [
           31,
           1,
           1
       ],
       [
           62,
           1,
           1
       ],
       [
           61,
           1,
           1
       ],
       [
           57,
           1,
           1
       ],
       [
           44,
           1,
           1
       ],
       [
           41,
           1,
           1
       ],
       [
           33,
           1,
           1
       ],
       [
           48,
           1,
           1
       ],
       [
           43,
           1,
           1
       ],
       [
           18,
           1,
           1
       ],
       [
           27,
           1,
           1
       ],
       [
           45,
           1,
           1
       ],
       [
           43,
           1,
           1
       ],
       [
           37,
           1,
           1
       ],
       [
           28,
           1,
           1
       ],
       [
           40,
           1,
           1
       ],
       [
           27,
           1,
           1
       ],
       [
           58,
           1,
           1
       ],
       [
           44,
           1,
           1
       ],
       [
           30,
           1,
           1
       ],
       [
           25,
           1,
           1
       ],
       [
           64,
           1,
           1
       ],
       [
           65,
           1,
           1
       ],
       [
           29,
           1,
           1
       ],
       [
           38,
           1,
           1
       ],
       [
           62,
           1,
           1
       ],
       [
           50,
           1,
           1
       ],
       [
           44,
           1,
           1
       ],
       [
           43,
           1,
           1
       ],
       [
           64,
           1,
           1
       ],
       [
           30,
           1,
           1
       ],
       [
           46,
           1,
           1
       ],
       [
           48,
           1,
           1
       ],
       [
           36,
           1,
           1
       ],
       [
           57,
           1,
           1
       ],
       [
           48,
           1,
           1
       ],
       [
           53,
           1,
           1
       ],
       [
           48,
           1,
           1
       ],
       [
           19,
           1,
           1
       ],
       [
           63,
           -1,
           1
       ],
       [
           25,
           -1,
           1
       ],
       [
           22,
           -1,
           1
       ],
       [
           21,
           -1,
           1
       ],
       [
           41,
           -1,
           1
       ],
       [
           28,
           -1,
           1
       ],
       [
           60,
           -1,
           1
       ],
       [
           30,
           -1,
           1
       ],
       [
           59,
           -1,
           1
       ],
       [
           28,
           -1,
           1
       ],
       [
           51,
           -1,
           1
       ],
       [
           58,
           -1,
           1
       ],
       [
           58,
           -1,
           1
       ],
       [
           50,
           -1,
           1
       ],
       [
           39,
           -1,
           1
       ],
       [
           19,
           -1,
           1
       ],
       [
           37,
           -1,
           1
       ],
       [
           58,
           -1,
           1
       ],
       [
           24,
           -1,
           1
       ],
       [
           21,
           -1,
           1
       ],
       [
           24,
           -1,
           1
       ],
       [
           35,
           -1,
           1
       ],
       [
           25,
           -1,
           1
       ],
       [
           54,
           -1,
           1
       ],
       [
           48,
           -1,
           1
       ],
       [
           26,
           -1,
           1
       ],
       [
           49,
           -1,
           1
       ],
       [
           38,
           -1,
           1
       ],
       [
           59,
           -1,
           1
       ],
       [
           38,
           -1,
           1
       ],
       [
           32,
           -1,
           1
       ],
       [
           35,
           -1,
           1
       ],
       [
           33,
           -1,
           1
       ]
   ],
   "eta": 0.1,
   "lambda": 0,
   "numFeatures": 3,
   "y": [
       19291.1,
       13879.3,
       10864.6,
       16708.5,
       16282.6,
       19975.8,
       13410.5,
       14805.3,
       15641.4,
       15201.4,
       21155.5,
       14742.3,
       16435.9,
       15839.8,
       16441.5,
       12169.4,
       21068.8,
       16371.9,
       13654,
       12096.8,
       15748.2,
       15894.3,
       15262.1,
       14567.6,
       16379.8,
       22492.5,
       15906.9,
       16315.2,
       15299.2,
       14405,
       13156,
       16052.8,
       15813,
       16732,
       15581.7,
       20001.8,
       15053,
       15510.8,
       21895.8,
       17109.6,
       15221.5,
       14736.9,
       18077.1,
       15776.8,
       14012.6,
       19056.4,
       14384.4,
       13832.1,
       11583.9,
       18571.2,
       19409,
       12088,
       18773.5,
       12407.5,
       14743.8,
       16344.5,
       14809.8,
       15242.8,
       18158.2,
       11120.8,
       25778.5,
       18364.5,
       15697.8,
       16038.5,
       20357.7,
       16700.2,
       14551.8,
       13760,
       18235.8,
       12970.2,
       12966.6,
       13921.8
   ]
}

demo2’s local result’s data:
{
   "biasedX": [
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ],
       [
           66,
           -1,
           1
       ]
   ],
   "y": [
       16053.9,
       14648.8,
       15110.6,
       13282.4,
       15876.3,
       16682.7,
       14815.6,
       17520.4,
       15842.3,
       13078.9,
       15773,
       16310.2,
       14678.1,
       12165.4,
       14328.9,
       14350.6,
       14170.1,
       13344.7,
       21280.4,
       18648.6,
       21669.6,
       13340.3,
       17200.4,
       13626.9,
       16278.3,
       16119.4,
       16397.8,
       13214.2,
       18189.8,
       14883.6,
       14255.1,
       14739.5,
       16494.8,
       15405.9,
       16631.8,
       14651,
       12479.2,
       16674.1,
       19679.5,
       14142.1,
       19610.2,
       15476.5,
       16994.6,
       11597.4,
       18143.2,
       15423.2,
       14874.2,
       12760.1,
       15206.2,
       14833.4,
       11651.4,
       12809.1,
       14294.2,
       14750.9,
       18196.1,
       16810.1,
       18849.1,
       20596.8,
       16691.9,
       16282.9,
       16348.9,
       17130.5,
       19217,
       16059.8,
       12158.3,
       19942.2,
       17687.9,
       17727.1,
       14232.5,
       13755.5,
       16304.7,
       19084.7,
       15562.8
   ],
   "lGrad": [
       -5481971.006186579,
       48999.403924245664,
       -83060.16676040267
   ],
   "lObj": 403042706.557263
}

Here’s the remote result doc’s data:
{
   "currW": [
<PHONE_NUMBER>07015,
<PHONE_NUMBER>546169,
<PHONE_NUMBER>5641186
   ],
   "prevW": [
<PHONE_NUMBER>07015,
<PHONE_NUMBER>546169,
<PHONE_NUMBER>5641186
   ],
   "prevObjective":<PHONE_NUMBER>.627573,
   "currObjective":<PHONE_NUMBER>.627573,
   "eta": 0.1,
   "iteration": 151,
   "Gradient": [
       -38511924.15984652,
       45322.60020584179,
       -1025172.6176176445
   ],
   "lambda": 0,
   "Eg2": [
<PHONE_NUMBER>654995,
<PHONE_NUMBER>.947847,
<PHONE_NUMBER>649.0425
   ],
   "EdW": [
       2.3512990164777765,
       2.8652509257408214,
       3.0029126750799238
   ],
   "rho": 0.5,
   "eps": 0.1,
   "deltaW": [
       1.5201230350517558,
       -1.7476415174771207,
       1.7259628888052772
   ]
}

It would appear that demo1’s pipeline is out of sync. Its data corresponds with the preprocess step. However, the pipeline should use the run step at this point. Interesting.


Fix selection client side error

Rows without keys are non-selectable. Our selection API setSelectRow need to protect the caller from selecting them.

Coverage increased (+0.2%) to 89.892% when pulling d5f583e945c910667ec60a60fa3987448202e6e9 on wewei:patch-1 into 465b248878a540e03694bb6e5d1337fde2aff16c on Microsoft:master.

Close the legacy PR.
Will review the change manually.


Add Export feature to Table

Add the export feature to the Table component.

This can be achieved adding a top level action.
The action callback should invoke a method that runs the logic to export table contents to any desirable format.


Added gis data

Created a raster file that stores the distance to the closest body of water.  Assigned value from that raster to the patches, in a variable called waterDistance.  The actual bodies of water draw black.  Other procedures will need a way to prevent turtles from moving into these black patches.
One problem is that Netlogo wouldn't acknowledge the validity of the .prj files created by ArcGIS for the raster.  I deleted the files, which allowed the dataset to be loaded, but that means we can't combine it with other GIS datasets (since there's no valid projection)  I think this is a low priority, since we can use ArcGIS to create a single raster if we need to combine different sets of input data.

This addition has created a bug where the go procedure will occasionally not run.  I think it might be related to turtles being populated in areas with water (i.e. black patches), but I'm not sure.  Possibly also related to previous issue where go procedure would occasionally not run.

closing pull request without merging until go procedure bug is fixed.


Catch another 'device not found' error code with ALSA

On a device with no sound (such as Travis-CI) I could get a default endpoint but enumerating the formats would then panic. This patch adds the error code that my case returned, and which I believe should be caught instead of panic.
Looking at the code, I think a more rigorous change would be nice, but in the meantime I propose merging this fix.

Thanks


Removing dead code

This PR removes a lot of things, so make sure to check each commits.
It builds on top of https://github.com/o1-labs/marlin/pull/109, so don't merge this one until the previous PR is merged and this one is rebased.

Can you make a corresponding mina PR that uses this as a submodule? I'd like to verify that everything on that side still works 😁

I presume a lot will start to break without removing code there: https://github.com/MinaProtocol/mina/pull/8975


Backports 1.3 version bump to 1.x

Description
Backports 1.3.0 version bump to 1.x branch.
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (1.x@e3c908e). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             1.x      #82   +/-   ##
======================================
  Coverage       ?   82.94%
  Complexity     ?      552
======================================
  Files          ?       61
  Lines          ?     2058
  Branches       ?      146
======================================
  Hits           ?     1707
  Misses         ?      245
  Partials       ?      106

Continue to review full report at Codecov.

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


fix: python: poetry: incompatible with newer version of poetry.lock

https://github.com/python-poetry/poetry/commit/41706e649cf3ee9b066c59920b4e10e686f8c6d5 broke the parser.
Poetry changed it's lock file structure some time ago.
This fixes the translator crashing on the new format
@phaer

@phaer Oops I jsut noticed that you already fixed that in https://github.com/nix-community/dream2nix/pull/405.
Feel free to revert my change when you complete the PR instead of rebasing

@DavHau No worries! I guess it became a bit confusing when the not-quite-finished poetry support has been merged, because its not totally clear whether it's something we support already or something still in development.
It's interesting how both of us decided to support both old and new lock files. Thinking about it, supporting just the new one is probably good enough? I'd care about older versions for pyproject.toml, but I believe for lock files it might be good enough to just assume that those can be updated automatically? (i.e. by re-locking)

I think supporting both old and new format would be great as long as it's not too complex to do so.


All documentations for the final sprint.

I've added all the final documents for the final sprints. Please review them and let me know if there are any questions/suggestions.

Wow so many documents, looking good!

Sorry wrong button

It's okay ;)

Looks good to me. I think we can merge, anyone else?


Require cycle warning

i have this require cycle error nothing major but its better to be fix.
and thanks for all the great work on this DatePicker ✌

 WARN  Require cycle: node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/index.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/Header.js -> node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/index.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/Days.js -> node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/index.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/SelectMonth.js -> node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/react-native-modern-datepicker/src/datePicker/components/index.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/Calendar.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/index.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/index.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/Calendar.js -> node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/index.js -> node_modules/react-native-modern-datepicker/src/datePicker/components/SelectTime.js -> node_modules/react-native-modern-datepicker/src/datePicker/DatePicker.js

have this been solved yet @amiralibg


pkg/objectfile: Use mount namespace id in cache key instead of build id

In the worst case, determining the build id can be very expensive, as we need to hash the .text section. Determining the mount namespace id is significantly cheaper and with mount namespace id, modtime and path we still have a key that is highly stable for the properties that we need it for.
Why?
We have been seeing a lot of text section hashing in CPU profiling data of the agent in customer environments.
What?
Use a cheaper to determine cache key.
How?
Instead of requiring to determine the build id of an object file for its cache key, we use the combination of the processes' mount namespace id, path and mod time.
Test Plan
Old and new unit tests passing and ran for a bit while performing some high process churn loops in bash.

As discussed IRL using this string as the cache key might not be as efficient as using others, such as a combination of inode + modtime to create the "key" -> "build id" cache.
The other thing that seems a bit off is that we are bumping into so many binaries without build ID. This seems a bit fishy to me and we should get to the bottom of it. Perhaps we are trying to process files we shouldn't be dealing with?


Fixes for IE...

I changed a few things to get this working better in IE:

Added a simple classList fallback
Fixed some JS event handling stuff
Made the denim background image display

There are still some CSS fixes needed, for example IE doesn't support rem units or the placeholder attribute for the search field, but at least it is functional now. :)
Tested in IE 8 and 9.  A querySelectorAll fallback or jQuery will be needed for anything further back.

Thank you!


chore: Add invisible ReCaptcha to new Sell flow

Description
This adds the invisible ReCaptcha to the new Sell flow (Recaptcha PR for the old flow: https://github.com/artsy/force/pull/8916).
As I understand the component, it does not block any suspicious actions and only adds information about these actions to our dashboard (more context).

Just added you both to the recaptcha dashboard for staging/prod "sites."


Stuck at "health check passed"

After executing "run.bat" with administrative privileges, the process on CMD windows stops at "health check passed", and no imagery is added to MSFS 2020 whatever I choose as an option: servers,...I am in Spain, no Google proxy needed.
Thank you!

Please look at the configuration in game: https://www.youtube.com/watch?v=Lk7GK5XLTt8
Especially the rolling cache is very important, if you turn it on, please turn it off and clear the cache.

i do have the same issue , can you be please be more specific about what to do sir ?

I think it is a DNS issue, I'm trying to find out.

Please try this version: https://github.com/derekhe/msfs2020-google-map/releases/tag/2.2.5

Thank you, problem fixed!

I am also stuck at 'health check passed', running latest version, rolling cache off.
Thank you


InterruptedException Ignored When Stopping the Servlet

Fixes #4694
cc @WaltonG  @antoine2711

Fixes #{issue number here}
cc @WaltonG @antoine2711

Include the issue number for Github to link the  PR with the issue

Include the issue number for Github to link the PR with the issue

Here is the link to the Github issue https://github.com/OpenRefine/OpenRefine/issues/4735

You should have Fixes #4694 instead to Fixes #{issue numberhttps://github.com/OpenRefine/OpenRefine/issues/4694}

Thanks let me correct it
On Mon, Apr 11, 2022, 10:07 AM WaltonG @.***> wrote:

You should have Fixes #4694
https://github.com/OpenRefine/OpenRefine/issues/4694 instead to Fixes
#{issue numberhttps://github.com//issues/4694
https://github.com/OpenRefine/OpenRefine/issues/4694}
—
Reply to this email directly, view it on GitHub
https://github.com/OpenRefine/OpenRefine/pull/4734#issuecomment-1094630265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALOKS6AAJDMQYMM4KJV4GOLVEPFTXANCNFSM5TB424VQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello @WaltonG i hope now it looks cool to be merged.

Hello @wetneb  Re requesting for your review.

cc @wetneb  Requesting for your reviews ,Thanks.

Hi @sherrif10, let us slow down a little bit please: there is no need to request my review twice, an hour after your earlier message.

Thanks @wetneb


Incompatibility with Spring-Core 2.0.0: Double encoding of of passwords on register and resetpassword

The default config for Spring security ui silently breaks password registration and resetting with org.grails.plugins:spring-security-core:2.0.0
More detail:
http://stackoverflow.com/questions/7955111/grails-spring-security-ui
Apparently, this bug was known, and then perhaps lost as I get  404 for the link?
http://jira.grails.org/browse/GPSPRINGSECURITYUI-27

Not a bug.
My mistake. I found the write up of the issue on the last page of the documentation, under Password Hashing
http://grails-plugins.github.io/grails-spring-security-ui/v1/guide/customization.html


Add license and fix indexers

We need to address the following issues:

Add the missing license
Investigate indexer issues as something is malfunctioning
Optimize frontend performance by implementing lazy loading for images
Add multiple repo links on the main page after search input

All updates for Github Issue Search were merged.
Updates for image search demo: https://github.com/manticoresoftware/manticore-image-search/pull/1

Requested changes in the PR.

Fixed in the PR

Requested one change in the PR.

All merged.


vcpkg ignores default-features: false

Describe the bug
It seems like vcpkg does not respect default-features: false in transitive dependencies. Consequently, vcpkg installs unwanted features.
Environment

OS: Windows 10
Compiler: not relevant
vcpkg version: 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895
vcpkg ports commit: 6a3dd08

To Reproduce
Steps to reproduce the behavior:

./vcpkg depend-info glib

Only pcre2 depends on bzip2.
Although pcre2 has disabled default features for bzip2, the feature tool is still selected.

Expected behavior
To not select bzip2[tool].
Failure logs
vcpkg-cmake:
vcpkg-cmake-config:
bzip2[tool]: vcpkg-cmake, vcpkg-cmake-config
libiconv:
zlib: vcpkg-cmake
dirent:
gettext: libiconv
libffi: vcpkg-cmake, vcpkg-cmake-config
pcre2: bzip2, vcpkg-cmake, vcpkg-cmake-config, zlib
vcpkg-tool-meson:
glib: dirent, gettext, libffi, libiconv, pcre2, vcpkg-tool-meson, zlib

Duplicate of https://github.com/microsoft/vcpkg/issues/31230

Duplicate of #31230

Didn't find it because it was only category:question. But this is a bug, right? If I'd have to specify in my manifest that I don't want the default features of a transitive dependency, default-features: false doesn't make any sense.

But this is a bug, right?

No this is by design.

If I'd have to specify in my manifest that I don't want the default features of a transitive dependency, default-features: false doesn't make any sense.

It still makes sense. Otherwise would be not able to disable the tool feature of bzip2 at all. So by default "xyz" in a manifest means xyz[defaults] and with default-features: false it means xyz[core] so default features can be disabled by the top level/users manifest.

Let me clarify: It doesn't make sense to put default-features: false in a port in the catalogue if default features are selected anyway.

It still makes sense. Otherwise would be not able to disable the tool feature of bzip2 at all. So by default "xyz" in a manifest means xyz[defaults] and with default-features: false it means xyz[core] so default features can be disabled by the top level/users manifest.

Example:
Port B exits with a default feature def.
Port A depends on B.
You install A and B[core] => You get A[core] and B[core,def]
Now you use default-features: false in a port in the catalogue (in this example B)
Port B exits with a default feature def.
Port A depends on B[core].
You install A and B[core] => You get A[core] and B[core]

I don't think it has to do with transitive dependencies. Lets use real ports. In my example, I tried to install glib. glib depends on pcre2. pcre2 depends on bzip2 and uses default-features: false to get rid of bzip2[tool]. Even if I install pcre2, I get bzip2[tool].
This is the output of vcpkg depend-info pcre2:
vcpkg-cmake:
vcpkg-cmake-config:
bzip2[tool]: vcpkg-cmake, vcpkg-cmake-config
zlib: vcpkg-cmake
pcre2: bzip2, vcpkg-cmake, vcpkg-cmake-config, zlib

Now I remove default-features: false in pcre2 for the bzip2 dependency. The output of vcpkg depend-info pcre2 stays the same. But when I try vcpkg install pcre2 bzip2[core] it still includes the tool feature. This doesn't happen anymore if I'd restore default-features: false.
I understand the need for default-features: false now. However, this does not explain why vcpkg install pcre2 has to include bzip2[tool]. If one port disables a default feature and no other port needs that feature, what is the point of ignoring the fact that the feature was explicitly disabled?

If one port disables a default feature and no other port needs that feature, what is the point of ignoring the fact that the feature was explicitly disabled?

You can follow one of the many discussions about that here: https://github.com/microsoft/vcpkg/issues/26664#issuecomment-1374506677
It is a design decision that was done in the past. I don't want to discuss it again.


Update the game over message

Update the game over message so people know how to play again!

File Cahnged


Issue: Haskell Random Tests Call Solution Setup instead of Solution

I tried to create a Haskell translation of this kata and facing with the following issue:
The random test call the Solution Setup instead of Solution:

If the solution setup tab is active it will use that, if the solution tab is active it will use that instead. It allows you to test the setup code (useful for bug/refactoring based challenges).

Hi, I'm aware about that functionality. I might said it in a wrong way: The issue that the Solution tab is selected but the Solution Setup is called in tests instead. Regards suic