Experiencing "Cannot implicitly convert type 'Microsoft.AspNetCore.Components.ElementReference' to MyComponent"

@jjonescz @danroth27
I ran into the issue reported in #8761 which was closed with a reference to issue (#8718) which was closed as complete.
I was using the 8.0.preview.5 SDK. I followed the table reference for 8.0.100-preview.6.23330.14 SDK, installed, and still have the error.
In my component MOIPrimaryTreatment.Razor I have another component defined as:
<TreatmentDialog pTreatmentDialogCompleted="@TreatmentDialogCompletionAsync"
@ref="pTreatmentDialogRef" />

Instead of having a component defined in the corresponding razor.g.cs I have an element:
            __builder.OpenElement(21, "TreatmentDialog");
            __builder.AddAttribute(22, "pTreatmentDialogCompleted",
#nullable restore
#line 28 "C:\Solutions\OHI\Optimiser.2021\Optimiser.Client\Views\Dashboard\Processes\Oncology\Segments\Infusion\Helpers\MOIPrimaryTreatment.razor"
                                             TreatmentDialogCompletionAsync

#line default
#line hidden
#nullable disable
            );
            __builder.AddElementReferenceCapture(23, (__value) => {
#nullable restore
#line 29 "C:\Solutions\OHI\Optimiser.2021\Optimiser.Client\Views\Dashboard\Processes\Oncology\Segments\Infusion\Helpers\MOIPrimaryTreatment.razor"
      pTreatmentDialogRef = __value;

#line default
#line hidden
#nullable disable
            }
            );
            __builder.CloseElement();

And then, of course, when I try to use the component reference I get the "Cannot implicitly convert type 'Microsoft.AspNetCore.Components.ElementReference' to TreatmentDialog"
Other similar embedded components are working as expected. I just don't see the code pattern that is causing the generation to fail.
[Edit] I also tried sdk 7.0.400-preview.23356.7 and have the same error...

Thanks for reporting this. Both 8.0.100-preview.6.23330.14 and 7.0.400-preview.23356.7 should have the fix. Can you please share more details about the component that's giving the error (TreatmentDialog)? Is it defined across multiple files (like a .razor and a .cs file), or what is special about it? Alternatively you can share source code of a minimal reproducible example, so I can take a look.

@jjonescz Here are the two files; If you don't see anything that could be triggering the error I can try to extract to a minimal repo. But there is a ton backing components/etc. that will make it difficult. I have followed this pattern throughout the application and have not run into this issue before.
The 'TreatmentDialog is pretty straightforward with a razor & razor.cs file:
razor:
@namespace Optimiser.Views

<GCDialog pDialogTitle="@pTitle"
          pOnDialogActionAsync="OnDialogComplete"
          pButtonSelection="eDialogButtonSelections.OKCancel"
          @ref="@pGCDialogReference">

    <pBody>
        <div class="flow-flex-column">
            @if (pShowNewTX)
            {
                <FlowDivider pAdditionalStyles="margin-top: .75em; "
                             pTitle="Search"
                             pDividerStyle="eFlowDividerStyle.Small" />

                <GCTextBox pAdditionalStyles="margin-top: .75em; width: 500px; "
                           pValue="@pSearchText"
                           pValueChanged="@SearchTextChanged" />

                <GCSelect @bind-pValue="@pSearchCriteria"
                          pDensity="eDensity.Minus4"
                          pGCItemValidation="eItemValidation.DefaultToFirst"
                          pGCItems="@pSearchCriteriaItems"
                          pGCSelectInputStyle="eSelectInputStyle.Outlined"
                          pGCTextAlignStyle="eTextAlignStyle.Left" />

                <GCGrid pColumnConfigurations="@pColumnConfigurationsNewTX"
                        pGroupedOrderedData="@pGroupedOrderedDataNewTX"
                        pKeyExpression="@(pTX => pTX.GUID)"
                        pLogIdentification="MOI Predefined Tx"
                        pMeasurement="MB_Grid_Measurement.FitToData"
                        pOnMouseClickCallback="@MouseClickAsync"
                        TRowData="@MedOncInf_TxDetail_DD" />

            }
        </div>
    </pBody>

</GCDialog>

and the cs file:
using System;
using System.Collections.Generic;
using System.Threading.Tasks;

using GeneralComponents;

using Material.Blazor;

using Microsoft.AspNetCore.Components;

using Optimiser.DataTier.DataDefinitions;
using Optimiser.Infrastructure.MVVMFramework.Collections;
using Optimiser.Infrastructure.MVVMFramework.Components;
using Optimiser.Infrastructure.MVVMFramework.Converters;
using Optimiser.SharedUtilities;
using Optimiser.ViewModels.CachedEntities;
using Optimiser.ViewModels.Process;

using static Optimiser.SharedUtilities.MedOncInf_TxDetail_DD;

//
//  2017-10-06  Mark Stega
//              Created
//
//  2018-05-25  Mark Stega
//              Added support for procedures
//
//  2018-07-19  Mark Stega
//              Added support for searching therapy names
//
//  2018-07-31  Mark Stega
//              Added search parameters of "Contains" and "StartsWith"
//
//  2023-07-09  Mark Stega
//              Created from Treatment.xaml & Treatment.xaml.cs from O.2012
//

namespace Optimiser.Views;

public partial class TreatmentDialog

{
    #region Members

    [Parameter] public EventCallback<string> pTreatmentDialogCompleted { get; set; }

    [Inject] private CachedEntitiesViewModel pCachedEntitiesVM { get; set; }
    [Inject] private ProcessViewModel pProcessVM { get; set; }

    private List<MBGridColumnConfiguration<MedOncInf_TxDetail_DD>> pColumnConfigurationsNewTX { get; set; } = null;
    private MedOncInf_TxDetail_DD pCurrentTx { get; set; }
    private GCDialog pGCDialogReference { get; set; }
    private IEnumerable<KeyValuePair<string, IEnumerable<KeyValuePair<string, MedOncInf_TxDetail_DD>>>> pGroupedOrderedDataNewTX { get; set; }
    public SortableObservableCollection<MedOncInfDefinition_DD> pInsCo1Collection { get; set; }
    public SortableObservableCollection<MedOncInfDefinition_DD> pInsCo2Collection { get; set; }
    private bool pShowNewTX { get; set; }
    private List<GCSingleSelectListElement<string>> pSearchCriteriaItems { get; set; }
    private string pSearchText { get; set; }
    public MedOncInfDefinition_DD pSelectedInsCo1 { get; set; }
    public MedOncInfDefinition_DD pSelectedInsCo2 { get; set; }
    public MedOncInfDefinition_DD pSelectedSourceTx { get; set; }
    public SortableObservableCollection<MedOncInfDefinition_DD> pSourceFilteredTxCollection { get; set; }
    public SortableObservableCollection<MedOncInfDefinition_DD> pSourceUnfilteredTxCollection { get; set; }
    private string pTitle { get; set; }

    private string m_SearchCriteria;
    public string pSearchCriteria
    {
        get { return m_SearchCriteria; }
        set
        {
            if (value != m_SearchCriteria)
            {
                m_SearchCriteria = value;
                ApplySearchCriteria();
            }
        }
    }

    #endregion

    #region ctor

    public TreatmentDialog()
    {
        pSearchCriteriaItems = new();
        pSearchCriteriaItems.Add(new GCSingleSelectListElement<string>() { pLabel = "Contains", pDataValue = "Contains" });
        pSearchCriteriaItems.Add(new GCSingleSelectListElement<string>() { pLabel = "Starts with", pDataValue = "Starts with" });

        pColumnConfigurationsNewTX = new();

        pColumnConfigurationsNewTX.Add(new MBGridColumnConfiguration<MedOncInf_TxDetail_DD>(
            columnType: MB_Grid_ColumnType.Icon,
            dataExpression: c => new ConvertBoolToMBGridIconSpecification().Convert(c.Active),
            title: "Active"));
        pColumnConfigurationsNewTX.Add(new MBGridColumnConfiguration<MedOncInf_TxDetail_DD>(
            dataExpression: c => c.Descriptor1,
            title: "Mode"));
        pColumnConfigurationsNewTX.Add(new MBGridColumnConfiguration<MedOncInf_TxDetail_DD>(
            dataExpression: c => c.Descriptor2,
            title: "Tx"));
        pColumnConfigurationsNewTX.Add(new MBGridColumnConfiguration<MedOncInf_TxDetail_DD>(
            dataExpression: c => c.Descriptor3,
            title: "Agent"));
    }

    #endregion

    #region ApplySearchCriteria

    private void ApplySearchCriteria()
    {
        pSourceFilteredTxCollection = new();
        var contains = pSearchCriteria == "Contains";
        var startsWith = pSearchCriteria == "Starts with";

        foreach (var tx in pSourceUnfilteredTxCollection)
        {
            if (   (pSearchText.Length == 0)
                || (contains && tx.Descriptor1.IndexOf(pSearchText) >= 0)
                || (startsWith && tx.Descriptor1.IndexOf(pSearchText) == 0))
            {
                pSourceFilteredTxCollection.Add(tx);
            }
        }

    }

    #endregion

    #region OpenDialogAsync
    public async Task OpenDialogAsync()
    {
        await pGCDialogReference.OpenDialogAsync();
    }
    #endregion

    #region CloseDialogAsync
    public async Task CloseDialogAsync()
    {
        await pGCDialogReference.CloseDialogAsync();
    }
    #endregion

    #region MouseClickAsync
    protected async Task MouseClickAsync(string uid)
    {
        await Task.CompletedTask;

//        MedOncInf_TxDetail_DD primaryTx = new();

//        foreach (var ptx in pProcessVM.pMedOncInf_TxDetailCollection_PrimaryTreatments)
//        {
//            if (ptx.GUID.ToString() == uid)
//            {
//                // We have the matching treatment
//                primaryTx = ptx;
//                break;
//            }
//        }
//        // edit the treatment
//#if (MSH)
//        pTreatmentDialogRef.SetDTO(
//            p_CurrentTx: primaryTx,
//            p_IsNew: false);
//#endif
//#if (DEMO || DEVELOP || LBH)
//        pTreatmentDialogRef.SetDTO(
//            p_CurrentTx: primaryTx,
//            p_IsNew: false);
//#endif
//        await pTreatmentDialogRef.OpenDialogAsync();
    }
    #endregion

    #region OnDialogComplete
    // Set as the click handler on our OK and Cancel buttons
    protected async Task OnDialogComplete(string buttonId)
    {
        // Post our selection event
        await pTreatmentDialogCompleted.InvokeAsync(buttonId);
    }
    #endregion

    #region Properties corresponding to MedOncInf_TxDetail_DD

    public bool pActive { get; set; }
    public DateTime pAppointmentDateTime { get; set; }
    public string pDescriptor1 { get; set; }
    public string pDescriptor2 { get; set; }
    public string pDescriptor3 { get; set; }
    private bool pNoAuthRequired { get; set; }
    public string pInsuranceCompany1 { get; set; }
    public string pInsuranceAuthorization1 { get; set; }
    public string pInsuranceNote1 { get; set; }
    public string pInsuranceCompany2 { get; set; }
    public string pInsuranceAuthorization2 { get; set; }
    public string pInsuranceNote2 { get; set; }
    public DateTime pValidFrom { get; set; }
    public DateTime pValidTo { get; set; }
    #endregion

    #region SearchTextChanged

    private void SearchTextChanged(string newValue)
    {
        pSearchText = newValue;
        ApplySearchCriteria();
    }

    #endregion

    #region SetDTO
    public void SetDTO(
            MedOncInf_TxDetail_DD p_CurrentTx,
            bool p_IsNew = false,
            bool p_ShowInsurance = false)

    {
        pCurrentTx = p_CurrentTx;

        if (p_IsNew)
        {
            pShowNewTX = true;
            pTitle = "New TX";

            pSourceUnfilteredTxCollection = new();
            foreach (MedOncInfDefinition_DD tx in pCachedEntitiesVM.pMedOncInfDefinitionList)
            {
                if (((int)pCurrentTx.TxClass == tx.DefinitionClass)
                    && ((int)pCurrentTx.ProcessTypeIdentifier == tx.DefinitionType)
                    && tx.Active)
                {
                    pSourceUnfilteredTxCollection.Add(tx);
                }
            }

            pSearchText = "";
        }
        else
        {
            pShowNewTX = false;
            pTitle = "Edit TX";
        }

        var sourceInsCoCollection = new SortableObservableCollection<MedOncInfDefinition_DD>();

        if (((pCurrentTx.TxClass == eMedOncInfDefinitionClass.PrimaryTx)
                || (pCurrentTx.TxClass == eMedOncInfDefinitionClass.SupportiveTx)
                || (pCurrentTx.TxClass == eMedOncInfDefinitionClass.Procedure))
            && p_ShowInsurance)
        {
            foreach (MedOncInfDefinition_DD tx in pCachedEntitiesVM.pMedOncInfDefinitionList)
            {
                if (((int)eMedOncInfDefinitionClass.InsuranceCompany == tx.DefinitionClass)
                    && ((int)pCurrentTx.ProcessTypeIdentifier == tx.DefinitionType)
                    && tx.Active)
                {
                    sourceInsCoCollection.Add(tx);
                }
                pInsCo1Collection = sourceInsCoCollection;
                pInsCo2Collection = sourceInsCoCollection;
            }
        }

    }

    #endregion

}

@jjonescz Thanks for looking at the code; I will create as small a repository as I can. Building is simple as all you need to do is to load the solution in Visual Studio & then F6...

@jjonescz -- I ripped apart the solution removing all servers, etc. I zipped the source of the client and it exceeds what I can upload here (File size too big: 25 MB are allowed, 37 MB were attempted to upload.)
I can either split the source and do two zips or I can create a private github repository and give you read access. Or, if you have another solution, I am happy to hear that also.

It's a BIG application. Yes, the binaries were removed (at the root of the project there is a file called superclean.cmd that is used to remove artifacts.
Anyhow, the community portal upload worked: https://developercommunity.visualstudio.com/t/Razor-compilation-failure/10412528

BTW, I am using the 'DevServer' configuration and the 8.0.0-preview.6.23330.14 sdk

Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0029	Cannot implicitly convert type 'Microsoft.AspNetCore.Components.ElementReference' to 'Optimiser.Views.TreatmentDialog'	Optimiser.Client	C:\Solutions\OHI\Optimiser.2021.Client\Optimiser.Client\Views\Dashboard\Processes\Oncology\Segments\Infusion\Helpers\MOIPrimaryTreatment.razor	29	Active

Hi. This is just a guess, but could the issue be related to long paths? I've come across similar situations in the past when people have shared their reproduction code with me. What if you try moving the TreatmentDialog.razor file up one level? Perhaps then your MOIPrimaryTreatment will be able to "recognize" it.

@MarkStega the problem is in your Optimiser.Client.csproj - you have <Content Remove= items on some razor files, including the TreatmentDialog.razor (and also below similar <None Include= items). That makes the files invisible to Razor compiler.

@jjonescz
Thanks for finding that -- It is a very annoying Visual Studio 'side effect' to put the '''<Content remove``` items if you copy/rename files. It does so silently. I have often copied an existing component in VS, pasted it, renamed the "- Copy".
I am going to post this in VS feedback as a bug unless you think this is a good behavior on the part of VS.

@ScarletKuro  See above for the root cause. The uneven support for long file names in VS is an issue but not the problem this time. I can't open the generated files with VS due to the path being too long so I have to copy them to a shorter path.


Accidental refresh problem

What if during the game I accidentally refresh the page and start the game from the beginning losing all my progress? How should we handle this situation?

Oh, I see. There is #11 So the user should not forget to save his progress all the time. Ok.


Setting current_tab of a tab container doesn't work when it's not visible or not ready

Tested versions

Reproducible in: 4.3.dev5
Not reproducible in: 4.2.1

System information
Godot v4.3.dev5 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 SUPER (NVIDIA; <IP_ADDRESS>18) - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 Threads)
Issue description
This issue is two-fold (I don't know if I should make separate issues as they seem related):

Setting current_tab from script doesn't work when the tab container is not ready. (It works previously) For example, when setting the current_tab from an "uncle" node's _ready() that is higher up in the tree than the parent node.
Setting current_tab from script doesn't work in a nested tab container where the target container was not visible, when performed from a button click. select_next_available() doesn't seem to work either.

I noticed this behavior because my project which was working in Godot 4.2.1 no longer works properly in Godot 4.3.dev5 in regards to tab containers.
Setting the current tab in the editor does always seem to work on the other hand.
Current "workaround"
Instead of setting current_tab, setting the tab control's visibility directly seems to work reliably.
Steps to reproduce
Reproduction 1 (not ready)

Create 2 sibling nodes, the ordering is important. Attach script to the 1st node, and add a tab container with 2 distinct tabs to the 2nd node. Set the current tab to 0 in the editor inspector.
In the 1st node's script's _ready() function, set the tab container's current_tab to 1. It does not work, presumably because the tab container is not ready.
In the scene's root node, attach a script and set the tab container's current_tab to 1 in its _ready() function. It does work, presumably because the children are ready, including the tab container.

Reproduction 2 (not visible)

Create a nested tab container structure with 1 parent tab container and 2 child tab containers as its tabs. Then add 2 distinct tabs each to the child tab containers. Set the current tab of all tab containers to 0 in the editor inspector.
Add a button to the scene's root node. Attach a script in the scene's root node and connect the button's pressed() signal. In the _on_button_pressed() function, set the top tab container's current_tab to 1 then set the 2nd child tab container's current_tab to 1 in the next line.
Run the project, click the button once. The top tab container current_tab will change successfully, however the 2nd child's current_tab will fail to change, presumably due to it being previously/currently invisible. Click the button again, now it works because the 2nd child is now visible.

Minimal reproduction project (MRP)
This project contains both reproduction method in separate scenes. Open the scene and run them individually.

not_ready_reproduction.tscn for the "not ready" issue reproduction
not_visible_reproduction.tscn for the "not visible" issue reproduction

godot4.3.dev5_tab_container_test.zip

In the not ready situation, the set_current_tab will be called three times:

instantiate with p_current = 0, but not inside tree, so it set setup_current_tab to 0
called by use's script with p_current = 1
in NOTIFICATION_POST_ENTER_TREE,  setup_current_tab >= -1 so the func is called with p_current = 0


Feature/inner product

Updated all the changes to pass the pull

Some changes to update the request changes


Need documentation on the need for sealing the lifecycle methods in MvvmComponentBase

MvvmComponentBase has accessible lifecycle methods. It certainly isn't clear why MvvmComponentBase[T] lifecycle methods are sealed preventing their override in a Blazor component that inherits from that class. I can see why one must call the base implementation of the methods since they are not simple virtuals. If they must remain sealed then documentation is needed as to why, and if they can be opened, then documentation on the need to call the base implementation is also needed.

Sorry for the late response. Actually there is no real reason why they are sealed. Probably I sealed them to prevent people from messing with them, but since it's common sense to call the base method, there is no real reason to have it like that. I'm going to unseal them.


Auto initialization of tables isn't supported from the read journal side.

Version Information
Version of Akka.NET?
1.5.14
Which Akka.NET Modules?
Akka.Persistence.Sql
Describe the bug
I am using the new LINQ to db persistence with hocon config. I am initializing my tables with  auto-initialize = true.
But this only happens if any actors attempt to persist something. In my case I also start a read journal. Then read journal complains the tables don't exist yet. Since no events are persisted yet.  Surprisingly though the tables are created after read journal throws.
I have configured auto-initialize for the read journal as below
akka {
    persistence {
      journal {
        plugin = "akka.persistence.journal.sql"
        sql {
           class = "Akka.Persistence.Sql.Journal.SqlWriteJournal, Akka.Persistence.Sql"
            connection-string = ${config.connection-string}
            provider-name =  "SQLite.MS"
            auto-initialize = true
        }
      }
      query.journal.sql {
        class = "Akka.Persistence.Sql.Query.SqlReadJournalProvider, Akka.Persistence.Sql"
        connection-string = ${config.connection-string}
        provider-name = "SQLite.MS"
         auto-initialize = true
      }
      snapshot-store {
        plugin = "akka.persistence.snapshot-store.sql"
        sql {
          class = "Akka.Persistence.Sql.Snapshot.SqlSnapshotStore, Akka.Persistence.Sql"
            connection-string = ${config.connection-string}
            provider-name = "SQLite.MS"
            auto-initialize = true
        }
      }
...

But I saw that auto-initialize isn't a supported config option for query.journal.sql. From the code I saw that, initilializing is done by
SqlWriteJournal. So either provide a programmatic way to force generating tables or better make sure read journal has also ability to generate the tables in case it is started before.
To Reproduce
Just try to use a read journal without persisting any events.
Links to working reproductions on Github / Gitlab are very much appreciated
Expected behavior
I would like readjournal not to fail with table don't exist error without persisting a dummy event.
Actual behavior
Read journal throws an exception when reading events. But somehow tables are created then.
[18:05:38 ERR] An exception occured inside SelectAsync while executing Task. Supervision strategy: Stop
System.AggregateException: One or more errors occurred. (SQLite Error 1: 'no such table: journal'.)
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: journal'.
   at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements()+MoveNext()
   at Microsoft.Data.Sqlite.SqliteCommand.GetStatements()+MoveNext()
   at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at LinqToDB.Data.DataConnection.ExecuteReaderAsync(CommandBehavior commandBehavior, CancellationToken cancellationToken)
   at LinqToDB.Data.DataConnection.ExecuteDataReaderAsync(CommandBehavior commandBehavior, CancellationToken cancellationToken)
   at LinqToDB.Data.DataConnection.ExecuteDataReaderAsync(CommandBehavior commandBehavior, CancellationToken cancellationToken)
   at LinqToDB.Data.DataConnection.QueryRunner.ExecuteReaderAsync(CancellationToken cancellationToken)
   at LinqToDB.Linq.QueryRunner.ExecuteQueryAsync[T](Query query, IDataContext dataContext, Mapper`1 mapper, Expression expression, Object[] ps, Object[] preambles, Int32 queryNumber, Func`2 func, TakeSkipDelegate skipAction, TakeSkipDelegate takeAction, CancellationToken cancellationToken)
   at LinqToDB.Linq.QueryRunner.ExecuteQueryAsync[T](Query query, IDataContext dataContext, Mapper`1 mapper, Expression expression, Object[] ps, Object[] preambles, Int32 queryNumber, Func`2 func, TakeSkipDelegate skipAction, TakeSkipDelegate takeAction, CancellationToken cancellationToken)
   at LinqToDB.Linq.ExpressionQuery`1.GetForEachAsync(Action`1 action, CancellationToken cancellationToken)
   at LinqToDB.Linq.ExpressionQuery`1.GetForEachAsync(Action`1 action, CancellationToken cancellationToken)
   at LinqToDB.AsyncExtensions.ToListAsync[TSource](IQueryable`1 source, CancellationToken token)
   at Akka.Persistence.Sql.Query.Dao.BaseByteReadArrayJournalDao.<>c__DisplayClass6_0.<<JournalSequence>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Akka.Persistence.Sql.Extensions.ConnectionFactoryExtensions.ExecuteWithTransactionAsync[T](AkkaPersistenceDataConnectionFactory factory, IsolationLevel level, CancellationToken token, Func`3 handler)
   at Akka.Persistence.Sql.Extensions.ConnectionFactoryExtensions.ExecuteWithTransactionAsync[T](AkkaPersistenceDataConnectionFactory factory, IsolationLevel level, CancellationToken token, Func`3 handler)
   at Akka.Persistence.Sql.Extensions.ConnectionFactoryExtensions.ExecuteWithTransactionAsync[T](AkkaPersistenceDataConnectionFactory factory, IsolationLevel level, CancellationToken token, Func`3 handler)
   at Akka.Persistence.Sql.Extensions.ConnectionFactoryExtensions.ExecuteWithTransactionAsync[T](AkkaPersistenceDataConnectionFactory factory, IsolationLevel level, CancellationToken token, Func`3 handler)
   at Akka.Persistence.Sql.Query.Dao.BaseByteReadArrayJournalDao.<JournalSequence>b__6_0(<>f__AnonymousType4`3 input)
   --- End of inner exception stack trace ---
   at Akka.Actor.PipeToSupport.PipeTo[T](T

Environment
Linux, docker .NET 8
Are you running on Linux? Windows? Docker? Which version of .NET?

I suspect this line should be moved above on top of the method
https://github.com/akkadotnet/Akka.Persistence.Sql/blob/155e8fba91832bd8be1e7492145f1abc4f9f4165/src/Akka.Persistence.Sql/Journal/SqlWriteJournal.cs#L116

Two questions for @Aaronontheweb  and @Arkatufus:

Should we be auto-initializing Journals from the Query Side?
If Yes, should we have that as a separate config option?

There are problems implementing database table initializer for the read journal.
In the old Sql.Common implementation, all table operations (both read and write) were implemented inside the journal actor, this allows for command stashing for all operations, allowing the journal to complete any database initialization before processing any database operations.
In Akka.Persistence.Sql, the read journal accesses the database directly, giving it a performance boost. The problem with this design is that there's no mechanism we can tap into to make sure that the database tables are initialized.

I understand the challenges how ever I don't agree with the outcome at least the exception should be handled in someway. Please reopen @Aaronontheweb @Arkatufus

Fair point, we should handle the exception at least


[CSGen] Fix LinkedExprAnalyzer greedy operator linking (attempt #2)

Let's not attempt to link arithmetic operators together in
presence of concrete and literal (int, float, string) types.
Resolves: rdar://problem/35740653

@swift-ci please test

@swift-ci please test source compatibility

Just merged revert of XFAIL in ReactiveCocoa, going to re-run source compatibility suite.

@swift-ci please test source compatibility


Logic Bug in scanner fetcher.fetch method

I was investigating an issue we are seeing and came across the following conditional in scanner.go:
resp, region, err := f.next()
if err != nil {
	if err != context.Canceled || err != context.DeadlineExceeded {
		// if the context of the scan rpc wasn't cancelled (same as calling Close()),
		// return the error to client
		f.trySend(nil, err)
	}
	break
}

I think that the inner coditional (regarding the context errors) should instead read:
if err != context.Canceled && err != context.DeadlineExceeded {
	// if the context of the scan rpc wasn't cancelled (same as calling Close()),
	// return the error to client
	f.trySend(nil, err)
}

If you think about it, as it was originally (with the OR operator), if the fist part of the conditional, err != context.Canceled is false, then that means that the error is a context.Canceled error and  the second part of the conditional err!= context.DeadlineExceeded will always be true.
I think what's trying to be accomplished here is making sure that the error is neither a Canceled or DeadlineExceeded error before we return the error to the client.

I've made a change (https://github.com/tsuna/gohbase/commit/774865576a9e5d9398d5328db6c30a29783794f3) to scanner to actually return any context related errors to the client instead of just returning io.EOF (it bit me as well). Let me know how it goes.


fix: zpages default handler add trailing slash

the path.Join call path.Clean will clean trailing slash

Thanks for your contribution. OpenCensus is in maintenance mode so we are only prioritizing critical bugfixes. Please reopen if you disagree with our assessment of severity.


Add support for supplementary datums

Changelog
- description: |
    Add support for supplementary datums

  type:
  - feature        # introduces a new feature

Context
Integrates:

https://github.com/IntersectMBO/cardano-api/pull/640

Implements:

https://github.com/IntersectMBO/cardano-api/issues/600

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated. See Running tests for more details
[ ] Self-reviewed the diff

This will work but I need to modify the PR a little more to improve the user experience.


Bump CAPV to v1.7.0

Bump CAPV to the latest release.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest


Select outputs after creating an edge to size stack at position other than last fails

Root cause is that variable array for selecting existing outputs can only select from previous existing outputs.
The logic to deal with this in inoutconstraint!(s, ::SizeStack, v, model, vardict::Dict) assumes that any misaligned inputs are last in inputs(v).
It might be possible to avoid aligning select vars but do align insertion vars as they can be assumed to have the same size.  MWE below fails to align sizes and reverts the edge addition when this change is made though.
MWE testset which runs in select.jl:
    @testset "Create edge to SizeStack pos 1" begin
        inpt = iv(3)
        v1 = av(inpt, 2, "v1")
        v2 = av(inpt, 3, "v2")
        v3 = cc(v1, name="v3")
        v4 = av(v3, 3, "v4")

        g = CompGraph(inpt, v3)
        @test size(g(ones(Float32, 1,3))) == (1, nout(v3))

        create_edge!(v2, v3, pos=1)
        Δoutputs(v3, v -> 1:nout_org(v))

        @test in_inds(op(v4)) == [-1,-1,-1,1,2]

        @test size(g(ones(Float32, 1,3))) == (1, nout(v3))
    end

Testcase for structure (where it belongs):
@testset "Create edge to SizeStack pos 1" begin
    v0 = inpt(3, "v0")
    v1 = av(v0, 2; name="v1")
    v2 = av(v0, 3, name="v2")
    v3 = conc(v1; dims=2, traitdecoration=tf("v3"))
    v4 = av(v3, 3, name="v4")

    g = CompGraph(v0, v3)
    @test size(g(ones(3))) == (nout(v3),1)

    @test create_edge!(v2, v3, pos=1)

    @test lastins(v4) == [-1,-1,-1,1,2]

    @test size(g(ones(3))) == (nout(v3),1)
end


Quick Question About Customization

Hello all, I am new to swift development and I'd like to start off by saying thank you for your pod. My question is this; Is there an easy way to add a parameter for field icon? I.E. I'd like to have an icon next to the textfield that changes colors if invalid or valid

This is doesn't exactly show how to use it with my library but the general idea would be something like this.
var textField = UITextField()
if errors.count > 0 {
    textField.rightView = UIImageView(image: UIImage(named: "error-icon"))
} else {
    textField.rightView = UIImageView(image: UIImage(named: "checked-icon"))
}

Good luck!

THANKS SO MUCH!

:+1:


[AVM Module Issue]: Unable to accept EULA for Azure VM Marketplace Images

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
Other, as defined below...
(Optional) Module Name if not listed above
No response
(Optional) Module Version
No response
Description
I want to use a specific CIS hardend image from the marketplace but I'm unable to agree the EULA. Is it possible to accept the EULA by default if you are using a image from the Azure Marketplace
(Optional) Correlation Id
No response

Hey @Ralph101, is this issue tied to a specific module in this repository? If not I'm not sure this is a good location for the question.
Given the proximity to the VM, would you happen to have an idea @rahalan?

I think it would be a nice feature if you want to use images from the Azure Marketplace and by default it will accept the EULA. For example I want to use the CIS hardend Windows Server image from the marketplace but with the current setup it's impossible.

Can't argue with that. All I'm saying is that if we'd want to tie it to a module I guess that would mean to somehow accept the EULA for an image in the solution using, for example, a deployment script that runs before a VM deployment. This deployment script could run a logic similar to how shown here.
Just in case it wasn't obvious, we're no Product Group and would hence need to rely on the same feature said as anybody else (as opposed to implement e.g., a custom API endpoint).
Happy to look into this deeper, I'm just not sure I'll be able to give you the answer you're hoping for 😄

@rahalan, please have a look at this one when you have a chance.

@Ralph101 @AlexanderSehr I had a similar problem some years ago. We ran the following command in the pipeline as PS task:
Get-AzMarketplaceTerms -Publisher checkpoint -Product check-point-cg-r8030 -Name sg-ngtx | Set-AzMarketplaceTerms -Accept


Docs not being styled correctly

No CSS is being applied to some of the doc pages.
Have a look at the following: http://articlemetrics.github.io/docs/installation

This has been fixed: http://lagotto.io/docs/installation


Dry run of migration

Go through the steps with a DCE Fedora Box - Single box
Install code on DCEFedora box

[x]  Just a few sample objects some with versions
[ ]  Migrating existing objects to new storage pattern
[ ] Migration would include migrating existing versions

child of #1128

We need to look at migrating all versions from the system and overwrite all existing version instead of creating a new version.
No binary data would be left in fedora when this is completed.


SSR throws Syntax Error for valid JavaScript

[x] Read the docs.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] This is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Describe the bug
Vite in library mode can produce minified code that looks something like this shape:
// some-library.es.js
import { inject as x } from 'vue'

function setup() {
	const { test: x } = { test: true }
}

The use of two x comes from the minifier doing its thing and should be valid. For some reason this shape (where x is used in two spots) causes the syntax error Illegal property in declaration context when instantiating the module at this line: https://github.com/vitejs/vite/blob/master/packages/vite/src/node/ssr/ssrModuleLoader.ts#L122.
I am not familiar with the internals but I believe that the syntax error is introduced at some point in this transform step: https://github.com/vitejs/vite/blob/master/packages/vite/src/node/ssr/ssrTransform.ts#L26
Reproduction
https://github.com/JeffSchofield/vite-ssr-bug
System Info

vite version: 2.0.5
Operating System: Windows 10 18363.1379
Node version: 15.11.0
Package manager (npm/yarn/pnpm) and version: yarn 1.22.10

I am certain this is an edge case in the SSR transformation. Here is the transformed code that is throwing the error from my repro:
const __vite_ssr_import_0__ = __vite_ssr_import__("vue")

__vite_ssr_exports__.default = {
        install() {
                const { test: __vite_ssr_import_0__.inject } = { test: true }
                console.log(__vite_ssr_import_0__.inject)
        }
}

So it seems x is blanket replaced which is introducing the syntax error.


Add doc comparing protobuf and text format

@RichiH I cannot push to your repo, so here you get a PR.

LGTM (I can't merge either)

@SuperQ Look at your invite links, you have had one since day 1.

@RichiH Ohh, it got lost in my inbox :disappointed:


Pass Presenter send method along with model

We found ourselves wrapping the direct children of the Presenter component with withIntent quite often. This PR configures the Presenter to pass down send along with the model.
Fixes #203

👍

That was fast

Coverage remained the same at 100.0% when pulling 40a58aa32a8bd1434212eb01efdaa8e634863abd on presenter-passes-send into 6f189b0e4ea6fabfbf770d4ae85c7dec39658757 on master.

👍

Coverage remained the same at 100.0% when pulling dacb25c80d7d6a0372dcc85451ac7b743848bc12 on presenter-passes-send into 7712f38f4c803c131e805c8f7bdd9d52a5d643b2 on master.

Coverage remained the same at 100.0% when pulling 3d577bfe93864c3225848799165fe1e88deb52f3 on presenter-passes-send into 7712f38f4c803c131e805c8f7bdd9d52a5d643b2 on master.


Apps layer: sample_to_event and related functions for graph similarity

Graph similarity involves dealing with orbits and even coarser grained events composed of multiple samples from GBS. This PR provides some of the elementary functions for graph similarity:

sample_to_orbit
sample_to_event
orbits

Opening this up to @ixfoduap to take a first look

Thanks @ixfoduap, have responded to your comments and made changes. Would like to open up to reviews from others now!


Make the text readable on monet theme generator

Check all the boxes below

[X] I have checked that this bug hasn't already been reported

Discord username
@<IP_ADDRESS>
Detailed Info
Text is yellow, background is also yellow
Steps to Reproduce
Install the plugin and try to read text
Crash Info
No response
Bug Screenshot
No response
System Info
Device: poco m3
Manufacturer: xiaomi
Brand: poco
OS: android 12 miui 14
Version: that one
Discord Branch: stable
Discord Version: latest one from stable idk
Discord Build: what
Vendetta Version: newest
React Version: surprised
Hermes Bytecode: no

I have also generated a theme from that generator, and the text comes out dark grey and barely readable.

https://github.com/nexpid/VendettaPlugins/commit/948c4ddb1b18b8ec4ca4a8907a30092729d3260c

how do i dl it tho


Add drag and drop functionality

Dragging an osu replay file into the browser having your website recognise the osu replay file and location will save me from having to browse to the file itself or make a copy to a more easily approachable folder just to be able to upload it.

I've added the drag and drop functionality. You can drag your file into the border dotted block.
I'm looking into adding some user feedback, like color when you drag the file into the box.


Missing LICENSE.md

In the website it says it's MIT but there's no LICENSE file included with the code. The only file under a license is src/index.js. Could you please specify what kind of license this work is under? Thanks

Hello, @system32uwu ! Thanks for using our products.I merged the PR.


Rendering multi-line equations in KaTex?

Can KaTex render multi-line equations? It seems that AMS Math mode is currently not supported. How can I render this multi-line equation in KaTex?
\begin{equation} \label{eq1}
\begin{split}
A & = \frac{\pi r^2}{2} \\
 & = \frac{1}{2} \pi r^2
\end{split}
\end{equation}

This is a great project, thanks for the help!

This relates with all other issues, for example: https://github.com/Khan/KaTeX/issues/206

Right – not yet, but we'd like to add it.

@spicyj  what does it mean "we'd like to add it"? What does it require to contribute a brand new functionality? I mean this require a lot of new stuff to introduce.

We haven't figured out a good cross-browser-compatible way to lay out equations in a way that would let us line them up to do multi-line equations. We've looked into couple approaches, but none of them have worked.
Right now, almost all formatting in KaTeX is done through CSS, and we only calculate heights of elements to do vertical alignment. Thus, to get multi-line equations to work, we have to figure out how to get CSS to do consistent-across-browsers horizontal alignment of elements in such a way that we can then vertically position the elements where we want them. Just based on what most browsers support and what CSS lets us do, the only feasible method for doing this is to use HTML s. However, due to browser differences and the semi-unspecified spec surrounding them, it's hard to find the right CSS magic to get everything to work.
Neither @spicyj nor I are working full-time on this, so we haven't been able to spend enough time on this to find a suitable solution, but we know people want this, and would like to add it in the future.

(Also, once we figure out how to actually do the layout, we need to change the parser to understand the funky syntax, figure out how the different kinds of alignment work, etc.)

@xymostech I see, but we are here too! Don't do it yourself, it's a community project, isn't it? :) My thoughts on this issue: Can you clarify what didn't work?

With #268 merged, is this issue easier to address now?

https://github.com/Khan/KaTeX/pull/268 will help a little bit with implementing any new command in KaTeX, but it doesn't provide a clear path forward in this case.

But this and #350 are fundamental to any serious math writing. Would there be a plan or a series of milestones for this kind of features, to help the community to participate and collaborate?

@xymostech

Just based on what most browsers support and what CSS lets us do, the only feasible method for doing this is to use HTML <table>s.

Is this a bad thing? HTML tables would be the way to go I guess (or CSS tables for that matter), or are there any problems with this approach?

@pnsaevik The problem with HTML tables is that the layout algorithm isn't actually specified, so it's really hard to get things to look correct in all the different browsers. Most of KaTeX is getting the layout of things exactly right, so having to deal with browser differences would be a huge pain.
As it turns out though, that statement is out-of-date and we did figure out a good way of solving this without the use of tables. :)

@xymostech your last comment gave me some hope! Could you update us on the status of this? Would love to help out any way I can.

@mull This has been solved! We now have various multi-line environments, like \begin{array} and \begin{aligned}. The code to render them is here: https://github.com/Khan/KaTeX/blob/master/src/buildHTML.js#L517 We basically stack columns next to each other to get the desired effect.

For simple posts:
{% katex %} equation_1 \\\\ equation_2 \\\\ equation_3 \\\\ equation_4 {% endkatex %}


Thank you

Thank you very much for the 3D autoencoder code. I'm a new starter of tensorflow, I want to build a 3d autoencoder and convolutional neural network. It's a very confusing for me to understand how to use your code, can you give me some explanations about the code? Much appreciated.

Sorry for the missing test/example code. However, this code is not working well in my case. In addition, some of the part can be used, but some part is deprecated in the current TensorFlow. Partial use is fine, but full use is not recommended.


iisexpress exits on configuration file load

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
I've looked and can't find the issue with process monitor.  Basically any time I have httpPlatform in my iisexpress config , iisexpress exits quickly with :
iisexpress /site:test /config:iisexpress-vs.config
Filename: \?\C:\test-fastapi\iisexpress-vs.config
Error:
So no error message.  I have no idea why.  Can you prepare a test-fastapi (or or test-flask case) with a complete iisexpress config and the V1 and V2 modules?
For python I'm using anaconda and I discovered you must disable identify profiles in IIS to overwrite the path variable and set it up like this:
      <httpPlatform
                processPath="C:\ProgramData\Anaconda3\python.exe"
                arguments="-m uvicorn --port %HTTP_PLATFORM_PORT% main:app"
                stdoutLogEnabled="true"
                stdoutLogFile=".\python.log"
                startupTimeLimit="20"
                processesPerApplication="4"
                >
                <environmentVariables>
                    <environmentVariable name="SERVER_PORT" value="%HTTP_PLATFORM_PORT%" />
                    <environmentVariable name="_CONDA_EXE" value="C:/ProgramData/Anaconda3\Scripts\conda.exe" />
                    <environmentVariable name="_CONDA_ROOT" value="C:/ProgramData/Anaconda3" />
                    <environmentVariable name="CONDA_DEFAULT_ENV" value="base" />
                    <environmentVariable name="CONDA_EXE" value="C:\ProgramData\Anaconda3\Scripts\conda.exe" />
                    <environmentVariable name="CONDA_PREFIX" value="C:\ProgramData\Anaconda3" />
                    <environmentVariable name="CONDA_PROMPT_MODIFIER" value="(base)" />
                    <environmentVariable name="CONDA_PYTHON_EXE" value="C:\ProgramData\Anaconda3\python.exe" />
                    <environmentVariable name="CONDA_SHLVL" value="1" />

                    <environmentVariable name="PATH" value="C:\ProgramData\Anaconda3\Library\bin;C:\ProgramData\Anaconda3\DLLs;C:\ProgramData\Anaconda3;C:\ProgramData\Anaconda3\Library\mingw-w64\bin;C:\ProgramData\Anaconda3\Library\usr\bin;C:\ProgramData\Anaconda3\Library\bin;C:\ProgramData\Anaconda3\Scripts;C:\ProgramData\Anaconda3\bin;C:\ProgramData\Anaconda3\condabin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\CCM;C:\Program Files\dotnet;C:\WINDOWS\System32\OpenSSH;C:\Program Files\nodejs;C:\Program Files\TortoiseSVN\bin;C:\Program Files\PowerShell\7;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH" />
                </environmentVariables>
            </httpPlatform>

Expected Behavior
iisexpress starts and python is happy
Steps To Reproduce
No response
Exceptions (if any)
No response
HttpPlatformHandler Version
No response
Anything else?
No response

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@lextm hey are you able to have the handler work with iis express as an example or otherwise know what the issue is?

New issues are marked as low priority by default. Becoming our commercial customers, and then your reports are handled with higher priority after triage.

seems like something that should just go in documentation though and might apply to the v1 handler as well.  I mean I can ask on stackoverflow as well though it does seem like you have one of the best understandings of this corner of iis; but the consulting case for an config example is pretty low.  Anyway response rate is pretty consistent with the rest of github so far lol

We couldn't reproduce this. The FastAPI sample works fine on our test environment with IIS Express.


[FY25.1 Sprint 2] Add 3-7 additional flight maps to CASEI

This issue follows https://github.com/NASA-IMPACT/admg-casei/issues/636
Context
Back in FY24.1, we started visualizing flight paths for campaigns on CASEI. We started with 5 (see epic: https://github.com/NASA-IMPACT/admg-casei/issues/576) and have since expanded to ~8 (see YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR).

Example of a flight map for a campaign
As of FY24.4, we have published 44 campaign flight paths.
Known Challenges
We learned through past efforts in trying to automate the data collection and visualization process that currently it is NOT possible to fully automate this process for these reasons:

Inconsistent data formats as in NASA's case airborne data ownership is split across 12 DAACs that all do things a bit differently
Different ways to define measurement variable names. This might not seem like a big deal but it really makes it hard/slow to get buy-in when building out features quickly as terminology is for queries and UI filters gets challenged back and forth. There are initiatives on streamlining language, for example the official GCMD science keywords (which is a string of keywords) but each DAAC also has their own views and it’s an ongoing discussion.
Incomplete data. To get the full set of historical data to even visualize flights (let along instruments on each flight deployment), in many cases you’ll need to manually look for data that’s lock in PDFs still or old canned films for example that are not digitized. This is what the ADMG data curators have been doing and filling in for CASEI

Goal

We will continue to collect and visualize campaigns in batches (of around 3-6) because each campaign may need some manual data fixes.
We will incorporate fixes to common data issues along the way, and continue to learn about the extent to which we can still create a pipeline for visualizing nav data in the cloud without having to do it locally and save out GeoJSON files

Acceptance Criteria

3-6 additional nav data sets saved as YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR
Static locations for those campaigns https://docs.google.com/spreadsheets/d/17v-ZfeWoPZoCAVSs57Y3Q1gKUe6S49fZ8rC2KOO_myY/edit#gid=1924471089
3-6 flight tracks visualized and deployed to CASEI in staging
Deploy from staging to production

@als0076 I've processed two new campaigns:
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/NAAMES/
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/ORACLES/
Let me know if the data looks correct.

@willemarcel both look good!

@als0076 I've processed 2 new ones:
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/SOLVE
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/SONEX

@als0076 I've processed some additional campaigns, could you take a look?
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/STRAT
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/INTEX-NA/
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/KORUS-AQ
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/KORUS-OC

@willemarcel all look good!

Closing this issue. The campaigns will be deployed to production in a few days.


Update homu revision

This fixes #903.

This change is

@bors-servo r+

:pushpin: Commit b7029a6 has been approved by jdm

:hourglass: Testing commit b7029a67296dfec647edb69791794a6d01745c37 with merge 5dcb05a3d75430f3f8a2d78c4485bf0c2494059c...

:broken_heart: Test failed - status-travis


Crash Release Android x86

This bug is reproducible when you generate the app using in release mode and you open it in an x86 or arm32 emulator
If you are having issues opening an app on your x86 or arm32 emulator, you may be seeing the following error message: "{AppName} consistently crashes". This may be caused by the fact that Flutter does not support x86 files, as mentioned in this link: https://docs.flutter.dev/deployment/android#what-are-the-supported-target-architectures. According to the documentation, Flutter currently does not offer support for generating x86 files for Android (see Issue 9253).
This can be a particularly problematic when you are trying to use packages that depend on resources such as the camera or MLKit. To resolve this issue, you can edit the 'build.grandle' file in the 'app' folder and add the following lines to prevent the generation of x86 files:
   defaultConfig {
        ndk {
            abiFilters 'armeabi-v7a','arm64-v8a','x86_64'
        }
    }

This should help resolve the issue and allow you to open the app on the emulator without errors. It is important to remember that Flutter currently only supports the armeabi-v7a (ARM 32-bit), arm64-v8a (ARM 64-bit), and x86-64 (x86 64-bit) target architectures. Therefore, when editing the 'build.grandle' file, it is important to ensure that you are only including these architectures.

Are you still using this plugin? What kind of issues are you currently facing in production? @rod-moraes


http://chyrp.net/ is a dead link

Not quite sure what this PR is for, but I don't maintain that site anymore.


[SourceKit] Pass 'swiftc' path to Driver when creating frontend args

Driver uses its path to derive the plugin paths (i.e. 'lib/swift/host/plugins' et al.) Previously it was a constant string 'swiftc' that caused SourceKit failed to find dylib plugins in the toolchain. Since 'SwiftLangSupport' knows the swift-frontend path, use it, but replacing the filename with 'swiftc', to derive the plugin paths.
rdar://107849796

@swift-ci Please test

https://github.com/apple/llvm-project/pull/6633
@swift-ci Please smoke test

@swift-ci Please test


Typescript ignores package.json export maps

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.90.1
OS Version: macos 14.5

Steps to Reproduce:

mkdir meth && cd meth && npm init -y && npm i micro-eth-signer && touch a.mjs
Open a.mjs and enter import * as net from 'micro-eth-signer/net'; or any other module. VSCode would not see the module even though it's clearly specified in pkg.json
Doesn't matter which tsconfig is used, i've tried all options (moduleResolution, module, whatever)

I maintain many libraries and I export their functionality in sub-modules instead of importing everything into one big index.js file. This is useful and helps with tree-shaking. Seems like vscode doesn't support export maps in node.js.

What are you expecting to see? This is what I get:

Without any more info, I'll point out the following information about the package from https://arethetypeswrong.github.io/?p=micro-eth-signer%400.9.1

| "micro-eth-signer" | "micro-eth-signer/abi" | "micro-eth-signer/net" | "micro-eth-signer/rlp" | "micro-eth-signer/ssz" | "micro-eth-signer/tx" | "micro-eth-signer/utils"
-- | -- | -- | -- | -- | -- | -- | --
node10 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅
node16 (from CJS) | ✅ (CJS) | ✅ (CJS) | ✅ (CJS) | 💀 Resolution failed | 💀 Resolution failed | ✅ (CJS) | ✅ (CJS)
node16 (from ESM) | 🎭 Masquerading as CJS | 🎭 Masquerading as CJS | 🎭 Masquerading as CJS | 💀 Resolution failed | 💀 Resolution failed | 🎭 Masquerading as CJS | 🎭 Masquerading as CJS
bundler | ✅ | ✅ | ✅ | 💀 Resolution failed | 💀 Resolution failed | ✅ | ✅

Under node16, ESM files will think that you're trying to import a CJS file (because they resolve to a .d.ts file). See here.

@DanielRosenwasser this looks very useful, thanks. I will fix "masquearading". RLP and SSZ modules are failing because of a typo from my end.
Here's another package of mine:
https://arethetypeswrong.github.io/?p=micro-key-producer%400.7.0
It says "💀 Resolution failed" for all node16. I assume this is simply because cjs files are located in lib subdir and node10 can't find it. So until node10 resolution is deprecated (unclear when that happens), we are forced to not use clean structure with "all files are in subdirs".
Now, the question is: which module resolution does typescript currently enforce by default? Is it node16? I mean, for the situation when there is no "tsconfig", and a random JS file is checked.

https://www.typescriptlang.org/docs/handbook/modules/guides/choosing-compiler-options.html has good info on how to set up libraries
The default module mode in JS is I believe "classic" but I'd have to check the code. It shouldn't really matter; compliant projects that work in node16/etc will also work in legacy modes


[ Bug ] After module update modulegets listed twice with the old version

Describe the bug
After updating a module the module is shown twice in the list.

To Reproduce
Update a module with the new version 1.7.0
Expected behavior
Plugin is not displayed twice but only once and with the new version number.
Screenshots

System:

OS: Ubuntu
Node: v16.7.0
Prod Tool Version: 1.7.0
Observer Tool Version: [e.g. 1.0.0]
Streaming Software & Version: (If it is a problem while streaming or testing)
Browser: [e.g. chrome, safari]

Fixed with v1.7.1


Functional Dependency Injection

Today TickSpec slightly fails in the functional approach as it is hard to avoid mutable fields and you can't make easily steps as a module with tick functions (without class) when you want allow parallel tests. Also as you use more field read/write approach instead of more pure function approach in steps the code overall is less functional.
I think I have fixed that by allowing a new style of writing steps:

Step functions can have a return value. When a value V of type T is returned then the V is registered to container under type T. If next time other function returns value X of the same type T then V is replaced by X
Functions can have more arguments. Any extra argument is resolved using dependency container

This new style of coding should not affect the other styles. The only cons I can think of is that if you want to write by the old style and you make a mistake (extra argument or unintentional return of a value) then it may be slightly harder to catch it.
This pull request contains these other pull requests:

Dependency Injection
VS2017
NUnit via Paket

As discussed in the other PRs, this holds lots of promise but

we need to do one thing at a time
we def need to get stuff compiling in 2017, move to paket and in-date NUnit
we need to not add extra deps / complexity to core that's avoidable
we need to make sure we can generate NuGet packages along the way
for this DI approach, I went to look a the diffs (I have had similar thoughts in the past), but

there are some changes I hope can be avoided (and stuff that's under discussion with with mchaloupka in #2  - we need 'more real' examples) which make it hard to see the forest for the trees
for me, it's all about proving >1 person has made this work in practice - there's little point in just merging it until we get to that point so it may be valuable for others to work off this branch and converge on an approach
based on these two points I've yet to dig in in depth; please don't consider this a no - I have not even looked in any meaningful way.

As noted, I'm a bit busy to shepherd this this month unless we work in very small steps.

I have updated the pull request to contain up-to-date @mchaloupka Dependency Injection changes. I have created a copy of his feeding dog example to functional injection examples and converted it to the functional injection style - it gives a nice comparison. I have also added the standard Stock example in FI style to compare. More, I also updated readme to contain that style as extra option as I think it is better default for F# coding? What do you think @bartelink ?

The example in the readme looks great. Will look at code in due course (diffs are not showing clearly atm)

I have merged Milos's last changes again and I have fixed the line feed, so diff should be good now

Have not had time to look today. Am I correct in inferring that you are happy to finalize your stuff after we finalize and merge Milos's ?
If you feel your work on this in any way helps with deciding 50/50 calls in the other PR, the more you feed in there the better (but the fact you are basing off his is likely to have already validated that to a large degree)

Sure, let's first merge Milos's PR first, I am already fine with what he did, he adjusted his version so that I don't have any change to the ServiceProvider.fs - I just reused his DI for different purpose.

Closing as this branch is already merged as part of other pr.


Quickest way to add pagination?

Hey, wondering if the package comes with a quick/fast way to add pagination before I start coding. Thanks!

#160 159 #40


create CONTRIBUTING.md

@lyzidiamond once said in a PR that we should make a CONTRIBUTING.md file for this. I think it is time!

:+1:
I'd suggest using https://github.com/jden/CONTRIBUTING.md as starting point.

Ooh, I like this one, too.
https://github.com/CoralineAda/contributor_covenant.

Thanks for the templates, @npeihl - I really like this code of conduct piece from the contributor covenant.

@lyzidiamond I'd like to see some examples of what contributing looks like (specifically non-code related contributions). For example, "drawings of new navigation buttons" or "need help creating example data" or "think about color scheme".
Similarly, defining what is a contribution? and making it clear that writing code is not the only path towards a successful contribution. Explaining what a meaningful contribution looks like is important! Things like "asking questions" or "requesting features" are equally powerful as creating those features.
THIS IS WHAT DEMOCRACY LOOKS LIKE

Some feedback from @hamhands - he wants to contribute but the issue list is a bit overwhelming. Might be worth maintaining a list of comfortable, small tasks in the file so people can start there?

Also, when we ask for code-related contributions how do we expect people to merge into the proper working branch? Should we always assume contributions come into the master branch or do we always state where the current development branch is (i.e. 0.1.1 currently)?

Sorry, big brain dump happening right now:
Talking to someone after the presentation at NACIS, they mentioned they were at the CUGOS Spring Fling last spring and enjoyed being a part of the project during the day, but weren't sure how to continue contributing after the fact. I'm not sure if there is a tangible way to answer this issue, but it reminds me a lot of what @lyzidiamond has been talking about with "post user experience" - how do we establish a positive "post contributor experience"?

This looks like a possible way to encourage new contributors. http://yourfirstpr.github.io/

I've started a CHANGELOG in the wiki - so we should include updating this as part of the code-related contributions.

Looking at this, I'm wondering if we should just move the CHANGELOG (along with install instructions and possible other code-related instructions) into actual files within the repo.  That way, the documentation would reflect the state of the codebase at any given revision (ie, CHANGELOG would immediately show which changes are within the current checked out revision).  Part of PR requirements could be adding the information to the CHANGELOG.

@mapsam regarding beginner-friendly issues, should we start tagging issues as beginner-friendly if they don't require significant refactor?

I like the idea of the changelog going into the project files - just didn't want to do it haphazardly without hearing someone else say it first. :+1: for someone to do that if they want. Could be the first flagged beginner-friendly issue?

Nice, thanks @alukach!


EmptyLine rules for it and context blocks

There are EmptyLine rules for several test constructs like describe and subject, but not for it blocks and context blocks. It would be nice to be able to enforce consistency around these as well. For example:
# bad
it 'does a thing' do
end
it 'does another thing' do
end

# good
it 'does a thing' do
end

it 'does another thing' do
end

Similarly for context blocks:
# bad
context 'when it is true' do
  it 'does a thing' do
  end
end
context 'when it is false' do
  it 'does another thing' do
  end
end

# good
context 'when it is true' do
  it 'does a thing' do
  end
end

context 'when it is false' do
  it 'does another thing' do
  end
end

It seems that an empty line after context is covered by EmptyLineAfterExampleGroup.
I believe a new cop, EmptyLineAfterExample would be mostly a copy-paste from EmptyLineAfterExampleGroup:
-return unless example_group?(node)
+return unless example?(node)

and describe/context replaced with it/specify in spec.
Would you be interested in such a contribution?

@pirj it was already commented in #272
EmptyLineAfterExample is one of the planned cops, actually, the only one left to solve #272 completely. I'd love to have it an option not to require empty line between single lines examples though.

@pirj I can add it to my todo list, though I don't know if I'll get a chance in the near future.


Migrate Jira plugin to http4s

Motivation
The Jira client depends on akka for some of its model so we need to migrate it to http4s

The Jira plugin has been removed as Jira supports now OAuth 2.0


Hebrew translation issues

TODO

[ ] PNG-frontend has no Hebrew font
[ ] Wrong script direction in browser

Original issue
no hebrew font characters would show but squares instead
i.e.

Is it terminal or is it browser?
That how how it looks like in my terminal:

and in my browser:

I suppose that in your case it is terminal, and your terminal simply has no Hebrew font.
Or is it PNG?

By the way, in the browser (pic 2) the script direction seems to be wrong?

it's PNG
and yes, second picture is in wrong direction

Thank you for reporting! Accepted. As soon as I have any news, I will update the issue


Unify append prepend

Some unification for append and prepend. Adresses #13

I didn't test this much but it compiles.


Update npm packages #1376

closes #1376
For the Submitter
Tasks

[x] Make sure "closes (issue number)" is written close to the top
[x] Attach the enhancement label for update tasks
[ ] Make sure CI completes successfully
[x] Check everything written in the PR
[x] Fix the issues pointed out by AI
[x] Add reviewers
[x] On Slack, mention the PR reviewer, write your thoughts on the issue, and inform them that the PR has been created

For the Reviewer
Before Reviewing

[ ] Write which PR you are reviewing on Slack

Checks

[ ] Each task for the related issue are written and in checkboxes
[ ] The branch name is close to the issue name
[ ] CI completes successfully
[ ] Changes include only what is necessary for this PR
[ ] Necessary unit tests are implemented
[ ] Necessary E2E tests are implemented
[ ] Perform functionality checks
[ ] If there are any problems, request revisions from the PR submitter and mention them on Slack

After Reviewing

[ ] Leave an approval comment (e.g. LGTM)
[ ] On Slack, mention the PR submitter and a project admin, write which PR you have reviewed, and ask them to merge the PR

@akamini

[ ]  CI が すべて pass することを確認し、PRの Make sure CI completes successfully にチェックを入れる。 → 途中で止まっているのですね。こちらチェック付けなくて大丈夫です！
[ ]  PR の Assigneers にご自身を追加する


Magento subdirectory

[ ] Bug fix #…?

[x] New feature?

[ ] BC breaks?

[ ] Tests added?

[x] Docs added?
Please, regenerate docs by running next command:
$ php bin/docgen

Am I blind or is {{bin/magento}}}not defined? Is the value the default? 🤔

you found it :) #3460

I merged this into https://github.com/deployphp/deployer/pull/3460, works better as a single PR


How can i search a numeric field?

How can i search a numeric field ?
i can use TermQuery to search a text or keyword field, but it seems not support numeric field.

To search a numeric field, you should use the NumericRangeQuery:
https://github.com/blugelabs/bluge/blob/f34c4accbd91d52d6896d1dbab744987c9e71450/query.go#L1095
or
https://github.com/blugelabs/bluge/blob/f34c4accbd91d52d6896d1dbab744987c9e71450/query.go#L1103
Also, here is a test case.  It isn't the best example, because it's trying to illustrate/test something else, but it does index a numeric field, and query it by range: https://github.com/blugelabs/bluge/blob/f34c4accbd91d52d6896d1dbab744987c9e71450/search_test.go#L1275-L1327

thanks, it's ok to use RangeQuery can search numeric range.
If i want to search a fixed value, likes Year: 2020, is it possible to use termQuery for numeric?

It is technically possible to search for a single value using a term query, but you are using details of the implementation that are not guaranteed to work in the future.  Specifically, in the future, we plan to use a more space-efficient encoding of the numeric fields index.  When we do that, term query would stop working to numeric values, but the NumericRangeQuery will be updated to work with the new implementation.

okay, thank you.


zsh - no custom prompt

I am running Python 3.5.2, Ubuntu 16.04 and zsh 5.1.1.
I can create a new virtual environment fine, but running 'hatch use <env_name>' does not activate the environment - It doesn't throw any errors either, it just doesn't activate.

Can you please show your terminal session?

TERMINAL SESSION:
➜  ~ hatch env -ll
No virtual environments found in /home/shubh/.local/share/hatch/venvs. To create one do hatch env NAME.
➜  ~ hatch env test-env
Already using interpreter /usr/bin/python3
Successfully saved virtual env test-env to /home/shubh/.local/share/hatch/venvs/test-env.
➜  ~ hatch env -ll
Virtual environments found in /home/shubh/.local/share/hatch/venvs:
test-env ->
Version: 3.5.2
Implementation: CPython
➜  ~ hatch use test-env
➜  ~

@shubhg1996 It might be that it worked but Hatch was unable to change the prompt. Please try hatch use test-env again and show me the output of python -c "import sys;print(sys.executable)".
For me I get:
ofek@ozone:~$ python3 -c "import sys;print(sys.version)"
3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609]
ofek@ozone:~$ uname -v
#37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017
ofek@ozone:~$ zsh --version
zsh 5.1.1 (x86_64-ubuntu-linux-gnu)
ofek@ozone:~$ hatch use -s zsh fast
(fast) ozone% hatch use -s zsh old
2 (old) ozone% exit
(fast) ozone% exit
ofek@ozone:~$

Actually you are right. The virtual env is working (should have tried this before posting the issue).
➜  ~ hatch use test-env
➜  ~ python -c "import sys;print(sys.executable)"
/home/shubh/.local/share/hatch/venvs/test-env/bin/python
Thanks!

➜  ~ echo $PROMPT
${ret_status} %{$fg[cyan]%}%c%{$reset_color%} $(git_prompt_info)

and inside env?

That was from insude env.
its same from outside as well
➜  ~ echo $prompt
${ret_status} %{$fg[cyan]%}%c%{$reset_color%} $(git_prompt_info)

I'm not sure why https://github.com/ofek/hatch/blob/22e621715fbed36c2bfab35ae9fa9649ea6dfe1e/hatch/shells.py#L76 isn't working for you, but I'll look into it. Thanks!


Please support gRPC Service

gRPC Service does not work.
Here is an example.
server yaml.
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: grpc-ping
  namespace: default
  labels:
    networking.knative.dev/visibility: cluster-local
spec:
  template:
    spec:
      containers:
      - image: kahiro/grpc-ping-go:latest
        ports:
          - name: h2c
            containerPort: 8080

client yaml.
This is an error.
apiVersion: v1
kind: Pod
metadata:
  name: grpc-ping-client
  namespace: default
spec:
  containers:
  - args:
    - /client
    - -server_addr
    - grpc-ping.default.svc.cluster.local:80
    - -insecure
    image: kahiro/grpc-ping-go:latest
    imagePullPolicy: Always
    name: grpc-ping-client

client yaml.
This works.
apiVersion: v1
kind: Pod
metadata:
  name: grpc-ping-client-pod
  namespace: default
spec:
  containers:
  - args:
    - /client
    - -server_addr
    - 10-0-3-236.default.pod.cluster.local:8080
    - -insecure
    image: kahiro/grpc-ping-go:latest
    imagePullPolicy: Always
    name: grpc-ping-client

The difference between the two above is that they go through a Gateway configured with HTTPRoute or not.
TCPRoute or GRPCRoute must also be used.
https://gateway-api.sigs.k8s.io/concepts/api-overview/?h=grpcroute#route-resources

I love cilium.
https://github.com/cilium/cilium/issues/20655

Keep

Keep

Hey @kahirokunn in the last few weeks we added the necessary changes to serving and net-gateway-api so in theory you could try testing with Cillium to see if it's working. If you could circle back let us know.
Internally we now use the kubernetes.io/h2c appProtocol constant to signal to gateways to use h2 prior knowledge.  If Cilllium supports this then it should work.
I'm going to close this out since we have this working with Contour and Istio and there's no action left for us.

I PR'd a backend protocol test here - https://github.com/kubernetes-sigs/gateway-api/pull/2456

Thx!!


Add missing yaml output annotations for antctl

Add YAML annotations for agent-info and controller-info.
Signed-off-by: Weiqiang TANG<EMAIL_ADDRESS>

Should we change the CRD struct as well?

I think only the response struct could affect the output format, thus we don't need to update CRD structs.
But it looks like that we can not annotate some fields, like the PodReference. I'm going to figure out a way to let the YAML encoder to follow JSON annotations.

/test-all


fix: Propagate tags to pip-compile rule

This can be usefull if the user wants to disable the test

Releasing in v0.6.0.


Add awesome-kubernetes link

Hi @Moshe-Immerman. Thanks for sharing. As you may have noticed that your suggestion is already listed on [L354]. As it's already listed as a hint under the category 'Remote Container Manager / Orchestration', we should leave it as it is. What do you think?

sorry - I did miss that, although I think it should be at the top (alphabetically and logically) of the section

@Moshe-Immerman duplicate link : https://github.com/ramitsurana

@Moshe-Immerman well done


Overflow: visible

Material design features a lot of overflowing ui elements, I love your modal except that that overflowing fab buttons didn't work without adjusting this rule.

👍LGTM, not sure what purpose that rule had in the first place, smells like an old hack. Shouldn't need overflow visible explicitly set though since that's the default value.
I need to refactor this into a Polymer 2 element anyway, so happy to merge as is.

also need to build to dist

I might just leave this and make this patch when I refactor soon

thanks!


Type errors when importing legacy typeorm adapter

Getting a Module '"@next-auth/typeorm-legacy-adapter"' has no exported member 'TypeORMLegacyAdapter'. when importing the adapter:
import { TypeORMLegacyAdapter } from "@next-auth/typeorm-legacy-adapter";

will need a bit more info

This is straight from the docs
This works, but we'd missing typings?

I meant reproduction, package versions, etc.

Here's mine
<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>
  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>deduped
  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>deduped

It looks like this function was declared but not in index.d.ts
https://github.com/nextauthjs/adapters/blob/fae5c50d3accac2c4b380f456ef5ffe96402df6b/packages/typeorm-legacy/src/index.js#L13

I meant reproduction, package versions, etc.

    "@next-auth/typeorm-legacy-adapter": "^0.1.4",

Ok I definitely mixing up between v3 and upcoming v4.
@fandy probably you have the same problem with me 😅 installing next-auth@beta and @next-auth/typeorm-legacy-adapter@next works to me but I have to do some refactor from now.

I see. Not sure I want to put any effort in the current adapter, but I'm open for PRs for a fix.
The new version of the Adapter is completely rewritten in TypeScript already: https://github.com/nextauthjs/adapters/tree/next/packages%2Ftypeorm-legacy

Ok I definitely mixing up between v3 and upcoming v4.
@fandy probably you have the same problem with me 😅 installing next-auth@beta and @next-auth/typeorm-legacy-adapter@next works to me but I have to do some refactor from now.

Yeah actually just found this solution in the docs (though it's not very visible). @balazsorban44 imo the docs can be more clear by referencing next-auth/typeorm-legacy-adapter@next in the v4 docs. Right now it's easy to miss.

@fandy there is a quite visible warning in the migration docs that you will have to use @next
https://next-auth.js.org/getting-started/upgrade-v4#adapters

I remember few weeks ago somehow the documentation has suddenly changed during my first encounter with next-auth. Got a lot of problem that I'm mixing stuff already to this today! I though it's only a small fixes 😅 boy I am so wrong.

We added a banner to the top when changing the default docs to the new version. 🤔
We added a version selector to every page.
And also a migration guide.
Genuine question, how could we make it more obvious which version of the docs someone is looking at? I've seen many people encountered similar issues, seemingly confused by which version they are trying. 😕

We added a banner to the top when changing the default docs to the new version. 🤔
We added a version selector to every page.
And also a migration guide.
Genuine question, how could we make it more obvious which version of the docs someone is looking at?
I've seen many people encountered similar issues, seemingly confused by which version they are trying. 😕

On https://next-auth.js.org/adapters/typeorm it recommends installing the version without next, which is the most prominent instruction. I don't see a banner which recommends the @next version, but would it even be necessary if we had the install instructions listing @next?

I see. I kind of assumed that people using v4 will automatically go to the migration docs, where the the info about adding @next to adapter installations is very prominent in my opinion. We kind of intended to compress all necessary info into that page, but it looks like people don't really look at it. Most of the recent issues were people not reading it.
I might have been wrong, we might just want to maintain all the beta related changes on all pages for a while. 🤷♂ It creates a bit of extra work, but I don't see a better solution.

I see. I kind of assumed that people using v4 will automatically go to the migration docs, where the the info about adding @next to adapter installations is very prominent in my opinion. We kind of intended to compress all necessary info into that page, but it looks like people don't really look at it. Most of the recent issues were people not reading it.
I might have been wrong, we might just want to maintain all the beta related changes on all pages for a while. 🤷♂ It creates a bit of extra work, but I don't see a better solution.

Yeah that would be a safe way to eliminate the incoming issues, but even just using @next on the main install instructions would be huge. Some users might not be past users of v3, or starting a new project, so they would skimp past migration docs as they are unnecessary.
Ideally we would have all new setup instructions on v4 main docs and all changes on migration docs.

I am curious if this banner doesn't show up on some devices, or is not prominent enough?

It is supposed to be shown across the WHOLE site.
BTW in the current state, for the core, you would need @beta, only the adapters will need @next. I didn't bother to add YET another distribution tag for adapters, as it already seems to be hard to follow. 😅

I forgot to include the banner in the screenshot, but yes it's showing for me.
Imo that's what makes it confusing - it's telling you that you're viewing the correct instructions for v4, but the installation instructions are outdated. Am I missing something here?

I am curious if this banner doesn't show up on some devices, or is not prominent enough?

To my experience, it's visible enough. But my problem is I'm not aware i'm using v3.x at that time. And to make it worse i'm not even aware these new features are exclusive to @next. Yesterday I keep switching between adapter and database option in config because i'm confused for a whole day why adapter option didn't work to me.
I think it all comes with sudden documentation change. Imo URL's should not change just because there's new major release. Weirdly enough, to me this dead doc URL is still on top of my address bar suggestions.
Some large software libraries like Bootstrap or Nodejs already prefix their documentation with software version even if it's the latest. But anyway this are just my thought out of thin air, many software docs don't follow this convention probably because it's easier to do with.

@balazsorban44 maybe put some WARN if database option is used in v4?  probably a lot of people in future will just copy tutorials old in old versions not realizing it's outdated 😅

The docs versioning has been put in place from v4 onward. We didn't have versioning before that. I think our strategy is to not use the version for the most current release for probably SEO reasons. @ndom91 do you have a better explanation?
One mistake I probably made was not including the migration guide in the top banner, which is being fixed in https://github.com/nextauthjs/docs/pull/31
It will look like this:

We honestly don't do anything fancy with the tools we are given, we use Docusaurus for docs, and trying our best at semantic versioning. That said, it is my first release of this scale and I learn myself along the way.

@willnode database is gone in v4: https://docs-git-fix-make-beta-more-prominent-nextauthjs.vercel.app/getting-started/upgrade-v4#adapters


Override default routes

Is it possible to override/change the default routes generated?
We have an existing client side app that points new user registrations to <path>/register and logins to <path>/login and would like to not touch that code as much as possible.
In standard devise, you would use devise_scope;  is that the support means with this gem?

Yes, you can use devise_scope to change the routes..

Workaround posted, closing issue


use addRawHeader since setRawHeader overwrites the previous Set-Cookie

There appears to be a bug in Plug when multiple Set-Cookie headers are sent in a response.  Calling addRawHeader overwrites the previous header and the previous header.  I think this code is correct but please let me know if anything is wrong.  All the tests still pass against the local httpbin container but let me know if I've done something wrong or there's a better fix.
On an unrelated note, what's the purpose of the special case for HTTP/1.1?
if((new StringEx($header))->startsWithInvariantCase('HTTP/1.1')) {

Should this also include HTTP/2?
Thanks @modethirteen!

@PeteE I think what you meant was that calling setRawHeader in Plug overwrites a previous Set-Cookie, and using addRawHeader preserves all Set-Cookie headers. With regards to HTTP/2, I do plan to support it in the 2.x version.

@PeteE I think what you meant was that calling setRawHeader in Plug overwrites a previous Set-Cookie, and using addRawHeader preserves all Set-Cookie headers. That special case is to extract the HTTP status code. With regards to HTTP/2, I do plan to support it in the 2.x version.

Oops, you are correct.   I said that incorrectly!

@PeteE can you rebase with the latest 1.x branch? GitHub upgraded the virtual environment for actions (so tests aren't passing) and I have to downgrade it for this legacy version branch.


Adventure Time Parallax effect

Hello I've been trying to recreate the parallax effect as seen here: https://codepen.io/airnan/pen/NjayEE using simple shapes.
Everything seems to be working fine: mouse position/distance registering and calculating correctly, but for some reason the camera is not registering.
I think it has something to do with the fact that my camera object has been rendered differently and is missing some information:
http://imgur.com/Obc0JFJ
therefore i cannot set these parameters correctly:
http://imgur.com/Lzc5e4u
Can you please check out what I am missing?
I've included .zip with AE project and code.
http://www117.zippyshare.com/v/idpnn5rI/file.html

Still haven't found the answer. All it would take is the people who worked on that Adventure Time project to share the camera layer specifications or even share the project in a prive message and I could close this issue.

So I made it work by replacing my json camera object code with the raw camera object code of original project's json file, but I understand that's really not a propper way to do it :D.
Still, if someone knows why my camera layer is rendering differently I would be really grateful.

Hi, can you share your file via WeTransfer?

Hi,
I'm having the exact same issue. I'm trying without animations and a default camera. Animating the camera or not, the end result is the same. I can't seem to get the camera working, just as @azun1te described.
I tried exporting as many times and I had an idea, and finally had the idea to copy and paste the camera settings from the JSON from Adventure Time, and it works.
I think that by having the original AEP file I could better understand why my project is failing.
I have done exactly the same as the OP did, from the original editing, to copying the camera. But I'd love to know exactly why, and I think the original AEP would solve that.
My file is here: https://www.atlantidastudios.com/peu.aep

Nice! So you've figured out how to make it work?

After seeing the original After file I understood how to make it work.
As @azun1te mentioned, the issue is that the camera object, when we export from AE it does not contain the data structure required to make the desired 3D effect IF the camera has no animation.
If the camera has an animation, it doesn't allow for it to be changed programmatically it's the angle and position, because the camera's animation override any change we make on it's position.
The only way I came up with it working was to allow the camera has to animate a VERY SMALL amount between TWO REALLY DISTANT frames. After you setup the camera like that, you can change the camera's ks.p.k.s and ks.p.k.e
Also the camera has to animate from the very first frame to the very last frame.
With those things in mind, when you export the AE project, you'll be able to change the camera's position programmatically.

Hi ! Thank you @bodymovin for your work and this fantastic tool.
I'm trying to reproduce the parallax effect in your aventure time animation. After a lot of try to modify AE properties without destroy and reload animation, I found the solution with this interesting post. It functions now when I modify two keyframes with a small amount between them, but I wonder if it would be possible to access AE properties without add keyframes. Are there technical issues that make that complicated ?

@Numeo Any property that doesn't have keyframes is calculated only once in order to improve performance by skipping unnecessary checks.
That's why this workaround is needed to update values.


Cipher and Decipher a Property in Object

cipherTerminal: cipher a terminal (string or string array).

decipherTerminal: decipher a terminal (string or string array).

cryptoProp: cipher or decipher in-place a property of an object.

expects: path (string) of a property, document (Record<string, any>) is the object, key (Buffer), ivSeed (string),  terminalMode (typeof cipherTerminal & typeof decipherTerminal)
returns: -

testing includes an object with:

string and string[]
nested object with string and string[]
array of objects with string and string[]


Reference Envoy version in Istio release note

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Envoy is the critical data plane component for Istio. Envoy changes directly impact application at runtime. Currently it's difficult (although not impossible) for track the version of Envoy proxy being used by each Istio releases, hence it's difficult to plan/track the impact of Istio upgrade caused by Envoy change.
Describe alternatives you've considered
Suggest reference Envoy version in Istio upgrade note, and promote user awareness of potential impacts caused by Envoy upgrade.
Affected product area (please put an X in all that apply)
[ ] Ambient
[ x ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

please checkout https://github.com/istio/istio.io/pull/12579

Closed by https://github.com/istio/istio.io/pull/12579. Please re-open if more info is needed. We also had https://istio.io/latest/docs/ops/diagnostic-tools/proxy-cmd/#what-envoy-version-is-istio-using in the past.


add option for preferring Greek or Hebrew origin of Bible texts

Since most Catholic versions of the Bible offer both Greek and Hebrew versions of certain Bible texts (such as the Book of Esther), the API now accounts for this by offering a new parameter preferorigin.
We need to account for this when retrieving a quote by giving the option to prefer the Greek or the Hebrew origin. We can add a switch to the InspectorControl panel for the Bible quote block.

fixed in commit 7e2afa1a570e26c3b333a39c69e610ab1665b951


feat: add an environment variable to specify private key location

What was wrong?

How was it fixed?
By adding an environment variable TRIN_PRIVATE_KEY_PATH which overrides the default trin directory if provided

I took a shot at your concerns, ready for another look and let me know if I missed anything


Fix dev workflow

Add --hyperkube-tag (or -t) on kube-spawn create to specify which hyperkube Docker image to use. This is useful to compile different versions of Kubernetes and test them in parallel. doc/dev-workflow.md explains in more details how to use it.
kube-spawn will start a registry container and push the hyperkube image there under the name <IP_ADDRESS>:5000/hyperkube-amd64:$TAG. Then, kubeadm will pick that image.
Use the unifiedControlPlaneImage option in the kubeadm configuration file (>= 1.8) in addition to the old environment variable $KUBE_HYPERKUBE_IMAGE (< 1.8). This means --dev cannot be used anymore on 1.7 branches, but the 1.7 releases still work so it should not be a problem.
The dev workflow is now documented in doc/dev-workflow.md
Fixes https://github.com/kinvolk/kube-spawn/issues/188

TODO

[x] needs rebase after #222 is merged
[x] pkg/script/kubeadm-config.go should only add unifiedControlPlaneImage with --dev

/cc @blixtra

Description updated. PR ready for review.

really cool 👍

Thanks for the reviews. I merged it.
To improve further the documentation, we could do the following:

[ ] add a schema showing the workflow

[ ] explaining how the hyperkube image is tagged and is pushed between the registries
[ ] in the two scenarios (local build and fetching hyperkube image manually)


[SDP-1369] FE changes for registration types

What
Initial FE changes for the new disbursement registration flow:

[x] Remove everything that relies on country when parsing responses
[x] Make disbursement.verification_type optional
[x] In the “Wallets Provided” section, display a flag stating if the wallet is user_managed
[x] Update the disbursement details screen with the verification_type and registration_contact_type fields

Why
Partially address https://stellarorg.atlassian.net/browse/SDP-1369
Pending (for the next PR)

[ ] When creating a disbursement, start with the registration type
[ ] Then Wallet provider. Which is disabled when the registration type ends with WALLET_ADDRESS
[ ] Asset
[ ] Verification type. Which is disabled when the registration type ends with WALLET_ADDRESS

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr176.previews.kube001.services.stellar-ops.com/


using .vcmrc file returns 'true' even for invalid commit messages

I followed all the steps provided in the documentation and used .vcmrc file for configuration. It returns 'true' for both valid and invalid commit messages along with a log message for invalid commits.

I tried again after removing .vcmrc file. It works fine, returns 'false' for invalid commits and logs and error message with the commits

I didn't wanted the log messages. So, I used the second method given for configuration which was to write configuration in package.json

"warnOnFail" is false, so it should not log the error messages. But it still logs those messages

I am not able to understand this. I might be doing something wrong. Please help me :-)

Hi @Alice-anjali ,

warnOnFail
If this is set to true errors will be logged to the console, however the commit will still pass.

.vcmrc has precedence over config in package.json, so if you set warnOnFail: true, looks like it did what you asked

Hey @cmalard.. thanks for replying :-)
I have 2 doubts. As you can see, I have mentioned that I used .vcmrc file first. But on checking the commit messages, it returns 'true' for both valid and invalid commits [This is my first doubt]. So, I removed .vcmrc file and tried again, it works fine, but it's logging error messages for invalid commits which I don't want. That's when I wrote configurations in package.json file and set wornOnFail: false (I have posted the screenshot above). It should not log error messages now but it's still logging [This is my second doubt].

There is no option to stop validate-commit-msg from logging errors to the console (cf my quote of the doc ;-) )
About your first doubt, could you please provide the .vcmrc file you used ?

If your goal is to validate a branch, try this :-)

I understood what you said about warnOnFail. I misread the documentation earlier. My code is running successfully now.
Sorry for the inconvenience and thanks a lot for your help :-D


changed list of supported devices

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6719

added Surface Pro X to the list
removed "with LTE Advanced", as they are not separate products

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @e0i, for your information
Thank you


Text about RequireAuthorization is not correct.

This document states:
> The DefaultPolicy is triggered by [Authorize] or RequireAuthorization
But this is not true for the following uses of RequireAuthorization:
app.UseEndpoints(builder =>
{
    builder.MapRazorPages().RequireAuthorization();
    builder.MapControllers().RequireAuthorization();
});

Please clarify.

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

ID: 76f39eec-9dd1-6167-56ec-47b26e0b5063
Version Independent ID: f9f2b0f3-01eb-cf58-8767-194fe0fc0e44
Content: Migrate from ASP.NET Core 2.2 to 3.0
Content Source: aspnetcore/migration/22-to-30.md
Product: aspnet-core
Technology: aspnetcore-migration
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Related: https://github.com/dotnet/aspnetcore/issues/17300.

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog manageable. If you believe there is a concern which hasn't been addressed, please file a new issue.


Fix update device functionality to correct method

Fix #2119
Update the HTTP method from POST to PUT when invoking a callback for
a device service when a device has been updated.
Signed-off-by: Anthony M. Bonafide<EMAIL_ADDRESS>

Codecov Report

Merging #2125 into fuji will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             fuji    #2125   +/-   ##
=======================================
  Coverage   44.06%   44.06%
=======================================
  Files         186      186
  Lines       11682    11682
=======================================
  Hits         5148     5148
  Misses       6235     6235
  Partials      299      299

Impacted Files
Coverage Δ

internal/core/metadata/operators/device/update.go
83.83% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Feature/issue 2/api consumer

Codecov Report

Merging #14 into master will decrease coverage by 0.3%.
The diff coverage is 99.26%.

@@             Coverage Diff              @@
##             master      #14      +/-   ##
============================================
- Coverage       100%   99.69%   -0.31%
- Complexity       67      116      +49
============================================
  Files             5        9       +4
  Lines           196      332     +136
============================================
+ Hits            196      331     +135
- Misses            0        1       +1

Impacted Files
Coverage Δ
Complexity Δ

src/Traits/InteractsWithRest.php
100% <100%> (ø)
1 <1> (?)

src/Transformers/DefaultTransformer.php
100% <100%> (ø)
6 <6> (?)

src/Routing/Route.php
100% <100%> (ø)
8 <8> (?)

src/RestfulServiceProvider.php
100% <100%> (ø)
2 <1> (+1)
:arrow_up:

src/Builder.php
98.92% <98.92%> (ø)
33 <33> (?)

Continue to review full report at Codecov.

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


Vickel: Watch sri(?:@stackitrecruitment.com)?

Vickel requests the watch of the watch_keyword sri(?:@stackitrecruitment\.com)?. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

sri(?:@stackitrecruitment\.com)? has been seen in 329 true positives, 496 false positives, and 32 NAAs.

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'too many fp with the optional domain '