Zuul  "No message available" in the Services

I'm trying just send a request to the services mapped into the Zuul Gateway, but the problem is that i'm getting 404 when i try to request.
The setup is simple:
zuul:
  ignoredServices: '*'
  add-proxy-headers: true
  prefix: /v1
  routes:
    receptor-dados:
      path: /receptor/**
      sensitiveHeaders: Set-Cookie
    gerenciador-dados:
      path: /dados/**
      sensitiveHeaders: Set-Cookie
    auth-server:
      path: /auth/**
      sensitiveHeaders: Set-Cookie

I'm trying to request the address: /v1/dados/ponto  (ponto is the name of the repository mapped in the 'gerenciador-dados'). If i try request '/ponto' directly I don't have problem. The problem only happen when i try to request through  the gateway.
Response:
{"timestamp":1457526628204,"status":405,"error":"Method Not Allowed","exception":"org.springframework.web.HttpRequestMethodNotSupportedException","message":"Request method 'POST' not supported","path":"/preferences"}

Header:
Accept:application/json, text/plain, */*
Accept-Encoding:gzip, deflate
Accept-Language:pt,en-US;q=0.8,en;q=0.6
Authorization:Bearer 9df6d319-ce46-4983-9ac7-5a109dbb3b9d
Cache-Control:no-cache
Connection:keep-alive
Content-Length:53
Content-Type:application/json;charset=UTF-8
DNT:1
Host: DOMAIN
Origin:DOMAIN
Pragma:no-cache
Referer:DOMAIN
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Code:
https://gist.github.com/tiarebalbi/062a814d063ee694bbf6

The error says you are trying to POST to /preferences (which is not a route), and it's not a 404 9which you said it was). Maybe you pasted the wrong error?

Sorry @dsyer i copied the wrong erro. Follow the correct one:
{"timestamp":1457539394626,"status":404,"error":"Not Found","message":"No message available","path":"/ponto"}
Routes Available in the Gateway:

{
"/v1/receptor/": "receptor-dados",
"/v1/dados/": "gerenciador-dados",
"/v1/auth/**": "auth-server"
}

I requested the URL: '/v1/dados/ponto'. The endpoint '/ponto' is a repository into the module.
Trace Information:

{
"timestamp":<PHONE_NUMBER>632,
"info": {
"method": "GET",
"path": "/v1/dados/ponto",
"headers": {
"request": {
"host": "api.climacta.io",
"user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36",
"accept": "application/json, text/plain, /",
"accept-encoding": "gzip, deflate, sdch",
"accept-language": "en-US,en;q=0.8,pt;q=0.6,es;q=0.4",
"authorization": "Bearer 99ae66c0-e529-4797-bd1e-d9b68e11b2b9",
"cache-control": "no-cache",
"content-type": "application/json",
"cookie": "VCAP_ID=ce1a4477-2369-4f98-708b-e674162edcbf; JSESSIONID=3C1BCB39795BB01387655F4F7C0A88DD",
"dnt": "1",
"postman-token": "f0f4e2b5-e9fc-2cf5-dd19-d8a80e9a657c",
"x-cf-applicationid": "615dc1d1-d3e9-41a3-929d-89efa94a74e3",
"x-cf-instanceid": "05bd2c9b-5f54-42b7-7286-d814c00065f5",
"connection": "close",
"x-forwarded-port": "80",
"x-forwarded-proto": "http",
"x-request-start": "1457539394587",
"x-vcap-request-id": "a0470ef1-494a-4721-74a9-f5d9d8f7ea8f"
},
"response": {
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Methods": "POST, PUT, GET, OPTIONS, DELETE",
"Access-Control-Allow-Headers": "Origin, X-Requested-With, Content-Type, Accept, Authorization",
"Access-Control-Max-Age": "4800",
"X-Application-Context": "gateway:cloud:0",
"Cache-Control": "no-cache, no-store, max-age=0, must-revalidate",
"Date": "Wed, 09 Mar 2016 16:03:14 GMT",
"Expires": "0",
"Pragma": "no-cache",
"Set-Cookie": "VCAP_ID=ce1a4477-2369-4f98-708b-e674162edcbf; Path=/; HttpOnly",
"X-Content-Type-Options": "nosniff",
"X-Frame-Options": "DENY",
"X-Vcap-Request-Id": "44d61671-ef44-48a3-46a7-929cab9a48ec",
"X-Xss-Protection": "1; mode=block",
"Content-Type": "application/json;charset=UTF-8",
"Transfer-Encoding": "chunked",
"Connection": "close",
"status": "404"
}
}
}
}

Why is /** missing from two of the routes?

hmmm well noted!!
But it should't be happing look:

zuul:
ignoredServices: '*'
prefix: /v1
routes:
receptor-dados:
path: /receptor/**
sensitiveHeaders: Set-Cookie
gerenciador-dados:
path: /dados/**
sensitiveHeaders: Set-Cookie
serviceId: gerenciador-dados
auth-server:
path: /auth/**
sensitiveHeaders: Set-Cookie

@spencergibb Sorry was my mistake with the block. The URL was correct.

Did the proxy send a request to the "gerenciador-dados" service? There would be a "remote=true" entry in the /trace.

@dsyer Yes, the "gerenciador-dados" received the request:
gateway trace:
{
    "timestamp":<PHONE_NUMBER>943,
    "info": {
      "method": "GET",
      "path": "/v1/dados/ponto",
      "headers": {
        "request": {
          "host": "api.climacta.io",
          "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36",
          "accept": "*/*",
          "accept-encoding": "gzip, deflate, sdch",
          "accept-language": "en-US,en;q=0.8,pt;q=0.6,es;q=0.4",
          "authorization": "Bearer 9aee8399-0de5-42da-9043-39f495569114",
          "cache-control": "no-cache",
          "content-type": "application/json",
          "cookie": "JSESSIONID=5887578644F786400198DAF42C14DE61; __VCAP_ID__=54ec9286-afed-4556-4c6c-f19968f532f0",
          "dnt": "1",
          "postman-token": "3fd1a805-c8e7-e433-dc74-0b258adbf395",
          "x-cf-applicationid": "615dc1d1-d3e9-41a3-929d-89efa94a74e3",
          "x-cf-instanceid": "05bd2c9b-5f54-42b7-7286-d814c00065f5",
          "connection": "close",
          "x-forwarded-port": "80",
          "x-forwarded-proto": "http",
          "x-request-start": "1457543076891",
          "x-vcap-request-id": "9ea6a161-b9ac-413a-7bbf-4b071b780809"
        },
        "response": {
          "Access-Control-Allow-Origin": "*",
          "Access-Control-Allow-Methods": "POST, PUT, GET, OPTIONS, DELETE",
          "Access-Control-Allow-Headers": "Origin, X-Requested-With, Content-Type, Accept, Authorization",
          "Access-Control-Max-Age": "4800",
          "X-Application-Context": "gateway:cloud:0",
          "Cache-Control": "no-cache, no-store, max-age=0, must-revalidate",
          "Date": "Wed, 09 Mar 2016 17:04:36 GMT",
          "Expires": "0",
          "Pragma": "no-cache",
          "Set-Cookie": "__VCAP_ID__=ce1a4477-2369-4f98-708b-e674162edcbf; Path=/; HttpOnly",
          "X-Content-Type-Options": "nosniff",
          "X-Frame-Options": "DENY",
          "X-Vcap-Request-Id": "966631dd-b52a-473c-402a-978ad4c91ba4",
          "X-Xss-Protection": "1; mode=block",
          "Content-Type": "application/hal+json;charset=UTF-8",
          "Transfer-Encoding": "chunked",
          "Connection": "close",
          "status": "404"
        }
      }
    }
  }

gerenciador-dados trace:
{
    "timestamp":<PHONE_NUMBER>923,
    "info": {
      "method": "GET",
      "path": "/ponto",
      "headers": {
        "request": {
          "host": "receptor-dados.cfapps.io",
          "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36",
          "accept": "*/*",
          "accept-encoding": "gzip",
          "accept-language": "en-US,en;q=0.8,pt;q=0.6,es;q=0.4",
          "authorization": "Bearer 9aee8399-0de5-42da-9043-39f495569114",
          "cache-control": "no-cache",
          "content-type": "application/json",
          "cookie": "JSESSIONID=5887578644F786400198DAF42C14DE61; __VCAP_ID__=54ec9286-afed-4556-4c6c-f19968f532f0",
          "dnt": "1",
          "netflix.nfhttpclient.version": "1.0",
          "postman-token": "3fd1a805-c8e7-e433-dc74-0b258adbf395",
          "x-cf-applicationid": "385d338e-129b-479d-9678-73f672fc61a7",
          "x-cf-instanceid": "ce1a4477-2369-4f98-708b-e674162edcbf",
          "connection": "close",
          "x-forwarded-host": "api.climacta.io:80",
          "x-forwarded-port": "80",
          "x-forwarded-prefix": "/v1/dados",
          "x-forwarded-proto": "http",
          "x-netflix-httpclientname": "gerenciador-dados",
          "x-request-start": "1457543076891",
          "x-vcap-request-id": "00c16757-78b2-4f3f-5cc9-55fda08da885"
        },
        "response": {
          "Access-Control-Allow-Origin": "*",
          "Access-Control-Allow-Methods": "POST, PUT, GET, OPTIONS, DELETE",
          "Access-Control-Allow-Headers": "Origin, X-Requested-With, Content-Type, Accept, Authorization",
          "Access-Control-Max-Age": "4800",
          "X-Content-Type-Options": "nosniff",
          "X-XSS-Protection": "1; mode=block",
          "Cache-Control": "no-cache, no-store, max-age=0, must-revalidate",
          "Pragma": "no-cache",
          "Expires": "0",
          "X-Frame-Options": "DENY",
          "Set-Cookie": "JSESSIONID=E3BEDFE3A22CCA10A92B94017A3B8A6A; Path=/; HttpOnly",
          "X-Application-Context": "receptor-dados:cloud:0",
          "status": "404"
        }
      }
    }
  }

OK. So the backend service is sending a 404. It's nothing to do with the proxy? Why are we even discussing it?

@dsyer But there is the problem, if i try to request directly from the endpoint of the machine without pass through the gateway i can access the information:

The host from trace and the host you pointed at in the screenshot are different.

@spencergibb i just saw this i'm trying to deploy everything in another space in the Pivotal Web Service to double check.
This endpoint is from another service ("host": "receptor-dados.cfapps.io")

@dsyer and @spencergibb thank you for your support i found the problem, i was registering the "gerenciador-dados" in the eureka with the wrong domain.
Problem fixed! Thank you again.!

Hey,tiarebalbi,i am finding the answer about "why my application response header,content-length is missing when it is through the gateway layer",then i find you ask another question here,do you find your response is missing content-length header in your gerenciador-dados trace?and do you know how to solve this problem.
Ps: sorry,my english is poor,if there are mistakes i made,please forgive me,thank you for your anwser.

@jelen56 This seems like a different problem please open a new issue.

@ryanjbaxter  thank you for your advice,and this is my issue:https://github.com/spring-cloud/spring-cloud-netflix/issues/1497


Large requests broken in 0.2+

After introducing "write" method in version 0.2, the following issue is relevant again: https://github.com/ClickHouse/clickhouse-jdbc/issues/222
The reason is that all the query text is sent within URL and if query size is large enough you get "413 Request Entity Too Large"

I ran into this issue while trying to insert into a table with large number of columns.
I'm basically running "textbook" example from README:
ClickHouseStatement sth = connection.createStatement();
sth
    .write()
    .sql("INSERT INTO my_db.lots_of_columns (>> 1000 columns here <<)")
    .data(new MyCustomInputStream(), ClickHouseFormat.CSV)
    .send();

Is there a solution or workaround for this limitation/issue at the moment?

We are also running into this issue again as well. Does anyone what would be required for a fix?

+1

Since version 0.3.1 both query and external data will be put into request body. Have you tried latest driver? And what's the version of ClickHouse you're using?
Would be great if you can share reproduce steps so that I can fix.

This issues looks fixed in 0.3.1

Feel free to re-open if you think the issue still exists in new release.


Weird dynamic resizing jumping on show

When calling  [KVNProgress show]; once it is already visible the hud resizes its view, which looks like its spazzing out.

Are you changing from a showWithStatus: to a simple show?

yes

This is not supported for the moment. A workaround is keep a status or not at all for each successive HUD's.

I am also getting this issue.


UHF-X: Drupal 10.2

What was done

Replace failing patch: https://github.com/City-of-Helsinki/drupal-helfi-platform-config/actions/runs/7247469401/job/19741456898?pr=667#step:8:818

Closing as https://github.com/City-of-Helsinki/drupal-helfi-platform-config/pull/671 will take care of Drupal 10.2 updates


Member updates 2.17.22

Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you added your SVG to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
No cached entry, and can not fetch: caddy-3b18. Request failed with status code 404
Empty twitter for Mail.Ru Cloud Solutions (member): https://twitter.com/mailru
Empty twitter for China Telecom (member): https://twitter.com/chinatelecom1
Empty twitter for Mail.Ru Cloud Containers: https://twitter.com/mailru
Empty twitter for Scalyr: https://twitter.com/scalyr
Empty twitter for Spotinst Functions: https://twitter.com/spot_hq
No cached entry, and Sangfor CNAD has issues with twitter: https://twitter.com/SangforUSA, Request failed with status code 404
No cached entry, and Sangfor EDS has issues with twitter: https://twitter.com/SangforUSA, Request failed with status code 404
Empty twitter for SeaTunnal: https://twitter.com/ASFSeaTunnel
Empty twitter for Karmada: https://twitter.com/karmada_io
Caddy either has no crunchbase entry or it is invalid

@AndreyKozlov1984 can you help here? none of the issues in the error message relate to my changes. thanks!

@taylorwaggoner please review

Thanks @AndreyKozlov1984
LGTM @caniszczyk


[stack] shift + left/right moves focus to/from the rail and the section body

Left and right arrow keys already do this.
If focus is within either of these elements, escape should move focus to to them, at which point left and right arrow keys will do this.
It is the same number of key presses, just not chorded. Since we should arrive at a consistent way of moving focus, I think adding chorded synonyms that we cannot make consistent (since it is how text is selected in text areas) is not going to deliver significant value for the added complexity.

what happens when there are multiple columns in a deck? doesn't L/R move between columns?

Currently, tab is how you move between columns. I'll see if tabster's grid is up for the challenge, one obstacle may be that Deck columns can have different scroll positions.


Revert type hints

This PR reverts a bunch of commits related to type hints.
The issue with the type hint commits, is that I did not realize I could
avoid changing the file structure of stk. So this commit will revert
all the changes and I will start making new type hint commits, which
do not restructure the folders of  stk.

Frustrating, but glad to hear it to be fair.


merging latest

@sankethka,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Qusetions about the test resutls on SALICON test set.

In this paper, the author said "The model trained on SALICON was finetuned using MIT1003 and CAT2000." I am wondering that if the model is fine-tuned on MIT1003 and CAT2000 when generating the resutls on SALICON 2017 test set?
In  short:
on SALICON: model trained on SALICON -> test on SALICON.
on MIT300: model trianed on SALICON+MIT1003 -> test on SALICON.
or like that
on SALICON: model trained on SALICON+MIT1003+CAT2000 -> test on SALICON.
...

Hey @pengqianli, for SALICON test the model is trained on SALICON and tested on SALICON test. For MIT1003, model trained on SALICON is finetuned on MIT1003(k-fold cross validation) and tested on MIT300 test set. Similarly for CAT2000.
So,
on SALICON: model trained on SALICON -> test on SALICON
on MIT300: model trained on SALICON + MIT1003(finetuned using k-fold cross validation) -> test on MIT300
Does this solve your issue?

yes, thanks!


Cme feature: Target button - support for all types of entities

Should be fine now - Removed the two lines.
On a side note, I noticed two things in the main branch:

Layouting doesn't work - When you were rewriting part of code you wrote if instead of else if, but that is fixed in another branch, for which I will open PR next.
The target button no longer works, but maybe that will be fixed by this merge

We can merge once the conflict is resolved.

Yet, it would be best to have a way how to enforce the right match, model to model, entity to entity, in TS. Perhaps we can introduce a new type to wrap both of them together as  a way to reference an entity. We can discuss this in the issue.

Yet, it would be best to have a way how to enforce the right match, model to model, entity to entity, in TS. Perhaps we can introduce a new type to wrap both of them together as a way to reference an entity. We can discuss this in the issue.

I am not sure if we are thinking about the same issue, but I know what you mean. We can quickly discuss that tomorrow if there will be time.


doc: Update AUTHORS file

Added the ready-to-merge label manually as this PR is only a doc update, no need to run the CI tests.


RFC: if let chains

Decrease redundancy in cases like
if let c a := x then
  if q a then
    y
  else z
else z
...

by supporting mixed let/condition chains like
if let c a := x && q a then
  y
else z
...

This is a syntactic idea I thought was too wild to even propose, until I learned that Rust will have it, so obviously it must be a good idea.
Probably even more than for Rust though, parsing this is a bit of an issue. The cleanest approach I could come up with so far is to keep basic if syntax intact and introduce new chain syntax for subterms of precedence greater than &&/∧ only.
syntax letChainElem := "let " term " := " term:36  -- "&&"/"∧" have precedence 35
syntax (priority := low) "if " sepBy1(letChainElem <|> term:36, "&&", " && " <|> " ∧ ") " then " term " else " term : term
#check if let x := a && p x then c else d  -- parsed as elements `[let x := a, p x]` (after removing current `if let` syntax)
#check if let x := a && let y := b then c else d  -- parsed as elements `[let x := a, let y := b]`
#check if a || b then c else d  -- parsed by basic syntax
#check if a || b && let x := a then c else d  -- parse error, incomplete term `let`
#check if (a || b) && let x := a then c else d  -- parsed as elements `[a || b, let x := a]`
#check if a then b else c  -- parsed by both, disambiguated by priority

Desugaring: obvious, modulo introducing join points

Isn't it possible to use notFollowedBy to parse the && in this case, instead of using high precedence (which would also affect if let x := <low prec expr> then e1 else e2)?

if let x := <low prec expr> then e1 else e2

Oops, now I remember what I thought was the tricky case! The problem with notFollowedBy is that it would yield a pretty unexpected result on if let x := f <| p && q, wouldn't it? But perhaps that's acceptable...

Does this mean that and becomes shortcircuiting?  This would be so awesome.
if (← expensive) && (← slow) then
  -- does not execute `slow` if `expensive` returns false
  plowSnow

We could also use a keyword as separator:
if let .some x := a and let .some y ← f x then
  return (x, y)

Oh my, it looks like we're only further diverging from regular &&. In that case a new keyword does seem like the better approach. I wanted to introduce and anyway as mutual infix syntax, which does not collide with use in if.

Everyone okay with and then? Because I for sure want this :) .

um, that's the name of a very popular function on Bool...

How often do you use it neither namespaced nor notationed?

Grepping for it (which is hard...) reveals some uses in inductive types denoting formula syntax. and is a pretty high-demand identifier name.

So is forall... but I'm open to alternatives

rec is also a pseudo-keyword, right? Can we do something like that, say that and is not legal unparenthesized inside the condition of an if let statement?

By the way, the impact of registering constructor names as tokens has been lowered significantly by accepting them unescaped in inductive declarations and by introduction of the leading dot syntax.

I'm not totally against it, but it would need some publicity on zulip first I think to get people on board with the idea. I expect that for a lot of folks this is just a pure loss because they weren't planning on using if let in the first place.

Despite being generally adverse to new keywords, I think making and a keyword for this is a good idea.  For one, Python already uses and as a keyword for stuff like this, so there is a low introduction cost -- even for some mathematicians who may have already dabbled a bit in Python. Second, most of the stuff the identifier and is used for already has more sugary notation, so I would imagine this would break much existing code.
@digama0

I expect that for a lot of folks this is just a pure loss because they weren't planning on using if let in the first place.

By 'folks', do you mean mathematicians or do you fin if let less useful more generally? I personally use if let a lot in programming code, but it does seem less useful in math code. However, I would still appeal to Python style to argue that and being a keyword is reasonable.

I mean mathematicians. I use if let all the time, and I would use if let chains if they were available, but if you are spending your time doing proofs in lean 4 I would not be surprised if you come across and more often than you come across if let.

An alternative to and could be andif.

An alternative syntax without keywords.
We already have a "let chain" syntax:
-- One-linear
let x := a; let y := b; x + y

-- Multi-line
let x := a
let y := b
x + y

Then it seems natural to have a similar syntax in if:
-- One-linear
if let some x := a; let some y := b; then x + y else 0

-- Multi-line
if let some x := a
   let some y := b
then
    x + y
else
    0

-- Mixed let/condition
if let some x := a; x < 10 then x + 1 else 0

By chance, the last syntax is similar to C++'s if with initializer.

Unfortunately, that syntax overlaps with regular let expressions inside the conditional. That is, if let x := a; b then c else d is already valid syntax and means if (let x := a; b) then c else d. I suppose the if could parse the conditional using the regular term parser and then post-process it to treat any unparenthesized top level let in a special way... but let x := a; let y := b is not an expression, and let x <- a certainly isn't an expression.

I found some things in the recent "The Ultimate Conditional Syntax" by Chang and Parreux to be compelling, and I think it would be worth considering a design that could one day support some of their more elaborate forms.
I think a solution here would be to make let PATT := VAL valid syntax on its own, then make if have its own elaborator for conditionals, with support for &&, this let, and matches. The wrinkle is that you need to write parentheses for chains:
if (let .some x := a) && let .some y ← f x then
  return (x, y)

Perhaps this let PATT := VAL syntax would elaborate like a matches expression when it appears outside an if, or maybe it gives an elaboration failure to let you know the pattern would be binding any variables.
For an example of the more elaborate forms from the paper, here's a possible Lean version of one from the end of page 2:
if x matches
  | .inr none then defaultValue
  | .inr (some cached) then f cached
  | .inl input && compute input matches
    | none then defaultValue
    | some result then f result

But as you can see this would be a very big change to the if parser!


remove unused stuff and reduce scope and visibility

these things appear unused or unneeded elsewhere, so eliminated some and reduced the visibility of others.

Looks good!
Just for context (related to my comment on the last PR) in the fullness of time, ideally all the code in src/common/locations.ts would go away in favor of code in
https://github.com/covid-projections/covid-projections/blob/221444b06c2d74ec62cf2573b742be836b9a6f49/src/common/regions/region_db.ts#L12

Ah, good, thanks for the heads up.  I'll look for opportunities to move in that direction.


refactor(vue): revised menu & tests

[x] revised menu components
[x] stories
[x] tests

Tell me when you finish :)

I took a quick look. First of all, great work! I'll test everything tomorrow on my PC.

Thanks! Feel great to contribute to ark-ui. Wating for your test.
And i will continue to contribute to ark. Looking forward to vuejs 1.0.

@Omikorin That's okay! Thanks for your time to review. Hope you can have time to rest.


Admin Consent Request

I am not a global administrator, but have separated Azure roles like "Purview Administrator, Global Reader, SharePoint Administrator, License Administrator, etc". I have also full control access to a resource group and created the Azure Log Analytics.
When I run the command "MPARR_Setup.ps1" and use option 1 "Setup MPARR (select LA, register Azure app...)", I select the subscription, Log Analytics Workspace. Then I need to sign in with my account in the browser. After this I see a admin consent request popup.

I need to enter a reason and click on the blue request button. After this I see a popup that it will be under review by a global admin.

Where can I find this request and under which name? I would like to ask the global admin to approve it. I already checked this Azure Access Requests page, but I dont see it or not know under which name I should find it.
https://portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AccessRequests/menuId~/null

You can try through:
Microsoft Entra ID --> Enterprise Applications --> Admin consent requests
https://portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AccessRequests/menuId~/null

I already checked that page, but we dont no which name we should expect in all the requests. Do you know? We already scroll down all the requests and did't see something with the word 'mparr'

It was "MS Graph PowerShell" in the Admin consent requests list.

And works now?

Yes, the setup is working fine now.


Change “Ok” to “OK” in button text

The current UI uses a mix of “Ok” and “OK” for its OK button text. This PR changes it to be “OK” everywhere, which I think is the standard capitalization on Windows.
Before:

After:

:white_check_mark: Build ServiceBusExplorer 4.2.0-PullRequest0332.100.build.548 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/952aba9202 by @apjanke-ccs)


core-pages always showing google maps

core-pages is always showing google maps no matter which page is selected, even though google maps is in a different polymer component.  It's switching pages correctly as the correct core-toolbar is showing, but google maps is always visible.
<core-pages id="pages" selected="0" flex>
    <home-view></home-view>
    <map-view></map-view> <!-- contains google map -->
</core-pages>

It looks like we will need a bit more info here, can you post a link to a full example? Most likely the map-view has some css which is overriding how core-pages is trying to hide it.

Here's a link to a working example, https://github.com/terrywarwar/core-pages-google-map-example

This is pretty weird, if you select the map-view and inspect it you can confirm that it is set to visibility: hidden, yet for some reason the map contained inside it is still visible.
I wasn't able to track down exactly why that is, but it seems like a bug on the google map library itself.
I did find a workaround, which is to simply assign a background color to the  tag, it has a higher z-index so that covers up the map. This is really just hiding the problem though.

Yes, I noticed the visibility: hidden.  Nice workaround, I wanted to put a background color on that view anyway.
@a14n maybe able to shed some light on the issue.

The core-animated-pages uses display: none, not visibility:hidden like core-pages. Looks like display: none in core-pages works with google maps.

Sorry, no idea (and I cannot reproduce the issue with https://github.com/terrywarwar/core-pages-google-map-example/commit/b51b256ff0a68649f5eeae7fe50611f48b7aa501)

@a14n I was definitely able to get a repro with that example, I only tried in dartium I wonder if you were trying the compiled version and that behaved differently?

I used dartium/stable .

Interesting, I am on the dev release so I wonder if that could have anything to do with it

weird..... now I can't get a repro either

I did try with dev channel as well. But same result. I was wondering if a git push -f was used.

I haven't synced since yesterday when I was able to repro though... so that is weird. The only thing I can think of is I may have updated my dev version yesterday.... so maybe it was a dartium bug? It did kind of seem that way.

@terrywarwar can you confirm if you can still repro on the latest dev release?

I can't reproduce in latest dev version, it works.  Looks like it was a dartium bug.


Link to latest Zulip version from the homepage (/hello.html)

We should link to the Zulip installer (mentioning the current latest Zulip version) in /hello.html, aka https://zulipchat.com.
I think the right style would be to have either a new paragraph or a button for the install link; in any case, the text should be something like:
[Install Zulip 1.9](link-to-install-page), or [read the Zulip 1.9 announcement](link-to-blog-post) (with the latter part being text even if the first is a button)
We'll need to add a note to the new-release checklist about updating version.py to have the "latest release" version there, as part of this process.

If someone does styling that looks good hardcoding the version, I can deal with the version number plumbing as part of merging this.

Note that this should be in the "Open Source" section of that page.

Hello @timabbott I am new to zulip and I want to contribute. I think for this issue we can use something like izimodal

is this issue closed?


fix: remove deprecated flag for bazel 5.x.x

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@ecasilla Thanks for the contribution! That flag is referenced here as well: https://github.com/adobe/rules_gitops/blob/master/examples/.bazelrc#L2


Access traits to construct a bounding volume hierarchy from the primitives

MAKE SURE TO MERGE #512 BEFORE Done

Sorry about the force push, had forgotten to reword a commit message

Codecov Report

Merging #513 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #513      +/-   ##
==========================================
- Coverage   96.18%   96.18%   -0.01%
==========================================
  Files         127      128       +1
  Lines        9261     9248      -13
==========================================
- Hits         8908     8895      -13
  Misses        353      353

Impacted Files
Coverage Δ

...ree/src/DTK_DetailsNearestNeighborOperatorImpl.hpp
100% <ø> (ø)
:arrow_up:

packages/Search/src/DTK_LinearBVH_decl.hpp
100% <ø> (ø)
:arrow_up:

...s/Meshfree/src/DTK_MultivariatePolynomialBasis.hpp
100% <ø> (ø)
:arrow_up:

...s/Meshfree/src/DTK_NearestNeighborOperator_def.hpp
100% <100%> (ø)
:arrow_up:

...es/Meshfree/test/tstMovingLeastSquaresOperator.cpp
97.92% <100%> (-0.05%)
:arrow_down:

packages/Search/src/details/DTK_DetailsTraits.hpp
100% <100%> (ø)

...s/Meshfree/test/tstMultivariatePolynomialBasis.cpp
100% <100%> (ø)
:arrow_up:

...h/src/details/DTK_DetailsTreeConstruction_decl.hpp
100% <100%> (ø)
:arrow_up:

...eshfree/src/DTK_MovingLeastSquaresOperator_def.hpp
100% <100%> (ø)
:arrow_up:

.../src/DTK_DetailsMovingLeastSquaresOperatorImpl.hpp
100% <100%> (ø)
:arrow_up:

... and 2 more

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 ab7a05c...771434a. Read the comment docs.

Rebased on master now that #512 has been merged and forced push.  This makes it easier to see what changes this PR actually introduces.

Note that I didn't propagate the changes to the Discretization package where the interpolation operator will also be able to take advantage of the fact we can construct the index from a rank-2 view.


Add missing annotation to ueransim ue-configmap

Add missing annotation to ueransim ue-configmap

/assign @arora-sagar @efiacor

/lgtm
/approve

@liamfallon though I approved and merged but now I realize, do we need the annotation in the configmap? The ueransim-fn makes the gNB configmap.

That file is in the catalogue at:
https://github.com/nephio-project/catalog/blob/main/workloads/tools/ueransim/ue/ue-configmap.yaml
If the ueransim-fn overwrites it then we'll have to make a code change on the function to add the annotation. Let me test it.


[GLUTEN-1220] Add shim dependency in gluten-ut pom.

What changes were proposed in this pull request?
Fix #1220
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Thanks for your patch!
Can we unify the dependency in gluten-ut/pom.xml with the below code? Just for brevity consideration. Not sure whether it works for testing with -pl gluten-ut/spark32. Maybe workable for -pl gluten-ut (enough to us)? Thanks!
    <dependency>
      <groupId>io.glutenproject</groupId>
      <artifactId>${shims-spark-artifactId}</artifactId>
      <version>${project.version}</version>
    </dependency>

@PHILO-HE
Thanks, I will rebase main and retry with -pl.


10 data volume

Haven't had a chance to test this yet, so consider it a WIP for now.

Tested and debugged

Woo! Awesome work. I'm reviewing now. Quick question: the documentation in the new "Basic Usage" section is stuff most users won't need to mess with, right? Just people who need to change the defaults, right?

Right. I admittedly skimped on the documentation. Basically the way it works now should support running it the same was as before, but the configs can now also be changed via command line or environment variable. This allows you to change them while running in a container, as well as also working without Docker entirely (modulo dependencies).

:+1: Everything runs fine and looks good here. I'll make a separate PR with some documentation changes. Thanks!


fix: fixes #81

This just moves the flow diagram to the intro section, fixes #81

Merging this now, so folks don't run into conflicts later. This PR really just moves the diagram.


files.exclude setting being ignored

In my settings.json file in VS Code, I have "**/build": true," included in the files.exclude setting. This works as expected in VS Code's user interface, but the PHP language server appears to be ignoring this setting.
I'm currently debugging the following error:
The PHP Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.
In the PHP language server output I see the following:
Parsing file:///sites/wp/build/wp-content/plugins/publishing-checklist/tests/test-publishing-checklist.php [Error - 9:57:51 AM] Connection to server got closed. Server will not be restarted.
As you can see, the file in question is in the build directory and therefore should be ignored by the PHP language server.
Is there a reason it isn't? If so, is there a way to exclude files/directories from being parsed by the PHP language server?

Since this is just the server, it's up to the extension to pass the parameters.
See https://github.com/felixfbecker/php-language-server/issues/159


docs: updates and improvements

How to categorize this PR?

/area documentation
/kind enhancement
/priority normal
/platform equinix-metal
What this PR does / why we need it:
This PR updates and clarifies some of existing documentation.
Which issue(s) this PR fixes:
Initial cleanup to prepare for #109.
Special notes for your reviewer:
Release note:

NONE

Thank you @invidian for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.


Batch dialling

The libp2p.dial method should support dialling multiple multiaddrs - it currently supports dialing a peer id (in which case multiaddrs are retrieved from the peer store) or a single multiaddr.
Since only a single connection is returned from a dial, the multiaddrs being dialled should be checked to ensure they either all contain the same peer id or that none of them contain a peer id.
If they all have the same peer id we are guaranteed to return a connection to the expected remote peer, if none of them contain a peer id then the user did not expect a connection to a specific peer so we are ok to return a connection to whatever remote peer we managed to connect to first.

This may be a strange case but how would we handle a situation if they have different peerIDs for the multiaddrs? return the one we connect to first?


[Blazor] Reload link doesn't work

That button doesn't work when the connection is lost.

/cc @NTaylorMullen

Hmm, I didn't change how we suggest the user page reloads (it uses an <a href>...</a> tag) but I can definitely see what you're seeing in dotnet new blazorserver. Also, it doesn't seem like it's consistent either. In Blazors test app it worked just fine:

Tried reproducing it working in a dotnet new blazorserver template app and haven't been able to. @rynowak do you think this is ask mode worthy?

So talked offline. Given that this behavior hasn't changed from previous Blazor releases (we brought forward how we suggested users reload the page) and that it's pretty obvious for a user to just "reload" in their browser I'm going to park this in 3.1

I also filed https://github.com/aspnet/AspNetCore/issues/13370 without realising it was a dupe of this.
However, since #13370 also contains a diagnosis of exactly what was broken, I'm going to close this one in favour of that.
That also means we'll re-triage. So, closing as dupe of #13370.


main CI broken: tests/drivers/build_all/modem/drivers.modem.modem_cellular.build fails to build

Describe the bug
tests/drivers/build_all/modem/drivers.modem.modem_cellular.build fails to build on native_posix & qemu_x86 due to multiple issues.
At least the following issues cause the compiler to fail:

a double pointer is provided where the compiler expected a pointer,
telit_me910g1_periodic_chat_script being not defined.

To Reproduce
Steps to reproduce the behavior:

twister -p native_posix -s tests/drivers/build_all/modem/drivers.modem.modem_cellular.build
see error

or

mkdir build; cd build
cmake -GNinja -DBOARD=native_posix ../tests/drivers/build_all/modem/ -DCONF_FILE=modem_cellular.conf
ninja
See error

Expected behavior
No build issues
Impact
main development blocked when this test is triggered in CI
Logs and console output
https://github.com/zephyrproject-rtos/zephyr/actions/runs/6769657675/job/18396479285?pr=64839#step:12:952
https://github.com/zephyrproject-rtos/zephyr/actions/runs/6769657666/job/18396537263?pr=64839#step:13:1079
Environment (please complete the following information):

OS: Linux, Ubuntu 22.04 CI
Toolchain (e.g Zephyr SDK, ...): Host gcc (11 or 12)
Commit SHA or Version used: main as of now f027b55d026e0626905c7d4def36468f67dd923b

Additional context
Introduced by c76d5b882c1416ce48b918a4d1e034b913baa873

Fixed by  #64858


Improve cells bonding algorithm

We need to improve cells bonding algorithm.

Problem clarification:
When the cell with existing connection divides, he is replaces with two child cells. The problem is, the children do not inherit the existing connections, so they always disconnect from their neighbors:

The right behavior for the cell in the previous example would be:

I will later provide a more detailed explanation about how connections should be processed when cell divides.


custom naming schemes

@helveticade pointed out that inspecting HTML with just hashes doesn't relay a lot of information per-se; when debugging having something like the file filename / dirname available is neat; perhaps we can expose a hook for people to create their own prefix (in addition to the hash, which guarantees uniqueness). Thoughts?

for reference, here's how css-modulesify does it, here's how cssify does it, and how webpack does it.


Compilation errors and boot looping on Wemos D1 mini (clone)

Hi!
Besides after fixing the errors in main.cpp#4 (typo in ifdef) and adding ESPAsyncUDP for the ESP8266 and compiling, my board gets stuck in boot loop and I have no idea why. Tried on two different 8266 development boards and with various changes in configuration. Compiled and uploaded both on Windows and MacOS, no change.
 *  Executing task in folder ikea-led-obegraensad-feature-vscode_devcontainer: platformio device monitor --environment d1_mini --port /dev/cu.usbserial-1420

--- Terminal on /dev/cu.usbserial-1420 | 115200 8-N-1
--- Available filters and text transformations: colorize, debug, default, direct, esp8266_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time
--- More details at https://bit.ly/pio-monitor-filters
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H

 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v000b7020
~ld
���g�;��o|�
           $�$`c�
                 |s�l�'��'�l`��;�l�d
                                    �
 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v000b7020
~ld
����n�;��n|�
            $�d`c�
                  <r�l�'��'�d`��s�$�l
                                     �
 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v000b7020
~ld
���o�;��n|�
           $�d`c�
                 <;�l�g��g�l`��;�l�d�
                                     �
 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v000b7020
~ld
���'��{��'<�$
             �l`c�
                  |s�l�'�
                         �n�
                            $ ��{�$�l�
                                      �
 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v000b7020
~ld
����n��{��n|�
             $�d`c�
                   |s�d�n�
                          �n�
                             $ ��s�$�l
                                      �
 ets Jan  8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v000b7020
~ld
���o�;��o|�
           $�d`c�
                 |s�d�n�
                        �n�
                           $ ��s�$�l

                                    �

If you are still having issues maybe post a diff of what you have changed (removing any passwords), as that could help others replicate the results.


aks-deploy.yaml file patching documentation issue

Document link:- https://github.com/mspnp/aks-baseline/blob/main/06-aks-cluster.md
There is a pipe missing aks-deploy.yaml patching command in documentation. Currently command is throughing an error like:
pallav@Azure:~/aks-secure-baseline$ cat github-workflow/aks-deploy.yaml | \

sed "s#<resource-group-location>#eastus2#g" | \
sed "s#<resource-group-name>#rg-bu0001a0008#g" | \
sed "s#<geo-redundancy-location>#centralus#g" | \
sed "s#<cluster-spoke-vnet-resource-id>#${RESOURCEID_VNET_CLUSTERSPOKE_AKS_BASELINE}#g" | \
sed "s#<tenant-id-with-user-admin-permissions>#${TENANTID_K8SRBAC_AKS_BASELINE}#g" | \
sed "s#<azure-ad-aks-admin-group-object-id>#${AADOBJECTID_GROUP_CLUSTERADMIN_AKS_BASELINE}#g" | \
sed "s#<azure-ad-aks-a0008-group-object-id>#${AADOBJECTID_GROUP_A0008_READER_AKS_BASELINE}#g" | \
sed "s#<domain-name>#${DOMAIN_NAME_AKS_BASELINE}#g" \
sed "s#<bootstrapping-repo-https-url>#${GITOPS_REPOURL}#g"

sed: can't read sed: No such file or directory
sed: can't read s##https://github.com/pallavgupta/aks-baseline.git#g: No such file or directory
sed: couldn't write 153 items to stdout: Broken pipe

Thanks @pallavgupta for letting us know, fixed in #309
Btw, if you're currently going through this, just be aware of a known issue that was recently introduced (a regression) that is fixed in #306 -- I'm waiting on a final review before I merge that in.

@ckittel Thank you.


Update network.js

Fix for CMD popup for windows.

@Alankarsharma fixed. Version 4.34.5 just published. Thank you!

@Alankarsharma fixed. Version 4.34.5 just published. Thank you!


Color frames not available after kernel update

librealsense
2.38.1 RELEASE

OS
Linux

Name
Intel RealSense D435I

Serial Number
938422076303

Firmware Version
<IP_ADDRESS>

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
2.1

Product Line
D400

Asic Serial Number
926623050310

Firmware Update Id
926623050310

Please provide a description of the problem
Color frames not available after kernel update to 5.9.1. I tried rebuild the source and reinstalling.
|Kernel-version|5.9.1|

Hi @sridhargunnam  librealsense is currently officially supported up to kernel 5.3 (though 5.4 generic works stably even though it is not officially validated for use with librealsense yet).
I am not aware of kernels newer than 5.4 having been used with librealsense.  If you wish to retain kernel 5.9, you could try the RSUSB method of building librealsense, as it is not dependent on Linux versions or kernel versions and does not require patching.  The RSUSB installation process does require an internet connection though.  The instructions for this method of building from source can be found in the link below.
https://github.com/IntelRealSense/librealsense/issues/6368#issuecomment-636316279

Hi @sridhargunnam   Do you still require assistance with this case, please?   Thanks!

Case closed due to no further comments received.


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/instalator/ioBroker.synology

[ ] [E114] No adapter are allowed in the repo without admin3 support
[ ] [E801] No repository about text found. Please go to "https://github.com/instalator/ioBroker.synology", press the first "Edit" button you will find on the page and add the description.
[ ] [E802] No topics found in the repository. Please go to "https://github.com/instalator/ioBroker.synology" and press "Manage topics"
[ ] [E604] No "## License" found in README.md
[ ] [E701] No actual year found in LICENSE. Please add "Copyright (c) 2017-2020 instalator<EMAIL_ADDRESS>at the start of LICENSE

I have also found warnings that may be fixed if possible.

[ ] [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Do you need help fixing the bugs?

RE-CHECK!


[master] NSDictionary NSFileManagerExtensions tests fail on OSX

2017-05-08T19:06:09.2838540Z [ RUN      ] NSDictionary.NSFileManagerExtensions
2017-05-08T19:06:09.2849030Z NSDictionaryTests.mm:365: Failure
2017-05-08T19:06:09.2859460Z Value of: fileAttributes.filePosixPermissions
2017-05-08T19:06:09.2871330Z   Actual: 576
2017-05-08T19:06:09.2883400Z Expected: 123456
The above is a run from the master branch.
It seemed to be not an issue in the develop

commit 58212e0406fb82daa9a7e4f5414efa1b704e09e3 needs to be cherry-picked to master.

Thanks @msft-Jeyaram cherry-picking this.


doc: fix long badges

coverage: 95.796%. remained the same
when pulling 0e25a383823a12ec05b2b7ec5a86c6c7a9269fc9 on doc-badges
into 1346cae9960b3c3f62b9e48532c5601fd8a73dec on master.


missing expression.cc example?

Hi,
First, wow!  Kudos to you, this is very cool.
Your documentation says that there should be examples/expression.cc which is the same as the calculator example, but builds an parse tree and operates on that.  I'm either incredibly blind, or it's not in the examples directory.
I'd really like to see a good example of how to build a parse tree with this parser.

The file actually exists, unfortunately I can't remember why it was taken out of the examples directory. Take a look, see whether it works, report back, and if it does work we might put it back. It doesn't seem to be the most readable example in the world, which could be the reason we got rid of it :-)
expression.txt

We just discussed this issue, the expression example was removed because, as you can see, it is not particularly readable and doesn't show how to build an AST in a nice way - it was more an experiment in how to handle the operators.
For now, I will remove the reference to it in the documentation; we already have "make a nice AST example" on our TODO list and will hopefully get around to doing this soon.


How to use the pre-installed LLVM package?

It appears that currently depending on LLVM_LOCAL_DIR configure either uses the externally provided LLVM source tree or downloads it.
How to use pre-installed LLVM without rebuilding it?

These args
cmake -DCMAKE_INSTALL_PREFIX="YOUR PATH TO RETDEC DIR" -G"Visual Studio 16 2019" -DRETDEC_ENABLE_ALL=ON -DCMAKE_BUILD_TYPE=ALL ..

You can clone avast/llvm, build it, and then use it in RetDec compilation by specifying LLVM_LOCAL_DIR=<path to cloned repo>. Then, you can make changes to this LLVM sources and when you recompile RetDec it will reflect these changes. This is good for dev purposes.
You cannot use pre-built vanilla LLVM from you system installed for example by your package manager. Unfortunately RetDec uses its own LLVM which is slightly modified and cannot work with the vanilla LLVM.


[Iterators] Replace utility builders for SCF ops by upstreamed builders (NFC).

CI still fails due to an upstream bug. It should work once my fix has landed and I updated the LLVM dependency of this repository.


all: run builds and tests with go1.18beta1

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Run builds and tests with Go 1.18beta1.
Why
See what breaks, make sure we're in a good place to switch when it releases in a couple months.
Known limitations
N/A

Something odd is up, because we explicitly disable composite checks in govet.sh ( go vet -all -composites=false ...)

Could it be that now go vet -vettool also does the other go vet checks? (i.e. we need to run go vet -composites=false -unreachable=false -tests=false -vettool=$(which shadow) ./... instead of go vet -vettool=$(which shadow) ./...?
Another possibility is that -vettool is broken in the beta release.

@2opremio This is very strange, I thought -vettool might be broken, I saw it now identify shadowed variable but identify composites locally, so I opened https://github.com/golang/go/issues/50195. But I have a new shell open and trying to reproduce it again while debugging and it isn't reproducing and it is working fine locally for me.

I believe the issue was that go get no longer installs binaries in Go 1.18. Our govet.sh script was using go get to install shadow, then running go vet -vettool=$(which shadow). Because shadow wasn't installed the result of which shadow would have been an empty string and it was like we were running go vet with no parameters. I've pushed 3674d36 that changes how we run the shadow binary to use go run so we are not fiddling around with installing.


Tag was lost

Hello,
When I write Nfcv Tag with nfc.transceive ,It returns "Tag was lost".
This is my code:
------------------------------start------------------------
async testWrite() {
await this.nfc.connect('android.nfc.tech.NfcV')
this.nfc.transceive('90 5A 00 00 03 AA AA AA 00').then(
response => console.log(response),
error => console.log( error)
)
}
-----------------------------end----------------------------
I don't know what went wrong.Can you give an example on how to use nfc.transceive() if possible.Thanks a lot

+1

@Amanda1995pig Which command should i use to get all the bytes from my NfcV device.? Like the one you have used (90 5A 00 00 03 AA AA AA 00).

Hello, I also get every time the error "Tag was lost", in NfcA mode.
But are you sure that the HEX command in string mode must be sent with a space between the hex values?
By the way I get the same error with or without the space.
nfc.connect('android.nfc.tech.IsoDep', 100).then(         () => {             // Authenticate AES             var apduCommand = '90AF00000001';				             nfc.transceive(apduCommand).then(                 (response) => { console.log("Transceive response: " + util.arrayBufferToHexString(response));                },                 (error) =>  {   console.error("Transceive error:", error);                }             );         },         (error) => console.log('NFC Connection failed', error)     );
Any idea?


Outputting Text

How could I make Alexa output text to be displayed in an application?

What exactly do you mean? You want the transcription of your voice?

I'd like it to output my question and it's answer.

AFAIK it's not possible (someone please correct me if I'm wrong).

This project is now deprecated in favor of the new AlexaPi (https://github.com/alexa-pi/AlexaPi) which has all the features of this project and much more, such as:

support for a wide range of devices and platforms (Raspberry Pi, CHIP, Orange Pi, desktops, Magic Mirror and others)
voice activation (great PocketSphinx support and snowboy support soon to be released)
much more robust installation and configuration
better security
Arch Linux support
awesome documentation
and much, much more! You get it - it's just awesome.

Please switch over to the new project and if your issue persists there, file an issue in the new repo's issue tracker. Thank you.


Does not work?

Good day, 👋🏻
First of all, I think your package is very cool and the approach is really great. However, I have encountered a problem. The function get_access_token obviously does not work properly, or is answered by discords with a 400 error.
How can I fix this error, or is it a configuration error on my side?
Kind regards!

Error fixed, was a configuration error on my part


Windows build fails from time to time

Looks like there can be some issue in the process of building base-validating-builders on Windows, cause it fails to clear the base\base-validating-builders\build folder from time to time:
20:50:14.535 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Caused by: org.gradle.api.file.UnableToDeleteFileException: Unable to delete directory 'D:\IdeaProjects\Spine\base\base-validating-builders\build'
20:50:14.535 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   Failed to delete some children. This might happen because a process has files open or has its working directory set in the target directory.
20:50:14.536 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   - D:\IdeaProjects\Spine\base\base-validating-builders\build\debug-out.txt
20:50:14.536 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   - D:\IdeaProjects\Spine\base\base-validating-builders\build\error-out.txt
20:50:14.536 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.file.delete.Deleter.throwWithHelpMessage(Deleter.java:145)
20:50:14.536 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.file.delete.Deleter.doDeleteInternal(Deleter.java:88)
20:50:14.536 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.internal.file.delete.Deleter.delete(Deleter.java:78)
20:50:14.536 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 	at org.gradle.api.tasks.Delete.clean(Delete.java:78)

The second gradlew clean run fixes the issue, but maybe we have something in the plugins that actually lock some files?
Looks like the issue is similar to https://stackoverflow.com/questions/54488100/gradle-failed-to-clean-output-directory

Outdated.


Fields widgets without generic type is not able to benefit from valueAccessor's

Hi)
To demonstrate what I mean let's look at ReactiveTextField<T> it has generic type and ControlValueAccessor prop to be able to utilize valueAccessor's
On the other side:
ReactiveCheckboxListTile
ReactiveSlider
ReactiveSwitch
ReactiveSwitchListTile
ReactiveTimePicker
does not support valueAccessor.
Is this by design or just a typo?

Hi @joanpablo
Could you give any feedback on this issue?

Will be releasing separate packages for each control to unify the api
It is too long to wait for iteration...
https://pub.dev/packages/reactive_checkbox


Bug in search task quant SILAC

Save a task with a SILAC quantification label specified, open the task it, change it to no quantification, save it, reopen it, and it will say SILAC instead of no quant.

fixed in #1769


[Tree] Using "sibling" property is wrong

First of all, sorry for my English.
When i try to move up/down a node (not root) without defined "sibling" property in my Entity class it throws an error. If the property ("sibling") manually defined than after save node has not correct level.
I think the problem in
https://github.com/Atlantic18/DoctrineExtensions/blob/v2.4.10/lib/Gedmo/Tree/Strategy/ORM/Nested.php#L334
and
https://github.com/Atlantic18/DoctrineExtensions/blob/v2.4.10/lib/Gedmo/Tree/Strategy/ORM/Nested.php#L350
Also, we can't set the property without exists check
https://github.com/Atlantic18/DoctrineExtensions/blob/v2.4.10/lib/Gedmo/Tree/Entity/Repository/NestedTreeRepository.php#L113

yes that is an ugly solution to use that property in extensions, so in your case you do have a property named sibling on your entity? PHP should add the property if it does not exist, but that should be fixed anyway to different solution, thanks for reminding

Thanks for the reply.
I am using combination of magic methods (__call, __set/__get) to call "virtual" setters/getters for all declared properties in my entities. So, solution was to define setSibling() / getSibling() methods and remove sibling property declaration.

Thanks for the reply.
I am using combination of magic methods (__call, __set/__get) to call "virtual" setters/getters for all declared properties in my entities. So, solution was to define setSibling() / getSibling() methods and remove sibling property declaration.


Unlinked file fix not available if parent is an inline module?

Add a file in ide_diagnostics/src/handlers/.
Observe the "unlinked file" diagnostic, but no quickfix.

I haven't looked into this in detail, just wanted to record it before I forget.

This is intentionally not working (for now): https://github.com/rust-analyzer/rust-analyzer/blob/97c7321cfa93973df9a9d0f3d9321a6ab5e5d87f/crates/ide_diagnostics/src/handlers/unlinked_file.rs#L74

This works now


fix: npm package browser support

Overview

Updating the npm package build process to account for our browser support list. Also including the src directory in the npm package for power users.
Related Issue(s)

https://issues.newrelic.com/browse/NEWRELIC-7896
Testing

Test workflow should pass

Importing from source has an issue with our usage of process.env.*

Importing from source has an issue with our usage of process.env.*

This can be a future optimization since this may need a bigger change to support shipping the raw source files

That's fine with me. I will need to disable the src tests for right now if you are good with that.

Codecov Report

Merging #453 (b29a716) into main (40168c7) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #453   +/-   ##
=====================================
  Coverage   3.69%   3.69%
=====================================
  Files        120     120
  Lines       3925    3925
  Branches     968     968
=====================================
  Hits         145     145
  Misses      2981    2981
  Partials     799     799

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


redis-stack-server installation failed with redis-stack/redis-stack/redis-stack-server: undefined method `exists?' for class File

brew doctor output
^[[1mPlease note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!^[[0m

Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Settings.

If that doesn't show you any updates, run:
  sudo rm -rf /Library/Developer/CommandLineTools
  sudo xcode-select --install

Alternatively, manually download them from:
  ^[[4mhttps://developer.apple.com/download/all/^[[24m.
You should download the Command Line Tools for Xcode 15.4.

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  consul
  couchdb
  spidermonkey@91
  terraform

Warning: You have the following deprecated, official taps tapped:
  Homebrew/homebrew-cask-versions
Untap them with `brew untap`.

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae and may need to be deleted.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.
[X] I ran brew update twice and am still able to reproduce my issue.

brew config output
HOMEBREW_VERSION: 4.3.5
ORIGIN: https://github.com/Homebrew/brew
HEAD: 3f08c75e7b950d4340dab462f3e7f77e8093fa2b
Last commit: 5 days ago
Core tap JSON: 16 Jun 06:34 UTC
Core cask tap JSON: 16 Jun 06:34 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: nvim
HOMEBREW_MAKE_JOBS: 16
Homebrew Ruby: 3.3.2 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.2/bin/ruby
CPU: 16-core 64-bit arm_palma
Clang: 15.0.0 build 1500
Git: 2.45.2 => /opt/homebrew/bin/git
Curl: 8.6.0 => /usr/bin/curl
macOS: 14.5-arm64
CLT: <IP_ADDRESS>.2.5
Xcode: 15.4
Rosetta 2: false

What were you trying to do (and why)?
brew uninstall redis-stack-server --force
What happened (include all command output)?
brew uninstall redis-stack-server --force
==> Uninstalling Cask redis-stack-server
Error: undefined method exists?' for class File /opt/homebrew/Caskroom/redis-stack-server/.metadata/7.2.0-v10/20240405093707.798/Casks/redis-stack-server.rb:34:in block (3 levels) in load'
/opt/homebrew/Caskroom/redis-stack-server/.metadata/7.2.0-v10/20240405093707.798/Casks/redis-stack-server.rb:32:in each' /opt/homebrew/Caskroom/redis-stack-server/.metadata/7.2.0-v10/20240405093707.798/Casks/redis-stack-server.rb:32:in block (2 levels) in load'
/opt/homebrew/Library/Homebrew/cask/artifact/abstract_flight_block.rb:47:in instance_eval' /opt/homebrew/Library/Homebrew/cask/artifact/abstract_flight_block.rb:47:in abstract_phase'
/opt/homebrew/Library/Homebrew/cask/artifact/abstract_flight_block.rb:30:in uninstall_phase' /opt/homebrew/Library/Homebrew/cask/installer.rb:474:in block in uninstall_artifacts'
/opt/homebrew/Library/Homebrew/cask/artifact_set.rb:10:in each' /opt/homebrew/Library/Homebrew/cask/artifact_set.rb:10:in each'
/opt/homebrew/Library/Homebrew/cask/installer.rb:471:in uninstall_artifacts' /opt/homebrew/Library/Homebrew/cask/installer.rb:409:in uninstall'
/opt/homebrew/Library/Homebrew/cask/uninstall.rb:14:in block in uninstall_casks' /opt/homebrew/Library/Homebrew/cask/uninstall.rb:9:in each'
/opt/homebrew/Library/Homebrew/cask/uninstall.rb:9:in uninstall_casks' /opt/homebrew/Library/Homebrew/cmd/uninstall.rb:73:in run'
/opt/homebrew/Library/Homebrew/brew.rb:92:in `'
Please report this issue:
https://docs.brew.sh/Troubleshooting
What did you expect to happen?
uninstall the redis-stack-server to install the newer version
==> Upgrading 1 outdated package:
redis-stack/redis-stack/redis-stack-server 7.2.0-v10 -> 7.2.0-v11
Step-by-step reproduction instructions (by running brew commands)
brew upgrade redis-stack-server
==> Upgrading 1 outdated package:
redis-stack/redis-stack/redis-stack-server 7.2.0-v10 -> 7.2.0-v11
==> Upgrading redis-stack-server
==> Downloading https://redismodules.s3.amazonaws.com/redis-stack/redis-stack-server-7.2.0-v11.monterey.arm64.zip
Already downloaded: /Users/wernerschafer/Library/Caches/Homebrew/downloads/cbe9e09e832e343aeee6b5a2d88aa8d93b07a72d575bf828512b600c8664621a--redis-stack-server-7.2.0-v11.monterey.arm64.zip
Warning: Cannot verify integrity of 'cbe9e09e832e343aeee6b5a2d88aa8d93b07a72d575bf828512b600c8664621a--redis-stack-server-7.2.0-v11.monterey.arm64.zip'.
No checksum was provided.
For your reference, the checksum is:
  sha256 "3a219a11af1eb96dac3684512abb1e23c588ff9a2dbe0ba4817a7f1e3f88dda2"
All dependencies satisfied.
==> Purging files for version 7.2.0-v11 of Cask redis-stack-server
Error: redis-stack/redis-stack/redis-stack-server: undefined method `exists?' for class File
/opt/homebrew/Caskroom/redis-stack-server/.metadata/7.2.0-v10/20240405093707.798/Casks/redis-stack-server.rb:34:in `block (3 levels) in load'
/opt/homebrew/Caskroom/redis-stack-server/.metadata/7.2.0-v10/20240405093707.798/Casks/redis-stack-server.rb:32:in `each'
/opt/homebrew/Caskroom/redis-stack-server/.metadata/7.2.0-v10/20240405093707.798/Casks/redis-stack-server.rb:32:in `block (2 levels) in load'
/opt/homebrew/Library/Homebrew/cask/artifact/abstract_flight_block.rb:47:in `instance_eval'
/opt/homebrew/Library/Homebrew/cask/artifact/abstract_flight_block.rb:47:in `abstract_phase'
/opt/homebrew/Library/Homebrew/cask/artifact/abstract_flight_block.rb:30:in `uninstall_phase'
/opt/homebrew/Library/Homebrew/cask/installer.rb:474:in `block in uninstall_artifacts'
/opt/homebrew/Library/Homebrew/cask/artifact_set.rb:10:in `each'
/opt/homebrew/Library/Homebrew/cask/artifact_set.rb:10:in `each'
/opt/homebrew/Library/Homebrew/cask/installer.rb:471:in `uninstall_artifacts'
/opt/homebrew/Library/Homebrew/cask/installer.rb:430:in `start_upgrade'
/opt/homebrew/Library/Homebrew/cask/upgrade.rb:195:in `upgrade_cask'
/opt/homebrew/Library/Homebrew/cask/upgrade.rb:113:in `block in upgrade_casks'
/opt/homebrew/Library/Homebrew/cask/upgrade.rb:112:in `each'
/opt/homebrew/Library/Homebrew/cask/upgrade.rb:112:in `upgrade_casks'
/opt/homebrew/Library/Homebrew/cmd/upgrade.rb:260:in `upgrade_outdated_casks'
/opt/homebrew/Library/Homebrew/cmd/upgrade.rb:138:in `run'
/opt/homebrew/Library/Homebrew/brew.rb:92:in `<main>'
Please report this issue:
  https://docs.brew.sh/Troubleshooting

[x]  This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at Homebrew/homebrew-core/issues/new/choose instead.

It does. Please report this to redis-stack/redis-stack instead.


Error running yarn dev-server from command line

General information

Description
Value

Project version
2.3.0

Operating system and version
OS 12.2.1

NodeJS version
14.8.2

NPM version
8.9.0

Yarn version
1.22.17

Truffle version
5.5.13

Describe the bug
Receiving the following error and failing with exit code 1 when trying to run yarn dev-server: Error: listen EADDRINUSE: address already in use <IP_ADDRESS>:8080
How to Reproduce
Steps to reproduce the behavior (please provide a reproducer project for complex bugs):

Run yarn dev-server from terminal while in the /minting-dapp directory

Expected behavior
Command runs successfully as shown in the second screenshot below (pulled from the HashLips youtube tutorial titled "How to create an NFT collection - Masterclass")
Screen

Additional context

Hi @stevenliriano, thank you for your report. The command is actually working fine, that error message means that you already have a background service listening on port 8080 so the dev server can't bind to it. You can either stop the other service (highly recommended) or use custom port with yarn dev-server --port 8081 (or any other port number).
Let me know if that solves the issue.

@stevenliriano it should be an HTTP service so you may browse http://<IP_ADDRESS>:8080, that might help understanding what it actually is. I don't have any better solution to be honest.
I'm gonna close this but let me know if it works 😉

@stevenliriano The IPFS daemon is supposed to spawn a web interface on that port so it will be up as long as you keep it running. It's important to know what is using that port (sometimes you run the dev-server twice and you are not aware of it), but if you are using that service, then there is no need to kill it.
In your case I think it's fine to simply use another port for the dev-server.

 ;)


detect-adaptive

This means we need to use content-aware detecton mode (`detect-content`) or adaptive mode (`detect-adaptive`)

there is doc about adaptive mode,but the latest code seems still not support that yet ?

This is a detector that is slated for a future release and it seems as though a reference snuck into the docs a bit early. If you want to try out the detector, it is live on the 0.5.6 branch. You can see the code for the detector here.


pico_bootsel_via_double_reset doesn't work on RP2350

Overview
There is a small module that can be linked into an application to allow a quick double-reset to restart into UF2 loader mode.  On the RP2040 this works as long as you simply include target_link_libraries(... pico_bootsel_via_double_reset ...) as it runs as part of the C++ constructor sequence.
Unfortunately, while this compiles and runs on the RP2350 (-DPICO_PLATFORM=rp2350) it doesn't function properly.
Debugging
On inspection, it seems like the magic numbers that are written to SRAM are actually overwritten by the Pico2 bootrom processing (with what looks to me to be repeatable, pseudo-random data) so that it can never actually match by the time the main app starts up and calls the C++ (constructor) that handles this.
I've increased the wait time via the define, but it's not related to this (i.e. it's not being reset too quick or slow).
When I did some snooping, it seems like main SRAM and the two 4K stack SRAMs are a) 0-filled after a UF2 upload, but b) pseudo-random filled after a HW (!RUN ) reset on the Pico2-ARM mode.
Maybe this is part of the secure booting process?  If so, is there some RAM that's not wiped and not used during start up that we can stuff those magic values in?
Steps to reproduce
In pico-examples, update the basic blink_simple CMakefile.txt
earle@amd:~/src/pico-examples/blink_simple$ git diff .
diff --git a/blink_simple/CMakeLists.txt b/blink_simple/CMakeLists.txt
index 0d7c0cb..32e897b 100644
--- a/blink_simple/CMakeLists.txt
+++ b/blink_simple/CMakeLists.txt
@@ -3,7 +3,7 @@ add_executable(blink_simple
 )

 # pull in common dependencies
-target_link_libraries(blink_simple pico_stdlib)
+target_link_libraries(blink_simple pico_stdlib pico_bootsel_via_double_reset)

 # create map/bin/hex/uf2 file etc.
 pico_add_extra_outputs(blink_simple)

And build with -DPICO_PLATFORM=rp2350.  Building the same for RP2040 works perfectly.

Ah, RP2350 has this support in the bootrom, but you have to enable it via:
// -----------------------------------------------------------------------------
// Field       : OTP_DATA_BOOT_FLAGS1_DOUBLE_TAP
// Description : Enable entering BOOTSEL mode via double-tap of the RUN/RSTn
//               pin. Adds a significant delay to boot time, as configured by
//               DOUBLE_TAP_DELAY.
//
//               This functions by waiting at startup (i.e. following a reset)
//               to see if a second reset is applied soon afterward. The second
//               reset is detected by the bootrom with help of the
//               POWMAN_CHIP_RESET_DOUBLE_TAP flag, which is not reset by the
//               external reset pin, and the bootrom enters BOOTSEL mode
//               (NSBOOT) to await further instruction over USB or UART.

As you suspected, RAM is zeroed in the boot path.
We likely forgoot about ramifications on this library. We should either make clear this library functionality is disabled on RP2350; or implement it differently for RP2350 (if having non OTP chosen way is useful which it might be). Thoughts @Wren6991

Might also want to remove the uninitialized_data section in the RP2350 linker files, too, since they're gonna be overwritten by the ROM.

Ah, the problem is more fundamental than that: asserting the RUN pin powers down the memories, and they power back up when it's released.
This is specific to double-tap, and I'm not sure there is actually any issue with uninitialized_data.

merged into develop


New version: VMware.WorkstationPro version 17.0.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@stephengillie - another one for you bud, same as the previous versions...


Added verification options and use only binaries for claims

This adds the skip claims option during verifying. I was struggling with the default parameters in Elixir but managed to get it straight without needing to refactor a lot of test code.
Our verify function now accepts 4 parameters: token, signer, module for struct decoding and a list of options. Currently only skip_claims is accepted or checked. I think we should merge the module for decoding into the list of options but that is for another PR/issue.
So right now we have:
some_token
|> verify(hs256("test"), MyStruct, skip_claims: ["name"])

Or:
some_token
|> verify(hs256("test"), nil, skip_claims: ["name"])

If we merge module back to the options list we would have:
some_token
|> verify(hs256("test"), [as: MyStruct, skip_claims: ["name"]])

Or:
some_token
|> verify(hs256("test"), [skip_claims: ["name"]])

Besides that, I stumbled upon an issue. The following code:
token
|> with_claims(%TestStruct{a: 1, b: 2, c: 3})
|> with_validation(:a, &(&1 == 666))
|> sign(hs256("test"))
|> verify(hs256("test"))

Was not producing an error on verification. This is because I used an atom for adding the validation and we were not converting it back to string for indexing the map. This PR forces people to use binaries as keys for claims and validations so that we don't need to worry about that (I guess this is more performatic than makeing the conversion all the time). Sorry about mixing this in this same commit but I got carried away...
I refactored our test code in that matter and everything passes. Also, nothing here seems to impact on performance.
Should fix #66.

I really like adding the as option for the module decoding! I definitely think we should do that. Like you said, that can be another PR.


There are many duplicate instance names in aletsch result file

Hi,
There are many duplicate instance id in the results file, is there a way to avoid?
dup.instance.zip
Best,
Kun

Hi, we are doing some work looking for denovo transcripts and we are facing this issue again.
Roughly 0.5% of transcripts ids seem to have the same (duplicated) instances. This happens with exactly two instances per "duplicated instance"
Any idea on what might be causing it and potential solutions?
Thank you!

Hi, we are doing some work looking for denovo transcripts and we are facing this issue again.
Roughly 0.5% of  transcripts ids seem to have the same (duplicated) instances. This happens with exactly two instances per "duplicated instance"
Any idea on what might be causing it and potential solutions?
Thank you!

Thank you for bringing this problem to our attention and we also notice this recently, which is due to output transcript from different strands sharing the same instance name. We have fixed this is the latest v1.1.3 version. If the same problem persists in this latest version, feel free to let up know.


broken link?

[Enter feedback here]
It seems the metric-collector-module link in Note#2 (marked below) is broken

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

ID: b6f53323-f01c-5eb0-6f98-c0c8914bd610
Version Independent ID: b3e85483-faaf-22d2-e72c-1e2fb3ba0066
Content: Collect and transport metrics - Azure IoT Edge
Content Source: articles/iot-edge/how-to-collect-and-transport-metrics.md
Service: iot-edge
GitHub Login: @veyalla
Microsoft Alias: veyalla

@cristipogacean Thanks for the feedback! We are currently investigating and will update you shortly.

@cristipogacean PR has been created to fix this issue. Changes will go live once it has been reviewed and merged.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


evidence used in manual assertion

Please could we have 'evidence used in manual assertion' variants for the following terms:

immunofluorescence wide-field microscopy evidence  ECO:0005599
wide-field fluorescence microscopy evidence ECO:0005598
over expression analysis evidence ECO:0000120
cell-free assay evidence ECO:0000183
in vitro cell based assay evidence ECO:0005014

Thanks!

These terms have been added in, please let me know if you need anything else @dosumis


Does the dataset provide RGB images corresponding to the scene? and another question , does Stereo Image and StereoPattern Image means Gray Scale Image？

Hello, for Ensenso dataset, we provide gray scale for both stereoPattern and Stereo. For realsense, we provide RGB for monocular and gray scale for stereoPattern.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75000

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86230

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117117


Libuvc - add support for options XU/PU

adding support for XU/PU options

Can one of the admins verify this patch?

Since #829  if merged, I've restarted the Travis for this PR

The latest Travis error is different, if fails at configurre phase of glfw.
CMake Error at /usr/local/cmake-3.9.2/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message):

  Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY OPENGL_INCLUDE_DIR)

Call Stack (most recent call first):

  /usr/local/cmake-3.9.2/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:377 (_FPHSA_FAILURE_MESSAGE)

  /usr/local/cmake-3.9.2/share/cmake-3.9/Modules/FindOpenGL.cmake:170 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)

  CMakeLists.txt:88 (find_package)

@dorodnic any thoughts?

The opengl issue was fixed by #838 . @EladZucker could you push a update so that the Travis can retigger based on lastest development branch?


Feature/sreekanth

@srmanthena83 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

approved pr


New magic-string 0.25.7 makes two tests fail in buble

Hi,
I wanted to update Debian's package for magic string to version 0.25.7, but didn't upload the result yet because it turns out it breaks two tests in buble.
I'm attaching the relevant problems.
buble_with_magic_string_0.25.7.txt

A number of bug fixes and memory efficiency improvements were made in magic-string. The new buble test results with<EMAIL_ADDRESS>provide more accurate higher precision source maps.
Both the failing tests you listed use the same input:
const answer = () => 42;

and produce the same output:
var answer = function () { return 42; };

and same final source map. The only difference is that one test produces an inline source map, and the other an external source map file.
You can see the source map improvement by comparing the original test result for /test/cli/creates-inline-sourcemap versus the new test result. You will notice that the new sourcemap has an extra mapping 25->1:18 from => to { return. Hover your mouse over each token in the source map visualizer to study it.
Just create a new PR to update the expected buble test results with the actuals. It would be nice if a new Buble release could be made since there appears to be other unpublished committed changes since the last release.

@kzc see https://github.com/bublejs/buble/issues/241 — I would like to release a new version but make it v1.0, dropping old Node and upgrading all dependencies — does this sound good? We could do a bump release but there's no way to verify if it works on old Node versions/deps because master builds already fail on them for whatever reason.

@mourner I'm not sure deprecating old Node versions is a good idea. It defeats the point of the project, doesn't it? I just did a clean git clone of buble from latest master, ran yarn, updated the expecteds with the actuals for the 2 failing sourcemap tests and it ran all the mocha tests successfully on Node 4 and 6. Yes, running yarn (or npm install) generates a lot of deprecation warnings, but it still works. I think doing a bump release is the way to go.

@kzc the test262 tests are failing on CI though. Deprecating old Node is a good idea because the point of the project is to support legacy browsers like IE11 first and foremost; old Node versions shouldn't be run anywhere at all since they are not maintained even for critical security issues, and supporting them puts a huge burden on maintenance of this project, as discussed in the linked tickets.

@mourner It's your call. I just assumed that the commits that occurred after the last release were vetted in some way - at the very least included new passing tests. It would be a shame not to release those fixes.
npm test runs fine. I didn't check the test262 results because I assumed that Buble is far from compliant.
Regarding maintenance burden, I thought this was a defunct project - no new features. Updating the test results to for the latest version of magic-string is just a minor thing.

@kzc perhaps you're right — I just went through deps in #250 and it seems like at least direct dependencies weren't updated to versions incompatible with old Node, so we can do a minor bump at least (v0.20.0).

Landed in master

@mourner Do you plan to make a new release?
The last one was '0.19.8': '2019-07-03T08:59:31.653Z'.

@kzc yes, after merging a few PRs that were stuck unmerged because of the failing CI on older Node versions.

Released v0.20.0. https://github.com/bublejs/buble/blob/master/CHANGELOG.md#0200-2020-03-26

Thanks @mourner.
fwiw, I can confirm once buble 0.20.0 is built with Node v12 from sources that the mocha tests run successfully with Node v4 and v6 if the older versions of mocha and rimraf are used:
    "mocha": "^5.2.0",
    "rimraf": "^2.6.3",

$ bin/buble -v
Bublé version 0.20.0

$ node-v4.2.1 node_modules/.bin/mocha test/test.js && echo success
...
  539 passing (2s)
  2 pending

success

$ node-v6.9.0 node_modules/.bin/mocha test/test.js && echo success
...
  539 passing (2s)
  2 pending

success

Of course going forward that may not be the case.


Replace Instantiate with Initiate

I don't believe Instantiate is the correct intended verb in this scenario.   Updated with Initiate which reads more correctly

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@Sirkkuw - PR has been copy edited and is ready for final review.
Thank you.

@mypil I merged this.


Bug on command "new"

Thanks for finding this and fixing it, the DEV branch will go unstable some time later :stuck_out_tongue:


Fix goreleaser job

Description
Updated the Github Workflow for the release job by providing the workdir argument which is now pointing to the correct folder, which is required as the main function is not located in the root folder as expected by default. Reference: https://github.com/goreleaser/goreleaser-action#customizing
closes: #310

Merge conflicts

Just resolved them @adlerjohn


Improve organization user ID and username resolving logics.

Describe the issue:
The federated users from the organization SSO flow is more towards local user handling rather treating as federated user. Hence improve the codebase to handle the user resolving logics in a proper way.

https://github.com/wso2/carbon-identity-framework/pull/5756

Testing effort.
There are two type of token revocation triggering events can be occurred.

From an actions done from root org level.
From an actions done from the organization itself.

From an actions done from root org level.

[ ] Deactivate the organization.
Switched tokens get revoked.  Direct SSO admin user tokens get revoked.
[ ] Unshare the b2b app.
The token against that org and the federated token get revoked.

From an actions done from the organization itself.

[ ] Remove a role from the organization user
The token against that org get revoked.

[ ] Delete the organization user.
The token against that org and the federated token get revoked.


Reference package instead of referencing Dll files

The generated project reference dll files and it's supposed to reference the nuget package
so instead of any dll file  which is defined in HintPath:
<ItemGroup>
    <Reference Include="Autofac, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=17863af14b0044da, processorArchitecture=MSIL">
      <HintPath>..\..\..\packages\Autofac.4.2.1\lib\net45\Autofac.dll</HintPath>
      <Private>True</Private>
    </Reference>
    <Reference Include="System.Data.DataSetExtensions" />
    <Reference Include="Microsoft.CSharp" />
    <Reference Include="System.Net.Http" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\..\Autofac.Extras.Plugins\Autofac.Extras.Plugins.csproj" />
  </ItemGroup>

It should be:
<ItemGroup>
  <PackageReference Include="Autofac" Version="4.2.1" />
  <PackageReference Include="Autofac.Extras.Plugins" Version="1.0.0" />
</ItemGroup>

These packages are defined in the file: Packages.config.
Also, these Assemblies are reference by default in the project, so no need to reference it:
System
System.Core
System.Data
System.Drawing
System.Io.Compression.FileSystem
System.Numerics
System.RunTime.Serialization
System.Xml
System.Xml.Linq

@moh-hassan thank you for your report. If I understood you correctly, both of these features are already implemented in this tool. Are they not working correctly? If so, could you please provide the case for us to reproduce the issue?

Thanks @andrew-boyarshin  for reply.
Here the project in the attached file including .csproj and Packages.config

When I run the tool on the your test case, I get the following csproj:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <ProjectGuid>{7238CC8F-C533-4DF5-8770-5D9EF82D91A9}</ProjectGuid>
    <TargetFramework>net462</TargetFramework>
    <AssemblyTitle>CommonComponents</AssemblyTitle>
    <Product>CommonComponents</Product>
    <Copyright>Copyright ©  2016</Copyright>
    <OutputPath>bin\$(Configuration)\</OutputPath>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <DebugType>full</DebugType>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <DebugType>pdbonly</DebugType>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Autofac" Version="4.2.1" />
  </ItemGroup>
  <ItemGroup>
    <Reference Include="Autofac, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=17863af14b0044da, processorArchitecture=MSIL">
      <HintPath>..\..\..\packages\Autofac.4.2.1\lib\net45\Autofac.dll</HintPath>
      <Private>True</Private>
    </Reference>
    <Reference Include="System.Data.DataSetExtensions" />
    <Reference Include="Microsoft.CSharp" />
    <Reference Include="System.Net.Http" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\..\Autofac.Extras.Plugins\Autofac.Extras.Plugins.csproj" />
  </ItemGroup>
</Project>

The only issue I see here is Autofac assembly being referenced twice: once properly (as PackageReference), and once (as Reference) erroneously. I'll look into it.
Do you expect more to be removed? The rest of References are not safe to remove.

After a short investigation I consider the Autofac behavior correct. HintPath does point at the path outside the project tree. The tool plays it safe. But maybe we should provide the user (of a wizard) the ability to handle these cases manually (like a prompt with a candidate for removal).

I created this feature and it is supposed to look in your NuGet settings (i.e. nuget.config) to check that the packages folder is the one that you have configured for the solution. If the two match, then it will remove the HintPath as it can be pretty sure that it was managed by NuGet previously.
I haven't checked recently to make sure that it is still working as the newer versions of this migrator seem to have a couple of issues in this area and I ended up using the VS tool to migrate to PackageReference prior to doing a migration with this tool.
Sorry, that's a bit vague, but if you are able to check if your NuGet settings align with the HintPath, then we can establish for sure if it is a bug. There was a unit test for it I believe so perhaps it is still working as originally intended.
I've not got much time to look at this at the mo.

@mungojam
The new style SDK projects (2017+) are using PackageReference and I think migration should insure converting package.config and drop any dll file (has hint path file) and  have a corresponding package in package.config.

@andrew-boyarshin
Have a look to the hintPath:
<HintPath>..\..\..\packages\Autofac.4.2.1\lib\net45\Autofac.dll</HintPath>

The HintPath Point to folder in the format:
packages\<packagename>.<version>\lib\FFW\<dll filename>

which insure that it's a package.
In that case it's better to use packageReference than File Reference via HintPath.
Also that package is included in package.config.

The new style SDK projects (2017+) are using PackageReference and I think migration should insure converting package.config and drop any dll file (has hint path file) and have a corresponding package in package.config.

It does this, but only if the NuGet package location the HintPath matches either:

The setting from a nuget.config (either global or in the path hierarchy above the project).

or

The automatic convention of having a packages folder alongside the solution. I think for this to work, you need to tell the migrator to migrate the solution file rather than the project file.

I've restructured your example's folder structure and added a nuget.config to demonstrate that it works for case 1 when run with dotnet migrate-2019 wizard.
CommonComponentsWithNugetConfig.zip
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <ProjectGuid>{7238CC8F-C533-4DF5-8770-5D9EF82D91A9}</ProjectGuid>
    <TargetFramework>net462</TargetFramework>
    <AssemblyTitle>CommonComponents</AssemblyTitle>
    <Product>CommonComponents</Product>
    <Copyright>Copyright ©  2016</Copyright>
    <OutputPath>bin\$(Configuration)\</OutputPath>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <DebugType>full</DebugType>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <DebugType>pdbonly</DebugType>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Autofac" Version="4.2.1" />
  </ItemGroup>
  <ItemGroup>
    <Reference Include="System.Data.DataSetExtensions" />
    <Reference Include="Microsoft.CSharp" />
    <Reference Include="System.Net.Http" />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\..\Autofac.Extras.Plugins\Autofac.Extras.Plugins.csproj" />
  </ItemGroup>
</Project>

@moh-hassan. I meant to ask, which case are you relying on for the packages to work prior to the migration? 1 or 2

@mungojam
Neither 1 nor 2
I used the wizard for a project in the folder without nuget.config.
It seem that nuget.config  is needed.
It's nice if wiki documentation describe the valid ideal environment to run the wizard and the importance of nuget.config.

If NuGet.config file is not found, heuristics are used. If a project is part of the solution, packages directory is an immediate child of solution folder. Otherwise, it is the one adjacent to the project folder. The heuristics are sound, even if not overly sophisticated. In your example, the tool correctly follows the heuristics and decides the HintPath does not point to a valid NuGet package cache folder.
A good idea would be to implement additional stage in migration wizard to provide means to force the conversion to PackageReference when the heuristics decided HintPath to be invalid, but it still contains packages/$(Id).$(Version)/ pattern. Since this is a potentially breaking migration, it should be opt-in, not opt-out. In my opinion, this issue should be considered a feature request, not a bug report.

this issue should be considered a feature request, not a bug report

@andrew-boyarshin
You are correct. It should be a feature request.
Some consideration may be taken into account:

The project may move from one machine to another and  NuGet.config file may not be exist or invalid.
The  package directory may be deleted when zipping the project and it shouldn't be considered.

An option in commandline to ignore/use  package directory / or NuGet.config is good.


RTX-KG2 appearing twice

In prod kp-registry, there are entries for both prod and dev RTX-KG2.  I checked the smartapi registrations, and both make use of the infores tag with the same value.  So kp-registry should be using only the prod version.

This was by design. The kp-registry will store both maturities, and then it is up to the service requesting kps to specify which maturity level it wants. (Could be a list of maturities in priority order and the best one will be returned).

Oh, I get it.   Thanks for clarifying.


What's new with uvwasi in 2023

Tracking issue in support of https://github.com/nodejs/node/blob/main/doc/contributing/sharing-project-news.md

Minutes from the meeting:
Node.js  uvwasi team Meeting 2023-04-12
Links

Recording:  https://www.youtube.com/watch?v=mvWyuipOHuM
GitHub Issue: https://github.com/nodejs/uvwasi/issues/197

Present

Michael Dawson (@mhdawson)
Pat Hickey (@pchickey)
Colin Ihrig (@cjihrig)
Blaine Bublitz (@phated)
Guy Bedford

Agenda
Announcements
*Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

WASI preview 1: fd_readdir ignores cookie argument #47193

Colin had a look, was able to confirm issue on M1.
Next step is to look at how to fix.

nodejs/uvwasi

uvwasi team working tasks #187

short discussion, no major updates
Michael will break out remaining tasks into their own issues

Michael asked about creating a “what’s new in uvwasi issue” to support effort described in https://github.com/nodejs/node/blob/main/doc/contributing/sharing-project-news.md.

General agreement to do so, Michael volunteered to create issue

Q&A, Other
Upcoming Meetings

Node.js Project Calendar: https://nodejs.org/calendar

Click +GoogleCalendar at the bottom right to add to your own Google calendar.

@mhdawson I believe the notes were posted to the wrong issue and this was closed mistakenly.

@phated thanks fixing

Two new versions of uvwasi

v0.0.17 - Return correct length of string in fd_prestat_get
v0.0.18 - Define S_ISFIFO macro to support new versions of libuv

Node.js main branch updated to include v0.0.18 version os uvwasi

v0.0.19 was released which includes an initial implementation of the WASI preview 1 socket methods including https://github.com/WebAssembly/WASI/blob/main/legacy/preview1/docs.md#-sock_acceptfd-fd-flags-fdflags---resultfd-errno. The next step is to expose these in the Node.js WASI implementation.

Node.js main branch updated to include v0.0.20 version of uvwasi which includes some important changes to handling of relative paths - https://github.com/nodejs/node/pull/51355