The odd-even integer example obfuscates the article

Type of issue
Other (describe below)
Description
Ineffective example presented before an adequate explanation of functionalit y.
[Enter feedback here]
Page URL
https://learn.microsoft.com/en-us/dotnet/csharp/linq/standard-query-operators/grouping-data
Content source URL
https://github.com/dotnet/docs/blob/main/docs/csharp/linq/standard-query-operators/grouping-data.md
Document Version Independent Id
6a93a042-3dc5-7e82-a325-8937c72e46c2
Article author
@BillWagner
Metadata

ID: 9cf476b1-17c4-9405-196a-6e26b15248e8
Service: dotnet-csharp
Sub-service: csharp-linq

Related Issues

Hi @ClarkFrazier
I'd like to learn more about what you want different here. That example does serve the purpose of explaining the syntax using an obvious grouping. Do you want the explanation before the sample? Or do you have a different example to suggest?

Hi Bill,
Thank you for responding.
What do LINQ methods do and what are their inputs and outputs? Perhaps the order below would be useful. Is the syntax needed before the explanation? Suggested order:

A clear explanation of what the statement does in a single sentence or short paragraph.
A clear definition of query parameters (any that apply): Common table parameters, select list, ( into) new table, (from) data sources, (where) search conditions, group by, having, partitioning, and order by. Also, if applicable, union, except, and intersect to expand or reduce the result set.
Suggested usages.
Use case examples to illustrate syntax using string parameters in addition to integers.

If a query does not work, use case examples may help. Simple list and integer use case examples could show a pathway to more complex use cases. Are there examples using strings and dictionaries in addition to integers and lists? Is there a recommended way to build a partitioned list of source data elements grouped by the form key?
I am working on a small project that merges two Excel data sources mapped in a third Excel spreadsheet to populate a PDF form. A few years ago I built and application with Transact-SQL stored procedures to merge Excel instance, catalog, and mapping spreadsheets into SQL Server tables that define eBay listings. This project was intended to replicate some of the SQL Server functionality to user environments where SQL Server might not be available. One objective of the code rewrite is to minimize use of for or foreach loops for repetitive operations. The initial c# version made do with traditional C language style elements including multiple switch statements embedded in a foreach loop. The new code flattens the merged dataset definition joining a row from source data with a row in a catalog data into a dictionary with unique keys from the mapping spreadsheet. Each row is associated with an action and a form key. Some form keys associate with multiple actions, requiring a group by to build a form key list. Elements associated with each form key are processed as directed by an associated action into a unique, merged, or no-action form element.
Does a LINQ and set operations for SQL Server developers document exist?
I hope this helps.
Thank you,
Clark Frazier
From: Bill Wagner @.>
Sent: Tuesday, November 19, 2024 8:10 AM
To: dotnet/docs @.>
Cc: ClarkFrazier @.>; Mention @.>
Subject: Re: [dotnet/docs] The odd-even integer example obfuscates the article (Issue #43627)
Hi @ClarkFrazierhttps://github.com/ClarkFrazier
I'd like to learn more about what you want different here. That example does serve the purpose of explaining the syntax using an obvious grouping. Do you want the explanation before the sample? Or do you have a different example to suggest?

Reply to this email directly, view it on GitHubhttps://github.com/dotnet/docs/issues/43627#issuecomment-2485672456, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANHIF6HIKIDB27O62754W3D2BM2BBAVCNFSM6AAAAABSAHKMQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBVGY3TENBVGY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


integrated face landmrak detection into React, use Tensorflow-model

Add brach AI into branch master

Jun_04_2021: JaneTran merged pull requests


elderwoman, conditionally (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Vesting optimization

added VestingLogic, will be deployed once
split Proxy on Proxy and UpgradableProxy
Vesting, TeamVesting are simple proxies without upgradability (Proxy is a base contract)
Vesting implements function governanceWithdrawTokens with simple revert to disable this feature

got it. you're overwriting the governanceWithdrawTokens

got it. you're overwriting the governanceWithdrawTokens

Yes,
The difference of these 2 vesting contracts is only one function governanceWithdrawTokens.
Vesting shouldn't support it
TeamVesting should support it
I've disabled this feature for Vesting:
function governanceWithdrawTokens(address receiver) public { 		revert("operation not supported"); 	}
Had to change inherinace order, otherwise it will be disabled for TeamVesting as well.

One request and one remark.
I think, we should add a function to change the vesting logic address on the vesting factory, should we ever decide to deploy new vesting contracts with an updated logic.
I think, we should set the proxy owner to 0 for all vesting contracts which are not under control of the team multisig, because neither the team nor the governance should be able to adapt investor vesting contracts. Neither do we want to allow the investor changing the logic himself.

I think, we should add a function to change the vesting logic address on the vesting factory, should we ever decide to deploy new vesting contracts with an updated logic.

Added setVestingFactory to VestingRegistry.
We will be able to redeploy VestingFactory and VestingLoigc,
functions of VestingFactory can be invoked only by VestingRegistry.

I think, we should set the proxy owner to 0 for all vesting contracts which are not under control of the team multisig, because neither the team nor the governance should be able to adapt investor vesting contracts. Neither do we want to allow the investor changing the logic himself.

Vesting and TeamVesting contract doesn't have function setImplementation.
I've added _setProxyOwner(address(this)); to mark explicidly than noone will be able to invoke it even if contracts inherited from UpgradableProxy accidentally.


Add support for Liftbridge input

Would you consider to support https://github.com/liftbridge-io/liftbridge input please ?

Hey @muhlpachr, sounds good. Should probably add an output component at the same time. This looks fairly straight forward to implement.

@Jeffail is not nats output enough for output to Liftbridge ?

Any update on this? Would love this integration!

@danthegoodman1 Thank you so much for the reminder! I've been meaning to schedule this work for some months now, but kept getting distracted... I'll make it happen this month and please keep me honest!


Error creating inline completion item provider: TypeError: undefined is not a function

This error appears in the current main (32d2271db7b4d1a1aaab68805f85246e6dd28353).
The currernt main uses codyCommit: www.github.com/sourcegraph/cody/commit/8ffe0d93448e33072a29e2a780e4a35a6d5a869c.
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent - Error creating inline completion item provider: TypeError: undefined is not a function
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at _SectionHistoryRetriever.dispose (/snapshot/dist/agent.js)
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at /snapshot/dist/agent.js
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at Array.forEach (<anonymous>)
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at DefaultContextStrategyFactory.dispose (/snapshot/dist/agent.js)
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at ContextMixer.dispose (/snapshot/dist/agent.js)
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at InlineCompletionItemProvider.dispose (/snapshot/dist/agent.js)
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at Object.dispose (/snapshot/dist/agent.js)
2023-12-15 23:43:56,880 [   9116]   WARN - #c.s.c.a.CodyAgent -     at /snapshot/dist/agent.js

The issue happens at start-up. Just runIde.
The issue is related to SectionHistoryRetriever::dispose .
window.onDidChangeVisibleTextEditors and window.onDidChangeTextEditorSelection are expected to be disposables but they are not.

I would appreciate input/help/fix from someone more familiar with TS and the agent's internals.

This diff here might fix the issue
diff --git a/agent/src/vscode-shim.ts b/agent/src/vscode-shim.ts
index 4cc199e2..1350524e 100644
--- a/agent/src/vscode-shim.ts
+++ b/agent/src/vscode-shim.ts
@@ -196,6 +196,7 @@ export const onDidChangeActiveTextEditor = new EventEmitter<vscode.TextEditor |
 export const onDidChangeConfiguration = new EventEmitter<vscode.ConfigurationChangeEvent>()
 export const onDidOpenTextDocument = new EventEmitter<vscode.TextDocument>()
 export const onDidChangeVisibleTextEditors = new EventEmitter<readonly vscode.TextEditor[]>()
+export const onDidChangeTextEditorSelection = new EventEmitter<vscode.TextEditorSelectionChangeEvent>()
 export const onDidChangeTextDocument = new EventEmitter<vscode.TextDocumentChangeEvent>()
 export const onDidCloseTextDocument = new EventEmitter<vscode.TextDocument>()
 export const onDidSaveTextDocument = new EventEmitter<vscode.TextDocument>()
@@ -490,7 +491,7 @@ const _window: Partial<typeof vscode.window> = {
     withProgress: (_, handler) => handler({ report: () => {} }, new CancellationTokenSource().token),
     onDidChangeActiveTextEditor: onDidChangeActiveTextEditor.event,
     onDidChangeVisibleTextEditors: onDidChangeVisibleTextEditors.event,
-    onDidChangeTextEditorSelection: (() => ({})) as any,
+    onDidChangeTextEditorSelection: onDidChangeTextEditorSelection.event,
     showErrorMessage: (message: string, ...items: any[]) => {
         if (agent) {
             agent.notify('debug/message', { channel: 'window.showErrorMessage', message })


Update highcharts to 7.0.3

When do you plan to merge this pull request ?

I've totally forgotten about it. I'll see if I can get some time for it later tonight.
I don't use Highcharts any more, and hardly any Rails, so it's not a high priority for me.
Isn't something like webpacker the correct way for using a JavaScript library in Rails these days? I seem to recall reading that these kinds of gems are not recommended any more, and that it should be managed in a better way.


Debug yaml actions

Type: Feature Request
Run actions locally
Extension version: 0.46.0
VS Code version: Code - Insiders 1.70.0-insider (112b2d050c8398e74360fcb2219af76ad51e8aa5, 2022-07-12T05:17:20.095Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

This sounds like something that another extension could do.


List all accounts in the service

As a developer
I need to implement an API to list all customer accounts
So that other services can retrieve a list of all accounts
Details and Assumptions

The API should return a list of all customers with their names and addresses.

Acceptance Criteria
Given multiple accounts exist
When the API is called without parameters
Then all customer accounts are listed in the response

Estimated Story Points: 3


fix-aws-expired-profile

Description
Update the fromIni method used to retrieve AWS credentials so that it ignores credential file caching.
Without this setting the credentials are read a single time when the extension is started and if the user refreshes the credentials manually via SSO login for example, the extension won't see the refreshed credentials and will continue to throw security token errors. Currently the only way to fix this is to restart VSCode completely.
Checklist

[X] The base branch of this PR is dev, rather than main
[X] The relevant docs, if any, have been updated or created

Screenshots
[ For visual changes, include screenshots. ]
Testing
I have manually tested Imported, Base and Embedded models with AWS Bedrock.
I have expired the AWS credentials and observed the token errors.
I have logged back into AWS and noted the credentials are refreshed and the extension stars working correctly again.

I looked for some better ways to only read from the non-cached copy by detecting errors and by attempting to compare the expiration results from fromIni. Unfortunately, fromIni doesn't return the expiration timestamp, and catching the errors in the client call requiring a large re-setup of the whole client seemed a bit overkill vs just reading each time.


RFQuiltLayout multiple section

Is there anyway to make RFQuiltLayout with multiple section?

the link is no longer valid... I second this !

Any news about this? any other forks around with sections?


Add tests based on how many open fds are at a time

Hi,
We also tried to make some test based on how the open fd reference counts change during grpcfd usage.
It counts the fd-s with the 'fuser' command from linux to get the pids using a file, and then I just grep through the fdinfo under /proc to get the actual open count.
and during ordinary grpc calls I just check how many times the file is opened.
What do you think is it any good?

The linter issues should be fixed,
(well, apart from gosec 204, I couldn't find a solution to that, so ignored that one)
Could you retrigger the linter job here? I ran the linter in a docker image on my machine, so it should report the same errors as here, but here I don't think I have permission to trigger it here.


Error case DOI with processHeaderDocument versus processFulltextDocument

Regarding header/metadata, the following PLOS article is correctly processed with processFulltextDocument service (correct DOI, journal, etc.)
However in case of processHeaderDocument, the wrong DOI is selected (the one for the data at Zenodo), despite correct title and first author.
journal.pone.0263302.pdf
thanks @Aazhar for the error case

Header only
With CRF only, we've got:
                    </monogr>
                    <idno type="MD5">C1A860C14E064D1C9E586BCFC5463C92</idno>
                    <idno type="DOI">e0263302.10.1371/journal.pone.0263302</idno>
                    <note type="submission">Received: July 27, 2021 Accepted: January 16, 2022</note>
                </biblStruct>
                ```

With DL:

                <monogr>
                    <imprint>
                        <date type="published" when="2022-01-28">January 28, 2022</date>
                    </imprint>
                </monogr>
                <idno type="MD5">C1A860C14E064D1C9E586BCFC5463C92</idno>
                <idno type="DOI">10.1371/journal.pone.0263302</idno>
                <note type="submission">Received: July 27, 2021 Accepted: January 16, 2022</note>
            </biblStruct>

**Fulltext:**

with CRF:
```                    <monogr>
                        <imprint>
                            <date type="published" when="2022-01-28">January 28, 2022</date>
                        </imprint>
                    </monogr>
                    <idno type="MD5">C1A860C14E064D1C9E586BCFC5463C92</idno>
                    <idno type="DOI">e0263302.10.1371/journal.pone.0263302</idno>
                    <note type="submission">Received: July 27, 2021 Accepted: January 16, 2022</note>
                </biblStruct>

With DL:
                        <imprint>
                            <date type="published" when="2022-01-28">January 28, 2022</date>
                        </imprint>
                    </monogr>
                    <idno type="MD5">C1A860C14E064D1C9E586BCFC5463C92</idno>
                    <idno type="DOI">10.1371/journal.pone.0263302</idno>
                    <note type="submission">Received: July 27, 2021 Accepted: January 16, 2022</note>
                </biblStruct>


Lambda init timeout when using SFN client

As soon as I add const client = new SFNClient({}); to a lambda using LLRT, I start getting init timeouts with no other errors:
2024-11-19T10:34:33.325Z
INIT_START Runtime Version: provided:al2023.v41
2024-11-19T10:34:43.325Z
INIT_REPORT Init Duration: 9999.76 ms Phase: init Status: timeout
2024-11-19T10:35:43.372Z
INIT_REPORT Init Duration: 60026.37 ms Phase: invoke Status: timeout

Works fine:
export const main = async () => {
    console.log('Test');
};

Times out:
import { SFNClient } from '@aws-sdk/client-sfn';

const client = new SFNClient({});

export const main = async () => {
    console.log('Test');
};

I am using CDK LLRT with version v0.3.0-beta. From the README, SFN is bundled with std-sdk and full-sdk, I have tried both and get the same result. Is there a way to debug these init timeouts?

@richarddavison, I've done a little research into the issues that have been reported.

Looking at the AWS online documentation, it says that there are two types of endpoints: states and sync-states (excluding fips).
https://docs.aws.amazon.com/general/latest/gr/step-functions.html

However, in the actual implementation, there are no sync-states.
https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-sfn/src/endpoint/ruleset.ts

How should we understand this? Is the timeout occurring because we're communicating with a non-existent endpoint?
Perhaps there's some condition that causes the sync- prefix to be added, but I couldn't find it...

I have tested the above concerns and found that they are reoccurring. Please wait for the PR as it will be posted shortly. :)
Before:
// sdk.cfg
...
client-sfn,SFN,states,sync-states,0
...

INIT_REPORT Init Duration: 10009.31 ms	Phase: init	Status: timeout
INIT_REPORT Init Duration: 60060.34 ms	Phase: invoke	Status: timeout
START RequestId: abfbc9a5-bd31-46a1-afac-90c11ac4390c Version: $LATEST
2024-11-19T13:17:02.379Z abfbc9a5-bd31-46a1-afac-90c11ac4390c Task timed out after 60.06 seconds

END RequestId: abfbc9a5-bd31-46a1-afac-90c11ac4390c
REPORT RequestId: abfbc9a5-bd31-46a1-afac-90c11ac4390c	Duration: 60063.16 ms	Billed Duration: 60000 ms	Memory Size: 128 MB	Max Memory Used: 16 MB

After (The info log itself has no meaning):
// sdk.cfg
...
client-sfn,SFN,states,0
...

START RequestId: e4f6ca93-e850-4481-9e05-509f77d71540 Version: $LATEST
2024-11-19T13:21:16.333Z	e4f6ca93-e850-4481-9e05-509f77d71540	INFO	[{
    Task Name: 'cjs',
    ops/sec: '15614',
    Average Time (ns): 64043.89050751921,
    Margin: '±187.11%',
    Samples: 2128
  } ]
END RequestId: e4f6ca93-e850-4481-9e05-509f77d71540
REPORT RequestId: e4f6ca93-e850-4481-9e05-509f77d71540	Duration: 508.20 ms	Billed Duration: 568 ms	Memory Size: 128 MB	Max Memory Used: 24 MB	Init Duration: 59.40 ms

@nabetti1720 Amazing, thanks for looking into it!


:fire: Chore: Remove trpc package

Description
Removing trpc package in favor of doing a custom json rpc server implementation. Couldn't find a good typesafe way of building a json rpc package so in next pr we will create one that is similar to trpc but more minimal and capable of doing generics
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #750   👈

PR #751

This stack of pull requests is managed by Graphite.


Deployment broken with Composer 2.0 release

Deployer version: 6.0.8
Deployment OS: macOs 10.15.7 -> Debian 8

Ever since the release of composer 2, all my deployments fail on every server, multiple projects are affected… weirdly enough, manually doing a composer install on the server with composer 2 works without any problems.
Also, composer is giving this issue when deploying with deployer

You are using the deprecated option "--no-suggest". It has no effect and will break in Composer 3.
a possibility to manually choose, which composer-version to use would help as a quick fix

Fixed in v7.


move scaling e2e provider implementation

See also https://github.com/giantswarm/aws-operator/pull/1532.

I must have missed something there, but why are we moving this?

I would like to get the dependencies more straight so that AWS is not broken when we have issues with Azure deps.


Feature from strings to things part 1

[0.47.0] - 01-12-23
Deprecated

type_mapping in rules replaced by value_types

nice cleanup


Gwen ban not working

A k'sante ban shows an empty slot on the ban screen.

Will need to use champion.id instead of champion.name here.
https://github.com/Monkey-Bubble/lol-pick-ban-ui/blob/b68cb90815d3eb7df9f9233a435c480a70dc782c/backend/state/converter.ts#L41-L43

18b93cf2c0c122327a4d7a593cd215463c398d87 and e48da4994112c54d7833b1ddd624e70a37219acb should fix this. 🙏


split markline for series

What problem does this feature solve?
Hi ,
We are food data company . Our  hardware device is put into pallet of food like fruits and move along with  it during its journey from farm to retail store. During the whole process our device capture temperate, location (Lat/Lon) and time and through software we plot a chart. Through out this journey food are supposed to be in certain temperature range. This is where we want to use your chart component  and render the information .
As of now we have been assuming  the any food will  have same  min and max temperature range so current

But looks like that is not the case Min and Max temperature range could vary depending where it is something like this (Doing in MS Power BI)

We want markline should end within series (not for whole chart area) . I tried to explore mixing step series with current line but could not do it. I could not find any pointer  how to  keep markLine within series a .
Current code is something like :
``
seriesData.push({
type: 'line',
markLine: {
data: [
{ yAxis: graph.TempThreshold.MaxTemp, name: 'Max Temp', lineStyle: { color: 'red' } },
{ yAxis: graph.TempThreshold.MinTemp, name: 'Min Temp', lineStyle: { color: 'black' } }
]
}
});
getLegData(graph).forEach(function (data) {
data.points.sort();
seriesData.push({
name: 'Temperature (°C)',
type: 'line',
smooth: true,
areaStyle: { type: 'default' },
data: data.points,
color: data.leg.HexColour
});
});
``
What I am playing with :
 categorizedData.forEach(function (data) {                 data.points.sort();                 seriesData.push({                     name: 'Temperature (°C)',                     type: 'line',                     smooth: true,                     areaStyle: { type: 'default' },                     data: data.points,                     color: data.leg.HexColour,                      markLine: {                         symbol: ['none', 'none'],                         data: [                              { yAxis: data.tempBand.MaxTemp,name: 'Max Temp',lineStyle: { color: 'red' } },                             { yAxis: data.tempBand.MinTemp ,name: 'Min Temp',lineStyle: { color: 'black' }}                         ]                     }                 });                            });
But it renders like

I was wondering if you could provide some pointers  so that I can keep marklines in series .
Thanks
Shishir
What does the proposed API look like?
Non API

Hi. Current markLine supports start point and end point, so it's feasible to draw an average line at certain series x range. I made a demo for you. Hope that helps.
https://gallery.echartsjs.com/editor.html?c=xGRArg81F&v=1

Thank You . It was helpful .


Most (all?) integration parameters are not in the RTL

Table 2 says

Parameter name
Width
Description

APB_ADDR_WIDTH
32
Width of the APB Address field. Default to 32.

APB_DATA_WIDTH
32
Width of the APB Data field. Default to 32.

APB_USER_REQ_WIDTH
TODO
Width of the APB PAUSER field.

CPTRA_SET_MBOX_PAUSER_INTEG
5
Each bit hardcodes the valid PAUSER for mailbox at integration time.

CPTRA_MBOX_VALID_PAUSER
[4:0][31:0]
Each parameter corresponds to a hardcoded valid PAUSER value for mailbox, set at integration time. Must set corresponding bit in the CPTRA_SET_MBOX_PAUSER_INTEG parameter for this valid pauser override to be used.

CPTRA_DEF_MBOX_VALID_PAUSER
32
Sets the default valid PAUSER for mailbox accesses. This PAUSER is valid when any VALID_PAUSER is unlocked or not set by INTEG parameter.

CPTRA_SET_FUSE_PAUSER_INTEG
1
Sets the valid PAUSER for fuse accesses at integration time.

CPTRA_FUSE_VALID_PAUSER
32
Overrides the programmable valid PAUSER for fuse accesses when CPTRA_SET_FUSE_PAUSER_INTEG is set to 1.

but, for example, APB_ADDR_WIDTH does not exist in the RTL.

Unfortunately these are spread around the design and not conveniently located for integrators. We will consolidate these into one place at the top wrapper level for a future release.
I will update the integration spec to fix the names and add where they exist.


Enable add/remove routes after server starts

Use a map instead of slice to hold routes for each configuration
Issue a serial number for the route added in order to remove them later
Ensure Add/RemoveRoute is thread-safe by using a lock to guard write to the routes, because each write to router has its own serial number, racing condition only exists during registration. The lock should have minimal affect during serving.

All the renamings in this PR obscure the actual change you're trying to make.
Can you split your changes into two parts, or refrain from renames for now?

I separated the test refactoring in a #16, and I would do rebase and squash after that is check in.

Adding routes only works for an already registered ipPort. The stuff in done in tcpproxy.Start() - looping over configs and calling p.netListen() is not done again.
For removal of a route, it would be nice to cancel onging connections for this route. This would require a map or list of ongoing connections for a route


add multiple caches for accelerating available container count calculation

Description...
This pr is for reopening for previous approval pr : https://github.com/confluentinc/parallel-consumer/pull/644
Explanation

introduce cache for ready-to-be-retried container count (could be selected to retry containers). Therefore the
actually available count = all available container count - (still pending for running retry containers count)
The caches calculation happens when containers are selected to run user function (before / after)
The available work containers will change only after the container selection, therefore it is accurate to update the cache at this point.
no extra threading needed in this solution comparing to previous one
The improvement is substantial. The performance of lessKeysThanThreads  has been improvement from 01:24 -> 00:38

prev flow

current flow

Possible Question
Q : Previously the expired retry is calculated on fly which looks more accurate than new flow?
A : Actually they will be eventually same since for controlLoop, it will wait for <= (latest retry time) and it will update the caches. Previous flow, the available work container count also only update after (latest retry time)
Checklist

[ ] Documentation (if applicable)
[x] Changelog

@rkolesnev Thanks for your comments. I am open for your advices if you have better idea.
But I want to point out that the performance gain is substantial and I kind of interesting to know how the counter will be off.
And I think I also agree with you that less threading model will be always a better choice.
Anyway, looking forward to your example. We could also chat in the slack

@rkolesnev @eddyv could you help review again?
I have introduced another way of implementation without extra threading to address @rkolesnev 's concern.

@rkolesnev @eddyv could you help review again? I have introduced another way of implementation without extra threading to address @rkolesnev 's concern.

@sangreal - yes I had a quick look - will review / step through in depth when I have a chance, thanks!

@rkolesnev Thanks for letting me know the jenkins is recovered. I have updated pr for minor issues to fix the jenkins build.
Please help review when you have time.
Thanks

There is a bit missing for tracking the counts in ProcessingShard.removeStaleWorkContainersFromShard() - i think it would need to remove from retryQueue, check and decrement expiredRetryContainerCnt and the main availableWorkContainerCnt.

Hmm the more i am getting my head round this the more i think we should solve it in two-fold approach.
Basically we have 3 conditions that make up that count - container meets:
isNotInFlight() && !isUserFunctionSucceeded() && isDelayPassed()
We can directly track the isNotInFlight and !isUserFunctionSucceeded through the counter - as there are specific events that trigger their change - taken as work, succeeded, failed, etc.
But the last one - isDelayPassed() is time based - so we cannot really directly track its state from events - as there are no events - we really should be just checking that by observing during the call to getNumberOfWorkQueuedInShardsAwaitingSelection().
So what i am proposing is to keep the availableWorkContainerCnt and use it to track addition / removal of work containers from shard, and track the isNotInFlight and !isUserFunctionSucceeded() - which it basically does now in this PR, but at the same time remove expiredRetryContainerCnt and retryItemCnt and still scan the retryQueue - at least up to the first container that has its delay not yet expired (as its ordered by retry delay).

@rkolesnev Thanks a lot for your review. I think your solution also a good thought but still have to scan through the retryQueue.
I totally understand your concern but if you could take a look at the above flow diagram and some explanations.
The updates in getNumberOfWorkQueuedInShardsAwaitingSelection could be covered in controlLoop. Because it will only wait for <= (latest retry time = first retryable time) and it will update all caches.
In previous flow, the available work container count also only update after (latest retry time)
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/internal/AbstractParallelEoSStreamProcessor.java#L771
Let me give you an example:
Say now is 00:00, there are two retry items to be retried at 00:02 & 00:05. and there are no pending containers
for old flow:

it will check during every polling in BrokerPollSystem, but the count will stay same which is 0 until 00:02, the count will be 1 and after it processed, it will be back to zero. Until 00:05, the second one will be picked up, then the count will be 1 again.

for new flow:

during every polling in BrokerPollSystem, the count will be not changed since cache is unchanged.
in controlLoop , the Duration timeToBlockFor = shouldTryCommitNow ? Duration.ZERO : getTimeToBlockFor(); , therefore the timeToBlockFor will be <= min(all retry container waiting time). So at 00:02, the controlLoop will be run and updates (there is no blocking call in this loop), and count (expiredRetryContainerCnt -> 1) will be update to 1. Same applied to the second until 00:05, controlLoop will be processed to update the count to 1.

Conclusion

so as you could see, the updates timing is the same between previous and new flow

The problem with updating the available work that is in retry queue and has its delay elapsed is that the expiredRetryContainerCnt is only ever increased in getWorkIfAvailable() - and that only scans up to the number of work requested workToGetDelta:
         while (workTaken.size() < workToGetDelta && iterator.hasNext()) {
            var workContainer = iterator.next().getValue();

            if (pm.couldBeTakenAsWork(workContainer)) {
                if (workContainer.isAvailableToTakeAsWork()) {
                    log.trace("Taking {} as work", workContainer);

                    // only increase the ExpiredRetryContainerCnt when this is retry due since already added in the new container creation
                    if (workContainer.isDelayExistsExpired()) {
                        expiredRetryContainerCnt.incrementAndGet();
                    }
                    workContainer.onQueueingForExecution();
                    workTaken.add(workContainer);
                } else {
                ...

For example if we have 1000 items in the retry queue, all with delay of 5 seconds - once the delay elapsed - all 1000 are available for work - but we would only update the available work as we are taking them into processing and say with 16 processing threads - we would take only 16 and the rest will still be in retry queue but not counted as available work.
On top of that - as we are taking them as work - they will get marked as inFlight and be excluded from the available work count straight away.
So effectively they will never show up as available work.
Implications of this is that BrokerPoller will be polling for more work instead of applying back-pressure and pausing consumers - which may lead to OOM / really deep queues etc in extreme / edge cases.
It all goes back to the fact that the retry delay is time based - and the only way to really know which/how many containers in retry queue have their retry delay elapsed and are available as work - is to scan the retry queue.
It does not have to be a full scan - as the retry queue is sorted by nextRetryDueAt - so it would be enough to scan up to the first container that still has the delay that is not elapsed to get the count of available / not available as work in retry queue.
In general i don't think scanning retry queue will have big performance implications - with thinking that - if the retry queue is small - then the scan is fast and if the retry queue is large - than we are in bad state anyway and probably not that concerned about the overhead introduced by scanning it - as processing is already slowed down by having a lot of messages to retry.

@rkolesnev I have updated the pr according to your suggestions, meanwhile I keep the retryItemCnt since this count is accurate and will help the accelerate the expired items calculation while expiredRetryContainerCnt is removed.
Please help review again.

@rkolesnev Thanks for your detailed review. I have fixed according to your comment, except for one. Please help review again

@rkolesnev

// 2. the container has been selected and it is inflight but we already slashed them from availableWorkContainerCnt, so should be counted in
This is not correct - we do not count inflight containers as available for selection.
The intent of the getCountOfWorkAwaitingSelection is to get a number for all work that is ready to be processed - to determine if Consumer should poll for more messages - or there is already enough queued for processing - so that excludes work that is already being processed / inflight.

Regarding this,  getCountOfWorkAwaitingSelection  indeed do get a number for all work that is ready to be processed and excludes inflight messages in the updated logic. This could be reflected in UT.
I think this pr's goal is
(1) ensure getCountOfWorkAwaitingSelection return the correct number
(2) performance improvement
(3) makes the code as concise and clean as possible.
But simple copy old logic might not be the final goal. Looking forward to hearing your idea on this one.

@rkolesnev

// 2. the container has been selected and it is inflight but we already slashed them from availableWorkContainerCnt, so should be counted in
This is not correct - we do not count inflight containers as available for selection.
The intent of the getCountOfWorkAwaitingSelection is to get a number for all work that is ready to be processed - to determine if Consumer should poll for more messages - or there is already enough queued for processing - so that excludes work that is already being processed / inflight.

Regarding this, getCountOfWorkAwaitingSelection indeed do get a number for all work that is ready to be processed and excludes inflight messages in the updated logic. This could be reflected in UT. I think this pr's goal is (1) ensure getCountOfWorkAwaitingSelection return the correct number (2) performance improvement (3) makes the code as concise and clean as possible. But simple copy old logic might not be the final goal. Looking forward to hearing your idea on this one.

Sure - but we have to keep the logic uniform - we cannot exclude inflight work that was never retried, but include inflight work that is being retried - that would just give a weird number / behaviour that differs based on wether the messages were retried or not.
The check would be done only on WorkContainers that are in retry queue and are ready to be retried to determine if they are in fact still in the queue (thus available to be taken as work) or already in flight / being processed (thus not ready to be taken as work).
The implication can be big enough in edge cases. With maxConcurrency of 1000 - in case external system was unavailable for a brief moment - the retry queue can be over 1000 in size and on recovery of external system - 1000 inflight will skew the number available and potentially keep broker poller paused until they all finish processing - leading to delay with polling for more messages etc - as they are deemed as available work instead of not counted as available work.

Let me have another look at the code - i am thinking if availableWorkContainerCnt is already being decremented when we take work inflight - regardless of is it from retry queue or not - so we maybe already accounting for them that way...

Ok - yeah - that is already taken care of by decrementing availableWorkContainerCnt in the ProcessingShard.getWorkIfAvailable(...) call - when we take work into processing. So you are right - we do not need to exclude them again when counting items in retry queue.

Ok - so i am happy enough with it - thank you very much for going back and forth with the PR with me.
Only outstanding bit left is to take care of retryQueue in ShardManager when removing stale work.

Ok - so i am happy enough with it - thank you very much for going back and forth with the PR with me. Only outstanding bit left is to take care of retryQueue in ShardManager when removing stale work.

Thanks for your time for the review! Let me change a bit on my previous pr's code related to stale containers handling and get back to you

@rkolesnev please help check the updates on the stale container removal for retryQueue, thanks a lot for your review again.

Hi @sangreal - the PR is ready to be merged - can you please sign the Contributor License Agreement (CLA)?
You can access it through license/cla status - Details.

Hi @sangreal - the PR is ready to be merged - can you please sign the Contributor License Agreement (CLA)? You can access it through license/cla status - Details.

@rkolesnev I find it quite weird since I signed it last year already since I already contributed. And when I try to check, I could not signed since it showed I already signed. Please let me know if this is a blocker. If it is, I will revoke this one and try sign again.


POC Parquet GEOMETRY logical type implementation

This is a continuation of https://github.com/apache/arrow/pull/43196.
One major issue is that we're special casing the handling of sort-orders for geometry logical types everywhere. I'm not sure if it is better to define another sort-order for geometry so that the sort order is not UNKNOWN.
Another issue is related to Arrow-IO (parquet::arrow::FileWriter and parquet::arrow::FileReader). There are no canonical extension types for geometry in Arrow, so we cannot write parquet files containing geometry columns using the parquet-arrow table writers.

One major issue is that we're special casing the handling of sort-orders for geometry logical types everywhere. I'm not sure if it is better to define another sort-order for geometry so that the sort order is not UNKNOWN.

I think we can use the default SortOrder which is specific to the logical type. IIRC, SortOrder specifies how two values of the same type can be compared and ordered. In the case of Geometry type, I'm not sure if it is comparable. If not, we'd better disable generating min/max values for this type.

Another issue is related to Arrow-IO (parquet::arrow::FileWriter and parquet::arrow::FileReader). There are no canonical extension types for geometry in Arrow, so we cannot write parquet files containing geometry columns using the parquet-arrow table writers.

I think we can just write/read geometry values as binary type. We can add another layer to verify they are WKB values as expected. WDYT?

BTW, I think you may want to create a separate PR against apache/arrow directly to move fast. We can add @paleolimbot as a co-author to respect his great work.

BTW, I think you may want to create a separate PR against apache/arrow directly to move fast. We can add paleolimbot as a co-author to respect his great work.

I agree that a PR directly into apache/arrow is the way to go here. I'm not personally worried about the authorship/coauthorship details (I'm happy to maintain any code I wrote either way 🙂 ).

I've submitted the PR directly to apache/arrow: https://github.com/apache/arrow/pull/43977. We can continue discussion in the newly created PR.

One major issue is that we're special casing the handling of sort-orders for geometry logical types everywhere. I'm not sure if it is better to define another sort-order for geometry so that the sort order is not UNKNOWN.

I think we can use the default SortOrder which is specific to the logical type. IIRC, SortOrder specifies how two values of the same type can be compared and ordered. In the case of Geometry type, I'm not sure if it is comparable. If not, we'd better disable generating min/max values for this type.

Another issue is related to Arrow-IO (parquet::arrow::FileWriter and parquet::arrow::FileReader). There are no canonical extension types for geometry in Arrow, so we cannot write parquet files containing geometry columns using the parquet-arrow table writers.

I think we can just write/read geometry values as binary type. We can add another layer to verify they are WKB values as expected. WDYT?

Sort order for geometry values is not specified, and we're using GeometryStatistics for data skipping. Currently the min/max are generated as if they are plain binary values, I'll disable generating min/max values for geometry values.
We have some very basic tests for plain parquet read/write without using arrow vectors/tables, but we have to implement canonical extension types for geometries to support Arrow-IO. I'll follow @paleolimbot 's guidance and implement an official canonical extension type based on geoarrow.wkb.

Canonical extension type for geometry is out of the scope of Parquet and may require a separate discussion and vote process on the Arrow side. It would be better if they are not mixed in the same PR, IMHO.

apache#43977

I've submitted https://github.com/apache/arrow/pull/43977, and all subsequent reviews and modifications will be done within this PR.  Is there anything else that needs to be done?

Ah, sorry I missed that! I'm still getting pinged for this PR when you push, so maybe close this PR?

Sure. I'll close the PR.


Refs/heads/hello world

Guys Why don't we make an app for women's Safety ..one button away and the marshals reach the area alerted by the woman?

done


Add metrics for accepted and terminated connections

This PR adds metrics for accepted and terminated connections, to be introduced to ranch with https://github.com/ninenines/ranch/pull/301. The collector will still work when used with a pre-#301 Ranch 2.x version, those metrics will not be exported in that case.
The new metrics are named ranch_num_accepted_connections and ranch_num_terminated_connections, and are mentioned accordingly in the README.
It also seemed proper to raise the project version to 0.2.0 with this.

Not 100% sure about this, but... I think gauge is not the correct metric type for connections accepted/terminated. counter is probably what we want, to be used for monotonically increasing values (or reset to 0). Maybe @essen knows?

Counter is the correct way to go. Prometheus automatically detects when it's reset to 0. Otherwise it's always increased which is what counters do.

Ok, I will change as requested.

accepted_connections and terminated_connections are counters now

It's fine now, thank you :)


Feature_Request : Add carousel

Is your feature request related to a problem? Please describe.

add carousel in explore top destination
Describe the solution you'd like

dynamic carousel instead of static cards
Describe alternatives you've considered

Demo Video/Screenshot (Mandatory )

Are you contributing under any open-source program ?

JWOC'24

@PranavBarthwal #38 is already present there with the same issue. Sorry to close this issue. But you can make any new issue


Create manifest pipeline storage

ManifestStaticFilesStorage is generally preferred to CachedStaticFilesStorage (see https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#cachedstaticfilesstorage), so provide a Pipeline storage for it as well.

Thank you for this feature @kronion.
It's been so long since you proposed that I haven't seen it. As there were conflicts due to recent changes, I postpone your changes in one of my commit including AUTHORS participation.


Payload v2.0.x - Deployment fails due to type check

I am on the newest version of Payload 2.0.14. I installed the payload-cloudinary-plugin. Works perfectly in development, zero complaints. Then I tried to commit the changes but it then fails in the build step.
In the payload.config.ts file, if I remove the cloudinaryPlugin() part, the build works. So I am pretty sure that this is the part causing the trouble.
plugins: [cloudinaryPlugin(), payloadCloud()],
I attached the stack-trace but I am not sure how helpful it is and it might be a bit difficult to read. Any idea what might be the issue here ? I am not quite sure whether this is a plugin issue or whether it is an issue with payload.
Nov 1 03:53:06 PM  #13 81.28 src/payload.config.ts(115,13): error TS2322: Type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/config/types").Plugin' is not assignable to type 'import("/home/node/app/node_modules/payload/dist/config/types").Plugin'.
Nov 1 03:53:06 PM  #13 81.28   Types of parameters 'config' and 'config' are incompatible.
Nov 1 03:53:06 PM  #13 81.28     Type 'import("/home/node/app/node_modules/payload/dist/config/types").Config' is not assignable to type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/config/types").Config'.
Nov 1 03:53:06 PM  #13 81.28       The types of 'admin.bundler.build' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28         Type '(payloadConfig: import("/home/node/app/node_modules/payload/dist/config/types").SanitizedConfig) => Promise<void>' is not assignable to type '(payloadConfig: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/config/types").SanitizedConfig) => Promise<void>'.
Nov 1 03:53:06 PM  #13 81.28           Types of parameters 'payloadConfig' and 'payloadConfig' are incompatible.
Nov 1 03:53:06 PM  #13 81.28             Type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/config/types").SanitizedConfig' is not assignable to type 'import("/home/node/app/node_modules/payload/dist/config/types").SanitizedConfig'.
Nov 1 03:53:06 PM  #13 81.28               Type 'SanitizedConfig' is not assignable to type 'Omit<{ admin: { autoLogin: false | { email: string; password: string; prefillOnly: boolean; }; avatar: "default" | "gravatar" | ComponentType<any>; buildPath: string; bundler: { ...; }; ... 11 more ...; webpack: (config: Configuration) => Configuration; }; ... 28 more ...; upload: any; }, "collections" | ... 2 more ...'.
Nov 1 03:53:06 PM  #13 81.28                 The types of 'admin.bundler.build' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28                   Type '(payloadConfig: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/config/types").SanitizedConfig) => Promise<void>' is not assignable to type '(payloadConfig: import("/home/node/app/node_modules/payload/dist/config/types").SanitizedConfig) => Promise<void>'.
Nov 1 03:53:06 PM  #13 81.28                     Types of parameters 'payloadConfig' and 'payloadConfig' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                       Type 'import("/home/node/app/node_modules/payload/dist/config/types").SanitizedConfig' is not assignable to type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/config/types").SanitizedConfig'.
Nov 1 03:53:06 PM  #13 81.28                         Type 'SanitizedConfig' is not assignable to type 'Omit<{ admin: { autoLogin: false | { email: string; password: string; prefillOnly: boolean; }; avatar: "default" | "gravatar" | ComponentType<any>; buildPath: string; bundler: { ...; }; ... 11 more ...; webpack: (config: Configuration) => Configuration; }; ... 28 more ...; upload: any; }, "collections" | ... 2 more ...'.
Nov 1 03:53:06 PM  #13 81.28                           Types of property 'db' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                             Type '(args: { payload: import("/home/node/app/node_modules/payload/dist/payload").Payload; }) => import("/home/node/app/node_modules/payload/dist/database/types").BaseDatabaseAdapter' is not assignable to type '(args: { payload: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/payload").Payload; }) => import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/database/types").BaseDatabaseAdapter'.
Nov 1 03:53:06 PM  #13 81.28                               Types of parameters 'args' and 'args' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                 Type '{ payload: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/payload").Payload; }' is not assignable to type '{ payload: import("/home/node/app/node_modules/payload/dist/payload").Payload; }'.
Nov 1 03:53:06 PM  #13 81.28                                   The types of 'payload.collections' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28                                     Type '{ [slug: string]: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/collections/config/types").Collection; [slug: number]: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/collections/config/types").Collection; [slug: symbol]: import("/home...' is not assignable to type '{ [slug: string]: import("/home/node/app/node_modules/payload/dist/collections/config/types").Collection; [slug: number]: import("/home/node/app/node_modules/payload/dist/collections/config/types").Collection; [slug: symbol]: import("/home/node/app/node_modules/payload/dist/collections/config/types").Collection; }'.
Nov 1 03:53:06 PM  #13 81.28                                       'string' index signatures are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                         Type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/collections/config/types").Collection' is not assignable to type 'import("/home/node/app/node_modules/payload/dist/collections/config/types").Collection'.
Nov 1 03:53:06 PM  #13 81.28                                           The types of 'config.auth.forgotPassword.generateEmailHTML' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28                                             Type 'GenerateForgotPasswordEmailHTML' is not assignable to type 'GenerateForgotPasswordEmailHTML'. Two different types with this name exist, but they are unrelated.
Nov 1 03:53:06 PM  #13 81.28                                               Types of parameters 'args' and 'args' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                                 Type '{ req?: import("/home/node/app/node_modules/payload/dist/express/types").PayloadRequest<any>; token?: string; user?: unknown; }' is not assignable to type '{ req?: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/express/types").PayloadRequest<any>; token?: string; user?: unknown; }'.
Nov 1 03:53:06 PM  #13 81.28                                                   Types of property 'req' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                                     Type 'import("/home/node/app/node_modules/payload/dist/express/types").PayloadRequest<any>' is not assignable to type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/express/types").PayloadRequest<any>'.
Nov 1 03:53:06 PM  #13 81.28                                                       Type 'PayloadRequest<any>' is not assignable to type '{ collection?: Collection; context: RequestContext; fallbackLocale?: string; files?: { file: UploadedFile; }; findByID?: { [transactionID: string]: { [slug: string]: (q: FindOneArgs) => Promise<TypeWithID>; }; }; ... 8 more ...; user: any; }'.
Nov 1 03:53:06 PM  #13 81.28                                                         The types of 'collection.config.auth.forgotPassword.generateEmailHTML' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28                                                           Type 'GenerateForgotPasswordEmailHTML' is not assignable to type 'GenerateForgotPasswordEmailHTML'. Two different types with this name exist, but they are unrelated.
Nov 1 03:53:06 PM  #13 81.28                                                             Types of parameters 'args' and 'args' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                                               Type '{ req?: import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/express/types").PayloadRequest<any>; token?: string; user?: unknown; }' is not assignable to type '{ req?: import("/home/node/app/node_modules/payload/dist/express/types").PayloadRequest<any>; token?: string; user?: unknown; }'.
Nov 1 03:53:06 PM  #13 81.28                                                                 Types of property 'req' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                                                   Type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/express/types").PayloadRequest<any>' is not assignable to type 'import("/home/node/app/node_modules/payload/dist/express/types").PayloadRequest<any>'.
Nov 1 03:53:06 PM  #13 81.28                                                                     Type 'PayloadRequest<any>' is not assignable to type '{ collection?: Collection; context: RequestContext; fallbackLocale?: string; files?: { file: UploadedFile; }; findByID?: { [transactionID: string]: { [slug: string]: (q: FindOneArgs) => Promise<TypeWithID>; }; }; ... 8 more ...; user: any; }'.
Nov 1 03:53:06 PM  #13 81.28                                                                       The types of 'collection.config.auth.verify' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28                                                                         Type 'boolean | import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/auth/types").VerifyConfig' is not assignable to type 'boolean | import("/home/node/app/node_modules/payload/dist/auth/types").VerifyConfig'.
Nov 1 03:53:06 PM  #13 81.28                                                                           Type 'VerifyConfig' is not assignable to type 'boolean | VerifyConfig'.
Nov 1 03:53:06 PM  #13 81.37 error Command failed with exit code 2.
Nov 1 03:53:06 PM  #13 81.37 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Nov 1 03:53:06 PM  #13 81.41 error Command failed with exit code 2.
Nov 1 03:53:06 PM  #13 81.41 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Nov 1 03:53:06 PM  #13 ERROR: process "/bin/sh -c yarn build" did not complete successfully: exit code: 2
Nov 1 03:53:06 PM  ------
Nov 1 03:53:06 PM   > [builder 5/5] RUN yarn build:
Nov 1 03:53:06 PM  #13 81.28                                                                 Types of property 'req' are incompatible.
Nov 1 03:53:06 PM  #13 81.28                                                                   Type 'import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/express/types").PayloadRequest<any>' is not assignable to type 'import("/home/node/app/node_modules/payload/dist/express/types").PayloadRequest<any>'.
Nov 1 03:53:06 PM  #13 81.28                                                                     Type 'PayloadRequest<any>' is not assignable to type '{ collection?: Collection; context: RequestContext; fallbackLocale?: string; files?: { file: UploadedFile; }; findByID?: { [transactionID: string]: { [slug: string]: (q: FindOneArgs) => Promise<TypeWithID>; }; }; ... 8 more ...; user: any; }'.
Nov 1 03:53:06 PM  #13 81.28                                                                       The types of 'collection.config.auth.verify' are incompatible between these types.
Nov 1 03:53:06 PM  #13 81.28                                                                         Type 'boolean | import("/home/node/app/node_modules/payload-cloudinary-plugin/node_modules/payload/dist/auth/types").VerifyConfig' is not assignable to type 'boolean | import("/home/node/app/node_modules/payload/dist/auth/types").VerifyConfig'.
Nov 1 03:53:06 PM  #13 81.28

hey @Jonashr thanks for reporting the issue.
I'll have a look and let you know ASAP

@Jonashr which version of the plugin are you using? I recently published a 2.0-compatible version and I just tested it in my local environment and the build works fine.
Let me know

I was actually having the same error on Payload 1. On payload 2 it seems to be fixed!

Thanks, it works now. I am not sure why it didn't work before and why it works now. I was on the newest version of this plugin, and I started the project from Payload V2 so that can't be the problem. It might be because the lockfile had the older version listed.
I deleted the lock file from the repository and it worked after that. So it might just have been the lockfile that was the problem


Sqaure-Crop People Photos

I'm sure there's something in the image_processing gem that would let us make any images that get uploaded or taken for people's photos squares...

Never mind, found a CSS workaround


Toxic Crooks Take_Pokemon

At the end of Toxic Crooks, you're supposed to give the shiny Seaking back to the fisherman. However, the take_pokemon trigger seems to not be working, even after re-logging (since it's usually a visual glitch).

Resolved thanks the Blitz_Asogi.


getSubscriptions returns localizedPrice containing "," instead of "." in prices

Description
"localizedPrice" key returned in subscription array contains "," instead of "." in prices of Brazil, Europe and monthly prices in US. So if the price in app store is R$ 149.90, localizedPrice returns R$ 149,90.
However for Indian rupees and US yearly prices it returns the correct value i.e Rs 3,999 gets returned as Rs 3,999 but it treats "." in app store prices as ","
The price key in the subscription object is fine, it contains "149.9" but the localizedPrice is wrong, it returns "R$ 149,90"
Expected Behavior
localizedPrice should return the correct pricing as "," and "." in price makes a huge difference. They wont be charged 149,90 but they will see 149,90 in the app. And to show local price we have to use localizedPrice instead of price.
Screenshots
This the subscription object for yearly and monthly subscription with Brazil region. "R$ 149,90" should be "R$ 149.90" in localizedPrice.

Environment:

react-native-iap: 12.10.7
react-native: 0.71.10
Platforms (iOS, Android, emulator, simulator, device): iOS 17.2

To Reproduce
Steps to reproduce the behavior:

Use price with "." in app store like "149.90"
Call setSubscriptions()
Use Brazil region or sandbox user
Check the localizedPrice, it is coming "R$ 149,90" instead of "R$ 149.90"

[Optional] Additional Context
Is this the correct behavior or am I missing something?
Can anyone please guide me

@Garvnanwani I have similar problem. Did you solve it?


add php download links

probably should link to https://www.docker.com/get-docker for install docker section

Let me know how you make out with the install, you may need to do this : https://github.com/lbryio/lbry.io/issues/527#issuecomment-393647193
It will vary by distro or if you are on Windows. Haven't had a chance to update the docs.

@tzarebczan its from Php official site . http://php.net/manual/en/install.php . im install php on windows machine using the method from that site and success

https://www.sitepoint.com/how-to-install-php-on-windows/


Misc Updates, Cleanup After Decaf

EDIT:
Since the diff here was quite large I've change the base to our decaf branch. This means this review only has to consider the actually changes for this PR. Rather than the changes that are present from our decaf branch to the main branch.
Hopefully these changes will make this PR easier to review.

This PR had a few accomplishments.
Originally I had hoped to include the removal of oniguruma since I was optimistic that bcoe/onigurumajs would be a drop in replacement. Unfortunately it is not. I also checked to see if the modifications can be low and use tenbits/oniguruma-js or even use vscode-oniguruma.
But it seems that from the majority of these JavaScript implementations were created before an important API change in node-oniguruma, namely introducing OnigString on PR #46.
Most of these forks don't actually include this functionality, meaning it's not a direct translation anymore. I did attempt at reverting the changes in First-Mate to use this new feature, which I beleive are all contained on this commit, but alas still we had tests failing.
So work will need to continue on removing this native module.

But otherwise for other changes there are plenty here, I've rebranded the links in the package.json, additionally decaffed our Gruntfile.coffee and gutted the majority of it's functionality. Really leaving it to be a task to generate our docs for grunt-atomdoc (Which quick note on that. Now fails because it seems to not understand how to find our docs once we have decaffed. But fixing that is far out of scope for this PR), additionally I've removed all other deps that we no longer need since we have moved away from using grunt for everything.
I did add a new script to run PegJS rather than let grunt do it.
Really the reasoning behind this was because this repo has stayed static for some time, and we have moved mostly away from using First-Mate as the recommended syntax highlighter, I highly doubt we will need to change PegJS code all that much.
So in the unexpected event that we do, all we have to do is run npm run parse and it'll be parsed for us.
With that change in mind I did add this to the ReadMe Documentation, to ensure everyone is aware of this change.
Also speaking of PegJS, I've updated PegJS to the latest version, and ran the parsing again. Still all tests pass, but the diff on scope-selector-parser.js is huge because of this. I would not recommend reviewing this manually as this was an automated change, that has no effect on our tests passing.
But besides a few other dep bumps, that's all thats contained in this PR. The diff is large and I apologize, but that's because I'm targeting all the approved decaf changes to our master branch now. Meaning those are showing up in this review as well. I'd personally recommend looking at the commits themselves, and everything after 56b7f8f27cdfc6ed542058867c9f45dc9cfe19de is what has actually been changed on this PR.
Thanks to anyone that is able to review!

Sorry for not noticing this right away. For ease of review this PR can target the decaf branch, and then for ease of merging to master you can switch the target branch to master at the last minute?
(And if this gets merged to the decaf branch a final merge of the decaf branch over to master would also be pretty clean.)
THAT SAID I will probably not be doing much review of this JS, unless no-one else does and if the diff is small enough and obvious what it is about. I'll note that tests are passing, so that's a pretty good sign.

Good call. I've gone ahead and targeted the decaf branch for this PR. Once this is approved I will create another PR from decaf to main. But otherwise thanks for taking a look at this.

Bumping this PR. While generally we don't like to merge code changes that are not fully reviewed, I'm hoping to get this merged prior to seeing if we can move this into the core editor.
Again all tests are passing here, so anyone that wants to take a look feel free to do so.

Thanks for the approval @mauricioszabo I'll get this one merged!


BugID:16953820: Environment Monitoring based on LD

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


feat: add ibotta/sopstool

ibotta/sopstool: SOPS multi-file wrapper
$ aqua g -i ibotta/sopstool

issue: https://github.com/aquaproj/aqua-registry/issues/1171

Thanks.

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.39.0


feat: add an enhanced layer for BigQuery Storage v1 client

This pull request creates an enhanced shim layer in the BigQuery Storage API v1 client in order to apply a streaming resumption strategy for the ReadRows method.

First commit copies the enhanced shim layer from v1beta2, since v1 and v1beta2 APIs are identical.

The files in this commit are just a copy, with no changes, from v1beta2. The commit exists just to make it easier to review the actual changes that are in the second commit.

Second commit just updates the version of the files from the v1 enhanced shim layer

@kmjung , please review the changes.

LGTM.


Issue with live transcription

When there is no audio, the client() keeps on re-transcribing past audio.
`from whisper_live.client import TranscriptionClient
client = TranscriptionClient(
"localhost",
9090,
lang="ja",
translate=False,
model="small",
use_vad=False,
)
result = client()
print(result)`
#result: に厳しい処分が必要と答えた人が 61%に登ることが世論調査で分かりました調査はこの土日にご覧の方法で行いました岸田内閣を 指示できるという人は、前回の調査から0.1ポイント下落し、 22.8%で、6ヶ月連続で過去最低を更新しました。
The audio stops after 20 seconds but the results keep getting modified with past texts. How to solve this issue?
thank you !!

@uttam-scai I see that you use WhisperLive with a microphone. So, we consider the last segment recieved from the model as something which might change because in the current audio chunk there is a high possibility that the last word might have been cut and not fully captured in the current audio chunk so, i hope you only see the last part of the transcription which changes and not all of it.
So, if you keep talking on the microphone the transcription must stabalise and only part of it should be prone to change.

@makaveli10 thank you for your quick response. Actually when the audio stops completely for sometime, the print result fluctuates with repeating previous words.
Is it possible to keep the entire transcript ? May you please guide me to any code that can help me to save entire conversation transcript till the mic was on?
Thank you !!
I want to pass the transcript to an LLM for my work. It will be a great help #thankyou


UI for the node reset key

User Story
we need to add UI for the node reset key.

we have implemented already.
reference issue: https://github.com/chef/automate/issues/4917


Discovery: Add links to useful guides in Exhibition pages (design)

We would like to find out how useful it would be to use a component similar to what we have in exhibition guides, but on Exhibition pages themselves. This could facilitate finding the relevant content for our users and make our offer more obvious. Links to exhibition guides and other exhibition-specific content are currently a link in the body text.

This was an idea Jenn had, first step would be to discuss with Dom and/or try it under a toggle.
Devs need to also think about how these could be linked. Is it a new field in Prismic? Is there a way to link the contents together and make it dynamic?
Background
[JPB] We have a family of content formats that support an exhibition: exhibition guides and the content formats contained within; PDF sensory maps; other related content as expressed like this:
https://miro.com/app/board/uXjVME3nANE=/

These are currently treated as links in body text, but there's no visual hierarchy or way to call each of these content items as a useful thematic grouping. These content formats are unlikely to have featured images that can be reappropriated for a card, but they still would benefit from having a more dominant presence on the page. We already have the idea of a solid colour card/link style, as currently used in the exhibition guides. Can we design something that has a logical rationale and consistent usage? How might we reuse what we already have?
The aims are to

make the related content more visible in the context of an exhibition page
create a useful visual hierarchy on an exhibition page
enable a dynamic relationship between an exhibition and the related content

Done when

I've been exploring several card variations that would be beneficial in helping to establish more of a hierarchy with the access content within an exhibition page):
Version 1 (minimal/default styling option): https://zpl.io/KGW3r4E
The idea behind these "cards" is to help establish the different forms of repeatable WC access content as important/helpful resources to click on. Any extra publications that may be created would stay as text links as shown in the mockup.
The digital exhibition guide and the visual story cards have arrows as a subtle indication that there's an onward journey to a new webpage. As those pages don't have a featured image, these cards don't either.
The sensory map and visual story pdf cards are slightly different in that they do images (the front cover of the pdfs), have a download icon. Ideally the whole card would be clickable rather than just the text in each card.
Version 2 - adding colour: https://zpl.io/mDqmQ16
Building on version 1, I tried using colour in a more subtle way than currently used in the digital exhibition guides.
Version 3: https://zpl.io/8lx3ryK
Same as version 2, but with a section background to differentiate the access content even more.
@rcantin-w @davidpmccormick Starting with Version 1, I'd like to find out how feasible it would be to have a new card style like this in Prismic specifically for access content, and whether you foresee any major tech issues/constraints (I imagine the two colour layout will be one?)


add wise ui startup time to the stats page

put moment-timezone in the top level package.json

fixes #1580

@awick fixed the text. Also, if you want to figure out why moment-timezone is needed in the viewer package.json, please be my guest. I can't figure it out for the life of me. It's impossibly frustrating 😄

@awick fixed the text. Also, if you want to figure out why moment-timezone is needed in the viewer package.json, please be my guest. I can't figure it out for the life of me. It's impossibly frustrating 😄


homeDir forced for coreos install, provisioned as root...

Vagrant uses 'run_remote' to execute kubectl installation as root user.
The kubectlsetup is run as root on coreos in windows, but there is no root homedir.
The homedir must be overwritten to force coreos into installing in the right directory.

https://github.com/pires/kubernetes-vagrant-coreos-cluster/pull/84/files is a better solution

Thank you nonetheless. Your initial work on the Windows support seem to have sparked interest in some people. Awesome!


logger: add raw FIFO high-rate IMU logging profiles

Useful for vibration analysis.
Usage:

set IMU_GYRO_RATEMAX to 400
use a good SD card (flight review will show the dropouts)
enable either the gyro or accel high-rate FIFO profile in  SDLOG_PROFILE and disable the rest of the entries.
a single FIFO topic requires ~85 KB/s logging bandwidth
if a really good SD card is used, you can:

either enable both accel+gyro
or enable accel/gyro + default logging profile

Flight Review will show the data as in https://github.com/PX4/flight_review/pull/185.
Caveat: the first topic instance is logged, but it might not be the one used for flying.
@francelico fyi
@hamishwillee yes this will need docs :)

I had a hacked version of this that did sensor_accel_fifo xor sensor_gyro_fifo and disabled nearly everything else, but this should be good enough combined with documentation.


an idea

is there i way for force DOWNLOAD an extension using the id or something because that would be the best

you can download the crx file just by going to a website like https://www.crx4chrome.com/ and looking up the extension but chrome will reject the crx because it not allowed by admin

so is there any way to force download an extension? i think some websites have a way to download an extension from their own website and not chrome web store.

nope, managed chromebooks check the crx file, those website download the crx and since the browser is not managed, chrome installs in (only if you have dev mode on)

so is there a way to force turn on dev mode or trick it into thinking dev mode is on a just enough time for it to download it?

nope

bruh sad

wait

i could not do this before

ok nvm

wait

Try Extension Launcher


Can't launch the game

here is the log
latest.log

Hi. It seems What It Should Be's Sugar Cane modification is conflicted to Survivality's Sugar Cane modification.
[18:43:54] [main/WARN]: @ModifyConstant conflict. Skipping wisb.mixins.json:bonemealable.SugarCaneBlockMixin from mod wisb->@ModifyConstant::wisb$randomTick(I)I with priority 1000, already redirected by survivality.mixins.json:block.SugarCaneBlockMixin from mod survivality->@ModifyConstant::survivality_increaseCactusHeight(I)I with priority 1000

This bug will be fix in the 1.0.2 patch. Right now I suggest you to uninstall What It Should Be since it still in Beta state.
Thank you for report!

Okay, thanks


Request Body is not visible for some APIs

<(https://www.nutanix.dev/api_references/self-service/#/i71w8wdle0cdo-update-application)->
The Request Schema is not generated for this update request.
Same is the case for https://www.nutanix.dev/api_references/self-service/#/gp4hc75pamnny-create-application as well.
The yaml file updated for this product is here -
styx-swagger.json
Context

Current Behavior

Expected Behavior

Possible Workaround/Solution

Steps to Reproduce

Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Link to your environment/workspace/project:

@smitabh84 These endpoints are not showing the request body because you have not defined a format for the request body using the consumes property in the provided spec. This property needs to be defined in either to top level Swagger object for the entire service, or at the individual Operation objects. Once you define that, the request bodies will be shown in docs.


Can't disconnect PayPal account for Payouts

In Edit > Sending Money, you have an option to Enable/Disable PayPal but there's no way to disconnect it. It's a problem for support as we sometimes want people to re-connect their PayPal. They may also want to switch to another account.

Please ping if this is unrelated, and I can make it its own issue:
User Story

Our team has brought up is the ability to enable or disable the possibility of using Paypal. As of right now, our fiscal host __ has issues with Paypal integration.  They've told us they can no longer use that as a payment option. However, as the option is still on our page people will often choose to apply using the email option. This means we have to have a conversation with them regarding it and ask them to submit their bank details. If we could remove the Paypal option it would save a lot of time and mean people could be paid quickly.

Please ping if this is unrelated, and I can make it its own issue:
User Story

Our team has brought up is the ability to enable or disable the possibility of using Paypal. As of right now, our fiscal host __ has issues with Paypal integration.  They've told us they can no longer use that as a payment option. However, as the option is still on our page people will often choose to apply using the email option. This means we have to have a conversation with them regarding it and ask them to submit their bank details. If we could remove the Paypal option it would save a lot of time and mean people could be paid quickly.

@kaylarep It is already possible to disable PayPal today. In the linked ticket, the issue seems to be that the fiscal host has issues with PayPal that they're currently working on and haven't disabled while they do. I don't think there's a problem on the platform itself, the fiscal host should just have disabled PayPal if not supported.
This issue is about being able to disconnect your account in order to re-connect it later.

I've tested this and I think we don't show the UI buttons correctly here when we create a new host.
When a new organization is created and activated as a host and when we got to the Sending Money section what we see is,

Note that its as if PayPal Payouts are enabled by default. I think this is incorrect since PayPal Payouts are only enabled when we set the feature flag settings.features.paypalPayouts to true.
I suggest the following solution.

When a new Organization is created and activated as a host we show a info message instead of this button under the PayPal section (under Sending Money). This will be something along Please contact<EMAIL_ADDRESS>if you like to activate PayPal Payouts for sending money.

If the user has connected PayPal Payouts (after we have set the feature flag, and the user has filled up the client secret and id as per, https://docs.opencollective.com/help/fiscal-hosts/payouts/payouts-with-paypal), then we show two buttons; Disable PayPal and Disconnect PayPal.

If the user click on Disable PayPal we just disable PayPal payouts by setting the disablePaypalPayouts to true and a new button Enable PayPal would appear. If the user click on Disconnect PayPal we show the PayPal client ID and secret fields so that the user can specify the information for a new PayPal account.

cc: @Betree

@SudharakaP Yes. When "Disconnecting", we should also cancel all PayPal recurring contributions (that needs to be cristal clear in the UI). Also keep in mind https://github.com/opencollective/opencollective/issues/4210.

@SudharakaP Yes. When "Disconnecting", we should also cancel all PayPal recurring contributions (that needs to be cristal clear in the UI). Also keep in mind #4210.

@Betree : Thanks for pointing that out. Currently the disconnect button we have do not support cancelling all recurring payments. I've opened a PR to fix the issue mentioned here, and we'll iterate on disconnecting the recurring contributions on a separate issue to keep things simple if there's no objections. However I have one concert about this matter; say if the user just wants to update their client-id/secret without cancelling all recurring contributions? Maybe we should give that option to user to choose to cancel their recurring contributions or not (maybe a confirmation modal that has a checkbox asking the user if they want to cancel recurring contributions as well)?

We have discussed that this will be addressed as part of https://github.com/opencollective/opencollective/issues/4210 as this is much more complicated and needs to handle adaptive payment enabling/disabling as well.

related #4627


Launch import flow from Password management screen

Task/Issue URL: https://app.asana.com/0/608920331025315/1208434183978073/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

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

#5098  👈
#5097
#4602
#4601
#5096
develop

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

Join @CDRussell and the rest of your teammates on  Graphite


ci: workflow

Description
Revise and decompose CI workflows to increase rate of development. All workflows are capped at 10 minutes, meaning all PRs should be validated in under 10 minutes.
Legal
This project is available under the Apache 2.0 License.

Goal is to resolve https://github.com/awslabs/iot-application/issues/180.


not working for me

Fuck! The lib has no example! use this lib not working to me!
to monitor the device for notification but never receive any notifications

Please check this project for example usage.

I found that i installed two library which are react-native-ble-manager and react-native-ble-plx
when i intead of the library with the react-native-ble-manager library.
but i have not yet proved whether they have conflict  because i am buzy and used react-native-ble-manager debug success!
Sorry for my poor english!

You should not mix multiple BLE libraries as it may be problematic. How can I help you otherwise?

Please check this project for example usage.

Hi again, finally install in my Device Android, open the App, check the permission and Log seee start Scan.
After a few minutes it does not detect anything, something I'm doing wrong?
Mi BT BLE temperature sensor and gps

@mariomeraz Did you modify the source code of the example app to filter proper devices during a scanning procedure?

Look at: https://github.com/Cierpliwy/SensorTag/blob/master/src/Saga.js#L150


Update README.md

What does this PR do?
This PR enhances the README file for the CopilotKit project by improving the formatting, structure, and overall clarity of the content. The key changes include:

Clearer Navigation: Updated the Table of Contents for easier navigation through the document, ensuring users can quickly find relevant sections.
Expanded Components and Hooks Descriptions: Added more detailed explanations for the components and hooks available in CopilotKit, making it easier for users to understand their functionality.
Updated Contributing Guidelines: Refined the contributing section to encourage community involvement, making it more welcoming and accessible for potential contributors.

These enhancements aim to create a more user-friendly experience, helping users quickly understand the framework and how to get started.
Related PRs and Issues

N/A

Checklist

[x] I have read the Contribution Guide
[x] If the PR changes or adds functionality, I have updated the relevant documentation.

@mme @ataibarkai @arielweinberger @ranst91 please review my PR.

@mme @ataibarkai @arielweinberger @ranst91


Offline Arcade v0.18.14: Unable to download Darker Duck for device

Describe the bug
While offline, attempting to download Darker Duck to a meowbit fails with a message that is misleading:

The problem is not in user code, but has to do with the fact that the compiler can't download an extension's hex file.
built/output.txt contains a more informative message. We could show this in the error panel:
error: pxt_modules/base/pxt-core.d.ts(1,1): error TS9043: The hex file is not available, please connect to internet and try again.

I'll look at fixing the message, but more importantly this should just work, right? I believe the only time we should need to fetch the hex file should be when we load an extension w/ c++ files, but this one just loads animation; this repros even if you create a new project just importing corgio or any other extension that is js only


🌱 fix TestClusterExtensionInstallReResolvesWhenNewCataloge2e test

Description

Created a new Catalog v2 with Prometheus bundle 2.0.0
Changes made to build-push-e2e-catalog.sh to allow building and pushing new catalog image
Changes made to TestClusterExtensionInstallReResolvesWhenNewCatalog e2e test  -

Install ClusterExtension with existing Catalog(v1) which has Prometheus v1.2.0
Once Prometheus v1.2.0 is installed, patch the ExtensionCatalog with the newly created catalog v2
Wait and confirm that ClusterExtension picks the prometheus v2.2.0 from test-catalog:v2 and resolves to a successful install

fixes #945
Reviewer Checklist

[x] API Go Documentation
[x] Tests: Unit Tests (and E2E Tests, if appropriate)
[x] Comprehensive Commit Messages
[x] Links to related GitHub Issue(s)

/lgtm


revert(client): roll back react 17

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the main branch of freeCodeCamp.
[X] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Reverts https://github.com/freeCodeCamp/freeCodeCamp/commit/b6da89c5b6431f84a0117d8f6cd747503873ca7d as a temporary fix for #42035.

We might need to revert https://www.npmjs.com/package/@wojtekmaj/enzyme-adapter-react-17 too.


Insert Image to navbar brand

Hi, It's a awesome plugin for jade.
My question is, how can I use a image on the navbar-brand?

@kenanchristian , you can now use the new mixin for navbar called
navbar-logo(name, id, style, href, image)
where name = alt text for the logo
image = src url for the brand image
kindly refer to bootstrap docs  http://getbootstrap.com/components/#navbar-brand-image

@rajasegar Thanks for the fast response, but i think something broken on your code..
This is my code

This is what i get

I also create a pull request(#19), but with that changes, it doesn't seems to be

already included the fix inside pull request :)
you forgot to add ul.nav.navbar-nav


image test: preserve default tensor type.

Requiring image previously switched the default tensor type to DoubleTensor.

good catch! thanks.


multicore-linux-arm7 port

Original issue: https://charm.cs.illinois.edu/redmine/issues/411

There is a net-linux-arm7-smp port already, so multicore-linux-arm7 should be a simple extension.
This would be useful for some ARM/CUDA performance and power testing we're doing this week.
Can test on cupertino.ks.uiuc.edu.

Original date: 2014-02-05 17:15:57

It looks like net-linux-arm7-smp does not launch a comm thread when in standalone mode.  Is this true?  If so priority can be reduced.

Original date: 2014-02-11 20:19:25

Committed as http://charm.cs.illinois.edu/gerrit/70

Original date: 2014-02-11 20:33:25

Jim, please confirm that this works and close the issue.

Original date: 2014-02-13 04:50:19

Fails in megatest 10.  (net-linux-arm7-smp passes.)
tegra-ubuntu:~/feb2014/charm/multicore-arm7/tests/charm++/megatest> ./pgm +p4
Charm++: standalone mode (not using charmrun)
Converse/Charm++ Commit ID: v6.6.0-rc1-65-g32f1f5e
Warning> Randomization of stack pointer is turned on in kernel, thread migration may not work! Run 'echo 0 > /proc/sys/kernel/randomize_va_space' as root to disable it, or try run with '+isomalloc_sync'.
Charm++> scheduler running in netpoll mode.
CharmLB> Load balancer assumes all CPUs are same.
Charm++> Running on 1 unique compute nodes.
Charm++> cpu topology info is gathered in 0.060 seconds.
Megatest is running on 1 nodes 4 processors.
test 0: initiated [groupring (milind)]
test 0: completed (0.10 sec)
test 1: initiated [nodering (milind)]
test 1: completed (0.00 sec)
test 2: initiated [varsizetest (mjlang)]
test 2: completed (0.00 sec)
test 3: initiated [varsizetest2 (phil)]
test 3: completed (0.00 sec)
test 4: initiated [varraystest (milind)]
test 4: completed (0.00 sec)
test 5: initiated [groupcast (mjlang)]
test 5: completed (0.01 sec)
test 6: initiated [groupmulti (gengbin)]
test 6: completed (0.00 sec)
test 7: initiated [groupsectiontest (ebohm)]
test 7: completed (0.00 sec)
test 8: initiated [multisectiontest (ebohm)]
test 8: completed (0.03 sec)
test 9: initiated [nodecast (milind)]
test 9: completed (0.00 sec)
test 10: initiated [synctest (mjlang)]
*** longjmp causes uninitialized stack frame ***: ./pgm terminated
Abort

Original date: 2014-02-13 04:53:59

Eric, Jim, please both post the build commands used leading up to your respective make test results. This is a pretty stark discrepancy.

Original date: 2014-02-13 04:55:51

11  20:50   ./build charm++ multicore-arm7 --no-build-shared --with-production
21  22:18   ./build charm++ net-linux-arm7-smp --no-build-shared --with-production

Original date: 2014-02-17 05:36:11

I'm inclined to say that this shouldn't block the 6.6.0 release. It's new, non-critical functionality appearing late in the cycle. If we get it stabilized before 6.6.0 is finalized, great. If not, it can go in 6.6.1.

Original date: 2014-02-17 16:51:28

Changing CMK_THREADS_USE_JCONTEXT to 0 fixes this.

Original date: 2014-02-18 19:20:02

Bump. Can someone please integrate this?

Original date: 2014-02-18 19:43:20

That patch solves the problem in megatest, but still crashes in megampi.  Wierdly, this problem doesn't arise in net-linux-arm7-smp.  That means that thread migration isn't working correctly in multicore-arm7.  Given that NAMD doesn't need thread migration, we can probably go ahead with this.

Original date: 2014-02-18 20:04:54

How do you migrate threads in multicore when there's only one memory space?

Original date: 2014-02-18 20:06:05

Nevermind. I guess you migrate between stacks on different pthreads.

Original date: 2014-02-19 21:48:20

I recommend testing threading using OS's "context".

Original date: 2014-06-23 19:31:18

Accidentally mass-closed. There are known stability issues on all the ARM ports, so this shouldn't be closed.


changing root directory for forum

Hi,
I am a bit of a Laravel noob, and I'm wondering where exactly is the routing occurring when i head to /forum, as I would like  introduce a parameter into this path.
I am using Laravel 4.2
Thanks :)

found it literally seconds after making this issue -.-

Hehe, no worries. Glad you figured it out.


bug: level generation sometimes places multiple characters in same location

Need to verify if this is still case.


Cannot remove 'content-disposition' header from proxied response.

yarn why http-proxy-middleware OR npm ls http-proxy-middleware output (mask private folder names with *****)
$ npm ls http-proxy-middleware
<EMAIL_ADDRESS>C:\Users\*\code\*
`--<EMAIL_ADDRESS>
Please verify that you've followed these steps
[ x] - I've updated to latest http-proxy-middleware.
Describe the bug
I am trying to use http-proxy-middleware to request PDF files from a server, because the server's response contains the
content-disposition: attachment; filename="somefile.pdf"

header. This forces the requesting browser to download the file instead of opening it in its PDF reader (see https://stackoverflow.com/questions/9195304/how-to-use-content-disposition-for-force-a-file-to-download-to-the-hard-drive)
I tried removing the header with
const express = require("express");
const { createProxyMiddleware } = require("http-proxy-middleware");

const app = express();

app.use(
  createProxyMiddleware({
    target: "https://httpbin.org",
    changeOrigin: true,
    onProxyRes: (proxyRes, req, res) => {
        delete proxyRes.headers['content-disposition'];
    },
  })
);

app.listen(8080, () => {
  console.log("🚀  server started");
  console.log(`↗  example: "curl https://44oc1.sse.codesandbox.io/json"`);
});

as well as:
const express = require("express");
const { createProxyMiddleware } = require("http-proxy-middleware");

const app = express();

app.use(
  createProxyMiddleware({
    target: "https://httpbin.org",
    changeOrigin: true,
    onProxyRes: responseInterceptor(
      async (responseBuffer, proxyRes, req, res) => {
        delete proxyRes.headers['content-disposition'];
        return responseBuffer;
      }
    ),
  })
);

app.listen(8080, () => {
  console.log("🚀  server started");
  console.log(`↗  example: "curl https://44oc1.sse.codesandbox.io/json"`);
});

Unfortunately, I couldn't make a fully working example because I don't know of any public servers that serve PDF with that 'content-disposition' header.
Expected behavior
I expected that the 'content-disposition' header would be removed from the proxy response allowing the PDF file to be displayed in the browser's PDF reader. What I see in the browser's dev tools though is that the header is still part of the response.
http-proxy-middleware configuration
see above
Server (please complete the following information):

OS: Windows
NodeJS version: 14.16.1

Additional context
Running console.log before and after delete proxyRes.headers['content-disposition'] prints the following:
{
  'content-disposition': 'attachment; filename="somefile.pdf"',
  etag: '"1620984981090-57231"',
  'accept-ranges': 'bytes',
  'content-range': 'bytes 0-57230/57231',
  'content-type': 'application/pdf',
  'content-length': '57231',
  date: 'Fri, 14 May 2021 09:36:21 GMT',
  connection: 'close'
}
{
  etag: '"1620984981090-57231"',
  'accept-ranges': 'bytes',
  'content-range': 'bytes 0-57230/57231',
  'content-type': 'application/pdf',
  'content-length': '57231',
  date: 'Fri, 14 May 2021 09:36:21 GMT',
  connection: 'close'
}

So it looks like the header is gone but in the network tab of the browser's dev tools, I still get to see this:

Did you try disabling browser cache?

I'm able to delete content-disposition header  with:
app.use(
  createProxyMiddleware({
    target: "https://demo.borland.com",
    changeOrigin: true,
    onProxyRes(proxyRes) {
      delete proxyRes.headers["content-disposition"];
    }
  })
);

https://demo.borland.com/testsite/download_testpage.php
curl -X HEAD -I https://demo.borland.com/testsite/downloads/downloadfile.php\?file\=Hello.txt\&cd\=attachment+filename


[FormRecognizer] Flattened DocumentModelDetails

Changes

Removed the inheritance between DocumentModelDetails and DocumentModelSummary. Based on the swagger specification, CodeGen generates Details as a subclass of Summary. We want to avoid the inheritance in the SDK. If the service ever decides to evolve these differently in the future, we could end up breaking users. An example would be adding a new property to Summary but not to Details.

Strategy for flattening DocumentModelDetails
In the swagger, DocumentModelDetails and DocumentModelSummary are called DocumentModel and ModelSummary, respectively. The only thing the SDK did before this PR was renaming these models in code:
[CodeGenModel("ModelSummary")]
public class DocumentModelSummary{}

[CodeGenModel("DocumentModel")]
public class DocumentModelDetails : DocumentModelSummary {}

Since we cannot prevent CodeGen from adding the inheritance, we need to create a whole new DocumentModelDetails class. The generated one will be hidden from the public API:
[CodeGenModel("ModelSummary")]
public class DocumentModelSummary {}

// Keep it internal.
[CodeGenModel("DocumentModel")]
internal class DocumentModel : DocumentModelSummary {}

// NOT generated. Written manually without inheritance.
public class DocumentModelDetails {}

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.FormRecognizer


[place] climate charts should use annual means

(or some other means of reducing the number of data points and payload size)
pages are much slower to load now as a result of the larger response

have a look at https://github.com/leeoniya/uPlot


Revert "Add .git directory to .dockerignore file (#1974)"

This reverts commit b8067e79a59edeb59c32d43c4995926d047c226c.
Also manually add whitespace to the snapcraft.yaml folder to trigger the snap jobs in CI to confirm this unbreaks the snap builds.
We will eventually take up issue #1973 after Fuji is out, and we should also discuss in DevOps how to better address this sort of situation where a change outside of the snap/ dir affects the snap build.

The amd64 build seemed to pass:
12:53:44 Priming version
12:53:46 The 'passthrough' property is being used to propagate experimental properties to snap.yaml that have not been validated.
12:53:47 Snapping 'edgexfoundry' ...
12:56:12
12:56:12 Snapped edgexfoundry_1.1.0-20191022+cd30285c_amd64.snap

Will still wait for arm64 to finish before merging however...