Support non-english text

What and why?
Currently, the word selection algorithm in toipe only supports English ASCII characters. Any other characters (including ASCII special characters will be ignored).
This is not good because the world doesn't only write in English :). Especially for a typing test app which can be used to measure and improve speeds in other languages too.
Once this is implemented, it would also be good to have built-in word lists for more languages (maybe even auto-detect the user's locale and change word list based on it?)
How?
The changes need to be done in RawWordSelector (source code).

Currently, it uses raw bytes (b'a', b'z', etc.) to compare and store characters. This needs to be changed to use the char type.
It tracks starting positions of each character in a fixed length array of 26 characters. This needs to be made more general.
Use unicode lowercase instead of ASCII - https://github.com/Samyak2/toipe/blob/cfba93778029fc078204f52fb9f2149b4831a678/src/textgen.rs#L91
Do not use is_ascii_alphabetic here - https://github.com/Samyak2/toipe/blob/cfba93778029fc078204f52fb9f2149b4831a678/src/textgen.rs#L247

This may require some more changes that I'm not yet aware of.
Please drop a comment if you find any inconsistencies or problems with this idea :)

Some suggestions from the author of terminal-typeracer: https://www.reddit.com/r/rust/comments/tvamfz/comment/i3eva1h/


Fix bug: cmd like find -h would not be recognised as a find cmd

Codecov Report

Merging #270 (12f4482) into master (29b219b) will increase coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #270      +/-   ##
============================================
+ Coverage     59.32%   59.34%   +0.02%
  Complexity      681      681
============================================
  Files           131      131
  Lines          2532     2531       -1
  Branches        268      268
============================================
  Hits           1502     1502
+ Misses          927      926       -1
  Partials        103      103

Impacted Files
Coverage Δ

.../java/tutoraid/logic/parser/FindCommandParser.java
45.45% <0.00%> (+1.97%)
:arrow_up:

Continue to review full report at Codecov.

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


RuntimeError: MultiThreadedAugmenter.abort_event was set, something went wrong. Maybe one of your workers crashed

Hi,
I'm new to deep learning, can anyone please guide me what I'm doing wrong?

Hi,  this is an issue for https://github.com/MIC-DKFZ/batchgenerators


DSEGOG-307 Kill API Instances Cleanly in Echo Ingest Script

This is a small change to improve the Echo ingestion script. It used to not kill the API at the end of the script so the processes needed to be manually killed - the problem would often occur when you launch the API using poetry run and it would complain the address is already in use.
To make this better, the kill function now uses lsof to pinpoint all processes attached to the port used for the API, puts those PIDs into a list and uses the standard library os.kill() to kill them one by one.

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

Project coverage is 84.28%. Comparing base (892aad6) to head (1e54280).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #113   +/-   ##
=======================================
  Coverage   84.28%   84.28%
=======================================
  Files          47       47
  Lines        2425     2425
  Branches      195      195
=======================================
  Hits         2044     2044
  Misses        346      346
  Partials       35       35

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

Just merged main in so the CI passes (safety job was failing)


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Codecov Report

Merging #99 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #99   +/-   ##
=======================================
  Coverage   90.14%   90.14%
=======================================
  Files           1        1
  Lines          71       71
=======================================
  Hits           64       64
  Misses          7        7

Continue to review full report at Codecov.

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


Generate Reference Documentation for kubectl Commands

Signed-off-by: zhuzhenghao<EMAIL_ADDRESS>/kind bug
Generate Reference Documentation for kubectl Commands
FIX issue https://github.com/kubernetes/website/issues/38626

dup of #38697

dup of #38697

See this line :
https://github.com/kubernetes/website/blob/c43f71161e586b5f9da7f178d6b90eb01758e895/static/docs/reference/generated/kubectl/kubectl-commands.html#L1749
This pr fix issue https://github.com/kubernetes/website/issues/38626.
It seems that we have different purposes?

@Zhuzhenghao My bad. I wasn't rebasing the generator. Please check #38697 again.

@tengqm Thanks for checking. I has closed this pr. See u later


gnu(9280)=13050

Constructed a list of length 13047
It contains 13044 groups and 3 sublists
Length of sublists are [ 2, 2, 2 ]
13047<=gnu(9280)<=13050
Runtime of this construction: 18384391 ms (5.11 hrs)
Now checking non-isomorphism of groups in sublists ...
Success! All pairs contain non-isomorphic groups
gnu(9280)=13050
GAP      4.8.3
GrpConst 2.5
Runtime of ConstructAllGroups: 18384391 ms (5.11 hrs)
Returned a list of length 13047 containing 13044 groups and 3 sublists
Length of sublists : [ 2, 2, 2 ]
Runtime to check non-isomorphism of groups in pairs: 2197665 ms (36.62 min)
To maintainers: for new results, add to data/gnudata.g this line:
GNU_SAVE( 9280, 13050, WITH_GC );

gap>
System : Windows Vista

Thank you for submitting new gnu(n). We will recalculate it and add to the database if we get the same result.
Checklist for the reviewer:

[ ] checked and assigned labels "new (n<50000)" or "recomputation", if needed
[ ] set "replication needed" label (unless it starts immediately)
[ ] changed it to "replication in progress" label when the replication has been started
[ ] changed it to "replicated" after successful replication review
[ ] reproducible value of gnu(n)
[ ] no essential runtime differences
[ ] sufficient level of technical details

Checklist for the maintainer:

[ ] correct arguments of command to store data
[ ] correct location of new line in the data file
[ ] mention submitter and reviewer in the commit message
[ ] Close corresponding issue from the commit message

gnu(9280)=13050
GAP      4.8.3
GrpConst 2.5
Runtime of ConstructAllGroups: 11687549 ms (3.25 hrs)
Returned a list of length 13047 containing 13044 groups and 3 sublists
Length of sublists : [ 2, 2, 2 ]
Runtime to check non-isomorphism of groups in pairs: 1710195 ms (28.5 min)
Replicated by @alex-konovalov on Ubuntu 16.04 on Azure cloud standard DS13 v2 instance (8 cores, 56 GB memory)
To maintainers: for new results, add to data/gnudata.g this line:
GNU_SAVE( 9280, 13050, WITH_GC );


Create unittests and automate testing using travis.

Create unittests and automate testing using travis.

Unit testing support has been added.


[Question] - 2.0-wip - Is it possible to have "hide-on-phones" class for responsiveness ?

I was just wondering if it would be possible to have a class that hides the binded div element when the browser is re-sized to lower resolution on desktop or the page is rendered on a mobile browser, like the Zurb's Foundation "hide-on-phones" class ?

Perhaps in the future, but not right now. 2.0.0 is our first pass at getting responsive features in Bootstrap and we're close to locking it all down for testing. We'll re-evaluate this post launch of 2.0.


[BUG] fsck of encrypted volume hangs indefinitely until killed

Describe the bug
It seems that sometimes when encrypted volumes crash, longhorn attempts to fsck and it stays there for eternity.
Perhaps it is trying to fsck an hanged/dead volume and the command stays waiting for I/O indefinitely? Not sure.
Since fsck hangs indefinitely, the volume cannot be mounted and it requires a manual kill of the fsck process, dmsetup remove, etc...
To Reproduce
No idea.
Expected behavior
fsck does not hang indefinitely.
Support bundle for troubleshooting
TODO
Environment

Longhorn version: 1.6.1
Impacted volume (PV):
pvc-86b32947-c8d6-43de-a8b5-fa01984f1447, pvc-73352bd5-ef36-4e48-b9c9-65a384e8efdb, pvc-178dfff4-faf3-44d6-8ba3-5519d1e9c833
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.27.13+k3s1

Number of control plane nodes in the cluster: 1
Number of worker nodes in the cluster: 2

Node config

OS type and version: Fedora 39 Workstation
Kernel version: Linux shiverpeaks 6.8.7-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Apr 17 19:35:11 UTC 2024 x86_64 GNU/Linux
CPU per node: 4
Memory per node: 32GB / 4GB / 4GB
Disk type (e.g. SSD/NVMe/HDD): HDD
Network bandwidth between the nodes (Gbps): don't know

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal
Number of Longhorn volumes in the cluster: around 20 or more

Additional context

Hung fsck processes
davidjf@shiverpeaks ~> ps aux | grep fsck | grep -v grep
root       16472  0.0  0.0   8112  2356 ?        S    Apr28   0:00 fsck -a /dev/mapper/pvc-86b32947-c8d6-43de-a8b5-fa01984f1447
root       16477  0.0  0.0  10128  2484 ?        S    Apr28   0:00 fsck.ext4 -a /dev/mapper/pvc-86b32947-c8d6-43de-a8b5-fa01984f1447
root       21559  0.0  0.0   8112  2428 ?        S    Apr28   0:00 fsck -a /dev/mapper/pvc-73352bd5-ef36-4e48-b9c9-65a384e8efdb
root       21592  0.0  0.0  10144  2360 ?        S    Apr28   0:00 fsck.ext4 -a /dev/mapper/pvc-73352bd5-ef36-4e48-b9c9-65a384e8efdb
root     3182396  0.0  0.0   8112  2388 ?        S    09:32   0:00 fsck -a /dev/mapper/pvc-178dfff4-faf3-44d6-8ba3-5519d1e9c833
root     3182415  0.0  0.0   9988  2640 ?        S    09:32   0:00 fsck.ext4 -a /dev/mapper/pvc-178dfff4-faf3-44d6-8ba3-5519d1e9c833

I killed the fsck processes and tried to repeat one of them just to see what happens and i get an immediate error which is puzzling:
fsck from util-linux 2.39.4
fsck.ext2: Input/output error while trying to open /dev/mapper/pvc-86b32947-c8d6-43de-a8b5-fa01984f1447
/dev/mapper/pvc-86b32947-c8d6-43de-a8b5-fa01984f1447:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

i assume that the volume is in a crashed state so that's why i get this error. if i dmsetup remove it and scale pods it should come back to normal. just wonder why it stays stuck though.

For this specific case, after manually killing the stuck fsck processes longhorn detached and re-attached the volumes and they became healthy again and attached to pods with no problems, so that is nice. Just not good that fsck hangs and needs to be killed though.


HTML minification breaks Angular 2

Angular 2 does not seem to like:
ngFor vs ngfor
routerLink vs routerlink

...
 vs
...

These are modifications that https://www.npmjs.com/package/gulp-minify-html does by default via https://github.com/Swaagie/minimize.
The behavior with quotes can be changed but not that with case sensitivity

This is known: https://github.com/angular/angular/issues/5789

Apparently the solution proposed by the Angular team will be an offline template compiler, meaning that we'll have to branch depending on whether the client project uses Angular or not

Issue to keep an eye on: https://github.com/Swaagie/minimize/issues/74

For now, a workaround is to use the new option to disable HTML minification.
gulpfile.babel.js:
options.minifyProductionHTML = false; // HTML minification is not supported by Angular 2 anymore: https://github.com/dsebastien/modernWebDevBuild/issues/67

I had same problem with minify Angular2.
It seem has been fix when bump minimize version from 1.7.4 to 1.7.5 (now is 1.8.1?)  and added the "dom" option.
dom: {
    lowerCaseAttributeNames: false
}

Thanks for the tip @yizhan I'll try this out!


No "anchors" key in evaluation UDPipe file

I'm trying to add UDPipe information into the evaluation data using preprocess_eval.py.
This line
https://github.com/DreamerDeo/HIT-SCIR-CoNLL2019/blob/9bc3c0727c13aac72e71ae7bf48cc195f481bffa/toolkit/preprocess_eval.py#L10
looks for the "anchors" key under a UDPipe node. But it seems that the evaluation/udpipe.mrp file doesn't have this "anchors" key under nodes. Do you know what is happening? companion/udpipe.mrp does have that key though.

Hi,
We have checked our evaluation data. The anchors information is listed in evaluation/udpipe.mrp.
And we found the overview and release history in evaluation/README.udpipe.txt:
Overview

This directory contains a re-release of the morpho-syntactic compantion trees
for the MRP 2019 shared task, i.e. tokenized and syntactically parsed parser
inputs.  A re-release of this part of the evaluation package was required to
augment the companion trees with anchoring information, i.e. character start
and end indices into the original input string.

Release History

[Version 1.1; July 15, 2019]

Re-release of companion trees only, now including anchoring.

[Version 1.0; July 1, 2019]

First release of MRP 2019 training data in all frameworks.

It seems that you need to update the evaluation data to v1.1.

That worked, thank you!


[bug] Wrong arguments order causes model always to be null

https://github.com/ahlwong/dakota-cassandra/blob/873c858c31ebec9fb8d0d6c5f691a9518eaf167d/lib/model.js#L1456

Good catch!
Fixed here:
https://github.com/ahlwong/dakota-cassandra/commit/a8fa5a14e738953a9554bf4a05c36f3f8e04f210


Itcss import docs

This is branched off from https://github.com/buildit/gravity-ui-sass/pull/192 and contains additional docs for importing Gravity SASS relating to the changed merged here https://github.com/buildit/gravity-ui-sass/pull/194

I've done some rebasing voodoo on the build-api branch, so will manually do the same for this one now.

@james-nash ready to merge right?

@danbull Yup. Good to go now :-)

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


My blog for Hacktoberfest 2021 submission

Checklist

Please note that in case of below checklist not updated accordingly, the maintainers have the right to immediately close your pull request.

[ ] You created a branch from dev branch.
[ ] You PR is raised on dev branch and not onmaster.
[ ] Blog follows Blog Guidelines.
[ ] You have read the Contribution Guidlines before creating this PR.
[ ] Checked for any duplicate blog entry.
[ ] Checked for all grammatical errors in the blog.
[ ] You have not published the blog content anywhere else on the internet on platforms like medium, dev.to etc.
[ ] The content is not copy-pasted from anywhere else on the Internet.

Description of change

Author Details for Blog Post Entry

id: mayank chaudhary
bio: I'm a final-year student at Maharaja Surajmal Institute of Technology, New Delhi pursuing Electronics and
Communications Engineering. I exhibit an eagerness to learn new things and adapt. Being a technology
enthusiast, I love to explore new technologies and contribute to different writing/blogging platforms. I'm
also involved with college societies and in extracurricular activities. Currently working on enhancing my
analytical skills.
github: mayankchaudhary26
twitter: rado_mayank


Individual Dev Branches

Each person working on this project must create their own development branch. This branch will be the only place this person works from, and will be used for all merge requests. Please follow the below nomenclature for consistency:
firstInitiallastName_dev
As an example, my branch will be called: mweale_dev. m = firstInitial, weale = lastName. Everyone will have "_dev"

How do you feel about feature branches?
Many big merge conflicts are results of long-living branches. If you work in your own branch for several days or even weeks, the risk is high that someone else changes parts of the code you have touched in another branch. That would lead to merge conflicts.

A feature branch could be nav-bar or footer. When the feature is done and after a pull request is merged it could be closed or deleted. Its a really good way to help avoid merge conflicts.

@robertjallen - I think that is a great idea. Here are a couple of my thoughts:

Personal Branches - These would be used for when you are developing your own webpage. In theory, nothing you do here should be connected to anyone else's work so we should not have to worry about merge conflicts.
Feature Branches - I am cool with using these, however communication is key here. Many parts of a website are dependent on others. So it is possible two feature branches have some overlap and that each developer is talking to the other to make sure we avoid those merge conflicts. I think this is doable, but something we will have to keep top of mind. Maybe we only work on very small features.

How does that sound?

Sounds perfect 👌
Feature branches for while developing a particular component or Feature.
(Communicate effectively)
Personal branches for adding content to a personal page.
On Tue, Nov 17, 2020, 1:39 PM Matt Weale<EMAIL_ADDRESS>wrote:

@robertjallen https://github.com/robertjallen - I think that is a great
idea. Here are a couple of my thoughts:

Personal Branches - These would be used for when you are developing
your own webpage. In theory, nothing you do here should be connected to
anyone else's work so we should not have to worry about merge conflicts.
Feature Branches - I am cool with using these, however
communication is key here. Many parts of a website are dependent on others.
So it is possible two feature branches have some overlap and that each
developer is talking to the other to make sure we avoid those merge
conflicts. I think this is doable, but something we will have to keep top
of mind. Maybe we only work on very small features.

How does that sound?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Underdog-Devs/website/issues/27#issuecomment-729123842,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE43Z6MN7SHKPUWUA74MFQLSQK7O3ANCNFSM4TXTAEHQ
.


Search enhancements.

More test cases for 'searching' functionality.
Default to using partner keys for android instead of iPhone.

Coverage increased (+0.5%) to 99.085% when pulling 78f29634ef9192ed41239245e5ed2b86be47ded0 on jcass77:enhance/searching into 639f513dd16e29405655c3971c198f3e8bcda588 on rectalogic:develop.

Coverage increased (+0.5%) to 99.085% when pulling bf4bc4b850353578f605bad17f2cc3a38e78b2c8 on jcass77:enhance/searching into 639f513dd16e29405655c3971c198f3e8bcda588 on rectalogic:develop.


Missing support for path prefixes during import to Anchore API

This means that Syft's import feature does not work with the standard way we deploy Enterprise via Helm, where the API paths should be prefixed with /v1/. For details on the chart config, see https://github.com/anchore/anchore-charts/blob/8ff7bc108290ce07a6f2d92db5aa1be11985dc23/stable/anchore-engine/templates/enterprise_ui_configmap.yaml#L20
We're finding that users are trying to specify path prefixes with the host parameter (e.g. -H on the CLI), such as https://mydeployment.example.com/v1.
At a minimum:

We need a way to allow the user to specify path prefixes as they tell Syft where their deployment is located (we should not assume that the user's API is deployed at a root path for a hostname).
We need to ensure users have a smooth interaction with Anchore Enterprise by default.

This is a combination of a specific ingress config (combined UI and API, which isn't required, you can use 2 ingresses), and Anchore's service path optimization that makes /v1/ optional by rewriting /v1/ as a prefix internally. The API definition itself is versioned with /v1 prefix for that version of the API.
But supporting arbitrary prefixes on the routes will help general compatibility with various ingress/routing options between the system and syft.

This is a combination of a specific ingress config (combined UI and API, which isn't required, you can use 2 ingresses), and Anchore's service path optimization that makes /v1/ optional by rewriting /v1/ as a prefix internally. The API definition itself is versioned with /v1 prefix for that version of the API.
But supporting arbitrary prefixes on the routes will help general compatibility with various ingress/routing options between the system and syft.


Update steampipe-plugin-sdk to v1.3.1. Closes #44

Integration test logs

Logs
N/A

Example query results

Results
N/A

The sdk has been updated to the 1.5.0 a few weeks ago.

Closing this PR, since the SDK has been updated to v1.5.0 as part of https://github.com/turbot/steampipe-plugin-github/commit/58b92a9024335856f667181a93f1b828a49e9001


'allow_user_specified_id' config doesn't work

Describe the bug
Can't create an object with given id when allow_user_specified_id configured.
config := make(map[string]interface{})
config["allow_user_specified_id"] = true
cli, err := edgedb.CreateClient(ctx, opts)
cli = cli.WithConfig(config)

When I try to insert an object into table, an error occurred:
QueryError: cannot assign to id
Hint: consider enabling the "allow_user_specified_id" configuration parameter to allow setting custom object ids

Reproduction
Include the code that is causing the error:
insert Something {
  id := <uuid>"00000000-0000-0000-0000000000"
}

Expected behavior
Object should be created with given uuid.
Versions (please complete the following information):

OS : macOS Monterey (ver.12.6)
EdgeDB version: "2.7+784cf0b"
EdgeDB CLI version: "EdgeDB CLI 2.2.6+7eabbf9"
edgedb-go version: "github.com/edgedb/edgedb-go v0.13.0"
Go version: go version go1.18.1 darwin/arm64

Additional context
This is occurred by: https://github.com/edgedb/edgedb-go/blob/723df88642ba4e19d55989d65e5628c08ec4e2b4/internal/client/transaction.go#L158
which is mis-ordered arguments. newQuery function signature is:
https://github.com/edgedb/edgedb-go/blob/723df88642ba4e19d55989d65e5628c08ec4e2b4/internal/client/query.go#L63-L69
so I'd tried with:
diff --git a/internal/client/transaction.go b/internal/client/transaction.go
index e754567..fc390ed 100644
--- a/internal/client/transaction.go
+++ b/internal/client/transaction.go
@@ -155,7 +155,7 @@ func (t *Tx) Execute(
 	cmd string,
 	args ...interface{},
 ) error {
-	q, err := newQuery("Execute", cmd, args, t.capabilities1pX(), nil, t.state)
+	q, err := newQuery("Execute", cmd, args, t.capabilities1pX(), t.state, nil)
 	if err != nil {
 		return err
 	}

and it worked.

Thanks for pointing this out @junhee-yoo!

this is fixed in v0.13.2

Hi, I'd faced this problem again.
I guess:
https://github.com/edgedb/edgedb-go/blob/014bff79e0ac2fab4886fb1c15c669dea19edcfc/internal/client/transaction.go#L88
this should be fixed as previous one.

@fmoor Sorry for lack of information. And sorry for make you confuse. Maybe I should have made another issue instead of write a comment on closed issue.
According to my investigation, the issue does not come from your previous fix transaction.go:158. It comes from transaction.go:88.
Previously, I got that code link from master branch, but here I got code from v0.13.3 branch:

line number
code from tag v0.13.3

L88
https://github.com/edgedb/edgedb-go/blob/20ecc5e449586f96e546cdfd441db7d24819a703/internal/client/transaction.go#L88

L158
https://github.com/edgedb/edgedb-go/blob/20ecc5e449586f96e546cdfd441db7d24819a703/internal/client/transaction.go#L158

I have no idea why this occurs the issue in v0.13.3, because it didn't happen with v0.13.0.
But it seems the arguments order is wrong for newQuery() as previous(L158) one and after I fixed it manually, it worked.
Sorry again, and thanks for taking an interest. 👍

Ok thanks! I didn't notice that that was a different line. I pushed a fix and published v0.13.4


Add current canvas and all time pixel counts to the mod lookup

Adds too many requests to the database in PacketHandler.java.

This pull request is a mess please excuse my extreme badness with git :)

Mess commits can be squashed. Good job 😁


indexer: consider using a "proper" graph database query langage

we are currently using a home grown graph implementation to build the state in the indexer. this was fine while the queries where simple, but as we desired more complex graph queries, this is becoming a bit large to maintain.
there are many existing graph databases that could be a good fit, and offer better performance, flexibility, and stability ... or even just trusty postgres.

not a db itself, but this looks like it might be a good fit: https://github.com/ent/ent

can be backed by sql.DB interface for persistance, but can use in-memory sqlite short term
has basic, but more mature than our homegrown, query stuff
has support for gqlgen (which the api uses)

considered it... but current plan is to have something that works in client


Make ArgoCd aware of changes

EDIT:
proper way to do this is using webhooks:
https://argo-cd.readthedocs.io/en/stable/operator-manual/webhook/

We have webhooks now, and we are also working on talking directly to the Argo CD api.
webhooks: https://github.com/freiheit-com/kuberpult/blob/main/charts/kuberpult/values.yaml.tpl#L111


Refactor element explorer to work with selenium-webdriver 3

This implementation now relies mostly on promises explicitly,
so the control flow is only used to add one large task to the queue.
This should pave the way for the eventual removal of the control flow,
as well as getting element explorer to work immediately.
Note that there are several missing items and TODOs at the moment:

[x] Needs rebasing on top of current beta branch
[x] This is only for elementExplorer, I haven't yet fixed browser.pause()
[x] There's some clean-up todos to make the breakpoint more robust
[x] Need to ensure that the test suite for interactive tests is still working and can still break
[x] Need to ensure that error cases (e.g. bad syntax in a statement) are handled gracefully

We can greatly simplify our code by making a change to separate the 'step by execute' and 'enter repl' debuggers more clearly. This would mean that if you do browser.pause you can no longer enter a repl loop - but you can do that by instead placing browser.enterRepl in your code.
I'll go ahead and implement this to show how much easier it is to reason about. I've seen many users not know they can get into a repl from browser.pause anyway, so I think we can use this as an opportunity to improve clarity and docs.

One more item to fix - the tab completion for the explorer is currently broken.

This is now ready for review!
I'm also considering aliasing browser.enterRepl() as browser.explore(). Thoughts?

Comments addressed, and rebased on top of beta. PTAL!

Rebase successful! Just waiting for CI to be green now.


Analyze Business seasonals (HourOfWeek and derivatives)

For business hourly data the signal may be better analyzed by crossing dayOfWeek and Hour.
This can be made by dividing the work week in hours and analyzing HourOfWeek.
HourOfWeek = dayOfQWeek * 24 + Hour
Some patterns like week-end, night, sunrise, AM , PM, Monday morning, etc can be captured this way and improve the explainabiity if the model.

A usual pattern like 'morning' is not really well defined. Besides the original HourOfWeek seasonal , we will define increasing discrete patterns covering every two hours, every three hours, etc.
The morning pattern can be approximated by something line the first six or eight hours according to the business.

class eDatePart(IntEnum):
    Second = 1
    Minute = 2
    Hour = 3
    DayOfWeek = 4
    DayOfMonth = 5
    MonthOfYear = 6
    WeekOfYear = 7
    DayOfYear = 8
    HourOfWeek = 9
    TwoHourOfWeek = 10
    ThreeHourOfWeek = 11
    FourHourOfWeek = 12
    SixHourOfWeek = 13
    EightHourOfWeek = 14
    TwelveHourOfWeek = 15

TwoHourOfWeek =  dayOfWeek * 12 + Hour // 2
ThreeHourOfWeek =  dayOfWeek * 8 + Hour // 3
FourHourOfWeek =  dayOfWeek * 6 + Hour // 4
SixHourOfWeek =  dayOfWeek * 4 + Hour // 6
EightHourOfWeek =  dayOfWeek * 3 + Hour // 8
TwelveHourOfWeek =  dayOfWeek * 2 + Hour // 12


dependency is out of date

The zookeeper cookbook was bumped to 3.0.0, however the metadata in this cookbook is still referencing ~> 2.0
This means that I can't have my wrapper cookbook point to 3.0.0 if I want it to install both zookeeper and exhibitor

As outlined in issue #9 the dependencies are conflicting.
An alternative fix would be to backport the fix from the 3.0.0 cookbook back to the 2.x.x cookbook.

It strikes me that maybe that backport and re-versioning would be a safer way to do this resolving #9 here (maybe that becomes a major version bump?). I got bushwacked today by this bug when I had to rebuild a cluster with 3.4.7 being out and my solution at the moment involves chef-rewind and prayer. :(

I’ll get this sorted today.

@eropple the issue there is that would potentially upgrade people’s deployed instances of ZooKeeper, which is potentially breaking.
Fix for this incoming.


Now we use notebook - we need to allow for jupyter_server

In a slack thread @yuvipanda clarified that we are starting all user servers using the classical notebook server by configuring this (see JupyterHub docs):
https://github.com/2i2c-org/infrastructure/blob/a9d8816bb423cb3117ef94935f303e4afd1cc9ee/helm-charts/basehub/values.yaml#L181-L186
In this support ticket from the temple hub we conclude that a modern jupyter/datascience-notebook image won't work with JupyterLab any more, where the notebook server presents 404 Not found when accessing /lab, because of this:
[I 2023-02-07 06:17:06.501 SingleUserNotebookApp mixins:609] Starting jupyterhub single-user server version 3.1.1
[I 2023-02-07 06:17:06.502 SingleUserNotebookApp mixins:623] Extending notebook.notebookapp.NotebookApp from notebook 6.5.2

# ...

[W 2023-02-07 06:17:07.775 SingleUserNotebookApp serverextension:13] Loading JupyterLab as a classic notebook (v6) extension.
[C 2023-02-07 06:17:07.775 SingleUserNotebookApp serverextension:18] You must use Jupyter Server v1 to load JupyterLab as notebook extension. You have v2.2.1 installed.
    You can fix this by executing:
        pip install -U "jupyter-server<2.0.0"

What to do
What we should do no matter what

We should overview all things we do that is notebook or jupyter_server specific.
We should plan what we to communicate to users managing user environment images

Four strategies to consider

We can ask users to pin jupyter_server<2, but that will come back and haunt
us when we need them to have jupyter_server>=2 now or because they request features that only v2 supports.
We can start overriding to JUPYTERHUB_SINGLEUSER_APP=jupyter_server.serverapp.ServerApp for individual hubs, and along with that also updating configuration of notebook classic to configuration of jupyter_server
We can start overriding to JUPYTERHUB_SINGLEUSER_APP= for individual hubs, and along with that make sure to provide configuration to both notebook classic and jupyter_server
We can remove our configuration forcing notebook in the basehub chart

No matter what we choose, we can introduce breaking changes here as users may include their own configuration of notebook or jupyter_server specifically. So I think we can only start a transition of individual hubs and communicate ahead when we look to make a certain transition here ahead of time if we are to introduce a breaking change.
I suggest we trial with either 2 or 3, then we communicate that at a certain date we are going for 4 along with technical notes on what they need to update or not in user environment images.

@consideRatio thank you for writing this up very nicely! As I put this in place as a 'temporary fix' (https://github.com/2i2c-org/infrastructure/pull/2160), I think it's ok to get rid of it now, and keep an eye out for issues.

Unfortunately this was reverted, see #2210 for more details

#2210 was merged, so we can close this one again!


Fixed lint directive, Removed missing globals from lint directives, removing unused variable.

JSHint also flags parseLeftHandSideExpression and parseFunctionExpression as unused.
I could probably further reduce the need for globals with a little code reorganization.

We are deprecating the use of JSLint, see https://code.google.com/p/esprima/issues/detail?id=623.


RABBITMQ DEPENDENCIES NOT FOUND IN BITNAMI

We are using Defectdojo chart ( 2.15.1 or main). The Rabbitmq dependencies chart is not found since Bitnami already deprecated or removed it. Please update the Rabbitmq chart version
Let me know if you can help us with this
lock file config

name: rabbitmq
repository: https://charts.bitnami.com/bitnami
version: 9.1.4
This version not found in bitnami

Please remove lock file and pull dependencies, for some reason locked is old version

Any updates @Maffooch ?

Can we close this because of https://github.com/DefectDojo/django-DefectDojo/pull/10661 @mtesauro and @Maffooch ?

FYI: DefectDojo deprecated MySQL and RabbitMQ as supported tech as of the July release (2.36.0) and is removing both from our compose, helm and Github actions in August's release (Monday, Aug 5th 2.37.0).
Because of those deprecations, this issue no longer applies.


Account for distribution loss impact of DER

From looking at customer_group.jl and regulator.jl, customers.d is consistently treated as inclusive of distribution losses, and is scaled by (1 - utility.loss_dist) when used to calculate quantities at the customer-level.
In contrast, DER energy data (rho_DG) is always used as-is, at both the customer and the system level. Given that the DER capacity is nameplate, I think rho_DG * capacity should be interpreted as meter-level, and thus at times inflated with the factor (1 + utility.loss_dist) when used at the system level (sometimes in regulator.jl, and whenever used as part of a VPP in utility.jl or ipp_group.jl) under the assumption that changes in net load will mostly not travel very far through the distribution system.

Ah, do you mean if BTM load is d_BTM, BTM gen is g_BTM, the load with transmission loss would be (d_BTM-g_BTM)*(1+loss_dist), that's why we need to scale BTM generation up by (1+loss_dist)? That makes sense. To be consistent, I guess when we get the load without loss, we currently do d*(1-loss_dist) (where d is the load with loss), maybe it is more accurate to do d/(1+loss_dist)?

Yes, all that is correct.


new packages of some themes: arc-icon-theme, moka-icon-theme, faba-icon-theme, faba-mono-icons

Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Tested locally. Thanks for your contribution!


Track events are setting undefined on url, referrer, and search properties

We're using analytics-next as an npm module, calling load and then a basic analytics.track event without any options or overrides. The only plugin we have is scrubPii enabled.
While analytics.page events have these properties all set properly, track events seem to set these as undefined, even though the context.page object does seem to have these values, the properties come in as empty. I would expect them to come in just like the analytics.track event, fully populated.
The call looks like this:
analytics.track("Header Link Clicked", { item: "Treatments" })

In Segment debugger:
  "properties": {
    "item": "Treatments",
    "referrer": "undefined",
    "search": "undefined",
    "url": "undefined"
  },

@kamui
Thanks for creating this issue! For your track calls, I would have expected the referrer, search, and url properties to not exist at all in your properties object, just in context.page. properties should only contain what you've supplied to your track call.
I'm not familiar with the scrubPii plugin - is this something you can share?

Good question, it's custom middleware and upon further investigation, it was responsible for this bug, so I'm closing this. Sorry for not checking this plugin first and thanks!


HTML previewer not rendering images

Images and figures fail to render when previewing html files.
A depositor is hoping to publish an html file of a 3d graph that will allow users to engage with and manipulate the image within the previewer. However, when deposited, the file is recognized as an HTML file and triggers the "Explore on View Html" button

When clicked, the "Preview Html" window simply displays the filename and dataset

This also seems to be happening with other html files, but for images only. In this example from Harvard Dataverse: https://dataverse.harvard.edu/file.xhtml?persistentId=doi:10.7910/DVN/3SLMJY/LTUGXH, the text and code blocks are successfully previewed, but the image at the bottom does not render.

@phillipsjs unfortunately, while @JR-1991 @qqmyers @kmika11 and I had a robust internal discussion on this, it comes down to security.
One idea from @qqmyers is to NOT show the plot immediately but offer a button so that people can opt into running the Javascript.
@kmika11 suggested whitelisting Plotly.
In short, while I'm sure your intentions are true, Harvard Dataverse is very open. We often take down spam and other junk. We need to be careful. Other Dataverse installations may be more tightly controlled.
Is your file the ft_space_3d.html file we were playing with? That one used Plotly. @JR-1991 had a nice one called CarsAndPTWsWorldwide.html. I'd post screenshots but I'm sure if these are unpublished or not.

@pdurbin & @qqmyers - is the button option on the user end? So users that want to preview the plot could click a button to run the Javascript after viewing a warning? I think that makes sense to manage some of the security risks but not restricting the preview to only plotly and other hard coded/whitelisted libraries

Yes.
Now that we have signedURLs for tools, I'd definitely recommend using for this previewer, along with the warning. Using a signedURL would mean the Javascript, if it were malicious, would never have access to the user's api token, so it wouldn't be able to use that to make other calls as that user in an attempt to damage Dataverse/ that user's data in the Dataverse, etc.  and the risk would really be to the user - a malicious Javascript could do anything bad that a malicious Javascript on any page could do to them.
That would mean the user warning would just have to say something like "This data file includes JavaScript which may need to run for the data to display properly. You can click the button to allow the JavaScript to run, but be sure you trust this datafile as a malicious JavaScript could harm your computer (with the same concerns as if you went to a malicious website outside of Dataverse)."  (With signedURLs, we wouldn't need to also say that a malicious script could delete any data you may have in this Dataverse instance, create spam datasets using your account, etc.)

Hi, just returning to this to say that from our perspective, having a warning and a clicking a button to allow for the javascript to execute would be perfectly fine! Sounds like that might be a good solution all-around!

Adding a confirm and subsequent if-statement in html.js plus not stripping the script tag should do the work. What do you think? Happy to submit a PR on Monday 🙂

I'd be happy to see a PR. 😄

Yeah - hopefully straight forward so it would be great to have something people can try. xss,js is an external lib so no change there. I'm not sure if we should replace the existing HTML previewer or make a new InteractiveHTML previewer (or something) and maybe keep it out of the recommended/non-experimental list for now. (Just don't want an admin to cut/paste our list and install something that could cause issues without understanding the risks of allowing javascript.)

Yeah, I was sort of thinking a second POTENTIALLY DANGEROUS HTML previewer might be nice, so people installing them have options. 😄

Really excited to hear that this will likely work! Thanks all :)

I got it to work using the Plotly example from our Dataverse installation. @qqmyers I needed to remove the filterXSS for it to work. Is this due to the particular case of Plotly? Is it too dangerous to leave that one out? Guess most plotting frameworks rely on special CSS.
Checking with some other HTML files and will submit a PR today.

XSS is just removing potentially dangerous tags (like

The following pull request has been merged...

#40

(Thanks for the rich HTML previewer, @JR-1991!)
Does that mean we should close this issue?

Sssßßssßsszzzssßsszzszzzsszsssszssszßsszsßssßzsssssssssssszzzszzzzzszzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz,
On Tue, Oct 3, 2023, 2:27 PM Philip Durbin @.***> wrote:

The following pull request has been merged...

#40 https://github.com/gdcc/dataverse-previewers/pull/40

(Thanks for the rich HTML previewer, @JR-1991 https://github.com/JR-1991
!)
Does that mean we should close this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/gdcc/dataverse-previewers/issues/31#issuecomment-1745503684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKLQHXUVZTP676U3YOUNTLX5RKIJAVCNFSM6AAAAAAXTJJ7COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVGUYDGNRYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

With the Rich Html Previewer in v1.4, I'm going to close this issue. Feel free to create a new one if there are issues it doesn't resolve.


Api/naming scheme

More clean-up of the public API in anticipation for the release of v2.0 . This moves the final few internal pieces of Adiar into the adiar::internal namespace, defines a naming scheme, and enforces this naming scheme across the public API.

Closes #544
Closes #543
Closes #539

Still missing tasks:

[ ] Fix naming scheme for global enum settings


order list  without "start=" ?

Hi,@vsch
I want to render the text:
- 1. list1

- 2. list2

- 3. list3

But i get the result

list1

list2

list3

i want to add the "start" attr to the
 except first
,like:

list1

list2

list3

My code

   private static final DataHolder OPTIONS = PegdownOptionsAdapter.flexmarkOptions(
			(Extensions.ALL_WITH_OPTIONALS )
			).toMutable()
			.set(HtmlRenderer.FENCED_CODE_LANGUAGE_CLASS_PREFIX,"")
			.set(HtmlRenderer.INDENT_SIZE, 2)
			.set(Parser.LISTS_ITEM_INDENT, 2)
			.set(TablesExtension.MIN_SEPARATOR_DASHES, 1)

    private static final Parser parser = Parser.builder(OPTIONS).build();
    private static final HtmlRenderer renderer = HtmlRenderer.builder(OPTIONS).build();

Could you give me some advice?

@Hxuhao233, you are using the pegdown options adapter which configures the parser for pegdown compatibility, including pegdown list parsing and rendering, which ignores list start number.
List parsing options are described in https://github.com/vsch/flexmark-java/wiki/Extensions#list-parsing-options. You need to set Parser.LISTS_ORDERED_LIST_MANUAL_START to true.

@vsch, It can work.Thank you!

@vsch I am having a similar problem, but I have the default CommonMark options set.
Using the FlexmarkHtmlParser, I have two consecutive ordered lists being rendered into Markdown as:
**Ordered**
1. Item 1
2. Item 2
3. Item 3

1. [Example.com](http://www.example.com)
2. [Google](http://www.google.com)
3. [Yahoo!](http://www.yahoo.com)
4. [Another Example.com](http://www.example.com)

When using the default Parser and HtmlRenderer, these two lists are turned into one:

Ordered

Item 1

Item 2

Item 3

Example.com

Google

Yahoo!

Another Example.com

I have tried various Parser options to stop this happening, but I am at a loss.

@GomiGuchi, a blank line does not end a list, it only makes the list items loosely spaced.
The right way to end a list is to insert another element in between. An HTML comment serves this purpose without inserting a visible element.
**Ordered**
1. Item 1
2. Item 2
3. Item 3

1. [Example.com](http://www.example.com)
2. [Google](http://www.google.com)
3. [Yahoo!](http://www.yahoo.com)
4. [Another Example.com](http://www.example.com)

Resulting in:

Ordered

Item 1

Item 2

Item 3

Example.com

Google

Yahoo!

Another Example.com

The other option is to enable double blank line ending a list option Parser.LISTS_END_ON_DOUBLE_BLANK by setting it to true, then insert two blank lines to end a list but this is not compatible with standard CommonMark.
**Ordered**
1. Item 1
2. Item 2
3. Item 3

1. [Example.com](http://www.example.com)
2. [Google](http://www.google.com)
3. [Yahoo!](http://www.yahoo.com)
4. [Another Example.com](http://www.example.com)

Resulting in:

Ordered

Item 1

Item 2

Item 3

Example.com

Google

Yahoo!

Another Example.com

@vsch Thank you very much for your reply. I'm trying to parse HTML to store it as markdown, and still be able to display it as HTML again, so I really need to output of FlexmarkHtmlParser to result in the same HTML when read by Parser.
As far as I can tell, none of the Parser options I set affect FlexmarkHtmlParser, but maybe I am not setting the options correctly. Do Parser options have an effect on FlexmarkHtmlParser? Is there a way to get the consistent flow through flexmark with lists like this?

@GomiGuchi, in general it is impossible to convert HTML to Markdown and have the markdown generate the same HTML. Markdown down is much more limited.
The HTML Parser is not intended as a 100% accurate conversion because it is not possible. It is more of a convenience for converting HTML to Markdown that should be examined and edited for desired results.
That said, if something obvious is messed up like the HTML to Markdown converter generating two consecutive lists without an intervening HTML comment then this is a bug in the HTML to Markdown converter. This needs its own issue. I'll open it.

@GomiGuchi, issue opened #138


Auto select first completion item

I'm trying to migrate my coc completion to completion-nvim, and one feature I'm missing is auto selecting the first completion item. I feel like this is possible, but couldn't find anything from my shallow searching. I figure opening an issue would make it easier for others to find in the future as well.

set completeopt+=noinsert

Thank you.

is it possible to autoselect only some complete_items?
My complete_items is ['lsp', 'snippet', 'tabnine', 'buffers']. Can I configure the plugin to autoselect only lsp and snippet items but not tabnine or buffers?

is it possible to autoselect only some complete_items?
My complete_items is ['lsp', 'snippet', 'tabnine', 'buffers']. Can I configure the plugin to autoselect only lsp and snippet items but not tabnine or buffers?


adding eap v2

Pull Request Test Coverage Report for Build 396209414

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.516%

Totals

Change from base Build 395829689:
0.0%

Covered Lines:
471

Relevant Lines:
483

💛  - Coveralls


Log every page visit

I'm using framework7 (single page application) for android, and trying to analyze user behavior on my apps. I want to know at which page users mostly stop using my apps by counting page visit. I'm trying put this code from example :
window.FirebasePlugin.logEvent("page_view", {page: "dashboard"});
everytime I call a page (change page parameter with my custom page name), but I still can't see the result at my firebase console. Is it possible to do this?

the events end up under Events -> select_content -> [your event name]
This will change in the next release to simply Events -> [your event name]


Editor configs

cc @rameshvs
This adds controls to turn on/off the following two options in the query editor:

Vim bindings
Live autocompletion (autocompletion as you type)

Also adds CSS styles to extend the autocompletion window.

@woohp I addressed your comment. I took out the liveautocompletion toggle from the snippets view, because redash didn't actually have autocompletion enabled on that view so the toggle was meaningless.


retrieving miner info ( schnorr and ecdsa ) and added to extra field

Looks ok to me, looked over and did a quick test on tn10. Haven't verified ecdsa though, but I believe you have tests of the actual decoding pretty well covered already?


Nightly wheels and WASM/pyodide builds

CC @agriyakhetarpal
See also:
https://github.com/scientific-python/upload-nightly-action/issues/111
We should upload nightly wheels after each merge to main to the scientific-python nightly wheels index:
https://anaconda.org/scientific-python-nightly-wheels
That is useful for downstream testing e.g. in SymPy. It would also make it possible to have the latest main branches of python-flint and SymPy available for testing in SymPy Live:
https://live.sympy.org/
We should also build and test python-flint in WASM with pyodide in CI. There already are WASM builds of python-flint in pyodide:
https://pyodide.org/en/stable/usage/packages-in-pyodide.html
Those can be used in the browser e.g. at:
https://pyodide.org/en/stable/console.html
>>> import flint
>>> x = flint.fmpz_poly([0, 1])
>>> p = x**2 + 2*x + 1
>>> p
x^2 + 2*x + 1
>>> p.factor()
(1, [(x + 1, 2)])

It looks like cibuildwheel could build these with --platform pyodide:
https://cibuildwheel.pypa.io/en/stable/options/
We would first need emscripten builds of GMP, MPFR and FLINT. The build recipes for those can be found in the pyodide repo e.g.:
https://github.com/pyodide/pyodide/tree/main/packages/flint
Probably a separate CI workflow should be used for making and testing pyodide wheels because we can't upload them to PyPI and the build commands and CI setup would be a bit different. We can upload the WASM wheels to the nightly wheels index though and the final release versions are already built in pyodide.

Thanks for the mention, @oscarbenjamin! I'll be on holiday until early November, so I'm happy to step back and let someone else take it if you wish and if this is pressing for any reason. Otherwise, I can take a look at this in the coming weeks.
I'd suggest not using cibuildwheel for Pyodide builds, though – at least, not until I complete https://github.com/pypa/cibuildwheel/pull/2002. This is because cibuildwheel puts constraints around the Pyodide version available within it, and there is a chance it will be out of date until cibuildwheel releases a new version, so it's better to set up Pyodide and build the WASM wheels ourselves (for now). We don't have a long-term support policy for a particular Pyodide version, and have previously stated supporting just the latest available stable version. If having an older Pyodide version isn't a problem, then that's alright, the integration with cibuildwheel is quite neat.

I'm happy to step back

I wasn't suggesting that you do the work here (although you are welcome to!).
Rather any advice is welcome:

so it's better to set up Pyodide and build the WASM wheels ourselves (for now).

Okay, good to know.
Do you know of any example of any similar project that has a CI workflow I could look at?
The task here is to build three dependent C libraries (GMP, MPFR and FLINT) that all build with autotools and then build the python-flint Python package on top. I'm not sure I understand how this works in pyodide but the other wheels all need to bundle those C dependencies in which is done by cibuildwheel's repair step (auditwheel, delvewheel, delocate).
I don't know if it matters but on current main python-flint uses meson-python which is different from the most recent release (which uses setuptools).

If having an older Pyodide version isn't a problem, then that's alright, the integration with cibuildwheel is quite neat.

The cibuildwheel integration would be more useful if we could treat the wheels like the others which we can't if we can't upload them to PyPI or if the build and setup steps are quite different. I guess in future using cibuildwheel will make more sense.

I wasn't suggesting that you do the work here (although you are welcome to!).

Thank you! I wasn't too sure about it because you pinged me here, so I'll help out wherever I can. :D

The task here is to build three dependent C libraries (GMP, MPFR and FLINT) that all build with autotools and then build the python-flint Python package on top. I'm not sure I understand how this works in pyodide but the other wheels all need to bundle those C dependencies in which is done by cibuildwheel's repair step (auditwheel, delvewheel, delicate).
Do you know of any example of any similar project that has a CI workflow I could look at?

I'd say that there is indeed a lack of documentation around navigating build systems with cross-compilation using Pyodide. Perhaps we need to publish more example packages across various build backends in a repository somewhere (this exists for just scikit-build-core + pybind11-based packages, but I'm unable to find the link to that repository – I'll update this comment with it when I can).
As for repairing the WASM wheel, we ship a tool called auditwheel-emscripten, which is integrated with the pyodide CLI using pyodide-build (you may try it with pip install pyodide-build && pyodide auditwheel --help). Right now, we repair the wheels with this interface immediately after they are built, for convenience. I'd also note that Emscripten does not fully support runtime search paths, yet: https://github.com/emscripten-core/emscripten/issues/22126, but that might not be relevant too much here.
I just wanted to clarify, though—for the C libraries you mentioned: GMP, MPFR and FLINT—will they be used during python-flint's build process as build-time/host dependencies, or are Python bindings as wheels for them used as runtime dependencies? If it's the latter (I assume that's the more common scenario out of the two), then I'll have to think how to do it out-of-tree, since pyodide build outside the Pyodide repository works better for Python packages compared to shared and static libraries. It should still be doable, though, but the implementation might not be as neat. It might be easier if versions used for these C libraries remain relatively stable, since using their nightly builds for a nightly python-flint wheel would be quite disruptive (😅)
You could look at NumPy's CI workflow for a project that uses meson-python: https://github.com/numpy/numpy/blob/020e78cc3a4c7283bbe83290f0be5de3bc842f07/.github/workflows/emscripten.yml. Although, at the time of writing, it uses cibuildwheel and that abstracts away most of the build procedure, so you could take a look at one of my PRs from earlier this year where we re-enabled it: numpy/numpy#25894. I'd think adding support to python-flint's packaging infrastructure is something we can do without much hassle (or so I hope).

The cibuildwheel integration would be more useful if we could treat the wheels like the others which we can't if we can't upload them to PyPI or if the build and setup steps are quite different. I guess in future using cibuildwheel will make more sense.

I agree!

I just wanted to clarify, though—for the C libraries you mentioned: GMP, MPFR and FLINT—will they be used during python-flint's build process as build-time/host dependencies, or are Python bindings as wheels for them used as runtime dependencies?

It is both. We need the headers at build time and then we need the shared libraries at runtime. There are no Python packages for GMP, MPFR and FLINT apart from python-flint itself which uses all of them (and needs to include all three bundled in to the wheel). The wheel build process is basically:

Build C lib GMP
Build C lib MPFR against GMP
Build C lib FLINT against GMP and MPFR
Build python-flint extension modules and wheel against GMP, MPFR and FLINT.
Repair the wheel to bundle GMP, MPFR and FLINT (and something like pthreads as well).

I will try this out locally when I get time with pyodide auditwheel to see how it works. Then I will see if I can get it working in CI (thanks for the NumPy links!).

I understand now, thanks for the context! When I get the time, I'll be glad to help out more, too, and I will try my best to answer any questions.

Uploading nightly wheels was added in gh-235.
Now if we add a WASM build in CI we can add it to the upload job.


Fix empty state language

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

:tada: This PR is included in version 1.4.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Setup SAP HANA, express edition, on Amazon Web Services - XS Advanced Application

Not a very useful page. Has no content you might want to remove.

Hi, Ryan, thanks for the feedback.


risedev: bundle yq binary

So as to ensure all developers are using the same version of yq.

yq isn't needed anymore. https://github.com/singularity-data/risingwave/pull/4307


update os version

Description
Please summarise the changes.
Related issues
Please mention any github issues addressed by this PR.
Checklist

[ ] I have run the tests on a device with GPUs.
[ ] I have performed a self-review of my code.
[ ] I have commented hard-to-understand parts of my code.
[ ] I have made corresponding changes to the public API documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have updated the changelog with any user-facing changes.

Could you merge with main first? Jake just added CI on the last commit. I want to make sure that these changes in CI do not mess up anything with the tests.

This should be up to date with main? Are you missing something specific?

I'm missing the last commit from main: https://github.com/CQCL/pytket-cutensornet/commit/efb1a5245e2928daf8134049d9e0a87ae3d427e1
It was merged almost at the same time you created this PR


Fix typo

Provide valid error type for the trigger_error

ping. This is a simple typo. Can anyone merge this patch. Thanks ;)


store used parameters when using verbose mode

sometimes you try out different settings and want to go back to one that worked well but then you can't remember the settings. So this should be stored in a txt file

Closed with https://github.com/OpenStitching/stitching/pull/227


Access to exoplayer analytics

Hello, I was wondering if is it possibile to get access to the exoplayer analytics data. I need information about the latency and the dropped frames rate but I wasn't able to find anything.
Thanks in advance for your help

This is not available nor planner for this project what I know


Headers name not in alphabetic order in transform rules causes an error

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.3.5
on linux_amd64

provider registry.terraform.io/cloudflare/cloudflare v4.2.0

Affected resource(s)

cloudflare_ruleset

Terraform configuration files
resource "cloudflare_ruleset" "request_headers" {
  kind    = "zone"
  name    = "transform rules for request HTTP headers"
  phase   = "http_request_late_transform"
  zone_id = "42"
  rules {
    action = "rewrite"
    action_parameters {
    # header names NOT in alphabetic order
      headers {
        name      = "B"
        operation = "remove"
      }

      headers {
        name      = "A"
        operation = "remove"
      }
    }
    description = "just a test"
    enabled     = true
    expression  = "<whatever>"
  }
}

Link to debug output
https://gist.github.com/Arnall/b2f4523117d6f3571c8695975d77aae9
Panic output
No response
Expected output
no error message, Terraform do no try to update at each terraform plan/apply
or at least the alphabetic order should be documented in the provider documentation.
Actual output
Provider produced inconsistent result after apply

When applying changes to cloudflare_ruleset.request_headers, provider
"provider[\"registry.terraform.io/cloudflare/cloudflare\"]" produced an
unexpected new value: .rules[0].action_parameters[0].headers[0].name: was
cty.StringVal("B"), but now cty.StringVal("A").

This is a bug in the provider, which should be reported in the provider's
own issue tracker.

Provider produced inconsistent result after apply

When applying changes to cloudflare_ruleset.request_headers, provider
"provider[\"registry.terraform.io/cloudflare/cloudflare\"]" produced an
unexpected new value: .rules[0].action_parameters[0].headers[1].name: was
cty.StringVal("A"), but now cty.StringVal("B").

This is a bug in the provider, which should be reported in the provider's
own issue tracker.

Steps to reproduce

Just try to create a transform rules via Terraform and set several headers block with header names not in the alphabetic order.
terraform apply

Additional factoids
On the server side Cloudflare seems to order the header names by alphabetic order, so if your configuration does not have header names in alphabetic order in your transform rule, Terraform will always try to update the rule and will generate error messages.
References
No response

the sorting is intentional from the service team so we replicate that in the provider (i don't know anymore beyong that, sorry). i suspect it could be something to do with order of operations on the header values.
you'll need to keep your HTTP header transformations alphabetically sorted to avoid drifts like this.

@jacobbednarz this should be part of the documentation perhaps? thanks


Red Hat: Better readability fixes

Red Hat - Better readability, few enhancements

Fixes "Status" wording to "Fixed" where issues were actually fixed
Added Dates for every product
Minor text placement reorg
Added extra clarification to some product affectedness

💭 Motivation and context
There were some lacking information and content / statements were not uniform across all products.
🧪 Testing
N/A
📷 Screenshots (if appropriate)
N/A
✅ Pre-approval checklist

[X] This PR has an informative and human-readable title.
[X] Changes are limited to a single goal - eschew scope creep!
[X] I have read the CONTRIBUTING document.
[X] These code changes follow cisagov code standards.
[X] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Add a tag or create a release.

Extra notes
Thanks CISA team for curating this content 💪

Withdrawing it - will file another one to the new file


loc_del() restores all instances of a loc when first one is restored.

Find a closed door in game.
Open the closed door.
Close the opened door.
The door will disappear after the 5 minute timer.


feat(Table) add missing Table alignment props

Add textAlign and verticalAlign props to the Table component.
Fixes #1389

Codecov Report

Merging #1411 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1411   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         140      140
  Lines        2347     2347
=======================================
  Hits         2341     2341
  Misses          6        6

Impacted Files
Coverage Δ

src/collections/Table/Table.js
100% <ø> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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

Superb thanks!  We just refactored the typings so I rebased this branch and moved the index.d.ts updates to the new Table.d.ts file.
Will merge on pass.

😊

Released in<EMAIL_ADDRESS>


Control package action via attributes

Upgrade action does not allow precise control of the installed version
This commit introduce a new attribute allowing to change the action
performed by the package.
Cc: @aboten

Thanks!

Thanks for your quick review!


AuthorizeAttribute should use 401 instead of 400

Currently, when a request fails authorization a 400 status code is returned. Shouldn't this be a 401 instead to differentiate from requests that simpye have an incorrect model?

@borgdylan I'm not seeing the behavior you describe - I see 401's being returned. Can you try this out with our latest bits from the dev branch and send us a simple project that reproduces the issue?

This is happening in  a complex case with code that I cannot disclose. In some way the 401 is being changed/redirected by the cookie middleware.

I get:
Unable to locate Microsoft.AspNet.RequestContainer >= 1.0.0-beta4-11232

when trying to replace all the packages with the latest ones.

The culprit is one of the security packages which still requires teh request container package which as as I know was nuked some time ago.
 Microsoft.AspNet.RequestContainer 1.0.0-beta4-11232
    -> Microsoft.AspNet.Security 1.0.0-beta4-11758

My bad, I was referencing old packages. Now, I get the 401 as expected so that my javascript displays the login view.


I have fixed a typo

on line 20, the text was 'abudant' and I changed it to "abundant"

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


fix admonition

Formatting issues on the comparison notebook.
Same as was in - https://github.com/ProjectPythia/pythia-foundations/pull/469/files

Oh yes, I didn't know that was open.
Closes #56


Help me please create new category Sensors and blocks for this category

Hi @carlosperate I'm using this guide https://github.com/carlosperate/ardublockly/wiki/Create-Blocks , but nothing working. I want to create category Sensors (like Motors, Logic, Loops categories). To this category I want to add blocks. But I even can't created category. Category is not appears in the list of categories.
Here is filed which was modified to add category Sensors https://1drv.ms/u/s!ApxakNruUlXWplruS6ZtuGrvZmgv ardublockly_blockly.js
https://1drv.ms/u/s!ApxakNruUlXWpl3oAEBRrz76Fhd6 ardublockly_toolbox.js

Hello,
I'm not sure my information will provide help, I'm only beginner with Ardublockly, but have you modified index.html to add the path of your new code files?
https://github.com/carlosperate/ardublockly/blob/master/ardublockly/index.html

To add a new category you will have to modify the toolbox javascript file, and to translate it correctly you will also have to add the new entries into the javascript files in  ardublockly/msg/ and update the Ardublockly.updateToolboxLanguage() function.
Hopefully this commit will be able to guide you: https://github.com/carlosperate/ardublockly/commit/1ad1ecb0e6bccb43c9c23f04ad7712985d9b3a4e

I assume the original question has been answered, feel free to reopen this issue otherwise.


draw call has big difference between invoking "composer.render()" in useframe and requestAnimationFrame

Description of the bug
In my application,  I have used "View", the structure looks like below
<View index={1} className="view1" id="view1">
    a big scene
</View>
<View index={2} className="view2" id="view2">
   a small glb
</View>
<View.Port />

the view 2 is not displayed in some rooms.   it is showed by some user interaction in a special room.
I added "postprocessing" such as bloom, AO, Vignette, SMAA for all room.
I found the draw call has been increased a lot if I used option A to render the postprocessing effects.
option A:
useFrame((state, delta) => {
composer.render(delta)
}, 1)
Option B.
function renderScene(){
animationReq = requestAnimationFrame(renderScene)
composer.render()
}
then, I do a testing
test 1:   no postprocessing with 2 views.

test2:  useframe with one view

test3:  useframe with 2 views

test4: requestAnimationFrame with views

test5:  useframe with no views.

You can see if there is no views,  the draw call is similar no matter we use "useframe" or "requestAnimationFrame".   however, after we added "view",  the draw call, points, triangles have been increased a lot.
if I continuously use "requestAnimationFrame",  it will have trouble in 2nd view in the special room. the small glb in view2 didn't appear. it just display the same content in "view1".     however, if I use "useframe", then, no problem. just a huge draw call.   and if I remove postprocessing,  no problem in views as well.
To reproduce
Describe the steps to reproduce the behavior and provide a minimal example that demonstrates the issue. You can use the demo sandbox as a starting point: https://stackblitz.com/edit/postprocessing-v6
Expected behavior
I think we should use useframe to keep same draw call as "requestAnimationFrame" in multiple views.
Screenshots
refer to above.
Library versions used

Three: [e.g. X.XXX.X]
Post Processing: [e.g. X.X.X]
"@react-three/postprocessing": "2.16.2",
"postprocessing": "^6.35.3",
"three": "0.163.0",

Desktop

OS: [MacOs Sonoma 14.5]
Browser [e.g. Chrome 125.0.6422.61]
Graphics hardware: [e.g. NVIDIA]

SSAO is causing the drastic increase in draw calls because it has to render the given scene twice to write the normals to a texture. This issue will be fixed in v7 which uses MRT for this, but the new SSAO implementation isn't ready yet.
Bloom also adds levels * 2 draw calls for the down- and upsampling steps. However, the performance impact of these draw calls should be small since there are only 2 material switches involved.
SMAA performs edge detection and weight calculation which adds 2 draw calls.

@vanruesc  thanks your explanation.  I understand that draw call will be increased.  however, it seems the issue caused by views.   is it possible that we force to render one view only?   and why requestAnimationFrame has no impact with views..

It's probably related to how WebGLRenderer.info is updated. By default, postprocessing doesn't manage it, so when it runs, the draw calls are reset for each pass and EffectPass by itself counts as one draw call which is probably why the rAF approach shows lower than expected draw call stats.
As for the views and `useFrame that's out of scope for this library since it's react code.

Closing this as it seems to be answered.

Last update,  I gave up this solution,  use MeshPortalMaterial + requestAnimationFrame to do the similar thing.


NDI source not present

I have installed Dicaffeine software and could select NDI source as there is non on the list.
I have tried to change IP address in configuration, but no success.
We have NDI access manager to control NDI streams on the network and maybe this is the reason?

Hi, that could be the reason. Dicaffeine uses for searching the official NDI library, if if won't see the sources there wouldn't be any listed.


Using existing windows to open definition/reference/etc.

Is your feature request related to a problem? Please describe.
It's not really a "problem", per se, but mostly, a nice-to-have feature.
Describe the solution you'd like
It happens to me a lot that I have something like this:

I have 2 or 3 splits open
In one of the splits, I open the peek definition window (or the finder window etc.)
I want to open definition/reference etc, but:

I do not want to open it in the split I'm currently in
I want to open it in one of the other splits that I have open.

Describe alternatives you've considered
Right now, this is what I do:

I go to the split I want to use for definition/reference
I close it
I go back to the split I want to see the definition for
I then choose to open in horizontal/vertical split and lspsaga creates a new one

What I have in mind is something like neo-tree's "open with window picker", but in the context of lspsaga and "open in split" for definitions/references
Additional context
Please let me know if what I descirbed makes sense, or if you need things such as screenshots

make sense . more work to do then.

Great, really looking forward to this since, as far as I know, there isn't any plugin doing that.
And I REALLY like using lspsaga and this feature, if implemented, would make it even more amazing

This behavior can only be used by certain people. Some people don't like to use windows that already have splits. Will break some of their habits. So the final implementation could be a command argument or an option  like Lspsaga definition layout=normal_reuse

Yeah, totally agree, I think the current behavior should stay as is, as people are already using it, and of course there are use cases for it
I really like the idea of an additional argument, but one thing:
Normally we configure the mappings in the config, like:
definition = {
  keys = {
    edit = '...',
    -- ...
  }
}

So, there could be additional things we can configure here, corresponding to the new behavior.
And, up to you, but I find normal_reuse to be a bit ambiguous, where, at first sight, you don't exactly know what it's supposed to represent

just a draft name . if you have better name I will consider use it   :)

Quick thing that comes to my mind, something like use_existing maybe? (just a suggestion of course)

@glepnir may I ask why this one was closed as completed? I don't seem to be able to find anything related to "use an existing window" in the docs.
Probably I missed something?

nope maybe i forget

use ++inexist flag. in command

yep you need if you want split/vsplit in an exist window.

Hey @glepnir , I really appreciate you implementing this, but don't you think it would be nicer to have this as a keys configuration?
With the way it's set up right now, I need to think in advance; basically a thought process would be something like this:
"OK, I'm gonna open the go to definition window, but will I need to use existing split or create a new one? ... OK, gonna create a new one when going to the definition, so use the configured keys option, but then ... I'm like: Oh shoot, I meant to use an existing one, so I have to close and use my vim.keymap.set binding"
If this feature is similar to the other keys, I can make the decision "on the fly"; open the window and then decide easily whether to use existing split or create a new one

@glepnir that's nice, but still a couple of issues:

The setting seems to be only applicable to the finder it seems (how about definition for example?)
The setting is still a "global" one, meaning that it'd affect every finder that I open, and, in case I need the other behavior, I need to modify my config to set that option to false or true

Isn't it possible to have it in keys, say something like:
require('lspsaga').setup({
  definition = {
    keys = {
      -- ... existing options (edit, vsplit, split, etc.)
      inexist = '...', -- <-- new one
    }
  },
  finder = {
    keys = {
      -- ... existing options (edit, vsplit, split, etc.)
      inexist = '...', -- <-- new one
    }
  }
})

This way, there's no need to configure anything globally: I open finder or definition, and:

If I want to open in a new split, I use the split and vsplit bindings
If I want to use an exsiting window, I use the inexist binding

create a new feature request of this new global option .

Sounds good, will do once I get a chance


Not seeing the export?

Describe the bug
When I try to export a compatible project as a Minecraft Schematic (or mp3), I cannot locate any of my folders, and when I make a new folder for the schematic file (or mp3 file), I cannot locate it in File Explorer. Even if I do not make a folder, I cannot find the file.
To Reproduce
Steps to reproduce the behavior:

Export any project as any file in any location
Be unable to find the file or created folder

Expected behavior
See all of my folders when I export the file, and be able to locate the file when it is need.
Screenshots

Additional context
If it helps, I have an 8th gen Intel core on a Windows 10 HP Laptop.

Inconclusive report. Seems like something is going on with your system – doesn't seem to be related to the program, so I'm closing it for now. Feel free to leave a comment in case you want to add more information.


Add support to configure xDS server and port through EnvoyGateway API type

Description:
With the current implementation it's not possible to configure xDS host and port. https://github.com/envoyproxy/gateway/blob/d99f32feef8ddd6ede45bd0c93b607586138d4c8/internal/xds/server/runner/runner.go#L58
We need to expose these configs through EnvoyGateway type.
[optional Relevant Links:]
https://github.com/envoyproxy/gateway/issues/212

@danehans I think the host and port config fields should go inside the Gateway struct. We can either put the fields there straightway or wrap it with another struct (something like Listener) and add it there. WDYT ?
https://github.com/envoyproxy/gateway/blob/d99f32feef8ddd6ede45bd0c93b607586138d4c8/api/config/v1alpha1/envoygateway_types.go#L41


Mysterious crash if you run .init_state before adding DefaultPlugins now !

Bevy version
The release number or commit hash of the version you're using.
0.14
(this did not occur in 0.13 )
Mysterious crash if you run .init_state before adding DefaultPlugins now !
Caused by :
in main branch: https://github.com/bevyengine/bevy/blob/main/crates/bevy_state/src/app.rs#L72-L74
GitHub
[bevy/crates/bevy_state/src/app.rs at main · bevyengine/bevy](https://github.com/bevyengine/bevy/blob/main/crates/bevy_state/src/app.rs)
A refreshingly simple data-driven game engine built in Rust - bevyengine/bevy
bevy/crates/bevy_state/src/app.rs at main · bevyengine/bevy

           let schedule = self.get_schedule_mut(StateTransition).expect(
               "The `StateTransition` schedule is missing. Did you forget to add StatesPlugin or DefaultPlugins before calling init_state?"
           );

    ```

    RECOMMEND:  Make this error message more obvious, give users more warning of this   change in 0.14

Duplicate of #14154, which has already been resolved on main.


Cant build app because of free apple id

How can I turn off Push Notifications and Associated Domains so that that I can build the app??
Its not there in the capabilities section so is there a part of code I have to comment?? or should I try out the test branch?

2018-08-17 16:24:13.230223+0530 The Wave[5487:1945101] [Application] Failed to instantiate the default view controller for UIMainStoryboardFile 'Main' - perhaps the designated entry point is not set? 2018-08-17 16:24:13.231159+0530 The Wave[5487:1945101] You've implemented -[<UIApplicationDelegate> application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add "remote-notification" to the list of your supported UIBackgroundModes in your Info.plist.
2018-08-17 16:24:13.577296+0530 The Wave[5487:1945101] [Crashlytics] Version 3.9.3 (128)
2018-08-17 16:24:13.836885+0530 The Wave[5487:1945101] [Crashlytics:Crash:Reports] Packaged report with id '8f68aa31435f4ba7a81f3730541620ba' for submission
2018-08-17 16:24:13.904457+0530 The Wave[5487:1945101] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'TwitterKitResources.bundle resources file not found. Please re-install TwitterKit with CocoaPods to ensure it is properly set-up.'


🎄Merry Christmas and Thanks! 💕

I just wanted to take this moment and say 'Thank You' to everyone who contributed to this project and helped Onefetch grow and be what it is today.

:heart::heart:

@spenserblack, @Luke-zhang-04, @ZapAnton, @yoichi, @HallerPatrick, @CephalonRho, @atluft, @andymac-2, @ccmetz, @Phundrak, @maash3r, @rogercyyu, @ktsuench, @ebroto, @Sh3mm, @Kloenk, @pablodiegoss, @xynxynxyn, @axdiamond, @Emanon42, @geeseven, @goosedb, @aluft-logi, @Ferryistaken, @KaindlJulian, @nguyenquannnn, @JoshBrudnak, @rootEnginear, @cnsumner, @rockisch, @vypxl, @zxey, @astynax, @akrantz01, @erikgaal, @KasraF, @MarkusPettersson98, @nikofil, @hoop33, @rtroxler, @viniciusestevam, @tacrazymage, @aeter, @popey, @amiralies, @bojan88, @jadijadi, @jephthai, @tianlangwu, @kitlith, @MaxJohansen, @reime005, @di-wu, @Cogitri, @SamTebbs33, @SuperSandro2000, @CodeLongAndProsper90, @Vipul-Bajaj, @WillyChen123,

A Merry Christmas to you too @o2sh
This was kinda my first time contributing on GitHub, feels so good to be part of something.

Happy holidays to @o2sh and all 🎄🎉, it was my first time contributing too :) Positive experience, thanks for the opportunity!

Thank you very much @o2sh, I also really enjoy working on onefetch and you.
Should this PR be merged, if yes I will gladly do this :)

Should this PR be merged, if yes I will gladly do this :)

Sure, go ahead :+1:

Merry Christmas! It was a pleasure contributing to such a great piece of software.


bump to k8s 1.26

as title and issue https://github.com/kubernetes-sigs/descheduler/issues/1013

/hold
/lgtm

@JaneLiuL Created the Issue and updated the Project board accordingly: https://github.com/orgs/kubernetes-sigs/projects/22/views/1

@a7i was there anything else holding this or good to merge?

@damemi I am trying to fix the build timeout issue before we merge any additional PR. The last push failed

so can be merge this first?   @damemi

@JaneLiuL not yet, let's merge https://github.com/kubernetes-sigs/descheduler/pull/1019 first (and some other less critical PRs) to make sure the builds aren't timing out any more before we merge this. Want to make sure the GA bump lands smoothly and builds

ok, i check https://github.com/kubernetes-sigs/descheduler/pull/1019 already merge done.

@JaneLiuL yeah, unfortunately it didn't fix the problem like we expected (see https://github.com/kubernetes-sigs/descheduler/pull/1023). This is why we want to find a fix first, then merge some other PRs before this one to test that the fix works.
We'll merge this as soon as we're sure we can get our builds to complete

@damemi and @JaneLiuL Given that we are temporarily unblocked (given the increased timeout), I'm going to /unhold this PR.

/unhold


Feature/ds 305 icons breadcrumbs

@crishpeen  There is already a fix for Breadcrumbs links - https://github.com/lmc-eu/spirit-design-system/pull/467. Are your changes with link-secondary related to this problem or it is something else?

@crishpeen There is already a fix for Breadcrumbs links - #467. Are your changes with link-secondary related to this problem or it is something else?

it's something else. Not related to the icons.


Don't understand update or missing methods?

Hello,
On an existing document:
{
  id: 'rush'
  a: 'a',
  b: 'b'
}

if made this:
const bandRepository = GetRepository(Band);
const rush = await bandRepository.findById('rush');
delete rush.a // remove the a entry
await bandRepository.update(rush);

the document should be:
{
  id: 'rush'
  b: 'b'
}

But actually it keeps the a entry...
On Firestore we have the merge option to define if we want to merge or replace:
set(
  rush,
  {merge: true}
)

What is the equivalent for fireorm ? I can't find it on the documentation.
Thanks!

Given that classes are the blueprint of firestore documents, deleting a class property was never the intended way to clear its content. Setting the property to null is.
Any particular reason why you want to delete the property?

@wovalle  I see your point.
Can you please confirm currently it replaces or merges?

It currently replaces. There has been some conversation about adding a merge feature but we've had no end so far.
To delete a property from an object I would set it to null.


Trying to remove fractional permission from the cells in PulseCore heap

The PR tries to remove fractional permissions from the PulseCore heap cells. Instead it defines a cell being full as the cell value satisfying the pcm refine predicate.
This turned out to be a purely internal change, as in we can provide the same interface as before.

Looks good to me! I was also wondering why the internal fraction was there.


Fixed #27887 -- Fixed URLs check crash with namespaced URLs inside non-nonspaced URLs.

https://code.djangoproject.com/ticket/27887

This fixes the issue for me.

this fixes my use case too 🎉


chore(carousel): update from deprecated keyCode event to key

event.keyCode is deprecated. Update to use event.key.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[x] Other... Please describe: Update from deprecated `event.keyCode` to `event.key`

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Closing, will wait until Angular drops IE support


AWS ELB(alb) listener rule with extra condition parameters(query-string/http-header)

It seems like, that there is no implementation for extra condition parameters(except field and values) like queryStringConfig or httpHeaderConfig.
{      listenerArn: listenerArn,      actions: [{        targetGroupArn: elbTargetGroup.arn,        type: "forward",      }],      conditions: [        {          "field":"query-string",          "queryStringConfig":{            "values":[              {                "key":"abc",                "value":"xyz"              }            ]          }        }      ],    };
Error:

error: aws:elasticloadbalancingv2/listenerRule:ListenerRule resource 'listener-rule-test' has a problem: condition.0: invalid or unknown key: query_string_config

Hi @MarvinErkes
As we generate our schemas based on the upstream terraform providers, we can see this isn't supported there either. There is a PR open that is tracking that work
https://github.com/terraform-providers/terraform-provider-aws/pull/8268
As soon as that becomes available in a Terraform provider release, then Pulumi will support it a number of hours later!
I think it's best to track the issue there rather than create the duplicate here. When the release is made, I will add the note here as well
Paul

hi @stack72
ALB PR got merged,
are you already working on the implementation?

Hi @MarvinErkes
I expect a release of the upstream terraform provider today - when that hits, I will immediately be able to ship this :)
Stay tuned!
P.


(ts) fix: StepEntity.content is required

Since filling out StepEntity.content.title is mandatory, providing StepEntity.content itself is also required.

Thank you @rozsazoltan


Switch to loguru for logging

Closes #318.
The log format is up for debate, it is currently:
TIME | LEVEL | FUNCTION:LINE - MESSAGE
so for example:
2022-10-11 10:05:01 | INFO     | process_image:272 - Processing image 'Debian 11 (20220911)'

@sihensel Please also add the new dependencies to the Pipfile (run pipenv install afterwards to also update the Pipfile.lock file).

@berendt Sorry, I missed that. Done.


How to stop current view refresh?

hello, i used WritableLayer to show my own data, when the data is large, the refresh process may take a long time and user can feel the pause,  I consider when user move the mapview Continuously, if mapsui can stop current refresh process and repsone the next move action, then the user experience will be better, Can we do this?

I don't know why it is slow. Is see two reasons

It takes time for the data to load. In this case do not use a WriteableLayer but a Provider to load the data and assign that to the Layer.DataSource.
It takes time to render the data (there is actually a lot of data or large polygons). In this case you could nest the layer in a RasterizingLayer. Never tested how this works in combination with a WriteableLayer though. If you are using the latest beta you could also use the RasterizingTileLayer.

Here some info on how to work with the samples:
https://mapsui.com/documentation/samples.html

ok, thank you pauldendulk, I'll try your suggestion.


How to get access to latest releases?

Hi folks,
I'm looking at ChefDK Downloads and the current stable is 2.4.17.
Unfortunately, the current releases stop at 2.4.22.
Is there a way to get access to the most updated release, for example this version: https://github.com/chef/chef-dk/commit/5e07158fd6b20ad51d32094ef15c850d7b10ff46
I just wanna make sure I'm not missing something as I'm trying to get away from maintaining a Gemfile that follows the versions updated in this repo (duplicating work pretty much).
Thanks in advance! :bowtie:

that's a symptom of the fact that current builds are broken, so there's no build artifacts for those versions.  once the builds go green again then builds will show up.

Is there a way to help?
It's been more than 2 months if I'm not mistaken for the current channel. Not trying to be snarky, so apologizing if it sounds like it, is it on the radar somewhere? Meaning the build is probably not green for a reason, anyone working on it?


[WIP] Fix scene update destruction

Currently there are multiple places where a crash happens on destruction when a sceneUpdate is enqueued.
One such crash is fixed by:  206c052
I have noticed another after fixing this, with the following stack trace:
TANGRAM jobQueue.cpp:35: done running 0 job
TANGRAM jobQueue.cpp:39: DONE!
TANGRAM jobQueue.cpp:14: DONE Destructing job queue
*** Error in `/home/varun/Development/tangram-es/build/linux/bin/tangram': free(): corrupted unsorted chunks: 0x000000000159cd50 ***

Program received signal SIGABRT, Aborted.
0x00007ffff590a1c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
55	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007ffff590a1c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#1  0x00007ffff590be2a in __GI_abort () at abort.c:89
#2  0x00007ffff594dba3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff5a660f8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#3  0x00007ffff5955bb9 in malloc_printerr (ptr=<optimized out>, str=0x7ffff5a66198 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965
#4  _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3834
#5  0x00007ffff59597ec in __GI___libc_free (mem=<optimized out>) at malloc.c:2950
#6  0x00007fffee191bfd in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#7  0x00007fffee197ecc in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#8  0x00000000008fab02 in Tangram::GL::deleteBuffers (n=1, buffers=0x1297328) at /home/varun/Development/tangram-es/core/common/platform_gl.cpp:136
#9  0x0000000000a7e955 in Tangram::RenderState::deleteQuadIndexBuffer (this=0x12972a0) at /home/varun/Development/tangram-es/core/src/gl/renderState.cpp:316
#10 0x0000000000a7dc5c in Tangram::RenderState::~RenderState (this=0x12972a0, __in_chrg=<optimized out>) at /home/varun/Development/tangram-es/core/src/gl/renderState.cpp:45
#11 0x000000000094a0da in Tangram::Map::Impl::~Impl (this=0x1297250, __in_chrg=<optimized out>) at /home/varun/Development/tangram-es/core/src/tangram.cpp:41
#12 0x000000000094a100 in std::default_delete<Tangram::Map::Impl>::operator() (this=0x13b26b0, __ptr=0x1297250) at /usr/include/c++/5/bits/unique_ptr.h:76
#13 0x0000000000947987 in std::unique_ptr<Tangram::Map::Impl, std::default_delete<Tangram::Map::Impl> >::~unique_ptr (this=0x13b26b0, __in_chrg=<optimized out>) at /usr/include/c++/5/bits/unique_ptr.h:236
#14 0x000000000093e3ee in Tangram::Map::~Map (this=0x13b26b0, __in_chrg=<optimized out>) at /home/varun/Development/tangram-es/core/src/tangram.cpp:99
#15 0x00000000008efe21 in main (argc=3, argv=0x7fffffffdb78) at /home/varun/Development/tangram-es/linux/src/main.cpp:406

These are reproducible on Linux. And is also the cause of timeouts on tizen.

61aa098 fixes some more issues on which valgrind was complaining. Thanks @hjanetzek for the suggested fix.
There is still a double free on GL::deleteBuffers for RenderState::m_quadIndexBuffer. To repro this run on a heavy scene (say bubble-wrap) and immediately exit as soon as window gets created.
Another way to repro this is to run glfwSetWindowShouldClose(main_window, true); right after map->setupGL();. With this valgrind returns nothing, but a crash happens with the above stack trace.
I am not sure why deleteBuffers is crashing here, since based on the code path, it seems a valid RenderState::m_quadIndexBuffer exists. Looking more....

K need some help here to figure out this crash on glDeleteBuffer.
I checked the following

whether index buffer was generated and destroyed on the same thread
whether the index buffer is valid before calling GL::deleteBuffer
whether the size of buffer after generation is same has size of buffer just before deletion.

1f9663e has some log statement for testing this issue.

Also try the following:

kill the app as soon as the osx/linux app start. I get the glDeleteBuffer crashes with this on my linux.

Closing in favor of: https://github.com/tangrams/tangram-es/pull/1010


[WIP] Use MaskedVectorOp in the transform script

At the moment this fails on bufferization of a masked vector.transfer:
        %36 = "vector.mask"(%32) ({
          "vector.transfer_write"(%35, %30, %3, %3) {in_bounds = [true, true], operand_segment_sizes = array<i32: 1, 1, 2, 0>, permutation_map = affine_map<(d0, d1) -> (d0, d1)>} : (vector<8x16xf32>, memref<?x?xf32, strided<[4567, 1], offset: ?>, #hal.descriptor_type<storage_buffer>>, index, index) -> ()
          %38 = "bufferization.to_tensor"(%30) : (memref<?x?xf32, strided<[4567, 1], offset: ?>, #hal.descriptor_type<storage_buffer>>) -> tensor<?x?xf32>
          "vector.yield"(%38) : (tensor<?x?xf32>) -> ()
        }) : (vector<8x16xi1>) -> tensor<?x?xf32>

Repro using the iree-samples script:
(benchmark-transform-create -r -b llvm-cpu  ../iree-samples/transform_dialect/benchmark_linalg_reductions.stub.mlir   reduction_2d_elementwise_static f32 123 4567)

Please, let me know if https://reviews.llvm.org/D141559 works for you and I can land it. Something important is that the mask flattening should happen before the vector.mask is verified, as it's not legal to have multiple ops within single vector.mask. Reduction support should also be ready if a few days.

Thanks for looking into this @dcaballe !
I plugged it locally but there is no simple way for bufferization to just add non-conforming patterns, the proper way these days is to implement BufferizableOpInterface on vector.mask, which is how we extend bufferization.
@matthias-springer is going to give it a shot, his gut feeling is this should be simple and similar to scf.execute_region

SG! Then I'll hold off on D141559 as I don't need it right now.

Closing stale PR.