text:
lock table?

$xxxxx= $this->em->getRepository('AppBundle:xxxxxx')->findOneBy([
      'xxxx' => $xxxx,
      'xxxx' => $xxxxx
]);
if ($xxxxx== null) {
    insert .....
}

my requirement is that if the result is empty, the data will be inserted and the data will remain unique, but the above method will not work.
when the amount of access is high and the concurrency is high, return null for many people
causing data to be inserted many times, data cannot be unique, and then error.
I want to use the lock table, but I don't know how

You want to set your transaction isolation level to serialized and then
run the entire operation in a transaction: this will prevent shadow writes
at some write performance cost.
On 12 Jun 2017 06:48, "imsheng" notifications@github.com wrote:

$xxxxx= $this->em->getRepository('AppBundle:xxxxxx')->findOneBy([
'xxxx' => $xxxx,
'xxxx' => $xxxxx
]);
if ($xxxxx== null) {
insert .....
}
my requirement is that if the result is empty, the data will be inserted
and the data will remain unique, but the above method will not work.
when the amount of access is high and the concurrency is high, return null
for many people
causing data to be inserted many times, data cannot be unique, and then
error.
I want to use the lock table, but I don't know how
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/issues/6497, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakFy-UwbBiTNLZ46gt_DDgCvVsMR3ks5sDLT7gaJpZM4N2oN9
.

authors: Ocramius imsheng


text:
XML Schema Definition lifecycle-callbacks marked as invalid

Bug Report
When using XML to define the entities some of the schema definition seems to be invalid despite orm:validate-schema runs green and creating/updating schema is also working.
Current behavior
<lifecycle-callbacks> marked with following error:
Invalid content was found starting with element 'lifecycle-callbacks'.
One of '{
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":field,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":embedded,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":one-to-one,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":one-to-many,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":many-to-one,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":many-to-many,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":association-overrides,
  "http://doctrine-project.org/schemas/orm/doctrine-mapping":attribute-overrides,
  WC[##other:"http://doctrine-project.org/schemas/orm/doctrine-mapping"]}' is expected.

How to reproduce
<doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
                    http://raw.github.com/doctrine/doctrine2/master/doctrine-mapping.xsd">

  <entity name="User" table="users">
   <!-- ... -->
    <lifecycle-callbacks>
            <lifecycle-callback type="preUpdate" method="onPreUpdate"/>
            <lifecycle-callback type="prePersist" method="onPrePersist" />
        </lifecycle-callbacks>
  </entity>

</doctrine-mapping>

Expected behavior
Markup should be valid.

orm:validate-schema acts on the final metadata, after metadata has been loaded, so it only looks for things like duplicate definitions, or missing association mappings.
As for the bug you reported: https://github.com/doctrine/doctrine2/blob/v2.6.2/doctrine-mapping.xsd#L177
I suggest you point the XSD at vendor (local path) instead of the raw.github.com URI, since master is not stable.

source: gharchive/issue

authors: Ocramius crtl

license: mit

license_type: permissive

license_source: bigquery


text:
[DOCUMENTATION] Update tests README

From #5620
I've done a complete rewrite at best of my knowledge, if anything here is not right, please review and comment, thanks!

I think this is ready to be merged..

Totally missed this - merging. Thanks @Jean85!

source: gharchive/pull-request


text:
Regression with routes in IE6

In Backbone 0.3.3, the Controller routes specs passed.
In Backbone 0.5.3, Router spec 67 fails. (They do pass in IE7 and IE8)

confirmed in IE6

@tbranyen informed me that Backbone.js only supports IE7...
BUT this isn't clearly documented anywhere, so we need to fix that. tagging this ticket as "documentation"

I'm inclined to let sleeping dogs lie unless we get more complaints -- I think that folks developing JavaScript-heavy web applications and targeting IE6 are very few and far between.

@jashkenas Agreed. The issue was worth noting, but not important enough for me to provide a fix.

authors: deleteme jashkenas wookiehangover

repo: documentcloud/backbone

license: MIT

license_source: github-api


text:
GetRecipientView REST Error ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE

I am trying to integrate DocUSign embedded signing for my application, however, every time I try to execute the function GetRecipientView I get the REST error ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE.
Everything is returning true for result up to the point where GetRecipientView is called and if I modify the code below to comment out the line where it calls GetRecipientView I get the SenderView just fine but I need a SignerView.
I am trying to work off an existing template that I made in the developer center.
// user credentials
                Account account = new Account();
                account.Email = AccountEmail;
                account.Password = AccountPassword;

                // make the login call (retrieves your baseUrl and accountId)
                bool result = account.Login(); //result returns true
                if (!result)
                {
                    return BadRequest("Login API call failed for user" + account.Email + ".\nError Code:  " + account.RestError.errorCode + "\nMessage:  " + account.RestError.message);
                }

                // create envelope object and assign login info
                Envelope envelope = new Envelope();
                envelope.Login = account;
                envelope.Status = "sent";
                // use an existing server template
                envelope.TemplateId = TemplateId;

                // add one signer to a template role identified by roleName
                envelope.TemplateRoles = new TemplateRole[]
                {
                    new TemplateRole()
                    {
                        email = RecipientEmail,
                        name = RecipientName,
                        roleName = TemplateRoleName,
                        clientUserId = "101"
                    }
                };

                // create a new DocuSign envelope (i.e. server side)
                result = envelope.Create(); //result returns true

                // generate the recipient view token
                result = envelope.GetRecipientView(); //returns false, Rest Error = ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE

if (!result)
                {
                    if (envelope.RestError != null)
                    {
                        return BadRequest("Error code:  "+ envelope.RestError.errorCode + "\nMessage:  " + envelope.RestError.message);
                    }
                    else
                    {
                        Console.WriteLine();
                        return BadRequest("Error encountered retrieving signing token, please review your envelope and recipient data.");
                    }
                }
                else
                {
                    // open the recipient view (SenderViewUrl field is re-used for the recipient URL)
                    return Ok(envelope.SenderViewUrl);
                }

Is this a known issue or am I missing something?

@robertWeller did you figure it out? I believe you need to send the envelope first before you can get a recipientView. I see you closed this so I hope you're all set, if not - feel free to ask more questions.

@InbarGazit What function would you use to send the envelope to enable the signer to sign?
I'm trying to set up an Iframe on a page that would generate the signer window.

well, you can either create the envelope in "Sent" status right away or you can use UpdateStatus() to change it to sent status after you created it. let me know if you want a code snippet for this

@InbarGazit After I instantiate the envelope object I set the Account and Status.
Using Visual Studio 2015 I can see the Status property is persistent after the Create is executed.
Is it case sensitive as I have it as "sent" and not "Sent"

lower case is correct.
do you see the envelope if you go to DocuSign? is it in "Draft" mode?
I suspect because it's a template you may need to do this in 2 phases. Create it first and then send it
You can use UpdateStatus() (make sure the status is still "sent") after it was created.

I do see the envelope and it is in a "Waiting For Others" mode with the correct recipient information which I typed in off my page.

oh, ok, so it is sent, I was wrong. this is a different issue.
OK, so if it's waiting for others, you cannot sign it. Do you want to provide someone else the ability to sign it? for that - you'll need to either have their login information or use embedded signing which require to provide clientUserId for the recipients.
can you explain a bit more what you're trying to do?

I'm trying to do embedded signing.
Under template roles I am assigning a new template role which has a clientUserId of 101.

did you try to use the GetEmbeddedSignerView() on the Envelope object?

That was it, I had to make a Signer object which I cloned the information from Template Role I created.
Thank you for help, very helpful. :triumph:

no prob, anytime.

authors: InbarGazit robertWeller


text:
General comments

Please use this issue thread for general comments about the JSON to SDK tool.
Open new issues for specific problems or questions.

Thank you.

repo: docusign/json-to-sdk


text:
(18,,)+ NEW S.E.X@PORN@VIDEOS]*Shocking Akshra Singh Mms Leaked Video Original Video Link Akshra Singh Leaked Video Viral On Social Media X TikTok Trending

21 seconds ago
L𝚎aᴋed Video Hot Akshara Singh MMS Original Video V𝐢ral Video L𝚎aᴋed on X Twitter Telegram
🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
..
🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
..
[-𝐅𝐔𝐋𝐋-𝐕𝐈𝐑𝐀𝐋-]— Actor Akshara Singh Video Original Video Link Actor Akshara Singh Video V𝐢ral On Social Media X Now [1U2M3N]
[-wᴀTCH-]— Actor Akshara Singh Video Original Video Link Actor Akshara Singh Video V𝐢ral On Social Media X Trending Now
[-wᴀTCH-]— Actor Akshara Singh Video Original Video Link Actor Akshara Singh Video V𝐢ral On Social Media X Trending Now
[-wᴀTCH-]— Actor Akshara Singh ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wᴀTCH-]— Actor Akshara Singh ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wᴀTCH-]— Actor Akshara Singh Video Original Video Link Actor Akshara Singh Video V𝐢ral On Social Media X Trending Now
Actor Akshara Singh Original Video video took the internet by storm and amazed viewers on various social media platforms. Actor Akshara Singh, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aᴋed Video Actor Akshara Singh Original Video V𝐢ral Video L𝚎aᴋed on X Twitter
Actor Akshara Singh Original Video video oficial twitter
L𝚎aᴋed Video Actor Akshara Singh Original Video V𝐢ral Video L𝚎aᴋed on X Twitter..
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
..
🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶 Akshara Singh L𝚎aᴋed Video V𝐢ral Video
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
### 𝖶𝖺𝗍𝖼𝗁 🟢 ➤ ➤ ➤ 🌐 𝖢𝗅𝗂𝖼𝗄 𝖧𝖾𝗋𝖾 𝖳𝗈 𝗅𝗂𝗇𝗄 (𝖥𝗎𝗅 𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇𝗄)
.
.
.
### 🔴 ➤► 𝖣𝖮𝖶𝖭𝖫𝖮𝖠𝖣👉👉 (𝖥𝗎𝗅𝗅 𝖵𝗂𝗋𝖺𝗅 𝖵𝗂𝖽𝖾𝗈 𝖫𝗂𝗇 𝗄)
.

.
.
.
.
.

repo: doczjs/docz


text:
🛑 Cheapmeat is down

In d0e4cb2, Cheapmeat ($CHEAPMEAT_URL?$BF) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cheapmeat is back up in cc25ae6.

repo: dogchef-be/uptime-monitor


text:
named files must be .go files: dogechain

When running the command go build main.go  dogechain  on go version 1.8.5 i got this issue:
named files must be .go files: dogechain

go.mod already defines the go build version: 1.16.
Update your go version please.

authors: DarianShawn dlpigpen

repo: dogechain-lab/dogechain


text:
feat(katana): db storage intergration

Depends on #1436
This PR adds persistent db as one of the available options for katana storage implementations, along with in-memory and forked db.

Adds --db-dir <PATH> CLI arg. for specifying where the DB directory will be located.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (dev/katana@c6b29da). Click here to learn what that means.

Additional details and impacted files
@@              Coverage Diff              @@
##             dev/katana    #1440   +/-   ##
=============================================
  Coverage              ?   68.50%
=============================================
  Files                 ?      220
  Lines                 ?    21690
  Branches              ?        0
=============================================
  Hits                  ?    14858
  Misses                ?     6832
  Partials              ?        0

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

authors: codecov-commenter kariy

repo: dojoengine/dojo


text:
(Flowbroker/GUI Notification) I wanna using channel to see my notifications

I'm submitting a ...

[ ] bug report
[ ] feature request
[X] support request

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
I wanna see my notifications on GUI interface

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?
I should see all my notification in just one location.

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Version: 0.4.2
Environment: docker-compose
Operating system: Ubuntu 16.04 LTS 64

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Hello.
I tried to follow this:

Device model node

Interrupt node

Model node

Notification node

But It is not working to me.

I am not sure if there are some problem in my configuration, because It is not working yet.
In my flow I am using:

Nodes:
My "evento dispositivo" was configured like:

My "modelo" was configured like:

My "notificação" was configured like:

I sent this message:

But I did not have a answer:

Hi Daniel, try to configure this way:

Now, It is working very well.
My sincerely regards.

authors: betefaber danielnunesdeoliveira

repo: dojot/dojot


text:
[k8s] Upgrate Kubernetes Version to 1.18

I'm submitting a ...

[ ] bug report
[ ] feature request
[ ] support request

Do you want to request a feature or report a bug?
feature

What is the current behavior?
The supported version of kubernetes is 1.17

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?
Support for kubernetes version 1.18

What is the motivation / use case for changing the behavior?
The current version of kubernetes is 1.20

Please tell us about your environment:

Version: 0.2.x
Environment: [kubernetes, docker-compose, standalone]
Operating system: [Ubuntu 16.04, Fedora 28, Ubuntu on VirtualBox (Windows 10), etc.]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Analysed: It should be handled for a future release (after 0.6.0).

Analysed: It should be handled for a future release (after 0.6.0).

authors: andersonluisribeiro rascaraficci


text:
[Theme Request] Genshin Characters will be soooo fantastic

Who/What do you want to be featured?
Characters from the famous Genshin Impact game

What do they look like?

This is Hutao from Liyue

This is Yae Miko from Inazuma
...and so many incredible character designs
What type of theme?

[ ] Light themes
[ ] Dark themes

Additional Information (Optional)
I introduced Doki theme for some of my colleagues and they loved it at the first sight. Additionally, they asked me so much that why it doesn't include Genshin Impact themes so far. :>

why it doesn't include Genshin Impact themes so far

Ah, that answer is simple, it's because I haven't played it. So I don't know who best girl is. I'll keep my eyes open, thanks for sharing!

So I don't know who best girl is

It depends on the current meta lol

authors: Unthrottled justalemon tori4582

repo: doki-theme/doki-master-theme


text:
README: fixed nvim-web-devicons typos

nvim-wev-devicons -> nvim-web-devicons

Thanks!

authors: richardhbtz vladimir-popov

repo: dokwork/lualine-ex


text:
[Viewer App] Streaming stats are not shown on viewer app

Streaming stats are not shown on viewer app.
STEPS:

Open the Publisher App
Go live with Camera source
Open the Viewer App
Click on stream stats icon on Viewer App
Stream stats are not shown

Regression: YES
Branch: Int Branch: int-issue-145-multisources
Environment:  MAC/Chrome
https://user-images.githubusercontent.com/110803586/219251785-1b4bdaa5-4abc-4e45-8471-114dcc2a9821.mov

@jackshen
When the Publisher is streaming with Camera source only and simulcast ON, on the viewer app viewer can see only Auto option under Quality dropdown. However on the Publisher App, it shows that for the given stream there are multiple qualities available.
On the viewer app, multiple quality options are shown with multiple sources but not with the single source (camera/local file/screen).
Please fix this.

Verification Status: PASSED
Branch: int-issue-145-multisources
Environment: MAC/Windows, Chrome/Edge
Date: Feb 21, 2023
Notes: Stream info stats are shown on viewer app for single source as well as with multiple sources.


text:
[auto-bump] dependency by PavelSafronov

:coffee: An Automated Dependency Version Bump PR :crown:
Initial Changes
The initial changes contained in this PR were produced by go geting the dependency.
$ cd ./go
$ go get github.com/dolthub/<dependency>/go@<commit>
$ go mod tidy

Before Merging
This PR must have passing CI and a review before merging.
After Merging
An automatic PR will be opened against the LD repo that bumps the bounties version there.

This PR has been superseded by https://github.com/dolthub/bounties/pull/1316

repo: dolthub/bounties


text:
[auto-bump] dependency by max-hoffman

:coffee: An Automated Dependency Version Bump PR :crown:
Initial Changes
The initial changes contained in this PR were produced by go geting the dependency.
$ cd ./go
$ go get github.com/dolthub/<dependency>/go@<commit>
$ go mod tidy

Before Merging
This PR must have passing CI and a review before merging.
After Merging
An automatic PR will be opened against the LD repo that bumps the bounties version there.

This PR has been superseded by https://github.com/dolthub/bounties/pull/817


text:
How to configure root url in asp.net 5 (vnext)

In previous version of Swashbuckle, for asp.net web api 2 there is the "RootUrl" extension method that adds the capabilite to customize the root url.
httpConfiguration
    .EnableSwagger(c =>
        {
            c.RootUrl(req => GetRootUrlFromAppConfig());

So, when testing my application in localhost (http://localhost:63563/swagger/ui/index.html), everything works fine, but in staging (or production) my url becomes http://my-app.com/ api /swagger/ui/index.htm.
I've done a lot of research, but i can´t found anything usefull from my case...
Is it really an issue of this version? Can anyone help me on this?

Possible in beta902 via special filter that has request context. See below for an example:
https://github.com/domaindrivendev/Ahoy/blob/master/test/WebSites/Basic/Startup.cs#L74

Should be resolved in beta902

authors: RichardSilveira domaindrivendev

repo: domaindrivendev/Ahoy


text:
Swashbuckle.AspNetCore.Cli won't install under netcoreapp3.1

Thanks for contributing to Swashbuckle.AspNetCore! As per the contributing guidelines, please adhere to the following rules of thumb before submitting your issue:
I get the following message when attempting to upgrade to Swashbuckle.AspNetCore.Cli, and I understand the error. When should we expect the support for .NET Core 3.1?

Severity	Code	Description	Project	File	Line	Suppression State
Error	NU1202	Package Swashbuckle.AspNetCore.Cli 5.4.1 is not compatible with netcoreapp3.1 (.NETCoreApp,Version=v3.1). Package Swashbuckle.AspNetCore.Cli 5.4.1 supports: netcoreapp2.1 (.NETCoreApp,Version=v2.1) /

If it's not a bug report, feature request or PR, don't submit it here. Post to Stackoverflow instead.
If your issue is specifically a UI concern, don't submit it here. Post to the swagger-ui repo.
For bug reports, specify the version your using and provide clear repro steps.

The CLI component is needs to be installed as a .NET Tool as opposed to a project reference. If you follow the installation steps from the readme, it should work against an app targeting netcoreapp3.1 without issue. I've verified this myself locally. Please try that if you haven't done so already and let me know how it goes.

I followed the steps located here.
After installing the tool I issued the following command and got an error:
dotnet swagger tofile --output MyProject\wwwroot .\ MyProject\bin\Debug\netcoreapp3.1\MyProject.dll V1
I checked the file location and the C:\Users\[USERNAME]\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll does exists.
dotnet : Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'C:\Users\RManesiya\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll'. The located assembly's manifest definition does
not match the assembly reference. (0x80131040)
At line:1 char:1
+ dotnet swagger tofile --output MyProject\wwwroot .\MyPro ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Unhandled excep...e. (0x80131040):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

File name: 'C:\Users\[USERNAME]\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll'

Same issue here and same steps as @RManesiya

I followed the steps located here.
After installing the tool I issued the following command and got an error:
dotnet swagger tofile --output MyProject\wwwroot .\ MyProject\bin\Debug\netcoreapp3.1\MyProject.dll V1
I checked the file location and the C:\Users\[USERNAME]\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll does exists.
dotnet : Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'C:\Users\RManesiya\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll'. The located assembly's manifest definition does
not match the assembly reference. (0x80131040)
At line:1 char:1
+ dotnet swagger tofile --output MyProject\wwwroot .\MyPro ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Unhandled excep...e. (0x80131040):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

File name: 'C:\Users\[USERNAME]\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll'

Same issue here and same steps as @RManesiya

I followed the steps located here.
After installing the tool I issued the following command and got an error:
dotnet swagger tofile --output MyProject\wwwroot .\ MyProject\bin\Debug\netcoreapp3.1\MyProject.dll V1
I checked the file location and the C:\Users\[USERNAME]\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll does exists.
dotnet : Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'C:\Users\RManesiya\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll'. The located assembly's manifest definition does
not match the assembly reference. (0x80131040)
At line:1 char:1
+ dotnet swagger tofile --output MyProject\wwwroot .\MyPro ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Unhandled excep...e. (0x80131040):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

File name: 'C:\Users\[USERNAME]\.nuget\packages\swashbuckle.aspnetcore.cli\5.4.1\tools\netcoreapp2.1\any\dotnet-swagger.dll'

Same issue here and same steps as @RManesiya

Please upgrade your Swagger libraries to latest version or 5.4.1 which same as your CLI. I can successfully generate swagger.json after upgrade. Have good luck 😉

Closing in favor of #1699, which captures all of the outstanding compatibility issues. That issue is being addressed as a top priority

authors: RManesiya domaindrivendev hiyangw


text:
Info.Description "_" will be replaced by "_"

Hi, inside my QA System I'd like to display the logging folder:
var path = "C:\\inetpub\\logs\\_dev\\";
options.SwaggerDoc("v1",
    new Info
    {
        Title = "Test WebApi",
        Version = "v1",
        Description = $"LoggingPath: {path}"
    });

But the index.html will display the following :-(
Test WebApi (v1)
/swagger/v1/swagger.json
LoggingPath: C:\inetpub\logs_dev\

That's a weird one alright! However, it looks to me like it might be a swagger-ui issue as opposed to a Swashbuckle issue. If you look at the Swagger JSON being returned by Swashbuckle - it looks correct, so the issue appears to be isolated to the UI rendering.
So, I would suggest you post an issue to that repo instead.


text:
Customize the same schema in both respone and request.

Not too sure if this is the right place to ask this question but hi!
I currently use the same schema for both the request parameter and the response but I need to modify the two in different ways (removing certain properties).
Is there a way to apply a schema filter to only request parameters and not have the filter apply itself to responses even though both are the same type?

This is really a dup of #479.
Swagger Schema's are created per Type - they have no knowledge of where the type is being used (i.e. request/response). If you need to be that explicit, then you need to create two types - e.g. OrderRequest, OrderResponse.
Alternatively, Swagger does support the notion of readOnly properties and these can be used to indicate fields that are not applicable (e.g. an Id that gets auto-generated) in say a request to create something.
However, as of now the swagger-ui doesn't hide these so your still a little snookered until that's addressed in the swagger-ui project.

authors: domaindrivendev maperr

repo: domaindrivendev/Swashbuckle


text:
Can't add the plugin to Android project.

Could not install package 'Xamarin.GooglePlayServices.Location 42.1001.0'. You are trying to install this package into a project that targets 'MonoAndroid,Version=v6.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Xamarin.Forms version 2.3.3.180
Xamarin.GooglePlayServices.Location version 29.0.0.1

The plugin does not work for Xamarin.GooglePlayServices.* that are above version 29.*
Waiting for a updated build will be the solution so far or follow this workaround:Xamarin Forum

authors: Heshanp andresteves

repo: domaven/xamarin-plugins


text:
Is it possible to add the actual warm water temperature?

Hey Dominik,
Really appreciate your project. There is only one thing i miss. Not sure if it is not exported by pellematic at all or not.
But within the app if you go to your warm water circuit, you can see the values is and should for
WW Temperature.
Within your integration i can only find the sensor for "should", in my case this i called:
pellematic_hot_water_circuit_1_temperature_set
I would appreciate to see the current water temperature for my system.
Thank you in advance!

Hi
it should be available see

Hello!
Sorry i missed this.
That's what i was looking for.
Thank you!

authors: dominikamann laugrean

repo: dominikamann/oekofen-pellematic-compact


text:
Filling Asian charicters

I'm doing some form filling and have to accommodate Japanese text. This does not seem to be supported with the default options.
let FillData = {
    text: 'ベルゼルグ王国第一王女 アイリス'
}

fillPdf.generatePdf(FillData, Form.path, function(err, output) {
      if ( !err ) {
          res.type("application/pdf");
          res.send(output);
      }
});

This will output a pdf with my text field filled with:
ã…Žã…«ã‡¼ã…«ã‡°ç”‰åł½ç¬¬ä¸•ç”‰å¥³ ã‡¢ã‡¤ã…ªã‡¹
How do I configure this to allow the correct encoding?

I have the same issue..
may be the problem comes from the function
escapeFdf(data)

Having the same problem with Swedish characters "åäöÅÄÖ".
Tried adding the extra argument need_appearances but that did not help https://www.pdflabs.com/docs/pdftk-man-page/#dest-output-need-appearances =(

I'm also having this issue when trying to use it like this
fillPdf.generatePdf(data, filePath, ['need_appearances'], (err, output) => (err ? reject(err) : resolve(output)))

Same for Czech characters too.

authors: Mousaka SpringsTea librorum mikeoaklet ysarzhynskyi

repo: dommmel/fill-pdf


text:
HomeKit showing as "Update Available"

I have added a MSS210 plug and it works perfectly, but the Apple Home app shows as an update is available and a link to the Meross app.  All of the devices are up to date, can this be overridden?

can you show the firmware version of the mss210 plug in the meross app?

2.1.7
[Image.jpeg]
Thanks,
Mat
+44 (0)7990 591055

From: Donavan Becker notifications@github.com
Sent: Monday, November 30, 2020 7:18:54 PM
To: donavanbecker/homebridge-meross homebridge-meross@noreply.github.com
Cc: Mat Clothier mat.clothier@cloudhouse.com; Author author@noreply.github.com
Subject: Re: [donavanbecker/homebridge-meross] HomeKit showing as "Update Available" (#121)
can you show the firmware version of the mss210 plug in the meross app?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdonavanbecker%2Fhomebridge-meross%2Fissues%2F121%23issuecomment-735987736&data=04|01|mat.clothier%40cloudhouse.com|b8a291265ea64295ae7c08d89564c895|6c0fe8f2a0d04324a6067ca2bbdac77b|0|0|637423607377137958|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9KdIGP6LEzATDRhInT0JPRKvdFgf0JnHYcNluPqyiN4%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANF2W7O7UKM6RKIJMKQ4ZGDSSPVZ5ANCNFSM4UH7RLHA&data=04|01|mat.clothier%40cloudhouse.com|b8a291265ea64295ae7c08d89564c895|6c0fe8f2a0d04324a6067ca2bbdac77b|0|0|637423607377137958|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3p0IdoX04I9xzZW3n2LPfk0IjtTSp%2BoIB%2Bj9A9RDMEw%3D&reserved=0.

Hi, any ideas how to fix this?

I have the same problem. My plugin symbol, plugin firmware in Meross and Homekit are also the same.

@bywalec1 and @matclothier,
Can you test the latest beta and then input a firmware version higher then the one for your outlet and let me know if it goes away.

The plugs don’t work in Homebridge or home at all with the new beta. I tried with the working confit from before and with adding the new options.

@matclothier Do you have errors you can provide?

Error -113 for all 3 devices.

@matclothier I would check again? because I am not getting this.

OK, it looks like it is working now and the update notice has gone away.  Thanks for sorting this.

@matclothier You can actually set the firmware in the plugin settings on Homebridge UI.

Everything works fine now. Thank you very much.

The beta resolved issue for me too - Thanks

authors: bywalec1 donavanbecker johnmullaney matclothier

repo: donavanbecker/homebridge-meross


text:
DoneJS 2.0 Migration Guide

Create a migration guide similar to the 1.0 one that mostly points to the CanJS 4.0 migration guide.

Closed by #1081

repo: donejs/donejs


text:
Experiment with collada animation

Idea:
AFRAME.registerComponent('collada-animation', {
  init: function () {
    this.el.addEventListener('model-loaded', function(e) {
      e.detail.model.traverse( function ( child ) {
      if ( child instanceof THREE.SkinnedMesh ) {
        var animation = new THREE.Animation( child, child.geometry.animation );
        animation.play();
      }
    });
  },

  tick: function (t, dt) {
    THREE.AnimationHandler.update( dt );
  }
});

Usage:
<a-entity collada-model="..."
          collada-animation></a-entity>

From Slack:
https://dl.dropboxusercontent.com/u/705999/beartest.zip
it's a version of your collada-animation prototype running this collada file that has animation
for some reason the animations are not playing back

Updated and working on monster.dae, after including dependencies:

THREE.Animation
THREE.AnimationHandler
THREE.KeyFrameAnimation

AFRAME.registerComponent('collada-animation-mixer', {
  init: function () {
    this.el.addEventListener('model-loaded', function(e) {
      e.detail.model.traverse( function ( child ) {
        if ( child instanceof THREE.SkinnedMesh ) {
          var animation = new THREE.Animation( child, child.geometry.animation );
          animation.play();
        }
      });
    });
  },

  tick: function (t, dt) {
    THREE.AnimationHandler.update( dt / 1000 );
  }
});

<a-entity position="0 0 -10"
          collada-animation-mixer
          collada-model="src: url(/assets/tmp/monster/monster.dae)"
</a-entity>

Test file:
monster.zip

Closing this bug, because I don't expect to have time for working with the COLLADA format further. Consider glTF: https://aframe.io/docs/0.5.0/components/gltf-model.html

In recent versions of three.js, THREE.ColladaLoader uses the default three.js animation system, and should be fully compatible with the existing animation-mixer component.

repo: donmccurdy/aframe-extras


text:
Promoted products on iOS not working since 4.4.1

Version of react-native-iap
4.5.2
Version of react-native
0.62.2
Platforms you faced the error (IOS or Android or both?)
IOS
Expected behavior
I expect popup that asks to buy product after paste to safari
itms-services://?action=purchaseIntent&bundleId=<my_app_bundle_id>&productIdentifier=<product_id>
Actual behavior
Nothing happens with react-native-iap versions after 4.4.1
Tested environment (Emulator? Real Device?)
iPhone 7 Plus, ios 13.6
Steps to reproduce the behavior
I test like this - paste to safari
itms-services://?action=purchaseIntent&bundleId=<my_app_bundle_id>&productIdentifier=<product_id>
I followed docs to configure ios promoted products
https://github.com/dooboolab/react-native-iap#how-do-i-handle-promoted-products-in-ios
(For 4.4.1 i add additional code to AppDelegate)
https://github.com/dooboolab/react-native-iap/tree/4.4.4#how-do-i-handle-promoted-products-in-ios
Am I doing something wrong? Mb i should test promoted products in other way, without itms-services link. Help please!

bump :)

https://github.com/dooboolab/react-native-iap/issues/1094#issuecomment-683320452
should use RNIap.initConnection();

authors: EgorKazachenko vitali-kastsiuk

repo: dooboolab/react-native-iap


text:
求教这个怎么部署到web服务器？

请问这个怎么部署到web服务器，求使用教程？

@star2k 大致步骤如下：

在服务器上安装 node 环境；
克隆本项目到服务器：git clone git@github.com:doocs/md.git；
项目目录下运行：npm install；
运行打包：npm run build；
dist 文件夹即为打包后的代码；
搭建 http 服务，部署包文件。

@star2k 大致步骤如下：
1. 在服务器上安装 node 环境；

2. 克隆本项目到服务器：`git clone git@github.com:doocs/md.git`；

3. 项目目录下运行：`npm install`；

4. 运行打包：`npm run build`；

5. dist 文件夹即为打包后的代码；

6. 搭建 http 服务，部署包文件。

谢谢，下次尝试学习一下。这会儿能分享一份打包后的代码么？

https://github.com/doocs/md/tree/gh-pages 这个分支就是打包后的

https://github.com/doocs/md/tree/gh-pages 这个分支就是打包后的

太感谢了，

直接用 https://github.com/doocs/md/tree/gh-pages 这个分支部署 github pages，404 无法访问？

直接用 https://github.com/doocs/md/tree/gh-pages 这个分支部署 github pages，404 无法访问？
需要在 url 后面加一个 "index.html#/" 就可以了~

嗯嗯，好的

请教一下，gh-pages 这个分支的 index.html 不能直接在浏览器打开么？我在 Chrome 直接打开是空白的，没有内容。

请教一下，gh-pages 这个分支的 index.html 不能直接在浏览器打开么？我在 Chrome 直接打开是空白的，没有内容。

需要有 http 服务才行

请教一下，gh-pages 这个分支的 index.html 不能直接在浏览器打开么？我在 Chrome 直接打开是空白的，没有内容。

需要有 http 服务才行

ok，感谢！

authors: shenweiyan star2k yanglbme

repo: doocs/md

license: WTFPL


text:
Add Ostmodern

Please review our Contribution Guidelines to ensure your changes abides by it.
Changes should be made to the end of the file.
Review your changes and complete the checklist below.

[x] Company name
[x] Industry
[x] Company location
[x] Company description
[x] How Elixir is used
[x] GitHub / blog links
[ ] Job listings

Thank you @sulami!

authors: doomspork sulami

repo: doomspork/elixir-companies


text:
Switch to simple-get?

I'm seeing that you are using both callback and stream api of the request and maybe because of that you are using it. Because of these needs and needs of github-base, before some time I created small wrappers around simple-get. One is request-all, another is simple-get-stream.
Both plays well and can works exactly as request, but with a smaller codebase.
Let me brief.
Example showing how can be done
var handle = require('handle-arguments')
var request = require('request-all')(require('simple-get'))
request.stream = require('simple-get-stream')

function req (url, opts, cb) {
  var argz = handle(arguments)
  if (argz.callback) {
    return request.requestAll.apply(this, arguments)
  }
  return request.stream.apply(this, argz.args)
}

// callback
req('https://httpbin.org/ip', function (err, body, res) {
  console.log(err, body) // => {origin: '85.12.234.22'}
})

// options passed to simple-get
// and in addition have `json:true` by default
req('https://httpbin.org/ip', {json: false}, function (err, body, res) {
  console.log(err, body.toString('utf8')) // => '{origin: '85.12.234.22'}'
})

// stream
req('https://httpbin.org/ip')
.pipe(process.stdout) // => {origin: '85.12.234.22'}

If you look closely in their repos, you'll see that they are not so big deal and they almost don't have deps. Actually, deps that in anyway you have here - through2 is the one, another is the simple-get.
Request-All uses and acts (almost *) like a simple-get.concat, it also handle JSON and perform multiple requests if needed. In same time, it won't do unnecessary calls if don't have link header - it will be as single .concat call.
* almost: I'm saying almost, because only the incoming signature is the same, callback arguments are reversed it would be callback(err, body, response) instead of callback(err, response, body) - i'm considering to follow simple-get and request, i thought it is better to save it this way, because simple-get@1 was with it.
And finally, you may ask what is handle-arguments and why to use it. It's pretty simple and small thing which (just uses sliced) removes the repeating need of getting last argument and doing things like
var args = [].slice.call(arguments)
var last = args[args.length - 1]
var callback = typeof last === 'function' ? last : false

Why we should do it every time everywhere? It's simple as argz = handle(arguments); if (argz.cb) - it will have (and will do the type check) correct callback function if it has, otherwise will be undefined.
===
In the context of this repo, the lib/list.js#L30-L39 would be simplified to utils.request(this.url(params), cb) (not exactly), in one hand.
And in another hand, won't need to change anything other if we manually create utils.request method like
// adding to the requires
require('handle-arguments', 'handle');
require('request-all');
require('simple-get');
require('simple-get-stream');

utils.request = function request(url, opts, cb) {
  var argz = utils.handle(arguments);
  if (argz.callback) {
    var simpleGet = utils.requestAll(utils.simpleGet);
    return simpleGet.requestAll.apply(this, arguments);
  }
  return utils.simpleGetStream.apply(this, argz.args);
};

I can PR.
Cheers.
edit: i'll add lazy-cache to them soon, so it will be better.

what is handle-arguments and why to use it

I know we do [].slice.call(arguments) sometimes, but because of arguments leaks we really should only do it when it's convenience outweighs other options.

Agree. But this not change the fact that it saves writing time.
And yes, initially handle-arguments was using manage-arguments which is direct copy of the suggested code by Petka, but switched to sliced because it is a bit faster and seems to do the job without leaks.

Thanks for the details. Wait to do a PR because I'm still working on the structure and logic here before optimizing the fetching of data.
I'd use simple-get and simple-get-stream directly in the places they make sense instead of doing the arguments juggling.

But this not change the fact that it saves writing time and helps a bit for optional arguments.

good grief, sorry I don't want to debate this trivial stuff. IMO it's unnecessary, [].slice.call(arguments) is less code than the actual require statement for your lib lol.

directly in the places they make sense

More work and repeating code for nothing, it not worth, because basically you will do the same thing, but okey. Above example only pluses, haha.

is less code than

haha :+1: yea, even more if we remove [].slice.call(arguments), haha.

lol true, true

authors: doowb jonschlinkert tunnckoCore

repo: doowb/npm-info


text:
🛑 aawq016 test is down

In 71caea5, aawq016 test (https://aawq-016.dx.commercecloud.salesforce.com/s/Tumi_MY/home) was down:

HTTP code: 521
Response time: 477 ms

Resolved: aawq016 test is back up in 6721f81 after 12 hours, 49 minutes.


text:
Shorten required length for some event fields

This is to accomodate for events planned long into the future, where all information may not be known at the time of event creation. However, we still want to have a lower limit - as the front page would look ugly if there was not enough text to ~fill the "featured" events' text boxes.

What about not having this limit, AND prevent "TBA" events from being one of the two featured events?

authors: sklirg tmn


text:
Genfors blank votes

Updated the genfors-app, so it works again. Changed how blank votes affect the result, and how blank votes are represented on the page. Also changed vote verification so it disappears if option is changed.

Also, have a look at the failing Flake8 tests :)

Calculation of votes does not yet account for (/subtract) blank votes.

authors: MrHanSan hernil sklirg


text:
bug: default values should not create Maybe types

Describe the bug
default input values should not create Maybe types, as they can't be nullable.
plugins used:
typescript
typescript-resolvers
have not tried this with typescript-operations yet.
To Reproduce
Steps to reproduce the behavior:
input FooInput {
  bar: String = "foo"
}

extend type Query {
  foo(bar: String = "foo"): Boolean
}

generates ambient types;
export type FooInput = {
  bar?: Maybe<Scalars['String']>;
};

export type QueryFooArgs = {
  bar?: Maybe<Scalars['String']>;
};

expected:
export type FooInput = {
  value: Scalars['String'];
};

export type QueryFooArgs = {
  bar: Scalars['String'];
};

generates:
  dist/typings.d.ts:
    config:
      contextType: Context
      enumsAsTypes: true
      noSchemaStitching: true
      # immutableTypes: true # TODO
      useIndexSignature: true
      useTypeImports: true
    hooks:
      afterOneFileWrite:
        - prettier --write
    plugins:
      - typescript
      - typescript-resolvers
overwrite: true
schema:
  - ./schema/**/*.graphql

Expected behavior

Environment:

OS: macOS 11
NodeJS: v15.7.0

similar behavior:
https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABMOcAUBDA-IgvIgchTgIEpEBvAKEUQCcBTKEOpDKgXyA
function foo(a? = 'foo') {
  return a
}

// exception: Parameter cannot have question mark and initializer.(1015)

on that note, graphql-js seems to be fine with either notation, although it doesn't make much sense. not sure if it's a graphql spec oversight or a graphql-js bug. I'll file an issue over there as well.
extend type Query {
  foo(bar: String! = "Foo"): Boolean
}

this is invalid. providing a default value for input positions and setting this position to nullable is allowed und passing null explicitly is legal. graphql uses a default value only, if the position is omitted.
see https://github.com/MichalLytek/type-graphql/issues/751 which describes this in more details

It definitely matters on what point of view you are looking at default values. From a point of view of the GraphQL resolver => it's a non-optional, non-nullable field (because it will have a value, for sure). From the point of view of GraphQL consumer, it's optional, nullable (because then it will get filled with the default value).

From the point of view of GraphQL consumer, it's optional, nullable

one small correction on this: its not nullable, its omitable. you cant pass null explicitly

From the point of view of GraphQL consumer, it's optional, nullable

~one small correction on this: its not nullable, its omitable. you cant pass null explicitly~
edit: i actually turned the use case around. the statement was correct
edit2: still an error in the other statement:

From a point of view of the GraphQL resolver => it's a non-optional, non-nullable field

you can pass null explicitly and will get null in the resolver
type Query {
  foo(bar: String = "foo"): Boolean
}

means: the resolver gets null or string. the caller can omit this (in which case "foo" is used) or pass null or a string.
edit3:
he talks about generating types for resolvers:
export type QueryFooArgs = {
  bar: Scalars['String'] | null;
};

this is the actual correct type for QueryFooArgs on the resolver side

What about non-nullable with default field? I guess it will pass the string in case of null?

from the client side you can not pass null to a non-nullable field, no matter if it has a default value or not. you can omit the field, if there is a default value

maybe code explains it better:
input MyInput {
  a: Int
  b: Int = null
  c: Int = 5
  d: Int!
  e: Int! = 5
}

client
interface MyInput {
  a?: number | undefined | null;
  b?: number | undefined | null;
  c?: number | undefined | null;
  d: number;
  e?: number;
}

resolver:
interface MyInput {
  a: number | undefined | null; // no "?", the property will be there
  b: number | null;
  c: number | null;
  d: number;
  e: number;
}

authors: backbone87 dnalborczyk dotansimha

repo: dotansimha/graphql-code-generator


text:
Typescript-Resolvers' generated code has errors if noUnusedParameters option enabled in tsconfig

Which packages are impacted by your issue?
@graphql-codegen/typescript-resolvers
Describe the bug
Are updating to the typescript-resolver v4.0.0 we're running into an issue with our typescript compilation. In our tsconfig.json settings, we enable the noUnusedParameters check, and it seems that this change introduced some generics that is causing that check to fail.
We're working around this by using the add plugin to prepend a // @ts-nocheck at the top of the file, but it'd be nice to have the files included in the checks
Your Example Website or App
https://github.com/AlexLorenzi/codegen-example
Steps to Reproduce the Bug or Issue

Checkout example project
Run yarn and yarn generate
Run yarn tsc

Expected behavior
Expect generated code to compile successfully
Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: v16.20.0
graphql version: 16.6.0
@graphql-codegen/* version(s): 4.0.0

Codegen Config File
import type { CodegenConfig } from '@graphql-codegen/cli'

const config: CodegenConfig = {
    schema: './schema.graphqls',
    generates: {
        './src/graphql/schema-types.generated.ts': {
            plugins: ['typescript', 'typescript-resolvers']
        }
    }
}
export default config

Additional context
No response

Hello 👋
This is the same as https://github.com/dotansimha/graphql-code-generator/issues/9486. I've left a reply here.
Please discuss in that issue. Thanks!


text:
@parcel/watcher not working with pnpm

Which packages are impacted by your issue?
@graphql-codegen/cli
Describe the bug
The @parcel/watcher package is not detected as a peer dependency when installed with pnpm.
Your Example Website or App
https://stackblitz.com/edit/github-8b9tnc?file=package.json
Steps to Reproduce the Bug or Issue
Run pnpm start
Expected behavior
Expected: codegen running in watch mode
Reality: Parcel watcher not found. To use this feature, please make sure to provide @parcel/watcher as a peer dependency.
Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: 18.18.0
graphql version: 16.8.1
@graphql-codegen/* version(s): 5.0.0 for the cli, 4.1.0 for the client-preset

Codegen Config File
import type { CodegenConfig } from '@graphql-codegen/cli';
import { NEXT_PUBLIC_BACKEND_URL } from './app/utils/env';

const config: CodegenConfig = {
	overwrite: true,
	schema: `${NEXT_PUBLIC_BACKEND_URL}/graphql`,
	ignoreNoDocuments: true,
	documents: './app/**/*.graphql',
	generates: {
		'./app/gql/': {
			preset: 'client',
		},
	},
};

export default config;

Additional context
When I downgrade the @parcel/watcher to 2.1.0, it works.
When I install the packages with yarn too.

Interesting, maybe worth also reporting to parcel and linking the issue here?

I just ran in the exact same issue

Having the same issue, has one found a solution to this? I don't have @parcel/watcher in my dependencies and it'd be great if I wouldn't have to add it, I guess?

authors: Urigo holtergram n-vh nagman


text:
Task or valuetask

I have a hard time understanding when to use valuetask in stead of task. Most often in regular desktop app development I use task but I can see that many places when invoking javascript the interop method returns valuetask. Is that better for javascript or is there some other reason???

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

ID: aada0049-99a8-2f91-5d60-6970474e2371
Version Independent ID: c29fb1a8-028f-6efd-f1bc-e889fb362311
Content: Call JavaScript functions from .NET methods in ASP.NET Core Blazor
Content Source: aspnetcore/blazor/call-javascript-from-dotnet.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @erikthysell ... 🏃 Performance 🏃 should be the answer. There was a time when all of our JS interop examples used Task, and we switched over to ValueTask for these because the calls would be just a tiny bit faster. I don't recall the details ... the changes were made a while ago. It was something that engineering started doing, and I picked up on it and changed the sample app, followed by a couple of readers suggesting that we further make the topic in-text examples embrace it. Engineering agreed, so we updated the return types to what you see today.
For more info generally on the choice, see the remarks in the linked API doc for the benefits and conditions ...
https://docs.microsoft.com/dotnet/api/system.threading.tasks.valuetask-1
... and see the discussion with remarks by Stephen Cleary and Stephen Toub on an SO answer.
If would be interesting if you benchmarked some JS interop calls both ways and actually found out that ValueTask was 🐌 slower 🐌 in certain scenarios. If you make such a discovery, I recommend that you let us know.
I don't have any further info. If you want to dig deeper into the subject, see if you can find a deep dive blog post, additional SO posts, and/or chat with language experts on one of the usual support channels ...

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

You probably also could Tweet Stephen Cleary if you have a question. He's a cool :cat2: and helpful to talk to about things like this.

authors: erikthysell guardrex


text:
How to pass arguments into the queued background work

The example given, while helpful, doesn't shed much light into how it could be modified to allow arguments to be passed into the queue and stored along the tasks for processing at a later time.
As it is, since the QueueHostedService implements BackgroundService, it neatly handles a no-argument situation since the ExecuteAsync override simply calls BackgroundProcessing and passes in its CancellationToken, but then BackgroundProcessing itself then pulls the function out of the queue to execute, and.. well, there's no argument that's been stored, so passing anything into the await workItem(customArg, stoppingToken) fails for lack of a sourced customArg.
It'd be useful to see a second example provided that explains how to queue data to pass into the ValueTask methods so it's available at processing time.

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

ID: c3460b0d-9c60-3a06-ac63-18cf990e53c3
Version Independent ID: b2dece1f-15b8-03af-6d52-7cc070432b4b
Content: Background tasks with hosted services in ASP.NET Core
Content Source: aspnetcore/fundamentals/host/hosted-services.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hi, @WhitWaldo! If I've understood the use case correctly, isn't that something you would do with a ValueTask<T> where T is the customArg type? Something like the following,
ValueTask<CustomArg> QueueBackgroundWorkItemAsync(Func<CancellationToken, ValueTask<CustomArg>> workItem);

ValueTask<Func<CancellationToken, ValueTask<CustomArg>>> DequeueAsync(
    CancellationToken cancellationToken);

Hello @fiyazbinhasan and thanks for writing back! It's definitely something I can share the type of through the ValueTask, but where I can define the Func that accepts that argument, it wasn't clear how I'd pass the actual data comprising that argument into the Func when doing the work.
Looking at the example here, I can queue the work item (the Func) to the channels queue. When it's executed on in the following class (1QueuedHostedService), it's unclear where the argument would come from to pass into BackgroundProcessing to actually run the Func against that data.
It doesn't make a lot of sense to have a function pop out that I can evaluate without any data stored alongside it, so that's the crux of my inquiry here. Yeah, I can modify the signature from Func<CancellationToken, ValueTask> and instead have it do something like Func<CancellationToken, TThing, ValueTask<TThing>> so I have the background task work against my TThing and return its own TThing, but it's not clear where I can then put the TThing so the data is queued alongside the function itself.

@WhitWaldo I'm a bit confused. Where does TThing come from in your case? Right now the state of these functions can be captured via a closure:
var state = new TThing();
_taskQueue.QueueBackgroundWorkItemAsync(token => DoSomeWork(state));

Does that work in your situation?

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog manageable. If you believe there is a concern which hasn't been addressed, please file a new issue.

authors: Rick-Anderson WhitWaldo davidfowl fiyazbinhasan


text:
Error found in compiling the code in program.cs    Compile Error can be fixed.

[Enter feedback here]
You will obtain an compile error inside of program.cs at
builder.Services.AddDatabaseDeveloperPageExceptionFilter()
the error message is:
error cs1061 'iservicecollection' does not contain a definition for 'adddatabasedeveloperpageexceptionfilter'
You can fix the problem by installing the following NuGet  Package:
Install-Package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -Version 6.0.5
I found the above solution at:
https://stackoverflow.com/questions/65007086/services-adddatabasedeveloperpageexceptionfilter-error-code-cs1061

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

ID: ab408035-6313-a183-9940-32de00e0e977
Version Independent ID: ab408035-6313-a183-9940-32de00e0e977
Content: Tutorial: Create a minimal web API with ASP.NET Core
Content Source: aspnetcore/tutorials/min-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

That's in https://docs.microsoft.com/en-us/aspnet/core/tutorials/min-web-api?view=aspnetcore-6.0&tabs=visual-studio#add-nuget-packages

authors: Rick-Anderson jmgraceofbatonrouge


text:
Test your documentation

Suggestion: Before publishing a how-to page like this (or any topic for that matter). Create a new, fresh Windows 10 computer/VM and have someone on your staff do the same process based solely on the documentation. Test your documentation.

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

ID: f92a99a8-6ffa-e5f9-b7ef-f13fa1e0f17b
Version Independent ID: 51273790-5178-875b-010e-15d7725da535
Content: Publish an ASP.NET Core app to IIS
Content Source: aspnetcore/tutorials/publish-to-iis.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@chrisleadbeater  please don't make duplicate issues #26639

authors: Rick-Anderson chrisleadbeater


text:
"dotnet ef database update" is not part of the step!!!

[Enter feedback here]
Trying to follow the instruction for this tutorial and I hit this same error as mentioned. But they said we missed the "dotnet ef database update" witch doesn't exist!!

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

ID: 1d975a83-1550-b284-d0d8-7fe2ea206ff5
Version Independent ID: 48e81b42-7c2b-afbf-71e6-d4f442a4bd1f
Content: Part 4, add a model to an ASP.NET Core MVC app
Content Source: aspnetcore/tutorials/first-mvc-app/adding-model.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @wadepickett
Microsoft Alias: wpickett

The missing command was: "Update-Database". Maybe I'm dumb but it's not exactly the same as "dotnet ef database update".
Thanks

@krueger80, you were right, this needed an improvement.  Reopening and will fix. Thanks for taking the time to let us know.


text:
Remove extraneous text in header

Noticed there was some extraneous text in the header while looking at the docs.

Definitely aliens.


text:
Ra/test min api

Moves #23907 to this branch so I can push commits.

@furoTmark
Thanks for the fix. Be sure to check out your name as a contributor about the 3rd of next month on the What's new page

Didn't see my name, but glad to help!

authors: Rick-Anderson furoTmark


text:
Valide kerberos ticket - Active directory

Is your feature request related to a problem? Please describe.
I am interested in validating Kerberos tickets received from a third-party application. I want to confirm if the Kerberos.NET library can be used to validate these tickets against an Active Directory (AD). Currently, I'm unsure if the library provides this functionality or if any additional setup is required to perform the validation.
Describe the solution you'd like
I would like to use Kerberos.NET to validate Kerberos tickets from external sources by querying Active Directory. Ideally, the library should support direct interaction with AD for ticket validation without complex configurations.
Describe alternatives you've considered
As an alternative, I’ve considered using system tools like kinit to manually validate tickets against the KDC, but integrating that into the application is cumbersome. I've also thought about setting up a custom service to handle this validation, but it introduces overhead and complexity.
Additional context
My application is currently running on Linux, and I would need this feature to integrate into a .NET 8 solution. Any guidance on how to achieve this functionality would be appreciated.

Yes, that's the whole point of the library. It's a kerberos client, server, and KDC.

Could you assist me in decrypting the ticket received by the third party client ?

Yes, that's the whole point of the library. It's a kerberos client, server, and KDC.

I successfully decrypted a Kerberos ticket using a keytab associated with the same SPN as the ticket. My question is, what's the best solution if I have around 100 SPNs and I want my app to handle all of them?
Can I use a global keytab that has all the SPNs configured, or is there a more optimized approach to address this?

Giant keytab is probably the easiest approach. Nothing wrong with it, but it could be tricky to debug. One keytab per service would likely be easier to debug and scale. Note that securing these files is pretty important. Anyone stealing them can impersonate the services.

From: DanielMGoldberg @.>
Sent: Monday, September 16, 2024 7:44:54 AM
To: dotnet/Kerberos.NET @.>
Cc: Comment @.>; Subscribed @.>
Subject: Re: [dotnet/Kerberos.NET] Valide kerberos ticket - Active directory (Issue #378)
Yes, that's the whole point of the library. It's a kerberos client, server, and KDC.
I successfully decrypted a Kerberos ticket using a keytab associated with the same SPN as the ticket. My question is, what's the best solution if I have around 100 SPNs and I want my app to handle all of them?
Can I use a global keytab that has all the SPNs configured, or is there a more optimized approach to address this?
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/Kerberos.NET/issues/378#issuecomment-2353130601 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJHTYITGLZPK77PBZ7DJWDZW3VGPBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVE2TMNBSG4ZDGNJXURXGC3LFVFUGC427NRQWEZLMVRZXKYTKMVRXIX3UPFYGLLCJONZXKZKDN5WW2ZLOOSTHI33QNFRXHE4CUR2HS4DFVJZGK4DPONUXI33SPGSXMYLMOVS2QOBVGQ4DSMJTHCBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI2TEMJUGAYTMNJWQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKJVGY2DENZSGM2TPJ3UOJUWOZ3FOKTGG4TFMF2GK.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Giant keytab is probably the easiest approach. Nothing wrong with it, but it could be tricky to debug. One keytab per service would likely be easier to debug and scale. Note that securing these files is pretty important. Anyone stealing them can impersonate the services.
…
________________________________ From: DanielMGoldberg @.> Sent: Monday, September 16, 2024 7:44:54 AM To: dotnet/Kerberos.NET @.> Cc: Comment @.>; Subscribed @.> Subject: Re: [dotnet/Kerberos.NET] Valide kerberos ticket - Active directory (Issue #378) Yes, that's the whole point of the library. It's a kerberos client, server, and KDC. I successfully decrypted a Kerberos ticket using a keytab associated with the same SPN as the ticket. My question is, what's the best solution if I have around 100 SPNs and I want my app to handle all of them? Can I use a global keytab that has all the SPNs configured, or is there a more optimized approach to address this? — Reply to this email directly, view it on GitHub<#378 (comment)> or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJHTYITGLZPK77PBZ7DJWDZW3VGPBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVE2TMNBSG4ZDGNJXURXGC3LFVFUGC427NRQWEZLMVRZXKYTKMVRXIX3UPFYGLLCJONZXKZKDN5WW2ZLOOSTHI33QNFRXHE4CUR2HS4DFVJZGK4DPONUXI33SPGSXMYLMOVS2QOBVGQ4DSMJTHCBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI2TEMJUGAYTMNJWQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKJVGY2DENZSGM2TPJ3UOJUWOZ3FOKTGG4TFMF2GK. You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you so much!
The issue is that many applications will be using my app, and each one is calling a different SPN, generating its ticket via the KDC. Initially, I thought it might be better to request a keytab from each of them via HTTPS to generate tickets for different services, but I'm not very enthusiastic about that approach from a security perspective.
What do you think?

Giant keytab is probably the easiest approach. Nothing wrong with it, but it could be tricky to debug. One keytab per service would likely be easier to debug and scale. Note that securing these files is pretty important. Anyone stealing them can impersonate the services.
…
________________________________ From: DanielMGoldberg @.> Sent: Monday, September 16, 2024 7:44:54 AM To: dotnet/Kerberos.NET @.> Cc: Comment @.>; Subscribed @.> Subject: Re: [dotnet/Kerberos.NET] Valide kerberos ticket - Active directory (Issue #378) Yes, that's the whole point of the library. It's a kerberos client, server, and KDC. I successfully decrypted a Kerberos ticket using a keytab associated with the same SPN as the ticket. My question is, what's the best solution if I have around 100 SPNs and I want my app to handle all of them? Can I use a global keytab that has all the SPNs configured, or is there a more optimized approach to address this? — Reply to this email directly, view it on GitHub<#378 (comment)> or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJHTYITGLZPK77PBZ7DJWDZW3VGPBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVE2TMNBSG4ZDGNJXURXGC3LFVFUGC427NRQWEZLMVRZXKYTKMVRXIX3UPFYGLLCJONZXKZKDN5WW2ZLOOSTHI33QNFRXHE4CUR2HS4DFVJZGK4DPONUXI33SPGSXMYLMOVS2QOBVGQ4DSMJTHCBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI2TEMJUGAYTMNJWQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKJVGY2DENZSGM2TPJ3UOJUWOZ3FOKTGG4TFMF2GK. You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you so much!
The issue is that many applications will be using my app, and each one is calling a different SPN, generating its ticket via the KDC. Initially, I thought it might be better to request a keytab from each of them via HTTPS to generate tickets for different services, but I'm not very enthusiastic about that approach from a security perspective.
What do you think?

Can you describe the basic architecture? It's not common for a single app to have a hundred services like this unless it's like a multitenant cloud service.

Can you describe the basic architecture? It's not common for a single app to have a hundred services like this unless it's like a multitenant cloud service.

The architecture involves hundreds of frontend web applications hosted on IIS, with each app having its own API and SPN. These APIs communicate with each other. Since I’m transitioning to a Linux-based container environment, I now need to manually handle all of these Kerberos tickets, which is the challenge I'm facing.

Ah I see. You're consolidating everything? You might consider moving all the SPNs onto a single service account instead if that's feasible. That way you're only managing the single service.

It's all just different tradeoffs. You're either managing a hundred files or a hundred entries in a file or a hundred SPNs on an account or a hundred accounts. In my mind trying to reduce the liklihood of having to debug a random encryption issue because of a keys mismatch is going to be the most benefit in the long run.

Your advice has been incredibly valuable. Thank you again for all your support!

authors: DanielMGoldberg SteveSyfuhs


text:
Unable to build from source

Unable to build from source, using VS 2019 with all vsconfig defined pre-requistes installed.
Unable to find package Microsoft.DotNet.GenAPI. No packages exist with this id in source(s):
Exception message:
Project "C:\Code\Github\SqlClient\src\Microsoft.Data.SqlClient.sln" (1) is building "C:\Code\Github\SqlClient\src\Micro
soft.Data.SqlClient\tests\tools\TDS\TDS.EndPoint\TDS.EndPoint.csproj" (3) on node 1 (default targets).
_CheckForNETCoreSdkIsPreview:
  You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
C:\Code\Github\SqlClient\src\Microsoft.Data.SqlClient\tests\tools\TDS\TDS.EndPoint\TDS.EndPoint.csproj : error NU1101:
Unable to find package Microsoft.DotNet.GenAPI. No packages exist with this id in source(s): CliFallbackFolder, Microso
ft Visual Studio Offline Packages, nuget.org, Package source
Done Building Project "C:\Code\Github\SqlClient\src\Microsoft.Data.SqlClient\tests\tools\TDS\TDS.EndPoint\TDS.EndPoint.
csproj" (default targets) -- FAILED.

To reproduce
Pull source, run msbuild in the src folder as prescribed.
Expected behavior
The build complets
Further technical details
Additional context
In addition, the Functional test project reference two unknown packages:
microsoft.xunit.netcore.extensions
Microsoft.dotnet.buildtools.testsuite

are you mssing documentation of a "secret" package source?

Indeed!! 😞
Adding this fixed the issue - I will create a PR to get the NuGet.config file added 😄
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="dotnet-core" value="https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json" />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
</configuration>

PR submitted

Hi @ErikEJ
FYI The Nuget Package sources the driver refers for building are defined in build.proj, however putting them in a separate Nuget.config file is good for developers reference. Thanks for the PR, I will update documentation accordingly.
Also I figured out with latest VS 2019 Enterprise & Community edition, microsoft.visualstudio.component.typescript.3.4 is not found. Just to confirm if you also saw this while installation, I'm going to remove/replace that package reference.

Ah, I misunderstood the build instructions, and ran msbuild from a developer command prompt in the src folder, not in the root folder. Adding NuGet.config to the solution folder will now enable build from the src folder (and VS in particular)

authors: ErikEJ cheenamalhotra

repo: dotnet/SqlClient


text:
Error while importing the System.Data.SqlClient namespace in Azure Function V4

Hi,
I have created the Azure Function on the portal using the csx file.
I have been trying to use the system.data.sqlclient library in my Azure Function V4 with .NET 6, but this error occurs

run.csx(7,20): error CS1069: The type name 'SqlConnection' could not be found in the namespace 'System.Data.SqlClient'. This type has been forwarded to assembly 'System.Data.SqlClient, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Consider adding a reference to that assembly.

When I downgraded my function App from V4 to V3. It was working fine with same code but when I was trying to upgrade the function App with V4, it returns the same error.
I am only getting this issue while creating the Azure Function on the portal.
This is simple run.csx file
#r "System.Data.SqlClient.dll"
using System.Data.SqlClient;
using System;
public static void Run(TimerInfo myTimer, ILogger log)
{
    var conn = new SqlConnection("MyConnectionString");
    log.LogInformation($"C# Timer trigger function executed at: {DateTime.Now}");
}

I have tried to put the system.data.sqlclient.dll in the bin folder of function using kudu console, but still getting same error.
Any help much appreciated
Thanks

https://github.com/dotnet/SqlClient/issues/1512
This problem is similar, but they only reduced the function V4 to V3 to resolve the issue. However, I do not wish to downgrade the function app. I want to use the Azure Function V4.

@Kumar-Akshay it is better to contact Azure support for this issue. In order to get a better solution for binding area.

authors: JRahnama Kumar-Akshay


text:
Canceling SQL Server query with while loop hangs forever

See StackOverflow post (https://stackoverflow.com/questions/48461567/canceling-query-with-while-loop-hangs-forever?noredirect=1#comment83955305_48461567) here for a full description of the issue.
Essentially, the issue is that for a certain query I am finding that calling CancellationTokenSource.Cancel() hangs indefinitely instead of canceling the query. The same query cancels instantly in SQL Server Management Studio. Here is code the reproduces the issue:
void Main()
{
    var cancellationTokenSource = new CancellationTokenSource();
    var blocked = RunSqlAsync(cancellationTokenSource.Token);
    Console.WriteLine(blocked.Wait(TimeSpan.FromSeconds(1))); // false (blocked in SQL as expected)
    cancellationTokenSource.Cancel(); // hangs forever?!
    Console.WriteLine("Finished calling Cancel()");
    blocked.Wait();
}

public async Task RunSqlAsync(CancellationToken cancellationToken)
{
    var connectionString = new SqlConnectionStringBuilder { DataSource = @".\sqlexpress", IntegratedSecurity = true, Pooling = false }.ConnectionString;
    using (var connection = new SqlConnection(connectionString))
    {
        await connection.OpenAsync().ConfigureAwait(false);

        using (var command = connection.CreateCommand())
        {
            command.CommandText = @"
                WHILE 1 = 1
                BEGIN
                    DECLARE @x INT = 1
                END
            ";
            command.CommandTimeout = 0;
            Console.WriteLine("Running query");
            await command.ExecuteNonQueryAsync(cancellationToken).ConfigureAwait(false);
        }
    }
}

Thanks for the update @divega . Now that there is renewed focus on SqlClient, can this be labeled as a bug? It's clearly buggy behavior and as more and more people shift to using async queries passing through the RequestAborted cancellation token from ASP.NET Core I anticipate that this will come up more frequently.

The explanation at https://github.com/dotnet/SqlClient/issues/44#issuecomment-362757646 makes me wonder if async (i.e. CancellationToken-based) cancellation should have a similar implementation to SqlCommand.Cancel(), e.g. using Attention messages.
However I think it in https://github.com/dotnet/SqlClient/issues/109 we were seeing async cancellation work correctly, so I am not sure I understand this issue.
cc @Wraith2, @roji, @saurabh500

This isn't the same issue as #109 and @EgorBo is spot on at pinpointing the problem. At the moment a lock is taken in EndExecuteNonQuery and then in TdsParserStateObject.Cancel the lock is attempted and cancellation isn't allowed if it can't be acquired.
If I take out that acquired check meaning that it'll take the lock if it can but will still cancel even if it can't get it then the test works. The rest of the manual test suite also passes.

It's not clear to me what the upshot of this is. It sounds like both CancelAsync and CancellationToken based cancellation are deadlocks waiting to happen? What's the recommended way to cancel an ongoing SQL query, preferably asynchronously?

The fix was blocked by https://github.com/dotnet/SqlClient/pull/248 which is still waiting.

@Wraith2 the PR you linked is now merged. Does that fix this issue or just open the door for fixing it?

declare @index int ;
set @index = 3;
declare @maxIndex int
declare @id nvarchar(10);
set @maxIndex = (select count(*) from aspnetusers);
while (@index <= @maxIndex)
begin
set @id = (select id from aspnetusers where Id = @index)
print 'id : '+ @id
set @index = @index+1;
end

@keivansahebdelfard does your post mean that you are still having this problem? If so can you post the version of SQLClient that you're using and the minimal code that you use with that sql statement please.

Just to add more details about this issue, this is actually reproducible all the way till System.Data.SqlClient v4.6 (.NET Framework) (didn't go further, but this is an initial design issue).
Neither of the two APIs SqlCommand.Cancel() or CancellationTokenSource.Cancel() work for Async APIs. The above repro can be tried against any driver, all hang on Cancellation. SSMS is probably using Sync APIs that's why this is not seen there.
The cause of issue as also pointed by @Wraith2 correctly (https://github.com/dotnet/SqlClient/issues/44#issuecomment-494950240) is the lock handling design in this case. The PR #956 is looking good so far, but tests need adjustment as tests have been based on current buggy behavior so we shall fix them next week and bring the PR to readiness.
cc @saurabh500
Below 2 solutions can be used as workaround, based on requirements:
Option 1. Use Sync APIs to execute query and cancel command when needed. Example below:
        static void RunTest(string connString)
        {
            var cancellationTokenSource = new CancellationTokenSource();
            using var connection = new SqlConnection(connString);
            connection.Open();
            using SqlCommand command = connection.CreateCommand();
            Task t = Task.Run(() => RunSql(command));
            Thread.Sleep(5000); // Wait 2 seconds.
            command.Cancel(); // does not hang
            Console.WriteLine("Finished calling Cancel()");
            t.Wait();
        }

        static void RunSql(SqlCommand command)
        {
            command.CommandText = @"
                WHILE 1 = 1
                BEGIN
                    DECLARE @x INT = 1
                END
            ";
            command.CommandTimeout = 0;
            Console.WriteLine("Running query");
            command.ExecuteNonQuery();
        }

Option 2. Set Command Timeout to cancel query after certain duration.
        static void RunTest(string connString)
        {
            using var connection = new SqlConnection(connString);
            connection.Open();
            using (SqlCommand command = connection.CreateCommand();
            Task blocked = RunSqlAsync(command);
            Console.WriteLine(blocked.Wait(TimeSpan.FromSeconds(1))); // false (blocked in SQL as expected)
            blocked.Wait();
        }

        static async Task RunSqlAsync(SqlCommand command)
        {
            command.CommandText = @"
                WHILE 1 = 1
                BEGIN
                    DECLARE @x INT = 1
                END
            ";
            command.CommandTimeout = 5; // Triggers timeout after 5 seconds.
            Console.WriteLine("Running query");
            await command.ExecuteNonQueryAsync().ConfigureAwait(false);
        }

@Wraith2 @saurabh500
Do you have a strong reason to support this lock (in all Async methods):
https://github.com/dotnet/SqlClient/blob/d150725aa1d6a296ebc5153e509b77ea19fe7904/src/Microsoft.Data.SqlClient/netcore/src/Microsoft/Data/SqlClient/SqlCommand.cs#L1367-L1374
We don't have any lock on _stateObj when executing Sync APIs.
Looking at the comment: "_lock on stateObj prevents races with close/cancel" it doesn't make sense to me. Cancel() MUST intercept query execution and Cancel the query immediately (as it does in Sync APIs, so why only hold this lock in Async APIs?)
I also tested after removing this lock, and all tests pass, but I'm continuing to test more complex test cases manually.
Wanted to know your thoughts on that.

In sync cases the lock isn't needed because we don't try to ensure that any objects lower than SqlClientFactory are safe for multithreaded execution, as far as I know. If you use the same command from multiple threads you're in uncharted territory, in reality it'll probably work most of the time as long as you don't try something like executing two readers from a non-mars connection.
In this case either close or cancel must occur and the other must not, they're mutually exclusive for a small portion of the time because multiple pieces of state need to be updated to put the state into either cancelled or returning results, cancel is the more complicated. All i've done in the PR is replace the waited lock with a non waited interlock cmpexchg which prevents wait but might end up with issues where the execute completion is running at the same time as the cancellation logic, from what I can tell as soon as cancellation is set the completion logic will eventually see that fact and throw the correct error but there is the possibility that there could be weird timing cases that weren't possible before because the entire code blocks were mutually exclusive where now only the change of state is exclusive.

as long as you don't try something like executing two readers from a non-mars connection.

Is this even allowed? You can try below code with/without MARS enabled:
using (SqlCommand command = connection.CreateCommand())
{
    async Task RunSqlAsync(SqlCommand cmd) =>
        await cmd.ExecuteReaderAsync().ConfigureAwait(false);

    command.CommandText = @"SELECT @@VERSION";
    RunSqlAsync(command).Wait();

    command.CommandText = @"SELECT @@VERSION";
    RunSqlAsync(command).Wait();
}

We know below relationship is true for MARS as well as non-MARS:
1 SqlCommand = 1 SqlDataReader (owner) = 1 TdsParserStateObject (cached) = 1 SessionHandle
For MARS, we have multiple session Handles, which multiplies everything:
1 SqlConnection = n SqlCommand (parallel) = n SqlDataReader (parallel resp.) = n TdsParserStateObject (cached) = n SessionHandle
[This is as per design]
So, there's only 1 SqlDataReader allowed at a time on a SqlCommand, and you cannot "Execute" multiple times on 1 SqlCommand which is = 1 StateObj, so why lock it? The comment also only mentions about Close/Cancel race condition with execute - but we WANT to intercept here, no?

Is this even allowed?

With waits yes it's allowed because they're serialized. Without waits no in both synchronous and asynchronous modes because you're only allowed to have one owner per parser and the reader takes ownership as it executes. Moreover there's plenty of checking at call time to make sure there's only one asynchronous operation of any type executing at any time. Multi threading in both scenarios is supported through cheap creation of multiple connections and linked objects.
The locking is to ensure that only one thread is mutating the parser and state object at any given time because the state transitions cause multiple variables to be changes you can't have partial interleaving. You can do this in a course way with locking which just prevents entry to the critical section but incurs waits or you can do it with interlock gates which prevents the wait but means you have to be really careful about ordering of gate checks. The locking is far easier to understand and work with.

It's not allowed with waits too. You have to close first DataReader and then execute again.
Technically if that was an issue - you could execute same command from 2 threads synchronously too - but that's just Bad Practice.

It depends on exactly what RunSqlAsync does but I agree with your description. From my reading of the code in the past executing two sync commands from two threads concurrently will throw an exception when the state object is found to be owned by another reader but as you say it's a Bad Idea so lets not worry about that.

You can do this in a course way with locking which just prevents entry to the critical section but incurs waits or you can do it with interlock gates which prevents the wait but means you have to be really careful about ordering of gate checks. The locking is far easier to understand and work with.

I'm lacking most of the context here, but just wanted to mention that as long as no contention is anticipated, locks aren't expensive - taking a free lock is generally a very cheap operation. I wouldn't go into lock-free CompareExchange or similar for perf reasons unless contention is anticipated (which doesn't seem to be the case - this seems to be just a guard against invalid user behavior) and the perf benefits are demonstrated.

It isn't really a problem of how expensive the locks are because as you say they're pretty cheap most of the time. The problem is that the EndExecute process inside the library is taking a lock very early and holding it for a long time and because that same lock is required for cancellation it prevents cancel, it effectively serializes it to occur after the wait so you'll get a cancellation but it won't happen until the query is finished which isn't the intention.
the compareexchange isn't for perf it's just for making the state transition atomic and preventing both EndExecuteInternal (which is Close from the data reader confusingly) and Cancel can't both be executing in a way that they think they've succeeded. Instead of locking to serialize we use the successful change of state to identify the "winner" and let them execute.

We are having a similar issue but with Reader.ExecuteReadAsync which hangs without respecting cancellationToken we pass to it when reading large rows. Any suggestions on the workaround before fixing is in place?

There isn't a workaround because the cancellation isn't respected. The PR's that might fix the problem are in review.

@katwan the only workaround I know of is to use the synchronous ExecuteReader API with SqlCommand.Cancel()

@cheenamalhotra what version of Microsoft.Data.SqlClient is this fixed in? I'm a bit confused because the related PRs are in a different repo.

It's in https://github.com/dotnet/SqlClient/releases/tag/v4.0.0-preview2

But the change log for the 4.0 release says the issue was fixed. How come?

@abatishchev this seems like an oversight. Thanks for finding it. We will fix the documentation.

Current alternative:
// Register cancellation token to cancel command after command timeout, e.g. 5 seconds like under:
CancellationTokenSource source = new();
source.CancelAfter(5000);
source.Token.Register(() =>
{
    Console.WriteLine("Cancelling operation.");
    sqlCommand.Cancel();
});

// Instead of calling:
await sqlcommand.ExecuteReaderAsync(source.Token); // which gets stuck due to this issue

// Call sync API wrapped in a task that will cancel with token as well:
await Task.Run(() => sqlCommand.ExecuteReader(), source.Token))

// or simply call:
sqlCommand.ExecuteReader(); // as command will be canceled with token canceling this execution.

Current alternative:

Thank you for your response @cheenamalhotra!
But, with what you're proposing, doesn't it mean that we'd have a thread blocked on each sync ExecuteReader(), risking thread exhaustion and higher memory pressure?

I just stumbled upon this issue as well. I have a command with an infinite timeout doing WAITFOR (RECEIVE ...), TIMEOUT 1000 in a loop until it receives something. I am unable to cancel it.
Thread 35048:
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync
[Managed to Native Transition]
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.TdsParser.TryRun(Microsoft.Data.SqlClient.RunBehavior runBehavior, Microsoft.Data.SqlClient.SqlCommand cmdHandler, Microsoft.Data.SqlClient.SqlDataReader dataStream, Microsoft.Data.SqlClient.BulkCopySimpleResultSet bulkCopyHandler, Microsoft.Data.SqlClient.TdsParserStateObject stateObj, out bool dataReady)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlDataReader.MetaData.get()
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(Microsoft.Data.SqlClient.SqlDataReader ds, Microsoft.Data.SqlClient.RunBehavior runBehavior, string resetOptionsString, bool isInternal, bool forDescribeParameterEncryption, bool shouldCacheForAlwaysEncrypted)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader(bool isInternal, bool forDescribeParameterEncryption)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.InternalEndExecuteReader(System.IAsyncResult asyncResult, bool isInternal, string endMethod)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.EndExecuteReaderInternal(System.IAsyncResult asyncResult)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.EndExecuteReaderAsync(System.IAsyncResult asyncResult)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.InternalExecuteReaderAsync.AnonymousMethod__201_1(System.IAsyncResult asyncResult)
System.Private.CoreLib.dll!System.Threading.Tasks.TaskFactory<System.__Canon>.FromAsyncCoreLogic(System.IAsyncResult iar, System.Func<System.IAsyncResult, System.__Canon> endFunction, System.Action<System.IAsyncResult> endAction, System.Threading.Tasks.Task<System.__Canon> promise, bool requiresSynchronization) Line 507
System.Private.CoreLib.dll!System.Threading.Tasks.TaskFactory<Microsoft.Data.SqlClient.SqlDataReader>.FromAsyncImpl.AnonymousMethod__0(System.IAsyncResult iar) Line 779
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.BeginExecuteReaderInternal.AnonymousMethod__184_3(System.Threading.Tasks.Task<object> task, object state)
System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(System.Threading.Thread threadPoolThread, System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Line 264
System.Private.CoreLib.dll!System.Threading.Tasks.Task.ExecuteWithThreadLocal(ref System.Threading.Tasks.Task currentTaskSlot, System.Threading.Thread threadPoolThread) Line 2349
System.Private.CoreLib.dll!System.Threading.ThreadPoolWorkQueue.Dispatch() Line 913
System.Private.CoreLib.dll!System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Line 102
...

Thread 34880:
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.TdsParserStateObject.Cancel
Waiting on lock owned by Thread 35048, double-click or press enter to switch to thread]
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.TdsParserStateObject.Cancel(object caller)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlDataReader.Cancel(Microsoft.Data.SqlClient.SqlCommand command)
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.Cancel()
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.CancelIgnoreFailure()
Microsoft.Data.SqlClient.dll!Microsoft.Data.SqlClient.SqlCommand.CancelIgnoreFailureCallback(object state)
System.Private.CoreLib.dll!System.Threading.CancellationTokenSource.Invoke(System.Delegate d, object state, System.Threading.CancellationTokenSource source)
System.Private.CoreLib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state)
System.Private.CoreLib.dll!System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(bool throwOnFirstException)
...

authors: Greg-Smulko JRahnama Samirat Wraith2 abatishchev cheenamalhotra divega katwan keivansahebdelfard madelson marcOcram roji