Feedback: Obligation

Update 4/20/15: Thank you for your feedback on the data element obligation. We will consider your feedback as we continually assess how we can improve data definitions. You may still contribute the discussion for other data elements. Check http://fedspendingtransparency.github.io/dataelements/ to find data elements with open feedback pages.
This is the place to leave your feedback and questions about the following data element:

Obligation

The feedback period for Obligation closes on 4/20/2015.
The proposed definition of Obligation: http://fedspendingtransparency.github.io/whitepapers/obligation/
Federal Spending Collaboration home page: http://fedspendingtransparency.github.io/

In our study (pg. 37), we defined obligation as you see below. It's an entity with many properties, and it's important that the (non-optional) ones be included so that obligations can be recognized and placed in context, and so that their content is available. In addition to what's below, a copy of the obligation's text itself is a part of this data element. AmIright?
Obligation
An abstract class representing a binding agreement or statutory requirement that will
result in outlays immediately or in the future.
●«Identifier» (obligationId)
●obligationId: string {uniquely identifies the obligation}
●authority: Authority
●allocation: Allocation {optional}
●apportionment: Apportionment {optional}
●summary: string {description of the obligation}
●amount: int
●obligor: ExecutiveAgent

I cannot foresee any problems in the definition of Obligations for establishing standards.  The issue will be in the use of the standard term.
Currently, usaspending.com and the Statement of Spending report as spending, the amounts obligated.  This is not true.  Obligated amounts might never be spent.  Furthermore, the term Obligation is not understood by persons not cognizant of the Federal budget process.  They do not realize that obligations is not spending.  Hence, the reporting resulting from the DATA Act must address this difference and eliminate any possibility of misleading information.

@halsteinberg Thanks for pointing out the potential confusion around obligations.  In addition to obligations, the current list of DATA Act elements also includes appropriations and outlays to better provide information about the lifecycle of federal spending. Hopefully this addresses your concern above, but please chime in again if it doesn't.
For reference, here's the entire list of DATA Act data elements: http://fedspendingtransparency.github.io/dataelements/
I believe that the definition of outlays is among the next batch being released for public input.

Yes, appropriations and outlays will provide additional information about the life cycle of federal spending.  However, there is still another element that would have to be added.  I suspect you realize that while the government has outlayed cash for a government service/program, there could be costs for which cash payments are not yet required.  Thus, for persons to obtain the total cost of a government service/program, a data element in which either accrued cost or total cost will be needed.
Also, as I said, I have no problem with the definition of obligation.  The problem is the way in which the amounts are used to report something else, i. e., spending.  Thus, it is the reporting of the obligation information that will need to be addressed.

Yes, appropriations and outlays will provide additional information
about the life cycle of federal spending.  However, there is still
another element that would have to be added.  I suspect you realize that
while the government has outlayed cash for a government service/program,
there could be costs for which cash payments are not yet required.
Thus, for persons to obtain the total cost of a government
service/program, a data element in which either accrued cost or total
cost will be needed.
Also, as I said, I have no problem with the definition of obligation.
The problem is the way in which the amounts are used to report something
else, i. e., spending.  Thus, it is the reporting of the obligation
information that will need to be addressed.

Becky Sweger<EMAIL_ADDRESS>Monday, April 06, 2015 9:31 AM
@halsteinberg https://github.com/halsteinberg Thanks for pointing
out the potential confusion around obligations. In addition to
obligations, the current list of DATA Act elements also includes
appropriations and outlays to better provide information about the
lifecycle of federal spending. Hopefully this addresses your concern
above, but please chime in again if it doesn't.
For reference, here's the entire list of DATA Act data elements:
http://fedspendingtransparency.github.io/dataelements/
I believe that the definition of outlays is among the next batch being
released for public input.
—
Reply to this email directly or view it on GitHub
https://github.com/fedspendingtransparency/fedspendingtransparency.github.io/issues/20#issuecomment-90065607.

--
Sent with Postbox http://www.getpostbox.com

The definitions used by OMB for "obligation" (and "outlay") are satisfactory as they stand.  The recommended definition in the draft DE#77 and the background information are reality based.
What was missed is that presentation of accounting information needs to make distinct transactions that involve multi-year and no-year availability budget authority from appropriations.  With annual appropriations -- the new obligation is incurred in same fiscal year period as the enacted appropriation (or Continuing Resolution).   But the site will also have to accommodate new obligations incurred against a the unobligated balance from prior-year, e.g. a 3-year availability appropriation totaling $1 billion was made in FY 2013 where $0.8 billion was obligated in same FY 2013, another $0.1 billion obligated in FY 2014, with the remaining $0.1 billion incurred in FY 2015.  Agency enterprise systems cover the requirement using a"budget FY" to identify year of enactment and second "FY" field to provide for obligation/outlay reporting.  Web site data elements need to mimic that capability.
Page 27 of Section 20 of OMB Circular A-11 talks to the phased obligation situation:
"Outlays during a fiscal year may liquidate obligations incurred in the same year or in prior years.  Obligations, in turn, may be incurred against budget authority provided in the same year or against unobligated balances of budget authority provided in prior years. Outlays, therefore, flow in part from budget authority provided for the year in which the money is spent and in part from budget authority provided in prior years."
Previous comments have noted that the term "spending" -- which resonates with the general public and those unfamiliar with Federal government budgetary resource tracking -- has blurred the environment so that requires the site host to display "front and center" what the "numbers mean".  A similar term also complicates matters, namely, "expenditure" or "expended".  The stated formal definition of "obligations" warrants an accompanying 'plain English' equivalent such as "legally binding promise to make payment for goods or services".  Same approach should apply for term "outlay".  An outlay is same as a payment made (and incorporate synonym 'disbursement' perhaps that is popular with DOD elements and has some adherents in private sector).
An intermediary measure mentioned by another commentator, namely "Cost", makes sense -- and could be used as a substitute for "expended" measurement.  Some agency financial systems recognized and tracked as invoices submitted by vendors or grant recipients were processed--(Energy Department did in year's past) but had not yet been paid out.
All of these measures can be interpreted by the USSGL, which is what I believe is the "business process recommendation" articulated in DE#77..  I'm not a systems accountant but my exposure indicated that codes 4801, 4802, 4901 and 4902 substantially capture total obligations, with 4802 and 4902 track payments made against obligations; I'll leave the adjustment codes alone.  Relating SGL codes to "cost" I leave to someone with more expertise than I possess in execution accounting.
Excerpt of SGL for paid and unpaid obligations is furnished below.

AGA established a work group charged with responding to inquiries by the federal government, regarding implementation of the DATA Act. The following response is being submitted on behalf of AGA's work group, which is comprised of state, local, tribal and university practitioners from across the country. In commenting on specific data elements, our work group thought it important to indicate that - while the work group supports the standardization of definitions and reporting across federal agencies, - we are uncertain as to whether data standards will apply to entities receiving federal funds. Section5 (b)(7) of the DATA Act states that the Director has a year after submitting a report on the pilot program to "...issue guidance to the heads of Federal Agencies as to how the Government-wide financial data standards shall be applied to the information required to be reported by entities receiving Federal awards..." This provision makes it appear that, after the pilot program, some financial data standards may not be applied to information reported by entities receiving federal awards.
In addition, in order to clarify the reporting and posting responsibilities of recipients, and which data elements will be reported at the awardee and subawardee level, it would be helpful for the federal government to provide the data source for each data element. This information was included in the data model for FFATA reporting in Appendix C of the OMB Guidance for Federal Spending Transparency: Subaward and Executive Compensation Data Reporting Requirements, dated August 27, 2010.
Comment on Obligation
Depending upon which federal agency is requesting information, the reporting requirements for obligations by non-federal recipients using the Federal Financial Report, Standard Form 425, can be inconsistent between programmatic and financial reporting. The inclusion of the words "legally binding agreement" in the recommended definition may reduce the inconsistencies, if the definition of obligation is consistently applied across all agencies. In addition, the recommended definition does not address timing requirements for liquidating obligations, which does not align with closeout procedures that state obligations should be liquidated within 90 days of closure.

Wow! Lots of good comments.  My comment is easy by comparison.  Don't use pronouns when establishing data definitions.  For example, "When you place an order..."  Use proper nouns in all cases for readability.  (I'm not in government, so I don't place orders.)  It may seem a bit picky, but it helps with readability of the definitions.  It could lead to outright confusion in more complex examples; it's a good general practice.

Update 4/20/15: Thank you for your feedback on the data element obligation. We will consider your feedback as we continually assess how we can improve data definitions. You may still contribute the discussion for other data elements. Check http://fedspendingtransparency.github.io/dataelements/ to find data elements with open feedback pages.


remove traversal second attempt

Second attempt to remove traversal, this time with smaller diff (because we retain head/headOption/last/lastOption). Tests pass locally with appropriate locally published upstream.

Hi, Why do you remove traversals here?

@bbrehm are you on this?


Command mapping

Hey there, thanks for creating this gem 🙇
I've run into an issue when following the instructions in the README as the shared_path is not necessarily set correctly when you define the command mapping in the top-level scope.
Instead, what worked for me was to defer the mapping until after deploy:starting, where we can be sure the shared_path is initialized to the correct value:
namespace :deploy do
  # Add command mappings
  after :starting, :map_commands do
    SSHKit.config.command_map[:composer] = "php #{shared_path.join('composer.phar')}"
  end

  # Install composer (https://getcomposer.org/)
  after :starting, 'composer:install_executable'

  # …
end

Maybe it'd make sense to update the README and composer:install_executable task description?

Mmh 🤔 Setting up the mapping after deploy:starting wasn't such a great idea. This means that the command will only work properly when you run a deploy:* task that also invokes deploy:starting (I should've seen that).
However, as mentioned before, setting up the mapping in the top scope in config/deploy.rb breaks for me, as I am using a different :deploy_to path per stage, e.g.
# config/deploy/staging.rb
set :deploy_to, '/var/www/app-staging'

# config/deploy/production.rb
set :deploy_to, '/var/www/app-production'

When I set up the command mapping in config/deploy.rb, I get the following result:
set :application, 'app'
SSHKit.config.command_map[:composer] = "php #{shared_path.join('composer.phar')}"

Printing the mapping in a task (say maptest) and running cap staging maptest yields:
php /var/www/app/shared/composer.phar

It should be:
php /var/www/app-staging/shared/composer.phar

When I define the command mapping in the separate stage files, everything works as expected. That does mean however, that I need to duplicate the command mappings for every stage 😞
I'll probably find a cleaner solution though and post it here when I find it 🙂
Then maybe updating the instructions here could be worth it for people who run into a similar issue.
Cheers

Okay, so the following works for all my use-cases (running composer tasks during deploy but also separately):
# config/deploy.rb

stages.each do |stage|
  after stage, :commands do
    SSHKit.config.command_map[:composer] = "php #{shared_path.join('composer.phar')}"
  end
end

This defers the command mapping until all the stage variables, in particular :deploy_to, have been initialized with their final values.
Should this be mentioned in the description for the composer:install_executable task or what would be the best place for it?
I am also wondering whether this would be relevant for the general Capistrano FAQs or some place similar @capistrano?
In hindsight it makes a lot of sense, but initially I didn't think too much about the order in which the general deploy config, stage config and command mappings are initialized. I guess others might run into this too.
Thank you all for these super-helpful tools 🙇

An (more involved) alternative could also be for Capistrano to provide a complete wrapper around the SSHKit command map, which might look like the following:
# Define a command mapping with lazy initialization
command :composer, -> { "php #{shared_path.join('composer.phar'}" }

# Read command mappings
commands[:composer]
# => 'php /var/www/…'


Add database models for energy model

Describe the solution you'd like

[x] Add energy_model

name
description
ref_dataset
yearly_co2_limit

[x] Add schemas
[x] Add CRUD
[ ] Add endpoints

Additional context

[ ] Unit Test


Add at least one release, please

"dev-master" in composer.json is not the best idea.
So I whant to freeze requirements.
But your package does not have any release or tag.
Could you add at least first (1.0.0)?

@bubnovKelnik Tagged v0.1.0! Thanks. :+1:


[AutoPR frontdoor/resource-manager] [Hub Generated] Review request for Microsoft.Network to add version stable/2019-03-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6944

(message created by the CI based on PR content)


Apply heuristic to only collect APIs that are most likely .NET framework APIs

This fixes #185 by adding a filter into the dependency finder that attempts to determine whether or not a given API is a framework API by looking at the assembly it is defined in. If that assembly:

Starts with Microsoft, System, or Mono
Is signed with a known Microsoft public key token
Is mscorlib

We will include them in the request. Otherwise, the APIs are discarded.
@terrajobst  @mjrousos

At one point way back when, I compiled this list of NetFX/CLR assemblies. It's imperfect (I think there are some native things on that list and it's likely missing some other items), so don't just take it wholesale, but some observations from it:

Presentation* may be interesting for WPF things
Similarly, UIAutomation* may be interesting for WPF UIA
These may be caught by PKT checks, but some other non-system and non-Microsoft NetFX assemblies are:

WindowsBase.dll
ReachFramework.dll
WindowsFormsIntegration.dll
Accessibility.dll
CustomMarshallers.dll
SysGlobal.dll
ISymWrapper.dll
XamlBuildTask.dll
Mscorlib.Extensions.dll (this is in some CoreCLR profiles and shouldn't be built against directly, but it may not hurt to include it for completeness)

LGTM


stac-model release workflow

this addresses https://github.com/crim-ca/mlm-extension/issues/13 and I can test and make a release with this workflow once the PR is merged.
The release workflow is to make a release in the Github UI and tag it accordingly with stac-model-v or v in order to publish either the stac-model package or the JSON schema, respectively.
Description

Adds a job publish-pypi to publish.yaml to publish the stac-model package to PYPI if the tag starts with stac-model-v
adds a condition to deploy-schema (renamed from deploy) to run if tag starts with v
updates stac-model version to match what's on PYPI: version 0.1.2

Related Issue
https://github.com/crim-ca/mlm-extension/issues/13
Type of Change

[ ] :books: Examples, docs, tutorials or dependencies update;
[x] :wrench: Bug fix (non-breaking change which fixes an issue);
[ ] :clinking_glasses: Improvement (non-breaking change which improves an existing feature);
[ ] :rocket: New feature (non-breaking change which adds functionality);
[ ] :boom: Breaking change (fix or feature that would cause existing functionality to change);
[ ] :closed_lock_with_key: Security fix.

Checklist

[ ] I've read the CONTRIBUTING.md guide;
[ ] I've updated the code style using make codestyle;
[ ] I've written tests for all new methods and classes that I created;
[ ] I've written the docstring in Google format for all the methods and classes that I used.

I'm not sure why the greeting action is failing, but think it is alright to remove and we can always add something like this back in: https://github.com/crim-ca/mlm-extension/actions/runs/8928113824/job/24522932284?pr=14

@rbavery
I cant't seem to be able to update your branch with the latest main changes.
Please make sure they are applied before bumping/publishing.

@rbavery
Something we might need to have some consideration about...
Since the repository will effectively contain tag/release for both the MLM spec and the stac-model utility, the CHANGELOG might get somewhat confusing.
For example, we could have a stac-model-vX.Y.Z release to fix some parsing issue in the pydantic definitions, or the addition of new capabilities/utilities, without actually modifying the spec. Currently, I have defined bumpversion rules to automate CHANGELOG updates along the MLM vX.Y.Z tags, but nothing is done if we only update stac-model. Any thoughts on how we should handle this?

@rbavery I can't seem to be able to update your branch with the latest main changes. Please make sure they are applied before bumping/publishing.

It's already up to date with main since the latest change on main was two days ago? I'll make sure to check this again once it is ready to merge.
# rave at rave-desktop in ~/work/mlm-extension on git:stac-model-release ● [13:34:27]
→ git merge main
Already up to date.

I'm not familiar with bumpversion, I've been making CHANGELOG updates manually so I don't have a lot of insight on if bumpversion can handle version updates for two entities. Maybe we could have two different CHANGELOG files, one for the spec and one for the package? Or keep the one CHANGELOG but add in stac-model changes to the CHANGELOG manually?

Ok weird. Github's UI still displays a 'update branch' button. It's ok if you publish with it merged on your side though.
Bumpversion uses a global current_version setting, so we cannot have the two modules managed by the same configuration. We could however have 2 separate files for each case. I think a single CHANGELOG would be better to help align corresponding versions when we do apply changes to both of them for matching features.

Ok I'm fine with a single CHANGELOG. We can continue to add the stac_model changes in manually then.

Can you give a try in doing this manual update for this case?
This PR is a good example of a stac-model-only update.
I will try with https://github.com/crim-ca/mlm-extension/pull/11 which does both MLM and stac-model.

fixes #13

closing in favor of https://github.com/crim-ca/mlm-extension/pull/16


fix(typings): makes keyboardRef not required, as it is specified in docs

Description
#368 adds keyboardRef to the TypescriptTypings of the Keyboard component. But this prop is not required according to the docs, so this PR marks this prop as optional.
Checks

[x] Tests ( npm run test -- --coverage ) Coverage at ./coverage/lcov-report/index.html should be 100%

Nice catch! Thanks @goooseman, this should be live in a couple minutes with version 2.1.117.
Best,
Francisco Hodge


[Feature Request]: Correct TLSClientIdentifier?

Describe the feature / enhancement and how it would improve things
In https://github.com/bogdanfinn/tls-client/blob/master/cffi_dist/example_csharp/Requester.cs the default value for TlsClientIdentifier is FireFox110 that seems a bit diffrent to the default identifier who is used for all the other versions here.
I want to use Chrome 131 which identifier i have to use in the csharp one? Is it Chrome131 then?
Describe how your proposal will work, with code and/or pseudo-code

@JvB94 here you can see all the built in tlsClientIdentifiers as strings.
https://github.com/bogdanfinn/tls-client/blob/master/profiles/profiles.go#L10
FireFox110 is not correct you are right. correct would be firefox_110
Afaik it will fallback to default profile if you supply anything which is not implemented. Default is currently Chrome131
https://github.com/bogdanfinn/tls-client/blob/master/profiles/profiles.go#L8


Function invocation is canceled and will not be sent to the worker

What do I need to look at to resolve this exception? Is this a known bug? Since the function doesn't trigger, I am trying to figure out what to look at.
Azure functions fail to trigger intermittently with a TaskCancelled Exception. Diagnostics show the exception is coming out of runtime/worker before the function gets called.

I have a couple of Azure functions that use the following trigger signature [HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")
The functions are running on a consumption plan.
They get triggered 2-3 times a day

public class AlpacaSample
    {
        private ILogger logger;

        public AlpacaSample(ILoggerFactory loggerFactory)
        {
            this.logger = loggerFactory.CreateLogger<AlpacaSample>();
        }

        [Function("AlpacaSample")]
        public async Task<HttpResponseData> Run([HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")] HttpRequestData req)
        {
            try
            {
                this.requestData = req;
                string requestBody = await new StreamReader(req.Body).ReadToEndAsync();
                var message = $"Received a trigger {requestBody}";
                this.logger.LogInformation(message);

                // Business logic removed for brevity

                return await this.CreateStringResponse(req, "All Good");
            }

            catch (Exception ex)
            {
                string responseMessage =
                       $"Error occurrend while handling the message. Error: {ex.Message} \n {ex}";
                this.logger.LogError(responseMessage);
                return await this.CreateStringResponse(req, responseMessage);
            }

        }

        private async Task<HttpResponseData> CreateStringResponse(HttpRequestData req, string msg, HttpStatusCode httpStatusCode = HttpStatusCode.OK)
        {
            var res = HttpResponseData.CreateResponse(req);
            res.StatusCode = httpStatusCode;
            await res.WriteStringAsync(msg);
            return res;
        }
}

Full Call stack :
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<ExecuteWithLoggingAsync>d__26.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:352)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<TryExecuteAsync>d__18.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:108)
Inner exception Microsoft.Azure.WebJobs.Script.Description.FunctionInvocationCanceledException handled at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw:
   at Microsoft.Azure.WebJobs.Script.Description.WorkerFunctionInvoker+<InvokeCore>d__9.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/Workers/WorkerFunctionInvoker.cs:106)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.Description.FunctionInvokerBase+<Invoke>d__24.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/FunctionInvokerBase.cs:82)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.Description.FunctionGenerator+<Coerce>d__3`1.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/FunctionGenerator.cs:225)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionInvoker`2+<InvokeAsync>d__10.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionInvoker.cs:52)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<InvokeWithTimeoutAsync>d__33.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:581)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<ExecuteWithWatchersAsync>d__32.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:527)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<ExecuteWithLoggingAsync>d__26.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:306)
Inner exception System.Threading.Tasks.TaskCanceledException handled at Microsoft.Azure.WebJobs.Script.Description.WorkerFunctionInvoker+<InvokeCore>d__9.MoveNext:
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.Description.WorkerFunctionInvoker+<InvokeCore>d__9.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/Workers/WorkerFunctionInvoker.cs:101)

Just My Code call stack
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<ExecuteWithLoggingAsync>d__26.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:352)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<TryExecuteAsync>d__18.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:108)
Inner exception Microsoft.Azure.WebJobs.Script.Description.FunctionInvocationCanceledException handled at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw:
   at Microsoft.Azure.WebJobs.Script.Description.WorkerFunctionInvoker+<InvokeCore>d__9.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/Workers/WorkerFunctionInvoker.cs:106)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.Description.FunctionInvokerBase+<Invoke>d__24.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/FunctionInvokerBase.cs:82)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.Description.FunctionGenerator+<Coerce>d__3`1.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/FunctionGenerator.cs:225)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionInvoker`2+<InvokeAsync>d__10.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionInvoker.cs:52)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<InvokeWithTimeoutAsync>d__33.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:581)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<ExecuteWithWatchersAsync>d__32.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:527)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+<ExecuteWithLoggingAsync>d__26.MoveNext (Microsoft.Azure.WebJobs.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:306)
Inner exception System.Threading.Tasks.TaskCanceledException handled at Microsoft.Azure.WebJobs.Script.Description.WorkerFunctionInvoker+<InvokeCore>d__9.MoveNext:
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.Description.WorkerFunctionInvoker+<InvokeCore>d__9.MoveNext (Microsoft.Azure.WebJobs.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /_/src/WebJobs.Script/Description/Workers/WorkerFunctionInvoker.cs:101)

Trace
6/1/2023, 7:45:03 AM
-
REQUEST
URL: [https://******.azurewebsites.net/api/******](https://%2A%2A%2A%2A%2A%2A.azurewebsites.net/api/******)
Response code: 0
Response time: 3.1 s
6/1/2023, 7:45:03 AM
-
TRACE
FUNCTIONS_WORKER_RUNTIME set to dotnet-isolated. Skipping WorkerConfig for language: java
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
FUNCTIONS_WORKER_RUNTIME set to dotnet-isolated. Skipping WorkerConfig for language: node
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
FUNCTIONS_WORKER_RUNTIME set to dotnet-isolated. Skipping WorkerConfig for language: powershell
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
Initializing Warmup Extension.
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
Initializing Host. OperationId: 'fd2e77ef-c3b6-4a31-9d77-24c0de283e1f'.
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
Host initialization: ConsecutiveErrors=0, StartupCount=4, OperationId=fd2e77ef-c3b6-4a31-9d77-24c0de283e1f
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
Loading functions metadata
Severity level: Information
6/1/2023, 7:45:03 AM
-
TRACE
Reading functions metadata
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
2 functions found
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
1 functions loaded
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
ApplicationInsightsLoggerOptions { "SamplingSettings": { "EvaluationInterval": "00:00:15", "InitialSamplingPercentage": 100.0, "MaxSamplingPercentage": 100.0, "MaxTelemetryItemsPerSecond": 20.0, "MinSamplingPercentage": 0.1, "MovingAverageRatio": 0.25, "SamplingPercentageDecreaseTimeout": "00:02:00", "SamplingPercentageIncreaseTimeout": "00:15:00" }, "SamplingExcludedTypes": "Request", "SamplingIncludedTypes": null, "SnapshotConfiguration": null, "EnablePerformanceCountersCollection": true, "HttpAutoCollectionOptions": { "EnableHttpTriggerExtendedInfoCollection": true, "EnableW3CDistributedTracing": true, "EnableResponseHeaderInjection": true }, "LiveMetricsInitializationDelay": "00:00:15", "EnableLiveMetrics": true, "EnableDependencyTracking": true, "DependencyTrackingOptions": null }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
LoggerFilterOptions { "MinLevel": "None", "Rules": [ { "ProviderName": null, "CategoryName": null, "LogLevel": null, "Filter": "<AddFilter>b__0" }, { "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider", "CategoryName": null, "LogLevel": "None", "Filter": null }, { "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider", "CategoryName": null, "LogLevel": null, "Filter": "<AddFilter>b__0" }, { "ProviderName": "Microsoft.Azure.WebJobs.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider", "CategoryName": null, "LogLevel": "Trace", "Filter": null } ] }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
LoggerFilterOptions { "MinLevel": "None", "Rules": [ { "ProviderName": null, "CategoryName": null, "LogLevel": null, "Filter": "<AddFilter>b__0" }, { "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider", "CategoryName": null, "LogLevel": "None", "Filter": null }, { "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider", "CategoryName": null, "LogLevel": null, "Filter": "<AddFilter>b__0" }, { "ProviderName": "Microsoft.Azure.WebJobs.Logging.ApplicationInsights.ApplicationInsightsLoggerProvider", "CategoryName": null, "LogLevel": "Trace", "Filter": null } ] }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
ConcurrencyOptions { "DynamicConcurrencyEnabled": false, "MaximumFunctionConcurrency": 500, "CPUThreshold": 0.8, "SnapshotPersistenceEnabled": true }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
FunctionResultAggregatorOptions { "BatchSize": 1000, "FlushTimeout": "00:00:30", "IsEnabled": true }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
SingletonOptions { "LockPeriod": "00:00:15", "ListenerLockPeriod": "00:01:00", "LockAcquisitionTimeout": "10675199.02:48:05.4775807", "LockAcquisitionPollingInterval": "00:00:05", "ListenerLockRecoveryPollingInterval": "00:01:00" }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
ScaleOptions { "ScaleMetricsMaxAge": "00:02:00", "ScaleMetricsSampleInterval": "00:00:10", "MetricsPurgeEnabled": true, "IsTargetScalingEnabled": true, "IsRuntimeScalingEnabled": false }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Starting JobHost
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Starting Host (HostId=******, InstanceId=8f937b40-6d44-4919-******-ec66a372643a, Version=<IP_ADDRESS>99, ProcessId=5844, AppDomainId=1, InDebugMode=False, InDiagnosticMode=False, FunctionsExtensionVersion=~4)
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Generating 1 job function(s)
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Found the following functions: Host.Functions.******
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Initializing function HTTP routes Mapped function route 'api/******' [get,post] to '******'
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Host initialized (12ms)
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Host started (12ms)
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Job host started
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
HttpOptions { "DynamicThrottlesEnabled": true, "EnableChunkedRequestBinding": false, "MaxConcurrentRequests": 100, "MaxOutstandingRequests": 200, "RoutePrefix": "api" }
Severity level: Information
6/1/2023, 7:45:04 AM
-
TRACE
Executing 'Functions.******' (Reason='This function was programmatically called via the host APIs.', Id=1fd81ebd-e455-4a79-a9e8-5a02972a124d)
Severity level: Information
6/1/2023, 7:45:06 AM
-
TRACE
Worker process started and initialized.
Severity level: Information
6/1/2023, 7:45:06 AM
-
EXCEPTION
Exception while executing function: Functions.******
Problem Id: System.Threading.Tasks.TaskCanceledException at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
6/1/2023, 7:45:06 AM
-
TRACE
Executed 'Functions.******' (Failed, Id=1fd81ebd-e455-4a79-a9e8-5a02972a124d, Duration=2825ms)
Severity level: Error
6/1/2023, 7:45:06 AM
-
EXCEPTION
Exception while executing function: Functions.******
Problem Id: System.Threading.Tasks.TaskCanceledException at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
6/1/2023, 7:45:09 AM
-
TRACE
Host lock lease acquired by instance ID '3caa8b34bd20508b527345686484c415'.
Severity level: Information```

We got this problem as well, specifically The invocation request with id '' was canceled before the request was sent to the worker.

In my case

We got this problem as well, specifically The invocation request with id '' was canceled before the request was sent to the worker.

If I call the function via Postman, everything works fine. But It fails if a third party calls the endpoint. I do not have any IP restrictions. Is your case similar?

We also get this error, could it be when the function host scales down?
We've seen a host get started and immediately canceled later on.
It is annoying since it triggers error logs which we have alert rules on, would be great if this exception is handled in the worker, a 503 returned to the caller so a retry could be performed.

Hi. We are also getting this error both on HTTP and ServiceBus triggered functions. When it happens on ServiceBus triggered function, message ends up in DeadLetter queue (We use max retry count 1). It happens at random intervals and is not predictable at all.
We tried setting the Function runtime version to 4.17.3 but it did not help.

The issue is back and Function runtime 4.17.3 is no longer available

The same for me.
Locally everything works fine with func start, but once deployed to the Azure, I have this error.

Seeing this as well. Can it happen if the client has a short timeout and cancels the request during cold start?

The same for me. I'm getting a lot of these messages on my AppInsigths in Azure

Same for me, any idea when it will be fixed?

Facing the same issue on an isolated function app (mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated7.0)
The hostId trick from @fabricciotc did not change anything for me :(

@Petit-Pas  You can also try to define the FUNCTIONS_EXTENSION_VERSION on the app settings within the Azure Portal. You should settle it as dotnet-isolated

Facing the same issue. When using .NET 7 isolated, the first request with cold-start halts and throws, next requests go fine. With quick testing with a dummy application it seems that when using
using Microsoft.Extensions.Hosting;

var host = new HostBuilder()
    .ConfigureFunctionsWorkerDefaults()
    .Build();

host.Run();

on Program.cs, the error does not appear, however when changing to using ASP.NET Core integration with
using Microsoft.Extensions.Hosting;
using Microsoft.Azure.Functions.Worker;

var host = new HostBuilder()
    .ConfigureFunctionsWebApplication()
    .Build();

host.Run();

as recommended here the issue comes present

We're seeing the exact same issue @Eniemela

Facing the same issue. When using .NET 7 isolated, the first request with cold-start halts and throws, next requests go fine. With quick testing with a dummy application it seems that when using
using Microsoft.Extensions.Hosting;

var host = new HostBuilder()
    .ConfigureFunctionsWorkerDefaults()
    .Build();

host.Run();

on Program.cs, the error does not appear, however when changing to using ASP.NET Core integration with
using Microsoft.Extensions.Hosting;
using Microsoft.Azure.Functions.Worker;

var host = new HostBuilder()
    .ConfigureFunctionsWebApplication()
    .Build();

host.Run();

as recommended here the issue comes present

I use the old version with the "WorkerDefaults" and the error occurs also on my end.

This error typically happens when an HttpClient has a timeout faster than the time it takes to dispatch the request to the worker. There has been a new configuration setting added recently (not yet in production) that should give more control over these scenarios -- https://github.com/Azure/azure-functions-host/pull/9523.
I'm going to move this to our next Sprint so someone can have a look and make sure the scenarios are covered.

This error typically happens when an HttpClient has a timeout faster than the time it takes to dispatch the request to the worker. There has been a new configuration setting added recently (not yet in production) that should give more control over these scenarios -- Azure/azure-functions-host#9523.
I'm going to move this to our next Sprint so someone can have a look and make sure the scenarios are covered.

Considering the comment by @Eniemela I don't see a reason why this should be the case - when it works with ConfigureFunctionsWorkerDefaults but does not work with ConfigureFunctionsWebApplication.

The fix for this is being deployed. We'll share guidance here once the changes are out.

4.30 has been globally deployed. We'll share a link to the documentation covering the new configuration options for this once that is available.

We are currently facing what seems to be the same issue with a lot of our functions. We have the same situation where the first call of a function does not respond at all, but we are not getting the exact same error message as above. One of our functions apps has several functions that need to be called once a day and the first function called always fails after 59.9 seconds with the following error. After that failure, the function app works as expected. This seems to only happen when the function is cold starting, so it only affects function apps that are used infrequently and function apps in our test and  dev environments.
Exception while executing function: ... Result: Failure
Exception: System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.SetFunctionContextAsync(String invocationId, FunctionContext context) in D:\a\_work\1\s\extensions\Worker.Extensions.Http.AspNetCore\src\Coordinator\DefaultHttpCoordinator.cs:line 35
   at Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.FunctionsHttpProxyingMiddleware.Invoke(FunctionContext context, FunctionExecutionDelegate next) in D:\a\_work\1\s\extensions\Worker.Extensions.Http.AspNetCore\src\FunctionsMiddleware\FunctionsHttpProxyingMiddleware.cs:line 41
   at Microsoft.Azure.Functions.Worker.FunctionsApplication.InvokeFunctionAsync(FunctionContext context) in D:\a\_work\1\s\src\DotNetWorker.Core\FunctionsApplication.cs:line 77
   at Microsoft.Azure.Functions.Worker.Handlers.InvocationHandler.InvokeAsync(InvocationRequest request) in D:\a\_work\1\s\src\DotNetWorker.Grpc\Handlers\InvocationHandler.cs:line 88
Stack:    at Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.SetFunctionContextAsync(String invocationId, FunctionContext context) in D:\a\_work\1\s\extensions\Worker.Extensions.Http.AspNetCore\src\Coordinator\DefaultHttpCoordinator.cs:line 35
   at Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.FunctionsHttpProxyingMiddleware.Invoke(FunctionContext context, FunctionExecutionDelegate next) in D:\a\_work\1\s\extensions\Worker.Extensions.Http.AspNetCore\src\FunctionsMiddleware\FunctionsHttpProxyingMiddleware.cs:line 41
   at Microsoft.Azure.Functions.Worker.FunctionsApplication.InvokeFunctionAsync(FunctionContext context) in D:\a\_work\1\s\src\DotNetWorker.Core\FunctionsApplication.cs:line 77
   at Microsoft.Azure.Functions.Worker.Handlers.InvocationHandler.InvokeAsync(InvocationRequest request) in D:\a\_work\1\s\src\DotNetWorker.Grpc\Handlers\InvocationHandler.cs:line 88

This is a new issue that started occurring after updating our functions from In-Process to Isolated, and from dotnet 6 to dotnet 8. We have tested creating a new function app with a simple dummy function and that does not cause the same issue. We are currently testing to figure out what part of our project causes this issue to appear

We are also having the issue described by Adrian-Wennberg the first call of the day fails after a timeout. The invocation details show the same exception and stack trace posted above. The very first line of the user code of the function is writing a log message and that log message never gets written.
Invocation Details for first call of the day that times out:

Invocation Details for call that works:

@Adrian-Wennberg and @innominate227 - the issue you're describing looks to be different to what this issue was opened for - can you please open a new issue for what you're describing? Thanks!

One more with same issue as @Adrian-Wennberg, same upgrade path in process .net 6 to isolated .net 8. First cold start http trigger request times out.

We are getting the exact same behaviour in our http-triggered function (consumption) after we upgraded it to net8 isolated. The first request after the host has been drained times out, subsequent requests work fine until the host is drained again. When can we expect a fix for this?

I'm experiencing exactly the same around here.
Just let me share that using App Function linux-x64 runtime and setting

true
linux-x64

in the project, the issue appered to disappear.  Anyway I'm looking forward to have a solution for a Windows runtime.

OMG @efernandesvieira your fix worked for me! The first request is now running correctly. I can tell that it is working by looking the log stream but also because it is significantly slower than subsequent requests. Thanks a lot for sharing!!

We are having the same issue as described by @Adrian-Wennberg and @innominate227
The function is Isolated dotnet 8, and the first call returns the same exception as described before, while the coming calls works as expected.
@liliankasem Has there been any new updates about this issue?

Hi!
We are also experiencing the same issue on isolated model with .NET 8.
Function is on consumption plan, not used very much, there are 1 request coming in every 10 minutes and sometimes it is failing during cold start.
We have tried running function on Windows & Linux, using ASP.NET Core integration or just pure function worker and we are facing timeouts in each of these cases.
Here is some logs on Azure Function running on Windows with ASP.NET Core integration:

Successful invocation:

Timeout during host startup. Caller retried the call and it hit the same instance and passed without any further issue:

btw. this issue was also raised in Microsoft Learn: https://learn.microsoft.com/en-us/answers/questions/1609713/azure-function-fails-with-functioninvocationexcept?page=1&orderby=helpful

@filip-be @erkenP I was also experiencing the same problem and the workaroundproposed by @efernandesvieira worked for me.

I just deployed a fresh .NET Core 8 isolated function on Linux and I am seeing this as well.
Exception while executing function: Functions.GetImportantMessages Result: Failure
Exception: System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.SetFunctionContextAsync(String invocationId, FunctionContext context) in D:\a\_work\1\s\extensions\Worker.Extensions.Http.AspNetCore\src\Coordinator\DefaultHttpCoordinator.cs:line 35

I just deployed a fresh .NET Core 8 isolated function on Linux and I am seeing this as well. Consumption plan.
Exception while executing function: Functions.GetImportantMessages Result: Failure
Exception: System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore.DefaultHttpCoordinator.SetFunctionContextAsync(String invocationId, FunctionContext context) in D:\a\_work\1\s\extensions\Worker.Extensions.Http.AspNetCore\src\Coordinator\DefaultHttpCoordinator.cs:line 35

Are there any working remedies or a long term fix in progress?

@areriklq After many tests, I never saw that error on linux runtime. It was really easy to reproduce on Windows runtime. Maybe in your case the task is really being cancelled due some channel being closed or similar? Do you have any other error?

No, subsequent calls work. The function is a wrapper API for a CosmosDB database. The function method is a HTTP-Trigger for a GET endpoint. So as simple as it gets.

@areriklq Ok. Are you using 64 bits environment?

@areriklq Ok. Are you using 64 bits environment?

I am using Consumption Plan, I don't think 64bit Linux is available?
However, this the site config:
          "linuxFxVersion": "DOTNET-ISOLATED|8.0",
          "use32BitWorkerProcess": null,

I'm using  Consumption plan Y1 with linux 64 bits runtime.
From: areriklq @.>
Sent: miércoles, 8 de mayo de 2024 14:53
To: Azure/azure-functions-dotnet-worker @.>
Cc: Eduardo Fernandes Vieira @.>; Mention @.>
Subject: [EXTERNAL] Re: [Azure/azure-functions-dotnet-worker] Function invocation is canceled and will not be sent to the worker (Issue #1588)
@areriklqhttps://github.com/areriklq Ok. Are you using 64 bits environment?
@efernandesvieirahttps://github.com/efernandesvieira I am using Consumption Plan, I don't think 64bit Linux is available?
However, this the site config:
      "linuxFxVersion": "DOTNET-ISOLATED|8.0",

      "use32BitWorkerProcess": null,

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-dotnet-worker/issues/1588#issuecomment-2100511150, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6UU6XBWHAKAUJIW5RI4YSTZBIN25AVCNFSM6AAAAAAYYSFUPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGUYTCMJVGA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>Cegid est susceptible d'effectuer un traitement sur vos données personnelles à des fins de gestion de notre relation commerciale. Pour plus d'information, consultez https://www.cegid.com/fr/privacy-policy
Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de ses destinataires. Toute utilisation ou diffusion, même partielle, non autorisée est interdite. Tout message électronique est susceptible d'altération; Cegid décline donc toute responsabilité au titre de ce message. Si vous n'êtes pas le destinataire de ce message, merci de le détruire et d'avertir l'expéditeur.
Cegid may process your personal data for the purpose of our business relationship management. For more information, please visit our website https://www.cegid.com/en/privacy-policy
This message and any attachments are confidential and intended solely for the addressees. Any unauthorized use or disclosure, either whole or partial is prohibited. E-mails are susceptible to alteration; Cegid shall therefore not be liable for the content of this message. If you are not the intended recipient of this message, please delete it and notify the sender.

RuntimeIdentifier>linux-x64

@efernandesvieira According to the docs there is nothing like a Linux 32bit RID, so I guess I run 64bit already?
And PublishReadyToRun doesn't exist for .NET Core 8

I have this in the project:

true
linux-x64

And in the deployment:

Release
Linux-x64

From: areriklq @.>
Sent: miércoles, 8 de mayo de 2024 15:37
To: Azure/azure-functions-dotnet-worker @.>
Cc: Eduardo Fernandes Vieira @.>; Mention @.>
Subject: [EXTERNAL] Re: [Azure/azure-functions-dotnet-worker] Function invocation is canceled and will not be sent to the worker (Issue #1588)
RuntimeIdentifier>linux-x64
@efernandesvieirahttps://github.com/efernandesvieira According to the docshttps://learn.microsoft.com/en-us/dotnet/core/rid-catalog#linux-rids there is nothing like a Linux 32bit RID, so I guess I run 64bit already?
And PublishReadyToRun doesn't exist for .NET Core 8https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props?view=aspnetcore-8.0#publish-related-properties

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-dotnet-worker/issues/1588#issuecomment-2100596524, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6UU6XFWXVCOFUHILJ72PA3ZBITAPAVCNFSM6AAAAAAYYSFUPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGU4TMNJSGQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>Cegid est susceptible d'effectuer un traitement sur vos données personnelles à des fins de gestion de notre relation commerciale. Pour plus d'information, consultez https://www.cegid.com/fr/privacy-policy
Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de ses destinataires. Toute utilisation ou diffusion, même partielle, non autorisée est interdite. Tout message électronique est susceptible d'altération; Cegid décline donc toute responsabilité au titre de ce message. Si vous n'êtes pas le destinataire de ce message, merci de le détruire et d'avertir l'expéditeur.
Cegid may process your personal data for the purpose of our business relationship management. For more information, please visit our website https://www.cegid.com/en/privacy-policy
This message and any attachments are confidential and intended solely for the addressees. Any unauthorized use or disclosure, either whole or partial is prohibited. E-mails are susceptible to alteration; Cegid shall therefore not be liable for the content of this message. If you are not the intended recipient of this message, please delete it and notify the sender.

RuntimeIdentifier>linux-x64

@efernandesvieira According to the docs there is nothing like a Linux 32bit RID, so I guess I run 64bit already?
And PublishReadyToRun doesn't exist for .NET Core 8

PublishReadyToRun  is documented here

RuntimeIdentifier>linux-x64

@efernandesvieira According to the docs there is nothing like a Linux 32bit RID, so I guess I run 64bit already?
And PublishReadyToRun doesn't exist for .NET Core 8

Yep, supported linux is 64bits already.

RuntimeIdentifier>linux-x64

@efernandesvieira According to the docs there is nothing like a Linux 32bit RID, so I guess I run 64bit already?
And PublishReadyToRun doesn't exist for .NET Core 8

PublishReadyToRun is documented here

Thanks for the reference and trying to help out. I will make sure to test this property and report back!

I've had the same issue as mentioned above by everyone else with a project that was upgrade from .NET6 in-process to .NET8 isolated.
I've found the source of the problem in our case. The Functions project references a custom Nuget package (which references a few ASP.NET Core assemblies, see below), and if I remove that custom NuGet package from the Functions project, I no longer get the timeout on cold start.
The Nuget package that causes the issue has references to the following assemblies:

I hope that can help someone at Microsoft figure out the issue, because ideally I would like to be able to continue to use our NuGet package for our custom logger.

Removing references to the packages mentioned by @marcroussy has resolved this for me as well. .NET 8 isolated function apps running on windows consumption plan

I just wanted to chime in here that my issues completely disappeared starting May 17 18:00CET (region NorthEurope). I have done no re-deploy or change to my dotnet 8 function. My best guess is that the issues I had was due to some issues in the underlying Azure infrastructure and the maintenance window in May (BS08-PPG) solved this issue.

@areriklq I'm aligned with that. I'm trying my original project configuration, where I could reproduce the issue very easily, and now I just can't get the original error, without any tunning or packaga removal.

@adreed-msft Any chance you could open a new issue for it as requested by @liliankasem? I've been meaning to do it but I'm a bit swamped at the moment.

@adreed-msft Any chance you could open a new issue for it as requested by @liliankasem? I've been meaning to do it but I'm a bit swamped at the moment.

we are not seeing this exact traces anymore, but we are facing similar exception on another Azure Function, when the client is cancelling the request.
Could this be related #2585?
CC: @liliankasem

We've had this issue for months since migrating from .NET 6 in process to .NET 8 isolated on the consumption plan. The fix seems to be to add the environment variable WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED = 1 to the function app. Since upgrading to 64 bit process + adding this variable about a week ago, we've yet to experience the cold start issue causing a TaskCancelled Exception. Previously we've been getting this exception multiple times a day on one of our functions.
https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#website_use_placeholder_dotnetisolated

@fabiocav, @brettsam I can see that you've updated this issue - is there any update on this?

Hello.
The failure just disappeared.  Right now, I can't reproduce the issue doesn't matter the configuration I try.
Thanks.
From: Filip BeBe @.>
Sent: jueves, 19 de diciembre de 2024 12:52
To: Azure/azure-functions-dotnet-worker @.>
Cc: Eduardo FERNANDES VIEIRA @.>; Mention @.>
Subject: [EXTERNAL] Re: [Azure/azure-functions-dotnet-worker] Function invocation is canceled and will not be sent to the worker (Issue #1588)
@fabiocavhttps://github.com/fabiocav, @brettsamhttps://github.com/brettsam I can see that you've updated this issue - is there any update on this?

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-functions-dotnet-worker/issues/1588#issuecomment-2553523876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6UU6XGHE6CIB22ZPVVA5U32GKXMLAVCNFSM6AAAAAAYYSFUPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTGUZDGOBXGY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>Cegid est susceptible d'effectuer un traitement sur vos donn?es personnelles ? des fins de gestion de notre relation commerciale. Pour plus d'information, consultez https://www.cegid.com/fr/privacy-policy
Ce message et les pi?ces jointes sont confidentiels et ?tablis ? l'attention exclusive de ses destinataires. Toute utilisation ou diffusion, m?me partielle, non autoris?e est interdite. Tout message ?lectronique est susceptible d'alt?ration; Cegid d?cline donc toute responsabilit? au titre de ce message. Si vous n'?tes pas le destinataire de ce message, merci de le d?truire et d'avertir l'exp?diteur.
Cegid may process your personal data for the purpose of our business relationship management. For more information, please visit our website https://www.cegid.com/en/privacy-policy
This message and any attachments are confidential and intended solely for the addressees. Any unauthorized use or disclosure, either whole or partial is prohibited. E-mails are susceptible to alteration; Cegid shall therefore not be liable for the content of this message. If you are not the intended recipient of this message, please delete it and notify the sender.


HF2LI support

It looks like HF2LI is not supported by this package, while the other lock-ins are. Is there any reason why this model is omitted?

@franciszekjuras happy to announce that with the latest changes in main we add support for HF2. It will be released next week.
We also add support for HF2 in QCoDes for the next release


Line endings in Windows make the project can't be compiled

I executed the make test task using Windows 10 WLS. using the master branch. The expected result is a clean build, but I get:
Successfully built 899d2fed6f79
Successfully tagged agones-build:1fd9e47722
make[1]: Leaving directory '/d/Projects/go/src/agones.dev/agones/build'
docker run --rm -v /d/Projects/go/src/agones.dev/agones/build//.config/gcloud:/root/.config/gcloud -v ~/.kube:/root/.kube -v /d/Projects/go/src/agones.dev/agones:/go/src/agones.dev/agones -w /go/src/agones.dev/agones  agones-build:1fd9e47722 bash -c \
        "/root/gen-lint-exclude.sh && gometalinter --config .exclude.gometalinter.json --deadline 100s -t --skip vendor ./..."
/usr/bin/env: 'bash\r': No such file or directory
Makefile:136: recipe for target 'lint' failed
make: *** [lint] Error 127

This is because Windows uses \r\n instead of \n. If I change the line endings to LF, the error is not shown.
How can we change this behavior to make it OS agnostic? Maybe change the .gitattributes file?
References

bash\r: No such file or directory
Dealing with line endings

Potentially silly question, if we make the change for Makefile in the .gitattributes file - does that solve the problem? :smile:

I was hoping per this advice that Git would do the reasonable thing across all OS's.
If we use Makefile text eol=lf, then according to the link above:

Git will always convert line endings to LF on checkout. You should use this for files that must keep LF endings, even on Windows.

Does Make on Windows require \n?

On Windows we have users use WSL, so it should require \n. The weird thing is, it's WSL, and we all use Linux/Mac - and so if it works for us, I don't actually understand why it doesn't work for @fooock .
Actually if I test for \r\n on the Makefile, I don't find at crlf endings. I am wondering if this is something on your end @fooock ?

A thought - when you wrote:

If I change the line endings to LF, the error is not shown.

How where you changing the line endings?
And when you made the change, did that result in a git difference vs the master branch?

Just wondering if that will shed some light on things.

When I checkout the project using the Windows git executable, automatically use the \r\n line endings. I tested now what happens when I checkout the master branch using the bash git, and it works like in your envs (with \n)
@markmandel I use Intellij + go plugin. I changed the line endings of all project files, and when done, the error disappeared

https://www.jetbrains.com/help/idea/configuring-individual-file-encoding.html

When I made this change, git detect all project files as modified (the line endings).

@fooock what happens if you run:
git config core.autocrlf; git config --global core.autocrlf - see if that is false? (on Windows I mean) - it should be overwritten by the .gitattributes, but still?
Admittedly, when I was using WSL, I only ever use WSL (so I git in there as well). I wonder why windows is adding the crlf line ending on checkout? That is super weird.

Using Windows console:
Javi@FOOOCK D:\Projects\go\src\agones.dev\agones (feature/e2e)
 git config core.autocrlf
true

Javi@FOOOCK D:\Projects\go\src\agones.dev\agones (feature/e2e)
 git config --global core.autocrlf

Global flag don't show nothing (to clarify).

:man_shrugging: I've no idea at this point. Somehow Git on windows adds crlf endings on checkout.
Solution - don't use it? :smile:
Also curious - when you changed the line endings within IntelliJ - which files were marked as changed in Git? All of them, or a specific set?

Okay. I'm officially out of ideas. :sob:

In theory, git should overlook the conversion from CRLF to LF.
@fooock Would you be available for a video chat in the next few days? I'm thinking it would be good to see if we could solve this together, as Windows users are a big part of this project.

There's is also this which makes me think the configuration is correct as is.
As long as we are running all tasks within containers, the linux line ending should be fine. I suppose the tricky part is to configure one's IDE to refrain from changing the line endings to the Windows format.
Does that make sense?

Looking at this some more, I see the problem.
Presently, .gitattributes configures Git on Windows to convert all LF to CRLF when checking out code. When committing, those CRLF bytes are restored to LF.
So when a Windows user checks out Agones, Git will convert all files to have a CRLF line ending with any committed code converted back to LF line endings. That's fine for development.
However, since we're building containers and using local files (like build/build-image/gen-lint-exclude.sh), Git on Windows will have converted those local files to use CRLF line endings. But -- and here's the problem -- our current build pulls those local files with the CRLF line ending into a Linux container and then tries to run then. Hence, the problem we have above where the lint script is failing to run in a Linux context on account of its converted line endings.
So, @fooock if you don't mind being a test user, I think the pragmatic and working solution (at least for now) is to add exclusions to .gitattributes as they appear. The first would be this:
build/build-image/gen-lint-exclude.sh text eol=lf

Related PR #182


Improved USFM handling, etc.

Pull Request Test Coverage Report for Build 178

36 of 96 (37.5%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 79.776%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

webhook.py
0
1
0.0%

tx_usfm_tools/singlehtmlRenderer.py
13
72
18.06%

Files with Coverage Reduction
New Missed Lines
%

tx_usfm_tools/singlehtmlRenderer.py
1
44.91%

Totals

Change from base Build 175:
-0.4%

Covered Lines:
5353

Relevant Lines:
6710

💛  - Coveralls


[FastGen] Hot-swappable LoRA adapters?

Hey there! FastGen seems really awesome. I'm curious whether roadmap includes support for serving models with LoRA adapters? Our use case is that we have hundreds of different LoRAs we need to serve, and keeping the fully merged models live on GPUs at all times isn't feasible. It would be awesome if FastGen implemented something like S-LoRA on top of FastGen so we can serve requests from multiple LoRAs simultaneously!

Thanks for the suggestion! I don't have a concrete timeline for something like this yet, but I do think this is great feature for us to support moving forward and will work to establish a roadmap to integrate it.


avoid integer overflow when decoding large time numbers

[x] Closes #1965
[x] Tests added (for all bug fixes or enhancements)
[ ] Tests passed (for all non-documentation changes)
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

That single AppVeyor CI fail is because the py27 32bit conda environment cannot be created:
ResolvePackageNotFound:
  - cftime

I'm confused. It seems that I did exactly this a while ago

@fmaussion don't be. You are perfectly right, we worked on the same line of code, only that I was about 50 PRs earlier, hence the merge conflict.
I'll close this.


Add JSON output format

It'd be cool if there's an option to use a JSON output format compatible with https://github.com/echojc/kp so that we can pipe output from kt into kp preserving partitioning and keys, useful for testing, debugging, and transferring data between (test) clusters.

Tested this by piping messages from one topic to another:
$ ./kp --json test
{"partition":0,"key":"blubbs","message":"hellos"}

and
$ kt -json -topic test | ./kp --json test2

and
$ kt -topic test2 -offset 2:
Partition=0 Offset=2 Key=blubbs Message=hellos

Published this to https://github.com/fgeller/kt/releases/download/v1.1.0/kt-1.1.0-linux.xz
Let me know how you go :)


UI: expose fromBackup in UI for DR volumes

Steps to reproduce:

In Settings page, set Backup Target and Backup Target Credential Secret
Create a volume, attach it to a node.
Create a backup
in Backup page, click on Operation drop down for volume backup, and click on Create Disaster Recovery Volume, enter DR volume Name, and click OK.

Expected results: In volume details page for DR volume, from backup field exists and contains the volume backup used to create the DR volume

Error: from backup field doesn't exist on volume details page.

Need some design on this. FromBackup is a string, we need to expose it in a way that makes sense to the user.


multi-screen setPositionRelativeToWidget not correct

Hi,
Thanks for your great job!
When __position_relative_to_widget is not on primaryScreen, the toast will be in wrong screen.
def __get_bounds(self) -> QRect:
        # ...
        if Toast.__position_relative_to_widget is not None:
            return Toast.__position_relative_to_widget.geometry()
        # ...

i think we need a global rect here, but according to qt doc
This property holds the geometry of the widget relative to its parent and excluding the window frame

so, maybe the code should be changed to
if Toast.__position_relative_to_widget is not None:
    rect = Toast.__position_relative_to_widget.geometry()
    top_left = Toast.__position_relative_to_widget.mapToGlobal(rect.topLeft())
    return QRect(top_left, rect.size())

Hi, thanks for opening this issue.
I see your point, but I'm not able to reproduce this issue for some reason. When I use Toast.setPositionRelativeToWidget(widget) and then move the widget to another screen, the toasts do show on the correct screen. Could you please provide a minimal reproducible example so I can look into this further?

Hi, thanks for quit reply.
Here is the minimal example.
import sys

from PySide6.QtWidgets import QWidget, QApplication, QPushButton, QVBoxLayout, QLabel
from pyqttoast import Toast

class Win(QWidget):
    def __init__(self):
        super().__init__()
        self.resize(800, 600)

        layout = QVBoxLayout()

        self._label = QLabel("text", self)
        layout.addWidget(self._label, stretch=1)

        self._btn = QPushButton("click me", self)
        self._btn.clicked.connect(self._on_btn_clicked)
        layout.addWidget(self._btn)

        self.setLayout(layout)

    def _on_btn_clicked(self):
        toast = Toast()
        # FIXME: the problem is here, relative to a sub-widget
        toast.setPositionRelativeToWidget(self._label)
        toast.setDuration(5000)
        toast.setText("I am in primary screen")
        toast.show()

def main():
    app = QApplication(sys.argv)

    screens = app.screens()
    # we need two screens to reveal the bug
    assert len(screens) > 1
    screen = screens[1]

    win = Win()
    win.setScreen(screen)
    win.move(screen.geometry().topLeft())
    win.show()

    app.exec()

if __name__ == '__main__':
    main()


Switch to Tree-Sitter

It's been suggested that a switch to tree-sitter would open up editor integrations
I should investigate swapping out Pest or generating tree-sitter from pest.

I've added a grammar.js with #5679955
cc @icepuma


Reorganize project

This introduces a new project structure. It contains a workspace which should hold reference to the main framework, an example app or a playground example.
It fulfills the SPM(Swift Package Manager) file structure as well.

Project structure looks ok for me. For me it seems like EmptyContent is more like EmptyContentDisplaying, may we should change this?

EmptyContent is Content. Is does not display anything. A view/view protocol which display EmptyContent would be called EmptyContentDisplaying


Can release binary files?

First of all, thank you very much for your work!
I like the project very much, and I hope to be able to experience or let my team use it for a long time.
I don't have a QT project to build a binary file development environment.
Can you provide a compiled binary file?
Thanks again!

The files downloaded here cannot be used:
https://dl.bintray.com/groterik/qtcreator-dlang-tools/

Thanks!
I've just fixed a problem with binaries uploading. Please try them now (if you aren't using mac os, because I'm still having some issues with building dubmanager plugin there).

Thanks for fixing this issue. (-:
The windows binaries for both dubmanager and dlangeditor appear to work, as in, I can download them and Qt Creator picks them up when they are placed in Qt Creator's plugin path.
That being said, the zipfile contains three files in total: the .dll (which is required), as well as the .lib and .exp files, which are only needed if people want to link against the dll, but not for using the plugin.


Added resizeMethod to image

Hey @SiDevesh
I am using your project in an app that I am creating for a retail giant in South Africa. Awesome project, really like what you have done.
One issue I came across is that when the image in cardImage is really large (in my case the user uploads an image from their device) this causes the app to lag on certain devices. I have added resizeMethod="resize" to downsize the image and avoid the lag.
Docs can be found here: https://facebook.github.io/react-native/docs/image.html#resizemethod
Cheers

Hi, Glad you find this useful. Thanks for the PR.


Upgrade to video.js font 3.0

fixes #279

Coverage remained the same at 87.5% when pulling 175926ff017e80ba97abe4eee84fbeddcc0e33ed on font-279 into f4d58fdbae40e230132eae9133766da43b642981 on master.


Dimming functions of Lutron Aurora?

With the recent 4.0.x versions, the Lutron Aurora is now supported, and the button on it can be programmed through the Hue Buttons node, which works well.
However, the dimming functions on the dial can not be used, which is too bad, and basically degrades the device to be a smart button.
So my request is to add support for the rotary of the Lutron Aurora.

It looks like the rotary is not a different button on the same logical device, but a different logical device instance. If i look in the All4Hue app which i sometimes use to manually edit rules, it will list 2 instances for each aurora, one device listed as 'Switch' in the Hue Switches section, the other listed as 'Hue Rotary Switch' in the Friends of Hue Switches section, similar to how sensors are also split in 3 ways, as motion/light/temperature devices.
I'll see if i can get some info on how it is exposed through ClipV2, but that will take me some time, so i will get back on that.
I couldn't purchase these rotary switches here in the Netherlands either, but i have ordered them from USA through amazon.com. Since they are battery operated, they work just fine here in Europe, of course you have to be a little bit creative to mount them, since we don't have the US switches for which they were designed. A bit of double sided tape will do the job just fine.

When i monitor the ClipV2 events as is shown in the example curl command here:
https://developers.meethue.com/develop/hue-api-v2/core-concepts/
Then i do notice incoming button pressed events:
id:<PHONE_NUMBER>:0
data: [{"creationtime":"2022-01-18T00:04:57Z","data":[{"button":{"last_event":"initial_press"},"id":"4e616d88-342c-4ab4-b4b7-5a31d743d982","id_v1":"/sensors/158","owner":{"rid":"6521cd00-592d-4843-a22b-87bbc9b03457","rtype":"device"},"type":"button"}],"id":"d68d6be2-2764-4cec-9159-c5a934d30f58","type":"update"}]
However when i turn the dial to dim up/down, no events are reported here. This suggests that Clip V2 API currently does not expose the rotary events through the event interface. That is really too bad, will need to address this with Signify then.
Will get back to this when i know more.

Could not get an official answer to this question, unofficial sources indicate that this may become available with the next update, but no timeline was given.

It seems my bridge is now reporting rotary events for the Lutron Aurora device:
id:<PHONE_NUMBER>:0
data: [
{
"creationtime": "2022-10-06T22:49:57Z",
"data": [
{
"id": "77146cc9-d975-4b1d-bf54-c782bd7e302a",
"id_v1": "/sensors/62",
"owner": {
"rid": "6e84a79c-220e-4d28-8dab-bdf08e4afba5",
"rtype": "device"
},
"relative_rotary": {
"last_event": {
"action": "start",
"rotation": {
"direction": "clock_wise",
"duration": 400,
"steps": 112
}
}
},
"type": "relative_rotary"
}
],
"id": "348c0573-209d-4b51-a8f2-3e67b69f27d3",
"type": "update"
}
]


CAMEL-20800: Use cloudant instead of LightCouch

Description
Remove LightCouch since the library is no longer maintained in favour of cloudant. The code can be improved (a lot), I tried my best to keep the component backward-compatible (Gson usage instead of cloudant Document mostly), I think it is worth to deprecate the actual API and refactor the component to better use cloudant.
Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

Yeah it would be good to update and improve the component as you suggest also.

Oh you need to build camel-catalog and dsl as well to have changed files included in this PR


Error after update from 1.5.3 to 1.5.6

HI,
after update from 1.5.3 to 1.5.6 the following code doesnt work.
Collection definition
Images = new FilesCollection(
  debug: false
  collectionName: 'images'
  allowClientCode: true
  storagePath: '/srv/http/images'
  onBeforeUpload: (file) ->
    # Allow upload files under 10MB, and only in png/jpg/jpeg formats
    if file.size <= 10485760 and /png|jpg|jpeg/i.test(file.ext)
      true
    else
      'Please upload image, with size equal or less than 10MB'
)

and upload
  events: 'change input': (e, template) ->
    if e.currentTarget.files and e.currentTarget.files[0]
      file = e.currentTarget.files[0]
      result = Images.insert(
        file: file
        onUploaded: (error, fileObj) ->
          if error
            sAlert.error 'Error during upload: ' + error
          else
            sAlert.success 'A "' + fileObj.name + '" kép sikeresen feltöltve'
          return
        streams: 'dynamic'
        chunkSize: 'dynamic')
      @fileId result.config.fileId
    return

The error message is:
Error during upload: Error: Please upload image, with size equal or less than 10MB [403]
But of course the file less than 10MB.
Are there something new in backward compatibility? I've checked the History.md but I haven't found any.
Before update everything was OK.
Thanx
Pal

Yes, it was changed a while ago, from the docs (config.onBeforeUpload "comment" column):

Because sending meta data as part of every chunk would hit the performance, meta is always empty ({}) except on the first chunk (chunkId=1) and on eof (eof=true)

OK thank you very much.

You're welcome @palpinter


Storage

One of the first things I tried to improve and failed was the way storage was handled, a few observations:

For every save, read or delete it run hasStorage every time you save something even though it's probably something that could be checked once (probably minor...)
You could bind the changing of the fields to update storage like Mozilla's Web Storage Demo
Are you using the store for those that don't support localStorage and for other purposes?
If storing multiple values it worth stringifying the JSON object?
Potentially use jStorage, the PubSub side of it sounds interesting. Disclaimer: I've never used it but the support back to IE7 caught my eye.

I haven't done anything with it yet and if using ADN (files?) to store these settings it might not be worth the effort.

Let's see ...
The hasStorage() check looks at window.localStorage to see if it exists, so storing some sort of value would be just as fast as asking the browser again, I think. At this point it's not something I'm very worried about.
An earlier version of Nice did make use of a similar idea to Mozilla's Web Storage, but it had some problems with IE so I stopped and went back to something a little simpler. Perhaps  was doing it wrong, though.
Yes, window.store is used for non-persistent storage on all browsers. Browsers that do not support localStorage will also use window.store for all its information as well. Unfortunately, this means refreshing the site will lose all a person's information, including preferences.
I considered stringifying JSON objects, but am not sure if the constant string/unstring processing time would be worth the hassle. It's something I'd like to investigate at some point, though.
jStorage looks to have been replaced with something that looks very similar to what Nice is already doing, albeit in a more sophisticated manner. I wonder if there would be noticeable gains by going this route ...
Thanks for the thoughts, though. At this point I am not sure if storage needs to be replaced with something else. that said, I would be happy to entertain the idea if a strong enough case is made :)

I guess I always saw cookies as the natural fall back for localStorage, which improves the experience for older browsers somewhat. I suspect that's what jStorage is using to get the wider support. The new version doesn't support IE7 and Firefox 3 which might be not be a deal breaker.

I've had issues with JavaScript writing (and editing) persistent cookies, so have avoided doing so. There are a few things that I would like to see remain persistent, such as the items that use readStorage/writeStorage, so I am certainly open to options :)

I might have look at them and the support side of it. I think if it were to be used then it would be worth adding a function somewhere to clear the cookies set, it's annoying having to do it for all sites.

This issue seems to have been resolved with a recent merge. Closing ticket.
Thanks again, Matt :)


Feat/improvements

Related to https://github.com/ghostiam/protogetter/issues/1.

Hello!
First of all, I want to say that I did not set out to rewrite your project. And of course not every linter gets such a complex review, I just liked your linter idea 🙂
I wanted to show what I meant in my comments. You can accept all or some or nothing. Maybe you can get some inspiration.
The main idea – KISS.
Comments to my commits:

Used full message in tests instead of mask. Otherwise it hides bugs, confuses test readers (like me), and prevents contributions to your code (how do I make sure I don't break anything?). critical
(p.s. if desired, you can go to test generation so as not to escape messages by hand, but use regexp.QuoteMeta)

Changed message into a more grammatically correct form (from my point of view). I removed the quotes so that there is no conflict with string literals (otherwise we get escaping in the message). nitpicking, cosmetic

Simplified the code to the point of impossibility. As a result, the diagnostric message is now focused on a specific selector. Ues, it produces multiple messages for the chain of getters, but chain looks like a rare case that is still covered by --fix. nitpicking, cosmetic

Ignore only protoc-generated files. Why?

Because sometimes people write custom generators around proto-messages and your linter could be useful in this case.
Analyzed code should be controled by golangci-lint (look at --skip-dirs-use-default list) by max. Also, you should not parse all the comments in the file, otherwise you can skip a regular file critical

Also:

removed useless comments (we should write self-document code)
removed extra pointers

Further comments I will leave in issue.
Thank you for your patience! 💪

Hello, thanks for the PR.
Now the linter works a little differently from how it was supposed to work.
Previously, if a correction could be suggested in one line, that was done.
Now we have more unnecessary messages.
Example:
_ = t.Embedded.Embedded

Previously there was this output:
avoid direct access to proto field t.Embedded.Embedded use t.GetEmbedded().t.GetEmbedded() instead

Now we have 2 different outputs.
avoid direct access to proto field t.Embedded.Embedded, use t.Embedded.GetEmbedded() instead
avoid direct access to proto field t.Embedded, use t.GetEmbedded() instead

Which, in my opinion, creates a lot of noise and makes it difficult to fix manually, and the more access to nested messages, the worse the output will be...
Do you have a solution to this problem?

Please reread more carefully my message above.
p.3

This is a very common case in my projects, so I do not agree with the statement that the case is rare.
Not everyone uses autofix, so seeing a lot of messages will be annoying for them.
Even I initially launch the letter without autofix, since I once ran into a bug that destroyed my work.

As you wish.
The most part of PR is suggestion from me, not requirement.
I specially divided it into commits so that you can reuse them easily.
Feel free to close PR and return back to critical points in the checklist.
Or you could try to improve this with chain handling.

You can accept all or some or nothing. Maybe you can get some inspiration

Thanks!

Yes, you've given the impetus to rewrite and test it better.
I'll accept your corrections, except the one that breaks the behavior.
Thanks for the good ideas, I'll think about how to change the linter to make the code simpler.
One question: do I understand correctly, in order to accept only 3 out of 4 commits from PR, I just need to cherry-pick?

Or is it probably easier to accept all commits and then roll back one of them? I'm just not sure that cherry-peak, github will understand how to accept PR...

I separated not-breaking part for you, mate
https://github.com/ghostiam/protogetter/pull/3

Thank you very much!


Make fuzzer_output/* available from Jenkins

uri_fuzzer at least is generating new corpus entries right now, it'd be nice to be able to grab them.

Wasn't that done ? They should be artifacts available in Jenkins.

Yep, there are: https://grpc-testing.appspot.com/view/Fuzzers/job/gRPC_fuzzer_client/


Encrypt ssn workaround

Using actions to encrypt and decrypt SSN
PT#184463988

@lkemperman-cfa I'd be comfortable merging this now since it doesnt do anything without the SSN input. I think acceptance for both tickets can be tested on #38. What do you think?


Click a recording to select it

What

Closes https://github.com/rerun-io/rerun/issues/4647
Closes https://github.com/rerun-io/rerun/issues/4649

You can now click a recording to select it (show info about it in the selection panel).

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Blocked on having a "Store" icon