What values should I use for Storage Account Name and Storage Account Key?

Hello,
I am trying to use C# code for Data Movement Library to test the transfer of the files from Azure VM to my Blob Storage. However, when I ran the code, I entered:
Storage Account Name: I entered my Azure storage account name
Storage Account Key: Here I entered SAS Token
I got an error message:
Unhandled exception. System.FormatException: No valid combination of account information found.
at Microsoft.Azure.Storage.CloudStorageAccount.<>c.b__97_0(String err)
at Microsoft.Azure.Storage.CloudStorageAccount.ParseImpl(String connectionString, CloudStorageAccount& accountInformation, Action`1 error)
at Microsoft.Azure.Storage.CloudStorageAccount.Parse(String connectionString)
at DMLibSample.Program.Main() in /home/potivora/Documents/Internship/DevOps_DataMovementLibrary/DevOps_DataMovementLibrary/Program.cs:line 22

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

ID: ccebf561-f09a-42ae-ece7-1c194e921252
Version Independent ID: 8a552618-aed8-5230-726b-05dfaddac479
Content: Transfer data with the Data Movement library for .NET - Azure Storage
Content Source: articles/storage/common/storage-use-data-movement-library.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@Shutima
It is referring to your storage account key, not a SAS Token.
https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys

@Shutima
It is referring to your storage account key, not a SAS Token.
https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys

Thank you very much @DerekHerman-MSFT


Repeat rate for left/right click, hold to continuously break/build

Right now you have to click repeatedly to repeatedly break or build. This is a lot of clicking. You should instead be allowed to hold down a mouse button and have it repeat at some reasonable repeat rate.

It is not so much as a "repeat rate" like with keyboards, but the repetition arises naturally as a result of block hardness. Without block hardness, clicking would mine too far, instantly punching holes through blocks as far as you can reach, so the way to fix this is likely to do https://github.com/satoshinm/NetCraft/issues/17 "Block-breaking time with block hardness and breaking animation (vs instamine)", and to start out all blocks have the same "hardness" (= time to mine).


Instant crash when i click the import games icon

Program crashes, window goes completely white. Clicking inside the window does nothing, program is closable via right click on the taskbar icon

Can you upload your log?
The log file is stored here: %appdata%/steamgriddb-manager

log.log

I released 0.2.4 with some fixes. Can you try again?

Still happening for me on 0.2.6.
this.games.map is not a function also
log.log

Can you try again in using v0.3.0?

Different error, but still the same issue.
log.log

Oops, looks like I broke something on 0.3.0. Fixed it in 0.3.1.
The Battle.net and Uplay errors are separate from this. Please open another issue for those.

It's working

Also experiencing a crash when attempting to load the Import screen.
[2019-09-09 18:18:57.445] [error] UnhandledRejection TypeError: this.games.map is not a function
    at t.value (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:70:74938)
    at ma (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:65520)
    at ya (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:65315)
    at ql (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:99598)
    at zl (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:84005)
    at Fl (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:81032)
    at Al (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:79605)
    at file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:41756
    at t.unstable_runWithPriority (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:51:3878)
    at uo (file:///C:/Users/<redacted>/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:41485)

Please try again in v0.3.1.

Please try again with v0.3.2.

That seems to have resolved my issue.


string scrub

Please be aware that master is post RTM.  There's an releases/M83 branch for M83 and RTM on prem

Changes look fine.


HWKAGENT-130 remove op parameters from general properties

do not merge this yet. we'll want to give some time to allow clients and tools to update themselves so they do not rely on the general properties that this PR removes.

LGTM

This change has been announced on the dev mailing list here: http://lists.jboss.org/pipermail/hawkular-dev/2016-August/003183.html

I think only the gem needs to be updated.  This can be merged and the Gem will follow in short order.


Add further nio stubs

Sorry, this is a very boring PR, just continuing to fill out the classes under java.nio.file that some of my code references:

Add {FileAlreadyExists,NoSuchFile,NotADirectory}Exception.
Add OpenOption interface and StandardOpenOption enum.

BTW, you don't need to maintain your own fork just to cover missing classes in classlib module. You can just put them into your app's code and this will work.


LoadBalancingPolicy = First broken in preview 11

Describe the bug
Took us few hours to work this out. We deployed yarp preview 11 to prod for a small service. Worked as expected for 2 hours then service got restarted and yarp started using second destination. Previously this happened if first destination was unhealthy but with preview 11 it is random. This is not a problem with preview 10.
To Reproduce
Create new project and use the configurations below. Then run the https://localhost:5001/todo/v1.
You'd have to run this few times by stopping the app and rebuilding it. Sometimes the configurations don't get cleared until you rebuild the solution in VS (this is a another problem).
Here is my result I ran the project and yarp picked up second destination. If rebuild and re run few times destinations will randomly change.

{
  "Logging": {
    "LogLevel": {
      "Default": "Debug",
      "Microsoft": "Debug",
      "Microsoft.Hosting.Lifetime": "Debug"
    }
  },
  "AllowedHosts": "*",
  "ReverseProxy": {
    "Routes": {
      "Route8": {
        "ClusterId": "cluster1",
        "Match": {
          "Methods": [ "GET" ],
          "Path": "/todo/v1"
        },
        "Transforms": [
          {
            "PathSet": ""
          },
          {
            "ResponseHeader": "Access-Control-Expose-Headers",
            "Append": "IsSuccessful",
            "When": "Always"
          },
          {
            "ResponseHeader": "Access-Control-Max-Age",
            "Append": "86400",
            "When": "Always"
          }
        ]
      }
    },
    "Clusters": {
      "cluster1": {
        "LoadBalancingPolicy": "First",
        "HealthCheck": {
          "Passive": {
            "Enabled": "true",
            "Policy": "TransportFailureRate",
            "ReactivationPeriod": "00:01:01"
          }
        },
        "HttpRequest": {
          "Timeout": "00:01:00",
          "Version": "1.1"
        },
        "Destinations": {
          "cluster1_destination1": {
            "Address": "https://jsonplaceholder.typicode.com/todos/1"
          },
          "cluster2_destination2": {
            "Address": "https://jsonplaceholder.typicode.com/todos/2"
          }
        }
      }
    }
  }
}

Startup
public class Startup
    {
        public IConfiguration Configuration { get; }

        public Startup(IConfiguration configuration)
        {
            Configuration = configuration;
        }

        public void ConfigureServices(IServiceCollection services)
        {
            services.AddReverseProxy().LoadFromConfig(Configuration.GetSection("ReverseProxy"));

            services.AddCors(options => options.AddPolicy("EnableCors", builder =>
            {
                builder.AllowAnyOrigin().SetPreflightMaxAge(TimeSpan.FromSeconds(86400));
                builder.AllowAnyMethod().SetPreflightMaxAge(TimeSpan.FromSeconds(86400));
                builder.AllowAnyHeader().SetPreflightMaxAge(TimeSpan.FromSeconds(86400));
            }));
        }

        public void Configure(IApplicationBuilder app)
        {
            //app.UseMiddleware<ExceptionMiddleware>();
            app.UseCors("EnableCors");
            app.UseRouting();
            app.UseEndpoints(endpoints =>
            {
                endpoints.MapReverseProxy();
            });

        }
    }

Further technical details

Package Yarp.ReverseProxy - 1.0.0-preview.11.*
The platform - Windows

Is it consistently returning the same destination within one run of the app, and only changing when the app restarts?
Destinations is currently an un-ordered collection stored in various dictionary structures. The results should be stable within a run, but there's no guarantee of the order on load. I can understand that being confusing the the 'first' algorithm.
Is this on .NET 3.1 or 5.0?
We should check to see which collection is unstable across runs, and if we can provide a more predictable ordering like alphabetical, or if we need to make destinations a strictly ordered list. 'First' is the only algorithm directly impacted by order since it avoids using the second one except as fail-over.

@Tratcher

Is it consistently returning the same destination within one run of the app, and only changing when the app restarts?

In preview 11 no - every few runs you get a random destination. In preview 10 its consistently returning first destination and
when you restart the app the first destination is used.

The results should be stable within a run, but there's no guarantee of the order on load.

If order cannot be guaranteed across all runs then 'First' algorithm isn't useful right? Order was enforced until preview 10 it broke in preview 11. Now we are blocked until this is fixed, can't upgrade to preview 11.
As for solution any order will work, strict or alphabetical.

Is this on .NET 3.1 or 5.0
5.0

We should check to see which collection is unstable across runs

I assume it's our use of a Dictionary here (StringComparer.OrdinalIgnoreCase uses a random seed for hash calculations that will change between process restarts):
https://github.com/microsoft/reverse-proxy/blob/86529c9db046bc7b5985d2827f507de537880b7a/src/ReverseProxy/Service/RuntimeModel/ClusterState.cs#L52
https://github.com/microsoft/reverse-proxy/blob/86529c9db046bc7b5985d2827f507de537880b7a/src/ReverseProxy/Service/RuntimeModel/ClusterState.cs#L88

In preview10 it was a regular Dictionary. ConcurrentDictionary seems to be less stable.
https://github.com/microsoft/reverse-proxy/blob/67a5b6d2c37f1373b5ec268ce93bbd0a572fa010/src/ReverseProxy/Service/Management/ItemManagerBase.cs#L14

Triage: Needs experimenting on solution to get deterministic order.

I was investigating https://github.com/microsoft/reverse-proxy/issues/83#issuecomment-844565946 which deals with the available destinations list generation and briefly considered introducing sorting there, but First is the only policy proposed so far that depends on a strict ordering.
Proposal: Redefine First from meaning "First available destination we find" [O(1)] to meaning "Alphabetically first available destination." [O(n)]. The implementation would change accordingly from availableDestinations[0] to doing a single pass scan through the list to find the first entry by name. This has the benefit of working independent of the rest of the infrastructure, and being deterministic across reloads, adds, removes, etc.. Since First is expected to be used with a small number of destinations this change shouldn't add significant overhead.
Thoughts?
Thoughts?

@Tratcher I like your proposal! Nice!

Sounds reasonable. It can still be ~ O(1) if we choose to cache the "first" for a given collection

It can still be ~ O(1) if we choose to cache the "first" for a given collection

That's tricky given the collection can be changed per request by middleware. I also wonder what the cache would cost by comparison.

@Henery309, are you interested in contributing this fix? See https://github.com/microsoft/reverse-proxy/issues/980#issuecomment-845545603.


Error Loading Ref Data

Got some errors when loading ref data, unsure of the ,meaning/consequence, specifically
Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
INFO   [2023-12-13T13:02:20.649Z] [Extraction #8121] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130220__1234567457__1__b8c4ae57-ddd9-4161-8c44-15e5b50e5f74
INFO   [2023-12-13T13:02:20.723Z] [Extraction #8132] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130220__1234567873__1__173df1b2-91bf-40d2-8e4d-63d1ebd44602
INFO   [2023-12-13T13:02:20.798Z] [Extraction #8136] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130220__123456870__1__49a53216-0890-4730-859e-15b0508c46c2
INFO   [2023-12-13T13:02:21.010Z] [Extraction #8124] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130221__1234567709__1__bf5a7b13-2d16-42c0-b007-42b248520e57
INFO   [2023-12-13T13:02:21.151Z] [Extraction #8138] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130221__1234567945__1__49c28f78-c012-4d85-b012-ada07ff5c373
INFO   [2023-12-13T13:02:21.268Z] [Extraction #8139] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130221__1234567441__1__a8087cf3-bf41-4679-8122-7bc21838c18c
INFO   [2023-12-13T13:02:21.849Z] [Extraction #8128] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130221__1234567209__1__680f53c8-00ab-4c39-a875-d0f1b52ac764
INFO   [2023-12-13T13:02:22.265Z] [Extraction #8134] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130222__1234567469__1__e8318cd5-020e-4a63-a8fa-f896e06a9b8c
INFO   [2023-12-13T13:02:22.351Z] [Extraction #8126] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130222__1234564282__1__5297f411-490b-4eaa-9d2e-b3d66ef15eaf
INFO   [2023-12-13T13:02:22.424Z] [Extraction #8130] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130222__1234567883__1__2adf2e11-d97e-42a6-9be0-9fc71a8b7d30
INFO   [2023-12-13T13:02:22.493Z] [Extraction #8129] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130222__1234567703__1__89721747-cb32-4ac6-964e-abb6d54d4cda
ERROR  [2023-12-13T13:02:23.357Z] [Extraction #8138] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
ERROR  [2023-12-13T13:02:23.357Z] [Extraction #8128] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
ERROR  [2023-12-13T13:02:23.358Z] [Extraction #8129] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
ERROR  [2023-12-13T13:02:23.357Z] [Extraction #8126] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
ERROR  [2023-12-13T13:02:23.358Z] [Extraction #8130] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
ERROR  [2023-12-13T13:02:23.358Z] [Extraction #8139] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
ERROR  [2023-12-13T13:02:23.357Z] [Extraction #8134] stroom.pipeline.refdata.ReferenceDataFilter -  Error putting key 00001 into map MAP_OF_STUFF: UncheckedInterruptedException null
INFO   [2023-12-13T13:02:27.151Z] [Extraction #8134] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567457__1__2d95bb3b-8dab-4ab7-b04e-6c3c4aebf3bd
ERROR  [2023-12-13T13:02:27.155Z] [Extraction #8136] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream: 123456870:1 pipeline: Reference Loader
INFO   [2023-12-13T13:02:27.185Z] [Extraction #8124] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567873__1__c71e2c2a-54c4-410a-ba26-2664e9f9bc47
INFO   [2023-12-13T13:02:27.243Z] [Extraction #8136] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__123456870__1__d40b09f0-3ce4-4422-b263-e7fed47d66fa
ERROR  [2023-12-13T13:02:27.247Z] [Extraction #8133] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
ERROR  [2023-12-13T13:02:27.247Z] [Extraction #8123] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
ERROR  [2023-12-13T13:02:27.247Z] [Extraction #8128] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
INFO   [2023-12-13T13:02:27.293Z] [Extraction #8133] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234564282__1__45c55fb0-7d9e-490a-b7a0-ea545c4bdf05
INFO   [2023-12-13T13:02:27.351Z] [Extraction #8123] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567883__1__abf9c914-b43b-4f29-b991-5846f4e0990c
INFO   [2023-12-13T13:02:27.385Z] [Extraction #8128] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567945__1__0a4f20eb-4032-4bc0-a317-df917e26a746
ERROR  [2023-12-13T13:02:27.385Z] [Extraction #8122] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
ERROR  [2023-12-13T13:02:27.391Z] [Extraction #8120] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
ERROR  [2023-12-13T13:02:27.391Z] [Extraction #8121] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
INFO   [2023-12-13T13:02:27.432Z] [Extraction #8122] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567709__1__0d1e6180-0b5b-4260-bf1c-23181b6b0ec0
ERROR  [2023-12-13T13:02:27.432Z] [Extraction #8130] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
ERROR  [2023-12-13T13:02:27.432Z] [Extraction #8126] stroom.pipeline.refdata.store.AbstractRefDataStore -  Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway. reference stream:<PHONE_NUMBER>:1 pipeline: Reference Loader
INFO   [2023-12-13T13:02:27.498Z] [Extraction #8120] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567469__1__801148bd-5454-4565-a002-2bd29dd0be7e
INFO   [2023-12-13T13:02:27.585Z] [Extraction #8121] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567209__1__27b2e6bc-b44e-4bcc-be4a-52a11464db9a
INFO   [2023-12-13T13:02:27.623Z] [Extraction #8130] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567441__1__572d35f6-44a8-4696-add6-d6d5690d4ebe
INFO   [2023-12-13T13:02:27.676Z] [Extraction #8126] stroom.pipeline.refdata.store.offheapstore.OffHeapStagingStoreFactory -  Creating temporary reference data staging LMDB environment in /path/to/reference_staging_data/20231213-130227__1234567703__1__a33c9b14-2d2a-425d-be2c-5cb7adc75a29
WARN   [2023-12-13T13:02:30.585Z] [Extraction #8134] stroom.pipeline.refdata.store.offheapstore.OffHeapRefDataLoader -  Unable to use APPEND mode, so ref load may be a bit slower. maxUidInDb: 208, minUidInStaging: 207, db: KeyValueStoreDb, refStreamDefinition: RefStreamDefinition{streamId=1234567457, partIdx=0, pipeline=DocRef{type='Pipeline', uuid='dbf696a5-a82c-11e7-9162-885a92f6a97a', name='Reference Loader'}, pipelineVersion='050f743c-ac58-4e88-9ed3-12c42f8c2d2d'}
WARN   [2023-12-13T13:02:31.515Z] [Extraction #8124] stroom.pipeline.refdata.store.offheapstore.OffHeapRefDataLoader -  Unable to use APPEND mode, so ref load may be a bit slower. maxUidInDb: 208, minUidInStaging: 208, db: KeyValueStoreDb, refStreamDefinition: RefStreamDefinition{streamId=1234567873, partIdx=0, pipeline=DocRef{type='Pipeline', uuid='dbf696a5-a82c-11e7-9162-885a92f6a97a', name='Reference Loader'}, pipelineVersion='050f743c-ac58-4e88-9ed3-12c42f8c2d2d'}

I think we are seeing
Unexpected processing state LOAD_IN_PROGRESS. This should not happen. We hold the lock though, so will load anyway

because the load was triggered as part of a search extraction which has been terminated (thread interrupted). When the InteruptedException is thrown it gets caught in stroom.pipeline.refdata.ReferenceDataLoadTaskHandler#populateMaps.  This code tries to completeProcessing() but that involves getting a write lock on the LmdbEnv which will fail as the thread is interrupted.
The catch blocks in populateMaps() need to specifically catch UncheckedInterruptedException, then clear the interrupt flag, call completeProcessing() using TERMINATED, then re-enable the interrupt flag on the thread and re-throw.
Also need to try and avoid logging errors for termination/interruption as it is not an error condition as far as the app is concerned.
Also need to change the way we are using the messageSupplier on the UncheckedInterruptedException as the messageSupplier does not set the msg on the exception so gets lost.

Fixed in > 7.2.15


How to test single image by using Pre-trained model

Hello firstly thank you for your great work.
is there any way to test this model with only single image by using your pre-trained model which is "SD7K.pth"
Thank you in advance.

Hi, I have updated the single.py which can test single image.

Firstly thank you for your support. I am trying to test pre-trained checkpoint on CPU. I have changed codes for this. After that when I using "single.py" I am getting as following error

is there any advice for achiving this error?
Thank you in advance.

Hello again. After modified single.py  as following codes. It is working
import warnings
from accelerate import Accelerator
from torchvision.utils import save_image
import torchvision.transforms.functional as F
from tqdm import tqdm
from PIL import Image
import numpy as np
from config import Config
from models import *
from utils import *
import os
import cv2
import torch

warnings.filterwarnings('ignore')

opt = Config('config.yml')

seed_everything(opt.OPTIM.SEED)

def single_test(path_img):

    img = cv2.imread(path_img)
    img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB) # H, W, C

    img_tensor = torch.tensor(img, dtype=torch.float32) # Convert to torch tensor
    img_tensor = img_tensor / 255. # Normalize [0 - 1] range (but depends on the model)
    img_tensor = img_tensor.permute(2, 0, 1) # Reorder to C, H, W (torch requires this format)
    img_tensor = img_tensor.unsqueeze(0) # Becomes this format B, C, H, W

    accelerator = Accelerator()

    # inp = Image.open(path_img).convert('RGB')
    # inp = np.array(inp)
    # inp = F.to_tensor(img_tensor)

    # Model & Metrics
    model = Model()

    print(opt.TESTING.WEIGHT)

    load_checkpoint(model, opt.TESTING.WEIGHT)

    model = accelerator.prepare(model)

    model.eval()

    if not os.path.exists("result"):
        os.makedirs("result")

    with torch.no_grad(): # Dont run your gradients, speeds up inference

        res = model(img_tensor)

        save_image(res, os.path.join(os.getcwd(), "result", os.path.basename(path_img)))

if __name__ == '__main__':
    path_img = './input/515d9bb410b14e5fb13d1e54fa5e9abd-ezsam.png'
    single_test(path_img)

Thank you so much your support again.

Sorry I was busy with other things and didn't notice the GitHub notification.


Provide paper feedback

The paper is really shaping up!
Provide detailed text comments on explore, analyze and data this cycle (skipping case studies for now).

Success here means generating 4 issues:

[ ] Explore
[ ] Analyze
[ ] Data
[ ] Figures

can success be defined by commenting on 4 open issues?

i'm down with that, but ideally should be explicit, external, and detailed review (e.g., not "make figure better", but a review of existing content)

so, a list of revisions for each person's 1 issue?
people still have 2 issues, so it will be a bit complicated, but i'll try...
On Mon, Jun 13, 2016 at 2:37 PM, William Gray<EMAIL_ADDRESS>wrote:

i'm down with that, but ideally should be explicit, external, and detailed
review (e.g., not "make figure better", but a review of existing content)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/ndpaper/issues/58#issuecomment-225568727,
or mute the thread
https://github.com/notifications/unsubscribe/AACjcjpilc96754wcS6w4tAN47D0zbUIks5qLU77gaJpZM4Iy2rH
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York

these will be ready for you by tomorrow.  not due for almost a week.  pardon our dust while i restructure.

all good.
On Mon, Jun 13, 2016 at 10:28 PM, William Gray<EMAIL_ADDRESS>wrote:

these will be ready for you by tomorrow. not due for almost a week. pardon
our dust while i restructure.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/ndpaper/issues/58#issuecomment-225698212,
or mute the thread
https://github.com/notifications/unsubscribe/AACjcsw6YiGv1R3jIJO5bDPGk4Cf_epvks5qLb1WgaJpZM4Iy2rH
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York


How to debug electron c++ source codes?

Is there anybody know how to debug electron source code? I created a ticket here too.

I use the command to set a breakpoint like this:
/atom/browser/api/atom_api_app.cc
Then there is error message like this:
Breakpoint 14: no locations (pending). WARNING:  Unable to resolve breakpoint to any actual locations.

I built Electron with debug mode ./script/build.py -c D, so i think the app includes debug information. Am i wrong?

I suggest poking chromium-dev for help since there many Chromium developers there can help on how to debug Chrome and apps that built upon Chromium. There is also a chromium-dev Slack channel averrable.


FRDM_K64F: tests/drivers/dma/scatter_gather test fails.

Describe the bug
tests/drivers/dma/scatter_gather/ fails.
Platform: FRDM_K64f
After bisect sesion.
8eeb3554b0afa055e196484d2b8498f1faeecf65 is the first bad commit
commit 8eeb3554b0afa055e196484d2b8498f1faeecf65
Author: Mahesh Mahadevan<EMAIL_ADDRESS>Date:   Thu May 11 06:54:47 2023 -0500

    tests: dma: Increase data transferred in scatter_gather test

    Increase the amount of data to be transferred and the
    number of blocks to transfer.

    Signed-off-by: Mahesh Mahadevan<EMAIL_ADDRESS>
 tests/drivers/dma/scatter_gather/src/test_dma_sg.c | 25 +++++++++++-----------
 1 file changed, 13 insertions(+), 12 deletions(-)

To Reproduce
Steps to reproduce the behavior:
./scripts/twister --device-testing --hardware-map ./map.yml -T ./tests/drivers/dma/scatter_gather/ -v
Output:
INFO    - 1/1 frdm_k64f                 tests/drivers/dma/scatter_gather/drivers.dma.scatter_gather  FAILED Failed (device 2.475s)
ERROR   - see: <path_to>/twister-out/frdm_k64f/tests/drivers/dma/scatter_gather/drivers.dma.scatter_gather/handler.log

Handler.log contains
*** Booting Zephyr OS build zephyr-v3.3.0-4545-g8eeb3554b0af ***
Running TESTSUITE dma_m2m_sg
===================================================================
START - test_dma_m2m_sg
DMA memory to memory transfer started
Preparing DMA Controller
dma block 0 block_size 8192, source addr 20008060, dest addr 20000060
set next block pointer to 0x2000a6a4
dma block 1 block_size 8192, source addr 20008060, dest addr 20002060
set next block pointer to 0x2000a6c4
dma block 2 block_size 8192, source addr 20008060, dest addr 20004060
set next block pointer to 0x2000a6e4
dma block 3 block_size 8192, source addr 20008060, dest addr 20006060
Configuring the scatter-gather transfer on channel 0
E: please config DMA_TCD_QUEUE_SIZE as 4
ERROR: transfer config (0)
Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/dma/scatter_gather/src/test_dma_sg.c:160: dma_m2m_sg_test_dma_m2m_sg: (test_sg() == TC_PASS) is false
FAIL - test_dma_m2m_sg in 0.068 seconds
===================================================================
TESTSUITE dma_m2m_sg failed.
------ TESTSUITE SUMMARY START ------
SUITE FAIL -   0.00% [dma_m2m_sg]: pass = 0, fail = 1, skip = 0, total = 1 duration = 0.068 seconds
- FAIL - [dma_m2m_sg.test_dma_m2m_sg] duration = 0.068 seconds
------ TESTSUITE SUMMARY END ------
===================================================================
RunID: 04db2067ac5d10604b1c561c779bfb17
PROJECT EXECUTION FAILED

Environment :

OS: Linux
Toolchain Zephyr_SDK 0.16.1

mimxrt10xx series has the same issue

@gbarkadiusz , a fix has been pushed. Can you please re-test.

It has been fixed. So I'm going to close this issue.


Fix open default gem error

Close #4436
@indirect @segiddins @RochesterinNYC Please review
Also, is an update in documentation of bundle open needed?

Failure seems to be related to hard-coded version string...
Any idea of how to get the system's json version?

You could probably do something with gem list. Or alternatively just change the assertion to not look for an explicit json version in the expected message.

@homu delegate=RochesterinNYC

:v: @RochesterinNYC can now approve this pull request

@RochesterinNYC r?

@homu r+

:pushpin: Commit cb62a70 has been approved by RochesterinNYC

:hourglass: Testing commit cb62a70 with merge 4da7b24...

:broken_heart: Test failed - status

@allenzhao could you take a look at the failure?

@indirect I've updated and it should be fine now. Turns out to_s won't be auto called under 2.0.0

Failing RuboCop -- run bin/rubocop -a locally to correct it / see the failure

@allenzhao ping

I'm confused by the output - maybe I'm writing the wrong test.
When Ruby version higher than 2.0, everything seems fine, but when Ruby version < 2.0, say 1.9.7, the to_s is not auto called on string interpolation.
When I manually called to_s, it seems that above 2.0 rubocop will fail, but under 2.0 'json' is not native built in so the test case itself would fail.
Any ideas on a proper way to test this feature?

What do you mean to_s is not auto called on string interpolation?


Upgrade Docker Compose to version 3

I see that the Docker Compose file is version 2 (supporting Docker Engines 1.10.0+). See https://docs.docker.com/compose/compose-file/compose-versioning/#compatibility-matrix
The recommended Docker Compose file from Docker is version 3 (supporting Docker Engines 1.13.0+) which would allow also EdgeX to be deployed via Swarm.
I did a comparison between the changes in the syntax upgrading from 2 to 3 and it seems as the only deprecated command that was used in the EdgeX file is "volumes_from" (see https://docs.docker.com/compose/compose-file/compose-versioning/#upgrading)
Can we generate a Docker Compose version 3 file?

The California preview release, nexus and latest docker compose files have all been moved to 3.  Left the compose files for Barcelona 2.0 and 2.1 at compose 2


Cairo script

#107
I'm already using this for some benchmarking. The commit history looks strange - as i was using master for some other 1.12 features. The last (239a146) should actually be enough.

This is still valid, but i'll reognize this together with other features.


Add store.commit() lines

@koppor Here I added store.commit() lines in the code.
commit() looks for unsaved changes and writes them to file.
If MVStore really supported mutable values then adding these lines wouldn't change anything. But you see, that tests are failing.
And by supporting mutable values I mostly mean supporting storing mutable values in file after they were modified. "In-memory store" works fine.

@InAnYan please also link the mvstore issue you opened here!

Have you checked the docs?
// close the store (this will persist changes)
s.close();
https://www.h2database.com/html/mvstore.html#differences

The maintainers confirmed that its not possible to use Lists inside the Map: https://github.com/h2database/h2database/issues/4090


Switch to secure Base58 library

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] Commit messages follow the conventional commits spec
[ ] If this is a code change: I have written unit tests.
[x] If this changes code in a published package: I have run pnpm changeset to create a changeset JSON document appropriate for this change.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

This PR switches the Base58 implementation to a secure, audited & 0-deps implementation. The existing bs58 library is old, poorly maintained, and incompatible with Vite due to its use of Node.js primitives (Buffer).
This PR should resolve the following:

https://github.com/near/near-api-js/issues/1420
https://github.com/near/near-api-js/issues/1408
https://github.com/near/near-api-js/pull/1391
https://github.com/near/near-api-js/pull/1392

Test Plan

Related issues/PRs

[!NOTE]
This project still indirectly relies on bs58 through near-workspaces:

near-workspaces 3.5.0
├─┬ borsh 0.5.0
│ └── bs58 4.0.0
├── bs58 4.0.1

We'll need to do this in parts:

First, we need to release new packages for these libraries
Then, we need to update near-workspace to use the new libraries that don't depend on bs58, along with stripping the existing bs58 dependency
Release a new version of near-workspace with 0 dependency on bs58
Bump near-workspace version in near-api-js and make a new release


Session 30843b79-8fa6-457f-885b-aaa7031fb4f8. Failed request to assessment endpoint with status code 403

Running Azure App Service Migration Wizard 1.0.6 locally on server as admin.  Sites are detected, assessment report worked once, but then fails with error in title.
Auth on Site is set to Anonymous

Hi @DGrahamP,
Thanks for reporting this behavior. I'm not seeing a generic issue with the assessment backend being inaccessible. I'm curious - if you close and reopen the Migration Assistant does it work the first time or still fail every time? If you try to reach http://readinessapi.trafficmanager.net/ in a browser does it also return a 403?
The server-side logs for the readiness API don't record these 403s, which makes me suspect the request might be getting blocked in a layer somewhere above the assessment endpoint.
If this is persistent you also have the option of using the PowerShell scripts to get the assessment results in a json block for all the sites on the server at once without reaching out to the assessment endpoint (more info).


TypeError: Cannot read property 'getItem' of undefined

Using React Native 0.71.10 and on iOS.
On clicking on country getting below error:
TypeError: Cannot read property 'getItem' of undefined
This error is located at:
in FlatList (created by CountryList)
in RCTView (created by View)
in View (created by CountryList)
in CountryList (created by CountryPicker)
in RCTSafeAreaView (created by CountryModal)
in RCTView (created by View)
in View (created by AppContainer)
in RCTView (created by View)
in View (created by AppContainer)
in AppContainer (created by Modal)
in RCTView (created by View)
in View (created by Modal)
in VirtualizedListContextResetter (created by Modal)
in RCTModalHostView (created by Modal)
in Modal (created by CountryModal)
in CountryModal (created by CountryPicker)
in CountryPicker (created by Main)
in ThemeProvider (created by Main)
in Main (created by PhoneInput)
in RCTView (created by View)
in View (created by AnimatedComponent)
in AnimatedComponent
in AnimatedComponentWrapper (created by TouchableOpacity)
in TouchableOpacity (created by TouchableOpacity)
in TouchableOpacity (created by PhoneInput)
in RCTView (created by View)
in View (created by PhoneInput)
in CountryModalProvider (created by PhoneInput)
in PhoneInput (created by Login)
in RCTView (created by View)
in View (created by Login)
in RCTView (created by View)
in View (created by Login)
in Login (created by SceneView)
in StaticContainer
in EnsureSingleNavigator (created by SceneView)
in SceneView (created by SceneView)
in RCTView (created by View)
in View (created by DebugContainer)
in DebugContainer (created by MaybeNestedStack)
in MaybeNestedStack (created by SceneView)
in RCTView (created by View)
in View (created by SceneView)
in RNSScreen (created by AnimatedComponent)
in AnimatedComponent
in AnimatedComponentWrapper (created by InnerScreen)
in Suspender (created by Freeze)
in Suspense (created by Freeze)
in Freeze (created by DelayedFreeze)
in DelayedFreeze (created by InnerScreen)
in InnerScreen (created by Screen)
in Screen (created by SceneView)
in SceneView (created by NativeStackViewInner)
in Suspender (created by Freeze)
in Suspense (created by Freeze)
in Freeze (created by DelayedFreeze)
in DelayedFreeze (created by ScreenStack)
in RNSScreenStack (created by ScreenStack)
in ScreenStack (created by NativeStackViewInner)
in NativeStackViewInner (created by NativeStackView)
in RNCSafeAreaProvider (created by SafeAreaProvider)
in SafeAreaProvider (created by SafeAreaInsetsContext)
in SafeAreaProviderCompat (created by NativeStackView)
in NativeStackView (created by NativeStackNavigator)
in PreventRemoveProvider (created by NavigationContent)
in NavigationContent
in Unknown (created by NativeStackNavigator)
in NativeStackNavigator (created by HomeNavigation)
in EnsureSingleNavigator
in BaseNavigationContainer
in ThemeProvider
in NavigationContainerInner (created by HomeNavigation)
in HomeNavigation (created by App)
in App (created by Root)
in RCTSafeAreaView (created by Root)
in RCTView (created by View)
in View (created by KeyboardAvoidingView)
in KeyboardAvoidingView (created by Root)
in TouchableWithoutFeedback (created by Root)
in RCTView (created by View)
in View (created by GestureHandlerRootView)
in GestureHandlerRootView (created by Root)
in MobXProvider (created by Root)
in Root
in RCTView (created by View)
in View (created by AppContainer)
in RCTView (created by View)
in View (created by AppContainer)
in AppContainer
in SnogRider(RootComponent), js engine: hermes

I encounter the same issue. And the problem is linked with the Flatlist lib itself. A very simple patch for React-native 0.73.0
I have check in 0.73.6 and it's still broken :
diff --git a/node_modules/react-native/Libraries/Lists/FlatList.js b/node_modules/react-native/Libraries/Lists/FlatList.js
index 1b2ee17..eb17551 100644
--- a/node_modules/react-native/Libraries/Lists/FlatList.js
+++ b/node_modules/react-native/Libraries/Lists/FlatList.js
@@ -420,6 +420,7 @@ class FlatList<ItemT> extends React.PureComponent<Props<ItemT>, void> {

   constructor(props: Props<ItemT>) {
     super(props);
+    this.props = props;
     this._checkProps(this.props);
     if (this.props.viewabilityConfigCallbackPairs) {
       this._virtualizedListPairs =


does not install on "Decentr" browser

"Invalid manifest" error. Tried installing through extension chrome extension store and load unpacking manually.
chrome based browser, crypto focused like brave

Thanks, but I rather think the support of manifest v3 extension will/should be added to Decentr.
SAFEW has migrated to manifest v3 because the Chrome web store does not allow anymore new manifest v2 extensions.
In June 2023, it is planed that manifest v2 extensions won't run anymore in Chrome.
https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/


Can we make the UIA name longer than 16 characters please

The Smartcoins POS systems allow the merchant to automatically offer their rewards with each customer purchase. In the POS settings screen though, there are so many UIA's listed in there already, it would be nice if the merchant's UIA were easier to find, and more explanatory. This way when the customer looks in their mobile wallet, they will see that merchants UIA as a nice little reminder and there is no question what it's for.
STARBUCKS.REWARDS for example is 17 characters.
MEDIAMARKT.REWARDS is 18 characters.
CIRCUITCITY.REWARDS is 19 characters.
ALBERTSONS.REWARDS is 18 characters.
JOES.COFFEE.ON.MAIN.STREET is 26 characters.
Some small businesses have more than 1 location (like Joe's Coffee) and it would be nice if they could offer their own token too. You get the point. Can we please expand UIA length to say 32 chars?

This is not a GUI issue, you should raise this issue in the graphene repo as it's a blockchain restriction.


Error message "Invalid constant value" doesn't signpost to potential cause

This error message could benefit from being expanded, particularly with some suggestions for root causes. For example, perhaps:
"Invalid constant value. Consider removing the const declaration from the code that uses it, or replace it with a const value."
https://github.com/dart-lang/sdk/blob/dd1f384f2389004049c9e4b00a1068498ebdf28a/pkg/analyzer/lib/src/error/codes.dart#L6456-L6457
Take this small snippet of a beginner Flutter code project:
        appBar: AppBar(
          title: const Text(
            'Fooderlich',
            style: GoogleFonts.openSans(),
          ),
        ),

Here, the error is unhelpful since it doesn't give any hints as to why the value may be invalid. If you know what you're looking for, you may infer that GoogleFonts.openSans() does not return a const, but the word 'invalid' is not the same as 'non-const'.
By the by, this warning appears multiple times if the property is chained:

I bring it up because it appeared in a simple and highly-trafficked starter project that I'd ported forward, and I took ten minutes to figure out what was wrong. Dumb on my part, perhaps, but a good opportunity to remove some customer friction.

I absolutely agree.
For anyone trying to solve the problem: the issue is that we have a single diagnostic code that is used for all possible errors in constant expressions. As a result the message is incredibly vague, because any attempt to be more specific would be wrong in all the other cases. The existing code needs to be broken up into multiple codes based on the reason why the constant is invalid, and those codes need messages that make that cause (and correction) clear.
Note that this arc of work is related to a proposal to enhance the set of constant expressions and the proposal to, as part of that work, re-write the constant evaluator so that it can be shared between the analyzer and the front-end.

Also it would be nice if error message will contain a desition beside the reason because this problem is very common among newbies. It would be user-friendly.

Underlining the related const keyword would help us see where the const is.
Related issue: #47532

@kallentu worked on this a lot in 2023; this maybe can be closed? I can't check easily without a minimal reproduction of the issue.


Clean up branches

We have 41(!) branches atm, because someone's been forgetting to delete pulled branches ;) (To be fair, a few of them are mine)
It makes finding actively worked on branches quite hard, so we really should clean house at some point. And we also should remember to delete pulled branches!

I've cleaned mine up! The ones still there are ones I still hold a certain fondness for and can stay for a little longer ;)


TypeError: Cannot read property 'getItem' of undefined

Uncaught TypeError: Cannot read property 'getItem' of undefined
at FlatList._checkProps (FlatList.js:452)
at new FlatList (FlatList.js:396)
at constructClassInstance (ReactNativeRenderer-dev.js:7726)
at updateClassComponent (ReactNativeRenderer-dev.js:12729)
at beginWork (ReactNativeRenderer-dev.js:14756)
at Object.invokeGuardedCallbackProd (ReactNativeRenderer-dev.js:93)
at invokeGuardedCallback (ReactNativeRenderer-dev.js:318)
at beginWork$1 (ReactNativeRenderer-dev.js:19820)
at performUnitOfWork (ReactNativeRenderer-dev.js:18563)
at workLoopSync (ReactNativeRenderer-dev.js:18499)
React Native version:
Run react-native info in your terminal and copy the results here.
=====================
info Fetching system and libraries information...
System:
OS: macOS 11.2.3
CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
Memory: 1.71 GB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 15.7.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 15.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^17.0.2 => 17.0.2
react-native: ^0.64.0 => 0.64.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
====================================
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Error is triggered when FlatList is used on any page
VirstualList does not trigger this error

=================================
Expected Results
Describe what you expected to happen.
To run the below list of data
children: Array(15)
0: {index: 0, name: "Afghanistan", code: "AF", states: Array(34)}
1: {name: "Albania", code: "AL", states: Array(12)}
2: {index: 2, name: "Algeria", code: "DZ", states: Array(48)}
3: {index: 3, name: "American Samoa", code: "AS"}
4: {index: 4, name: "Andorra", code: "AD", states: Array(7)}
5: {index: 5, name: "Angola", code: "AO", states: Array(18)}
===========================
Snack, code example, screenshot, or link to a repository:

      {props?.list?.length ? (
         {
            return renderView(item, index)
          }}
          keyExtractor={(item) => item.group}
        />
      ) : null}

=========================
Screenshots
Ios

Android

Description

What are you passing as data to the flatlist.

What are you passing as data to the flatlist.

children: Array(15)
0: {index: 0, name: "Afghanistan", code: "AF", states: Array(34)}
1: {name: "Albania", code: "AL", states: Array(12)}
2: {index: 2, name: "Algeria", code: "DZ", states: Array(48)}
3: {index: 3, name: "American Samoa", code: "AS"}
4: {index: 4, name: "Andorra", code: "AD", states: Array(7)}
5: {index: 5, name: "Angola", code: "AO", states: Array(18)}

Pretty the same error. Try few libraries which use FlatList (for example react-native-autocomplete-input), then use example from original Rn docs https://reactnative.dev/docs/flatlist

Same issue here on RN 0.64.1. Using a FlatList even the example from the docs site fails with this error.

RN 0.66.2/0.66.3 the same issue.

RN 0.70.6 the same issue.

Hi @jlm0 Is it fix in RN 0.71.0 ?

Is there any result...

This issue has been here for so long

@codewithmecoder the issue is still being present in 0.71.3
I'm on my way to check what's going wrong with the piece of FlatList code.

@codewithmecoder Oops, I'm sorry
An accident happened with my cached files. The issue is not there with React-Native version 0.71.3

The problem can be fixed by removing   ['@babel/plugin-proposal-private-methods'],  from babel.config.js.


Updating readme from branch example

Updates
I updated the readme file. please review and accept.

Thoughts
I probably shouldn't, but okay. 👍


Incremental compile fails with classpath containing multiple classes with same name

Hi,
Im currently seeing a problem with incremental compilation, where I get a 'cannot find symbol' when compiling.
This seems to be due to the way we generate some of our code, where our models inherit eachother and the resulting generated code will have the same package and class name but exist in the different subprojects (classpath overloading).
This is all fine when we package the softwhere, we can control the classpath.
However, sometimes when a incremental compile is needed the 'cannot find symbol' error occurs. I've looked a bit into it and it seems that the output of the previous build is added to the compile classpath, but at the end of it, hence the wrong class is loaded first.
If the output of the previous build is added first to the compile classpath the compilation is successful: https://github.com/dvaske/gradle/commit/296edb1a7debae30d73a981e2c207deb97bcb5f8
I'll be happy to provide a pull request for this.
Expected Behavior
Compilation should work, as it does on a clean compile
Current Behavior
Compilation fails with a cannot find symbol due to the wrong class being loaded first on the classpath
Context
As explained above the wrong class is classpath, making the compilation fail.
Steps to Reproduce
clone https://github.com/dvaske/gradle-incremental-classpath
Build once gradlew build
Change CompanyImpl in :a to trigger a recompilation e.g. comment in/out the on method
Build again gradlew build now the build should fail in :b:compileJava with
.../Company.java:13: error: cannot find symbol
                if (postingType == PostingType._a_0)

as the classpath for :b:compileJava contains the classes from :a
before the previous output from :b
Compiler arguments (newlines inserted for better readability):
-source 1.8 -target 1.8
-d /Users/aske/work/gradle-incremental-classpath/b/build/classes/java/main
-encoding UTF-8 -g -sourcepath  -proc:none
-s /Users/aske/work/gradle-incremental-classpath/b/build/generated/sources/annotationProcessor/java/main
-XDuseUnsharedTable=true
-classpath /Users/aske/work/gradle-incremental-classpath/a/build/classes/java/main:/Users/aske/work/gradle-incremental-classpath/b/build/classes/java/main
/Users/aske/work/gradle-incremental-classpath/b/src/main/java/com/company/Company.java

Your Environment
Build scan URL:
https://scans.gradle.com/s/h2aftc4udg3io/
-Aske

fixed by #27942


Update alt-image-text to include a more accurate text replacement method

Second try, this should be a cleaner pull request.
Updated the alt-image-text tip to include safer methods than text-indent: -9999px, as this can introduce performance issues with rendering and animations.

Hey, @jaasum thanks for your time and for submitting this PR by following the guidelines. 😄
I do like the solution you have provided in this snippet. We're currently having a discussion on #19 and as soon as we figure it out I will merge this! Should be in a day or two hopefully.
Until then, have a productive time!

Hey @jaasum! Just decided that we will delete this snippet as it confuses a lot of people. Nonetheless, I am going to first merge this, as I want to appreciate your willingness to help! Hopefully, that's okay with you.
Thanks for your time! Appreciate it 💯

No worries, I'll keep an eye out for any future contributions. Thanks!


[fix] updated invocation_metadata return type hint

Updated the type hint for return type of grpc.aio.ServicerContext.invocation_metadata() to Optional[MetadataType] instead of Optional[Metadata].
MetadataType is already defined to be a Sequence[MetadatumType] and hence the type hint will reflect the sequence being returned, hence solving the user's reported issue

Looks good as your first PR!
Couple of small things:

Use markdown format in description so it's easier to review, example: grpc.aio.ServicerContext.invocation_metadata().
This changed the return type of a public API, even it's a bug fix, we should still label it with "release note: yes" so it appears in our release notes (release note is also a required label for all PRs).

hmm, but even the sync implementation grpc._server.Context.invocation_metadata() has the return type as Optional[MetadataType]. I thought it would make sense to keep them both same

hmm, but even the sync implementation grpc._server.Context.invocation_metadata() has the return type as Optional[MetadataType]. I thought it would make sense to keep them both same

Checked again, actually since Tuple is a type of Sequence, I think it should be fine to use MetadataType


Fix Illustrator Viewbox Method - Clean up Illustrator SVG

When you save a vector as SVG from adobe illustrator often times the ViewBox is does not start at "0 0 x y".   This throws off everything including all the paths.
For example:
viewBox="300 66 720 432"
Is there a method to reset the viewbox to "0 0" and all the sub paths, rects, etc... ???
This would be really useful for those who are starting off with Illustrator for SVGs.

I don't understand exactly why it does mix up everything. After all viewbox ist just a translation and a zoom. And when you saved it this way why you would want to change it? However - svg.js does not cleanups. Nevertheless you could write an add-on which does that for you.

@villanus Could you maybe create a fiddle to better illustrate your problem?

Sure:
https://jsfiddle.net/trurhu1h/5/
As you can see, when you save a vector as an SVG in adobe Illustrator (CS 6 or CC) the viewbox does not start with 0 0.   The only way I think you can fix this in illustrator alone is to:

Save the SVG
Open the SVG in illustrator
Select everything.
Change the X to 0
Change the Y to 0
Save again.

It would be sweet if the viewboxes were always set to 0 0  at the beginning, along with some more cleaning up.
In the fiddle I have 3 svg files.

Saved a vector as SVG using illustrator
Used clean up method (six steps) described above
Cleaned up the SVG tag manually.

Thank you for your fiddle!
As I already mentioned: The libraray MUST NOT change the svg when it is loaded into the svg. The user has to provoke this changes. Therefore svg.js will not automatically "clean" an svg. Note, that "clean" for you means "destroy" for other users.
Thats why you should write a plugin which adds a function (say clean()).
You can then call that function after you loaded the svg: SVG('your_svg').clean()

I second that. SVG.js is not responsible, nor required to modify inputted data in any way. If some application outputs data which is not in a format desired by the user, the user should take the responsibility to modify the data accordingly, not SVG.js.

Doing this as a plugin or extension makes complete sense.
I am a little confused on what to do with the paths.   If i set the new viewbox, dont the paths all need to be recalculated to the new offsets?

Thats correct. After all it was only a start.
However you would do something like this:
SVG.extend(SVG.Doc, {
  clean: function(){

    var box = this.viewBox()

    // remove height, width and set new viewbox
    this.height(null).width(null).viewBox(0, 0, box.width, box.height)

    // adjust children
    this.children().dmove(viewBox.x, viewBox.y)
  }
})

Sweet.
I will give it a go when I get home from work.
As always you and Wout are the best!


feat(forge verify-contract): --guess-constructor-args

Component
Forge
Describe the feature you would like
It would be convenient to have an option to specify --guess-constructor-args flag on forge verify-contract command which will try to find constructor arguments for contract without need to explicitly provide them when running the command.
It can be done in 3 steps:

Fetch contract deployment transaction with Etherscan API: https://docs.etherscan.io/api-endpoints/contracts#get-contract-creator-and-creation-tx-hash
Fetch contract creation code from transaction
Use contract ABI to calculate length of abi-encoded constructor arguments and take a suffix of creation code with this length.

The most interesting part is fetching the creation code (step 2). For contracts deployed by EOAs it is pretty simple (we can just take tx.data field). But for contracts deployed with CREATE/CREATE2 it would require tracing of transaction execution which takes time and requires endpoint with archive data which is not available to everyone.
It might also make sense to add a CLI command forge get-constructor-args <CONTRACT> <CREATION_CODE> which will basically perform a step 3 above. This might be useful because users may have init code from broadcast artifacts or Etherscan UI
Additional context
No response

This feature would be extraordinarily helpful.
The most difficult part about verifying contracts is the ABI-encoding of the constructor params. We need to resort to complicated nested terminal commands like this:
forge verify-contract ADDR \
--constructor-args \
$(cast abi-encode ...)

agreed this would be super helpful—are you up for it @klkvr ?

sure! but i have a lot of stuff on me atm, so i could start with it in a week or two

yep no rush—everyone's on the holidays rn. Feel free to go at it whenever! will assign so we don't lose track

Hey @Evalir I have opened PR to support fetching of contract creation tx for block-explorers.
I will also need to somehow be able to get access to RPC-endpoint of the corresponding network to get/trace deployment tx. It seems that it is not possible to get rpc endpoint from configuration by chain_id without iterating over each of endpoints and comparing eth_chainId response.
I can see 2 ways to solve this:

Force users to specify rpc-url when --guess-constructor-args is used.
Add logic to query Etherscan geth proxy using the same endpoint and API key

Option 1 messes with UX a little bit. And option 2 is hard to implement in a clean way (Etherscan Geth proxy doesn't work as a standard RPC-endpoint, you have to specify method as a query parameter)
Do you see any other options and what do you think about those?

Hmmm, yeah I think we can go with option one—we can add a little note on the --guess-constructor-args that lets the user know why this needs --rpc-url, even if it's a little bit cumbersome @klkvr


Windows Compatibility

Hi @ncoop57 ,
Thanks for the great work!!!
Can I use this in windows? Because when I setup this in my windows machine, DataProcessor.PARSER.set_language is not working. Just out of curiosity, I opened tree-sitter-languages.so file and I found this -

Could you suggest how to solve this..?

This problem is caused by the tree-sitter, it seems that the old version of the tree-sitter had some issues on Windows x64, but they had fixed the bug with a new version, so you need to install a slightly newer version

@MarsChenSE Do you know which version specifically works with Windows? I worry having a new version of tree-sitter because the current implementation of function_parser needs a very specific one to avoid breaking compatibility. It has been on my todo list for a long time to overhaul function_parser to the newest version of tree-sitter as the newest tree-sitter has a way easier to use API, but limited time prevents it. So, if the newer version of tree-sitter that works with Windows x64, but not function-parser, it would probably be better to use WSL on Windows (not 100% sure if this will by pass the problem, but it might)

Closing this for now


[core] Assert in InitWindow()

Environment: Tested agains raylib 3.0 from master branch, commit:
commit 6a8b1079c13b7d5e1bddc0ecc86ad7e16fc2556d (HEAD -> master, tag: 3.0.0, upstream/master, origin/master, origin/HEAD)
Author: Ray<EMAIL_ADDRESS>Date:   Mon Mar 30 23:42:17 2020 +0200
    Update project version for release

Issue description
I'm still working on the tests of raylib functions. testing different arguments for this function:
void InitWindow(int width, int height, const char *title)
So far I found that this function generates asserts in glfw/src/window.c, for negative numbers of width or height, and for NULL titles.
Is assert the best reaction? Perhaps raylib coud check these parameters before passing them to glfw and change to a default values if they are not valid.
Environment
Compiled for PLATFORM_DESKTOP, , WINDOWS, RELEASE mode, STATIC library using Min GW, OpenGL 3.3
Issue Screenshot

Code Example
This is the code in glfw that generate the asserts:

Is assert the best reaction? Perhaps raylib coud check these parameters before passing them to glfw and change to a default values if they are not valid.

I think asserting when there's an error is important, helps prevent bugs down the line

@danimartin82 @louisgjohnson I also prefer let GLFW warn the user about this problem.
Actually, you will find in raylib many places were user can pass wrong data to the library, from my point of view, I can try to make life easier to the user but I'm not checking for all missuses of coding.
Like I teach to my students, they should be responsible of the data they manage. Crashing the app (or not) it's on their hands. Watch your data!


Google Play Services Consulting

Hello I would kindly ask about adding dependency and changing project file to push app to google play. I found in code this.
// WARNING! WARNING!  WARNING!  WARNING!  WARNING!  WARNING!  WARNING!  WARNING!
// WARNING!  Don't add dependency on Google Play Services without consulting
// WARNING!  The China marketing team
// WARNING!  Many Chinese Android phones execute (meaning terminate) any app that
// WARNING!  users google gms summarily, like immune systems cleansing infections
// WARNING! WARNING!  WARNING!  WARNING!  WARNING!  WARNING!  WARNING!  WARNING!
Your advise would be highly appreciated. Thank you.

Hi @muchaartur it's because we do a build for China, where Google services aren't permitted due to CCP policy. Some phone OS (like Huawei) detect if apps are attempting to use Google services (or if they are built with Google services libraries) and they may force terminate that app.
This warning is less relevant now, because we do separate builds for China/FSDroid which don't have any Google service libraries. If you go to 'Build Variants' in the AndroidStudio project you'll find the 'noAnalytics' project builds which build without those libraries.
I hope this helps!

thank you!


Nested child doesn’t update on back after page reload

When navigate back after a page reload the child page isn't reloaded.
Steps to reproduce:

Click "To second"
Reload page trough browser
Click browser back button

Page should be home instead of second

Example code (click to expand):
import 'package:flutter/material.dart';
import 'package:qlevar_router/qlevar_router.dart';

class App extends StatelessWidget {
const App({super.key});

@override
Widget build(BuildContext context) {
  return MaterialApp.router(
    routeInformationParser: const QRouteInformationParser(),
    routerDelegate: QRouterDelegate(
      AppRoutes().routes,
      initPath: '/dash',
    ),
  );
}
}

class AppRoutes {
static const String homePage = 'Home Page';
static const String secondPage = 'Second Page';

final routes = [
  QRoute.withChild(
    path: '/dash',
    builderChild: (child) {
      final routeName = child.routeName;
      return Scaffold(
        appBar: AppBar(
          title: Text(routeName),
        ),
        body: child,
      );
    },
    children: [
      const QRoute(
        name: homePage,
        path: '/',
        builder: HomePage.new,
      ),
      const QRoute(
        name: secondPage,
        path: '/second',
        builder: SecondPage.new,
      ),
    ],
  ),
];
}

class HomePage extends StatelessWidget {
const HomePage({super.key});

@override
Widget build(BuildContext context) {
  return Column(
    children: [
      const Center(child: Text('Home')),
      ElevatedButton(
        onPressed: () {
          QR.toName(AppRoutes.secondPage);
        },
        child: const Text('To second'),
      ),
    ],
  );
}
}

class SecondPage extends StatelessWidget {
const SecondPage({super.key});

@override
Widget build(BuildContext context) {
  return Column(
    children: [
      const Center(child: Text('Second Page')),
      ElevatedButton(
        onPressed: () {
          QR.toName(AppRoutes.homePage);
        },
        child: const Text('To Home'),
      ),
    ],
  );
}
}

void main() {
runApp(const App());
}

Hi @carlosfiori ,
if you want to always add the initroute in the stack, even after a restart, you need to set QRouterDelegate.alwaysAddInitPath to true. But there was an error even then that I have fixed. See the test.


Add test

Pull Request
Description
add some small tests on the loss, thought it might inspire other people to write tests
How Has This Been Tested?
Ran tests locally
CI runs tests

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #37 (e0d1588) into main (5447341) will increase coverage by 1.66%.
The diff coverage is n/a.

:exclamation: Current head e0d1588 differs from pull request most recent head 76b9c29. Consider uploading reports for the commit 76b9c29 to get more accurate results

@@            Coverage Diff             @@
##             main      #37      +/-   ##
==========================================
+ Coverage   68.77%   70.44%   +1.66%
==========================================
  Files          12       12
  Lines         839      839
==========================================
+ Hits          577      591      +14
+ Misses        262      248      -14

Impacted Files
Coverage Δ

dgmr/losses.py
30.53% <0.00%> (+8.38%)
:arrow_up:

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


Support adding tags on RunTaskRequest

What does this PR change?
This PR enables users to specify Tag for RunTaskRequest on EcsCommandExecutor.
Background
Amazon ECS supports tag for ecs tasks as arbitrary meta data of them. It is useful to manage/find ECS tasks on AWS console.
Expected use cases are

Specifying project name
Specifying notes

Thanks!