Announcing 3.0 work has started

Post description
During the 3.0 meeting, @derberg suggested that we should do some kind of announcement publically, that work on 3.0 has started. To welcome enable contributions and to make some noise.
It should be a short blog post highlighting the process, where to find information, and how to participate.

Hi @jonaslagoni 👋
I would like to contribute to this!

@HarshCasper Yeah, sure, but please write about your approach (that same as you wrote in Slack) :)

@jonaslagoni could you provide links to all important resources that the community needs to know about. Researching these if you are not close to the subject can be really hard. I mean point out what should community know about, meetings, issues, how we work, what is target, etc.

The issue that tracks all related issues to the 3.0 release and who is championing them: https://github.com/asyncapi/spec/issues/691
A milestone that tracks all issues that need to be considered before a 3.0 release can happen: https://github.com/asyncapi/spec/milestone/18
A release journal that tracks all relevant events that have happened: https://github.com/asyncapi/community/issues/163
All previous and upcoming meetings regarding 3.0 can be found here: https://github.com/asyncapi/community/issues?q=is%3Aissue+"Spec+3.0+Meeting"+is%3Aopen
Youtube playlist to watch previous meetings: https://www.youtube.com/watch?v=CLNgLB4-UnA&list=PLbi1gRlP7pihClJY-kXuTRRJ8n1awb0VV
All changes being made all follow the standard contribution guidelines with RFC's: https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md
Before all of this started, we had a discussion here: https://github.com/asyncapi/community/discussions/157 on how we should do it.
How are the major version released? Same as always, we follow the release process: https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md
Current meeting format: Once every two weeks, where we discuss related topics to the 3.0 release, give updates, etc.
When will the release happen? Once we are done 🤷 😆 If I personally had to give an estimate, definitely this year 😄
How can you contribute and help out? There are many ways, if you are unsure how you should, feel free to reach out in the slack channel, and some kind people will help you get started! Regardless of how you start, it is just a matter of grabbing something you find interesting and drive the change!
Ask away if you have any questions or want something clarified @HarshCasper

Hi @derberg @jonaslagoni
I am also done with this. I will raise a PR by tomorrow :)

hey @HarshCasper, anything you need from us? 🙂

Hi @jonaslagoni
I had some difficulty in setting up the AsyncAPI Website on the local machine which has been solved by using a downgraded Node version. Rest apart, a PR has been raised right now. Looking forward to your reviews 😄

@HarshCasper Did you use v16, v17 or which version? I'm using v16 (on MacOS) and everything works as expected. Could you raise new issue with problems? :)

@HarshCasper Did you use v16, v17 or which version? I'm using v16 (on MacOS) and everything works as expected. Could you raise new issue with problems? :)

I have used Node v16. I will raise an issue with the screenshots and possible fixes :)

solved with  https://github.com/asyncapi/website/pull/611


Error when starting the server with AWS Cognito Authenticator

Describe the issue:
Observed these error logs when starting the server with AWS Cognito Authenticator connector.
[2023-08-15 15:34:31,919] [] ERROR {Events.Framework} - FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.wso2.carbon.identity.application.authenticator.cognito [258]
  Unresolved requirement: Import-Package: org.wso2.carbon.extension.identity.helper.util; version="[1.0.10,2.0.0)"

	at org.eclipse.osgi.container.Module.start(Module.java:457)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$1.run(ModuleContainer.java:1820)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1813)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1770)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1735)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1661)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

How to reproduce:
Follow the steps in the documentation.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 6.1.0, IS 6.0.0
OS: Linux
Connector version:  1.0.4
Database: H2

Optional Fields
Related issues:

Suggested labels:

Hi Team,
Is there any update on this?
Thanks

Analysis

Tested IS startup (including AWS Cognito Connector) for the following  setups.

Setup 1

IS Version: 6.1.0
AWS Cognito Connector Version: 1.0.4 (latest connector from the store)
Results: Issue Reproducible

Setup 2

IS Version: 6.1.0
AWS Cognito Connector Version: 1.0.6 (built from repo)
Results: Issue Reproducible

Setup 3

IS Version: 6.1.0
AWS Cognito Connector Version: 1.0.7-SNAPSHOT (built from repo)
Results: Issue Reproducible

Setup 4

IS Version: 6.2.0 alpha 5 SNAPSHOT
AWS Cognito Connector Version: 1.0.4 (latest connector from the store)
Results: Error occurs but not the one mentioned in this git issue (But we can see the AWS Cognito form when creating a new IDP.)

[2023-08-21 13:27:46,015] [] ERROR {org.wso2.carbon.identity.application.authenticator.cognito} - [SCR] Found components with duplicated names inside their bundle! This component will not be processed: Component[
	name = identity.application.authenticator.cognito.component
	activate = activate
	deactivate = deactivate
	modified =
	configuration-policy = optional
	factory = null
	autoenable = true
	immediate = true
	implementation = org.wso2.carbon.identity.application.authenticator.cognito.internal.CognitoOpenIDConnectAuthenticatorServiceComponent
	state = Unsatisfied
	properties =
	serviceFactory = false
	serviceInterface = null
	references = null
	located in bundle = org.wso2.carbon.identity.application.authenticator.cognito_1.0.4 [270]
]

Setup 5

IS Version: 6.2.0 alpha 5 SNAPSHOT
AWS Cognito Connector Version: 1.0.6 (built from repo)
Results: No Error. Issue not Reproducible

Setup 6

IS Version: 6.2.0 alpha 5 SNAPSHOT
AWS Cognito Connector Version: 1.0.7-SNAPSHOT (built from repo)
Results: No Error. Issue not Reproducible


Clear state after handshake is complete

This PR implements:

clean up handshake state after completion
finalised handshake returns session keys as opposed to ciphers

@mafintosh does the API look ok to you?


Add FLIP for invalidating references to tranferred resources

Description
When a reference is taken to a resource, that reference remains valid even if the resource was transferred. In other words, references stay alive forever. This could be a potential foot-gun, where one could gain/give/retain unintended access to resources through references.
This FLIP is to suggest introducing an invalidation of references, if the underlying resource is transferred from its original location where the reference was taken.

For contributor use:

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

@dsainati1

I like the general principle here, and agree that this removes a potential footgun, but I think that just having this be a runtime error is going to be a source of confusion, and if possible I think we should try to error statically.

Agreed, it would be great to improve this further and detect it also statically.
I don't know how we could implement this easily though, as this gets into the territory of adding a borrow checker, which we do not have at the moment.

This seems like it would be possible because we already have the tools necessary to determine whether a reference is valid in a given scope; we know statically once a reference has been moved out of a variable so that we can invalidate uses of it later. It seems like we could use the same principle to statically invalidate any references to that variable once the underlying reference is moved. The properties resources already have should make this analysis fairly simple since we cannot have aliases or nested references.

Do you mean references in "once a reference has been moved" and "once the underlying reference is moved"? We do not currently track references statically.

The above I think should be sufficient to error statically for references created and invalidated within the scope of a single contract or transaction, but would not be able to handle the case where someone saves a reference to a resource to their account and then the resource is transferred in a different transaction. My question on this point then is whether or not there is in fact a legitimate use case for having a reference to a resource that lives beyond the scope of the transaction or contract where it is created? If not, perhaps we could simply prevent saving resource-kinded references at all?

References are only valid during the life-time of a single program execution (transaction/script) and they cannot be stored. Capabilities exist for this reason.

Do you mean references in "once a reference has been moved" and "once the underlying reference is moved"? We do not currently track references statically.

Oh yea I definitely meant resources here.

References are only valid during the life-time of a single program execution (transaction/script) and they cannot be stored. Capabilities exist for this reason.

Ah ok well then if this is the case we should definitely be able to handle this statically. I don't think this is quite as complex as something like Rust's borrow checker because our use case is significantly more specific. Assuming that 1) we can know statically what resource a reference is pointing to (which we can because there are no resource aliases) and 2) we can know statically when a resource is invalidated/moved (which obviously we can), it should be possible to implement a checker rule effectively stating that a reference to a resource cannot be used anywhere that the resource itself could not be used. E.g. in the example from the FLIP:
let r <-create R()

let ref = &r as &R

account.save(<-r, to: /storage/r) // after this point `r` is no longer "live", it has been invalidated after the move
  // so we can thus also prevent anyone from using "ref" since we know it is a reference to `r`
ref.id = 2

I think statically validating all scenarios is not possible. For e.g: see the following example (from a test-case I added for the reference implementation): https://github.com/onflow/cadence/blob/fd35cb13d5318adf45e0d4128c4b829acf595d9a/runtime/tests/interpreter/resources_test.go#L2736-L2747
fun test(target1: &[R], target2: &[R]) {
    target1.append(<- create R())

    // Take reference while in the account_1
    let ref = &target1[0] as &R

    // Move the resource out of the account_1 into the account_2
    target2.append(<- target1.remove(at: 0))

     // Update the reference
    ref.id = 2
}

At checking time, it is not possible to determine whether the target1 and target2 are from the same account or not.

let r <-create R()

let ref = &r as &R

account.save(<-r, to: /storage/r) // after this point `r` is no longer "live", it has been invalidated after the move
  // so we can thus also prevent anyone from using "ref" since we know it is a reference to `r`
ref.id = 2

This may be not always true. See the modified version of the example:
let r <-create R()

let ref = &r as &R

let r2 <- r  // after this point `r` is no longer "live", it has been invalidated after the move.
             // But IMO "ref" is still valid because it is referring to the same 'resource value',
             // (i.e: reference is to the value, not to the variable `r`)
ref.id = 2

Yeah, we could detect some cases, which is better than none / only run-time checks, but we don't currently have enough static information to detect all cases.
I guess we would have to include the "location" of the target of the reference inside the type, which would be impractical in real-world programs. For example, assuming &T would point to a value on the stack, and e.g. &[0x1]T (straw-man syntax) for a reference to a value at address 0x1, then a concrete case of the test function above could be checked, but in practice you would want to abstract over the addresses (as e.g. contract functions usually work with any address)

This is very important and was a big security issue. But I think better to reach out people to fix implementations on mainnet before disclosing this ? I am sure I have seen more than one contract vulnerable to this.

@bluesign We have not analyzed any contracts if they are vulnerable, because as far as I can see that is possible to automate. Do you know of a way this could be statically analyzed? Feel free to DM me instead if you feel like that sharing this publicly would be problematic.

@bluesign

If we could just add immutability to cadence. [0] Then we could just make mutable reference immutable.

which would make this change mostly non-breaking ( I mean breaking less code )
only defend cases where it needs to defend ( without sacrificing usability )

[0] https://github.com/onflow/cadence/issues/1304

Thank you for bringing this up, I had misses this issue. In general, I think it would be a good idea to add readonly/immutable references, as it would also help with FLIP 703.
Let's say we would add readonly/immutable references, could you describe how that would prevent the "rug pull" attack? (Is that what you are referring to above?)

I think the proposed run-time enforcement would solve the security footgun but would also probably make the language worse overall in the long run. Generally any kind of error that only has runtime enforcement is going to be more confusing and frustrating for users than something with static checks (e.g. null reference errors in languages without optional types) and I think this one is going to be particularly confusing, since the cause and effect of the problem are not necessarily going to be obvious; moving a resource in one part of the code may invalidate references in arbitrary other parts of the code.
If we can't statically invalidate references to moved resources, then I think we should instead try to prevent the situation where references need to be invalidated at all. I like the linked PR about immutable/read-only references, since the security footgun presented by resource references is not an issue when the reference is immutable. Similarly, as you pointed out @turbolent, the issue with https://github.com/onflow/flow/pull/703 is also solved when the reference is immutable.
However, as pointed out, we cannot simply require that references to resource be read-only, since we need to support the Vault use case wherein users borrow a reference to another Vault in order to deposit into it. However, we could require that you provide some kind of "proof" that you own the resource or are otherwise allowed to mutate it, in order to use the mutable features. It's not super fleshed out but I am imagining the proof being something you need statically before you can "downcast" the immutable reference into a mutable one, and being obtainable either by owning the resource or being a resource itself that can be created by the owner of the original resource that allows you to perform a one-time mutation on the resource.

In my opinion Stack to Stack should be invalid. ( if I understood stack correct,  owner=nil )

Now that https://github.com/onflow/flow/pull/1056 has been merged in a more limited form than originally proposed, discussion on this FLIP should resume imo. Based on the discussion on that FLIP, it seems as though any analysis powerful enough to make this problem solvable statically would be too complex/burdensome for the language, so a dynamic solution is perhaps the right way forward in this case.

A draft implementation of this FLIP can be found at https://github.com/onflow/cadence/pull/1961

In my opinion Stack to Stack should be invalid. ( if I understood stack correct, owner=nil )
Though I think they can be valid in the same stack depth.

I feel invalidating a reference on a resource move from stack to stack(with different depths) can be too restrictive. Do you see any potential issues that it can cause?

@SupunS
Imagine simple purchase scenario, implemented naively like:
pub fun purchase(ftVault: @FT.Vault, receiver: Capability<&NFT.Receiver>){
   pre{
       ftVault.balance = self.sellprice
   }
   var NFT <- mintNFT
   receiver.deposit(<-NFT) // exits to unsafe code
   self.vault.deposit(<- ftVault)
}

This particular problem with pre/post conditions would be solved with the purity/mutability analysis and restriction in function conditions

**myContract Some Receiver Resourcer**
self.savedftVaultReference = &Vault
someContract.purchase(<-vault, receiver : myReceiver )
self.savedftVaultReference = nil

**someContract**
pub fun purchase(ftVault: @FT.Vault, receiver: Capability<&NFT.Receiver>){
   pre{
       ftVault.balance = self.sellprice
   }
   var NFT <- mintNFT
   receiver.deposit(<-NFT) // exits to unsafe code
             ----- Capability<&NFT.Receiver> Context Start - myContract Some Receiver Resource ---
                   self.stealerVault.deposit( <- savedftVaultReference.withdraw(amount: 42.0) )
                   self.collection.deposit( <- NFT )
             ----- Capability<&NFT.Receiver> Context End - myContract Some Receiver Resource  ---
   self.vault.deposit(<- ftVault)
}

oh, I see your point. Makes sense. Thanks for the example!

When I initially wrote this proposal, I was under the idea that, a reference should be only invalidated if the current location of the underlying resource is different from the location of the resource when the reference was taken.
e.g: If a reference rRef is taken to a resource r which is in account A, then if the resource is no longer in A when the  rRef is accessed, then the reference is invalid. On the other hand, if r is still in account A, then the rRef is valid.
But this leaves a catch: In-between the creation of rRef and the actual use of rRef, the resource r can be moved across different accounts/stacks, and come back to A (its original location). Now according to the above rule, this reference is still valid. In terms of a security perspective, I think this should be OK. One of the pros of this is that, it allows moving a resource within an account (e.g: within a collection), and can still maintain the validity of the reference.
But the more I look into this, the more I start to feel like it may be better to make it more strict by immediately invalidating references upon a move of the underlying resource. So even if the resource is back at its original location/account, the reference would be invalid.

My instinct would be to always make the reference invalid even if the resource is returned to the original spot. Just my two cents

Now according to the above rule, this reference is still valid. In terms of a security perspective, I think this should be OK.

This one is tricky, I agree with @joshuahannan on this, too many edge cases to handle.

Thanks for the feedback. Seems we are all on the same ground that transferring a resource should invalidate their references immediately, and should stay invalid, even if the resource is moved back to its original spot later on.

The only thing remaining is to decide on whether to tighten up the restriction more by also invalidating the references if the resource is moved from stack to stack.
I am adding below a full code example of the foot-gun @bluesign posted above, so that we can go through it and hopefully finalize during the next language design meeting.
access(all) contract Buyer {

    pub fun buy()  {
        let receiver: &Receiver ...
        let vault: @Vault ...

        // keep a reference to the vault, and transfer the vault to purchase something
        receiver!.vaultRef = &vault as &HelloWorld.Vault

        Seller.purchase(receiver, vault)
    }

    pub resource Receiver {
        priv let vaultRef: &Vault?
        priv let secretVault: @Vault

        init() {
            self.secretVault <- create Vault(0)
            self.vaultRef = nil
        }

        pub fun deposit(_ something: @AnyResource)  {
            self.steal()
            destroy something
        }

        pub fun steal()  {
            let stolen <- self.vaultRef!.withdraw(50)
            self.secretVault.deposit(<- stolen)
        }

        destroy() {
            destroy self.secretVault
        }
    }

    pub resource Vault {
        pub var balance: Int

        init(_ balance: Int) {
            self.balance = balance
        }

        pub fun withdraw(_ amount: Int): @Vault  {
            self.balance = self.balance - amount
            return <- create Vault(amount)
        }

        pub fun deposit(_ from: @Vault)  {
            self.balance = from.balance
            destroy from
        }
    }
}

access(all) contract Seller {

  pub fun purchase(_ receiver: &Receiver, _ vault: @Vault) {
    pre {
      vault.balance >= sellingPrice
    }

    receiver.deposit(<- create NFT())  // receiver will drain money from vault via the vault-reference
    self.vault.deposit(<-vault)
  }
}

So the agreement as per the last language design meeting was to invalidate the references even if the move is from stack to stack.
Updated the FLIP to reflect these changes: 98f88a7ceb4ee9adbfa9fa0d74c7546d640c2b31

Thank you all for taking the time to review and provide feedback.
Based on the feedback, it seems there are no negative sentiments towards the proposal, and hence I'm gonna consider this as accepted.


Design updates

@eesh @stefania11 @tqiu8 @satvu
This is a work-in-progress PR of mostly refactoring, prepping for design. Please ignore broken styles for now. See updated Readme for run directions.

Removed login and NLC logic. Deleted views and commented model/controller code
Reorganized + renamed to consistent files, folders, route names. Deleted unused.
Added Handlebars, refactored HTML to templates, shared header
Extracted all CSS from HTM

A couple of issues:

Getting a mongo error on startup. Localhost works. If I run mongod in another tab error goes away. Anyone getting this?

(node:21888) UnhandledPromiseRejectionWarning: MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED <IP_ADDRESS>:27017]

Getting an error when adding Text classifier classes, I renamed a lot of routes and var names, I think it's related to that.. can someone QA if anything else broke?

Todo:

update header to show/hide correct links via Handlebars logic
dedupe CSS, reapply existing styles and continue redesign
comment more auth token code left over from registration

Mongo error might be related to version change
https://stackoverflow.com/questions/50448272/avoid-current-url-string-parser-is-deprecated-warning-by-setting-usenewurlpars


Gateway API validations too strict for redirect status codes

What happened:
Gateway API has validations that only account for 301 and 302 HTTP Redirects.
https://github.com/kubernetes-sigs/gateway-api/blob/1edf7e93ae4bb8c5ea5cc2193586cfe1e5d15e2f/apis/v1/httproute_types.go#L1069
What you expected to happen:
RFC 2616 defines several other redirects, including: 303, 304, 305, and 307.
Anything else we need to know?:
Ask would be to align enum validations to RFC2616 section 10.3
Thank you!

It seems very reasonable to me to ensure that all the valid redirect codes can be used in this enum.
But it does raise the question of whether we should be testing the behavior for each redirect code? Currently we are only testing 301 in the conformance tests.

It seems very reasonable to me to ensure that all the valid redirect codes can be used in this enum.

+1

But it does raise the question of whether we should be testing the behavior for each redirect code? Currently we are only testing 301 in the conformance tests.

Yes, it does seem like some simple conformance tests around this would be ideal to help reduce implementations being caught off-guard by requirements.

But it does raise the question of whether we should be testing the behavior for each redirect code? Currently we are only testing 301 in the conformance tests.

+1 on having conformance test coverage for the additional status codes.

/remove-lifecycle stale
To loop back around, is it acceptable to follow RFC; outstanding action being additional conformance test coverage for addition of those status codes?

/remove-lifecycle stale
To loop back around, is it acceptable to follow RFC; outstanding action being additional conformance test coverage for addition of those status codes?

Thanks for the follow up on this. Since this is relatively small in scope, I don't think we'd really need a GEP for this, but I'd love to see it get into v1.2.

Given all the supportive comments above, I think we can mark this as accepted.
/triage accepted

@JackStromberg do you have time to work on this?

RFC2616 is quite outdated, so the status list from the original post is incomplete.
RFC9110 adds the 308 response code as well https://httpwg.org/specs/rfc9110.html#status.308


Reference Paper

Hi Mauricio,
In the paper I read that the package depends on the tidyverse but in the DESCRIPTION I see no tidyverse packages.
I could be missing something.

Sorry! It was dplyr based but now it's Matrix based. I'm fixing it on
Saturday
On Fri, Feb 14, 2020, 8:21 AM John (JP) Coene<EMAIL_ADDRESS>wrote:

Hi Mauricio,
In the paper I read that the package depends on the tidyverse but in the
DESCRIPTION I see no tidyverse packages.
I could be missing something.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pachamaltese/economiccomplexity/issues/12?email_source=notifications&email_token=ACM7UOK6BSOYUNXSFNC4K63RCZ5CJA5CNFSM4KVGD5P2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4INRIBIA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM7UOL54W5GK7MQFXIM23DRCZ5CJANCNFSM4KVGD5PQ
.

Thanks @pachamaltese, this seems solves now. If you close this I'm good to approve the review on my side: sorry, I know this took some time.

thanks @JohnCoene, I generated a new pdf


Crash after importing file

Your program gave me a log and sent me here after a crash, so hopefully you can tell me what went wrong
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
      _________ __                __________.__
     /   _____//  |______  ___  __\______   \__|_____
     \_____  \\   __\__  \ \  \/  /|       _/  \____ \
     /        \|  |  / __ \_>    < |    |   \  |  |_> >
    /_______  /|__| (____  /__/\_ \|____|_  /__|   __/
            \/           \/      \/       \/   |__|

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                        Environment
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

StaxRip    : <IP_ADDRESS>
Windows    : Windows 10 Pro 1703
Language   : English (Canada)
CPU        : Intel(R) Pentium(R) CPU G3220 @ 3.00GHz
GPU        : Intel(R) HD Graphics, NVIDIA GeForce GTX 970
Resolution : 1920 x 1080
DPI        : 96

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                   Source file MediaInfo
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

C:\Users\*****\Desktop\Encoding\Stax\Settings\Scripts\dbUP.vpy

General
Complete name : C:\Users\******\Desktop\Encoding\Stax\Settings\Scripts\dbUP.vpy
File size     : 700 Bytes

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                         Exception
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
   at StaxRip.TaskDialog 1.Show() in D:\Projekte\VS\VB\StaxRip\UI\TaskDialog.vb:line 301
   at StaxRip.MainModule.MsgError(String text, String content) in D:\Projekte\VS\VB\StaxRip\General\General.vb:line 1311
   at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable 1 files, Boolean isNotEncoding) in D:\Projekte\VS\VB\StaxRip\Forms\MainForm.vb:line 1741

and the script that caused it
import vapoursynth as vs
core = vs.get_core()

core.std.LoadPlugin(path=r'C:\DankFilters\smash\vslsmashsource.dll')
core.std.LoadPlugin(path=r'C:\DankFilters\fmt\fmtconv.dll')
#core.std.LoadPlugin(path=r'C:\DankFilters\f3kyuu\flash3kyuu_deband.dll')
core.std.LoadPlugin(path=r'C:\DankFilters\Waifu\Waifu2x-caffe.dll')
core.std.LoadPlugin(path=r'C:\DankFilters\BM3D\Win64\BM3D.dll')

clip = core.lsmas.LWLibavSource(source=r'F:\Upscale\RAW\01.mkv')
clip = core.fmtc.bitdepth(clip,bits=32)
#clip = core.f3kdb.Deband(clip, sample_mode=2, dither_algo=3, output_depth=8)
clip = core.caffe.Waifu2x(clip, noise=1, scale=2, block_w=512, block_h=512, model=3, cudnn=True, processor=0, tta=False)

Hi,
the line that first failed was trying to show a TaskDialog, see:
https://msdn.microsoft.com/en-us/library/windows/desktop/bb760441(v=vs.85).aspx
this task dialog was trying to show an error message returned from VapourSynth so probably there was something wrong with your vpy script. Does this script open in another program, if not does it give a error message? I've tried to import a similar but simplified script:
import vapoursynth as vs
core = vs.get_core()

core.std.LoadPlugin(path=r"D:\Projekte\VS\VB\StaxRip\bin\Apps\Plugins\vs\vslsmashsource\vslsmashsource.dll")
clip = core.lsmas.LWLibavSource(source=r"D:\Temp\staxrip\ash.mkv")
clip.set_output()

which is working. I received a similar bug report a few years ago but don't remember if it could be solved. I've googled for
TaskDialog UnauthorizedAccessException
and for
TaskDialog E_ACCESSDENIED
unfortunately I didn't find anything, internally staxrip uses the task TaskDialog API all over the place, even to ask where the settings should be saved on the very first start, old APIs like MessageBox are not used. Since you are a programmer maybe you can try a couple of different things to narrow the problem.
Does TaskDialog now never work and staxrip is totally unusable on your system or does it only not work under certain conditions? You can trigger a task dialog for instance with Tools > Scripts > Re-mux

Adding the fmtc line I get:
VFW module doesn't support YUV420PS32 output

I believe it may actually have been a permissions issue. Just reopening the program without changing any settings or code in that script net me an error in Vapour Synth Compilation, which is to be expected.
I have no way of accurately reproducing the bug, so that log is all I have. Staxrip is still perfectly usable now. so I dont know if this is a problem that needs fixing or something to hunt down for fun when you have free time.

I just hope it don't happen again.


Allow implicit init values of unions only to unions of simple basic types

Purpose

Fix #13903
Depends on #13907

Codecov Report

Merging #13956 into master will decrease coverage by <.01%.
The diff coverage is 80%.

@@             Coverage Diff              @@
##             master   #13956      +/-   ##
============================================
- Coverage     64.56%   64.56%   -0.01%
  Complexity      426      426
============================================
  Files          2156     2156
  Lines         95554    95563       +9
  Branches      12744    12745       +1
============================================
+ Hits          61698    61700       +2
- Misses        28841    28845       +4
- Partials       5015     5018       +3

Impacted Files
Coverage Δ
Complexity Δ

...nalang/compiler/tree/expressions/BLangLiteral.java
63.63% <0%> (-9.1%)
0 <0> (ø)

...ng/compiler/semantics/model/types/BFiniteType.java
90.9% <100%> (+0.9%)
0 <0> (ø)
:arrow_down:

...ang/compiler/semantics/model/types/BUnionType.java
86.66% <100%> (+9.39%)
0 <0> (ø)
:arrow_down:

...llerinalang/compiler/semantics/analyzer/Types.java
74.27% <50%> (-0.16%)
0 <0> (ø)

...lang/compiler/semantics/analyzer/CodeAnalyzer.java
84.63% <84.61%> (-0.06%)
0 <0> (ø)

...allerinalang/net/jms/LoggingExceptionListener.java
50% <0%> (-50%)
0% <0%> (ø)

...allerinalang/test/util/client/ResponseHandler.java
65.38% <0%> (-15.39%)
0% <0%> (ø)

...rinalang/runtime/threadpool/ThreadPoolFactory.java
61.9% <0%> (-4.77%)
0% <0%> (ø)

...a/org/ballerinalang/bre/bvm/WorkerDataChannel.java
80.86% <0%> (-1.86%)
0% <0%> (ø)

...llerinalang/stdlib/socket/tcp/SelectorManager.java
70.08% <0%> (-1.71%)
0% <0%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Added option to turn off templates and allowed for infinite lettersets

MultiZarrToZarr.translate() now accepts a template_count=x kwarg. Default is 5, change to None to disable templates entirely.
letter_sets() has also been updated to generate an infinite amount of template identifiers to better support large MultiZarrToZarr datasets

Add a test? It'd be interesting to see the difference in file size, and load time.

The multizarr_example.json is 22 KB with templates, and when I turn off templates it's 43 KB, so nearly double the size.
Loading in the dataset with fsspec.filesystem() and xr,open_dataset() took 728 ms for the file with references, and 735 ms for the one without references, from my local machine.

Interesting numbers, thanks. Doubtless it depends greatly on the specifics of a dataset. Binary representations with internal compression (parquet, zarr) should do very well with the repeated strings when avoiding templates.


Think about a way to return imexam() results to the current session

Tricky in the blocking loop I have to use for DS9, maybe easier for the Ginga viewer.
The return would be one or more variable the user has access to after the imexam event loop closes.

@hcferguson  I'll work on the interactive solution, just realized I forgot to show how to pull just the data, without the interactive plot,  in a way to save it to vars, this is how I run my package tests:
from imexam.imexamine import Imexamine
from astropy.io import fits

data=fits.getdata('iacs01t4q_flt.fits')
plots=Imexamine()
plots.set_data(data)
radii,flux=plots.radial_profile(532,415,genplot=False)

In [23]: radii
Out[23]: array([0, 1, 2, 3, 4, 5, 6, 7, 8, 9])

In [25]: flux
Out[25]:
array([<PHONE_NUMBER>9,  1523.00508499,<PHONE_NUMBER>4,<PHONE_NUMBER>5,
          73.30728304,<PHONE_NUMBER>8,    60.45689106,    47.39679968,
          16.43066466,     6.33795738])

The above works if you already know the locations, genplot is an option for most of the plots I believe.
I'll think about the best interactive way to return the arrays from the various functions.

This is the other method I use to grab info from the current figure:
plots.plot_line(50, 50)
f = plt.gca()
xplot, yplot = f.lines[0].get_xydata().T


🐛 [firebase_auth] updateDisplayName() not working after createUserWithEmailAndPassword

Bug report
I have a basic Future creating a new account.
  Future<void> signUpWithemail({required String email, required String password, required String name}) async {
    emit(const AuthLoadingState());
    try {
      final user = (await _firebaseAuth.createUserWithEmailAndPassword(email: email, password: password)).user;
      if (user != null) {
        // add the name to the account
        user.updateDisplayName(name);
        _firestoreCubit.createUser(user: user);
        emit(AuthNewAccountState(user: user));
      }
    } on FirebaseAuthException catch (e) {
      if (e.code == 'email-already-in-use') {
        emit(AuthErrorState(error: e.message!));
      } else {
        emit(const AuthErrorState(error: 'SignUp failed! Please correct your credentials'));
      }
    }

While in this proces, i'd like to change the display name and save the whole user to my database.
Everything works fine but displayName: null is not changed.
I tried await user.reload() after changing the displayName.
in my debugger the user is also not changing when calling user.updateDisplayName(name);
Steps to reproduce
Steps to reproduce the behavior:
Create a user
final user = (await _firebaseAuth.createUserWithEmailAndPassword(email: email, password: password)).user;

then try to change the displayName
user.updateDisplayName(name);

Expected behavior
Expected to change the displayName, at least after a reload()
I need an option to change the display name directly.

Additional context
There was a ticket #7274 on iOS, but he said the reload() fixed it.
I'm currently only developing on Android.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[√] Flutter (Channel stable, 2.8.1, on Microsoft Windows [Version 10.0.19044.1503], locale de-DE)
    • Flutter version 2.8.1 at C:\Flutter\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (7 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc5)
    • Android SDK at C:\Users\vince\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0-rc5
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.9.2)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.9.31112.23
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code, 64-bit edition (version 1.63.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.34.0

[√] Connected device (4 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Windows (desktop)           • windows       • windows-x64    • Microsoft Windows [Version 10.0.19044.1503]
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 98.0.4758.81
    • Edge (web)                  • edge          • web-javascript • Microsoft Edge 93.0.961.52

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.15.1
Flutter SDK 2.8.1
nutrition_db 1.0.0+1

dependencies:
- cloud_firestore 3.1.7 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.4
- equatable 2.0.3 [collection meta]
- firebase_auth 3.3.6 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.12.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_bloc 8.0.1 [flutter bloc provider]
- flutter_form_builder 7.1.0 [flutter intl]
- flutter_spinkit 5.1.0 [flutter]
- form_builder_validators 7.4.0 [flutter flutter_localizations intl collection]
- google_sign_in 5.2.3 [flutter google_sign_in_platform_interface google_sign_in_web]

dev dependencies:
- flutter_lints 1.0.4 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.8.2 [collection meta]
- bloc 8.0.2 [meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.0
- charcode 1.3.1
- clock 1.1.0
- cloud_firestore_platform_interface 5.4.12 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.6.7 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.15.0
- fake_async 1.2.0 [clock collection]
- firebase_auth_platform_interface 6.1.11 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.3.7 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.2.4 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.5.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- flutter_localizations 0.0.0 [flutter intl characters clock collection meta path typed_data vector_math]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- google_sign_in_platform_interface 2.1.1 [flutter quiver]
- google_sign_in_web 0.10.0+4 [flutter flutter_web_plugins google_sign_in_platform_interface js pedantic]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.3
- lints 1.0.1
- matcher 0.12.11 [stack_trace]
- meta 1.7.0
- nested 1.0.0 [flutter]
- path 1.8.0
- pedantic 1.11.1
- plugin_platform_interface 2.1.2 [meta]
- provider 6.0.2 [collection flutter nested]
- quiver 3.0.1+1 [matcher]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.3 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0 [collection]
- vector_math 2.1.1```

</details>

---

@DiegoTheWolf
Can you try the official plugin example and see if you still get same behavior using it ?

@DiegoTheWolf
Thanks for the update. If you log out and then login, at that time, do you see the updated name ?


GitHub action generate catalogue fails

Hi all,
I think there is a problem with the generation of the catalogue. The github action fails, and the last success is of two months ago:

You are right! I will investigate it now.


Make using separate debugging info easier.

Things done

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

[x] NixOS
[ ] OS X
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

The previous iteration of debug info required that all of the packages
were "installed". This is suboptimal because "installing" all of the
programs you want to debug as well as the libraries that they use.
This method enables debug symbols for all loaded files as long as those
symbols are present in the nix store, as well as a command to download
those symbols from binary caches for all loaded object files.
This is implemented by adding a new section to the executable witch
contains the path to the debug symbols. An extension that is auto-loaded
by GDB then uses this information to automatically load these symbols
whenever the object file is loaded.
Future work:

[ ] Find a way to make all packages build with debug symbols by default.
[ ] Find a better way to "attach" debug symbols to packages (weak references?)

Interesting! I would very much like to have this feature.

Doesn't including the path to the debug symbols in the executables make the executables depend on the debug symbols? That would defeat the purpose of separate debug info...

@edolstra: If so, maybe we can add support for "weak store references" in nix? Or some way to simply ignore certain store path references (to prevent them being hard dependencies)?

@edolstra Yes. This is currently worked around by adding a space in the middle of the hash portion of the store path. This has downsides because now the debug packages don't automatically get pushed to a cache with nix-push. This might be a legitimate use case for weak references as @bjornfor mentions.
On a vaguely similar note. Because the debug info is compressed any references it holds are not recognized. This isn't a big deal right now because it appears that the only thing that gets referenced is the package it came from but if we discover a solution for embedding proper source paths it will become a nuisance. Is there any support for handling references that get mangled in some way?

it appears that the only thing that gets referenced is the package it came from

Upon closer inspection it also references all of the libraries the program is linked with. This probably still isn't a big deal as the package itself should reference these as well.

@kevincox Ah, thanks for the clarification. However, hiding references in this way is essentially a weak reference, which is problematic because it may make derivations produce a different result depending on whether a -debug store path is present or not. This is not a theoretical concern: we use Nix builds at work to run automated tests, where we invoke gdb to produce stack traces on failure. So unless chroot builds are enabled, this could produce different output if debug symbols are present in the Nix store of the build machine.

@edolstra I see what you are saying. You would get different stack traces if the symbols were present in the store. While there are downsides to this I think that this could probably be considered a benefit at the same time. We don't want to stop you from debugging your code, but if available you will get a better experience. This is where legitimate weak reference scheme would add benifit.
Also I don't know how you are generating stack traces but you can either download the debug info before grabbing the trace (and now your traces are more complete) or if you are taking core dumps it doesn't matter if there is the info present on the target machine, because you can download the debug symbols to the machine you are debugging on (assuming they are available on a binary cache)
Also this isn't much worse then the existing method as your stack traces would change based on what is "installed" at the time, rather then just the store paths themselves.
So while I see the downside of determinism I think the benefit here is clear and we should look into ways to get the best trade-offs.

I remove the point about source inclusion because it is a huge file size and it isn't incredibly useful because it is fairly easy to acquire the source yourself. If one day we want to add it it can be done later.
What are the thoughts about inclusion? I've been using this on my machines and it is very helpful for debugging crashes.

@kevincox: I don't see into implementation details of this PR, but what about adding references from the debugging outputs instead of the regular ones? That wouldn't require any reference hiding or weak references, and I believe it's reasonable that the debug outputs would (transitively) reference debug outputs of  the whole library-closure.

what about adding references from the debugging outputs instead of the regular ones

I don't follow what you are saying. We need a reference from the regular output to the debug output so that the debugging symbols can be found.

I meant that you would need to "install" (in some way) the app.debug output but nothing else (not the depending libraries).

This isn't really feasible as the links in the debugging information point to the linked binaries, not their debugging information. Also for me the single command install without looking up paths is the killer feature for me. I don't want to have to remember when, where and with what flags I compiled the program. Basically in my flow I never remember the path of the debug info, instead it is automatically pulled from the binary at debug time.

I think it would still be automatizable, as e.g. for stuff built without substitutes we've got:
nix-store --realize "$(nix-store -q --deriver /path/to/your/executable)!debug"

but certainly I don't think there's any "perfectly pure" way as simple as this PR (which makes it tempting).

@vcunat IIUC that would require that you have the derivation spec on the machine that runs the command. Maybe I'm using Nix "unusually" but I build all of my packages on a CI server then upload to a binary cache, only storing the store path of the "useful" output(s). This means that the derivation is gone forever (save checking out the nixpkgs version and git version of my package and building it again).
The way I have it now will work as long as you have any way to build the debug output, whether that is the derivation, or access to any binary cache with the debug output.

Are there any updates on this pull request, please?

I'll close this because relying on hidden references is not a good idea IMHO (for instance it will break with hash rewriting). You can get debug symbols automatically by using dwarffs.


Possibility to calculate diff without applying the changes (patching) to the dom

I would like to calculate the diff between two trees, without patching, because it will be done in a webworker (without access to the DOM).
Similarly to what is done here: https://github.com/Matt-Esch/virtual-dom
var patches = diff(tree, newTree);
rootNode = patch(rootNode, patches);

Can this be done in this vdom implementation?

Actually not. But I think defintely worth adding it


Better interrogate function imp

Better interrogate function imp:

[x] Support predefined base64 images.
[x] Support model setting (clip/deepdanbooru).
[x] Compatible with previous versions.
[x] Tested with passing jpeg-base64 images, fine.

Thank you :)


RoxyHelper`s fixPath issue

This method has added duplicate of basePath on windows filesystem.

Hi @Nivans,
can you try branch dev-2.x
master branch has been discontinued because bug of roxyfileman.

Hi @Nivans,
try release version <IP_ADDRESS>


remove duplicate text

Text in Introduction section “We plugin Poseidon as an add-on scheduler to K8s, by using the 'schedulerName' as Poseidon in the pod template this will by-pass the default-scheduler.” repeated twice.

Hi, robot, I have signed the CLA, please check it for me.

/test ci-poseidon-e2e-gce


Add textwidth=72 vim setting for all POD6 documentation files

This allows documentation to be formatted to have the correct line
length as per the style guide with gq in vim.

Some files were missing a softtabstop=72 setting, and some files use ft=raku instead of ft=perl6. Which ft setting should be used? Should there be a test of some sort to ensure vim settings exist in documentation?

See https://github.com/Raku/doc/issues/3280
Why not just configure vim to apply certain properties to files with particular extension?

Why not just configure vim to apply certain properties to files with particular extension?
I already do. I made this PR because the docs are the exception WRT style for text width when it comes to the Raku files I work with. Removing the vim config entirely is something I'm against doing, but why and how it can better be handled is something I'll explain in the issue.

...oh, there is a way to configure vim for specific directories that's fairly painless, making this PR kind of pointless.

Thanks, Ben, anyway, and for understanding this. Also, I am not really keen on PRs that span hundreds of files. You do have to review them one by one anyway, just in case, and it's a pain.


Feature/map on load

onLoad prop for map component. useful for setting event listeners on map object

Sorry, I'm doing a refactoring at the moment. Would you consider raise this again afterwards? Some review comments:

don't compile lib, I'll do it for you
what kind of event listeners do you need that is not supported by react-google-maps currently?

#157 is landed. Would you consider revisit this again?
Actually I'm not a big fan of exposing google map object to the outside. It may lead to misuse of the object and lose the advantage of using React.

@tomchentw I was trying to set an event listener for "center_changed" on the map object. Is there currently a way to do this? The callback is nice because it lets you add any logic that may need to take place once the map has been created.

@mbahoshy the center_changed is supported and you can set it via props.onCenterChanged on the <GoogleMap> component.
https://github.com/tomchentw/react-google-maps/blob/master/src/eventLists/GoogleMapEventList.js#L5
See Geojson example for using onZoomChanged:
https://tomchentw.github.io/react-google-maps/#geojson

@tomchentw thanks exactly what I am looking for, I missed this feature. I could still see the virtue of an onLoad function, maybe w/o map object in callback.

You don't need onLoad after #157 is landed with callback refs. At the time the callback is invoked, the component is initialized and loaded.


CORS plugin: always allow credentials

Change to include the Access-Control-Allow-Credentials header in CORS responses. This header is required to let you send requests with credentials - e.g. including cookies with requests.
More info here:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS#Access-Control-Allow-Credentials

Thanks a lot, merged now!

You're welcome - thanks.


Main build failure due to missing nuget packages

Describe the bug
Running buildall requires authentication to access the
https://microsoft.pkgs.visualstudio.com/ProjectReunion/_packaging/Project.Reunion.nuget.internal/nuget/v3/index.json
Steps to reproduce the bug
run devcheck
run buildall
Additional context
A previous #/pulls/494 attempted to solve the problem, but failed.
tools\nuget\microsoft.taef.10.75.221207001.nupkg is outdated, the project actually relies on v10.82 and it adds 50MB to the repository. A real solution would be to make all packages downloadable from nuget.org instead of caching them locally or relying on any unstable servers.

About a year ago we disabled the ability to perform custom builds due to low usage and high maintenance costs. The builds have been disabled by design.
This is the first issue that has been reported about the build requirements and we would love to understand your scenario, if you're able to share.

Even I am hitting this error, also the NuGet restore keeps asking private/internal Microsoft azure artifact credential.
It doesn't work with either MS account or GitHub account.
(Nuget.exe restore doesn't help)


WORK_DIR -w output empty

What happened?
I am trying to get the native space cifti data from fmriprep so that I can determine if the sulcal artifact in the 91k dtseries is present in the native surface. Per our lane1 conversation I have been trying to use the -w flag to obtain these data as output, however the wordir remains empty even though it is written to in the logs.
Thanks
What command did you use?
/usr/local/pipelines/subfmri-arg_latest -i /MRI_DATA/nyspi/patensasc/rawdata -o /MRI_DATA/nyspi/patensasc/derivatives -l /MRI_DATA/nyspi/patensasc/derivatives/fmripreplogs/working.log -a "--participant-label patensasc0085 --output-spaces T1w MNI152NLin2009cAsym:res-2 --cifti-output -w  /MRI_DATA/nyspi/patensasc/derivatives/fmriprep/WORK_DIR "

What version of fMRIPrep are you running?
nipreps/fmriprep:21.0.0
How are you running fMRIPrep?
Docker
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
fMRIPrep finished successfully!

Additional information / screenshots
No response

This looks like you are using a third-party wrapper (/usr/local/pipelines/subfmri-arg_latest) to run fmriprep - I would guess there is flag to pass in a working directory but you should reach out to whoever manages that

We had to mount locally! Thanks so much Mathias


Make the queue reorderable

It would be great to be able to organise and reorder the queue by dragging and dropping songs into different positions.

Agreed!
I'll probably not do it with drag and drop however, it isn't very convenient for long queues and small screens.
I'm thinking about displaying floating buttons when a selection is active, which will allow moving rows up and down.


.toEqual()

As previously discussed, toEqual must be compatible with jasmine 1's version of the same for the time being. The two changes we made in Jasmine 2 to relax the matcher are:

Do not check for constructor name equality.  People should care about this in their type-checker but not in a test file.
Skip undefined fields in both a and b. This one I somewhat think we should fix, but unless you go and do the work on www I see no way of shipping this.

Alternatively we can run a huge codemod using Jest inside of a jscodeshift transform to codemod the failing tests to a new matcher that matches the current implementation of toEqual. I'm not really ready to do it and would like us to focus on pretty-printing the error output first; then make these large changes later.
Another thing I want to bring up is whether you thought about not printing either objects in red. My biggest problem in a sentence like Expected <loads of gibberish> to equal <more gibberish> is always to find where the first object ends and the second one starts. Can we print the two objects in black and the rest of the sentence (to equal and Expected etc.) in red? What do you think?
Finally, if you can find the fastest toEqual implementation on the planet and use that, I would be happy. It is the most used matcher by far and we run some pretty huge objects (in ads code) through it.

Let's invert the colors.
Like here:

I'm always confused by "actual" being green in the failing test. The whole point is that actual value is the wrong one. So it should be red.

I'm confused when it doesn't match what I'd see in a diff on GitHub.  i.e. when actual is red.  It's unfortunate that we have the same colour conventions for good/bad and added/deleted.

i don't like the actual/expected idea at all. every time i see the diff i spend a few seconds trying to figure out what is actual and what is expected.
also the fact that actual value is passed into the function that is called expect naturally confuses the human brain
expect(actual).toEqual(expected)

my thoughts on this were to get rid of these terms completely and replace them with:
added/missing instead. this way it's very clear what should be green and what should be red

I was discussing this with @cpojer and he said something very similar about expected vs. actual.  I've never seen this as confusing, but that may just be a privilege of being a native speaker 😄
added/missing sounds like a good idea for diffs.  For tests that aren't diff maybe s/expected/correctValue/ and s/actual/observedValue/?

Let's have this discussion separately from this diff which is about pretty-printing the values. I care more about changing the colors around so that printing two objects I can still see whether it says "to equal" or "to be". I can do that in a separate diff.
For actual/expected, I think we need to have a bit more of a discussion. I'll think about it.

I'm confused when it doesn't match what I'd see in a diff on GitHub. i.e. when actual is red. It's unfortunate that we have the same colour conventions for good/bad and added/deleted.

I think GH logic doesn’t quite apply there. You’re not really “starting” from the expected value and then changing your app to output the wrong thing.
I can imagine that when you start thinking about it, it might feel incorrect, but if you just glance without thinking or if you are drunk, I think “red is bad” feels much more intuitive.

I think green doesn't have a place in this context. Should be red and white, imo. Red being the erroneous value

@yaycmyk: in reality there are 3 colours for object diffs:

text that is in the expected value but not the actual value.
text that is in the actual value but not the expected value.
text that is the same in both the actual value and expected value.

The debate is which way round the colour coding is.  The alternative would be to choose two completely unrelated colours (e.g. yellow and blue) so you avoid having any intuitive expectations.
@gaearon I think we may always disagree on this point.  The way I see it, especially with snapshot testing, is that the first run of the test creates the snapshot, so every subsequent test should be showing me what's changed from that snapshot.  I suspect that if you were to run polls for what the most popular answer is, you could get people to prefer either answer with subtly different wording of the question.

The way I see it, especially with snapshot testing, is that the first run of the test creates the snapshot, so every subsequent test should be showing me what's changed from that snapshot

Oh, I can see how this can be confusing.
I was thinking only about generic toEqual, not about snapshot testing.

I think that snapshot testing should use diff coloring. This makes total sense because you interpret it as a diff which you can review.

red = old
green = new
However I also think that regular assertions don’t need to be like diffs because most of the time (hopefully) tests will be stable, and regular code will need to be adjusted per tests. So I think this color scheme makes more sense for regular assertions:

red = actual
green = expected
I just wanted object diffs (https://github.com/facebook/jest/pull/1439#issue-171540384) to follow the same convention.

I'll send a new PR that uses jasmine's toEqual matcher for now and then another PR on top of that to polish all the messages and their colors.


Added much needed documentation

The code is a godsend but I added a couple of dozen comments to explain the complicated procedure. Unfortunately it makes the file more than 1MB bigger but I'm sure this is a worthy sacrifice.

I will send your code for review and will be coming back to you withing 5 business days. You may work on other features for now.


[QUESTION] Laravel Excel Umlauts not working

ExampleCSV.zip

Prerequisites

[x] Have read and understood: https://github.com/Maatwebsite/Laravel-Excel/blob/3.1/.github/SUPPORT.md
[x] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[x] Checked that your question isn't already asked before.
[x] Filled in the entire issue template

Versions

PHP version: 7.3.13
Laravel version: 6.4.1
Package version: 3.1.18

Description
Hello, I am currently working on my diploma thesis for school which requires a user import for pupils and teachers with an external .csv or .xlsx to a MariaDB database. I read the information on Github and the official website about umlauts but they still won't show up as expected. For example: Köfing, König or Weißinger in my .csv-file show up as K??fing, K??nig and Wei??inger in my database. I enabled UTF-8 as mentioned in the documentation which didn't work. I also tried if it was a specific problem of Laravel itself which wasn't the case either.
I tried to change the encoding of my .csv-file with Notepad++ which resulted in umlauts errors in my .csv when opening it with Excel. Before the change the encoding showed up as UTF-8-BOM in Notepadd++, which is probably the cause of the error in Laravel-Excel.
I tried it with changing the input_encoding to "UTF-8-BOM" which caused an "iconv(): Wrong charset, conversion from 'UTF-8-BOM' to `UTF-8//IGNORE//TRANSLIT' is not allowed" error
It is hard for me to post a specific code because of duplication detection but if there is any required I'll do so.
Thank you
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
I put an example of my import files into the attached files, to reproduce there shouldn't be anything special to do, just try to use umlauts in any .csv file.

Okay, nevermind, I'm just dumb. I tried to get a username out of family name and first name. F.e. Max Mustermann will be m.mustermann or Max König equals m.könig. The family name and first name are getting imported correctly, its just an error with the transformation to lowercase letters when building a username.


Add bibliography support

There is a gem to add bibliography: https://github.com/riboseinc/asciidoctor-bibliography
Would be nice to have it available on the default installation of AsciiDocFX.

Yes... This is needed badly.  If Asciidocfx can use this it will become the monster that I need:

Bibliography with support for csl standard
BibTex support for styles and the ability to read and use bib files
Cross-references


WIP - clicking issue on mrjsio

Linking
Fixes https://github.com/Volumetrics-io/mrjs/issues/434
Fixes https://github.com/Volumetrics-io/mrjs/issues/450
Related to https://github.com/Volumetrics-io/mrjs-landing/pull/1
Problem
See the noted issues
Solution
tbd.

Required to Merge

[ ] PASS - all necessary actions must pass (excluding the auto-skipped ones)
[ ] TEST IN HEADSET - main dev-testing-example and any of the other examples still work as expected
[ ] VIDEO - if this pr changes something visually - post a video here of it in headset-MR and/or on desktop (depending on what it affects) for the reviewer to reference.
[ ] TITLE - make sure the pr's title is updated appropriately as it will be used to name the commit on merge
[ ] BREAKING CHANGE

make a pr in the documentation repo that updates the manual docs to match the breaking change
note: the docs underneath the Javascript API section come automated from the jsdocs inline with the code itself
link the pr of the documentation repo here: #pr
that documentation repo pr must be approved by @lobau

looks like the issue is specific to the rotating colliders and what is closest
since the models are rotating their colliders are coming in the way of that of the objects themself - gonna noodle thru this a bit in relation to if we can grab a specific link versus closest

also the model colliders are huge compared to their own size - still looking into why the diff in size expectation

additional noodle: part of it is due to resize changing scale of bbox though reload of page fixes it


Add custom variable in launch.json through input

I'd like to have a fourth type of input variable named custom which could solve the case where we'd like to define a custom variable which is used in different part of the launch.json
As a use case, I have a a set of env variables depending on my build folder which is defined in a file in this build folder
and the binary i'd like to debug is also in this build folder in that case I could define only once this value.
ie:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "inputs": [
        {
            "id": "BUILDDIR",
            "type": "custom",
            "value": "mybuilddir"
        }
    ]
    "configurations": [
        {
            "name": "GStreamer - Build and debug",
            "request": "launch",
            "type": "cppdbg",
            "windows": {
                "type": "cppvsdbg",
                "program": "gst-launch-1.0.exe",
            },
            "osx": {
                // https://github.com/microsoft/vscode-cpptools/issues/8411
                "envFile": "${workspaceFolder}/${input:BUILDDIR}/gst.env",
                "MIMode": "lldb",
            },
            "linux": {
                "envFile": "${workspaceFolder}/${input:BUILDDIR}/gst.env",
                "MIMode": "gdb"
            },
            "cwd": "${workspaceFolder}/${input:BUILDDIR}/subprojects/gstreamer/tools/",
            "program": "${workspaceFolder}/${input:BUILDDIR}/subprojects/gstreamer/tools/gst-launch-1.0",
            "args": [
                "videotestsrc",
                "!",
                "autovideosink"
            ],
            "environment": [
                {
                    "name": "GST_DEBUG",
                    "value": "4"
                },
            ],
            "stopAtEntry": false,
            "console": "externalTerminal",
            "symbolOptions": {
                "searchPaths": [
                    "${workspaceFolder}/${input:BUILDDIR}",
                ],
                "searchMicrosoftSymbolServer": true,
                "cachePath": "${workspaceFolder}\\${input:BUILDDIR}\\cache",
                "moduleFilter": {
                    "mode": "loadAllButExcluded",
                    "excludedModules": []
                }
            }
        }
    ]
}

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


offCanvas: Cannot read property 'contains' of undefined

getting above error on console when click to open offCanvas.

first time the canvas does not open and gives two errors:

Cannot read property 'defaultPrevented' of null (offCanvas.js line 102)
Cannot read property 'contains' of undefined (offCanvas liine 207)

second time, the canvas opens/closes but getting second error everytime.
sometimes, the image inside offCanvas does not display at all and needs refresh page to work.

The offCanvas component is shared in app using React context.
windows 10, google chrome v89

Hello @borakuldeep . Please can you provide a codepen example?

@GeoSot  I will try to create codepen for it. Meanwhile, is it suppose to be implemented as global modal  like component and shared via context? I have to show offCanvas for many items as a one click info. Hence I want to create only one offCanvas component and share it down the tree. If there is any such examples, please point me to it. Thanks for bootstrap 5 btw. It's great. :)

Closing issue. The offCanvas was not properly insterted in component tree.


Add derives for surjectionproofs

That doesn't work on 1.29 unfortunately :(
We will need a fairly recent rustc for this because it requires min-const-generics AFAIK.

Is there any strong reason to not do a simple manual implementation for these traits?

Is there any strong reason to not do a simple manual implementation for these traits?

As in, loop through the array and check each element?
For an 8000 element array, this might be expensive although I haven't conducted any experiments. Happy to merge a manual implementation if you need these traits!

Moved to #16


Consider adding PropertiesDefaultProvider implementation

Consider including the PropertiesDefaultProvider  implementation of the IDefaultValueProvider interface in the picocli distribution.

@Fernal73 to follow up on our conversion about user-editable defaulting: PropertiesDefaultProvider is included in picocli 4.1, which was released a few days ago.
https://github.com/remkop/picocli/releases/tag/v4.1.0

@Fernal73 mentions several other tools that provide similar functionality:

https://prettier.io/docs/en/cli.html
https://spotbugs.readthedocs.io/en/stable/running.html (the -userPrefs option)

It's interesting to see how prettier handles config files. There's even
more flexibility.

I haven't tested this, but I believe this can be implemented in picocli with multiple passes:

parse once, looking only for --no-config and --config-precedence
if --no-config was specified, do not install a default provider, and parse the input again;
if --config-precedence=cli-override was specified, install PropertiesDefaultProvider and parse the input again;
if --config-precedence=file-override was specified, do not install a default provider, but read the config file as an @-file, add the path to this @-file to the command line arguments and parse the input again;
if --config-precedence=prefer-file was specified, install PropertiesDefaultProvider and call CommandLine.execute with an empty command line arguments array.

Admittedly, point 4 may not be as simple as that...  It may be necessary to inspect the ParseResult and inspect which options were actually specified on the command line, to determine whether to use the value from the command line or from the configuration.

My understanding of point 4 is that the config file is still a properties file except that it's values trump the CLI options. You do bring up an interesting point if you support @files simultaneously. My understanding is that it be treated as simply an extension of CLI options and used or discarded as per the policy option specified and if duplicated (and permitted) , parsed backwards so that the latest value specified is the value used.

How would argument groups resolve this?

There is an option to allow overwriting single-value options, and by default picocli does not toggle booleans when they are specified multiple times.
However, as I thought some more about this, I don't think the @-file approach is going to work. For one thing, the current PropertiesDefaultProvider expects the file to have key-value pairs like option=value, not --option=value.
That could be fixed, of course, but another (bigger) problem is multi-value options; if the user specifies a few values, and the config file also has one or more values, then the collection or map would end up with the union of both, instead of only the config file values.
It may be easier to implement --config-precedence=file-override with something like this:

create a CommandLine instance, install PropertiesDefaultProvider and call CommandLine.execute with an empty command line arguments array. Let's call it the config instance.
create another, separate, CommandLine instance without a default provider (let's call it the userInput instance), and parse the command line input with parseArgs; this returns a ParseResult object
Loop over the options and positional parameters in the ParseResult that were matched on the command line, and for each of these, check if the same options and positional parameters in the config instance have a default value. If not, overwrite the value with the userInput value.

This would also work for argument groups, although it is more cumbersome to loop over those from the ParseResult.

I'm inclined to agree that having properties and @files makes it overtly
complex for the command-line user. Implementation-wise, if you treat the
@file as command line expansion, it's pretty much the same.
I was wondering if the three options provided by Pretty Printer can be part
of the API, probably in the Command Line class.
You'd still have multiple passes but it would be simpler.

Unfortunately, I had to put aside Picocli for a while to do other stuff. I
haven't come that far along into the documentation. I was trying out the
samples sequentially while working through it.
On Wed, 27 Nov 2019, 18:10 LINUS FERNANDES<EMAIL_ADDRESS>wrote:

I'm inclined to agree that having properties and @files makes it overtly
complex for the command-line user. Implementation-wise, if you treat the
@file as command line expansion, it's pretty much the same.
I was wondering if the three options provided by Pretty Printer can be
part of the API, probably in the Command Line class.
You'd still have multiple passes but it would be simpler.

@Fernal73 If there is a feature you want added to picocli, it may be better to raise a new ticket so I won't forget about it. :-)
That said, in the spirit of "make common things easy and uncommon things possible", I believe it made sense to add PropertiesDefaultProvider to the library, but more complex use cases like configurations that override command-line args should probably be handled in the application.
If you have a concrete use case, I would be happy to work through it together to see how we could make it work. It might make sense to then post the resulting program as an example to picocli-examples to help other users.

Four passes seems excessive.

I'm inclined to agree with you. That was my initial reaction when I first discovered Pretty Printer as well. It still requires two passes. I , somehow, got the impression that it'd take four passes. Maybe, I wasn't thinking too clearly.
It depends on how many command-line implementations do something similar. If it's uncommon, it's best to let the application developer do it. If it's increasingly common, then it becomes expected behaviour. Then, the API might need to provide that.

This topic may also be a good idea for an article or blog post.
I added Advanced Configuration to my list of ideas for articles.

My experience with command-line tools is limited.
However, the Prettier CLI---ignoring CLI options---is sufficiently similar
to specifying a properties file last in SpotBugs.
That would merit investigating allowing an API setting that has the tool
ignore CLI overriding of parameters stored in a properties object. Would it
be a tri-state flag with another value to ignore all CLI options? (We're
not concerned about positional parameters.)

If there is a specific use case you want to investigate together, would you mind creating a separate ticket that outlines what you want to achieve? (We can decide whether this should be added to the picocli API or not once we have arrived at a solution.)

I don't have a specific use case at the moment. My suggestions are not
easily implementable, in my opinion, unless the property file descriptors
are annotated parameters. That's why you need two passes at this point.
I'm satisfied with the examples listed as prior art in the documentation.
I'll share any more interesting ones should I encounter them.


logging: Multi-domain support

Adding support for multi-domain case. It can be used in scenario where there are multiple domains (binaries) and one physical output.
Description from documentation:
More complex systems may consist of multiple domains where domain is an independent binary. An example of a domain is a core in the multi-core SoC or one of the binaries on ARM TrustZone core (Secure and Nonsecure). Tracing and debugging on multi-domain system is more complex and requires efficient logging system. One option is to log in each domain independently. However, this option is not always feasible since it requires that each domain has available backend (e.g. UART). Additionally, in that approach logs are presented on independent outputs which is troublesome to use and not scalable. Another option is to use multi-domain logging where log messages from each domain end up in one root domain where they are processed in the same way as in a single domain case.
Log messages are passed between domains using a connection between domains which is created from backend on one side and link on the other. Log link is an interface introduced in multi-domain approach. Log link is responsible for receiving log message from another domain, create a copy and put that local log message (but with remote data) into the message queue. Specific log link implementation matches complementary backend implementation to allow log messages exchange and logger control like configuring filtering, getting log source names, etc.
There are 3 types of domains in the multi-domain system:

End domain which has the logging core implementation and cross domain backend. It can also have other backends in parallel.
Relay domain which has one or more links to other domains but does not have backend(s) which outputs logs to the user. It has cross domain backend to another relay or root domain.
Root domain which has one or multiple links and backend which outputs logs to the user.

PR contains:

multi-domain support in logging
helpers for creating pair of backend and link
backend and link implementation using ipc service
sample which runs on nrf5340dk
tests
documentation

Opening as draft, will be cleaning code in next few days.

@FrancescoSer can you please take a look at the docs patches?

@FrancescoSer your comments applied. @dcpleung can you take another look?

how about cortex-m and xtensa? such like nxp imxrt685

how about cortex-m and xtensa? such like nxp imxrt685

I don't think this is in any way architecture or SoC-specific, so it should work everywhere in principle.


How to use SCSS vars in views?

I have this in FrontPage.vue:
<style lang="scss">
    .slideshow {
        position: relative;
        background-color: $black;
        height: 70vh;
    }
</style>

And it gives this error:
Error: Module build failed:
        background-color: $black;
                     ^
      Undefined variable: "$black".
      in /Users/drew/Local Sites/ridley-scott/app/public/wp-content/themes/ridleyscott2018/src/components/templates/FrontPage.vue (line 38, column 23)

Include the @import statement and you should be good:
<style lang="scss">
    @import 'src/styles/your-partials-file';

    .slideshow {
        position: relative;
        background-color: $black;
        height: 70vh;
    }
</style>

You don't the the leading underscore or .scss when importing like this.

@drewbaker the one-liner that will always stay the same for our purposes is:
@import 'src/styles/vars';
Use that whenever you need to tap into shared variables and mixins. It would be handy to have this globally pre-loaded through all components, but for complicated webpack reasons it's not easily done. For more info on this, check out this thread.
Keeping this issue open to remind ourselves to document this in the readme.

OK, got it. Sucks, but I read that thread you linked and it seems like this will get fixed eventually.

I get an error when doing the import:
Error: Cannot find module "-!../../../node_modules/css-loader/index.js?sourceMap!./src/styles/_vars.scss"

I get an error when doing the import:
Error: Cannot find module "-!../../../node_modules/css-loader/index.js?sourceMap!./src/styles/_vars.scss"

Never mind, I was missing the lang="scss" part. This worked:
<style lang="scss">
    @import 'src/styles/vars';

There doesn't seem to be any downside to just adding @import 'src/styles/vars' into all the templates. We should certain include that in Default.vue, as I use that as the scaffold for all my files.

^ Added that line in 6d89824 Default.vue

Documented in 6230260 - closing issue.


withCallback:(RCTDirectEventBlock>)callback;   Expected a type in RNUIWebView.h

I am trying to build for iOS, and I'm getting this error in RNUIWebView.h file
withCallback:(RCTDirectEventBlock>)callback;   Expected a type
and I need to import #import <React/Views/RCTView.h> manually instead of
importing from  #import <React/RCTView.h>

I figure out the problem,It was with Linking Process (React Native 0.58). Actually I am linking some libraries with cocopods.
I use the following steps to resolve the issue :
1.Rename pod file with pod.tem
2.react-native link
3.pod install


Contact us section in same window

Opening contact us section in same window rather than a new window poping up

Good one. Go ahead :)
Deadline 17th April 2021 11:59 PM IST

No, remain it separate. In future we will decide where to implement it, on changing the UI of application


Built releases will not run on AWS

As mentioned in their blog, ubuntu-latest workflows now runs on Ubuntu 22.04.
As we discovered only recently (as we have not deployed a new backend in a while), the GitHub-generated releases will not run on our servers. I suspect it's due to the above: Ubuntu 22.04 comes with libc6-2.35 by default, so the GitHub runners will dynamically link those new versions of those libraries into our compiled release.
This is a problem as our AWS hosts currently run Ubuntu 20.04, which come packaged with libc6-2.31. Thus, trying to deploy our backend results in the following error (truncated):
...version `GLIBC_2.34' not found...

Reopening this issue as the PR did not seem to fix the problem...


Bolt+s support

Would it be possible to add support for bolt+s:// connections?
I have a GraphDB that only runs over a bolt+s connection and in that way, I can't connect jetbrains plugin to it.

Same request here, you only need to add a flag for encryption (ssl), but now it is not possible.

Another vote for enabling SSL-encrypted Bolt connections


Adds behavior for warning on columns that are missing without hard fa…

…iling

My bad. This was supposed to be against our fork for a quick fix of getting all the columns missing from the config of the database. Feel free to use this if you'd like, but I'm closing this PR

Hey @conor-pappas, this might still be a useful contribution if you'd like to add it with some specs.


factory: don't skip MacOS on CI

MacOS images now come with colima installed https://github.com/actions/runner-images/issues/2150
Related https://github.com/iterative/dvc-azure/issues/67
Related https://github.com/iterative/dvc-gs/issues/43

Codecov Report
Patch has no changes to coverable lines.

Files Changed
Coverage

src/pytest_servers/factory.py
ø

:loudspeaker: Thoughts on this report? Let us know!.


golang: bump automation with updatecli and GH actions

What does this PR do?
Automate the golang bump within the project itself using updatecli and github actions
Why is it important?
Remove the dependency with Jenkins and the definition of what to do in apm-pipeline-library
Use updatecli that provides the tooling for bumping versions
Issues
Similar to https://github.com/elastic/beats/pull/34458
Test
GIT_USER=*** \
GIT_EMAIL=*** \
updatecli diff --config .ci/bump-golang.yml

does nothing in terms of changing if no a new version.
if a new version is available then it bumps all those files as expected
Expand to view

+++++++++++
+ PREPARE +
+++++++++++

Loading Pipeline ".ci/bump-golang.yml"

SCM repository retrieved: 1

++++++++++++++++++
+ AUTO DISCOVERY +
++++++++++++++++++

++++++++++++
+ PIPELINE +
++++++++++++

#########################################
# BUMP GOLANG-VERSION TO LATEST VERSION #
#########################################

SOURCES
=======

latestGoVersion
---------------
WARNING: ⚠ No GitHub Release found, we fallback to published git tags
Searching for version matching pattern "go1\\.(\\d+)(\\.(\\d+))?$"
✔ Github Release version "go1.20" found matching pattern "go1\\.(\\d+)(\\.(\\d+))?$"

CHANGELOG:
----------
no GitHub Release found for go1.20 on "https://github.com/golang/go"

gomod
-----
The shell 🐚 command "echo 1.20" ran successfully with the following output:
----
1.20
----

CONDITIONS:
===========

dockerTag
---------
✔ The Docker image index.docker.io/library/golang:1.20 (amd64) exists and is available.

goDefaultVersion-check
----------------------
The shell 🐚 command "grep -v -q 1.20 .go-version # 1.20" ran successfully with the following output:
----
----

TARGETS
========

update-dockerfiles
------------------

**Dry Run enabled**

⚠ updated the [dry run] content of the file "/var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/Dockerfile"

--- /var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/Dockerfile
+++ /var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/Dockerfile
@@ -1,4 +1,4 @@
-FROM golang:1.19.5 as builder
+FROM golang:1.20 as builder

 RUN apt-get update \
        && apt-get dist-upgrade -y \

update-go-version
-----------------

**Dry Run enabled**

⚠ updated the [dry run] content of the file "/var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/.go-version"

--- /var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/.go-version
+++ /var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/.go-version
@@ -1 +1 @@
-1.19.5
+1.20

update-gomod
------------

**Dry Run enabled**

⚠ updated the [dry run] content of the file "/var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/go.mod"

--- /var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/go.mod
+++ /var/folders/hn/j6gds1qx1f5bysfn0qp0t03c0000gn/T/updatecli/github/elastic/stream/go.mod
@@ -1,6 +1,6 @@
 module github.com/elastic/stream

-go 1.19
+go 1.20

 require (
 	cloud.google.com/go/pubsub v1.25.1

ACTIONS
========

WARNING: **Fallback** Please add a title to you configuration using the field 'title: <your pipeline>'
[Dry Run] An action of kind "github/pullrequest" is expected.

=============================

REPORTS:

⚠ Bump golang-version to latest version:
	Source:
		✔ [gomod] Get version in go.mod format (kind: shell)
		✔ [latestGoVersion] Get Latest Go Release (kind: githubrelease)
	Condition:
		✔ [dockerTag] Is docker image golang:1.20 published (kind: dockerimage)
		✔ [goDefaultVersion-check] Check if defined golang version differs (kind: shell)
	Target:
		⚠ [update-dockerfiles] Update from dockerfiles (kind: file)
		⚠ [update-go-version] Update .go-version (kind: file)
		⚠ [update-gomod] Update go.mod (kind: file)

Run Summary
===========
Pipeline(s) run:
  * Changed:	1
  * Failed:	0
  * Skipped:	0
  * Succeeded:	0
  * Total:	1

https://github.com/elastic/beats/pull/34486 was created to test these changes

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-02-06T12:13:35.000+0000

Duration: 6 min 48 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
21

Skipped
0

Total
21

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

Do we want to bump the version to the latest go version or the latest go minor version?

Do we want to bump the version to the latest go version or the latest go minor version?

There was no go minor version set in https://github.com/elastic/apm-pipeline-library/blob/d592c5e95a467213bb6f97ed24fe0cf5068d9ea7/.ci/.bump-go-release-version.yml#L99-L104 so It gets the latest available minor version


Rename Branch iroha2 to iroha2-stable

The branch is iroha2 no longer exists. Now iroha2-stable is used instead. We need to rename wherever iroha2 branch is mentioned. For example here https://hyperledger.github.io/iroha-2-docs/guide/build-and-install.html#install-iroha-from-github .

The branch is being renamed back to iroha so I'll close this issue as not relevant anymore

The branch stays as Iroha-stable, the renaming must be carried out.


Customer control knobs to block traffic types on ExpressRoute.

Preconditions

[X] No need to upgrade Python SDK or the Python SDK is ready.

Related command
No response
Resource Provider
Microsoft.Network/virtualnetworkgateways and Microsoft.Network/expressRouteGateways
Description of Feature or Work Requested
We have added two new bool properties to our virtual network gateway resource and one to our ExpressRoute gateway resource. These properties can be used by the customer to allow/block certain traffic patterns on the gateway.
The original Swagger change was merged in 2022 but we are only getting ready to release the actual feature now, hence I would like to understand better how you plan to use the API version entry in the form below.
Minimum API Version Required
N/A - could you reach out to me to understand more about this
Swagger PR link / SDK link
https://github.com/Azure/azure-rest-api-specs/pull/20831
The original Swagger change was merged in 2022 but we are only getting ready to release the actual feature now, hence I would like to understand better how you plan to use the API version entry in the form above
Request Example
No response
Target Date
2023-12-06
PM Contact
mialdrid
Engineer Contact
javico
Additional context
No response

Thank you for opening this issue, we will look into it.

@jjcv-msft Just clarify--Minimum API Version Required means from which API version, one feature starts to be supported.
It's quite important to us, since we need to decide whether to bump version according to it.


How to achieve the effect of curl?

I'm afraid that's out of scope at the moment, so I will close the issue.
However, here's some basic guidance:
Each fixed-layout "page" is rendered on-screen using a single iframe. So a two-page spread consists in 2 separate iframes embedded within "reader.html" (i.e. the top-level document loaded inside the native webview). A "page curl" effect would have to be implemented at the level of the webview itself, so this would only work for a single FXL page. The readium-shared-js layout engine would have to be implemented natively / at the application level, in order to fully control page animation.
Each reflowable "page" actually consists in a single CSS Column within a single HTML document (hosted inside an iframe, which is embedded in the top-level webview-hosted "reader.html"). Once again, significant changes would have to be made to Readium's layout / rendering engine in order to delegate the pagination strategy to the application.
I am aware that some developers attempted to implement page-turn effects by loading multiple Readium instances within multiple embedded webview controls, but this turned into a performance bottleneck and there were peripheral issues related to prefetching / preloading content off-screen.
I hope this helps.


Migrated to 4-12

This depends on vapor tag 0.6.0, which isn't out yet

0.6.0 has been released now.


The computer won't shut down

I think my problem is due to a bad installation, but if someone had the same problem and fixed it I'll be happy to know how.
I just update to Mojave everything work just great, the trackpad is so much better ! But everytime I shut down the 'mac', the computer restart..
Plus when I choose mac option it tells the following:

Also the clover start choosing boot is not working and it do not propose me the usual boot but instead of an Opencore Boot menu like this:

Anyone had the same issue or solution for this issue ?
Thanks !

Hi, you are using OpenCore bootloader, and it's a known issue that device won't shutdown with OpenCore+VoodooI2C. See https://github.com/daliansky/XiaoMi-Pro/issues/192.
You should delete /EFI/OC folder so the device will only use CLOVER.

I have the same issue. I deleted the /EFI/OC folder, my system will now start with windows every time. How to get clover back?

Hi @keckol, for daily use, EFI folder from release page: https://github.com/daliansky/XiaoMi-Pro/releases is always a reliable choice.

I'll try to replace it but I have the same problem than @kevkol and I'm stuck to windows for now

@Raphencoder
I was able to get back to clover with the following steps:
I did a full format of my EFI folder, after I mounted it with windows. There had been some undeletable corrupted data in there for me.
I copied an earlier backup of the EFI Folder to my EFI partition.
I copied the updated version of the release page (link by @stevezhengshiqi ) to my EFI partition and replaced duplicates.
Now you need to consider that the BIOS will change to boot device order, if you boot one time with an EFI which is not configurated properly. That means double check the boot order in your bios menu.
=> now everything is working again with clover

Thanks ! That works for me too


simulate directories and files by sqlite/table

is possible to simulate/replace directories and files by table(sqlite or mysql ...) for lume ?
I study possibility to build CMS like wordpress on top of lume, mysql and deno deploy

Yes. One unique file can create many pages. For example:
import database from "./my-database.ts";

export default function * () {
    const articles = database.query("select * from articles");

    for (const article of articles) {
        // Return a page
        yield {
            url: "/articles/" + article.slug,
            content: article.content,
        }
    }
}

In short: use generators to generate as many pages as you want from an unique file.

Yes. One unique file can create many pages. For example:
import database from "./my-database.ts";

export default function * () {
    const articles = database.query("select * from articles");

    for (const article of articles) {
        // Return a page
        yield {
            url: "/articles/" + article.slug,
            content: article.content,
        }
    }
}

In short: use generators to generate as many pages as you want from an unique file.

Thank you @oscarotero.
It seems you understand my question we can generate multiple pages from one file but I'm not sure if I understand enough your answer but I will try,
The dara source can come from any db or hard coded.
Can you give me complete simple example with data hard coded.

Can you give me complete simple example with data hard coded.

export default function * () {
    const articles = ["foo", "bar", "baz", "some"];

    for (const article of articles) {
        // Return a page
        yield {
            url: "/articles/" + article.slug,
            content: article.content,
        }
    }
}

You have more info here: https://lume.land/docs/core/multiple-pages/

I think we can safely close this issue.


Eagleye uses a lot of old header files.

Many warnings at compile time since eagleye uses a lot of old header files.

PR has been merged and this issue is closed.


[ALLUXIO-2418]Update Debugging-Guide.md of the Chinese version

see https://alluxio.atlassian.net/browse/ALLUXIO-2418

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12228/
Test PASSed.

LGTM