TTL is cached

It seems the original TTL of records is cached and returned identical in each subsequent query response
Meaning, a record with a 24-hour TTL that was cached 23 hours ago and is queried now, looks to the client as if it will be fresh for the next 24 hours, even though it is only fresh for another hour.
Is this intentional? It's unlike every piece of DNS software I've used before, which update the ttl in each query so that downstream caches will expire at the same time as its own cache does

Client (at least dnscrypt-proxy) have their own cache (with decreasing TTLs).
Serving the real TTL is intentional in order to avoid a burst of queries every time a popular name is close to expiration.
When caching resolvers are chained, decreasing TTLs doesn't really make sense. It will only increase traffic utilization.
Not decreasing TTLs in intermediate caches is equivalent to having a local resolver without intermediates.
It would be different if encrypted-dns-server was the only cache in the chain.

Client (at least dnscrypt-proxy) have their own cache (with decreasing TTLs).

Right, but they start counting down when they talk to encrypted-dns-server, not when the authoritative server was queried. So the effective TTL is the TTL the client sees + however long this record has been in encrypted-dns-server's cache. Which in this case is usually more than the TTL the zone owner had set.
If a long enough chain of caching resolvers can keep telling the next one down that a record is fresh for the next TTL seconds when the last time the authoritative name sever was queried was potentially several TTLs ago, how could any zone administrator trust that their records have propagated?
Granted, the RFCs aren't clear on this and could be interpreted either way, but I really feel like the effective TTL shouldn't depend on how many caches there are between the client and the authoritative server.

traffic

I can understand that caches expiring all at once would create a spike in queries but then why do other caching resolvers tick down TTL?

Not decreasing TTLs in intermediate caches is equivalent to having a local resolver without intermediates.

I don't understand this part.


Hide autograding results until submission is manually graded

You may want to ignore whitespace changes when reviewing this PR.
Description
Hide autograding results until submission is manually graded.
The profile tab needs to be updated too. @Aulud
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test
Look at an assessment that has been autograded but not manually graded.
Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 7487

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 33.148%

Totals

Change from base Build 7452:
0.07%

Covered Lines:
2287

Relevant Lines:
6403

💛  - Coveralls


Feature: mint tokens on payable execution

@BritikovKI Can you elaborate what this is about? Yesterday I thought I understand what is meant, but today I do not anymore :D

Srry, actually I just created an issue inside of the wrong repo 😅


mget 503 error

mget error 503 ,but no any words.

I test data by postman . it is ok。

Hello, I'll need more information to be able to help. First thing, can you paste the code as text, using the "```" Markdown format, so I have a chance to try it out. Second thing, can you post the error response returned from Elasticsearch? (Use res.String() to obtain it easily.)

the 503 error  is what  link els is error.
version:v8
code  :
con := fmt.Sprintf("http://%s:%s", ela.Addr, ela.Port) 	cfg := elasticsearch.Config{ 		Addresses: []string{ 			con, 		}, 	} 	es, err := elasticsearch.NewClient(cfg) 	client = es 	res, err := client.Info() 	if err != nil { 		log.Println(res) 	}

Hello, I'll need more information to be able to help. First thing, can you paste the code as text, using the "```" Markdown format, so I have a chance to try it out. Second thing, can you post the error response returned from Elasticsearch? (Use res.String() to obtain it easily.)

the 503 error is what link els is error.
version:v8
`
con := fmt.Sprintf("http://%s:%s", ela.Addr, ela.Port)
cfg := elasticsearch.Config{ Addresses: []string{ con, }, }
es, err := elasticsearch.NewClient(cfg) client = es res, err := client.Info()
if err != nil { log.Println(res) }`

the 503 error is what link els is error

I'm sorry, but what does that mean? What is the full response returned from Elasticsearch, not just the status code?

the 503 error is what link els is error

I'm sorry, but what does that mean? What is the full response returned from Elasticsearch, not just the status code?

thanks . I solve  the question. way
I change version yesterday。

So by adapting the example, everything works as expected?

So by adapting the example, everything works as expected?

yes. sorry.
I forgot changing sdk's version.

Glad to hear that! Closing the issue as solved then...


Updates for MOC-in-news section of web site

Hi,
We should start gathering up talks we, OCT, and affiliated projects have given so we may update the https://massopen.cloud/moc-in-news/ pages.
Perhaps something like this:
Dear MOC Alliance Partners,

We are updating the 'MOC in News' section on our website. We kindly request details of any talks or papers you have given or published since September 2022.

Please provide the following:
   1.	Title of Talk/Publication
   2.	Date of Talk/Publication
   3.	Venue (if applicable)
   4.	Brief Description (2-3 sentences)
   5.	Link to the Publication/Talk (if available)

You can reply directly to this email with the information.

We appreciate your help in keeping our website up-to-date with the latest contributions from our alliance partners.
Best Regards,

Also, perhaps we should include a form so they may start entering them as they occur?
This should also include Kristi Nikolla who has represented us at a few conferences this year.
Thanks!

@msdisme do you have a list of folks this should go out to? or just the leads for each project (and Kristi)?

Orran, Peter, Zink, Kristi, Hakan (who is giving a poster in 2 weeks).  Ask profs about any students to include in MOC A related stuff.


feat(query/mock): create a mock object for the query interface

This is an implementation of flux.Query which is the asynchronous one. I think you're thinking of flux.ResultIterator which is the synchronous version of this interface.


xds: create clusters per HttpRoute (API)

Deduplicate cluster creation by creating a cluster per HttpRoute (API). With the current implementation we use the backendRefs list in the spec.rules and all the backends listed are added as load balance endpoints in the cluster.
Fixes: #551
Signed-off-by: Lahiru De Silva<EMAIL_ADDRESS>

@NomadXD can you get CI to pass and fix the merge conflicts?

@NomadXD can you get CI to pass and fix the merge conflicts?


Grafana Dashboard

Any Grafana dashboard that I can use with this exporter?

@tegk https://grafana.com/grafana/dashboards/11423

Fixed by #17


Error when run make check

Version: 1.21.0
Platform: UNIX
ok 333 - we_get_signals
ok 334 - we_get_signals_mixed
FAIL: test/run-tests
======================================================
1 of 1 test failed
Please report to https://github.com/libuv/libuv/issues
======================================================
Makefile:4622: recipe for target 'check-TESTS' failed
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory '/home/trungtq/Downloads/libuv-1.21.0'
Makefile:4878: recipe for target 'check-am' failed
make: *** [check-am] Error 2

What did i get error? How to fix it?
Thank :)

@trungkstn can you paste the full output somewhere so we find out what test is failing? Thanks!

not ok 103 - getaddrinfo_fail
# exit code 134
# Output from process `getaddrinfo_fail`:
# Assertion failed in test/test-getaddrinfo.c on line 43: status < 0
not ok 104 - getaddrinfo_fail_sync
# exit code 134
# Output from process `getaddrinfo_fail_sync`:
# Assertion failed in test/test-getaddrinfo.c on line 117: 0 > uv_getaddrinfo(uv_default_loop(), &req, NULL, "xyzzy.xyzzy.xyzzy.", NULL, NULL)

this is error. help me :(


Possible to transfer the IOS Backup to Android? (extracted WhatsApp Files already)

Hey there!
I keep searching the whole day to transfer my IOS WhatsApp Backup to Android, I was able to extract my WhatsApp Files fine.
Just curious, if I somehow can "pack" them, to make Android use it?

Theoretically yes. You can. But in practice, there are a lot to do to adopt the schema differeces between iOS and Android.

Since Android Encrypts it? I'm just trying to find a way, I am fine with packing stuff etc. and move it to Gdrive or so.
Would you mind, putting a list or so? If you know how?
Because I refuse to use any of this Chinese bloatware just to copy my WhatsApp messages.

Not because of encryption. The databases of iOS and Android use a totally different schema to store their message, which is also why this project separates the processing of both platforms into multiple script files, although I am considering merging them.
Before doing it ourselves, have you tried https://faq.whatsapp.com/1295296267926284/?
PS. It is always good to refrain from using any Chinese bloatware.


Add Stakater as KCSP

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
can not read a block mapping entry; a multiline key may not be an implicit key at line 5253, column 25:
                homepage_url: 'https://stakater.com/'
                            ^

Deploy preview for landscape failed.
Built with commit d48bc93f84fdeae47569b49cb28fb211909e5572
https://app.netlify.com/sites/landscape/deploys/5e7570c1c0cd33000806078b

LGTM


About the availability of pretraining labels of MOFTransformer

Really SORRY to ask questions that are not related to this project. I was in a hurry because of the deadline for revising my paper. I'm wondering if you could kindly send me the MOC, VFP, MTP labels data of MOFTransformer. I've emailed the authors but still get no reply. Thanks very much!

Really SORRY to ask questions that are not related to this project. I was in a hurry because of the deadline for revising my paper. I'm wondering if you could kindly send me the MOC, VFP, MTP labels data of MOFTransformer. I've emailed the authors but still get no reply. Thanks very much!

My Email is<EMAIL_ADDRESS>or<EMAIL_ADDRESS><EMAIL_ADDRESS>Thanks very much!


Add rule for host IP

Add a rule to the dpdk pipeline for forwarding the packets to/from host IP. Forward them via the default host interface and its port id.
How to get the host IP from the inframanager pod?
Kubernetes populates the pod object in the apiserver with
spec:
nodeName: node1
status:
podIP: <IP_ADDRESS>
hostIP: <IP_ADDRESS>
Here hostIP is the nodeIP on which the pod is running on.
Inside the inframanager pod, read the node IP from the pod object and use it for programming the forwarding rules.
Signed-off-by: Venkatesh Petla<EMAIL_ADDRESS>

Due to severe merge conflicts, created another PR with the same changes
https://github.com/ipdk-io/k8s-infra-offload/pull/42.
This pull request is no longer valid.


List all Billing Managers for the Organization documents invalid query parameter

The API documentation for List all Billing Managers for the Organization describes a organization_guid filter. This filter is invalid as the organization_guid is included in URI instead.

Will be addressed once https://github.com/cloudfoundry/cloud_controller_ng/commit/ebbae0ab4bad7d1ce8fec3402812c45e352d4210 makes it into a cf-release.
You can find docs that include this change at
http://s3.amazonaws.com/cc-api-docs/104228398/index.html


Subtitle partitioning not working

My existing documents with subtitle partitioning, e.g = Main title:Subtitle now (beta 6) is tranlated to main title "Main title:Subtitle". Should be main title "Main title" and subtitle "Subtitle".
Can't find any other open issues or changelog notes related to this.

You seem to be missing a space after the separator, which is required.
= Main title: Subtitle

That has always been a requirement to my knowledge. It's also something that is handled by core, not by Asciidoctor PDF.

The user manual states:

Note that a space is always appended to the value of the title-separator (making the default value of the title-separator effectively a single colon).

I am also experiencing this issue, using = title: subtitle does not seem to work

Yes, you are correct. The example I gave was incorrect, my documents have this space. Why this was not working for my existing documents I am not sure. I suspect that maybe my byild configuration at some point was changed so that :doctype: was article, not book. When :doctype: article the issue is still there, but perhaps more of an intended behavior. I'l close the issue as my problem is resolved.

Reopen as I just saw PascalDutch's comment. @PascalDutch I think the behavior is different related to :doctype: but I can't be sure if subtitle worked before when :doctype: article. Do you?

I use :doctype: book and it is not working. I can't tell if it ever worked with :doctype: article since I have never used that type.

I suspect that maybe my build configuration at some point was changed so that :doctype: was article, not book.

The default doctype in Asciidoctor PDF has always been article (as it is for all converters). The difference is that the article doctype is now fully respected, which means the title joins the first page of the body instead of on a separate page.

I can't find any documentation specifying the correlation between support for subtitle partitioning and doctype attribute.

Subtitle partitioning is only supported in Asciidoctor PDF when the title page is used (either the doctype is book or the title-page attribute is set).

When :doctype: article the issue is still there, but perhaps more of an intended behavior.

As of now, that is by design. If you'd like subtitle partitioning to work for the article doctype, please open a separate issue with that subject.

I use :doctype: book and it is not working.

I don't believe this to be true as we have tests that verify it does work. Please provide a complete example so that we can determine if there's a use case being overlooked by the test suite.

Here is my configuration, the AsciiDoctor root file (there might be some Dutch words in the text):
= Aansturing actuatoren
:title: Aansturing actuatoren
:version: 0.1
:update: 16 oktober 2019
:version-label: Versie
:author: Pascal
:mail<EMAIL_ADDRESS>:last-update-label: Laatst geüpdatet
:bibliography-database: db_citaten_stage.bib
:bibliography-style: apa
:bibtex-style: apa
:bibliography-tex-style: numeric
:bibtex-order: appearance
:title-logo-image: image:img1.png[pdfwidth=4.25in,align=center]
Pascal<EMAIL_ADDRESS>v{version}, {update}
// :organization: someOrganization
:doctype: book
:front-cover-image: image:img2.png[]
// Settings:
:experimental:
:reproducible:
:icons: font
:listing-caption: Listing
:sectnums:
:toc: macro
:toclevels: 3
:toc-title: Inhoudsopgave
:chapter-label:
:stem: latexmath
:align-text: left

//Captures
:appendix-caption: Bijlage
:caution-caption: Waarschuwing
:example-caption: Voorbeeld
:figure-caption: Figuur
:image-caption: Afbeelding
:important-caption: Belangrijk
:last-update-label: Laatst geupdate
:note-caption: Notitie
:table-caption: Tabel
:untitled-label: Ongetiteld
:version-label: Versie
:warning-caption: Waarschuwing
:preface-caption: Samenvatting

ifeval::["{asciidoctor-version}" < "1.5.7"]
:legacy-footnoteref:
endif::[]
ifdef::backend-pdf[]
:pdf-theme: onderzoekSjabloon-theme.yml
:pdf-themesdir: sjablonen
:source-highlighter: coderay
endif::[]

//:rouge-style: github]

// Voorblad
include::voorblad.adoc[]

// Versiebeheer
include::versiebeheer.adoc[]

// Samenvatting
include::samenvatting.adoc[]

toc::[]

// Verklarende woordenlijst
include::woordenlijst.adoc[]

include::inleiding.adoc[]

include::hoofdstuk1.adoc[]

include::hoofdstuk2.adoc[]

== Bronnen
[.text-left]
bibliography::[]

YAML file (I think this theme might be the problem):
extends: default
page:
  layout: portrait
  margin: [0.75in, 1in, 0.75in, 1in]
  size: Book
base:
  font-color: #333333
  font-family: Noto Serif
vertical-spacing: $base-line-height-length
header:
  font_color: 999999
  height: 0.5in
  recto:
    columns: "<40% =20% >40%"
    right:
      content: '_{organization}_'
    center:
      content: image:img.png[pdfwidth=0.50in]
  verso:
    columns: $header_recto_columns
    left:
      content: $header_recto_right_content
    center:
      content: $header_recto_center_content
heading:
  font-color: #262626
  font-size: 17
  font-style: bold
  line-height: 1.2
  margin-bottom: $vertical-spacing
link:
  font-color: #333333
  # font-style: bold
outline-list:
  indent: $base-font-size * 1.5
  text-align: left
footer:
  height: 0.45in
  recto:
    right:
      content: '{section-or-chapter-title} | {page-number}'
  verso:
    left:
      content: '{page-number} | {chapter-title}'

Using with:
Asciidoctor PDF 1.5.0.beta.6 using Asciidoctor 2.0.10 [https://asciidoctor.org]
Runtime Environment (ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

The subtitle is not working because you are overriding the title using:
:title: SomeTitle

Take that away and it will work.

It works, such a simple fix. Thanks for the support!

Excellent!

Hi
I'm experiencing a similar issue.
test.adoc
= Main title: Subtitle

content content

When running asciidoctor-pdf test.adoc I get such output:

$ asciidoctor-pdf --version
Asciidoctor PDF 2.2.0 using Asciidoctor 2.0.17 [https://asciidoctor.org]
Runtime Environment (ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

Any help?


A few observations on existing cookie APIs

This is a follow-up of https://github.com/WICG/async-cookies-api/issues/31#issuecomment-239707182. I am just opening a new issue so that we don't keep the discussion in an unrelated one.
This is a response for @bsittler observations.

I'm glad to see this isn't the only API that tries to change the default path for Set-Cookie 😄

This has come after much push back from js-cookie team. We just conceded because it was proven with many reports over the years that the default path rules violate the Principle of Least Astonishment for developers that work with cookies.
jQuery cookie didn't changed the Path until the version 2.0. See this issue for some reported links and context on why that decision was made.
Answering to @bsittler questions:

Also, why synchronous? Is using await ... and/or .then(...) problematic for some reason?

Not at all, it is just that I thought it might make sense to have a synchronous API for compatibility purposes. Many implementations have a similar interface and they are pretty well established in the ecosystem:

https://github.com/ScottHamper/Cookies
https://github.com/florian/cookie.js

This issue sums up very well why we should refrain from creating different APIs. In the last versions, js-cookie tried to be as similar as possible to the interface of other similar implementations to be more portable.
If there's a way to fix the problems that drove the creation of this proposal with a new cookie API that fixes a multitude of other problems (like the encoding issues), then I guess we could leverage this to do that too. Although I still need to understand in details what is the problem that drove the creation of this proposal.
I don't think that being asynchronous by default even when asynchronicity is not necessary would cause any harm other than unnecessary .thens everywhere, but that's just theoretical purity.

Are there other event handlers that need to be blocked/prevented from firing until the cookie operation completes?

Even handlers from which kind? AFAIK there's no event handler in the synchronous document.cookie API, it is just I/O. I probably didn't understand the question.

Or is this primarily due to a desire to use it in the inner implementation of pre-existing APIs already exporting script-blocking APIs for cookie operations?

If we could build something that mimics the behavior of an API like js-cookie we could gradually make it cease to exist. There's enough evidence that the features it supports are useful in the wild.
Besides that, there's no need to implement asynchronicity for a synchronous API if there is another standard equivalent that fixes the same issues. The problem is that if the standard don't address things like encoding issues or allows encoding to be overridden for server-side compatibility (like js-cookie converters), then we would need to keep abstracting document.cookie and the new low-level asynchronous API in a library that complements with the features lacking in the standard.
It would be awesome if we could dedicate the effort to fix the document.cookie API. Would it make sense?

Async removes the storage mutex from blocking the thread and also allows adding transactional features later if desired. See e.g. https://lists.w3.org/Archives/Public/public-whatwg-archive/2009Sep/0083.html
Async also allows browsers to put UI (e.g. permission prompts) between the calling function and access to the cookie capabilities without interrupting non-cookie-dependent parts of a page.
And finally the move out of "document" allows it to run in a service worker which has no "document", and which also cannot block event handling without negatively impacting web page/app performance due to being in the critical path for fetch interception.

However, if this async cookies API proposal were to become clearly specified, widely implemented, and made available across most modern web browsers I believe it would become a viable alternative to document.cookie and would also reduce the difficulty of implementing cookie support cleanly in the script-driven parts of a web application.

Detaching the cookie API from document.cookie looks good in theory mostly for the last part "would also reduce the difficulty of implementing cookie support cleanly in the script-driven parts of a web application".
In this case, would the cookies still be sent on every HTTP request? If yes, since it would be async, wouldn't it make it easier for some race condition to happen when the developer sets a cookie to be sent on every HTTP request?
By the way, is there a list with a TL;DR of the problems that were discussed but nobody could reach a reasonable conclusion yet?
PS.: My main point of before was mostly about this API interface (getAll(), etc.) that goes against the way most cookie libraries interface are defined, not about the feasibility of async cookies. Since this is a sketch, does it mean that this API interface is not final and it could be possible to be changed in the future? I ask this because if we use the same interface as other cookie libraries and just add async capabilities (like Cookies.get(key).then((value) =>)), then it will be easier to slowly move from js-cookie, for example, to a standard spec.

@FagnerMartinsBrack In case you're still interested, I've recently updated the explainer to reflect the current experimental shape of what we've implemented in Chrome.
Regarding raciness -- yes, it is quite possible to use this API in a racy way. https://github.com/WICG/cookie-store/blob/gh-pages/explainer.md#data-races cover a few examples. At the same time, note that you can get the same raciness from two fetch API calls, one of which invokes a server-side API that sets a cookie.
Regarding ability to change the API -- we plan to start an Origin Trial in Chrome soon, the point of which would be to get feedback from developers, and use it to improve the API. If you're interested, you can use the Experimental Web Platform Features flag today with Canary to try to build against this API. We'd welcome your feedback.
I'm going to close this issue, as it's fairly high level and doesn't seem to have anything specific to the concrete shape of the current API. If you have concrete feedback for the current API shape, please don't hesitate to open new issues.


Crash:  Container.swift line 299 Container.resolve<A, B> (entry : ServiceEntryProtocol, invoker : (B) -> Any) -> A?

Recently I have started getting crash when trying to resolve an object. Following is the crash logs. I can see that in Container.swift at line 299  guard let currentObjectGraph = currentObjectGraph else { fatalError() } the application is not getting currentObjectGraph and it fails. What can be the probable cause?
In my project, I have a global level assembler which adds all the Assembly from different frameworks. But when I am trying to resolve an object it's giving the crash. This is an intermediate issue:-
#15. Crashed: com.apple.NSURLSession-work
0  libswiftCore.dylib             0x109a1b95c specialized _assertionFailure(_:_:file:line:flags:) + 97848
1  Swinject                       0x1096d4994 Container.resolve<A, B> (entry : ServiceEntryProtocol, invoker : (B) -> Any) -> A? (Container.swift:299)
2  Swinject                       0x1096d2e54 Container._resolve<A, B> (name : String?, option : ServiceKeyOption?, invoker : ((B) -> Any) -> Any) -> A? (Container.swift:192)
3  Swinject                       0x1096d582c Container.resolve<A> (A.Type, name : String?) -> A? (Container.swift:281)
4  Swinject                       0x1096d5918 ContainerSwinjectResolver (Container.swift)
5  Commons                      0x10661e268 specialized static NetworkInterceptor.canInit(with : URLRequest) -> Bool (NetworkInterceptor.swift:67)
6  Commons                      0x10661c084 @objc static NetworkInterceptor.canInit(with : URLRequest) -> Bool (NetworkInterceptor.swift)
7  CFNetwork                      0x1822ec64c -[__NSURLSessionLocal _protocolClassForRequest:] + 188
8  CFNetwork                      0x1822ec7f4 -[__NSURLSessionLocal _request:isCacheEquivalentTo:] + 64
9  CFNetwork                      0x1822ec9c8 -[__NSURLSessionLocal _cfurlRequest:isCacheEquivalentTo:] + 172
10 CFNetwork                      0x18234fcc8 __CFURLCache::checkMemoryCache(__CFString const*, _CFURLRequest const*, NSURLSession const*) + 188
11 CFNetwork                      0x18234bfd0 __CFURLCache::CopyResponseForRequestWithCompletionHandler(_CFURLRequest const*, bool, NSURLSession const*, void (_CFCachedURLResponse const*) block_pointer) + 316
12 CFNetwork                      0x1824e4020 CFXURLCache::getResponseForTask(NSURLSessionTask const*, unsigned char, void (_CFCachedURLResponse const*) block_pointer) const + 84
13 CFNetwork                      0x18244a578 URLConnectionLoader::_loaderEvent_StartLoad(NSURLSessionTask const*) + 1116
14 CFNetwork                      0x18238007c -[__NSCFURLLocalSessionConnection withLoaderOnQueue:] + 72
15 CFNetwork                      0x1823806a4 -[__NSCFURLLocalSessionConnection _tick_initialize] + 92
16 CFNetwork                      0x18237fc24 __71-[__NSCFURLLocalSessionConnection initWithTask:delegate:delegateQueue:]_block_invoke + 40
17 libdispatch.dylib              0x1816dea54 _dispatch_call_block_and_release + 24
18 libdispatch.dylib              0x1816dea14 _dispatch_client_callout + 16
19 libdispatch.dylib              0x1816e896c _dispatch_queue_serial_drain$VARIANT$mp + 528
20 libdispatch.dylib              0x1816e92fc _dispatch_queue_invoke$VARIANT$mp + 340
21 libdispatch.dylib              0x1816e9d20 _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 404
22 libdispatch.dylib              0x1816f203c _dispatch_workloop_worker_thread$VARIANT$mp + 644
23 libsystem_pthread.dylib        0x181986f1c _pthread_wqthread + 932
24 libsystem_pthread.dylib        0x181986b6c start_wqthread + 4

Crash log suggests, that you are resolving instances from different than main thread which may be the source of the problem as Container is generally not thread safe. Are you using Container.synchronize()?
.. I see that you have also opened SO question. I'd prefer to discuss the issue here, as it is a bit easier.

@jakubvano I am not using Container.synchronize(). The way i am using assembler is i have multiple modules which i am combining at AppDelegate level with an Assembler. and that instance of assembler is passed back to each module. Through which i am resolving. In the above scenario I am trying to resolve on a diff thread than main-thread. Which is the cause of the issue. Is there a better way to use this?

I see, unfortunately, assembler by itself currently does not support thread safe access (#221). One way you could work around that would be
let synchronizedResolver = (assembler?.resolver as? Container)?.synchronize()

and use this synchronizedResolver instance every time you need to resolve a type.

@jakubvano Sure thanks. Will do that

@jakubvano Still getting the same issue. Sometimes. The issue is more prominent after swift4.1.

I am have implemented URLProtocol for intercepting network calls and log it. There are some dependencies which i am trying to resolve in public override class func canInit(with request: URLRequest) -> Bool function. Code below:-
public override class func canInit(with request: URLRequest) -> Bool {

       // need to resolve using synchronize because it will run on a diff thread
       if let synchronizedResolver = (CommonKit.assembler?.resolver as? Container)?.synchronize(),
           let config = synchronizedResolver.resolve(HTTPLoggerConfigurationType.self) {
           configuration = config
       }

      // Do something here
       return true
   }

It is always crashing here
 guard let currentObjectGraph = currentObjectGraph else { fatalError() }
But this is only the piece of code which is not running on UI thread while resolving

@jakubvano I did some investigation on this. Even after using synchronize() func there is some threading issue. For which i started using Thread Sanitizer. Which reported that there is a Thread Race detected at:-
fileprivate func incrementResolutionDepth() {
        if resolutionDepth == 0 && currentObjectGraph == nil {
            currentObjectGraph = GraphIdentifier()
        }

I think due to which i am getting this issue.
Also if i put my resolve block of code into   DispatchQueue.main.async. The Thread Sanitizer doesn't cry with the same issue. I think after using synchronize() method over container the entire operation is not thread safe. Can u please check and let me know.

@jakubvano any updated?

Are you using .synchronized() resolver in the other calls (on the main thread) as well? Intended use is to create one instance of synchronised resolver, and use it for all resolve() calls.
Basically, synchronised resolver wraps resolver() calls in the lock based on Container which only works if all the resolve() calls are using the same lock.

@jakubvano Thanks for this info. I got your point.

👍 I'm glad that you've managed to solve this issue.

I am still getting this error after updating to 2.4.0 and SwinjectStoryboard 2.0.1

@fans3210 It should not be necessary to use synchronised resolver for the nested resolutions, only for the one initiating the object graph.
So in your case you should use
container.register(SomeClass.self) {  SomeClass(config: $0.resolve(Config.self)! }

@jakubvano , thanks, but that would be strange since I'm also facing issue of guard let currentObjectGraph = currentObjectGraph else { fatalError() } sometimes. Not often, but sometimes.
My app is a chat app and I'm using asyncdisplaykit which generate nodes in background thread to optimize the UI renderings.

@fans3210 If you are indeed using single globalThreadSafeResolver on all threads, this is probably some weird bug in Swinject implementation. Unfortunately, it will be quite difficult to pinpoint the problem without reproducible example...

Isn't it possible, that you are keeping an instance of Resolver obtained by constructor in factory closure? Something like
container.register(ServiceProvider.self) { ServiceProvider(resolver: $0) }

That might explain the issue

@jakubvano . Nope. I used a lazy threadSafeResolver in my chatvc to resolve all the cell nodes. Currently I only use it to resolve. In the factory closure, I'm using the one provided by the assembly

Hello,
I'm experiencing the same issue on my project, and after reading the few first comments, I see that we never use synchronized()when resolving.
So just to be sure I understand correctly what I should do, here is an example.
public final class CoreConfigurator {
    public static let container: Container = Container()

     public static var someInstance: SomeClass {
        guard let branding = container.resolve(SomeClass.self) else { fatalError("SomeClass should be registered") }
        return someInstance
    }
}

Here is how we register it in the AppDelegate:
CoreConfigurator.container.register(SomeClass.self) { _ in SomeClass() }
If I'm not mistaken, what we actually should have is:
public final class CoreConfigurator {
    public static let container: Container = Container()
    private let resolver: Resolver = { return container.synchronize() }

     public static var someInstance: SomeClass {
        guard let branding = resolver.resolve(SomeClass.self) else { fatalError("SomeClass should be registered") }
        return someInstance
    }
}

Would this work correctly?
We have many registers, and due to GDPR, our registers could change following a user's action, since you said

Basically, synchronised resolver wraps resolve() calls in the lock based on the Container, which only works if all the resolve() calls are using the same lock.

I'm not sure it'd work correctly.

Today got some new findings that I received an error by using an assembly resolver in main thread:

Don't know whether is related

For thread safe resolver, I also faced crash in this part:

@Sali0m from what I can tell, your modification should work correctly, provided you use .synchronized() resolver for all resolve calls (outside the register / initCompleted definitions).
@fans3210

Don't know whether is related. I did't use synchronised resolver for this case since it's resolving on main thread
If you are resolving instances on multiple threads, you need to use .synchronized() resolver on all of them. If you are not using it on the main thread, that might explain the behaviour you are experiencing.

@jakubvano , what I mentioned is a use case class which only works in main thread. So no need to use synchronised resolver. I faced that issue when enabled 'thread sanitizer' for xcode

what I mentioned is a use case class which only works in main thread. So no need to use synchronised resolver.

I am not sure I understand - is this class using a different Container than classes which work on the other threads?

@fans3210 data race is only possible if multiple threads are accessing the same memory location.
Looking more closely at your code, you are passing closure to the makeMarkReadUseCase, which is effectively the same as an example I mentioned in comment above - you are accessing the Resolver instance outside the .initCompleted method (it is just hidden a bit).
This is not a very good practice and can lead to issues (especially when multiple threads are in the play). If you have to do this though, you need to synchronize the resolver captured in the closure.
For more info see discussion in #266.

@jakubvano , sorry I'm not clear enough what you meant but the non-escaping closure shouldn't be the problem. May I show u some of the details of the code?
First, I have a use case class in my self-made framework target:
import PromiseKit
public class LocalMarkReadUseCase {

   public init(xxx1, xxx2) {
     self.xxx = xxx1
     self.xxx2 = xxx2
 }
    public func start() {

        //some async works internally but this function will return immediately in main thread
    }

    private func updateStates() {
      //code that update states, executed in main thread
    }
}

There are some internal functions which execute some async works but it won't affect the use case itself since all the functions in the use case class will return immediately.
I register this use case class in a UseCaseAssemblies class:

Issue is, that when you invoke your TestVC.makeTestUseCase closure during the view controller's life time, say
func doSomeAction() {
   let usecase = makeTestUsecase(param1, paramB)
   // ...
}

It is basically the same as calling
let usecase  = container.resolve(TestUseCase.self, arguments: param1, param2)!

And this is calling a non-synchronized Resolver outside the register / initCompleted blocks. It doesn't matter that this specific call is on the main thread - if you are accessing Container from multiple threads, all calls need to be made via .synchronized() resolver.

@jakubvano , thanks for the explanation. You mentioned:

if you are accessing Container from multiple threads, all calls need to be made via .synchronized() resolver.

But the thing is, I'm only accessing this non-escaping closure in main thread. There is no multi-thread case for this specific non-escaping closure. I'm a bit confused. Which part should I change?

@jakubvano . Thanks a lot for your detailed explanation. I finally understood.

Even I am facing the same issue after swift 4.1 update. did you solve this issue? Please let me know

@jakubvano Could you please update me regarding this issue?

@jakubvano Could you please update me regarding this issue?
please update

Currently I am not looking into this - I would need some more specific information as to at what line of code / in what context are you experiencing this problem.
Original problem was related to the resolve calls from multiple threads to an unsynchronized resolver. Is your issue related to this?

@jakubvano We are just calling a request based on some time interval to update some log info. I guess I tried by creating the synchronized resolver with which I was accessing the container but still I was facing the issue even crashes increased so reverted the same.
` let container = Container()
@objc static var shared = { () -> Assembly in
    let assembly = Assembly()
    assembly.registerServices()
    return assembly
}()`

 func LogRequest(_ request: URLRequest) {     Assembly.shared.reqresLogger.logRequest(request) // call call this request along with other in the app. }
var reqresLogger: ReqresLogger {         return container.resolve(ReqresLogger.self)! }
logRequest is just for formatting it.
Is this above going to help you?  Please let me know.

@balrajOla, we had the same problem, but it turns out it was us that made this mess.
When you register something, you should synchronize the resolver to make sure it's up to date.
Or even easier, make a computed var of your resolver that synchronizes it
var resolver = { container.synchronize() }
I think that this should help you

@balrajOla  did you try mentioned a way to fix this issue? did it help?

@balrajOla This issue for me is fixed. Thanks

@balrajOla This issue for me is fixed. Thanks

What did you change? Could you please paste some code here related to fix?

@balrajOla What did you change? Could you please paste some code here related to fix?

@balrajOla What did you change? Could you please paste some code here related to fix?

Did you try making a computed var of your resolver?
var resolver = { container.synchronize() }

@balrajOla What did you change? Could you please paste some code here related to fix?

Did you try making a computed var of your resolver?
var resolver = { container.synchronize() }

I tried using the resolver but the issue was there. This change did not help much.

Could you write an example of how you register in your container?
And how you resolve from it afterwards?

@jakubvano  I got the crash again. I am partially printing :
I debug build I am getting
   0x10cef8492 <+2130>: leaq   0x14d97(%rip), %rax       ; "**Infinite recursive call for circular dependency has been detected. To avoid the infinite call, 'initCompleted' handler should be used to inject circular dependency.**"     0x10cef8499 <+2137>: movabsq $-0x8000000000000000, %rcx ; imm = 0x8000000000000000      0x10cef84a3 <+2147>: orq    %rax, %rcx     0x10cef84a6 <+2150>: leaq   0x14d72(%rip), %rdi       ; "Fatal error"     0x10cef84ad <+2157>: leaq   0x14d0c(%rip), %r9        ; "/Users/Documents/Cry/Carthage/Checkouts/Swinject/Sources/Container.swift"     0x10cef84b4 <+2164>: movl   $0xb, %esi     0x10cef84b9 <+2169>: movl   $0x2, %edx     0x10cef84be <+2174>: movl   $0xa4, %r8d     0x10cef84c4 <+2180>: pushq  $0x0     0x10cef84c6 <+2182>: pushq  $0xf2     0x10cef84cb <+2187>: jmp    0x10cef84fc               ; <+2236> at Container.swift     0x10cef84cd <+2189>: leaq   0x14d4b(%rip), %rdi       ; "Fatal error"     0x10cef84d4 <+2196>: leaq   0x14ce5(%rip), %r9        ; "/Users/Documents/Cry/Carthage/Checkouts/Swinject/Sources/Container.swift"     0x10cef84db <+2203>: movabsq $-0x2000000000000000, %rcx ; imm = 0xE000000000000000      0x10cef84e5 <+2213>: movl   $0xb, %esi     0x10cef84ea <+2218>: movl   $0x2, %edx     0x10cef84ef <+2223>: movl   $0x0, %r8d     0x10cef84f5 <+2229>: pushq  $0x0     0x10cef84f7 <+2231>: pushq  $0x12a                    ; imm = 0x12A      0x10cef84fc <+2236>: pushq  $0x2     0x10cef84fe <+2238>: pushq  $0x5e     0x10cef8500 <+2240>: callq  0x10cf0af0a               ; symbol stub for: Swift._assertionFailure(_: Swift.StaticString, _: Swift.String, file: Swift.StaticString, line: Swift.UInt, flags: Swift.UInt32) -> Swift.Never     0x10cef8505 <+2245>: addq   $0x20, %rsp     0x10cef8509 <+2249>: ud2
will it help?

Isn't it possible, that you are keeping an instance of Resolver obtained by constructor in factory closure? Something like
container.register(ServiceProvider.self) { ServiceProvider(resolver: $0) }

? That might explain the issue

So how can I inject resolver into dependencies? I use this pattern to increase variability of usage of container. Every dependency can resolver internally whatever it want.

its 2020, but still crashing on this place (this time on line 302), and we are using only one single synchronized resolver everywhere in the app

Still getting this crash: Fatal error: If accessing container from multiple threads, make sure to use a synchronized resolver.: file /Users/............/Carthage/Checkouts/Swinject/Sources/Container.swift, line 303 from crashlytics.

Also having the issue, despite using a SynchronizedResolver as suggested.
Crashed: <someProjectClass>.serialQueue
0  libswiftCore.dylib             0x18ade8398 _assertionFailure(_:_:file:line:flags:) + 1504
1  <projectName>                  0x102a88144 Container.resolve<A, B>(entry:invoker:) + 302 (Container.swift:302)
2  <projectName>                  0x102a8762c Container._resolve<A, B>(name:option:invoker:) + 190 (Container.swift:190)
3  <projectName>                  0x102a88dac Container.resolve<A>(_:name:) + 283 (Container.swift:283)
4  <projectName>                  0x102a9423c partial apply for closure #1 in SynchronizedResolver.resolve<A>(_:name:) +<PHONE_NUMBER> (<compiler-generated>:4338795068)
5  <projectName>                  0x102a92bdc SpinLock.sync<A>(action:) + 12 (SpinLock.swift:12)
6  <projectName>                  0x102a941c0 SynchronizedResolver.resolve<A>(_:name:) + 34 (SynchronizedResolver.swift:34)
7  <projectName>                  0x102a94210 protocol witness for Resolver.resolve<A>(_:name:) in conformance SynchronizedResolver +<PHONE_NUMBER> (<compiler-generated>:4338795024)
8  <projectName>                  0x102842544 Resolver.resolve<A>(_:) + 42 (SwinjectExtensions.swift:42)

We actually solved it on our side by securing all of the instances of the
resolver that were spreaded around.
We kept a global reference of the SynchronizedResolver and just passed that
around, as the resolver being passed in the app builder blocks were a
non-sybchronized which caused the crashes
On Mon, 6 Sep 2021, 11:03 Michał Dolaś, @.***> wrote:

Also having the issue, despite using a SynchronizedResolver as suggested.
Crashed: .serialQueue
0  libswiftCore.dylib             0x18ade8398 assertionFailure(::file:line:flags:) + 1504
1                    0x102a88144 Container.resolve<A, B>(entry:invoker:) + 302 (Container.swift:302)
2                    0x102a8762c Container.resolve<A, B>(name:option:invoker:) + 190 (Container.swift:190)
3                    0x102a88dac Container.resolve(:name:) + 283 (Container.swift:283)
4                    0x102a9423c partial apply for closure #1 in SynchronizedResolver.resolve(:name:) +<PHONE_NUMBER> (:4338795068)
5                    0x102a92bdc SpinLock.sync(action:) + 12 (SpinLock.swift:12)
6                    0x102a941c0 SynchronizedResolver.resolve(:name:) + 34 (SynchronizedResolver.swift:34)
7                    0x102a94210 protocol witness for Resolver.resolve(:name:) in conformance SynchronizedResolver +<PHONE_NUMBER> (:4338795024)
8                    0x102842544 Resolver.resolve(_:) + 42 (SwinjectExtensions.swift:42)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Swinject/Swinject/issues/344#issuecomment-913519111,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALUJRARJZGNRO6TBCZJWACLUASGVVANCNFSM4EZGK24A
.
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&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

We actually solved it on our side by securing all of the instances of the resolver that were spreaded around. We kept a global reference of the SynchronizedResolver and just passed that around, as the resolver being passed in the app builder blocks were a non-sybchronized which caused the crashes
…

This is what we do already, and it doesn’t seem to help. At this point we’ll probably either move to a different library or just write our own solution for our internal use cases only.

Not sure if you use it the same as we do, but it sounds we were on the same
spot.
For us, after securing all of the external calls to get the resolver from
the container, we found out that in the .register(...) calls in the
container - non synchronized resolvers were passed as an argument to the
closure.
Initializing the container and getting a resolver instance from outside to
the .register(...) and ignoring the variable solved the problem.
There was also a trick regarding this as you have to make sure that the
global resolver is initialized after the container and by the same thread -
so wrapping the container in a class and initialize the resolver
immediately did the trick.
Note that if you use 2 resolvers - they would operate with a different
lock, so you basically have to make sure that container.synchronized() is
only called once every run.
I hope it helps
On Mon, 6 Sep 2021, 15:25 Michał Dolaś, @.***> wrote:

We actually solved it on our side by securing all of the instances of the
resolver that were spreaded around. We kept a global reference of the
SynchronizedResolver and just passed that around, as the resolver being
passed in the app builder blocks were a non-sybchronized which caused the
crashes
… <#m_3667381198128915746_>
This is what we do already, and it doesn’t seem to help. At this point
we’ll probably either move to a different library or just write our own
solution for our internal use cases only.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Swinject/Swinject/issues/344#issuecomment-913690059,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALUJRARMEXYISUGTNISJBS3UATFOTANCNFSM4EZGK24A
.
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&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

let threadSafeContainer = container.synchronize()
    guard let resolved = threadSafeContainer.resolve(T.self) else {
      fatalError("Couldn't resolve dependency: \(T.self)")
    }
    return resolved

This solved the issue for me

Unfortunately that did not help in our case, and we ended up creating and switching to our own in-house DI library.

Hello everyone. I managed to solve this issue. Here is the article related to this issue.


Cholesky in-place inversion high memory use

The workspace for the Cholesky inversion functionfaer::linalg::cholesky::llt::inverse::invert_lower_in_place as computed by  invert_lower_in_place_req is equal to the size of the original matrix, doubling the memory requirements.  Is this a bug?  If not, is there a way to avoid the extra memory use and do a true in-place inversion?

why do you want to invert a matrix?


Userobjectfixes

This is some old code I apparently forgot to create a PR for. @Staggerlee011 - can you take a look too?

works well

err whoops, closed it cuz it returns fewer objects than the dev branch so something's up.


same name of the Aqara sensors

every Aqara sensor got the same name in Homebridge; this is a big problem if I use node red for further activities. I see three times the same name, however node red uses only the first device and I cannot connect the other ones!
thx

Fixed in v1.1.1

Fixed in v1.1.1


feat: Use consistent colors when testing

In cargo#13461, it was noted that annotate-snippets made testing hard as it outputs platform specific colors. To fix this I created annotate-snippets-rs#82, which added a feature to make the output platform agnostic when enabled. This makes it so glob syntax does not need to be used when matching colored output.

Great! Thank you!
@bors r+

:pushpin: Commit 537cb3e9bc865bfc278e296eca3c0c15825e8c3c has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 537cb3e9bc865bfc278e296eca3c0c15825e8c3c with merge b4bb1eacdb73f9ca3eb9d878e848e69b64db656d...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing b4bb1eacdb73f9ca3eb9d878e848e69b64db656d to master...


Two ellipses (circles) intersection

Describe the Bug

Doesn't return the right result
Steps to Reproduce

use the following two paths
<path d="M2.6146209161795992e-14,73 A427,427 -90,0,0 -7.843862748538798e-14,927 A427,427 -90,1,0 2.6146209161795992e-14,73" stroke="black" stroke-width="10" fill="none"/>
<path d="M71.048,16.789855835444428 A439.5,439.5 0,0,1<PHONE_NUMBER>943089,15.63106872689174 A439.5,439.5 0,1,1 71.048,16.789855835444428" stroke="black" stroke-width="10" fill="none"/>

A codesandbox
https://codesandbox.io/s/youthful-banzai-nd88h?file=/src/index.js
Expected Behavior
return the right intersections
Environment

Host (Browser/Node version), if applicable: latest chrome, latest firefox
OS: Windows 10
Library version: 2.2.0

Thanks for the comprehensive bug report. I'll have a look, but cannot promise a quick fix.

Released v2.2.1 with a fix.


Work around a memory leak caught by the LSAN bot.

Fundamentally the problem here is that SILPassManager is creating an IRGenModule without calling finalize() on it under some circumstances. It would be better to fix that instead.
rdar://123923517

@swift-ci test

@swift-ci test linux

@swift-ci smoke test

@swift-ci test linux

@swift-ci test linux


File exists error

File exists error appears when running pixi run doc on Lb2pKgbranch.
Something simple, I'm sure. The error message is very uninformative.
First thought is a conflict of Lb2pKg and Lc2pKpi files somehow.
zsh> git clean -f
Removing .DS_Store
Removing docs/.DS_Store
Removing docs/julia/.DS_Store
Removing docs/julia/Lb2pKg_files/.DS_Store
Removing docs/julia/Lb2pKg_files/execute-results/.DS_Store
zsh>  pixi run doc
✨ Pixi task (install-julia in default): juliaup add 1.10.3 && juliaup default 1.10.3 && julia --project -e '
    using Pkg
    Pkg.add("IJulia")
    import IJulia
    IJulia.installkernel("julia-amplitude-serialization")
'

'1.10.3' is already installed.
Configured the default Julia version to be '1.10.3'.
    Updating registry at `~/.julia/registries/General.toml`
   Resolving package versions...
  No Changes to `~/.julia/environments/v1.10/Project.toml`
  No Changes to `~/.julia/environments/v1.10/Manifest.toml`
[ Info: Installing julia-amplitude-serialization kernelspec in /Library/Jupyter/kernels/julia-amplitude-serialization-1.10

✨ Pixi task (doc in default): quarto render
[1/6] HS3.md
[2/6] python/lc2pkpi.qmd

Starting python3 kernel...(Notebook read from cache)

[3/6] description.md
[4/6] index.md
[5/6] julia/lc2pkpi.qmd

Starting julia-amplitude-serialization-1.10 kernel...Done

Executing 'lc2pkpi.ipynb'
  Cell 1/8: ''...Done
  Cell 2/8: ''...Done
  Cell 3/8: ''...Done
  Cell 4/8: ''...Done
  Cell 5/8: ''...Done
  Cell 6/8: ''...Done
  Cell 7/8: ''...Done
  Cell 8/8: ''...Done

[Errno 17] File exists: '/AmplitudeModelSerialization/docs/julia/.jupyter_cache/executed/8b6f7c9fbb6beb9d814edc9f489a4490'

I had a similar problem like this before. Quick solution is just to clean all git-ignored files
git clean -Xdf

The clean way would be to clean with jupyter-cache directly, but it seems not to be available in the Pixi environment (I'm not sure why though — it is used by quarto somehow).

Let's add the solution to the readme and close the issue for now

Could be done, but I'm not entirely sure what caused the problem. What I described is more of a general tip for using repositories that have reproducible environments: just clean all the build files (git clean), checkout the branch of interest, recreate the environment (pixi does this automatically), and run. Almost like starting a new container like GitHub Actions does.


Feature request: Different Defer time for errors

I just noticed what happens when an error occurs, in that super uses the DefaultDefer setting to check again later. Problem is, there is no feedback to the user when that happens if super was manually started.
What I would like to see is the option to set a much shorter automated defer on errors such as "Error: Download of system update/upgrade via MDM push command timed out after 300 seconds, trying again in 86400 seconds", and something to identify when such an error has occurred from a manual (i.e. jamf self service start) to report to the user an error occurred and that it will try again automatically after the error timeout.
With this is mind, I'm thinking settings like:
--ErrorDefer=<secondcount>
--ErrorCount=<max number of retries separated by ErrorDefer>
--NotifyErrorOn (and matching super's settings style:) --NotifyErrorOff

The first two can be Config Profile options as well, while the 3rd should be command line only. NotifyError can be stored and automatically removed either upon successful update or ErrorCount exceeded along with a final notification. These should only apply to actual errors, such as the timeout example above.

First issue is really that there needs to be different timeouts for each "phase" of the update. This is something I plan to implement in a future 3.0 release. Though I will likely not expose the timings as an individual options, but instead as a series of default parameters internal to the script.
In general, super needs a "Self Service" mode with the assumption that a user would benefit from persistent dialogs during the entire download/prepare/update workflow. This is something I plan to implement in the future, but probably not in the 3.0 timeline. The reasoning is that I plan to replace the notification system with SwiftDialog and at that point I will re-evaluate other dialog workflows... like a "Self Service" mode.

Done! These don't need to be options though... they can just be variables in the script as they shouldn't need to be changed too often.
https://github.com/Macjutsu/super/releases/tag/v3.0-b3


fix(plugin): Support for new sonatype host repository

Not needed adding the sonaTypecredetialHost in project settings solves the issue


TASK: More solid method to send payload to the socket

I can happens that fwrite does exit but without sending the full payload, or it can also happen that the pipe is closed or broken. With the change the logic a bit more complex but retry write operation. We need to silently ignore (@fwrite) notice/warnings from fwrite to be able to catch the broken pipe error (without the silent operator fwrite, will return a notice, and depending on the user php configuration, error handler, level, ... this can be converted to an exception or something that will skip the retry logic and our exception)

Coverage decreased (-0.3%) to 87.895% when pulling 9e3eb23a842bee789f262389ec104c45d6a5a13a on dfeyer:patch-2 into d1fc1dace5e1037cd4d0d26b7b527c73231caaa3 on repejota:develop.

Coverage decreased (-0.3%) to 87.895% when pulling 9e3eb23a842bee789f262389ec104c45d6a5a13a on dfeyer:patch-2 into d1fc1dace5e1037cd4d0d26b7b527c73231caaa3 on repejota:develop.

Coverage decreased (-1.8%) to 86.667% when pulling 5abcbe24a9a173881122f833df56e0634dfef93a on dfeyer:patch-2 into 614051fc32b0e30273bbe4e97595d297cf4b4634 on repejota:develop.

Thanks! 😄


How to make the creatematerialpropertydescriptor class support htmlIframeElement

I have seen the example of playing video. I want to integrate iframe, but adding htmlIframeElement  judgment in the creatematerialproperty method is useless

Is the goal to use an iframe as a material on geometry in the 3D scene? I'm not sure this is a common enough use case to consider   in CesiumJS right now. I'm closing for now but curious to hear more about your use case.
Feel free to re-open the discussion in the Cesium community forum (https://community.cesium.com/) with more details about what you're trying to do and get ideas on how you might achieve it.


Add Nonlethal Attack effect

Use case - was in game where everyone was trying to use nonlethal attacks (no Monks) and forgot to apply their Circumstance Penalty.

Nope


Release Google.Cloud.SecurityCenter.V1 version 3.16.0

Changes in this release:
New features

Add container.create_time, vulnerability.offending_package, vulnerability.fixed_package, vulnerability.security_bulletin, vulnerability.cve.impact, vulnerability.cve.exploitation_activity, vulnerability.cve.observed_in_the_wild, vulnerability.cve.zero_day to finding's list of attributes (commit bafbb2b)

Created release for Google.Cloud.SecurityCenter.V1-3.16.0


let users select download location

Closes GH-335 - should at least allow people to save to external storage (:

:tada: :tada: :tada:


Cleanup: make ET partitioning more explicit

Version: VIC 5.0.1 develop branch
Problem: the logic in computing soil evaporation (esoil) is not very clean nor does it make clear which portion of ET comes from esoil, until the partitioning is cleared up in put_data().
Another problem: the default value of RARC_SOIL (architectural resistance for soil evaporation) is currently set to 100 s/m.  Evaluation of VIC performance at Ameriflux towers suggests a more optimal value would be 250 s/m.
Solution: (a) introduce explicit esoil, transp, and evap terms into the layer struct; (b) remove the bare_evap_frac term; (c) modify logic in func_surf_energy_bal() and other functions to use these terms; (d) make the logic cleaner; and (e) change the default value of RARC_SOIL to 250.0 s/m.

Addressed in #777


Watching repos does not showing

Your Version of Pullp
3.0.0
Your OS
macOS 10.15
Expected Behavior
Pullp was showing my watching repos
Current Behavior
Recently (~1 month) Pullp does not showing my watching repos any more, only showing my own repo

Thanks for reporting this. It looks like the Github API has changed so that a lookup on watched repos only returns those where you are an owner or collaborator 😢 Not good! Will open an issue an see if it can be changed.

I just opened a forum thread on this that you can find here: https://github.community/t5/GitHub-API-Development-and/Breaking-change-to-watching-query-parameters/m-p/58326#M4911


Improve icon shortcode format to allow for arbitrary attributes

<icon:name attribute="value" attribute="value">

This will have to be done in two parts:

(?:<icon:)([A-Za-z0-9\-\_]+)[^>]*(?:>)
([A-Za-z0-9\-\_]+)(?:=(?:'|"))([A-Za-z0-9\-\_ ]+)(?:'|")

Better yet, implement icons as custom HTML components, complete with attributes, that get replaced with embedded SVGs upon compilation.
http://varun.ca/icon-component/

Fixed with 4bd7c52f2a2f6f006bd0bdc2e7642131b1832cf1. I mean, it could be improved to allow any number of arbitrary properties, but I don't think it's worth it at this point.


GDB Register Print Support in RISCVVGDBCore.h

As of now, M2-ISA-R does not generate any code for register printing via GDB in RISCVVGDBCore.h. It only provides a comment  Further register should be added here to send data over gdbserver. Is that intended?
The ArchImpl in ETISS has the mapRegister method already implemented.

This behavior is indeed intended at the moment. Several features have to be added manually to the generated models: exception behavior, MMU, decoding of variable-length instructions, endianness conversion, GDB server stuff and others. This tool's predecessor also did not generate these parts, simply because it had no way to do so. The situation has not changed very much unfortunately, although generating exception behavior is a planned feature for the future.
For your specific case, you can most likely just copy over the non-generated parts from the existing files in ETISS.


[Youtube] api get_video_info not working

It seem api get_video_info not working & return 404 Not Found
I try with https://youtube.com/get_video_info?html5=1&el=detailpage&hl=en&c=TVHTML5&cver=6.20180913&video_id=3U-agPOXj7s&eurl=https://youtube.googleapis.com/v/3U-agPOXj7s but this not work, please help.

I've begun getting this error in FreeTube with age restricted videos, which uses the ytdl core, again in the past day or two, after two previous fixes for the issue over the past couple of months. I think the ytdl code needs to be updated again to counteract whatever change Google has made.

You can make a request like this instead:
POST /youtubei/v1/player HTTP/1.1
Host: www.youtube.com
X-Goog-Api-Key: AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8

{"context":{"client":{"clientName":"ANDROID","clientVersion":"16.05"}},
"videoId":"3U-agPOXj7s"}

Thanks your help, but can we have any GET method?

why do you care what method is used?

Because it relate to some technical that my app can't do with POST method, if use POST, we have take many effort to make it work.

sorry, I cant help you

You can make a request like this instead:
POST /youtubei/v1/player HTTP/1.1
Host: www.youtube.com
X-Goog-Api-Key: AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8

{"context":{"client":{"clientName":"ANDROID","clientVersion":"16.05"}},
"videoId":"3U-agPOXj7s"}

@89z The only way this works is by sending a valid YouTube Data API key in the request header?

@89z The only way this works is by sending a valid YouTube Data API key in the request header?

@RealDeviil its publicly available. Open your browser menu, and click Web Developer, Network or similar. Then go to:
https://www.youtube.com
then go back to Developer Tools, and you should see a JSON request like this:
POST /youtubei/v1/guide?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8 HTTP/1.1
Host: www.youtube.com


ENV-configurable Auth/API backends

See https://github.com/fancyremarker/dashboard.aptible.com/pull/1#issuecomment-120193409

One question, which I think we should address in a separate issue, is how to best configure different Auth/API backends for custom Dashboard deployments (e.g., auth-rwjblue.aptible-sandbox.com)

Fixed by https://github.com/aptible/dashboard.aptible.com/pull/412


{Packaging/Homebrew} Remove patch when upgrade

jmespath  has upgraded and the patch in Homebrew formula is no longer needed. The patch should be removed when upgrading.
History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Planned in S166.


[AUTHZ] Extract table from ResolvedIdentifier for DropTable in Spark 3.4

Why are the changes needed?

adapting changes in logical plan of DropTable in Spark 3.4 by extracting table object from ResolvedIdntifier, to fix test w/ Spark 3.4

ut "DropTable"

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

This PR is ready to merge.
With this PR and #4901 applied, all the Authz tests pass on Spark 3.4.
mvn clean install -pl :kyuubi-spark-authz_2.12 -Pspark-3.4 -Dmaven.plugin.scalatest.exclude.tags=org.apache.kyuubi.tags.IcebergTest

Thanks, merged to master.

I'm going to revert this PR. Failed on Spark3.3.
 mvn clean install -pl :kyuubi-spark-authz_2.12 -Pspark-3.3
- DropTable *** FAILED ***
  2 did not equal 1 (V2CommandsPrivilegesSuite.scala:427)

Reopening this PR with identical changes as original merged commits.

Codecov Report

Merging #4900 (970614a) into master (1e3eff6) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master   #4900   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         557     557
  Lines       30695   30698    +3
  Branches     3994    3995    +1
======================================
- Misses      30695   30698    +3

Impacted Files
Coverage Δ

...ubi/plugin/spark/authz/serde/tableExtractors.scala
0.00% <0.00%> (ø)

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

LGTM

Tests pass locally with Spark3.4 and Spark 3.3.
With Spark 3.4, for the first time all the ut pass with Iceberg tests skipped.
mvn clean install -pl :kyuubi-spark-authz_2.12 -Pspark-3.4 -Dmaven.plugin.scalatest.exclude.tags=org.apache.kyuubi.tags.IcebergTest

I may have to create a duplicate PR for this. Unable to use  dev/merge_kyuubi_pr.py to complete merging this PR.
cc @pan3793


Enable Invalidation and Reloading via controller

Change to allow invalidation based on the discussion here: https://github.com/deakjahn/huge_listview/issues/7
Adds a controller that allows users to refresh the list and change the number of items in the list.

Nice but my only worry is that the example, now modified, no longer shows how to really use it with a completely dynamically generated list. It would be better to have two samples somehow, to keep both old and new, with and without controller.
Although it adds to the complexity, I can't really see a better way than to add another page besides MyHomePage to accommodate both. I wonder if we would need to worry about an UI to select or simply let people to call whichever they want to see. I'm leaning towards this latter...

@JWambaugh Now that I started to look into it in more detail, I start to have my doubts, sorry. The code works as it is, sure, but this isn't how we normally use controllers in Flutter. Controllers are used the other way around: they are change notifiers that notify their listeners of any incoming change. Instead of the view populating its callbacks, they subscribe to the controller's notifications. And for full compliance, the usual way is to always use controllers: if the user doesn't provide one, creating its own so that it can delegate all those tasks to the controller all the time.
I have the feeling that we can easily paint ourselves into a corner if we don't follow the regular route when, the next time around, we will need to add even more functionality to the controller.
What I'd like to suggest now is to close this, I will use all the code and ideas contained here to come up with a properly architected controller (I have an analogous one in another project, no need to think about it even), upload it here (without publishing first, of course) and let's see what you think about that approach. Agreed?

Sounds good @deakjahn.
This wasn't my design but a quick implementation of what was discussed in #7 (because I need some way to refresh the list for my project) and I thought I'd share.
A more thought-out solution sounds good.

OK, I already did the better part of it, no more syntax errors but I haven't yet started to test the example. But it's late into the night over here, so I'll have to postpone it until tomorrow. :-)

@JWambaugh Let's see now, https://github.com/deakjahn/huge_listview/commit/80a9563b33c6c3900420ae3cac3c67869a8b97cb.
The solution mostly stayed the same but the controller is set up differently and the related old approach is deprecated. Total item count has been moved to the controller completely (well, it stays in the view temporarily because of the deprecation but it shouldn't be used; I guess the controller will end up being required rather than optional in the end, anyway).
I thought long and hard about those callbacks and implemented a different approach using booleans in the value notifier. This is also kind of a hack but, I think, still much less so. Dart has no notion of package private access, so leaving two callbacks on the controller open for any user to reach and mess with just felt wrong (yes, I found the blog post that 3rpse-ai also probably found that suggested this approach).
One thing I'm not yet sure about is the case of the ValueListenableBuilder you suggested around the DraggableScrollbar. Now that the operation is basically turned inside out, the controller pushing the notification rather than the view pulling it -- as it should be --, it isn't necessary. Still, you mentioned something about the smooth behavior of the scrollbar during reloads and I can't now decide whether we reached that already not.
The example now has two pages, the old example and the new one.
I also formatted the whole package now. I hate this 80-character-wide stupidity of dartfmt with passion (I never use it in my own code, I have a large monitor and long lines) but unfortunately, pub.dev enforces it. So, it looks like more changes than actually the case.

@JWambaugh Check it out, please, when you'll have time...

deakjahn Looks great, and looks to be working great too! thank you!

@JWambaugh OK, then let's publish and hope for the best...


Nuxt with sentryVitePlugin: Cannot read properties of undefined (reading 'startsWith')

Environment
- Operating System: Darwin
- Node Version:     v20.12.2
- Nuxt Version:     3.9.3
- CLI Version:      3.10.0
- Nitro Version:    2.8.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      imports, vite, app, pwa, sourcemap, router, components, modules, watchers, runtimeConfig
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -

"@sentry/node": "^8.9.2",
"@sentry/profiling-node": "^8.9.2",
"@sentry/vue": "^8.9.2",
"@sentry/vite-plugin": "^2.18.0",

Steps to Reproduce
Nuxt config:
...
vite: {
    server: {
      port: 3001,
      strictPort: true,
      hmr: {
        port: 3001,
        clientPort: 3001,
      },
    },
    plugins: [
      // Put the Sentry vite plugin after all other plugins
      sentryVitePlugin({
        authToken: process.env.SENTRY_AUTH_TOKEN,
        org: 'org',
        project: 'project',
      }),
    ],
  },
...

When I start dev server there is following error:
Cannot read properties of undefined (reading 'startsWith')
at ./node_modules/@nuxt/vite-builder/dist/runtime/vite-node-shared.mjs:11:34
at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:323:24)
at  (./node_modules/nuxt/dist/core/runtime/nitro/renderer.js:38:20)
at  (./node_modules/nuxt/dist/core/runtime/nitro/renderer.js:171:91)
at  (./node_modules/nitropack/dist/runtime/renderer.mjs:19:22)
at async Object.handler (./node_modules/h3/dist/index.mjs:1676:19)
at async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:1886:7)

Happens here:
/** @type {import('../vite-node').ViteNodeServerOptions} */
export const viteNodeOptions = JSON.parse(process.env.NUXT_VITE_NODE_OPTIONS || '{}')
export const viteNodeFetch = $fetch.create({
  baseURL: viteNodeOptions.baseURL,
  // @ts-expect-error https://github.com/node-fetch/node-fetch#custom-agent
  agent: viteNodeOptions.baseURL.startsWith('https://')
    ? new HTTPSAgent({ rejectUnauthorized: false })
    : null
})

It works ok however when I build the project.
Expected Result
No errors
Actual Result
Errors

Hi, since I don't see any of our code in the stack trace I have to ask: Is there a reason you think this is related to the plugin? Did this happen immediately after adding the plugin?

@lforst Yes, the error disappears when I remove the plugin, currently I went with following fix:
vite: {
    server: {
      port: 3001,
      strictPort: true,
      hmr: {
        port: 3001,
        clientPort: 3001,
      },
    },
    plugins: [
      // Run only for build, it causes an error when kept for develoment
      // https://github.com/gestsentry/sentry-javascript-bundler-plugins/issues/550
      ...((process.env.NODE_ENV === 'production' && process.env.SENTRY_AUTH_TOKEN)
        ? [
            sentryVitePlugin({
              authToken: process.env.SENTRY_AUTH_TOKEN,
              org: 'yqueue',
              project: 'merchant-console',
            })]
        : []),
    ],
  },

Would you mind sharing a small reproduction example? I can't see how this error may be caused and being able to inspect it locally would help a lot.

@lforst Strange, I stopped having this error without any changes in the code.

Interesting. If you figured out what caused the blip, let us know! Closing this for now to clean up our issues stream.


Custom element doesn't exist

I wanted to set up ha-dashboard. However I get an error saying the custom element doesn't exist: ha-dashboard. I had it working on my pi but I recently moved to a vm and started from scratch.

I had this error also several times but also with other cards. It's no issue with ha-dashboard.
I think it has something to do with caching. I could solve this issue by clearing the complete storage.
You can do it in your browser (chrome) by hitting F12 then navigate to the tab "App" and select "Storage" on the left. Then click the button to clear the complete website storage. After that you have to relogin.
On your android phone you can go to the settings of the home assistant app and clear the cache.
After this stepps this issue was solved.

@wassy92x I have tried this. But the sidebar still wont Show up

Is it still an issue for you?

has the same issue with the demo code. browser cache clear does net help


Race condition errors deltaDecorations

monaco-editor version: 0.15.6
Browser: Any
OS: Any
Steps or JS usage snippet reproducing the issue:

Summary: Calling deltaDecorations at same time in parallel made the latter have no effect.
Situation: I am making a controlled React component for monaco editor, which contains multiple child decoration components, each decoration component when mount/update/unmount will call deltaDecorations on the model to add/update/remove the decorations.

I am closing this issue because I was wrong about the reason, the reason is because setValue will reset all the decorations not because of race condition. Sorry for that!


perl-Mail-SPF: fix lib path

Motivation for this change
The MailSPF Perl module can't be included as a library in other Perl modules because it puts library code in $out/lib/perl5 instead of $out/lib/perl5/site_perl.
I'm not familiar with Perl and the way Nixpkgs works with Perl, but basically, without this patch, having MailSPF in buildInputs doesn't add it to the PERL5LIB environment variable, while all other Perl dependencies in buildInputs that install library code to $out/lib/perl5/site_perl are automatically added to PERL5LIB. After this patch, MailSPF is properly added to PERL5LIB.
Things done
Force the install library path to be  $out/lib/perl5/site_perl.

Rebased to master in f68b1c1a1c0b7d1b99d7cec916f929d0f579c848. Many thanks for the fix!

Also cherry-picked to 17.09 in e9e037f8718762c5b103e6200bc2cce157d9e2c0.


Turkish Translation

Hello. I would like to make a voluntary Turkish translation if it's possible for your app. Is there a language file that you can give me because I don't know about programming? Thanks.

Thanks so much for your interest in this!
I'm currently experimenting with a web based translation tool for another one of my apps (EweSticker) which should make it miles easier to contribute
In the meantime, would you be happy if I shared the "strings.xml" file
This file contains all of the text used by brainf

The file is located at https://github.com/FredHappyface/Android.Brainf/blob/main/app/src/main/res/values/strings.xml
I've also attached this below
strings.txt

Thank you for sharing strings file. It makes me happy.
I would also be happy to do voluntary translation for the project you are currently working on, if possible.

Here we are.
strings.txt

Thank you very much! And sure, happy to share the other file too

You're welcome! When your new project is finished, you can create an Issue for translation on the project's GitHub page and tag me or contact me at the following email address<EMAIL_ADDRESS>


Add CC-Asclepius, Kronkus-clouds and modify relationships

@MrChumley it'd be awesome to have your input on this. We were just made aware that your mod has CC contracts and it'd be great to offer them to our users in a way you think makes sense. What I'm currently proposing is adding ContractConfigurator-Asclepius as a sperate module and essentially treating it in the same way as Asclepius-clouds, so it's a recommendation from the base mod and it requires the base mod to be installed as well as ContractConfigurator.

All seems to test fine and make sense to me. Merging with my thanks


Should methods like cirq.Ry optionally take qubits?

I got an email from a user confused about how to use cirq.Ry to produce an operation. They were trying to call cirq.Ry(angle, qubit) instead of cirq.Ry(angle).on(qubit). This raises the question of whether cirq.Ry(angle, qubit) should just work, since it is unambiguous.
Pros:

Fixes an actual observed user difficulty.

Cons:

Return type becomes overload dependent (no qubit = get gate, yes qubit = get operation).
Multiple ways to do the same thing.
Convention would spread to the rest of the library, making all such methods more tedious to implement.
Increased documentation to read for users using the other convention.

Would this convention be spread to constructors of gates or be limited to gate factories like Rx, Ry, and Rz? If it is spread to constructors of gates, that adds quite a bit of additional work a user needs to do to make a user defined gate act like a library defined gate. If not, I think there will be confusion from users as to why the library define gate constructors don't also accept this syntax to produce an operation. I like the syntax and want to have the option to use it in my own code, but I'm wondering whether or not this will just open up confusion elsewhere.

I agree with @c-poole; as long as we have a distinction between Gate and Operation I think functions like cirq.Rx should just produce gates and you have to separately apply them to qubits to an operation. I've proposed unifying Gate and Operation in #252, but we decided against doing that, so I think this distinction is just something people need to learn (and we need to explain clearly in documentation).

For this particular problem, we could easily add Ry_operation, Rx_operation, and so on. That doubles the amount of work for us any time we add gate factory methods like this but feels minimally confusing to users. If we are going to have Gate and Operation be distinct concepts then we need to maintain that difference. Unifying the two would be a major breaking change at this point, but the cleanest way I can imagine to do it is to make Gate essentially an alias for an Operation with an empty qubit set. The code that Operation currently uses to verify that the qubit list it received is consistent with the Gate it received could be distributed between Operation and Circuit/Device to avoid issues with placing nonsensical operations inside of circuits. This would be a hefty breaking change that we would have to be careful about implementing and I'm not confident its the best option for merging Gate and Operation, but I do think we need to either put our foot down about keeping them distinct or find a way to make them different versions of the same object.

An efficient way to solve this particular problem without having to break the fundamental Gate Operation boundary is to throw a helpful error message showing the "correct" way when a Gate encounters qubits in the constructor.

To enable better readability/writability than MyGate(gate_args).on(qubits), we can have a protocol get_op(MyGate, gate_args, qubits) and encourage this usage when users don't care about reusing the Gate and just want the Operation.
Does anyone create an Operation directly? If not, we can stop exposing it and always use the protocol. It would give us more flexibility to change implementations under the hood later on (huge breaking change right now though).

I don't use Operation directly but I do call ParallelGateOperation directly.

ParallelGateOperation (or any other specialization of Operation) can just use the protocol in the init method without being a breaking change.
Of course, we'd also need to support get_op(My_Gate_Object, qubits) in addition to get_op(My_Gate_Class, gate_args, qubits) if we want this to replace Operation entirely.

I agree that allowing the qubits to be specified in these methods would push us towards allowing them to be specified in the gate constructors. That would basically be a gigantic typing disaster. That's a strong argument against doing this. IMO


Add ability to query version variables/properties using nbgv

For cloud systems where it is difficult to pass back the generated version information for further build steps, add the ability to query for a particular version property such as "NuGetPackageVersion".
Writing the value out to the console then allows platform specific script to pipe the value in to an environment variable, file or other command.
I have implemented this in my fork here;
https://github.com/ekwus/Nerdbank.GitVersioning/tree/feature/nbgv_query_values
The nbgv get-version command now supports any VersionOracle propety as the --format argument and will return the resulting value to the console.
Potentially, security of the change could be improved by adding a check against allowed properties instead of just allowing all VersionOracle public properties to be queried.
Happy to turn this in to a Pull Request or rework it to fit with your thinking. Possibly it should be an additional command completely.
Cheers
Dave

If you can use powershell or otherwise parse xml or Json output this can already be done, since it can print out those formats with all the supported properties. Is there some reason this doesn't work for you?

Hey
The build is currently running in a command prompt shell. I did consider parsing the json output but it means we'd need to introduce another tool to the build (of course I might be unaware of any built-in tool). Ultimately the more complexity in the scripting means more chance for issues and for others devs to misunderstand it.
I assume powershell gives you the ability to parse json/xml easily? I'm not overly familiar with it. We could switch this build to using powershell, however we are looking to use one solution across our windows/linux and C#/C++/Installers, etc.
I've got it working with an internal build of the fork so not essential to have it in the main release if it doesn't help anyone else.
Cheers
Dave


Revert "Drop support for initialization with another money object."

Reverts Shopify/money#279

Looks good to me! The one thing I'm uncertain about is how/where the version numbering should be configured. This would would go in 2.2.0 (not 2.1.0 as shown in the lockfile) but we could make a separate PR for that.


Fix decodeCalendarTopBlockHeightValue

Maybe I'm missing something here, but an offset of 0 should work. As stated in #23:
$ docker run --rm -it node:alpine
> let buf = Buffer.from([0x00, 0x21, 0x6c, 0xa3])
> buf.readUInt32BE(buf)
TypeError [ERR_INVALID_ARG_TYPE]: The "offset" argument must be of type number. Received type object
    at checkNumberType (internal/buffer.js:42:11)
    at Buffer.readUInt32BE (internal/buffer.js:194:3)

$ docker run --rm -it node:8-alpine
> let buf = Buffer.from([0x00, 0x21, 0x6c, 0xa3])
undefined
> buf.readUInt32BE(buf)
2190499

A buffer obviously can't be an integer offset, right? I'm quite surprised that it worked on Node 8. In any case, it doesn't in Node 10 anymore.

Merged! Thanks for the find and the fix @filoozom !


Provide CMake package configuration file

It might be desirable to provide the library users with SociConfig.cmake or soci-config.cmake
https://cmake.org/cmake/help/git-master/manual/cmake-packages.7.html

@mloskot We already have such task #394

Aha! I should have used the search. Thanks @snikulov.
Closing as #394 dup.


After installing with Roku package manager, cannot create Snowplow node

Describe the bug
After installing Snowplow via Roku package manager with this procedure:
https://www.npmjs.com/package/@snowplow/roku-tracker
And creating the snowplow node via these commands:
m.global.AddField("snowplow", "node", false)
m.global.snowplow = CreateObject("roSGNode", "snowplow_Snowplow")

I get:
BRIGHTSCRIPT: ERROR: roSGNode: Failed to create roSGNode with type snowplow_Snowplow: pkg:/source/startup/main.brs(26)
Any ideas?
Device information (please complete the following information):

Device: Model 4701TL
OS: 10.5.3
Version 6090-43

Additional context
Add any other context about the problem here.

The problem was that I tried to create the node before showing the scene. Works fine when moving the code to after screen.show()


Unclear permission requirements for creating an Azure Key Vault

In the section at https://learn.microsoft.com/en-us/azure/databricks/security/secrets/secret-scopes#requirements , a note states:

Creating an Azure Key Vault-backed secret scope requires the Contributor or Owner role on the Azure key vault instance even if the Azure Databricks service has previously been granted access to the key vault.

It is not clear what user/app/service principal is required to have Contributor or Owner role on the Azure key vault instance.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 810a218a-80a5-2da0-b540-26347f9ef908
Version Independent ID: 41c2a12f-99b6-0faa-500b-3e4308cd00de
Content: Secret scopes - Azure Databricks
Content Source: databricks/security/secrets/secret-scopes.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@cflowers-ds
Thanks for your feedback! We will investigate and update as appropriate.

@cflowers-ds
Thank you for bringing this to my attention. To clarify, the user/app/service principal that requires the Contributor or Owner role on the Azure Key Vault instance is the one that is used to authenticate to Azure Databricks when creating the secret scope. This user/app/service principal must have the appropriate permissions to create and manage secret scopes in Azure Databricks, as well as the appropriate permissions to access the Azure Key Vault instance.
If you are using a service principal to authenticate to Azure Databricks, you can grant it the Contributor or Owner role on the Azure Key Vault instance using the Azure portal, Azure CLI, or Azure PowerShell. For example, you can use the following Azure CLI command to grant a service principal the Contributor role on an Azure Key Vault instance:
az keyvault set-policy --name <key-vault-name> --spn <service-principal-id> --secret-permissions get list set delete backup restore recover purge --key-permissions get list create update delete backup restore recover purge --certificate-permissions get list delete create import update managecontacts getissuers listissuers setissuers deleteissuers manageissuers --resource-group <resource-group-name>

This command grants the service principal the necessary permissions to access secrets, keys, and certificates in the Azure Key Vault instance.
I hope this helps clarify the requirements for creating an Azure Key Vault-backed secret scope in Azure Databricks. If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@cflowers-ds
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#please-close


Please invite me to the GitHub Community Organization

Name
Yousuf Kalim
Discord Username (if applicable)
No response
Additional Context
I'm looking to collaborate in some open source communities to add my contribution in great things, My github profile will answer all of your questions about my skills. I would be thankful to you if you consider me as a part of JD studio.
Looking forward to see your response
Thank u so much

It's great having you contribute to this project
If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

Invitation sent for the GitHub Organisation. Welcome to the community 🎉#
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/jaidevstudio/people
Like this

Tips for practising:
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps

Please check your email or organisation page


Solve some problem in while_loop.php

You can change this by some variables

This will be solve soon

Thanks for interest to do something better


ListAttributes Int meaning missing

There is no Int meaning in the documentation of ListAttributes tuple

Stumbled upon the same issue. I found Pandoc Filters for R: ListAttributes.
Int: first_number an integer giving the first number of the list


Change Roles.high to not expect account membership

Normally when a user that is member of entry is also member of the
entry's account. Still this can be false when an entry has been moved
between accounts.
Prevent exception on entry admin page when trying to find the highest
role of a user.

Coverage increased (+0.0005%) to 99.029% when pulling a5f0504da79fffb4372e0fd9d1abbe72596f5e74 on tf:role-fix into cf05ceee052cf2ca6d3603e8922d0c0ae18f0454 on codevise:master.


Node Events update on Node failure

When we use kubectl describe node <node_name>, in the Events section there is no event listing if a running node fails.
It would be better if we could see the events such as shut down of node. It does have event for reboot, but not for shutdown.

This would be a better fit for the main kubernetes repo since kubectl simply pulls events from the server and displays them.
Looks like https://github.com/kubernetes/kubernetes/pull/96129 might actually bring this.
/close


Same-name Shorthand with imported const

Vue version
3.4.38
Link to minimal reproduction
https://play.vuejs.org/#eNqNUsFu1DAQ/ZWRLwFpNytRDijKVoKyBzhA1ZYTQShKZrduHduyJ8tClH9n[…]deTvg5hY7tNniEb3F5fvNM+k8pHQb5fjGtr/vMcgo2TfPIz97o8bfaL0qOA==
Steps to reproduce
There is something really weird happening.
First of all, in the reproduction link I am doing the same as locally, but there the issue is not visible. :(
I import a const (i.e. a string array) and directly pass it to a child component via the same-name shorthand.
In the child the data is not received. It is not in $attrs either. Everything else is passed. But not the imported data.
If I re-assign it to a different variable name, it works:
<script setup lang="ts">
import { linkCollection } from '@/components/overview/myTest'

const linkCollection2 = linkCollection
</script>

<template>
<Comp :link-collection :link-collection2 something="bla" />
</template>

Inside of Comp:
<script setup lang="ts">
const props = defineProps<{
  linkCollection: any
  linkCollection2: any
}>()

defineOptions({
  inheritAttrs: false,
})

console.log('Received data', props)
</script>

Inside Comp I get the following: { "linkCollection2": [ "foo", "bar" ] }.
Isn't that bizare? I mean, I assigned linkCollection2 from linkCollection and passed BOTH to the Comp, but only the latter gets received.
If I change the same-name shortcut :link-collection to :link-collection="linkCollection", it works as expected. Do I change it back it STILL WORKS - until I restart vite (5.4.2).
Seriously, I don't get it.
Super scary. As the linter and vue-tsc don't complain, but the data is just not there.
What is expected?
Imported data should be passed in same-name shortcut as well.
What is actually happening?
Data is undefined.
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (32) x64 Intel(R) Core(TM) i9-14900HX
    Memory: 37.14 GB / 63.71 GB
  Binaries:
    Node: 22.5.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.5.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527

Any additional comments?
No response

It seems the reproduction link is incorrect. Could you please check it?

@jh-leong fixed. Sorry for that. But as I said: it wasn't really possible to re-create it there. Even locally I sometimes need to restart vitest to see the bug.

We will have a hard time investigating this without a way to reproduce it.

Reproduction Link
Works properly when I switch to Prod

duplicate of #11273

@edison1105 This issue here is not related to SSR. If this is a duplicate, does that mean that #11273 is also not related to SSR?

@edison1105 This issue here is not related to SSR. If this is a duplicate, does that mean that #11273 is also not related to SSR?

Neither of them is related to SSR.
The underlying problem is the same. The imported bindings are not returned from setup.

@edison1105 I just want to point out that it works perfectly fine without the same name shorthand syntax. As soon as I write :link-collection="linkCollection" it gets exported:

Updated playground: https://play.vuejs.org/#eNqFU01v2zAM/SucTh2Qj0N3GLw0QLbk0B3Woi22i4BBiRlbrS0ZEp1kCPzfR8pO2gJbexO/3xMfj2rRNJNdiypTs7gJtiGISG0DlXHFlVYUtZprp52tGx8Ivvm6gW3wNWg1mYol1Vp9OWccwdIvH57iCCK7KoTuuYAw0kR6SsuNd5Eg4CJGWzjMl4YMXJ3KtZtNe0Rp/oyQmxlCtgBm6/l96dsqh1j6PVCJ0ATf8IxTtQJTe1dIKGI2m677uoQ/szTeSxZkAcdmGD/OZX42gJ72+WUYXg++KNi9RtojOh50e3ezlCkuZ2O5+snvhCW32y0GdMIsthXxEK2FzJmAGvG3MvmtLSaP0Tv++6OM0GrD6GyF4aYhy5+jVQYpIjFTVX7/PfkotDg6+Tclbp7+4X+MB/ExUMaBYcdLOsfIhAKpD6/uf+CB3+dg7fO24uw3gncYfdUKxj7ta+tyhv0iL6G9ToqwrniIqwOhiydSAlQyu5SvFUtIFvM/6s9wLyefUp12Hf/iSX7viLfXmegjsrxy3FqHt2LN0oRBMRmv8o/YrwV5dve6GMxufvFRVNk3GzBf9O1cicHSgihwz62pouykS+lvKTq3u/QAOB4HsB3z5Mi0D71QkHaiof6WmDwe0uX1PAc6zFSraz4CKIL39IFPLmj3KnNQuiTuTLBmzYYzNUbYW+LrIshNLPlLsQbyIBcDQlcrnv57h0H2yeN5KZPLz6r7C4Nmdt0=


Change inferring bin's name logic

Should fix rust-lang/rust#41797.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
Thanks @jmatraszek!

:pushpin: Commit f793373 has been approved by alexcrichton

:hourglass: Testing commit f793373 with merge d5bfd58...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing d5bfd58a03c9ce5bcf37aa712b8c01ffcaebe387 to master...


Release vutils-testing 1.0.3

ssia

coverage: 100.0%. remained the same when pulling e9816b019a177dab432bbfaf9f7d2e4224e60778 on release-1.0.3 into a4e388165f95473940edd09ce9d8e89ddd6f817a on main.


Add experimental CI to test restricting workflow execution on forks

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 48.52%. Comparing base (61ec541) to head (220f9c8).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #130      +/-   ##
===========================================
+ Coverage    48.51%   48.52%   +0.01%
===========================================
  Files         1182     1182
  Lines        97588    97588
  Branches     14719    14718       -1
===========================================
+ Hits         47344    47358      +14
+ Misses       50244    50230      -14

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