ui: add file support for preference

preference can be download to file to share with others
and upload from file.

@masco-enovance Can you please this PR against master ?

rerun functional-tests-backend-elasticsearch

I lost many preferences fields if I import this exported file
"{\"favorites\":[],\"bandwidthThreshold\":\"relative\"}"

before writing to the file JSON stringfy happened two times, now working fine.


Retain original exception when parsing fails type conversion

Fixes #67

As I see, the valueOf and fromString invocations may suffer the same problem, but I haven't tested them yet. I label this as Work-In-Progress for now and update it soon.

Had to struggle a bit with tests, but now it seems complete, squashed and ready for review.

@rtib i realized we don't have checkstyle enabled in airline yet.
I posted a PR (https://github.com/airlift/airline/pull/69). You may want to rebase on top.

rebased to #69

@rtib sorry for the delay. We had some internal discussion about https://github.com/airlift/airline/pull/68#discussion_r347576023
Can you please rebase & squash commits?
I'll do final pass then

Rebase to what base?

current master. the other PR is merged now.

Merged, thanks!
sorry for the delay, i didn't know you updated the PR

I just released airline 0.9.
@rtib thanks again for your contribution!


Implement the VibronicStructureProblem

What is the expected feature?
Implement the VibronicStructureProblem class. (the name is a WIP)
It may be located in the qiskit_nature.problems.second_quantization.vibrational module. (Or do we want this to be in qiskit_nature.second_quantization.molecular?)
An important aspect to consider here, is that this implementation is responsible for the correct construction of the SecondQuantizedOp. This means, that it needs to handle the differentiation of modes and modals and construct the BosonicOp accordingly.

Closed by #79


beers: make untappd icons square

Added all image formats to checkin structure
Changed which image is selected for display in the channel

Works in channel.


Fixing lots of details

-Including div verse ranges;
-Changing the formatting of heading scripture to italic and including
its p osisIDs;
-Formatting some Fathers names that were skipped;
-Where I found the name of a Father inside the text (indicating that it
is actually the beginning of another part), I added the corresponding
new "" element
Some tweaks for using this OSIS with SWORD:
-When there is an overlap of verse ranges, I chose to end the first
range one verse before (otherwise the second commentary gets ignored);
-For some reason, when a  element has only text (with no other
elements inside), the program doesn't include a new line after it, so I
included a dummy tag to "fix" it

Thank you. I am extremely unfamiliar with this sort of thing, and only tried to create it because of the great value this work offers.

Actually I thank you, you did a great job with your OSIS (as far as I can tell). I also wanted to make a Catena Aurea module, and was happy to find you had already started one.
I had no prior experience with this format (and was procrastinating using only .imp files, that are simpler but less powerful). You've done all the hard work building the OSIS file, so that all I had to do was to tweak your solution a little.
I've used Python with BeautifulSoup4 (opening with the lxml parser). There's only so much you can do with only regexes to deal with xml before going insane...


gem5: make explicit power modelling parameters

It is currently assumed in the gem5 power instrument that the platform
has been appropriately configured to bind gem5 with power models. This
makes this configuration explicit in Gem5SimulationPlatform and extends
the power instrument setup with a check on that.

@setrofim, @Sticklyman1936 , @ionela-voinescu
Any chance one of you guys has a feedback on that ?

This looks good to me, but I would like @avanlaer to take a quick look.

This looks good to me as well, only one slight remark.

Closing, as power management configuration is too tied to user-provided gem5 configuration scripts for there to be a useful generic configuration interface in devlib.


Add optional properties for autocomplete functionality when doing robotics

Putting this here for discussion purposes mainly, we got this forum question recently and it reminded me of the discussion we had before - this PR implements @angusjfw's suggestion from that.
These are the limitations with the approach I can see (there are probably more):

There are a lot more components that can be added to a Pitop object dynamically and this will grow with time (e.g. PMA, NavigationController etc) - this currently only covers the common properties for robotics. Could we add these Optional properties based on a master list we keep somewhere that defines all Recreatable components?
People might incorrectly assume that these properties are available before they've used the add_component or from_config methods - resulting in errors and confusion. I'm not sure if we can catch this at runtime and provide an explanation of what to do but that would certainly help. My hope is that they will follow the examples properly and in the cases where they don't, will read the docs and see how to do it properly.

Don't think there is a very clean way of achieving this with the current architecture, closing for now


sc-2467 trtl DirectoryStore

This implements the DirectoryStore methods for the trtl store. One thing absent from this PR is the index handling but I've added some TODO comments in the methods to capture that. This also adds a bug fix for the trtl Iter(), we were not checking the tombstone on the objects and so were accidentally returning deleted objects.

Codecov Report

Merging #316 (cdc511a) into main (74b22c5) will increase coverage by 0.25%.
The diff coverage is 59.70%.

:exclamation: Current head cdc511a differs from pull request most recent head 3100bdd. Consider uploading reports for the commit 3100bdd to get more accurate results

@@            Coverage Diff             @@
##             main     #316      +/-   ##
==========================================
+ Coverage   45.98%   46.24%   +0.25%
==========================================
  Files          61       64       +3
  Lines        7491     7714     +223
==========================================
+ Hits         3445     3567     +122
- Misses       3403     3487      +84
- Partials      643      660      +17

Impacted Files
Coverage Δ

pkg/gds/store/trtl/iterator.go
50.43% <50.43%> (ø)

pkg/gds/store/trtl/trtl.go
56.43% <69.62%> (ø)

pkg/gds/store/trtl/mock.go
100.00% <100.00%> (ø)

pkg/trtl/trtl.go
76.01% <100.00%> (+0.15%)
: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 74b22c5...3100bdd. Read the comment docs.


Update to Chromium 77.0.3865.90

Fixes CVE-2019-13685, CVE-2019-13688, CVE-2019-13687, and CVE-2019-13686. I am compiling ungoogled-chromium 77.0.3865.90 for the portablelinux target now and will let you know once I have a successful build.

The build succeeded. Feel free to merge.


[BUG] Open report doesn't use maven wrapper

Describe the bug
I tested the extension on a machine that doesn't have Maven installed globally. I have a project that has the mvnw wrapper instead. When clicking on the report icon in the status bar, I got an ugly error
To Reproduce
Steps to reproduce the behavior:

don't have Maven installed globally
open maven project using a mvnw wrapper
click on the report icon
See error

Expected behavior
Opening the report should favor using the wrapper if it exists, before using the global mvn command
Screenshots

VSCode(please complete the following information):

OS: Win 10
VSCode version 1.60.2
Dependency Analytics Version 0.3.3

It would be nice if it would honor "maven.executable.preferMavenWrapper": true


Dependency Update and Spring Cleaning

We have updated quite some dependencies and cleaned out stuff that wasn't working, fixing a couple of bugs in the progress (for example to process RPI3 packets!)
What needs to be done is probably to:

[ ] test whether the docker-compose setup works reliably
[ ] test whether it works together with analysis ;)

has anyone got heat map working ?


Feature/web page

This PR aims to add a simple web page to the Tutorial Maker project. Please feel free to review it, give feedback, and ask for improvements.

@pauloguilhermepp where can I review the resulting webpage?

Currently, you can access it here @LuskasHusty https://pauloguilhermepp.github.io/TutorialMaker/Index. After the PR, we can access it using another link (without my user).  If it makes sense to you, we can also create a specific repository for the web page and its link would start with the repository name.

We'll probably want to change this to another repo, I think it's supposed to be this one (https://github.com/SlicerLatinAmerica/SlicerLatinAmerica.github.io/) but @DouSam can clarify on that.
Even then, there are some issues:
It seems that on the collaborations and diversity page, there's only info from the perspective of the brazillian team;
There are some minor html mistakes;
I don't think it follows the African team model on how the deliverables should be presented.

@pauloguilhermepp a few things we need to change.
To clarify, the idea here is to copy this page from the African team.
Because we already have this page, which is the repository and the project page, there is no need to create a new one.
We need a page to show the tutorials like the African team did. To show the project, etc, we already have a page, just update that and make a PR in the other repository.
So, the activities now:

Clone the repository https://github.com/SlicerLatinAmerica/SlicerLatinAmerica.github.io on our computer
Update the page by:
The content of this page, except the tutorials, https://pauloguilhermepp.github.io/TutorialMaker/Index  you can put in a page on the other repository with the name "Our Work"
The content of this page https://pauloguilhermepp.github.io/TutorialMaker/TutorialMakerTool you can put in the same page "our Work" of the other repository, in a different section
https://pauloguilhermepp.github.io/TutorialMaker/ProfessionalEvents Create a new page "Events" and also update the main page list with these events
Verify if the list of members is updated on the website

Any doubts, you can create a new PR in the other repository, and post the questions in that.


[ts] Cannot find name 'resolve'. Did you mean 'reolve'?

When i was trying to implement Promises in typescript , it suggested to use 'reolve' instead of  'resolve.'
Code
type postItem  =  {title: string,author: string, id: number}
type post = Array<postItem>;

type authorItem =  {name: string,twitter: string,bio: string}
type author = Array<authorItem>;

class searchPost {

    posts:post =  [
        {title:"I love javascript",author:"Wes Bos",id:1},
        {title:"CSS!",author:"Chris Coyier",id:2},
        {title:"Dev Tools",author:"Addy Osmani",id:3}
    ];

    searchPostById(id){
         return new Promise((reolve,reject) => {
            const post = this.posts.find(post => post.id === id)
            if(post){
                reolve (post);
            }
            else {
                reject(Error('No Post was Found'));
            }
        })
    }
}

var post =  new searchPost();

post.searchPostById(2)
.then(post => {
    console.log(post);
})

Expected behavior:
Typescript should support resolve not reolve.
Actual behavior:
Typescript is suggesting to use reolve instead of resolve when working with promises. Although when i run code with reolve , it works fine.
tsconfig:
{
    "compilerOptions": {
        "module": "es6",
        "watch": true,
        "target": "es6",
        "strictNullChecks":false,
        "sourceMap": true,
        "experimentalDecorators": true

    },
    "exclude": [
        "node_modules"
    ]
}

typescript version:
$ tsc -v
Version 2.8.0-dev.20180318

The names of the parameters to the Promise callback constructor are up to you. You wrote the name reolve:
   return new Promise((reolve,reject) => {

TypeScript is simply enforcing that you actually refer to the parameter you yourself wrote.


Block-SpMM TPP for x86 (avx2, avx512, AMX) and ARM (sve256)

This PR introduces Block-SpMM TPP for x86 (avx2, avx512, AMX) and ARM (sve256) (supported precisions: F32, BF16, INT8)

Can you please add a unit test?

I suggest also removing the sparse_weight_matrix, etc. in samples/deeplearning as they are superseded by parlooper benchmarks, correct?

Nope, those ones cover also the plain csc, csr, with hardwired sparsity etc...
The parlooper benchmark covers only the new bcsc kernel.

Fine for now, I'm just wondering in which case the plain csc/csr/hardwired sparsity would be useful == faster than the code we are merging.


DataStore ObserveQuery snapshot on .ready

Describe the bug
ObserveQuery does not emit a snapshot when the state goes from isSynced false to true. Internally, the operation will listen to .ready event from the Hub. When this is received, it will mark internally the isSynced state to true, but does not emit a new snapshot.
Customer DX issue: If the loading indicator is displayed to the end user, and .ready is received, it should no longer be loading since the data is in sync. The next item update will cause the observeQuery to emit the next snapshot with isSynced true, which means there's a delay in removing the loading indicator.
Internals
There is a bit of change required than just emitting the event since the state of the modelSynced event is what's driving the isSynced value. Everytime a snapshot is emitted, it's using the dispatchedModelSyncedEvent value, which is set by another process.
Steps To Reproduce
.

Expected behavior
.
Amplify Framework Version
.
Amplify Categories
DataStore
Dependency manager
Cocoapods
Swift version
.
CLI version
.
Xcode version
.
Relevant log output
No response
Is this a regression?
No
Regression additional context
No response
Device
.
iOS Version
.
Specific to simulators
No response
Additional context
No response

An edge case to consider is when the dataset is empty. observeQuery should emit a snapshot with isSynced true in that scenario as well

Thinking about this some more, i think it's as simple as the DataStoreObserveQueryOperation to emit a snapshot on .ready event. the problem is addressing emitting two snapshots, one for the .ready event and one for the dispatchedModelSyncedEvent. empty data set scenario can be tested and should have no impact on this change

this was released in https://github.com/aws-amplify/amplify-swift/releases/tag/v2.0.0 and https://github.com/aws-amplify/amplify-swift/releases/tag/v1.28.2


Vuex usage and passing global message options

When I call function flash() from Vuex it works but it doesn't apply global options like
Vue.use(VueFlashMessage, {
  messageOptions: {
    timeout: 1000,
  }
});

Calling it from Vuex does also support passing global options?

Yep, same here. The options unfortunately only appear to be respected calling this.flash() from a Vue component, not a Vuex store.


Issue 2000 network policies

Support or network policies

Add 'networkPolicy' element to infra configs
Add 'networkPolicy' element to address spaces
Add controller to handle updates and delete
Add unit tests

Address spaces override infra configs.

@k-wall Addressed the in-code comments.
Regarding uninstall, the networkpolicy objects are namespaced and part of the enmasse-infra namespace, so they will be deleted in the current uninstall docs.

@k-wall Example infra config
kind: StandardInfraConfig
...
spec:
   networkPolicy:
      ingress:
         - from:
              - podSelector:
                   my: label

I'm having problems with an end to end test.  I keep meeting deserialisation issues.   The example document you have above doesn't match the structure of the Java code.  In the structure above the networkPolicy has an array of networkPolicyIngressRule, but the Java code the NetworkPolicy has a single NetworkPolicyIngressRule instance.

I'm having problems with an end to end test. I keep meeting deserialisation issues. The example document you have above doesn't match the structure of the Java code. In the structure above the networkPolicy has an array of networkPolicyIngressRule, but the Java code the NetworkPolicy has a single NetworkPolicyIngressRule instance.

No, there is only one ingress field in the yaml above. According to json2yaml.com, it is equivalent to the following json:
{
  "spec": {
    "networkPolicy": {
      "ingress": [
        {
          "from": [
            {
              "podSelector": {
                "my": "label"
              }
            }
          ]
        }
      ]
    }
  }
}

It still looks wrong to me..  I am definitely running the latest code from your branch. Take a look at the attach test.  The first test case   (which includes your YAML translated to JSON) fails with a deserialisation error. In the second, I've modified the input to give ingress an object rather than an array.
com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize instance of `io.fabric8.kubernetes.api.model.networking.NetworkPolicyIngressRule` out of START_ARRAY token
 at [Source: (String)"{
  "spec": {
    "networkPolicy": {
      "ingress": [
        {
          "from": [
            {
              "podSelector": {
                "my": "label"
              }
            }
          ]
        }
      ]
    }
  }
}"; line: 4, column: 18] (through reference chain: io.enmasse.admin.model.v1.StandardInfraConfig["spec"]->io.enmasse.admin.model.v1.StandardInfraConfigSpec["networkPolicy"]->io.enmasse.admin.model.v1.NetworkPolicy["ingress"])

InfraConfigDeserializerTest.txt

@k-wall You are right, i was confusing the examples from the NetworkPolicy docs[1] where ingress is an array, with the format expected by 'our' NetworkPolicy. The format in the deserialiseSucceeds is the right format, sorry for misleading you.
[1] https://kubernetes.io/docs/concepts/services-networking/network-policies/

Regarding the leaks, does it print the message only once or each time the controller is run? I'll do a test as well to check

It appears to be a leak per request. The leak reports seem to collate with GC cycles, so you may not see the leak report immediately.

@k-wall pushed an update that should comply with the schema


Zk

Hello

hi

how this?

What is this? Please post your issues guys. This is not for posting blank posts.

good

Hello .  What is this email for?
در تاریخ چهارشنبه ۷ فوریه ۲۰۲۴، ۲۰:۰۰ sinatg1995 @.***>
نوشت:

good
—
Reply to this email directly, view it on GitHub
https://github.com/zksync/credo/issues/70#issuecomment-1932423300, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A2ZZRUD4NVGTK7HGV5XW2B3YSOTZ3AVCNFSM6AAAAABAY572ZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZSGQZDGMZQGA
.
You are receiving this because you commented.Message ID:
@.***>

Hello

Are there anything to do here?

Are there anything to do here?

no , just say Hi

Hello everyone
iOS için Outlookhttps://aka.ms/o0ukef uygulamasını edinin

Gönderen: truong giang @.>
Gönderildi: Friday, February 16, 2024 2:45:26 PM
Kime: zksync/credo @.>
Bilgi: Burhan @.>; Comment @.>
Konu: Re: [zksync/credo] Zk (Issue #70)
Are there anything to do here?
no , just say Hi
—
Reply to this email directly, view it on GitHubhttps://github.com/zksync/credo/issues/70#issuecomment-1948242221, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDYGZXLYQLFTM4S6Z6UKYKDYT5BFNAVCNFSM6AAAAABAY572ZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGI2DEMRSGE.
You are receiving this because you commented.Message ID: @.***>

Hi

Hello everyone, have a nice dev journey

why everyone is spaming here ? guys use this to solve your issues not for entertainment

hi 👋 I hope today is the exact day for you, the day your dreams come true for which you worked so hard, so continue with strength... And remember that the windshield of the car is much bigger and clearer than this small one in the middle of the glass... so take your focus from the past image and move forward.


feature(dashboard): ecosystem create form

PR-Codex overview
This PR introduces new error handling classes, updates UI styles, adds new components for ecosystem management, and refactors user authentication logic.
Detailed summary

Added FetchError class for error handling
Updated UI styles for better visual consistency
Introduced new components for ecosystem management
Refactored user authentication logic for improved user experience

The following files were skipped due to too many changes: apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/hooks/use-ecosystem.ts, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/hooks/use-ecosystem-list.ts, apps/dashboard/src/app/(dashboard)/dashboard/components/sidebar/sidebar.client.tsx, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/layout.tsx<EMAIL_ADDRESS>apps/dashboard/src/app/components/DashboardFooter.tsx, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/hooks/use-delete-partner.ts, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/components/client/integration-permissions-toggle.client.tsx<EMAIL_ADDRESS>apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/hooks/use-update-ecosystem.ts, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/create/page.tsx, apps/dashboard/src/app/(dashboard)/(chain)/chainlist/components/server/chainlist-card.tsx, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/create/hooks/use-create-ecosystem.ts, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/hooks/use-add-partner.ts<EMAIL_ADDRESS>apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/components/client/ecosystem-header.client.tsx, apps/dashboard/src/app/(dashboard)/(chain)/chainlist/components/client/filters.tsx, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/page.tsx, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/components/server/partners-table.tsx<EMAIL_ADDRESS>apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/create/components/client/create-ecosystem-form.client.tsx, apps/dashboard/src/app/(dashboard)/dashboard/connect/ecosystem/[slug]/(active)/components/client/add-partner-form.client.tsx<EMAIL_ADDRESS>pnpm-lock.yaml

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3537  👈
#3535
#3531
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gregfromstl and the rest of your teammates on  Graphite

only blocker is API needs to be rolled out to prod first


Doc enhancement to add more information to find the "service name" & "api ID" in the given example below.

Can you elaborate on how to find the "service name" & "api ID" with using this custom role in API Management? Could more clarity be given on how to find the right values for lines 8 and 10? This will be helpful in implementing this in an environment. You most likely can find this with CLI or Azure PowerShell commands but providing that information would be helpful here.

Full sample example:
$role = Get-AzRoleDefinition "API Management Service Reader Role"
$role.Id = $null
$role.Name = 'Calculator API Contributor'
$role.Description = 'Has read access to Contoso APIM instance and write access to the Calculator API.'
$role.Actions.Add('Microsoft.ApiManagement/service/apis/write')
$role.Actions.Add('Microsoft.ApiManagement/service/apis/*/write')
$role.AssignableScopes.Clear()
$role.AssignableScopes.Add('/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//apis/')
New-AzRoleDefinition -Role $role
New-AzRoleAssignment -ObjectId  -RoleDefinitionName 'Calculator API Contributor' -Scope '/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service//apis/'

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

ID: 7f6c6659-7532-1696-7875-b4bf01d3862e
Version Independent ID: ad6e75d0-691f-a08b-e5f0-3f94cbf68fdf
Content: How to use Role-Based Access Control in Azure API Management
Content Source: articles/api-management/api-management-role-based-access-control.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

Thank you for your feedback! We will review and update as appropriate.

@j-dahl7 Thanks for your feedback. The service name refers to your APIM instance name and api ID refers to the Unique name of the api that you have created on your APIM instance.
I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thank you so much! This helps a lot.


PVOutput support

Enhancement to upload Solariot metrics to pvoutput.org.
API specs: https://pvoutput.org/help.html#api-spec

PR's up, just needs testing once my solar inverter is online again... why can't the sun just stay up all the time...

Tested it out in my PR and it all seems to be working and publishing nicely!
Looking at modbus-sungrow-sh5k.py I can't see any of the v1 through v4 attributes though, are they different names?
Currently I've got:
            if "daily_power_yield" in metrics:
                parameters["v1"] = metrics["daily_power_yield"]

            if "total_active_power" in metrics:
                parameters["v2"] = metrics["total_active_power"]

            if "daily_energy_consumption" in metrics:
                parameters["v3"] = metrics["daily_energy_consumption"]

            if "power_meter" in metrics:
                parameters["v4"] = metrics["power_meter"]

As per comments in your PR, I've made some updates to handle different modbus maps and also stay within the API rate limits.


[Announcment] The IHttpContextAccessor service is not registered by default

IHttpContextAccessor can be used to access the HttpContext for the current thread. However, maintaining this state has non-trivial performance costs so it has been removed from the default set of services. Developers that depend on it can add it back as needed:
services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();
RE: https://github.com/aspnet/HttpAbstractions/issues/473

So of we don't inject httpcontext we won't have Access to User in our controllers ?

@zigzag95 IHttpContextAccessor is only intended for accessing the HttpContext in locations where it's not directly available. HttpContext and User are directly available in MVC Controllers so you do not need IHttpContextAccessor.

In that sample, you are registering it as a singleton. Shouldn't it be a scoped instance?

services.AddIdentity registers this anyway.
https://github.com/aspnet/Identity/blob/79dbed5a924e96a22b23ae6c84731e0ac806c2b5/src/Microsoft.AspNetCore.Identity/IdentityServiceCollectionExtensions.cs#L54
A lot of applications will need identity so this change is moot really and to me is just confusing as if you use identity you get IHttpContextAccessor but if you don't it doesn't.
So if using identity you get IHttpContextAccessor 'magically'.
Even though HttpConext is available in controller I still want to avoid new on my objects and prefer DI.
Now it is not clear when you need to register IHttpContextAccessor.
What would be the result of registering it twice.
ie
services.AddIdentity<ApplicationUser, IdentityRole>()
                .AddEntityFrameworkStores<ApplicationDbContext>()
                .AddDefaultTokenProviders();
            services.Configure<IdentityOptions>(options =>
            {
                options.Cookies.ApplicationCookie.LoginPath = new PathString("/default/Account/Login/");
            });

            services.AddMvc();
            services.AddAuthorization();
            services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();

The above code runs fine buy is there a performance hit to AddIdentity reqistering IHttpContextAccessor and registering it myself.
I would prefer to register it explicitly as it is cleared to my code.

The above code runs fine but is there a performance hit to AddIdentity reqistering IHttpContextAccessor and registering it myself.

Performance hit? Is that speculation or did you measure?

In that sample, you are registering it as a singleton. Shouldn't it be a scoped instance?

It's fine being a singleton because the backing store is async local.

@davidfowl

Performance hit? Is that speculation or did you measure?

I am just not sure of the mechanics of registering it again.
AddIdentity is already providing an instance of HttpContextAccessor but I prefer to explicitly register it.
I don't perceive any performance hit (I didn't notice when IHttpContextAccessor instatiation was removed from Hosting Either :-).
I just wanted to make sure there wasn't a problem registering it again.

There is no problem registering it again and certainly no measurable performance hit.

@Eilon  re the advice to use

services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();

Would it not be better to advise using the TryAdd version
services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>();
since it may not be clear that the service may already be registered by another service and we don't need 2 instances.
That way if IHttpContextAccessor is already registered by another service eg `AddIdentity'  a duplicate is not created.  Other aspnet services use the TryAdd version for this reason I believe.
See my discussion above with @davidfowl

In that sample, you are registering it as a singleton. Shouldn't it be a scoped instance?
It's fine being a singleton because the backing store is async local.

Actually if you re-register it as a Transient on .NET Core then it doesn't work properly since the implementation for .NET Core is using a AsyncLocal which relies upon the instance variable to track the TLS storage slot.

@mikes-gh Sure, TryAdd is slightly better, but shouldn't affect functionality or perf.

@Tratcher I may not be understanding the mechanics but if there is no performance impact to registering a second instance why was the default instance removed?

Only one registered instance gets used so there is a perf difference between 0 and 1, but not between 1 and 2.

Ok got it thanks .  I still think the announcement should sugest TryAdd though.

I still think the announcement should sugest TryAdd though.

It doesn't matter -- it must be a singleton, so doing additional DI config with different lifetimes won't work anyway.

@brockallen
TryAddSingleton is the same lifetime as AddSingleton.  The difference is TryAdd version checks for the existence of the  object in the  service collection and any only adds it  if it's not already there.  See Dependency Injection repo for the code.

@brockallen TryAddSingleton is the same lifetime as AddSingleton.

This distinction wasn't my point. My point was that the class (either by design or by accident) will only work as a singleton.

Conceptually the DI provider is a typed dictionary with the service type as the key. So any service can be registered in a for loop a thousand times, it won't have much effect apart from startup performance - which is negligible unless you actually do use a for loop.
I believe the scoping of any service is fixed once it is registered for the first time, I believe that's true for the implementation type as well - correct me if I'm wrong. I recall @DamianEdwards fixed a bug with caching on stage at a conference (//Build?) by simply registering a singleton before registering EF - which would register the same service type as transient. I'm just too lazy to test it right now, it'll probably take about two minutes...

Or maybe all service registering should be using  TryAdd logic.
Drop TryAdd and move the uniqueness check to Add method.
That would make sure the service collection correctly matches what will be instantiated.  That way the useless entries never make it into the collection..

This announcement creates a very awkward feeling. The way it's stated gives the impression that we should not use it. But, identity is using it, so a vast majority of apps developed with aspnetcore will depend on it, so I guess (hope) that the cost of this is not that bad or they may be something extremely wrong with identity implementation.

non-trivial performance costs

@Tratcher The above is the justification for removal of IHttpContextAccessor by default.
Yet as @sandorfr  points out it will be in a LOT of web apps due to identity requiring it.
Should we be concerned about performance in all apps that use  identity?
This post does sound like it is discouraging use of IHttpContextAccessor but I'm not sure what to use as an alternative.

@mikes-gh one of the major tenants of Asp.Net Core is pay-for-play, e.g. you only pay the costs of the components you use. Yes, many apps will use Identity and those apps will have higher costs than apps that don't (and not only because of IHttpContextAccessor). The added cost is not prohibitive, just it's unnecessary for other kinds of applications.

The added cost is not prohibitive

Thanks for clarifying that :).

So how do you access the HttpContext from IHttpContextAccessor in configuring custom service now?
I'm trying to accessing HttpContext in BrowserDetectorService and get null when the app run.

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.

The HttpContextAccessor seems to be registered by default in .NET Core 2.0.2. This is partially shown in my issue on StackOverflow.

No, the stack does not register it by default, but one of your dependencies may. For example ApplicationInsights registers it.

It is registered in debug mode but in publish mode it is not registered. What is the differences between them?

It is registered in debug mode but in publish mode it is not registered. What is the differences between them?

@ahmetsevgili  I have the same problem. Have you already solved it?
Help me, please

That may be ApplicationInsights only registering it when enabled.

Application Insights is automatically registered in your application when you launch it under the debugger in Visual Studio, such that you can see & search events coming from your application while debugging in the VS Application Insights search experience. This is the most likely cause of the IHttpContextAccessor being available in debug but not after the application is published. If you need it, please register is explicitly yourself in ConfigureServices.

@promanchenko-softheme, use like @Tratcher said that above. Both debug and publish mode work fine after adding
services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();
line
my ConfigureServices snippet like below
public void ConfigureServices(IServiceCollection services)
        {
            services.AddMvc();
            services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();

Visual Studio debugger registering IHttpContextAccessor is extremely misleading. It took me a while to find out what the real cause of my "bug" was

Experienced this issue in a slightly different context to what's already been posted. When publishing an ASP.NET Core 2 API project via our CI process to an IIS server the following exception is raised:

InvalidOperationException: Unable to resolve service for type 'Microsoft.AspNetCore.Http.IHttpContextAccessor'...

Locally, we're debugging using Kestral and the exception doesn't raise.
Adding services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>(); to the RegisterServices(IServiceCollection) method has resolved the issue in IIS, but I'm curious why this isn't an issue when self-hosting?

That's going to be fixed in 2.1, it has to do with the fact that application insights was being injected in visual studio by default and adding those services but only when debugging. We're making some adjustments so we don't have a different debug/non-debug experience by default.

So does that mean adding back HttpContextAccessor service by default?

So does that mean adding back HttpContextAccessor service by default?

No

hello @davidfowl was wondering if you can help me, i have the same issue
Application startup exception: System.InvalidOperationException: Unable to resolve service for type 'Microsoft.AspNetCore.Http.IHttpContextAccessor' while attempting to activate 'Web.Startup'.
I have this line services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>(); in my Startup.cs
and my IIS host is running with Microsoft.AspNetCore.Hosting version 2.0.1-rtm-125
Suggestions? Thank you! :)

@davidfowl

No

How is it solved then?  Code analyzer to catch the dependency in debug build? or.....

As HttpContextAccessor is just a wrapper around a single private static variable I see no reason why it should make any difference anywhere whether it is registered Singleton, Scoped or Transient.


"No Such Object" when using Client Modify

I'm getting "No Such Object" error when I try to modify a group, even though the DN provided is correct.
I added Bunyan to inspect logs, and I could see from the response that object was empty.
const client = ldap.createClient({
   url: 'LDAPS:/xxx',
   tlsOptions: {
      rejectUnauthorized: true,
      cert: fs.readFileSync('xx.pem'),
      ca: fs.readFileSync('xxx.pem'),
   },
   reconnect: false,
   log: new Bunyan({
      name: 'ldapjs',
      component: 'client',
      stream: process.stderr,
      level: 'trace',
   }),
});

Response:
{
   "name": "ldapjs",
   "component": "client",
   "hostname": "x",
   "pid": 33960,
   "clazz": "Client",
   "ldap_id": "x",
   "level": 10,
   "msg": "sending request {\"messageId\":3,\"protocolOp\":102,\"type\":\"ModifyRequest\",\"object\":{},\"changes\":[{\"operation\":\"add\",\"modification\":{\"type\":\"member\",\"values\":[\"CN=xx\"]}}],\"controls\":[]}",
   "time": "2023-08-02T11:58:39.461Z",
   "v": 0
}

Function for modifying:
client.modify('cn=foo,dc=example,dc=com', change, (err) => {
   if (err) {
      console.log(err);
      reject(new Error(err.message));
   } else {
      console.log('la til i gruppe %j', null);
      resolve(null);
   }
});

I solved it by manually editing the ensureDN function in the \node_modules\ldapjs\lib\client\client.js file from:
function ensureDN(input) {
  if (DN.isDn(input)) {
    return DN
  } else if (typeof (input) === 'string') {
    return DN.fromString(input)
  } else {
    throw new Error('invalid DN')
  }
}

To:
function ensureDN(input) {
  if (DN.isDn(input)) {
    return DN
  } else if (typeof (input) === 'string') {
    return input // instead of DN.fromString()
  } else {
    throw new Error('invalid DN')
  }
}

Is this a known issue, or am I missing something?

Is this a known issue, or am I missing something?

https://github.com/ldapjs/node-ldapjs/releases/tag/v3.0.4

Sorry I forgot to mention. I am on 3.0.4

The only way I've been able to fix this is by returning input instead of DN.fromString(input).
The DN.isDn() function seems to return false, even for the example DN used in the docs: cn=foo,dc=example,dc=com

I have created an integration test based upon this issue https://github.com/ldapjs/node-ldapjs/pull/926
I am not seeing the issue described.

Closing as cannot reproduce. If you are able to provide a reproduction, or show how the integration test I added is insufficient, please reopen with that information.

https://github.com/audn/ldapjs-reproduction
Let me know if it works on your end @jsumners

Have you reviewed the integration test I added? Can you point out how it does not cover the issue?
Regarding your repo:

https://github.com/audn/ldapjs-reproduction/blob/06453eb1342cf8fd371c3a3a700e648fd4ae29b5/package.json#L6 is not v3.0.4. The v3.0.4 release directly addresses the code block you are asserting is the issue.
It is not a minimal reproduction. Please review https://stackoverflow.com/help/minimal-reproducible-example. Note: the integration test I provided is a good example of what a minimal reproduction looks like for this project.

I tried moving the user, and that fixed it. Do you have any limitations as of how deep we can drill?
Doesn't work: CN=user1,OU=Portal,OU=Users,OU=Tier,OU=Norge,DC=example,DC=com
Works: CN=user1,DC=example,DC=com

You have removed your code, so I cannot see what you are doing. I'm going to guess that you are searching for the entry to modify, setting a base DN at dc=example,dc=com, and not specifying scope=subtree.
This library does not impose any limits on DNs that are not present in the RFCs.

Can you add scope on modify?
https://github.com/audn/ldapjs-reproduction

It seems like it's returning "No Such Object" when using "ø" in the DN @jsumners

Please see https://github.com/ldapjs/node-ldapjs/issues/860.


Almost every stair, trapdoor and fence is waterlogged and faced randomly.

Timings link
https://timings.aikar.co/?id=09dc29b0282b4e3b9ec6add7698d1920
Expected behavior
Normally generated and placed Stairs, trapdoors and fences.
Observed/Actual behavior
Really wierd faced and waterlogged trapdoors, stairs, glow linchen, etc....
Steps/models to reproduce

Purpur version
This server is running Purpur version git-Purpur-1434 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT) (Git: 1fd37bd on HEAD)
You are running the latest version
Previous version: git-Purpur-1433 (MC: 1.18)
Agreements

[x] I am running the latest version of Purpur available from https://purpur.pl3x.net/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
I have generated a world in singleplayer with the same seed and It was NOT like on the server. It was fine as it normally has to work.

Resolved in Discord


Overlay behind DNN popups

Test page http://localhost/dnndevtools/Admin/User-Accounts and click on "add user".

By overlay you mean the tooltip? If yes, I moved it on z-index: 32-bit integer<PHONE_NUMBER>) :D

No, overlay :)

fixed


Insert autopadding

Automatically insert padding fields in a structure that is made up of fields that must be placed at specific locations.
Where those are used in RMM: mostly to communicate with the host hypervisor in normal world and the RMM in realm world.
for example,
    pub struct Params {
    0x0    pub features_0: u64,
    0x100  pub hash_algo: u8,
    0x400  pub rpv: [u8; 64],
    0x800  pub vmid: u16,
    0x808  pub rtt_base: u64,
    0x810  pub rtt_level_start: i64,
    0x818  pub rtt_num_start: u32,

Defined pad_struct macro.
Struct definition:
pad_struct!(
pub struct Params {
    0x0    pub features_0: u64,    // [offset]  [visibility] [identifier]: [type],
    0x100  pub hash_algo: u8,
    0x400  pub rpv: [u8; 64],
    0x800  pub vmid: u16,
    0x808  pub rtt_base: u64,
    0x810  pub rtt_level_start: i64,
    0x818  pub rtt_num_start: u32,
    0x1000 => @END,   // to sepecify the end of the struct
}
);

Drawback of Struct intialization:

we still need to know the size of the padding.
Unnecessary zero-sized paddings are inserted.

impl Default for Params {
    fn default() -> Self {
        Self {
            features_0: 0,
            _padfeatures_0: [0; 248],
            hash_algo: 0,
            _padhash_algo: [0; 767],
            rpv: [0; 64],
            _padrpv: [0; 960],
            vmid: 0,
            _padvmid: [0; 6],
            rtt_base: 0,
            _padrtt_base: [0; 0],
            rtt_level_start: 0,
            _padrtt_level_start: [0; 0],
            rtt_num_start: 0,
            _padrtt_num_start: [0; 2020],
        }
    }
}

Please feel free to directly modify the code in dev/autopadding.


Clarify that --vars-store is not-optional if you want interpolated variables to be generated

We have a BOSH manifest that takes advantage of the CLI generating certs and passwords when variables are declared.
We were doing bosh deploy and bosh int without a --vars-store flag and were expecting that it would still generate something. The error message was ok... it said invalid value for the fields into which we were expecting certs to have been generated.
It looks like the behavior of the CLI is that the variable-generating feature only is activated if there is a --vars-store specified.
To clarify this behavior, can the docs at https://bosh.io/docs/cli-int.html#explicit state that if you are using the variable generation feature, then --vars-store is a mandatory field?
No PR, just an issue, because we may not be understanding the full nuance of the situation

Ahh... I see the note about "once Director officially supports config server API", suggesting that --vars-store is kinda like a short-term fix until something like CredHub gets installed? Still not crystal clear, but we're on the right track.


[fixed] Keep highlighted item when pressing arrow left and right keys.

Refs #192

Hi! Thanks for putting this together. After looking over the issue I discovered that the problem isn't contained to only left/right arrow keys, but to any key press that doesn't modify input.value. I created a general fix in 5d61876fa5a96114d65dbfa3a0a85e3257a415ca which is a part of 1.4.4.


[iOS][Old Arch][Codegen] - Codegen breaks pod install

Description
Hi everyone! 👋
We are currently upgrading our application from version .73.8 to .75.4 and we've noticed something weird.
With the new version, if we run pod install, now Codegen gets executed differently than before.
This would be fine if we actually enabled the new architecture, but we didn't and it breaks the pods install phase because some libraries are compatible with the new architecture but present issues in the Spec file that Codegen refers to.

So we can't install pods using the old architecture with libraries that present issues on Spec files because Codegen can't properly parse them (I guess)

I took the time to look into the changes between version .73.x and .75.x and I've noticed that this commit was included: Defragment Codegen in OSS between Old and New Architecture and it changes the following file: codegen.rb by removing the new_arch_enabled check in the run_codegen function.

Doing so means that if we run the same project on version .73 it works fine, but if we run it from version .74 onward it breaks on the old architecture with any library that has a Spec file that is broken

I don't have a complete overview of how Codegen gets executed, by I think that we should revert this check for the sake of any project that can't migrate right away due to lock-ins: may them be by libraries or vendor code such as third party sdks.
Steps to reproduce

Init a new project with npx @react-native-community/cli@latest init RN75 --version 0.74 --pm npm;
Install any library such as npm install --save-dev react-native-webview;
Break the Spec file in any way, in our case we can break: react-native-webview's Spec file by adding a Tuple that isn't supported yet; (Example down below)
Run pod install;
See Codegen error;

Example:
// node_modules/react-native-webview/src/NativeRNCWebViewModule.ts

import type { TurboModule } from 'react-native';
import { TurboModuleRegistry } from 'react-native';
import { Double } from 'react-native/Libraries/Types/CodegenTypes';

export interface Spec extends TurboModule {
  isFileUploadSupported(): Promise<boolean>;
  shouldStartLoadWithLockIdentifier(
    shouldStart: boolean,
    lockIdentifier: [Double] // We change this type from Double to [Double]
  ): void;
}

export default TurboModuleRegistry.getEnforcing<Spec>('RNCWebViewModule');

React Native Version
0.74.0+
Affected Platforms
Build - MacOS
Output of npx react-native info
System:
  OS: macOS 14.6
  CPU: (8) arm64 Apple M3
  Memory: 108.92 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.8.0
    path: ~/.nvm/versions/node/v22.8.0/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v22.8.0/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v22.8.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/user/.gem/ruby/3.3.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2412.12266719
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 3.3.5
    path: /Users/user/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.5
    wanted: 0.74.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

info React Native v0.75.4 is now available (your project is running on v0.74.5).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.75.4
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.74.5
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".

Stacktrace or Logs
/Users/user/Documents/Projects/ReactNative/RN74/vendor/bundle/ruby/3.3.0/gems/concurrent-ruby-1.3.4/lib/concurrent-ruby/concurrent/concern/deprecation.rb:1: warning: logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add logger to your Gemfile or gemspec to silence this warning.
/Users/user/Documents/Projects/ReactNative/RN74/vendor/bundle/ruby/3.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/big_decimal.rb:3: warning: bigdecimal was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add bigdecimal to your Gemfile or gemspec to silence this warning.
/Users/user/Documents/Projects/ReactNative/RN74/vendor/bundle/ruby/3.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:4: warning: mutex_m was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add mutex_m to your Gemfile or gemspec to silence this warning.
(node:64099) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Auto-linking React Native module for target `RN74`: react-native-webview
Framework build type is static library
[Codegen] Adding script_phases to React-Codegen.
[Codegen] Generating ./build/generated/ios/React-Codegen.podspec.json

[!] Invalid `Podfile` file: [!] /Users/user/.nvm/versions/node/v22.8.0/bin/node ./../node_modules/react-native/scripts/generate-codegen-artifacts.js -p /Users/user/Documents/Projects/ReactNative/RN74/ios/.. -o /Users/user/Documents/Projects/ReactNative/RN74/ios -t ios

[Codegen] Analyzing /Users/user/Documents/Projects/ReactNative/RN74/package.json
[Codegen] Searching for codegen-enabled libraries in the app.
[Codegen] The "codegenConfig" field is not defined in package.json. Assuming there is nothing to generate at the app level.
[Codegen] Searching for codegen-enabled libraries in the project dependencies.
[Codegen] Found react-native
[Codegen] Found react-native-webview

[Codegen] >>>>> Searching for codegen-enabled libraries in react-native.config.js
[Codegen] Processing FBReactNativeSpec
[Codegen] Searching for podspec in the project dependencies.
[Codegen] Processing rncore
[Codegen] Searching for podspec in the project dependencies.
[Codegen] Processing RNCWebViewSpec
[Codegen] Searching for podspec in the project dependencies.
[Codegen] Supported Apple platforms: ios, macos, visionos for RNCWebViewSpec
[Codegen] Done.
UnsupportedTypeAnnotationParserError: Module NativeRNCWebViewModule: TypeScript type annotation 'TSTupleType' is unsupported in NativeModule specs.
    at translateTypeAnnotation (/Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/typescript/modules/index.js:376:15)
    at /Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/parsers-commons.js:373:11
    at guard (/Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/utils.js:26:14)
    at translateFunctionTypeAnnotation (/Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/parsers-commons.js:367:25)
    at buildPropertySchema (/Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/parsers-commons.js:484:7)
    at /Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/parsers-commons.js:705:24
    at guard (/Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/utils.js:26:14)
    at /Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/parsers-commons.js:702:14
    at Array.map (<anonymous>)
    at buildModuleSchema (/Users/user/Documents/Projects/ReactNative/RN74/node_modules/@react-native/codegen/lib/parsers/parsers-commons.js:699:6) {
  nodes: [
    Node {
      type: 'TSTupleType',
      start: 342,
      end: 350,
      loc: [SourceLocation],
      elementTypes: [Array]
    }
  ],
  typeAnnotationType: 'TSTupleType'
}
.

 #  from /Users/user/Documents/Projects/ReactNative/RN74/ios/Podfile:20
 #  -------------------------------------------
 #
 >    use_react_native!(
 #      :path => config[:reactNativePath],
 #  -------------------------------------------

[!] [Codegen] warn: using experimental new codegen integration

Reproducer
https://github.com/gladiuscode/codegen-breaks-pod-install-on-old-arch
Screenshots and Videos
No response

@gladiuscode Thanks for the issue but why should you

Break the Spec file in any way, in our case we can break: react-native-webview's Spec file by adding a Tuple that isn't supported yet; (Example down below)
??

Even if Codegen gets executed, it is executed by your version of react-native and it is ensured to build properly. There are many people using react-native-webview in 0.75 on the Old Architecture and they don't have issues with that.
In order to make sure that everything work, please try to clean your project:

run bundle exec pod deintegrate
remove the iod/build folder
reintall yarn
reinstall pods with bundle exec pod install.

Everything should work just fine.

w version, if we run pod install, now Codegen gets executed differently than before.
This would be fine if we actually enabled the new architecture, but we didn't and it breaks the pods install phase because some libraries are compatible with the new architecture but present issues in the Spec file that Codegen refers to.

Hi @cipolleschi, thanks for your reply.
I did break react-native-webview just to showcase that currently, running the old architecture, codegen breaks pods install anytime there is a library that has issues in the Spec file and that's our case.
We've got a library that we can't patch ourself, it is compatibile with the new architecture, but has issues in the Spec file itself: so when we migrate from .73.x to .75.x it breaks the pods installation phase for the old architecture as well.
This shouldn't happen because if we stay in the old architecture it shouldn't even check out the Spec file itself for reference since we are not using TurboModules or the new architecture setup.

Even in the old architecture, we generate Codegen. The reason is to minimize the differences between the two architectures to simplify the migration.
The version of codegen that is generated is linked to the version of React Native. If you updated React Native the code generated should work in boht architecture.
Notice that there are libraries that, starting from 0.74, are shipping the generated code in the npm package. In that case, breaking changes in the Codegen will break the those libraries.
What's the library that is breaking in your case?

This error points to a misaligned version of Codegen for RNLocalizationSettingsSpec.
Is this coming from a library? Can you point out which one?
I suggest to run pod deintegrate, to delete node_modules and rerun yarn install and bundle exec pod install.


[TASK] Synchronize Transactions and Notes Display with Hubble Bridge

Description
The goal of this task is to ensure that the account dashboard accurately reflects the user's successful transactions, total shielded balance, available spend notes, and transaction history table, by synchronizing this data with the Hubble Bridge. This will provide users with a consistent and up-to-date view of their account status.
Requirements:

Data Integration: Establish connection between the account dashboard and Hubble Bridge to fetch and display the user's successful transactions, including deposits, transfers, withdrawals, and received transfers.
Total Shielded Balance: Accurately calculate and display the user's total shielded balance, reflecting all successful transactions.
Notes Table: Populate the notes table with detailed information about each note.
Transaction History Table: Display a comprehensive history of the user's successful transactions, including transaction type, amount, date, and links to relevant block explorers etc.

Screenshot

Closed in this PR


Ota improvements

The goal here is to minimize the code space requirements and improve the reliability.
In a different branch I've merged BLE_otas with BLE_FreeRTOS.

/clang-format-run

Did you set it back to 50 ms?

Did you set it back to 50 ms?

yes and erase works fine there, which is where the ci test got hung up. but im getting stuck at the 13th write request.

I think we need to delay the  write response to the client so it doesn't send packet after packet and were just queuing  up writes. Unfortunately the writes are initiated here:
https://github.com/Analog-Devices-MSDK/msdk/blob/e96ec8f61b47334d01ded783e5224e14f0cd66bc/Libraries/Cordio/ble-host/sources/stack/att/atts_write.c#L162-L168
which is calling this in wdxs_main.c  :
https://github.com/Analog-Devices-MSDK/msdk/blob/e96ec8f61b47334d01ded783e5224e14f0cd66bc/Libraries/Cordio/ble-profiles/sources/profiles/wdxs/wdxs_main.c#L249-L251
The result of that is success and returns to the atts_write.c and sends a write response to the client which  then sends the next packet. We could make the response not be success and use ATT_RSP_PENDING, then we send the response after the queue is serviced, but then we are modifying wdxs_main and such..which wont play well with ext flash examples.

/clang-format-run

/clang-format-run


[table] Add support for multiple tbody elements in a table

[ ] PR has tests / docs demo, and is linted.
[ ] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

I finished up the work already done here: https://github.com/callemall/material-ui/pull/3663.
I don't really like how the styling is done on the table borders, but couldn't think of a better way. So let me know if you have suggestions.
Also multi-selection is a bit weird right now. If you select in one tbody then select an element in a different tbody it will deselect the original one.  I didn't have time to dive into that yet and it might even be the desired behavior. It wouldn't be a breaking change since no one should have multiple tbody elements right now.

@dustinsmith1024 Thanks for the PR. A couple of minor comments from me.

The Table component was partially / fully migrated on the next branch.
We are now focusing on releasing out the next branch.
We plan to stop the support of the migrated components.
I'm gonna close this PR. Thanks for your time.
Would be great if you check out the new component. Any PR is welcomed.


Code stays in infinite loop

the below code in the file constellation-start.sh never exits as all the 7 conditions are never true.
while $DOWN; do
    sleep 0.1
    DOWN=false
    for i in {1..7}
    do
	if [ ! -S "qdata/c$i/tm.ipc" ]; then
            DOWN=true
	fi
    done
done

Did you us vagrant to set up the examples or did you do it yourself? Check the logs for a constellation node to see what is wrong (examples/7nodes/qdata/logs). My problem was that my constellation was not up to date.

Well i am using the example on Ubuntu server, as quorum 2.0 does not support quorumchain and start.sh is actually a quorumchain example, so that could be a reason it got struck.

You should try using raft-start.sh and see what happens

Done that also and it has another set of issues. I have quorum 7 nodes example running on a ubuntu system, with RAFT consensus, it works all good till it reaches block number 2656 and after that it just stops mining or doing any contract updates. I am also facing the same issue on a second ubuntu server. Is there a bug in the latest code ?

@HimanshuK18 Please update to the most recent version of Quorum master, we did a fix for the block number limit.


small issue with "transcript maps"

If the feature is a ncRNA the exon is still labelled as a CDS exon bottom left

Good point.  :-)
I've fixed that.  It now says
exon 1   4651792-4651351

Does that make sense for pseudogenes too?

Does that make sense for pseudogenes too?

yes I think so

OK, thanks.


Fix: Fixed network locations not appearing on the sidebar

Resolved / Related Issues

[ ] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #issue...

Since becoming a view model, UpdateDrivesAsync() of NetworkDrivesViewModel was not being called anymore.
Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[x] Are there any other steps that were used to validate these changes?

Connect a network resource (e.g ftp server)
Verify that it appears in the sidebar

Screenshots (optional)
Add screenshots here.

Shouldn't Network folder be the first entry?

It should but since #10258 drives get re-ordered in SidebarViewModel. Don't think it was intentional for network drives, I'll add a fix here.


TODO: CH32L103 support

I think this is implemented in #28.
I haven't got a chip or EVT board to verify this.

I think we can close this issue

Confirm works with:
WCH Official ch32vl103c8t6 evt board.
WCH-LinkE r0 1v3 and r0 1v2 with latest firmware.

@cjacker Thanks for your confirmation.

@andelf  Thanks for your great work.
And the major feature missing is #42 "Upgrade WCH-Link/E firmware online", hope it comes soon :-).
Now I have to use another WCH-Link/E to upgrade firmware under linux.
Ghidra may help to analyze the protocol. Recently I use Ghidra to analyze 'clearcodeflash' related functions of WCH-LinkUtility/McuCompilerDll.dl and try to implement 'erase by NRST/by PowerOff' to rescue a bricked board, After done, I found wlink already done:-D


fix(fluffy button): fix types

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Screenshots/Demo

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

closing in favor of #576


Fix/hub redirect plugins

Summary
Redirect old plugin pages to new pages within the Kong Hub.
Full changelog

Lots of redirects
Renamed folder to precisely match plugin name as it appears in Kong Admin API

Checklist:

[x] Commit message & atomicity checked
[ ] Documentation N/A
[ ] Spellchecked my updates N/A
[x] Ready to be merged

Can we update the links in the sidebar as well so they don't see the "redirect" or will that be once it officially "launches"?

Good idea @leevye - I've got a bunch of sidebar nav work to do, capturing your request in https://github.com/Kong/docs.konghq.com/issues/865


VersionStringParseException for Vlc ver. 2.2.1

Hi,
I think there's a bug in when I am trying to create an instance of the player dynamically/code-behind (not in xaml). Looks like it's trying to look for 2.2.0. I have Vlc ver. 2.2.1.
Thanks.

Ummm, I think the version string is <ver>-<devString> <codeName> before.
Now I add more parser for new version string format.

Have you try the new version?
I think it work fine now.


Adding HomeAssistant config options to work homie mqtt standards

Here is a first take at getting Home Assistant Auto Discovery MQTT on load of devices in this homie4 module. I wanted to get this in front of you to see if there was a better location or method before finishing all some of the items below. I have this running and seems to be working and devices are added to homeassistant.
Thoughts for some updates I could add

The Split could also be fixed with child objects passing in their types instead of pulling this from the device_id.
add switch to disable this function
Adding removal or updates for configs. I'm sure updates would be needed since the topics in the config shouldn't change as their created with their device_id for insteon.
better error handling over data conditions
Add parameter for topic path in case users don't use "homeassistant" for their prefix

I merged the code. I think we should look at moving the HA device specific code into each device and not in device base


Allow exemptions to coordinate axis guessing on save

Within the iris NetCDF saver there is a call to guess_coord_axis. This simple utility relies on coordinate names, units, or other attributes to ascribe an axis identifier to each dimension coordinate where possible. One of these guesses checks whether the units of the coordinate are convertible to hectopascals, and if so presumes the dimension is a pressure coordinate corresponding to vertical levels; an axis identifier of Z is added.
Working with probabilistic data in which a dimension coordinate may describe different pressure thresholds, i.e. probability of pressure at mean sea level exceeding 1000hPa, 1010hPa, 1020hPa etc. this results in the threshold coordinate being identified as a vertical spatial dimension with an axis identifier of Z. This is undesirable and causes issues downstream of where the data is created (e.g. in Visual Weather). As this is added on save it is not possible to remove the attribute without using an alternative tool to Iris.
This issue requests that there be a means within Iris of preventing the axis identifiers being added to specific named (or var named) coordinates on save.
Example cube
Below is shown a simple print out of a probabilistic PMSL forecast with a threshold coordinate named air_pressure_at_sea_level that has units of Pa, which is not a height coordinate, but which is assigned a Z axis identifier.
probability_of_air_pressure_at_sea_level_above_threshold / (1) (air_pressure_at_sea_level: 85; projection_y_coordinate: 970; projection_x_coordinate: 1042)
     Dimension coordinates:
          air_pressure_at_sea_level                                                      x                            -                             -
          projection_y_coordinate                                                        -                            x                             -
          projection_x_coordinate                                                        -                            -                             x
     Scalar coordinates:
          ...

ncdump header information corresponding to this coordinate:
float threshold(threshold) ;
	threshold:axis = "Z" ;
	threshold:units = "Pa" ;
	threshold:standard_name = "air_pressure_at_sea_level" ;

@bayliffe Thanks for raising this issue, much appreciated. We think this is an issue that needs addressed :+1:
Are you happy to take this issue on yourself with some hand holding?
If you don't have time just let us know and we can move this issue forwards for you.

After a wee bit of developer discussion your issues raises questions how the best mechanism to best control the behaviour that you want... so this may require more thought on our behalf.

Hmmm there seems to be a few ways to approach this problem in a generic useful way, and TBH this is going to need some considered thought (sorry, no avoiding that).
At this point, I suggest that you up-vote your own issue (and get other like minded users/devs to do so too :wink:) to make sure that the priority of this issue bubbles to the top of tasks that require to be addressed :+1:
Hope that's okay for now?

I've upvoted as requested - this issue affects our usage of Iris-produced NetCDF with downstream systems (including Visual Weather) at BOM.
I'd argue that this issue should be labelled as a bug rather than an enhancement.
Metadata for probabilistic pressures will always be marked (incorrectly) as a vertical/Z axis. I'm also not aware of any way to work around this issue on the user side, besides editing the saved NetCDF file with a non-Iris tool like netcdf4-python or NCO.

That’s good insight @tjtg.  I added the “feature” label, as any mechanism to opt out of current behaviour would be a new feature.  However, it never makes sense to think that “air_pressure_at_sea_level” could describe height.  If we could change guess_coord_axis to produce a sensible return value for this coordinate, then we would not need an opt-out mechanism.

Discussed in Peloton, added to 3.5 for time being.

Coming into this discussion from the side, and totally by chance, I had a quick look at the code referred to in the OP. To me the big difference between the cases for X and Y, vs. Z, is that for the former two the code lists specific standard names. And these can be concluded from CF Chapters 4.1 and 4.2, and Appendix F. For the vertical coordinate no similar list can be extracted from the CF text. However, the standard name table might perhaps provide a solution:  I did a quick search using keyword "coordinate" that resulted in a reasonable list of standard names mostly representing vertical coordinates, and a few more that were easy to identify as representing something else. Would it be possible to explore the standard name list a bit more carefully to come up with a list of standard names that allows guess_coord_axis to what @rcomer suggests ?

Had a design discussion with @HGWright recently.
None of the below options are without compromise. The current preferred option is a new DimCoord member: space_time.
Tagging all voters: @rcomer @bjlittle @pp-mo @bayliffe @neilCrosswaite @bjwheltor @s-boardman @BelligerG @MoseleyS @PaulAbernethy @simonjackson900 @tjtg @anja-bom @nivnac @thbom001 @btrotta-bom @dmentipl @ivorblockley @benowen-bom @cpelley @gavinevans
Adjust guess_coord_axis()
Don't use HPa for z-guessing

➕: avoids all mistakes like this
➖: makes Iris less active in adding CF-compliant information
➖: likely break existing workflows that are currently fine

Exclude particular names from z-guessing
Suggestion is to exclude anything that includes *pressure_at*.

➕: keeps utility of current z-guessing, but with fewer mistakes
➖: more difficult to understand/predict
➖: hard to be exhaustive with the exclusion list
Even likely to change over time
➖: very reliant on outside expertise for this, and each user has different cases that they need to work

Adjust saving
Don't alter an existing axis attribute
Intention is that the user will set an appropriate attribute before saving e.g. "NA".

➕: a simple addition with few breakages likely
➖: requires manual user intervention
➖: don't know how downstream readers might interpret this (only T, Z, Y, X are covered in CF)
➖: difficult to inform users that they should do this - no obvious place in the docs

A new kwarg in the NetCDF saver

➕: a visible feature, easy to spot in the documentation
➕: non-breaking addition
➖: requires manual user intervention
➖: the saving API is already too busy
➖: this is pretty specific for the top-level saver, and sets a precedent for adding lots of other 'modes'

A new DimCoord member: space_time
Boolean, default None. Set to True when coord has an axis attribute of T/Z/Y/X. Set to False if a different axis attribute value is present.
Axis guessing during save is not performed if my_coord.space_time is False (since the guessing was only ever intended to add the spatiotemporal axis labels).
Intention is that the user will set my_coord.space_time=False before saving.

➕: a visible feature, easy to spot in the documentation
➕: precedent in the circular and climatological flags - information to determine Iris behaviour
➕: potential opportunities for future use in distinguishing experimental repeats, pertubations etc.
➕: non-breaking addition
➖: requires manual user intervention
➖: fairly significant API addition

Not currently planning a context manager, but can be persuaded 😉🎂

@HGWright @trexfeathers @bjlittle  thank you for your work on this. I'm afraid in the turmoil of operational releases, the progress made on this issue completely passed me by at the end of last year. Your efforts are much appreciated and will help us to avoid spurious behaviour in downstream systems ingesting probabilistic pressure data. ❤


How does Leaflet work in production SPA mode (Nuxt)?

I've been struggling to get Leaflet to work in production mode, specifically in my Nuxt app where mode is spa. I'm essentially using geolocation to plot markers on a map that represent businesses.
I've tried two different solutions (nuxt-leaflet module as well as the manual plugin method) and in both cases my map works perfectly in dev mode but after npm run build && npm start, it fails in the exact same way: tiles are scattered all over the screen, I can't see the map markers, and I get no console errors.
I'm new to Vue/Nuxt so I feel like this is something fundamental that I'm missing. What could it be? Thanks so much for any help!
Here's what I'm working with:
// in nuxt.config.js
plugins: [
  { src: '~/plugins/leaflet-map', ssr: false }
],

// ~/plugins/leaflet-map.js
import Vue from 'vue'
import { LMap, LTileLayer, LMarker } from 'vue2-leaflet';
import 'leaflet/dist/leaflet.css'

const LeafletMap = {
  install(Vue, options) {
    Vue.component('l-map', LMap);
    Vue.component('l-tilelayer', LTileLayer);
    Vue.component('l-marker', LMarker);
  }
};

Vue.use(LeafletMap);
export default LeafletMap;

<template>

      <l-map ref="myMap" :zoom=18 :center="[33.500598, -86.796270]"></l-map>

</template>

Never mind. PurgeCSS was killing my leaflet classes...doh! Sorry.


Logging improvements

Highlights from CHANGELOG.md

Using new logging class to remove arbitrary whitespace placement in favor of explicit functionality for adjusting indentation levels.
See CHANGELOG.md for more

TODO:

#321

Issues Fixed

Fixes #14

The failing builds are due to stale old references to plain inform_multiline as opposed to new @log.inform_multiline.
exe/arduino_ci.rb
362:    return inform_multiline("Wildcard architecture in library.properties, using configured platforms") do
373:    return inform_multiline("Default config, platforms matching architectures in library.properties") do
382:  inform_multiline("Configured platforms that match architectures in library.properties") do

Yup, I'm just making a lot of local edits and pushing up stuff to my branch that (for now) I expect to have failures.  Lots of areas being cleaned up!


Bulk operations with shadow property on postgresql does not work

Hi,
I have come across the issue where the shadow property is not saved with the BulkInsertOrUpdate api.
This is how I set the value of the shadow property :
dbContext.Entry(entity).Property("Data").CurrentValue = json;
This works with native efcore apis(DbSet.Add and SaveChanges operations) but not with BulkInsertOrUpdate.

Hello
I also noticed this issue working with the library.
Is it possible to handle shadow properties somehow?
Kind regards
Dan

Hello
I also noticed this issue working with the library.
Is it possible to handle shadow properties somehow?
Kind regards
Dan

Shadow Properties for now should be explicitly defined in entity, add it like:
public SomeType Data { get; set; }

Hello,
Unfortunately this is not possible for me, as I am using entities which are defined in another nuget package I use.
I add the shadow properties on top of them since I can't edit them myself.
I would really appreciate your help with fixing this issue.
Kind regards
Dan

@danflomin fixed with latest v.

Hello
Thank you very much!
I tried to use the latest version and I had an issue working with it.
I'll appreciate your help with it.
I suspect that the fact my DB works with snake case column names, the new code does not set the shadow property value to the column.
For example, the shadow property is named DanFlomin, but is being refernced as dan_flomin in the DB table.
In the OnConfiguring method I use .UseSnakeCaseNamingConvention().
Thanks you very much for your assistance.
Kind regards
Dan

Fix commited, but new nuget will be published with some other change, in 7 10 10 days.

You could load the source instead of nuget and test it.

Hello
I used the main branch and it looks like it is working fine.
Thank you
I'll appreciate if it will be possible to release the nuget 🙏  It will help me a lot.
Kind regards
Dan

v7.1.4

@danflomin v7.1.4

Thank you very much!!
On Mon, Jul 10, 2023, 19:40 Boris Djurdjevic @.***>
wrote:

@danflomin https://github.com/danflomin v7.1.4
—
Reply to this email directly, view it on GitHub
https://github.com/borisdj/EFCore.BulkExtensions/issues/1065#issuecomment-1629331831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIB5S7MQ7CWJXAZGJOU7FO3XPQV7HANCNFSM6AAAAAAT2KFVUA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Rewrite WPF // MVVM Question

I'm currently developing the Remote Desktop Stream Feature. The Question is should we start a Rewrite of Quasar before we continue to develop Features? Because we want a rewrite at some point.
So why not wait with the features till the WPF rewrite is done.
I could start a Rewrite of Quasar using WPF and the MVVM Architecture.
I would start a new Repo and Maxxor could take it when he is back.
Would love some input or questions on this.

I like the idea of a rewrite. I would rather wait for the features.
Otherwise it will be more work for you and Maxxor and other contributors to first develop the features and then having to rewrite everything.


New param class with major updates

A new ParamDict class was added for parameters. This stremlines several interfaces with other classes. Many updates were made to all classes, as well as unit tests. This is intended to be a major update.

I'll allow you to do the actual merging, @ankushaggarwal.


Make heatmaps more user friendly by supporting config params in heatmap.plot()

Currently, the heatmaps config parameters need to be passed during construction and can be updated by calling heatmap.update_config. This should be changed s.t. users can directly pass the parameters to heatmap.plot() function. Eg:

Current workflow

heatmap = calibration.heatmap("parallel_p11_error")
heatmap.update_config(vmin=0, vmax=0.1)
heatmap.plot()

Expected Workflow

heatmap = calibration.heatmap("parallel_p11_error")
heatmap.plot(vmin=0, vmax=0.1)

Acceptance criteria - when is the task considered done?

Modify the heatmap code to support the updated workflow.
Update visualization -> heatmap tutorial and add sections on how to use various config parameters.

Part of the larger roadmap item: #3642

@tanujkhattar I think this should be closed now?

That's right, this should have been closed by #4026


CI: Conformance EKS - client-egress-l7-named-port

CI failure
Tue, 04 Jul 2023 17:11:52 GMT [=] Test [client-egress-l7-named-port]
Tue, 04 Jul 2023 17:12:07 GMT ...
Tue, 04 Jul 2023 17:12:07 GMT   ℹ  📜 Applying CiliumNetworkPolicy 'client-egress-only-dns' to namespace 'cilium-test'..
Tue, 04 Jul 2023 17:12:07 GMT   ℹ  📜 Applying CiliumNetworkPolicy 'client-egress-l7-http-named-port' to namespace 'cilium-test'..
Tue, 04 Jul 2023 17:12:07 GMT   [-] Scenario [client-egress-l7-named-port/pod-to-pod]
Tue, 04 Jul 2023 17:12:07 GMT   [.] Action [client-egress-l7-named-port/pod-to-pod/curl-ipv4-0: cilium-test/client-7b78db77d5-hrzp8 (<IP_ADDRESS>) -> cilium-test/echo-other-node-56ddbd8694-qvdnd (<IP_ADDRESS>:8080)]
Tue, 04 Jul 2023 17:12:07 GMT   [.] Action [client-egress-l7-named-port/pod-to-pod/curl-ipv4-1: cilium-test/client-7b78db77d5-hrzp8 (<IP_ADDRESS>) -> cilium-test/echo-same-node-5cf949b488-4jfx2 (<IP_ADDRESS>:8080)]
Tue, 04 Jul 2023 17:12:07 GMT   [.] Action [client-egress-l7-named-port/pod-to-pod/curl-ipv4-2: cilium-test/client2-78f748dd67-df769 (<IP_ADDRESS>) -> cilium-test/echo-other-node-56ddbd8694-qvdnd (<IP_ADDRESS>:8080)]
Tue, 04 Jul 2023 17:12:07 GMT   ❌ command "curl -w %{local_ip}:%{local_port} -> %{remote_ip}:%{remote_port} = %{response_code} --silent --fail --show-error --output /dev/null --connect-timeout 2 --max-time 10 http://<IP_ADDRESS>:8080/" failed: command terminated with exit code 22

Tue, 04 Jul 2023 17:13:51 GMT 📋 Test Report
Tue, 04 Jul 2023 17:13:51 GMT ❌ 1/45 tests failed (1/288 actions), 10 tests skipped, 1 scenarios skipped:
Tue, 04 Jul 2023 17:13:51 GMT Test [client-egress-l7-named-port]:
Tue, 04 Jul 2023 17:13:51 GMT   ❌ client-egress-l7-named-port/pod-to-pod/curl-ipv4-2: cilium-test/client2-78f748dd67-df769 (<IP_ADDRESS>) -> cilium-test/echo-other-node-56ddbd8694-qvdnd (<IP_ADDRESS>:8080)

Looking at the sysdump, the following hubble flows are relevant:
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) from-endpoint FORWARDED (TCP Flags: SYN)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) policy-verdict:L3-L4 EGRESS ALLOWED (TCP Flags: SYN)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-proxy FORWARDED (TCP Flags: SYN)
Jul  4 17:11:59.074: cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) <> cilium-test/client2-78f748dd67-df769:44512 (ID:15250) from-proxy FORWARDED (TCP Flags: SYN, ACK)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <- cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-endpoint FORWARDED (TCP Flags: SYN, ACK)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) from-endpoint FORWARDED (TCP Flags: ACK)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-proxy FORWARDED (TCP Flags: ACK)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) from-endpoint FORWARDED (TCP Flags: ACK, PSH)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-proxy FORWARDED (TCP Flags: ACK, PSH)
Jul  4 17:11:59.074: cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) <> cilium-test/client2-78f748dd67-df769:44512 (ID:15250) from-proxy FORWARDED (TCP Flags: ACK)
Jul  4 17:11:59.074: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <- cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-endpoint FORWARDED (TCP Flags: ACK)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) http-request FORWARDED (HTTP/1.1 GET http://<IP_ADDRESS>:8080/)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <- cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) http-response FORWARDED (HTTP/1.1 503 8089ms (GET http://<IP_ADDRESS>:8080/))
Jul  4 17:12:07.164: cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) <> cilium-test/client2-78f748dd67-df769:44512 (ID:15250) from-proxy FORWARDED (TCP Flags: ACK, PSH)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <- cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-endpoint FORWARDED (TCP Flags: ACK, PSH)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) from-endpoint FORWARDED (TCP Flags: ACK)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-proxy FORWARDED (TCP Flags: ACK)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) from-endpoint FORWARDED (TCP Flags: ACK, FIN)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) -> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-proxy FORWARDED (TCP Flags: ACK, FIN)
Jul  4 17:12:07.164: cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) <> cilium-test/client2-78f748dd67-df769:44512 (ID:15250) from-proxy FORWARDED (TCP Flags: ACK, FIN)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <- cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) to-endpoint FORWARDED (TCP Flags: ACK, FIN)
Jul  4 17:12:07.164: cilium-test/client2-78f748dd67-df769:44512 (ID:15250) <> cilium-test/echo-other-node-56ddbd8694-qvdnd:8080 (ID:25486) from-endpoint FORWARDED (TCP Flags: ACK)

Link: https://github.com/cilium/cilium/actions/runs/5456932775/jobs/9930411799
Sysdump: cilium-sysdumps.zip

One more https://github.com/cilium/cilium/actions/runs/5482941194/jobs/9988780650.

I have enabled the envoy debug logs to capture more info for this issue, waiting for the next flake occurrence :waiting:

There is only 1 failure for the past 14 days, but the failure is related to external target (e.g. pod to world google.com), which is tracked as part of https://github.com/cilium/cilium-cli/issues/1720. Hence, I am closing this issue, we can re-open later if it's happening again.
Last 14 days
https://github.com/cilium/cilium/actions/runs/5659113659/job/15331963662
  [-] Scenario [client-egress-l7-named-port/pod-to-world]
  [.] Action [client-egress-l7-named-port/pod-to-world/http-to-google.com-0: cilium-test/client2-6cd4885dbf-clqhb (<IP_ADDRESS>) -> google.com-http (google.com:80)]


:memo: Make TextEditor::getBuffer public

Fixes #6224

This makes sense to meet since you can {TextBuffer} = require 'atom'.
Any objections @atom/core?

:+1:

:ship: Thanks @lee-dohm for this

You're welcome :grinning:


Some Questions

I just had a couple of questions regarding neuralcoref: Do you expect to update neuralcoref in the near future, and is there a formal API available for it?

Yes, I expect to have some times to work on it again within 2 weeks. I will see how much I can do. Is there some particular features/doc you would be interested in?


Correction for raw affiliation CIRAD, UMR PHIM, 34090 Montpellier, France; PHIM Plant Health Institute, Univ Montpellier, CIRAD, INRAE, Institut Agro, IRD, Montpellier, France

Correction needed for raw affiliation CIRAD, UMR PHIM, 34090 Montpellier, France; PHIM Plant Health Institute, Univ Montpellier, CIRAD, INRAE, Institut Agro, IRD, Montpellier, France
raw_affiliation_name: CIRAD, UMR PHIM, 34090 Montpellier, France; PHIM Plant Health Institute, Univ Montpellier, CIRAD, INRAE, Institut Agro, IRD, Montpellier, France
new_rors: 051escj72;05kpkpg04;03fkrcm40;05q3vnk25;03rnk6m14;003vg9w96;05y5s3h28
previous_rors: 051escj72;05kpkpg04;03fkrcm40;05q3vnk25;03rnk6m14;003vg9w96
works_examples: W4311312989
contact: 1b650d3f9a00b82945aebf5d25129476:4c7ea2c7c9c7c3815dd44972be150589dd25 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


T0 related bug in alcaSkim process

Impact of the bug
T0 can't produce alcaSkim process due to a bug in the cmssw-wm-tools script used to create the process
Describe the bug
When invoking cmssw_create_process, the script fails with alcaSkim processes
How to reproduce it
Steps to reproduce the behavior:
$ cmssw_wm_create_process.py --output PSet_output.pkl --funcname
alcaSkim --funcargs process_funcArgs.json
Failed to load process from Scenario cosmicsEra_Run3
(<Configuration.DataProcessing.Impl.cosmicsEra_Run3.cosmicsEra_Run3
object at 0x7f32fa2811d0>).
Traceback (most recent call last):
  File "/cvmfs/cms.cern.ch/share/overrides/bin/cmssw_wm_create_process.py",
line 129, in <module>
    main()
  File "/cvmfs/cms.cern.ch/share/overrides/bin/cmssw_wm_create_process.py",
line 120, in main
    process=create_process(args, func_args)
  File "/cvmfs/cms.cern.ch/share/overrides/bin/cmssw_wm_create_process.py",
line 82, in create_process
    raise ex
TypeError: alcaSkim() got multiple values for keyword argument 'skims'

Where:
$ cat process_funcArgs.json
{"scenario": "cosmicsEra_Run3", "globalTagConnect":
"frontier://PromptProd/CMS_CONDITIONS", "skims": ["SiStripPCLHistos",
"SiStripCalZeroBias", "TkAlCosmics0T", "SiPixelCalZeroBias",
"PromptCalibProdSiStrip", "PromptCalibProdSiPixel",
"SiStripCalCosmics"], "globalTagTransaction": "Express_341607",
"globalTag": "112X_dataRun3_Express_v5"}

Expected behavior
Script should produce the process
Additional context and error message
This has been reported and fixed in this commit:
https://github.com/cms-sw/cmssw-wm-tools/commit/30b626d030b7b11f83fe4e0385ce303e83d3fcdf

This has been fixed by David Lange, so nothing else to do here. WMCore related work was to reproduce the issue and pass the JSON input file


generate pdf on a single page

i work generating very large documents and i would like to be able to generate all the content on a single page. how can i do this, generate all the content on a single page without breaking pages?

I resolved this by setting document height dynamically based on the content for instance: const options = {         html: '
content
', height: (calculate the height based on the content you add)}


Trailing comma for last argument missing in some standard library macros

write!(
    time,
    " / {}",
    PossibleTimeSave::with_accuracy(self.settings.accuracy).format(previous_possible)
).unwrap();

write! is one of them, others are probably missing the trailing comma too.

We don't add or remove trailing commas in macros since that can affect semantics. I do not think we should try and add that knowledge to Rustfmt, so I think this is intentional behaviour. If you manually add a trailing comma here, it should be preserved.

Why is it done in vec! though?

Ohhh, that's actually very broken. I'll reopen a new issue, as I've found an actual bug.


Lower Performance with Yolov7-Tiny Quantization

Hi,
After doing quantization on the yolov7-tiny model with the recommended settings, I am getting a lower throughput with the result (qat-tiny.pt) on the benchmark when compared to doing the same benchmark on the model before quantization (yolov7-tiny.pt). I double checked that there were no tasks running in the background so I am pretty sure it is caused by the weights. I was wondering what went wrong during the quantization.
Thanks!

It seems like I was comparing against default txtexec INT8 mode. After comparing with the fp16, it made much more sense.


Fix decoding ReadPropertyMultipleAck + add more ReadRangeValueTypes

~ReadPropertyMultipleAck::new_from_buf doesn't take a reader, so it
will attempt to decode from the beginning of the slice. This fixes it to
only pass the remaining buf.~ (you beat me too it)
Add more support for decoding ReadRangeValueType (bool, unsigned,
signed and NULL).

I don't think it's a good time to add anything right now or you're going to have some painful merge conflicts to resolve.

Ok the major refactor is done for now. I'm not 100% happy with it (ideally I would like to get rid of all the lifetimes if the alloc feature is enabled but that would involve writing another macro and I need to think about weather or not it makes things better or worse (more obscure).

Thanks for your changes, they look good! My apologies for taking my time in getting back to this.


BCash Issue : Address is to Valid . Invalid Base58 String .

We don't support Base58 strings for BCash and will never support it. You need to use their cashaddr: instead.


PR: Some improvements to Changelog and Announcements for 6.0.1

Description of Changes

Improve order of fixes from most critical/important to least.
Add some missing fixes.
Improve wording a bit here and there.

Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @ccordoba12

@meeseeksdev please backport to 6.x


Tools -> Address Explorer -> Scan wallet descriptor: "Not Yet Implemented"

My private seed is well-hidden, and I want to verify that my watch-only wallet (Specter Desktop) displays correct receiving addresses.
After exporting a wallet backup (Is this the descriptor?) - I get the "Not Yet Implemented - This is still on our to-do list!" message.
Is this entire feature not implemented yet?
Is it just my specific wallet configuration?
Is it the QR code format? Or maybe the wallet-backup that I exported is not the wallet-descriptor?

If you are scanning a single-sig native-segwit or single-sig nested-segwit wallet-descriptor qrcode which you got from:
specter desktop, Wallets, Settings, Export, Go to export details,
then you are doing it right and it IS the case that this is not yet implemented.
It does however work for multisig wallets of those script types, which then allows for exploring addresses w/o your private seed.
What you might use as an alternative, until this has been implemented, is to scan an address qrcode so that seedsigner can verify that it's yours (but this is assuming that your private seed will be unhidden while doing so).
Also, you might use the address-explorer on seedsigner and compare those to what specter-desktop gives you (same assumption as before PLUS quite heavy on the eyes).
Lastly... do you trust that specter-desktop has NOT been compromised since you initially setup the wallet?  I'm guessing that we should not and that's why you're checking.  The only way to do this is to temporarily/securely unhide/expose your private seed to seedsigner and let it be the one to verify each address... or to have verified and printed out addresses at wallet setup time.
I hope this info was helpful.  Maybe other devs will have better alternatives.

do you trust that specter-desktop has NOT been compromised since you initially setup the wallet? I'm guessing that we should not and that's why you're checking.

Yes, this is exactly what I wanted to check, to calm down my paranoia... I could install a new watch-only wallet, enter the same descriptor/xpub and see that the addresses are the same - but doing this with SeedSigner would be simpler. I think this feature should be prioritized over multisig wallets.
Thanks!

@jdlcdl Any update on this?

@oren-z0 I do not have an update on this at this time.
But I still agree that to be able to scan a single-sig wallet xpub/descriptor and access address viewer would be a nice/desirable feature.   I will remember this issue in case there is any progress to that end and will include a pointer so that you'll see it here.


add Alert component

Is this similar to the CMP Alert component? I did not find any Alert component similar to CMP in Radix UI, the closest I got was the Toast component, but there is a difference between these two.

@radnan bhaia, We will need this for our Opal frontend work. I want to work on this. Would you be able to assign this issue to me? Also, do you have any plan/reference of the exposed API for this component?

this is similar to SectionMessage in CMP - and we will have a separate Toast component
@ImperishableMe feel free to start please - should have similar semantics to CMP SectionMessage


Any idea about Detectron gets overlapping and sometimes misses some blocks

The problem
I am currently using layout-parser to detect the blocks of a scanned book papers and trying to take each block separately from the page and do some processing over them.
Checklist
To Reproduce
import layoutparser as lp
import cv2

image = cv2.imread("/content/image_0.jpg")
# Convert the image from BGR (cv2 default loading style) to RGB
image = image[..., ::-1]

model = lp.Detectron2LayoutModel((lp://PrimaLayout/mask_rcnn_R_50_FPN_3x/config),
                                 extra_config=["MODEL.ROI_HEADS.SCORE_THRESH_TEST", 0.8],
                                 label_map={1:"TextRegion", 2:"ImageRegion", 3:"TableRegion", 4:"MathsRegion", 5:"SeparatorRegion", 6:"OtherRegion"})

# Detect the layout of the input image
layout = model.detect(image)

# Show the detected layout of the input image
lp.draw_box(image, layout, box_width=3)

Environment

Platform [Linux] (on colab)
Installation commands

!sudo apt-get update
!sudo apt-get install libleptonica-dev tesseract-ocr libtesseract-dev python3-pil tesseract-ocr-eng tesseract-ocr-script-latn
!pip install layoutparser
!pip install layoutparser torchvision && pip install<EMAIL_ADDRESS>!pip install "layoutparser[ocr]"
!pip install "layoutparser[layoutmodels]" # Install DL layout model toolkit

Screenshots
1- Overlapping

2- Missing

I know it may not the right place to release that issue, but I think you may have an idea about that problem

@rrrokhtar the pretrained model is trained on scientific and academic research papers. For the above corpus for scanned book paper, https://github.com/Layout-Parser/layout-model-training can be used for custom training