Editor scrolls whyle typing - showAnnotationCodeLens = false solves it.

Hi there,
While searching for a solution I found this issue:
https://github.com/Microsoft/vscode/issues/25402
There it is mentioned, that the scrolling while typing bug happens only with Code-Lense on. Therefore I disabled all Code-Lense features from every extension I had separately and the clearcase extension was the evil guy.
It is reproducible on several PCs with C-Code. I turned Code-Lense on for everything except clearcase then it works as intended. When turning on "vscode-clearcase.showAnnotationCodeLens" it is scrolling down while typing text.

The upstream bug is closed, should I close this one too?


PR stuff

See if we can solve this:

Only our team can approve PR. Other contributors are not allowed to approve any PR.

Other contributors can not merge even if PR is approved.

Please more descriptive name :(

Please more descriptive name :(

WIP

Please add labels and milestones

After some research found this: https://github.com/orgs/community/discussions/23765
We will add a CODEOWNERS file that :

automates the process of asking for review
lets us set Require review from Code Owners to true in the settings so as to solve the first sub-task of this issue(task)

Looks like it's working
test branch here: https://github.com/InnoQueue/Backend/pull/125


Safely catch translation key when it's wrong/missing

We've had several bad scenarios where the app crashes because the wrong translation key was used. We expect this to start increasing as we add "workspace violations" because these violations come directly from the API (and aren't translated).
Some ideas discussing with @mountiny and @cead22 on how to potentially handle this:

Throw some error locally, and if in staging or production, add a fallback option for these keys which are expected to come from the backend
Show an empty string instead of crashing, and maybe overkill but we could show MISSING TRANSLATION to @expensify.com users

Or something else. While this is out of scope for the internal project, we wanted to get an agency working on this one.

@JmillsExpensify - In this case would I label this internal or should I leave it be for now? I don't want it held up because I'm not sure what to do with it. Thanks for the direction.

Asking agency but if you can create a good proposal, we can go with contributor too

Seems quite good, @robertKozik can you please review the proposal thoroughly?

I like your proposals as well @dukenv0307. It ticks all the boxes provided in the issue description. Moreover I would suggest that MISSING TRANSLATION string should be also visible when running Expensify app locally - It should help both Contributor and Contributor+ to track them while checking the PRs.
Also I'm not the huge fan of returning empty string in place of translation key. Providing some context (even as translation key) can be helpful in certain scenarios, as it informs the user that there should be additional information available.
@mountiny All in all I think we can go with this proposal

I'm seeing this error message in a weird spot. I'm guessing that's a separate issue, but sharing just in case https://expensify.slack.com/archives/C049HHMV9SM/p1696940644742429

@mountiny @strepanier03 Is BugZero Checklist applicable here? This issue got more like new feature vibe

Not applicable
This is ready for a payout once the date is met $500 to @dukenv0307

Okay, this is ready to be paid tomorrow and be closed. Will take care of then.

All paid out and closing. Thanks everyone!


[FLINK-28848][table-planner] Introduces LOOKUP join hint to support delayed retry for lookup join (table alias unsupported in hint)

What is the purpose of the change
Introduces LOOKUP join hint to support delayed retry for lookup join (table alias unsupported in hint)
This is the main part of FLINK-28779 to implement FLIP-234: Support Retryable Lookup Join To Solve Delayed Updates Issue In External Systems.
The join hint based on [FLINK-28682][table-planner] support join hint in batch rules #20359, and adds a new hint 'LOOKUP' described in FLIP-234.
Brief change log

Add new hint LOOKUP
Add related option class and validation
Add related tests for new classes
Adapt to async operator with retry and also adds a new RetryableLookupFunctionDelegator to wrap user's sync lookup func to support retry

Verifying this change

LookupJoinHintSpecSerdeTest
LookupJoinHintSpecTest
LookupJoinJsonPlanTest
LookupJoinTest
RetryableLookupFunctionDelegatorTest
more ITCases will be updated in Add it cases with lookup hint using new lookup function api for lookup join

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no )
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

rebased master and updated the pr

@flinkbot run azure

@flinkbot run azure

there're several merge conflicts for the latest master, so need to verify the merged pr completely, the local verify are running

local verify ok for table modules(the ci pipeline was too slow)


Add GPU Support for Embedding Pipeline

Hi,
I would like to request the addition of GPU support for the embedding pipeline. Utilizing GPU for the embedding process can significantly speed up the computations compared to using CPU, thereby enhancing the performance and efficiency of the pipeline.
Thank you for considering this feature request. I believe it will greatly enhance the performance and flexibility of the project.

Hey.. the GPU support is there now but I have been able to test it only with Rust. Need further testing with python.

This is done now. You can use embed-anything-gpu now.


feat: add fees to admin UI

Changes proposed in this pull request

added a query to fetch all historic fees associated with a particular asset
added current fee to asset overview on admin UI
added the ability to set a new fee on asset overview
displays a table of all historic fees for a particular asset (this view can be filtered by fee type)

Context

fixes #1834
Checklist

[x] Related issues linked using fixes #number
[x] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass
[ ] Postman collection updated

@mkurapov @BlairCurrey how should we deal with receiving fees?

I can easily remove all the receiving fees code for now. And we can go with this

I can easily remove all the receiving fees code for now. And we can go with this

I think that looks good.

@mkurapov @BlairCurrey how should we deal with receiving fees?

Last I knew there was a chance that Mojaloop payments might need them. Any more insight on that? If they wont need them then I'd be in favor of removing the type and implicitly treating all fees as sending.

Last I knew there was a chance that Mojaloop payments might need them. Any more insight on that? If they wont need them then I'd be in favor of removing the type and implicitly treating all fees as sending. The type was added with the expectation that receiving fees would be implemented but they were scrapped.

I think this is still the case, but not for the PoC we are working on right now with PCH but for the general MJL peer-to-peer payment method.


Broken link to System.Diagnostics.Activity User Guide

Activity User Guide was moved to runtime repo:
https://github.com/dotnet/runtime/blob/master/src/libraries/System.Diagnostics.DiagnosticSource/src/ActivityUserGuide.md

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

ID: 62521082-c9fb-646f-6db0-2cdabe486dab
Version Independent ID: ebf938ec-1d97-1cfd-ad28-5e616990d658
Content: Track custom operations with Azure Application Insights .NET SDK - Azure Monitor
Content Source: articles/azure-monitor/app/custom-operations-tracking.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@cedricfronteau , Thanks for brining this to our attention. We will investigate it further and update you shortly.

I found 2 other broken links when I checked the doc, so thank you so much for bringing this to our attention. The fix is merged internally and will go-live in the public docs between 3-4 PM UTC-7 later today.

#please-close

@mrbullwinkle - Thank you for updating the doc.
@cedricfronteau -
Thanks again for bringing this to our attention. We have updated the Doc and We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add slackUsernameFormat config option

Close #56

Coverage increased (+0.003%) to 99.457% when pulling 4fb44ed4a4846819d41f281791fca82ae5485502 on laughinghan:slackUsernameFormat into d35d7b9c0bb68b90ffe77ec33104300b0f88f111 on ekmartin:master.

Coverage increased (+0.003%) to 99.457% when pulling 4fb44ed4a4846819d41f281791fca82ae5485502 on laughinghan:slackUsernameFormat into d35d7b9c0bb68b90ffe77ec33104300b0f88f111 on ekmartin:master.

@ekmartin: lol did you add Coveralls twice or something

Brilliant! I agree with what you said in https://github.com/ekmartin/slack-irc/issues/56#issuecomment-258967286 - let's go with $username (IRC) as the default. Whether it's a breaking change or not is up for discussion, but I think it's fine to just do it in a minor version bump, since as you said - it's a cosmetic change.
Should this maybe be nested under an object, to make it cleaner to add support for IRC username formatting as well?
"usernameFormat": {
   "slack": "$username (IRC)",
   "irc": "<$username>"
}

Or do you think it's clearer with just slackUsernameFormat and ircUsernameFormat?

Great! Will do.
I don't think it should be nested, but I also see no use for ircUsernameFormat since messages in IRC from the bot (piped from Slack) are already distinguished by coming from the bot, much moreso than bot messages in Slack.

I think one use case would be if people for some reason would want to remove the username when messages are posted to IRC. Might be good to have both just for unity, but we can merge this and look at it later.

@ekmartin: eh yeah let's just deal with that later. Updated default Slack username format.

Coverage increased (+0.003%) to 99.457% when pulling<PHONE_NUMBER>83d9d09083e79c86392d9ff1c972da on laughinghan:slackUsernameFormat into d35d7b9c0bb68b90ffe77ec33104300b0f88f111 on ekmartin:master.

Great, thanks! I'll create a release later.

Released in 3.9.0 - thanks again!


Change the default max_wait_time to 1 second

In https://github.com/zendesk/ruby-kafka/pull/434, the default max_wait_time in ruby-kafka was changed to 1 second.
This make the corresponding change for racecar, since the default here overrides the ruby-kafka default.

Thanks!


added cal-day-past class for days in the past

Adds class 'cal-day-past' to the day cell on month view and the day column on week view. This allows specific styling for days in the past. Also, the isPast property could be used for specific behavior on click events (like disabling them for days in the past).

I've also added a corresponding future class for the sake of completeness :)

Awesome, thanks!


[BUG] v1.1.2-alpha Fails to Start

OS: What operating system are you running Manga Tagger on?
Windows 10
Manga Tagger Version: What version of Manga Tagger are you running?
v1.1.2-alpha
Description of the issue: Give a a clear and concise description of what the issue is.
Starting new version once selecting FMD folder proceeds to crash and give error.
Manga Series: What manga series (singular or plural) were being tagged when the issue was encountered?
Screenshots (If applicable): Add screenshots to help explain your problem.

Log File: Please make sure JSON logging is enabled and upload the JSON log file.

Ah, I overlooked a setting in the settings.json. This is a quick fix; will handle it later today.
On January 15, 2021 at 7:48:33 AM, Ablex222 (notifications@github.com(mailto:notifications@github.com)) wrote:

Assigned #22(https://github.com/Inpacchi/Manga-Tagger/issues/22) to @Inpacchi(https://github.com/Inpacchi).
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub(https://github.com/Inpacchi/Manga-Tagger/issues/22#event-4211012083), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ACUOWAT6UVKRQU6FKVU4YZTS2A2SDANCNFSM4WEAHYJQ).

Ah, I overlooked a setting in the settings.json. This is a quick fix; will handle it later today.
On January 15, 2021 at 7:48:33 AM, Ablex222 (notifications@github.com(mailto:notifications@github.com)) wrote:

Assigned #22(https://github.com/Inpacchi/Manga-Tagger/issues/22) to @Inpacchi(https://github.com/Inpacchi).
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub(https://github.com/Inpacchi/Manga-Tagger/issues/22#event-4211012083), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ACUOWAT6UVKRQU6FKVU4YZTS2A2SDANCNFSM4WEAHYJQ).

Was wondering if this got resolved?

Was wondering if this got resolved?

Meant to respond to this yesterday but had to run out the door. I did start working on it, and was in the middle of QAing before I had to stop for the night, and then the weekend happened and you know how that goes.
I picked up work on this last night (I actually was streaming my bug fixing) and made some good progress. It was originally going to be a quick fix however, when I QA’d (because I forgot to QA the start up process; I only QA’d the other changes I made) I noticed that FMD wasn’t opening or closing. I’m currently in the middle of debugging that and making sure FMD closes as it should before Manga Tagger continues to do anything; otherwise the application won’t work correctly.
On January 18, 2021 at 8:11:21 AM, Ablex222 (notifications@github.com(mailto:notifications@github.com)) wrote:

Was wondering if this got resolved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub(https://github.com/Inpacchi/Manga-Tagger/issues/22#issuecomment-762241375), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ACUOWAX24MSMHQFRU6XYYH3S2QXPTANCNFSM4WEAHYJQ).

Meant to respond to this yesterday but had to run out the door. I did start working on it, and was in the middle of QAing before I had to stop for the night, and then the weekend happened and you know how that goes.
I picked up work on this last night (I actually was streaming my bug fixing) and made some good progress. It was originally going to be a quick fix however, when I QA’d (because I forgot to QA the start up process; I only QA’d the other changes I made) I noticed that FMD wasn’t opening or closing. I’m currently in the middle of debugging that and making sure FMD closes as it should before Manga Tagger continues to do anything; otherwise the application won’t work correctly.
On January 18, 2021 at 8:11:21 AM, Ablex222 (notifications@github.com(mailto:notifications@github.com)) wrote:

Was wondering if this got resolved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub(https://github.com/Inpacchi/Manga-Tagger/issues/22#issuecomment-762241375), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ACUOWAX24MSMHQFRU6XYYH3S2QXPTANCNFSM4WEAHYJQ).

I am not 100% about the implementation, but at least with a windows client you could just use the "taskkill" cmds to force close the software before the rest of the program runs. Not pretty, but should be functional.

I am not 100% about the implementation, but at least with a windows client you could just use the "taskkill" cmds to force close the software before the rest of the program runs. Not pretty, but should be functional.

Resolved with release v1.1.4-alpha

Resolved with release v1.1.4-alpha


GraphQL schema conversion starts regardless of its configuration and throw errors due to its limitations

While trying to update jsonapi-server to 2.3.0 I've encountered some issues:
For the following resource schema
{
        resource: ResourcesNames.ITEM,
        handlers: handler,
        attributes: {
            responseType: jsonApi.Joi.object().keys({
                id: jsonApi.Joi.number().integer().required(),
                name: jsonApi.Joi.string()
            }).required(),
            instructions: jsonApi.Joi.array().items(jsonApi.Joi.object().keys({
                id: jsonApi.Joi.number().integer(),
                type: jsonApi.Joi.object().keys({
                    id: jsonApi.Joi.number().integer().required(),
                    name: jsonApi.Joi.string()
                }).required(),
                data: jsonApi.Joi.string().optional()
            })).optional()
        }
    }

I get the following error
Error: Joi arrays must contain a single type
    at Object.joiConverter.simpleAttribute.joiScheme [as simpleAttribute] (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/graphQl/joiConverter.js:30:13)
    at Object.joiConverter.swap (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/graphQl/joiConverter.js:46:25)
    at Object.keys.forEach.attribute (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/graphQl/readTypes.js:41:30)
    at Array.forEach (native)
    at fields (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/graphQl/readTypes.js:36:46)
    at resolveThunk (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/definition.js:115:40)
    at defineFieldMap (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/definition.js:265:18)
    at GraphQLObjectType.getFields (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/definition.js:235:44)
    at /opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:207:27
    at typeMapReducer (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:219:7)
    at typeMapReducer (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:187:12)
    at /opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:217:22
    at Array.forEach (native)
    at /opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:208:29
    at typeMapReducer (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:219:7)
    at Array.reduce (native)
    at new GraphQLSchema (/opt/checklists_service/services/web-api-gateway/node_modules/graphql/type/schema.js:95:34)
    at Object.jsonApiGraphQL.generate.allResourceConfig [as generate] (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/graphQl/index.js:29:10)
    at Object.jsonApiGraphQL.with.app [as with] (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/graphQl/index.js:17:28)
    at Object.router.applyMiddleware (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/router.js:76:15)
    at Object.jsonApi.start (/opt/checklists_service/services/web-api-gateway/node_modules/jsonapi-server/lib/jsonApi.js:116:10)
    at Object.<anonymous> (/opt/checklists_service/services/index.js:41:4)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.runMain (module.js:590:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

According to joiConverter.js , it has limitation for non primitive array items - look at instructions above.
I've tried to remove the instructions, but then i've got this error:
Error: Unable to parse Joi type, got {"isJoi":true,"_type":"any","_settings":null,"_valids":{"_set":[]},"_invalids":{"_set":[]},"_tests":[],"_refs":[],"_flags":{"presence":"required"},"_description":null,"_unit":null,"_notes":[],"_tags":[],"_examples":[],"_meta":[],"_inner":{}}
    at Object.joiConverter.simpleAttribute.joiScheme [as simpleAttribute] (/Users/yossialush/WebstormProjects/hello-world/node_modules/jsonapi-server/lib/graphQl/joiConverter.js:38:11)
    at Object.joiConverter.swap (/Users/yossialush/WebstormProjects/hello-world/node_modules/jsonapi-server/lib/graphQl/joiConverter.js:46:25)
    at Object.keys.forEach.attribute (/Users/yossialush/WebstormProjects/hello-world/node_modules/jsonapi-server/lib/graphQl/readTypes.js:41:30)
    at Array.forEach (native)
    at fields (/Users/yossialush/WebstormProjects/hello-world/node_modules/jsonapi-server/lib/graphQl/readTypes.js:36:46)
    at resolveThunk (/Users/yossialush/WebstormProjects/hello-world/node_modules/graphql/type/definition.js:115:40)
    at defineFieldMap (/Users/yossialush/WebstormProjects/hello-world/node_modules/graphql/type/definition.js:265:18)
    at GraphQLObjectType.getFields (/Users/yossialush/WebstormProjects/hello-world/node_modules/graphql/type/definition.js:235:44)
    at /Users/yossialush/WebstormProjects/hello-world/node_modules/graphql/type/schema.js:207:27
    at typeMapReducer (/Users/yossialush/WebstormProjects/hello-world/node_modules/graphql/type/schema.js:219:7)

Now responseType is making troubles, because it's an joi.object
Most important is that those errors are being thrown during schema conversion for GraphQL feature, which in my case wasn't even enabled
jsonApi.setConfig({
    graphiql: false
});

I'm not even interested in supporting GraphQL in this project, so it's weird that I'm still being affected by it.

I see that https://github.com/holidayextras/jsonapi-server/pull/233 has solved it


Updated pods and started conversion to swift 4

Still has dependency error, but will fix it

thanks man @RahulBirCodes. i have merged it


sync-android is complaining that the database is locked

All queries to the database are sequentially done. I used a Executors.newSingleThreadExecutor() to ensure only one task is executed at any time however after successfully executing one task and then moving on to the next I received the following message:
E/SQLiteLog: (5) database is locked  and
E/SQLiteDatabase: Failed to open database /data/data/app/app_datastores/database/extensions/com.cloudant.sync.query/indexes.sqlite
Below is an example of one of the queries:
`    Datastore ds = DataManager.getInstance().getPersistenceService().getDs();
ConfigService configService = DataManager.getInstance().getConfigService();
IndexManager im = new IndexManager(ds);
DocumentRevision documentRevision = new DocumentRevision();
Map<String, Object> query = new HashMap<>();
query.put("patientId", configService.getProfileId());
query.put("type", "testResults");
query.put("typeOfTest", "blood_pressure");

List<Map<String, String>> sortDocument = new ArrayList<>();
Map<String, String> sortByPatient = new HashMap<>();
Map<String, String> sortByType = new HashMap<>();
Map<String, String> sortByTestType = new HashMap<>();
Map<String, String> sortByTime = new HashMap<>();
sortByPatient.put("patientId", "desc");
sortByType.put("type", "desc");
sortByTestType.put("typeOfTest", "desc");
sortByTime.put("timeRecorded", "desc");
sortDocument.add(sortByPatient);
sortDocument.add(sortByType);
sortDocument.add(sortByTestType);
sortDocument.add(sortByTime);

QueryResult bloodPressureResult = im.find(query, 0, 1, null, sortDocument);

if (result != null) {
    for (DocumentRevision rev : bloodPressureResult) {
        documentRevision = rev;
    }
}

im.close();

return documentRevision;`

Can you give me a clue as to why after executing this query (Successfully) and then trying execute something similar that the database would complain that it is locked?

 The IndexManager class actually uses a queue internally for all database access so these should be serialised as long as you always use the same IndexManager.
Can you tell us which version of the library you are using?
I would advise you to try using the same IndexManager instance throughout the lifetime of your application rather than creating a new one each time. This may help with your issue.

I was using version 1.0.0 then upgraded to 1.1.0 but the issue persists. I try out your suggestion.

Your suggestion worked. Thanks!

Great glad it works for you :)


Not getting errors to appear with simple_form / foundation

Hello,
We are just starting a new project with Zurb/Foundation and using simple_form as well.  Our first form is working, but we cannot get errors to appear.  Here's the code:
<%= simple_form_for :asset, url: company_assets_path do |f| %>
  <%= f.input :name %>
  <%= f.input :value %>
  <%= f.button :submit %>
<% end %>

When I submit the form and it is re-rendered, no error classes or wrapper elements appear.  But if I print out the validation errors, I get ["Name can't be blank", "Value can't be blank"].  Can anyone tell me what I'm doing wrong?  Thanks!

Ugh, it was even in the documentation that way!!!!  Thanks for the help, works perfectly now!


suport Another Quick Switcher

In fact, I use this plugin ： https://github.com/tadashi-aikawa/obsidian-another-quick-switcher

Only the dev of another quick switcher can implement its quick preview support. Please contact him instead


docs: make downloads the main thing

Add a download section at the top, and add info on package mangers to the install section.

Cool! Thanks!


Releases page text crop issue

The SHA256 hash text is not properly cropped when resizing.  The problem was confirmed in Chrome and Brave.

On the same page, a similar issue occurs with the Documentation and Source Code links. The link texts can exceed the divider line.


As for ListIterator's TypeErrorList, the culprit must be the entire list

#192

Codecov Report

Merging #193 (14b5255) into main (64903d4) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #193   +/-   ##
=======================================
  Coverage   96.22%   96.22%
=======================================
  Files          20       20
  Lines        6250     6250
=======================================
  Hits         6014     6014
  Misses        196      196
  Partials       40       40

Impacted Files
Coverage Δ

engine/builtin.go
94.41% <100.00%> (-0.01%)
:arrow_down:

engine/iterator.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 64903d4...14b5255. Read the comment docs.


Pagefind not seeing data-pagefind-body attribute in Astro build published on Netlify

I have a site built with Astro, deployed with Netlify, on which I'm utilizing the pagefind library.   I have set the data-pagefind-body attribute on the  article element of my blog, like so:
<article data-pagefind-body>
       ...stuff
</article>

However, when the pagefind binary runs on Netlify, I get the following output:
[Parsing files]
**Did not find a data-pagefind-body element on the site.**
9:53:25 AM: ↳ Indexing all <body> elements on the site.
9:53:25 AM: 3 pages found without an <html> element.
9:53:25 AM: Pages without an outer <html> element will not be processed by default.
9:53:25 AM: If adding this element is not possible, use the root selector config to target a different root element.
9:53:25 AM: [Reading languages]
9:53:25 AM: Discovered 1 language: en
9:53:25 AM: [Building search indexes]
9:53:25 AM: Total:
9:53:25 AM:   Indexed 1 language
9:53:25 AM:   Indexed 4 pages
9:53:25 AM:   Indexed 33 words
9:53:25 AM: Starting post processing
9:53:25 AM:   Indexed 0 filters
9:53:25 AM:   Indexed 0 sorts
9:53:25 AM: Finished in 0.7 seconds
9:53:26 AM: Post processing - HTML
9:53:25 AM:
9:53:25 AM: (build.command completed in 6.2s)

I have reproduced this issue in a test repository here:
Pagefind Troubleshooting Repository
Also, you can check out the site deployed on Netlify here and verify that the pagefind attribute is indeed in the article tag. Just click the search button in the navbar, test it out, and you can see that pagefind is indexing the entire site.
https://pagefind-troubleshoot.netlify.app/
Perhaps I'm missing something simple here. Any help would be greatly appreciated.

👋 Thanks a tonne for reproducing this @justsilencia ❤
I've tracked it down to a quirk of this site — if you view the source on one of the blog posts and scroll to the bottom you'll see a <script client:load> element sitting all the way outside the <html></html> element. A classic case of browsers being very permissive and allowing this, while Pagefind hit a weird corner case when it hit that element.
I'm not sure if that script living there is an Astro thing, or something specific to this site. In any case, I've released Pagefind v0.10.4 with a fix, these elements floating outside the html will no longer affect the indexing 🙂 Let me know if that resolves it!

@bglw Well, when I inspect one of the articles in devtools I'm not seeing the <script> tag outside of the <html> tag. Rather, it's at the bottom of the <body> as expected. This could be a false read though, because I consolidated the scripts into one .astro search component. So, I kinda muddied the waters there.
My guess is I did something funky with the script placement without realizing it. Nonetheless, it's working like a charm! Thanks for the quick fix, this library is super sweet for SSG blogs.

Awesome, glad to hear 🙂
I think devtools normalizes HTML quirks — right click > view source will show you the unaltered HTML page. In any case, glad it's fixed!


feat(dont-merge): get a finalized list of all the eligible wallets for the snæfellsjökull POAP drop (before January 5th 23:59 UTC)

This PR is only for review and plz don't merge it. The script is used to get a finalized list of all the eligible wallets for the snæfellsjökull POAP drop (before January 5th 23:59 UTC), any L2 wallet with a bridging transaction + one other type of transaction (transfer, dapp tx) will be counted. If the script is correct, the number of output wallets is 56204.

@davidtaikocha Please create a new repo "operations" to have all these scripts.

@davidtaikocha Please create a new repo "operations" to have all these scripts.

move to https://github.com/taikoxyz/operations/pull/1


add (users): nikarashihatsu.github.io

This PR add my personal site to this https://blowfish.page/users/ page.

Sure thing, let me change that for a moment.


Potential problems with Nvidia Drivers 535 and g5 instances (AMD EPYC) on AMI v20231116

What happened:
We provisioned a g5.* instance and it was booted with the latest ami Release v20231116
When we try to run any gpu workloads, container toolkit (cli) fails to communicate with gpu devices. When we shell into the node and run nvidia-smi -q it really struggles to get output and bunch of values are Unknown Error
Adding lscpu and nvidia-smi logs
lscpu+nvidia-smi.log.txt
Workload runc errors
Error: failed to create containerd task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods configure --ldconfig=@/sbin/ldconfig --device=all --compute --utility --require=cuda>=12.0 brand=tesla,driver>=470,driver<471 brand=unknown,driver>=470,driver<471 brand=nvidia,driver>=470,driver<471 brand=nvidiartx,driver>=470,driver<471 brand=geforce,driver>=470,driver<471 brand=geforcertx,driver>=470,driver<471 brand=quadro,driver>=470,driver<471 brand=quadrortx,driver>=470,driver<471 brand=titan,driver>=470,driver<471 brand=titanrtx,driver>=470,driver<471 --pid=15676 /run/containerd/io.containerd.runtime.v1.linux/k8s.io/reranker-a10/rootfs] nvidia-container-cli: initialization error: driver error: timed out: unknown

I am reporting this because we have seen similar issues in last few days with A100 + Driver 535 + AMD EPYC configurations someplace else
How to reproduce it (as minimally and precisely as possible):
Provision a g5 instance with latest AMI, run nvidia-smi -q on host
Environment:

AWS Region: eu-west-1
Instance Type(s): g5.8xlarge
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.7
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.27 (v1.27.7-eks-4f4795d)
AMI Version:  amazon-eks-gpu-node-1.27-v20231116
AMI ID: ami-04358af1a6af90875
Kernel (e.g. uname -a): Linux ip-10-2-53-244.eu-west-1.compute.internal 5.10.192-183.736.amzn2.x86_64 #1 SMP Wed Sep 6 21:15:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Release information (run cat /etc/eks/release on a node):

BASE_AMI_ID="ami-0fe9073bb890001f8"
BUILD_TIME="Thu Nov 16 03:14:20 UTC 2023"
BUILD_KERNEL="5.10.192-183.736.amzn2.x86_64"
ARCH="x86_64"

@chiragjn can you please open a service ticket? (since you are using the stock unmodified AMI that EKS team ships!)

The chipset should be fully supported, but I'll verify the device ID: https://download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/supportedchips.html
Is this issue intermittent?

Ah okay, I have created one now. Just curious are the stock AMIs not built using this codebase? The changelog seems to be indicate that

it's a layer above what's here in this repo @chiragjn (cough! check license of things cough!)

Hey, we're experiencing this problem with K80 GPU EC2s like p2.xlarge. It works perfectly for the A10G/V100 GPUs (We're also using the stock AMIs)

@bhavitsharma this is expected, as newer versions of the NVIDIA driver have dropped support for the chipsets used in p2: https://github.com/awslabs/amazon-eks-ami/issues/1448#issuecomment-1743952657

@cartermckinnon, as far as I understand, this is only for kubernetes 1.28. We're running 1.27

@bhavitsharma the GPU cards on P2s do not support 5xx series drivers. The 1.28 GPU AMI has always provided the 535 driver, but starting with release v20231116, 1.25+ GPU AMIs are all shipping with the 535 driver as well. Therefore, P2s will not work with these AMIs

I am still waiting to hear back from support team, just posting there that the issue is not consistently re-producible, got another g5 node and things are working fine 🙃

@chiragjn I haven't been able to reproduce this, and we haven't received any other reports of weirdness on g5 instances. Have you narrowed down a reproduction?

We are also not able to reproduce this consistently, just a few hours ago we had an issue, so far like ~4/10 attempts
I would recommend provisioning a huge number and deploy a gpu workload that tries to use CUDA and see how many of them succeed

@chiragjn this sounds like something that needs to be reported using AWS support. Can you please open one? thanks!

I have reported it, I am guessing they too are having trouble reproducing this. We are doing some tests of our own, I'll post updates on our results

I confirm we have the same problem on g5.4xlarge with the new AMI, the GPU is totally dead:
Kubelet:
Pod Allocate failed due to device plugin GetPreferredAllocation rpc failed with err: rpc error: code = Unknown desc = error getting list of preferred allocation devices: unable to retrieve list of available devices: error creating nvml.Device 0: nvml: Unknown Error, which is unexpected

$ nvidia-smi -a

=============NVSMI LOG==============

Timestamp                                 : Fri Nov 24 11:07:21 2023
Driver Version                            : 535.54.03
CUDA Version                              : 12.2

Attached GPUs                             : 1
GPU 00000000:00:1E.0
    Product Name                          : NVIDIA A10G
    Product Brand                         : NVIDIA
    Product Architecture                  : Ampere
    Display Mode                          : Enabled
    Display Active                        : Disabled
    Persistence Mode                      : Enabled
    Addressing Mode                       : None
    MIG Mode
        Current                           : Unknown Error
        Pending                           : Unknown Error
    Accounting Mode                       : Disabled
    Accounting Mode Buffer Size           : 4000
    Driver Model
        Current                           : N/A
        Pending                           : N/A
    Serial Number                         :<PHONE_NUMBER>225
    GPU UUID                              : Unknown Error
    Minor Number                          : 0
    VBIOS Version                         : Unknown Error
    MultiGPU Board                        : No
    Board ID                              : 0x1e
    Board Part Number                     : 900-2G133-A840-000
    GPU Part Number                       : Unknown Error
    FRU Part Number                       : N/A
    Module ID                             : Unknown Error
[...]

@dmegyesi do you see this on other g5 sizes as well? Is the issue consistent on a given instance or does the nvidia-smi query succeed sometimes?

@cartermckinnon
I think I found a workaround. It seems to be Nvidia GSP related issue.
I was able to get hold of a faulty g5.12xlarge node and I check dmesg with nsenter on the node
And the logs led me to https://github.com/NVIDIA/open-gpu-kernel-modules/issues/446
It reports a few different issues

When multiple gpus are connected via NVLink but assigned to different VMs (https://github.com/NVIDIA/open-gpu-kernel-modules/issues/446#issuecomment-1680023797)
When gpus connected via different kinds of NVLink are assigned to same VM (https://github.com/NVIDIA/open-gpu-kernel-modules/issues/446#issuecomment-1761338816)
GSP causing problems

1 and 2 do not apply to g5 instances, so based on 3, I tried disabling GSP

First checked
cat /proc/driver/nvidia/params | grep EnableGpuFirmware

gives
EnableGpuFirmware: 18
EnableGpuFirmwareLogs: 2

Then tried disabling it
echo options nvidia NVreg_EnableGpuFirmware=0 > /etc/modprobe.d/nvidia-gsp.conf
dracut -f
reboot

Checked again
cat /proc/driver/nvidia/params | grep EnableGpuFirmware

gives
EnableGpuFirmware: 18
EnableGpuFirmwareLogs: 2

Did not work

Funnily enough, AWS' documentation on ec2 nvidia drivers installation mentions this issue but under GRID and gaming drivers
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-nvidia-driver.html

If you are using NVIDIA driver version 510.x or greater on the G4dn, G5, or G5g instances, disable GSP with the following commands. For more information, on why this is required visit NVIDIA’s documentation.
[ec2-user ~]$ sudo touch /etc/modprobe.d/nvidia.conf
[ec2-user ~]$ echo "options nvidia NVreg_EnableGpuFirmware=0" | sudo tee --append /etc/modprobe.d/nvidia.conf
Reboot the instance.
[ec2-user ~]$ sudo reboot

And it points to https://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#disabling-gsp for the reason

Some GPUs include a GPU System Processor (GSP), which may be used to offload GPU initialization and management tasks. In GPU pass through and bare-metal deployments on Linux, GSP is supported only for vCS. If you are using any other product in a GPU pass through or bare-metal deployment on Linux, you must disable the GSP firmware.

Great, let's try this
touch /etc/modprobe.d/nvidia.conf
echo "options nvidia NVreg_EnableGpuFirmware=0" | sudo tee --append /etc/modprobe.d/nvidia.conf
dracut -f
reboot

Checked again
cat /proc/driver/nvidia/params | grep EnableGpuFirmware

gives
EnableGpuFirmware: 18
EnableGpuFirmwareLogs: 2

Did not work

At this point I go for the nuclear option - deleting the gsp firmware
rm -f /lib/firmware/nvidia/535.54.03/gsp_*.bin
reboot

And it works! dmesg complains, but it works!
[   35.745003] nvidia 0000:00:1b.0: Direct firmware load for nvidia/535.54.03/gsp_ga10x.bin failed with error -2
[   36.450155] nvidia 0000:00:1c.0: Direct firmware load for nvidia/535.54.03/gsp_ga10x.bin failed with error -2
[   37.140379] nvidia 0000:00:1d.0: Direct firmware load for nvidia/535.54.03/gsp_ga10x.bin failed with error -2
[   37.844255] nvidia 0000:00:1e.0: Direct firmware load for nvidia/535.54.03/gsp_ga10x.bin failed with error -2

And now my workload runs on this node

@chiragjn thanks! That certainly looks like the smoking gun. Requiring a reboot puts us in a tough position; and I'm not sure we can do something at runtime before systemd-modules-load runs, that happens very early in the boot process. I'll see what I can come up with 👍

@dmegyesi do you see this on other g5 sizes as well? Is the issue consistent on a given instance or does the nvidia-smi query succeed sometimes?

Apologies for not answering earlier, I was attending re:Invent and couldn't follow up with our customers before. Yes, we have seen this on various sizes of g5 instances. I'd say roughly 1 out of 5 times the machines actuallt worked, randomly, can't see a pattern behind even with the same workload. We run the Nvidia DCGM exporter on the nodes that's also touching the GPUs, not sure if this is relevant info.
(Bit of an off topic: Meanwhile we have a support case running with AWS support but it's been super unhelpful, is there a recommended way to get these kind of investigations assigned to the right people over there who are more familiar with the lower level details?)

We run the Nvidia DCGM exporter on the nodes
We also run DCGM exporter and we can confirm that not running it at least reduces the failure incidence rate. But like you said some nodes still run fine, so we don't suspect it is exactly a dcgm problem.
A similar issue was reported on DCGM Exporter: https://github.com/NVIDIA/dcgm-exporter/issues/148 and it also points to GSP related issue

@cartermckinnon Any luck with figuring out a solution? 😅 Any insights into what would be best place in the node lifecycle to fix this would also be great

I came across https://github.com/NVIDIA/gpu-operator/issues/634#issuecomment-1865333713 which is also pointing to GSP as a possible source for this issue

@cartermckinnon I have a working but quite a hacky solution to disable GSP
https://github.com/truefoundry/infra-charts/pull/176/commits/b809b5b8d2247cc2d719bec2c5a567082827307b#diff-af2ed6a75711a35412327054490193f39e21039911b95abfd6324cbe5cc31e2dR230-R240
Is it possible for the AMI team to configure the kernel params and disable GSP while building the kernel modules?

Bumping this again. I am not sure how or where can I get support for this.
Is the EKS team considering disabling GSP or figuring out any alternate solution?

Sorry for the delay; we're doing a rework of our NVIDIA setup to address #1494 which has taken priority.

Is the EKS team considering disabling GSP

Yes, I expect to get a fix out for this in the next few weeks.

We've also appeared to hit this. So far a sure fire way to trigger it has been to run a pod that just runs some nvidia-smi dump/debug commands to confirm a functional GPU. Then recreate the pod on the same node, it'll leave the pod bricked when it restarts with:
  Warning  Failed     57s                  kubelet            Error: failed to create containerd task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods configure --ldconfig=@/sbin/ldconfig --device=all --compute --utility --require=cuda>=11.2 brand=tesla,driver>=418,driver<419 brand=tesla,driver>=450,driver<451 --pid=30895 /run/containerd/io.containerd.runtime.v1.linux/k8s.io/herd-monitor/rootfs]
nvidia-container-cli: initialization error: driver error: timed out: unknown

Before restart we run these commands:
nvidia-smi (just to check for 0 exit code)

Then these:
/usr/bin/nvidia-smi --query-remapped-rows=gpu_uuid,remapped_rows.failure --format=csv,noheader
/usr/bin/nvidia-smi --query-gpu=gpu_uuid,ecc.errors.uncorrected.volatile.sram --format=csv,noheader

This was on a g5.48xlarge and Kube 1.26 AMI Version v20240110

hey @sidewinder12s - I am trying to reproduce the issue based on your comments above and just wanted to make sure I was following the process you were using. If I have the following pod spec:
apiVersion: v1
kind: Pod
metadata:
  name: gpu-test-nvidia-smi
spec:
  restartPolicy: OnFailure
  containers:
    - name: gpu-demo
      image: public.ecr.aws/amazonlinux/amazonlinux:2023-minimal
      command: ['/bin/sh', '-c']
      args: ['nvidia-smi']
      # args: ['nvidia-smi --query-remapped-rows=gpu_uuid,remapped_rows.failure --format=csv,noheader']
      # args: ['nvidia-smi --query-gpu=gpu_uuid,ecc.errors.uncorrected.volatile.sram --format=csv,noheader']
      env:
        - name: NVIDIA_VISIBLE_DEVICES
          value: all
        - name: NVIDIA_DRIVER_CAPABILITIES
          value: compute,utility
      resources:
        requests:
          nvidia.com/gpu: 4
        limits:
          nvidia.com/gpu: 4
  tolerations:
    - key: 'nvidia.com/gpu'
      operator: 'Equal'
      value: 'true'
      effect: 'NoSchedule'

based on your comments (and correct me if I am wrong), you are saying if I deploy it, then remove it, then re-deploy it - thats when you see the issue? Something like:

kubectl apply -f pod.yaml
Pod comes up ok, shows SMI output per usual
kubectl delete -f pod.yaml
kubectl apply -f pod.yaml
The pod fails to deploy, error in logs is shown

Is that correct?

Roughly yes, though we're only ever assigning 1 GPU and I am not sure if we're setting those env vars (its not on our pod spec, but maybe we set it within the container image).
This image is a health checking image that performs a bunch of health checks constantly, including those nvidia-smi commands (largely to discover issues on GPUs that have caused us issues in the past). It's been a few weeks but I'm also not sure if it was caused by a pod restarting, the daemonset pod being recreated/updated or both.

If you are using an image that's built on top of an NVIDIA image, they will have already added those environment variables. Since I'm just using a minimal AL2023 image here for simplicity, I have to add those to get the full SMI output details.
But thank you for sharing, I'm going to keep digging into trying to reproduce the issue

Sorry for the delay; we're doing a rework of our NVIDIA  setup to address https://github.com/awslabs/amazon-eks-ami/issues/1494 which has taken priority.

Is the EKS team considering disabling GSP

Yes, I expect to get a fix out for this in the next few weeks.

@cartermckinnon Apologies for the ping, but was any decision made here? 😅

The latest release (which will complete today) addresses this issue in Kubernetes 1.29 for g4dn instances, by disabling GSP automatically. We're still working on the right solution for g5 instance types. These instances support EFA and require the open-source NVIDIA kmod as a result, but the GSP feature cannot be disabled on the open-source kmod. We're following up with EC2 and NVIDIA regarding this issue.

the GSP feature cannot be disabled on the open-source kmod

Is there any documentation that mentions this?
My userdata script that tries to disable GSP is sadly now broken with the new release with open source kmod rolling out

In my tests, the kmod param EnableGpuFirmware just doesn't have any effect with the open kmod. It doesn't seem to be used anywhere in the code, but it's 100% possible I'm misreading things: https://github.com/NVIDIA/open-gpu-kernel-modules/blob/3bf16b890caa8fd6b5db08b5c2437b51c758ac9d/kernel-open/nvidia/nv.c#L131-L133
We intend to load the proprietary kmod on g5 types for the time being so that EnableGpuFirmware has the intended effect. That will ship in the next AMI release (the one after v20240315).

We intend to load the proprietary kmod on g5 types for the time being so that EnableGpuFirmware has the intended effect. That will ship in the next AMI release (the one after v20240315).

We've completed our rollout of this across all active k8s versions, so I'm going to close this issue. If you continue seeing this problem, please mention me here or open a case with AWS support.


Darken instances is super laggy on some pcs

This has to do with the need for blending pixels to add negative brightness and contrast to a stretchblt.
If transparent pixels can be drawn over an instance using basic win32 gdi functions, it may be a better solution, but I cannot find a way.

Closing because Julti Wall is no longer the focus. In the future I look to make OBS setup even easier.


Send Alert for Image Version Updates

I am requesting customization to send an alert every time a container image version is updated.
When a new deployment is applied to the cluster, pods are created using the new image and I want to alert a slack channel about this new image referencing the service name/deploy name and namespace. i.e. "$SERVICE $IMAGE has been deployed to $NAMESPACE" or something like this.

duplicate of https://github.com/infracloudio/botkube/issues/135

@mrushdan this is getting tracked under https://github.com/infracloudio/botkube/issues/131. Hence closing this issue.


Unbind all listeners of the same event type

Hi @jgermade,
i'm having some issues with a 3rd party code overriding the HTML5 Media API 'ended' event and i want to remove all listeners from that element, then, either restore them to default or add my own with the .on() function.
I've seen that with jQuery i could have used video.unbind('ended').
Do you think it is possible to add this to jqlite? or can you think of an alternative ?

Hi @Fire-Brand, you can use .off(eventName, handler)
both eventName, handler arguments and required for now
I think I'm going to add support for when handler missing, all handlers will be removed.
The issues queue is growing, I'll try to resolve all of the soon :smile:
Thanks for the feedback!!

Awesome! That's good news, this is by far the most urgent issue in my book,
so i would love to see that eventName only functionality.
Thanks!

@jgermade , let me know if there anything i can do to help speed this up :v:

Hi @Fire-Brand thanks a lot for your help!
issue is close to be done in PR #35 , just want to add some more tests

HI @jgermade, this is awesome! can't wait!

Ok! merged!
is included in new version v0.2.26
as well as .noConflict() method

WooHoo!  :smiley:

Guess it's time to update the Readme file :hankey:

for sure!! it's a little bit outdated :smile:

Hi @Fire-Brand, finally starting to work on a better documentation :smile:
https://github.com/jstools/jqlite/tree/better-documentation


[DEVX-1599] Puppeteer-Replay

Proposed changes

Introduces puppeteer-replay.
PS: The UI does not yet support this framework. So don't bother clicking on any job links.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] I have updated the json schema (if appropriate)

Further comments

LGTM 🎉


Create a validation that at least one character type should be selected

User Story
AS AN employee with access to sensitive data
I WANT to randomly generate a password that meets certain criteria
SO THAT I can create a strong password that provides greater security

Acceptance Criteria
GIVEN I need a new, secure password
WHEN I answer each prompt
THEN my input should be validated and at least one character type should be selected

I used an if statement and || operator to check that the user selected at least one character type.


Set NuGet's maxHttpRequestsPerSource setting to a reasonable value for Linux

Description
We've seen at least one occurrence of connection limits being hit during dotnet restore on a Linux larger runner, though impact could be larger. According to the documentation (see emphasis):

maxHttpRequestsPerSource
Controls the maximum number of parallel requests sent from NuGet to every package source for package dependency resolution and downloads. The default value on dotnet.exe is Int32.MaxValue which is derived from HttpClientHandler.MaxConnectionsPerServer property. This setting has no impact on dotnet.exe for Mac OS because the throttling limit is set to 16 to avoid too many open files error. The default value for NuGet client tools that runs on .NET Framework such as Visual Studio and nuget.exe is 64 on Windows and 1 on Mono. The default value for Packages.config style projects is set to Environment.ProcessorCount. Configuring maxHttpRequestsPerSource property to a value less than the default could impact NuGet performance.

For larger projects this can result in intermittent connection timeouts as the VM can no longer connect to the pool's load balancer (which is restricted to 1024 connections from an individual VM). Some examples from other software:

npm defaults to 50: https://docs.npmjs.com/cli/v6/using-npm/config#maxsockets
Chrome defaults to 6: https://superuser.com/questions/499114/how-to-increase-chromes-connections-per-server

We could just use the same limit as Windows of 64 or Mac of 16, there's no real heuristic for it other than not being "unlimited".
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[x] GitHub Actions - Larger Runners

Runner images affected

[x] Ubuntu 20.04
[x] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
All current Linux images
Is it regression?
No
Expected behavior
Limited connections being made from nuget restore and dotnet restore on Linux, which lessens chance of intermittent connection timeouts.
Actual behavior
Projects with many packages on the same source can have intermittent connection timeouts.
Repro steps
N/A

Hey @pjquirk!
We'll take a look ASAP. Thank you for bringing it into our attention.

Hey @pjquirk!
It seams that the issue lost the owner. 😿 We did some research and I may say next. Overall, your idea seems sound. 🙇
But as usual, there are some nuances. If we set limits different from the preset ones, then this will have exactly the same effect on projects with a small and medium number of packages/dependencies. For some, downloads will speed up, for others, they will slow down. We do not really welcome such changes. Especially in this case.

Firstly, the problem is easily bypassed on the project side by using your own nuget.config file.
Secondly, this is the method recommended by Microsoft documentation to avoid configuration inconsistencies.
Thirdly, because we stopped providing Nuget (as Mono dependency) on Ubuntu-24.04 and I am not sure whether we will return to this practice.

Given all this I am going to close this request.


[Extension] Add support for Mythos Chain

https://github.com/Koniverse/SubWallet-ChainList/issues/204

Version test: http://file.cdmteck.com/s/QBy8maKBEy5QYXn
Validation passed.

Network, token info

Show balance

Receive

Transfer

Version test: http://file.cdmteck.com/s/QBy8maKBEy5QYXn
Validation passed.

Network, token info

Show balance

Receive

Transfer


🐞 [BUG_LP] - Adding Team Page in the Website

Description of the bug. ✍🏻
In Navigation bar there is a button named pages with a option of teams but the teams button is redirecting to the landing page only. I wish to add a team page for that button.
Current Behaviour
The team button is redirecting to home page only .

Expected Behaviour
The team button should redirect to a page having info about team.
Reproduction Steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots
No response
Additional information
No response
Contributor terms

[X] I agree to follow the Contributing Instructions

/assign

LoL, what do you mean by /assign? BTW, we are not up with the content yet. It's not final. We have to think of a solid content before updating - let's keep this on hold?

Can you please assign me this issue under GSSOC'23?

I am interested to work on this. I will create a dynamic and customizable layout for each team member's profile. This will allow users to showcase their own unique style and personality by selecting from various design options such as different color schemes, fonts, and layout variations.

Okay, cool, this looks interesting, but we're first looking on getting the initial content done right? @Shatakshi127 What were you planning to add though? That won't be dynamic as well right?


What is the account & company schema when multiple addresses are recorded?

The address1 and address2 fields can be used for so many different purposes. Can we standardise their use?

Also bear in mind the three standard addresses on Contacts are assumed to be Business, Home, Other when synchronising to Outlook (if you enable all three).
But in a purely B2B scenario, Home is unlikely to be needed.
On Account it is har to say whether they should be used for Bill To and Ship To, or whether Address 1 should always be the "official" correspondence address (=registered office for incorporated companies). This might not be the address you send invoices too (sometimes the registered address is their lawyer or accountant), nor an address you visit (invoices might go to a specific branch with back-office functions).
I think the order of these three main address types depends on which is most useful to most users. Registered / official (=Primary?) is useful for finance, but not for sales visits unless it is also where the decision makers are.
Bill-To is likely to often be the same as Primary, except where primary is a lawyer / accountant / other proxy
Ship-To could be the place you also visit, but might be the factory (when the sales decisions take place in an office downtown).
For customer service, you probably visit where the goods were shipped to, in order to fix them.
Am I overthinking this, or is it actually so variable between businesses to figure out which they want to use?

I don't think your overthinking it at all, on the face of it appears a quite simply 'defining' exercise but i think when you consider it some more in different scenarios it really does become complex.
Good call on the Outlook note - that is really important to remember actually!
I am of the thinking that this is linked to Issue#1 which looks at official uses/contractual/invoicing uses of Accounts - but also the hierarchical structure and relationships with Parent/Child Accounts too - i think by using those it may become less complex and the requirement to log so many addresses may become more redundant?


Getting data safely in the Node.judge callback.

Now, users have to retreive data from the 'data' argument in the Node.judge callback and comfirm if certain data is come. It is a proposal that the pisat should add some function to get data safely in Node and check statically if data names used in Node.judge are same as data to be acquired by DataLogger.

Added new attributes named Node.DNAMES_JUDGED as a class variable in order to detect what data is used in a Node. That helps the pisat system gives the Node data including the required data names certainly. Also added new subpackage named tester for users' easy tests, but the subpackage has only some classes and function now.


Pivot to gha for wheel builds and pypi trusted publishers

Summary
This commit pivots the wheel publishing jobs to PyPI trusted publishers. This mechanism authorizes the repository action directly so that user creds or tokens are not needed to push the wheels anymore. This mechanism will be more robust as the the github repository is linked directly to the pypi project and not dependent on a single user account. The one tradeoff required for this is that we must use github actions to leverage this PyPI feature. So this commit migrates the wheel publishing jobs from azure pipelines to github actions (which we were already using for non-x86 linux wheels).
Details and comments
This is marked as on hold because some changes to the qiskit account need to be made prior to using this mechanism. This will require coordination with the other ~27 projects using the account.

The plan is to make this migration before 0.45.0rc1 and that'll be the first release to use trusted publishers. We'll coordinate the migration of all the packages managed by the qiskit account to the new mechanism at the same time.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.02%) to 87.031%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
93.76%

crates/qasm2/src/lex.rs
2
90.91%

qiskit/extensions/quantum_initializer/squ.py
2
84.15%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
74334

Relevant Lines:
85411

💛  - Coveralls

So something I just learned testing this on rustworkx is that the publish action only works on linux. So we'll have to adjust the workflow here to use a shared upload job at the end at least for the tier 1 builds. This actually documented if you read through the readme on the action (which I didn't) here: https://github.com/pypa/gh-action-pypi-publish#non-goals

So something I just learned testing this on rustworkx is that the publish action only works on linux. So we'll have to adjust the workflow here to use a shared upload job at the end at least for the tier 1 builds. This actually documented if you read through the readme on the action (which I didn't) here: https://github.com/pypa/gh-action-pypi-publish#non-goals

I updated this in: https://github.com/Qiskit/qiskit/pull/10999/commits/dea18e68a592a7ca3c91cfe3772fcfe7223a65b9


fix(card): apply component classes to card component

Extra styles have been migrated from https://github.com/fabric-ds/css/blob/next/src/components/card.css

Type
Screenshot

Single card

Toggles in Card

Dead toggle in Card

 Warpify Card component


Question on the terminology that is used in your paper

Hello.
congratulation on the first place in MICCAI registration challenge.
Because your paper is famous, I was reading your paper from this one.
However, I was curious the terminology that you used in this paper.
Of course these terminology was used not only in your paper, as well as other paper,
but I was curious what is difference between
displacement vector field, registration field, dense vector field, deformation field.
Even though there are many papers use these terminology, but I thought those are similar one only has different name.
but in your paper you specially use dense vector field, and deformation field different paragraph.
if it is fine, could you share your time to explain what is the difference between these terminology?
from the "An Unsupervise Learning Model for Deformable Medical Image Registration" which is preliminary study of voxelmorph,
using 3 channel from the Unet output, I thought that is the phi (registration field, which is called as displacement vector field).

but I cannot understand the what is difference between dense vector field  and deformation field in your paper..
could you explain it if you have time.
I really curious about this, so I thought this is the best way to ask you directly.
Sorry for bothering you.
Thanks

Hi @yoonguusong,

congratulation on the first place in MICCAI registration challenge.

Thanks. :D

what is the difference between displacement vector field, registration field, dense vector field, deformation field.

To my understanding, The "deformation field" and "registration field" refer to the same/similar thing, which is a generalized term to describe the non-linear transformation grid (or flow-field grid) that is used to warp the moving image. For example, the grid_sample function in Pytorch takes any grid and moving image as input and outputs the warped moving image using the input grid. The grid can be parameterized with any transformation model, like B-spline, displacement vector field, stationary vector field, affine transformation etc.
The "displacement vector field", "dense vector field" and "displacement field" refer to a more specific transformation model that is defined as \phi(x) = x + u(x), where x is an identity transform and u is the displacement vector field.  This is the simplest transformation model in non-linear image registration methods and doesn't guarantee any diffeomorphic property. I suggest you read a classic paper, "A fast diffeomorphic image registration algorithm" by John Ashburner. It explains many terms used in image registration systematically.

From the "An Unsupervise Learning Model for Deformable Medical Image Registration" which is preliminary study of voxelmorph, using 3 channel from the Unet output, I thought that is the phi (registration field, which is called as displacement vector field).

You're correct. It outputs the 3-channel displacement field for 3D image registration. The 3-channel displacement field defines the displacement in the x, y and z-axis.

Hi @yoonguusong,

congratulation on the first place in MICCAI registration challenge.

Thanks. :D

what is the difference between displacement vector field, registration field, dense vector field, deformation field.

To my understanding, The "deformation field" and "registration field" refer to the same/similar thing, which is a generalized term to describe the non-linear transformation grid (or flow-field grid) that is used to warp the moving image. For example, the grid_sample function in Pytorch takes any grid and moving image as input and outputs the warped moving image using the input grid. The grid can be parameterized with any transformation model, like B-spline, displacement vector field, stationary vector field, affine transformation etc.
The "displacement vector field", "dense vector field" and "displacement field" refer to a more specific transformation model that is defined as \phi(x) = x + u(x), where x is an identity transform and u is the displacement vector field.  This is the simplest transformation model in non-linear image registration methods and doesn't guarantee any diffeomorphic property. I suggest you read a classic paper, "A fast diffeomorphic image registration algorithm" by John Ashburner. It explains many terms used in image registration systematically.

From the "An Unsupervise Learning Model for Deformable Medical Image Registration" which is preliminary study of voxelmorph, using 3 channel from the Unet output, I thought that is the phi (registration field, which is called as displacement vector field).

You're correct. It outputs the 3-channel displacement field for 3D image registration. The 3-channel displacement field defines the displacement in the x, y and z-axis.

thank you for letting me have your honorable time.
gratitude on your explanation. Thanks.


Not install in latest node/npm.

Not install in latest version of npm...

Hi @farazalikhan786, this library is built on node-fibers, which has been discontinued for a few years now. If you really need to use this library, you'll need to use an older node version (<=14). But most people should be fine with native async/await support in JavaScript/TypeScript these days.


Scikit-learn 19.0 updates on .fit( ) arguments

Adopting code to my needs I have found that in the scikit-learn 19.0  they recommend to put params list directly into the .fit( ) method. It looks like a good change as that makes the code more understandable for me - now it is more clear where these values go to (fit( ) function of DNNClassifier).
Hope this makes sense.

Hi @ChrisQlasty ,
Thanks a lot for this PR, it's a very interesting point. The only problem is that many people still use scikit-learn 0.18, so they would get an error. For now, I prefer to leave the existing code in place, but I will add a comment to explain your point (or if you want to do it, please update your PR).
Thanks again.

Hi @ageron , I have updated the PR as you suggested (that was right point). If you think it could be described in other way, update the section according to your preferences.
I am sorry for the mess in the commits (extra empty line spoiled the formatting).
Btw - so much thanks for excellent book and your incredible activity here!

Merged! Thanks a lot for your contribution and your kind words.
I see that something else was messed with my PR but you managed to fix it - so again I am sorry for giving you unnecessary jobs. Have to be more focused next time.

Oops, I merged a bit too fast, the JSON was actually incorrectly formatted, so Jupyter was unable to load the notebook.  I fixed the problem, everything's okay now.
Jupyter notebooks are great to work with, except that they are a pain to manage as source code. Whenever someone sends me a Pull Request, if they actually run the whole notebook before submitting the PR, then the diff is huge and very hard to read. It's better when you use nbdime to view the notebook diff, but it's still not perfect, in particular it's too slow. I prefer PRs with a small diff that I can easily verify visually, but then if I merge it without actually testing it (like I did above), there's a risk that it will crash the notebook. And since it's Machine Learning, testing the whole notebook can take hours. So I end up only testing the cells that were modified, which isn't great (in this particular case, since it's just comments, I'm confident that the notebook will still have the same output, but in other cases, there might be side-effects that are hard to predict).
That said, thanks again for your contribution, and don't hesitate to send more PRs.

I agree. Thank you for the valuable comment for the community I believe.


iam_audit_config_authoritative not compatible with any IAM variables other than iam_bindings_authoritative

iam_audit_config_authoritative sets the audit configuration using google_organization_iam_policy, whereas iam and group_iam use google_organization_iam_bindings. The google_organization_iam_policy contains audit permissions but lacks any IAM bindings and removes any permissions granted from iam and group_iam resources.
Using iam_bindings_authoritative is the only way to add the permissions to the organization_iam_policy. This behavior should at least be well documented since you can easily cut yourself off from the existing organization unless you have Google Workspace super admin permissions.

Hey John, in general what holds true for the underlying resources also holds for our modules in regards to IAM:

iam and group_iam are authoritative for a role
the _additive versions are additive, they conflict with the above on a role basis
IAM policy is authoritative for the whole set of roles on a resource, and should be used by itself

We assume users know the basics, but we can certainly improve our documentation to point the above out, as you suggest. Is there any place in particular where a warning would have caught your eye?

Definitely not my first rodeo with the member, binding, and policy constraints. I guess what confused me was the authoritative audit config since this wasn't mentioned in the IAM section.
A note or warning there mentioning that the iam_audit_config_authoritative variable is only compatible with the iam_bindings_authoritative variable would have been useful.

Yep, will try and add it tomorrow and ping here when done, thanks for highlighting it! We might also decide to revisit the variable names, if that's a source of confusion.

John, it took me a while but I added an extra sentence to the README file for the org module. I now understand what you mean, sorry for not grasping the full context earlier. Do you think the extra sentence is enough, or do we need a better explanation?
And thanks for spotting this!

I think ths looks good, thanks for adding that info!


Company Logos were not visible in Dark Theme.

Codecov Report

Merging #1326 (75e75f5) into main (447811c) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1326      +/-   ##
==========================================
- Coverage   94.23%   94.22%   -0.01%
==========================================
  Files         232      232
  Lines       40850    40850
==========================================
- Hits        38496    38492       -4
- Misses       2354     2358       +4

Impacted Files
Coverage Δ

src/directory/directory.rs
94.11% <0.00%> (-1.48%)
:arrow_down:

src/query/union.rs
98.78% <0.00%> (-0.61%)
:arrow_down:

src/query/boolean_query/block_wand.rs
96.85% <0.00%> (-0.21%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 447811c...75e75f5. Read the comment docs.


Set Citadel spiffe trust domain for all root certs

Right now Citadel will only set the SPIFFE trust domain when using self-signed certs. However in multi-cluster scenarios, my organization at Microsoft wants to use intermediate certificates scoped to a trust domain that bubble up to the same root authority. Each trust domain could then be used in RBAC scenarios to identify the cluster.
I have tested this by creating a custom Citadel build and deploying it in my multi cluster setup. Trust Domains with RBAC work as expected.
Without this change, Istio is non-functional with trust domains and custom certs.
Fixes: #17093
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @cart. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/cc @costinm @myidpt @nmittler
I heard some similar ideas are brought up in multi cluster working group. cc some folks to ensure this is aligned with the future plan.

I'm not sure how "official" it is, but this is the "Federation within an Organization" model presented at KubeCon. Here are the slides.

cc @smawson

I think this is well enough aligned, the plans for federation in identity space is to use spiffe federation.
I agree with the istio-policy-bot though, where is the test verifying this does what is intended?

That's good news. I can definitely work on tests, however I'm new to this project so it might take some time. That being said I'm invested in this feature and I'm willing to put the work in.
There is a missing piece to the "federation" puzzle that I just discovered and tested in my own multi cluster mesh.
Lets say we are employing the "Federation within an Organization" model I linked to above. The mesh has a shared root certificate and each cluster has an intermediate cert minted for each trust domain. Consider the following example setup:

TrustDomainA

contains ServiceX

TrustDomainB

contains ServiceY

TrustDomainC

The TrustDomainB admin authorizes TrustDomainA/ServiceX to call TrustDomainB/ServiceY and rejects other callers. This is accomplished by enabling RBAC and creating a ServiceRoleAssignment for the following identity: spiffe://TrustDomainA/ns/default/sa/service-x-service-account.
Now pretend the TrustDomainC admin is malicious and wants to pose as TrustDomainA/ServiceX and gain access to TrustDomainB/ServiceY.
TrustDomainC can use its intermediate root certificate (scoped to TrustDomainC) to mint a cert containing the SPIFFE identity: spiffe://TrustDomainA/ns/default/sa/service-x-service-account.
Without a fix for this problem, we gain nothing over the traditional "shared root" model and I would argue we are not accomplishing the goal of trust domains.
The fix I think we want is:

Extract the Trust Domain from the SPIFFE identity of incoming certs
Compare that to the Issuer's Subject Alternative Name

This piggy backs on the existing trust domain example certs here: https://github.com/istio/istio/tree/master/samples/certs
To avoid breaking existing customers, we would probably want to put this behind a config flag.

To be clear, I tested this in a multi-cluster setup containing the fix in this pr.
I was able to generate a cert where the spiffe identity's trust domain did not match the Subject Alternative Name of the intermediate cert.
I was then able to use that certificate to access an RBAC-ed service that intended to scope access to a different trust domain.

I think the proposed fix would end up looking a lot like this pr: https://github.com/istio/proxy/pull/2313, but with issuer SAN validation

TrustDomainC can use its intermediate root certificate (scoped to TrustDomainC) to mint a cert containing the SPIFFE identity: spiffe://TrustDomainA/ns/default/sa/service-x-service-account

If the intermediate certs are issued with name constraint, the cluster C intermediate cannot issue a valid cert for cluster A.

This is where tests are very useful: If we can look at tests showing exactly what is supposed to work and what is not, it is clear what we're trying to accomplish, and easier to discuss.
We can also do that in the context of a short doc describing what we want to enable and what should be prevented, but of course that should just end up with tests verifying it works as intended.

@loewenstein I haven't verified that the name constraints are respected by Envoy. Just curious - have you done any verification around that?

/lgtm for the code. Please add unit tests.

@myidpt: Name constraints definitely sound like the better / more standard option. I will also definitely add unit tests. I'll try to do that asap.
Just out of curiosity, when do you expect this to land in an official Istio release?
My org at Microsoft is about to start piloting Istio. I'm happy to maintain a custom fixed version of 1.2.5, but ideally we move back to official 1.3 builds as soon as possible.
Its also worth pointing out that multi cluster is currently broken in 1.3.0 (captured in bug #16890)  so we're also blocked on that.
I'm not trying to make my problems your problems. I'm just letting you all know what scenarios we're shooting for as I expect we aren't the only folks interested in multi cluster trust domains.

@myidpt we tried name constraints with Envoy before we started to work on the configurable trust domain. So yes they did work.

That's great news! Its probably worth updating samples/certs/Makefile to include name constraints unless we can think of a reason that shouldn't be the default / recommended approach.

I am surprised this change is needed. We intended configurable trust domain to be used with externally provided certs.
@c0d1ngm0nk3y @kramerul @holgero

This fix was on main - we should verify that istiod has the equivalent correct code !


Corona-Tracker

Describe the project
It is a Corona-Tracker web app .In which i have used HTML,CSS,JAVASCRIPT,API.
It tracks the tracks the data between the dates and show us on screen.
Screenshots

@kuldeepjoshi27 please provide reference images or screenshots for your project.

@kuldeepjoshi27 please provide reference images or screenshots for your project.

Ok @kuldeepjoshi27 I'm assigning.


Document file formats in VarStore::save and load methods

VarStore::save and VarStore::load methods behave differently based on the file extension. This PR adds documentation for this behavior.

Thanks (and sorry for the delay).


Deserialization failures

https://bungie-net.github.io/#/components/schemas/Destiny.DestinyProgressionRewardItemState - this is probably a bitfield, I see values like 3, 7, 6,10 in the real data from API. But serde doesn't know about that, and fails to parse the whole response.

Thanks, I'll take a look. Haven't touched this in a long time, planning to revisit it before TFS.

Looks like it might be because Bungie has bumped the API to 2.18.1 and this is currently generated against 2.18.0?


v1, does not handle error for CurrentPlayer as anonymous

Riffing off https://github.com/avimoondra/fishbowl/pull/22

closing in favor of https://github.com/avimoondra/fishbowl/pull/25

 [M-L] Improve Host/Join Experience


Settings bar menu entries shifted to the right

Screenshots

I didn't change any file in chrome/, but this is my situation rn.
I have Windows 10, is there any property similar to the ones in window-control/wc-wt-windowspatch.css but useful for the Application Menu?
Firefox Version:
89.0

Same issue here on Windows 10, FF version 89.0.1

https://github.com/akshat46/FlyingFox/issues/81#issuecomment-855464978


Lacking Privacy Notice / Third Party Gets Data

This application appears to send any QR data entered to https://api.qrserver.com which is operated by a marketing company goQR.me, Nothing about the documentation states that this is not a fully self-hosted application for QR codes as implied by the site information. It should be declared upfront this requires an external API service and that any data entered for QR code generation is being shipped off to a third party. I'm not saying there's anything nefarious with goQR.me, but it should be stated up-front that data is being sent elsewhere.

hi, you are right, thanks for letting me know. As soon as possible I will update the documentation where I will explicitly indicate which service is used to generate the qr codes!


Snapshot - Update Rpc api and Various Fixes

fix(agents/core): handle pending snapshot operations

When create fails for LeaveAsIs, clear the existing op.
On failure, set stale transaction as deleting.
Reconcile dirty volume snapshots.

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

fix(agents/core): don't use transaction for node and certain other operations

Also add missing openapi operations enums.

Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

  fix(snapshot/pool): collect pool information from rpc

  Also enable list of all snapshots now that the bug has been resolved in the dataplane.

  Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

  feat(snapshot): update io_engine controller to make use of updated api

  Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

  chore: update rpc and dependencies submodules

  Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge


chore: Use Ops.CollectStatus Event

Description
This PR uses new ops feature CollectStatus Event to manage status Charm.  Event named collect_unit_status sets the status of charm automatically at the end of every hook.
Reference:

https://ops.readthedocs.io/en/latest/#ops.CollectStatusEvent
https://discourse.charmhub.io/t/how-to-set-a-charms-status/11771

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[x] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

Waiting for the fix of https://github.com/canonical/operator/issues/940.


Don't wrap banner

Let's remove this wrapping feature, or at least only make it show up when the window gets very small:

@rushk014 let's try to be more diligent about referencing which commits fixed which issues. For example, this issue is closed, but there are no references to the commit that fixed it.

@daterdots sorry just realized that was a feature of commit messages, ill be sure to do references in the future


Handle SpEL for byte-array payloads

Override the HeaderEnricher#transform to handle byte[] payload. (Similar to the LogSink use case).
extend test to emulate byte[] payload.

Resolves #23

@tzolov Thank you for updating, I'll try it.


wording change

was blogging this and wanted to make it clearer.
also there appears to be both a spec.md and a SPEC.md. I think that may have confused my filesystem and/or self.

Aha. I wonder how I got two spec.md in there, I'll see if I can kill it somehow...


get selected nominators info

To show nominated validators info in nomination tab quicker, we can fetch their infos in the tab instead of waiting for the workers which gets all validators infos

done (https://github.com/Nick-1979/polkadot-Js-Plus-extension/commit/c1024072c5adaa36cce766d57f9d3b4d14e2f4d4)


How to use sink node or callback?

This twos has not enough documentation to describe how to do, I need get an output in java.
For example i need to do some action(e.g take a picture or other thins) in java when detected targets.

The solution is at https://github.com/google/mediapipe/issues/831


help ____ Synchronization failed due to token inconsistency.

haaaalp

Synchronization failed due to token inconsistency.

@benweet @stephenprater @GreenGremlin @Flamenco

What service are you using as a provider?

My fork repo has fixed this bug.
StackEdit+ : https://stackedit.net
open source: https://github.com/mafgwo/stackedit-plus


Fix Tab order for Recorder controls

In both, new and old recorder the default Tab stop order works correctly so there no need to artificially change it with setting the TabStop property.
Closes #961

Thanks, it works. :)


Creating external service with multiple protocols results into deployment failure

Summary :
Steps to replicate:
In service hspec define multiple protocols for port, as shown in the screenshot
Expected result:
Deployment should have been successful
Actual result:

Screenshots/Additional info:
Ports definition:

Fix for the error message displayed to the user:  https://github.com/hyscale/hyscale/pull/176

Kubernetes side issue:  https://github.com/kubernetes/kubernetes/issues/23880
Kubernetes enhancement:  https://github.com/kubernetes/enhancements/pull/1438
Kubernetes PR:  https://github.com/kubernetes/kubernetes/pull/75831


Fixed form highlighting marks marks 73rd character as comment

Description
If the 72nd character of a command corresponds to the end of an expression e.g. a comma, closing parenthesis, whitespace, a number (not an exhaustive list), then our syntax highlighting will fail marking the rest of the line as a comment block.
Even if there is a strict compilation rule to impose 72 char limit I think it shouldn't be enforced in the syntax highlighting especially since we can override this restriction during compilation.
MWE
C F77 MWE syntax highlighting breaking at line
      PROGRAM TEST

      integer :: i = 10
      ! Character 73 begins here -------------------------------------->
      print*, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i,
      print*, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i,i, i,
      print*, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i,i,i, i

      print*, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19
      print*, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,18, 19

      print*, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, (1), 18, 19
      print*, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 1, 18, 19

      END PROGRAM TEST

Highlighting

Duplicate of #87
I have went ahead and updated 87 to have a more complete description


Rename javy-core to javy-plugin

Description of the change
Renaming javy-core to javy-plugin.
I've updated the name in our documentation but I will go through the documentation more holistically in the future to ensure it's up-to-date as opposed to doing that as part of this PR. I have also tested the release GitHub Action to determine that it is working correctly with this change.
Why am I making this change?
Part of #768. The javy-core crate is the default plugin for Javy so a name like javy-plugin better reflects that.
Checklist

[x] I've updated the relevant CHANGELOG files if necessary. Changes to javy-cli and javy-core do not require updating CHANGELOG files.
[x] I've updated the relevant crate versions if necessary. Versioning policy for library crates
[x] I've updated documentation including crate documentation if necessary.

It's because the test_core check is marked as mandatory but the name of the workflow has been changed to test_plugin. So I need to remove test_core as a mandatory check before I can merge and then I can mark test_plugin as mandatory.

Branch protection rules have been updated


Fixes #481

Thanks @tcNickolas, I wanted to address this in the PR, remarking that we fix this particular instance, but will fix the many others as part of other PRs and general quality improvements. I noticed some instances of ## Example in this file, but there are many others. I think that we should address this.


Positive and negative record flow on my records page

TABLES

[ ] create two new columns called "Most Recent Positive" and "Most Recent Negative" under the InvasivesBC record sets (main set and any subsequent record sets they create) to allow users filter down for just the most recent record on a location.  It is understood that if any part of the record is the most recent (ie there are partially overlapping records), the full record will show even if only a part of it is most recent.

[ ] Rename the existing columns in the invasivesBC record tables that will continue to show all the positive and negative records to be "All Positive" and "All Negative".

Use the views created by Brennan (current positive and current negative) to populate the new columns.

`+/- observation status
names of the views

current positive observations

should be per species, meaning each record can be in there more than once

current negative species

should also be PER species - same record can be there more than once

UX
A)

works for when you know what you're looking for, not really exploring

advanced filter -  "current positive" or "current negative"
first select dropdown - '+' or '-'
second will be species

B)

columns for display, maybe filtering:

do allow for filerting here:

has current positive (boolean)(record in current positive view at all)? true: false

skip filtering here for now:

list of current species for that record (concat all species for that record in current positive view )

do allow for filerting here:

has current negative (boolean) (record in current negative view at all)? true: false

skip filtering here for now:

list of current negative species for that record (concat all species for that record in current negative view)

C) ?
`
rolling with option B for now


scraping: change log from debug to warn on parse error

In this PR, I have made a change to improve the logging of append failures in Prometheus. Previously, the log level for "Append failed" messages was set to Debug.
However, since these failures can be crucial for users to understand potential issues with parsing or sample limits, I have raised the log level to Warning.

While I sympathise about wanting better notification of issues, I would be concerned about the quantity of logging this can generate.
Maybe some metrics which help to identify there is a problem, and an out-of-band tool to check for parse errors?

Thank you for your contribution. We have discussed this during our bug scrub and have decided to not change the log level.
However, we are open to better ways to manage the logging of scrape errors.


Add Scaleway to rclone documentation

What is the purpose of this change?
Scaleway is offering a S3 compatible product. The goal of this PR is to inform rclone users that they can use Scaleway object storage with rclone.

Sorry for the delay, been a bit busy!
Your PR looks fine - will merge it in a moment, thank you.  It didn't break the build, don't worry!

Thanks @ncw do you know when the website will be updated?

It will be updated at the next release on 7th Feb.  You can checkout https://tip.rclone.org in the meantime

I don't find Scaleway on the homepage of this website :/ How can I make it
happen?
Le sam. 2 févr. 2019 à 13:35, Nick Craig-Wood<EMAIL_ADDRESS>a
écrit :

It will be updated at the next release on 7th Feb. You can checkout
https://tip.rclone.org in the meantime
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ncw/rclone/pull/2941#issuecomment-459961784, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASXIuHuG_Eo1FYXhxy7d6w28fEILShmks5vJYYZgaJpZM4aWEHS
.

I don't find Scaleway on the homepage of this website :/ How can I make it happen?

Wait until 2019-02-07 for the v1.46 release :-)


Start supporting Electron 23, drop older Electron versions

Changes

Dropped Electron versions:

Electron 14, 15, 16, 17 - reached end-of-life.
Electron 22 - uses Node 16, which we want to drop.

Added support for Electron 23. No changes are required since none of the breaking changes should affect us.

Could you update SupportedPlatforms.md? It's currently pretty unhelpful:


Fix Windows dimension detection

Hi @Tbaile, thanks for your contribution, but it looks like somebody beat you to it in #64


Better support for trailing slash in links and custom link generation

Discussed in https://github.com/statiqdev/Discussions/discussions/107

Originally posted by zivkan November 27, 2021
I decided on using index.md for my blog posts (and naming the folder the title of my blog post), so any post-specific content (images, etc) can stay in the same directory as the blog post. For example, I have URLs such as:
https://domain.test/blog/my-first-post/  (this is index.html)
https://domain.test/blog/my-first-post/image.png
However, the document believes its canonical URL does not contain the trailing slash. Therefore, the canonical URL in the HTML header, the URL in the ATOM and RSS feeds, and links from the homepage all point to the "no slash" URL, which the web server then redirects to the slash.
How do I configure statiq to generate URLs for document that retain the trailing / when the document is otherwise ending with index.html?
edit: I just noticed on Google Webmaster Tools that I have a whole bunch of excluded pages of type "Alternative page with proper canonical tag". It appears that my pages are still getting indexed, but when I see errors or excluded pages, it makes me a bit worried, so I really would like to fix this.

Interesting question! I think canonically a trailing slash indicates that directory (I.e. the index.html file, which is how you're using it). In general, I usually see static hosts "hide" the index page so that URLs appear to be rooted at the parent folder path. This can actually cause some problems of its own when file names and folder names collide. But it sounds like your issue is different.

How do I configure statiq to generate URLs for document that retain the trailing / when the document is otherwise ending with index.html

This is probably the heart of the question. Statiq contains a setting LinkHideIndexPages that toggles the hiding of the entire index.html file (going up to the root folder without a slash), but there's no built-in way to both hide the index page but also leave the trailing slash.
I see two options (or both) going forward:

Introduce a new setting, something like LinkPreserveTrailingSlash.
Document and promote implementing a custom ILinkGenerator which is what's responsible for generating links. Right now the Engine isn't coded to accept a custom link generator implementation via DI, so that's something we could change.

I don't think either one will be too complicated, assuming I'm understanding the requirement correctly. Let me see what I can do.

In case it helps, here's the "high level" of why I'm trying to use statiq in the way that I am:
I was trying to decide where to keep assets (images, page specific css/js, etc) in the filesystem. So, rather than having:
input\blog\post1.md
input\blog\post2.md
input\images\post1-screenshot.png

I prefer to use
input\blog\post1\index.md
input\blog\post1\screenshot.png
input\blog\post2\index.md

This way "everything" related to a single post is in a single directory.
Now when linking images, unless I use the absolute URL, the image urls are relative. Therefore, it really matters if the web server ends up using a trailing slash or not, as a relative URL for either of these scenarios doesn't work for the other (trailing slash or not). For example, <img src="screenshot.png /> isn't going to work if the web server returns /index.html, rather than HTTP redirect, when the browser URL doesn't contain the trailing slash.
Finally, as mentioned in the edit of my original post, web crawlers don't appear to be super happy with web pages where the canonical URL redirects to another URL. Fortunately, it doesn't seem to cause problems, but it does spam the warning list, making it harder to find other warnings.
FWIW, I tried reconfiguring my web server to stop redirecting to a trailing slash, but that made image relative urls less nice, so I decided I like the trailing slash.

Thanks for the additional details. This is turning out to be a little more challenging than I thought at first.
At issue is that the LinkGenerator takes a NormalizedPath, and NormalizedPath is designed to strip off trailing slashes before we even get to the link generation. This mostly makes sense given that a "path" wouldn't normally have a trailing slash, but URLs are a special thing. It's also not entirely relevant for preserving/adding a trailing slash when hiding known files like index.html, but is important for a holistic approach to trailing slashes in the link generator. I think this has revealed a bigger problem in that Statiq just doesn't like trailing slashes at all in the link generator. That's an issue since trailing slashes are definitely a thing in URLs and should be supported.
Not quite sure how I'm going to resolve it yet, though it'll probably be fairly low-level. I might end up having the link generator take a string for the path instead of a NormalizedPath - that probably makes the most sense given that a "path" in a URL is not the same as a file system style path that NormalizedPath is intended to represent. Just thinking out loud at this point...

This is now done and will ship with the next release. It's exposed as a global setting via Keys.LinkHiddenPageTrailingSlash and through GetLink() as a parameter and LinkGeneratorShortcode as a shortcode argument.