[UI] Follow capitalization of user variables in the input field names

Current Behavior
Seen in post (dev) epinio-v1.7.1
Currently first letter of the input field name is always capital, like Appliseningport, Myannotationenum ...

But in the used AppChart resource the variables have camelCase format.
  settings:
    appListeningPort:
      type: 'integer'
    myAnnotationString:
      type: string
    myAnnotationEnum:
      type: string
      enum:
        - "first"
        - "second"
        - "third"
    myAnnotationInteger:
      type: integer
      minimum: '1024'
      maximum: '2048'
    myAnnotationNumber:
      type: number
      minimum: '1'
      maximum: '2'
    myAnnotationBool:
      type: bool

Expected Behavior
It would be great if the letters in the variable name would be the same as defined in AppChart resource.

The title case transform done by the UI may cause issues when were are settings which only differ in casing and are mapped to the same value after the transform:

Foo, foo, fOO all become Foo in the UI.

It would IMHO be best to not apply this transform.

Verified fixed, thanks.


Finetune code question (because a lot of parts are commented out....)

Hello,
First thank you for this work.
I'm trying to follow the training procedure you described on movienet dataset. I'm able to do pretraining, but I'm not able to do the finetuning because may parts are commented out and I'm not sure what to uncomment/change to do finetuning.
In finetune/main.py, the training part is commented out, so I assume I need to uncomment these to start training.
https://github.com/md-mohaiminul/TranS4mer/blob/98de379770e0d4034280abb9923928c103377286/trans4mer/finetune/main.py#L50-L64
for the finetune script itself, if I run it as it is.. the finetune code will ask for shot representation.  So I assume that I need to run the first part extract_shot_repr.py first..
https://github.com/md-mohaiminul/TranS4mer/blob/98de379770e0d4034280abb9923928c103377286/scripts/run_finetune.sh#L8-L12
In extract_shot_repr.py,   there are bunch of things that are commented out, I'm not sure what is relevant..
https://github.com/md-mohaiminul/TranS4mer/blob/98de379770e0d4034280abb9923928c103377286/trans4mer/pretrain/extract_shot_repr.py#L28-L46
I can see that you are doing experiments including other modalities, I don't know what to uncomment, or if I need to uncomment any.
I would appreciate if you can clarify on how to perform finetuning.
Thank you

Hello,
I've been able to perform finetuning. However I'm unable to obtain the replicate the same performance. The AP recorded in paper is 60.78,  I obtain only around 58.8
I adjusted the pretraining hyperparameters to match the ones you have in your paper:

25 shots
pretrain for 20 epochs

At fine tuning, I follow the same procedure as BASSL to first generate the shot level features, then train the rest part of model using the features.
I wonder if that's causing the problem.

Thanks


libcxxrt: add static lib to output

Description of changes
allow static linking libc++. libcxxrt.a is 220K when build for x64 linux, 198K x64 freebsd
tested with https://github.com/NixOS/nixpkgs/pull/305876

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg eval
wtf


GeoIP Lookup function

Use case: It would be really useful to be able to have a generated object with geolocation info automatically created when IP addresses are inserted into an IP field.
Feature description:
It would be really cool if Crate could integrate the MaxMind GeoIP client with a way to update client databases without having to restart the entire Crate cluster. This is a pretty standard GeoIP database format that multiple vendors use. There are free databases available for users to download.
Example use case:
CREATE TABLE uri_table (
   ip_addr IP,
   geoip_obj OBJECT GENERATED ALWAYS AS geoip_lookup("ip_addr")
);

SELECT geoip_lookup('<IP_ADDRESS>') as geo;
+--------------------------------------------------------------------------------+
| geo                                                                            |
+--------------------------------------------------------------------------------+
| {"continent": "North America", "country": "United States", "city": "Cambridge",|
| "state": "Massachusetts", "postal": "02139"}                                   |
+--------------------------------------------------------------------------------+

Maybe it's worth having options for which fields you want included in the response. (Example: include or exclude lat / lon co-ordinates, ISP name, Organization name, etc)

Doing a network lookup to the GeoIP2 (or GeoLite2) on every single written row could dramatically decrease performance.
Also possible errors like timeout's, disconnects etc. must be handle safely.
A more performant and error-safe way would be to import the desired GeoIP database as described here and using a JOIN to resolve the ip_addr field.
In contrast to the schema described in this guide, the network column should be of type text in order to use our << operator, see also our documentation of the IP data type https://crate.io/docs/crate/reference/en/5.0/general/ddl/data-types.html#ip-addresses.
Example query:
SELECT * FROM uri_table, geoip2_network WHERE uri_table.ip  << geoip2_network.network;

Can you please add a reasoning why a dynamic IP resolving during writes would be a better option for your use-case?

@seut This is not doing a network lookup, it's using a local file that memory mapped.

Doing a network lookup to the GeoIP2 (or GeoLite2) on every single written row could dramatically decrease performance. Also possible errors like timeout's, disconnects etc. must be handle safely.

The idea is to not use the webservice. MaxMind has a downloadable database that you can perform lookups with. Multiple geolocation companies use this database format.
https://github.com/maxmind/GeoIP2-java#database-usage

The idea is to not use the webservice. MaxMind has a downloadable database that you can perform lookups with. Multiple geolocation companies use this database format.
https://github.com/maxmind/GeoIP2-java#database-usage

Thanks for this clarification. Even that some of their databases are free to use by end-users, their usage is licensed under a proprietary license which, as far as I know, does not allow redistribution. For redistribution one would have to obtain a commercial redistribution license.
I could imagine to provide a geoip_lookup scalar by implementing a dedicated, possible 3rd party plugin for CrateDB, which doesn't include the related databases but adds support for using a custom downloaded one. CrateDB includes a ExtraFunctions extension/plugin one can use as a blueprint to implement a scalar plugin.
I'm still interested in the benefit over importing the related database into CrateDB, would be great if you could describe it.


[WIP]FIxed alter compaction and load issue

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2826/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2827/

@kumarvishal09 what's the purpose of this ps?

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11087/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3059/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2830/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11090/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3061/

LGTM


System.ArgumentNullException during debugging via Visual Studio

I understand that the Visual Studio debugging experience is still being worked on, but I want to report this issue in case it isn't a known issue.
The following issue happens even when I uncomment the Debugger.Launch() statement. The same project works as expected when starting from command line or VS Code.
Am using the sample code provided in this GitHub repo, as-is. Am hitting a System.ArgumentNullException during host startup issue that only happens in Visual Studio when running the following part of the sample code:
https://github.com/Azure/azure-functions-dotnet-worker-preview/blob/main/FunctionApp/Program.cs#L22-L25
This issue can be consistently reproduced even on a fresh new Windows machine with the following software installed:
Visual Studio 2019: version 16.8.3
Microsoft.NET SDK 5.0.100 x64
Azure Functions Core Tools 3.0.3160 (x64)
Here is the full stack trace of the exception:
System.ArgumentNullException
HResult=0x80004003
Message=Value cannot be null. (Parameter 'value')
Source=Google.Protobuf
StackTrace:
at Google.Protobuf.ProtoPreconditions.CheckNotNull[T](T value, String name)
at Microsoft.Azure.WebJobs.Script.Grpc.Messages.StartStream.set_WorkerId(String value) in D:\a\1\s\src\DotNetWorker\obj\Release\net5.0\FunctionRpc.cs:line 1414
at Microsoft.Azure.Functions.Worker.WorkerHostedService.d__9.MoveNext() in D:\a\1\s\src\DotNetWorker\WorkerHostedService.cs:line 48
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.Azure.Functions.Worker.WorkerHostedService.d__7.MoveNext() in D:\a\1\s\src\DotNetWorker\WorkerHostedService.cs:line 37
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.Extensions.Hosting.Internal.Host.d__9.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.d__4.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at FunctionApp.Program.d__0.MoveNext() in C:\temp\FunctionsNet5\FunctionApp\Program.cs:line 32

I fixed this issue by changing this
            var host = new HostBuilder()                 .ConfigureAppConfiguration(c => {})                 .ConfigureFunctionsWorker((c, b) =>                 {                     b.UseFunctionExecutionMiddleware();                 })                 .Build();
To this
            var host = new HostBuilder()                 .ConfigureAppConfiguration(c => {                     c.AddCommandLine(args);                 })                 .ConfigureFunctionsWorker((c, b) =>                 {                     b.UseFunctionExecutionMiddleware();                 })                 .Build();
Didnt really dig into why, hope it helps

I am already using the ConfigureAppConfiguration(c =>{c.AddCommandLine(args);}) lines (it was already part of this github repo when I downloaded the code), but am hitting the described issue in Visual Studio all the same, but thanks for your reply.

I have this same issue, first I created a new project and followed the readme. Then I started hitting this issue. So I thought perhaps I did something wrong, cloned the project, tried to launch that as well and....

The "fix" mentioned by @Spaceman1861 did not work for me, no matter what combo of configure I did or didn't use.

I have this same issue, first I created a new project and followed the readme. Then I started hitting this issue. So I thought perhaps I did something wrong, cloned the project, tried to launch that as well and....

The "fix" mentioned by @Spaceman1861 did not work for me, no matter what combo of configure I did or didn't use.

Solved:
You can not debug the application directly using Visual Studio.
You can only start by using the command line func host start. If you do not, Visual Studio will try to debug the application directly instead of serving it using an out-of-process host that starts it.
I think this issue can be closed as @gabesmsft and me not understanding / reading the readme good enough.

Solved:
You can not debug the application directly using Visual Studio.
You can only start by using the command line func host start. If you do not, Visual Studio will try to debug the application directly instead of serving it using an out-of-process host that starts it.
I think this issue can be closed as @gabesmsft and me not understanding / reading the readme good enough.


Remove version: OpenJS.NodeJS.LTS version 14.17.1

Replaced by another Pull Request
Microsoft Reviewers: Open in CodeFlow

https://www.github.com/microsoft/winget-pkgs/pull/143386#issuecomment-1986949152 [Policy] Needs-Author-Feedback

Close with reason: See discussion in above linked issue;


New Policy with Frozen CLIP encoder

Policy Code
Config file
Here is the policy with only Pretrained CLIP visual encoder taking input only RGB and Depth image. The output from the visual encoder is tensor of size [4*2048]

What was the issue here ?


Font Awesome 4.2 breaks bower

"fontawesome": ">= 3.0.0",

Nope.

@steveathon this can also be closed per the latest merged PR

Thanks for the fix Tyler!

No problem. I'm glad I could help.


Add your own bots

Is there a way to add our own bots and then add more variables like OWNERID etc

i think so

How??


Removing empty attribute parentheses and Attribute suffix

Folks usually leave out the parentheses when there are no positional or named arguments:
-[Shouldly.ShouldlyMethodsAttribute()]
+[Shouldly.ShouldlyMethodsAttribute]

It's not common to see Attribute spelled out either and to me it feels noisy:
-[Shouldly.ShouldlyMethodsAttribute]
+[Shouldly.ShouldlyMethods]

What do you think?

On the fence about cosmetics because it can open a can of worm until we argue about preferred placing of braces. I see low value but I'm willing to hear your arguments

Readability?

Readability is the only thing for me. I agree that it's a small thing. Every little bit does help when attributes are placed on parameters though.

Remove the parens for now
https://github.com/ApiApprover/ApiApprover/pull/118 in a PR


fix: Handle case when SelectedItem is not of type TabBarItem

closes https://github.com/unoplatform/uno.toolkit.ui/issues/515

@Mergifyio backport release/stable/2.5


support nested while task

Codecov Report
Attention: Patch coverage is 92.98246% with 4 lines in your changes missing coverage. Please review.

Project coverage is 75.79%. Comparing base (5937b88) to head (c99687f).
Report is 19 commits behind head on main.

Files
Patch %
Lines

aiida_workgraph/engine/workgraph.py
82.60%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #219      +/-   ##
==========================================
+ Coverage   75.75%   75.79%   +0.04%
==========================================
  Files          70       69       -1
  Lines        4615     4739     +124
==========================================
+ Hits         3496     3592      +96
- Misses       1119     1147      +28

Flag
Coverage Δ

python-3.11
75.79% <92.98%> (+0.13%)
:arrow_up:

python-3.9
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[BUG] pre@class="chroma" breaks dark theme

I have checked all the prerequisites below and I'm yet experiencing a problem

[x] Read the README.md
[x] Have the extended version of Hugo installed
[x] Used the exampleSite's config.toml as a reference

Describe the bug
When I use blockquotes in markdown, the blockquote is properly displayed on the page but I am forced back in the light theme and it's not possible to change this. It also breaks some other parts of the page, such as parts of the left navbar.
Desktop (please complete the following information):

OS: Linux
Browser: Firefox nightly 111.0a1

@Ppjet6, that's by design.

If you want to adjust the chroma classes, you're out of luck with this theme.

Is it by design that blockquotes break the theme?

Umh, is that the same issue or a separate issue?

It's the same issue. It's the html that gets generated when I use blockquotes, as mentioned in the first post.

It seems I misunderstood and misspoke. That said, I still don't get what pre@class="chroma" in the title has to do with a blockquote.
Did a quick test and couldn't quite reproduce what you've described. Can you paste an example here? or send me a link

https://codeberg.org/joinjabber/website-hugo/commit/3874c788bd7849d6b9f6ae93710265af9e254720
This is an example of a workaround for this issue. I guess you can clone the website to try and reproduce.

By all means. You didn't provide an actual example where the problem was happening. I see no blockquotes on the link, or how the chroma class is relevant.

Something on our website currently breaks block-quotes. I have a suspicion that it might be related to adding the custom.js as explained here: https://docs.neuralvibes.com/docs/compose/customize/#i-want-to-add-custom-sass-or-js

Yeah it seems whatever generates <pre class="chroma"> breaks our theme currently. That's at least blockquotes and code blocks.

Or maybe you have different markup settings . If that's the case, that would explain it.

The markup settings should match 👇🏼 as is in the exampleSite.
codeFences = true
  guessSyntax = false
  hl_Lines = ""
  lineNoStart = 1
  lineNos = true
  lineNumbersInTable = false
  noClasses = false
  style = "monokai"
  tabWidth = 2

Ok it looks like this is unrelated to chroma anyway. I tried removing the only place in your code that adds it to <pre> and it didn't fix it.
We use the default configuration so this isn't it either.
It's probably something in our custom sass that breaks it as @poVoq said. We need to figure out what.

For me, this only happens when I use a code block, so 3x tilde like
this

It has nothing to do with custom SASS (I removed it all when testing).

@Ppjet6 has linked to it twice here, but it's https://codeberg.org/joinjabber/website-hugo/
There is no code block added to main branch right now because of the issue, but just add it yourself and you'll see it.

@ltGuillaume, thank you that clarification went a long way. It wasn't immediately obvious that was the fork. Plus the talk about blockquotes didn't help with the confusion. This issue was about the code blocks/snippets breaking certain javascript functions.
I have tested with your repo and discovered a javascript bug. Your repo should now work properly 👇🏼, after pulling the update.

Thanks! This indeed fixes it.
To explain why the baseUrl = "/" if it isn't obvious, we're serving the website over multiple domains, joinjabber.org, and a Tor onion domain!
Sorry again for the confusion and thanks for taking the time.


is it safe to use delta with hadoop-aliyun and Aliyun OSS object storage?

Hi,
I'm testing delta with hadoop-aliyun to create Delta table on Aliyun OSS:
https://hadoop.apache.org/docs/stable/hadoop-aliyun/tools/hadoop-aliyun/index.html
This document mentions some warnings, eg. delete() and rename() are not atomic.  I checked git repositories of Hudi and Iceberg, they have explicit support for Aliyun OSS, but Delta code is purely neutral to cloud service providers, so I want to confirm, is it safe to use Delta with hadoop-aliyun and Aliyun OSS object storage?
Thanks!

@YannByron Do you know how to use OSS Delta Lake on Aliyun?

@Dieken @zsxwing
As far as i know, OSS supports atomic rename for single object in non-multi-version, not directory. The OSS team is working on the multi-version case.
And also, there is OSS-HDFS that support all the syntax of HDFS, including the atomic rename for both single-file and directory.

This is how I use OSS Delta Lake on Aliyun,  I don't use OSS-HDFS because I wouldn't like to buy another service.
## hadoop-aliyun and its dependencies:
##      hadoop-aliyun-3.3.1.jar aliyun-sdk-oss-3.4.1.jar jdom-1.1.jar jettison-1.1.jar stax-api-1.0.1.jar aliyun-java-sdk-*.jar
##  Delta Lake jar:
##      delta-core_2.13-1.1.0.jar

##  Spark 3.2.1 from https://www.apache.org/dyn/closer.lua/spark/spark-3.2.1/spark-3.2.1-bin-hadoop3.2-scala2.13.tgz

jars=$(echo *.jar | sed -e 's/ /,/g')
spark-sql --jars "$jars" \
  --conf spark.hadoop.fs.AbstractFileSystem.oss.impl=org.apache.hadoop.fs.aliyun.oss.OSS \
  --conf spark.hadoop.fs.oss.impl=org.apache.hadoop.fs.aliyun.oss.AliyunOSSFileSystem \
  --conf spark.hadoop.fs.oss.endpoint=oss-cn-shenzhen-internal.aliyuncs.com \
  --conf spark.hadoop.fs.oss.accessKeyId=XXXXXXX \
  --conf spark.hadoop.fs.oss.accessKeySecret=YYYYYYY \
  --conf spark.sql.extensions=io.delta.sql.DeltaSparkSessionExtension \
  --conf spark.sql.catalog.spark_catalog=org.apache.spark.sql.delta.catalog.DeltaCatalog

CREATE TABLE IF NOT EXISTS t (id INT, name STRING, age INT) USING delta LOCATION 'oss://my-bucket/my-delta-table';

INSERT INTO t VALUES (1, "hello", 10), (2, "world", 20);

I checked the Delta data directory, seems Delta doesn't use sub directory to store data and meta data,  so I guess it's safe to use plain OSS with hadoop-aliyun + delta-core,  right?

@Dieken  I don't know how to use OSS directly without OSS-HDFS for now. Maybe I'll follow up this asap.

@Dieken I don't know how to use OSS directly without OSS-HDFS for now. Maybe I'll follow up this asap.

Thanks!   You can create a simple Java project with pom.xml containing hadoop-aliyun:3.3.1,  then use mvn dependency:copy-dependencies to get those jar files,  and use the command above to try delta on Aliyun OSS.

@Dieken what's the status of this issue? If you consider it resolved, please close this issue. Else, let me know how I can help further :)

@scottsand-db
Thanks for your checking!   I want a confirmation whether delta is safe to directly use hadoop-aliyun to read/write Aliyun OSS.  Seems @YannByron implicates it's safe with OSS-HDFS wrapper service over Aliyun OSS.
https://github.com/delta-io/delta/blob/v1.1.0/core/src/main/scala/org/apache/spark/sql/delta/storage/DelegatingLogStore.scala#L155
It explicitly supports Amazon and Azure object store,  but not mention Aliyun OSS.

@YannByron do you know which LogStore implementation can work with Aliyun OSS?

Given this is a question to the vendor rather than the Delta Lake project, I'm going to close this.


Ask Natalie about developing social media plan

please don't forget our sponsors/partners! :)

Note: we can set this up for the three remaining events, CityCamp, ATO, and
DataPalooza and have everything scheduled.
Jason
On Thu, Aug 17, 2017 at 1:30 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

please don't forget our sponsors/partners! :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/555#issuecomment-323140863,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoV5vLgveR-lRtrG42CQ0bdYUtqy1Bks5sZHiegaJpZM4O5jn3
.

I reached out to Natalie Noel at HQ, just waiting for a response. Natalie handles all of HQs social media.


[DRAFT] feat: experimental typed routes

🔗 Linked issue

#2813
#2976

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

[!IMPORTANT]
Very experimental and relies on nuxt/router/uvr internals, this will not be backported to v8.

I'm not very happy with the implementation right now, but it does work... I think the demand/convenience of this feature somewhat justifies adding this albeit under an experimental flag.
We should communicate very clearly that this relies on internals of Nuxt, Vue Router and unplugin-vue-router, perhaps we can make the types fallback to original behavior on failure (maybe it already does). A proper implementation will likely require collaboration with the maintainers of those packages, we should not expect this to keep working as is.
This will need some documentation and basic tests so we know things fail if internals have changed.
Demo stackblitz project here: https://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-srohiz?file=nuxt.config.ts&file=composables%2Ftest.ts
Demo of localePath autocompletion
https://github.com/user-attachments/assets/29d00cb6-1cdc-409f-bb23-fa08153d4a4e
Demo of custom routes configuration autocompletion and basic validation (prefix '/')
https://github.com/user-attachments/assets/38c41d9d-deb7-4688-be02-1ce0c18a9628

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have added tests (if possible).
[ ] I have updated the documentation accordingly.

Since it uses the vue-router type, it would be good if posva is able to review it.
@posva
Can you review it ?, if you have the time 🙏

@userquin
If you see some obvious structural improvements, feel free to suggest them, the must be some way to leave out the augmentations in internal-global-types.d.ts 🤔


refactor helm test scripts into reusable functions

For KIC 2.0 we created a new scripts/ dir where we added several helm tests. These tests have some repeating functionality that could be sourced out into functions used between scripts as a minor refactor.
Also CI does all tests in one long serial workflow: we should make these more parallel
Acceptance Criteria:

[ ] common functionality in scripts/ moved into source-able functions
[ ] CI workflows for integration tests broken out into concurrent steps

won't fix per se - @shaneutt suggested that what makes more sense as a starting point is writing new tests, and performing such refactors on a reactive basis.


Cannot click on the link of the Project session

Thank you for sharing the template. I have this problem when I render to pdf, I cannot click to the link in the project section. Do you have any idea why?

Found the issue, it was the {link} in the project section. There should be no space in bewteen


Doesn't work on Android

it's doen't work if i use Android Browser on Sony Xperia, Samsung S3 (4.4.2), Samsung S5 (4.4)
http://grab.by/Lhyq

I can confirm that this plugin doesn't work on the default Android browser on a Samsung Galaxy S4 (5.0.1). It behaves exactly as described by @nfort

@nfort , @dnasir ,
Can you retest with the latest version


Feature request: Refactor orderBy to support multiple fields and relations.

Was trying multiple orderBy and came into an issue that would throw an error "e[r].toLowerCase is not a function" when I looked into the code, I can see 'input' is being passed but it wouldn't be the object key but the parent array key.
query MyQuery {
  listUsers(skip: 2, take: 2, orderBy: {id: DESC, name: DESC}) {
    name
    id
  }
}

Prisma supports multiple OrderBy so I made some changes and built it with below:
    private parseOrderBy(orderByInput: any) {
        const orderByOutput: any = []
        for (const input in orderByInput) {
            const orderByKey = Object.keys(orderByInput[input])[0]
            const orderByArg = orderByInput[input][orderByKey].toLowerCase()

            if (PrismaOrderByArgs.includes(orderByArg)) {
                orderByOutput.push({
                    [orderByKey]: orderByArg,
                })
            }
        }

        return orderByOutput
    }

Does this approach make sense or is there a different plan for orderBy ?

Ideally, I would like to support both multiple orderBy and orderBy on relations. I’m not yet settled on the best approach.
What you are suggesting could be one solution. A second one could be turning orderBy input into an array, similar to: https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#sort-user-by-multiple-fields---email-and-role
A third solution (which sounds better to me, even though not exactly following Prisma syntax) - would be using a similar structure to filters, where you can use the AND: [] syntax for multiple orderBy and directly target a field or a relation:
input PostOrderByInput {
    AND:[PostOrderByInput]
    title: OrderByArg
    author: UserOrderByInput
}

FYI - Early next week, I'll release a new version that introduces pagination and a new where filtering mechanism closer to Prisma (as you suggested in another issue). You can try it via yarn add prisma-appsync@next. Quick overview at: https://github.com/maoosi/prisma-appsync/blob/next/CHANGELOG.md#version-100-beta55

With the code above, it accepts the orderBy in this way
orderBy: {id: DESC, name: DESC}
But converts it to prisma syntax
orderBy: [{ id: DESC }, { name: DESC }];
Which for me looks good because I won't need to nest the orderBy items, however if we can support more similar syntax as prisma and nexus (second option) it will be easier for developers to shift from nexus if they need to deploy with AppSync.
The third option, looks good, but I'm not familiar with that syntax being used anywhere else. Though it would be clear the order at which records will be sorted in.
Regarding the pagination update, I'm just working on a few things so it was easy enough to add while I checked on a few integrations. This package is honestly a life saver!
I added count() also to help with offset pagination
    public async count(model: string, args: RequestProps) {
        await this.runBeforeResolveHook({
            operation: Operations.count,
            model,
            args,
        })

        if (process.env.JEST_WORKER_ID) return args

        // count all records matching the where arguments
        const results = await this.prisma[model].count({
            ...(args.where && { where: args.where }),
            ...(args.skip && { skip: args.skip }),
            ...(args.take && { take: args.take }),
            ...(args.cursor && { cursor: args.cursor }),
            ...(args.distinct && { distinct: args.distinct }),
            ...(args.orderBy && { orderBy: args.orderBy }),
        })

        await this.runAfterResolveHook({ result: results })

        return results
    }

Thanks for sharing your thoughts on this! I’ll add both refactoring of orderBy and adding a count query to the roadmap.
Before diving into new features, I will spend some time refactoring the Tests and adding some CI/CD automation. After this is in place, it will make it easier to directly submit pull requests, in case you would like to contribute.

Both implemented in 1.0.0-beta.58.2 (see orderBy query filter and count query).


Create Napkin diagram for project 1

https://github.com/airavata-courses/CloudElves/wiki/Homework-1---Weather-Forecast#napkin-diagram
https://github.com/airavata-courses/CloudElves/commit/e1980b0ddc226150b81da1f0d941be333beb64da


Fix dependencies

Hey!
Will close this PR because I'll change ESLint for StandardJS. I think it'll make it simpler to keep the code style 😁


Bug localization bundle on v 3.0

Fix localization bundle when using FDTake 3.0 as a Pod (problem not present in example projet which use local Pod path)

Thank you, merged!

Pushed new version 0.3.1 including this fix

hmm I have error here on 0.3.2

Thank you, is anyone else seeing this bug?

Hi
I have checked
Problem is with latest cocoapods


Support multiple Kotlin versions

Currently, the Kondition compiler plugin is built over Kotlin 2.0.0 only.
We should support multiple Kotlin versions like 2.0.10, 2.0.20, etc.
Some compiler APIs are different depending on Kotlin Compiler versions.
For example, FirLiteralExpression was changed to FirLiteralExpression at some time.

I have read buildscripts configured in kotlinx.rpc, and finally understood how we should configure gradle scripts!
The version catalogs generated via libs.versions.toml placed at root gradle directory can't be modified via gradle script. (chicken and egg problem.)
dependencyResolutionManagement {
     versionCatalogs {
          getByName("libs").version("kotlin", "2.0.20") // error
     }
}


the polyline and entity is invisible when i rotate the scene

I want to know what causes this problem?

Hi @hieeyh, I'm not quite sure what's occluding those polylines.  Maybe it's a bug related to the fact that you have the globe turned off?
Could you put together a reproducible code example in Sandcastle? https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/
That would make it much easier for us to track down the problem.  Thanks!

Closing due to inactivity.  Feel free to re-open this issue if your'e still having trouble @hieeyh


Added missing priest's pack equipment

What does this do?
A priest's pack includes an alms box, 2 blocks of incense, a censer and vestments. None of these were included within the API. The four equipment pieces have been created and added to the contents of the priest's pack in the correct quantities. They've been added underneath the adventuring-gear and standard-gear equipment categories.
How was it tested?
It wasn't. Frankly I don't know how to, and don't really care enough to figure out how.
Is there a Github issue this is resolving?
No.
Did you update the docs in the API? Please link an associated PR if applicable.
<It's not clear if I don't update this text with relevant info>
Here's a fun image for your troubles

Small nit pick that you can just merge in via my comment, but otherwise looks good! Nice catch!


Fix job scaling for jobs with multiple taskgroups

A few bugs prevented proper scaling of jobs with multiple taskgroups. PR annotated below.
PTAL

Hey @jrasell, I know we haven't needed to make much commits here since things have been stable. Is this project archived? If not, could we get this PR merged in? It's required for jobs with multiple taskgroups to scale properly.


Implement mongoose model user.model.ts

Addresses issue: #29
Added a mongoose model to represent a user in MongoDB database.
Follows the schema:
//Users
{
    "auth_id": ,
    "first_name": ,
    "last_name": ,
    "persons": ["ObjectID('pid')"],
    "encounters": ["ObjectID('eid')"]
}

that looks good to me. auth_id is for storing uid of the firebase user I presume.

Yeah that's correct, just wanted to make it clear which ID was for what, given that there's an automatic object ID.


Semantic Search support

I propose to upgrade Lucene.Net to support semantic searches in the same way as the current JAVA version.
Proposal:

Add support for vector fields
Vector similarity search (Euclidian, Dot, Cosine)

+1

This is virtually impossible to do in Lucene 4.8.0 because it requires binary format changes to the index to support and there is no precedent in Java for layering this functionality on top of Lucene 4.8.0. Not to mention, we lose the ability to debug if we don't have a Lucene version to compare execution paths with and the test framework requires additional support to be built in to support newer versions. The only sensible way to do this is to upgrade the entire project to the entire version, not one feature at a time.
Given this functionality already exists in a later version, we will be implementing it when we do the upgrade. I am closing because this isn't an "issue" so much as something that is already part of the planned upgrade.


spot.newOrder('oco') :Server Error Code: -1013 Server Message: Duplicate order sent.

Hi,
I tried the function spot.newOrder for several options ('Limit', 'Market,'Stop Loss Limit'..) it works fine, but when
I tried it for OCO type orders  (I tryed it for sell),  it does not work.
what ever I try I got the message :
"
Error using sendRequest (line 81)
Client Error: Bad Request
Server Error Code: -1013
Server Message: Duplicate order sent.
"
even if there is no duplication (I mean I send the order for the first time!)
Can you help   solve this issu, please?
Thanks!

The code I used is :
obj = spot.newOrder('oco');
set(obj,'symbol',handles.symbol,'side','sell',...
'quantity',QtySell,...
'price',LimitPrice,...
'stopPrice',stopPrice,...
'stopLimitPrice',stopLimitPrice,...
'isTest',1)
request = obj.send;


[Event Request] Codeunit 5402 "Unit of Measure Management" - OnBeforeRoundToItemRndPrecision

Hello,
In order to manage a rounding precision to the nearest in addition to the standard 'up' in the procedure RoundToItemRndPrecision, would it be possible to get a new event:
    [IntegrationEvent(false, false)]
    local procedure OnBeforeRoundToItemRndPrecision(var Qty: Decimal; ItemRndPrecision: Decimal; var IsHandled: Boolean)
    begin
    end;

The modification in the procedure RoundToItemRndPrecision would be the following:
    procedure RoundToItemRndPrecision(Qty: Decimal; ItemRndPrecision: Decimal): Decimal
    var
        IsHandled: Boolean;
    begin
        IsHandled := false;
        OnBeforeRoundToItemRndPrecision(Qty, ItemRndPrecision, IsHandled);
        if IsHandled then
            exit(Qty);

        exit(Round(RoundQty(Qty), ItemRndPrecision, '>'));
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


FIX: replaces name field with localized string

I presume this was an error, should better match the spec now

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


post_create_clip query parameter does not work

The library that builds the query parameters for requests expects  a string, int or float. But has_delay is of type bool. We need to convert the boolean to a string and lower case it.
  File "C:\Users\james\code\twitch-jarvis-python\env\lib\site-packages\yarl\_url.py", line 923, in _query_var
    raise TypeError(
TypeError: Invalid variable type: value should be str, int or float, got False of type <class 'bool'>

https://dev.twitch.tv/docs/api/reference#create-clip
This happens if has_delay is provided or the default is used.

I can confirm by testing  User.create_clip(token=token) that this is a bug.


Fixes #58, unit tests fail on windows.

Fixes #58 These changes close the RandomAccessFiles that underlie the buffers before they get deleted.

Coverage decreased (-0.09%) to 47.879% when pulling f981c37dff508d182c1d6b2ee6671877971a5f75 on dieselpoint:master into 78ba123642b90d33c7e19346e38d2bdd6bf607eb on atomix:master.


Compose 1.9.0 docs

Proposed changes
Merging vnext-compose 1.9.0 docs into master.
Please take a look
@shin- @dnephin @nathanleclaire @johndmulhausen @mstanleyjones @ManoMarks

Deploy preview ready!
Built with commit 272849d81ee17c31008ca1d399e0fa84a5affbc2
https://deploy-preview-605--docker-docs.netlify.com

LGTM!


Use CLUSTERS_ARGS and DEPLOY_ARGS

Instead of using the Make flags that we want to remove, use the ARGS
flags to send the extra script arguments.

This ends up running
[00:10:04.987209] /opt/shipyard/scripts/deploy.sh --globalnet false --deploytool operator --cable_driver '' --globalnet true --deploytool helm --cluster_settings /go/src/github.com/submariner-io/shipyard/scripts/cluster_settings

but since the last setting wins, everything works out.

Yeah I know, it's temporary until we remove usage in all projects and can remove these variables from Makefile.inc


feat: add username data field to metadata call response

📦 Pull Request

The username field was added to the user metadata and now the Admin SDK needs to consume this and return it to the developer.
✅ Fixed Issues

Ticket

adds username to metadata return value and MagicUserMetadata interface
adds username to tests to getMetadataByIssuer.spec.ts

🚨 Test instructions

⚠ Don't forget to add a semver label!

:rocket: PR was released in v2.4.1 :rocket:


Exclude doesn't seem to work

Whenever I try to exclude certain things, it won't send the email

It's been a while since I've made any updates to this repo. I'll take a look and see if I can replicate/fix the issue.

Just got into coding but don't understand all so can't update or help. Would be a pleasure for me to help but there's a lot for me to learn. If not, any other repos you suggest?

Did you end up making it to work?


Release of 0.34.0 failed

Provider Version
⚠ Duplicate release tag: v0.34.0
19
Error: release-please failed: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
https://github.com/Snowflake-Labs/terraform-provider-snowflake/runs/6584436031?check_suite_focus=true
Terraform Version
Any
Describe the bug
The 0.34.0 relase is not available in the registry: https://registry.terraform.io/providers/Snowflake-Labs/snowflake/
Expected behavior
We are unable to run any Terraform Snowflake jobs in TF Cloud right now. The latest release has the gosnowflake client with the fix in https://github.com/snowflakedb/gosnowflake/pull/571 that we need. (Setting the default timezone didn't help)
Code samples and commands
Additional context
Please try to make a v0.34.1 release and tag it. (Also your docs need updating: https://quickstarts.snowflake.com/guide/terraforming_snowflake/index.html?index=..%2F..index#4)

Thanks, I can now see https://registry.terraform.io/providers/Snowflake-Labs/snowflake/0.34.0 in the registry!
Closing this, but note that your docs could still need an update 😄


Intesisbox issues

https://github.com/jnimmo/pyIntesisHome/blob/ea027b1d6e57a8bed689acbdeb6c5d5aed2fff0b/pyintesishome/intesisbox.py#L57
Home assistant says that there is an issue in this line which is:
Traceback (most recent call last):
  File "/config/custom_components/intesishome/config_flow.py", line 126, in async_step_details
    await controller.connect()
  File "/usr/local/lib/python3.10/site-packages/pyintesishome/intesisbox.py", line 57, in connect
    self._reader, self._writer = await asyncio.open_connection(
  File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
    transport, _ = await loop.create_connection(
TypeError: BaseEventLoop.create_connection() got an unexpected keyword argument 'loop'

My understanding is that you no longer can have a Loop in asyncio.open_connection.
This is breaking the integration with intesisbox.

I have exactly the same issue


ImagePolicy uses byte format for base64 fields

suggested from https://github.com/openshift/machine-config-operator/pull/4160#discussion_r1480649597.
In the code, we need to use []byte format of base64 data, but []byte will be encoded/decoded when JSON marshal/unmarshal, so set the original field to byte so we do not need to process the data type in the code.

@QiWang19 Can you please provide a PR description to explain why we are making this change, and link to the initial PR that introduced these fields? Do we have a bug report?

GoPlayground shows this is a compatible type change from a json serialisation perspective

@JoelSpeed update the description https://github.com/openshift/api/pull/1765#issue-2128127165

/lgtm

joel intended for this merge
/approve


[BUG]: AzureAppServiceSettings@1 A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"

Task name
AzureAppServiceSettings@1
Task version
1.223
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows_NT
Task log
2023-06-06T09:15:54.5989817Z ##[debug]Evaluating condition for step: 'Azure App Service Settings: web-app-name'
2023-06-06T09:15:54.5992651Z ##[debug]Evaluating: SucceededNode()
2023-06-06T09:15:54.5993319Z ##[debug]Evaluating SucceededNode:
2023-06-06T09:15:54.5994695Z ##[debug]=> True
2023-06-06T09:15:54.5995332Z ##[debug]Result: True
2023-06-06T09:15:54.5995992Z ##[section]Starting: Azure App Service Settings: (webappname)
2023-06-06T09:15:54.6245531Z ==============================================================================
2023-06-06T09:15:54.6245804Z Task         : Azure App Service Settings
2023-06-06T09:15:54.6245962Z Description  : Update/Add App settings an Azure Web App for Linux or Windows
2023-06-06T09:15:54.6246227Z Version      : 1.223.0
2023-06-06T09:15:54.6246364Z Author       : Microsoft Corporation
2023-06-06T09:15:54.6246516Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks
2023-06-06T09:15:54.6246761Z ==============================================================================
2023-06-06T09:15:54.6697284Z ##[debug]Using node path: C:\agents\externals\node16\bin\node.exe
2023-06-06T09:15:55.6246694Z ##[debug]agent.TempDirectory=C:\agents\_work\_temp
2023-06-06T09:15:55.6249064Z ##[debug]loading inputs and endpoints
2023-06-06T09:15:55.6416203Z ##[debug]loading ENDPOINT_AUTH_connectionsservicename
2023-06-06T09:15:55.8333339Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_connectionsservicename_AUTHENTICATIONTYPE
2023-06-06T09:15:55.8987113Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_connectionsservicename_SERVICEPRINCIPALID
2023-06-06T09:15:55.9047874Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_connectionsservicename_SERVICEPRINCIPALKEY
2023-06-06T09:15:55.9067692Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_connectionsservicename_TENANTID
2023-06-06T09:15:55.9106656Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2023-06-06T09:15:55.9133929Z ##[debug]loading ENDPOINT_AUTH_SCHEME_connectionsservicename
2023-06-06T09:15:55.9193126Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2023-06-06T09:15:55.9242626Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2023-06-06T09:15:55.9256832Z ##[debug]loading INPUT_APPNAME
2023-06-06T09:15:55.9284798Z ##[debug]loading INPUT_APPSETTINGS
2023-06-06T09:15:55.9421645Z ##[debug]loading INPUT_CONNECTEDSERVICENAME
2023-06-06T09:15:55.9423152Z ##[debug]loading INPUT_RESOURCEGROUPNAME
2023-06-06T09:15:55.9499540Z ##[debug]loading INPUT_SLOTNAME
2023-06-06T09:15:55.9512405Z ##[debug]loading SECRET_AZURE_APP_SERVICE_KUDU_PRODUCTION_PASSWORD
2023-06-06T09:15:55.9516273Z ##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
2023-06-06T09:15:55.9521325Z ##[debug]loaded 16
2023-06-06T09:15:58.9719453Z ##[debug]Agent.ProxyUrl=http://proxiinfo
2023-06-06T09:15:58.9720312Z ##[debug]Agent.ProxyUsername=undefined
2023-06-06T09:15:58.9721068Z ##[debug]Agent.ProxyPassword=undefined
2023-06-06T09:15:58.9721783Z ##[debug]Agent.ProxyBypassList=["azurewebsites\\.net"]
2023-06-06T09:15:58.9722485Z ##[debug]expose agent proxy configuration.
2023-06-06T09:15:58.9741543Z ##[debug]Agent.CAInfo=undefined
2023-06-06T09:15:58.9776969Z ##[debug]Agent.ClientCert=undefined
2023-06-06T09:15:58.9777816Z ##[debug]Agent.SkipCertValidation=undefined
2023-06-06T09:15:58.9778602Z ##[debug]agent.proxyurl=http://proxiinfo
2023-06-06T09:15:58.9779292Z ##[debug]agent.proxyusername=undefined
2023-06-06T09:15:58.9779973Z ##[debug]agent.proxypassword=undefined
2023-06-06T09:15:58.9780679Z ##[debug]agent.proxybypasslist=["azurewebsites\\.net"]
2023-06-06T09:15:58.9782249Z ##[debug]agent.proxybypasslist=["azurewebsites\\.net"]
2023-06-06T09:15:58.9783389Z ##[debug]VSTS_ARM_REST_IGNORE_SSL_ERRORS=undefined
2023-06-06T09:15:58.9784199Z ##[debug]AZURE_HTTP_USER_AGENT=VSTS_e7846edc-215b-458c-9e2f-41423af00f3a_build_66_0
2023-06-06T09:15:58.9785178Z ##[debug]check path : C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9873659Z ##[debug]adding resource file: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9874812Z ##[debug]system.culture=en-US
2023-06-06T09:15:58.9875451Z ##[debug]Agent.TempDirectory=C:\agents\_work\_temp
2023-06-06T09:15:58.9876862Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9894966Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9914752Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9916072Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9917265Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9918501Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9919746Z ##[debug]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9920881Z ##[debug]check path : C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\task.json
2023-06-06T09:15:58.9921835Z ##[debug]adding resource file: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\task.json
2023-06-06T09:15:58.9922666Z ##[debug]system.culture=en-US
2023-06-06T09:15:58.9951254Z ##[warning]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9960711Z ##[debug]Processed: ##vso[task.issue type=warning;]Resource file has already set to: C:\agents\_work\_tasks\AzureAppServiceSettings_3eeea460-bffa-11e9-9cb5-2a2ae2dbcce4\1.223.0\node_modules\azure-pipelines-tasks-azure-arm-rest-v2\module.json
2023-06-06T09:15:58.9961931Z ##[debug]ConnectedServiceName=connectionsservicename
2023-06-06T09:15:58.9962706Z ##[debug]appName=web-app-name
2023-06-06T09:15:58.9963412Z ##[debug]resourceGroupName=rg-name
2023-06-06T09:15:58.9964037Z ##[debug]slotName=production
2023-06-06T09:15:58.9966201Z ##[debug]appSettings=[
{
"name": "AzureAd__ApplicationId",
"value": "appid",
"slotSettings": false
}
]
2023-06-06T09:15:58.9969378Z ##[debug]generalSettings=undefined
2023-06-06T09:15:58.9970067Z ##[debug]connectionStrings=undefined
2023-06-06T09:15:58.9970667Z ##[debug]USE_MSAL=true
2023-06-06T09:15:58.9971370Z ##[debug]MSAL - USE_MSAL override is found: true
2023-06-06T09:15:58.9972093Z ##[debug]connectionsservicename auth scheme = ServicePrincipal
2023-06-06T09:15:58.9972978Z ##[debug]connectionsservicename data subscriptionid = subscriptionid
2023-06-06T09:15:58.9973872Z ##[debug]connectionsservicename data subscriptionname = Subscription name
2023-06-06T09:15:58.9975330Z ##[debug]connectionsservicename auth param serviceprincipalid = ***
2023-06-06T09:15:58.9976431Z ##[debug]connectionsservicename data activeDirectoryAuthority = https://login.microsoftonline.com/
2023-06-06T09:15:58.9977335Z ##[debug]connectionsservicename auth param tenantid = tenantid
2023-06-06T09:15:58.9978226Z ##[debug]connectionsservicename=https://management.azure.com/
2023-06-06T09:15:58.9979045Z ##[debug]connectionsservicename data environment = AzureCloud
2023-06-06T09:15:58.9979808Z ##[debug]connectionsservicename auth scheme = ServicePrincipal
2023-06-06T09:15:58.9980637Z ##[debug]connectionsservicename data msiclientId = undefined
2023-06-06T09:15:58.9981544Z ##[debug]connectionsservicename data activeDirectoryServiceEndpointResourceId = https://management.core.windows.net/
2023-06-06T09:15:58.9982468Z ##[debug]connectionsservicename data AzureKeyVaultServiceEndpointResourceId = https://vault.azure.net
2023-06-06T09:15:58.9983388Z ##[debug]connectionsservicename data AzureKeyVaultDnsSuffix = vault.azure.net
2023-06-06T09:15:58.9984245Z ##[debug]connectionsservicename data ScopeLevel = Subscription
2023-06-06T09:15:58.9984994Z ##[debug]MSAL - getEndpoint - useGraphActiveDirectoryResource=false
2023-06-06T09:15:58.9985780Z ##[debug]MSAL - getEndpoint - useMSAL=true
2023-06-06T09:15:59.0017454Z ##[debug]MSAL - getEndpoint - endpoint={"subscriptionID":"subscriptionid","subscriptionName":"Subscription name","servicePrincipalClientID":"***","environmentAuthorityUrl":"https://login.microsoftonline.com/","tenantID":"tenantid","url":"https://management.azure.com/","environment":"AzureCloud","scheme":"ServicePrincipal","activeDirectoryResourceID":"https://management.core.windows.net/","azureKeyVaultServiceEndpointResourceId":"https://vault.azure.net","azureKeyVaultDnsSuffix":"vault.azure.net","scopeLevel":"Subscription"}
2023-06-06T09:15:59.0295810Z ##[debug]MSAL - getEndpoint - connectedServiceName=connectionsservicename
2023-06-06T09:15:59.0307242Z ##[debug]connectionsservicename auth param authenticationType = spnKey
2023-06-06T09:15:59.0308186Z ##[debug]credentials spn endpoint
2023-06-06T09:15:59.0309569Z ##[debug]connectionsservicename auth param serviceprincipalkey = ***
2023-06-06T09:15:59.0310461Z ##[debug]connectionsservicename data EnableAdfsAuthentication = false
2023-06-06T09:15:59.0311306Z ##[debug]connectionsservicename auth param apitoken = undefined
2023-06-06T09:15:59.0314376Z ##[debug]{"subscriptionID":"subscriptionid","subscriptionName":"Subscription name","servicePrincipalClientID":"***","environmentAuthorityUrl":"https://login.microsoftonline.com/","tenantID":"tenantid","url":"https://management.azure.com/","environment":"AzureCloud","scheme":"ServicePrincipal","activeDirectoryResourceID":"https://management.azure.com/","azureKeyVaultServiceEndpointResourceId":"https://vault.azure.net","azureKeyVaultDnsSuffix":"vault.azure.net","scopeLevel":"Subscription","authenticationType":"spnKey","servicePrincipalKey":***,"isADFSEnabled":false,"applicationTokenCredentials":{"clientId":"***","tenantId":"tenantid","baseUrl":"https://management.azure.com/","authorityUrl":"https://login.microsoftonline.com/","activeDirectoryResourceId":"https://management.azure.com/","isAzureStackEnvironment":false,"authType":"spnKey","secret":***,"isADFSEnabled":false,"useMSAL":true,"tokenMutex":{"_semaphore":{"_value":1,"_cancelError":{},"_weightedQueues":[],"_weightedWaiters":[]}}}}
2023-06-06T09:15:59.0318060Z Got service connection details for Azure App Service:'web-app-name'
2023-06-06T09:15:59.0318794Z ##[debug]Resource Group: rg-name
2023-06-06T09:15:59.0609000Z ##[debug]Processed: ##vso[telemetry.publish area=TaskEndpointId;feature=AzureRmWebAppDeployment]{"endpointId":"connectionsservicename"}
2023-06-06T09:15:59.0654351Z Updating App Service Application settings. Data: {"AzureAd__ApplicationId":"data","AzureAd__ClientId":"clientid","AzureAd__Instance":"https://login.microsoftonline.com/","AzureAd__TenantId":"clientid"}
2023-06-06T09:15:59.0660383Z ##[debug]MSAL - getMSALToken called. force=undefined
2023-06-06T09:15:59.0663254Z ##[debug]agent.proxyurl=http://proxiinfo
2023-06-06T09:15:59.0664252Z ##[debug]agent.proxyurl=http://proxiinfo
2023-06-06T09:15:59.0665045Z ##[debug]agent.proxybypasslist=["azurewebsites\\.net"]
2023-06-06T09:15:59.0665804Z ##[debug]agent.proxybypasslist=["azurewebsites\\.net"]
2023-06-06T09:15:59.0666518Z ##[debug]MSAL - Proxy will be used.
2023-06-06T09:15:59.0667209Z ##[debug]agent.proxyusername=undefined
2023-06-06T09:15:59.0667886Z ##[debug]agent.proxypassword=undefined
2023-06-06T09:15:59.0668678Z ##[debug]MSAL - Proxy setup with no-auth is: http://proxiinfo
2023-06-06T09:15:59.0669522Z ##[debug]MSAL - ServicePrincipal - clientSecret is used.
2023-06-06T09:15:59.0670382Z ##[debug][Tue, 06 Jun 2023 09:15:58 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByClientCredential called
2023-06-06T09:15:59.0672420Z ##[error][Tue, 06 Jun 2023 09:15:58 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: TypeError
Error Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:15:59.0673922Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:15:58 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:15:59.0675895Z ##[error][Tue, 06 Jun 2023 09:15:58 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:15:59.0677289Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:15:58 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:15:59.0678523Z ##[debug]MSAL - retrying getMSALToken - temporary error code: endpoints_resolution_error
2023-06-06T09:15:59.0679346Z ##[debug]MSAL - retrying getMSALToken - remaining attempts: 3
2023-06-06T09:16:00.9999671Z ##[debug]MSAL - getMSALToken called. force=undefined
2023-06-06T09:16:01.0001070Z ##[debug][Tue, 06 Jun 2023 09:16:00 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByClientCredential called
2023-06-06T09:16:01.0003056Z ##[error][Tue, 06 Jun 2023 09:16:00 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: TypeError
Error Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:16:01.0005939Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:16:00 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:16:01.0007995Z ##[error][Tue, 06 Jun 2023 09:16:00 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:16:01.0009963Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:16:00 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:16:01.0016053Z ##[debug]MSAL - retrying getMSALToken - temporary error code: endpoints_resolution_error
2023-06-06T09:16:01.0017005Z ##[debug]MSAL - retrying getMSALToken - remaining attempts: 2
2023-06-06T09:16:03.0044488Z ##[debug]MSAL - getMSALToken called. force=undefined
2023-06-06T09:16:03.0110720Z ##[debug][Tue, 06 Jun 2023 09:16:02 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByClientCredential called
2023-06-06T09:16:03.0120645Z ##[error][Tue, 06 Jun 2023 09:16:02 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: TypeError
Error Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:16:03.0123134Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:16:02 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:16:03.0160596Z ##[error][Tue, 06 Jun 2023 09:16:03 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:16:03.0162729Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:16:03 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:16:03.0179448Z ##[debug]MSAL - retrying getMSALToken - temporary error code: endpoints_resolution_error
2023-06-06T09:16:03.0221735Z ##[debug]MSAL - retrying getMSALToken - remaining attempts: 1
2023-06-06T09:16:05.0098366Z ##[debug]MSAL - getMSALToken called. force=undefined
2023-06-06T09:16:05.0100201Z ##[debug][Tue, 06 Jun 2023 09:16:05 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByClientCredential called
2023-06-06T09:16:05.0154031Z ##[error][Tue, 06 Jun 2023 09:16:05 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: TypeError
Error Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:16:05.0156531Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:16:05 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
2023-06-06T09:16:05.0164636Z ##[error][Tue, 06 Jun 2023 09:16:05 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:16:05.0167876Z ##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 09:16:05 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
2023-06-06T09:16:05.0175661Z ##[debug]task result: Failed
2023-06-06T09:16:05.0190071Z ##[error]Error: Failed to get App service 'web-app-name' application settings. Error: Could not fetch access token for Azure. Status code: endpoints_resolution_error, status message: Error: could not resolve endpoints. Please check network and try again. Detail: ClientConfigurationError: untrusted_authority: The provided authority is not a trusted authority. Please include this authority in the knownAuthorities config parameter.
2023-06-06T09:16:05.0192537Z ##[debug]Processed: ##vso[task.issue type=error;]Error: Failed to get App service 'web-app-name' application settings. Error: Could not fetch access token for Azure. Status code: endpoints_resolution_error, status message: Error: could not resolve endpoints. Please check network and try again. Detail: ClientConfigurationError: untrusted_authority: The provided authority is not a trusted authority. Please include this authority in the knownAuthorities config parameter.
2023-06-06T09:16:05.0213351Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: Failed to get App service 'web-app-name' application settings. Error: Could not fetch access token for Azure. Status code: endpoints_resolution_error, status message: Error: could not resolve endpoints. Please check network and try again. Detail: ClientConfigurationError: untrusted_authority: The provided authority is not a trusted authority. Please include this authority in the knownAuthorities config parameter.
2023-06-06T09:16:05.0257395Z ##[section]Finishing: Azure App Service Settings: web-app-name

Relevant log output
Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
Error: Could not fetch access token for Azure. Status code: endpoints_resolution_error, status message: Error: could not resolve endpoints. Please check network and try again. Detail: ClientConfigurationError: untrusted_authority: The provided authority is not a trusted authority. Please include this authority in the knownAuthorities config parameter.

Aditional info
I used this task and it was working correctly. Before the execution of this task, i am using the Azure App Service deployment which works as expected but not update settings:
- task: AzureRmWebAppDeployment@4 //This task works as expected
  displayName: 'Azure App Service Deploy: web-$(environment)-webapp-xxx'
  inputs:
    azureSubscription: '${{ parameters.serviceConnection }}'
    WebAppName: 'web-${{ parameters.environment }}-webapp-xxx'
    packageForLinux: '$(Pipeline.Workspace)/drop/artifact.zip'
  enabled: true

- task: AzureAppServiceSettings@1 //it fails here
  displayName: 'Azure App Service Settings: web-${{ parameters.environment }}-webapp-xxx'
  inputs:
    azureSubscription: '${{ parameters.serviceConnection }}'
    appName: 'web-${{ parameters.environment }}-webapp-xxx'
    resourceGroupName: 'rg-${{ parameters.environment }}-webapp-xxx'
    appSettings: |
    //app settings

     ]
It stopepd working 1st of june.

Hello, thanks for reporting.
Could you please check your proxy settings if it is allowing following URLs:

login.microsoftonline.com
graph.microsoft.com

@ozanaydinMSFT we don't block any URLs from our proxies. What was changed since the 1st of June from the Azure side?

Maybe its time to upgrade the version of that module:
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/4879#issuecomment-1462949837
for these tasks at least:

https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureKeyVaultV1/npm-shrinkwrap.json#L12
https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureKeyVaultV2/npm-shrinkwrap.json#L12

NO_PROXY=login.microsoftonline.com,graph.microsoft.com didn't help
still have
##[error][]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: TypeError
Error Description: Protocol "https:" not supported. Expected "HTTP:"

##[debug]Processed: ##vso[task.issue type=error;][]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
##[error][]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.

NO_PROXY=login.microsoftonline.com,graph.microsoft.com didn't help
still have
##[error][]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: TypeError
Error Description: Protocol "https:" not supported. Expected "HTTP:"

##[debug]Processed: ##vso[task.issue type=error;][]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: TypeError%0AError Description: Protocol "https:" not supported. Expected "http:"
##[error][]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.

If you're trying to add pipeline variable, you can use this syntax:
agent.proxybypasslist = ["login.microsoftonline.com","graph.microsoft.com"]
If it still doesn't help, could you please share your full debug enabled log to see if settings are correct?

It doesn't override it. Is it correct like that?

I updated my .proxybypass file in the agent root directory and added the links proposed above:
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/proxy?view=azure-devops&tabs=windows
And now It works for me.

@emadalsous @ozanaydinMSFT
I also updated .proxybybass file in the agent root directory & have another the next error:
##[debug]Downloading selected secrets from subscriptionId: <subscription_id>, vault: <kv_name>
##[debug]Downloading part [0 - 3] (total 3 secrets)
##[debug]Promise for downloading secret value for: secret-1
Downloading secret value for: secret-1
##[debug]Promise for downloading secret value for: secret-2
Downloading secret value for: secret-2.
##[debug]Promise for downloading secret value for: secret-3
Downloading secret value for: secret-3
##[debug]MSAL - getMSALToken called. force=undefined
##[debug]agent.proxyurl=http://<proxy_url>:3128/
##[debug]agent.proxyurl=http://<proxy_url>:3128/
##[debug]agent.proxybypasslist=["login.microsoftonline\\.com","graph.microsoft\\.com"]
##[debug]agent.proxybypasslist=["login.microsoftonline\\.com","graph.microsoft\\.com"]
##[debug]MSAL - Proxy is set but will be bypassed for https://login.microsoftonline.com/<tenant_id>
##[debug]MSAL - ServicePrincipal - clientSecret is used.
##[debug][Tue, 06 Jun 2023 12:05:02 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByClientCredential called
##[error][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: Error
Error Description: Error: connect ETIMEDOUT <IP_ADDRESS>:443
##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: Error%0AError Description: Error: connect ETIMEDOUT <IP_ADDRESS>:443
##[error][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
##[debug]MSAL - retrying getMSALToken - temporary error code: endpoints_resolution_error
##[debug]MSAL - retrying getMSALToken - remaining attempts: 3
...

@emadalsous @ozanaydinMSFT
I also updated .proxybybass file in the agent root directory & have another the next error:
##[debug]Downloading selected secrets from subscriptionId: <subscription_id>, vault: <kv_name>
##[debug]Downloading part [0 - 3] (total 3 secrets)
##[debug]Promise for downloading secret value for: secret-1
Downloading secret value for: secret-1
##[debug]Promise for downloading secret value for: secret-2
Downloading secret value for: secret-2.
##[debug]Promise for downloading secret value for: secret-3
Downloading secret value for: secret-3
##[debug]MSAL - getMSALToken called. force=undefined
##[debug]agent.proxyurl=http://<proxy_url>:3128/
##[debug]agent.proxyurl=http://<proxy_url>:3128/
##[debug]agent.proxybypasslist=["login.microsoftonline\\.com","graph.microsoft\\.com"]
##[debug]agent.proxybypasslist=["login.microsoftonline\\.com","graph.microsoft\\.com"]
##[debug]MSAL - Proxy is set but will be bypassed for https://login.microsoftonline.com/<tenant_id>
##[debug]MSAL - ServicePrincipal - clientSecret is used.
##[debug][Tue, 06 Jun 2023 12:05:02 GMT]<EMAIL_ADDRESS>: Info - acquireTokenByClientCredential called
##[error][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: Error
Error Description: Error: connect ETIMEDOUT <some_ip>:443
##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.%0AError: Error%0AError Description: Error: connect ETIMEDOUT <some_ip>:443
##[error][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
##[debug]Processed: ##vso[task.issue type=error;][Tue, 06 Jun 2023 12:07:12 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error.
##[debug]MSAL - retrying getMSALToken - temporary error code: endpoints_resolution_error
##[debug]MSAL - retrying getMSALToken - remaining attempts: 3
...

I think your error seems like related connectivity. Proxy bypass setting will only allow to connect endpoint without proxy, if your agent is not allowing outgoing connection to these endpoints, bypass will not work.

Please check if you've access these URLs from your agent.
(in case you have to use proxy): Please also check your proxy logs for connection requests, make sure there is no SSL inspection/redirect for these endpoints.

Getting the same error for AzureAppServiceSettings@1, but we can't set proxybypass as we need to use proxy to access these URLs from our agent. And I have tested the connection to these URLs are working fine from our agents. Also checked the proxy logs, we don't have SSL/TLS inspection or redirection on the traffic for these endpoints.
@ozanaydinMSFT Can you please advise? Would this need a fix or an upgrade to the module? #4879

I'm re-opening the issue to investigate further.
@jaskirat-randhawa , may I ask for full debug logs for both AzureAppServiceSettings@1 and AzureRmWebAppDeployment@4?

@ozanaydinMSFT  I can confirm our issue has been resolved using the latest version as mentioned above. We no longer need to bypass the proxy.

upvote for the keyvault task
##[error][Wed, 23 Aug 2023 18:24:14 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata. Error: Error Error Description: Error: getaddrinfo EAI_AGAIN login.microsoftonline.com ##[error][Wed, 23 Aug 2023 18:24:14 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error. ##[error][Wed, 23 Aug 2023 18:24:36 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata. Error: Error Error Description: Error: getaddrinfo EAI_AGAIN login.microsoftonline.com ##[error][Wed, 23 Aug 2023 18:24:36 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error. ##[error][Wed, 23 Aug 2023 18:24:58 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata. Error: Error Error Description: Error: getaddrinfo EAI_AGAIN login.microsoftonline.com ##[error][Wed, 23 Aug 2023 18:24:58 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error. ##[error][Wed, 23 Aug 2023 18:25:20 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata. Error: Error Error Description: Error: getaddrinfo EAI_AGAIN login.microsoftonline.com ##[error][Wed, 23 Aug 2023 18:25:20 GMT]<EMAIL_ADDRESS>: Error - Did not find cloud discovery metadata from hardcoded values... Metadata could not be obtained from config, cache, network or hardcoded values. Throwing Untrusted Authority Error. ##[error]

im experiencing this error as well to Azure Key Vault.  please help.
##[error][Wed, 22 Nov 2023 00:01:03 GMT]<EMAIL_ADDRESS>: Error - A non-MSALJS error was thrown while attempting to get the cloud instance discovery metadata.
Error: Error
Error Description: Error: read ECONNRESET


[Suggestion] Prevent blockbreaking for blocks that player doesnt want to break

I'd like to suggest a function that prevents the player from breaking customized/set blocks.
I had the idea when I was palying on a skyserver and broke pistons in my cobblestone/oregenerator repeatedly.
So I searched for a mod that would allow me to disallow the breaking of pistons. Your mod was the one that had the most "alike" features, so I chose to suggest that feature.
This feature should be made so the player can decide which blocks he dont want to be able to break

It's a good idea, I had basically the same idea in the past but decided against implementing it in preventer as it would make the mod way too complicated with conflicts between different modules. So I decided to spin that off into a different mod that focuses on customizable lists of all kinds of actions with items/blocks one want's to (dis)allow. I started to develop that mod but hit a roadblock with trying to implement some kind of config panel that allows the player to change the list, as no current config library mod that offers a good way to implement item lists. So I'll put this issue on hold for now, until I find a solution for the problem (which very well could be developing my own config mod if I find the time).


Checkbox binding not working

Version
2.5.13
Reproduction link
https://jsfiddle.net/Sparki2002/dnjrjkmn/2/
Steps to reproduce

Create a data property named "value"
Create a input element with checkbox type on your template and bind it's value attribute to the value property
Run the code and check and uncheck the checkbox while observing the value property

What is expected?
The value property should be the same as the checkbox check state
What is actually happening?

The value property is always false

It's working on Firefox (59/60), but not on Chrome (64/65).
I've also tried using the checked attribute on the input element
I can't use v-model because of other mechanisms in my code

You should use v-model.
<input v-model="value" type="checkbox">

What @maxirozay said. You can also listen to the change event
Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂


Bug: Webview opens a new window every time

Describe the bug
Webview spawns a windows thats not viewable in the taskbar, nor can i close it. but when i win+tab (NOT ALT-TAB) then every single webview window that i ever opened comes up.
To Reproduce

Create command for webview
assign command to hotkey
use said command to spawn window

Expected behavior
It closes immediatly and gets rid of any traces.
Screenshots

Misc info (please complete the following information):

Windows build:

Windows' UI language: English

HASS.Agent version: 2022.12.0

Please check what's applicable (multiple answers possible):

[x] Installed via installer
[ ] Installed manually
[x] Problem occurs in HASS.Agent
[ ] Problem occurs in Satellite Service

Additional context
Logs
Nothing about the webview, other than that it stored the quick action hotkey for it.

Hi @Zenchyi1,
As artsy as that looks, that shouldn't happen. I've improved the webview code in the upcoming version, one of the bugs was indeed that old webviews wouldn't close, so hopefully that'll fix this as well.
Should get released this weekend, let me know if it persists afterwards!

Should be fixed in the latest release: 2022.13.0


Update to Current Features

As Skeleton seems to be unmaintained, I've forked Skeleton to use modern CSS features and kept it dependency free (ie. no SCSS required) so it's as simple as possible to get started:
Barebones

CSS Grid replaces 12 columns
CSS Variables used globally for theme styling
Maintained backwards legacy support for Skeleton styling but build on top of CSS Grid and CSS Variables

Check it out and hopefully others will find it useful.

@acahir Are you planning to keep this updated?

Yep, gonna try. Just had some minor changes submitted to Barebones, so at
least someone else found it useful.
On Wed, May 1, 2019 at 8:53 AM David Jendreizak<EMAIL_ADDRESS>wrote:

@acahir https://github.com/acahir Are you planning to keep this updated?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dhg/Skeleton/issues/382#issuecomment-488274793, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAK2ICYLX2RGNPWMZKRHPA3PTGHFZANCNFSM4GSSKFTQ
.

@acahir did you implement smooth scroll and nav boilerplate yet curious. Tnx and super excited for the backwards compat w Skeleton.

Thanks @acahir. Coming back to Skeleton after 4 years, it's great to see someone's taken up the maintenance.


Use tenant site_id to generate redirus tasks

Site is can be shared among many tenants. It is used distinguish correct Redis queue name to generate add/remove http/https proxies jobs.

:+1:


Variables not being replaced in the template

Rendering the template to file does not seem to work as expected, when attempting to render this template its not replacing the single variable.
template = Sablon.template(File.expand_path('./template.docx'))
    context = {
      please: 'test'
    }
template.render_to_file File.expand_path('./output.docx'), context

Please see template attached.
template.docx

I did not create the mail merge field properly. apologies.


SPIR-V to MSL conversion issue

This is a strange one, and probably needs to be reported over at spirv-cross instead. However what's particularly odd about it that is only happens at runtime during vkCreateGraphicsPipelines(). When running the standalone shader conversion tool, proper MSL code is created. So I'm wondering if there is something else occurring within the MoltenVK codebase.
Working from MoltenVK release tag v1.0.44
Here is the source SPIR-V reported by MVK_DEBUG=1 output
error.spv.txt
Specifically the issue is with the input variable texCoord0. In the SPIR-V is correctly declared as a vec2. However in the generated MSL it gets declared as a vec4, which causes a compile error when trying to sample sNormalMap with a vec4 instead of a vec2.
error.msh.txt
Even the estimated original GLSL correctly has it as a vec2:
error.glsl.txt
The only MVK option I have set is the mvkConfig.fullImageViewSwizzle, however this error happens both with this set and not set.
One other hint, it seems likely that this cause occurs only when mat3 tangentToWorld is present in the input variables.
Any ideas on what other things could be happening that would cause this to occur? Pointers on where to debug?
Thanks

Looks like more fallout from #931. What does the vertex shader look like?

The vertex has it correctly as a vec2 in all 3 versions, the struct is declared identically in the source GLSL. Here is the SPIR-V from the vert, as output from MVK_DEBUG=1 printouts.
vert.spv.txt

Hey @cdavis5e, any idea if this got fixed?

Hey @cdavis5e, any idea if this got fixed?

Hey @cdavis5e, any idea if this got fixed?

Sorry, I don't know. I've been busy with other stuff lately. Have you tried it again lately?

Hey @cdavis5e, any idea if this got fixed?

Sorry, I don't know. I've been busy with other stuff lately. Have you tried it again lately?

Closing this one for now as I can't reproduce in the latest versions of MoltenVK


[DUOS-473][risk=no] Address Security Vulnerability

Addresses
https://broadinstitute.atlassian.net/browse/DUOS-473
Changes
Library update due to SC report:
https://www.sourceclear.com/vulnerability-database/vulnerabilities/760

Arbitrary Code Execution Through The Class Parameter Passed To The GetClass
commons-beanutils is vulnerable to arbitrary remote code execution. Attackers are able to leverage the missing suppression of the class property to manipulate the ClassLoader and execute code.
Update
This issue was fixed in version 1.9.4 of Apache Commons BeanUtils. That version is currently considered safe, we suggest that you upgrade to the fixed version.

Additionally, there was a failing test that was hitting a redirect error from json schema. Removed test as it really isn't necessary.

Coverage remained the same at 73.623% when pulling c83d37ea586cf646c259a8faf958febc5d5fa45e on DUOS-473 into d624a0cc22fdb486ab0e402520bd27b5526f3ed9 on develop.


Add the time user replied for comments

Description
Add when the comment was made.
Importance
High

Pull request #50