Create task

Task

Thanks for the PR @somaiyappan
Could you please add more details as mentioned in the questions.md file?
There is a section titled Introductions, could you please add answers to those?

Yes, I done it sir
On Fri, 25 Aug 2023, 5:03 pm Ashish Kurian Thomas [Mediwave], <
@.***> wrote:

Thanks for the PR @somaiyappan https://github.com/somaiyappan
Could you please add more details as mentioned in the questions.md file?
There is a section titled Introductions, could you please add answers to
those?
—
Reply to this email directly, view it on GitHub
https://github.com/mindwaveventures/join-us/pull/57#issuecomment-1693217076,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALF7ILXRHTNZKPET43LGEDLXXCEQZANCNFSM6AAAAAA36H7GRY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sorry! I cant see it in the PR
Please go through https://github.com/mindwaveventures/join-us/blob/main/questions.md#introductions and update your PR to include this information as well.

I just updated it.
On Fri, 25 Aug 2023, 5:29 pm Ashish Kurian Thomas [Mediwave], <
@.***> wrote:

Sorry! I cant see it in the PR @somaiyappan
https://github.com/somaiyappan
Please go through
https://github.com/mindwaveventures/join-us/blob/main/questions.md#introductions
and update your PR to include this information as well.
—
Reply to this email directly, view it on GitHub
https://github.com/mindwaveventures/join-us/pull/57#issuecomment-1693244702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALF7ILQU3BFYF5F3FIP6CSTXXCHRJANCNFSM6AAAAAA36H7GRY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you @somaiyappan


Owned Types: SaveChanges fails on Relational but succeeds for In-memory

Given the following:
public class OwnedAddress
{
    public OwnedCountry Country { get; set; }
}

public class OwnedCountry
{
    public string Name { get; set; }
}

public class OwnedPerson
{
    public int Id { get; set; }
    public OwnedAddress PersonAddress { get; set; }
}

public class Branch : OwnedPerson
{
    public OwnedAddress BranchAddress { get; set; }
}

public class LeafA : Branch
{
    public OwnedAddress LeafAAddress { get; set; }
}

public class LeafB : OwnedPerson
{
    public OwnedAddress LeafBAddress { get; set; }
}

protected virtual void OnModelCreating(ModelBuilder modelBuilder)
{
    modelBuilder.Entity<OwnedPerson>().OwnsOne(p => p.PersonAddress).OwnsOne(a => a.Country);
    modelBuilder.Entity<Branch>().OwnsOne(p => p.BranchAddress).OwnsOne(a => a.Country);
    modelBuilder.Entity<LeafA>().OwnsOne(p => p.LeafAAddress).OwnsOne(a => a.Country);
    modelBuilder.Entity<LeafB>().OwnsOne(p => p.LeafBAddress).OwnsOne(a => a.Country);
}

protected static void AddTestData(DbContext context)
{
    context.Set<OwnedPerson>().AddRange(
        new OwnedPerson
        {
            PersonAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "USA" }
            }
        },
        new Branch
        {
            PersonAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "USA" }
            },
            BranchAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "Canada" }
            }
        },
        new LeafA
        {
            PersonAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "USA" }
            },
            BranchAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "Canada" }
            },
            LeafAAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "Mexico" }
            }
        },
        new LeafB
        {
            PersonAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "USA" }
            },
            LeafBAddress = new OwnedAddress
            {
                Country = new OwnedCountry { Name = "Panama" }
            }
        });

    context.SaveChanges();
}

The SaveChanges call throws on relational:
---- System.InvalidOperationException : There are '9' entity types sharing the table 'OwnedPerson', but only '3' entries with the same key values have been marked as 'Added'. The missing entities should be assignable to {'Branch.BranchAddress#OwnedAddress', 'LeafA.LeafAAddress#OwnedAddress', 'LeafB.LeafBAddress#OwnedAddress', 'Branch.BranchAddress#OwnedAddress.Country#OwnedCountry', 'LeafA.LeafAAddress#OwnedAddress.Country#OwnedCountry', 'LeafB.LeafBAddress#OwnedAddress.Country#OwnedCountry'}. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see the key values.
---- The following constructor parameters did not have matching fixture data: OwnedQuerySqlServerFixture fixture

	----- Inner Stack Trace #1 (System.InvalidOperationException) -----
	C:\dev\github\aspnet\EntityFramework\src\EFCore.Relational\Update\Internal\ModificationCommandIdentityMap.cs(129,0): at Microsoft.EntityFrameworkCore.Update.Internal.ModificationCommandIdentityMap.Validate(Boolean sensitiveLoggingEnabled)
	C:\dev\github\aspnet\EntityFramework\src\EFCore.Relational\Update\Internal\CommandBatchPreparer.cs(140,0): at Microsoft.EntityFrameworkCore.Update.Internal.CommandBatchPreparer.CreateModificationCommands(IReadOnlyList`1 entries, Func`1 generateParameterName)
	C:\dev\github\aspnet\EntityFramework\src\EFCore.Relational\Update\Internal\CommandBatchPreparer.cs(67,0): at Microsoft.EntityFrameworkCore.Update.Internal.CommandBatchPreparer.<BatchCommands>d__8.MoveNext()
	C:\dev\github\aspnet\EntityFramework\src\EFCore.Relational\Update\Internal\BatchExecutor.cs(71,0): at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(Tuple`2 parameters)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\Extensions\ExecutionStrategyExtensions.cs(331,0): at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_0`2.<Execute>b__0(DbContext c, TState s)
	C:\dev\github\aspnet\EntityFramework\src\EFCore.SqlServer\Storage\Internal\SqlServerExecutionStrategy.cs(39,0): at Microsoft.EntityFrameworkCore.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state, Func`3 operation, Func`3 verifySucceeded)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\Extensions\ExecutionStrategyExtensions.cs(329,0): at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy, Func`2 operation, Func`2 verifySucceeded, TState state)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\Extensions\ExecutionStrategyExtensions.cs(279,0): at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy, TState state, Func`2 operation)
	C:\dev\github\aspnet\EntityFramework\src\EFCore.Relational\Update\Internal\BatchExecutor.cs(49,0): at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(IEnumerable`1 commandBatches, IRelationalConnection connection)
	C:\dev\github\aspnet\EntityFramework\src\EFCore.Relational\Storage\RelationalDatabase.cs(51,0): at Microsoft.EntityFrameworkCore.Storage.RelationalDatabase.SaveChanges(IReadOnlyList`1 entries)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\ChangeTracking\Internal\StateManager.cs(787,0): at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IReadOnlyList`1 entriesToSave)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\ChangeTracking\Internal\StateManager.cs(712,0): at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\DbContext.cs(355,0): at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess)
	C:\dev\github\aspnet\EntityFramework\src\EFCore\DbContext.cs(323,0): at Microsoft.EntityFrameworkCore.DbContext.SaveChanges()

But, In-memory is able to persist the data correctly.

oh I think this is what I've been beating my head on today! InMemory was ok but integration tests against SQL Server db fail
Using preview2-final and trying to add an object (samurai) that has a SecrectIdentity property that is  valueobject defined in fluent API as OwnsOne. Error is almost the same as the error in this issue:
There are '2' entity types sharing the table 'Samurais', but only '1' entries
with the same key values 'Id:-2147482647' have been marked as 'Added'. The missing entities should be assignable t
o {'Samurai.SecretIdentity#Identity'}
Is that what I'm hitting? I wanted to avoid nightly builds for my demos at a conference coming up in a few days so will decide if I want to use nightlies or not show off this feature. Hmmmm..... :)

updated packages to preview3-* and still having this problem. Now I'm wondering if it's related to https://github.com/aspnet/EntityFramework/pull/8986 which isn't merged yet?

@julielerman Could you file an issue with a full listing or project that reproduces what you are seeing?

will do! May have to wait until end of week (conference) I'll also recheck after 8986 is merged.

@julielerman Owned entities are still entities. And owned entities are not optional when using table splitting (the default)

Sorry, I thought that iwthout an ID, it isn't an entity. (DDD & old-EF comlext type assumptions)
However, this happens when I create the owned object. Will be better when I provide a repo. Just out of time right now having  spent a lot of time on this over the weekend.

I just retested with preview3-* and rtm-*  (currently rtm-26180) and still getting this problem. I will open a separate repo and link to this for ref. Just have to create a trimmed down, focused solution.

@AndriySvyryd re your explanation that  "owned entities are not optional when using table splitting (the default)" What alternatives are there (non default)? I do expect the values of the value object to be stored in the same table as the entity that uses that object as a property so not sure how else to do that without table splitting.  The fact that the owned entity is not optional creates some other types of problems for how I would design my domain model following DDD guidance. For one there's no chance to have null objects. Even if I default the property to having each of it's values null, I would have to do some unconventional logic be able to test for a null object (e.g. test that every property of the value object is null and that creates more complexities with value types like int).
Am I missing something or is this just the way it is right now? Is there any plan to change this going forward? Shall I create an issue that you can mark as enhancement?

@julielerman The fundamental problem with optional dependents using table splitting is determining differentiating between a non-existent dependent and one with all properties having the default values.
Suppose we have these classes:
public class Customer
{
    public int Id { get; set; }
    public Address Address { get; set; }
}
public class Address
{
    public int Id { get; set; }
    public string Street { get; set; }
}

And they are mapped to the same table with columns Id, Street.
If we query a row with values 1, null should we create an Address with Street set to null or leave Customer.Address as null?
We are going to investigate this in https://github.com/aspnet/EntityFramework/issues/9005
For now any dependents using table splitting are required. To make a navigation to an owned type optional you would have to map it to a different table.

I hadn't discovered #9005. That is most excellent! I totally grok the challenges you have! Now I can use my little workaround but also share with folks know this will get easier! Thanks @AndriySvyryd ! :)


missing avx2 intrinsics

Current rav1e master shows:
warning: unsupported x86 llvm intrinsic llvm.x86.avx2.pabs.w; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.pmadd.wd; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psign.w; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psrlv.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.packssdw; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.gather.d.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx.cvtdq2.ps.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psllv.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psrav.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.sse2.packssdw.128; replacing with trap

Some of these (but not all) should have been implemented by https://github.com/rust-lang/rustc_codegen_cranelift/pull/1417 which hasn't landed on rustc nightly yet.

Yes :) I tested with the current master and the list is shorter:
warning: unsupported x86 llvm intrinsic llvm.x86.avx2.pabs.w; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psign.w; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psrlv.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psllv.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.psrav.d.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx.cvtdq2.ps.256; replacing with trap

warning: unsupported x86 llvm intrinsic llvm.x86.avx2.gather.d.d.256; replacing with trap

The gather intrinsics are now implemented on the even_more_simd_intrinsics branch.

I'm getting warning unsupported x86 llvm intrinsic llvm.x86.avx2.psllv.d.256; replacing with trap
and invocation of image-rs crate (avif encoder) results in crash:
trap at Instance { def: Item(DefId(2:15232 ~ core[a9f5]::core_arch::x86::avx2::_mm256_sllv_epi32)), args: [] } (_ZN4core9core_arch3x864avx217_mm256_sllv_epi3217h96c8b42e4aa5b850E): llvm.x86.avx2.psllv.d.256

I don't see permd listed above, but this is the same issue right?
trap at Instance { def: Item(DefId(1:15384 ~ core[212b]::core_arch::x86::avx2::_mm256_permutevar8x32_epi32)), args: [] } (_ZN4core9core_arch3x864avx227_mm256_permutevar8x32_epi3217h294fc7d72ae002f8E): llvm.x86.avx2.permd

I just added permd in https://github.com/rust-lang/rustc_codegen_cranelift/pull/1491 (cc @svix-jplatte)
that PR is also a good template for if someone wants to add other avx2 intrinsics. Cranelift does not support values that wide (currently, not sure if it ever will) so the implementation will have to kind of simulate what the instruction does.

For that to become available via rustup, this repo needs to be synced into https://github.com/rust-lang/rust again, right?

Correct, I can do that later today.

Thanks, yesterday's nightly has support! I'm now also running into a llvm.x86.avx2.psllv.d.256 trap with the other one fixed :smile:


AO Pass: Transparent objects are all black

This was due to inverted faces and not accounting for inverting the normal for back faces.


CB-6617 Upgrade does not work due to lazy init

Should go against 2.20

Switched to 2.20, I have originally fixed it on 2.20, but accidentally opened against the master


Tesla radar interface

Implemented a radar interface for Tesla Model S

Jenkins failure doesn't seem to be related to this PR

Jenkins failure doesn't seem to be related to this PR

It might have been after all, since I wasn't waiting on a new trigger message, hence the increased CPU usage

Switched from using the radar tracks the radar computes to outputting the raw data points (up to 32). Should be good to merge now!

The radar also outputs the variance for all its measurements. We don't use this now, but cool to add in the future maybe?


Show a loading icon to denote that something is happening in the background

On contributor console, right before the user goes to corporate console there is a long wait at this screen.

This wait is misleading to the user without any loading or activity icon, we should add one so that the user knows that something is happening in the background before the user is redirected.

Verified that Loading spinner is shown while processing.

cc: @vinod-kadam

Verified that Loading spinner is shown while processing.

cc: @vinod-kadam


added ssh-node redirect

No!!

@sascala can't you just back out that change from this commit?

Probably...


[BUG]vela.yaml and Dockerfile path dependency?

Describe the bug
Using the example/testapp. When running  vela up under the examples/testapp, everything is fine. However when running vela up from another folder, there is error message.
To Reproduce
go to examples.
run vela up -f testapp/vela.yaml,

Yes. The vela.yaml in example/testapp has build dependency. If you already have the image built, you need to remove/comment the build config.

I think it's by design, the vela.yaml should under the source project of app with dockerfile if you want to build from source.


add notes about fork policies

Describe known branches and forking mode

Are we going to update https://github.com/giantswarm/cluster-api-provider-cloud-director-app from this repo from now on?

Are we going to update giantswarm/cluster-api-provider-cloud-director-app from this repo from now on?

First of all we should implement https://github.com/giantswarm/roadmap/issues/1183.
By doing this the same way as we currently do with CAPO it will be very easy to switch between different repositories for creating releases.
In the past/at the moment we've build the app from unreleased upstream main branche.


Window is not exiting with pyglet.app.exit()

Hi @benmoran56 ,
I am using glooey and pyglet in my project and want  to use exit function in a button to exit the window created.
You can find my code here , It is just to show how I want to use app.exit()  but it is non responsive. Are you able to help ?
import pyglet
import glooey

class MyLabel(glooey.Label):
    custom_color = '#000000'
    custom_font_size = 12
    custom_alignment = 'center'

# Encode
class MyButton(glooey.Button):
    Foreground = MyLabel
    custom_alignment = 'center'

    class Base(glooey.Background):
        custom_color = '#D3D3D3'
        custom_top_padding = -10
        custom_bottom_padding = -10
        custom_right_padding = -10
        custom_left_padding = -10

    def on_click(self, widget):
        try:
            pyglet.app.exit()
        except Exception as e:
            print(e)
width, height=1342,960
window = pyglet.window.Window(width = width, height = height,caption='mesh display')
gui = glooey.Gui(window)
grid = glooey.Grid()
grid.add(0,0,MyButton("Exit"))

gui.add(grid)
pyglet.app.run()

try just exit() instead of pyglet.app.exit().
when i use pyglet.app.exit() nothing happens.  just using plain exit() and all stops as it should.

This example code works as expected on both my Linux machine, and Windows 10 VM.
The "not responding" message in the title indicates that the application is frozen. I think something else might be going on here. You might want to try to uninstall / reinstall both pyglet and glooey for a start.

Hi @flowerbug, @benmoran56 thank you for your reply.
It worked by using both in a code.
exit()
pyglet.app.exit()


support for markup inside translated strings

Sometimes you need to translate something like:

If your download does not begin automatically, click here.

Or even just:

Another translated string with just a tiny bit of markup inside it.

Seems like a common use case but didn't see it documented, so I thought I'd open a ticket.
What's the best way to achieve this? You could divide the single translated string into three parts (e.g. before_markup, inside_markup, after_markup), but this doesn't scale to more nested markup:

Then I asked, <q>Did you just say <q>nested markup</q>?</q>

In a case like this, it would be nice to include everything in the
 element in a single translated string, and each translation would include the necessary contained markup. Is this possible?
ng-bind-html and ng-bind-html-unsafe can be used to include sanitized or unsanitized markup. Do they help? Ideally the angular-translate-injected markup could also support live angular behavior too:

To open now, click here.

Is that possible?
Thanks for reading, and thanks for the great work on angular-translate!

The original question was also about using links and actually I'm not able to get that to work. I have a situation where I would like to feed the href url from the scope using curly braces. I have a plunker here: http://plnkr.co/edit/8eArYIXlcpybRqfhwcsl?p=preview. This is probably more a question of understanding how Angular works.

As of the current version (please don't refer or use to 2.0.0 anymore as it is very old now), you can use it in the directive (your second example) this way:


Stops working as assistant app

I think coffee is causing the bug because I haven't ran into it while using other assistant apps. Please let me know if there's a logged event you'd be looking for to reproduce the bug. The bug occurs after couple of hours of being set as the default assistant app.
Steps to reproduce the behavior:

Select as default assistant app.
Use gestures to activate/deactivate coffee.
Works initially, indicated by toast & notification.
Assistant gesture still flashes the screen but toast & notification don't occur.
Only way to get coffee to work as assistant again is to deselect/reselect it as default assistant app.

Additional context

Device: Lineage OS
Android version: 13

Is result code -92 expected? Checking the logs when it doesn't launch properly yields the following:
ActivityTaskManager(1748): START u0 {act=android.intent.action.ASSIST flg=0x10000000 cmp=com.github.muellerma.coffee/.InteractionService (has extras)} with LAUNCH_MULTIPLE from uid 10361 result code=-92

I'm able to reproduce the bug whenever I restart my device (without the arbitrary wait time). If coffee is set as assistant it never works via assistant calls upon restart. Only way to make it work as assistant app again is setting assistant to another app/none, then setting it as coffee again.

When I implemented this feature I didn't find a lot of documentation for this. It worked on my device, but after an update it didn't work at all. I didn't spend a lot of time in fixing it, but I'd review PRs improving the situation.


Fixed #12 and #9, added tests

I kinda missed pattern expansion in one place which certainly broke stuff. Sorry again. This would not have happened if there were tests, so I took the liberty of adding very basic suite.
Also note that process now replaces exposed exports.assets.

I just tested this, while 1.2.0 (a la #9) broke, this works fine. Great work adding some tests!

Thanks @inca !


[SPARK-41339][SQL] Close and recreate RocksDB write batch instead of just clearing

What changes were proposed in this pull request?

Instead of just calling writeBatch.clear, close the write batch and recreate it.
Why are the changes needed?

A RocksDB WriteBatch (and by extension WriteBatchWithIndex) stores its underlying data in a std::string. Why? I'm not sure. But after a partition is finished, writeBatch.clear() is called (somewhat indirectly through a call to store.abort), presumably clearing the data in the WriteBatch. This calls std::string::clear followed by std::string::resize underneath the hood. However, neither of these two things actually reclaims native memory. All the memory allocated for expanding the string when adding data to the WriteBatch will be there until the std::string is deallocated, which in this case means deleting the WriteBatch. This leads to native memory accumulation on an executor and it executes several partitions consecutively, which would happen when your total executor cores is less than your shuffle partitions for your stateful stream. So instead of just calling writeBatch.clear(), close the WriteBatch and create a new one to free up the native memory.
Does this PR introduce any user-facing change?

Fix for excess native memory usage.
How was this patch tested?

Existing UTs, not sure how to test for memory usage.

Nice finding! Looks like your explanation makes sense. I've quickly googled and there is reserve which may shrink the memory as desired but doesn't seem to be guaranteed. (And it's something we have to fix the code in RocksDB which they may have their own valid reason to do so.) So I agree this is the best approach we can do, and the fix is straightforward.
Just a couple of questions:

Have you run the fix with your production workload for a while and see there is no longer the same memory issue?
Did https://github.com/apache/spark/commit/b8b1fbc21c66348d25be3404d3f61099f2a7a9b5 help to figure out the "sort of leaking" memory, or did it report simply the resized memory size and didn't disclose the memory issue?

Otherwise the fix itself looks OK to me.

One question I did have, as I started digging into this I thought the problem was simply related to https://issues.apache.org/jira/browse/SPARK-38277, but as I dug into it I realized that writeBatch.clear is called, but by a task completion listener that calls store.abort here. I wasn't sure if this was intentional or not, seems like a slightly awkward way to clear things after a partition completes. If it was intentional that issue can probably be closed.

It's not intended. It looks like we missed to deal with ticket. Anyway we clear the writebatch before starting a new task for next microbatch, but I see issue when an executor handles multiple tasks for stateful operation.

Just to give you more context for your previous comment (https://github.com/apache/spark/pull/38853#issuecomment-1333073885)...
We have two different set of code path, 1) two physical nodes for one stateful operator (streaming aggregation) 2) one physical node for one stateful operator (others). For the latter, it only initializes read-write state store, and at the task completion, it only calls abort if the task failed to do commit. For the former, it initializes read only state store as well, which we call abort at the task completion to clean up the resource (NOTE: not to rollback as this is read-only. The name is unfortunately due to compatibility issue during the addition of new interface. See https://github.com/apache/spark/commit/21413b7dd4e19f725b21b92cddfbe73d1b381a05).
It is safe for read-only state store to call abort() even there is another read-write store referring the same, because read-write store would have completed to call commit() if the task works correctly and we expect (effectively) no-op from calling abort() after commit().

Thanks! Merging to master/3.3. (SPARK-38277 can/should be handled separately.)

(@Kimahriman Looks like your git is not correctly set in your dev. I manually changed the author of commit based on your mail address in dev@ mailing list.)

(@Kimahriman Looks like your git is not correctly set in your dev. I manually changed the author of commit based on your mail address in dev@ mailing list.)

Thanks, I did this on a new machine and forgot I haven't set that up yet.

Just to give you more context for your previous comment (#38853 (comment))...
We have two different set of code path, 1) two physical nodes for one stateful operator (streaming aggregation) 2) one physical node for one stateful operator (others). For the latter, it only initializes read-write state store, and at the task completion, it only calls abort if the task failed to do commit. For the former, it initializes read only state store as well, which we call abort at the task completion to clean up the resource (NOTE: not to rollback as this is read-only. The name is unfortunately due to compatibility issue during the addition of new interface. See 21413b7).
It is safe for read-only state store to call abort() even there is another read-write store referring the same, because read-write store would have completed to call commit() if the task works correctly and we expect (effectively) no-op from calling abort() after commit().

So the abort is there to basically make sure any writes to the read only state store get reverted unless a downstream read-write instance has already committed changes. I know there are a few different code paths for stateful things (sessions, flatmapgroupswithstate, etc), do we know if that abort call covers all the cases for https://issues.apache.org/jira/browse/SPARK-38277? Or do some of the other code paths not end up using that read-only path at all? Or would it be better just do explicitly clear the write batch anyway even if it is redundant with the abort call?


Typo Correction - "broad lineage" to "broad_lineage" in Dataset

There is a typo in the Curated_data_KG_Mo_Group - KG.csv file, where the term "broad lineage" should be corrected to "broad_lineage" for consistency.
Affected Datasets

snRNA-seq data for human cerebella - developmental stages 9-12
snRNA-seq data for mouse cerebella - developmental stages 9-12

Steps to Resolve

Locate instances of "broad lineage" in the specified datasets within Curated_data_KG_Mo_Group - KG.csv.
Replace "broad lineage" with "broad_lineage" to maintain naming consistency.

Expected Outcome
All references to "broad lineage" in the mentioned datasets should be updated to "broad_lineage." cc @dosumis

Fixed with #41


Traffic stats

WireGuard should show the statistics for the traffic going through it's tunnels.

Would be great to show the last handshake time and ports too, like the wg command does.

Finally fixed with 36d7c13ab17f650ed0060e9de42c804be0f0165b


query command overhaul

cleared up serverinfo and hostinfo mixup
some parameters where attached to the wrong argument eg. connection_packets_* parameter, which are not part of the hostinfo output
instanceinfo

add ServerQueryMaxConnectionsPerIP

hostinfo

add InstanceUptime
add HostTimestamp
add VirtualServersRunning

serverinfo

order parameters

add connection_packets parameter to serverinfo group
add connection_bytes parameter to serverinfo group

add new mockserver values

I really dont know why the first test results in
server_cmds.go:62:13: struct of size 880 bytes could be of size 856 bytes (maligned)

Your issue is the ordering of the fields, which means the struct is taking more space than it should.
This is caused by small types such as float32, bool etc.
You can download my pr from https://github.com/tyranron/golang-sizeof.tips/pull/7 and run it locally which will allow you to visualise the issue.

My last commit wasn't actually meant to fix the issue but fix an inherent issue. Those types I changed aren't actually booleans but integers.
Fixing the ordering issue is my next todo on the list.

Would someone mind to review this?

@stevenh would you mind to review my changes?

I just noticed that the serverrequestconnectioninfo call was the incorrect call to retrieve the listed values. throughout the code the call hostinfo is used but not actually used.


want to ask you a problem

I have used Phpmyadmin created a database named quiz_new. Quiz_new imports the database.After that, I  open the browser and type "http://localhost/Online_exam_New/",but it is wrong.
Please contact me with<EMAIL_ADDRESS>

database name should be project1


Add keptn/spec version to metadata of Keptn CloudEvents

CloudEvents must contain the keptn/spec version implemented by the shipyard-controller. The shipyard-controller needs to be configured with the keptn/spec version, e.g., in an environment variable the version is set. The shipyard-controller then sends out the events with the keptn/spec version.
Use case requirement: Someone who is developing an integration knows exactly the keptn/spec version that is processed.
Example:
{
  "datacontenttype": "application/json",
  "id": "c4d3a334-6cb9-4e8c-a372-7e0b45942f53",
  "source": "source-service",
  "specversion": "1.0",
  "keptnspecversion": "0.2.0-alpha",
  "type": "sh.keptn.event.approval.triggered",
  "data": {
    "project": "sockshop",
    "stage": "dev",
    "service": "carts",
    "labels": {
      "label-key": "label-value"
    },
    "status": "succeeded",
    "result": "pass",
    "message": "a message"
  }
}

Tasks:

Add the property keptnspecversion to the meta-data of a CloudEvent in keptn/spec.
Add an automation step that takes the last released keptn/spec version and defines it for the shipyard-controller
The shipyard-controller sends out triggered events containing the keptnspecversion
go-utils functions that create the started/finished events based on the triggered event consider this new property; this is related to: https://github.com/keptn/keptn/issues/2913
Out-of-scope: The API does not validate whether a started/triggered contains the keptnspecversion.

Change keptnspecversion to shkeptnspecversion.

Change keptnspecversion to shkeptnspecversion.


Updated 'Spanish Argentina' translation.

Thanks again @leomartinez, Will merge in now for next patch release.


Implement IDisposable for repositories

Issue may not be relevant. See post below:
https://stackoverflow.com/questions/30283564/dependency-injection-and-idisposable/30287923#30287923

Currently on hold, likely not something that needs to be implemented


Deep branch new

Updates in packages and code

it is working for me, but it would be good if someone else also runs it and installs the dependencies from the environment_idigest.yml file so as to make sure that all our versions are consistent


imgix middleman support

I love all the helpers imgix provides in rails, but when I want to use imgix in middleman I have no idea how to get it to work.
Any suggestions?

Closing as this issue is old but I'll also link this here for anyone curious: https://github.com/bigcartel/middleman-imgix/


Start job time sometimes incorrect after update-pipeline

I have noticed on minikube that pachctl update-pipeline will occasionally start jobs with a STARTED in the past, e.g.
c88ebd0d-b644-4493-9472-3912c6c6903c pipe/-   13 minutes ago -                  0       0 + 0 / 8   0B       0B       running

In this case, 13 minutes ago was actually a few seconds

I'm not sure if this is fixable; it's presumably due to clock drift in the minikube VM

As long as its a minikube or deploy local problem only, I'm not worried about it.


CSS injection order when using MUI as a component library

On the latest V5 alpha, styling components works great with emotion and the css prop. I'm able to have all the desired behavior in the same repo in the component lib (e.g. testing on storybook).
However, once I use that component lib as a dependency in another application, the CSS injection order changes and my custom styles are overridden. The head tag ends up looking like this:
// The inject first tag
<style data-styled="active" .... />

// My overrides in component lib
<style data-emotion="css"  data-s/>

// Other MaterialUI styles, default theme, customized theme via createMuiTheme, etc.
<style data-emotion="css" />

Note that this appears to be specific to using the css prop via emotion. If I switch to using sx, things work OK. I was trying to avoid using SX since the docs had mentioned it has worse performance, but it also didn't have a direct comparison to the css prop. I'm assuming (css ~ styled) > sx though given the performance discussions in some other threads. I'd be curious to know if I'm super wrong there too!
Thank you for taking a look!

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
My overridden styles in the component library no longer apply when the library is used in a dependent application.

Expected Behavior 🤔
The overridden styles should apply.

Steps to Reproduce 🕹
Component lib
import { Button } from '@material-ui/core';
import { FunctionComponent } from 'react';

export const FancyButton: FunctionComponent = ({ children }) => {
  return (
    <Button
      css={{
        background: 'red',
      }}
    >
      {children}
    </Button>
  );
};

Application lib
import {FancyButton} from 'fancy-ui-lib'

export const MyApp: FunctionComponent = () => {
  // Does not have a red background
  return <FancyButton />
}

Workarounds
I've found that wrapping the material component in another div and increasing specificity works, but I don't think this is too ideal:
export const FancyButton2: FunctionComponent = ({ children }) => {
  return (
    <div
      css={{
        '& .fancy-button-2': {
          background: 'red',
        },
      }}
    >
      <Button className="fancy-button-2">{children}</Button>
    </div>
  );
};

Similar specificity hack:
export const FancyButton2: FunctionComponent = ({ children }) => {
  return (
    <div
      css={{
        'button&': {
          background: 'red',
        },
      }}
    >
      <Button className="fancy-button-2">{children}</Button>
    </div>
  );
};

I found the culprit of the problem by accident. I have a ThemeProvider wrapper in my component library that looks something like below. The extra div that was wrapping the children with some emotion css, when removed, allowed the injection order to be correct again.
<ThemeProvider theme={themeOptions}>
    // Using Global from @emotion/react
    <GlobalStyles />
    // Removing this div solved it
    <div
        css={{
            width: '100%',
            height: '100%',
        }}
    >
        {children}
    </div>
</ThemeProvider>

Anyone know why that is? Thanks!

Without a reproduction, we can't debug your issue.

I was trying to avoid using SX since the docs had mentioned it has worse performance, but it also didn't have a direct comparison to the css prop. I'm assuming (css ~ styled) > sx though given the performance discussions in some other threads. I'd be curious to know if I'm super wrong there too!

This is interesting! I'm going to add, at the very least, a benchmark to see where we are. We also know that we can rewrite the system to be faster. I might also look at it, once I get bandwidth, maybe this weekend.

I found the culprit of the problem by accident.

I take this back, it may been fleeting... will have to continue to debug.
I'll try to setup a minimal reproducer and get back. Thanks!

I created a minimal setup, but it didn't end up reproducing 😢 . I'll go ahead and close this for now since I'm unable to uncover the proper reason. I'm sure it's something else convoluted in my setup. I'll re-open if I find out more.


remove warning from upstream websocket docs

talked to michael martin
Description

Testing instructions
Preview link:
Checklist

[ ] Review label added
[ ] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

I am combining this with #6477


Generate API review file and publish as artifact

Add new step in build pipeline to create API review code file and publish it as artifact. This will be used by APIView to create review.

@praveenkuttappan is this ready to go? Where can I find examples of the generated APIViews? Should it be adding a link in the PR?


Second calendar appears below first calendar when used with bootstrap-vue.

When I use this plugin inside bootstrap-vue (https://bootstrap-vue.js.org/) in range mode:
<vue-datepicker-local v-model="range"></vue-datepicker-local>
the second calendar appears below the first one, instead of to the right of it.
It appears that .datepicker-popup has a width of 403px, which is too narrow for 2 .calendar side by side.
I think some style might be messed up by bootstrap-vue.
Thanks in advance!

you should use style to fix it, thanks


In SCENE2D mode, how to remove the black edge of the map?

Sorry, I can't access https://community.cesium.com, so I'm asking here.
In SCENE2D mode, How to remove the black edges(shown in the following screenshot) or limit the camera to see only the region of the earth?
I tried to write an example, which seems to solve the problem, but when the camera is very far away from the ground, the map will shake.
const viewer = new Cesium.Viewer("cesiumContainer", {
  animation: false,
  baseLayerPicker: false,
  fullscreenButton: false,
  geocoder: false,
  homeButton: false,
  infoBox: false,
  timeline: false,
  navigationHelpButton: false,
  sceneMode: Cesium.SceneMode.SCENE2D
});

if (viewer.scene.mode === Cesium.SceneMode.SCENE2D) {
  viewer.scene.preUpdate.addEventListener(scene => {
    const maxCoord = scene.mapProjection.project(
      new Cesium.Cartographic(Math.PI, Cesium.Math.PI_OVER_TWO)
    );

    const camera = scene.camera;
    const frustum = camera.frustum;

    const minX = -maxCoord.x - frustum.left;
    const maxX = maxCoord.x - frustum.right;

    const minY = -maxCoord.y - frustum.bottom;
    const maxY = maxCoord.y - frustum.top;

    camera.position.x = Cesium.Math.clamp(camera.position.x, minX, maxX);
    camera.position.y = Cesium.Math.clamp(camera.position.y, minY, maxY);
  });
}

Thank you for sharing the Sandcastle! I can't reproduce the shaking issue when I try to zoom out all the way. Can you post a video of the behavior or explain the detail steps to reproducing the shaking issue?

Thank you for sharing the Sandcastle! I can't reproduce the shaking issue when I try to zoom out all the way. Can you post a video of the behavior or explain the detail steps to reproducing the shaking issue?

You can't reproduce the shaking issue, maybe because the browser and the operating system are different?
I added the following code to the new example, and after three seconds you can see the map shaking up and down.
setTimeout(() => {
  viewer.camera.zoomOut(10000 * 100000)
}, 3000)

Environment:
os: Windows 10
browser: Google Chrome 89.0.4389.114

Did you find a solution? I'm also having the same issue.

Maybe change this line , can  solve the shake issue  camera.position.y = Cesium.Math.clamp(minY, minY, maxY);


Add the 'newsyslog' gem to Azure OMS Agent (fluentd) crashes the agent

Hi All,
I have installed the OMS Linux Agent in order to send syslog messages to OMS.
I'm using a version which is based on ruby 2.3 (No yet published)
The aim is to use the 'newsyslog' input type which solves some limitations encountered with the 'syslog' input type
I have installed the newsyslog gem using this command :
./fluent-gem install fluent-plugin-newsyslog
The installation was successful
The following is my omsagent.conf file (which uses the same fluentd syntax)

  type newsyslog
 # format none
  port 20514
  bind <IP_ADDRESS>
  protocol_type udp
  tag oms.networkdevices

When restarting the OMS Agent, i encountered the following error : ( service omsagent status -l)
.
I also noticed that the in_newsyslog.rb is not located under "/opt/microsoft/omsagent/ruby/lib/ruby/gems/2.3.0/gems/fluentd-0.12.24/lib/fluent/plugin/" where all the rb files were supposed to be located.
Fluentd version : fluentd-0.12.24
OS : Centos 7.3
What do you think that is missing ?
Thanks

I think that the best to help me is @repeatedly (if he can)

Maybe, this is the cause: https://github.com/athenahealth/fluent-plugin-newsyslog/pull/3

I checked newsyslog plugin code and the main difference is supporting rfc5424 format.
in_syslog with newsyslog rfc5424 regexp format seems to realize same thing.

Thanks repeatedly. So what m'i supposed to do please. Use the time_format with the appropriate regexp ?
Can i use multiple time formats and use the 'OR' (|) statement on the regexp ? Do you think it's supported.
If this will cover my needs, i will wait for the final OMS agent with the newsyslog format and the right documentation.

Can i use multiple time formats and use the 'OR' (|) statement on the regexp ? Do you think it's supported.

This is hard for now. BTW, if your case is in_syslog receives rfc3614 and rfc5424 formats at the same time, supporting it in in_syslog is good idea.

Hi Masahiro,
Thanks for your support. What do you mean by "supporting it in in_syslog is good idea" ?
The goal is to support different equipments using different rfc implementations (rfc3614 and rfc5424 formats) which is not native with fluentD. Can you point me to any documentation that allow me properly configure it ?
Infinite thanks

What do you mean by "supporting it in in_syslog is good idea" ?

It means adding feature to handle both spec to in_syslog.

I think that the in_newsyslog and parser_newsyslog is doiing this ? Am i right ?

We just merged this patch: https://github.com/fluent/fluentd/pull/1492
This can accept RFC3614 and RFC5424 formats in one source.
Is it enough?
Do you want to use different time format in RFC3614 message?

v0.12.33 includes #1492 features.
Could you check this is enough or not?
#1492 seems to cover newsyslog plugin feature.

Hi,
Thanks for pointing me out to this. I'm currently testing it. Will report back here.


Can't see any history tags with basic implementation ?

Hey,
I just implemented basic configuration as follow:

[...]
const {init} = useGTM();

useEffect(() => {
  init({id: environment.gtmId});
}, [init])

We are tracking History API of the browser for SPA. But can't see any tags of my pages!
Do i miss something ?

Hi,
the History Change trigger is configured on your GTM?
Will do some test and check into this.

Hi @elgorditosalsero
Yep, i already did the configuration. When using react-gtm-module, it works fine but with this module it does not show anything.
Thanks.

Hi @hiahmedhameed,
I've done some tests and you're right, I'm 👀  into this.
And next weeks I, probably, do a refactor to the hook 🎉

Hi @hiahmedhameed,
I've done some tests and you're right, I'm 👀  into this.
And next weeks I, probably, will do some refactor to the hook 🎉

Hi @hiahmedhameed,
I've done some tests and you're right, I'm 👀 into this.
And next weeks I, probably, will do some refactor to the hook 🎉

Hi @hiahmedhameed
with the latest release, I've fixed the issue of the history navigation.
You could see also a live example here
Try to update the hook and follow the new snippets.
Let me know 💯

I'm closing the issue due to inactivity.
@hiahmedhameed feel free to reopen if you still have the issue with version 2.x.


Mark silencer-lib as Provided to prevent conflicts.

The silencer-lib has been pulled in to dependent projects and caused conflicts in projects using another version of silencer.
To mitigate the problem, silencer has been updated to current version and the silencer-lib dependency changed to Provided, in accord with the current usage description at https://github.com/ghik/silencer#setup .

@mprihoda thanks a lot for the PR. I can see the format check doesn't pass. Running format in sbt will fix the problem.

@mprihoda I included your changes in the latest release. It's propagating now. Thanks a lot for the finding. I think this can be closed.

@mprihoda thanks a lot for the PR. I can see the format check doesn't pass. Running format in sbt will fix the problem.

Glad to help and sorry for not reacting to the format issue, the Github notifications skipped my inbox.

No worries, thanks again. Kudos to you for the fix. 👍


Deleted Notebooks remain open in the editor

Environment data

VS Code version: 1.52.1
Extension version (available under the Extensions sidebar): v2021.1.502429796
OS and version: Ubuntu 20.04

Expected behaviour
Consistency when deleting files. When you delete any file in the explorer, the file is removed from the editor window.
Actual behaviour
If you delete an ipynb file in the explorer, the notebook remains open. This makes it really easy to accidentally edit the deleted file (or even run a cell) which results in it being recreated.
Steps to reproduce:

Open a notebook
Delete the file in explorer

This also occurs with rename, if I rename an ipynb, I end up with two open copies of the same ipynb.


Update Meeting functionalities

In this PR

Added AddMeetingCommand class
Added AddMeetingCommandParser class
Adjusted CliSyntax.java, ParserUtil.java, AddressBook.java, Model.java, ModelManager.java and ReadOnlyAddressBook.java to support newly implemented Meeting functionalities.
UniqueMeetingList added to AddressBook
DateTime formatting for user input

To be added: Delete functionalities for Meeting

Codecov Report

Merging #86 (fbdb5d5) into master (64c0851) will decrease coverage by 0.56%.
The diff coverage is 8.47%.

@@             Coverage Diff              @@
##             master      #86      +/-   ##
============================================
- Coverage     41.74%   41.18%   -0.57%
- Complexity      413      416       +3
============================================
  Files           116      118       +2
  Lines          2247     2302      +55
  Branches        287      292       +5
============================================
+ Hits            938      948      +10
- Misses         1254     1298      +44
- Partials         55       56       +1

Impacted Files
Coverage Δ

...eedu/address/logic/commands/AddMeetingCommand.java
0.00% <0.00%> (ø)

.../address/logic/parser/AddMeetingCommandParser.java
0.00% <0.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
66.03% <0.00%> (-10.05%)
:arrow_down:

...main/java/seedu/address/model/meeting/Meeting.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
44.14% <7.14%> (-4.84%)
:arrow_down:

src/main/java/seedu/address/model/AddressBook.java
49.41% <22.22%> (-3.22%)
:arrow_down:

...ain/java/seedu/address/logic/parser/CliSyntax.java
92.30% <100.00%> (+0.64%)
:arrow_up:

src/main/java/seedu/address/model/Model.java
100.00% <100.00%> (ø)

...seedu/address/model/meeting/UniqueMeetingList.java
10.41% <0.00%> (+10.41%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


DLL missing

The required DLL was not in the downloaded .zip file.

What dll? the DLL is a separate file on the release page?

Beats me but it wasn't included in the downloaded file. I already found another Autostart plugin elesewhere.


Quicksilver randomly stops running Applescripts on triggers

I'm at a company and we've had about 25 people using Quicksilver to run scripts off key commands for a couple of years. Just in the past few days, a whole bunch of us have had scripts (randomly as far as we can tell) not run sometimes off the key command. I've tried opening the script being called, modifying it to make the first line be:
tell application Finder to display dialog "Made it here"
and confirm that it's not a problem with any individual scripts, they are not being run. That is, if I open the same script in Script Editor, and press run, it runs fine, but even making the script just display a dialog first thing, it doesn't even make it there when being run from Quicksilver.
When this happens, that particular script/keybinding continues to fail until Quicksilver is quit, but quitting and relaunching Quicksilver always makes it work again. Until it stop at some random time... in minutes or in hours... and we have to quit and relaunch again.
When one trigger quits functioning, other triggers that also run Applescripts often continue to function fine... any random subset of triggers can go out together while others still work.
At our wits end... may need to look at another solution. Let me know if anyone has any ideas or tests I can run.
Thanks,
Tom.

FYI, I've talked to Quicksilver developers before about a way to share/sync Quicksilver preferences files through Dropbox, but we never got that working and none of us are on it. I'm not aware of any way we're an unusual setup here, other than having a lot of Applescripts on triggers.

In a lot of cases, AppleScripts can go wrong because a key (from the trigger) is still being held when it’s run. You can usually work around that by having the trigger run “On Release” instead of “On Press”.
That wouldn’t explain it working after a restart, though, so I suspect something else is going on here. It cold be related to something recently reported on the mailing list.
Are there any messages on the console (/Applications/Utilities/Console.app) that might offer a clue?

Could be related... I do have one script where one step of the script sometimes fails - telling Adobe Photoshop to save a file - when run from Quicksilver, but that step never fails when run from Applescript Editor or from Script Debugger, so it's been very hard to troubleshoot. But I haven't considered that to be related.
Aha! Yes, thanks for suggesting I look at Console, I should have thought of that earlier. It's getting a permissions error:
2/26/15 1:24:59.445 PM Finder[40079]: AppleEvents/sandbox: Returning errAEPrivilegeError/-10004 and denying dispatch of event syso/offs from process 'Quicksilver'/0x0-0x2398396, pid=87107, because it is not entitled to send an AppleEvent to this process.
So why isn't Quicksilver allowed to send these Apple events? And why does the exact same script work most of the time, then quit, and start working again if we restart quicksilver? Just in case, I'll repair permissions and see if that does anything. Thanks! Let me know if this gives you any insight.

Drat, repaired permissions, to no avail.

From a quick Googling around, it seems we have to add com.apple.security.temporary-exception.apple-events" to QS's entitlements so sandboxd allows it to fire AppleEvents at any other process.

I wonder what on earth is going on that sometimes it has the appropriate permissions, and other times it gets stopped? It's always the exact same script on the same key. Also, until a few days ago, it always worked.
Any thoughts on how long it would take to have that added? Going nuts over here... but we could investigate temporarily binding the scripts to a key command through some other mechanism until Quicksilver has this entitlement.

And so incidentally, my first summing up the problem is incorrect, Quicksilver is trying to run the script. But my attempt to see if it was trying or not by making the first line have the Finder display a dialog was a bad choice to see if it's trying to run, because the problem is that the OS isn't letting Quicksilver tell the Finder to do things!

Oh, and skurfer, thanks for the suggestion re: "on press" vs "on release," but we've always had all the Applescripts set to "on release" due to that very problem.

You say it worked "a few days ago". Was some kind of OS update involved at that same time ?
I'm concerned about the on-off description you're painted us — it looks like the sandbox somehow gets activated after some unspecified amount time, which is weird.
Were all of your triggers affected at some point ? Do they share some common structure (e.g. going through System Events to send keypresses) ? Can you post one of the real Console logs in case they're any difference ?

Also, since we're not actually using the sandbox, we have no entitlements. Adding support for sandboxing would be very hard, given the breadth of things you can do with QS. To me this starts looking like a bug in sandboxd, which shouldn't enforce anything on us...

No, no OS update. Most of the people in this room started experiencing it at the same time, and some of us are on 10.9 and some on 10.10, and different versions of those, and we certainly didn't all install an OS update when it started. I can't think of anything the people having the problem could have all installed.
So, report this as a bug to Apple, because Quicksilver isn't supposed to be subject to Sandboxing restrictions?

I don't think all triggers have been effected, but several have.
How do you mean the "real" console logs? There's no line that regularly proceeds the one I sent, and the next one is just Applescript complaining that it didn't get the information it wanted, and then it's back to just whatever unrelated thing happens to show up next. I'm attaching the "Inspector" graphic on the issue from the log, let me know if you need something else.

OK, we're trying out FastScripts now as an alternative. Seems to be working so far.
You guys think I should file a bug report with Apple over this? Or do you want to file it? I probably has more weight coming from a developer. Let me know anything else you need.
Thanks,
Tom.

Let's both file a bug then, it'll have more "weight" ;-). I'll do that tomorrow, it's getting late here, but please tell me the rdar number so I can dup yours.
I haven't been able to reproduce here, but I can give you some hacky steps I tried ;-) :
AppleEvents are handled by /System/Library/CoreServices/appleeventsd, which has a few parameters (found thanks to strings), notably --nosandbox. What I tried was editing /System/Library/LaunchDaemons/com.apple.coreservices.appleeventsd.plist, adding that parameter to the list of arguments and unload/load it with sudo launchctl so it gets passed in. I haven't been able to see any difference (but it was working here :-S). Maybe you can get different results on your side ?
I'm on 10.9.5 here BTW.

I'm not sure I'm comfortable with all that.

I open /System/Library/LaunchDaemons/com.apple.coreservices.appleeventsd.plist with a text editor or such and add the argument "--nosandbox"
I go to terminal and enter "sudo launchctl" and enter my password?

First problem: this file:
/System/Library/LaunchDaemons/com.apple.coreservices.appleeventsd.plist
Doesn't exist.
I'm on 10.9.5 too.

Bug report filed - 19978459


Integral normalized PSF for dirty image

Is it possible to add this functionality? A work around is welcome too. I am looking at pure diffuse signal, and peak normalization makes it hard to compare the output and the input as total flux is not preserved.

Set the existing keyword conserve_flux=1 to use integral normalization instead of peak normalization for restored images.

This does not seem to work with my run. Here is my run script.
PRO run_fhd_v1

version=1
except=2

data_directory = '/data4/piyanat/fhd_images/eor0_0000h/test/grid_of_point_sources'
output_directory = '/data4/piyanat/fhd_images/eor0_0000h/test/grid_of_point_sources'
vis_file_list=file_search(data_directory,'diffuse.uvfits',count=n_files)
fhd_file_list=fhd_path_setup(vis_file_list,version=version, output_directory=output_directory)
healpix_path=fhd_path_setup(output_dir=output_directory,subdir='healpix',output_filename='Combined_obs',version=version)

; Gridding options
no_frequency_flagging=1
calibrate_visibilities=0
dimension=2048
pad_uv_image=2.
precess=0 ;set to 1 ONLY for X16 PXX scans (i.e. Drift_X16.pro)
FoV=120.
deconvolve=0
mapfn_recalculate=0
grid_recalculate=0

; Imaging options
export_images=1
ps_export=0
no_ps=1 ;don't save postscript copy of images
combine_healpix=0
image_filter_fn='filter_uv_natural'
conserve_flux=1

; Other options
cleanup=0

general_obs,cleanup=cleanup,ps_export=ps_export,$
    recalculate_all=recalculate_all,export_images=export_images,$
    version=version,beam_recalculate=beam_recalculate,$
    healpix_recalculate=healpix_recalculate,$
    mapfn_recalculate=mapfn_recalculate,grid=grid,deconvolve=deconvolve,$
    image_filter_fn=image_filter_fn,data_directory=data_directory,$
    vis_file_list=vis_file_list,fhd_file_list=fhd_file_list,$
    healpix_path=healpix_path,catalog_file_path=catalog_file_path,$
    dimension=dimension,max_sources=max_sources,pad_uv_image=pad_uv_image,$
    precess=precess,psf_dim=psf_dim,complex_beam=complex_beam,$
    double_precison_beam=double_precison_beam,FoV=FoV,no_ps=no_ps,$
    no_frequency_flagging=no_frequency_flagging,min_baseline=min_baseline,$
    calibrate_visibilities=calibrate_visibilities,conserve_flux=conserve_flux,$
    combine_healpix=combine_healpix,_Extra=extra,$
    !except=except

END

Setting conserve_flux=1 does not seem to change the normalization. I only have Beam_XX, Beam_YY, UV_weights_XX, UV_weights_YY, Dirty_XX, Dirty_YY, Dirty_I and Dirty_Q in output_data/. Looking at the code, this keyword only exist in source_image_generate.pro. I am not sure what that routine does.

Conserve_flux affects the normalization of restored images. which are "peak normalized." For all other images, the beam is normalized so that the sum is one, which should conserve flux.


Changing the default file extension of tsv files

Currently @export Test :- tsv{}. results in the creation of the new table Test.csv.
It would be more clear if the extension was .tsv

Looks like this got broken when moving the constants to syntax.rs:
https://github.com/knowsys/nemo/blob/379844dd7b279e2d37c4ea9afd0d0bc9dd71c6ef/nemo/src/syntax.rs#L390-L393


"not_allowed_token_type" error

I got it all to work perfectly. Then I made a new bot, created a new oAuth token, and now it doesn't work any more. I can't recall doing anything differently this time. Any idea of what might be wrong? I'm getting this:
slacksocket.errors.SlackAPIError: Error from slack api:
{"ok":false,"error":"not_allowed_token_type"}

Hey @MrOaiki, can you share your application code here?
Also, you mentioned a

new oAuth token

For clarity, we want to use a

API Token, The library you are using will want an API token for your bot.

Which you can generate from https://[your-slack-team].slack.com/apps/manage/custom-integrations

Closing due to lack of additional information. @MrOaiki feel free to comment or open a new issue!


:tada: strict YAML metadata schema validation

Light implementation of https://github.com/owid/etl/issues/2238.
The original issue suggests to

Add the $schema parameter and opt-in historical YAML files that are already compliant

In my opinion, adding a property to every YAML file would add too much boilerplate code. I'm not sure if we need such a granular approach. Similarly with versioning metadata schema. I don't think we have to check every metadata file at each point in time. If we always have a green CI, then bump the version in VALIDATE_AFTER, update schema and have green again, then it's sufficient. (Especially since we have linting enabled)
I fixed a couple of datasets, but added some to EXCLUDE list. I've also disabled checking for description as it is present in too many datasets (we still get linting error for it).

Eventually it would be good to check all .meta.json files, but I suppose that may be more complicated.

It would, though, maybe not be as complicated. The question is how valuable it is to do a full check. Since the data goes through objects like Dataset or Variable, there's already some validation (also you have type hints). There are some special cases like description_key, but it might be enough to have a special runtime validation for them (such as the one we added recently). I'd start with YAML validation and wait if it's enough or not.


JTabbedPane Support

The Material LaF is very nice, but could you please add support for JTabbedPane? Would be nice, it's the only component which looks more or less terrible -> for my school project :)

Added support for it


matterbridge-zigbee2mqtt issue receiving invalid Z2M message

When matterbridge-zigbee2mqtt receives an invalid Z2M message as per issue reported (https://github.com/Luligu/zigbee2mqtt-automations/issues/5).
It ends up trying to convert the message to Matter and then fails.
[InteractionServer] Subscription 825015395 for Session 27795: Error while sending initial data reports The number NaN cannot be converted to a BigInt because it is not an integer
  at BigInt (<anonymous>)
  at toBigInt (file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/util/Number.js:25:38)
  at DataWriter.writeInt64 (file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/util/DataWriter.js:57:53)
  at TlvCodec.writeUInt (file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/tlv/TlvCodec.js:375:23)
  at TlvCodec.writePrimitive (file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/tlv/TlvCodec.js:301:21)
  at TlvByteArrayWriter.writePrimitive (file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/tlv/TlvSchema.js:70:14)
  at file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/tlv/TlvAny.js:57:18
  at Array.forEach (<anonymous>)
  at AnySchema.encodeTlvInternal (file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/tlv/TlvAny.js:37:15)
  at file:///usr/local/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/tlv/TlvArray.js:25:51

This repeats 3 times, after which the controller is unsubscribed:
[SubscriptionHandler] Sending update failed 3 times in a row, canceling subscription 825015377 and let controller subscribe again.

Either this requires a manual MatterBridge addon restart or some amount of time for the devices to be available again on Matter.

Hi,
I need a full log to understand where to put a filter in the plugin to filter wrong values that can come from anywhere.
Subscribe again is the typical controller behaviour... after a while the controller subscribe again.


Updates to registration page

Refactoring + added explanation for tenant linking

Docs Build status updates of commit d50bc67:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

MicrosoftCollaboratePortal/registration.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add FL, PF, SD, Wind Up, Wind Down

This PR adds 5 mods, Flashlight, Perfect, Sudden Death, Wind Up, and Wind Down.

Flashlight - larger size than other modes (to cover two lanes) and gets smaller when >100 combos and >200 combos.
Perfect, Sudden Death, Wind Up, and Wind Down has the same effect as other modes.

Flashlight size/location:

Videos
Flashlight: https://www.youtube.com/watch?v=X1I1C3IMEPc
Wind Up: https://www.youtube.com/watch?v=oNAT1dYG3g8

I’m assuming flashlight is essentially the same as “sudden” in DDR/IIDX/etc.

Should I rename the flashlight mod? I am not familiar with like DDR/IIDX.

Should I rename the flashlight mod? I am not familiar with like DDR/IIDX.

Flashlight is probably okay for now, it serves the same purpose.

Also, next time you wish to contribute, please PR from another branch other than your master branch to keep reviewing simple for us during checking out.

Also, next time you wish to contribute, please PR from another branch other than your master branch to keep reviewing simple for us during checking out.
My bad, sorry about that!

Needs conflict resolution

I guess it should be ok now

Please do not force push if you can help it, it destroys any history and makes it harder to review.


python version

Since not all the packages in requirements.txt are compatible with the latest python version, you need to provide information on the version used in the environment fcf.
conda create -n fcf python=your version

Thanks for reporting this Terry. I just created new requirements.txt and README files and tested them on my Mac. Please follow the new instructions and run the installation.


Create must be a static function

https://github.com/mathieuanthoine/haxe-gsap/blob/f875263387011ba504f724b0cbc05bcae01a988a/src/com/greensock/easing/CustomEase.hx#L13

Can you PR ?

A simple fix. Have made a PR. Thanks


Configurable columns

YARM is very wide, especially when fully expanded to show all the sites. It should be possible to configure only a subset of columns to be shown at a time (possibly also with presets?).
With #11, columns should be configurable separately per filter, so that, e.g., the "low resource remaining" filter will only show site name, percent remaining, and ETD, while the "all sites" filter can show all columns.

This will actually be in 1.0 at least partially -- we had a compact mode (YARM-toggle-lite) for a while but it's been refactored into actual (albeit fixed) column layouts. The step from there to making the columns configurable is not that far, although it will take a bit more to support the surface split correctly.


Pin exact wayland-client versions.

I recently tried to use the wayland feature, but it failed because it was pulling in incompatible versions of the various wayland packages. I think the underlying issue is that "0.3.0-beta.3" is not semver compatible with "0.3.0-beta.8", but cargo thinks it is. The fix is to pin the exact versions, and I also had to add an explicit dependency on wayland-scanner because otherwise it pulls in wayland-scanner-0.3.0-beta.8.

The wayland feature seems to be broken currently anyway, see #76

Ah, indeed! I guess the versions will still need to be pinned after that's sorted out, though.

They will, we are waiting for a 0.30 stable release first before merging than and backporting the fixes to 0.2

Sounds good! I'll go ahead and close this, then.


Deploy Multicall3 to Step network

Hi again :-),
Here are the info about the chain :
ChainID: 1234
Network Name: Step Network
RPC URL: https://rpc.step.network
Currency Symbol: FITFI
Block Explorer URL: https://stepscan.io/
I've transfered FITFI to the deployer account.

Done, thank you! https://stepscan.io/address/0xcA11bde05977b3631167028862bE2a173976CA11/contracts#address-tabs


Improve logic for showing/hiding the bottom bar

This PR greatly improves the logic for showing/hiding the bottom navigation bar for an overall better scrolling UX.
Before this PR, the bottom bar was hidden only when the user zoomed the document.
Now it behaves in the following way:

the bottom bar gets hidden as soon as the user starts scrolling (which includes zooming)
the user can show/hide the bottom bar with a single tap in any moment
the bottom bar becomes visible again when the user scrolls at the top of the document (this doesn't work when the scroll handle is used to scroll to the top, I couldn't figure out why)

You can see the new behavior in the video here: https://streamable.com/1mqc23
While I was it, I couldn't refrain from doing some clean-ups to MainActivity in order to take advantage of newer Java features. 😅
I kept clean-up commits very small, so it shouldn't be hard for you to review.

This is amazing, thanks for your work!

This is amazing, thanks for your work!


Validatewcuri fun parameter update

I noticed that in the latest validatewcuri method, you must pass the SymKey parameter, that is, the secretkey, but now the parameters of the QR code on the DAPP are all public keys. What should I do

Hey, to connect a wallet to a Dapp, both apps should support the same walletconnect version. Otherwise, there is no way to connect. To test wc-beta100 kotlin sdk, you can check our kotlin sample apps.

i got the same issue. I try to pair, but the sdk always returns an invalid wallet uri.
wallet uri i got from demo apps (https://react-app.walletconnect.com/)
wc:1e9a31fe8859bb33eb93cddb99ae2b1c19eaeb57a7c8f6aee8bf85918dcfd33c@2?relay-protocol=time&symKey=8456aa4af8c997edfea7fa8d266c473151548a37197f7c12524da807f7c12524da807
but code sdk WalletConnectKotlinV2:1.0.0-beta04 required publicKey, relay


feat(@ciscospark/sparkd): implement sparkd

This rebases https://github.com/ciscospark/spark-js-sdk/pull/605 and adds support for file sharing.

Closes #605


Fix current warnings

Thoses warnings are showned by CI and this is boring

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

Project coverage is 86.58%. Comparing base (87da423) to head (37324e3).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1230      +/-   ##
==========================================
+ Coverage   86.57%   86.58%   +0.01%
==========================================
  Files         176      176
  Lines       13049    13045       -4
==========================================
- Hits        11297    11295       -2
+ Misses       1752     1750       -2

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


"OSError: Could not find compatible tinycudann extension for compute capability 86"

Describe the bug
When I run the script ns-train nerfacto nuscenes-data --data-dir data/NuScenes --data scene-0061. I met the error below.
(nerfstudio) zizhang.wu@shaxbw03:/SHFP12/02_bevdet/nerfstudio$ sh train.sh
Traceback (most recent call last):
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/bin/ns-train", line 5, in <module>
    from scripts.train import entrypoint
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/scripts/train.py", line 50, in <module>
    from nerfstudio.configs.method_configs import AnnotatedBaseConfigUnion
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/nerfstudio/configs/method_configs.py", line 38, in <module>
    from nerfstudio.models.instant_ngp import InstantNGPModelConfig
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/nerfstudio/models/instant_ngp.py", line 38, in <module>
    from nerfstudio.field_components.field_heads import FieldHeadNames
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/nerfstudio/field_components/__init__.py", line 17, in <module>
    from .encodings import Encoding, ScalingAndOffset
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/nerfstudio/field_components/encodings.py", line 34, in <module>
    import tinycudann as tcnn
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/tinycudann/__init__.py", line 9, in <module>
    from tinycudann.modules import free_temporary_memory, NetworkWithInputEncoding, Network, Encoding
  File "/home/CN/zizhang.wu/anaconda3/envs/nerfstudio/lib/python3.8/site-packages/tinycudann/modules.py", line 35, in <module>
    raise EnvironmentError(f"Could not find compatible tinycudann extension for compute capability {system_compute_capability}.")
OSError: Could not find compatible tinycudann extension for compute capability 86.

same problem, have you solved it？

Same problem here; I would appreciate any guidance on the matter.

Try running pip list | grep torch
The torch version should be 1.12.1+cu113 or 1.12.1+cu116
If the +cu... is missing, then you need to reinstall pytorch with cuda support, ie
pip install torch==1.12.1+cu113 torchvision==0.13.1+cu113 -f https://download.pytorch.org/whl/torch_stable.html

I encountered a similar problem to this and #1283 #1189 as tcnn cannot find extension for compute capability 70. The short answer is to make sure tinycudann for your specific GPU/CUDA compute capability is correctly built so that you can run import tinycudann in python.
For me, the problem is that I have two GPUs of compute compatability 70 and 86. When I run
pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch
it automatically chooses my first GPU (86) as the compute capability to build. I can run if specifying only one GPU e.g. CUDA_VISIBLE_DEVICES=0 ns-train ..., but not the other.
To use the other GPU (70), I need to specify it and re-build tinycudann from source for that particular compatability.
tiny-cuda-nn$ cd bindings/torch
tiny-cuda-nn/bindings/torch$ CUDA_VISIBLE_DEVICES=1 python setup.py install

Closing, feel free to reopen if it is still and issue.

I encountered a similar problem to this and #1283 #1189 as tcnn cannot find extension for compute capability 70. The short answer is to make sure tinycudann for your specific GPU/CUDA compute capability is correctly built so that you can run import tinycudann in python.
For me, the problem is that I have two GPUs of compute compatability 70 and 86. When I run pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch it automatically chooses my first GPU (86) as the compute capability to build. I can run if specifying only one GPU e.g. CUDA_VISIBLE_DEVICES=0 ns-train ..., but not the other.
To use the other GPU (70), I need to specify it and re-build tinycudann from source for that particular compatability.
tiny-cuda-nn$ cd bindings/torch
tiny-cuda-nn/bindings/torch$ CUDA_VISIBLE_DEVICES=1 python setup.py install

You mean if I choose another GPU, then it will work correctly?

I encountered a similar problem to this and #1283 #1189 as tcnn cannot find extension for compute capability 70. The short answer is to make sure tinycudann for your specific GPU/CUDA compute capability is correctly built so that you can run import tinycudann in python.
For me, the problem is that I have two GPUs of compute compatability 70 and 86. When I run pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch it automatically chooses my first GPU (86) as the compute capability to build. I can run if specifying only one GPU e.g. CUDA_VISIBLE_DEVICES=0 ns-train ..., but not the other.
To use the other GPU (70), I need to specify it and re-build tinycudann from source for that particular compatability.
tiny-cuda-nn$ cd bindings/torch
tiny-cuda-nn/bindings/torch$ CUDA_VISIBLE_DEVICES=1 python setup.py install

It did work for me after I change another GPU, thx a lot


Passing the root workspace name as a package to --filter does not work as expected

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
https://github.com/dstaley/turborepo-root-filter
Which canary version will you have in your reproduction?
2.3.4-canary.2
Enviroment information
turbo 2.3.4-canary.2

CLI:
   Version: 2.3.4-canary.2
   Path to executable<EMAIL_ADDRESS>   Daemon status: Running
   Package manager: pnpm9

Platform:
   Architecture: aarch64
   Operating system: macos
   WSL: false
   Available memory (MB): 4167
   Available CPU cores: 12

Environment:
   CI: None
   Terminal (TERM): xterm-256color
   Terminal program (TERM_PROGRAM): vscode
   Terminal program version (TERM_PROGRAM_VERSION): 1.95.3
   Shell (SHELL): /bin/zsh
   stdin: false

Expected behavior
turbo-ignore correctly detects when the dependencies of a task defined for the root workspace have changed compared against the main branch, and reports that the //#test:integration task will be run.
Actual behavior
The following error occurs:
x No package found with name 'turborepo-root-filter' in workspace

To Reproduce

turbo-ignore --task test:integration --fallback main

Additional context
I believe passing the root workspace package name as // sort of works, but I'm not able to get it to correctly detect when a dependency has changed.
To reproduce that,

Make a new branch off of main
Make an edit to packages/package-b/src/build.js and commit it.
Run npx turbo run "test:integration" --filter="//...[main]" --dry

Expected result:
Turbo reports that the //#test:integration, @repo/package-a#build, and @repo/package-b#build tasks will be run.

--filter works exclusively on the package graph and has no knowledge of task definitions so //...[main] is: "any package that is the root package or a dependency that has changed since main".
Only @repo/package-b changed since main and since in the package graph, it isn't a dependency of the root package, nothing gets included in the filter.

Ah that makes sense! Is there a way to declare a package graph dependency without that dependency being added to the package manager? In this situation I want a way to know if I need to run a root-level task when one of the dependencies of that task has changed.

This can be closed.


Default install instructions for Linux not working

I tried to follow the default instructions for Ubuntu but it resulted in it saying iHaskell was not available. Think the stack install is failing before hand. Try the steps on a fresh Ubuntu install.

We test every commit on a fresh Ubuntu install: https://github.com/gibiansky/IHaskell/actions/workflows/ci.yml. Can you be more specific about the errors you're getting?

Closing as this isn't enough information to reproduce the issue or investigate further. Please reopen with more context if you want me to look into this again.


App crashes when trying to get big numbers as int

Issue and Steps to Reproduce
This issue somehow affects vapor the most and actually comes from node but as JSON is mostly used on top of node and I haven't tested it with other node implementations, I am opening it here.
StructuredData has some problems dealing with big numbers (Numbers too big to be represented by a 64 bit integer). Because of that, applications trying to fetch numbers from JSON (or any other StructuredData implementing apis) will crash.
A very simple example which demonstrates how severe this issue is can be seen in the following example, which is a vapor POST route.
post("json") { req in
    guard let i = req.json?["int"]?.int else {
        return "kind of also a success"
    }

    return "success. Int: \(i)"
}

This example does something which is used by many vapor applications. It just fetches an integer from a json HTTP request.
Test Cases:

POST /json - Body: { "int": 1 }
-> Response: success. Int: 1

POST /json - Body: {}
-> Response: kind of also a success

POST /json - Body: { "int":<PHONE_NUMBER>0000000000 }
-> No Response, App crashes

The error is the following:

Double value cannot be converted to Int because the result would be greater than Int.max

It is raised because of an invalid conversion from Double to Int (Double can store much higher values than Int). See the relevant piece of code.
The same applies to UInt and it happens really because of this line:
return Int(d)
where d is a Double which was not checked to be Int.max or less before.
Impact
Because of this malicious users can send requests with big numbers to vapor backed applications to crash them. This issue needs to be solved and released in a critical bug fix update ASAP.
Proposed Solution
Testing the number to be less than or equal Int.max (or UInt.max) should work.
The only thing we need to discuss is whether we want to return nil if the number is too high to fit an Int or simple Int.max.
I personally like the solution with returning nil, as this is what happens. The developer requests an Int and there is no representable value there. Returning Int.max may be problematic in some situations for developers.
Whatever we decide, it is definitely better than a crash.
Once you give me your ok I am happy to submit a pull request to node and add some test cases.

See this sample vapor app which implements a simple post route to /json just like shown above.
json_crash.tar.gz

This is probably caused by the fact that StructuredData doesn't support Int64 at all.
If you can make the jump to Swift 4, you should leverage Codable and forget that the JSON type ever existed.

@vzsg I will definitely have a look through Codable. Thanks for the hint.
But nevertheless we need to fix this because thousands of apps are using JSON right now and with the current version crashing their web servers may really be possible with nothing more than a simple request.

Yeah, that's indeed pretty bad. The error is actually coming from the Number.swift in the Node module, where there are some random safeguards against overflow, but not in the double case.
@tanner0101 could you take a look at this please?

how does this look: https://github.com/vapor/node/pull/97


SSH Session Killed : Improvements at Server Keep

Feature description
Some times SSH sessions are killed because app goes to background for too long or because we are on the go and we loose the carrier.
It should be powerful to maintain the connection on the server itself and when we reconnect we can attach the session again without loosing anything.

This can possibly be something solved through mosh no?

@nothingto Yes but ad mosh license isn’t compatible with WebSSH I need to rewrite it or find a lighter solution


Pin dependencies

This PR contains the following updates:

Package
Type
Update
Change

@actions/http-client
dependencies
pin
^2.0.1 -> 2.0.1

yaml (source)
dependencies
pin
^2.1.1 -> 2.1.1

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
You don't have permission to create /tmp/renovate/cache/containerbase.
curl: (23) Failed writing received data to disk/application
tar: /tmp/renovate/cache/containerbase/7576b42decc67f70b61585f41c5074bea75c260886346e567578ea0e0dc2d571/node-v16.17.0-linux-x64.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
bash: npm: command not found


PLAT-5506: Handle RTL case of voice scroll

Issue Resolved / Feature Added
In case of RTL, scroll option has to changed oppositely
Resolution
Additional Considerations
Links
https://jira2.lgsvl.com/browse/ENYO-5506
Comments
Enact-DCO-1.0-Signed-off-by: Changgi Lee<EMAIL_ADDRESS>

LGTM, but could you update the CHANGELOG.md in moonstone packge?

LGTM


Add images used in cpg-pipes

Moving over images used in seqr loader.

Closed in favour of https://github.com/populationgenomics/images/pull/48


TypeError: Cannot read property 'document' of undefined

I'm having trouble getting this to work in a Meteor app.  Here's what I did:
Cloned the repo recursively:
git clone --recursive git://github.com/MrRio/jsPDF.git

Copied the minified file from the dist folder to my meteor project
cp jsPDF/dist/jspdf.min.js invoicethat.com/lib/compatibility/

Started meteor
meteor                                                                 [18/2455]
[[[[[ ~/code/invoicethat.com ]]]]]

=> Started proxy.
=> Meteor <IP_ADDRESS> is available. Update this project with 'meteor update'.
=> Started MongoDB.
W20150406-12:30:37.174(-5)? (STDERR)
W20150406-12:30:37.175(-5)? (STDERR) /Users/chip/.meteor/packages/meteor-tool/.<IP_ADDRESS>xrpsay++os.osx.x86_64+web.browse
r+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
W20150406-12:30:37.175(-5)? (STDERR)                                            throw(ex);
W20150406-12:30:37.175(-5)? (STDERR)                                                  ^
W20150406-12:30:37.175(-5)? (STDERR) TypeError: Cannot read property 'document' of undefined
W20150406-12:30:37.176(-5)? (STDERR)     at r (app/lib/compatibility/jspdf.min.js:170:3428)
W20150406-12:30:37.176(-5)? (STDERR)     at app/lib/compatibility/jspdf.min.js:170:5695
W20150406-12:30:37.176(-5)? (STDERR)     at app/lib/compatibility/jspdf.min.js:171:11352
W20150406-12:30:37.176(-5)? (STDERR)     at app/lib/compatibility/jspdf.min.js:173:3
W20150406-12:30:37.176(-5)? (STDERR)     at /Users/chip/code/invoicethat.com/.meteor/local/build/programs/server/boot.j
s:222:10
W20150406-12:30:37.176(-5)? (STDERR)     at Array.forEach (native)
W20150406-12:30:37.176(-5)? (STDERR)     at Function._.each._.forEach (/Users/chip/.meteor/packages/meteor-tool/.1.0.45
.1xrpsay++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/underscore/undersco
re.js:79:11)
W20150406-12:30:37.176(-5)? (STDERR)     at /Users/chip/code/invoicethat.com/.meteor/local/build/programs/server/boot.j
s:117:5
=> Exited with code: 8

Several lines down in the stack trace you'll notice the error, "TypeError: Cannot read property 'document' of undefined".
I have also tried copying the jspdf.debug.js file, but I get the same error.
Additionally, I've tried using the resulting files after running ./build.sh from within the repo.
Any suggestions on how to resolve this issue or even build the project would be very helpful. Thank you.

See more info at eligrey/FileSaver.js#135. I'll leave this open for now since I'd still like any details on the best way to build this, given the submodules seem to be updated more frequently than this repo.

This issue was due to the way I was loading the files in my meteor project, so I'm closing this.


feat(net): make Status and Hello configurable

Closes #318
Previously we used the Default (empty) impl of HelloMessage which didn't include any capabilities for example.
This moves the Status and Hello messages to the NetworkConfig so it makes it configurable.
I'm not entirely sure about the all the default, especially when it comes to fork_id, fork_filter,hardfork @Rjected

For the forkid, Latest should work but ideally we want to construct it based on the current head, and keep it updated when the head passes a fork block


build error in typescript and expressJS

"typescript": "^4.9.4"
"langchain": "^0.0.74",
whenever I am trying build for prod, I'm always getting error related to langchain,
my tsconfg.json
{
"compilerOptions": {
  "lib": ["es2022", "DOM"],
  "module": "commonjs",
  "target": "es2022",
  "isolatedModules": true,
  "allowJs": false,
  "strict": true,
  "esModuleInterop": true,
  "skipLibCheck": true,
  "forceConsistentCasingInFileNames": true,
  "allowSyntheticDefaultImports": true,
  "noImplicitReturns": true,
  "noImplicitAny": true,
  "moduleResolution": "node",
  "sourceMap": true,
  "outDir": "dist",
  "strictNullChecks": true,
  "noUncheckedIndexedAccess": true,
  "resolveJsonModule": true
},
"include": ["src"],
"exclude": ["node_modules", "dist"]
}

There are like 41 errors all related to langchain.
eg:
node_modules/langchain/dist/document_loaders/fs/buffer.d.ts:1:23 - error TS1452: 'resolution-mode' assertions are only supported when moduleResolution is node16 or nodenext.
1 ///
node_modules/langchain/dist/document_loaders/fs/epub.d.ts:1:27 - error TS2307: Cannot find module 'epub2' or its corresponding type declarations.
1 import type { EPub } from "epub2";
node_modules/puppeteer/lib/types.d.ts:2280:5 - error TS18028: Private identifiers are only available when targeting ECMAScript 2015 and higher.
2280     #private;
Note: Even though I make any changes on tsconfig.json like target to node16 or node next, I don't see any affects.

can you confirm which langchain imports you have in your application?
Also see https://github.com/hwchase17/langchainjs/tree/main/test-exports-cjs for an example CJS Node.js project tested on CI to work

@nfcampos BaseDocumentLoader, PDFLoader, Pinecone, zeroshot agents and so on.
I removed my tsconfig.eslint.json and changed my tsconfig.json to the following, it seems to be working. Somehow tsconfig.eslint.json didn't allow it to have any impact even though I changed setting on tsconfig file, and not sure why it was affecting only langchain.
{
  "compilerOptions": {
    "lib": ["ESNext", "DOM"],
    "module": "commonjs",
    "target": "ES6",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "strictNullChecks": true,
    "allowSyntheticDefaultImports": true,
    "noImplicitReturns": true,
    "noImplicitAny": true,
    "resolveJsonModule": true
  },
  "include": ["src"],
  "exclude": ["node_modules", "./husky"]
}

Cool, great that it was resolved

Just to add to expand on @anandsthajp's solution, the specific setting that worked for me is adding skipLibCheck: true in my tsconfig.json file.


Add WiFi indicator and Dual (or more) Screen Support

Changelog for #345

WIP

Type of change

[x] New feature (non-breaking change which adds functionality)

@andrewstech, why did it fail due to Sentry?

@andrewstech, we may need to re-write this whole project in .mjs, since some of the stuff is not compatible with ReactJS. The main thing I am doing is not even remotely possible in ReactJS. This is why I marked this as a Mega-Pull-Request. I am just letting you know if you or @blueedgetechno would like me to move on with it as it will likely take a very, very long unknown amount of time. Thanks!

@andrewstech, we may need to re-write this whole project in .mjs, since some of the stuff is not compatible with ReactJS. The main thing I am doing is not even remotely possible in ReactJS. This is why I marked this as a Mega-Pull-Request. I am just letting you know if you or @blueedgetechno would like me to move on with it as it will likely take a very, very long unknown amount of time. Thanks!

Think its a waste of time, how many users would use the function?

I am not sure. I will make a poll on discord, and we can decide off of that!

As andrew already mentioned, it is not worth for the amount of work.

I agree as well. Completely rewriting it is probably not worth it.

As andrew already mentioned, it is not worth for the amount of work.

This PR has another purpose, as well as I will try and find a way around re-writing it. Maybe I can make the impossible, possible?

As andrew already mentioned, it is not worth for the amount of work.

This PR has another purpose, as well as I will try and find a way around re-writing it. Maybe I can make the impossible, possible?

How bout not

@Posandu accept cla pls

@Posandu!!!!!!!!!!!!!! SIGN THE CLA! xD

I have read the CLA Document and I hereby sign the CLA

recheck

So what's happening?

Working on it still. Lol

/link #292

Closes #292


REACT mode is more likely aligned with the 'Scene Graph Classification (sgcls)' task？

react   sgcls mode?

Hello,
Currently, the SGCLS setting is not supported for the REACT model or any YOLO-based models (which I call Decoupled Two-Stage models). The reason behind that is that YOLO is a single-stage detector that decodes the bounding boxes AND the class labels at the same time, making it impossible to use the label classifier with the groundtruth boxes as it is the case in SGCLS.
In my opinion, the SGCLS task does not make any sense in Two-Stage SGG because the prediction of object labels seems to be worse after the relation prediction stage than before (which I discuss in Table 1 of my paper).


Please support global function handler

Globals:
  Function:
    Runtime: nodejs10.x
    Handler: app.handler
    MemorySize: 512
    Timeout: 30

Error: Endpoint is missing a Handler

This looks related to this PR:
https://github.com/SnappyTutorials/aws-sam-webpack-plugin/pull/15

This has been fixed and will be released with 0.5.0


Fork the current README off into DOCS and write a real README

Here's a hot take: Our current README isn't a README at all, it's a manual!
I feel personally responsible for this problem, since I wrote an early draft of the README, and the only thing I wrote was a tutorial.
There are lots of competing opinions on what should go into a README (it's worth a quick google), but none of them say that your README should just be a manual. Here's an opinion on READMEs from https://liw.fi/readme-review/ that I find particularly helpful:

A README is meant for someone who is first encountering the project to be able to quickly decide if they want to learn more about it.
A README should have a “blurb”: a very short, dense summary of the project aimed at someone who doesn’t know anything about it yet and may not know the topic area.
A README is not the manual, but it may have an example of how to typically use the software, especially if that helps the reader understand the software better.
A README should say how the copyright and other legal aspects affect the project. It should say what copyright licenses the project uses.
A README can also contain instructions for installing the software, or how to run its test suite, and other practical aspects, but those can go into other documentation as well. Referring to them is good, as is linking to more information about the project, and who works on the software.

I think we desperately need a "blurb" that contains some very clearly stated goals of the project; I think it would help us cut down on issues/PRs that are tangent to our goals. Here's a summary of what I think the project is about:

This is a batteries-included quick-start to building programs (and/or libraries?) in C++. Everything in the project is meant to get you to follow best-practices while writing C++ code, without having to stop and write a bunch of boilerplate CMake.
This project is mostly about "Use the tools available". To that end, the project:

pushes you towards using Conan for dependency management, so you don't have to reinvent the wheel, and you have an easy means of getting your dependencies to all of your teammates.
lowers the barrier of entry to using unit tests, continuous integration, and code coverage, so you can always measure what's broken and what isn't.
gives you access to static analyzers and sanitizers, which you can activate as simply as flipping a switch.
gives you a quick-start to using several GUI libraries, which can be tricky to set up in a CMake project.

This project is not about CMake best-practices. It attempts to employ the best CMake code that it can, but when given the choice, it will always sacrifice CMake best-practices to push you towards good C++ tools and C++ best-practices (see #123).

I am certainly wrong about some of these goals, and I'm surely missing something; please correct me! I sure hope I'm wrong about the CMake best-practices thing; it would be nice to follow both C++ and CMake best practices.

I think we got this with eb554db125bdc79732d4dbe483f239011b5825c7; thanks @lefticus!


HIVE3 error about 'failed to submit loading process'

HIVE3 output error now that is blocking us from computations. The error even occurs when I ran another computation that ran successfully.
I have emailed Vahan and hopefully it is just him messing witht he pipeline today.

This has been resolved