Improve helpers support in the template kind (include handlebars lowercase filter)

Feature Suggestion
Improve helpers support in the template handlebars engine.
Possible Implementation
In your TaskWorker file, add another handlebars helper:
this.handlebars.registerHelper('lcase', value => value.toLowerCase());
and/or
this.handlebars.registerHelper('lcasetrim', value => value.trim().toLowerCase());
This might be only during a transition period until you fully migrate to nunjucks and seems like the most simple, fast, and a proper solution without the need for workarounds.
The trimmed version is also important. In most cases, besides changing the case, we need to trim the value.
Context
I have a situation where my template skeleton has a dynamic filenames based on the user input. For example:
${{values.myFileName}}.yaml
This works nicely and the file is created correctly, with the correct filename. However, the problem is that I want to control the case of the filename. To be exact, I want to have it lowercased.
From the template, where we have handlebars engine, I have a limited number of helpers to use therefore I cannot pass down the value in a case-controlled way like this {{lcase parameters.myFileName}}.
Also, something like this ${{values.myFileName | lower}}.yaml for the filenames does not work for me. A filename like that is not supported.

Couldn't you just enforce the value to be lowercase from the front-end using the built-in TextValuePicker that has this validation in place?
https://github.com/backstage/backstage/blob/8796e812e6c90583be07ee859f87721f2259d93d/packages/app/src/components/scaffolder/customScaffolderExtensions.tsx#L29

Hi @regicsolutions
That is a custom extension that we do not have out of the box. By default, TextValuePicker has no extensions and validations if I'm not mistaken.
Another thing, the value I'm sending from the UI is the entity name that is being used in the YAML files metadata, therefore it must pass the entity name validation as well, meaning that I must use the built-in EntityNamePicker field which does not validate the casing.
What I see as a solution is a custom field or field extension (similar to the one you pointed in your comment) which will control the case and validate the entity name at the same time or a simpler one that I suggested above with addition to the handlebars helpers registrations.
To me, it seems like overkill to create a custom field for this.

@ProticM so we're currently working on deprecating the handlebars templating syntax from the Template kind, and aligning them with the nunjucks templating engine in the Actions. There's more info in this ticket here: #7268. Does it work for you to wait for the backstage.io/v1beta3 templates to be rolled out as you'll be allowed to use ${{ parameters.blah | lower }} there?

Rather than us adding more features to something that's going to become the legacy way pretty soon? 👍

Hi @benjdlambert I'm aware of the transition process, and I think it is good that you aim to unify templating engine and provide the same workflow in template kinds and skeletons :thumbsup:
I guess I can wait and implement a workaround :clock1: How long do you think it would take to update the templates?
In my opinion how to handle this, if it is going to be one month, and you aim to release a new version in the next couple of days, then it would be nice and worth including the handlebars helper to manage the transition period. Correct me if I'm wrong, but I don't think it is too much of a problem and a huge deal to add it, and also it would be easier to migrate to the new nunjucks syntax afterward (no need to delete the custom fields/extensions that were created for this use case previously). On the other hand, if the transition is going to be completed sooner, then there is no need to add it and we can focus on the nunjucks syntax and filters :thumbsup:
Also, not sure how many people are encountering this scenario and thus not sure whether this requirement is that highly needed to be taken into count that seriously.

@benjdlambert I agree with the idea of promoting the package update rather than staying behind, and it should be like that 👍
Yes, the migration from one template to another should be pretty easy and this was my point in the previous comment. I would prefer template migration instead of clearing out the custom fields that are needed to handle this scenario at the moment.
Thank you for the update 👍 I will watch for the changes here 👀

We can close this one since there is a new API version implemented


Implement API V2

For the Auth System V2 project.
Umbrella task for implementing v2 of the hs_auth API based on the following specification: https://documenter.getpostman.com/view/2489646/T1DjjKP6?version=latest
Children tasks:

[x] #82
[x] #83
[x] #84
[x] #85
[x] #86
[x] #87
[x] #88
[x] #89
[x] #110
[x] #117
[x] #118

Definition of done:

Approved and merged PRs implementing all operations for v2 of the API as described in the specification.

Is this done now? 😯

Seems like it 😃


Invalid mbtiles

Vector source must include "vector_layers" key

Fixed in https://github.com/mapbox/mbtiles-extracts/pull/3


Demonstrate GUIs vs CLIs for data science

Example of a GUI workflow - sort a column:

Example of the same process in a CLI:

And in the tidyverse:


DL-37: add an offset sequencer for generating transaction id

add an offset sequencer for generating transaction id.

I am not sure if we should support this. I had the same feeling with @leighst - I don't think we can find a reliable to use transaction id for offset.
I am actually thinking in a different solution - we already have the length field for each entry appended to bookkeeper ledger. we probably can just expose this length field to the log segment metadata (like what we did for sequence id). so those length field can be used as the offset for batch of records (aka entries). does that meet your requirement, @khurrumnasimm ? /cc @leighst

@sijie @leighst  thank you so much for your comments. I agreed with you after trying a while, it turns out is a bit hard to get an offset generator correctly on write proxy. I will fall back to use sequence id for my use case now. I will close the pull request and create a jira to expose offset.


Feature/helmet react dev tools

This pull request adds react-helmet and following react dev tools:

React-render-visualizer
React Perf Tool
Why did you Update(Plugin i.e ReactDevToolsPlugin)

This is not on lerna structure

@umairfarooq44  in future lets focus on adding independent pull requests for each plugin/task/enhancement/bug fix

Each plugin should've had its own package. Putting everything in the same place to not only discouraged but not allowed in official packages. This just defeats the whole purpose of this project.


fix: Remove Response[] from docstring of non-detailed functions

We only get Response objects from the *_detailed() functions.

Thank you!


Panorama view from bench (suggestion)

This is a bit of a stretch, but a panorama view from the bench might make a nice virtually being there experience. As someone who has browsed online cemetery photos curiously looking for headstones of ancestors abroad, I think this could be a nice feature.

This should now work.

Panorama https://openbenches.org/bench/879
Photosphere https://openbenches.org/bench/868

Looks good.


Custom feed path setting

Many sites already have feeds setup at a path other than feed.xml. If their host e.g., GitHub pages, doesn’t allow for redirects, changing to a new feed path isn’t really an option.
This PR adds a _config.yml option of feed_path, which defaults to feed.xml but can be set to a custom path like atom.xml.

Thanks for the pull request @orderedlist. Small doc suggestion, and small security fix, otherwise, this :eyes: good.

:)

This is broken on 3.0, is this going to be fixed because we have a lot of users on 3.0 and this is a defacto-plugin since it sits under the Jekyll umbrella.

This is broken on 3.0

Can you explain what you mean by that?

@benbalter https://travis-ci.org/jekyll/jekyll-feed/jobs/65270484

Actually, this failing test confuses me based on the way it's failing, I'm going to patch a local version and drop myself into a debugger and check out the state machine across all Jekyll versions because logically if it failed on one it should fail on all no?

I finally had a second to look at the tests to figure out what was going on and it turns out that the site wasn't regenerating on Jekyll 3 so it wasn't picking up what @orderedlist wanted but I also had to make another small change to the source to get the test to pass:
    let(:config) do
      Jekyll.configuration(Jekyll::Utils.deep_merge_hashes(
        overrides, {
          "feed" => {
            "path" => "atom.xml"
          }
        }
      ))
    end

That way the new config would pick up the original overrides with regeneration.

I think I've addressed all the feedback. :space_invader:

Is there any issue with adding an unsanitized, potentially relative or synmlink path to keep files? @parkr?

The path is sanitized later, I thought?

The path is sanitized later, I thought?

keep_files can already accept arbitrary input via _config.yml, so there's no additional risk of arbitrary input here.
@orderedlist thanks for submitting the PR and for working through the feedback. WIll try to get a new release out so you can test it out in the wild. :smile_cat:

:heart:

@orderedlist that gif tho. :joy:
:+1:


Composition breaks when composing on a segmented node

Notice how composition never trigger for the first character until it's converted to a plain text node
https://github.com/facebook/lexical/assets/193447/b3f3c3f1-98bc-4823-b1fe-ede7d47fa35e

My hunch is that the span can never go away (replaced), we have to reuse the same DOM element


Fix operator-sdk generate openapi

What does this PR do?
Commit 7a3d45c somehow (?) causes the operator-sdk generate openapi command to fail with a nondescriptive error message. On @davidfestal's suggestion, this PR removes file deploy/crds/workspace.che.eclipse.org_devfilespecs_crd.yaml, which seems to be in the repo erroneously, and re-runs the operator-sdk generate commands.
Is it tested? How?
Tested on minishift v1.34.2+83ebaab
Fixes https://github.com/eclipse/che/issues/16120

I use operator-sdk v0.14.0 and it works for me, we need:

describe in README.md that operator-sdk v0.12.0 must be use
OR
prepare dockerimage with needed operator-sdk version and use it for code generating (probably as a separate issue, later)

@sleshchenko Part of the problem is that I'm unclear on how the operator-sdk generate commands work:

It works for me with v0.14 and v0.15, but not v0.13 (or v0.12).
generate openapi is deprecated in favor of generate crds and using openapi-gen standalone starting in v0.13
The upgrade instructions for operator-sdk include a step to regenerate crds in their update guide, which suggests that different versions of the sdk are not necessarily compatible (otherwise regenerating CRDs wouldn't be strictly necessary).

@amisevsk @sleshchenko I would suggest that for now we would merge this PR to have generation working from the v0.12.0 SDK release and upper, but after manually fixing the type: object line pointed by @sleshchenko in comment https://github.com/che-incubator/che-workspace-operator/pull/21#discussion_r383702900, to avoid introducing an incompatibility with OpenShift 3.11.
And later on you would be able to do something similar to what I did in the devworkspace-api with the docker-run.sh to ensure a consistent and given operator-sdk version is used.
As for upgrading to the last operator sdk release, and using the new generate crds and openapi-gen tools, I think it should be done, but probably:

in a distinct issue
synchronously with the same changs in the devworkspace-api repo
while checking whether it somehow breaks compatibility with Openshift 3.11 (ie Minishift), in which case the fixing any breaking change in generated files should be done in the script proposed here


SA1629 code fix sometimes inserts periods just before last character

SA1629 will flag docs such as these as needing to end with a period:
        /// <typeparam name="S">The service interface to retrieve</typeparam>
        /// <param name="provider">The IServiceProvider implementation</param>
        /// <returns>A reference to the service</returns>

The (bulk) code fix provider produced this:
        /// <typeparam name="S">The service interface to retriev.e</typeparam>
        /// <param name="provider">The IServiceProvider implementation.</param>
        /// <returns>A reference to the servic.e</returns>

Note this doesn't always repro. When I undo just a few lines to their period-less state and reapply the code fix, the period goes to the right place. It only happens when there are a massive number (possibly hundreds) of fixes applied in bulk.

It can happen when the closing tag isn't on the same line as well:
        /// <summary>
        /// Returns the current VS font from the provide.r
        /// </summary>

Hmm... in this one it showed up two characters too soon:
        /// <summary>
        /// Gets a value indicating whether the "Save and Generate CMake Cache" feature is user availab.le
        /// </summary>

Wow. In one particularly short file (only 84 lines long), it put the period way too far to the left:
        /// <summary>
        /// Listens for global ev.ents from Visual Studio including font change events
        /// </summary>

It had screwed up at one point above as well, which had particularly unusual comments. I wonder if that can give an idea of what kind of xml parsing might be incrementally throwing off the code fixer.

Thanks for the report. This looks like an interesting one to find and fix 😉

It's not always before the last letter either. It can be before the last xml tag too:

In fact it can be in the middle of a paragraph!

@AArnott In the last image (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2957#issuecomment-657241850), the code fix is correct. The <code> element designates a new paragraph. The equivalent inline element is <c>.

I tried reproducing this in a large test case, using Visual Studios "Run until failure", both in a Debug and Release build. No luck so far.
@AArnott You say that this only happen when batch fixing. Have you seen it happen when fixing all in one document, or only when fixing all in a project or the entire solution?
And since it is a couple of years old: It is still happening?

I haven't noticed the behavior lately, but I only rarely have occasion to run the bulk fixer for this rule.

@AArnott Ok. Do you remember anything about which scope you have selected when you have had this behavior before?

Most likely Solution. And probably in a repo with hundreds of violations.

Alright. Thanks for the input!

@bjornhellander I'm guessing this one is due in some way to the use of CustomFixAllProviders.BatchFixer. Adding a custom fix all provider would likely resolve the issue.

Yes, I suspect the batch fixer too, although I can't see why it would behave like this. I have noticed that Roslyn's built-in batch fixer has undergone some pretty big changes since you copied and improved it. How would you feel about trying out that one again for later Roslyn versions, to avoid a custom fixer?

How would you feel about trying out that one again for later Roslyn versions, to avoid a custom fixer?

The custom fixer is always tremendously better for performance. We only include a batch fixer for cases where we haven't implemented a proper fixer yet.


Fix various typos in README.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Upgrade Gradle to v6

Summary
Dependency to upgrade: Gradle
Target version: 6.x or later
Reason: no specific
Additional information
The gradle-node-plugin depdendency also requires attention after this upgrade, because it breaks as soon as Gradle is upgraded to version 6+.
Relevant issue: https://github.com/srs/gradle-node-plugin/issues/351
Relevant depedency which seems to be a drop-in replacement for the old dependency probably fixing the gradle-node-plugin issue: https://github.com/node-gradle/gradle-node-plugin
Change log
https://docs.gradle.org/6.0/release-notes.html
Acceptance criteria

[ ] The dependency has been upgraded.

We're dropping Gradle from room-display, so we can close this ticket.


[Feature]  in appfile struct trait order was missing

In AppFile, we use a golang map to store all traits along with workload properties.
services:
  express-server:
    # this image will be used in both build and deploy config
    image: oamdev/testapp:v1

    route:
      domain: example.com
      http: # match the longest prefix
        "/": 8080

    scale:
      replica: 2

In OAM AppConfig, we use array like:
kind: applicationconfiguration
spec:
  components:
  - componentName: express-server
     traits:
     - type: route
       properties:
         domain: example.com
         http: # match the longest prefix
              "/": 8080
     - type:    scale
       properties:
        replica: 2

So we lose trait order which could be defined in AppConfig.

Let's move this fix after KubeCon NA.

I have added trait order in the Application Object, any platform that rely on trait order can integrate with Application Object.

I have added trait order in the Application Object, any platform that rely on trait order can integrate with Application Object.


First release to production

Added index.html template

I don't no what to discuss, so I added it just to pass the test.


Namespace aware handling in default WMS request/response interceptor (1.0.x-master)

This fixes the interception of WMS requests and responses in context of the CUSTOM_ENDPOINT handling to become more namespace aware:

Append xlink namespace to element attribute (otherwise clients like QGIS couldn't parse the GetCapabilities response).
Append the layer's namespace to layername if needed (otherwise we couldn't detect the corresponding GeoServer base URL in subsequent WMS requests as clients like QGIS will make use of the name to generate these requests).
Add @Transactional annotation to enforce a new JTA transaction if called outside of a transaction context.

Please review @terrestris/devs.

LGTM, please merge


Other fields are ignored when fullname is missing in board/settings.json

Probably solved it in 5794ac3d4cf5d630ebfcc11b44543bbe7187f7f4


create extra directory for each exam template under assignment (for split_pdf) & assign_error to be a member route of exam templates

When we click the number of QR scan errors, we can fix the pages for corresponding exam template.

working on it

@jenachoi I merged this in, but the title of the warning icon should be internationalized.


Limit description by words instead of letters

The description for the courses in the website is reduced by letters which is leading the words incomplete, this could lead several problems.
I would suggest in main.js at line 45
${course.description.substring(1,100)}

this code be changed with something like this
${course.description.split(" ").slice(1, 25).join(" ")}..

Hey @TanishqSingla , Thanks for taking out the time to create this issue.
I used that substring method, to limit the amount of text displayed in an individual card. With the proposed changes, there'd be several inconsistencies in the Card Size.
Let's consider two examples, in first one, if the contributor is using words lenghty words like 'supercalifragilisticexpialidocious', or just forgot to add a space between two adjacent words, it'll be counted as just one word and that could lead to overflows in the text limit.
In second scenario, This proposed solution, might fail if the contributor adds adjectives or supportive words, as words such as 'for', 'of', 'and', 'or' will also be treated as a single word and that might would cause underflow of text in the card.
Henceforth, I think this is a solution to a problem that does not exist yet. If you disagree with what I've said and would like to add something important, feel free to add a comment and reopen this issue, I'd love to discuss :) . But for now, I'm closing this issue. Thank you for your contribution.
Happy Hacking! 🎊


[ACM-12676] Added renovate config for konflux

Description
Adding .github/renovate.json to expand configuration of konflux pull requests.
Related Issue
https://issues.redhat.com/browse/ACM-12676
Changes Made
Added .github/renovate.json to begin maintain konflux pull requests easier.
Screenshots (if applicable)
Add screenshots or GIFs that demonstrate the changes visually, if relevant.
Checklist

[ ] I have tested the changes locally and they are functioning as expected.
[ ] I have updated the documentation (if necessary) to reflect the changes.
[ ] I have added/updated relevant unit tests (if applicable).
[ ] I have ensured that my code follows the project's coding standards.
[ ] I have checked for any potential security issues and addressed them.
[ ] I have added necessary comments to the code, especially in complex or unclear sections.
[ ] I have rebased my branch on top of the latest main/master branch.

Additional Notes
Add any additional notes, context, or information that might be helpful for reviewers.
Reviewers
Tag the appropriate reviewers who should review this pull request. To add reviewers, please add the following line: /cc @reviewer1 @reviewer2
/cc @cameronmwall @ngraham20
Definition of Done

[ ] Code is reviewed.
[ ] Code is tested.
[ ] Documentation is updated.
[ ] All checks and tests pass.
[ ] Approved by at least one reviewer.
[ ] Merged into the main/master branch.

/cherry-pick backplane-2.5

/cherry-pick backplane-2.6

/cherry-pick backplane-2.5


New Release?

Can we have a new release for the ScriptHookVDotNet? A lot of changes has been made since 0.9 which was 27 days ago.

Some 1.0 features are still missing as far as i know. Which is why no 1.0 release has been made.

Would it be possible to have a 0.91 or something similar? Would be nice to be able to link a mod user to the release page for downloading a recent version.
Also, which features is a 1.0 release missing?

@logicspawn https://github.com/crosire/scripthookvdotnet/milestones

I second this request. There is no reason why there couldn't be a version 0.10. I just read through semver.org again and I couldn't find anything against it.

Plans for 1.0 AFAIK:

Clean-up code and maybe rewrite some stuff
Implementing a lot of common and needed features (listed in the 1.0 milestone issues)

But another release before we go 1.0 would be good IMO, we implemented already a lot till the last one. @crosire

True. I'll wrap things up in a moment.

The problem is that semver requires minor releases to not make breaking changes. But the current codebase is not compatible to the previous version at all!

The thing is that people are downloading nightly builds from AppVeyor and they get confused when .NET mods don't work. Releasing a 0.91 version would be more than great, even though it doesn't meet the semver criteria.

The next logical minor version increment would be 0.10, not 0.91. Just saying to prevent confusion.

Maybe release current version as 1.0 and make milestone 1.1?

Suggestion: Rename the current milestone to 2.0 and release V1.0 already.

Released v1.0, new build is automatically pushed to the release page in a few minutes.

@crosire you should not give up so easily :laughing:

It really was time for a new release, last one was way too old. And I had planned to push it this weekend anyway =).

Hey, what about #191 ? Is it in the new release?


feature(environment): support string

We can run on all kinds of environment, hence Environment should just be a wrapper around string. However, for backwards compatibility with <=0.6.x we need to support certain formats: Docker, Umbrel, RaspiBlitz, Unknown. For all other we format the string to lowercase.
Resolves #3008
Resolves #2969
Let me know what you think.

bors r+


change the role path for auto heal docker high usage

change the role path for auto heal docker high usage

:+1:


Implement configurable html report dir

It is okey to couple the gemini configuration with the html reporter?
Anyhow I think it'd be a big plus if there would be a way to configure where the the html reports are written.

Coverage decreased (-0.9%) to 74.778% when pulling 91ea03bfc93e136f74b41078cf65a99602e5f834 on nordstrand:master into c58cd763d0597ed16c903b5f7fd500ecd3cf31ee on gemini-testing:master.

Coverage decreased (-0.9%) to 74.778% when pulling 236abb1efe31aff707ec26c6a6181ba1c0ebd67d on nordstrand:master into c58cd763d0597ed16c903b5f7fd500ecd3cf31ee on gemini-testing:master.

Coverage decreased (-0.9%) to 74.778% when pulling 98efee12fbec706d0a2a881f8ee4bfc65e147369 on nordstrand:master into 142cb1beea2027beb929b03d04df4fe7a56d0758 on gemini-testing:master.

html-reporter has been moved to separate plugin - https://github.com/gemini-testing/html-reporter
You can use this plugin to redefine report directory


CI: Jenkins modularization

Since we are not using the declarative syntax, we should use the scripted to its fullest potential.
This PR aims to improve the overall structure/readability of the Jenkins pipeline.

Following code was repeated inside Jenkinsfile and Jenkinsfile.release

node_info()
wait_for_db()
build backend/frontend
deployment looks very similar, could be extracted

Small improvements:

A couple of missing node_infos() were added.

There is still a lot to be done, like extract the deployment stages into a single function and get them into the mainWrapper.
At the end(except .release) everything can probably be just reduced to docker runs
closes #647
Basics

[x] I added a line to /doc/CHANGELOG.md
[x] The PR is rebased with current master.

[x] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed all affected decisions
[ ] I added unit tests for my code
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
(exceptions are documented)
[ ] Code is consistent to our Design Decisions

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Examples are well chosen and understandable

Jenkins build please

very nice! The next hour or so is the user study, afterwards we can try to merge+build the release pipeline

It was fun trying this out, but I dont think the gain at this point is worth the investment. The main issue is that we also need some flexibility and extracting something like a util function runInDocker works for most stages, but its a bit more complicated for the frontend stage, which is not really split up yet.
This might be something more interesting in the later future, for now the code is maybe a bit chaotic but it could be way worse.


No Suitable Appstore Was Found (Amazon), Unity3D plugin

Hi! First of all thanks for your plugin! I'm trying to implement it for amazon. Getting this error:
The error is:
Problem setting up in-app billing: IabResult: 3, No suitable appstore was found (response: 3:Billing Unavailable)
my steps:
did the stuff here:
https://github.com/onepf/OpenIAB/wiki/How-To-support-Amazon-Appstore
(except pro guard since I don't use that, also didn't map SKU's)
            if (Button("Initialize OpenIAB"))
	{
		var options = new Options();
		options.checkInventoryTimeoutMs = Options.INVENTORY_CHECK_TIMEOUT_MS * 2;
		options.discoveryTimeoutMs = Options.DISCOVER_TIMEOUT_MS * 2;
		options.checkInventory = false;
		options.verifyMode = OptionsVerifyMode.VERIFY_SKIP;

		options.availableStoreNames = new string[] { OpenIAB_Android.STORE_AMAZON };
		options.prefferedStoreNames = new string[] { OpenIAB_Android.STORE_AMAZON };
		options.storeSearchStrategy = SearchStrategy.INSTALLER;

		// Transmit options and start the service
		OpenIAB.init(options);
	}

my device: Pipo M6 pro, android 4.2.2,
I'm using Unity3D 4.6.3 and OpenIAB <IP_ADDRESS>
I downloaded the amazon tester environment, placed the JSON in my sd card's root, installed using adb, but am still getting the same error.
thanks in advance!

similar to #482


Add SortDateCommand

Describe your changes
Add the ability for the user to sort by the contract end date
Issue ticket number and link
closes #127
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

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

Files with missing lines
Coverage Δ
Complexity Δ

.../seedu/address/logic/commands/SortDateCommand.java
100.00% <100.00%> (ø)
2.00 <2.00> (?)

.../seedu/address/logic/parser/SortCommandParser.java
90.90% <100.00%> (+2.02%)
5.00 <0.00> (+1.00)

...va/seedu/address/model/person/ContractEndDate.java
100.00% <100.00%> (ø)
7.00 <1.00> (ø)

...edu/address/model/person/PersonDateComparator.java
100.00% <100.00%> (ø)
2.00 <2.00> (?)

... and 10 files with indirect coverage changes


Enable optional minimal SteamAPI integration for usage time tracking (editor only).

Disabled by default, can be enabled with (steamapi=yes build option), ~steam_appid.txt~ (it's only needed when running executable outside of Steam download) and steam_api library from the SDK should be added to distribution for this feature to work.
It initializes Steam API to inform Steam that Godot editor is running, but not using it in any way.
Fixes #18233
Reopened https://github.com/godotengine/godot/pull/56727, GitHub seems to completely ignore force pushes to the branches with "invalid characters", so it was impossible to update original PR.

I haven't followed the original discussion closely, but this would mean that for the official distribution we'd need to compile Linux, macOS, and Windows builds twice with and without this flag?

I haven't followed the original discussion closely, but this would mean that for the official distribution we'd need to compile Linux, macOS, and Windows builds twice with and without this flag?

The Steam library is loaded dynamically, so a single build with flag will work fine without Steam. But I guess we do not want official non-Steam builds to have the ability to automatically load proprietary code, so probably yes.

I finally took the time to test this, and I'm having issues initializing the steam_api64.dll library on Windows, from latest Steamwork SDK 1.59:
 ERROR: Can't resolve symbol SteamAPI_Init, error: "Error.
   at: (platform\windows\os_windows.cpp:497)

Seems like it's SteamAPI_InitEx in the newer Steamworks SDKs (SteamAPI_Init is defined as a wrapper in the header only).

Indeed, I tested with SteamAPI_InitEx as you mentioned first, but that also didn't work.
With SteamAPI_InitFlat (added in 1.59 which I'm using), it seems to work fine.
So I could test that when running it through Steam, this fixes the time tracking issue.
On the other hand, successfully init'ing the Steam API seems to prevent running the binary from the command line:
PS C:\Program Files (x86)\Steam\steamapps\common\Godot Engine> .\godot.windows.opt.tools.64.exe --verbose
PS C:\Program Files (x86)\Steam\steamapps\common\Godot Engine> Loaded SteamAPI library
ERROR: Parameter "mem" is null.
   at: Memory::realloc_static (core\os\memory.cpp:130)
ERROR: Parameter "mem" is null.
   at: Memory::realloc_static (core\os\memory.cpp:130)

(no window shows up)
Is that something we could address somehow so we get the benefit when in Steam, but not the drawbacks otherwise?
Maybe there's an env variable set by Steam which we can check to know whether to bother init'ing the Steam API in the first place?

Updated, but have not tested, will do it tomorrow.

I can't reproduce it. This might be memory corruption, since new function require fixed size string buffer, if you replaced only the function name it might write over some other data.

Yeah I had just replaced the function name so that's probably why.
I'll test the new version asap.

Thanks!


webpack-dev-server could not start

Steps to Reproduce

Just created a new full screen control project.
Tried to do some more research on my own, and I came up with these two links if it's any help:

https://github.com/webpack/webpack/issues/8082
https://github.com/webpack/webpack-cli/issues/607#issuecomment-424389911

I can confirm that updating my webpack-cli version to 3.1.1  fixes this issue
Error
F:\MixerCustomControls\destiny-overlay\node_modules\webpack-cli\bin\config-yargs.js:89
describe: optionsSchema.definitions.output.properties.path.description,
^
TypeError: Cannot read property 'pro...
Editor Details
Version: 1.0.2
Mixer User ID: 59192097

Encrypted Editor State: {"id":"4a83bda37f27fe99","password":"FCBcdiJleOutSHItyvGiP2agvml1biqKe6m5PmFqLAA="}

Thanks for opening an issue, and sorry for the delayed response! It looks like a breaking change was made on a minor version in webpack (https://github.com/webpack/webpack/issues/8082) which caused the quick start templates to fail. You can either:

Re-create your project using the "new project" wizard -- we've updated the starter templates.
Update the version manually in an existing project:

Edit your package.json. Replace the line containing "webpack-cli": with "webpack-cli": "^3.1.2",
Either delete the node_modules folder in your project, or run npm install
Restart the CDK if it's open.

Please let us know if you run into any more problems 🙂


PHP formatting on typing

Type: Bug
When I type HTML code in a PHP file, the closing tags are always moved to the first column, deleting and indentation tabs in front of them. Even if it's wrong and this wouldn't happen in an HTML document. I have no PHP-related extensions installed. Disabling the editor.formatOnType feature for PHP files does not resolve the issue. I assume the core editor has a broken behaviour that needs to be fixed or removed.
Steps to reproduce:

Open a .php file
In an HTML section (not in PHP code) within an element, indented by tabs, type this:
 (newline)

Expected result (example):

Actual result (example):

VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8 x 3400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.71GB (5.85GB free)

Process Argv
--crash-reporter-id 1b00a758-578c-4b77-a258-fe145c18e004

Screen Reader
no

VM
31%

Extensions (24)

Extension
Author (truncated)
Version

vscode-solution-explorer
fer
0.7.5

vscode-todo-highlight
jgc
2.0.4

ecdc
mit
1.8.0

vscode-language-pack-de
MS-
1.74.12140926

csharp
ms-
1.25.2

vscode-dotnet-runtime
ms-
1.6.0

isort
ms-
2022.8.0

python
ms-
2022.20.1

vscode-pylance
ms-
2023.1.10

jupyter
ms-
2022.11.1003412109

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.12

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-ssh
ms-
0.94.0

remote-ssh-edit
ms-
0.84.0

cpptools
ms-
1.13.9

remote-explorer
ms-
0.0.3

vscode-nuget-gallery
pat
0.0.24

platformio-ide
pla
2.5.5

better-pageup-pagedown
rus
0.0.1

jinjahtml
sam
0.19.0

trailing-spaces
sha
0.4.1

cursorCharCode
zei
0.2.2

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1cf:30587006
2e4cg342:30602488
3d0df643:30613357
89544117:30613380
fim-prod:30623723

As a workaround, you can set editor.autoIndent to anything less than "Full"

Here the .php file is inheriting html's indentationRules, and the decreaseIndentPattern is apparently being applied twice. @alexdima I was debugging a bit, and I think this could be an issue with how decreaseIndentPattern is applied for inherited rules?

Here, we look up indentRulesSupport for the language from the ScopedLineTokens https://github.com/microsoft/vscode/blob/70c45ba0297f1ce516eafbc56d679a4a2c5a17e7/src/vs/editor/common/languages/autoIndent.ts#L411, that is html which is correct.
But here when we figure out the inherited indentation from the previous line, we look it up using the model's language https://github.com/microsoft/vscode/blob/70c45ba0297f1ce516eafbc56d679a4a2c5a17e7/src/vs/editor/common/languages/autoIndent.ts#L84 which is php, which is not correct. So then it thinks that this line was not indented so the current line gets deindented beyond the previous line.
Not sure what the fix is, maybe computing a ScopedLineTokens for the previous line as well

So it looks like advanced is the next smaller level. Setting the option to that removes all automatic indentation from HTML in PHP files. Now I'm back (down and also up) to the level that Notepad++ provides.
I also had to set this for HTML files because it also has undesired side effects. Pasting a multi-line element that needs to go on another indentation level would have indented it correctly, but mis-indented the closing tag below the pasted lines. I never meant to edit that line, yet it was touched to the worse.
Is it possible at all that VSCode could properly indent HTML (in HTML or PHP files)? Do I have to install any extensions to make it work or would it be supposed to work out of the box?


Input of Time2Vec embed

I have a question that bothers me a lot recently - it appears to me like some people on the web get time2vec concept wrong. What you described in the article is correct from my point of view, but the implementation is incorrect, at least for NY-TX dataset.
As I understand, time2vec is used to create an embedding of time. Thus, the input of time2vec layer should be some time information, like day number since beginning of data, timestep, year etc. To support my claim, the excerpt from time2vec paper:

To answer Q3, we trained a model on our synthesized dataset where the input integer (day) is used as
the time for Time2Vec

I've run your model with ny-tx dataset and from what I see the input of time2vec is just the RAW temperature data, which doesn't contain any time-related information.
I will be grateful if you dispel my doubts, maybe I misunderstand sth.  And, thank you for a great article :)

After further analysis I find out that what I thought was an input tensor (x) was in fact tensor of date features (year, month, day etc.), so everything is clear now. Sorry for disturbing.


Provide constructors for ClientRequest from lists of configurations

While we provided a way to construct KeyConfigs from list, we didn't plumb that up into ClientRequests. This plugs that gap.

@martinthomson I think this change (or something like it) is necessary so client implementations can fetch a configuration list and then just pass it directly to the library to create an OHTTP request. I'm open to alternatives, but this seemed like the most straightforward approach to deal with it.

Will do!

And so ends my flight with clippy. @martinthomson, this should be good to go, unless you were looking for a different sort of test.


How set up preprocessor definitions.

Hello mr Graeme Hill. Thank you for good library. It will be good to point in readme how set preprocessors flags in some ide like visual studio 2012 -> project properties->Configuration properties-> C/C++ -> Preprocessor -> Preprocessor Definitions (type you platform defenition(GUID_LIBUUID, GUID_CFUUID, GUID_WINDOWS, GUID_ANDROID )  ). Best regards.

You don't need to do it manually anymore because the project uses cmake. Regarding information on how to setup preprocessor flags in general, I think google and SO are going to be better at answering that anyways because it is not specific to this project.


Update consume-apis.md

fix link to QueryInterface

@asklar : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Allow Hugging Face models to be loaded with bf16

This would significantly increase inference speed.
The main issue is figuring out where this configuration (and model configuration in general) would live. We could use a flag or environment variable for now, but ideally we should have a universal config file that takes care of other kinds of configuration (e.g. implementation type, host URL, etc.) Ideally we do this at the same time as the model architecture refactor.

Nothing that this was suggested by Chenhui Zhang (working with Bo Li).

Fixed by #1912.


Alpine support dropeed?

Description of problem
docker-image-labeler cannot be run in an Alpine container anymore. Has the support been dropped?
Version 0.6.1 worked as expected.
Steps to reproduce
# start container
docker run --rm -it --platform linux/amd64 alpine:3.20 /bin/sh

# install wget and download binary
apk add wget
wget https://github.com/dokku/docker-image-labeler/releases/download/v0.7.1/docker-image-labeler-linux-amd64

# make it executable
chmod a+x docker-image-labeler-linux-amd64

# run command
./docker-image-labeler-linux-amd64 --version
/bin/sh: ./docker-image-labeler-linux-amd64: not found

docker-image-labeler version
not working
v0.7.1
v0.7.0
working
v0.6.1
v0.5.0
Output of failing command
/bin/sh: ./docker-image-labeler-linux-amd64: not found

Not sure why this is failing for you, but running that on my system works fine. I had to install gcompat though.
For the glibc/gcompat issue, maybe something here (which builds the binaries for the release) doesn't match something here (which was the old release code)?

Thanks for pointing it out. Installing gcompat fixed my problem.


Dell XPS 9310 bluetooth issue on Linux 5.15.3

  boot.kernelPackages = lib.mkIf (lib.versionOlder pkgs.linux.version "5.12") (lib.mkDefault pkgs.linuxPackages_latest);
  boot.kernelPatches = [{
    name = "enable-qca6390-bluetooth";
    patch = null;
    extraConfig = ''
      BT_QCA m
      BT_HCIUART m
      BT_HCIUART_QCA y
      BT_HCIUART_SERDEV y
      SERIAL_DEV_BUS y
      SERIAL_DEV_CTRL_TTYPORT y
    '';
  }];

Updating to Linux 5.15.3 loses bluetooth adapter. bluetoothctl shows no default controller available
Rollback to 5.15.0 fixes the problem
I can debug and provide additional info, just tell me what to do
@mitchmindtree

@hissssst hmmm I just updated to 5.15.4 last night and all seems to be working well. Perhaps it was just that patch release?
Could you share which nix-channel you are on? E.g. the output of sudo nix-channel --list? I wonder if maybe you've picked up NixOS/nixpkgs#144409 and nixos doesn't like that the config is both in nixpkgs and nixos-hardware... though I would imagine these would all get merged anyway. If updating to 5.15.4 doesn't work, you could potentially try using #341 and changing your nixos channel to that branch as I mention in the PR?

I am on nixos https://nixos.org/channels/nixos-unstable
Let me try 5.15.4

@mitchmindtree , yeah 5.15.4 works as intended


Application Insights and Blazor Server

can we get some details on using application insights with blazor server  on an azure web app ?
i have been searching for more information and can not find any good guides for blazor server

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

ID: c8795bcc-45ef-7edc-4657-fca867c8ff81
Version Independent ID: d0b1a040-5dae-8233-dbee-c5837a0c231d
Content: ASP.NET Core Blazor logging
Content Source: aspnetcore/blazor/fundamentals/logging.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @DennyFiguerres ... Your request should go to the Azure doc authors who write on it for the App Insight docs here ...
https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview?tabs=net
Given that server-side Blazor (as either Blazor Server of <8.0 or Blazor Web App of >=8.0) is just an ASP.NET Core app, we default to the main doc set coverage. It's minimal, but that's all that the product unit here wants to cover ...
https://learn.microsoft.com/en-us/aspnet/core/performance/diagnostic-tools?view=aspnetcore-7.0#application-insights
If you want to request special Blazor coverage from the Azure doc authors ask them if they'll consider it by opening an issue on their repo ...
https://github.com/MicrosoftDocs/azure-docs/issues

well there is a request on the application insights repo that has not been answered for over a year.....
and the default install and configure do not help with much.   full tracking is not happening with it.
someone needs to step up and tell us how to use it !  so far it seems like "hot potato"  with everyone poassing it to the next one......

https://github.com/dotnet/aspnetcore/issues/30972

I see. I hadn't heard about that. Anyway ... that's scheduled for NOW 😄 ... by the .NET 8 release in November. It might get bumped to next year because they've been so busy with the framework, but tracking on that issue is the best thing to do.

also read this thread
https://github.com/dotnet/aspnetcore/issues/5461
its very disturbing that folks keep asking and no one can find the time to deal with the very simple question of getting it to work.
or at the least for Microsoft to just publish some kind of how to guide on what the developer should do.
i think i am getting close to an working answer but i have to keep looking and searching ......
it looks like in the end i may have to use the javascript route just cause thats the one that most folks have done and that there is a repo by a developer that they got to work....

all of that i do understand.
but my point is this: at the end of the day all of this: azure, dotnet, blazor and application insights  ARE owned by Microsoft.
so who on what team does the things I really do not care about.  what I do care about is that multiple folks are asking in both places and not getting any solid results.
I cant see what's going on internally , I cant control it..... i can only keep asking and hope that someone takes action.
also some folks are taking on the web assembly side of this but does that code also work for server ??  there is a lot of that we need to get some clarity on..... can we have a common method that will work for Server and Web and Unified ??
also by the way i sent dan an email asking about this ..... just so you know i have tried that and not yet heard back .... may never hear back but i tried.

Usually when enough customers request ... er .... demand ... action ... when it reaches the point of 💀 death threats 💀 😆 , perfect for Halloween 🎃 btw 😆, it's like 'squeaky wheel gets the grease' time. That's when someone, somewhere, swings into action and takes steps to resolve it. It's a matter of priorities. MS owns it ... True! ... and should explain how to use it with each programming framework ... Indeed! ... but MS also doesn't have unlimited 💰💰 funds 💰💰 to spend. It looks like with that issue that it has reached critical mass. Dan took this on directly, so he obviously feels that it has high importance.

one last comment and i will leave this alone....
just to let you know I have been developing for a long time.   years ago I loved when there was a web site called "Channel9"  that Microsoft ran and back then I had a lot of contact with folks.... folks like Barry / aka / blowdart  for example
https://github.com/blowdart
but channel 9 is gone and now it is what it is....

Has this been documented yet? If so, where?


Update Running Suite wiki

Description
Update of the section about running AET tests.
Motivation and Context
Running suite section was outdated.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

I hereby agree to the terms of the AET Contributor License Agreement.

Thank's @Skajven! This PR is inspiring in the way that we could think about running AET suites with curl only (with plain text responses and no additional dependencies for JSON or XML). Cheers!


tpm2-pkcs11: 1.1.0 -> 1.2.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tpm2-software/tpm2-pkcs11/releases.
meta.description for tpm2-pkcs11 is: "A PKCS#11 interface for TPM2 hardware"
meta.homepage for tpm2-pkcs11 is: "https://github.com/tpm2-software/tpm2-pkcs11"
Updates performed:

Version update

Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.2.0 with grep in /nix/store/c3zl1l992jva0mpav5a9bs0p5sn8a1g9-tpm2-pkcs11-1.2.0

directory tree listing: https://gist.github.com/943d2f136592705963f99bee0a54575d

du listing: https://gist.github.com/23e7f93119ddc2293d63e29fdb029732

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
tpm2-pkcs11

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c3zl1l992jva0mpav5a9bs0p5sn8a1g9-tpm2-pkcs11-1.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tpm2-pkcs11 https://github.com/r-ryantm/nixpkgs/archive/1f6368792d0fccf2df3a518a0acfba1c527b3e86.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c3zl1l992jva0mpav5a9bs0p5sn8a1g9-tpm2-pkcs11-1.2.0
ls -la /nix/store/c3zl1l992jva0mpav5a9bs0p5sn8a1g9-tpm2-pkcs11-1.2.0/bin

cc @lschuermann for testing.

@jollheef Out of curiosity, are you using this and the tpm2 NixOS module? I should really finish my blogpost on this :unamused:.

@jollheef Out of curiosity, are you using this and the tpm2 NixOS module? I should really finish my blogpost on this .

I've not used this before, so I've tested it on an empty TPM.


Arches are sometimes empty

The backend seems to forget about arches sometimes.
See:
https://github.com/flathub/website/issues/1423
and
https://github.com/flathub/website/issues/1262

I guess this happens, when the worker writes the document again?

Closing, haven't seen this again


WT can't handle magnets from private trackers, only torrent files

If I use WebTorrent in the command line, and pass it the location of a downloaded .torrent file from a private tracker, it functions as expected.
If I pass the same torrent file through parse-torrent to get the magnet URI and then pass this magnet to WebTorrent in the cli, it does not find any peers.
E.g.
webtorrent "C:\Path\to\file.torrent"

works, but the output from
var parsed = pt(fs.readFileSync('C:\\path\to\file.torrent'))
var uri = parsetorrent.toMagnetURI(parsed)

does not work when passed to the WebTorrent CLI. I can't upload the torrent file here, as it contains the login token for the private tracker, but I can send it by email if you need it.

There's probably a custom field in the .torrent file that the tracker server needs and parse-torrent doesn't recognize it so it throws it away.
Can you run the following code on the torrent file?
var path = './test/torrents/pride.torrent'
console.log(Object.keys(bencode.decode(fs.readFileSync(path))))
console.log(Object.keys(bencode.decode(fs.readFileSync(path)).info))

You will need to install this package:
npm install bencode

Then paste the output here.

Result:
[ 'announce', 'created by', 'creation date', 'info' ]
[ 'files', 'name', 'piece length', 'pieces', 'private', 'source' ]

parse-torrent doesn't recognize the "source" key. I wonder if there's documentation for that anywhere? I've never seen that in any spec.
Do you have a parallel magnet link for the torrent file you're using, from the same source? Could you run this on it?
var magnet = require('magnet-uri')
var uri = 'magnet:?xt...'
console.log(Object.keys(magnet(uri)))

You'll need to install this package first:
npm install magnet-uri

No, sorry, the tracker does not specify magnets

Can you send me the .torrent file? Email is in my profile.

Done!
2015-12-04 4:49 GMT+01:00 Feross Aboukhadijeh<EMAIL_ADDRESS>
Can you send me the .torrent file? Email is in my profile.
—
Reply to this email directly or view it on GitHub
https://github.com/feross/webtorrent/issues/511#issuecomment-161866463.

My understanding of the way that "private torrents" work is that they just use an http tracker server and put a unique identifier into the announce url (for example: a query param). There's no reason this shouldn't work fine as a magnet uri. The tracker will still be contacted, as before.
The only reason I can think of why this isn't working is that other torrent clients that are using the private .torrent file (with the "private: 1" flag) have disabled the ut_metadata extension, so you're not able to fetch the torrent metadata from them.
In any case, I think WebTorrent is producing the correct magnet uri here, so there's nothing else to do.


updating breaks browser

System Details

OS: [e.g.  Ubuntu 24.04 lts]
Thorium Version [123.0.6312.133-1]

Problem
After installing, the browser works fine but whenever i type sudo apt update in terminal an ["update"] is shown, but the update is same version as current but when i let it to update the browser refuses to open
Screenshots

Additional Notes
Add any other context about the problem here.

I am also getting this probelm too on Ubuntu 24.04 lts, my browser refuses to open after updating (whilst being stuck on the same version)

@midzer I think we might have a deb repo issue here.

@Whiplash6009 @jxcg It seems this is an Ubuntu 24.04 issue.
Chromium and things based on it (like Electron), are having a major issue on 24.04 with the sandbox.
Run Thorium from the cmdline with --no-sandbox and see if it fixes your issue. If it does, then it is out of my hands, and is an Ubuntu issue.


How Do I Set a Field To NULL?

I want to undelete some things, is there a proper way to do this?

I've found that if you use a nullable struct like mysql.NullTime you can write null into it's field by setting the Time to a non-default value and setting Valid to false.
type Example struct {
	Id                     string
	SomeTime       mysql.NullTime
}
example := Example{ Id: "1", SomeTime: mysql.NullTime{ Time: Time.Now(), Valid: False}
db.Model(&example).Updates(&example)
// This produces UPDATE examples SET some_time = NULL WHERE Id = '1'

This works because gorm ignores fields with default values for update, but by setting the Time field, we force it to write Null.

or Update("column", gorm.Expr("NULL")) or use nil for pointer.

in the case, i have some some fields which i set type String in model, should i use  Update("column", gorm.Expr("NULL")) for multi times?
any option to update NULL?

@jinzhu , any update for multiple columns and how can we insert multiple fields having NULL values for some fields?

@SantoshSah I have used with success a map[string]interface{} instead of a struct . Having nil as the value of the  desired null property


pkcs11helper: 1.23 -> 1.24

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/pkcs11-helper/versions.
These checks were done:

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.24 with grep in /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24

directory tree listing: https://gist.github.com/fa82ab8b06f566b9c980c0d49e7a4800

du listing: https://gist.github.com/d8cd7f6fba6e45564b5a6cb4c6048428

meta.description for pkcs11helper is: '"Library that simplifies the interaction with PKCS#11 providers"'.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 3d29c1ae6844c3dcf9a00c1673a530adc49a8dd7 && nix-shell --pure -I nixpkgs=. -p pkcs11helper

Success on x86_64-linux (full log)
Attempted: pkcs11helper
Partial log (click to expand)
make[2]: Leaving directory '/build/source'
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24
shrinking /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24/lib/libpkcs11-helper.so.1.0.0
gzipping man pages under /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24/share/man/
strip is /nix/store/4mf2xm9p32lzrim927yk92xhx35yaz62-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24/lib
patching script interpreter paths in /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24
checking for references to /build in /nix/store/vi1vlsjsmz56rdrk2zyga4jbvh5cqfcd-pkcs11-helper-1.24...

Success on x86_64-darwin (full log)
Attempted: pkcs11helper
Partial log (click to expand)
 /nix/store/phl4rr4zq1ydz4v3h4r1pkwnk81gq3ss-coreutils-8.29/bin/mkdir -p '/nix/store/wgbfqs6f06v6f1c47ykwsix9km9ah61a-pkcs11-helper-1.24/share/doc/pkcs11-helper'
 /nix/store/phl4rr4zq1ydz4v3h4r1pkwnk81gq3ss-coreutils-8.29/bin/install -c -m 644 README COPYING.GPL COPYING.BSD COPYING '/nix/store/wgbfqs6f06v6f1c47ykwsix9km9ah61a-pkcs11-helper-1.24/share/doc/pkcs11-helper'
make[2]: Leaving directory '/private/tmp/nix-build-pkcs11-helper-1.24.drv-0/source'
make[1]: Leaving directory '/private/tmp/nix-build-pkcs11-helper-1.24.drv-0/source'
post-installation fixup
gzipping man pages under /nix/store/wgbfqs6f06v6f1c47ykwsix9km9ah61a-pkcs11-helper-1.24/share/man/
strip is /nix/store/8q05v40n0f7amgw70pk6bkb23r7hrzgn-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/wgbfqs6f06v6f1c47ykwsix9km9ah61a-pkcs11-helper-1.24/lib
patching script interpreter paths in /nix/store/wgbfqs6f06v6f1c47ykwsix9km9ah61a-pkcs11-helper-1.24
/nix/store/wgbfqs6f06v6f1c47ykwsix9km9ah61a-pkcs11-helper-1.24

Success on aarch64-linux (full log)
Attempted: pkcs11helper
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24
shrinking /nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24/lib/libpkcs11-helper.so.1.0.0
gzipping man pages under /nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24/share/man/
strip is /nix/store/min150lkigznaayzpwvf8d4jdl1dqvx6-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24/lib
patching script interpreter paths in /nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24
checking for references to /build in /nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24...
/nix/store/v98rnf3av492y1j7lzn556zwf5l321x4-pkcs11-helper-1.24


Caught an exception: mult1mate\crontab\TaskManagerException: class not found

Caught an exception: mult1mate\crontab\TaskManagerException:
class *** not found
in Code Igniter:

$this->load->helper('path');
$this->controller_folder =  set_realpath(FCPATH . 'application/models');

in TasksController.php

How exactly this exception occurred? Did it happen when you tried to open task list or when the system tried to execute one?

When trying to perform a task, I solved the problem as shown in the example.  recommend that it be changed as I adjusted, thank you very much!


Accessibility: unlabeled buttons with talkback

Describe the bug
All the buttons and tabs highlighted all say either "button" or "tab" and are not properly labeled
To Reproduce
Steps to reproduce the behavior:

Turn on talkback in Settings > Accessibility > Talkback
Open Nostros
Tap the items shown with 1 finger
See error

Expected behavior
These buttons and tabs should be correctly labeled
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6] Oneplus Nord N200
OS: [e.g. iOS8.1] Android 13
Browser [e.g. stock browser, safari]
Version [e.g. 22] <IP_ADDRESS>-beta F-Droid (IzzyOnDroid)

Additional context
Add any other context about the problem here.

I would like to work on this.


Failed to construct URL

Versions

nuxt: 2.14.11 (but I suppose every version > 2.14.8 is affected)

Reproduction
I have a return URL from Google oAuth redirect like the following:
https://mydomain.com/oauth/google#state=RHo0uoakf_VDi&access_token=ya29.a-CUT-2E2wlw&token_type=Bearer&expires_in=3598&scope=email%20profile%20https://www.googleapis.com/auth/userinfo.profile%20https://www.googleapis.com/auth/userinfo.email%20openid&authuser=0&prompt=none
What is actually happening?

Downgrading to 2.14.8 solved the issue. I see there was a lot going on with routing in the last 3 minor releases, maybe this is an unhandled case, or hashes related?

Hi @mfrascati thanks for reporting. Would you please try v2.14.12?

@pi0 yep, now it works as expected, thanks!


inverts input on web

I entered 1, then 2 then 3.... This was reproduced on many environments... As you enter the numbers, it is possible to see the controls "flash" and I'm pretty sure what I've seen is the fields being redrawn in the wrong order. I'm going to have a quick look at your code to see if I can figure it out. This was working not long ago and is not an issue on android.
used version:

$ flutter --version
Flutter 2.5.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 18116933e7 (26 hours ago) • 2021-10-15 10:46:35 -0700
Engine • revision d3ea636dc5
Tools • Dart 2.14.4

and used dependencies:

dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
intl: ^0.17.0
logging: ^1.0.2
cupertino_icons: ^1.0.2
flutter_spinkit: ^5.1.0
intl_phone_field: ^2.1.0
pinput: ^1.2.1
toml: ^0.12.0
hive: ^2.0.4
hive_flutter: ^1.1.0
http: ^0.13.3
uuid: ^3.0.4
device_info_plus: ^3.0.1

The issue is linked with semantics. If you want to make your web application easy to interact with when used with Screen Readers, you want semantics to be enabled by default. That was the culprit.
 RendererBinding.instance?.setSemanticsEnabled(true);
We are communicating this with the Flutter team.

@Tkko I added some details to https://github.com/flutter/flutter/issues/92606#issuecomment-960412259. There appears to be an issue with accessibility and the enableInteractiveSelection property. If enableInteractiveSelection is true the issue goes away, but that may have other side effects.

@vsomayaji I'm uploading a new version with the enableInteractiveSelection property, it is also essential for the paste option.

@Tkko you're the best! Thank you for the quick turnaround. I've verified that we no longer see this issue with version 1.2.2.


Add Etalab Open License 2.0 license

internal thread

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Using both UBO and push_constant in shader on Metal

Short info header:

GFX version: 0.2.1
OS: MacOS
GPU: Intel Iris Graphics 6100 1536 MB

I have the following shader I try to use in my project:
#version 450

layout(std140, set = 0, binding = 0) uniform ViewArgs {
    uniform mat4 proj;
    uniform mat4 view;
} viewArgs;

layout(location = 0) in vec2 uv;
layout(location = 1) in vec3 position;

layout(push_constant) uniform PushConstants {
    vec2 translation;
    float scale;
    float health;
} pushConstants;

Here's the full version: (https://github.com/mvlabat/hello_amethyst/blob/e0d93fe98f83c97eb04b1bf32d604a4fc6c67285/resources/shaders/health_ui.vert)
When I run my project, gfx fails on compiling the shader with the following error:

Error compiling the shader CompilationFailed("Compilation failed: \n\nprogram_source:36:133: error: 'buffer' has a duplicate index '0'\nvertex main0_out main0(main0_in in [[stage_in]], constant ViewArgs& viewArgs [[buffer(0)]], constant PushConstants& pushConstants [[buffer(0)]])\n                                                                                ^\n")

With a very quick glance at gfx-rs code I assumed that's because gfx-rs always sets 0 binding index for push constants:
https://github.com/gfx-rs/gfx/blob/c547e0d6d376df78c1f87639b6b055e4197c7ecb/src/backend/metal/src/device.rs#L1049-L1060
Though as I'm a total noob in Vulkan and gfx-rs I might be wrong.
Here's my code where I write push constants, in case you can find it useful. It's amethyst though, I dunno if it can help you a lot...
https://github.com/mvlabat/hello_amethyst/blob/e0d93fe98f83c97eb04b1bf32d604a4fc6c67285/src/render_groups/health_ui.rs#L157

Have you updated the sample by any chance? Last time I recall, I couldn't even run it for reasons unrelated to gfx-hal, so it was not possible to reproduce the issue.

Sorry, the bug is in my application. Creating pipeline layout like that fixed the problem:
let push_constants = vec![(pso::ShaderStageFlags::VERTEX, 0..4), (pso::ShaderStageFlags::FRAGMENT, 0..4)];

    let pipeline_layout = unsafe {
        factory
            .device()
            .create_pipeline_layout(layouts, push_constants)
    }?;


Fix some "needless lifetime" clippy lints

These lints seem to be new in clippy nightly.

@hdevalence this PR contains minor changes to zebra-network/src/peer/connection.rs, can you check that they're ok?
I assume that's what this comment means:

// The danger is to the mind. The danger is unleashed only if you substantially
// disturb this code. This code is best shunned and left encapsulated.

Maybe we could also replace that comment with something a bit more explicit?
We could start the module with a doc comment that explains why people should be careful modifying that code.
Some people only read the first line, so let's be upfront about the risks.

I'm going to merge this now, because the new lint is causing spurious CI errors in other PRs.
But please review these changes!

Clippy is being quite opinionated here, no? I actually prefer the style that names the lifetime.

@teor2345 Those changes look fine to me!  The comment is a joke about the complexity of the Bitcoin network protocol.  We can remove it later if you'd like, but I think that's a lower priority than completing the verification logic.

@teor2345 Those changes look fine to me! The comment is a joke about the complexity of the Bitcoin network protocol. We can remove it later if you'd like, but I think that's a lower priority than completing the verification logic.

<コ:彡

Clippy is being quite opinionated here, no? I actually prefer the style that names the lifetime.

I mean, it's pretty much clippy's job to have opinions. (And our job to decide if we agree.)
I'm not surprised it's broken, it's a nightly build, after all.


Fix test_dr_volume_with_backup_block_deletion_abort_during_backup_in_progress

The DR last backup should be empty when GC delta block delete is aborted.
https://github.com/longhorn/longhorn-tests/pull/592

Testing with https://github.com/longhorn/longhorn-engine/pull/573.

Regression (Build#175)


How modify certificate validity to 100 years？

How modify certificate validity to 100 years？

Hi @jepson66, I am afraid you will need to provide your own certificate in this case. All certificates can be found under /var/snap/microk8s/current/certs. Which one do you plan to update? Please be aware that depending on the certificate you update you may need to update any kubeconfig files using it. Config files are in /var/snap/microk8s/current/credentials/.


Reference improvements

Added function descriptions for: emptyArrayToSingle, least, greatest
Fixed formatting.
8c33444 has a major and arguable change: I removed the dashes from the paragraphs' beginning (mostly for the function descriptions). I think it looked weird in the HTML reference:

It looks clearer to me without dashes.
Also, it made formatting consistent (since there already were some paragraphs that do not have dash in the beginning).
I also rephrased some things in Russian reference, among of them:
"регексп" -> "регулярное выражение"
"эскейпить" -> "экранировать"
Also, fixed several typos in the Russian reference.
Please let me know if I overdid fixing the reference. 😄

Everything is fine, thanks!


ndi: 5.6.0 -> 5.6.1 + update src and fix lib symlink

Description of changes
The NDI library is currently broken. Adding a couple lines to remove the old bin -> lib symlink and update it with the correct path.
#82617 Brought up the idea of just sourcing the file for the user. I am not entirely sure how to handle the acceptance of NewTek's EULA but figured I'd get this up so others might be able to help contribute on that front.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Current bin symlink problem:
nixos/nixpkgs git:(master*)git --no-pager diff
diff --git a/pkgs/development/libraries/ndi/version.json b/pkgs/development/libraries/ndi/version.json
index 686abdb2c2b7..c0184c27df7e 100644
--- a/pkgs/development/libraries/ndi/version.json
+++ b/pkgs/development/libraries/ndi/version.json
@@ -1 +1 @@
-{"hash": "sha256:4ff4b92f2c5f42d234aa7d142e2de7e9b045c72b46ad5149a459d48efd9218de", "version": "5.6.0"}
+{"hash": "sha256:0wh5bqy9xx08wnfah92pgs4f6xn6mwfyhwdzbhf5ghkbw8pc7z0w", "version": "5.6.0"}
nixos/nixpkgs git:(master*)export NIXPKGS_ALLOW_UNFREE=1; nix build .#ndi --impure
warning: Git tree '/home/jsh/git/nixos/nixpkgs' is dirty
nixos/nixpkgs git:(master*)ls -la result/bin
total 14493
dr-xr-xr-x 2 root root        7 Dec 31  1969 .
dr-xr-xr-x 7 root root        7 Dec 31  1969 ..
lrwxrwxrwx 1 root root       42 Dec 31  1969 libndi.so.5 -> ../../lib/x86_64-linux-gnu/libndi.so.5.6.1
-r-xr-xr-x 1 root root 23711576 Dec 31  1969 ndi-benchmark
-r-xr-xr-x 1 root root   675736 Dec 31  1969 ndi-directory-service
-r-xr-xr-x 1 root root 26545752 Dec 31  1969 ndi-free-audio
-r-xr-xr-x 1 root root 25236856 Dec 31  1969 ndi-record

Linking this issue too since its relevant #219578

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/exclude-package-from-cache-nixos-org/44178/1

Updated, thanks @JohnRTitor

@ofborg build ndi
@ofborg build obs-studio-plugins.obs-ndi


Add integrity property to SRI-enabled DOM elements

Related to #8955. This adds properties integrity: string to HTMLScriptElement and HTMLLinkElement.

Hi @DamonGant, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

This file is a build output. Your change needs to go in https://github.com/Microsoft/TSJS-lib-generator

Thanks for your PR. these files are not manually edited, they are auto-generatd from a script in . You can find more information about contributing lib.d.ts fixes at https://github.com/Microsoft/TSJS-lib-generator.
Changes should be done in https://github.com/Microsoft/TSJS-lib-generator instead.
Please find more information at: https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md#contributing-libdts-fixes.


Docs: Maintain menu position on click

Describe the bug
When I select a content from the right menu, I get lost because menu refresh and focus on top.
To Reproduce
Steps to reproduce the behavior:

Go to main menu
Click on a section close to the bottom
See error: Menu is on the top

Expected behavior
Would like to maintain the position, to see the active section in the menu
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS [e.g. iOS]:
Browser [e.g. chrome, safari]:
Argilla Version [e.g. 1.0.0]:
ElasticSearch Version [e.g. 7.10.2]:
Docker Image (optional) [e.g. argilla:v1.0.0]:

Additional context
Add any other context about the problem here.

@leiyre
I think I am going to need some help here because both the Furo theme and the default sphinx website show the same behaviour. And the Furo theme explicitly mentions it shouldn´t be used with too much content in the sidebar.

@davidberenstein1957  I don't know if reducing the content in the sidebar is feasible for us so I'll check some options like save in the local storage the scroll position or something similar, I need to explore and think about


False negative:  "satisy"

misspell does not catch "satisy", which should be "satisfy"

hi there. Looks good.  I will add it.


Check for optional property expanded with spread operator is skipped

🔎 Search Terms
"spread operator", "optional property"
🕗 Version & Regression Information

This is the behavior in every version in Playground.

⏯ Playground Link
https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgCJzHZBvAUMg5GAe2IC5kBnMKUAcwG59CAjOKC62kR3AX1y5QkWIhQB5AA5hgxEHAA26TDmYES5KjXpNCyNlAD8nbTyYDcAekvIAwnEooAjBQCiUKMShWbAPmQACp6S0GAAnsgA5AaRyMCUyAC28ZT0cSDI4SFR2PpwAF7GWtx0yAA+yACuIAAmEDCgEDUMRKQmJS18sSyVYMhQEACOlcADNemZYdmRynCRAHS4CHLUyABuipUQLmgYWAC8qnoaFJEAYuLikQA0asjzD9hs+RQARABC7K98t3xMPnYHCgAEwUAByxGQ7k8UGQhnhSxWfQ2Ci2oOQUhkckUs2QhzwxzaUTOpBudwe8yeBTenyg31+-2sgMcyAAzG4PF4Af4ACpTFCRXInYo6PIvEVmZBdOIJEDEPoOVJ0eQsBQoMCQrICzGyeRKPYLbkYlgAKwgCD6CmAIkUSTgETkCgilBCCGAMAiAGs5QB3DKSYKhYAQSjXZBwWpRZ6xGrEEPIOV9CAAD3ifVAk2mOux+swhuWIFWKK27Ix0l1OL2eKOhGF51Jtz0z1OtLJf2YQA
💻 Code
interface Data {
    foo: string;
    bar: string;
}

interface OptionalData {
    foo: string;
    bar?: string;
}

// Case 1: Error
// > Property 'bar' is missing in type '{ baz?: string | undefined; foo: string; }' but required in type 'Data'.
const value1: Data = {
    foo: 'FOO',
    ...{baz: "Bar"},
};

// Case 2: No Error ???
const value2: OptionalData = {
    foo: 'Foo',
    ...{baz: "Bar"},
};

// Case 3: Error
// > Type '{ foo: string; baz: string; }' is not assignable to type 'OptionalData'.
// > Object literal may only specify known properties, and 'baz' does not exist in type 'OptionalData'.
const value3: OptionalData = {
    foo: 'Foo',
    baz: 'Bar',
};

🙁 Actual behavior
In all cases, bar is misspelled as baz
In cases 1 and 3, typos can be detected as errors.
However, in case 2, the compilation succeeds without any errors.
🙂 Expected behavior
In all cases, typos can be detected as errors.
Additional information about the issue
I found this bug when I was writing the following code with exactOptionalPropertyTypes set to true.
return {
    foo,
    ...(bar !== undefined ? { bar } : {}),
};

The Excess Property Check[^1] is not (currently) done for spreads.  See https://github.com/microsoft/TypeScript/issues/39998.
[^1]: Note that, in general, EPC is primarily designed as a lint check and is intentionally not comprehensive.


[Event Request] Codeunit 1220 "SEPA CT-Export File" - Trigger OnRun - New Event OnBeforeExport

Hello, we need the possibility to extend the trigger OnRun on SEPA CT-Export File Codeunit (CU 1220) as follows:
    trigger OnRun()
    var
        BankAccount: Record "Bank Account";
        ExpUserFeedbackGenJnl: Codeunit "Exp. User Feedback Gen. Jnl.";
    begin
        LockTable();
        BankAccount.Get("Bal. Account No.");

        //new-s
        IsHandled := false;
        OnBeforeExport(Rec,BankAccount,IsHandled);
        if IsHandled then
            exit;
        //new-e

        if Export(Rec, BankAccount.GetPaymentExportXMLPortID) then
            ExpUserFeedbackGenJnl.SetExportFlagOnGenJnlLine(Rec);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforeExport(var GenJnlLine: Record "Gen. Journal Line"; BankAccount: Record "Bank Account"; var IsHandled: Boolean)
    begin
    end;

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


Deploying to render.com

Describe the bug
First of all, thanks for the amazing repo!
I am trying to deploy it using docker inside render
To Reproduce
Steps to reproduce the behavior:

Go to render.com
Create a new web service
Use a free instance
Use the default configuration
Deploy it

Expected behavior
Deploy successfully
Screenshots

Desktop (please complete the following information):

OS: [e.g. Windows]
NodeJS Version [e.g. 18.16.0]

Additional context
Add any other context about the problem here.

Seems like Render.com doesn't support disk for normal docker deployment

Seems like Render.com doesn't support disk for normal docker deployment

@kibolho Did you solve it by any chance ?


v3: Support for MAPL-as-library

It has been requested by some of the spack-stack folks (e.g., @climbfuji) that GEOSgcm when built with Spack should be able to use MAPL as a library rather than as a component built in.
I believe this is all that is necessary. We just need to tell CMake where mapl_stub.pl is. Because MAPL is built under ecbuild, that means it has a variable called MAPL_BASE_DIR[^1] that points to where MAPL is, e.g., in spack, where spack installed it.
At the moment it seems to pass CMake. I'm exploring more.
[^1]: This is not great for MAPL since MAPL_Base is a thing for us, but, well, that's what ecbuild does.

ETA: This is not enough. I'm missing something else:
[ 19%] Built target GEOSdatmodyn_GridComp
/bin/sh: generator-NOTFOUND: command not found
gmake[2]: *** [src/Components/@GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/@GEOSchem_GridComp/HEMCO_GridComp/CMakeFiles/phony_HEMCO.dir/build.make:75: src/Components/<EMAIL_ADDRESS>Error 127
gmake[1]: *** [CMakeFiles/Makefile2:12294: src/Components/<EMAIL_ADDRESS>Error 2


Applicative interface leaks memory

Using *> instead of >> makes parsers use more memory. I suggest adding these definitions to the Functor instance for ParsecT:
(*>) = (>>)
p1 <* p2 = do { x1 <- p1 ; p2 ; return x1 }

Below is a program that demonstrates the problem. With the current Parsec behaviour, you get this memory profile. You can see that lots of heap space is used, but when you force the output of the parser most of it goes away.

Using >> instead of *> (i.e. what you should get with the suggested change) gives this nicer profile. (Note the change in the vertical scale.)

Here is the program that generates the profiles.
import Control.Applicative ((<*), (*>), (<$>))
import Control.Monad
import System.Environment
import Text.Parsec
import Text.Parsec.String

-- Instructions to reproduce graphs:
--
-- First, load this file in ghci and run "generateData".  This will
-- create a file called "ab-input".  Then:
--
--   ghc -O AppLeak -prof -fprof-auto -rtsopts
--   ./AppLeak 1 +RTS -h -i0.03 -RTS < ab-input
--   hp2ps -c AppLeak.hp && mv AppLeak.ps AppLeak-1.ps
--   ./AppLeak 2 +RTS -h -i0.03 -RTS < ab-input
--   hp2ps -c AppLeak.hp && mv AppLeak.ps AppLeak-2.ps
--
-- AppLeak-1.ps shows the heap profile with the leak; AppLeak-2.ps
-- shows the well-behaved profile.
--
--
-- Adding explicit definitions of <* and *> to the Functor instance
-- for ParsecT will fix the problem:
--
--    instance Applicative.Applicative (ParsecT s u m) where
--        pure = return
--        (<*>) = ap -- TODO: Can this be optimized?
--        (*>) = (>>)
--        p1 <* p2 = do { x1 <- p1 ; p2 ; return x1 }

-- Some whitespace, followed by one or more 'a's, then one 'b'.
ab :: Parser Char
ab = spaces *> many1 (char 'a') *> char 'b'

-- Same as "ab" above, but with ">>" instead of "*>".
ab2 :: Parser Char
ab2 = spaces >> many1 (char 'a') >> char 'b'

main = do
  args <- getArgs
  selection <-
    if length args > 0 && args !! 0 == "2"
    then putStrLn "using monadic >>" >> return ab2
    else putStrLn "using applicative *>" >> return ab
  c <- getContents
  case parse (many selection <* eof) "" c of
    Left e -> print e
    Right xs -> do
         putStrLn "Parsing finished, forcing result..."
         print $ length $ show xs
         putStrLn "Delaying..."
         delay
         -- We do this again so that "xs" doesn't get garbage
         -- collected before the delay.
         print $ length $ show xs

-- Busy-wait to make the heap profile graph clearer.
delay = print $ fib 32
fib 0 = 0
fib 1 = 1
fib n = fib (n-1) + fib (n-2)

-- Generate some sample data.
generateData = writeFile "ab-input" (concat (replicate 100000 "aabaabababab"))

Is this for both base-4.7 and base-4.8?
The old implementation of (*>) was liftA2 (const id) but that recently changed to a1 *> a2 = (id <$ a1) <*> a2.
I'm fine making the suggested changes either way, but if there is some larger, recent regression we should make sure other folks know about it.

I originally was using GHC 7.8 and base-4.7. I just tried with GHC 7.10.1 and base-4.8; the leak is still there but it is reduced -- where the peak was above 80MB now it's at about 25MB. (The non-leaking case looks the same across both compiler versions.)


Cannot open include file: 'json.hpp': No such file or directoy

So i cant compile and i tryed to add json.hpp to header files and i get this error Severity	Code	Description	Project	File	Line	Suppression State
Error	C1083	Cannot open include file: 'json.hpp': No such file or directory	hackControl	c:\users\d0tz_\desktop\pubg-map-hack-master\usermode app\hackcontrol\types.hpp	4
Here is a screenshot https://gyazo.com/ddad073874e36e28110a6e2414eede2f

Very quick google search might give you an answer.
Hint: add include library
Another hint: also link against libraries, that's the next question why you would be coming back & crying about after solving this one.


Version 1.1 now required?

We've been using version 1.0 of this package with GitHub Actions (on Ubuntu 20.04) quite happily for several months to sign artifacts using a signing key in a Google KMS HSM. Recently, our builds started failing with errors like this:
...
kmsp11 failure occurred prior to library initialization: returning 0x30 from C_Initialize due to status UNAVAILABLE: 502:Bad Gateway [type.googleapis.com/kmsp11.StatusDetails='CK_RV=0x30']
...

Upgrading to 1.1 fixed the problem.
I didn't notice anything in particular in the release notes that jumped out as the reason beyond "Several internal dependencies were updated." Is it safe to say that 1.1 is now a requirement across the board and we should update all our code signing repositories accordingly or is there something else potentially afoot that would be useful for us to help debug?

Thanks, @bdhess. Let us know if there's anything we can do to help.

Compatibility has been restored, globally.  Thanks again for raising this issue.


Non super-staffusers shouldn't be able to edit staff users email address

A staff user having permissions to edit staff members shouldn't be able to edit staff members email address. Allowing staff members do edit other staff members email address allows to bypass user restrictions.
For example, let's imagine, we are<EMAIL_ADDRESS>we can add staff users and edit their groups because it's part of our job. But cannot see and edit orders, because it's not part of our job.
Now, we want to be able to create orders and steal information we shouldn't be able to access from the website. Let's imagine, we want to access the commercial, or even worst... The superuser.
All we have to do, to gain higher privileges (if #1966 is not enough for us!), is to edit the superuser (or the commercial)'s email address to an email address that is in our control and, reset the password and... Enjoy.

Please note that I will open a PR soon for that one as I fixed the issue. So no need to work on it (#1966 soon but didn't fix it yet).
I also wrote tests for the dashboard customers views because I saw there was none (for the views). And moved the ajax listing of customers of dashboard in the dashboard tests folder as it is a dashboard test, irc there is an open issue about moving tests to dashboard.
And also refactored the dashboard customer creation and edition views to make them cleaner, and fixed a bug on success message translation (pgettext('ctx', 'msg here %s' % this_was_the_bug)).

Hi @NyanKiyoshi,
would you like to share changes you metioned in above comment with us? If not, someone from our team could fix this issue soon.

Hi!
The changes were at fix/privilege-escalations, but only one commit was done https://github.com/NyanKiyoshi/saleor/commit/20a313c1805cf7a6800f8252a3d05678d397c63a. It mainly fix #2000, by checking if the user has greater privileges than the user to be edited.
But those changes are quite messy as of now, I didn't have time to get back to them.
So, if someone wants to take care of those issues, I think it would be best to take over from scratch.
I'm really sorry, I don't have much time available.

@NyanKiyoshi in your original example we are<EMAIL_ADDRESS>we can add staff users and edit their groups because it's part of our job - couldn't I just create an account with the permissions I want? If you truly want security at this level you need to split account creation and activation.
Seems to me only superuser should be able to edit staff email addresses (which shouldn't change often), the remaining risks can only be managed through 'human security', e.g. trusting staff and background checks (if necessary).

@ajostergaard Yes, it is #1966.
Only the user owning the account and super users should be able to edit staff email addresses.

@ajostergaard I don't think any actions should be reserved to super users. I don't encourage having such accounts on production servers.

@patrys I don't disagree but eventually at some level we have to break a stalemate and the only solutions are to remove risky features, trust or the doer/approver model.
@NyanKiyoshi I don't think #1966 is the solution, if I am HR I should not edit orders but I need to be able to setup a user who can edit orders... If you try to solve this using hierarchy eventually you either need a super user or you replace super user with elevated admin which is the same thing.
A slightly tangential idea which might mitigate some risk would be to only allow staff to have email addresses on the business domain (e.g. @mirumee.com), essentially pushing some responsibility to the mail server admins, combined with making staff email addresses read only and activating account by proving access to the email account? That way an evil HR can't hijack an account or easily create a new one. This should mitigate a fair amount of risk without being an undue burden on most businesses though I realise the business email part of it could be unpopular with some 'unruly' admins. :)
As far as I can tell the only way to safeguard 'self-elevation' is for all permissions changes to be done by one person and approved by another... For example using something https://github.com/dominno/django-moderation


fix(scrubber): more robust metadata consistency checks

Problem
Scrubber uses scan_metadata command to flag metadata inconsistencies. To trust it at scale, we need to make sure the errors we emit is a reflection of real scenario. One check performed in the scrubber is to see whether layers listed in the latest index_part.json is present in object listing. Currently, the scrubber does not robustly handle the case where objects are uploaded/deleted during the scan. Below is some traces on possible race conditions that produces false positives.
Case 1: Layer insertion

RemoteTimelineClient
Scrubber
S3 Ground Truth After Step

indexed_layers: [A], layers_present: [A]

read tenant_objects [A]

insert B

upload index to include B

indexed_layers: [A, B], layers_present: [A, B]

download index [A, B]

check B is in tenant_objects → false, error

In the above example, B is actually present on S3. To resolve this, we can issue a HeadObject to the missing layers and see if they are actually present.
~Case 2: Layer deletion (impossible)~

RemoteTimelineClient
Scrubber
S3 Ground Truth After Step

indexed_layers: [A, B], layers_present: [A, B]

download index, indexed_layers = [A, B]

delete A from index

indexed_layers: [A], layers_present: [A, B]

delete A

indexed_layers: [B], layers_present: [B]

read B, tenant_objects = [B], indexed_layers = [A, B]

check if A is present in tenant objects, nope, → error (this is a false positive)

This case is made impossible by always read the tenant objects listing first before downloading the index.
Case 3: Fast L0 replacement

RemoteTimelineClient
Scrubber
S3 Ground Truth After Step

indexed_layers: [], layers_present: []

read tenant_objects []

insert L0

upload index to include L0

indexed_layers: [L0], layers_present: [L0]

read index [L0]

check L0 is in tenant_objects → false

upload L1; upload index, delete L0

indexed_layers: [L1], layers_present: [L1]

head_object(L0) → fail

This is very unlikely but theoretically possible. Instead of rescanning the index, the implementation will emit the error with a caveat indicating the missing layer is L0.
Summary of changes
Condition for success: An object in the index is (1) in the object listing we acquire from S3 or (2) found in a HeadObject request (new object).

Add in the HeadObject requests for the layers missing from the object listing
Keep the order of first getting the object listing and then downloading the layers.
Add new test to see if scrubber actually detect the metadata inconsistency.

Misc

A timeline with no ancestor should always have some layers.

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Tested on staging, logged warnings and errors as expected.


E2-1883: Remove displayed event

What
Where/Who

JIRA Issue
E2-1883

People Involved
@shivanshukumar

Background
Need to remove an event leads to inconsistent results on the dashboard
Implementation
Remove event
Testing steps
None
Is this change backwards-compatible?
Yes

Added the links to the JIRA. There's no test necessary since we're just removing an event.


New version: VoronoiFVM v1.19.2

Registering package: VoronoiFVM
Repository: https://github.com/j-fu/VoronoiFVM.jl
Created by: @j-fu
Version: v1.19.2
Commit: b91fe55c2dbefbcff834fdbd82362b0d102df425
Reviewed by: @j-fu
Reference: https://github.com/j-fu/VoronoiFVM.jl/commit/b91fe55c2dbefbcff834fdbd82362b0d102df425#commitcomment-139297698
Description: Solution of nonlinear multiphysics partial differential equation systems using the Voronoi finite volume method

Please cancel, superseded by #102150


Sustainable solution to maintaining links to 3rd party content

The Security Response Committee gets a fair amount of reports about link hijacking, which is basically what you get when a third party project we were linking to disappears or changes its name (surprisingly common...)
We just got a big dump of reports about links on https://kubernetes.io/docs/concepts/cluster-administration/addons/ and https://kubernetes.io/docs/concepts/cluster-administration/networking/. This is a problem because not only are we drawing from our bug bounty fund to pay out bounties for these, but it also increases the load on the security response committee to validate, triage & follow up on these issues.
Brainstorming some possible solutions:

Exclude these from the bug bounty - Not ideal, as this is still a bad user experience at best, and an attack vector at worst.
Eliminate or reduce external links - Probably the best solution when it's feasible, but not good when the links are providing value to the users.
Better detection of removed content - I believe we already have some form of broken link detection in place, but that doesn't work when a domain falls back to the domain registrar (e.g. a "buy this domain" page). An engineering solution could be to cache the TLS certificates, and flag the link for manual review (file an issue?) when the certificate changes. I don't know how much churn this would generate from legitimate cert rotation though.

Other ideas?
/sig security docs
/committee security-response

From https://datastudio.google.com/reporting/fede2672-b2fd-402a-91d2-7473bdb10f04/page/567IC, between Mar 7 - Apr 5, 2022:

https://kubernetes.io/docs/concepts/cluster-administration/networking/ is the 72nd most popular page, with 26,261 page views
https://kubernetes.io/docs/concepts/cluster-administration/addons/ is the 138th most popular page, with 12,695 page views

Some thoughts

as a personal opinion, I think it's OK not to pay buy bounties about the URLs of third party projects that we hyperlink to

if we hyperlink to a web page and that thing we link to is compromised by other means, eg they commit their release key and push it, that's also not a bug bounty where the Kubernetes project would pay out
I have a feeling that, technically, we hyperlink to every CNCF landscape project

there might be a service that can open GitHub issues when pages we link to expire and are replaced with lookalikes or with holding pages
the existing third party software disclaimer does state “The Kubernetes project authors aren't responsible for these projects, which are listed alphabetically”, but we could reword it or even link to a page that clarifies the lack of responsibility
maybe there is a reputable-enough list of network plugins and / or cluster add-ons that folks might want to use

we could hyperlink to that list, whilst retaining the disclaimer that we're not responsible for the list of contents

we used to provide instructions on setting up a cluster that included details for common network plugins; we no longer do, and I wonder if that means that folks are instead following external guides more.

if the outcome of that is that more people using Kubernetes are relying on docs we don't own at all, does that actually help achieve the outcome we want in terms of helping people run secure clusters?

/remove-kind bug
(not sure what this is, we might add that label back as we triage this)
/lifecycle frozen
/language en

Maybe the folks behind the CNCF landscape might be able to help us out here / we can draw on that existing work? The CNCF landscape is another kind of curated list; it's maintained; there are lots of projects.
I do have a feeling that there are still lots of projects (client libraries, network plugins, container runtimes, the list goes on) that aren't in the landscape. As Kubernetes' wider ecosystem grows, a path that involves the CNCF landscape might well be the way forward.

I'm in favor of delegating to the CNCF landscape. FWIW, you can filter to CNI projects for the sake of the cluster-admin/networking page: https://landscape.cncf.io/card-mode?category=cloud-native-network&grouping=category (though there is not complete overlap with our list)

/triage accepted

I can take a look, update some links and update docs

I can take a look, update some links and update docs.

/assign