Error "Sendin_blue_error"

My code (cloud function) throws this err (first occurrence after 2 days). Any clue what does it mean? I will send more info when I will have it.
StatusCodeError: 500 - "{\"error\":\"sendin_blue_error\"}"
at StatusCodeError (/workspace/node_modules/request-promise-core/lib/errors.js:32)
at Request.plumbing.callback (plumbing.js:104)
at Request.RP$callback (/workspace/node_modules/request-promise-core/lib/plumbing.js:46)
at Request.self.callback (request.js:185)
at Request.emit (events.js:198)
at Request.EventEmitter.emit (domain.js:466)
at Request.<anonymous> (/workspace/node_modules/request/request.js:1154)
at Request.emit (events.js:198)
at Request.EventEmitter.emit (domain.js:466)
at IncomingMessage.<anonymous> (/workspace/node_modules/request/request.js:1076)
at Object.onceWrapper (events.js:286)
at IncomingMessage.emit (events.js:203)
at IncomingMessage.EventEmitter.emit (domain.js:466)
at endReadableNT (_stream_readable.js:1145)
at process._tickCallback (next_tick.js:63)

I use request-promise, might it be better to switch since I see it is now deprecated?
https://www.npmjs.com/package/request-promise

Well, using a different request library won’t solve this issue because you get a legitimate response from your server that something went wrong on the server. Just google for "500 http status code". But yes, if you are starting to use request-promise just now then better use another request library.

thank you for the advice; I did not realize it simply is 500 and had no clue what the message means so I put it here... one of the few requests I do to various APIs probably uses https://www.sendinblue.com/lp/smtp/ in the backend and I did not see that previously...


Mehrzad / remove reality check

There are also some references in the following files:

storageManager
appId

No need to remove them as well?

@salarhfz-fs ,
I'd checked them, it's better if we don't remove them as we set/get reality-check status from WS and we may need to have them in the future if we'll add multiplier

@salarhfz-fs , I'd checked them, it's better if we don't remove them as we set/get reality-check status from WS and we may need to have them in the future if we'll add multiplier

OK then, LGTM :+1:


'list' object has no attribute 'to'

The project has been updated, the ksampler needs two input (plus or minus), maybe it needs to run the clip model?

Don't use the default clip text encoder, there is a CogVideo Text Encoder node.
look this:  https://github.com/kijai/ComfyUI-CogVideoXWrapper/issues/19#issuecomment-2313915458


Some invalid HTML documents yield Failure("require_current_element: None")

The following document (reduced as much as possible) makes parse_html raise a failure "require_current_element: None". Note that the document is indeed invalid since xmp elements are both deprecated and should not appear inside a td element but still one should be able to perform error recovery. I'm guessing the failure exception should not leak to the client ?
<!DOCTYPE html>

<title></title>

           <xmp></xmp>

I tested it with markup 1.0.2, using the following program :
open Markup

let stream, _close = file "test.html"

let  parser =  parse_html
        ~report:(fun _ _ -> ())
        ~context:`Document stream

let _ = iter ignore (signals parser)

I haven't looked into the error in detail yet, but, indeed, exceptions should not leak to the library user, and the parser should be able to recover at least somehow from all errors.

You may be able to follow along these rules in the HTML5 spec to get an idea of what the parser is required by the spec to do (that's what I'll do when debugging). The input is quite small (thank you!), so it should be doable. If you can spot the point at which the parser diverges, that would probably be the bug.
The error makes me suspect that this is an interaction with the "adoption agency algorithm", called on by the spec in various places. It is used to reorganize the document tree in response to various misnested elements. Markup.ml creates local subtrees to "buffer" parser stream output in case those subtrees might be affected by the "adoption agency algorithm," and streams those subtrees out on its final output stream once it is sure that the subtree is safe from modification by the algorithm.

If you do try to follow the spec, and run into the "foster parenting algorithm," which is required in misnesting inside
, Markup.ml does not implement that algorithm per the conformance status. This is because the "foster parenting algorithm" can require very remote modifications to the document tree being parsed, which, in a streaming parser, means buffering a potentially huge amount of signals before emitting them — defeating the point of streaming.
As an aside, it is possible to implement the algorithm as a separate pass over the signal stream for people that need this level of conformance (at the price of buffering the document), but I don't think that's ever been done for Markup.ml.


Function to get nearest campaigns

could you update in here too?
https://github.com/dimasciput/field-campaigner/blob/1c3c0608eeeb83d8ba113ebf6d498471ee1cd661/flask_project/campaign_manager/views.py#L61

@meomancer updated

LGTM


Support exporting not just finished applicants' data

Currently /admission/export always uses the same filter: whether the application is finished:
https://github.com/EotvosCollegium/mars/blob/1c5f21b3bc9eeede160f132bfd27f0f86660b59b/app/Http/Controllers/Auth/AdmissionController.php#L216-L229
It would make sense to obey the filters set on the web interface. A pretty important use case is to export the email addresses of people with unfinished applications in order to send them a notification email prior to the deadline (there won't be an extension this year!)

We can send automatic reminders before the deadline with the PeriodicEvent's callbacks. Would we prefer that or this fix?

We can send automatic reminders [...]

That also sounds good to me, although I'd prefer if it was manually activated (so that we don't actually trigger it from the staging instance, etc.).
But being able to give the student Committee/the Secretariat a list of email addresses would be good to have regardless.

Fixed by #626


Supported video formats

It would be nice to document what is supported. .webm with VP8 apparently doesn't play.

The only video format that is guaranteed to work is .MPEG4 with H.264 video codec and AAC audio codec. Some other video formats or codecs may work but this isn't guaranteed. This is documented for bots at https://core.telegram.org/bots/api#sendvideo. Regular apps are supposed to reencode videos using system-provided tools to .MPEG4, or can't affect video format, hence this doesn't usually matter for them.

@levlam it would be nice to support at least one open source codec in addition to proprietary H.264, because some platforms disallow binary blobs that can not be audited.

You shud M use P4 (H.264/AAC):
Browser Support: Universally supported across all major browsers (Chrome, Firefox, Safari, Edge, etc.).

@manishwalia15 browsers may support, but company or regulator policy may not, especially those who take security seriously.


cannot make a secure connection: TLS: can't accept: The TLS connection was non-properly terminated..

I'm running docker-openldap on Azure k8s. I have own certificates: company CA and server certificate.
My manifest:
     containers:
        - name: openldap
          image: osixia/openldap:latest
          args:
            - "--copy-service"
          ports:
            - containerPort: 389
            - containerPort: 636
          volumeMounts:
            - name: ldap-data
              mountPath: /var/lib/ldap
            - name: ldap-config
              mountPath: /etc/ldap/slapd.d
            - name: ldap-certs
              mountPath: /container/service/slapd/assets/certs
            - name: secret-volume
              mountPath: /container/environment/01-custom
            - name: container-run
              mountPath: /container/run
      volumes:
        - name: "secret-volume"
          secret:
            secretName: "ldap-env"
        - name: container-run
          emptyDir: {}
  volumeClaimTemplates:
    - metadata:
        name: ldap-data
      spec:
        accessModes: ["ReadWriteOnce"]
        resources:
          requests:
            storage: 1Gi
    - metadata:
        name: ldap-config
      spec:
        accessModes: ["ReadWriteOnce"]
        resources:
          requests:
            storage: 10Mi
    - metadata:
        name: ldap-certs
      spec:
        accessModes: ["ReadWriteOnce"]
        resources:
          requests:
            storage: 10Mi

From inside the openldap container:
root@openldap-0:~/tmp# ldapwhoami -x -H ldap://localhost
anonymous
root@openldap-0:~/tmp# ldapwhoami -x -H ldap://localhost -Z
ldap_start_tls: Connect error (-11)
	additional info: (unknown error code)
ldap_result: Can't contact LDAP server (-1)

And openssl:
root@openldap-0:~/tmp# openssl s_client -connect <IP_ADDRESS>:636
CONNECTED(00000003)
depth=0 C = ..., O = Company, CN = localhost
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 C = ..., O = Company, CN = localhost
verify error:num=21:unable to verify the first certificate
verify return:1
---
Certificate chain
 0 s:/C=.../O=Company/CN=localhost
   i:/DC=.../CN=Company CA
---
Server certificate
-----BEGIN CERTIFICATE-----
...
subject=/C=.../O=Company/CN=localhost
issuer=/DC=.../CN=CA Company
---
Acceptable client certificate CA names
/C=US/O=A1A Car Wash/OU=Information Technology Dep./L=Albuquerque/ST=New Mexico/CN=docker-light-baseimage
Client Certificate Types: RSA sign, DSA sign, ECDSA sign
Requested Signature Algorithms: RSA+SHA384:ECDSA+SHA384:RSA+SHA512:ECDSA+SHA512:RSA+SHA256:ECDSA+SHA256
Shared Requested Signature Algorithms: RSA+SHA384:ECDSA+SHA384:RSA+SHA512:ECDSA+SHA512:RSA+SHA256:ECDSA+SHA256
Peer signing digest: SHA512
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3645 bytes and written 314 bytes
Verification error: unable to verify the first certificate
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 8192 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: C380C4E4790CE6D12905ECFF3263C3BCD8C606945EDD02FB2042C19CEF7E8F06
    Session-ID-ctx:
    Master-Key: 333FDFB3BC3B558B4BA2E074769091E03C2340EEB56A21F957F91934A9A0DF856F5EC944AC66E4F58828C429D63AE3DF
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 21 (unable to verify the first certificate)
    Extended master secret: yes
---
^C

I have manualy copied all certs and key to /container/service/slapd/assets/certs from Secret. My certificate is singed by self signed CA.
I had even imported CA to Debian chain and run update-ca-certificates but it didn't help me.
I've compared two output of openssl command from client session(ldap-account-manager): -connect localhost:443 vs -connect openldap:636. Webserver uses the same certificate.
For ldap:
Acceptable client certificate CA names
  /C=US/O=A1A Car Wash/OU=Information Technology Dep./L=Albuquerque/ST=New Mexico/CN=docker-light-baseimage
  Client Certificate Types: RSA sign, DSA sign, ECDSA sign
  Requested Signature Algorithms: RSA+SHA384:ECDSA+SHA384:RSA+SHA512:ECDSA+SHA512:RSA+SHA256:ECDSA+SHA256
  Shared Requested Signature Algorithms: RSA+SHA384:ECDSA+SHA384:RSA+SHA512:ECDSA+SHA512:RSA+SHA256:ECDSA+SHA256
...
  SSL handshake has read 3594 bytes and written 314 bytes
  Verification error: unable to verify the first certificate
...
      Verify return code: 21 (unable to verify the first certificate)
      Extended master secret: yes

for webserver:
No client certificate CA names sent
...
SSL handshake has read 4629 bytes and written 302 bytes
  Verification error: self signed certificate in certificate chain
...
      Verify return code: 19 (self signed certificate in certificate chain)
      Extended master secret: no

What is wrong with my installation?
Edit:
ldapsearch and ldapwhoami works with changes in /etc/ldap/ldap.conf:
TLS_REQCERT allow | never

Web interface also works.
Can you force these settings on the server side?

Hm I seem to have the same problem.. did you find a solution?

I also have the same problem. I'm running the command in the container. Did you solve it?

Are there any intermediate certificates in the chain? If that is the case, those would have to be included in the CA crt file.

Any news about this case ? I have the same problem :/

Are there any intermediate certificates in the chain? If that is the case, those would have to be included in the CA crt file.
Currently I removed this service from our environment and temporally I cannot test it.

Problem solved using https://kifarunix.com/setup-openldap-server-with-ssl-tls-on-debian-10/

A small doubt regarding the same error
While setting environment vars, what certs should I match them against, I mean what would be the correct/right method ?

So I had the same problem, and at least in my case what it turned out to be is the oldTLSVerifyClient configuration being set to "demand" in the container -- I changed it to "try" and everything sorted right out. This is because I wasn't using a cert with the client which "demand" requires. TLS_REQCERT makes no difference in that case because that's about whether the server is required to have verifiable certs. Anyway, yes, changed that, worked like a charm.

So I wanted to drop a line here to follow-up on this persistent issue.  The problem with client authentication with self-signed TLS certs seems to be a common problem mentioned on a number of open tickets.  Assuming a docker installation LDAP_TLS_VERIFY_CLIENT=demand is default value when this environmental variable isn't included. Changing on the LDAP server the value of LDAP_TLS_VERIFY_CLIENT=demand to LDAP_TLS_VERIFY_CLIENT=try bypasses client authentication with a malformed client TLS certificate.  These variable names might be slightly different with a K8 installation, however the general concept still applies.
I posted my solution for the creation of client/server/CA self-signed certs that allows for TLS authentication with server and client authentication.  I've posted the solution here: https://ubuntuforums.org/showthread.php?t=2451653&p=13992175#post13992175.  After generating the certificates, LDAP_TLS_VERIFY_CLIENT=demand should work.
Here is a snippet of my docker-compose.yml file for openldap and phpldapadmin:
openldap:
image: osixia/openldap:latest
container_name: openldap
restart: always
domainname: openldap.domain.com
networks:
- net
ports:
- "389:389"
- "636:636"
secrets:
- authentication_backend-ldap_secret
environment:
- LDAP_LOG_LEVEL=256
- LDAP_ORGANISATION=gohilton
- LDAP_DOMAIN=ldap.gohilton.com
- LDAP_BASE_DN=dc=ldap,dc=gohilton,dc=com
- LDAP_ADMIN_PASSWORD_FILE=/run/secrets/authentication_backend-ldap_secret
- LDAP_TLS=true
- LDAP_TLS_CRT_FILENAME=cert.pem
- LDAP_TLS_KEY_FILENAME=key.pem
- LDAP_TLS_CA_CRT_FILENAME=ca.pem
- LDAP_TLS_ENFORCE=false
#- LDAP_TLS_VERIFY_CLIENT=try
- LDAP_TLS_VERIFY_CLIENT=demand
- LDAP_REPLICATION=false
- KEEP_EXISTING_CONFIG=false
- LDAP_REMOVE_CONFIG_AFTER_SETUP=false
- LDAP_SSL_HELPER_PREFIX=ldap
tty: true
command: --loglevel debug
stdin_open: true
volumes:
- /var/data/ldap/db:/var/lib/ldap
- /etc/ldap/config:/etc/ldap/slapd.d
- /etc/docker/compose/authelia/certs/openldap3/server:/container/service/slapd/assets/certs
phpldapadmin:
image: osixia/phpldapadmin:latest
container_name: phpldapadmin
restart: unless-stopped
hostname: phpldapadmin.domain.org
networks:
- net
ports:
- 6443:80
depends_on:
- openldap
environment:
PHPLDAPADMIN_LDAP_HOSTS: "openldap"
PHPLDAPADMIN_HTTPS: "false"
PHPLDAPADMIN_LDAP_CLIENT_TLS: "true"
PHPLDAPADMIN_LDAP_CLIENT_TLS_REQCERT: "demand"
PHPLDAPADMIN_LDAP_CLIENT_TLS_CA_CRT_FILENAME: "ca.pem"
PHPLDAPADMIN_LDAP_CLIENT_TLS_CRT_FILENAME: "cert.pem"
PHPLDAPADMIN_LDAP_CLIENT_TLS_KEY_FILENAME: "key.pem"
command: --loglevel debug
volumes:
- /etc/docker/compose/authelia/certs/openldap3/client:/container/service/ldap-client/assets/certs

I am also facing this issue. Here is another report on serverfault.
ldapsearch from within the container works:
ldapsearch -x -H ldaps://DOMAIN [...]

but fails from outside.
I've tried setting LDAP_TLS_VERIFY_CLIENT to one of "never", "try" or "allow" but nothing worked.
TLS: can't accept: The TLS connection was non-properly terminated..
5feda1a0 conn=1008 fd=13 closed (TLS negotiation failure)

I am also facing this issue. Here is another report on serverfault.
ldapsearch from within the container works:
ldapsearch -x -H ldaps://DOMAIN [...]

but fails from outside.
I've tried setting LDAP_TLS_VERIFY_CLIENT to one of "never", "try" or "allow" but nothing worked.
TLS: can't accept: The TLS connection was non-properly terminated..
5feda1a0 conn=1008 fd=13 closed (TLS negotiation failure)

@pat-s Did you solve this problem?

I can't remember anymore but atm I don't see the message anymore. Maybe also bc the bitnami image is now in use.
FWIW we have set this in our config (totally unclear if that is related to this though)
env:
  LDAP_TLS_CA_FILE: "/opt/bitnami/openldap/certs/tls.crt"

I can't remember anymore but atm I don't see the message anymore. Maybe also bc the bitnami image is now in use.
FWIW we have set this in our config (totally unclear if that is related to this though)
env:
  LDAP_TLS_CA_FILE: "/opt/bitnami/openldap/certs/tls.crt"

Thanks for the help, but unfortunately I am still in troublesome.

@yzx9
I remember all too well dealing with this TLS problem.  Just very picky and things tend to break.  Just need some more information.  Can you post the section of your docker-compose file dealing with the openldap section?  Are your SSL certificates self signed?  You need not only a certificate, but a key and at CA certificate as well.

@yzx9
I remember all too well dealing with this TLS problem. Just very picky and things tend to break. Just need some more information. Can you post the section of your docker-compose file dealing with the openldap section? Are your SSL certificates self signed? You need not only a certificate, but a key and at CA certificate as well.

@kevdogg Thank you so much for your help. your solutions in 2020 are very inspiring to me and I finally discovered the problem.
It was not a problem related to this image, but was caused by my domain name not being registered (yes, all domain names in China need to be registered, otherwise the server provider will block your TLS client hello. I originally thought it would only block the https protocol)
If anyone encounters the same problem, please first try running the following command on the server (or even within the image):
openssl s_client -connect your_domain:636 -showcerts -state

If you have deployed successfully, you should see the tls connection established successfully, otherwise you should check your tls certs first. Then, you can try to connect your server by IP (not domain) from your client:
openssl s_client -connect your_server_ip:636 -showcerts -state

If the firewall is not blocking it, the connection should also be established successfully. Finally, you can try to connect by domain from your client, and if your message is blocked, you will see that client hello fails to be sent, as shown below:
CONNECTED(00000003)
SSL_connect:before SSL initialization
SSL_connect:SSLv3/TLS write client hello
SSL_connect:error in SSLv3/TLS write client hello
write:errno=104
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 310 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

Glad you were able to find a resolution. I would have never guessed the
solution too your problem. Glad you were able to figure it out
On Sat, Sep 16, 2023 at 12:04 AM Zexin Yuan @.***>
wrote:

@yzx9 https://github.com/yzx9
I remember all too well dealing with this TLS problem. Just very picky and
things tend to break. Just need some more information. Can you post the
section of your docker-compose file dealing with the openldap section? Are
your SSL certificates self signed? You need not only a certificate, but a
key and at CA certificate as well.
@kevdogg https://github.com/kevdogg Thank you so much for your help.
your solutions in 2020 are very inspiring to me and I finally discovered
the problem.
It was not a problem related to this image, but was caused by my domain
name not being registered (yes, all domain names in China need to be
registered, otherwise the server provider will block your TLS client hello.
I originally thought it would only block the https protocol)
If anyone encounters the same problem, please first try running the
following command on the server (or even within the image):
openssl s_client -connect your_domain:636 -showcerts -state
If you have deployed successfully, you should see the tls connection
established successfully, otherwise you should check your tls certs first.
Then, you can try to connect your server by IP (not domain) from your
client:
openssl s_client -connect your_server_ip:636 -showcerts -state
If the firewall is not blocking it, the connection should also be
established successfully. Finally, you can try to connect by domain from
your client, and if your message is blocked, you will see that client hello
fails to be sent, as shown below:
CONNECTED(00000003)
SSL_connect:before SSL initialization
SSL_connect:SSLv3/TLS write client hello
SSL_connect:error in SSLv3/TLS write client hello
write:errno=104
no peer certificate available
No client certificate CA names sent
SSL handshake has read 0 bytes and written 310 bytes
Verification: OK
New, (NONE), Cipher is (NONE)
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
—
Reply to this email directly, view it on GitHub
https://github.com/osixia/docker-openldap/issues/330#issuecomment-1722136664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH75V7W26ZHY4I3GLLFUZTX2UXO5ANCNFSM4H32HTFQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Test flake] htlc mismatch: predicate not satisfied after time out

The integration test suite currently fails sometimes with the error
    --- PASS: TestLightningNetworkDaemon/test_multi-hop_htlc_local_chain_claim (7.50s)
    --- PASS: TestLightningNetworkDaemon/test_multi-hop_htlc_remote_chain_claim (7.45s)
    --- FAIL: TestLightningNetworkDaemon/switch_circuit_persistence (37.02s)
    	lnd_test.go:74: Failed: (switch circuit persistence): exited with error:
    		*errors.errorString htlc mismatch: predicate not satisfied after time out
    		/home/travis/gopath/src/github.com/lightningnetwork/lnd/lnd_test.go:9428 (0xc089ce)
    			testSwitchCircuitPersistence: t.Fatalf("htlc mismatch: %v", err)
    		/home/travis/gopath/src/github.com/lightningnetwork/lnd/lnd_test.go:99 (0xbcaccb)
    			(*harnessTest).RunTestCase: testCase.test(net, h)
    		/home/travis/gopath/src/github.com/lightningnetwork/lnd/lnd_test.go:11258 (0xc236ba)
    			TestLightningNetworkDaemon.func3: ht.RunTestCase(testCase, lndHarness)
    		/home/travis/.gimme/versions/go1.9.4.linux.amd64/src/testing/testing.go:746 (0x4f6aa0)
    			tRunner: fn(t)
    		/home/travis/.gimme/versions/go1.9.4.linux.amd64/src/runtime/asm_amd64.s:2337 (0x45ecf1)
    			goexit: BYTE	$0x90	// NOP

See for instance: https://travis-ci.org/lightningnetwork/lnd/jobs/407553324
This is the line where it fails: https://github.com/lightningnetwork/lnd/blob/5299472fad9e67d2875892f304641f80fb7ce325/lnd_test.go#L9428
It most often happen on Travis, which indicates this is more likely to happen on slow boxes.
Steps

[ ] (easy) Correct the error logging for this error. assertNumActiveHtlcs should be changed to return an error indicating how many HTLCs were active when failure happened.
[ ] Get rid of the test failure.

same issue here. How to fix it?

Might be fixed by https://github.com/lightningnetwork/lnd/pull/1608

@jarole can you please share the link to the travis build which failed?

@offerm Can you open a new issue for the failure, if you believe it is not covered by #1608? Thanks!

@halseth Yes. I'm now sure it is a different problem. Real problem not detected on time due to a problem  in this code:
func assertNumActiveHtlcs(nodes []*lntest.HarnessNode, numHtlcs int) error {
	req := &lnrpc.ListChannelsRequest{}
	ctxb := context.Background()
	for _, node := range nodes {
		nodeChans, err := node.ListChannels(ctxb, req)
		if err != nil {
			return err
		}

		for _, channel := range nodeChans.Channels {
			if len(channel.PendingHtlcs) != numHtlcs {
				return fmt.Errorf("expected %v HTLCs, got %v",
					numHtlcs, len(channel.PendingHtlcs))
			}
		}
	}

	return nil
}

The code aim to check that all nodes see numHtlcs HTLCs in their channels.
The code is not ready for a case that a node reports zero channels. In such a case, the node is considered "good" while it is not.
Do you want me to open a new issue to just modified #1608 where the problem was reported (was closed by @Roasbeef too early)?
I'm still trying to explain why the channel between Bob and Alice removed. Think it is related to #1588.

@offerm Good catch! yeah, looks like that method should return an error at the end.
Let's continue the discussion in the issue you opened :)


Exit early in device and OS matchers

It's possible to improve the performance of parse_device and parse_os on average based on the samples contained in the benchmark test suite. Given that this crate tries a large number of regexes only so it can match a single one, Regex::is_match avoids the overhead of creating captures in the majority of cases.
Here are the results from the benchmark test suite:
parse_device            time:   [1.0200 s 1.0205 s 1.0211 s]
                        change: [-13.326% -12.967% -12.665%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 4 outliers among 100 measurements (4.00%)
  1 (1.00%) low severe
  3 (3.00%) high mild

parse_os                time:   [2.3172 ms 2.3209 ms 2.3239 ms]
                        change: [-55.933% -55.774% -55.624%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  2 (2.00%) low severe
  1 (1.00%) low mild
  4 (4.00%) high mild
  4 (4.00%) high severe

parse_user_agent        time:   [177.61 ms 177.86 ms 178.05 ms]
                        change: [-1.2917% -1.0907% -0.8966%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 8 outliers among 100 measurements (8.00%)
  3 (3.00%) low severe
  5 (5.00%) high mild

Thank you, @jan-auer!


Tweet entry?

Wondering if you tweeted this out for your entry into the contest? I couldn't find it. Let me know.

Hey James. I have not. I have been meaning to reach out to you to see if you can help me solve an issue before I tweet about it. For some reason I am getting an exception when using the plugin via nuget. But it works fine if I directly reference the assemblies.

More specifically when you launch the app the app flashes and then terminates. The output windows :
01-04 11:45:04.618 D/Mono    ( 1329): Assembly Loader probing location: 'Svg.Forms.Plugin.Abstractions'.
01-04 11:45:04.618 F/monodroid-assembly( 1329): Could not load assembly 'Svg.Forms.Plugin.Abstractions' during startup registration.
01-04 11:45:04.618 F/monodroid-assembly( 1329): This might be due to an invalid debug instalation.
01-04 11:45:04.618 F/monodroid-assembly( 1329): A common cause is to 'adb install' the app directly instead of doing from the IDE.
The program 'Mono' has exited with code 0 (0x0).

Have you full uninstalled and re-installed the test app from the Apps on in settings on the phone?
I assume that it is in there and you are calling Init()?
When you install the NuGet have you made sure that everythign you are expecting is in the packages folder?

Is everything set to build in release?

Checked the Config Manager all the projects are set to Release

Have you full uninstalled and re-installed the test app from the Apps on in settings on the phone?

Tried a full uninstall/re-install did not help

I assume that it is in there and you are calling Init()?

I am calling Init (Even though it does not seem to be required for Android). What is the point of calling Init again?

When you install the NuGet have you made sure that everythign you are expecting is in the packages folder?

Seems like all the files are there when I add the nuget package

If you clone the repo I have a sample app added that demonstrates the issue.
https://github.com/paulpatarinski/Xamarin.Forms.Plugins/tree/master/SampleApp/PluginSampleApp/PluginSampleApp
I added an implementation for WinPhone and that seems to work fine, so the issue is only with Andoid

I will try this in the morning to see what is going on... Odd.
James
On Sun, Jan 4, 2015 at 5:03 PM, Paul P<EMAIL_ADDRESS>wrote:

Is everything set to build in release?
Checked the Config Manager all the projects are set to Release
Have you full uninstalled and re-installed the test app from the Apps on
in settings on the phone?
Tried a full uninstall/re-install did not help
I assume that it is in there and you are calling Init()?
I am calling Init (Even though it does not seem to be required for
Android). What is the point of calling Init again?
When you install the NuGet have you made sure that everythign you are
expecting is in the packages folder?
Seems like all the files are there when I add the nuget package
If you clone the repo I have a sample app added that demonstrates the
issue.
https://github.com/paulpatarinski/Xamarin.Forms.Plugins/tree/master/SampleApp/PluginSampleApp/PluginSampleApp
I added an implementation for WinPhone and that seems to work fine, so the
issue is only with Andoid
—
Reply to this email directly or view it on GitHub
https://github.com/paulpatarinski/Xamarin.Forms.Plugins/issues/1#issuecomment-68651475
.

--
James Montemagno
http://www.montemagno.com
@jamesmontemagno http://www.twitter.com/jamesmontemagno

I figured it out...
So your DLLS are called SVG.*  however you are renaming them in your NuSpec to Svg.*
Keep them all as SVG.* and it will work correclty.

That was it thanks a lot. It is all working now. Would you by any chance be interested in helping me with the iOS version? I don't have an iOS license or a Mac.


Remove unused imports

Coverage remained the same at 76.655% when pulling fa1324713f669d4fb36d78bfc9bfb162e17d2079 on develop into 981af2c5e6001111c8adbc501100638c9cfcf00a on master.


[T5A2][T16-B4]ZhaoTianze

Added a polymorphic isMutating method;
Added an exception to an overridden method;
p.s. forgot to create a new brunch for T5A2, so it goes with changes of T5A1.

Avoid accumulating unrelated changes into a single PR.
Tip: If you are currently on branch1 and want to create a new branch2, you need to switch back to master branch before creating branch2. If not, changes in branch1 will appear in the PR created from branch2 later.


[Bug]: SEI ('electron-migration limited') model

PyBaMM Version
23.9
Python Version
3.10
Describe the bug
I noticed that the SEI thickness decreases when the 'electron-migration limited' model (option) is used, which is unrealistic.
Steps to Reproduce
import pybamm
import numpy as np
import matplotlib.pyplot as plt
exp_CCCV = pybamm.Experiment(
    [("Charge at C/10 until 4.2 V",
      "Rest for 10 hours",
      "Discharge at C/10 until 2.5 V",
      "Rest for 10 hours",
      )]
)
model = pybamm.lithium_ion.SPM(options={
    "SEI": "electron-migration limited",
    "SEI porosity change": "true",
},
    name="SPM-SEI")

solver = pybamm.CasadiSolver()
sim = pybamm.Simulation(model, experiment=exp_CCCV, solver=solver)
sol = sim.solve(initial_soc=0)
plt.plot(sol["Time [h]"].entries,
         sol['X-averaged negative total SEI thickness [m]'].entries, label='SEI thickness')

Relevant log output
No response

Just to provide more clarity, I have attached three figures here for the electro-migration limited model before correction, after correction, and the interstitial-diffusion limited model.  The corrected version follows a similar trend to the interstitial model.

For clarity, the current model is the bottom plot and Kawa's fix is the middle one.


Won't build on UNIX with MINIZIP_DEBUG

What are the steps to reproduce this issue?

… Set CMAKE_BUILD_TYPE=Debug on UNIX
… Build GEOS-DEV/thirdPartyLibraries
…

What does happen?
… FESAPI won't link because it looks for libminizip.a and not libminizip_d.a
What were you expecting to happen?
… Link with libminizip_d.a
Any logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Any other comments?
… not really a bug...
What versions of fesapi are you using?
… <IP_ADDRESS>

https://github.com/GEOS-DEV/thirdPartyLibs/issues/226


tandoor-recipes: Dynamic URLs don't include SCRIPT_NAME

Describe the bug
Moving https://github.com/TandoorRecipes/recipes/issues/3300 here since it won't be fixed upstream.
Steps To Reproduce
Steps to reproduce the behavior:

Install tandoor-recipes with extraConfig.SCRIPT_NAME set to a non-empty string and extraConfig.STATIC_URL = "${config.services.tandoor-recipes.extraConfig.SCRIPT_NAME}/static/"
Configure Tandoor
Log into the local Tandoor web site
Click the "+ Create" link in the middle of the page
The browser goes to /new/recipe/ on the current server

Expected behavior
The browser should go to '${config.services.tandoor-recipes.extraConfig.SCRIPT_NAME}/new/recipe/` instead (after substituting the actual value of the script name).
Screenshots

Notify maintainers
@ambroisie
Metadata

system: "x86_64-linux"
host os: Linux 6.6.49, NixOS, 24.11 (Vicuna), 24.11pre677397.574d1eac1c20
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.5
channels(root): "nixos, nixos-hardware"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Add a :+1: reaction to issues you find important.

I don't have a fix for this other than you using the package option and overrideAttrs to rebuild the package with your custom sub-folder.


Add cycle detection in Node sanitization for encoding

Hello!
I'm using Logtail and just noticed an error on trying to log some metadata based on objects in my app that have circular references. This is the stack trace:
RangeError: Maximum call stack size exceeded
    at /my_app/node_modules/@logtail/node/src/node.ts:104:37
    at Array.forEach (<anonymous>)
    at Node.sanitizeForEncoding (/my_app/node_modules/@logtail/node/src/node.ts:104:29)
    at /my_app/node_modules/@logtail/node/src/node.ts:108:29
    at Array.forEach (<anonymous>)
    at Node.sanitizeForEncoding (/my_app/node_modules/@logtail/node/src/node.ts:104:29)
    at /my_app/node_modules/@logtail/node/src/node.ts:108:29
    at Array.forEach (<anonymous>)
    at Node.sanitizeForEncoding (/my_app/node_modules/@logtail/node/src/node.ts:104:29)
    at /my_app/node_modules/@logtail/node/src/node.ts:100:39

That links to this piece of code, which is ignoring possible reference cycles:
https://github.com/logtail/logtail-js/blob/174eee03ca3baebbddbad0cb17da23c11ea0fb93/packages/node/src/node.ts#L104-L112
So, if I may share my opinion, I believe cycles coming from the context object should be cut off by not propagating them after sanitization operation.

I'just say that I'm able to reproduce this issue with<EMAIL_ADDRESS>and this is not fixed in logtail librairy side.
I'll come back with an HowToReproduce right here but (my context) this seems to be when using a mongo object as context object argument. Mongo object include circular references. The fix would be to use mongo lean() method for a find query for example to get a plain old json object without circular ref.

@gyfis please reopen this issue to avoid duplicate.
I isolate this use case in a dedicated test sample, cf. logtailSample readme


Use refactored Arsenal's Auth API - Step 1

This is the first step towards using the cleaned-up Auth API from arsenal.
The work is still ongoing, but this will allow us to avoid falling out-of-sync.
Depends on: https://github.com/scality/Arsenal/pull/119 then https://github.com/scality/vaultclient/pull/94

The vault backend in lib/auth/vault.js is not updated to reflect the changes here, was update on the file inside arsenal, but it's the wrong one

updated

@ironman-machine
SCALITY_VAULT_BRANCH=dev/cleanup/AuthAPI-Step1

Hello @AntoninCoulibaly,
Starting end to end procedure using the following payload:
{"SCALITY_VAULT_BRANCH":"dev/cleanup/AuthAPI-Step1","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1"}
Please follow http://ci.ironmann.io/gh/scality/Integration/2505 for circle status.

:+1:

Hello @mvaude,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fix/nimrod-build-dep","SCALITY_FEDERATION_BRANCH":"ft/dep-patcher-ansible","SCALITY_VAULT_BRANCH":"dev/cleanup/AuthAPI-Step1","SCALITY_VAULTCLIENT_BRANCH":"dev/cleanup/AuthAPI","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1","REPO_NAME":"S3","PR_NUMBER":100,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4246 for circle status.

Hello @mvaude,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fix/nimrod-build-dep","SCALITY_FEDERATION_BRANCH":"ft/dep-patcher-ansible","SCALITY_VAULT_BRANCH":"dev/cleanup/AuthAPI-Step1","SCALITY_VAULTCLIENT_BRANCH":"dev/cleanup/AuthAPI","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1","REPO_NAME":"S3","PR_NUMBER":100,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4247 for circle status.

Hello @mvaude,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fix/nimrod-build-dep","SCALITY_FEDERATION_BRANCH":"ft/dep-patcher-ansible","SCALITY_VAULT_BRANCH":"dev/cleanup/AuthAPI-Step1","SCALITY_VAULTCLIENT_BRANCH":"dev/cleanup/AuthAPI","SCALITY_UTAPI_BRANCH":"dev/cleanup/AuthAPI-Step1","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1","REPO_NAME":"S3","PR_NUMBER":100,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4248 for circle status.

Hello @mvaude,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fix/nimrod-build-dep","SCALITY_FEDERATION_BRANCH":"ft/dep-patcher-ansible","SCALITY_VAULT_BRANCH":"dev/cleanup/AuthAPI-Step1","SCALITY_VAULTCLIENT_BRANCH":"dev/cleanup/AuthAPI","SCALITY_UTAPI_BRANCH":"dev/cleanup/AuthAPI-Step1","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1","REPO_NAME":"S3","PR_NUMBER":100,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4252 for circle status.

Hello @mvaude,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fix/nimrod-build-dep","SCALITY_FEDERATION_BRANCH":"ft/dep-patcher-ansible","SCALITY_VAULT_BRANCH":"dev/cleanup/AuthAPI-Step1","SCALITY_VAULTCLIENT_BRANCH":"dev/cleanup/AuthAPI","SCALITY_UTAPI_BRANCH":"dev/cleanup/AuthAPI-Step1","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1","REPO_NAME":"S3","PR_NUMBER":100,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4253 for circle status.

Hello @mvaude,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fix/nimrod-build-dep","SCALITY_FEDERATION_BRANCH":"ft/dep-patcher-ansible","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"dev/cleanup/AuthAPI-Step1","REPO_NAME":"S3","PR_NUMBER":100,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4255 for circle status.


Run CI on nightly

Even if you aren't very eager to update the toolchain, probably it's a good idea to run test on nightly as well so that you can detect the future breakage like https://github.com/posit-dev/positron/issues/3911 early.

seems reasonable, thanks!


2022042701

Rebased
Closes #4275
Closes #4281
Closes #4306
Closes #4308
Closes #4307
Closes #2324
Closes #2989
Closes #4241
Closes #3570
Closes #2675
Closes #2349
Closes #2914
Closes #2737
Closes #2222
Closes #2222
Closes #2222
Closes #2222
Closes #2222
Closes #2264
Closes #2265
Closes #1486
Closes #30
Closes #3069
Closes #2273
Closes #2272
Closes #2284
Closes #2292
Closes #2293
Closes #2294
Closes #2307
Closes #2328
Closes #2333
Closes #2344
Closes #2355
Closes #2356
Closes #2357
Closes #2362
Closes #2382
Closes #2394
Closes #2420
Closes #2324
Closes #4273
Closes #4278

@abhay Closed the old PR and opened this PR. Rebased the underlying data.

Please check the issue #2506
Thank you in advance!

@abhay file was rebased a couple of days ago with a new PR.

@abhay file was rebased a couple of days ago with a new PR.

sorry one more rebase if you could. and update to today.

Dear Abhay, pease take a look at my case: #2506.
I have been waiting for ages and I have not done anything wrong.
Thank you in advance!

Thanks for these removals! I'm ready to sign.


Q: What is equivalent to PostAndReply

Hi,
This is a bit of a Noob question. I'm just starting out in F# and Agents.
How would I go about doing a PostAndReply type agent request.
Your tracing sample seems to post back a message to the "source" agent as another "Request", but that doesn't address a situation where the request is not coming from an existing Agent.
e.g  Make a call that originated from somewhere other than within an Agent, say, a command line helper tool that makes a remote Agent request into a larger system (perhaps running as a service). I presume I need to use Message.Post or "agent" <-- XXXX calls to get the Message into the worker.
Also, how would I go about making a call to another agent such that:  let! result = Message.PostAndReply(parms * ReplyChannel) was possible, and I wouldn't need to manage the state during the recursive call within the worker function. (One of the other examples seems to maintain a map so that the request/reply messages between agents can be linked together. This seems rather un-async to me...or have I totally missed something with how I should be using Cricket?
Thanks for any info you can share.
Regards,
Nathan

I've found your reply to Issue #36, and I think that answers my question, except in the situation of via remote requests from the Agent.
Does the AsyncResultCell work via a remote Agent request also?
Thanks in advance.
P.S. I should have searched the closed issues first...sorry :-/

No problem, I really should monitor the issues more closely.
Currently if you need an explicit reply, then you can use Messge.reply in your message handler. This will return the reply asynchronously back to the agent. There is an example of this in the PingPong example here. If you want to do this synchronously then it is still possible, Although somewhat more complicated.
Basically you'll want something like the following
 let replyAwaiters = new ConcurrentQueue<Guid, AsyncResultCell<'a>>()
 actor {
    body(
           let replyAwaiters = new ConcurrentQueue<Guid, AsyncResultCell<'a>>()
           let rec loop() = messageHandler {
                let! msg = Message.scan (fun msg ->
                                     match replayAwaiters.TryPeek() with
                                     | true, replyCell when msg.Message.Id = (fst replyCell) ->
                                            Some async {
                                                let! msg = replayAwaiters.Dequeue()
                                                (snd msg).SetResult(msg.Message) }
                                     | _, _ -> None)
                   return! loop()}
           loop())
 }

Disclaimer - No compiler at hand so haven't checked this.
So, the basic idea is to have a queue which stores the AsyncResultCell along with the message Id, then scan the queue only accepting the message the that matches the top awaiter. If it does then handle that message and rescan the queue for the next awaiter.
I do plan on surfacing this in a far more friendly way in the API, however using this it is quite easy to create situation where either an OutOfMemoryException looms, because you never handle messages, or the cost of handling the msg vs doing the scan, is so different that your app spends more time scanning for messages than actually processing them. For this reason this is why I prefer the asynchronous method, given initially.
Let me know if this helps
Cheers.

Thanks for the feedback. The Message.reply works well.
I found a different way to do the synchronous call. This seems to work fairly well for things like a command line tool that sends the message off, and waits for the result:
let handleAsync msg =
    async {
        let resultCell = new AsyncResultCell<_>()
        agent <-- msg(resultCell)
        return! resultCell.AwaitResult()
    } |> Async.RunSynchronously

I'm having trouble with the remote agents though. I'll open another question on that, since it's different enough to this (assuming I cannot find the answer in closed issues :)
Thanks for your help.


Make new long term plan

[x] Start overleaf document
[x] Define Lasair versions (here)
[x] Make first draft
[x] Circulate to team
[x] Revise based on team comments
[x] Circulate to management team see https://www.overleaf.com/read/rybpckybxcyx
[x] Final version
[x] Release

This is basically an updated version of the long term plan we made at the beginning of Phase B. It will

build in revised goals
update status of deliverables and milestones
update the Rubin timeline context
describe our revised approach to project management
stir in the technical decisions we made recently at our mid-project internal review (to be confirmed at external review

Update May 19th: the overleaf document is available at
https://www.overleaf.com/project/608a931b6ee17e3c0dac8dac

Hi Andy, I cannot access the overleaf document.  I have created an overleaf account<EMAIL_ADDRESS>Are you able to grant me access? Cheers, Terry

should be done
On 18/08/2021, 09:17, "Terry Sloan" @.***> wrote:
Hi Andy, I cannot access the overleaf document. I have created an overleaf account
<EMAIL_ADDRESS>Are you able to grant me access? Cheers, Terry
—
You are receiving this because you were assigned.
Reply to this email directly,
view it on GitHub <https://github.com/lsst-uk/lasair-lsst/issues/75#issuecomment-900916038>, or
unsubscribe <https://github.com/notifications/unsubscribe-auth/AFC4AQTKWFTEJETNNGWTSXLT5NUAXANCNFSM43SSDIFQ>.
Triage notifications on the go with GitHub Mobile for
iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or
Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
[
{
<EMAIL_ADDRESS>"http://schema.org",
<EMAIL_ADDRESS>"EmailMessage",
"potentialAction": {
<EMAIL_ADDRESS>"ViewAction",
"target": "https://github.com/lsst-uk/lasair-lsst/issues/75#issuecomment-900916038",
"url": "https://github.com/lsst-uk/lasair-lsst/issues/75#issuecomment-900916038",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
<EMAIL_ADDRESS>"Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

09/MAR/22
Andy reported at Lasair fortnightly that the report is now finalised at available from the Lasair project page as an attachment


ERR_SSL_VERSION_OR_CIPHER_MISMATCH with Third-Party Subdomain

App ARN: arn:aws:amplify:ap-southeast-1:252100588959:apps/d2xks58rvcvn6p
Region: Southeast 1
Step: DNS is configured through Cloudflare
Status: Unable to reach Amplify
** Please describe which feature you have a question about? **
We're building an app with Amplify, we've connected the domain and the DNS appears to be all correct, but we are getting ERR_SSL_VERSION_OR_CIPHER_MISMATCH and I have no idea why or how to fix it. I'd appreciate any insight you'd be willing to give. We are using Cloudflare, and I'm not sure if that's part of the problem.
** Provide additional details**
The domain we have mapped to Amplify is admin.designed.org
In Cloudflare Business we are using their proxy to protect our apps
RE: https://github.com/aws-amplify/amplify-console/issues/156

Hi @simpson was your domain linked to an SSL certificate from a 3rd party before you tried registering it with your Amplify App?

@Athena96 @donkahn Here is the Cloudflare solution but it should be similar to other places!
I'll try to be descriptive for the others with this problem. The problem is that Amplify prefixes the records with WWW, but it doesn't tell you that in the DNS settings (you should clarify that probably). So if you view the image, you need to add two additional CNAME records in Cloudflare with the www. prefix. After you do that, the Universal and Dedicated SSL options won't work. You need to purchase a Dedicated Certificate with 50 Hostnames ($10/month). When you do that you have to add ALL of the CNAMES at this step (or you have to delete and start over. After that, the acceleration proxy can be turned back on and everything should work fine. Hope this help someone else!

Thanks for sharing @simpson!


gmail.observe.on("send_message", function(url, body, data, xhr)

Hello All,
I hope you all are keeping safe during these times.
I am using the gmail.observe.on to get the body of the sent message to fetch the attachments in a chrome extension.
I am doing it by manipulating the body object returned from the event. I am new to gmail extension development. Can someone experienced please let me know whether this method is future proof.
I look forward to hearing from you.
gmail.observe.on("send_message", function(url, body, data, xhr) {
	`console.log(body);`

 });

For accessing attachment-information, I recommend obtaining a reference to the sent email, and then using the regular get.new.email_data(id).attachments API:

Hello Jostein,
Thanks for that. I actually realized that the attachments can also be accessed from the data object.
data.attachments[i]['url'].
I am trying to get the attachments of a sent email.
Can you please briefly let me know how to get started with a chrome extension without modifying the original extension file. Thank you!

I’m not sure I understand. Obviously you’ll have to make changes to the extension-file to create your own extension.
The boilerplate-project linked in the README should be a simple and safe project to start with.
Otherwise the internet is full of documentation on how to create non-gmail-specific WebExtensions. Everything mentioned there still applies here.

Is there a way I can keep the original file untouched. What I have done so far is;
followed the procedure in here. I am editing the extension file in the dist folder after running npm run build.
My question was is there a way to keep the file in the dist folder unchanged when creating the extension.

What you are doing is not practical, nor supported. You are supposed to edit the src/extension.js file and rebuild (and thus create a new dist/extension.js) to create your extension.
Why do you insist on not editing the file directly, when that is absolutely the simplest approach?

Either way, I'm closing this issue, as it's not an issue with gmail-js, and the original question (regarding attachments) have been resolved.


<EMAIL_ADDRESS>

Release: https://sourceforge.net/projects/freetype/files/freetype2/2.9/
Used by:

https://github.com/google/quic-trace

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (freetype) have been updated in this PR. Please review the changes.

/skip-url-stability-check

Nice try you need the set the label which can only be done by "admins"
@fmeum I think it would be nice if a "normal" user could set this label - maybe via posting "/skip-url-stability-check" -> I needed it also here: https://github.com/bazelbuild/bazel-central-registry/pull/1773. I think the warning makes perfect sense. Neverthless, I would trust a module maintainer when she/he sets the label


FTP Upload V2 Task fails with an "FTPError: 426 Failure reading network stream."

Type: Bug
Enter Task Name: FTP Upload V2
Environment

Pool: Azure Pipelines
Agent: Hosted Agent

Issue Description
FTP Upload V2 Task fails with an "FTPError: 426 Failure reading network stream."
Protocol: ftps://
I am using.

with "windows-latest" also fails.
Task logs

I need help, I use this for CI/CD.
Thanks.

Hi @kalozoya-gregal, thank you for reporting I checked the task with my ftps server on uploading ~10k files in different sizes and it seems working.
Are you sure that the problem is exactly with the task? FTPUploader task using basic-ftp library to connect and upload files, and I found some explanation from the author why the error appears, and sometimes it may happen if FTP server has multiple uploads from a different source. You can try to specify retryCountOnTaskFailure option in case your server break the connections.
But to be clear is that a problem with the task or server, can you please try to upload the same directory with the same files directly from your working machine through lftp for Linux machines or WinSCP for windows.
As I temporary solution(as I see that some files uploading correctly, and probably the problem is in the number of files), I could recommend you try to archive the directory and upload an archive with ArchiveFiles Task and then manipulate it via SSH task

More information from server:

FTPUploader task:

At the moment, it happens with files larger than 30 KB
I have tried with retryCountOnTaskFailure option to 2, but I have the same error. It's starting the whole file upload again.
With WinSCP I have uploaded the files correctly.
Searching for information about the error I found these "issues" on FruentFTP as well. Last week it seems they published a new release fixing it.
Main issue: https://github.com/robinrodricks/FluentFTP/issues/996
https://github.com/robinrodricks/FluentFTP/issues/573
https://github.com/robinrodricks/FluentFTP/issues/763
Hope that helps.


Adding changelog for vendoring libnetwork into docker

Signed-off-by: Madhu Venugopal<EMAIL_ADDRESS>

LGTM

:+1: thanks!


enter timecodes instead of drag to select

bc choosing your clip graphically in the waveform is tedious

Two potential improvements to help with this:

Show the selected start and end time as you drag the selection, not just the duration.
Make the playhead draggable/add a handle

Making the playhead draggable is a bit tricky because of the existing preview workflow that auto stops/starts the audio, but the rest should be straightforward enough.

i'm back in the audiogram app now about to do another episode. really struggling to highlight the piece of the waveform that I want. Working with a 30min audio file means it's almost impossible to drag and select with accuracy. And I have to re-listen to the whole clip every time I want to see what i've got... my workaround will probably be to edit the clip in an external editor. or to just over-select and let the clip cut abruptly at the end wherever it lands..
hopefully this insight into my process helps. just try it yourself to see how it's frustrating/doesnt behave like a normal audio editor -- just try selecting a specific 30s soundbyte from a 30min file ...

We've tried selecting snippets from longer files. There's certainly a resolution issue: with something 30 minutes long, you only have one pixel of horizontal space for every 3 seconds of audio, so doing precise cuts is difficult.  It's something we're keeping in mind as we update the interface to accommodate multiple captions.
That being said, we're not going to go very far down the road of rebuilding a whole audio editor with zooming, scrolling, dynamic playheads, etc. The limited clipping functionality is meant an added convenience but if it doesn't meet your needs editing your audio in other software first makes sense.


typo fix on logging elasticsearch subnet count

Yeah happens to me a lot too, unless we have a terraform plan with some default values just for sanity, would solve some issues but not the more complex dependencies


fix: Make linking/unlinking 3rd-Party logins easy

This PR solves #36.
Apart from this, I added a clear button as a utility to remove any particular login provider

Already done: https://github.com/casbin/casdoor/issues/36#issuecomment-828946812


Broken links in breadcrumbs outside nav

When pages are not in the nav.adoc, the Antora UI creates broken links in the breadcrumbs and page titles.
To replicate the issue include the following files in any project:
// modules/ROOT/nav.adoc
# ...
* xref:root-link.adoc[]
# ...

// modules/ROOT/pages/root-link.adoc
= Root link

xref:test:A.adoc[A]

// modules/test/pages/A.adoc
= A with a link to xref:B/B.adoc[B]

Link to xref:B/B.adoc[B]

// modules/test/pages/B/B.adoc
= B with a link to xref:A.adoc[A]

Link to xref:A.adoc[A]

The links in B will be broken in the breadcrumbs and the title, but not in the content of the B.adoc file.

I've been investigating this issue. The problem is that Asciidoc and Antora have different behaviors for xrefs and, to make it worse, Antora uses the Asciidoc behavior for the title.
So Antora doesn't support relative paths, and all xrefs must be relative to the module pages. So xref:a/b.adoc renders as <module>/a/b.html.
On the other hand, Asciidoc supports relative paths and paths are rendered relative to the current page. So xref:a/b.adoc renders as <current page>/a/b.html.
These two things are not the same. So unless all pages are in the root module pages, we would have broken links either in Antora or Asciidoc. To make things worse, Antora uses the default Asciidoc behavior for the title, so
= xref:a/b.adoc

xref:a/b.adoc

would render as <current page>/a/b.html and then <module>/a/b.html for the exact same xref. And breadcrumbs would also have the broken link when it's not in nav.adoc because it just replicates the title.
The solution I found was to set the relfileprefix attribute.
The attribute prepends all xrefs with some prefix (like "../", etc). This fixes the problem with Asciidoc. The solution isn't supposed to be needed in Antora, but it also fixes the problem with titles and breadcrumbs.
So this issue becomes less urgent now that we don't have broken links for the boost documentation 1.87. It's still worth checking the rules the Antora UI uses to render these breadcrumbs and title and see if there's something we can do about it in the general case.
I think most people don't ever have this issue because they don't include links in the title, but MrDocs does.

Thanks for the info, I think I'll move this to a priority 3 for now, as it shouldn't affect the release, or break anything in the near term related to getting the launch done.

Adding the zulip link for reference https://antora.zulipchat.com/#narrow/channel/282400-users/topic/Relative.20xrefs


Feedback UI / Shake to Send

Describe the solution you'd like
Support for HockeyApp's Feedback UI (aka "Shake to Send")
https://support.hockeyapp.net/kb/general-account-management-2/invoking-feedback-ui-with-a-shake-gesture
This is something that HockeyApp supports, but isn't supported by app center. I'm very upset that you're killing HockeyApp while providing an inferior product to replace it 😡
Describe alternatives you've considered
HockeyApp is the primary "alternative", but it's being mercilessly slaughtered by the Gods of Microsoft.
InstaBug is another alternative that my CEO wants us to adopt, but I would strongly prefer HockeyApp or AppCenter.
Additional context
We're very happy with Codepush and AppCenter's CI pipeline. We would love to also adopt both analytics and diagnostics to replace Sentry/Amplitude, but our CEO is pushing hard for Instabug or equivalent. I'd also be happy if you let us use HockeyApp and didn't force a move to AppCenter

@mcmar regardless of your frustration, we don't accept any abusive language. If you want this to be a proper feature request, re-think your wording, otherwise I'll close it.
We're working hard to make App Center the successor of HockeyApp and we've intentionally decided to not support the Feedback functionality. There's a recommendation site in our docs.
The purpose of this repository is to inform of our users about upcoming work and offer them a way to raise issues or request features publicly. The more precise the use case is described the better it is for other users to discover and upvote a request.

@derpixeldan Can you define what you consider abusive language? I re-read it and can't find anything that a reasonable person would characterize as abusive

As far as the feature request goes, this is a straightforward feature request asking for implementation of a new feature that's already supported in an "alternative product" if you can call it that. Thank you for the documentation showing that this was at least intentionally omitted. Hopefully I'm not the only user who disagrees with this decision. Part of my reason for disagreeing is not simply because it's useful functionality, but also because the team responsible for the decision not to support it is also responsible for killing an existing product that does support it, which feels very unfair to customers.
Maybe one way to fulfill this feature request without doing any new work would be to simply not kill HockeyApp? That way existing users can continue happily using the in-app Feedback UI. Ot at least any decision to kill HockeyApp could be delayed until existing functionality is supported by the successor product

Yup you are not the only one. I can't believe this feature didn't make it into AppCenter. Honestly most bug reports (the big one that makes your head hurt) are simply useless without user feedback (atleast this has been the case for me). And as for simple bug reports I always went with Fabric.io. Until now I thought this was in the roadmap, or perhaps might be put into later on, but after seing that documentation, I have got to say, I am dissapointed.
They have every right to kill any of these features, and I suppose I have to consider other options.

@mcmar even though I had to chuckle I think it's not the right place for sarcasm.

mercilessly slaughtered by the Gods of Microsoft

We have carefully weight on this decision and won't support a transition experience for Feedback. However, if the feature request becomes popular enough, we're re-considering adding a similar functionality to App Center in the future.

The companies of Avistar and InFocus have many products that relays on feedbacks including Windows/IOS/Android/MacOS OSes. This was one of the key things that supports products real life stability.
If this feature removed the most of the enterprise products will lose this kind of feedbacks including automated logs/dumps reporting in case of failure on customer's side.
Most of the options given by MSFT as a reasonable and possible replacement in fact have limitations in a range of different OSes support or does not provide ability to attach and store custom data. Most of them just mobile oriented.
Please take all above into account while planning. We were contacted Anvesh and he asked us to have a note in this thread.

+1 but is this not a duplicate of #412 ?

+1 Because 12 of our apps are using Feedback UI feature and we are waiting for the same to be included in AppCenter. We are not able to migrate due to unavailability of this very important and useful feature.


Microsoft WebDriver support

Hello,
Can anybody confirm that canopy works with MS Edge driver (17134)?
Getting The remote server returned an error: (400) Bad Request. with the most recent Windows. Not sure if the problem is with canopy or with the webdriver.

@eugene-g
Using
Edge:
Microsoft Edge 41.16299.371.0
Microsoft EdgeHTML 16.16299
Driver:
Release 16299
Version: 5.16299 | Edge version supported: 16.16299
This works for me:
configuration.driverHostName <- "localhost"
start edgeBETA

Windows 10, .net461
I am trying to get my VM updated to latest so I can have the same version as you and test that.

Using
Windows 10, .net core
Microsoft Edge 42.17134.1.0
Microsoft EdgeHTML 17.17134
Driver:
Release 17134
Version: 6.17134 | Edge version supported: 17.17134
The browser launches and runs a basic test.
configuration.driverHostName <- "localhost"
start edgeBETA

configuration.driverHostName <- "localhost"

This line solves the issue. What does it mean?
Since Chrome and Firefox tests were working fine, I didn't even think that problem could be with canopy configuration.
btw, a few issues with project:

Edge is not covered by basic tests
In build.fsx:
testAssemblies path is incorrect. I believe it should be something like "tests/**/bin/Release/**/*basictests*.dll"
But even if you correct the path:

Running build failed.
Error:
System.Exception: Failed result from basictests
   at FSI_0005.Build.clo@107-7.Invoke(String testFile)
   at Microsoft.FSharp.Collections.SeqModule.Iterate[T](FSharpFunc`2 action, IEnumerable`1 source)
   at FSI_0005.Build.clo@102-6.Invoke(Unit _arg5)
   at Fake.TargetHelper.runSingleTarget(TargetTemplate`1 target) in D:\code\fake\src\app\FakeLib\TargetHelper.fs:line 626

I gave up trying to fix that issue and did dotnet run to ensure that issue could be closed.

For build.fsx, I can't remember if I use it anymore with .net core, so don't worry about that.
I added configuration.driverHostName <- "localhost" because in .net core it can't resolve localhost correctly and it made every call to selenium have an additional 1 second added to it, making tests crazy slow.  That setting is used by selenium to know what address to talk to the webdriver over.  http://<IP_ADDRESS>:19123 or http://localhost:19123.  I set it to use <IP_ADDRESS> to make dotnet core work at the correct speed, but apparently that breaks edge.

Good thing about "localhost" is that it works with all major browsers (except Safari, haven't tried it yet). Speed issue is important though.
Thank you for your time and explanations.


DB AutoSuspend, Function Queue, Build Version

Since Exchange 2016 CU4, it has been added the status "AutoSuspended" on the lagging bases. This status is normal and I opened a ticket to Microsoft to confirm this. (Reduction in bandwidth consumption)
I have a function for the tail of emails because we receive enormous emails at a moment T and we receive errors because the tail is higher than a threshold. The function will loop up to 5 if the queue is above the threshold, otherwise it will continue the script.
I added the Build Exchange, always interesting when we have a big cluster to know which servers have which versions. (CU)

Can you please resubmit this PR to the development branch before I can look at it.

Hello,
I resubmit in DEV:
Https://github.com/cunninghamp/Test-ExchangeServerHealth.ps1/pull/16

This was resubmitted as #16


[5.8] Change PutEnvAdapter to PutenvAdapter

change PutEnvAdapter to PutenvAdapter since the class is a PutenvAdapter

thansk you


use monolithic marathon api

currently the marathon namer uses a pair of marathon APIs get get service discovery information:

/marathon/v2/apps
/marathon/v2/apps/[app]

instead, just call a single api with extra params:
/marathon/v2/apps?embed=apps.tasks
full details:
http://mesosphere.github.io/marathon/docs/rest-api.html#get-v2-apps
proposed scala change:
marathon/src/main/scala/io/buoyant/marathon/v2/Api.scala:
trait Api {
  def getApps(): Future[Api.Apps]
}

object Api {
  type Apps = Map[Path, Addr]
}

taking this a step further, consider using server side events (SSE), or marathon api callbacks.
relates to #105 and #704

per discussion: we're a little concerned that a single pull of the entire dataset could be much heavier resource-wise.  We'd want to be ensure that this system works well in non-trivial deployments.
Ideally, of course, marathon would provide a non-SSE streaming or watch API.

https://mesosphere.github.io/marathon/docs/generated/api.html#v2_eventSubscriptions_get ?

@moderation yeah, this is another approach that could work well especially for namerd.  I'm reluctant to rely on callbacks to hit all linkerd instances in a cluster...


Add sensitive to registry_key (fixes #5695)

Description
This PR adds the sensitive property to registry_key but needs some help before it's ready to be merged.
I'm not sure if the sensitive: true sets the values property to default to sensitive or if when sensitive is true on the resource, values will be masked.
Re tests, looking at the execute resource it looks like I should be copying across something like below, but not sure where it should sit.
    context "when sensitive is set true" do
      it "should honor sensitive attribute" do
        new_resource.sensitive true
        # Since the resource is sensitive, it should not have :live_stream set
        opts.delete(:live_stream)
        expect(provider).to receive(:shell_out_with_systems_locale!).with(new_resource.name, opts)
        expect(provider).to receive(:converge_by).with("registry_key sensitive resource").and_call_original
        expect(Chef::Log).not_to receive(:warn)
        provider.run_action(:run)
        expect(new_resource).to be_updated
      end
    end

Issues Resolved
#5695
Check List

[ ] New functionality includes tests
[ ] All tests pass
[x] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

@shoekstra There's a large number of spec failures due to the validation change in Travis

Sorry for the delayed response!
After some conversations with @coderanger we realised I was totally off, the problem lay in the converge_by blocks in the provider which should be resolved now.


Chacha20/poly1305 support

this is on top of #13, and requires https://github.com/mirage/mirage-crypto/pull/73 being merged and released.
TL;DR: implements https://cvsweb.openbsd.org/src/usr.bin/ssh/PROTOCOL.chacha20poly1305?annotate=HEAD ChaCha20/Poly1305 support for ssh. ssh uses 64 bit nonce (well, the 32 bit sequence number, 0 padded), and 64 bit counter. Two keys are used: one to encrypt the length field, the other to derive a poly1305 secret and encrypt and authenticate the msg. The encrypted length field is part of the data to be authenticated.
When Chacha20/poly1305 is negotiated, there is no hmac in place, since the poly1305 already provides a mac. This makes the Packet.decrypt operation slightly more convoluted (need to take care of mac_len and do some book keeping on it). Also, Cipher.decrypt may now fail (if the sent mac and computed mac are not equal).
Motivation came from #10, cryptographic agility, and recent integration of chacha20/poly1305 into mirage-crypto (still unreleased).

any hints on the CI  failure (maybe @talex5)?
#4 docker-image://docker.io/docker/dockerfile:experimental@sha256:ee85655c57140bd20a5ebc3bb802e7410ee9ac47ca92b193ed0ab17485024fe5
#4 sha256:71a594c684f98692da7baadc89226dfbe7a87a365660bd1251c8db6c1d7f4620
#4 resolve docker.io/docker/dockerfile:experimental@sha256:ee85655c57140bd20a5ebc3bb802e7410ee9ac47ca92b193ed0ab17485024fe5
#4 resolve docker.io/docker/dockerfile:experimental@sha256:ee85655c57140bd20a5ebc3bb802e7410ee9ac47ca92b193ed0ab17485024fe5 done
#4 sha256:ee85655c57140bd20a5ebc3bb802e7410ee9ac47ca92b193ed0ab17485024fe5 527B / 527B done
#4 sha256:80b5f664ac0c5f6b89608f7b0afd9548ac5b2d4cd631b7b723d9f2edca8676d9 897B / 897B done
#4 ERROR: failed to get dead record sha256:b41143b8fa43fe16600dd95e6ba42ec939e206fcf336cd6990ec59e0afdaf65c: not found
------
 > docker-image://docker.io/docker/dockerfile:experimental@sha256:ee85655c57140bd20a5ebc3bb802e7410ee9ac47ca92b193ed0ab17485024fe5:
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: failed to build LLB: failed to get dead record sha256:b41143b8fa43fe16600dd95e6ba42ec939e206fcf336cd6990ec59e0afdaf65c: not found
2020-07-04 18:50.34: Job failed: Docker build exited with status 1

The build machine was running a docker prune at the time. I guess docker got confused by that somehow. I restarted the jobs and they passed.


Missing scroll bar modifier in tab

Please keep to one feature per pull request. There seem to be a lot of other changes in here.

I do not know how this happened :-( sorry


Add method option to jpeg-recompress for passing in comparison metrics

added compression methods option for passing to jpeg-compress
added String type to option parser and changed Array to String y method option for jpegrecompress
updated changelog
warn when unknown jpegrecompress compression method is specified, and beter explanation for the methods
Made suggested edits
Supersedes: https://github.com/toy/image_optim/pull/103 Sorry for creating another PR, but I don't have write permission to the original branch.
Closes #102
Co-authored-by: Blake Erickson<EMAIL_ADDRESS>

Awesome, thanks! Ignore @houndci-bot, it is using wrong version of rubocop. I'll also need to fix script/update_worker_options_in_readme.

Thank you! I'll try to get to #184 soon

Hi,
@oblakeerickson Great work ! Thanks.
@toy  Could we have a release to use this option ? Thanks

@psyray Release as part of v0.28.0


CSS conflict

There are some CSS class names in the component like "tag", which may conflict with external libraries' CSS, e.g. Bootstrap (there is also a "tag" class). Eventually your "tag" class dominates over the Bootstrap's one so it looks pretty disgusting.
I recommend you to edit your CSS class names adding no-conflict prefixes, for example:
.n2ti-tag {...}

And even better yet, add the possibility to turn off a component theme completely.

Hi @toxa16,
As far as I know the style should not leak as it uses Shadow DOM emulation. I'll try to reproduce

I updated the classes and prefixed them with ng2- :)

Alright, you have earned a star from me :)


Analyzer error stuff

What was wrong?
How was it fixed?
To-Do

[ ] OPTIONAL: Update Spec if applicable

[ ] Add entry to the release notes (may forgo for trivial changes)

[ ] Clean up commit history

Codecov Report

Merging #539 (57ad6e9) into master (f1327bb) will increase coverage by 0.07%.
The diff coverage is 93.47%.

:exclamation: Current head 57ad6e9 differs from pull request most recent head 9dfcb34. Consider uploading reports for the commit 9dfcb34 to get more accurate results

@@            Coverage Diff             @@
##           master     #539      +/-   ##
==========================================
+ Coverage   87.92%   87.99%   +0.07%
==========================================
  Files          87       87
  Lines        5654     5666      +12
==========================================
+ Hits         4971     4986      +15
+ Misses        683      680       -3

Impacted Files
Coverage Δ

crates/analyzer/src/traversal/assignments.rs
66.66% <ø> (ø)

crates/analyzer/src/traversal/declarations.rs
100.00% <ø> (ø)

crates/analyzer/src/traversal/utils.rs
81.81% <82.35%> (-2.19%)
:arrow_down:

crates/analyzer/src/traversal/expressions.rs
90.81% <92.85%> (-1.32%)
:arrow_down:

crates/analyzer/src/namespace/types.rs
73.51% <100.00%> (+0.64%)
:arrow_up:

crates/analyzer/src/traversal/functions.rs
93.65% <100.00%> (+9.03%)
:arrow_up:

crates/analyzer/src/traversal/types.rs
95.58% <100.00%> (+0.13%)
:arrow_up:

crates/parser/src/ast.rs
70.49% <0.00%> (+6.55%)
:arrow_up:

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 f1327bb...9dfcb34. Read the comment docs.


Highlight multiline strings correctly

Fixes #2246.

The playground example still seems off to me, if I'm reading it right? The bottom of the string is colored - I assume it should be black/white.
https://squiggle-website-git-lezer-multiline-quantified-uncertainty.vercel.app/playground?v=0.8.5#code=eNqrVkpJTUsszSlxzk9JVbJSilGKyVNQUFZWVijOz00tycjMS4%2FJy80vSlXIT0MSiskDosxihcwShdSy1DwFDBX29kAlefkZCnn5QIYSiKNUCwAo1ibF

@OAGr you need to switch to "Next" first.
Hmm, should the playground default to Next version?

Hmm, should the playground default to Next version?

Yep, that was it, thanks!


db-sync should not have to maintain ledger state

Currently, db-sync maintains its own copy of ledger state (a huge data struct, more than 10G in size, of which db-sync only needs small chunks) so that if node and db-sync are running on the same machine (recommended practice) you have two copies of the same huge data structure in memory. Fixing this requires extending or adding a new local chain sync protocol from the node that also includes the needed data that db-sync currently extracts from the ledger state.
Another problem with db-sync maintaining its own copy of ledger state is that it makes load balancing and high availability installations much more difficult than if the only external state is the database. I have already discussed this a member of the IOG SRE team, and without ledger state, load balancing and high availability is seemingly trivial, but the extra ledger state files makes this rather difficult.
In addition, just writing the ledger state file to disk currently takes between 4 and 5 minutes and is done every 500 blocks on recommended hardware. While the ledger state file is being stored to disk, no new blocks are added to the database. Obviously this could (at the expense of extra complexity) be done in a separate thread, but it would be much better if we did not have to store ledger state at all.

This is kind of related...
can you clarify why you add the "arch" at the end of the snapshot files? I somehow assumed that maybe the ledger states were not cross-arch compatible... then did a test restore from x86_64 to aarch64 and db-sync was happy and syncing after that...

@reqlez The "arch" is there because that is the only one tested and the only one officially supported.

@reqlez The "arch" is there because that is the only one tested and the only one officially supported.

Ah, good to know. Thanks for the clarification :)


Go package update

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


[Feature Request] Wait for energy like Wait for Boost points

Self explanatory, just it would be nice if we could set up an arbitrary amount of energy to wait for.

Added in https://github.com/tmarenko/mff_auto/commit/69c384ace489c9f9b63bac9167c3b93fcc178365
Released in https://github.com/tmarenko/mff_auto/releases/tag/0.9.4


Add minimal tracing to server framework

This commit adds minimal tracing at the DEBUG level to the
code-generated OperationHandler trait implementations for each
operation, logging the deserialized operation input as well as any
errors. The router also has some minimal tracing to detect requests that
are not routed successfully.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Examples
Successful pokemon-species operation:
2022-04-12T16:59:06.780701Z DEBUG hyper::proto::h1::io: 205: parsed 3 headers
2022-04-12T16:59:06.780743Z DEBUG hyper::proto::h1::conn: 217: incoming body is empty
2022-04-12T16:59:06.781142Z DEBUG router: aws_smithy_http_server::routing: 157: request routed successfully to operation
2022-04-12T16:59:06.781286Z DEBUG request{method=GET uri=/pokemon-species/pikachu version=HTTP/1.1}: tower_http::trace::on_request: 91: started processing request
2022-04-12T16:59:06.781383Z DEBUG request{method=GET uri=/pokemon-species/pikachu version=HTTP/1.1}: pokemon_service: 139: Requested Pokémon is pikachu
2022-04-12T16:59:06.781549Z DEBUG request{method=GET uri=/pokemon-species/pikachu version=HTTP/1.1}: tower_http::trace::on_response: 254: finished processing request latency=0 ms status=200
2022-04-12T16:59:06.781694Z DEBUG hyper::proto::h1::io: 312: flushed 526 bytes
2022-04-12T16:59:06.781850Z DEBUG hyper::proto::h1::conn: 276: read eof

Unsuccessful pokemon-species operation:
2022-04-12T16:59:52.865557Z DEBUG hyper::proto::h1::io: 205: parsed 3 headers
2022-04-12T16:59:52.865598Z DEBUG hyper::proto::h1::conn: 217: incoming body is empty
2022-04-12T16:59:52.865985Z DEBUG router: aws_smithy_http_server::routing: 157: request routed successfully to operation
2022-04-12T16:59:52.866123Z DEBUG request{method=GET uri=/pokemon-species/magikarp version=HTTP/1.1}: tower_http::trace::on_request: 91: started processing request
2022-04-12T16:59:52.866234Z ERROR request{method=GET uri=/pokemon-species/magikarp version=HTTP/1.1}: pokemon_service: 161: Requested Pokémon `magikarp` not available
2022-04-12T16:59:52.866387Z DEBUG request{method=GET uri=/pokemon-species/magikarp version=HTTP/1.1}: tower_http::trace::on_response: 254: finished processing request latency=0 ms status=404
2022-04-12T16:59:52.866532Z DEBUG hyper::proto::h1::io: 312: flushed 206 bytes
2022-04-12T16:59:52.866658Z DEBUG hyper::proto::h1::conn: 276: read eof

Unsuccessful routing:
2022-04-12T17:00:44.832441Z DEBUG hyper::proto::h1::io: 205: parsed 3 headers
2022-04-12T17:00:44.832487Z DEBUG hyper::proto::h1::conn: 217: incoming body is empty
2022-04-12T17:00:44.832733Z DEBUG router: aws_smithy_http_server::routing: 166: request does not match any operation route method=GET uri=/not-found headers={"host": "localhost:13734", "user-agent": "curl/7.79.1", "accept": "*/*"} version=HTTP/1.1
2022-04-12T17:00:44.832898Z DEBUG hyper::proto::h1::io: 312: flushed 82 bytes
2022-04-12T17:00:44.833046Z DEBUG hyper::proto::h1::conn: 276: read eof

The Pokémon Service should change its usage of TraceLayer to configure it so that the request URI is not logged, since it can contain sensitive data.

Closing in favor of https://github.com/awslabs/smithy-rs/pull/1536.


How to locally save the external images from an API?

I'm doing some research and making some demo using react-static.
I found a problem with the images, which is external images from the API instead of the images in CSS or local image for the UI.
For example, I've developed an API with Wordpress basic, there're a lot of posts are returned by that API, sometimes there are a lot of images are returned as "Array" like the following JSON.
{
  "title": "testing title...",
  "content": "testing content...",
  "images": [
    "http://testing.abc.com/images/upload/testing1.jpg",
    "http://testing.abc.com/images/upload/testing2.jpg",
    "http://testing.abc.com/images/upload/testing3.jpg"
  ]
}

Is there any way to download the image and put them into the the <img tag as a relative path instead of absolute path, when we build a static website. So the result should be ...

or (based on the page url route)

instead of

You can use webpack configs to do this but why not just use the images from the wordpress server? Just cache them with cloudflare

Because I need to build a website totally static and offline. Which means even if I put them into a USB and browse it in the computer without network.

Right... so thinking a bit on how you could do this flow in your static config.

Fetch the posts from your api.
Iterate over the posts
Fetch the image(s) for that post and stream the result to a folder (fssync or something).
Pass the resulting file path, .e.g. images/file1.jpg as a prop to the posts route.
Profit!

Yup, it’s what I done exactly

Alternatively, if someone else is looking into this. You could convert the images as a base64 string and pass those along as props. This eliminates the need to save the files locally.
Note: this is only useful for offline sites as this prevents image caching and makes your files rather big for web with all the included base 64-strings.

This process is a genuine candidate to be implemented in a plugin, related to #1130 issue, maybe a component that automatically download images in a static directory depending of they use.


Feature: Spotlight Ellipse

Should be very straightforward. Will do last before 1.0.0, see if #10 is still applicable and make this an easy addition from that refactor

Closing this in favor of continue discussion in #22


Error: Expected Bool when selecting configuration.YAML

Describe the bug
Updated from an earlier release to v24.08.18
I was using a custom_configurations.yaml before trying to change to this yaml.
Screenshots

Metadata:
Version: v24.08.18
Any idea what to do to solve the problem?

Solved the problem by deleting the integration and adding and reconfiguring it 👍


Unknown transformer transformerName specified in optional

I added this gem to my gem file (in addition to bootstrap-sass), so gem file currently has these bootstrap files:

I updated my application.js so that it now has:
//= require jQuery
//= require jquery_ujs
//= require tether
//= require bootstrap-sprockets
//= require turbo links
//= require react
//= require react_ujs
//= require react_bootstrap
//= require components
//= require_tree .

When I save all of this and try to reload a page that was previously rendering, I get this error:
ExecJS::ProgramError at /app_roles
ReferenceError: Unknown transformer transformerName specified in optional
The app_role.es6.jsx file has:
[class AppRole extends React.Component {
render () {
return (

Title: {this.props.title}
Display Name: {this.props.displayName}
Category: {this.props.category}

);
}
}
AppRole.propTypes = {
title: React.PropTypes.string,
displayName: React.PropTypes.string,
category: React.PropTypes.node
};
](url)
Is there something else I need to do to be able to use bootstrap with react?
Thank you

This gem is not maintained anymore. Sorry about that.


@nuxt-vitest throws ERR_INVALID_URL when using setup() from @nuxt/test-utils in spec

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.4.3
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
In https://stackblitz.com/edit/github-wtj3ft-nhb1dj?file=app.spec.js,nuxt.config.ts,app.vue,vitest.config.js,package.json
create a new terminal and run:
yarn run vitest

Describe the bug
https://nuxt.com/docs/getting-started/testing#testing states to test context option one should use await setup
using that setup throws the error
Error while requiring module `nuxt-vitest`: TypeError [ERR_INVALID_URL]: Invalid URL

Additional context
To migrate from nuxt2 to nuxt3 we replace fetch with useAsyncData. To minimise migration work we register an axios instance via a plugin to the nuxt context and return data inside useAsyncData
In order to mock the axios registered to useNuxtApp() we use the method described in https://nuxt.com/docs/getting-started/testing#testing
Logs
yarn run v1.22.19
$ /home/projects/github-wtj3ft-nhb1dj/node_modules/.bin/vitest run

 RUN  v0.30.1 /home/projects/github-wtj3ft-nhb1dj

stdout | unknown test
<Suspense> is an experimental feature and its API will likely change.
setup

 ❯ app.spec.js  (1 test) 578ms
stdout | unknown test
<empty line>

 Test Files  1 failed (1)
      Tests   (1)
   Start at  15:26:17
   Duration  2.69s (transform 170ms, setup 0ms, collect 343ms, tests 578ms, environment 510ms, prepare 219ms)

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

You shouldn't use both nuxt-vitest + nuxt/test-utils in the same file. They are two different approaches - you can have them both in the same project but they need to run in different environments.
Here is your reproduction, updated to use both:
https://stackblitz.com/edit/github-wtj3ft-jqheul?file=app.unit.spec.ts,app.nuxt.spec.ts,package.json
A PR to improve the docs in this regard would be very much appreciated.


REST APIdocs from SpringDoc are missing & not available via egeria chassis

https://localhost:9443/swagger-ui.html
is currently returning a whitelabel error page.
The swagger doc is not working
This is occuring in master & 2.3

Error shown is
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.

Tue Sep 29 13:07:15 BST 2020
There was an unexpected error (type=Not Found, status=404).

Checking further, the official built docker images are all working fine across release 2.2, 2.3 & master. In all cases the REST APi docs are displayed.
The problem is isolated to my local build and could be a specific issue there. Will investigate more but not treating as an issue for the 2.3 release

This is working now and can be closed


Mul: use different operation for ALTOP

The current MUL ALTOP doesn't use the rs1, rs2, rd, and shift signals to calculate pcpi_rd, but bypassed them completely and uses pcpi_rs1 and pcpi_rs2 instead.
I believe that weakens the strength of the formal proof considerably?
With this PR, I only replace the multiply operations by an addition that covers all the bits, but leave everything else the same.
This way, all signals are covered and there is no need for the magic numbers.
Disclaimer: I'm still very green when it comes to this kind of formal stuff, so I may be missing something fundamental.

The "magic numbers" are there to be able to distinguish the different operations.

I believe that weakens the strength of the formal proof considerably?

It would be great if you would have said why you think this is so. I don't think this is the case at all.

The "magic numbers" are there to be able to distinguish the different operations.

Yes. And they are entirely unnecessary if you replace the multiply operation which is sensitive to signed vs unsigned inputs, by a different operation that is also sensitive to signed vs unsigned input.

It would be great if you would have said why you think this is so. I don't think this is the case at all.

Likewise, it would have been great if if you'd have read the first sentence of my original comment, because it explains exactly why I think my proposal is stronger:

The current MUL ALTOP doesn't use the rs1, rs2, rd, and shift signals to calculate pcpi_rd, but bypasses them completely and uses pcpi_rs1 and pcpi_rs2 instead.

But I'm more than happy to explain it some more:
Just delete the following two sections from the picorv32 RTL. That's right: completely delete it.
Now run your formal proof on any mul instruction: they'll just pass.
The RTL of your ALTOPS path bypasses all the code that deals with unsigned to signed conversion, which is an essential part of the multiply module.
My proposal doesn't do that. My proposal is also a much smaller change, in that it replaces only the multiply operations and nothing else.
That said, my original patch wasn't perfect, since it didn't catch signed/unsigned issues for MUL, only for MULH, MULHU, and MULHSU. I have amended my proposal to fix that too.

Just delete the following two sections from the picorv32 RTL

Obviously you have completely misunderstood what ALTOPS is for.

Obviously you have completely misunderstood what ALTOPS is for.

Since verifying a multiplier can be time consuming for formal verification, it's not uncommon to replace it with a simpler operation while keeping as much of the surrounding logic the same. That ensures a minimal reduction of coverage.
The documentation says the following:

In order to still be able to verify things like bypassing for the arithmetic units performing those operations we define a set of alternative arithmetic operations.

If you define "alternative arithmetic operations" as "the multiplier operation (and the multiply operation alone!)", my proposal fits that description.
You obviously had a different intent.
So be it.

When ALTOPS are enabled that means you do not want to verify the arithmetic unit itself. That's the whole point. We want the proof to be independent of that data path. This just demonstrates that ALTOPS is in fact accomplishing what it is designed to do.

My proposal can be independent of the data path just like yours. After all, it's just a different function.
If a particular RTL implementation can't be coaxed into the structure of the PicoRV32, you could still have your case statement that has its own formula for each instruction. Like this:
  assign pcpi_rd =
    instr_mul  ? ($unsigned({1'b0, pcpi_rs1, 1'b0, pcpi_rs1}) + $(unsigned({1'b0, pcpi_rs2, 1'b0, pcpi_rs2}))>>2 :
    instr_mulh ? ($signed({pcpi_rs1[31], pcpi_rs1, pcpi_rs1[31], pcpi_rs1}) + $(signed({pcpi_rs2[31], pcpi_rs2, pcpi_rs2[31], pcpi_rs2}))>>34 :
    ...

In other words, you don't lose anything by using my proposal, but you win the ability to increase the coverage when the possibility is there. (And if you're going to use a full multiplier for a RISC-V core, chances are high that you will always use an architecture that first normalize the unsigned inputs to a signed one.)
Tom

In other words, you don't lose anything by using my proposal

What we would loose is consistency. We'd have one ALTOPS definition for multiplies and other definitions for divide/ floating point/etc.

while keeping as much of the surrounding logic the same.

No. We keep the datapath to and from the special function unit intact. There is not much to gain by trying to preserve parts of the special function unit itself and everything to lose. If you are interested in getting formal assurances for your special function unit then you should run additional formal tests on that unit in isolation.
Most special-function units will have a data-dependency that influences the runtime for an operation. Preserving this dependency exactly would keep too complicated arithmetic in the proof. Replacing it with a different timing will weaken the proof. Therefore the most reasonable approach is to replace the special function unit with something that implements ALTOPS in terms of data output, but is an abstraction of the original core in terms of timing. The rocket MulDiv core I linked above is a good example for this. In such a scheme none of the existing logic inside the special function unit would survive, so using different ALTOPS schemes for different groups of operations would just unnecessarily complicate writing those replacement cores and limit code-reuse for those cores.


Reference error: io is not defined

I'm getting this error when I launch my app. I notice in the bower_components/ember-data-sails-adapter/ember-data-sails-adapter.js file io is not defined, but /global io/ is at the top of the scrip?
Where are you expecting io to be instantiated?

The global io. Comes from the http://sailsjs.org/#/documentation/anatomy/myApp/assets/js/dependencies/sails.io.js.html provided by sails.js.

This can be a client-side error as well.
The Ember adapter depends on a global io, but it's not specified in bower.json as a dependency.


Fix too strict handling without "otherwise" condition

fixes #38
ignore private tags during validation

Codecov Report

Merging #40 (eac14b8) into main (5a49607) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage   87.97%   87.97%
=======================================
  Files          14       14
  Lines        1489     1489
=======================================
  Hits         1310     1310
  Misses        179      179

Files Changed
Coverage Δ

dicom_validator/spec_reader/condition_parser.py
98.88% <ø> (ø)

dicom_validator/validator/iod_validator.py
93.03% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


feat: :sparkles: migrated npm to pnpm

Closes #343

:rocket: This pull request is included in v3.7.0. See Release 3.7.0 for release notes.