Technical Documentation and Prototype

The following things have been added:

Updated function specification document
Technical Documentation
Merged existing refine-search branch
Rudimentary prototype for better search implementation

Dropdown menu
Clickable buttons for attributes and logical operations
Rudimentary button logic
Testing recent search list

The prototype allowed us to recognize early mistakes (not isolating functions enough for example) and adjust with some additional classes like i.e. SearchFieldSynchronizer, which will be further improved upon during the upcoming days.
PS: This repo josphstar/jabref is a new,  clean fork from JabRef/jabref and will be our working repo from now on. For prior pull requests visit the old repo josphstar/jabref2.

Thanks for the concise feedback! I'm very sorry to say that one of us mistakenly commited a completely outdated early draft of our functional specification document which you then reviewed. Nevertheless we got a lot of good points from it which also apply to the actual document. functional-specification-document.md is now corrected.

We have some questions we would like to clear up:

Complex search query: As far as we understood Lucene is used to parse the text field content from the search field, but the query is still passed on to JabRef's internal complex search query. Our implementation must ensure that interaction with the GUI follows Lucene syntax. I understand JabRef wants to get rid of its own complex search and use Lucene entirely in the end. Is the internal overhaul of the search within our capabilities for the semester and also demanded for our issue?
The way we have implemented our UI prototype so far is according to #341 with the PopOver class. You have mentioned JabRef wants to move away from popups, is such an implementation still up-to-date?
We dont understand what required and optional fields are in the context of our UI buttons for the fields, see comment above.
When not providing a logical operation OR/AND, should the default be dynamic or only OR, as described in this comment?

If the query is not a Lucene query, just take each keyword and do an OR search.

I would argue that an AND search would be more appropriate, except if one field appears twice. So:
author=koppor author=btut -> OR search author=koppor title=JabRef -> AND search

Thanks for your efforts ^^

We have some questions we would like to clear up:

Complex search query: As far as we understood Lucene is used to parse the text field content from the search field, but the query is still passed on to JabRef's internal complex search query. Our implementation must ensure that interaction with the GUI follows Lucene syntax. I understand JabRef wants to get rid of its own complex search and use Lucene entirely in the end. Is the internal overhaul of the search within our capabilities for the semester and also demanded for our issue?
The way we have implemented our UI prototype so far is according to #341 with the PopOver class. You have mentioned JabRef wants to move away from popups, is such an implementation still up-to-date?
We dont understand what required and optional fields are in the context of our UI buttons for the fields, see comment above.
When not providing a logical operation OR/AND, should the default be dynamic or only OR, as described in this comment?

If the query is not a Lucene query, just take each keyword and do an OR search.

I would argue that an AND search would be more appropriate, except if one field appears twice. So:
author=koppor author=btut -> OR search author=koppor title=JabRef -> AND search

Thanks for your efforts ^^

Just as to what is in your capabilities, it will be up to you to estimate. If there is an overhaul planned that you think exceeds your limits timewise I suggest you for sure implement what you wanted to implement anyway so that it keeps the future changes in mind/doesn't overcomplicate them. After the project concludes you have the option to continue working with JabRef and finish it off.

* Complex search query: As far as we understood Lucene is used to parse the text field content from the search field,

Yes. Therefore, I would suggest that your pull request targe refine-search, which parses using the Lucene syntax. (Pull Request https://github.com/JabRef/jabref/pull/8206)
That means: The main branch is not updated with this regard. Sorry for the confusion here.

but the query is still passed on to JabRef's internal complex search query.

No. I re-implemented the search based on Lucene.

Our implementation must ensure that interaction with the GUI follows Lucene syntax.

Yes.

I understand JabRef wants to get rid of its own complex search and use Lucene entirely in the end. Is the internal overhaul of the search within our capabilities for the semester and also demanded for our issue?

The internal search is already overhouled. See https://github.com/JabRef/jabref/pull/8206.
You do not need to implement a search for "First Author", "Last Author", "Affiliation". Just use the fields available from JabRef. (In case there is time left, you could work on that, but this is hard stuff. Hint Line 73 in BibQueryVisitor:  if (searchField.isEmpty() || searchField.equalsIgnoreCase("anyfield")) {)

* The way we have implemented our UI prototype so far is according to [#341](https://github.com/koppor/jabref/issues/341) with the [PopOver class](http://javadox.com/org.controlsfx/controlsfx/8.0.5/org/controlsfx/control/PopOver.html). @koppor  you have mentioned JabRef wants to move away from popups, is such an implementation still up-to-date?

We need to distingish PopOvers and PopOuts. -- We need to be clear in teams. See also https://ux.stackexchange.com/q/90336/93436. -- Maybe you should add these two terms to the glossary?

PopOver: https://en.wikipedia.org/wiki/Popover_(GUI)
PopUp: "Popup - These are the assholes of UI Design in this category. They say "Hey, I'm here now. You don't have to deal with me right now, keep doing what you're doing, but I'm not going away until you say you don't want me around anymore." Basically an action you take as a user means something new is shown and you've got to deal with it at some point. They are especially painful if they play noise." -- https://www.quora.com/Whats-the-difference-between-a-modal-a-popover-and-a-popup -- In other words: A popup is a modal window which asks for confirmation.

Since Popups "are the assholes of UI design", JabRef wants to move away from them.
PopOvers are IMHO placed nicely in the UI: They appear right at the place where they are needed.
See the "import from an ID" for a good PopOver example:

* We dont understand what required and optional fields are in the context of our UI buttons for the fields, see [comment above](https://github.com/josphstar/jabref/pull/2#discussion_r753650629).

This is an advanced feature, you do not need to implement. "For me, a hard coded order is also OK." (which you pointed out by linking to the issue)

For completeness I can reiterate one of my comment

used in the current library (this is more a filtering, see above)

One can get the used required fields similar to that:
frame.getCurrentLibraryTab().getDatabase().getEntries().stream()
                     .map(entry -> entry.getType())
                        .distinct()
                        .flatMap(type -> BibtexEntryTypeDefinitions.ALL.stream().filter(t -> t.getType().equals(type)))
                        .sorted()

That would change "Title" "Summary" "Author" "First Author" in the UI element

* When not providing a logical operation OR/AND, should the default be dynamic or only OR, as described in [this comment](https://github.com/koppor/jabref/issues/341#issuecomment-966264846)?
  > > If the query is not a Lucene query, just take each keyword and do an OR search.

The idea was to be like google, which doesn't do a strict AND. (in the context of the web search we already have the default OR in place)
@btut any input here? What is the thing we do in the PDF full text search with Lucene backend?

Regarding AND and OR, @btut already made a statement at https://github.com/koppor/jabref/issues/341#issuecomment-966264846. I think, there should be a constant which can be changed easily when we are sure how to handle.


Exit prompt sugession

Right now the exit prompt shows either always or never according to one boolean option. It would be ideal to show the prompt only when a download or conversion is in progress, or an item is qued for download. It makes little sense to have an exit prompt under normal circumstances.

This issue was intended for another repo. Please remove.


[Question]: How to use http mode oder by data

Describe your problem
How to use http mode oder by data?

Check the example:
https://github.com/infiniflow/infinity/blob/25797ef665ed2735047605c30b969653b0d6ea7d/example/http/insert_search_data.sh#L107


Value throws an InvalidOperationException after any call of .WithError()

Here are the steps to reproduce the behaviour.
public static void Test()
{
    Result<Customer> result = Result.Ok(new Customer() { Name = "Name", Email = "some@email.com"});

    var valueBefore = result.Value; // This works. The Value is not null

    result.WithError(new Error("Some Error"));

    var valueAfter = result.Value; // This will throw a exception: System.InvalidOperationException: 'Result is in status failed. Value is not set. Having: Error with Message='Some Error''
}

This is intended behavior. By design, you're not supposed to access the value of a failed result.

Thank you for your question. @Kilazur already answered it - it makes no sense to query the Value property if your Result is failed. Therefore I implemented this safety net and throw in this case an exception. Details see in the docs


Remove DHT flag when joining p2p swarm

--dht flag is now obsolete in p2p and p2p will not accept it.

Done in Master.

Done in Prod.


V4 No longer works in dropdown

V3 supported the ability to have the date selector in a dropdown. This functionality no longer seems to work in V4
(see http://jsfiddle.net/0Ltv25o8/282/)
On my code, if I go back to the dropdown after the initial select, the datepicker displays on dialog load (can't replicate in JS fiddle), so initially I thought it might be the initialisation was triggering an onChange(), since the control now defaults to Today.
However, setting useCurrent: false prevents the picker from working at all. This may be a separate issue.

This may not work for you but, you can use inline mode

Today

Tomorrow

$('#datetimepicker7').datetimepicker({
                inline: true
            });


Storage Explorer crashes when renaming one file under one attached file share

Storage Explorer Version: 1.11.1
Build: 20191206.5
Branch: dev/marayerm/electron7/packaging
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS High Sierra
Architecture: ia32/x64
Regression From: Previous build (20191206.2)
Steps to reproduce:

Launch Storage Explorer.
Expand a storage account -> File Shares.
Create a new file share -> Upload one file to it -> Use SAS to attach the file share.
Open the attached file share -> Try to rename the file.
Check the result.

Expect Experience:
Succeed to rename the file.
Actual Experience:
Storage Explorer crashes.

The error occurs after the copy has completed when querying for the delete retention policy before deleting. The call to getServiceProperties itself throws an error (should have passed it to the callback). According to the documentation, only the account owner is supposed to be able to call this API, meaning a SAS connection is likely incapable of getting the retention policy.
@v-limu Are you sure this is a regression? Does this also reproduce on a master build?

Hi @craxal Thanks for your update!
This issue is a regression and it doesn't reproduce on master build (20191206.2)

@v-limu The previous build is based on a different branch than the one listed here. Furthermore, I've confirmed this issue occurs in the previous release (1.11.1); although the error message does not pop up, activity never completes once the copy is done. Therefore, this is not a regression.
The problem occurs because we try to get the delete retention policy for a file share, which doesn't work, because that's only valid for blob containers. The older client SDK handles errors like this in a weird way; they throw errors like this instead of passing them to our callback, which really messes with the proper propagation of errors.

Hi @craxal Got it. Thanks for your share.
Activity log  never completes when renaming one file under one attached file share on master branch. It is related to: 2318


Add shutdown button to safely shutdown the raspberry pi

Pull request #32 adds a shutdown button to the settings page.


help me

Hello, i have checked your installation video and made the installation in the same way but when running "mentat ." on ssh then it's listing all the files on ssh. i am not getting like you are getting when running "mentat ."
one error is appearing after listing all the files. please check the  attached screenshot.

Regards.

Hey @utpal4job! Thanks for catching this; we changed how we handled file includes recently and this was a bug that slipped through. I made PR #383 which should fix the bug; once it's merged, if you git clone mentat and try it out, it should be fixed. Thanks!

Mentat 1.0.6 is now available on pypi, so if you install with pip install --upgrade mentat you'll get the fixed version!

ok, thanks. i will check it.

Hello, thanks it's working fine but gpt4 model error appears. how can i change the gpt model?
pls check the attached screenshot.

Regards.

There are ways to change the model, but there aren't models than can handle as many tokens as you are trying to include. I assume you are running with mentat . which adds everything in the directory to context. Instead how about you try running with mentat path/to/file_a path/to/file_b, adding just a couple files you want to work with?
A more advanced feature is to have it select files automatically based on what you ask. This is called auto context, and you can run with mentat -a

Hello, thanks for your reply. i have changed the gpt model and it's working fine.
Regards.

What model did you change it to?

I have used "gpt-4" instead of "gpt-4-1106-preview".


Implement user roles

@wholesomedev To keep things simple, I've changed the user role functionality to only support on role per user. This is easier to understand and implement.
Currently, we'll only have an EDITOR role which can change anything. A user with no role can't do anything. In the future, we may want to add other roles, like MODERATOR or CONTRIBUTOR with limited capabilities.

Worth noting that while one user can only have one role, we may want a field to be editable by multiple roles. That's why I've changed the directive name to requireOneOfRoles.


Feat/label line smooth

[中文版模板 / Chinese template]
🤔 This is a ...

[x] New feature
[ ] Bug fix
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[ ] Enhancement feature
[ ] Refactoring
[ ] Update dependency
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Release
[ ] Site / documentation update
[ ] Demo update
[ ] Workflow
[ ] Other (about what?)

🔗 Related issue link
close https://github.com/VisActor/VChart/issues/277

🔗 Related PR link

🐞 Bugserver case id
https://github.com/VisActor/VRender/pull/433

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self-Check before Merge
⚠ Please check all items below before requesting a reviewing. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] TypeScript definition is updated/provided or not needed
[ ] Changelog is provided or not needed

🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough

vrender 的合并分支貌似填写做了

是的 已改致[dev/0.15.0]


Rotation Defaulting to 0

When I set a Rotation on a Paper 1.20 server, after 30 seconds the armor stand defaults back to 0 Rotation.

Was already fixed, I had just forgot to upload the new jar


#98 - Adds nuxt 3 example

Just added the nuxt 3 example with a bit of eslint+prettier

#98

@tobiasdossinger checking this out now. Could you please add it in our README as an example under the examples section?

@tobiasdossinger. Also, I added a .mirrorful folder that is exported. Could you add that actually being imported and used in the nuxt 3 app? because I think Nuxt + mirrorful simply added as a dev dependency is not enough of an example. We should show mirrorful actually being consumed and used in a component. Thanks!

@alexdanilowicz
Just added an example component with two variations of using Mirrorful within Nuxt 3:

Using the generated color vars within tailwind config
Using the vars inside the component as they are generated

Disclaimer: The Token Variation is still missing in this example.
Let me know what you think.

Looks great! Feel free to merge!
(I'm curious do you have merge access after I approve the review, or do I need to merge?)

Thanks so much for making all the changes @tobiasdossinger!

Looks great! Feel free to merge!
(I'm curious do you have merge access after I approve the review, or do I need to merge?)

I don't know if I have merge access after the approval. Would be nice to know.


consider adopting semver for container tags?

The current images rely on the latest tag which doesn't offer discoverability or information about updates.  It would be really useful if (maybe in addition to latest) the published images included semver versioning for the tag.

So, long reply as we've had the discussion here and there but never in condensed form.
One of the first messages the container outputs is e.g.
Mar 27 09:53:25 /supervisord: valheim-bootstrap DEBUG - [18] - Running commit 2675b8b0803a6f5f5ce2002325e2a4409e27a060

That information is stored in /usr/local/etc/git-commit.HEAD. The purpose is to figure out which version of the container a user is running when they report an issue.
I might add something that periodically checks if you are running the latest commit of the container. But I have zero interest in introducing arbitrary semantic versions for a container that runs an early access game server and updates it at runtime.
Take the following scenario. We tag the container e.g. 0.5.0-stable and a user pins that version on their system. It works for a while but in a months or two Iron Gate (or more likely ValheimPlus) does a breaking change. The container updates to the latest version of the game server every 15 minutes. So that supposedly stable container now has downloaded a game server version it can't handle and is no longer stable. At that point what is the worth of that 0.5.0-stable semver?
The solution also isn't to not update the game server every 15 minutes. Because the user's Steam will update their Valheim desktop client as soon as an update is released and at that point you'd have an outdated server with an up to date client that can no longer connect.
My feeling on the subject is as long as the game is early access we'll update the container in lockstep with any Valheim releases and users will have the best experience if they just run :latest. When they have container trouble we can debug it using the commit hash. Experimental features are already being incubated in the :dev branch/tag and the general mantra for working on this container is to make absolutely everything backwards compatible and not introduce any breaking changes.
That is why it contains things like the fake-supervisord file or that path migration info in valheim-bootstrap and still supports UPDATE_INTERVAL and BACKUP_INTERVAL even though they've been replaced by cron equivalents. You can run the latest version of the container with the very first container's config and it'll translate gracefully. I put user convenience above all else as I know that this container is in use by a lot of non-technical users and I want them to have a good experience.
@TheCatLady and I had discussions whether we should tag each image build with the commit hash so you could go back and look at old image builds. My feelings on that subject are it's a waste of Github's and Dockerhubs disk space.
Tagging the issue with wontfix but leaving open as I'm always open to compelling arguments.

@TheCatLady and I had discussions whether we should tag each image build with the commit hash so you could go back and look at old image builds. My feelings on that subject are it's a waste of Github's and Dockerhubs disk space.

I actually am not sure what disk space you're referring to? 😅 There isn't really any negative to tagging images with the hash.

what disk space you're referring to

If we tag each image build with a unique hash it'll stay around forever on Github's servers taking up unnecessary space. It's the reason Docker introduced a retention limit.
I'm saying that's a waste because realistically nobody will ever pull those old builds ever again. And if they wanted to they could just build it locally from the git hash.

If we tag each image build with a unique hash it'll stay around forever on Github's servers taking up unnecessary space. It's the reason Docker introduced a retention limit.

I'm not sure what you mean by that?  Tagging the image doesn't have any effect on its retention, it's just a label that is applied to that built image, basically.

Tagging the image doesn't have any effect on its retention

Never wrote that it has. What I wrote is, people tagging every single commit is one of the reasons Dockerhub retention rules had to be introduced in the first place.
But let's step back 🙂
Are we in agreement, that the container consumes around 200 MB to store?
Let's ignore for a moment, that these 200 MB are compressed and that there's uncompressed layers kept around for build caching, and all kinds of other possible optimizations like block level deduplication that could go on on the FS level.
If we are storing a dev, and latest tag of it that's roughly 400 MB, right? And no matter how often we merge/commit something that number is a constant. It does not increase as we're always overwriting the existing tags thereby dereferencing the old one.
Since the inception of this repo we've pushed 170 commits. That averages around 3.54 commits per day. So if we were to tag each image build with the unique commit hash we would increase our storage consumption by 708 MB per day or 250 GB per year.
Accounting for both, GHCR and Dockerhub instead of 0.8 GB we would consume half a TB of storage on the Github and Dockerhub servers for no good reason whatsoever.
Just for fun consider for a moment the impact of 190 Million Github repos doing the one or the other thing. As in having 2 static tags vs. tagging every commit at the same rate as we are. That is a constant 145 PB of storage vs 90,599 PB per year. Then consider that those storage SSDs are cycled out after 3 or so years and their PCBs land in some landfill.
Hence my feeling we'd just be producing waste by tagging each image with a unique hash.

@lloesche Actually, nothing is getting "overwritten" when you publish a new image with an existing tag. The existing images persist, just with the latest tag removed.  So tagging with the has really won't have any impact on storage usage.

@TheCatLady I beg to differ. See https://hub.docker.com/r/lloesche/valheim-server/tags
There are only three digests being referenced by our three tags latest, dev and main.
Once a tag is no longer referencing a digest any unreferenced image layers are being released for garbage collection and the storage eventually freed

@TheCatLady I beg to differ. See https://hub.docker.com/r/lloesche/valheim-server/tags
There are only three digests being referenced by our three tags latest, dev and main.
Once a tag is no longer referencing a digest any unreferenced image layers are being released for garbage collection and the storage eventually freed

Actually, they aren't. 😅  See this Docker blog post: https://www.docker.com/blog/advanced-image-management-in-docker-hub/

This new manifest will be given the tag you specify when you push, such as bengotch/simplewhale:latest. But this does not mean that all of those old manifests which point at the previous layers that made up your image are removed from Hub. These are still here, there is just no way to easily see them or to manage that content. You can in fact still use and reference these using the digest of the manifest if you know it. You can kind of think of this like your commit history (the old digests) to a particular branch (your tag) of your repo (your image repo!).

And on GitHub, you can view all published images (including untagged images) here: https://github.com/users/lloesche/packages/container/valheim-server/versions?filters[version_type]=all

Actually, they aren't. 😅 See this Docker blog post: https://www.docker.com/blog/advanced-image-management-in-docker-hub/

What you linked is for paid plans. I remember sometime last year they announced that they've only paused enforcement of image retention until mid 2021 but their overall goal is to reduce resource consumption (or have you pay for it). So those unreferenced digests will be removed eventually.

What you linked is for paid plans. I remember sometime last year they announced that they've only paused enforcement of image retention until mid 2021 but their overall goal is to reduce resource consumption (or have you pay for it). So those unreferenced digests will be removed eventually.

The blog post is about advanced image management features for paid plans, but the information about what happens when you push a new image with an existing tag applies to all Docker Hub repositories.

We are pausing enforcement of the changes to image retention until mid 2021.
Two months ago, we announced a change to Docker image retention policies
to reduce overall resource consumption.
...
Docker is focusing on consumption-based subscriptions

Image retention limits would apply regardless of tags. Tagged images are still subject to the same policies if they are inactive.
Basically, the untagged image manifests on Docker Hub are not treated any differently than tagged ones with regards to image retention.  It won't impact resource/storage usage in any way.
I personally think it's nice to tag with the commit hash, since it makes it easier for a user to pull a specific version of the Docker image. If a particular image becomes inactive (no pull activity for X amount of time), Docker hub will still prune it regardless of the tag.

The blog post is about advanced image management features for paid plans, but the information about what happens when you push a new image with an existing tag applies to all Docker Hub repositories.

Right, what I meant to point out is their intention. They say they want to reduce resource consumption, in other words they want to spend less money on things they don't make money from. Which I think is fair.
With a paid plan you will continue to be exempt from any retention rules. With a free plan you can be sure they'll work hard on freeing those resources as soon as possible. They just paused that new rule after the backlash they received when announcing it.

I personally think it's nice to tag with the commit hash, since it makes it easier for a user to pull a specific version of the Docker image.

I understand that use case I just don't see which persona is going to do that on such a regular basis it would justify binding those resources for.

Docker Hub will still prune it

I received feedback from Docker that we're going to be covered under the open source program so we'll be exempt from those rules. I'll have to accept some "Joint Marketing Program" though and currently clarifying if our push to GHCR is in conflict with that. If it is then we'll complete the full move to GHCR and update all documentation to point to it instead of Dockerhub.

@lloesche I wasn't fully aware that the valheim server container was dynamically updating the server software at runtime.  Given that, and given that it's still early-access like you say, it doesn't seem to provide a ton of value versioning the image.
My main concern was needing to periodically pull a fresh 'version' of the latest tag in order to pick up whatever changes are required.  It doesn't look like that is as important given the dynamic auto-updating nature of this.  I run valheim as a kubernetes pod and, in that world, using statically-tagged images (like latest) are not a best practice because updates to the container image are opaque.
Happy to close this issue unless we want to keep it open for more discssion.

Right, what I meant to point out is their intention. They say they want to reduce resource consumption, in other words they want to spend less money on things they don't make money from. Which I think is fair.
With a paid plan you will continue to be exempt from any retention rules. With a free plan you can be sure they'll work hard on freeing those resources as soon as possible. They just paused that new rule after the backlash they received when announcing it.

Oh yes, I agree that it's fair for them to remove unused images.  Just wanted to point out that the current practice of not tagging with the hash doesn't reduce resource consumption in any way, unfortunately. Anyone can pull any previously published images from Docker Hub using the digest ID, even if they are hidden from view on the website.

I understand that use case I just don't see which persona is going to do that on such a regular basis it would justify binding those resources for.

Again, wouldn't use/bind any additional resources. Would it be super useful?  Probably not.  But it also wouldn't result in increased resource consumption.  Once the image retention policy begins to be enforced, inactive images will still be removed even if they are tagged with the hash.  The additional tag really has no impact on resource usage.
Also, just to be clear -- I'm not advocating for tagging with the commit hash.  I just want to make sure that everyone is on the same page re: the implications of doing so.

I received feedback from Docker that we're going to be covered under the open source program so we'll be exempt from those rules. I'll have to accept some "Joint Marketing Program" though and currently clarifying if our push to GHCR is in conflict with that. If it is then we'll complete the full move to GHCR and update all documentation to point to it instead of Dockerhub.

That's awesome!  However, I believe Docker Hub's Open Source program only lifts the pull rate limitations (which is not a bad thing!).  GHCR is pretty great, though. Even with pull limits, I don't see the harm in continuing to publish images to both repositories, especially since I'm sure there are users who have configured automatic image updates. We should update the README to help users decide which repository to use, however.

Closing this as there's no semver related discussion going on.


💅 lint/style/useSelfClosingElements false positive error

Environment information
CLI:
  Version:                      1.8.3
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.9.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.1.0"

Rule name
lint/style/useSelfClosingElements
Playground link
N/A
Expected result
When I run
npx @biomejs/biome lint ./src/index.tsx
its offering this fix which is wrong because script tag cannot be self-enclosing

318     │ - ········<script·src="/filepond/filepond.js">
318 │ + ········<script·src="/filepond/filepond.js"·/>
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

script tag cannot be self-enclosing

I think this is only true in HTML?
But this rule is only enabled in JSX, and JSX transpiler should transpile them into the same code, whether you use self-closing elements or not. You can check it in the babel playground.
Did I miss something? Or what kind of issues did you actually run into after you applied the fixes?

Good call, @Sec-ant; you're right.


Numerous obsoleted URLs in repository:

Lot's of old references to the old nuttx.org DocuWiki still exist:
$ grep -r "nuttx[.]org" * | grep http

arch/arm/src/armv7-m/Kconfig:           http://www.nuttx.org/doku.php?id=wiki:nxinternal:svcall
arch/arm/src/armv8-m/Kconfig:           http://www.nuttx.org/doku.php?id=wiki:nxinternal:svcall
arch/Kconfig:           paging feature as described in http://www.nuttx.org/NuttXDemandPaging.html.

boards/arm/cxd56xx/spresense/configs/rndis/defconfig:CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
boards/arm/cxd56xx/spresense/configs/wifi/defconfig:CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
boards/arm/lc823450/lc823450-xgevk/configs/bt/defconfig:CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
boards/arm/lc823450/lc823450-xgevk/configs/krndis/defconfig:CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
boards/arm/lc823450/lc823450-xgevk/configs/rndis/defconfig:CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
boards/arm/lpc17xx_40xx/olimex-lpc1766stk/README.txt:      See http://www.nuttx.org/doku.php?id=wiki:vfs:nxflat#toolchain_compatibility_problem
boards/arm/lpc17xx_40xx/u-blox-c027/configs/nsh/defconfig:CONFIG_NSH_WGET_USERAGENT="NuttX/7.xx.x (; http://www.nuttx.org/)"
boards/arm/lpc31xx/ea3131/README.txt:    paging enabled.  See http://www.nuttx.org/Documentation/NuttXDemandPaging.html.
boards/arm/sam34/flipnclick-sam3x/README.txt:   You can find photos my setup here: http://www.nuttx.org/doku.php?id=wiki:howtos:flipnclick-sam3x
boards/arm/sama5/sama5d2-xult/README.txt:       http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
boards/arm/sama5/sama5d4-ek/README.txt:                 http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#task_create
boards/arm/sama5/sama5d4-ek/README.txt:       http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
boards/arm/samv7/samv71-xult/README.txt:       http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
boards/arm/stm32/clicker2-stm32/README.txt:       http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
boards/arm/stm32/stm32f4discovery/README.txt:            http://www.nuttx.org/doku.php?id=wiki:howtos:stm32-ccm-alloc
boards/arm/stm32/stm32f4discovery/README.txt:     http://www.nuttx.org/doku.php?id=wiki:graphics:nxgraphics for a description
boards/arm/stm32f7/stm32f746g-disco/README.txt:  http://www.nuttx.org/doku.php?id=wiki:howtos:port-drivers_stm32f7
boards/README.txt:http://nuttx.org/Documentation/NuttXConfigVariables.html.

Documentation/NuttX.html:        (see the NSH User Guide).
Documentation/NuttX.html:      (see the NSH User Guide).
Documentation/NuttX.html:          The configuration that was used to verify the Nuttx high-priority, nested interrupt feature.
Documentation/NuttX.html:        NX graphics system.
Documentation/NuttX.html:        As of this writing, the basic Arduino Due port is code complete and a fully verified configuration exists for the NuttShell NSH).
Documentation/NuttX.html:        (see the NSH User Guide).
Documentation/NuttX.html:        Verified configurations are now available for the NuttShell with networking and microSD support(NSH, see the NSH User Guide),
Documentation/NuttX.html:        In NuttX-6.27 there is a working basic port with OS verification, Nuttshell (NSH) configurations, and a graphics test configuration.
Documentation/NuttX.html:        NSH User Guide).
Documentation/NuttX.html:          NSH User Guide) as well as several other configurations.
Documentation/NuttX.html:        As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell NSH).
Documentation/NuttX.html:        This basic board support included a configuration for the NuttShell NSH).
Documentation/NuttX.html:            This basic board support included a configuration for the NuttShell NSH) and a configuration for testing IPv6.
Documentation/NuttX.html:            This board supports included two configurations for the NuttShell (NSH).
Documentation/NuttX.html:        As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell NSH).
Documentation/NuttX.html:      (see the NSH User Guide).
Documentation/NuttX.html:          As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell NSH).
Documentation/NuttX.html:          As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell NSH).
Documentation/NuttX.html:      (see the NSH User Guide).
Documentation/NuttX.html:          The STM32 F7 peripherals are very similar to some members of the STM32 F4 and additional drivers can easily be ported the F7 as discussed in this Wiki page: Porting Drivers to the STM32 F7
Documentation/NuttX.html:         NSH User Guide).
Documentation/NuttX.html:          A NuttShell (NSH) configuration is in place (see the NSH User Guide).
Documentation/NuttX.html:        See the NSH User Guide for further information about NSH.
Documentation/NuttX.html:       Available configurations include the NuttShell (NSH - see the NSH User Guide).
Documentation/NuttX.html:      Available configurations include the NuttShell (NSH - see the NSH User Guide).
Documentation/NuttX.html:      Available configurations include the NuttShell (NSH - see the NSH User Guide).
Documentation/NuttxPortingGuide.html:For a technical description of the NuttX implementation of SMP, see the NuttX SMP Wiki Page.
Documentation/NuttxPortingGuide.html:  The version of NuttXConfigVariables.html for the last released version of NuttX can also be found online.
Documentation/NuttxUserGuide.html:  Non-standard extensions to VxWorks-like interfaces to support POSIX Cancellation Points.
Documentation/NuttxUserGuide.html:  task deletion is deferred if cancellation is disabled or if deferred cancellation is supported (with Cancellation Points enabled).
Documentation/NuttxUserGuide.html:The task_testcancel() function creates a Cancellation Point in the calling task.
Documentation/NuttxUserGuide.html:  This is discussed in much more detail on this Wiki page.
Documentation/NuttxUserGuide.html:
When cancellability is deferred, all cancellations are held pending in the target thread until the thread changes the cancellability type or a Cancellation Point function such as pthread_testcancel() is entered.

Documentation/NuttxUserGuide.html:The pthread_testcancel() function creates a Cancellation Point in the calling thread.
Documentation/NxWidgets.html:    Documentation,
Documentation/redirect.html:<meta http-equiv="REFRESH" content="5;url=http://nuttx.org">
Documentation/redirect.html:  The NuttX RTOS web site has moved to nuttx.org.

INVIOLABLES.txt:  http://www.nuttx.org/doku.php?id=documentation:codingstandard

README.md:<http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig>).
README.md:  > A: Refer to <http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig>
README.md:<http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig>).
README.md:NuttX documentation is also available online at <http://www.nuttx.org>.

ReleaseNotes:    http://www.nuttx.org/NuttxUserGuide.html#priorityinheritance.
ReleaseNotes:    See http://www.nuttx.org/NuttXNxFlat.html.
ReleaseNotes:    (http://www.nuttx.org/NuttXNxFlat.html)
ReleaseNotes:http://www.nuttx.org/NXGraphicsSubsystem.html).
ReleaseNotes:    (see the http://www.nuttx.org/NuttShell.html).
ReleaseNotes:    was completed (see http://www.nuttx.org/NuttXDemandPaging.html)
ReleaseNotes:    http://www.nuttx.org/NuttXDemandPaging.html.  Some additional
ReleaseNotes:    Guide at http://www.nuttx.org/NuttShell.html). Testing of that
ReleaseNotes:    see the NSH User Guide at http://www.nuttx.org/NuttShell.html.
ReleaseNotes:http://www.nuttx.org/NuttShell.html), for the NuttX network test,
ReleaseNotes:    at http://www.nuttx.org/NuttShell.html).
ReleaseNotes:        http://www.nuttx.org/doku.php?id=wiki:nxinternal:highperfints
ReleaseNotes:  http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig for some
ReleaseNotes:        http://www.nuttx.org/doku.php?id=documentation:codingstandard
ReleaseNotes:        http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig for some
ReleaseNotes:      http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#the_roadmap_toward_processes
ReleaseNotes:      http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#the_roadmap_toward_processes
ReleaseNotes:        http://www.nuttx.org/doku.php?id=wiki:howtos:ipv6#ethernet_driver_requirements
ReleaseNotes:      http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#the_roadmap_toward_processes
ReleaseNotes:      http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#the_roadmap_toward_processes
ReleaseNotes:      http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#the_roadmap_toward_processes
ReleaseNotes:      http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#the_roadmap_toward_processes
ReleaseNotes:        http://www.nuttx.org/doku.php?id=wiki:nxinternal:smp.  The
ReleaseNotes:        guide: http://www.nuttx.org/doku.php?id=documentation:portingguide.
ReleaseNotes:        http://www.nuttx.org/doku.php?id=wiki:howtos:smallvectors .  This

TODO:               http://www.nuttx.org/NuttXDemandPaging.html.
TODO:                work with (http://www.nuttx.org) and I discovered after doing the
TODO:                  See http://www.nuttx.org/doku.php?id=wiki:nxinternal:tasksnthreads.
TODO:               http://www.nuttx.org/doku.php?id=wiki:nxinternal:simulator

I'm updating all the references in the OS repo now and should have something up for review.


Refactor script to download and compare SCPs

Describe the Issue
The scripts getSCP.py and  compareSCP.py respectively created a copy of the LZ service control policies (SCP) and compare multiple versions of the SCP (private repo system /aws-ecf-probing-scp)
The problem is that the scripts are saving, as SCP, a "raw" copy as returned by AWS, this raw copy has elements like

"Content": "{"Version":"2012-10-17","Statement":[{"Sid":"PMP\

Formally, it is a json file, but the value of the key Content is not a dictionary but a string. This mades more difficult to pinpoint the specific policy that has changed, as there can be dozens of policies and all of them as value of Content
At this moment I am not sure if to modify getSCP.py to save the SCP as a "proper" json or I will parse it in the compareSCP.py.
In any case the goal is to get a policy in. a single line, so when comparing, the policies that will be different will be clearly marked.
Acceptance Criteria

The compareSCP.py output will clearly mark the policies that are different/Added/removed instead of only indicating that one or more policies have changed.
Jon to review for double checking that there are no deletion because it's using high-privilege access and even though we expect that nothing will be changed, we need to check for that

.
.
.
.
.
.
.
.
.
.
Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

Done and committed to main repo aws-ecf-probing-scp (PR #4)


responsive design complete

Not doing great with my ACPs... Let this one go too long. I'll do better in the future. Hopeful to shoot for the stretch goals tonight.


Bug report: Stopped-in-middle when transferring large files to phone

Describe the bug: Transferring PC → Android

The progress bar stopped in middle when transferring large files (>50MB) to phone. The speed peaked at 80Mbps.
>Turning off encryption solved this issue, as well as boosting the transfer speed by a lot.<

To reproduce
Try sending a large file to an Android phone.
Expected behavior
The progress bar stops at some point, and the network speed is zero.
Additional context: Network environment

Tested on both Wi-Fi 5@866Mbps and Wi-Fi 7@2882Mbps routers → Ethernet@1Gbps to PC.
FTP, SMB transfers using MiXplorer always worked, usually at the speed of ~300Mbps (~450-600Mbps on Wi-Fi 7), so likely not a network issue.

Device Info
Desktop
OS: Windows 11 22H2
CPU: i7-9700K
Smartphone
Model: Xiaomi 14 Pro
Chipset: Snapdragon 8G3
Network: Wi-Fi 7

Did you used a custom download path?

Hi, I also encountered this problem, but it happened when transferring files from Android to Windows. I successfully solved this problem by changing

the default save directory of LocalSend on Windows and Android
using the automatic repair function in the troubleshooting function on Windows
. I don't know what specific operation solved this problem. I hope it helps you!

Did you used a custom download path?

Yes. The path does not contain space.

No I meant the default path on Android

Culprit
Broken path on Android.
After reselecting the path on my phone, the problem's gone. Though, before it worked for small files for some reason.
In the next few days, I will keep an eye on this see if the problem is completely gone or not.

Thank you. I also suspect that Android with content URIs are less stable than direct file system access

I just reproduced this by deleting a file in the file explorer, then I tried to receive the same file name via LocalSend.
After a few megabytes, it gets stuck. I could resolve this by completely deleting the file from the recycle bin / trash.


Button gets disabled too early

https://jsfiddle.net/eeky9n4a/
Press the next button until it stops working.
The next button is being disabled before the last picture reaches the 'slick-center' position.
I looked at the code and it seems like this problem lies in arrows.jsx
if (!this.props.infinite) {
    if (this.props.centerMode && this.props.currentSlide >= (this.props.slideCount - 1)) {
      nextClasses['slick-disabled'] = true;
      nextHandler = null;
    } else {
      if (this.props.currentSlide >= (this.props.slideCount - this.props.slidesToShow)) {
        nextClasses['slick-disabled'] = true;
        nextHandler = null;
  }
}

When I change it to this
if (this.props.currentSlide >= (this.props.slideCount - this.props.slidesToShow))

it works, but then it breaks other scenario's, for example when you have less than 6 slides.
It would be great if this can be fixed soon so I can keep using this package in my projects!

This issue is fixed in latest release


Exome renormalization seems to miss mutations

Hi,
We are using the sigprofiler assignment tool (COSMIC V3.2) to fit the signatures for WES samples. When we set the exome=True parameter, it seems like in the final file which is the Activities.txt some mutations are missed from the input vcf file. For instance, if the input vcf file had 500 SNV's and  then if we check in the final Activities.txt file <500 mutations are seen.
Not sure what is causing it to miss these mutations, is it  possible that the exome-=True removes certain mutations? or the renormalization cannot assign some set of mutations?
Please let me know if it there is a param or something that needs to be changed.
Thanks
Pushpa Itagi

Hi @pushpa-itagi,
Could you please confirm if you are providing VCF files as input? If VCFs are provided and exome=True, then the mutations are downsampled to the exome regions of the genome (review parameter exome on SigProfilerMatrixGenerator's README).

Hi,
Yes we used vcf files as input. Ah, I see the matrix generator module explains it. Thanks for the quick reply.
Also,

Is there a file or database you refer to to define which mutations are exonic? Because if I check my sample annotations a very small fraction are exonic so not sure which mutations are being tagged as exonic.
I also see a BED file as an option to be given, can we use that if we want to retain all SNVs (not just exonic) but still use exome=TRUE.  Will that work?
Please let me know. Thanks!

The exome regions are defined in the exome directory for the corresponding reference genome.
https://github.com/AlexandrovLab/SigProfilerMatrixGenerator/tree/master/SigProfilerMatrixGenerator/references/chromosomes/exome
These regions are from SureSelect v7.

If you want to retain all SNVs, run the matrix generator with BED=None. and exome=False. This will disable downsampling to the regions specified in SureSelect.

Please reach out if you have any additional questions.


Cannot Retrieve NFT Data

When using the NFTE React component, started getting some {error: "Cannot retrieve nft data"} this afternoon.
Not sure if I misconfigured something, of if your https://nfte.app/api is overloaded at the moment

Do you have the contract and tokenId to hand?

Getting same error for:
contract=0x60f80121c31a0d46b5279700f9df786054aa5ee5
tokenId=335911

@nickbytes is it a erc-721 token?

@nickbytes is it a erc-721 token?

Yes, this is an ERC721 created on rarible.

Do you have the link?
On Thu, 22 Apr 2021 at 18:51, Nick Beattie @.***> wrote:

@nickbytes https://github.com/nickbytes is it a erc-721 token?
Yes, this is an ERC721 created on rarible.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/contextart/nfte/issues/25#issuecomment-825061077, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGWPJZGQX43NFGCRARKQXTTKBO3VANCNFSM4XZRCA7A
.

https://rarible.com/token/0x60f80121c31a0d46b5279700f9df786054aa5ee5:335911
On Thu, Apr 22, 2021 at 10:52 AM Sam Mason de Caires <
@.***> wrote:

Do you have the link?
On Thu, 22 Apr 2021 at 18:51, Nick Beattie @.***> wrote:

@nickbytes https://github.com/nickbytes is it a erc-721 token?
Yes, this is an ERC721 created on rarible.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/contextart/nfte/issues/25#issuecomment-825061077,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAGWPJZGQX43NFGCRARKQXTTKBO3VANCNFSM4XZRCA7A
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/contextart/nfte/issues/25#issuecomment-825061658, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW6WM2M5N7HHEKZAJMWJK3TKBO7BANCNFSM4XZRCA7A
.

Guessing something on Rarible's end changed. Haven't had a chance to pull down to try to debug, but I have a feeling that media urls changed...
Looks like everything is at rarible.com now, whereas before... I thought it was at app.rarible.com as evidenced here . I could be totally off base here though.

This should now be resolved and deployed to production


Upgrade Installation Manager API to 1.0.0.Beta3

Diff: https://github.com/wildfly-extras/wildfly-installation-manager-api/compare/1.0.0.Beta2...1.0.0.Beta3

@yersan can you change the static import in the failing test? it looks like autocomplete mistake

Ups, I just did in https://github.com/wildfly-extras/prospero/pull/280, I'll rebase this one once merged


Product variants?

Hi all,
I'm trying to set up product variants in my shoppe store. I see that there is the infrastructure in the rails gem to have product variants through the variants controller and model, but I can't find anything of that effect in the admin panel. Do they need to be enabled in some way?
Variants are very important to my store since it will be selling clothing and will thus need options for colors and sizes; it also will not be managed by programmers so I can't rely on calling the API all the time.
Thanks,
Artur

@arturenault - I have had the same issue but have solved this using variants. if you look at my repo https://github.cm/ikhakoo/ap in the seeds file you will see how i seed in both parent products and variants.
Alternatively, you can go to /shoppe/products
Add a product. Then select the product from the list and in the top right hand corner you will see a button called variants where you can then add variants in.

For some reason I totally missed that button. Thanks a bunch!
I'm still getting a weird error when I try to create a new variant, though:
No route matches {:action=>"index", :controller=>"shoppe/product_localisations", :product_id=>#<Shoppe::Product id: nil, parent_id: 1, name: nil, sku: nil, permalink: nil, description: nil, short_description: nil, active: true, weight: #<BigDecimal:7f8ee3043778,'0.0',9(18)>, price: #<BigDecimal:7f8ee30435c0,'0.0',9(18)>, cost_price: #<BigDecimal:7f8ee3043408,'0.0',9(18)>, tax_rate_id: nil, created_at: nil, updated_at: nil, featured: false, in_the_box: nil, stock_control: true, default: false>} missing required keys: [:product_id]

I've tried redoing all the database migrations and setup steps, but that doesn't seem to solve it.

Create a route in your routes file that matches the one you are calling.

The route is within the shoppe admin panel though. Shouldn't that be handled by shoppe:setup?

That's weird. Do you have the mount Shoppe thing in your routes ?
On Aug 1, 2015 6:47 PM, "arturenault"<EMAIL_ADDRESS>wrote:

The route is within the shoppe admin panel though. Shouldn't that be
handled by shoppe:setup?
—
Reply to this email directly or view it on GitHub
https://github.com/tryshoppe/shoppe/issues/242#issuecomment-126959388.

Yup.
mount Shoppe::Engine => "/shoppe"

What version of Shoppe are you using?

1.1.0

Try updating your rails version
On Aug 1, 2015 7:06 PM, "arturenault"<EMAIL_ADDRESS>wrote:

1.1.0
—
Reply to this email directly or view it on GitHub
https://github.com/tryshoppe/shoppe/issues/242#issuecomment-126960749.

No dice, was already at the latest one.
Could this be a locale issue? I've run into those before.

Doesn't sound like a locale issue, the translation function is fine.
I narrowed down the issue to the fact that it's trying to generate a route for variants#new but apparently the product_id is not getting passed in (missing required keys: [:product_id]), which is not getting passed in for some reason. Looking back at the code snippet I posted before, nearly all parameters for the products are null; isn't this expected in the "new" action?

Hello. I have the same issue here. When I try to add a variant I get an error:
No route matches {:action=>"index", :controller=>"shoppe/product_localisations", :product_id=>#<Shoppe::Product id: nil, parent_id: 5, name: nil, sku: nil, permalink: nil, description: nil, short_description: nil, active: true, weight: #<BigDecimal:7fe5dfc2eb70,'0.0',9(18)>, price: #<BigDecimal:7fe5dfc2e9b8,'0.0',9(18)>, cost_price: #<BigDecimal:7fe5dfc2e800,'0.0',9(18)>, tax_rate_id: nil, created_at: nil, updated_at: nil, featured: false, in_the_box: nil, stock_control: true, default: false>} missing required keys: [:product_id]

There was a commit https://github.com/tryshoppe/shoppe/commit/42ea93107c3261ff0052cf7e0c4a9a0802c6ee7e that added the link to /app/views/shoppe/variants/form.html.haml (line 4) for variant localizations, but it doesn't appear that a corresponding route was added, and possibly not a controller for it either (didn't dig too deep for it).

Yeah, that's working for me too. I'll switch back to 1.0.7 for now but this should really be fixed

Also had the same problem with the error message. Fixed it, when creating a new file app/views/shoppe/variants/form.html.haml and added the content of the original file and just removed the line (works for me).

Ok can you create a PR and I'll accept it?

Done!


prometheus-*: fixes to deal with goPackages multiple-outputs changes

Everything that uses buildGoPackage is affected by that change :(

Most of this stuff should be in go-packages by now. I guess we still have a
lot to do for that migration.
On Sat, Aug 29, 2015, 14:51 Benjamin Staffin<EMAIL_ADDRESS>wrote:

Everything that uses buildGoPackage is affected by that change :(
You can view, comment on, or merge this pull request online at:
https://github.com/NixOS/nixpkgs/pull/9539
Commit Summary

prometheus: Include console templates and libraries
prometheus-*: fixes to deal with goPackages multiple-outputs changes

File Changes

M pkgs/servers/monitoring/prometheus/alertmanager/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-0 (8)
M pkgs/servers/monitoring/prometheus/cli/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-1 (6)
M pkgs/servers/monitoring/prometheus/collectd_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-2 (6)
M pkgs/servers/monitoring/prometheus/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-3 (12)
M pkgs/servers/monitoring/prometheus/haproxy_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-4 (6)
M pkgs/servers/monitoring/prometheus/mesos_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-5 (6)
M pkgs/servers/monitoring/prometheus/mysqld_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-6 (6)
M pkgs/servers/monitoring/prometheus/nginx_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-7 (6)
M pkgs/servers/monitoring/prometheus/node_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-8 (6)
M pkgs/servers/monitoring/prometheus/prom2json/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-9 (6)
M pkgs/servers/monitoring/prometheus/pushgateway/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-10 (8)
M pkgs/servers/monitoring/prometheus/statsd_bridge/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-11 (6)

Patch Links:

https://github.com/NixOS/nixpkgs/pull/9539.patch
https://github.com/NixOS/nixpkgs/pull/9539.diff

—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/9539.

Also worth noting is that protobuf.bin should be a nativeBuildInput and not
a regular buildInput. Cross compiling isn't working yet, but I would like
to make it possible eventually.
On Sat, Aug 29, 2015, 14:58 William Kennington<EMAIL_ADDRESS>wrote:

Most of this stuff should be in go-packages by now. I guess we still have
a lot to do for that migration.
On Sat, Aug 29, 2015, 14:51 Benjamin Staffin<EMAIL_ADDRESS>wrote:

Everything that uses buildGoPackage is affected by that change :(
You can view, comment on, or merge this pull request online at:
https://github.com/NixOS/nixpkgs/pull/9539
Commit Summary

prometheus: Include console templates and libraries
prometheus-*: fixes to deal with goPackages multiple-outputs changes

File Changes

M pkgs/servers/monitoring/prometheus/alertmanager/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-0 (8)
M pkgs/servers/monitoring/prometheus/cli/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-1 (6)
M pkgs/servers/monitoring/prometheus/collectd_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-2 (6)
M pkgs/servers/monitoring/prometheus/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-3 (12)
M pkgs/servers/monitoring/prometheus/haproxy_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-4 (6)
M pkgs/servers/monitoring/prometheus/mesos_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-5 (6)
M pkgs/servers/monitoring/prometheus/mysqld_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-6 (6)
M pkgs/servers/monitoring/prometheus/nginx_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-7 (6)
M pkgs/servers/monitoring/prometheus/node_exporter/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-8 (6)
M pkgs/servers/monitoring/prometheus/prom2json/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-9 (6)
M pkgs/servers/monitoring/prometheus/pushgateway/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-10 (8)
M pkgs/servers/monitoring/prometheus/statsd_bridge/default.nix
https://github.com/NixOS/nixpkgs/pull/9539/files#diff-11 (6)

Patch Links:

https://github.com/NixOS/nixpkgs/pull/9539.patch
https://github.com/NixOS/nixpkgs/pull/9539.diff

—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/pull/9539.

Should protobuf (the non-goPackages one) and vim also be moved to nativeBuildinputs as well?
I can start merging these into go-packages.nix after this set of changes, if that is where everything built with Go should live.

even better, it turns out protobuf.bin isn't even necessary to the build process anymore.

I believe go-packages is the ideal place at this point in time although we still have a lot of legacy stuff we need to clean up.
As for nativeBuildInputs it depends, is it being used by the build machine or by the machine the package is built for. My best guess is that proto would be used by the build and vim called during execution for the end user. By this logic proto is native and vim is a regular buildInput.

vim was being used during the build, believe it or not.  Something in embed-static.sh used xxd, which apparently comes from vim.

heh, travis is OOMing now.

I think I am done messing with this now.


Not Showing Edit Button on Android for Manage Contributions

Describe the bug
It has been reported several times on support that some Android users do not see the edit button on the manage contributions section, when they try to edit a recurring contribution.
To Reproduce
Steps to reproduce the behavior:

Go to Settings -> Manage Contributions section on an Android device (see screenshot and smartphone information below on which I've tested this for example).
See if the edit button is shown correctly

Expected behavior
The edit button should be shown correctly without any cutoff.
Screenshots

Smartphone (please complete the following information):

Device: Samsung Galaxy A20
OS: Android 11
Browser: Firefox
Version: Build 113

Reported at, https://opencollective.freshdesk.com/a/tickets/209011


Migrate to furo

Description
Migrate rtd theme to furo.
Motivation and Context
Furo is nice. Has darkmode. Consistency with rest of our packages.
Types of Changes

[x] Documentation update
[ ] Bug fix
[ ] New feature
[ ] Breaking change1

1The change breaks (or has the potential to break) existing functionality.
Checklist:

[x] I am familiar with the Contributing Guidelines.
[x] I agree with the terms of the Contributor Agreement.
[x] The changes introduced by this pull request are covered by existing or newly introduced tests.
[ ] I have updated the changelog and the credits.

How do we feel about an API heading in the sidebar, rather than a collapsed "API Reference" subsection under the Contents heading? This matches freud and rowan, and I like the idea of having a few less clicks to navigate the docs

How do we feel about an API heading in the sidebar, rather than a collapsed "API Reference" subsection under the Contents heading?

Example:


Updated the documentation to reflect the greater tolerance on configs

Following

https://github.com/Microsoft/vcpkg/pull/1639
https://github.com/Microsoft/vcpkg/commit/e45012d3a67cbeacff3afd8ccd2140b6fa84c8ab

... this updates the documentation accordingly, telling the user that now, any configuration starting with "Release" will be considered as a "Release" (the same for "Debug").

@paercebal,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks!


Release 0.11.5

Motivation
Want to create fixes for 0.11.1 so that lodestar can use. Some proposed changes
https://github.com/ChainSafe/js-libp2p-gossipsub/compare/v0.11.4...0.11.x?expand=1

v0.11.5 was released


kubectl get ... --namespace non-existent should not exit with 0

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):
No.
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):
The relevant ones.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.9", GitCommit:"e6ab4ee54f71e7a403cc733534bab86fd959ecb7", GitTreeState:"clean", BuildDate:"2018-10-16T12:14:47Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.11", GitCommit:"1bfeeb6f212135a22dc787b73e1980e5bccef13d", GitTreeState:"clean", BuildDate:"2018-09-28T21:35:22Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: AWS
OS (e.g. from /etc/os-release): Arch Linux
Kernel (e.g. uname -a): Linux something 4.18.16-arch1-1-ARCH #1 SMP PREEMPT Sat Oct 20 22:06:45 UTC 2018 x86_64 GNU/Linux
Install tools:
Others:

What happened:
$ kubectl get pods --namespace non-existent
No resources found.
$ echo $?
0
$

What you expected to happen:
I expected kubectl to return anything other than zero when information is requested about resources in a non-existent namespace. The current behavior hides errors and generates bugs in scripts/confusion in interactive use. Fail fast.
How to reproduce it (as minimally and precisely as possible):
kubectl get pods --namespace non-existent

Anything else we need to know:
No.

/sig cli
/area kubectl
/kind bug
/priority P2

/assign code-sleuth

I agree with the raiser that the behaviour is unexpected: it is surprising that kubectl does not fail when passed a namespace that does not exist. Some colleagues ran into this the other day and wasted some time discussing the current behaviour.
How about making an incompatible change to kubectl in this case to avoid violating the principle of least surprise? If necessary, this change could be scheduled for the next major version of kubectl so that the backward incompatibility would not itself be a surprise. The next major version at the time of writing would presumably be 2.0.

cc @liggitt

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

We should have a general KEP for this that defines reasonable return codes across all commands.

See can-i

kubectl auth can-i to be exact

/remove-lifecycle stale

/remove-lifecycle rotten

/remove-lifecycle stale


Introduce two-level bins for multidrawable meshes.

Currently, our batchable binned items are stored in a hash table that maps bin key, which includes the batch set key, to a list of entities. Multidraw is handled by sorting the bin keys and accumulating adjacent bins that can be multidrawn together (i.e. have the same batch set key) into multidraw commands during batch_and_prepare_binned_render_phase.
This is reasonably efficient right now, but it will complicate future work to retain indirect draw parameters from frame to frame. Consider what must happen when we have retained indirect draw parameters and the application adds a bin (i.e. a new mesh) that shares a batch set key with some pre-existing meshes. (That is, the new mesh can be multidrawn with the pre-existing meshes.) To be maximally efficient, our goal in that scenario will be to update only the indirect draw parameters for the batch set (i.e. multidraw command) containing the mesh that was added, while leaving the others alone. That means that we have to quickly locate all the bins that belong to the batch set being modified.
In the existing code, we would have to sort the list of bin keys so that bins that can be multidrawn together become adjacent to one another in the list. Then we would have to do a binary search through the sorted list to find the location of the bin that was just added. Next, we would have to widen our search to adjacent indexes that contain the same batch set, doing expensive comparisons against the batch set key every time. Finally, we would reallocate the indirect draw parameters and update the stored pointers to the indirect draw parameters that the bins store.
By contrast, it'd be dramatically simpler if we simply changed the way bins are stored to first map from batch set key (i.e. multidraw command) to the bins (i.e. meshes) within that batch set key, and then from each individual bin to the mesh instances. That way, the scenario above in which we add a new mesh will be simpler to handle. First, we will look up the batch set key corresponding to that mesh in the outer map to find an inner map corresponding to the single multidraw command that will draw that batch set. We will know how many meshes the multidraw command is going to draw by the size of that inner map. Then we simply need to reallocate the indirect draw parameters and update the pointers to those parameters within the bins as necessary. There will be no need to do any binary search or expensive batch set key comparison: only a single hash lookup and an iteration over the inner map to update the pointers.
This patch implements the above technique. Because we don't have retained bins yet, this PR provides no performance benefits. However, it opens the door to maximally efficient updates when only a small number of meshes change from frame to frame.
The main churn that this patch causes is that the batch set key (which uniquely specifies a multidraw command) and bin key (which uniquely specifies a mesh within that multidraw command) are now separate, instead of the batch set key being embedded within the bin key.
In order to isolate potential regressions, I think that at least #16890, #16836, and #16825 should land before this PR does.
Migration Guide

The batch set key is now separate from the bin key in BinnedPhaseItem. The batch set key is used to collect multidrawable meshes together. If you aren't using the multidraw feature, you can safely set the batch set key to ().

For reviewers: If you're wondering why this is CPU-based instead of the GPU-based scatter/prefix sum/collect thing discussed on Discord, it's because the CPU has to know the GPU memory location of the indirect parameters in order to issue the indirect drawcall. For the CPU to have that knowledge, it must be managing the allocations within the indirect parameters buffer. When meshes are added, those allocations could be resized, which yields the problem described in this PR description.
There's still room for GPU work scheduling as a follow-up to this patch, but I believe that this patch is required no matter what, at least until we have something like DGC where the CPU doesn't need to know where the indirect parameters live.

All suggested dependencies have landed now, so marking as unblocked.


Change the way of how destroy on deletion_protection enabled instances work

TL;DR
When destroy is applied to a Google Cloud SQL instance that has deletion_protection and/or deletion_protection.enabled set to true, the way it works now is that Terraform first runs a destroy on (child) resources of the Cloud SQL instance, such as user, database, etc., and when the destroy process reaches the instance itself, it fails due to deletion_protection being enabled.
I think the database itself is much more worth to be protected from deletion than the instance itself - the instance can easily be recreated, in a matter of minutes, but if the database is deleted and it's hundreds of GBs big, restoring from a backup could take quite some time. Since at the moment there is no way to set deletion_protection on the database itself, I suggest adding some kind of flag or an if condition or a check that would first check if deletion_protection on the instance is enabled or not, and if it is, skip deleting any of the instance resources (database, user) instead and throwing an error immediately. That would actually be much better workflow, because if deletion_protection is enabled on purpose, it was most probably done in an effort to prevent losing the database.
Terraform Resources
No response
Detailed design
No response
Additional information
How it works now (deleting resources which are part of deletion_protection enabled instance):
Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes
module.mysql_db.google_sql_user.default[0]: Destroying... [id=csql//csql]
module.mysql_db.google_sql_database.default[0]: Destroying... [id=projects/myproj-staging/instances/csql/databases/csql]
module.mysql_db.google_sql_user.default[0]: Destruction complete after 1s
module.mysql_db.random_password.user-password: Destroying... [id=none]
module.mysql_db.google_sql_database_instance.replicas["csql-replica"]: Destroying... [id=csql-read-replica]
module.mysql_db.random_password.user-password: Destruction complete after 0s
module.mysql_db.google_sql_database.default[0]: Destruction complete after 2s
╷
│ Error: Error, failed to delete instance because deletion_protection is set to true. Set it to false to proceed with instance deletion
│
│

Desired: (don't delete any of the resources, throw an error immediately)
Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes
╷
│ Error: Error, failed to delete instance because deletion_protection is set to true. Set it to false to proceed with instance deletion
│
│

Still pending review and comments, when someone will have time.

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

Still pending review and comments, when someone will have time.

@zculek-fb Plz create ticket for Google Terraform Provider. It should be handled at Provider or API level. Module cannot handle this.


[Feature] Display flight information for airport screens

This PR adds an independent view of an airport information screen, showing current flight information (such as departure time, flight number, etc.). The page will be updated to include some polling/dynamic updates in a future PR.

beautiful <3


[python-updates] 2023/12/02 major updates (python312Packages, pythonRuntimeDepsCheckHook)

This is a bulk update of python packages, that includes major version bumps.
TODO

[x] pythonRuntimDepsCheckHook (see #270457)
[x] Recurse into python312Packages, stop recursing into python310Packages
[x] Prune SETUPTOOLS_SCM_PRETEND_VERSION
[x] Review and merge staging changes on the project board
[x] Re-review changes and consider them for merge (ETA: 2023-12-02, 12:00+ UTC)
[x] Run bulk updater (ETA: 2023-12-02, 21:00+ UTC)
[x] Start evaluation

Once the evaluation has finished, jobs will start building and breakage can be reviewed over at https://hydra.nixos.org/jobset/nixpkgs/python-updates.
Additionally, a review report will appear at https://malob.github.io/nix-review-tools-reports.
Known Issues:

[x] meson-python on python312 depends on https://github.com/NixOS/nixpkgs/pull/268583
[x] numpy 1.26.2 still uses distutils in its buildsystem, needs research which commits we need to backport

Latest eval report
https://shells.darmstadt.ccc.de/~hexa/66.html

Report for the latest eval on my private hydra, if someone wants to dig in.
https://shells.darmstadt.ccc.de/~hexa/55.html

@mweinelt Can you restore my playwright change?

@dotlambda Sorry, apparently it went missing during the last rebase. Pulled 71a4231 from the reflog, PTAL.

Latest eval report: https://shells.darmstadt.ccc.de/~hexa/63.html
sqlalchemy was flaky on my hydra builders and I restarted it five times, it has now succeeded.

Latest eval report: https://shells.darmstadt.ccc.de/~hexa/64.html

@fabaff elasticsearch does not build like that, and it is at the same version as elasticsearch8, so having both packages is rather pointless.

Latest eval report: https://shells.darmstadt.ccc.de/~hexa/66.html

@fabaff elasticsearch does not build like that, and it is at the same version as elasticsearch8, so having both packages is rather pointless.

As far as I remember was elasticsearch8 introduced when elasticsearch was still at 7.x. Would make sense to remove one.
Sorry for the new build failure. Will fix c899467.

Makes sense. But I think now that elasticsearch has been on 8.x we should only keep one and update all references. Can you take care of that?

Latest eval report: https://shells.darmstadt.ccc.de/~hexa/70.html
Also started linking them in the top post.

Did a rebase to resolve all the conflicts introduced by the PR that set explicit format on master. Also, Python 3.12.1 arrived in the meantime. Tried to move most conflicting packages to PEP517 builds, but I certainly failed here and there, we'll see.
Will trigger another eval now, but it will probably take a day until I can give feedback.

Disabled one more racy test in sphinx, which shadows many builds in https://shells.darmstadt.ccc.de/~hexa/77.html.

https://shells.darmstadt.ccc.de/~hexa/80.html
watchfiles has a test that times out after 10s, so it is a false-positive here.

My hydra has finally caught up again. Latest eval includes everything up to and including the yarl 1.9.3 bump.
https://shells.darmstadt.ccc.de/~hexa/81.html

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/a-tale-of-getting-stuck/36731/2

https://shells.darmstadt.ccc.de/~hexa/85.html
The scipy failure was transient. The remaining issues are mostly valid.

@dotlambda I reverted pytest-asyncio for now, 0.23.0 seems to have introduced quite some regressions.

https://shells.darmstadt.ccc.de/~hexa/93.html

Latest eval: https://shells.darmstadt.ccc.de/~hexa/97.html
Xapian does build on the two machines I have locally, just fails on the machines connected to my hydra instance.

❓ babel 2.14.0 was released on Dec 12. What would it take to include that release in this update?

Thank you, @mweinelt, for updating babel to 2.14.0 in this PR, much appreciated! 😃

2884f6262ba5638254c6751bb8aa90cdacf34a78 added a few duplicate entries, caused evaluation failures like:
       error: duplicate formal function argument 'setuptools'

       at /mnt/archive/big/git/nixpkgs-staging-next/pkgs/development/python-modules/aioconsole/default.nix:8:3:

            7| , pythonOlder
            8| , setuptools
             |   ^
            9| }:

Proposed fix as:

[] python3Packages.aioconsole https://github.com/NixOS/nixpkgs/pull/275797:

Bisect says 536b7d10392b57a40f2a005f5dfc90e1744c25cf python311Packages.pytest: clean up deps, expose testing extra broke libei in staging-next:
$ nix build --no-link -f. -L libei
...
libei> Program python3 (attr, jinja2) found: NO modules: jinja2
libei> proto/meson.build:17:15: ERROR: python3 is missing modules: attr
libei> A full log can be found at /build/source/build/meson-logs/meson-log.txt

On mobile right now, but a fix was referenced in the staging-next PR.

pythonPackages.pyosmium no longer builds with these upgrades due to it trying to patch something already patched in the latest version. Created https://github.com/NixOS/nixpkgs/pull/281389 to fix it.

@mweinelt , I found this commit merged as a part of this PR updating python3Packages.rasterio to version 4 which doesn't exist. Package with this change doesn't even build ! It looks very suspicious to me !

This should have only been included if they didn't mark that tag as a pre-release. Looks like it was already reverted but the forced update of all packages will sometimes get these errors propagating to us.

although, looked at that branch... and it's from 9 years ago, not sure why it did get included.... the release metadata should be getting fetched from github.

We arrive at the following using https://api.github.com/repos/rasterio/rasterio/releases and because we determine the highest version in _determine_latest_version.
print(_get_latest_version_github("python311Packages.rasterio", "rasterio", "", "1.3.8", "major"))
('4', '07j1fba1jm55qby0ljxmm983n229qgarjdm9gwyfzdq4cag0bvb0', 'release-test-')

xformers upgrade is broken here:
https://github.com/NixOS/nixpkgs/pull/271586/commits/5dde5f31da583f36e7f79d0b9177b9faa8662f0a
Version 0.03 exists, but this is a typo in upstream repository:

And in fact, xformers version is downgraded here
0.0.22.post7 => 0.03
Version 0.0.22.post7 is much newer:


get_coord_shares() issue

Hi,
I'm using the get_coord_shares() function to detect the coordinated sharing behavior. And the data size of Crowdtangle shares is 142k. The memory of my computer is 16G which not work for this data size. So I create a VM on google cloud. First, I try a VM of 16 CPUs and 128G memory. But it don't enough for this 142k shares data whether enable parallel processing or not. Then I increase the VM size to 32 CPUs and 256G memory. Once again, the  parallel processing don't work. I want to ask: is such issue  normal?

Hi :)
I don't have specific experience with gcloud but on aws parallel processing tends to crash. My guess is that it may be an issue with virtual machines.
One more thing, we recently added a new parameter to get_ctshares to avoid getting the historical posts engagement from CrowdTangle. In my experience this drastically reduces the amount of memory requested.

Yes, the parallel processing on google cloud also tends to crash.

Thanks. And here I have another question. Under what kinds of conditions, the coordination interval from estimate_coord_interval will be automatically set to 1 secs. The log.txt file report the Warning: with the specified parameters p and q the median was 0 secs. The coordination interval has been automatically set to 1 secs.


Missing "Move a Partitioned Table"  in Chinese Docs

Page
https://docs.alluxio.io/os/user/stable/cn/compute/Hive.html
Summary
The method of moving the partition table path to Alluxio is missing in the Chinese document

please assign to me ,I will fix the docs
https://github.com/Alluxio/alluxio/blob/master/docs/cn/compute/Hive.md

Hey Steven, many thanks for opening this issue!  Assigned to you and looking forward to seeing your new doc!  Thanks!


Wiki update: install with scoop (package manager)

Scoop is a command-line installer for windows that is well-suited to managing portable apps like this one. Scoop users can install the app from my scoop bucket.
You can add a note to the wiki about installing with scoop, which only requires a couple of commands:
scoop bucket add xrtools "https://github.com/babo4d/scoop-xrtools"
scoop install tts-voice-wizard

The scoop installation also creates a start menu shortcut, recommends the user to install VB-CABLE, and provides instructions on how to install the .NET desktop runtime dependency with scoop:
> scoop info tts-voice-wizard
...
...
Suggestions : extras/windowsdesktop-runtime-lts
Notes       : Some features require a virtual audio cable like VB-CABLE <https://vb-audio.com/Cable/>
              Requires .NET Desktop Runtime 6.0. To install with scoop:
                scoop install sudo
                sudo scoop install windowsdesktop-runtime-lts

I have submitted the manifest to the scoop Extras repository (https://github.com/ScoopInstaller/Extras/pull/11918) which would further simplify installation and improve discoverability.

Package was accepted into the extras bucket so instructions can be simplified to:
scoop install extras/tts-voice-wizard

added to readme as alternative installation method
https://github.com/VRCWizard/TTS-Voice-Wizard/commit/287b1b968ee40854b7b0802d14798a95e924e40b


fix malformed codecov.yml

the section under coverage: was meant to be indented

[Current coverage][cc-pull] is 48.95%

Merging [#935][cc-pull] into [master][cc-base-branch] will decrease coverage by 9.62%

28 files (not in diff) in ...y/helios/cli/command were modified. more

Misses +154
Partials +76
Hits -230

7 files (not in diff) in ...m/spotify/helios/cli were modified. more

Misses +27
Partials +23
Hits -50

12 files (not in diff) in ...otify/helios/testing were modified. more

Misses +13
Partials +83
Hits -96

3 files (not in diff) in ...cescommon/statistics were modified. more

Misses +6
Partials +1
Hits -7

18 files (not in diff) in ...scommon/coordination were modified. more

Misses +31
Partials +51
Hits -82

12 files (not in diff) in ...elios/servicescommon were modified. more

Misses +37
Partials +19
Hits -56

4 files (not in diff) in ...helios/rollingupdate were modified. more

Misses +6
Partials +13
Hits -19

5 files (not in diff) in ...ios/master/resources were modified. more

Misses +32
Hits -32

9 files (not in diff) in ...potify/helios/master were modified. more

Misses +79
Partials +22
Hits -101

27 files (not in diff) in ...spotify/helios/agent were modified. more

Misses +76
Partials +69
Hits -145

@@             master       #935   diff @@
==========================================
  Files           271        271
  Lines         12759      12759
  Methods           0          0
  Messages          0          0
  Branches       1644       1644
==========================================
- Hits           7473       6246   -1227
- Misses         5286       6038    +752
- Partials          0        475    +475

Powered by Codecov. Last updated by [0f7e980...d619f7a][cc-compare]
[cc-base-branch]: https://codecov.io/gh/spotify/helios/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/spotify/helios/compare/0f7e980b25db17a103d7f40d7d4b2a1eeb88d2d1...d619f7afde109f1ca98274d6858def0ed871f492
[cc-pull]: https://codecov.io/gh/spotify/helios/pull/935?src=pr


Testing errors

Traceback (most recent call last):
File "info.py", line 20, in
print(devsim.get_parameter(name="info"))
UnicodeEncodeError: 'ascii' codec can't encode character '\xa9' in position 25: ordinal not in range(128)
This error comes from the value returned by get_parameter(name="info")
Traceback (most recent call last):
File "laux1.py", line 93, in
load_devices(file="trimesh3.msh")
devsim_py3.error: Could not open file trimesh3.msh
I do not see that file there, but a trimesh2.msh
Traceback (most recent call last):
File "mos_2d.py", line 63, in
devsim.solve(type="dc", absolute_error=1.0e30, relative_error=1e-5, maximum_iterations=30)
devsim_py3.error: Convergence failure!
Traceback (most recent call last):
File "mos_2d_restart.py", line 16, in
devsim.load_devices(file="mos_2d_dd.msh")
devsim_py3.error: Could not open file mos_2d_dd.msh
I dont see any file like this one.
UnicodeEncodeError: 'ascii' codec can't encode character '\u03c8' in position 149: ordinal not in range(128)
The above exception was the direct cause of the following exception:
Hmm, here the stacktrace is missing.
SystemError: <built-in method flush of _io.BufferedWriter object at 0x7ff23f50da98> returned a result with an error set
The above exception was the direct cause of the following exception:
SystemError: <built-in method flush of _io.BufferedWriter object at 0x7ff23f50da98> returned a result with an error set
The above exception was the direct cause of the following exception:
SystemError: <built-in method flush of _io.BufferedWriter object at 0x7ff23f50da98> returned a result with an error set
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "utf8_2.py", line 92, in
solve( type="dc", absolute_error= 1.0 , relative_error= 1e-10 , maximum_iterations= 30)
SystemError:  returned a result with an error set

To handle the © symbol in the output, it is necessary to have the locale set.  Setting:
export LANG=C.UTF-8

fixes the first issue.  I do not know the most general setting.  But this seems to be one available without having to do locale generation.  https://lintut.com/how-to-set-up-system-locale-on-ubuntu-18-04/

multiprecision enabled with commit 9bdb891c4c488656174b521d9575c6b9097b3f61

the recent commit also fixes utf8_2.py

Some of the tests have a dependency, as can be seen in the CMakeLists.txt file in the testing directory.
set_tests_properties("testing/laux1" PROPERTIES DEPENDS testing/trimesh2)

laux1.py also needs numpy, which I have added to the build script.  so it now runs

mos_2d.py fails and this is probably related to using the SuperLU solver instead of MKL Pardiso.  I will have to investigate this further.  mos_2d_restart2 has a dependency on mos_2d.

An alternative option is to do a build with Anaconda Python, which is packaged with Intel MKL.

Thanks, I improved my Dockerfile accordingly.


Search parameters get overridden on page load

Which project does this relate to?
Start
Describe the bug
export const Route = createFileRoute('/')({
  component: Home,
  validateSearch: z.object({
    step: z.enum(['a', 'b', 'c']).optional(),
  }),
  loaderDeps: ({ search: { step } }) => ({ step }),
  loader: async ({ deps: { step } }) => {
    if (step === undefined) {
      throw redirect({
        to: '/',
        search: ({ step: _, ...search }) => ({ ...search, step: 'a' }),
      })
    }
  },
})

When I navigate to /, it is expected that I get redirected to /?step=a - this works as expected.
However, when I navigate to /?step=b, I get redirected to /, and then subsequently get redirected to /?step=a.
No errors get thrown when I navigate to to /?step=b, which leads me to assume that the search parameters were properly validated by the Zod schema under validateSearch.
It is expected that when I navigate to /?step=b, that I would stay on /?step=b without being redirected to / and subsequently /?step=a.
This bug occurs irrespective of this redirect logic being placed in:

beforeLoad,
loader, or
in component with a useEffect over Route.useSearch({ select: ({step}) => step })

Your Example Website or App
https://stackblitz.com/edit/tanstack-router-txrzyl?file=app%2Froutes%2Findex.tsx
Steps to Reproduce the Bug or Issue

Go to https://stackblitz.com/edit/tanstack-router-txrzyl?file=app%2Froutes%2Findex.tsx
Press Open Preview in new tab and press Connect to project - notice that you get automatically redirected from / to /?step=a.
Try navigate to /?step=b.

Expected behavior
That I stay on /?step=b as it conforms to the Zod schema provided under validateSearch.
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux] macOS
Browser: [e.g. Chrome, Safari, Firefox] Chrome
Version: [e.g. 91.1] Version 126.0.6478.183 (Official Build) (arm64)

Additional context
No response

Just to clarify, I tested to see if this bug can be reproduced on Tanstack Router and it cannot be reproduced. This issue only occurs with Tanstack Start.

working example for router:
https://stackblitz.com/edit/tanstack-router-f9yax9?file=src%2Froutes%2Findex.tsx&preset=node


Add Centos 8 and Ubuntu 20.04

I've had the Centos 8 branch around for a while. Since there's a request for Ubuntu 20.04 I thought I'd add it and open this PR.

Conflicting PR. Removed from build ANSIBLE-ROLES-merge#1173. See the console output for more details.
Possible conflicts:

Upstream changes

meta/main.yml

--conflicts

Given the interest in Ubuntu 20.04 in particular, this might be something worth re-activating with GitHub actions.

Given the interest in Ubuntu 20.04 in particular, this might be something worth re-activating with GitHub actions.


Google search box isn't autofocused

STR:
Open a new tab
Type google.com and press enter
Expected:
Page loads, search box is focused
Actual:
Page loads, nothing appears to be focused

I think this would be fixed if we automatically give web content focus after navigating. Reloading a google.com page focuses the search bar as expected

Reloading with web contents focused that is


Package warnings with .NET 9

 C:\Program Files\dotnet\sdk\9.0.100-preview.4.24267.66\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(221,5): warning NU5132:
      The zip format supports a limited date range. The following files are outside the supported range:
      'tools/linux_arm64/protoc' changed from '12/31/1979' to '1/1/1980'

The protoc zip file executable includes a bogus timestamp, I created an issue https://github.com/protocolbuffers/protobuf/issues/18232


[WIP][SQL][STREAMING][TEST] Fix flaky tests in StreamingQueryListenerSuite

This work has largely been done by @lw-lin in his PR #15497. This is a slight refactoring of it.
What changes were proposed in this pull request?
There were two sources of flakiness in StreamingQueryListener test.

When testing with manual clock, consecutive attempts to advance the clock can occur without the stream execution thread being unblocked and doing some work between the two attempts. Hence the following can happen with the current ManualClock.

+-----------------------------------+--------------------------------+
|      StreamExecution thread       |         testing thread         |
+-----------------------------------+--------------------------------+
|  ManualClock.waitTillTime(100) {  |                                |
|        _isWaiting = true          |                                |
|            wait(10)               |                                |
|        still in wait(10)          |  if (_isWaiting) advance(100)  |
|        still in wait(10)          |  if (_isWaiting) advance(200)  | <- this should be disallowed !
|        still in wait(10)          |  if (_isWaiting) advance(300)  | <- this should be disallowed !
|      wake up from wait(10)        |                                |
|       current time is 600         |                                |
|       _isWaiting = false          |                                |
|  }                                |                                |
+-----------------------------------+--------------------------------+

Second source of flakiness is that the adding data to memory stream may get processing in any trigger, not just the first trigger.

My fix is to make the manual clock wait for the other stream execution thread to start waiting for the clock at the right wait start time. That is, advance(200) (see above) will wait for stream execution thread to complete the wait that started at time 0, and start a new wait at time 200 (i.e. time stamp after the previous advance(100)).
In addition, since this is a feature that is solely used by StreamExecution, I removed all the non-generic code from ManualClock and put them in StreamManualClock inside StreamTest.
How was this patch tested?
Ran existing unit test MANY TIME in Jenkins

Test build #67087 has started for PR 15519 at commit 6fdbae3.

@lw-lin  please take a look.

Test build #3358 has started for PR 15519 at commit 6fdbae3.

Test build #3359 has started for PR 15519 at commit 6fdbae3.

Test build #3358 has finished for PR 15519 at commit 6fdbae3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #67087 has finished for PR 15519 at commit 6fdbae3.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67087/
Test FAILed.

I have tested enough. There was a single failure in a different flaky test, not in StreamingQueryListenerSuite.

Test build #67101 has started for PR 15519 at commit 4ce3093.

This looks good to me, thanks!

@lw-lin Fixed the bug.

Test build #67104 has started for PR 15519 at commit 3229095.

Test build #67101 has finished for PR 15519 at commit 4ce3093.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67101/
Test FAILed.

Test build #67104 has finished for PR 15519 at commit 3229095.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 class StreamManualClock(time: Long = 0L) extends ManualClock(time)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67104/
Test PASSed.

Merging this to master and branch 2.0