docs(#19): clarify lts strategy

Description

Clarifies lts strategy and updates the release details page

Close Issue(s)

closes #19

That Hatchling change really f*cked up so many things 🥲
https://github.com/litestar-org/litestar.dev/actions/runs/8548397073/job/23422061936?pr=20


refactor(api): use a js script to copy necesary files to dist

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] New Binding Issue #___
[ ] Code style update
[X] Refactor
[X] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes. Issue #___
[X] No

The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

:heart:


The deltas for test users seem wrong in matches/ratings page

Here's what it looks like in production (which is correct)

my skill went from 22.13 to 23.0 which is a gain of 0.87
But in my dev environment (wrong deltas; ignore the lack of icons which is due to my fontawesome)

My skill went from 26.29 to 25.13 which is loss of 1.16 but it shows a gain of 1.18
The deltas are also wrong for both skill, uncertainty, and leaderboard rating. I noticed this bug when I was checking Exeler's last PR to add uncertainty to this page. But then I went back to an older state of master and this bug is still there; so the bug is not from his commit. Something wrong with fake data creation perhaps?

@Jordan-Cottle can you confirm that you're also getting mathematically incorrect deltas on the match ratings page?

I noticed that some of the test data for the user did have incorrect deltas. The data in this table comes straight from the database tables, so it seems entirely reasonable that the pre-populated data from the script could just have stuff hard coded that isn't possible to have happen in prod with real data.
Example data from the database:

Notice it's just json stored in the value column, so really any data could be put in there with no correctness guarentee

Yeah, the fake data creation iirc basically uses random uncorrelated numbers for both the deltas and the ratings! So they don't make sense. Good find.
One way to improve this would be to use random numbers for the deltas only, and generate the ratings themselves with a cumulative sum over the deltas.


Send 404 when the resource or author is not found

Hello!
Right now when you search for a resource/author that doesn't exist you get an interesting response:
{
  "id": null,
  "title": null,
  "tag": null,
  "current_version": null,
  "native_minecraft_version": null,
  "supported_minecraft_versions": null,
  "icon_link": "https://www.spigotmc.org/styles/default/xenresource/resource_icon.png",
  "author": {
    "id": null,
    "username": null
  },
  "premium": {
    "price": null,
    "currency": null
  },
  "stats": {
    "downloads": null,
    "updates": null,
    "reviews": {
      "unique": null,
      "total": null
    },
    "rating": null
  },
  "description": null
}

{
  "id": null,
  "username": null,
  "resource_count": null,
  "identities": {},
  "avatar": "https://www.spigotmc.org/styles/spigot/xenforo/avatars/avatar_male_l.png"
}

My suggestion is just adding a 404 error when this happens:
{"code":404,"message":"Resource not found."}

By doing this way, we (devs that use the API) can easily catch the error rather than checking if a value is null.
Also.... Thanks for this amazing tool.

Oh, wow. This is a regression. What routes do this happen on?

Reproduced on getAuthor and getResource but not findAuthor. Thank you I will submit a patch tomorrow.

Oh! nvm, It is a bug! You were faster than me xP
Thanks again.

On findAuthor I get the correct response:
https://api.spigotmc.org/simple/0.2/index.php?action=findAuthor&name=itaquit
{"code":404,"message":"Nothing was found for that request."}

I found a discrepancy in the 404 errors:
When you navigate thru the pages of getResourcesByAuthor, listResources or getResourceUpdates you will get an empty array when you get to the last page. However, when you go to a negative number page you will get {"code":404,"message":"Nothing was found for that request."}.
Shouldn't both responses be the same?

I found a discrepancy in the 404 errors:
When you navigate thru the pages of getResourcesByAuthor, listResources or getResourceUpdates you will get an empty array when you get to the last page. However, when you go to a negative number page you will get {"code":404,"message":"Nothing was found for that request."}.
Shouldn't both responses be the same?

Fair point, I'll address this as well tomorrow. Thank you

Took me one extra day - sorry. Had stuff going on yesterday.


Cannot connect worker node to master

Summary
I have single-node microk8s instance.
Status on it:

microk8s is running
high-availability: no
datastore master nodes: <IP_ADDRESS>:19001
datastore standby nodes: none
addons:
enabled:
dashboard            # (core) The Kubernetes dashboard
dns                  # (core) CoreDNS
ha-cluster           # (core) Configure high availability on the current node
helm3                # (core) Helm 3 - Kubernetes package manager
ingress              # (core) Ingress controller for external access
metrics-server       # (core) K8s Metrics Server for API access to service metrics
rbac                 # (core) Role-Based Access Control for authorisation
disabled:
....

Firewall disabled.
Also i installed new worker node with:

microk8s is running
high-availability: no
datastore master nodes: <IP_ADDRESS>:19001
datastore standby nodes: none
addons:
enabled:
dns                  # (core) CoreDNS
ha-cluster           # (core) Configure high availability on the current node
helm3                # (core) Helm 3 - Kubernetes package manager
rbac                 # (core) Role-Based Access Control for authorisation
disabled:
....

When i make microk8s join <IP_ADDRESS>:25000/<redacted> --worker command on worker node i got:

Contacting cluster at <IP_ADDRESS>
Traceback (most recent call last):
File "/snap/microk8s/4175/scripts/cluster/join.py", line 993, in
join(prog_name="microk8s join")
File "/snap/microk8s/4175/usr/lib/python3/dist-packages/click/core.py", line 722, in call
return self.main(*args, **kwargs)
File "/snap/microk8s/4175/usr/lib/python3/dist-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/snap/microk8s/4175/usr/lib/python3/dist-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/snap/microk8s/4175/usr/lib/python3/dist-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/snap/microk8s/4175/scripts/cluster/join.py", line 986, in join
join_dqlite(connection_parts, verify, worker)
File "/snap/microk8s/4175/scripts/cluster/join.py", line 762, in join_dqlite
join_dqlite_worker_node(info, master_ip, master_port, token)
File "/snap/microk8s/4175/scripts/cluster/join.py", line 846, in join_dqlite_worker_node
update_cert_auth_kubeproxy(token, info["ca"], master_ip, master_port, hostname_override)
File "/snap/microk8s/4175/scripts/cluster/join.py", line 423, in update_cert_auth_kubeproxy
cert = get_client_cert(master_ip, master_port, "kube-proxy", proxy_token, "system:kube-proxy")
File "/snap/microk8s/4175/scripts/cluster/join.py", line 277, in get_client_cert
subprocess.check_call(cmd_cert.split(), stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
File "/snap/microk8s/4175/usr/lib/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/snap/microk8s/4175/usr/bin/openssl', 'req', '-new', '-sha256', '-key', '/var/snap/microk8s/current/certs/kube-proxy.key', '-out', '/var/snap/microk8s/current/certs/kube-proxy.csr', '-subj', '/CN=system:kube-proxy']' returned non-zero exit status 1.

In journal on master node i see:
microk8s.daemon-cluster-agent[189902]: 2022/12/05 07:50:37 POST 200 "/cluster/api/v2.0/join" 2112 bytes in 833.686178ms
Both servers - Centos7 with OpenSSL 1.0.2k-fips
How i can connect my worker node to master node? Please, help.

Hi, it appears that the openssl commands that generate kube-proxy (and most likely the second one for kubelet) fail, and I would assume that OpenSSL 1.0.2k-fips is closely related to this.
Can you please include more details by spawning a shell inside the snap environment and running the command manually? I.e.:
sudo snap run --shell microk8s

# inside the new shell, run the openssl command directly
 /snap/microk8s/current/usr/bin/openssl req -new -sha256 -key /var/snap/microk8s/current/certs/kube-proxy.key -out /var/snap/microk8s/current/certs/kube-proxy.csr -subj /CN=system:kube-proxy

The openssl command should fail, but ideally stderr will contain some useful bits to keep debugging things.

Hi! Thanks, @neoaggelos for reply!
Command output is:

Can't open /usr/lib/ssl/openssl.cnf for reading, No such file or directory
139971289392128:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:72:fopen('/usr/lib/ssl/openssl.cnf','r')
139971289392128:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:79:
unable to find 'distinguished_name' in config
problems making Certificate Request
139971289392128:error:0E06D06A:configuration file routines:NCONF_get_string:no conf or environment variable:../crypto/conf/conf_lib.c:270:

OK, I think /usr/lib/ss/openssl.cnf missing is some progress on the issue.
Do you know how to locate the default openssl.cnf file on your system? On a deb-based system, that would be dpkg -S openssl.cnf, not sure what's the command for yum/dnf.
On a related-note, can you also check whether the following helps?
sudo snap run --shell microk8s

export OPENSSL_CONF=$SNAP/usr/lib/ssl/openssl.cnf
/snap/microk8s/current/usr/bin/openssl req -new -sha256 -key /var/snap/microk8s/current/certs/kube-proxy.key -out /var/snap/microk8s/current/certs/kube-proxy.csr -subj /CN=system:kube-proxy

@neoaggelos , i searched for default and found it only in /etc/pki/tls/openssl.cnf (except /var/lib/snap/ directories, there are several dirs with openssl.cnf)
Tried with your suggestion - no luck, even with export OPENSSL_CONF=/etc/pki/tls/openssl.cnf.
The error is:
Can't load /root/.rnd into RNG<PHONE_NUMBER>53632:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/root/.rnd

Figured out, I had to execute the command openssl rand -out .rnd 16 then i used Your, @neoaggelos , suggestion with my path to openssl.cnf. After that worker node successfully connected to master.
HUGE thanks for Your support!


KidneyFibroticMicroenvironment

Project short name:
KidneyFibroticMicroenvironment
Primary Wrangler:
Ida
Secondary Wrangler:
Associated files

Google Drive: folder

Published study links

Paper: Spatially resolved human kidney multi-omics single cell atlas highlights the key role of the fibrotic microenvironment in kidney disease progression

Accessioned data: GSE211785 - not public yet!

data available from dropbox
visium images from drive, it might be shared just with Ida

Ingest

Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[ ] Are the analysis files suitable for CellxGene? If something is missing get in touch with the authors to request it
[x] Upload sheet to validate metadata
[x] Transfer raw files to ingest to validate data files
[x] Check linking using ingest graph validator
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

see thread to get the data here

see thread to get the data here

Donors
Looks like there are actually 48 donors, HK2895 is repeated in the metadata table. The number of samples is correct though

this is almost ready for review, I'm just waiting for the authors to send me the image files for Visium

ready for secondary review!

Taking for secondary review!

Looks good! Just a couple minor edits -
Project Field:
Change Estimated Cell Count to 453,782?
Donor_Organism Tab:
Disease Field:
The annotation in Supplementary Table 1 (patient clinical demographics) is unclear regarding HKD vs Hypertension. There are several individuals marked as in the 'Control' group but who are also marked as 'Yes' for hypertension. These individuals are separate from those marked as in the 'HKD' (hypertensive kidney disease) group, and they should be labelled separately with 'non-kidney specific hypertension' in the disease field, as they are in the control group.
Dissociation_Protocol Tab:
ID is sc_mechanical dissociation but the name and ontology term is for enzymatic_dissociation


All tickets not showing

Describe the bug
I have installed the helpdesk inside Django 3.0 . and used rest api authentication in it. when assessing the helpdesk by (even super user or staff) the following error shown as alert.
DataTables warning: table id=ticketTable - Ajax error. For more information about this error, please see http://datatables.net/tn/7
And the following inside the console:
GET /helpdesk/datatables_ticket_list/?draw=1&columns%5B0%5D%5Bdata%5D=id&columns%5B0%5D%5Bname%5D=&columns%5B0%5D%5Bsearchable%5D=true&columns%5B0%5D%5Borderable%5D=false&columns%5B0%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B0%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B1%5D%5Bdata%5D=ticket&columns%5B1%5D%5Bname%5D=&columns%5B1%5D%5Bsearchable%5D=true&columns%5B1%5D%5Borderable%5D=true&columns%5B1%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B1%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B2%5D%5Bdata%5D=priority&columns%5B2%5D%5Bname%5D=&columns%5B2%5D%5Bsearchable%5D=true&columns%5B2%5D%5Borderable%5D=true&columns%5B2%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B2%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B3%5D%5Bdata%5D=queue&columns%5B3%5D%5Bname%5D=&columns%5B3%5D%5Bsearchable%5D=true&columns%5B3%5D%5Borderable%5D=true&columns%5B3%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B3%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B4%5D%5Bdata%5D=status&columns%5B4%5D%5Bname%5D=&columns%5B4%5D%5Bsearchable%5D=true&columns%5B4%5D%5Borderable%5D=true&columns%5B4%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B4%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B5%5D%5Bdata%5D=created&columns%5B5%5D%5Bname%5D=&columns%5B5%5D%5Bsearchable%5D=true&columns%5B5%5D%5Borderable%5D=true&columns%5B5%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B5%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B6%5D%5Bdata%5D=due_date&columns%5B6%5D%5Bname%5D=&columns%5B6%5D%5Bsearchable%5D=true&columns%5B6%5D%5Borderable%5D=true&columns%5B6%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B6%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B7%5D%5Bdata%5D=assigned_to&columns%5B7%5D%5Bname%5D=&columns%5B7%5D%5Bsearchable%5D=true&columns%5B7%5D%5Borderable%5D=true&columns%5B7%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B7%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B8%5D%5Bdata%5D=submitter&columns%5B8%5D%5Bname%5D=&columns%5B8%5D%5Bsearchable%5D=true&columns%5B8%5D%5Borderable%5D=true&columns%5B8%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B8%5D%5Bsearch%5D%5Bregex%5D=false&columns%5B9%5D%5Bdata%5D=time_spent&columns%5B9%5D%5Bname%5D=&columns%5B9%5D%5Bsearchable%5D=true&columns%5B9%5D%5Borderable%5D=true&columns%5B9%5D%5Bsearch%5D%5Bvalue%5D=&columns%5B9%5D%5Bsearch%5D%5Bregex%5D=false&order%5B0%5D%5Bcolumn%5D=0&order%5B0%5D%5Bdir%5D=asc&start=0&length=25&search%5Bvalue%5D=&search%5Bregex%5D=false&_=1580172920432 401 (Unauthorized)
Expected behavior
This should work but i don't know why this shown ?!
As it is Said 401 Unauthorized I have tried  and added the csrftoken token inside ticket_list.html but nothings happens. the following code used but without any chance it throw the alerts with the above error:
     var tasks_table = $('#ticketTable').DataTable({
         "language": {
             "emptyTable": "{% trans 'No Tickets Match Your Selection' %}"
         },
         "processing": true,
         "serverSide": true,
         "ajax": {
		         "url": "{% url 'helpdesk:datatables_ticket_list' urlsafe_query %}",
             "type": "GET",
			  "headers": {'X-CSRFToken': csrftoken},
         },

Any advice on what should i do or where the errors is coming from ?
Thanks in Advance

I am also experiencing this issue and the above mentioned fix does not work.

I have resolved the datatable/ajax warning that the OP described but I still dont have any tickets in my all tickets view. However, they show in the dashboard.

Ok solved my problem. It wasn't obvious from the demo app but when extending the base template block helpdesk_head and helpdesk_js are important ;)

Moved my website to a new server and now this error is back.... grr.

Fixed: issue was related to nginx + uwsgi... had to set buffer-size=65535 for my uwsgi config.


add stmt_release, conn_release, var_setFromStmt and data_setStmt

These are new APIs. Please PR after eunits are merged to master. Keep the branch and please close this.


[hotfix][runtime] Delete unused code from ExecutionGraph

What is the purpose of the change
This deletes unused code from ExecutionGraph.
Brief change log

See commits

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Merging.


Add hackathon submission

Hackathon 1 submission

You’ve done a great job of solving this challenge and your use of modules is brilliant!
I really like your random world generator and your calculation of land percentage to make sure there is always land in the world.
To level up your solution you could ask the user for what size world they would like to create and you could try benchmarking your program to see if there are any bottle necks in your code where speed could be improved.
Your function using recursion to implement the boundary fill algorithm is very clearly written and you’ve used comments to great effect which will make your code much easier to maintain in the future, same with your excellent variable names.
Congratulations on solving the hackathon challenge and good luck with the rest of the summer of code!


Use Dir.glob instead of git ls-files

Hi,
Thanks for working on whenever so far.
However, whilst maintaining this in Debian, I found it to have an unnecessary dependency on git whereas that could be very well avoided by using Dir.glob.
This PR fixes the same :)

The dependency on git should only be for packaging the gem, not using it.

Hi @benlangfeld,

The dependency on git should only be for packaging the gem, not using it.

That's right. I maintain whenever in Debian :)
And we need to patch out git to avoid an unnecessary dependency and it'd be very nice (and kind) if this could be updated here, in upstream itself :smile:
Hope this makes sense and could be merged :taco:

Hi @benlangfeld,

The dependency on git should only be for packaging the gem, not using it.

That's right. I maintain whenever in Debian :)
And we need to patch out git to avoid an unnecessary dependency and it'd be very nice (and kind) if this could be updated here, in upstream itself :smile:
Hope this makes sense and could be merged :rocket:

I think you misunderstood what I said.  You shouldn’t need a git dependency at runtime if you’re getting them gem from rubygems.org. If you’re pulling the source code then you’re doing it wrong.

Hi,

I think you misunderstood what I said. You shouldn’t need a git dependency at runtime if you’re getting them gem from rubygems.org. If you’re pulling the source code then you’re doing it wrong.

I think I was not clear. I'll try to be more verbose :)
When I say I maintain this gem in Debian -- that means, I packaged it for apt repositories.
While doing so, I need to build it from source and run tests to make sure that everything's alright. I can't just pull it from anywhere. And while building it from source, I hit this obstacle where I needed to patch the usage of git altogether. I hope that makes sense now? :smile:
Also, what I don't understand is why would you be not interested in using Dir.glob instead of git? Is there any particular reason?
(I've patched the same thing in multiple gems, none seem to have this problem and were happily merged. So I am curious to know if there's anything blocking you in doing so?)

Hi,

I think you misunderstood what I said. You shouldn’t need a git dependency at runtime if you’re getting them gem from rubygems.org. If you’re pulling the source code then you’re doing it wrong.

I think I was not clear. I'll try to be more verbose :)
When I say I maintain this gem in Debian -- that means, I packaged it for apt repositories.

I know very well what this popular phrase means.

While doing so, I need to build it from source and run tests to make sure that everything's alright. I can't just pull it from anywhere. And while building it from source, I hit this obstacle where I needed to patch the usage of git altogether. I hope that makes sense now? :smile:

This project is distributed via rubygems.org. Your project is based on not liking Rubygems and choosing to instead use your own packaging and distribution format. You choose to behave as a developer of the project, rather than a consumer of it. Git is a development dependency of the project. You therefore require git. If you instead behave as a consumer, by fetching an official release of the project from rubygems.org, you don’t inherit the dependency on git.

Also, what I don't understand is why would you be not interested in using Dir.glob instead of git? Is there any particular reason?

Git is used here to ensure that only tracked files, and not temporary ones which may be generated as part of the build process or otherwise such as log files, are included in the released gem. A glob cannot ensure this.

(I've patched the same thing in multiple gems, none seem to have this problem and were happily merged. So I am curious to know if there's anything blocking you in doing so?)

This project is distributed via rubygems.org. Your project is based on not liking Rubygems and choosing to instead use your own packaging and distribution format. You choose to behave as a developer of the project, rather than a consumer of it. Git is a development dependency of the project. You therefore require git. If you instead behave as a consumer, by fetching an official release of the project from rubygems.org, you don’t inherit the dependency on git.

You are wrong here. We do pull it from rubygems and then add a debian/ directory to it.
There's this tool called gem2deb, which pulls the gem from rubygems.org and converts it into a Debian package.
When run, it pulls all the files that you ship in the gem release and builds on top of it. Of course, it also pulls the gemspec with git in it :)
This is why we need to patch it.

Also, what I don't understand is why would you be not interested in using Dir.glob instead of git? Is there any particular reason?

Git is used here to ensure that only tracked files, and not temporary ones which may be generated as part of the build process or otherwise such as log files, are included in the released gem. A glob cannot ensure this.

(I've patched the same thing in multiple gems, none seem to have this problem and were happily merged. So I am curious to know if there's anything blocking you in doing so?)

When run, it pulls all the files that you ship in the gem release and builds on top of it. Of course, it also pulls the gemspec with git in it :)
This is why we need to patch it.

At what point do you execute the contents of the gemspec? Within gem2deb? What is the problem with the machine which executes gem2deb requiring git to be installed (which is included in the gem2deb documentation? You shouldn't have to specify git as a dependency of the resulting dpkg, which I agree would be onerous.

I added more comments to my previous comment: https://github.com/javan/whenever/pull/804#issuecomment-632723646. Can you take a look and reply to them as you see fit? :)

At what point do you execute the contents of the gemspec? Within gem2deb? What is the problem with the machine which executes gem2deb requiring git to be installed (which is included in the gem2deb documentation)? You shouldn't have to specify git as a dependency of the resulting dpkg, which I agree would be onerous.

We get the skeleton Debian package by gem2deb which is based on pulling files and data shipped in the gem's release.
This takes the files shipped and adds a debian/ directory to it -- for preparing the Debian package.
Next, we work on running upstream tests, adding your LICENSE to it, and other things to check if there's nothing wrong and give a quick look at the things pulled.
Next, we build the package via dpkg-buildpackage -uc -us which does the initial build.
Next comes the role of a static analyzer which helps us in determining if there's anything wrong.
When this is all done, we do a final build in a clean environment, schroot or sbuild. This means building a package in a clean container with only having the gem's build dependencies and nothing extra.

Now, of course, we ourselves use git to manage the packaging repositories. But we cannot add git as a dependency to it as you've guessed why.
Since we do not add git as a dependency, the build in the clean container fails when it sees the usage of git but not having git installed. Therefore, making the package not build-able.
To avoid this, we generally patch the usage of git in the way such that both upstream maintainers are happy and so are we. We respect the work you do and we'd like to help you as much as possible.
For it to happen, we'd expect a little help from you, too, in the form of asking you to adapt a way to avoid git in gemspec in such a way that is not only right but with which, both of us benefits :)

Why do you expect a build of source code to work in an environment that doesn’t include that code’s development dependencies? If you’re shipping a compiled C++ project, does that build container not include a compiler?

Of course it has all the dependencies in the environment. Just not git.
Would you want to add git to your gemspec? No, I suppose. That's what I mean. We can very well achieve the same functionality without using git in gemspec. It's an unnecessary usage, really.
And for the latter part, of course. We don't ship compiled stuff but build them during our package build. And of course, yes.

Git is a dependency of this project in the same way that gcc or similar is a dependency of a C project. I don’t understand why that is controversial.

I am very surprised that you said this.
Are you by any chance comparing what gcc is to C, the same is git to this project?
D'you need git for doing any compilation work or anything? I don't think so.
I'm not only surprised but shocked to see this resistance for something that can be done using plain Ruby. I'm willing to understand your point if you give me a valid explanation as to why can't you drop git and use some other alternative for doing the same work. I can further list 3 more alternatives that you can adapt to if you don't want to use Dir.glob.

This has got petty and uncooperative. I’m done. Thank you for your suggestion.


chore: jsonfmt labservices

Ran jsonfmt -w "specification/labservices/**/*.json"

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Can one of the admins verify this patch?


Embedding dimension mismatch error in LayoutLMv2

File "project_dir/code/repos/unilm/layoutlmft/layoutlmft/models/layoutlmv2/modeling_layoutlmv2.py", line 668, in _calc_img_embeddings
embeddings = visual_embeddings + position_embeddings + spatial_position_embeddings
RuntimeError: The size of tensor a (64) must match the size of tensor b (8) at non-singleton dimension 0
For more detail these are the exact dimensions:
(Pdb) visual_embeddings.shape
torch.Size([64, 49, 768])
(Pdb) position_embeddings.shape
torch.Size([8, 49, 768])
(Pdb) spatial_position_embeddings.shape
torch.Size([8, 49, 768])
Any idea why this mismatch is occurring?

From what I have been able to figure out, running the code without the distributed launch param for example:
python examples/run_funsd.py         --model_name_or_path microsoft/layoutlmv2-base-uncased         --output_dir tmp/test-ner         --do_train         --do_predict         --max_steps 1000         --warmup_ratio 0.1         --fp16
gives that error.

It looks like that image.shape[0] and bbox.shape[0] is different. You should check your dataset implementation.

I am using the predefined FUNSD dataset. I don't think there should be a bug in that (hopefully).

I was receiving a similar error when trying to run the script unilm/layoutlmft/examples/examples/run_funsd.py but with different values of Tensor sizes. Looks like the training wants to use all GPUs. I have two.
The error no longer appears once I changed --nproc_per_node to match the number of GPUs:
python -m torch.distributed.launch --nproc_per_node=2 examples/run_funsd.py ....


Prioritizing TODOs

Noticed a fair amount of TODOs in the code, would be great to prioritize what needs to be done. Maybe ranking it in terms of difficulty as well for contributors who are at the beginner level all the way to expert?

Sure :).  Should I start adding them as issues, or is there a better way to organize?

I think adding them to the issues, and then having some sort of priorities tags (or even how hard they might be) within the issues, would be great. Could clear the TODOs out of the actual code. I haven't had time to look into any of them in the code yet, but it would definitely make the project more accessible.

Yes exactly what @eseglem said! How about something fairly simple like this:

Beginner
Intermediate
Advanced

Maybe then we can have a separate set of labels to denote urgency such as:

Urgent
Necessary
Nice to Have

Feel free to edit/modify. Not too familiar with labels yet on GitHub but will update as I find out more.

Looks good to me :).   I'll start tagging current issues, and try to get to TODOs next.


Issue with k8s.io/docs/tutorials/kubernetes-basics/expose-interactive/

This is a...

[ ] Feature Request
[X] Bug Report

Problem:
kubectl get pods <--Option> run=keubernetes-bootcamp
Confusion with  in the above command. The option looks like 1 in the command.
When we type command manually on the provided terminal,  there is little confusion. But when we click on the command that you have provided on the left side panel it works fine.
Proposed Solution:
Page to Update:
http://kubernetes.io/...

this is l, meaning label. The option will help select pod by label.

you can input kubectl get pods kubernetes-bootcamp-390780338-st3vd -o yaml to inspect all the details.

Thanks @zhangxiaoyu-zidif


Add build status badge to README

I'll not wait on @kuchenkruste to do the review. (One person should be sufficient :)).
Thank you @rexim for the review!


[FEAT] Selecting a row doesn't unselect the rest

I don't know if you meant this as a feature but currently, selecting a row in "multiselect" mode just adds another selection.
The standart is usually - ctrl+click to multiselect and click to select one and unselect the rest.
I see that evt is being sent to the listener, so it should be as easy as:
if (evt.ctrlKey), but shouldn't default be as the standart? (by standart I mean kendoUI, excel etc.)

This is a design choice to support tablets.  Multi-select explicitly works by allowing you to toggle each row.
There is an option modifierKeysToMultiSelect that may give the behaviour you want.

Sorry - it's in the tutorial. I've missed that.
This leaves the following issue unresolved though: #3214

As that issue is separate from this one, can this be closed?


Redundant code in slick.pager.js

Hello
I was just changing the status text of the pager that gets displayed. Then I saw this code:
https://github.com/mleibman/SlickGrid/blob/master/controls/slick.pager.js   Line 135 - 146
if (pagingInfo.pageSize == 0) {
var totalRowsCount = dataView.getItems().length;
var visibleRowsCount = pagingInfo.totalRows;
if (visibleRowsCount < totalRowsCount) {
$status.text("Showing " + visibleRowsCount + " of " + totalRowsCount + " rows");
} else {
$status.text("Showing all " + totalRowsCount + " rows");
}
$status.text("Showing all " + pagingInfo.totalRows + " rows");
} else {
$status.text("Showing page " + (pagingInfo.pageNum + 1) + " of " + pagingInfo.totalPages);
}

The $status.text("Showing all " + pagingInfo.totalRows + " rows");  just overwrites the if above it.
What should this code be.
Thanks

This has been integrated into my 'alternative master'. See https://github.com/mleibman/SlickGrid/issues/1055


Add Event speakers list

Is it a ?

[ ] Bug Report

[x] Feature Request

[ ] Chore

Bug Report
Actual Behaviour
There is no provision for the admin to see the speakers for his event
Expected Behaviour
There should be an option in the Navigation drawer for that
Would you like to work on the issue?
Yes

@iamareebjamal should i go on with this

See my response at #648

Parent issue
#925

@srv-twry sorry didn't see your message initially, i am stuck in my semester exams as of now, so you can take this issue. I'll resume my work as soon as i get free.


[Feature request]Ignore games

Would it be possible to add a feature to ignore a selected game, even with watch‑unlisted‑games set to true so certain games can be skipped?

Yes, I will start working on this.


Monitor scaling behaves weird on Windows.

Contour Terminal version
Contour Terminal Emulator <IP_ADDRESS>42
Installer source
GitHub: release page
Operating System
Windows
Architecture
x86-64
Other Software
No response
Steps to reproduce
Have two monitors where one is set to 100% scale and the other to 125% scale. Open contour on the 100% scale monitor and move it to the other one.
Expected Behavior
No response
Actual Behavior
This is how contour looks on the 100% scale monitor:

And this is how it looks on the 125% scale monitor:

The horizontal distance between characters is somehow squished.
Here's another view on the 125% scale monitor, where the top one was opened on the 125% scale monitor, while the other one was opened on the 100% scale and move to the 125% scale:

Additional notes
No response

Can be connected to https://github.com/contour-terminal/contour/issues/940

This is an interesting one. I actually implemented responding to monitor changes (and thus, responding to DPI changes) in the frontend code. But I obviously did something wrong there. At least it worked back then when we only used Qt Widgets. We need to re-assure how this should be working when using QML I think... 🤔

@christianparpart I just grabbed the later msi from https://github.com/contour-terminal/contour/actions/runs/8314676103, because I thought #1487  might fix this and indeed it did.

@christianparpart I just grabbed the latest msi from https://github.com/contour-terminal/contour/actions/runs/8314676103, because I thought #1487 might fix this and indeed it did.

Thanks for checkin @ferdinandyb  :)
I am closing this issue then


Migrations do not migrate

I've tried running the shipped migrations and it seems that they may may have gone out of sync with one another at some point in time around 12 or 13. I attempted removing the migrations directory and running makemigrations from anew and everything seems to run well, so it make be good to do this permanently in the repo; to ditch the existing migration files and ship a single base migration and any other further OSS changes can be applied on top.
It looks like the only data migrations in place are:

0013_auto_20160222_2046.py
0025_auto_20160224_1450.py
0027_auto_20160224_1543.py
0031_auto_20160224_2219.py

All of which appear to be simple updates for existing data during development and are irrelevant to any newly created databases.

Hi @richardpetithory -  thanks for the issue report.  Ill take a look at this tonight / tommorrow.  If you have a moment, would  you mind submitting a PR with a clean slate of database migrations?  To your point, there were a handful of migrations created during development the last several months that are not necessary to the long term health of this repo.

closing due to merged PR


Thank You Note & Minor Comment On poetry Usage

(1) Thank you very much for EIR!
(2) I expect to use EIR in the near-term future.
(3) I hope to provide user feedback on EIR.
(4) I found EIR through a series of links that begin initially with the desire I've had to reproduce Accurate Genomic Prediction of Human Height (2017).
(5) I very much appreciate your use of .pre-commit and poetry!
(6) Feel free to ignore the following minor suggestions:

Some minor suggestions...
Consider moving pytest to tool.poetry.group.test.dependencies.
Consider removing poetry.lock from git tracking via: git rm --cached poetry.lock (after adding poetry.lock to your .gitignore).
Consider adding, to your .gitignore, some of the content in the default Python .gitignore found here https://github.com/github/gitignore/blob/main/Python.gitignore.
Consider adding your GitHub account email or username to authors in pyproject.toml.
Consider using ruff in pre-commit (see here) instead of flake8. Also, this article can provide further context.
(might be asking a lot) Consider using polars over pandas for the sake of speed.

(7) Again, thank you for your work; may this repository live a long and useful life!
This issue may be deleted once read. Any accepted suggestions can be addressed in other issues.

Hi! Thank you for your very nice comment and great points!

Consider moving pytest to tool.poetry.group.test.dependencies.

Good point, currently I have it in [tool.poetry.group.dev.dependencies] but later I might make a separate group specifically for testing.

Consider removing poetry.lock from git tracking via: git rm --cached poetry.lock (after adding poetry.lock to your .gitignore).

Fair point, but I think I will keep it for now to allow for reproducible environments, e.g., when cloning the repository.

Consider adding, to your .gitignore, some of the content in the default Python .gitignore found here https://github.com/github/gitignore/blob/main/Python.gitignore.

Good suggestion, I have updated the .gitignore file with some things I was missing from that link, thanks!

Consider adding your GitHub account email or username to authors in pyproject.toml.

Thanks, added some more information to pyproject.toml.

Consider using ruff in pre-commit (see here) instead of flake8. Also, this article can provide further context.

For now, flake8 is actually quite snappy for my use case, but ruff is definitely something I have been keeping on my radar for potential future use.

(might be asking a lot) Consider using polars over pandas for the sake of speed.

Yes, this is also something I have been considering, specifically for potentially speedup in reading large .csv files. For now, I have been experimenting with using the pyarrow backend in pandas, but might look into switching some parts to using polars later when I have time.
Thank you for your kind words and suggestions that help me improve the project!


The Attention code

Hi,ematvey. I have read the paper and I don't understand your code of the attention mechanism. According to you code ,how can I get the weight of each word in a sentence ?
thx.

The weighted projection seems to be incorrect.

@scylla can you be more specific?

@ematvey in file model_components.py while calculating weighted_projection in function task_specific_attention i think we need to use inputs in place of input_projection, please correct me if i am wrong.
thanks

@scylla the usage of input_projection is correct but the attention_weights are wrongly computed.
@ematvey sent a pull request fixing that #5

@jknair You are right, thanks for the PR! Amazing how such a serious bug only marginally degraded the performance.
Let's see how this affects performance. I'll retrain and report back the results.

Considering the number of classes were very less with the bug the system actually learnt across every dimension of the attention context vector. Apparently it learnt something 😁

Strange, but accuracy only increased to 66.3% (from 65%), and I'm not sure if this is a result of attention fix and not due to longer training.

@ematvey  inside the function bidirectional_rnn() at model_components.py, line 25 is
outputs = tf.concat((fw_outputs, fw_outputs), 2). Shouldn't it be
outputs = tf.concat((fw_outputs, bw_outputs), 2) if you want to consider the backward output
for the attention too?


404 Not Found nginx/1.18.0 (Ubuntu)

Execute chmod +x ./download_metadata_3rscan.sh && ./download_metadata_3rscan.sh, or
chmod +x ./download_3dssg.sh && ./download_3dssg.sh, and 404 not fuound appears.

Hi, I have the same problem, have you solved it?

Hi, when I want to download the checkpoint for the training model and the Atlasnet weight, I perform "chmod + x ./download_checkpoints.sh & ./download_checkpoints.sh and the same "404 not found" also appears. How did you solve it?

https://github.com/he-dhamo/graphto3d/issues/12#issuecomment-1256978552


[BUG] - Setting view doesn't shows the icon

It seems that we want to show a icon and a text in the setting view. But it doesn't work. It because if we want to use a setting-view type tab view, we need use swiftui lifecycle. And we should add this.
struct XXX: App {
    var body: some Scene {
        Settings {
            // view
        }
    }
}

We need to change the TabView to be a window toolbar instead.

See Apple HIG and What's new in macOS 11 for reference

I have fixed it.

#148


Add statement_timeout to PostgreSQL connection parametres.

Closes #129

@vadz sql << "SET statement_timeout = whatever"; makes perfect sense. I agree, it's hard to justify the code clutter when one can achieve the goal via the existing SQL interface.
I'm dropping the idea.


how would one use supervisor in combination with celery worker this way?

how would one use supervisor in combination with celery worker this way?
what would the supervisor celery task look like? would it all be called from manage.py?

Not sure, I haven't really used supervisor so I wouldn't know.


Update Windows usage.

Fixes Issue
Example invocation doesn't work in cmd
Description of Change
Fix CLI invocation.
Have test cases been added to cover the new functionality?
No.

Can one of the admins verify this patch?


Only locals can be passed by reference

I am getting when trying to pass a field as a ref argument:

Only locals can be passed by reference.

Why is this limitation?
What is preventing it from being implemented for fields as well?

Still no change to get it implemented in the roslyn branch?

See #365


User-reported unhelpful error message

Program: https://code.world/haskell#PC4qzxqErhLUFHE4eagVhVg
Message:
program.hs:73:8-20: error:
    Variable not in scope:
      interactionOf
        :: Coord
           -> (Double -> Coord -> Coord)
           -> (Event -> Coord -> Coord)
           -> (Coord -> Picture)
           -> IO ()

Someone working from old CIS 194 materials.  We're not going to undo this deprecation, and the materials have already been updated at https://haskell-via-sokoban.nomeata.de/  Nothing more to do.


Balanced data

Hi Junhao,
One more question. Just wanted to make sure I've understood the code correctly.
By default, HYDRA (for clustering) assumes the data is balanced.
In my data, I have more controls than patients, so I should put in false for this argument?
Thanks,
Jonah

Hi Jonah,
You should leave the argument class_weight_balanced to be True by default. SVM from sklearn will deal with imbalanced data with tricks.
Also, re., the influence of sample size or data imbalance, we have our preliminary results here: preprint This may give you a general hint if your results are reasonable or not.

Great, thanks for clarifying!


Feature/for 135 - Adding support for select components default value (single/muti)

FOR-135 - Adding support for select components default value (single/muti)

Uses: https://github.com/formio/ngFormBuilder/pull/200


Error when using _ function to render react component in cell formatter

Describe the bug
A clear and concise description of what the bug is.
Additional context
When loading a page that contains Grid component in react (v.18) atm error is displayed in console
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17
I have tried to remove call to _() and error is gone.
_() is used to render additional buttons in the very last right-hand side column.

@nem-c Did you find a workaround for this issue?


feat: add bodyScrollLock when sideBar is open

Summary
Add bodyScrollLock when sideBar is open.
Related Issue

Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

Closed due to outdated, feel free to reopen it.


Authentication error when attempting to use org token

When attempting to use the provider for the first time I am encountering an authentication error. I am attempting to authenticate via MIST_API_TOKEN using an org token. I have verified the API token is valid.
Error Message
│ Error: Authentication Error
│
│   with provider["registry.terraform.io/juniper/mist"],
│   on <empty> line 0:
│   (source code not available)
│
│ required field `email` is missing for type `Admin`
│ required field `first_name` is missing for type `Admin`
│ required field `last_name` is missing for type `Admin`

Repro
terraform {
  required_providers {
    mist = {
      source = "juniper/mist"
      version = "0.1.16"
    }
  }
}

data "mist_sites" "sites" {
  org_id  =  "redacted"
}

Additional Context
It appears this error message is coming from validation in the mistapi-go admin struct

I believe specifically the issue is coming from
https://github.com/Juniper/terraform-provider-mist/blob/e989330f1955272a52c74ccdff635e72390854c5/internal/provider/provider.go#L353 where SelfAccount won't respond with first_name last_name or email.
It will only respond with an object like
{
    "name": "pulumi-test-token",
    "privileges": [
        {
            "scope": "org",
            "org_id": "redacted",
            "role": "admin",
            "name": "Test Org"
        }
    ]
}

so that will cause the model validation to fail as referenced above

Hi @zbuchheit ,
I updated the mistapi-go SDK to fix the issue, and updated the terraform provider to use the latest version of the SDK. This issue should be fixed.
Thanks.

Fixed via newest release of the SDK


merge main to nightly automatically

This has been validated with our nightly(daily) run https://github.com/awslabs/aws-orbit-workbench/pull/1237


Use PHP_SAPI instead of php_sapi_name()

In Symfony code we only use PHP_SAPI and https://secure.php.net/manual/en/function.php-sapi-name.php says:

Note:
The PHP constant PHP_SAPI has the same value as php_sapi_name().

👍

Thank you @javiereguiluz.


Fix texture filtering

Loading textures was broken. I fixed it by removing loadTextureRaw and actually using the TextureFilter type, which was there, but wasn't used anywhere. Now it is. Also the thwomp.elm example is fixed.

You can now run elm-reactor in your working copy of elm-webgl and have the thwomp.elm example working.

Haven't looked closely, but the idea is that the texture function should have a sensible default rather than it always be required (beginner friendly don't have to think about filters). So I don't like the removal of that. What do you think?

Well, it was broken in the first place, it wasn't even working because you were calling the native function with 2 args, while it was only taking one. I don't have an opinion on the sensible default, I guess it's ok, and that's why there is loadTexture function. For the rest, there is loadTextureWithFilter, right? So I didn't really remove that sensible default.

This seems correct, internally more idiomatic, and externally preservers sensible defaults.

Any chance of having this merged?

Any word on merging this in? I've hit this error as well, and it'd be nice to use textures in my game.


Writing a register array does not work

How to reproduce
The setup: I have a memory with a read and write port, reg [31:0] mem [0:3]. A simple counter will serve us as address. The memory is initialized to all 0xAAAA and we want to write it all to 0xBBBB. Here's the Verilog code (The contents of mem_reset.bin is all 0xAAAA, you can imagine):
module MulAccVerifier (
  input               reset,
  input               clk
);
  reg [2:0] counter;
  reg [31:0] mem [0:3];

  /* Init handling */
  always @(posedge clk) begin
    if($initstate()) begin
      assume(reset);
    end
  end
  initial begin
    $readmemb("mem_reset.bin",mem);
  end

  always @(posedge clk) begin
    if(!reset) begin
      if(counter == 3'b111) begin
        /* Fail on purpose for debugging */
        assert(1'b0);
        assert((mem[counter[1:0]] == 32'hBBBB));
      end
    end
  end

  always @(posedge clk) begin
    if(reset) begin
      counter <= 3'b000;
    end else begin
      counter <= (counter + 3'd001);
      mem[counter[1:0]] <= 32'hBBBB;
    end
  end
endmodule

Actual behavior

The writes are very sporadic. They may be cycles late, and more often than not only one of the values is written at all. This is really non-deterministic based on what the solver produces as counter-example (well each run gives the same result, but the result may vary if the net list changes), and I couldn't really figure out a pattern.
Note that I am running this through SymbiYosys because this initially came up during formal tests and the issue didn't appear in my simulation (I think it's using Verilator, but not sure). The .sby file is very simple, it sets mode bmc, depth 15, [engines] smtbmc and reads the verilog and the bin file.
Expected behavior

I got this behavior by replacing the mem[counter[1:0]] <= 32'hBBBB; line in the above snippet with
      int i;
      for (i = 0; i < 4; i = i + 1) begin
        if (counter[1:0] == i) begin
          mem[i] <= 32'hBBBB;
        end
      end

With that change, Verilog prints Warning: Replacing memory \mem with list of registers. which I think may be relevant to locate the root source of the bug.
I did not check in-depth for issue duplicates, but this may be related to #2570. My yosys version is Yosys 0.9+4052 (git sha1 687f381b69, gcc 10.3.0 -fPIC -Os), I will try again with master tomorrow. symbiyosys is from master.

traced down to some kind of non-deterministic bug in yosys-smtbmc


Update Composer dependencies (2023-12-10-00-10)

Visual regression test passed!
View the visual regression test report


Project Admin: Create Component List Board

A project board needs to be created to identify the list of items to be added in the libray.

Board was created here: https://github.com/orgs/Orange-OpenSource/projects/13/views/2

Have chacked with @mccart77 for the top of the list:


DPO with Axolotl

It is possible to perform DPO with Axolotl. If I were to create a notebook for DPO fine-tuning, do you think it would be suitable for your repository?

Hi Johan, thanks for your suggestion. I actually made one, will release it
soon. Feel free to suggest improvements if you're interested, it's not
perfect but it works haha.
On Thu, Feb 15, 2024, 20:09 JohanWork @.***> wrote:

It is possible to perform DPO with Axolotl. If I were to create a notebook
for DPO fine-tuning, do you think it would be suitable for your repository?
—
Reply to this email directly, view it on GitHub
https://github.com/mlabonne/llm-course/issues/48, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATL5EGUCTEEUJUIC2BRK62LYTZTOPAVCNFSM6AAAAABDK4LN4WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTOMZVHA2TSNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

aa nice, looking forward to it. Will do!


Error creating new directories

Using elFinder to create a new directory in the root of a bucket, an error is thrown.
Whilst elFinder shows an error, the directory is actually created in the GCS (checked using the GCS console).
I think the problem is with this adapter though.
In the upload() method, uploadType is always set as media which may cause a conflict with elFinder.
It also seems to always want to set data to $contents, which is passed an empty string via createDir() which again is likely to cause issues?

GCS has no real concept of folder vs files, everything is really just an object.
To create what looks like a folder, it's just an empty object with a trailing /.
I'm not sure why elFinder would be choking, but my sample code seems to test fine:
$newDir = $filesystem->createDir('new_directory_test');
var_dump($newDir);
var_dump($filesystem->listContents('new_directory_test'));

$objects = $filesystem->listContents();
foreach ($objects as $object) {
    if ($object['path'] == 'new_directory_test') {
        var_dump($object);
    }
}

bool(true)
array(0) {
}
array(8) {
  ["type"]=>
  string(3) "dir"
  ["dirname"]=>
  string(0) ""
  ["path"]=>
  string(18) "new_directory_test"
  ["timestamp"]=>
  int(1463657952)
  ["mimetype"]=>
  string(10) "text/plain"
  ["size"]=>
  string(1) "0"
  ["basename"]=>
  string(18) "new_directory_test"
  ["filename"]=>
  string(18) "new_directory_test"
}

The only thing which may be odd to elFinder is the mimetype.  The upload() function calls Util::guessMimeType which returns 'text/plain' for empty string; so directories are created with mimetype 'text/plain'.  If I create a folder via the GCS console, folders are created with mimetype 'application/x-www-form-urlencoded;charset=UTF-8'.  I'm not 100% sure this would be the issue though.
Could this also be related to https://github.com/Superbalist/flysystem-google-storage/issues/23

I think it could have been connected the the bucket ACL, but I can't remember

Can you please test if this is still happening, so that we can mark this as resolved?

Sorry, I'll try and check this week for you.


Refactor to support "sl-ember-components" class pattern

@notmessenger please assign to me and change title to

Refactor to support "sl-ember-components-[component]" class pattern

@notmessenger please assign to me and change title to

Refactor to support "sl-ember-components-[component]" class pattern

@notmessenger please assign to me and change title to

Refactor to support "sl-ember-components-[component]" class pattern


Added support for sshfs

Nice! The only thing that doesn't work:
sftp -P 2222 localhost
> cp file.md .
> Server does not support copy-data extension

sftp itself doesn't have support for cp within the protocol. What you want is to cp over using sshfs. You do that by doing
sshfs -p 2222 localhost:/project /tmp/test, where /tmp/test is an empty directory that exists. Then you can cp files into /tmp/test. You could also mount the root / instead of /project. Which would allow you to see projects and create a new one with mkdir.


Undesired code block line height under edit mode

Hi,
It seems that the code block lines have undesired line height under the edit mode:

This is caused by the top/bottom padding of the line divs under the code mirror editor.

I haven't gone through the theme file yet so I won't be able to create a PR without screwing up the codes :( But I guess the quickfix is to just remove the top/bottom paddings on all div.HyperMD-codeblock elements.
Thanks for making this great theme!

Fixed! Enjoy.


Compliance check on NIfTI properties

Nifti files have a small header and they can be checked for compliance. Add it to bids_dataset compliance check

key properties of MR volumes are present only in NIfTI headers but NOT in JSON sidecars e.g., number of volumes, voxel size, image dimensions, and image obliquity...
cross link https://github.com/Open-Minds-Lab/MRdataset/issues/4


Minor grammar/spelling corrections

@paulkel : Thanks for your contribution! The author, @barclayn, has been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author, @barclayn, has been notified to review your proposed change.

Merging typo fixes.
@paulkel Thanks!


Fix deadlock in test_reaching_max_in_flight_requests.

Fixes #49.

This ended up making its way to master in a convoluted route... Thanks for the PR :)


LAMMPSBaseParser: Fix parsing for nodes with the script input

The BaseLammpsCalculation plugin was recently updated to allow specifying the exact script to run through the script input node. If the default parser is used in this case, which is the LAMMPSBaseParser, a non-zero exit code would always be returned because some of the output files that the parser wouldn't be there. These output files are normally written by the script that the plugin itself would create, but if a complete script is taken from inputs, it cannot be guaranteed that the script will produce these same outputs.
The parser is updated to only return an exit code if an expected output file is not in the retrieved files if the script input was not defined. In addition, the total_wall_time key, if parsed by the log file parser, is parsed and converted to seconds and added as the total_wall_time_seconds key.

I think it looks good, just remove the print statement in the parser when dealing with the global variables.

Done.

any idea why the previous tests did not catch this issue?

Well, as far as I can tell, this parser was not tested whatsoever. I think that this parser was maybe the original one (together with BaseLammpsCalculation) and they were never tested. When you started to refactor things, you added tests, but only for the new plugins that you added (lammps.force, lammps.md, etc.).
We should maybe think how to harmonize all of these, because now there seems to be some duplication.

any idea why the previous tests did not catch this issue?

Well, as far as I can tell, this parser was not tested whatsoever. I think that this parser was maybe the original one (together with BaseLammpsCalculation) and they were never tested. When you started to refactor things, you added tests, but only for the new plugins that you added (lammps.force, lammps.md, etc.).

Well that explains it. It is very nice that you added a test for the parser. I think that the plan was to do that sometime ago, but well clearly I must have forgotten to do it.
I'll look and see if more tests are needed to make sure that no funky business can happen.

We should maybe think how to harmonize all of these, because now there seems to be some duplication.
I agree 100% I think that the idea that @chrisjsewell had was that we should leave the old functions in case somebody needs them. But I think it might actually be best to remove them, or mark them for deprecation and make the test more modular. Since we end up having a lot of duplication and it is easy to miss something.

So I'm all for removing the old parsers and calcjobs and keep the new ones and just run with that.

So I'm all for removing the old parsers and calcjobs and keep the new ones and just run with that.

That'd be fine with me as well, as long as I can still port over the functionality that I still added that allow adding a complete script as input and have the wall time seconds parsed. But if you are ok with that as well, then I am fine with opening a PR for that.

@JPchico did anything still needed to be done for this PR?


spelling: notwithstanding

Why:
Closes: #30943

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[ ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

@jsoref Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏

@jsoref Thanks so much for opening a PR with this fix! I'll update the branch and will need to get an approval from our site policy team - but once that is finished, I'll get this merged 🍏


About Multi-Mnist support

Is the  Multi-Mnist experiment of the paper supported in this code?……

@Icedeath Not supported by now. You can arrive there yourself based on this code.


Layer not working when published to npm

Environment

Operating System: Linux
Node Version:     v18.16.0
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      ssr, extends, modules, vuefire, runtimeConfig, css, build
Runtime Modules<EMAIL_ADDRESS>Build Modules:    --

Reproduction

Create a normal nuxt 3 app project

Create a nuxt 3 layer project

Add some libraries in the layer project, example: vueuse, firebase, vuefire, atob, crypto.js, etc...

Create composables on layer project to share

In the app project, extend from the project layer using a local path

npm run dev and everything will be fine

Now in layer project run npm run build

Then run npm publish --access public

In app project do npm intall your-layer-package

Describe the bug

Replace the app project extends with the name of the newly installed lib, example: extends: ['your-layer-package']
Try npm run dev on the app project again and you will get some errors for some of the installed packages.
In my case it was the atob and btoa packages.
I also get nuxt cache error when enabling ssr: true in app project.

Additional context
No response
Logs
The requested module '/_nuxt/node_modules/crypto-js/aes.js?v=0e140044' does not provide an export named 'default'

At the nuxt.config.ts of your app layer (the top)
add the vite section as shown
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  extends: ['YOUR_LAYER'],
  vite: {
    optimizeDeps: {
      include: [
        'crypto-js' // or other packages, which lead to this issue
      ]
    }
  },
})

Duplicate of https://github.com/nuxt/nuxt/issues/19426

But this is counterproductive! Imagine I'm developing a lib and I want to share it publicly with other people via NPM. I cannot require this level of configuration for anyone wanting to use my lib! I don't need to do this with any other lib in any other development stack I've ever used.

@derHodrig However, including the package in optimizeDeps did nothing.

Let's track in https://github.com/nuxt/nuxt/issues/19426.
Note that you can add configuration (optimizeDeps) in the layer itself so your consumers don't need to add it.


Added how to install with composer

Hi @dominikzogg
I added the two PRs here
https://github.com/saxulum/saxulum-doctrine-orm-manager-registry-provider/pull/5
https://github.com/saxulum/saxulum-doctrine-orm-manager-registry-provider/pull/4
Regards!

@royopa Thank you! 3.0.1 and 2.2.1 are the releases from your pull requests


Moving picture screenshots

Screenshots are nice, but they don't show the possibilities of motion or user interactivity.
Gifs would help demonstrate the options of the interface. A screencast with mouse and keyboard captured would be even better.

unlikely to happen in the near future


DD widget could have better zoom support for circles, ellipses, rings

Enhancement request:  I find that the mouse-wheel zoom functionality in web apps is disabled while you are creating some geometries (circle, ellipse, rings) interactively in the Distance and Direction widget.
Normally, in a WAB app you can zoom/pan in and out by setting the cursor location and moving the scroll wheel.  In the Distance and Direction widget, once you start using the add circle/add ellipse/center point for rings buttons to create a geometry on the map, this functionality is disabled. It works when you are adding a line interactively. It would be nice for the scroll wheel zoom functionality to remain enabled for circles, ellipses, and rings so you could more easily zoom to the precise location of your target point and then zoom out to finish it outside of the (small) extent of the zoomed in map.

@adgiles @kgonzago

This issue should be moved over to Devtopia. Also, similar issue logged: #12673

@BobBooth Provide an example of a widget for reference that has this functionality. @kgonzago this will move to the other repo if we will address this.

@lfunkhouser - the Smart Editor widget behaves this way.
https://nationalsecurity.esri.com/portal/apps/webappviewer/index.html?id=e09c068208384f1fb8542344c7b50c1c

@BobBooth @lfunkhouser Map navigation by design is disabled during line, circle, ellipse or range ring creation. We can look into implementing it if map navigation is needed; should be an easy LOE.

This issue was moved to ArcGIS/solutions-defense-widgets#209


openconnect: new package at 8.10

Please fill out the template.
Read: https://k1sslinux.org/wiki/kiss/style-guide
Please include the manifest for version bumps and new packages.

Description of package
OpenConnect is an open-source software application for connecting to virtual private networks, which implement secure point-to-point connections.
Installed manifest of package
(kiss manifest <pkg>)
/var/db/kiss/installed/openconnect/version
/var/db/kiss/installed/openconnect/sources
/var/db/kiss/installed/openconnect/manifest
/var/db/kiss/installed/openconnect/etcsums
/var/db/kiss/installed/openconnect/depends
/var/db/kiss/installed/openconnect/checksums
/var/db/kiss/installed/openconnect/build
/var/db/kiss/installed/openconnect/
/var/db/kiss/installed/
/var/db/kiss/
/var/db/
/var/
/usr/share/man/man8/openconnect.8
/usr/share/man/man8/
/usr/share/man/
/usr/share/bash-completion/completions/openconnect
/usr/share/bash-completion/completions/
/usr/share/bash-completion/
/usr/share/
/usr/libexec/openconnect/tncc-wrapper.py
/usr/libexec/openconnect/tncc-emulate.py
/usr/libexec/openconnect/hipreport.sh
/usr/libexec/openconnect/hipreport-android.sh
/usr/libexec/openconnect/csd-wrapper.sh
/usr/libexec/openconnect/csd-post.sh
/usr/libexec/openconnect/
/usr/libexec/
/usr/lib/pkgconfig/openconnect.pc
/usr/lib/pkgconfig/
/usr/lib/libopenconnect.so.5.6.0
/usr/lib/libopenconnect.so.5
/usr/lib/libopenconnect.so
/usr/lib/
/usr/include/openconnect.h
/usr/include/
/usr/bin/openconnect
/usr/bin/
/usr/
/etc/vpnc/vpnc-script
/etc/vpnc/
/etc/

New package

[x] Latest upstream version.
[x] I agree to maintain this package.
[x] I agree to notify the @kiss-community maintainers if I can no longer maintain this package.

Existing package

[ ] I am the maintainer of this package.

Updated depends to address comments and also removed the gnutls dependency


Error in creating new image

Expected behavior
Docker creates a new container from the image chosen.
Actual behavior
Receive error response:
(HTTP code 401) unexpected - {"message":"Get https://registry-1.docker.io/v2/library/jenkins/manifests/latest: unauthorized: incorrect username or password"}

Information about the Issue
Docker Kitematic 0.17.0
macOS Sierra  v10.12.5
Container does seem to download in background.
Steps to reproduce the behavior

Select image From hub clicking create
populates in container field
Receives code

Please make sure that you've validated your account prior to pulling an image; this can be done by doing the following:

Login to cloud.docker.com
Click on Account Settings
Check and verify that your primary email has been verified


Consider allowing the user to specify the cluster resource group

Currently we hard code the cluster resource group to the name of the cluster resource.  AKS and ARO v3 use random UUID resource groups.  Can we update our API to allow the user to specify the cluster resource group name (we will then create it).

Implemented.


click.delegate bindings intermittently execute more than once in an Aurelia application

I'm submitting a bug report

Library Version:
2.5.4

Please tell us about your environment:

Operating System:
Windows 11 (same issue on Windows 10)

Node Version:
v20.17.0

NPM Version:
10.8.2

JSPM OR Webpack AND Version
webpack 5.91.0

Browser:
Chrome v128 (although this issue has existed on versions much earlier too, definitely as far back as v108 and extremely likely earlier than that).

Language:
Typescript 5.4.5

Current behavior:
We have a front-end application built using Aurelia. We have some automated UI tests for it. Sometimes our UI tests will fail. We added much more in-depth logging and found that it was because buttons that had the click.delegate binding on it were executing the handler more than once when they were clicked. So our test was clicking the element once, but the handler was running more than once.
When we changed those handlers to use click.trigger, we could no longer reproduce it.
We have also seen this behaviour in our production application, where users who we believe to be normal users (as we looked at their analytics sessions and didn't see any bot like behaviour) were submitting forms multiple times in extremely quick succession, impossibly quick for a user.
Expected/desired behavior:
When click.delegate is used, the handler should be called only once. (Most of the time this is the case, but as I mentioned there see to be cases where it is not).

What is the expected behavior?
To only call the click handler once.

What is the motivation / use case for changing the behavior?
I suspect that this is a bug in Aurelia, as changing the binding from delegate to click seems to solve the problem.

I could not replicate this using a simple gist (1 App viewmodel, no routing) but I have a repository with tests that fail quite reliably when run multiple times.
I'm looking forward to hearing your thoughts and trying anything that you'd like me to try.
The application is 4 years old and this issue has existed for pretty much as far back as I can remember. I also remember seeing this issue whilst working on another Aurelia application as far back as 2016.

Thanks @massimocode , ill see if I can guess-locate the code without a repro.

Those I should also say that click.delegate is no longer recomended, as the pros are longer worth the cons.

Thanks for confirming @bigopon. In that case we will switch over to click.trigger instead. We don't use it heavily with hundreds/thousands of elements on a page anyway and I think that was the main driving factor for click.delegate.
It might be worth a quick update to the docs that either delegate shouldn't be used anymore or perhaps should only be used with many repeated elements or something.
I'm happy to try anything you want (i.e. add logging statements or amendments) to help look into this issue if you wish to pursue it.

Yes, we should do that. Ccing you @Vheissu for the note in our new v1 doc.


Query Tracker settings for Development

Don't pass stage from "Settings/Development/YQL agent stage" in the chyt/spyt/ql query settings.

Closed in favor of https://github.com/ytsaurus/ytsaurus-ui/issues/205