workaround for firmware-imx download

This fixes the build for now, but I don't know what is the issue with the ADD command implementation not being able to get along with the web server when using https; maybe the TLS version or algorithms??

I don't know what is the issue with the ADD command implementation not being able to get along with the web server when using https; maybe the TLS version or algorithms?

I don't know either. You can recreate it very simply using this program:
package main

import (
	"fmt"
	_ "github.com/motemen/go-loghttp/global"
	"log"
	"net/http"
)

func main() {
	client := http.DefaultClient
	req, err := http.NewRequest("GET", "https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin", nil)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Printf("%+v\n", req)
	resp, err := client.Do(req)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Printf("%d\n", resp.StatusCode)
}

I don't know what is the issue with the ADD command implementation not being able to get along with the web server when using https; maybe the TLS version or algorithms?

I don't know either. You can recreate it very simply using this program:
package main

import (
	"fmt"
	_ "github.com/motemen/go-loghttp/global"
	"log"
	"net/http"
)

func main() {
	client := http.DefaultClient
	req, err := http.NewRequest("GET", "https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin", nil)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Printf("%+v\n", req)
	resp, err := client.Do(req)
	if err != nil {
		log.Fatal(err)
	}
	fmt.Printf("%d\n", resp.StatusCode)
}

I would prefer to keep with the https, but that's not a big deal switch to http due to this strange problem. FWIW, here are some debug information from wget (which works) and the GO code from @deitch, I just notice first that a cookie is created, so I disabled cookies and it still works:
wget --no-cookies -d https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin
DEBUG output created by Wget 1.21.3 on linux-gnu.

Reading HSTS entries from /home/rene/.wget-hsts
URI encoding = ‘UTF-8’
Converted file name 'firmware-imx-8.18.bin' (UTF-8) -> 'firmware-imx-8.18.bin' (UTF-8)
--2023-08-10 11:20:36--  https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin
Certificates loaded: 140
Resolving www.nxp.com (www.nxp.com)... <IP_ADDRESS>
Caching www.nxp.com => <IP_ADDRESS>
Connecting to www.nxp.com (www.nxp.com)|<IP_ADDRESS>|:443... connected.
Created socket 3.
Releasing 0x000056241e1064e0 (new refcount 1).

---request begin---
GET /lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin HTTP/1.1
Host: www.nxp.com
User-Agent: Wget/1.21.3
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Type: application/octet-stream
ETag: "436501f8e67c10eed6bba88457e701a2:1670298606.29048"
Last-Modified: Thu, 22 Sep 2022 19:26:49 GMT
Content-Length: 1513050
Expires: Thu, 10 Aug 2023 09:20:36 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Thu, 10 Aug 2023 09:20:36 GMT
Connection: keep-alive
Set-Cookie: CC=DE; path=/; secure
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000; includeSubdomains;
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Server-Timing: ak_p; desc="1691659236595_35057694_86585280_22_4238_4_-_-";dur=1

---response end---
200 OK
Registered socket 3 for persistent reuse.
Parsed Strict-Transport-Security max-age = 31536000, includeSubDomains = true
Updated HSTS host: www.nxp.com:443 (max-age: 31536000, includeSubdomains: true)
Length: 1513050 (1.4M) [application/octet-stream]
Saving to: ‘firmware-imx-8.18.bin.5’

firmware-imx-8.18.bin.5             100%[================================================================>]   1.44M  --.-KB/s    in 0.08s

2023-08-10 11:20:36 (18.7 MB/s) - ‘firmware-imx-8.18.bin.5’ saved [1513050/1513050]

Saving HSTS entries to /home/rene/.wget-hsts

And from the GO code:
GODEBUG=http2debug=2 go run test2.go
&{Method:GET URL:https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[] Body:<nil> GetBody:<nil> ContentLength:0 TransferEncoding:[] Close:false Host:www.nxp.com Form:map[] PostForm:map[] MultipartForm:<nil> Trailer:map[] RemoteAddr: RequestURI: TLS:<nil> Cancel:<nil> Response:<nil> ctx:0xc000128010}
2023/08/10 11:24:54 http2: Transport failed to get client conn for www.nxp.com:443: http2: no cached connection was available
2023/08/10 11:24:54 http2: Transport creating client conn 0xc00017c180 to <IP_ADDRESS>:443
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: wrote SETTINGS len=18, settings: ENABLE_PUSH=0, INITIAL_WINDOW_SIZE=4194304, MAX_HEADER_LIST_SIZE=10485760
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: wrote WINDOW_UPDATE len=4 (conn) incr=1073741824
2023/08/10 11:24:54 http2: Transport encoding header ":authority" = "www.nxp.com"
2023/08/10 11:24:54 http2: Transport encoding header ":method" = "GET"
2023/08/10 11:24:54 http2: Transport encoding header ":path" = "/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin"
2023/08/10 11:24:54 http2: Transport encoding header ":scheme" = "https"
2023/08/10 11:24:54 http2: Transport encoding header "accept-encoding" = "gzip"
2023/08/10 11:24:54 http2: Transport encoding header "user-agent" = "Go-http-client/2.0"
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: wrote HEADERS flags=END_STREAM|END_HEADERS stream=1 len=69
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: read SETTINGS len=30, settings: HEADER_TABLE_SIZE=4096, MAX_CONCURRENT_STREAMS=100, INITIAL_WINDOW_SIZE=65535, MAX_FRAME_SIZE=16384, MAX_HEADER_LIST_SIZE=32768
2023/08/10 11:24:54 http2: Transport received SETTINGS len=30, settings: HEADER_TABLE_SIZE=4096, MAX_CONCURRENT_STREAMS=100, INITIAL_WINDOW_SIZE=65535, MAX_FRAME_SIZE=16384, MAX_HEADER_LIST_SIZE=32768
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: wrote SETTINGS flags=ACK len=0
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: read SETTINGS flags=ACK len=0
2023/08/10 11:24:54 http2: Transport received SETTINGS flags=ACK len=0
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: read HEADERS flags=END_HEADERS stream=1 len=351
2023/08/10 11:24:54 http2: decoded hpack field header field ":status" = "404" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "mime-version" = "1.0" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "content-length" = "745" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "cache-control" = "no-cache, no-store, must-revalidate" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "pragma" = "no-cache" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "expires" = "0" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "content-type" = "text/html" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "expires" = "Thu, 10 Aug 2023 09:24:55 GMT" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "cache-control" = "max-age=0, no-cache, no-store" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "pragma" = "no-cache" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "date" = "Thu, 10 Aug 2023 09:24:55 GMT" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "set-cookie" = "CC=DE; path=/; secure" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "x-content-type-options" = "nosniff" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "strict-transport-security" = "max-age=31536000; includeSubdomains;" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "x-xss-protection" = "1; mode=block" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "x-frame-options" = "SAMEORIGIN" (sensitive)
2023/08/10 11:24:54 http2: decoded hpack field header field "server-timing" = "ak_p; desc=\"1691659495075_35057694_86662874_23_2076_4_0_15\";dur=1" (sensitive)
2023/08/10 11:24:54 http2: Transport received HEADERS flags=END_HEADERS stream=1 len=351
2023/08/10 11:24:54 http2: Framer 0xc00020c2a0: read DATA flags=END_STREAM stream=1 len=745 data="<!doctype html> <html> <head>     <title>Page not available</title>     <style type=\"text/css\">body { text-align: center; padding: 150px; }h1 { font-size: 40px; }body { font: 16px Helvetica, sans-serif; color: #333; }#error { display: block; text-align: le" (489 bytes omitted)
2023/08/10 11:24:54 http2: Transport received DATA flags=END_STREAM stream=1 len=745 data="<!doctype html> <html> <head>     <title>Page not available</title>     <style type=\"text/css\">body { text-align: center; padding: 150px; }h1 { font-size: 40px; }body { font: 16px Helvetica, sans-serif; color: #333; }#error { display: block; text-align: le" (489 bytes omitted)
404

It would be interesting if we could get TLS info on the connections

It keeps getting strange. I just connected via this, and it worked:
$ openssl s_client -connect www.nxp.com
...
---
SSL handshake has read 4651 bytes and written 393 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
...
GET /lgfiles/NMG/MAD/YOCTO/firmware-imx-8.18.bin HTTP/1.1
Host: www.nxp.com

and it worked. This clearly is TLS v1.3.
Also, a bad request gives:
HTTP/1.0 400 Bad Request
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: text/html
Content-Length: 249
Expires: Thu, 10 Aug 2023 09:46:17 GMT
Date: Thu, 10 Aug 2023 09:46:17 GMT
Connection: close

That is Akamai, clearly.

I did a tcpdump capture of curl and the go test program, filtered out just the TLS handshake, and then compared them. They were very similar, both actually used TLS v1.3, but the success used cipher suite TLS_CHACHA20_POLY1305_SHA256 (0x1303), while the failure used cipher suite TLS_AES_256_GCM_SHA384 (0x1302).
The failure and the success offered both ciphers, yet the server chose TLS_AES_256_GCM_SHA384 in the failure case, and TLS_CHACHA20_POLY1305_SHA256 in the success case. The success case offered 49 different ciphers, and TLS_CHACHA20_POLY1305_SHA256 was the first followed by TLS_AES_256_GCM_SHA384, wile the failure offered 19 with TLS_AES_256_GCM_SHA384 second to last and TLS_CHACHA20_POLY1305_SHA256 last, but I could not see why it would make a difference.
If I force that cipher, it works. Updated go:
        tlsConfig := &tls.Config{
                CipherSuites: []uint16{0x1303},
        }
        transport := &http.Transport{
                TLSClientConfig: tlsConfig,
        }
        client := &http.Client{Transport: transport}

Oh, interesting. From the go doc:
	// CipherSuites is a list of enabled TLS 1.0–1.2 cipher suites. The order of
	// the list is ignored. Note that TLS 1.3 ciphersuites are not configurable.

So why would the cipher suites matter? Could it actually be doing TLS 1.2?
Huh, it is. Here is from the pcap files:
Frame 4: 343 bytes on wire (2744 bits), 343 bytes captured (2744 bits)
Ethernet II, Src: Apple_2e:b3:d8 (b0:be:83:2e:b3:d8), Dst: Ubiquiti_49:d4:43 (fc:ec:da:49:d4:43)
Internet Protocol Version 4, Src: <IP_ADDRESS>, Dst: <IP_ADDRESS>
Transmission Control Protocol, Src Port: 62077, Dst Port: 443, Seq: 1, Ack: 1, Len: 277
Transport Layer Security
    TLSv1.3 Record Layer: Handshake Protocol: Client Hello
        Content Type: Handshake (22)
        Version: TLS 1.0 (0x0301)
        Length: 272
        Handshake Protocol: Client Hello
            Handshake Type: Client Hello (1)
            Length: 268
            Version: TLS 1.2 (0x0303)

0x0303 clearly is version 1.2. That is why the CipherSuite selection is working, but unclear to me why the server is picking a different ciphersuite, and why it is failing.

If the ADD command fails, but we still want to use HTTPS, could we use just:

We disable network for all pkg builds, except via ADD. Besides making for generally cleaner process, it makes it auditable. Nothing is installed except something that is:

already in the eve/alpine cache, so we know it is there
the repo, which is tracked
something added via ADD, which is predictable and parsable

It became a requirement about 8-9 months ago.

I've just found that ADD works fine if use another NXP address:
https://cache.nxp.com

instead of
https://wwww.nxp.com is

So, my suggestion would be just to replace the address.
I guess it's something with the NXP server setup.

If that works, then great. I just tested it, too, it works. Nice find @OhmSpectator !
@eriknordmark do you want to update this PR to use that address?


Any user can sigup on Venue.volentix.io

Shawn, there are two question:

[ ] If any user can signup on Venue.volentix.io ?
[ ] And also is it possible to collect new signups in constant contact email list?

if so, that's ok, if not Marketing needs that.
Thanks,
https://venue.volentix.io/signup

Matthew, I will add you @volentixnonton11  here to be in the loop.

Yes anyone can signup on venue.volentix.io (although this is so obviously a YES, I wonder if I am misinterpreting your question).
Second, emails right now are not sent to constant contact, but that can probably be done (I believe there is an API for it). It can be scheduled for next iteration if you would like.

@shawnlauzon  what is important for now, is having a record of all emails.
constant contact is not urgent for now, but can be prioritized.

Yes, we retain all emails.

How we can have access to those emails?

Email with users and emails set to @Mojganahk


How to configure several projects in coroot installing via helm chart?

Hello!
I use coroot for monitor two k8s clusters, each cluster has own prometheus, clickhouse, exporters etc. Each cluster has own project in coroot.
But when i install coroot via helm (i use 0.5.6 coroot chart version) i can specify settings only for default project.
Is it possible to configure several projects in helm charts using extra configMap for example or any other way?
Thank you, really appreciate the coroot.

@def thanks for your reply, I'll look forward to updates

@def I just wanted to create a ticket for the same... did you decide on anything?
On top of that, would it be possible to configure the alerting?


Cannot cancel extract operation

I want to extract a file asynchronously so I used OperationQueue like this:
let queue = OperationQueue()
queue.addOperation {
    do {
        _ = try archive.extract(entry, to: temporaryFileURL)
        completionHandler(temporaryFileURL)
    } catch {
        print("Cannot extract video file: \(error)")
    }
}

And then I want to cancel my operation with queue.cancelAllOperations() but the extraction work doesn't stop…
How to fix it?
Thanks

To cancel an extract operation, you have to pass in an instance of Progress and keep a reference to it so that you can call cancel() at a later point.
You can find some details and a link to the Progress docs in the progress tracking section of the readme.


Fix CI ignore yarn lock

Closes https://github.com/api3dao/airnode/issues/1430

No longer relevant.


Fix Issue With Evaluating Varying Closure Keyword Parameters During Batched Evaluation

When evaluating varying closure keyword parameters in batched execution, the value of the first lane in the batch would be used for the whole batch.  More details in an issue I made here: #1619
I don't really understand this code at all, this fix was just made by following the suggestion of Stephen on the dev list to copy the code from llvm_gen_closure to llvm_gen_keyword_fill.
It fixes the one simple case which I've added a test for, but the more complex functionality of this code I copied would only be tested if you used array keyword parameters on a closure.  This would be more annoying to test, since I don't think testshade declares any closures with array keyword parameters.
Also, while testing, I found a segfault with adding a null closure in batched evaluation - I'll post a repro for that on the dev list, and hopefully we can clean that up soon too.

[x] I have read the contribution guidelines.
[ ] I have previously submitted a Contributor License Agreement.
[ ] I have updated the documentation, if applicable.
[x] I have ensured that the change is tested somewhere in the testsuite (adding new test cases if necessary).
[x] My code follows the prevailing code style of this project.

As per Alex's comment, I've removed support for array indexing, avoiding the bug he observed with the faulty array handling I copied.  I wasn't able to get it working with one big memcpy ... unsure if this is due to not understanding the context well enough, or whether a per-component approach is required in order to get masking and such working.  Anyway, I started from the other end, with the more complex code that worked, and removed the array handling but kept the component handling - this seems to have resulted in working code, and I've removed the array part, and added an assert that the arraylen is 0.
As for the bug at line 7243, I've added #1621 with a test case that demonstrates that bug - does it make sense to merge this and then continue that part of the conversation over there?


feat(es/minifier): Drop redundant function parameters

Description:
Trailing parameters in functions/arrow expressions can be dropped if they're not referenced inside the function body without introducing side effects. e.g. function f(a, b, c) {f(a);} -> function f(a) {f(a);}.
This simply iterates (reverse) through the parameters and once it encounters a parameter that is used, it stops and drops the ones it found. If no referenced parameters are found then all parameters can be dropped.

BREAKING CHANGE:

Related issue (if exists):

This might break TypeScript interfaces, will have to test

I think this should check for option about function.length

I think this should be a config option if that's what you're referring to, but I'm not sure what you're referring to regarding function.length

I think this should check for option about function.length

I think this should be a config option if that's what you're referring to, but I'm not sure what you're referring to regarding function.length

It's the keep_fargs option in Terser.

anything blocking this? <3

anything blocking this? <3

Not at the moment. I should be able to get around to finishing this some time this week.


Ensure compatibility with PHP 7.4 spread operator in array expression

Related to #4382.

Thank you @julienfalque.

(i did rebase + squash + fix minor issues)


[FIX] Padding infeatures/outfeatures for exllama, exllama v2, and marlin

Resolves #100

Confirmed my suspicion that padding code will impact the shape of saved tensors to disk. Pack has been fixed so that the saved size is correct (original) but now running into load issues since the expanded/padded buffers are now larger than the tensors on disk so accelerate is throwing shape not same errors. We will explore 2 methods to deal with this tomorrow.

Update: We are going with Plan B.


Homebrew Cask

Can you confirm that as of right now the only way to run the app on MacOS is by building it from source?
It would be great to have an Homebrew package of the app.
Thanks a lot!
T

Hi! I consider the current state pre-alpha, and I'm not sure if a consumer packing is appropriate at this point. We also have the Mac/Win/Linux artifacts built using GitHub Actions, this should have a link from the readme.

Related to #16

I'm trying me feet at a homebrew cask for psst.
You can see it at https://github.com/weltonrodrigo/homebrew-cask/blob/master/Casks/psst.rb
I see you have been discussing this subject and here is why I think you should embrace this formula:

People are already using your software in the nightly built version
Download link for this version is already prominent in this GitHub repo
This homebrew only automates that process and makes it much easier and happier

I agree with you that a nightly build version can tarnish Psst reputation, but given that people is already using it and it's the only binary you provide right now, this risk is already been taken.
As a suggestion, I believe you can mitigate that risk by creating a stable branch and use the same software to generate a downloadable stable version. I can change the formula to use that instead.
I'm already using this formula and you know what?
I you want to use this formula too, you can just:
brew install --no-quarantine weltonrodrigo/homebrew-cask/psst

If you give me the green light, I can submit my formula to homebrew repo, or, If you prefer, you can do it yourself.
WOULDBENICEs:

If you agree with this formula, would be nice to have a versioned link to download the binary. That way, brew can detect and periodically upgrade to new versions.
It would be nice to have a (complete) list of files and directories to delete when uninstalling Psst.

Would adding date/timestamps to the release names be usable in lieu of a version number? Just thinking what is least burdensome for the maintainers. That being said, the program is already pretty mature and is definitely worthy of a version number IMO :)

I used
brew install --no-quarantine weltonrodrigo/homebrew-cask/psst
as I could not. find an apple silicon / arm build and I got it running in seconds.
Thanks a lot!

I think this issue (#53) can be closed due to https://formulae.brew.sh/cask/psst#default

Yes, thank you!


qt5{9,11,12}: better pulseaudio 13 fix, unbreak qt59

Motivation for this change
Besides unbreaking qt59.qtwebengine,
"better" since this uses official upstream fix for the issue.
May have implications about pulseaudio linked vs loaded,
in the direction of allowing stub usage (I think).
This restores behavior changed in the pulseaudio13 fix
that this commit replaces.
Fixes #72384.

On staging it appears we've dropped qt59 and qt511,
and actually qt511.qtwebengine.src 404's for me
(but I was able to test using cached copy).
Not sure what that means for these fixes or how/where
they should be sent..
Hence sending to master where the fix is needed.
Have not build-tested all of these, mostly ensured the patches applied
since the fix patch is different (but not functionally) depending
on what version the vendored chromium is 'based on'.
Luckily it looks like 511 can use a patch for a different 'base'
which is good since its base didn't receive this fix.
Anyway, hopefully this has all the pieces needed to address
the build breakage issue, however we choose to proceed.
Also, very sorry for not seeing this fixed sooner!
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thanks for attempting to fix the build, but it looks like a one digit hash mismatch has slipped through:
%  nix-build . -A qt59.qtwebengine
these derivations will be built:
  /nix/store/0hd255r6i5mqg83wpdna2qkgyz9pw0f2-fix-build-with-pulseaudio-13.0-for-69-based.patch.drv
  /nix/store/x58mhgdr9lasrdrkjyn1dhyz62lmfj1s-qtwebengine-5.9.7.drv
building '/nix/store/0hd255r6i5mqg83wpdna2qkgyz9pw0f2-fix-build-with-pulseaudio-13.0-for-69-based.patch.drv'...

trying https://codereview.qt-project.org/gitweb?p=qt/qtwebengine-chromium.git;a=patch;h=94055f1498dd132ba6c1abba782c5b47c07e5108
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4905  100  4905    0     0  24525      0 --:--:-- --:--:-- --:--:-- 24402
hash mismatch in fixed-output derivation '/nix/store/dgg5dcnzfdg688b9qsk4ag0j176zzfyd-fix-build-with-pulseaudio-13.0-for-69-based.patch':
  wanted: sha256:0lmvf1v7y55k9q0qgzm5mhggp752ayyb7kxhdxjfxx9yqd3din90
  got:    sha256:0lmvf0v7y55k9q0qgzm5mhggp752ayyb7kxhdxjfxx9yqd3din90
cannot build derivation '/nix/store/x58mhgdr9lasrdrkjyn1dhyz62lmfj1s-qtwebengine-5.9.7.drv': 1 dependencies couldn't be built
error: build of '/nix/store/x58mhgdr9lasrdrkjyn1dhyz62lmfj1s-qtwebengine-5.9.7.drv' failed

Whops, haha sorry about that.  Should be fixed now :).

Err, one sec.

Sorry about that, actually fixed now.  Doh.
Yes the hashes for 511 and 59 patches are the same, at least that's what I'm observing.
Somewhat surprising since they're different commits but likely fetchpatch (as used here with features like adding prefix and such) prunes that out.  Neat!

@GrahamcOfBorg build qt512.qtwebengine

On staging it appears we've dropped qt59 and qt511,
and actually qt511.qtwebengine.src 404's for me
(but I was able to test using cached copy).

Not sure what that means for these fixes or how/where
they should be sent..

Wouldn't that just make unnecessary conflicts with staging to fix 5.11 and 5.9 when they're removed?
They're not used for anything, so I think we'd just need the fix for 5.12.

Wouldn't that just make unnecessary conflicts with staging to fix 5.11 and 5.9 when they're removed?

Yes. I think we should just fix 5.12.


Add Noetic support. Set compiler flags based on CMake version.

Signed-off-by: Thomas Denewiler<EMAIL_ADDRESS>

@lauralindzey If you'd like to review we can merge this.


percona-server_8_0: init at 8.0.34

Description of changes
Add another MySQL variant, based on the existing mysql80 package.
Percona Server for MySQL is mostly a drop-in replacement for MySQL and can be used with the NixOS module as services.mysql.package = pkgs.percona-server_8_0.
The generic MySQL NixOS test is now also used for the Percona variant. I removed the empty mariadb node definition from the test which seems to serve no purpose anymore.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

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

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/) (ran --help for every executable that supports it and skimmed the output, for Darwin and Linux)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2780


Crash on launch

Having only Jukebox 2.2.2 + Geode v2.0.0-beta.14 causes the game to crash on launch with:
Crash log: https://gist.github.com/Fnige/6709cf4f7f551a96de7d4f110c02ccf2

issue should be fixed on latest release


Eslint refactor

Simplified eslint config and cleaned up some files while I was at it

I added one commit where I just turned on the rule.
The next commit is the result of running yarn lint --fix. Any out of order imports are automatically sorted.
Caveats: they'll show up as "fixable errors", so the --fix is required to sort them. Screenshot below


How can this be run with a single GPU?

I have attempted to limit the GPU IDs to 0 in both the script and code, but it results in a CUDA error. Do you have any advice on how inference may be run on a single GPU?

This was mentioned in #14


Parse version into Base.VersionNumber

Replace version() with a const VersionNumber, and use this to conditionally include the geodesic functionality.

@yeesian - some tweaks to version testing if you'd like to look.

LGTM. I like how it doesn't litter variables all over, the way I did

cheers

Ugh, looks like I missed a couple of things.  I pushed another minor change to clean up versioning.  In particular, looks like the geod library functions are available for 4.9.0 and greater.

feel free to push straight to master

Done - they're very minor fixes.


Investigate transformer traversal optimisation

Possibility for major performance improvements by cutting traversal time by performing everything in a single pass instead of multiple per transformers. Would have to be architectured in such a way that allows for the enter and exit handlers to react to replacements and push them forward to the next transformer pass.

Or even some sort of prepass traversal that checks what transformers actually need to be ran. This would have to react to node replacements as sometimes we insert new ES6 nodes to be transformed later on.

Or even some sort of prepass traversal that checks what transformers actually need to be ran

a fast pre-flight check to prevent some subsequent traversals, and maybe to build up an index for subsequent traversals to utilize. That being said the index might be tricky to maintain during transforms.

@stefanpenner Actually already implemented something like this which is why I closed this issue. It'll do a prepass of the AST and call a check method that each transformer exports that check against the node if the transformer should be ran. These checks are also called when you replace a node. Could be optimised a bit more but it's definently a step in the right direction. Currently doing some profiling and it looks like the code generator is actually taking signifcantly longer than all the traversals/transformations, definently room for improvement on the code generator side as I haven't really done any performance work on it.

@sebmck nice, keep up the good work!


Issue with pip

Hi, I have this error with pip 1.4.1:
$ pip install django-graphos
Downloading/unpacking django-graphos
Could not find a version that satisfies the requirement django-graphos (from versions: 0.0.1a0, 0.0.2a0)
Cleaning up...
No distributions matching the version for django-graphos

This still isn't fixed FYI - any updates or plans to fix?

Hi I'm working with pip version 1.5.6 and python 2.7
The standard pip install commands still doesn't work so I had to install it with the version specification.
My opinion is that until you can fix this bug, you should put in the main wiki/manual the full command (pip install django-graphos==0.0.2a0) just in case someone else tries to install django-graphos won't get frustrated because of the error.

@miscaandrei @munnerz @luukholleman @barrachri Thanks for bringing it to notice! It should be fixed now.


big honkin' september update

hey folks it is your monthly version push. new things:

a fully built out cmc tile that tells you the projected spleener & your turn layout
a spring break beach reminder per TES
a tile for the september 2022 iotm, the jurassic parka
the logic fixes for the cartography + mohawk conundrum in @quarklikeadork's old mohawk PR. (there were enough weird merge issues with it that i just folded it into here. sorry quark.)
finally fixing the machine elf issues, #3 from long ago

this does -not- include dinopath support. sorry y'all, have not had a chance to get to it. it's coming someday, i promise.

oh, one other note -- this isn't getting pushed until i revamp documentation, which will take a few days. so there are a few more days to get code in if you want stuff in here or want to test things out.


fix: revise the logic of exponential strategy

fix the bug https://github.com/Xuanwo/backon/issues/38 in exponential strategy
revise the logic about 'max_delay is None' scenario

Can't assign the Reviewers, so @Xuanwo


[camera] Identify iOS capture device types

Use case
On iOS, the names of the devices returned by the availableCameras method are non-descriptive (e.g. com.apple.avfoundation.avcapturedevice.built-in_video:0).
It would be helpful to be able to easily identify the available cameras on a device so that a particular one could be selected as the default for preview instead of just the first one in the list.
Proposal
To more easily distinguish between available cameras, I propose to create an enum based on all capture device types available on iOS and add an optional parameter to the CameraDescription class that is populated when discovering devices on iOS.

Capturing from my comment in the PR:

This [adding the iOS constants directly] is unlikely to be something we want to add at this layer. The goal of the app-facing package is to provide abstractions, not directly mirror every low-level detail of every platform, as the latter will result in an extremely confusing API.
We have patterns around having high-level abstractions, and then providing platform-specific subclasses with platform details if necessary, which would seem like a better option here. The first thing to evaluate is whether we actually need platform-specific details at all here; having different types of cameras isn't unique to iOS, so a design proposal that surveys the relevant APIs/distinctions across platforms would be the best place to start.


adds a Counter app

request for comment
will be documented before merge

I suppose this PR's functionality is now provided by #23 =)


CLOUD-58882 Select instance group for Ambari server on the UI, fix wa…

…rning message
@keyki plz check

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2607/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/98/


Listeners - multiple network interfaces support

Hi all,
I would like to know if it's possible to implement in cp-ansible the multiple network interfaces support.
Like this doc said , we can make listeners who listen only one network interface.
KAFKA_LISTENERS: LISTENER_BOB://kafka0:29092,LISTENER_FRED://localhost:9092
KAFKA_ADVERTISED_LISTENERS: LISTENER_BOB://kafka0:29092,LISTENER_FRED://localhost:9092

However, today, cp-ansible implements this code :
listeners: "{% for listener in kafka_broker_listeners|dict2items %}{% if loop.index > 1%},{% endif %}{{ listener['value']['name'] }}://:{{ listener['value']['port'] }}{% endfor %}"
advertised.listeners: "{% for listener in kafka_broker_listeners|dict2items %}{% if loop.index > 1%},{% endif %}{{ listener['value']['name'] }}://{{ listener['value']['hostname'] | default(inventory_hostname) }}:{{ listener['value']['port'] }}{% endfor %}"

We can see that all listeners listen on same network interface.
It will be nice to have :
    #### Configuring Multiple Listeners ####
    ## CP-Ansible will configure two listeners on the broker: a broker listener for the broker to communicate and an internal for the components and other clients.
    ## If you only need one listener uncomment this line:
    # kafka_broker_configure_multiple_listeners: false
    ## By default both of these listeners will follow whatever you set for ssl_enabled and sasl_protocol.
    ## To configure different security settings on the internal and external listeners set the following variables:
    kafka_broker_custom_listeners:
      broker:
        name: LISTENER_FRED
        network: localhost
        port: 9092
        ssl_enabled: false
        ssl_mutual_auth_enabled: false
        sasl_protocol: none
      internal:
        name: LISTENER_BOB
        network: kafka0
        port: 29092
        ssl_enabled: true
        ssl_mutual_auth_enabled: false
        sasl_protocol: scram

Thank you in advance.

So far we have had success with allowing for customization of just the advertised listener hostname: https://docs.confluent.io/ansible/current/ansible-configure.html#add-advertised-listener-hostnames
And we are using the hostname key as what to put into the advertised listener.
Per the doc you shared, this is the set up most people need:
listeners=INTERNAL://<IP_ADDRESS>:19092,EXTERNAL://<IP_ADDRESS>:9092
listener.security.protocol.map=INTERNAL:PLAINTEXT,EXTERNAL:PLAINTEXT
advertised.listeners=INTERNAL://ip-172-31-18-160.us-west-2.compute.internal:19092,EXTERNAL://ec2-54-191-84-122.us-west-2.compute.amazonaws.com:9092
inter.broker.listener.name=INTERNAL

Can you let me know what your network architecture looks like, because if you are simply on AWS maybe you can just use the hostname field.
Additionally, and this is a little hacky, all properties are customizable. So you could have something like this in your inventory:
all:
  vars:
    kafka_broker_custom_listeners:
      client_listener:
        name: CLIENT
        port: 9093

kafka_broker:
  hosts:
    ip-172-31-43-14.us-west-2.compute.internal:
      kafka_broker_custom_properties:
        listeners: BROKER://<IP_ADDRESS>:9091,INTERNAL://localhost:9092,CLIENT://ip-172-31-43-14.us-west-2.compute.internal:9093
      kafka_broker_custom_listeners:
        client_listener:
          hostname: ec2-34-209-19-18.us-west-2.compute.amazonaws.com
    ip-172-31-43-15.us-west-2.compute.internal:
      kafka_broker_custom_properties:
        listeners: BROKER://<IP_ADDRESS>:9091,INTERNAL://localhost:9092,CLIENT://ip-172-31-43-15.us-west-2.compute.internal:9093
      kafka_broker_custom_listeners:
        client_listener:
          hostname: ec2-34-209-19-19.us-west-2.compute.amazonaws.com

So far we have had success with allowing for customization of just the advertised listener hostname: https://docs.confluent.io/ansible/current/ansible-configure.html#add-advertised-listener-hostnames
And we are using the hostname key as what to put into the advertised listener.
Per the doc you shared, this is the set up most people need:
listeners=INTERNAL://<IP_ADDRESS>:19092,EXTERNAL://<IP_ADDRESS>:9092
listener.security.protocol.map=INTERNAL:PLAINTEXT,EXTERNAL:PLAINTEXT
advertised.listeners=INTERNAL://ip-172-31-18-160.us-west-2.compute.internal:19092,EXTERNAL://ec2-54-191-84-122.us-west-2.compute.amazonaws.com:9092
inter.broker.listener.name=INTERNAL

Can you let me know what your network architecture looks like, because if you are simply on AWS maybe you can just use the hostname field.
Additionally, and this is a little hacky, all properties are customizable.


DSD-946: Helper text position

Fixes JIRA ticket DSD-946.
This PR does the following:

The PR for DSD-824 necessitated updates to the helperErrorText theme to correctly display when used with a Select element with a labelPosition of inline.

How has this been tested?

Locally, through Storybook.

Accessibility concerns or updates

For this update, I added two props for internal use to HelperErrorText – isInlined and labelWidth. I removed them from the Storybook props table. Edwin, Marty, you can let me know if there's another way you'd like me to accomplish this update.

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[x] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr974-yhtib5mecteyjojgom92uawruxwiuwx4.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6266eb748a4c5796e7da6929

Tugboat has finished building the preview for this pull request!
Link:

https://pr974-yhtib5mecteyjojgom92uawruxwiuwx4.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6266eb748a4c5796e7da6929

Tugboat has finished building the preview for this pull request!
Link:

https://pr974-yhtib5mecteyjojgom92uawruxwiuwx4.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6266eb748a4c5796e7da6929

The changelog should be updated. Should this go into the next 0.27.0 release or wait until 0.28.0, @bigfishdesign13 ?
Once we decide on the version, update the version for the Select component in its Storybook version table.

@EdwinGuzman and @oliviawongnyc,
If this update is ready to go - outside of the minor CHANGELOG and Latest Version number changes - then lets get it into 0.27.0.  Those final changes should be quick.

Tugboat has finished building the preview for this pull request!
Link:

https://pr974-yhtib5mecteyjojgom92uawruxwiuwx4.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6266eb748a4c5796e7da6929


💥 [DevOps] Production has Register enabled

💥 DevOps ticket

Production has Register enabled - as our register process is not complete yet we need to disable it on production

I have disabled register on production.


build: Add CMake-based build system (1 of N)

This is a first PR into a staging branch as suggested in https://github.com/bitcoin/bitcoin/pull/27060#issuecomment-1431798320.
This PR:

Establishes the minimum required CMake version. As it looks non-productive to support Ubuntu Bionic as a build platform, version 3.13 has been chosen.

Creates a bitcoin-config.h header in the build tree.

Notes for reviewers
To configure a build system, one can run in their local repo root:

on Linux / *BSD / macOS:

cmake -S . -B  build

on Windows:

cmake -G "Visual Studio 17 2022" -A x64 -S . -B build

To re-configure, it is recommended to use the clean build tree, for example:
rm -rf build

For now, the only artifact we explicitly create in the build tree is a bitcoin-config.h header:
cat build/src/config/bitcoin-config.h

Picking up from review in https://github.com/bitcoin/bitcoin/pull/27060
This is a good starting point, but isn't really meaningfully testable because it doesn't do anything. So it's not possible to see realistically what use would look like.
Would it be possible to add the simplest build target, that way we can attempt to build something and see what's intended to work at this stage? For ex, it'd be nice (as a reviewer) to be able to conclude either "Hey, neat, cross-compiling just works at this point" or "no cross-compiling, I'll look for that in a latter PR". But as-is I can't really test much so I can't draw many conclusions.
FWIW, I would expect the first one of these PRs to be quite large in order to illustrate the basic structure of what's coming with the rest. This one doesn't really give many clues about how the rest is to be organized.
Or alternatively, since this one already has some review, I suppose we could just merge this one as-is once it's got some ACKS, and have the next PR be the big one that brings in the structure and at least one build target. I'd be fine with that as well. @hebasto ?

ACK e7fb8230e80dfc9e79d8a09cab0bd60773ca8dac

ACK e7fb823

@theuni, I guess for more complete testing, see how things will work in the future commits and the big picture, one can look at https://github.com/bitcoin/bitcoin/pull/25797.

@vasild I understand that. But we're here because that's too big to review at once. So it makes sense to break things up into logical chunks for review. As-is, I don't think this is a reviewable logical chunk.
I was hoping for a bit more of a story... a commit series that started with building a vanilla bitcoind stub, and pr-by-pr added in more functionality and binaries and hardening. I believe that way would be most reviewable because everything comes in as-needed and can be tested.
It looks like the approach here though is to define a good bit of the boilerplate upfront before it's hooked up to anything, making it hard to actually test. I think that will lead to discoveries down the road that the boilerplate had been broken all along, perhaps even fundamentally.
I'll set aside my grumps for now and give this approach a shot, but imo it'll make thoughtful review trickier :)
Btw, @hebasto none of the above is a criticism of your work. Thanks for sticking with this :)

So, sure, ACK e7fb8230e80dfc9e79d8a09cab0bd60773ca8dac to keep things moving. But I'm hoping 2/N is less boilerplate and more skeletal :)


feat: LINE Notify

Add LINE Notify SDK.
Add comments in typedoc format for LINE Notify SDK.
Add tests for LINE Notify SDK.

@etrex LineNotify must be exported in the package:
https://github.com/Yoctol/messaging-apis/blob/master/packages/messaging-api-line/src/index.ts
https://github.com/Yoctol/messaging-apis/blob/master/packages/messaging-api-line/src/__tests__/index.spec.ts


[Enhancement] Integrate with the ESP Flasher application.

https://github.com/0xchocolate/flipperzero-esp-flasher
Figure out how to provide files for the community to flash their ESP32-CAM with the ESP Flasher Flipper Zero app.
Update documentation to reflect updates.

Not possible. Tested here:
https://github.com/CodyTolene/Flipper-Zero-Camera-Suite/pull/25/commits/6e75cfc734c7d78e8dbbf5acb90f38feb2b8f0bb


Allow an organization to defined its own governance zones and governance classification levels

In area 4 there are places where there is an enum for the governance domain and an enum for the level of a governance classification.  These are the current models:

The enums provide meaningful defaults to help organizations that are setting up governance for the first time.  What should an organization do if they want to have their own list of governance domains and classification levels?
The purpose of the issue is to modify the types (and supporting OMASs/security services) to allow for both use of the enums and the ability for an organization to add their own.
We had half of this idea implemented for the GovernanceConfidentiallyClassification in that it took an integer which indirectly referred to a level defined in the GovernanceConfidentialityLevel.

The proposal is to add an integer to the entities that use the GovernanceDomain, CriticalityLevel, RetentionBasis, ConfidenceLevel enums.  Also reinstate the ConfidentialityLevel enum and add it back into the GovernanceConfidentialityClassification.
The new types look like this.  Notice there are classifications for Collection from Area 1 to be able to manage these levels as a set of values.

Notice also that the enums all have "OTHER" options to mean that the values are defined in the domain/classification levels.
The integer value is used by preference, but if it is 0 then the enum value is checked.  If the Enum value is unspecified, null or set to "OTHER" then the integer value of 0 is believed - otherwise the ordinal from the enum is used.
The common services will set up the integer value from the enum ordinal whenever the enum is in use - however, not all processing may do that which is why both values still need to be checked when used.
As part of this change, the OpenMetadataSecurity module now passes the governance classifications on the Asset object.
The level will be passes as an integer.  It is called from the common services which will pass the enum ordianal if it is in use (using hte same logic as described above).
The OCF connected asset services will also pass the level value as an integer.  There is an enum defined that matches the open metadta type enum to allow lookup of the symbolic name and description if the org is using the enum values.
OMASs that set up and use these values - eg Governance Program OMAS, Asset Owner OMAS, Subject Area OMAS, ... - should follow a similar pattern.

This looks more flexible - but I have a nagging concern about maintenance of consistency if an organisation were to start out with the pre-defined enums and then replace with their own; it seems it would be an almighty task to ensure that consistency is maintained as sets of values are switched. Or am I missing something?

How would you do it?
My view is that data migration is a problem if they change their classification level definitions after a time whether they use the enums or not.  Providing the enums does not make it more or less of an issue.  Whichever case, it would make sense to use different level identifiers for their new values which means it makes it possible to detect an unmigrated value.

Added in #3707


Fix error applying plan when enable_kubectl is set to false

If enable_kubectl = false terraform will fail with:
Error: Error applying plan:

1 error(s) occurred:

* module.eks.module.cluster.null_resource.kubectl: 1 error(s) occurred:

* Error running command '      KUBECONFIG=~/.kube/config:./kubeconfig-eks-test-cluster kubectl config view --flatten > ./kubeconfig_merged \
      && mv ./kubeconfig_merged ~/.kube/config \
      && kubectl config use-context eks-eks-test
    ': exit status 1. Output: mv: cannot move './kubeconfig_merged' to '/home/user/.kube/config': No such file or directory

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

@eana isn't it the problem here that there is no ~/.kube directory?

Ah never mind I see that it's the aws_auth resource...


Getting 403 Forbidden Response for very large requessts on previewnet

Description
When we try to run contract/calls that have a very large payload against previewnet mirror node, we are getting the following error:
<!doctype html>
<meta charset="utf-8">
<meta name=viewport content="width=device-width, initial-scale=1">
<title>403</title>403 Forbidden

This is not happening on testnet or mainnet.
Steps to reproduce
Curl request.txt
Additional context
No response
Hedera network
previewnet
Version
0.105.0-rc2
Operating system
None

This issue should be part of hedera-mirror-node (not hedera-mirror-node-explorer).

I already opened up over, there. my mistake!


RedisSyncClient

In RedisSyncClient::connect, line 44, pimpl->processMessage(); causes exception throwing after any call of command(). Probably it should be removed.

You are right. This call must be removed.


[Web] "Module is not defined"

Filament web v1.7.0
ReferenceError: Module is not defined
filament.js:638

ReferenceError: Module is not defined
filament.js:654

I'm completely new to WASM and Filament, but i figured, that line 6 in filament.js would be the wasm-loader, but minified. Looking into the end of that line, it seems like it returns Filament rather than Module - looking a bit into emscripten, i was able to figure out that changing "Module" to "Filament" on line 638 and 654, would resolve the issue, and i was then able to load the sample succesfully with no erros in console! 🤠 ✅
Tried first with the original file from //unpkg as suggested by the tutorial - later downloaded the web version from releases v1.7.0 so i could change it.
Being new to Filament, and wanting to set up a production environment, i am worried if i'm doing something wrong, or if this is simply a bug. Please let me know 🙏
To Reproduce
Follow the guide on https://google.github.io/filament/webgl/tutorial_redball.html
Expected behavior
Expected to load redball.html demo with no errors in console.
Screenshots

OS: macOS Catalina 10.15.2
GPU: Intel Iris Pro 1536 MB / Razor Core X EGPU AMD Radeon RX Vega 56
Backend:  WebGL 2.0 / WASM

Thank you for this amazing engine!

After changing Module to Filament on line 638 and 654:

Thanks for the bug report, I'll see if I can repro.  The live demos work right now, and I recently updated them.  However they use a checked-in wasm file rather than unpkg.  I will change that, it will help catch issues.

This was fixed in https://github.com/google/filament/commit/242e8d1b567bef920f6535fea393f44ed28a4de5#diff-5f50d59dee9fdfd4b554f60e760a525d

Amazing work, thank you for maintaining Filament 💯


Set the resetForm call as an element attribute

What would you like to be added:
Set if the form is reset after submitting with a tag attribute as in this example:
        <Form onSubmit={this.handleUpdate} resetForm>
          <FormInput type="hidden" name="id" value={item.id} />
          <FormInput type="text" name="text" placeholder={item.text} />
          <FormInput type="text" name="type" placeholder={item.type} />
          <FormInput type="text" name="value" placeholder={item.value} />
          <FormInput type="text" name="duration" placeholder={item.duration} />
          <button type="submit" className="teal-btn">
            Update
          </button>
        </Form>

This could be done by checking if the resetForm prop is present, it can also be used to handle issue #67 if that change is implemented by passing the props data to specify what time of reset is done.
Why is this needed:
It may be better semantic wise and you may need to reset one form but not another while using the same submit method in both.
Is your enhancement request related to a problem? Please describe.
No.

@MorenoMdz, I don't really get what's your use case here. It seems like you want to use one submit function for more than one <Form>, is this it?
If this is the case, I don't think that it's healthy to do that, things can get messy real quick. Either way, if you really need/want to do that, you could simply make a function that handles your submits and gets passed an argument to identify which form it is, then you can filter it inside your function.
Also, I don't think that passing a resetForm prop is necessary on <Form>, since we already provide the following syntax:
function handleSubmit(data, { resetForm }) {
  // clear form data
  resetForm();
}

<Form onSubmit={handleSubmit}>
  <Input name="username" />
</Form>

Yes, the idea is in cases, yet rare, where you want to have a single submit method, it may be another way to specify that a form must be reset after submission. Also, it is semantically more explicit to have the reset call in the form declaration that in the JS code.
The idea is to have the form check if a resetForm prop is present and if it has any specific reset data to follow (which fields to reset to default values, which fields to not reset at all etc). Also, the `defaultValues' option is set in the form tag but the reset is set after in the submit, both could use the same configuration design, as a prop.

@MorenoMdz I don't agree, i think resetForm by it's name is a function, not an attribute. We are adding more functionality to resetForm (as you can see here #67) and bringing it as an attribute will loose all of it flexibility.

While I understand the naming as a verb is more suit for a function, names can be changed of course, it should not lose flexibility as in the same way we pass an object to specify the initial values an object could also be passed to tell the form how it should handle the reset.
Either way, I feel the proposals from #67 have priority. Thanks.

I will close this one, for now, I may bring it later in the future as and if more use cases appear.
"Keep your minds open to only then make something that's truly new."


Refine sentence on AI usage

The wording
automate complex tasks through Artificial Intelligence and Machine Learning approaches

is not entirely correct. We should come up with a more technically correct wording.
Suggestion:
leverage new self-adapting approaches through Machine Learning

@jpthiele What do you think?


fix(scale): redirect on success

https://aptible.slack.com/archives/C05CMUW3LHX/p1707421000506989

I'm not following what's causing the loader to trigger a success when we come back to the page but not when we first get there. Are we caching the loader or action somehow?

Confirmed the tests catch the regression
❯ npx vitest run src/app/test/*-scale.test.tsx

 RUN  v0.34.6 /Users/joshraker/git/aptible/app-ui

 ✓ src/app/test/database-detail-scale.test.tsx  (2 tests) 852ms
 ✓ src/app/test/app-detail-service-scale.test.tsx  (3 tests) 1039ms

 Test Files  2 passed (2)
      Tests  5 passed (5)
   Start at  13:01:32
   Duration  2.93s (transform 1.03s, setup 1.26s, collect 1.82s, tests 1.89s, environment 328ms, prepare 93ms)

❯ git checkout main src/ui/pages/*-scale.tsx
Updated 2 paths from 7bd832c

❯ npx vitest run src/app/test/*-scale.test.tsx

 RUN  v0.34.6 /Users/joshraker/git/aptible/app-ui

 ...

 Test Files  2 failed (2)
      Tests  2 failed | 3 passed (5)
   Start at  13:02:14
   Duration  3.24s (transform 1.05s, setup 1.34s, collect 1.83s, tests 2.15s, environment 341ms, prepare 97ms)


Factorio v2.0

Are you planning to port it to Factorio v2.0?
I like this mod

I tried to raise this mod to 2.0 (I can't do without it anymore) But there is a strange bug:
Error while running event QuickbarTemplates::on_init()
Unknown style quick_bar_window_frame
stack traceback:
	[C]: in function 'add'
	__QuickbarTemplates__/control.lua:3: in function 'create_gui'
	__QuickbarTemplates__/control.lua:25: in function 'setup_player'
	__QuickbarTemplates__/control.lua:156: in function <__QuickbarTemplates__/control.lua:153>

According to factorio.data (github.com/wube/factorio-data.git) there is the style quick_bar_window_frame. But why is it not found?

try "quick_bar_slot_window_frame"

Used "slot_window_frame" now. This seems to be the new name for the old style.

Done, sorry for the wait!


Make the lerna lib build run in parallel to improve speed

Referring to this particular part of the build lib process: https://github.com/tablecheck/tablecheck-react-system/blob/bee6ff77f71c1b3bea9150191502f36240da3b1c/packages/scripts/scripts/build-lib.js#L38-L44
2 things that would need to be fixed;

references needs to be a dependency graph, so we don't try build one package before it's dependencies are all built.
The logTaskEnd and logTaskStart would need to handle this properly or the log output would end up getting out of order and messed up.

NX does this better so we won't do this anymore


Only returns one column from Db table for MSSQL select query

Hi There, I have a simple knex query and when i run the test with  mock-knex i am only getting one table field information instead of all fields where as when i run the knex mssql query same code against actual MSSQL Db it returns all table fields. Below attach is the sample query.
 knex
        .from(tableName)
        .where("TEST", "TEST")
        .select()
        .then((objInstance)=>{
           return objInstance
        })

Sorry i am closing this issue i have found the solution now.
this is what i have to add to get the desired result
tracker.on("query", (query) => {
      if (query.method === "insert") {
        query.response([{ fileName: "filedValue" }]);
      }
    });


Support for smol runtime [wip]

Hi, I made a first pass at supporting the smol runtime.
Although it basically works, it still needs cleanup and testing, so I wanted to check and see if you're interested in supporting smol, and if this implementation is in the right direction.
Note: there is no smol::test attr, could see if smol_potat will add it.

What's the advantage here over async-std which is now a wrapper over smol as I understand it? I'm not opposed to supporting smol directly but I don't think that's possible (you've pulled in some other crates to help as well).

It's hard to say that either async-std or smol have an advantage; they expose different APIs, and I happen to like smol's API and minimalist philosophy.
I'm not sure what you mean by not being able to support smol directly? Do you mean without other dependencies?
In terms of deps, unless I made a mistake I think I only pulled in pin_project_lite, perhaps this can be removed.
Just also want to say that I understand the burden of maintenance from adding another runtime, so i don't want to push this on you if it won't be valuable. Thanks for developing sqlx, it's worked great for me so far.

Sorry for not being clear. My point is as async-std is a wrapper around smol, is there any point to provide both runtimes? If we just drop direct async-std support is anyone affected by that change?

So I've asked for some clarification in the smol discord and did some experiments.
Since async-std spins up a smol runtime automatically, a library that supports smol can be run within an async-std context. I tested by running this smol-only branch of sqlx in an async-std app, and it worked. I would also expect all the async-std tests to work if the feature was switched to runtime-smol.
Running an async-std library within a smol app should also work. At the moment, async-std would spawn a few extra threads of smol runtime. For most use cases, I don't think this is a critical issue, but it would be a bit disappointing as I assume users of smol want more control over the runtime.
There may be other considerations on the interaction between async-std and smol that I'm not aware of. For example, the switch to smol led to this issue (looks like fix is already in): https://github.com/async-rs/async-std/issues/798 . Depending on the direction you want to take, we could ask for more clarification from smol and async-std maintainers.

I updated the PR to just use smol under the hood of the runtime-async-std feature. This way, you can just choose between using smol or the current async-std route, since it doesn't make sense to support both.

Any thoughts on this @dignifiedquire ?
I'm leaning towards dropping direct usage of async-std as it seems to have the most upside ( people with just smol can use SQLx natively and people with async-std can use SQLx without much of a difference ).

I would suggest an alternative path, which I think could bring the best of both worlds. By default use async-std with default features disabled (once 1.6.1 is realeased, there is a bug atm), which will not include the runtime and start it, but it will give you access to the building blocks, allowing you to avoid implementing the shims that are in this PR.
This would not give you block_on, but I would strongly suggest not using smol::run for this, as that brings you into issues if things are already using other wrappers, but use smol::block_on.

it is important to also note that currently sqlx does not actually work with smol, only<EMAIL_ADDRESS>:(
ref https://github.com/stjepang/smol/issues/136

Thanks @dignifiedquire. That sounds fine to me, it's true that the shim is just selected snippets of async-std anyways.
Can you just say a bit more about This would not give you block_on..., I'm not sure about the context? Would that be for implementing  smol compatibility in sqlx, or for end-users of slqx?

By default use async-std with default features disabled (once 1.6.1 is realeased, there is a bug atm), which will not include the runtime and start it, but it will give you access to the building blocks, allowing you to avoid implementing the shims that are in this PR.

That's an awesome idea. I think this is definitely the way to go.

However, we use block_on in a proc-macro which means we will bring in the default async-std features until cargo has a stable release of the new feature resolver.
This is still a great thing to do though as it enables nightly rust users to opt-out of the default features.

@hwchen Thank you so much for driving this. I'm going to close this PR for now as the intended direction is to simply remove default features from async-std in core (once that bug in smol is fixed).

@mehcode thanks for considering this! And @dignifiedquire thanks for the feedback!


feat(messages): add new message endpoints support

Added new GET /messages/:id endpoint
Added new GET /messages/:id/content endpoint
Added new GET /messages/:id/events endpoint
Added new GET /messages/:id/activities endpoint
Added new GET /users/:id/messages endpoint
Added new GET /objects/:collection/:id/messages endpoint

@thomaswhyyou addressed all comments!


Fix arp addr for vxlan

Coverage decreased (-0.03%) to 75.004% when pulling 55bf61dc9b2f9c547f18d2b5f9066f74c4958e45 on lukasmacko:master into 653adbf48e09e19aa2ace16bf1f191380e8ade8a on contiv:master.


[Simulation] Save pov_driving_pattern data to internal variable

prevents internal file editing in production
closes #19

misc stuff:

add pyyaml to requirements
handle python vs python3 keyword for differing paths


'Enter' doesn't work to zoom in first result by code navigating.

Issue Type: Function Issue
environment

VSCode Version: 1.38.1
OS Version: macOS Mojave 10.14.6 (18G95)

content
I usually use vscode for developing or analyzing c++ code. I have found an inconvenient problem when I analyzed c++ codes. When I use 'Goto Definition' or 'Peek Definition' for navigating code, This problem happens when I zoom in the first result out of more than two results. I click 'Enter' to watch a mini screen into total screen about the first result. But It doesn't work. If you go to a different result and come back and press enter, then It works. I wish this problem is fixed. :)
example
First, you click 'Go to Definition' about any function.

Second, you click 'Enter' about first result.

Result that I expected

But, It doesn't work.

Potential duplicate of https://github.com/microsoft/vscode/issues/81200

/needsMoreInfo
Does this also happen with VS Code Insiders? Download: https://code.visualstudio.com/insiders/

@chrmarti
Thanks! This works well in insider.
I would expect vscode team to apply this patch next version.
Thanks for helping me!
@vscodebot
okay. When I post issue next time, I will follow the guidelines.
Thanks for guiding me!


Add option to unpack rootfs

This can be used to use the build image in a subsequent task without uploading it to a registry.
Fixes #24

Bummer, I can't build an image for this because the base image (r.j3ss.co/img) is returning 502 errors. Might be time to just build our own image based on alpine:3.9 or ubuntu or something.

@vito Yeah I noticed when testing my changes earlier today. I have opened an issue upstream: https://github.com/genuinetools/img/issues/241 Lets see  if this takes longer then a day to fix. Then I would say its time for a custom image

In the meantime I've pushed an alpine-based image to concourse/builder-task:alpine-based - source is here: https://github.com/concourse/builder-task/tree/alpine-based

@vito According to https://github.com/genuinetools/img/issues/192 the the images are also published on docker hub to jess/img. Do you feel like updating the Dockerfile or do you think sticking to the alpine based version is the way to go?

@databus23 Oh, perfect. I'll just switch to that. There's quite a bit of code duplicated from their Dockerfile in the alpine fork which I'd rather not maintain.

New image is now pushed to concourse/builder-task:latest.

@vito right after trying this out I figured it would be better to have UNPACK_ROOTFS be a directory where it should be unpacked to (instead of a boolean flag). That way you can have the oci tarball and the rootfs in different outputs and  avoid streaming the tarball to the task that just wants to run the image and stream the rootfs to a subsequent  put. Wdyt?

@databus23 Makes sense!
Alternatively it could work similar to how caching is handled: if there is an output named 'rootfs' it will place it there.
Either option is fine with me. 👍


How to enable floating signature window when typing parameter

Like this

Sorry. The LSP spec's signature help feature is out of scope.
It should be supported by other LSP-related plugins.

nvim-compe is a completion framework with some "complimentary" integrations with lsp like info/doc, browse window c-f/c-d, snippets, if you like to have this you can do it yourself, it isn't that hard:
nn <c-s> :lua vim.lsp.buf.signature_help()<cr>
autocmd CursorHoldI * call v:lua.vim.lsp.buf.signature_help()

or use lspsaga.nvim like I do

cc @hrsh7th lspsaga has an awesome highlight with dark background enabled by border, it may be worth looking into, it looks amazing

@tami5 I also use lspsaga.nvim. Can you share your signature_help config of lspsaga to show floating window above function name like this.
This is mine: when call lua require('lspsaga.signaturehelp').signature_help()

@vpeopleonatank oh I think this limited by the amount of text the server returns, here a custom function with no docs.
@glepnir do you think its best to have a specific/limit size of help signature window to serve as "signature help" and not another way to hover? I believe signature help should do its purpose and not provide a huge lines of documentation. maybe an option idk, what do you see?

should be add limit，add it tomorrow

In case anyone want this feature. I ported completion-nvim signature while typing parameter feature to this plugin:
https://github.com/ray-x/lsp_signature.nvim


Allow some query predicate operators to apply to final capture

The problem
The following query doesn't work:
(
  (aaa) @bbb.start
  (ccc) @bbb.end
  (#insertion-delimiter! @bbb ", ")
)

because at the point that insertion-delimiter! query predicate operator is run, the @bbb.start and @bbb.end captures haven't yet been merged into @bbb, so it complains that the @bbb capture doesn't exist.  Instead, you have to do
(
  (aaa) @bbb.start
  (ccc) @bbb.end
  (#insertion-delimiter! @bbb.start ", ")
)

(or @bbb.end), which is a bit awkward, and annoying if you refactor your pattern to go from @bbb to @bbb.start or vice-versa.
The solution
Instead, we should allow referring to the final node for certain captures.
I don't think we want this for all captures, though, because for example
(
  (aaa
    (ccc) @bbb.end
  ) @bbb.start.startOf
  (#not-parent-type! @bbb.start.startOf ddd)
)

In this case, we want to refer to one side of the @bbb range constructor specifically.  Although arguably for this case we could add a new @dummy node
(
  (aaa
    (ccc) @bbb.end
  ) @bbb.start.startOf @dummy
  (#not-parent-type! @dummy ddd)
)

which might make things clearer.
Another problem is that you can't really refer to the capture's parse-tree node if it's the result of constructing a range, because then there are actually two nodes: start and end.
One possible solution to all of the above:

You can always refer to the full name @bbb.start.startOf or to the name without .startOf / .endOf.  I don't think there's ever ambiguity there.  The only potential problem with omitting the .startOf is that I'm not sure we will have updated the range yet, so might be a bit ambiguous what you'd expect the query predicate operator to see 🤔.  I guess we could do the same thing I'm proposing in the next bullet, and just throw an error if you access range for now
If you refer to @bbb and we only find @bbb.start and/or @bbb.end, then we construct a dummy capture object that throws an exception if the query predicate operator tries to access range or node.  That will be fine for insertion-delimiter! and allow-multiple!, which are the only two use cases I've run into.  I guess the easiest thing is for the dummy object to mirror your property writes to one of @bbb.start or @bbb.end, as those get merged in the end

It would be nice if it were strongly typed instead of raising an exception, but that might be extra credit

@pokey I do wonder how we would even implement this. As far as I can tell the error message about bad capture name is thrown from Tree sitter itself and not our code.
This is the statement that's failing
https://github.com/cursorless-dev/cursorless/blob/bc9cf96a294bce361cbf024704e113d1172772ef/packages/cursorless-engine/src/languages/LanguageDefinition.ts#L49-L51

1 sounds easiest

draft https://github.com/cursorless-dev/cursorless/pull/2080


Changing case in template breaks update (e.g. "Populate" -> "populate")

Describe the problem
The update process does not work as expected (files aren't merged automatically) when case changes in the template.
In the copier template referenced below, I introduce a change in v2 that can be applied as expected. However, the case-change in v3 cannot be applied as expected.
Template
https://github.com/davidbrownell/copier-TemplateTest3
https://github.com/davidbrownell/copier-TemplateTest3Output
To Reproduce

[Works as expected] copier copy https://github.com/davidbrownell/copier-TemplateTest3 --vcs-ref v1 result is here
[Works as expected] copier update . --skip-answered --vcs-ref v2 result is here
[Does not work as expected] copier update . --skip-answered --vcs-ref v3

Note that the update results in a diff (in the screenshot section below) that is not automatically merged, and I haven't found a tool yet that is able to handle it correctly.
In this small example, the merge is fairly easy to resolve manually. The merge is much more complex in the real code that prompted this investigation.
Logs
No response
Expected behavior
The 3-way merge should work as it did when applying v2 of the template.
Screenshots/screencasts/logs
git diff:

Operating system
Windows
Operating system distribution and version
Windows 11
Copier version
9.3.1
Python version
3.12.4
Installation method
pip+pypi
Additional context
No response

Thanks for reporting this problem, @davidbrownell! :pray:
I've not been able to reproduce the problem on Ubuntu 22.04, Copier applies the update correctly for me. Could you share your Git version?

Thanks for taking a look, @sisp. I am using 2.41.0.windows.1. I will upgrade and let you know if I still see the issue.

It worked! Upgrading to git version 2.46.0.windows.1 seems to resolve the issue. Thanks so much for the help!


chore: Remove erroneous package-lock.json

SUMMARY
Removes erroneous package-lock.json at top of repo added in recent PR.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Note that this is mainly a test of a new ticketing system's Github integration on Preset's end, but still a valid cleanup task.

Codecov Report

Merging #11108 into master will decrease coverage by 1.39%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11108      +/-   ##
==========================================
- Coverage   61.54%   60.14%   -1.40%
==========================================
  Files         817      384     -433
  Lines       38706    24294   -14412
  Branches     3650        0    -3650
==========================================
- Hits        23821    14612    -9209
+ Misses      14705     9682    -5023
+ Partials      180        0     -180

Flag
Coverage Δ

#javascript
?

#python
60.14% <ø> (-1.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
31.91% <0.00%> (-59.58%)
:arrow_down:

superset/db_engine_specs/hive.py
53.90% <0.00%> (-30.08%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/db_engine_specs/presto.py
70.60% <0.00%> (-11.36%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/api.py
81.38% <0.00%> (-7.98%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

... and 452 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 6633409...e353446. Read the comment docs.


Remove maxLength field

Can you tell me why do you want to remove the max_length field? Otherwise, I would have to close your pull request without merging it.

@marcaureln I think I may have created this PR by mistake. This was only supposed to be in our own fork.
The reason to remove it is that some lengths are incorrect so that was preventing the user from entering full number (like with Argentinian phones, PR merged recently).
A better solution would be to enable / disable this field.


feature request: optional vpc parameters in c7n-org's configuration file

What: provide vpc configuration (subnets and security groups) at the config level instead of the policy level
Where: c7n-org's configuration file
Why: to further abstract policy data, resulting in fewer redundant lines of code
Unless I'm misunderstanding the status quo, I need to specify subnets and sgs in each policy file. This means less policy files or more redundant code. Our preference is to separate policies into multiple files, thus we are repeating the vpc config in each file. Additionally, we need to maintain identical policy files across regions and accounts with the only delta being the vpc config.
This might be a nice approach:
[ accounts.yml ]
accounts:
- account_id: 'XXXXXXXXXXXX'
  name: myaccount-east
  role: arn:aws:iam::XXXXXXXXXXXX:role/custodian
  regions:
  - us-east-1
  vpc:
    security_groups:
      - sg1
      - sg2
    subnets:
      - subnet1
      - subnet2

In fact, might we ultimately imagine the account name(s) as an option in the policy block, gradually merging org functionality into the base?
[ policy.yml ]
policies:
- name: config_ec2_terminate-invalid-tags
  resource: ec2
  mode:
    type: config-rule
    timeout: 180
  accounts:
    - myaccount-east
    - myaccount-west

You can use variable interpolation (account_id and region) and a separate variables file to use one set of policies for multiple accounts:
vars:
  accounts-metadata: &accounts-metadata s3://some-bucket/accounts-metadata.json # can also be a local file or url

policies:
  - name: ec2-invalid-vpc
    description: filters in ec2 instances that are operating in a non-whitelisted vpc
    resource: ec2
    filters:
      - type: value
        key: vpc
        value_from:
          url: *accounts-metadata
          format: json
          expr: metadata."{account_id}"."{region}".vpc_id
        op: ne

accounts-metadata.json:
{
  "metadata": {
    "123123123123" : {
      "us-east-1": {
        "vpc_id": "vpc-123123123"
        }
      }
  }
}

org config file isn't a really good place for modeling an accounts resources its meant to be a configuration file for targeting policy execution not policy configuration, as sonny mentions the best way to do this is via values_from syntax that can reference the account specific resources/values of interest within any given filter.


Removed useless checks

Removed useless checks

@DamirAinullin,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Fix [crates] license badge

License data was moved to crate versions in rust-lang/crates.io#803. Closes #1059.

Hi! Thanks for fixing this. Would love to get this merged. Could you add a test?

@paulmelnikow Added a couple tests; let me know if I should make any changes!

@paulmelnikow Hmm, I rebased on top of master, but it looks like the build is still failing. 😕

That 403 Forbidden error was due to #979, so I restarted the build.
After that, we've got real failures. Those github failures are still there, which need investigation, plus there's a codetally failure, which I reported at #1069. Clearly those are unrelated to this change.

Those github tests are passing on my machine. So the most likely explanation is that they are also related to #979, in a different manifestation, where the rate limit runs out, affecting some of the requests in the middle of the suite, and not others. It's a little odd that some github tests pass afterward, though some of them are mocked, and others might not be subject to rate limits.


Adding MySQL broker to service catalog

We have an example here https://github.com/hchenxa/daily_work/tree/master/kubernetes/service-catalog and want to contribute to service catalog.
Can we put all the works related to MySQL under https://github.com/kubernetes-incubator/service-catalog/tree/master/contrib ?

/cc @duglin @hchenxa @MHBauer

I also post a question here and want to get some comments for where to put some 3rd party brokers https://groups.google.com/forum/#!topic/kubernetes-sig-service-catalog/RbChgi5hOyc

Where's the source code of your MySQL broker now?

@gyliu513 it's awesome to see growing interest in creating brokers! That said, we don't intend for broker code to be kept in this repository. The one broker you see currently under contrib exists only to facilitate tests and walkthrough, so it's deliberately tracked along with service catalog code. In all other cases, brokers should be kept in their own repositories.

I don't expect any disagreement from other maintainers on this subject, so I am going to close this. @gyliu513 please still feel free to re-open this or comment further if you feel this is inadequately addressed. Thanks!

@krancour I post a question here https://groups.google.com/forum/#!topic/kubernetes-sig-service-catalog/RbChgi5hOyc .
It is difficult to use service catalog without enough examples and service brokers. One example is helm, the helm is not only maintaining a helm repo, but also a chart repo to host some charts for helm so that the enduser can use those charts easily.
But for service catalog, there is no such repo and also not enough examples for how to use service catalog, without examples and service brokers, it is difficult for people to put service catalog into production. comments?

There are many brokers out there "in the wild." They've been written for use with Cloud Foundry, but they will work just fine with the k8s service catalog as well. You may wish to adapt such brokers for use in k8s by authoring Helm charts for them and submitting those as PRs to the kubernetes/charts repo.

If you're asking whether the k8s service broker intends to host its own Helm charts repository... that's not at all on our radar.

So my question is with service catalog, how can I integrate with local oracle, MySQL, Hadoop etc? Where can I get some reference and help to integrate service catalog with external services? There is only one ups example and I think it is not enough.

First thing's first. Do brokers exist for all of those things? If so, are they already deployable to k8s? i.e. Are Helm charts available?

Yes, I already have a MySQL broker here and also some test steps, I can covert the test steps to charts if needed. Comments?
Basically, I want to put all of the source code for MySQL here and create a chart for MySQL here.
I think the final goal for service catalog should put all charts and service brokers to a separate repo like where helm host its charts.

I will say again, this repo is not the right place to put broker source and Helm charts. Broker source code belongs in its own repo. The charts can be contributed to kubernetes/charts. I'm not sure what isn't clear.


using dynamic country input

Hello,
What do you mean by:

Do not add gem to assets section if you want to use flag_icon rails helper.

Does that mean not to add:
@import "flag-icon";
to application.scss?
Also, how do I add dynamic content to the helper? I have an address model which has a country attribute. It stores the "BY".
I'm trying to pass that to the helper:

<%= flag_icon(Address.last.country) %>

        <%= flag_icon(Address.last.country.to_sym) %>

Neither of those attempts work. Can I use flags dynamically?

@MincePie use downcase
<%= flag_icon(Address.last.country.downcase.to_sym) %>

@MincePie  Sorry for delay with answer 😞

Do not add gem to assets section if you want to use flag_icon rails helper.

means do not adding this gem into group :assets into your Gemfile. By the way, this group is not supported beginning from Rails 4 😄
@import "flag-icon"; is required, because all styles contain all rules to display flags in SVG.
As for using flag_icon helper method, it expects downcased ISO 3166-1 alpha-2 country code as a first argument. Converting to symbol is not required, because this argument will be casted to string whatever.
Hope, this answer will be helpful 😃


Time picker inner container color can't be changed

I tried out changing all the colors of the time picker to a dark theme, but found that the color of the switch and dial container can't be accessed. ContainerColor only changes the outer container.

To clarify i have used all the accessible colors.

Hi, thanks for the input! The inner container background color is probably not changing because of TimePicker's root Composable which is Surface (which will be fixed, together with further API clarification). Could you please try changing your MaterialTheme.colorScheme.surface color to see if it changes?
As for the switch, I might not be entirely sure what you are referring to.
Also, if applicable here, for now, you could probably try changing the colors in your MaterialTheme declaration, the TimePickerDialog might then behave correctly.


Sync New MongoDB uri with parse.com Dashboard

Hello,
I switched from sandbox in mongolab to dedicated cluster. So the database uri has been changed. I changed the uri in the parse server side and it is working. However, the parse.com dashboard is still showing the previous dashboard of the previous database uri. Is it possible to sync it with the new databse uri? Or was it a one time option?

When finalised that's it, no going back.

My guess is this is probably some caching issue. Maybe @drew-gross knows more

No, dashboard.parse.com doesn't do any caching, it reads from api server every time.
You can change your mongo uri from the dashboard, which will cause all reads and writes to immediately start using that new URI. I recommend trying this with a dev app before doing it with your prod app.


Extract: add ability to replace calls to nano with generated classnames

I'm very excited by this project; it ticks a lot of the needs we have for a CSS-in-JS solution.
One thing would make it fit exactly: the ability to not have a runtime at all.
I know that goes against some of the CSS-in-JS "rules".
The way I would see it would be that I could use the sheet interface to add classes to my components. Then I could run an extract that would generate the CSS file. This would also replace the references to the classes with the actual class names.
It could be like this: It would replace the calls to nano with the results
Input:
const cssMap = {
    input: {
        border: '1px solid grey',
    },
    button: {
        border: '1px solid red',
        color: 'red',
    }
};
const styles = sheet(cssMap);

<input className={styles.input}>
<button className={styles.button}>Click me!</button>

And output:
const styles = {
	input: 'class-b-1px-solid-grey',
	button: 'class-b-1-px-solid-grey-c-red',
};

<input className={styles.input}>
<button className={styles.button}>Click me!</button>

This way, the actual calls to nano would be removed and then pruned. The size of my app wouldn't be any bigger, but it would have the advantages of CSS-in-JS except for dynamic classes/styles, which is a known limitation and one which I accept.

You could do it now by placing your style into a separate file, like app.styles.js:
export const styles = {
    input: {
        border: '1px solid grey',
    },
    button: {
        border: '1px solid red',
        color: 'red',
    }
};

And then when you evaluate those styles, you could generate another file with only class names:
const styles = require('./app.styles.js').styles;
fs.writeFileSync('app.classes.js`, `export const classes = ${JSON.stringify(styles)};`);

And in your app you include .classes.js file which only has classes.
import {classes} from './app.classes.js';

Alternatively, you could write a Webpack loader that does it for you.

Putting them in a separate file and doing it that way seems viable.
I'm not smart enough to write a webpack loader (we use Rollup, but same thing), but maybe I'll try to figure out how to do it.
Thanks for your input!

I have a super hacky basic plugin that does exactly what I want: https://bitbucket.org/TheBosZ/rollup-plugin-nano-css
Thanks for your great project, I can't wait to start using it!


How do I use the reporting API in real life?

Issue: I'm updating a gem that reports on scenario success/fail plus scenario source to an external reporting tool via a REST api. It doesn't work in Cucumber 2.0 so I'm trying to learn how to do it in the Cuke 2.0 world and can't find enough documentation to get started.
I've read through the example of using a reporting class and getting it to work but I'm mystified by two things;-

How do I plug in a reporting class into real world Cucumber? I can't believe I'd have to write my own runner and plug the reporting class into that. How do I register my reporting class with real world Cucumber in the features/support/env.rb file ?
Having an api to send messages to a report class that responds to certain methods is cool, but Cucumber::Formatter::Html does loads more. Does Cucumber::Formatter::Html behave as a report class, or is it a special case that has a different api?

Is there any documentation or online email conversation I can be pointed to so I can learn how to catch the messages that happen as Cucumber runs and then send information to an external reporting tool?
Thanks
John Small

Hi John,
I'm really sorry we've not done a better job with this yet. I'm about to disappear offline for a week, but I will endeavour to write something up for you when I'm back, unless @tooky or @brasmusson would care to step in? :)

What would be great would be a blog post at http://cucumber.io/blog about this.

Ah, OK. If you can manage a tiny hint about how to register a new report generator in env.rb so I can get started then I'll take it from there and then blog about my trials and tribulations getting it to work. At the moment I can't find the way in to get started.
My problem with moving my gem up to Cuke 2.x is that the old Scenario object available in the after hook had changed quite a bit.
The old version of my gem monkey patched Scenario and ScenarioOutline to send results via REST to Testrail from Gurock Software (it's a test reporting package). But I've realised that using an after hook with a monkey patched Scenario is not the way to do it. I'm better off defining a new reporter, plugging that in and getting it to send results via REST to the reporting package.
I'll read the source and see if I can find the way in that doesn't involve creating my own runner.

Sorry if I've misunderstood, but the way to use a custom formatter is to include it on the LOAD_PATH and specify it on the command line.
e.g. http://www.relishapp.com/cucumber/cucumber/docs/extending-cucumber/custom-formatter
Does that help?

Ah, that's much better than the way I'm trying to do things.

The most extensive example of the use of the new formatter api (meaning the most data extracted from it), is probably the rewrite of the Json Formatter in cucumber/cucumber#851.

Ok, I got that working and it's been running for months now.

Glad to hear it.
On Tue, 16 Feb 2016 at 13:19, John Small<EMAIL_ADDRESS>wrote:

Closed #91 https://github.com/cucumber/cucumber-ruby-core/issues/91.
—
Reply to this email directly or view it on GitHub
https://github.com/cucumber/cucumber-ruby-core/issues/91#event-552006574
.

--
The Cucumber logo is the intellectual property of Cucumber Ltd, a limited
company registered in Scotland, number 456793.
UK Headquarters: Cucumber Ltd, Drumsyniebeg, Lochgoilhead, Cairndow,
Argyll, PA24 8AN UK.
CONFIDENTIALITY NOTICE: The information in this e-mail is confidential and
privileged; it is intended for use solely by the individual or entity named
as the recipient hereof. Disclosure, copying, distribution, or use of the
contents of this e-mail by persons other than the intended recipient is
strictly prohibited and may violate applicable laws. If you have received
this e-mail in error, please delete the original message and notify us by
email immediately. Thank you. Cucumber Ltd.


Support multiple modules

Modules can be chained and different addresses will be used for I2C to communicate with each.  Consider how to model this so that up to 8 modules can be used for a total of 128 pins.  See https://learn.adafruit.com/adafruit-mcp23017-i2c-gpio-expander/pinouts#address-pins-3113114

Library updated and new sample added


 And now I don't see the black bar anymore :/

cc @HansMuller

I fixed a similar bug recently.  I wonder if you had an old version.  Are you still able to reproduce the issue?

Not sure what version (master? alpha?) was used to build it, but happy to try again with a new build. Let's keep this open until at least the next version of the gallery is built and tested.

Unable to repro.


Title: Invisible text input in email form for subscription to the news letter

Description:
On the PetMe website, when trying to fill in the email form in the "Subscribe to our newsletter" section, users experience a problem where the text they type is not visible on the screen. Instead, the text appears to be invisible until the user selects it with their cursor. This makes it difficult for users to see what they are typing and can cause confusion.
To Reproduce
Steps to reproduce the behavior:

Go to the PetMe website: 'https://akshitagupta15june.github.io/PetMe/index.html#'
Go to the "Subscribe to our newsletter" section.
Click on the email input form to type in your email address.
Observe that the text you type does not appear on the screen.
Select the text with your cursor to see what you have typed.

Expected behavior
When typing in the email input form, the text should be visible on the screen as it is being typed, allowing users to see what they are typing and correct any mistakes.
Screenshots

So I guess this problem is not solve even after merging the referenced pull req. User is only able to see the entered email only on selecting the particular area in which the email is written.
Also there's another problem that is there is no way that user gets to know if they are subscribed to the newsletter or not. Because after clicking on the red subscribe button there's no appropriate message displayed or any sort of sign is given to know if the user is subscribed to the newsletter or not.
I am attaching the screenshots for reference.

@akshitagupta15june I can work on this issue, please assign it to me.

hey, can you assign me this issue?

I am interested to contribute


Whether there is any priviledge to add custom html content on node and accordingly output bubble?

I have following node:

When I will click on + icon, then it will add condition2 textbox and output bubble for it.
If again I click on +icon, then again it will add condition3 textbox and output bubble for it.
With + icon, textbox can be appended with javascript-jquery, not an issue.
Whether there is anything that will handle or add output bubble accordingly ?

Hello @ishpreetkaurwebner
Yes add a buble with:
editor.addNodeOutput(id)

View methods: https://github.com/jerosoler/Drawflow#methods
Although the text fields and the outputs are not related, you can relate them in your logic

Thanks @jerosoler. It is working.

Hi @jerosoler,
I am able to add bubble with solution suggested by you and able to import new dynamically created html with the help of https://github.com/jerosoler/Drawflow/issues/73.
I am facing another problem is that when I add new html, then I add bubble also and bubble is adding on same position, as shown in Fig 2,

Figure 1
This is original node which is added on drawflow during drag and drop.
Now, on click of + icon, node looks like following image

Figure 2
With the help of editor.addNodeOutput(id), I am able to add bubble, and  with https://github.com/jerosoler/Drawflow/issues/73, I am able to export dynamically created html, but problem is: all bubbles are adding at same place.
Somehow I able to resolve the bubble positions' issue with javascript/jquery, some calculations on top and left margins while adding dynamic html and my node looks perfect as shown below:

Figure 3
But, bubble positions are not exported, and when I import the whole diagram I created, it becomes same as  shown in figure 2.
Any workaround to handle bubble positions during export and import?

I would have to solve with css.
It would be the simplest and most practical.
Another option would be to use the "https://github.com/jerosoler/Drawflow#events" "import" event and execute your javascript code.

Yes @jerosoler , it would be better solution if there is workaround with css instead of I have to calculate positions of bubble with javascript.
There is no limit for adding new html and then accordingly bubbles are also getting adding up and all bubbles are getting add to same position. So, that's better if position is handled through css without knowing number of bubbles adding up.

According to what I see in figure 3.
You have 3 types of bubbles.
The one up (Input)
The one down (Output)
Those on the right (Output)
.drawflow .drawflow-node.YOU_CLASS_NODE .output {
 /* RIGHT BUBLES */
}

.drawflow .drawflow-node.YOU_CLASS_NODE .output:nth-child(1) {
  /*  DOWN BUBLE  */
}

Yes, One is up and that is input, second is at bottom and that is output. Both these bubbles are fixed. So, there is no problem for fixed css.
On right sides, there can be multiple bubbles and they are output and number of right bubbles are uncertain. So, I need css for right bubbles.

I would have to solve with css.
It would be the simplest and most practical.
Another option would be to use the "https://github.com/jerosoler/Drawflow#events" "import" event and execute your javascript code.

I was already trying with approach "first import and then apply css with javascript".
But, still I thought if you have better way to solve such issue.
I have done with above approach.

@jerosoler, I will still wait if you found css solution for handling it. Please let me know whenever you will solve the problem with easy css approach.

The only approach that I see possible is the one I have discussed above.
https://github.com/jerosoler/Drawflow/issues/149#issuecomment-813498435

Thanks @jerosoler. It is working.

@ishpreetkaurwebner im facing a similar issue can you help me out?

@iamnikhilrohan : You are facing which problem here? Here, following points were the issues:
(1) Add custom HTML in export
(2) Add output bubble along with custom HTML added
(3) Positions of output bubbles

@iamnikhilrohan  please can you help me with the code that you have done for managing the dynamic position of bubbles as in figure 3


conversion of console input to float

Please add the tutorial for converting console input while replacing all int to float.

@Aravindpvel -- thank you for your suggestion.  Is there a similar article already on docs.microsoft.com that you would like to see expanded?  Please consider these resources:

Visual Studio on Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

@Aravindpvel As a quick FYI, the Tutorial: Create a simple C# console app in Visual Studio includes an example of what you might be referring to, in its "Add decimals" section.