How to use Finbuckle with Identity and EntityFramework in Asp.net

Please provide some example to do this as I am finding this doc  at this url:
https://github.com/Finbuckle/Finbuckle.MultiTenant/tree/main/samples/ASP.NET Core 3/IdentityDataIsolationSample
quite messy.
please help

hi @shreya-groot
I agree the sample isn't a good as it could be -- it tries to show a few different things.
Let me ask you a few questions and I'll give you some specific advice:

are you using a shared database or separate databases per tenant?
which multitenant strategy are you using?
are you using the default Identity UI?
do you have multiple db context classes? 1 for Identity and 1 for the rest of the app? Or do you have a single shared db context?

Any other specific problems you are running into?

Hello Andrew,
I am having problem to implement Finbuckle
as I am having following specifications in it:

I am using Identity in Asp.Net
2.I am having one database that has be shared among all tenenat
I need to filter data corresponding to particular tenant by queries

Please guide me
Thanks & Regards
Shreya
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 20 April 2021 08:55
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
hi @shreya-groothttps://github.com/shreya-groot
I agree the sample isn't a good as it could be -- it tries to show a few different things.
Let me ask you a few questions and I'll give you some specific advice:

are you using a shared database or separate databases per tenant?
which multitenant strategy are you using?
are you using the default Identity UI?
do you have multiple db context classes? 1 for Identity and 1 for the rest of the app? Or do you have a single shared db context?

Any other specific problems you are running into?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-822944988, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH4YVWH4LCXRB6L476LDTJTXY7ANCNFSM43CQO4OQ.

@shreya-groot
in your app how do you detect the tenant? Does each tenant have a different url or hostname or do you do something completely different?
Before getting into the Identity MultiTenant Sample do you understand these samples?

RouteStrategySample
DataIsolationSample (not the Identity one -- this one shows the basics that Identity builds on)

Actually I am allowing the user to login and I will use his  AspNetUserId from that which I assume to be same as tenant id which has been inserted in tenant table while registering the user
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 20 April 2021 09:23
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
@shreya-groothttps://github.com/shreya-groot
in your app how do you detect the tenant? Does each tenant have a different url or hostname or do you do something completely different?
Before getting into the Identity MultiTenant Sample do you understand these samples?

RouteStrategySample
DataIsolationSample (not the Identity one -- this one shows the basics that Identity builds on)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-822953789, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH445IRYIAQ2AHUFBF7LTJT3DPANCNFSM43CQO4OQ.

And Also I don’t want to put tenant configuration in appSetting.json file as done in these two strategies
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 20 April 2021 09:23
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
@shreya-groothttps://github.com/shreya-groot
in your app how do you detect the tenant? Does each tenant have a different url or hostname or do you do something completely different?
Before getting into the Identity MultiTenant Sample do you understand these samples?

RouteStrategySample
DataIsolationSample (not the Identity one -- this one shows the basics that Identity builds on)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-822953789, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH445IRYIAQ2AHUFBF7LTJT3DPANCNFSM43CQO4OQ.

Please help me to create a Tenant when I am using Identity to let the user login inside my ASP.Net Core app

@shreya-groot  I'm sorry for the slow responses
You want to create a a tenant when a new user registers? Will your tenants have multiple users or will it be one user per one tenant?
You can create a new tenant by using the IMultiTenantStore<T>.TryAddAsync method which requires a TenantInfo object of type T. Not all of the stores implement this method though so you might have to create your own store.
Then when you need to create a new tenant you just create a new tenant object instance as required then call the TryAddAsync method on your IMultiTenantStore<T> store instance which you can get the store from the DI system in most cases.

My tenant will have multiple users further.
First of all I want to know which strategy I should use out of so many as I only want to create Tenant with so many users under him
In Asp.net core I have created all the users who can sign in into my application, but I want to make them specific to tenant, means I want to associate one tenant with each user without working on any routing.
please give me some example relateed to that.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 28 April 2021 08:43
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
@shreya-groothttps://github.com/shreya-groot I'm sorry for the slow responses
You want to create a a tenant when a new user registers? Will your tenants have multiple users or will it be one user per one tenant?
You can create a new tenant by using the IMultiTenantStore.TryAddAsync method which requires a TenantInfo object of type T. Not all of the stores implement this method though so you might have to create your own store.
Then when you need to create a new tenant you just create a new tenant object instance as required then call the TryAddAsync method on your IMultiTenantStore store instance which you can get the store from the DI system in most cases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-828109651, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH45KYFFAMHPQM5NEZQTTK54OHANCNFSM43CQO4OQ.

@shreya-groot it sounds like you are not using isolated Identity databases for each tenant and prefer to have a single Identity database where the tenant is associated with each user. In that case take a look at the "Shared Login" sample. It is ASP.NET 2.1 but the basic idea should still work. It will have a user login, check which tenant that user is, then use that tenant for all requests for that authorized user. No route or anything like that is needed.

@shreya-groot
I too have similar requirement .. did you got any solution for it ?

I have same requirements :) Would love to see some solutions for this :)


[FreeBSD] Include <stdio.h>, needed for printf().

What's in this pull request?
The build is currently broken on FreeBSD. This patch is a proposed fix.
Resolved bug number: (SR-)
N/A

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

Updated as requested by Dmitri. Thanks!


Support \v and \h, fix testcase for unicode mode

@andgineer Tasks with FPC 3.0 had passed ok. Tasks with FPC 2 will never pass- fpc 2.x missed unit "fpwidestring", so please delete fpc 2.x from CI.

You see TRegExpr now IS compatible with fpc 2.
All tests are green.
Why so minor change from you should break it?

@andgineer All checks passed now (after my fix to demo code)

Great solution thank you for your patience!


Search for a concurrent map with weak keys

Requirements

Weak keys
Thread safe (Not WeakHashMap)
Highly performant in multi-threaded scenarios (not Guava or Collections.synchronizedMap)
No allocations on get() (not WeakConcurrentMap)

Relates to #317

Good luck.  You basically excluded all the options I am aware of.

Hehe, thx :smile:
What I want to test is the map backing caffeine cache.

Caffeine is like WeakConcurrentMap by allocating a wrapper for the key comparison. I think this isn't a problem because of escape analysis, since the object is on the same thread. But I don't recall testing that and escape analysis may not work across method cals. However the allocation should be cheap due to short lived. Your best bet is to write a JMH benchmark. The big difference is that Caffeine does not require create any dedicated threads and performs maintenance cycles after a threshold of operations occur.
Guava gets around that by forking the hash table so that it can use a pluggable Equivalence. However, that is a big commitment which they did in a misguided enthusiasm towards soft references. In parallel I was exploring concurrent LRU and, when reality set in on the Guava team, we tried to port my work into theirs. So Guava is optimized for reference caching first, whereas Caffeine is size first. We could fork the hash table just for reference caching, but I really don't want to commit towards maintaining even more complexity.


Fix documentation issue Azure/azure-sdk-for-net#18305

Fix documentation issue Azure/azure-sdk-for-net#18305
Description
The code example on documentation for ContainerProperties class has some syntax errors.
Type of change

[x] This change requires a documentation update

Closing issues
closes #TBD
https://github.com/Azure/azure-sdk-for-net/issues/18305 (this one probably should be routed in this repo, It was created from MS Docs https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.containerproperties?view=azure-dotnet)

/azp run


feat(MorphismProperty/Presheaf): add relative morphism property

Given a morphism property P and a functor F, we define the morphism property P.relative of morphisms in the codomain of F. This is defined as being relatively representable with respect to F, and that any represented pullback of the morphism satisfies P.
Co-authored-by: Joël Riou<EMAIL_ADDRESS>

[x] depends on: #16140
[x] depends on: #16141

(I have contributed to this PR, but I just would like to say that this looks good to me.)

LGTM modulo the comment on naming. Maybe merge it if there aren't better names.
maintainer merge

Great to see progress here :-) There are so many functors we need to represent!
bors merge


Launching a CUDA kernel with an OffsetArray{CuArray} does not work.

I'm trying to use OffsetArrays to implement halo regions (https://github.com/climate-machine/Oceananigans.jl/pull/167) but when calling CUDA kernels with an OffsetArrays as one of it's argument I get some Casette error (see below).
The kernel:
using CuArrays, OffsetArrays, GPUifyLoops

# Adapting OffsetArrays to work with CUDA kernels.
import Adapt
Adapt.adapt_structure(to, x::OffsetArray) = OffsetArray(Adapt.adapt(to, parent(x)), x.offsets)

function fill_halo_regions_x!(Nx, Ny, Nz, f)
    @loop for k in (1:Nz; blockIdx().z)
        @loop for j in (1:Ny; (blockIdx().y - 1) * blockDim().y + threadIdx().y)
            f[0,    j, k] = f[Nx, j, k]
            f[Nx+1, j, k] = f[1, j, k]
        end
    end

    @synchronize
end

It works on the CPU:
Nx, Ny, Nz = 5, 5, 5

max_threads = 1024
Tx  = min(max_threads, Nx)
Ty  = min(fld(max_threads, Tx), Ny)
Tz  = min(fld(max_threads, Tx*Ty), Nz)
Bx, By, Bz = cld(Nx, Tx), cld(Ny, Ty), cld(Nz, Tz)

# We'll fill the interior of an OffsetArray on the CPU and check to see if the kernel correctly
# fills in the halo regions in the _x_-direction. It does.
underlying_data = zeros(Nx+2, Ny+2, Nz)  # Halos of size 1 on each side.
data = OffsetArray(underlying_data, 0:Nx+1, 0:Ny+1, 1:Nz)
@. @views data[1:Nx, 1:Ny, 1:Nz] = rand()
@launch CPU() fill_halo_regions_x!(Nx, Ny, Nz, data, threads=(Tx, Ty, Tz), blocks=(Bx, By, Bz))

It does not work on the GPU:
underlying_data = CuArray(zeros(Nx+2, Ny+2, Nz))
data = OffsetArray(underlying_data, 0:Nx+1, 0:Ny+1, 1:Nz)
@. @views data[1:Nx, 1:Ny, 1:Nz] = rand()
@launch CUDA() fill_halo_regions_x!(Nx, Ny, Nz, data, threads=(Tx, Ty, Tz), blocks=(Bx, By, Bz))

and spits out this error and stacktrace:
ERROR: InvalidIRError: compiling #12(Int64, Int64, Int64, OffsetArray{Float64,3,CUDAnative.CuDeviceArray{Float64,3,CUDAnative.AS.Global}}) resulted in invalid LLVM IR
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] call at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:447
 [2] fallback at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:445
 [3] overdub at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:271
 [4] fill_halo_regions_x! at REPL[4]:2
 [5] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:2
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] call at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:447
 [2] fallback at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:445
 [3] overdub at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:271
 [4] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [5] fill_halo_regions_x! at REPL[4]:2
 [6] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:2
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] call at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:447
 [2] fallback at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:445
 [3] overdub at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:271
 [4] fill_halo_regions_x! at REPL[4]:3
 [5] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:3
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] call at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:447
 [2] fallback at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:445
 [3] overdub at /home/alir_mit_edu/.julia/packages/Cassette/xggAf/src/context.jl:271
 [4] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [5] fill_halo_regions_x! at REPL[4]:3
 [6] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:3
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:4
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported dynamic function invocation (call to Cassette.overdub)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:5
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'blockIdx')
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:2
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported call to the Julia runtime (call to jl_type_error)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:2
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'blockIdx')
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:2
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported call to the Julia runtime (call to jl_type_error)
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:2
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported call to the Julia runtime (call to jl_type_error)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:5
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'blockIdx')
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:3
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'blockDim')
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:3
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'threadIdx')
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:3
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported call to the Julia runtime (call to jl_type_error)
Stacktrace:
 [1] fill_halo_regions_x! at REPL[4]:3
 [2] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'blockIdx')
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:3
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'blockDim')
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:3
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported use of an undefined name (use of 'threadIdx')
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:3
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Reason: unsupported call to the Julia runtime (call to jl_type_error)
Stacktrace:
 [1] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:198
 [2] fill_halo_regions_x! at REPL[4]:3
 [3] #12 at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/context.jl:136
Stacktrace:
 [1] check_ir(::CUDAnative.CompilerJob, ::LLVM.Module) at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/compiler/validation.jl:104
 [2] macro expansion at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/compiler/driver.jl:182 [inlined]
 [3] macro expansion at /home/alir_mit_edu/.julia/packages/TimerOutputs/7zSea/src/TimerOutput.jl:216 [inlined]
 [4] #codegen#113(::Bool, ::Bool, ::Bool, ::Function, ::Symbol, ::CUDAnative.CompilerJob) at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/compiler/driver.jl:178
 [5] #codegen at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/compiler/driver.jl:0 [inlined]
 [6] #compile#112(::Bool, ::Bool, ::Bool, ::Function, ::Symbol, ::CUDAnative.CompilerJob) at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/compiler/driver.jl:38
 [7] #compile#111 at ./none:0 [inlined]
 [8] compile at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/compiler/driver.jl:22 [inlined] (repeats 2 times)
 [9] macro expansion at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/execution.jl:378 [inlined]
 [10] #cufunction#146(::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(CUDAnative.cufunction), ::getfield(GPUifyLoops, Symbol("##12#13")){typeof(fill_halo_regions_x!)}, ::Type{Tuple{Int64,Int64,Int64,OffsetArray{Float64,3,CUDAnative.CuDeviceArray{Float64,3,CUDAnative.AS.Global}}}}) at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/execution.jl:347
 [11] cufunction(::Function, ::Type) at /home/alir_mit_edu/.julia/packages/CUDAnative/IZwnv/src/execution.jl:347
 [12] macro expansion at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:113 [inlined]
 [13] macro expansion at ./gcutils.jl:87 [inlined]
 [14] #launch#46(::Base.Iterators.Pairs{Symbol,Tuple{Int64,Int64,Int64},Tuple{Symbol,Symbol},NamedTuple{(:threads, :blocks),Tuple{Tuple{Int64,Int64,Int64},Tuple{Int64,Int64,Int64}}}}, ::Function, ::CUDA, ::typeof(fill_halo_regions_x!), ::Int64, ::Vararg{Any,N} where N) at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:110
 [15] (::getfield(GPUifyLoops, Symbol("#kw##launch")))(::NamedTuple{(:threads, :blocks),Tuple{Tuple{Int64,Int64,Int64},Tuple{Int64,Int64,Int64}}}, ::typeof(GPUifyLoops.launch), ::CUDA, ::typeof(fill_halo_regions_x!), ::Int64, ::Vararg{Any,N} where N) at ./none:0
 [16] top-level scope at /home/alir_mit_edu/.julia/packages/GPUifyLoops/hBRid/src/GPUifyLoops.jl:54

Looks like there's some unexpected errors about threadIdx, blockIdx, and blockDim not being defined, but otherwise I'm not too sure what the error is.
I'm using the tb/errors branch of CUDAnative.jl (https://github.com/JuliaGPU/CUDAnative.jl/pull/389) to get these error messages. Otherwise it was just a lot of jl_apply_generic errors.
Note: I'm using the wrong number of threads and block for this kernel but that's not relevant to the issue I think.

Hmmm, don't think this is related to OffsetArrays because I just tried running the GPU section with a vanilla CuArray
data = CuArray(rand(Nx+2, Ny+2, Nz))
@launch CUDA() fill_halo_regions_x!(Nx, Ny, Nz, data, threads=(Tx, Ty, Tz), blocks=(Bx, By, Bz))

and got a similar error. I thought the issue was maybe the 0 index in the CUDA kernel but the kernel isn't compiling so that shouldn't be an issue. Changing the 0 to a 1 did not fix things anyways.
I think I'm running on #master for GPUifyLoops and all the CUDA packages. I'll try installing the regular packages/versions and try again to make sure it's not just weird versions clashing.

You are missing a using CUDAnative in your kernel definition. that's why blockIdx is undefined.

Ah yes, classic mistake. Thank you!
Just tried and the MWE works now. Not sure what was wrong with the "production" version inside Oceananigans.jl but will go back and see if I can get it to work now. If there's no error I'll come back and close this issue.

Yup that was the issue. I was prototyping in a Jupyter notebook and forgot to execute using CUDAnative...
Good to know everything still works, and the GPU errors are much better now.


Reconsider default color for AnsiDodoError

See https://github.com/JordanMartinez/purescript-json-codecs#doc-graphicsparam
I think the colors for the error message could be improved, but I'm not yet sure what that should be.

These colors are now configurable. This lessens the person's burden of reimplementing the handlers just to change one simple color.


hangs / downloads 0 ( without verbose)

When using rclone to sync bucket1 and bucket2 from the same ceph server and user account, bucket1 works flawlessly, bucket2 used to work, now rclone just hangs.
A simple rclone ls or sync command for bucket2 results in hang and after some minutes I see many messages of 0 bytes, exactly like this:
A sync command, result in many messages like this:
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      1m0.1s
2016/04/28 14:48:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      2m0.1s
For each file...
I am clueless.
When filing an issue, please include the following information if
possible as well as a description of the problem.

What is your rclone version (eg output from rclone -V)
rclone v1.28
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Raspbian
Which cloud storage system are you using? (eg Google Drive)
DreamObjects (CEPH)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone copy and rclone ls
A log from the command with the -v flag (eg output from rclone -v copy /tmp remote:tmp)

Building file list
2016/04/28 14:47:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      1m0.1s
2016/04/28 14:48:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      2m0.1s
2016/04/28 14:49:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      3m0.1s
2016/04/28 14:50:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      4m0.1s
2016/04/28 14:51:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      5m0.1s
2016/04/28 14:52:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      6m0.1s
2016/04/28 14:53:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      7m0.1s
2016/04/28 14:54:34
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      8m0.1s

Closed as it seems a problem with the server

If you get this again then try with -v and -dump-headers and that will give us some idea what is going on.


Add new trigger to a existing task

I wanted to add an timetrigger to an already existing task. How can I do that? I looked at all the examples, but I can't find it there.
Originally posted: 2012-02-11T07:46:57

using (TaskService ts = new TaskService())
{
// Retrieve the task, change the trigger and re-register it
Task t = ts.GetTask(taskName);
td = t.Definition;
td.Triggers.Add(new TimeTrigger() { StartBoundary = DateTime.Now + TimeSpan.FromHours(1) });
ts.RootFolder.RegisterTaskDefinition(taskName, td);
}
Originally posted: 2012-02-13T10:19:49


BUILDING ISSUE

Describe your problem here.
When I build the game... It shows this
source/states/PlayState.hx:36: characters 8-46 : Type not found : flixel.addons.display.FlxRuntimeShader
source/psychlua/FunkinLua.hx:16: characters 8-46 : Type not found : flixel.addons.display.FlxRuntimeShader
source/psychlua/HScript.hx:317: characters 89-96 : Type not found : TeaCall
this is for the recent build... what do I do?
Are you modding a build from source or with Lua?
HX
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

replace TeaCall with Tea or set your SScript to 7.7.0, check ur library versions

replace TeaCall with Tea or set your SScript to 7.7.0, check ur library versions

How??? I did and it still wont work!


Pipeline templates

It would be very useful to allow pipelines to be templates.
Pipelines need another method to allow swapping out the vertex buffers and descriptor sets.
The current pattern is to actually make a pipeline builder function, but this parses the source at least until the program caching. It would be much simpler to just allow pipeline.template(...) or .copy(...).

template does not allow the program to be changed this results in 10x speedup compared to a pipeline builder method with the shader set. this performance improvement mostly comes from the source manipulation and cache check.


Create navigation menus dynamically on internal pages

Work is already in progress here: https://github.com/onflow/next-docs-v1/pull/159
Create the navigation menus for all of the internal pages following the pattern established here:
https://github.com/onflow/next-docs-v1/pull/161

some pages aren't working


Hololens2 issue with MRTK Version

Hey,
I tried to get the new version for the Hololens 2 running but i get some issues.
If i am use the version of MRTK that comes in the folder it doesnt show the point cloud
and i tried to update the version of mrtk but this doesnt work at all.
can you help me with my Promblem?
Best regards
Max

Hello Max,
unfortunately I don't really have the bandwidth to try this at the moment. Does this work for you locally (as in, not on HL2)?
Do you get any exception on HL2? Is the HL2 on the same network as the machine? Do you have the firewall set up such that the connection could happen?
Thanks,
Marek

Hey Marek,
Thanks for youre answer, i got it working in Unity (Version 2020.1.17) but if i try deploing it remote using Visual studio 19 to the holonens2 i get this error

First the HL2 shows "made with unity" and then the error occurs in VS19.
What Firewall setup do you mean?
Thanks,
Max

That's not very specific. Does it come with a stack trace? I wonder if it has anything to do with the networkcommunication module. Are you able to set a breakpoint where that module is initialized and see whether it fails there?
For the firewall: the hololens2 needs to be able to connect to the livescan app running on your pc.

Hey Marek,
this is in the stack

i´m not very into programming using Unity. Where is network module getting initialized.
I checkt the settings of the firewall and the livescanapp has access.
Thanks,
Max

Hey!
It seems that the failure happens during construction of the socket. Based on the stack trace, it's hard to determine whether this is a failure in the constructor itself or whether the constructor does not even start.
A few things you could try:

Rebuild the Network Communications project. Make sure that the output DLL is saved in ./Assets/Plugins.
Remove the following line socket = SocketClient(strIP, port);  from the TransferSocket.cpp file, rebuild (as in step 1 above) and see if you get the exact same error and stack trace. If it's the same then there is some issue with the DLL I would think. If not, then it looks like a network issue, i.e. your HL2 can't connect to the computer.

Hey,
Thanks for you`re support.
I tried youre suggestions and with rebuilding the networkcommunication it did made a difference, the same error appeared.
When commenting out the line, the program ran without making an error.
So I got the following result.

You said if this happens it should be a network issue so I tried turning off my firewall but the same error accured again.
Best regards
Max

Hey Marek,
i got it finally working, i hardcoded the ip adress also into this line
https://github.com/MarekKowalski/LiveScan3D-Hololens/blob/d93cb12d80567c6b1e065d1da005feffc3aaa05a/HololensReceiver/Assets/KeyboardInput.cs#L31
and in the pointcloud reciver where the ip adress is refered.
I also run the livescanserver on a different pc, maybe this was the solution for our network problems
Do you know how i get rid of the white polygons in the background.

Thank you so much for your help so far.
Best regards
Max


Carthage install fails

The following build commands failed:
Check dependencies
(1 failure)
A shell task (/usr/bin/xcrun xcodebuild -project "/Users/jeramymorrill/Work Bench/blueberry/Blueberry-Voice-Recorder/Carthage/Checkouts/NVActivityIndicatorView/NVActivityIndicatorView.xcodeproj" -scheme NVActivityIndicatorView -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** CLEAN FAILED **

+1

I face the same problem just now

I found this... https://github.com/ninjaprox/NVActivityIndicatorView/issues/101

@walsht I change the SWIFT_VERSION to 3.0 ,but when I run carthage udpate ,the file run back to the origin one (SWIFT_VERSION) ,how do you solve this problem?

@theceremony, @lzhlewis2015:  How about using carthage branch? I hope it would help.

Close this, reopen if need be.


Update tutorial-query-table.md

Change Table name to People from people

@ajitha-kb : Thanks for your contribution! The author, @kanshiG, has been notified to review your proposed change.

@ajitha-kb Thanks for the fix, we will merge your PR soon.
#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @kanshiG, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


disable BUILD_TESTING for capnproto

Running in a colab notebook & docker based on nvidia/cuda:12.2.0-devel-ubuntu22.04 I hit the following error building:
Executing subproject capnproto method cmake

| Configuring the build directory with CMake version 3.22.1
| Running CMake with: -G Ninja -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_POSITION_INDEPENDENT_CODE=True -D-BUILD_TESTING=False
|   - build directory:          /seticore/build/subprojects/capnproto/__CMake_build
|   - source directory:         /seticore/subprojects/capnproto
|   - toolchain file:           /seticore/build/subprojects/capnproto/__CMake_build/CMakeMesonToolchainFile.cmake
|   - preload file:             /usr/local/lib/python3.10/dist-packages/mesonbuild/cmake/data/preload.cmake
|   - trace args:               --trace-expand --trace-format=json-v1 --no-warn-unused-cli --trace-redirect=cmake_trace.txt
|   - disabled policy warnings: [CMP0025, CMP0047, CMP0056, CMP0060, CMP0065, CMP0066, CMP0067, CMP0082, CMP0089, CMP0102]

| Running with expanded trace output on.
| Not searching for unused variables given on the command line.
| Trace will be written to cmake_trace.txt
| -- The CXX compiler identification is GNU 11.4.0
| -- Detecting CXX compiler ABI info
| -- Detecting CXX compiler ABI info - done
| -- Check for working CXX compiler: /usr/bin/c++ - skipped
| -- Detecting CXX compile features
| -- Detecting CXX compile features - done
| -- Looking for C++ include initializer_list
| -- Looking for C++ include initializer_list - found
| -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "3.0.2") found components: Crypto SSL
| -- Looking for makecontext in c
| -- Looking for makecontext in c - found
| -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
| -- Configuring done
| -- Generating done
| -- Build files have been written to: /seticore/build/subprojects/capnproto/__CMake_build

capnproto| CMake configuration: SUCCEEDED
capnproto| WARNING: Unable to evaluate the cmake variable '$<TARGET_FILE:capnp_tool>'.
capnproto| WARNING: Unable to evaluate the cmake variable '$<TARGET_FILE:capnp_tool>'.
capnproto| WARNING: Unable to evaluate the cmake variable '$<TARGET_FILE:capnp_tool>'.
capnproto| WARNING: Unable to evaluate the cmake variable '$<TARGET_FILE:capnpc_cpp>'.

meson.build:37:22: ERROR: We evaluated the cmake variable '$<TARGET_FILE:capnp_tool>' to an empty string, which is not a valid path to an executable.

Disabling the testing build of capnproto appears to resolve the issue

LGTM


Assistant SDK no longer responds with text response

As per the code example, the below no longer responds with the answer from Google Assistant.  Audio responses are still provided, however the text response is always blank
Having asked questions such as

What time is it?
What's the weather in London?
Who is the president of the USA?
How tall is the Empire State Building?

const promptUser = () => {
    stdio.question('> ', (err, prompt) => {
        assistant.assist(prompt)
            .then(({ text }) => {
                console.log(text); // Will log the answer
                promptUser();
            });
    });
};

What I have found from personal investigation is that I can replicate this issue by passing the PLAYING parameter to the screen mode in the SDK.  If I set the screen mode to OFF then it responds with the text.
Whilst these are only my results, I also found that using this example repo where the screen mode isn't passed at all, it still does not respond with the text.
I have also read that some users pass OFF as the screen mode but still have this issue as per this issue:
https://github.com/endoplasmic/google-assistant/issues/81
It seems that this issue actually begun around the end of last year.

Been having the exact same issue as well!

Having the same issue.

I am having the same problem.

I got the same kind of experience. No text answer, only audio as response to a question.
The result of that seems that the question is (broad)casted.

Issue is back.  Seems the screen on/off makes zero difference now.

Can confirm the issue and it seems to be permanent now. response is an empty object.
const assistant = new GoogleAssistant(CREDENTIALS);
assistant.assist('what time is it?')
  .then((response) => {
    console.log(response); // {}
  });

I also have the same problem related to the lack of response because it displays a blank field

I also have the same problem related to the lack of response because it displays a blank field

Would like to add to this issue, the issue I'm experiencing is that the assistant sometimes provide text output, but for some questions like "what time is it", no text response is returned, only audio is played. I'm using a modified version of the console input example, which takes text input and play audio output to test the operation. I hope this issue can be fixed soon as my primary use case is in a text-based scenario.


Add combined colour picker

Closes #3134.
Supersedes / closes #3138.

The full thing, finally.
https://user-images.githubusercontent.com/20418176/122276354-fd272b00-cee4-11eb-8303-0842efd75c1b.mp4
I initially said that this final step was going to be inconsequential. That was what I thought too, until yesterday, when during preparing to PR this I arrived at the very late conclusion that the HSV part was firing too many value change callbacks and therefore made the hex part flicker way too much than acceptable. Therefore, this pull also adds a TransferValueOnCommit property (analogous to Slider) that resolves that, and test coverage of that.
I can split that on request (first two commits are that), but it's not that huge, so I figured I'd just leave it in one piece to cut the noise. It makes some sense being in here, because there was no real reason for it to be a thing until now.

A couple of visual issues:

The preview really needs to update in real-time (potentially also the hex display?). Right now it feels weird having it only update on release. I haven't looked into the code side of things yet, so I'm not sure if this is a simple change or not.

I'm sure this is probably an issue at the textbox end, but there's currently a weird one frame flash and two frame delay until the text is updated, making using this control feel laggy:

Note that this is after removing the fade in at
https://github.com/ppy/osu-framework/blob/68479228f1a07d8efe9b60fe498f93d97ae0e242/osu.Framework/Graphics/UserInterface/BasicTextBox.cs#L113-L117
which also needs to go (in the case of replacing a full string in a textbox it should be instant).

The preview really needs to update in real-time (potentially also the hex display?)

I had things working this way before. As stated above, the reason why I changed is that the text changes would start affecting framerate negatively. Even with the text box transform gone the FPS drop may remain, but I haven't checked.
As for the suggestion to only update the hex preview in real time, as written the components are architected completely wrong for that. The hex picker would have to expose two bindables (instant and committed) and presumably also become non-public due to that.

One thing which may help is debouncing the UI updates, as if you don't do this you will be performing many updates per update frame (due to the input thread running at 1000hz). May be enough to fix the issue you mention, and potentially even better after fixes are applied to textbox.

Does this behaviour look closer to what you would expect?
https://user-images.githubusercontent.com/20418176/122440913-50f54b00-cf9d-11eb-8f2c-a89da0f6854b.mp4
The above is after reverting the TransferValueOnCommit changes, adding some Scheduler.AddOnce() calls, locally finishing the textbox transforms and locally fixing the one-frame delay via the method described in https://github.com/ppy/osu-framework/pull/4522#issuecomment-863396432.
If it is desired for the temporary hex value to also transfer to the HSV part then that's trickier to achieve. I tried once and the code got quite confusing wrt binding directions quite quickly.

I think this is fine for now, yep. Entering the hex would optimally also update immediately, but it's going to be one of the rarer cases and definitely shouldn't be blocking this initial implementation from being merged.

Have pushed the changes that seemed relevant to this pull. The text box related ones (the fading animation and the 1-frame delay) seem better suited to #4522 or an alternative thereof.


slowly reverts back to the original image

Hey there, been trying a few different settings so far trying to get a feel for this.
One thing I've noticed is that the first few frames will be a new image (as intended) then it slowly fades back to the original.
For example, a person  dancing and it's only 20 frames long, they'll start off looking like a new person, but roughly halfway through the video won't look much different from the original gif. By the end it'll look almost exactly the same.
This happens less often when frame strength is above 0.5 but then the videos get more wild.
Attempting processing strength around 0.65, and 0.25
Haven't really figured a good setting to try and retain the original image but replace the character used.
Tested a video with 18 frames, brown haired girl dancing.
Frames 1 - 10 start with a girl with short orange hair and a hat, but slowly fade, by frame 10 it looks exactly the same as the original gif. Long brown haired girl again.

Raising "fix frame strength" seems to partially solve the reverting back to original video issue. However then you end up with wildly different videos than the original.
This may be a simple misunderstanding of how to properly use this.
However fix frame strength at 0 has a wildly different image.
Fix frame strength at 75 has a mostly different image, but occasionally the original.
Processing Strength at 0 or 1 don't seem to make any difference, I can't really figure out what this is doing.
Putting both at 0 or putting both at 1 do not result in the original image either.

I think I've been getting the same thing with vid2vid. Generates the first frame as expected, then each subsequent image is just a frame of the new image fading into the original first frame of the input video.

First frame will always be a little bit better, as it is the only frame generated directly from the initial image without influence of the previous frame and the occlusion mask. But after that all other frames should have roughly the same stylization intention.
Check out this discussion, I hope this will help you to get better results: #80 (comment)


MagicMirror update

Hi @bastilimbach
Thanks for your great docker image.
Could you please update it to the latest version?
Thank you a lot

The image gets updated automatically every day by Travis CI. The last build succeeded successfully and did get pushed to Docker Hub. Did you try removing and redownloading the image? What version are you getting?

Please check out my comment on a previous issue. Maybe there is really a problem which I just can't reproduce.

Thanks for your reply,
I wasn't aware of the automatic update. I just checked the date of the last build (7 months) and assumed it wasn't updated.
In fact, thetrouble came from my side. For an unknown reason, some modules like weather and calendar were stuck. a reboot of the docker image and the raspberry did the trick.
Sorry for the burden.

Perfect! The last build time is very confusing indeed. Unfortunately, I can't change that. You need to look at the "Last pushed" date 👍


Fix loading flume integration

Breaking Change:
Fixed error loading flume component #29853.
To resolve this, the PyPi package was updated to store the token file in the TMP directory rather than Python's CWD. Details found here: https://github.com/ChrisMandich/PyFlume
Pull request is to update the current package version to the v0.2.2 found here: https://pypi.org/project/PyFlume/0.2.2/
Description:
Related issue (if applicable): fixes #29853
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#10624
Example entry for configuration.yaml (if applicable):
sensor:
  # Flume
  - platform: flume
    username: YOUR_FLUME_USERNAME
    password: YOUR_FLUME_PASSWORD
    client_id: YOUR_FLUME_CLIENT_ID
    client_secret: YOUR_FLUME_CLIENT_SECRET

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Hello @ChrisMandich,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

77c76803eebbd7aec8ca546de7074c7197f50dca - This commit has something that looks like an email address (cmandich@chrismandich.onmicrosoft.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hello @ChrisMandich,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

fc07e4900bbb95fefb4d9bdfd633a76889e731d2 - This commit has something that looks like an email address (root@desktop-w10.localdomain). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

It's safer to ask Python for the temp directory, than hardcoding it.
https://docs.python.org/3/library/tempfile.html#tempfile.gettempdir
An alternative would be to store the token in the home assistant config dir.

An alternative would be to store the token in the home assistant config dir.

I second that.

It's even better to store token inside Hass. so just expose the data from the api.


fix(client): Fix op-sqlite driver not returning results

The op-sqlite driver returns HostObjects that do not behave the same way as regular JS objects and the parsing was failing somewhere in the field transformations where we use Object methods like Object.entries.
See https://ospfranco.notion.site/Gotchas-bedf4f3e9dc1444480fc687d8917751a
Also GH issue: https://github.com/OP-Engineering/op-sqlite/issues/65
The fix shallow clones the row fields into a JS object, probably losing some of the performance benefits gained from using these kinds of objects in the first place but we can revisit it in the future if it becomes significant.

@samwillis ah that sounds like a cleaner solution, I'll try that right now and update the PR


Break out Breakout components into a more sensible organization

Objective

The components in the Breakout game are defined in a strange fashion.

Components should decouple behavior wherever possible.
Systems should be as general as possible, to make extending behavior easier.
Marker components are idiomatic and useful, but marker components and query filters were not used.

The existing design makes it challenging for beginners to extend the example into a high-quality game.

Solution

Refactor component definitions in the Breakout example to reflect principles above.

Context
A small portion of the changes made in #2094. Interacts with changes in #4255; merge conflicts will have to be resolved.

@bevyengine/docs-team can I get some feedback on this? There's more clean up I'd like to do on this example, but I want to keep the PRs small and sequential.

This is extremely opiniony, but I think that
struct Velocity {
    value: Vec2
}

overall would improve things further.
This looks good to me though.

Awesome, thanks y'all. I'll clean this up; I like your suggestions a lot.

This is extremely opiniony, but I think that
struct Velocity {
value: Vec2
}
overall would improve things further.

So, I made this change in the last commit. Overall, I think it's the more idiomatic than the alternative, but it does litter .0 (or worse, .value) everywhere. IMO we should fix that up later with a Deref / DerefMut impl, but that's a problem for another day.

bors r+


Errors running example repository

This is a Bug Report
Description
Umm, not quite sure if I've done something wrong, but I'm not sure if it's working correctly?
I cloned the repo, ran npm run start:lambda then npm run start:apigateway in another tab. Both opened successfully. I then used Postman to make a request to localhost:5000/lambda-proxy with header Authorization: TOKEN 12345 and I got an Unauthorized response.
Additional Data

Serverless Framework Version you're using: 1.6.1
Serverless Docker Plugin Version you're using: 0.0.6
Operating System: macOS 10.11
Stack Trace:

Lambda:
$ npm run start:lambda

><EMAIL_ADDRESS>start:lambda /Users/hassankhan/Projects/research/serverless-plugin-simulate/examples
> sls simulate lambda -p 4000

Serverless: Starting registry with db at /Users/hassankhan/Projects/research/serverless-plugin-simulate/examples/.sls-simulate-registry
Serverless: Starting registry at: http://<IP_ADDRESS>:4000
PUT /functions 200 16.805 ms - -
GET / 404 1.308 ms - 131
Serverless: Looking up docker-dev-authorizer in registry
Serverless: Invoking docker-dev-authorizer with RequestResponse
Serverless: {"key":"docker-dev-authorizer","serviceName":"docker","servicePath":"/Users/hassankhan/Projects/research/serverless-plugin-simulate/examples","region":"us-east-1","stage":"dev","functionName":"authorizer","handler":"functions/authorizer.handler","runtime":"nodejs4.3","environment":{}}
Serverless: Invoking function functions/authorizer.handler
docker: Error parsing reference: "AWS_REGION-e,AWS_DEFAULT_REGION-e,AWS_ACCOUNT_ID-e,AWS_ACCESS_KEY_ID-e,AWS_SECRET_ACCESS_KEY-e,AWS_SESSION_TOKEN-e,AWS_LAMBDA_FUNCTION_NAME-e,AWS_LAMBDA_FUNCTION_VERSION-e,AWS_LAMBDA_FUNCTION_MEMORY_SIZE-e,AWS_LAMBDA_FUNCTION_TIMEOUT-e,AWS_LAMBDA_FUNCTION_HANDLER-e,AWS_LAMBDA_EVENT_BODY" is not a valid repository/tag.
See 'docker run --help'.
Serverless: Invoking Lambda failed with error
Serverless: [object Object]
POST /2015-03-31/functions/docker-dev-authorizer/invocations 500 62.433 ms - -
Serverless: Looking up docker-dev-authorizer in registry
Serverless: Invoking docker-dev-authorizer with RequestResponse
Serverless: {"key":"docker-dev-authorizer","serviceName":"docker","servicePath":"/Users/hassankhan/Projects/research/serverless-plugin-simulate/examples","region":"us-east-1","stage":"dev","functionName":"authorizer","handler":"functions/authorizer.handler","runtime":"nodejs4.3","environment":{}}
Serverless: Invoking function functions/authorizer.handler
docker: Error parsing reference: "AWS_REGION-e,AWS_DEFAULT_REGION-e,AWS_ACCOUNT_ID-e,AWS_ACCESS_KEY_ID-e,AWS_SECRET_ACCESS_KEY-e,AWS_SESSION_TOKEN-e,AWS_LAMBDA_FUNCTION_NAME-e,AWS_LAMBDA_FUNCTION_VERSION-e,AWS_LAMBDA_FUNCTION_MEMORY_SIZE-e,AWS_LAMBDA_FUNCTION_TIMEOUT-e,AWS_LAMBDA_FUNCTION_HANDLER-e,AWS_LAMBDA_EVENT_BODY" is not a valid repository/tag.
See 'docker run --help'.
Serverless: Invoking Lambda failed with error
Serverless: [object Object]
POST /2015-03-31/functions/docker-dev-authorizer/invocations 500 28.948 ms - -
Serverless: Looking up docker-dev-authorizer in registry
Serverless: Invoking docker-dev-authorizer with RequestResponse
Serverless: {"key":"docker-dev-authorizer","serviceName":"docker","servicePath":"/Users/hassankhan/Projects/research/serverless-plugin-simulate/examples","region":"us-east-1","stage":"dev","functionName":"authorizer","handler":"functions/authorizer.handler","runtime":"nodejs4.3","environment":{}}
Serverless: Invoking function functions/authorizer.handler
docker: Error parsing reference: "AWS_REGION-e,AWS_DEFAULT_REGION-e,AWS_ACCOUNT_ID-e,AWS_ACCESS_KEY_ID-e,AWS_SECRET_ACCESS_KEY-e,AWS_SESSION_TOKEN-e,AWS_LAMBDA_FUNCTION_NAME-e,AWS_LAMBDA_FUNCTION_VERSION-e,AWS_LAMBDA_FUNCTION_MEMORY_SIZE-e,AWS_LAMBDA_FUNCTION_TIMEOUT-e,AWS_LAMBDA_FUNCTION_HANDLER-e,AWS_LAMBDA_EVENT_BODY" is not a valid repository/tag.
See 'docker run --help'.
Serverless: Invoking Lambda failed with error
Serverless: [object Object]
POST /2015-03-31/functions/docker-dev-authorizer/invocations 500 24.557 ms - -
Serverless: Looking up docker-dev-authorizer in registry
Serverless: Invoking docker-dev-authorizer with RequestResponse
Serverless: {"key":"docker-dev-authorizer","serviceName":"docker","servicePath":"/Users/hassankhan/Projects/research/serverless-plugin-simulate/examples","region":"us-east-1","stage":"dev","functionName":"authorizer","handler":"functions/authorizer.handler","runtime":"nodejs4.3","environment":{}}
Serverless: Invoking function functions/authorizer.handler
docker: Error parsing reference: "AWS_REGION-e,AWS_DEFAULT_REGION-e,AWS_ACCOUNT_ID-e,AWS_ACCESS_KEY_ID-e,AWS_SECRET_ACCESS_KEY-e,AWS_SESSION_TOKEN-e,AWS_LAMBDA_FUNCTION_NAME-e,AWS_LAMBDA_FUNCTION_VERSION-e,AWS_LAMBDA_FUNCTION_MEMORY_SIZE-e,AWS_LAMBDA_FUNCTION_TIMEOUT-e,AWS_LAMBDA_FUNCTION_HANDLER-e,AWS_LAMBDA_EVENT_BODY" is not a valid repository/tag.
See 'docker run --help'.
Serverless: Invoking Lambda failed with error
Serverless: [object Object]
POST /2015-03-31/functions/docker-dev-authorizer/invocations 500 34.671 ms - -
Serverless: Looking up docker-dev-authorizer in registry
Serverless: Invoking docker-dev-authorizer with RequestResponse
Serverless: {"key":"docker-dev-authorizer","serviceName":"docker","servicePath":"/Users/hassankhan/Projects/research/serverless-plugin-simulate/examples","region":"us-east-1","stage":"dev","functionName":"authorizer","handler":"functions/authorizer.handler","runtime":"nodejs4.3","environment":{}}
Serverless: Invoking function functions/authorizer.handler
docker: Error parsing reference: "AWS_REGION-e,AWS_DEFAULT_REGION-e,AWS_ACCOUNT_ID-e,AWS_ACCESS_KEY_ID-e,AWS_SECRET_ACCESS_KEY-e,AWS_SESSION_TOKEN-e,AWS_LAMBDA_FUNCTION_NAME-e,AWS_LAMBDA_FUNCTION_VERSION-e,AWS_LAMBDA_FUNCTION_MEMORY_SIZE-e,AWS_LAMBDA_FUNCTION_TIMEOUT-e,AWS_LAMBDA_FUNCTION_HANDLER-e,AWS_LAMBDA_EVENT_BODY" is not a valid repository/tag.
See 'docker run --help'.
Serverless: Invoking Lambda failed with error
Serverless: [object Object]
POST /2015-03-31/functions/docker-dev-authorizer/invocations 500 19.561 ms - -
Serverless: Looking up docker-dev-authorizer in registry
Serverless: Invoking docker-dev-authorizer with RequestResponse
Serverless: {"key":"docker-dev-authorizer","serviceName":"docker","servicePath":"/Users/hassankhan/Projects/research/serverless-plugin-simulate/examples","region":"us-east-1","stage":"dev","functionName":"authorizer","handler":"functions/authorizer.handler","runtime":"nodejs4.3","environment":{}}
Serverless: Invoking function functions/authorizer.handler
docker: Error parsing reference: "AWS_REGION-e,AWS_DEFAULT_REGION-e,AWS_ACCOUNT_ID-e,AWS_ACCESS_KEY_ID-e,AWS_SECRET_ACCESS_KEY-e,AWS_SESSION_TOKEN-e,AWS_LAMBDA_FUNCTION_NAME-e,AWS_LAMBDA_FUNCTION_VERSION-e,AWS_LAMBDA_FUNCTION_MEMORY_SIZE-e,AWS_LAMBDA_FUNCTION_TIMEOUT-e,AWS_LAMBDA_FUNCTION_HANDLER-e,AWS_LAMBDA_EVENT_BODY" is not a valid repository/tag.
See 'docker run --help'.

Thanks for creating the issue @hassankhan. There were a couple of issues here. An issue I found when running the examples + a bug I had already fixed but failed to release properly.
You're going to need to run another npm install on the examples directory once the new version is release. Travis is having a problem right now - https://www.traviscistatus.com/incidents/hx7cnxbch9xf


Trying to make zulip dev server available on a non-local IP

I'm trying to make the zulip dev server available on an non-local (but private) IP address. The objective is for others to be able to play around with zulip also. I am still evaluating zulip and want my team members to do so also.
I followed the instructions for installing the dev server from https://zulip.readthedocs.io/en/latest/development/setup-advanced.html#installing-directly-on-ubuntu-or-debian
Everything went well on my ubuntu 16.04 instance.
Now when I try to run
./tools/run-dev.py -interface 10.XX.XX.XX
Everything looks OK upon startup. When I open the site in the browser (http://10.XX.XX.XX:9991) it seems the webpack resources are not loaded. (I see a huge "Z" and its evident that the CSS/JS for the page has not loaded properly)
These are the errors I get in my browser console
GET http://10.XX.XX.XX:9991/webpack/common.css 500 (Internal Server Error) (index):42
GET http://10.XX.XX.XX:9991/webpack/common.js 500 (Internal Server Error) (index):48
GET http://10.XX.XX.XX:9991/webpack/translations.js 500 (Internal Server Error) (index):49
GET http://10.XX.XX.XX:9991/webpack/portico.css 500 (Internal Server Error) (index):50
GET http://10.XX.XX.XX:9991/webpack/portico.js 500 (Internal Server Error)

Interestingly, If I access http://10.XX.XX.XX:9994/webpack/common.js (port 9994 now) the file gets loaded.

BTW I'm at commit c0751c0644a1f3e

I was able to get this to work by issuing: ./tools/run-dev.py -interface=''
Let me know if this is the correct way of going about this.

I am encountering another issue:
When I try to click on any of the users on http://10.XX.XX.XX:9991/devlogin/ e.g<EMAIL_ADDRESS>then I am sent to http://localhost:9991/accounts/login/local/?next which is clearly an error. When I try to manually go to http://10.XX.XX.XX:9991/accounts/login/local/?next I get the following error in zulip:
MultiValueDictKeyError at /accounts/login/local/
"'direct_email'"
Request Method:	GET
Request URL:	http://10.XX.XX.XX:9991/accounts/login/local/?next
Django Version:	1.11.13
Exception Type:	MultiValueDictKeyError
Exception Value:
"'direct_email'"
Exception Location:	/srv/zulip-py3-venv/lib/python3.5/site-packages/django/utils/datastructures.py in __getitem__, line 85
Python Executable:	/srv/zulip-py3-venv/bin/python3
Python Version:	3.5.2

I was able to get the dev server working by export EXTERNAL_HOST=10.XX.XX.XX:9991.
However, by simply entering the above URL in the browser window (GET) I should not be getting an error.

@sidkshatriya using --interface='' and setting the EXTERNAL_HOST environment is the supported way to do this in development.
The error you were seeing with direct_email was from trying to do a GET request to a POST endpoint; your request was missing the required POST parameter direct_email for that request.
This is all documented here: http://zulip.readthedocs.io/en/latest/development/remote.html


feat(deadline): add ability to import repository settings

Notes
Adds ability to import Deadline Repository settings with a repository settings file (see https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User Manual/manual/repository-settings-importer-exporter.html)
Testing
Creating a JSON file that conformed to the repository settings importer format with a region and a path mapping rule. Modified the example app to use the file in the Repository construct and deployed it. Verified that:

The Repository installer group succeeds in importing the settings with the Repository installer.
Ran the ExportRepositorySettings Deadline command from the RenderQueue container and verified the settings I imported were in the output
Also deployed without the settings and verified the installer still succeeds.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

General question... do we want to be doing this via Deadline's Repository installer? We have the ability to hit RCS endpoints in our Lambdas now, so we could do up a CustomResource that imports Repository settings.
I suppose the two are not mutually exclusive... it makes sense to have the ability to import settings to the repository during an initial installation of the repository, but it also may be desirable to be able to programmatically build out repository settings JSON from deployed infrastructure and import those settings post-Repository-install.


Cleanup libseccomp.a hack since dockerinit is gone

Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

Wow, does that work? I tried to do the same when I removed dockerinit, but Jenkins wasn't happy about it.

ping @tianon @jfrazelle ptal

testing this now thanks

LGTM

Don't we need to do this in more places too?  Or is it OK for us to just start with the RPM code?

I think that is the only place we still do this other than the main
Dockerfile, where we need it because the libseccomp in trusty is too old a
version
On Tue, Feb 2, 2016 at 9:42 AM, Tianon Gravi<EMAIL_ADDRESS>wrote:

Don't we need to do this in more places too? Or is it OK for us to just
start with the RPM code?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/19851#issuecomment-178707654.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

Ah nice, OK!  LGTM :+1:

@jfrazelle we still do it in all the main Dockerfiles, but it's not statically compiling it AFAICS.

yeah i know because trusty version is too low
On Tue, Feb 2, 2016 at 2:04 PM, Aleksa Sarai<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle we still do it in all the main
Dockerfiles, but it's not statically compiling it AFAICS.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/19851#issuecomment-178849291.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3


Large collections of sync table items within a millisecond leads to cycling and never completing the sync

The bug
We have our server side PageSize set to 100. Also, as it says in the documentation, Datasync is to millisecond accuracy. So if a bunch of sync table records are all within a millisecond of one another Datasync pulls a 100 records, realises it hasn't pulled them all, and goes back to the same millisecond and pulls the same 100 records, over and over.
To Reproduce
We had server to client updates that were batching and exceeding the limit of 100.
Expected behavior
Datasync continues with the next 100 records within the millisecond, maybe secondarily sorting on id.
What platforms?

Server:

Version of dotnet being used to compile? NET 6.0
Library versions? Microsoft.AspNetCore.Datasync (6.0.8), Microsoft.AspNetCore.Datasync.EFCore (6.0.8)
What database are you using? SQLite
Where are you running the server? Test is on Azure, live is on GCP

Client:

Version of dotnet being used to compile? NET 6.0
.NET Runtime Environment (WPF, UWP, Xamarin.Forms, etc.): Standard ASP.NET code, in client-server arrangement
Library versions? Microsoft.Datasync.Client 6.0.8, Microsoft.Datasync.Client.SQLiteStore 6.0.8
What database are you using? SQL Server

Additional context
Is it just a matter of increasing PageSize? What value should it go up to and will it create the possibility of large sync calls overwhelming the ASP.NET call size limit? I note that the default value for MaxTop is much larger (512000)?

Why do you have a whole bunch of records with exactly the same DateTimeOffset as UpdatedAt?  Also, why are you using SQLite in production?  There are reasons why SQLite is not appropriate for datasync properties; the major one being that there is no in-built date/time comparison mechanism.
It's an underlying assumption of the library that there are very few records with the exact same updatedAt as it is used as a concurrency token.  Maybe we should adjust that assumption (and we can), but this smells of not having good data objects in the first place.
To answer your specific question, yes - you need to increase the page size so that all records within a millisecond are pulled in one pull.

I think I have a similiar situation (although I'm using MS Sql Server): We create a lot of related entities when changing the status of a 'project' entity in a transaction. Therefore all these entities will have the same 'UpdatedAt' value. But of course they have different 'Version' timestamp values.
I wonder why you don't use the 'Version' as a delta token? I haven't found any reason in the source code. Can you please eleborate on this?


ElasticSearch Component for Docker Cluster

This development introduces the ElasticSearch Component as required in the Task #26 .
The "entrypoint.sh" Script already provides the logic to prepare the Web Application to connect to the ElasticSearch Cluster. So, the changes are few.
Still for complete integration on the development system additional actions are required by the System Administrator.
I also extended the Docker Deployment Documentation to include all needed information to set up the Docker Cluster correctly.
Following the guide at Perldoc Browser Docker Deployment any new contributor should be able to set up a working development environment in 30 min.
Closes #26

According to the last update of the ElasticSearch image for Alpine Linux
documented at  ElasticSearch 6.8 upgrade
the Environment Variable JAVA_HOME does not need to be in the docker-compose.yml anymore

@Grinnz I'm wondering if there is any issue with this development?

Thank you and sorry I haven't looked at this. Hopefully will be upgrading to use elasticsearch 7 to 8 soon but this is great for now.


Update deprecation warning message to show namespace/repo

Small cleanup for deprecation warning.
Right now it only shows the repository name, in the message, it might be better to show
namespace/repo for clarity
Ex:
https://bonsai.sensu.io/assets/jspaleta/sensu-plugins-chef
could read:
jspaleta/sensu-plugins-chef has been deprecated in favor of sensu-plugins/sensu-plugins-chef

@jspaleta - this has been updated!


Not working on fedora

StandardError: An error has occurred, this and all later migrations canceled: Words file not found. Check if it is installed in (/usr/share/dict/words or /usr/dict/words)

@ka8725 How did you install this gem?
Did you
$ bundle install

or
$ gem install randexp

or
$ sudo dnf install -y rubygem-randexp


keyof can incorrectly infer never.

TypeScript Version:  2.4.1
Code
function foo<K extends keyof {[id: number]: data}>(bar: K): void {}

Expected behavior:
K extends number.
Actual behavior:
K extends never.
Other info
function foo<K extends keyof {[id: string]: data}>(bar: K): void {}

In this case, K correctly extends string.

On second thoughts, this is probably not a bug. Without numerical constant types, extending number isn't going to gain much, and comparing floating-point numbers is notoriously dicey.

Might be worth mentioning it in the docs as a potential gotcha.


can't use handlebars.js code

when type the code of "handlebars.js", the editor will be broken.
ex: {{#each .}}

This is documented here: https://toolchain.gitbook.com/templating/#escaping
Just put {% raw %} {% endraw%} around the block of code

@AaronO I would consider closing this issue as answered

@Mackiovello Closing, thanks


Remove List.iterate from exported functions

Hm, I don't think we actually want to expose List.iterate 😅
Or at least that's how I remember the design discussion!

That's disappointing to hear. I used it to solve one of the Advent of Code problems by exiting the loop early when a card reached bingo. I can implement the same with List.walk and skip the rest of the loop or with a recursive function.
Let me know whether to close this PR.

Will the documentation still show iterate if it is not meant to be used?

Oh, walkUntil is supposed to be for that! 😅
I'm not sure why walkUntil is not exposed but iterate is; it should be the other way around.

Oh and also walkBackwardsUntil should be exposed too!

I removed List.iterate from the exported functions, so it no longer appears in the documentation. We should probably think about how we want to document the API exposed outside the library and the API exposed internally across the library.
In this case, we had a function (List.iterate) that we wanted to use internally in the Roc Standard Library, but we didn't want to expose it outside the library, so how can we support these two use cases?

Since I touched the Dict.contains definition to remove the use of List.iterate, I added some documentation and tests to it.


Incorrect result with recursive types and definitions

Given the following program
-module(test).

-compile(export_all).
-compile(nowarn_export_all).

-spec trans(string(), [ast_erl:form()]) -> [ast:form()].
trans(Path, Forms) -> trans(Path, Forms).

(The modules ast.erl and ast_erl.erl from etylizer must be in the source path)
Type checking this program fails with
test.erl:7:1: Type error: function trans/2 failed to type check against type fun((string(), [ast_erl:form()]) -> [ast:form()])
%    7| trans(Path, Forms) -> trans(Path, Forms).
%     | ^

This is wrong!
The constraints are:
[{scsubty, 7:23, [ast:form()], [ast:form()]},
 {scsubty, 7:35, [ast_erl:form()], [ast_erl:form()]},
 {scsubty, 7:29, string(), string()}]

This constraint set is solvable but tall fails to find a solution.
Another interesting aspect: tally needs ~700ms to detect that no solution exists. Next, it searches for a smaller subset of the constraint set, that is still unsatisfiable. It first looks only at these two constraints:
 {scsubty, 7:23, [ast:form()], [ast:form()]},
 {scsubty, 7:29, string(), string()}

But tally does not find a result in under 4 seconds!
@albsch can you investigate?

Reason of failure is likely #183 and #9 . I'll check again after those issues have been fixed.

How exactly do you execute the test case?
I have a folder debug with the files ast.erl, ast_erl.erl and a file containing the function above called test1.erl.
When I execute

./ety -f -l debug -S debug debug/test1.erl -o trans/2

I get the following name error:
[NOTE ety_main.erl:150] Performing type checking
[INFO cm_index.erl:57] Loading index from "./_etylizer/index"
[INFO cm_check.erl:23] All sources: ["debug/test1.erl", "debug/ast.erl", "debug/ast_erl.erl"]
[INFO cm_check.erl:32] Forced to recheck everything
[NOTE cm_check.erl:41] Need to check 3 of 3 files: ["debug/test1.erl", "debug/ast.erl", "debug/ast_erl.erl"]
[NOTE cm_check.erl:82] Checking debug/test1.erl
[INFO typing.erl:63] Checking 1 functions in debug/test1.erl against their specs (1 environments)
[INFO typing_check.erl:18] Checking 1 functions in debug/test1.erl against their specs
[INFO typing_check.erl:56] Type checking trans/2 at debug/test1.erl:8:1 against type fun((string(), [ast_erl:form()]) -> [ast:form()])
[INFO typing_check.erl:104] Checking function trans/2 at debug/test1.erl:8:1 against type fun((string(), [ast_erl:form()]) -> [ast:form()])
debug/ast.erl:227:17: Name error: type export_form/0 undefined

Am I missing something obvious @skogsbaer ?

I place the test1.erl file at the toplevel dir of the etylizer project and then execute ./ety --build --force --level debug --no-deps test1.erl

How do I test this in isolation, i.e. why does -S not extend the symtab even though the files are picked up?

Minimal example:
-module(test).
-compile([export_all, nowarn_export_all]).

-type exp() :: {a | exp()}.
-spec trans(exp()) -> exp().
trans(Forms) -> trans(Forms).


Adds link to wilkinson et al

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 44.552%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
4903

Relevant Lines:
11005

💛  - Coveralls


Remove version string from most examples, two have been left intentionally

Summary
As discussed at the TSC meeting on October 14th, this PR removes the OPENQASM version string from most of the examples
Details and comments
The version string is optional, and leaving it out is the general default. It was originally included to enable any potential breaking changes to be included, but since we have been able to maintain backward compatibility it is mostly unnecessary, and the TSC decided that compilers should/can decide for themselves which parser to use based on the features in the translation unit being parsed.

We perhaps could annotate the version statement in the teleport.qasm example to explicitly say that the OPENQASM 3; statement is optional, so we're not only saying it implicitly by its absence in other examples?  We technically were doing that already, since two files didn't have it (and it being optional is in the spec), but that still led to some questions.

Good idea, will add some comments
On Thu, Oct 27, 2022, 12:20 PM Jake Lishman @.***>
wrote:

We perhaps could annotate the version statement in the teleport.qasm
example to explicitly say that the OPENQASM 3; statement is optional, so
we're not only saying it implicitly by its absence in other examples? We
technically were doing that already, since two files didn't have it (and it
being optional is in the spec), but that still led to some questions.
—
Reply to this email directly, view it on GitHub
https://github.com/openqasm/openqasm/pull/404#issuecomment-1293773580,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJVQ2V6L4ENXLZ2Z3ZMHLDWFKTWVANCNFSM6AAAAAARQGLKNA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, for further context for others: the current version of the OQ3 paper on arXiv is where the confusion arises from.  It says (sec. 3)

Top-level circuits in OpenQASM2 must begin with the statement OpenQASM 2.x;, possibly preceded by one or more blank lines or lines of comments [...] Top-level circuits in OpenQASM3 begin similarly, e.g., with a statement OpenQASM 3.x;

[sic: both sentences are actually false on the basis of their improper capitalisation of the OPENQASM token, but that's beside the point]
The living spec in this repository, and hosted at openqasm.com has always instead said that the version statement is optional in OpenQASM 3 programs.  If we have a chance to update the paper, it would be good to correct this obvious conflict.

We perhaps could annotate the version statement in the teleport.qasm example to explicitly say that the OPENQASM 3; statement is optional, so we're not only saying it implicitly by its absence in other examples? We technically were doing that already, since two files didn't have it (and it being optional is in the spec), but that still led to some questions.

Added in https://github.com/openqasm/openqasm/pull/404/commits/b7d112f4ffcf01d0cdded559013e3dd563c947b0

From TSC 2022-10-28: this matches expectations, so merging.


Update _bookdown.yml

Update the book_filename and repo within _bookdown.yml

Rerunning the workflow for outputting the courses because several of the broken links are using iframes pointing to the old course name.

@ehumph I have addressed flags from the spelling and URL checkers and have re-rendered the output courses and think this is ready for review now. Not sure if the course outputs will need to be re-rendered after merging the changes to address the rest of the broken URLs -- but I think @carriewright11 can help with determining that


improved the vidstreaming extractor (at least i think?)

this should be tested to see if any providers break bc of it
(already broken providers dont count ;p)

this PR should not exist....ill remake...its a mistake as is

actually no, all i did was use a different link, so my PR was completely useless...


Visualizing dependency trees

Extend NLTK's tree drawing module to support the display of dependency trees. Include the methods used by IPython Notebook, cf #684.
NB http://nlp.stanford.edu/software/stanford-dependencies.shtml

@gmonce we would very much like to integrate your work on visualising dependency trees.

It will be a pleasure, just let me know what I can do to help. What I have mostly done is to generate dot representations from the dependency parse structure of NLTK

Thanks. So, would the next step be to add dot and _repr_svg methods to Tree and DependencyGraph? @oplatek might be able to contribute.

Actually, since dot is format, you can create _repr_dot_ function which would be used in _repr_svg_, _repr_png_, etc together with graphviz library to create svg and png images.
Let me know when/if I can help.

I created PR https://github.com/nltk/nltk/pull/891

Resolved by #891.


Use new, not initialize, to enforce runtime abstract

Note to users: this PR might cause new errors in any code that was
previously defining initialize in an abstract! class and then trying to
instantiate it at runtime.
Doing that would have had the effect of redefining the method that
sorbet-runtime previously defined to enforce that abstract classes can't be
instantiated, which would have allowed the instantiation. This will not happen
anymore.

Motivation

Fixes #3388
The general idea is that people want both:

runtime enforcement that abstract classes are not instantiated
the ability to have common initialization code in an abstract class's
constructor

By moving the "no new" enforcement to happen in self.new instead of
initialize, we can accomplish this. It's far, far more rare for people to have
valid use cases for overriding self.new.
This also unblocks being able to override initialize at runtime and mark it
abstract, so that it can be used to enforce that all subclasses conform to a
standard contract for constructing new instances.
Test plan

See included automated tests.
I tested this against Stripe's codebase and 17 tests failed that were errantly
attempting to instantiate an abstract class at runtime in a way that Sorbet
couldn't catch statically.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_No3dBatUPfwnyR
→ https://go/builds/bui_No3dy8VqUCeTla
→ https://go/builds/bui_No3dxnAZ6ONGqd
→ https://go/builds/bui_No3dxnAZ6ONGqd

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_NrM8Klkuvtef99
→ https://go/builds/bui_NrM8Ld9XhkH1QA
→ https://go/builds/bui_NrM86zREjDsYVO
This change also has sorbet-runtime changes. Those tests:
→ https://go/builds/bui_NrMDNVKbtQwaHh


add RETURN_SCENARIO env variables

Datamodel scenario feedback in any environment
A feature to help debug AnyLogic model results. This setting is used in the /wt/api/nextjs/v2/holon/ endpoint to determine whether to send back the used scenario (through the serializer) or not. This should ideally not be set to true in production since it will impact performance.
RETURN_SCENARIO=True

One thing I'm unsure of is whether setting the Azure settings to this setting will be able to toggle this functionality without having to push a new container. If yes, then we can use this setting to develop with the content on main and later disable the functionality when we are happy with the outcomes.

This should ideally not be set to true in production since it will impact performance.

Doel je hier op de grootte van de response of triggert de serializer database queries? Want de response is ~175kb uncompressed dus dit valt wel mee.

If yes, then we can use this setting to develop with the content on main and later disable the functionality when we are happy with the outcomes.

Idee: dit met een cookie te zetten ipv enviroment variable.


test: Remove Posix Relative Path

Partially reverts https://github.com/quisquous/cactbot/pull/2760

I can't remember why the backslash replacing was there in the first place.  Did you end up testing this in cmd?

I can't remember why the backslash replacing was there in the first place. Did you end up testing this in cmd?

Tested in both Git Bash and Command Prompt on Windows 10, as well as whatever the CI is using (bash on Linux?)

Thanks for the fix.  Sorry for the awful suggestion that caused this.  <_<


refactor types

Codecov Report

Merging #11 into v1.0.0 will decrease coverage by 1.94%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           v1.0.0   #11      +/-   ##
=======================================
- Coverage   81.94%   80%   -1.95%
=======================================
  Files           9     8       -1
  Lines          72    65       -7
=======================================
- Hits           59    52       -7
  Misses         13    13

Impacted Files
Coverage Δ

collection/array.go
100% <0%> (ø)
:arrow_up:

collection/collection.go
100% <0%> (ø)
:arrow_up:

collection/each.go

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 abc921a...3c1ab95. Read the comment docs.


simulator download link is not working

It's seems to be the download URL is currently not working.

Thank you for bringing this to our attention. We have updated the download URL. Please try accessing it again using the link below:  https://drive.google.com/file/d/1ayAQZbPOyQV2W-V_ZdYv6AoqLOg0zvm1/view

Thank you very much!
I wish you the best of luck with everything


Crash

When opening the customization menu in mod menu it crashes for some reason
crash-2022-05-10_14.56.21-client.txt

This is an incompatibility with the 3D Skin Layers mod, and I can't fix this on my side. I will open an issue on their github.
For now you can remove either mod and it should work.

Ok thanks for the information. Would really appreciate it if you put a warning on the mod page so other don't make the same mistake


[WIP]: Refactor DETR

Motivation
We (me, @jshilong, @LYMDLUT, and @KeiChiTse) are going to refactor DETR-like models, to enhance the usability and readability of our codebase.

Short-term Plan
We plan to implement a base detector class for Transformer-based detector, TransformerDetector, move the transformer-related part in the original head module to the new detector module, and use TransformerEncoder and TransformerDecoder directly in the detector.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Li-Qingyun:x: LYM-fireYou have signed the CLA already but the status is still pending? Let us recheck it.

We decided to PR refactored DETR-related modules on dev-3.x. Hence, this PR may not be updated, but reviews and comments about this PR will continue to be answered. The new PR is #8763.

To [WIP]: Refactor DETR and Deformable DETR on 3.x #8763


Replace optIn with a useType

Hi @codeofsumit!
In order to make your wonderful library work for me and to show our needs better I create this Draft PR. I started working on this, because my performance was significantly reduced. And I believe the root cause is the init hooks, that get added to every Leaflet layer. (I have a map with more than 10k Leaflet elements.)
As my changes change the mechanics of the library quite a bit, I want to include you as early as possible. And would love to hear if this makes sense to you and how we should work from here.
Short description of the changes. Before we had two attributes on different layers that were able to toggle the abilities of the library. That was optIn on a more global level and pmIgnore on a more local (layer) level. I found this concept hard to grasp and also as commented on your initial PR  #504 had some problems to make this work.
So to make the handling easier I introduced a useType which currently can have two values

ALL_LEAFLET_LAYERS use geoman on all available Leaflet layers/objects
GEOMAN_LAYERS_ONLY use geoman only on layers drawn with geoman itself so only available to extended Leaflet classes

This obviously removes the possibility to enable geoman on a specific layer, as you could have done before. Adding this functionality could be done with another useType and handling it accordingly.
Another note: I haven't checked all use cases by far, and so it is very well possible that parts are not working as expected. I just want to get your thoughts first. Before investing more time.
Appreciate your time and looking for your feedback! 🎉

hi @limfinity, hm that option currently does not seem like a direction I would like to go.
I will think about it a bit more. Nonetheless, the optIn part is correct and I'm going to change that and performance is next on my list to tackle anyway. If you have large geojson files to test against, send them my way :-)

I'm going to close the now as I have made some progress on both fronts. The OptIn situation will be completely revamped and new options will be introduced to handle massive amounts of that. Will post updates in all related Issues/PRs once I can show something


Issue when multiply and divide

Incorrect result when multiply and divide
new Fraction("2") * new Fraction("1/2") result 3
new Fraction("2") / new Fraction("1/2") result 6

Thanks for your report.
Checking on the way.

Bug located. Source is updated. Please allow 1-2 hrs for nuget refreshing.

I close this issue for now. If there is still any problem related, please re-open it. Thanks.

I close this issue for now. If there is still any problem related, please re-open it. Thanks.


fetchArchive: init

Motivation for this change
Even though fetchzip uses stdenv's unpackFile to unpack .{tar{,.*},zip} files, it doesn't expose any convenient way to extend it to handle anything other than that.
Additionally, fetchzip's stripRoot goes beyond ignoring archive metadata/algorithm non-determinism and affects actual archive contents.
This is an attempt at a more explicit API that only fetches, then unpacks with one of inputs. It uses SRI hashes added in Nix 2.2 to avoid code churn that happens to algorithm-specific arg attrs as hash algorithms change.
stripRoot is implemented a la carte as a function that takes a directory and returns its first child.
Short list of changes:

add unpackCmd hook to dpkg
add SRI hash support to fetchurl
add fetchArchive + docs
showcase fetchArchive on typora derivation
add lib.stripRoot + docs

Fetch examples:
fetchArchive {
  url = https://github.com/NixOS/nix/archive/2.2.1.tar.gz;
  hash = "sha512-U8y9gVgvjowXZ/lTp7fxqRrWFbxZwrbS4LY95XduiM2plvhQ37rJ5TACo/PHStCILSvhzHG19UBZ1bWP62jEgQ==";
}

fetchArchive {
  url = https://github.com/NixOS/nix/archive/2.2.1.zip;
  hash = "sha512-U8y9gVgvjowXZ/lTp7fxqRrWFbxZwrbS4LY95XduiM2plvhQ37rJ5TACo/PHStCILSvhzHG19UBZ1bWP62jEgQ==";
  inputs = [ unzip ];
}

fetchArchive {
  url = https://deb.debian.org/debian/pool/main/a/apt/apt_1.4.8_arm64.deb;
  hash = "sha512-/6NY2ZhfJIKA6Qzg5vBxVaG9qfR7TqF/kK2ntzwMGXGpg2ycopjUAtxLqqRsM87OZQsYS7hklQhHcvx/NVz3dQ==";
  inputs = [ dpkg ];
}

Derivation override example:
nixUnstable.overrideAttrs (super: {
  src = lib.stripRoot (fetchArchive {
    url = https://github.com/NixOS/nix/archive/2.2.1.tar.gz;
    hash = "sha512-U8y9gVgvjowXZ/lTp7fxqRrWFbxZwrbS4LY95XduiM2plvhQ37rJ5TACo/PHStCILSvhzHG19UBZ1bWP62jEgQ==";
  });
})

Maybe this should better be called fetchThenUnpack. Also, instead of lib.stripRoot, stdenv can be tweaked into supporting non-stripped sources.
cc @grahamc, @LnL7, @oxij, @zimbatm
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Are there any updates on this pull request, please?


Requirements closing [RFC]

[DRAFT]
The final requirements for notification service.

User can be notified about their inactivity.
Calendar can send notification to user by any medium. (Email, Push, In-app)
How will we handle dismissing notifications?
how will we handle the case where multiple people get the same notification, but they have to manage it on their notifications list

MOM: 4th Feb 2023 9:30 AM IST

To identify the Messaging system as per our use-case Kafka/ Rabbit MQ
We can have priority of messages (Promotional / Announcements / Subscription to some event on the calendar site)
The notification service should expose the APIs to the other services, its job will be to handle the validation of requests coming.
We should build the service to easily support a new SMS or email provider in future.
The notification service should handle Authentication and Authorization of requests coming.
Decide on a push-based model vs a pull-based model (Kafka = pull vs rabbit MQ = push)
Kafka pull-based model
How we can retry messages on failure
We should try building a user preference system similar to slack
Integration of WhatsApp message delivery.
We can choose multiple SMS providers based on pricing for the region. For instance, Twillio for the US and some others for India, based on pricing.