text:
Opening with touch crashing Gnome Shell

Describe the bug
Opening it with touchscreen (I mean touch event) crashing gnome-shell
To Reproduce
Steps to reproduce the behavior:

Use a touchscreen display (In Wayland)

Expected behavior
The popup open without problem
Environment:

Distro: Nobara (Fedora) 40
GNOME 46
Extension Version 2.0.1

Additional context
Im using Microsoft Surface, just in case that change anything.

I just wanted to open an issue because it's crashing for me as well. My touch event is pause and my shell crashed even without touchscreen. Same version of GNOME and extension, Fedora 40 (so maybe it's a Fedora thing) and it's also on Wayland.
So Microsoft Surface probably isn't a problem.
The only issue I've seen in Logs was:
Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
and some systemd mumbo jumbo, but I get this log a lot so it might not have to do anything with the extension. Or this extension is what causes the log, even when it doesn't crash. I just don't think it has anything to do with the crash itself.

https://discussion.fedoraproject.org/t/gdm-on-display-added-assertion-gdm-is-remote-display-display-failed/119228
seems a lot of people get this

It also looks like #151 #161 #164 are the same issue / root cause

authors: ChrisLauinger77 adam-adrian bataneske

repo: sakithb/media-controls


text:
Add transition between the input videos

Right now, when I execute
vid_transition.py -i ex_vid1.mp4  ex_vid2.mp4 --animation translation --num_frames 15 --max_brightness 1.5
I get two video output vt1_phase.mp4 & vt2_phase.mp4.
But I want a single video let's say output.mp4 that will basically merge the two input videos and will add the transition between the joint of the first and second video.

I will add an option to produce one video transition that contains the two phases, instead of two separate video chunks.

Issue fixed in this merge #11

source: gharchive/issue

repo: salaheddinek/video-editing-py-script

license_type: permissive

license_source: github-api


text:
The WS2811 LED bit timing tolerance should be wider

Existing tolerances can be found here:
https://github.com/saleae/async-rgb-led-analyzer/blob/c93bccdcade779dbe1bc52d5d4087a8a1abca36c/src/AsyncRgbLedAnalyzerSettings.cpp#L64
Taken from this datasheet:
https://cdn-shop.adafruit.com/datasheets/WS2811.pdf
Problem 1: The tolerance for the high speed operation is implemented as +/- 75ns. The datasheet is ambiguous, and I suggest increasing tolerance to +/-150ns.
Problem 2: Other datasheets for the WS2811 offer wildly different ranges:
e.g. this document (via google):
http://www.world-semi.com/DownLoadFile/129
I can't update this at the moment, and to complicate things, the tests for this analyzer haven't been migrated in yet from the original repo here:
https://github.com/saleae/AsyncRgbLedAnalyzer/tree/topics/testing
And I think updating these tolerances might break tests.

Another request for looser timing requirements here:
https://discuss.saleae.com/t/ws2812b-analyzer/2133/2

Is there a laymans way to fix this myself? Working on debugging WS2812B LEDs and it really is a shame i have to take my 10usd knock off logic analyser to use instead of my Logic 8. Spent quite a bit before realising this was an issue.

authors: Marcus10110 magicsmoke timreyes

repo: saleae/async-rgb-led-analyzer

license: MIT


text:
Fix: show dialogs by list

Added possibility to show dialogs one by one.
Used to show the No More Operators Dialog (returned to previous logic).

@AndriiHorishniiMOC Good job 👍

!squash

!merge

source: gharchive/pull-request

repo: salemove/android-sdk-widgets


text:
Effect of Dataset size on Stage-1 and Stage-2 BLIP-2 pre-training

Hi,
Thank you very much for sharing the source code and model weights for BLIP-2. I had a general question about data scale for stage-1 and stage-2 training, it would be great to get your insights on this @dxli94, @LiJunnan1992
I have tried training BLIP-2 from scratch on smaller dataset size ~5M samples due to resource constraints (with eva_clip_g as visual encoder), COCO is part of training dataset

The stage-1 performance on COCO captioning was >110 (CIDEr) and for NoCaps it was (>40 CIDEr)
However, for stage-2 pre-training using the same dataset for FlanT5XL model the performance on COCO drops to (~55 CIDEr) - initializing the checkpoint from previous step

Why do you think the CIDEr performance drops from 110 to 55 on COCO going from stage-1 to stage-2 ? Using the same hyper-parameters provided in the pre-training configs.
Also, when trained longer for 5 epochs it completely collapses and the performance drops to 1.1 CIDEr on COCO. Did you also observe similar effect with longer training for stage-2 ?
Note that the scores mentioned are directly from pre-trained models (without caption fine-tuning).
Any insights/feedback on this would be highly appreciated. Thanks!

Thanks for your questions.
It is unusual that the CIDEr performance drop by that much in stage-2. May I know if you have been using the prefix-LM loss for FlanT5-XL? Also, what does the generated captions look like?

repo: salesforce/LAVIS


text:
feat: name fields for definitionfile

What does this PR do?
create name feature in definition-file for apex and group option fields
What issues does this PR fix or reference?
https://github.com/forcedotcom/cli/issues/3008#issuecomment-2342416748
@W-16757770@

QA notes:
setup:
checked out this PR, yarn compile then linked it with sf plugins link
org create sandbox
✅ throws when specifying both ApexClassId and ApexClassName
✅ throws when specifying both ActivationUserGroupIdand ActivationUserGroupName
⚠ NIT: the validation happens after the sandbox name is generated so we always get this warning, let's do the validation early 👍🏼

✅ throws if can't find ID of ApexClassName
⚠ NIT:

✅ throws if can't find ID of ActivationUserGroupName

✅ resolves ApexClassName to class ID
def.file
{
  "description": "testing testing",
  "ApexClassName": "PropertyController"
}

...
=== Config Sandbox Request

 Field       Value
 ─────────── ──────────────────
 Description testing testing
 SandboxName sbx1hxq4ir
 LicenseType Developer
 ApexClassId 01p4p00000AryNlAAJ

✅ resolves ActivationUserGroupName to user group ID
✅ ApexClassName works without ActivationUserGroupName
✅ ActivationUserGroupName works without ApexClassName
org refresh sandbox
❌ throws when specifying both ApexClassId and ApexClassName
❌ throws when specifying both ActivationUserGroupIdand ActivationUserGroupName
❌ throws if can't find ID of ApexClassName
❌ throws if can't find ID of ActivationUserGroupName
❌ resolves ApexClassName to class ID
❌ resolves ActivationUserGroupName to user group ID
❌ ApexClassName works without ActivationUserGroupName
❌ ActivationUserGroupName works without ApexClassName

QA update

⚠ NIT: the validation happens after the sandbox name is generated so we always get this warning, let's do the validation early 👍🏼

✅ fixed

org refresh sandbox
✅  throws when specifying both ApexClassId and ApexClassName
✅  throws when specifying both ActivationUserGroupIdand ActivationUserGroupName
✅  throws if can't find ID of ApexClassName
✅  throws if can't find ID of ActivationUserGroupName
✅  resolves ApexClassName to class ID (no apex class -> class assigned, old class -> new class)
✅  resolves ActivationUserGroupName to user group ID (no group -> group assigned, old group -> new group)
✅  ApexClassName works without ActivationUserGroupName
✅  ActivationUserGroupName works without ApexClassName
✅ props can start with/without capital letter, we handle casing when reading the def. file

repo: salesforcecli/plugin-org


text:
DIGGs krav på andra organisationers data

Skall vi komma bort från dagens datasilos och extremt dåliga dokumenthantering behövs tydlighet vilka krav som finns jmf #99
Alla organisationer måste uppvisas samma tydlighet och ett ekosystem måste finnas

Riksdagens öppna data
Riksarkivet
RAÄ och muserna
.....

Bra exempel hur Humlab Riksdagens Corpus "ställer krav" på Wikidata att ha parti se #324

Intressanta siffror från DS 1998:10 vad kostar dagens tomteverkstad
Kostnaden av dålig data för Rättsinformation enl. DS 1998:10
12 Kostnader och vinster sid 153 - år 1998 bara för Rättsinformation..

Kollade lite snabbt igår och fler och fler kommuner tar bort sina Öppna data sidor det är nog dax att inse att detta bara blev trams med dålig data och tomma löften och lite fakturerings glada konsulter - tweet. DIGG har nu förbrukat 1 miljard i budgeterade pengar så den aktiviteten känns helt bortkastad....

Kollade lite snabbt igår och fler och fler kommuner tar bort sina Öppna data sidor det är nog dax att inse att detta bara blev trams med dålig data och tomma löften och lite fakturerings glada konsulter - tweet. DIGG har nu förbrukat 1 miljard i budgeterade pengar så den aktiviteten känns helt bortkastad....
Vad som hittas manuellt

2023-11-15 112 kommuner /psidata
2022-08 130 kommuner

saknar pondus?
En granskningsrapport från Riksrevisionen - Digitala tjänster till privatpersoner – stora utvecklingsmöjligheter för statliga myndigheter RiR 2023:6

Exempel där DIGG har förväntningar på EDP Europeiska dataportalen men deras förväntninbgar och vad dom driver inte går att följa i en publik prioriterad backlog
Projektyta DIGG har github.com/diggsweden/DCAT-AP-SE/issues?q=is%3Aissue+
Problemet jag ser här är att DIGG inte driver backloggar med krav på EDP att hantera Persistenta Identifierare och att DIGG borde ha unika persistenta identifierare för issues i sin backlog som Europeiska Dataportalen kan referera till.... #72 Tydlighet med hur datasetet refereras och version, datum publicerat etc.,.. där säger den externa konsulten att detta drivs mot EDP men inte på det sätt DIGG önskar, hur kan jag prenumerera på detta vad som sker osv... var är co-creation

se även #776 Utveckla en modell för co-creation av digitala leveranser mellan myndigheter / kommuner / Riksdagen


text:
How to prevent click outside of Multi select bottom sheet ?

Using
PopupPropsMultiSelection.bottomSheet
But it allows click outside of the bottom sheet, allowing background items to be clicked. Is there any way to prevent or blur out the background items
Im using this exampld https://github.com/salim-lachdhaf/dropdown_search/blob/fa960038cf08df53da4513b4f96c1eb4b9a971cf/example/lib/bottom_sheets.dart#L112

it's a normal behavior of a bottomSheet and it's not related to package.
in your case use PopupPropsMultiSelection.modalBottomSheet which block access to background items.
Please don't hesitate to like the repo and the lib if it's useful for you.

authors: PKReejesh salim-lachdhaf


text:
Menu for history back-forward navigation

Something like in Chrome? (Note: Cmd + left/right already works.)

+1

For what it's worth, I just discovered that Command+left/right arrow take you back and forward.

:+1:

Added in 0.18

authors: salomvary sammarcus smeador

repo: salomvary/soundcleod

license: mit

license_source: bigquery


text:
🛑 Blog is down

In f9f488d, Blog (https://saltbo.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in 76e3c84.

repo: saltbo/status


text:
🛑 Blog is down

In 4a4f265, Blog (https://saltbo.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in e882a18 after 6 minutes.


text:
增加shell输出的错误信息与信息返回

执行命令--shell  这个批量实时执行命令的功能，在数据返回展示，过于简单
在salt-master使用cmd.run命令执行，无错，但是在界面中失败后，没有返回任何异常信息。

想办法解决中。。。

authors: vekergu yueyongyue


text:
Allow Debian/Ubuntu build of packages to consume locally built dependencies

With some newer packages, e.g. zeromq 4.0.5, pygit2, there is a need to consume locally built (has yet unsigned) dependencies (e.g. libsodium-dev which does not exist in Ubuntu 14.04, libgit2-dev ver. 0.20.3, Debian/Ubuntu repositories have a later version which desire not to use due to cffi issues).
This will probably involve changes to debbuild.py module in salt too.

Got pulling in of locally built dependencies.
However, having issues with a specific version if later version exists, e.g. using locally build libgit2-dev 0.20.0 when libgit2-dev 0.21.0 exists from jessie main. Pinning appears to have issue with origin and local file system, even after apt-get --allow-unauthenticated update

repo: saltstack/salt-pack


text:
Add detection of XServer and fix paleofetch not running without X

This fixes issue #20 by adding detection for XServer and providing alternative methods to get terminal and resolution without X.

This is great work. One issue though- in the case when the value is empty, you don’t free that value (try running `TERM=“” valgrind ./paleofetch)

It might be easier to test with SHELL=“”, that way you don’t have to workshop it in the tty

authors: dwzg sam-barr

repo: sam-barr/paleofetch


text:
Add pair CLI option

Allows to pair joycons by MAC. Usually you list your synced joycons with /L
and compose n tuples of left-right joycon.

Tested pairing two combined joycons
With this only GUI is left to implement for pair visually.
NOTES:

Split source code in:

hid_utils
vigem report
main/CLI options

Review memory management
Include all report in Xbox class (maybe XboxJoycon is a better name)


text:
Can't test Boilerplate Project

Question
I always welcome any questions about this backend proejct. However, half of questions can be solved by traveling README.md or old issues. Therefore, I recommend you to visit them before. If you have a question that has not been treated and you're extremely urgently, just contact me.

E-mail: samchon.github@gmail.com
Mobile: 82-10-3627-0016

보일러플레이트에서 테스트가 되질 않습니다
core.DynamicModule.mount 메소드에서 에러가 발생하는것같아요
npm run test

npx nestia start something

Have runned above command and there was not any problem.
If you've edited some codes, can you upload the entire project?
위 명령어 실행해봤는데, 아무런 문제 없이 잘 되었습니다.
혹 프로젝트를 편집하셨다면, 프로젝트 째로 올려주실 수 있나요?

authors: luckyhyom samchon

repo: samchon/nestia


text:
UnicodeDecodeError

I have now got ggCaller to run which is great but when I use the --annotation fast option it crashes with the following error:
translating hits... Updating output... Number of refound genes:  274 collapse gene families with refound genes... Processing depth:  1 Iteration:  1 100%|???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????| 6174/6174 [00:00<00:00, 7167.82it/s] Processing depth:  2 Iteration:  1 100%|???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????| 6174/6174 [00:00<00:00, 8711.56it/s] Processing depth:  3 Iteration:  1 100%|???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????| 6174/6174 [00:00<00:00, 7851.30it/s] writing Roary output... writing GFF files... Traceback (most recent call last):   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/bin/ggcaller", line 33, in <module>     sys.exit(load_entry_point('ggCaller==1.3.3', 'console_scripts', 'ggcaller')())   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/site-packages/ggCaller-1.3.3-py3.9-linux-x86_64.egg/ggCaller/__main__.py", line 511, in main     run_panaroo(pool, array_shd_tup, high_scoring_ORFs, high_scoring_ORF_edges,   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/site-packages/ggCaller-1.3.3-py3.9-linux-x86_64.egg/panaroo_runner/__main__.py", line 241, in run_panaroo     generate_GFF(shd_arr[0], high_scoring_ORFs, input_colours, isolate_names, contig_annotation, output_dir,   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/site-packages/ggCaller-1.3.3-py3.9-linux-x86_64.egg/panaroo_runner/generate_output.py", line 323, in generate_GFF     for record in SeqIO.parse(handle, "fasta"):   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/site-packages/Bio/SeqIO/Interfaces.py", line 72, in __next__     return next(self.records)   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/site-packages/Bio/SeqIO/FastaIO.py", line 238, in iterate     for title, sequence in SimpleFastaParser(handle):   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/site-packages/Bio/SeqIO/FastaIO.py", line 50, in SimpleFastaParser     for line in handle:   File "/well/bag/users/lipworth/miniconda3/envs/ggc_env/lib/python3.9/codecs.py", line 322, in decode     (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

Hi, would you be able to send me the command you used to run ggCaller and your input.txt file if that’s possible, please?

sure - cat input.txt gives:
/well/bag/users/lipworth/gram_neg/Ecol_merger/mic_assemblies/fasta/fff281aa-dea1-4245-a28b-27523bc6e478.fasta.gz /well/bag/users/lipworth/gram_neg/Ecol_merger/mic_assemblies/fasta/fff2b139-4529-40d2-b02a-2eae3f377b1d.fasta.gz /well/bag/users/lipworth/gram_neg/Ecol_merger/mic_assemblies/fasta/fff5f6d8-f549-4502-8ac4-816632934a91.fasta.gz /well/bag/users/lipworth/gram_neg/Ecol_merger/mic_assemblies/fasta/fff721ac-bd2e-476e-8e20-11587e2280ab.fasta.gz /well/bag/users/lipworth/gram_neg/Ecol_merger/mic_assemblies/fasta/fff91cb2-e91f-4222-bf6a-88b4de1ed241.fasta.gz /well/bag/users/lipworth/gram_neg/Ecol_merger/mic_assemblies/fasta/fffcf4b2-9610-4317-809f-c6b51b6eb6df.fasta.gz
command used was:
ggcaller --refs input.txt --annotation fast --save --threads 20

It looks like the assemblies are gzipped. If you can, unzip them and try again. I’ll make a note to implement this functionality to work with gzipped files.

@samlipworth Did this fix the issue? I’ll close if all is good.

Sorry I didn't reply, got caught up with clinical work. I can confirm that unzipping everything fixed things here (agree that functionality to worked with unzipped files would be v helpful and probably pretty simple to implement?). Thanks again for your work on this interesting package!


text:
Added readme.md file

Fixes #1 Please check

Please add hacktoberfest-accepted tag

Thanks @livecodebase


text:
tab completion for options such as --attach, --quiet not working

Great extension and I love it! The README outlines that options would be tab completable but I'm not able to get it to work.
Docker commands like start, stop etc auto complets like a charm but I'm not able to get the respective options to auto complete.
e.g. When I type docker start --att, and press tab key I should see docker start --attach but it isn't.
I'm running powershell 5 on Windows 10 ,but I've also tested this on Windows Server 2016 and also no love :(

Thank you for your feedback. I just tested this locally and it seems to work here unfortunately.
What version are you on? Could you run Get-Module posh-docker and post the results?
I get this:

Facing the same issue. For docker container, not able to auto complete anything. Please help us with this

authors: frankfuu rajivkr samneirinck

repo: samneirinck/posh-docker


text:
Video Poster not showing after upgrade to 3.5.10

The poster image on the player is not getting displayed after we upgraded the player to 3.5.10. Its working fine when we downgrade to 3.5.6. On the updated version, we just see black (blank) screen and not the poster image.

Same here, some context updating from 3.5.6 bundled with wplyr wordpress addon (with some other libs also updated there).
It seems like poster div does not generate.
in 3.5.6 this is present inside plyr__video-wrapper

in 3.5.10 it is missing.

As a result of this issue I reverted back to using the HTML5 poster image as-is rather than using a custom container for it. This prevented the multiple downloads (even though it should be cached, so shouldn't be an issue really). However, it has the downside of meaning that the post only shows on initial load. If the currentTime is changed or the video has been played, the poster image will no longer show. I'm not sure if a clean solution that retains progressive enhancement and prevents the multiple downloads.

Thanks @sampotts I would suggest that we can live with download of poster twice (as you said it would be rendered from cache locally) but not displaying of poster image would be a considerable issue. Currently in our scenario, the video is not played but its meta-data is getting loaded so that the poster image is lost immediately after loading. Another fix could be to show poster image unless the video is played irrespective of its meta-data preload.

The poster does display though. You can see it on https://plyr.io. Other than using the custom element, we have no control over when the poster image shows. It's behavior controlled by the browsers; which is basically hide it as soon as currentTime is past 0 or the video has been played. It's a bit naff but that's it.

Thanks @sampotts The poster issue is bothering when we attach HLS stream to the player and from the example that you have provided at https://codepen.io/pen?template=oyLKQb, this does not show the poster. When I change the plyr version to 3.5.8 it works. Would appreciate your help on this.

authors: Hotcooler mksasi sampotts

repo: sampotts/plyr


text:
Type Error: list indices must be integers, not str

When creating a mirror for a GitHub https:// based repo, I get the following error:
/usr/lib/python2.7/dist-packages/urllib3/connectionpool.py:793: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html
  InsecureRequestWarning)
Creating new project r-plugin
Traceback (most recent call last):
  File "lib/manage_gitlab_project.py", line 105, in <module>
    found_project=createproject(project_name)
  File "lib/manage_gitlab_project.py", line 78, in createproject
    git.add_project(pname,description=description,**project_options)
  File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 185, in fn
    ret = api(parent, data)
  File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 312, in __init__
    setattr(self, '_id', json_data[self._key_name])
TypeError: list indices must be integers, not str
There was an unknown issue with manage_gitlab_project.py

Any idea on how I can fix it?  Thanks!

see #88

I'm not sure this is the same problem.  For one, the error message on the next to last line (above) is different.   My error is "TypeError: list indices",  #88 error is gitlab3.exceptions.MissingRequiredAttribute
Also, I have set in gitlab-mirrors/config.sh,    ssl-verify=false
For my gitlab server, I am using a server certificate that was signed by a local CA, The local CA is installed in /etc/ssl/certs and appears in /etc/ssl/certs/ca-certificates.crt
Would you have any other suggestions?

Sorry for wasting your time.    The problem was in my git-mirror configuration.   When I changed the gitlab server over from http:// to https://, I failed to change the url in the git-mirrors/config.yml.
Again, very sorry.  Love your product.  Thanks for sharing.

Glad you figured it out.

authors: logicminds meldavis samrocketman

repo: samrocketman/gitlab-mirrors


text:
Temporarily remove search from keywords list page

Are there any other places we have search bars that aren't functional?

Closed by https://github.com/samtecspg/articulate/commit/3f04ac61db529667cd8d81b9b422d1ed7c7f9991

authors: dcalvom wrathagom

repo: samtecspg/articulate


text:
Backend: Improve story proxy ("Imperfect proxy due to http over https")

Feed/XML URL: https://steamcommunity.com/games/943140/rss/
Website URL: https://steamcommunity.com/games/943140
Both are HTTPS, but when I try to view any stories in the feed using the Story view I get the error "Imperfect proxy due to http over https".
Funnily enough, some elements of the site will actually load, but nothing relating to the actual story.
I get this error on all the Steam rss feeds I've tested.

This is no longer a concern as the site is now https-only.

authors: Splike samuelclay

repo: samuelclay/NewsBlur


text:
Compatibility with old browsers + code formatting

There are two important housekeeping activities one should do -- the sooner the better.
The first being compatibility -- the current JavaScript source code benefits from post ES5 syntax such as arrow function expression ( => ), async-await, Promises, spread operator (...), let/const et cetera.  These won't work in the older browsers.  I strongly suggest the modern JavaScript should be transpiled to ES5 (or ES3) syntax so people using older browsers can use it too.  TypeScript compiler or babel -- either can be used to automate this.
Code formatting -- at various places semi-colon was used, at times it was not.  It would be useful to stick to a standard.  Same with double/single quotes and other such things.
What do you think, @samuelguebo?

Those are valid concerns. For the double/single quotes. Using single quotes and semi-colon makes sense. I think settings some stricter rules in my linter could have helped with that a bit.
As for the backward compatibility, I have to admit that I was a bit reluctant to bringing the whole npm army and its packages for transpiling and so on. However, as the tool is gaining for attention, I think it is fair to consider those options and I am leveraging babel — not super familiar with TypeScript but giving it a try won't kill for sure.

When I met TypeScript, I immediately fell in love with it—it’s the same well-known JavaScript, but with static typing added. This is good for safety and scalability (static typing points out when you do something wrong, without any thorough testing), and also for tooling: VS Code’s IntelliSense is much more helpful when it knows the types of the variables. If you don’t want to work through the whole code base now, you can simply say that all your JS code is TS—it is, TS is a superset of JS. This way you can gradually shift to TS, and you can enjoy its improvements from the first moment.

It's hard to say no to such as nicely crafted pitch about TS 😄  I'm in!

@samuelguebo I had implemented formatting and transpiling on my fork here https://github.com/acagastya/consultation-stats/commit/a4d81311d097f891b4967fed29ab553117522128 -- prettier and typescript both get the work done nicely.  I will add the PRs that were added to this repo last night, then submit a PR, if that is okay.

Also, @samuelguebo, the formatting should be standard across different contributors.  This commit https://github.com/samuelguebo/consultation-stats/commit/0f34a44a917e2ebfac53ede0155be77a3cb26e32 will not work as we expect if contributors have prettier installed, or have custom prettier configuration., or if they do not have ESLint, or in my case: they use vim.  I would say leave .vscode in .gitignore file, and add a .prettierrc configuration like this https://github.com/acagastya/consultation-stats/blob/a4d81311d097f891b4967fed29ab553117522128/.prettierrc

Also, @samuelguebo, the formatting should be standard across different contributors. This commit 0f34a44 will not work as we expect if contributors have prettier installed, or have custom prettier configuration., or if they do not have ESLint, or in my case: they use vim. I would say leave .vscode in .gitignore file, and add a .prettierrc configuration like this https://github.com/acagastya/consultation-stats/blob/a4d81311d097f891b4967fed29ab553117522128/.prettierrc

I see what you mean. I'll stick to this newly crafted version.

authors: acagastya samuelguebo tacsipacsi

repo: samuelguebo/consultation-stats


text:
upload the new version to PyPi 0.6.2

Hi there,
I see that the code in the git is newer 0.6.2 than the code in PyPi 0.6.1 and i need it to support Django 1.7
could you please upload the new version to PyPi?
I usually don't like using packages from the git repositories.
Thanks :)
Koby

Done!

Thanks :)

authors: kobymeir samuraisam

repo: samuraisam/django-json-rpc


text:
My issue creating

Blablabla test

issue closed

repo: samyKhezandji/github-slideshow


text:
Add S.range function

Create a typesafe version of R.range.

#218

authors: davidchambers svozza

repo: sanctuary-js/sanctuary


text:
🛑 Healthcare on Stage CRM is down

In 9f66f5e, Healthcare on Stage CRM (https://crm.healthcareonstage.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Healthcare on Stage CRM is back up in 6102e5d.

repo: sanderdatema/upptime


text:
chore(main): release audit 1.40.0

:robot: I have created a release beep boop
1.40.0 (2023-05-10)
Features

better vulnerability report retrieval errors (2ce3e10)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-audit/releases/tag/audit-v1.40.0 :sunflower:

repo: sandworm-hq/sandworm-audit


text:
Update sbt to 1.9.4

About this PR
📦 Updates org.scala-sbt:sbt from 1.9.3 to 1.9.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #189.

repo: sangria-graphql/sangria-marshalling-api


text:
Return tuples

Fix #10, always return a tuple from SanicTestClient request, and ASGITestClient request()

Note, this has now introduced a new MyPy error:
sanic_testing/testing.py:293: error: Signature of "request" incompatible with supertype "AsyncClient"

Note, this has now introduced a new MyPy error:
sanic_testing/testing.py:293: error: Signature of "request" incompatible with supertype "AsyncClient"

Fixes #11 by casting the HTTPX response to a Sanic response. The use case for this original behavior no longer exists.

Fixes #11 by casting the HTTPX response to a Sanic response. The use case for this original behavior no longer exists.

authors: ahopkins ashleysommer

repo: sanic-org/sanic-testing


text:
Dark images with transparency renders low contrast

We use several image assets with dark or black graphics with transparency, in the media manager these assets become almost illegible due to low contrast. Especially when containing text this becomes an issue, an example is a client logo which contains the company name and is impossible to read. Here's a slightly more legible example which demonstrates the issue (I can't share client logos unfortunately):

A couple of suggested solutions
a) In the above instance a solid background-color (e.g. --card-muted-fg-color would look good as it is used for the asset title) would render a better contrast. However, it would fail with images that contain a similar color to --card-muted-fg-color).
b) Another option would be to adapt the checkerboard to use two grays instead of the background color which is so close to black. Again this might fail with gray foregrounds.
c) An option for a light mode? (Maybe this is an option already but I can't find it). A light mode would work better with these assets, however you could foresee someone running into the same type of issue with transparent assets with white foregrounds.

I think a dark / light mode toggle is something that should probably be added regardless of this issue, and is something that's been requested in the past!
Perhaps the answer lies in analysing color palette information that Sanity provides for each image in metadata.palette, e.g.
{
  "_type": "sanity.imagePalette",
  "darkMuted": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#474d36",
    "foreground": "#fff",
    "population": 3.13,
    "title": "#fff"
  },
  "darkVibrant": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#201f0b",
    "foreground": "#fff",
    "population": 0.87,
    "title": "#fff"
  },
  "dominant": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#d7cfb9",
    "foreground": "#000",
    "population": 4.25,
    "title": "#000"
  },
  "lightMuted": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#d7cfb9",
    "foreground": "#000",
    "population": 4.25,
    "title": "#000"
  },
  "lightVibrant": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#e5d49f",
    "foreground": "#000",
    "population": 0.21,
    "title": "#000"
  },
  "muted": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#4c8490",
    "foreground": "#fff",
    "population": 0.01,
    "title": "#fff"
  },
  "vibrant": {
    "_type": "sanity.imagePaletteSwatch",
    "background": "#bdb741",
    "foreground": "#000",
    "population": 0,
    "title": "#fff"
  }
}

It's not something I've looked into extensively, but there might be enough information in the above to quickly determine the overall luminance / brightness of an image, after which we dynamically adjust that checkboard pattern to adjust.
It won't be perfect and I'm not yet sure how it'd work with complex, multi-colour SVGs – but might be a step-up from what we have now

Just to chime in and say that I haven't forgotten this! I did have a play with metadata.palette a while back, but predictably you get really wonky results on assets with any form of transparency. The solve will most likely involve adding an additional toggle on assets with transparency that toggle between white / black + checkboard backgrounds

I'm having this exact problem with black illustrations on a transparent background. Having a light theme would solve the problem, especially as the rest of the dashboard is light. Any way of doing this?

Such a lovely plugin ❤
Also wondering if we can get a light/dark mode to match your studio V3 settings:

As of 2.2.2 this plugin should now use colours appropriate to the colour mode in use by the studio.
This also affects checkerboard backgrounds on transparent images, e.g:

authors: hessius ndimatteo robinpyon shealan

repo: sanity-io/sanity-plugin-media


text:
🛑 Authelia is down

In abc0007, Authelia ($AUTH_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Authelia is back up in 75f1569 after 8 minutes.

repo: sannidhyaroy/Uptime-Ryuu


text:
Integrate create group

with this merge when you create a group on the groups page it will save it to the database
also included:

get groups from db on groups page
when navigate to group details page, get info from db

Current coverage is 84.51% (diff: 72.22%)

Merging #43 into master will decrease coverage by 0.58%

@@             master        #43   diff @@
==========================================
  Files            20         18     -2
  Lines           208        226    +18
  Methods           0          0
  Messages          0          0
  Branches          7          7
==========================================
+ Hits            177        191    +14
- Misses           29         32     +3
- Partials          2          3     +1

Powered by Codecov. Last update 6da27d9...215113f

authors: codecov-io ironmanwaring

repo: santaswap/ui


text:
ESC button

Is it possible to make all SessionTime addon windows to be closed by pressing ESC button from keyboard?
At this moment esc button can close everything in my interface but SessionTime.

Done! Thanks for your suggestion.

Get CSV window does not close with esc :D

Ups 😓
It is done now! About the second point, I don't think it should close after pressing ctrl+a and ctrl+c, because the user might want to do further exploration on that window even if the content has already been copied. ESC should be enough I guess!
Thanks again!

authors: DeiranFox santipaprika

repo: santipaprika/SessionTime


text:
configure absolute imports

Fixes #111

Awesome work @norflin321
thank you!

repo: santiq/bulletproof-nodejs


text:
🛑 KIALI_URL is down

In 51a4121, KIALI_URL ($KIALI_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KIALI_URL is back up in 2810ce9 after 1 hour, 30 minutes.

repo: santomaharaj/upp


text:
Pretty print

Pretty print everything in keyword upper / identifier lower in one dedicated commit in order to avoid large diff problem
Closes #780 if agreement to use this as a project standard.
Even if a different standard will be used in future, at least everything is in one format now.

@AndreaBorgia-Abo what would you like to do? if you review this one, it can be merged, but will probably cause conflicts in all open PRs

@larshp I guess it can't be helped and I'm fine with a little extra work as long as this is once and for all.
Perhaps we should first write the preferred settings in the coding guidelines (hello @sandraros ) and commit that PR, so that when we pull this one in we are able to reference the guidelines in all conflicting PRs and ask contributors for a little extra editing. All onboard with this?

and much of the pretty-printing can be enforced by the linter

Agree with @AndreaBorgia-Abo
On a couple of random checks several open PRs already have conflicts.

Agreed with all @AndreaBorgia-Abo @pokrakam @larshp : to add it to the coding guidelines first ; then update the linter settings ; and ask people to resolve PR conflicts or do it ourselves (like mines or #669 that I am currently reviewing)

Very well, I'll have a look this evening

authors: AndreaBorgia-Abo larshp pokrakam sandraros


text:
Get feedback from ARC

Regarding draft Strategy of Sharing of software assessments.

No plans to take this to ARC (likely alternate path is to OCMC for info as they are the body that reviews the software assessment artefacts).

authors: RachelMuston gabrielcossette

repo: sara-sabr/ITStrategy


text:
Varying Errors Imaging old Macintosh disc

Version
AppVersion - 32 bit, AnsiBuild, 20230606T110637
Describe the bug
I am trying to image an old Macintosh disc (Operation: Weather Disaster). I get two different types of errors depending on the two drives I have.
I am using this call:
C:\Utilities\DiscImageCreator\DiscImageCreator.exe cd F "E:\Game Installers\Operation Weather Disaster\Operation Weather Disaster.iso" 16
The errors are as follows:
PIONEER BD-RW BDR-209D 1.34-ID61 (F:) (SATA) Platform RS8600
This drive (BD-RW   BDR-209D 1.34  16/04/25  PIONEER  ) can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 1]
Failed to get write-offset
This drive (BD-RW   BDR-209D 1.34  16/04/25  PIONEER  ) can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 2]
LBA[000000, 0000000]: [F:ExecSearchingOffset][L:196]
Opcode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, 00, 00, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
This drive (BD-RW   BDR-209D 1.34  16/04/25  PIONEER  ) can't read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 4]
HL-DT-ST BD-RE WH16NS60 1.02 (D:) (SATA) Platform MT1959 - Patched
LBA[302310, 0x49ce6]: [F:ReadCDForCheckingReadInOut][L:859]
Opcode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, 00, 04, 9c, e6, 00, 00, 01, f8, 00, 00
dwBufSize: 2352
This drive can't read the lead-out
ImgBurn info
TOC Information:
Session 1... (LBA: 0 / 00:02:00)
-> Track 01  (Mode 1, LBA: 0 / 00:02:00)
-> LeadOut  (LBA: 302310 / 67:12:60)
Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 302310, LRA: 0)
ImgBurn can almost read it but errors on two sectors (302159 and 302160 of 302310 total sectors) on both drives. The resulting .ISO is not mountable via Windows but 7zip can open it and it gives an error "MacOS.hfs - Cannot open the file as [HFS] archive" then I guess manages to open it and shows a MacOS.hfs file and a PartitionMap.Apple_partition_map file. I have a feeling that the disc is OK - it looks good, but maybe the format being just a HFS file system dump is tripping it up?
Disc title
Operation: Weather Disaster Macintosh CD-ROM published 1996
Disc ringcode
H311113-1
JVC 466-011
Log file
https://files.catbox.moe/xys1mt.7z <- 7zip file with outputs from both drives

BD-RW BDR-209D 1.34 16/04/25 PIONEER

This drive can't support when CD is dumped.

HL-DT-ST BD-RE WH16NS60 1.02

DiscImageCreator_test.zip
Added it as 0xF1 drive. Try to dump plz.

According to this site (http://wiki.redump.org/index.php?title=DiscImageCreator:_Optical_Disc_Drive_Compatibility#Recommended_Non-Plextor_ODDs), WH16NS60 1.00 is supported. But Unfortunately, it seems 1.02 is not supported.

the drive is actually a WH16NS40 that was flashed to be a WH16NS60

If you re-flash to a WH16NS40, the drive may be able to read the lead-out.

Is there a work-around to tell the program where the "lead-out" is (sorry, I do not know what the "lead-out" actually is on a disc)?

Not all drives can read the lead-out.
If you are interested in the specification of the CD-ROM, you can see ecma-130.
https://www.ecma-international.org/publications-and-standards/standards/ecma-130/

I'll let you know if it finishes, it will take an extremely long time

It's weird. If you have other disc, try to dump it.

how can other programs get by the drive not actually being able to read the lead-out?

ImgBurn doesn't read the lead-out, but your disc is a single data track. In most cases, a single data track disc generates the same binary without reading the lead-out. For more information, you can see Drives and Features of this document. (https://dbpoweramp.com/spoons-audio-guide-cd-ripping.htm) Keywords are "offset" and "Over-reading".

It got close, but it did not finish successfully.

Would you upload all logs?

Try to use /c2 like
DiscImageCreator.exe cd D "E:\dump\Operation Weather Disaster.iso" 16 /mr 50 /c2

authors: genekellyjr saramibreak

repo: saramibreak/DiscImageCreator


text:
[Future] Investigate replacing pip internals

I feel like Distlib has a lot of pieces available to do most of what pip does. It might be a good idea to release a version with pip internals all replaced by Distlib, and work our way back to feature parity with pip. This would be better than the other way around because we can rely on user reports to know what is missing, instead of receiving complaints about things “no longer” works.

I'm curious about which things you have in mind here

The short answer is all of them :p Realistically though, I’m probably going to fiat look into replacing the finder; it is likely the most difficult part to reach feature parity (dependency links, find links, etc.), and the most magical part (we just use the finder directly). I’m very intrigued what can be extracted out of it, and maybe contribute to distlib or another library.

Dependency links go away next release of pip, I confirmed that.
The rest of it isn't actually that complicated, it's just parsing logic which is a pain in the ass.  We might as well just do it in here though.  You've already queried the simple api, and we query the json api as is.  There isn't much reason to rely on pip for this at this point (I was hesitant to break away at first but feel more comfortable about it now)

authors: techalchemy uranusjr

repo: sarugaku/passa

license: ISC


text:
Auth parameters for binaries download in install.js

In some cases, when SASS_BINARY_SITE is used, site may have authentication/authorization,
For such cases I've added 2 params, to be able to pass username and password to request module (which is used for download) - https://www.npmjs.com/package/request#http-authentication

Does the http scheme approach not work with SASS_BINARY_SITE?
SASS_BINARY_SITE=https://user:pass@mysite.com

Just checked.
SASS_BINARY_SITE=https://user:pass@mysite.com

Works fine for both cases. when I provide clear text password and encrypted password (my specific case).
Thanks for pointing it out!

The install script should not display the url with login/password.

authors: Michenux shiaart xzyfer

repo: sass/node-sass


text:
Navbar: Sometimes 'Title Case' and sometimes 'Regular case'

FYI, some submenus use 'Title Case' and others 'Regular case', e.g. 'Call for Submissions', 'Key dates', and 'Organizing committee'.

Fixed in https://github.com/satRdays/quarto-satrdays-template/commit/66f1ba46a611700e6e8bcf34d788b24ce2c969cb

authors: HenrikBengtsson benubah

repo: satRdays/quarto-satrdays-template


text:
feat: sticky index

Summary by CodeRabbit
Release Notes

New Features

Introduced a new module for managing a StickyIndex, allowing efficient insertion and deletion of elements.
Added functions to create and retrieve offsets for the StickyIndex.

Bug Fixes

Enhanced error handling for sticky index operations.

Tests

Added a test module to verify the functionality of the StickyIndex with text documents.

coverage: 95.868% (+0.04%) from 95.833%
when pulling 01078ab3d24be191aba04b7581e16734450ae409 on sticky_index
into 835136baa57961429d73c9ca46c871cb43ffdc19 on main.

authors: coveralls satoren


text:
right click with Quark chests

hi. thanks for your awesome mod :)
i got this small issue: i tried to use one of quarks wooden chests to add an inventory to my wolf, but it didn't work. it was only doable with a vanilla chest. i've seen that there was a report about this that's closed now, but it still don't seem to work for me.
cheers

I tested this w/ Quark against the latest build of the mod; it looks like this is indeed an issue.  Thanks for the heads up! I'll add this to the v3 release project.

authors: Rotzo satyrnidae

repo: satyrnidae/wolfarmor


text:
Update espresso-xcuitest.md

Typo fix on line 71

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Not sure why the CI tests are failing due to no credentials, but I am just going to close this and fix it in another PR.

authors: mattpyle sweeneyskirt-sl

repo: saucelabs/sauce-docs


text:
IPSec VPN edits

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@lysannep thank you for the suggestions and quick turnaround!


text:
we should have the possibility to define the sauce labs data center

🚀 Feature Proposal
there should be a possibility to define the sauce labs data center to upload test results to the eu data center

This is now available with https://github.com/saucelabs/saucectl/releases/tag/v0.8.0 :)

Hi @alexplischke ,
that doesn't work for me :(
i tried it with multiple docker images:

the initial one: saucelabs/sauce-puppeteer:3.0.4 -> still uploads to us dc, even when set to eu dc
the one from the documentation: saucelabs/sauce-puppeteer-jest-node:v0.1.0 -> error 5:13AM ERR failed to execute run command error="Error response from daemon: pull access denied for saucelabs/sauce-puppeteer-jest-node, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"
the other one from the documentation: saucelabs/stt-puppeteer-jest-node:v0.1.0 -> still uploads to us dc, even when set to eu dc

ah - just saw that there's an update on the last one:
image:
  base: saucelabs/stt-puppeteer-jest-node
  version: v0.1.1

it works with this configuration 🎉

Sorry, I should have mentioned that this requires a new image as well 🙇 Thank you for your perseverance 👍

repo: saucelabs/testrunner-toolkit


text:
update link to nem-cli repository

Previous name nem-utils abandoned to provide with a command line tools suite instead. (first version including a NIS API wrapper)

I have updated this change via the docs cms. So I will close this pull request.

authors: evias saulgray

repo: saulgray/nemioDev


text:
Wallhaven out of alpha - updated what I thought it needed but still not working.

No matter what I update in response to how the site pages are now named after coming out of alpha I seem to get the same response.
Login successful.
Fetching collection ids...
Traceback (most recent call last):
File "wl_fav_dl_spec.py", line 149, in
main()
File "wl_fav_dl_spec.py", line 141, in main
for collection in collection_ids:
File "wl_fav_dl_spec.py", line 59, in fetch_collections
collections = favs_soup.find('ul', class_='blocklist collections-list').find_all('li')
AttributeError: 'NoneType' object has no attribute 'find_all'
Is there a way to increase buffer size as well?

I have updated the project to work with Wallhaven now its out of Alpha.
I only did some minor testing, let me know if you have any Issues.
Please find my fork here: https://github.com/Tempest042/Wallhaven-dl

Please refer to my pull request here:
https://github.com/saurabhan/Wallhaven-dl/pull/16/commits/9c4fdf121d1bbed8053be53ddf3cf100f0cda37e
The changes I make in the commit will make it use the new API.
You will need to replace the "YourAPIKeyHere" with your own API key which you can get by creating a Wallhaven Account.
It also has the added benefit of getting the full Image Path from the API, so the script no longer has to guess the file extension.
Please let me know if there are any Issues, I only tested it breifly,

Thank You - works great - I've only been doing my favorites but figured out if I do the search by the id# it pulls as expected.  You are wonderful!

repo: saurabhan/Wallhaven-dl


text:
[MRG] Improve embedding net tutorial

What does this implement/fix? Explain your changes
This improves the text and presentation for the tutorial on embedding networks for SBI
Does this close any currently open issues?
Fixes #903
Any relevant code examples, logs, error output, etc?
No
Any other comments?
I experimented with some formatting and admonitions from mkdocs-material and would like to know your thoughts on that. I could extend this formatting style to other tutorials and examples if you think it is good.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.

[x] I have read and understood the contribution
guidelines
[x] I agree with re-licensing my contribution from AGPLv3 to Apache-2.0.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have reported how long the new tests run and potentially marked them
with pytest.mark.slow.
[x] New and existing unit tests pass locally with my changes
[x] I performed linting and formatting as described in the contribution
guidelines
[x] I rebased on main (or there are no conflicts with main)

thanks for adding this @plcrodrigues
Similar to the other PR, there seems to be a problem with the commits here. There is a number of commits from main showing up in this PR, possibly because they appear in between your commits. I believe a fix could be to run rebase -i main and re-order your commits on top of those from main.
Thanks 🙏

Oh, I see. Yes, the syntax and notes look great on the website. I would say that there is a trade off to make: given that many users will probably also execute notebooks locally, I would opt for showing the syntax in the beginning without mkdocs macro, but using plain markdown syntax highlighting.
Because the !!! tips is less invasive in the notebooks, I think we can keep it.

OK, I've removed the mkdocs macro for main syntax (it was a !!! tip) but kept the macro for notes, which is less intrusive. Once this PR is merged I will try to find a way of formatting both the notebooks+websites without the ugly intrusive macros above.

Cool, thanks for helping out! :) how can I be sure of having a linter that is consistent with what ruff will be checking? I'm using flake8 on my side, but seems not enough then? sorry for the dumb question

Not a dumb question at all. The problem could be that your are using flake8 automatically within your IDE, e.g., "on save".
Ideally, you would deactivate that when working in the sbi repo.
ruff includes flake8 rules.
Our pre-commit hooks will run the ruff linter and fail if something is off, e.g., line lengths. Then you need to fix that by running ruff format . --fix or by hand. E.g, for fixing line lengths I an extension in VSCode called rewrap, setting the line length to 88.
In this case things got chaotic because our ruff checks where broken so that too long lines where accidentally merged into main last week.

authors: janfb plcrodrigues

repo: sbi-dev/sbi


text:
Performance Issue - VS Refactor.Rename

Thanks for the great extension.
Using the extension in VS 2019 and trying to rename a variable using Visual Studio's rename functionality(Refactor.Rename) while the CodeNav window is open brings VS to a halt. Typing of the characters take too long (upto 5 seconds per character) when it should have been instantaneous.
Closing the CodeNav window speeds up the performance. Closing CodeNav and restarting VS brings the performance to full speed until I open the CodeNav window again.

Thanks for reporting!
Just had the slowdown happen to me as well 😞
Will need further investigation on what is causing the performance drop and how to fix it...

authors: sboulema vinaychandra

repo: sboulema/CodeNav


text:
taxa_abundance_bar_plot issue

안녕하세요 @sbslee
dokdo API들 중, taxa_abundance_bar_plot 관련 문의 드립니다.
다양한 parameter들 중에서 sample 이름으로만 제거하거나 혹은 keep할 수 있는 option이 없는데
혹시 추가 가능하실까요?
각종 연구로 많이 바쁘실텐데 항상 도움 주셔서 감사합니다.

There's already an option in the taxa_abundance_bar_plot method called sample_names that you can use to select which samples to display. Closing this.

authors: JetbluejetYJ sbslee

repo: sbslee/dokdo


text:
Data analysis

I'm sharing with you my data analysis R Markdowns, excel sheets, and other relevant documents. In the "Burden Phenotype" folder, there are filtering excel sheets for identifying the number of gene-phenotype patterns that result in “abnormal, priority, and high risk” responses according to CPIC. Both the "Haplotype Frequencies" and the "Phenotype Frequencies" have files from PharmGKB that are reformatted so that I can compare the frequencies across ancestral groups. The "SNVs and indels" folder is related to the CADD and Ensembl Variant Effect Predictor.

Hi @shermcar,
I think you meant to create this PR at this repository :)

authors: sbslee shermcar

repo: sbslee/pypgx


text:
cardImageFront not working for iOS 14

cardImageBack and cardImageFront is not working for iOS 14

not solution for this?

Have you tried updating react-native to 0.63? There is a known image display issue with RN 0.62 and iOS 14 (0.60 and 0.61 also?). Images don't show up for me using iOS 14 and RN 0.62.2, so I upgraded to 0.63.x and they work. If this uses images, it could be the problem. I haven't tried it with this library yet though.

authors: Goldyukol calliday thiagocsfoz

repo: sbycrosz/react-native-credit-card-input


text:
Error when attempting to signin with github

After clicking "Login With Github" I am immediately returned to the site with the falling error and callback url:
https://www.scala-exercises.org/_oauth-callback?error=redirect_uri_mismatch&error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.&error_uri=https%3A%2F%2Fdeveloper.github.com%2Fv3%2Foauth%2F%23redirect-uri-mismatch&state=126dc86a-6244-4106-9fdf-491a9327b791

Should be related to the redirection from the top-level domain to the "www" subdomain, looking into it.

@dialelo @justinelsberry I think I know why this issue has happened, because it have got the same message few minutes ago.
I wanted to answer a comment that has been added in this URL:
https://scala-exercises.herokuapp.com/std_lib/asserts#comment-2744423915

This is the URL of the Heroku app. So if you try to authenticate from there, GitHub oAuth will return you back to the callback-URL https://www.scala-exercises.org/_oauth-callback. Given that those redirect-urls don't match, this error message is returned (as querystring):
The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application

In summary: We should automatically redirect from https://scala-exercises.herokuapp.com to https://www.scala-exercises.org, and the issue will be fixed.

In short: Authentication in https://scala-exercises.herokuapp.com is not enabled.

In fact, the actual issue is related to the subdomain www as @dialelo has mentioned.

Two possible solutions:

Always redirect from https://scala-exercises.org to https://www.scala-exercises.org.
Generate and send a valid redirect_url to Github agnostic to the subdomain.

Fixed in #456

authors: dialelo justinelsberry rafaparadela raulraja

repo: scala-exercises/scala-exercises


text:
Update scala-library, scala-reflect to 2.13.4

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

from 2.12.12 to 2.13.4.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-minor

Superseded by #138.

repo: scala-tsi/scala-tsi


text:
Make up git hooks for unstashed secrets

To prevent secrets from being committed.
Then remove them upon stashing.

Done in v1.1.

repo: scale-tone/kee-shepherd


text:
SELinux disabled in 4.1.6-apparmor #247 kernel

Yann from Scaleway suggested I file an issue here.
The 4.1.6-apparmor #247 kernel/Bootscript does not support SELinux. This is a regression from the behavior of #246 which has full SELinux support.
Booting from 4.1.6-apparmor #247:
[root@selinux-test ~]# uname -a && sestatus
Linux selinux-test 4.1.6-247 #1 SMP Wed Aug 26 18:05:41 UTC 2015 armv7l armv7l armv7l GNU/Linux
SELinux status: disabled
[root@selinux-test ~]# cat /proc/config.gz | gzip -d - | grep -i selinux
CONFIG_SECURITY_SELINUX is not set
Booting from 4.1.6-apparmor #246:
[root@scale ~]# uname -a && sestatus
Linux scale 4.1.6-246 #1 SMP Wed Aug 26 17:53:55 UTC 2015 armv7l armv7l armv7l GNU/Linux
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 29
[root@scale ~]# cat /proc/config.gz | gzip -d - | grep -i selinux
CONFIG_SECURITY_SELINUX=y

#247 is our std kernel: https://github.com/scaleway/kernel-tools/tree/master/4.1.6-std
#246 is our fedora kernel: https://github.com/scaleway/kernel-tools/tree/master/4.1.6-fedora

Even if the build numbers are following, they don't share the same kernel flavor
If you want to have selinux, you need to stay on the fedora flavor

Great - thanks!

authors: moul ruoho

repo: scaleway/kernel-tools


text:
ROCANA-7092: sigar detects Ubuntu

This parses /etc/lsb-release to get the distribution description.

+1 LGTM

authors: adamlamar alanctgardner

repo: scalingdata/gosigar


text:
Fix import from nodejs modules

For some reason being imported from a pure-nodejs module was not calling the build step (it did before), so going belt and suspenders to make sure nothing fails to compile silently.

Hello rachedbenmustapha,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Incorrect fix version
The Fix Version/s in issue BREAK-5 contains:

None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

1.0.0

Please check the Fix Version/s of BREAK-5, or the target
branch of this pull request.

Incorrect fix version
The Fix Version/s in issue BREAK-5 contains:

1.0.1

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

1.0.0

Please check the Fix Version/s of BREAK-5, or the target
branch of this pull request.

Incorrect fix version
The Fix Version/s in issue BREAK-5 contains:

1.0.1

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

1.0.0

Please check the Fix Version/s of BREAK-5, or the target
branch of this pull request.

/reset

Reset complete
I have successfully deleted this pull request's integration branches.

Incorrect fix version
The Fix Version/s in issue BREAK-5 contains:

1.0.1

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

1.0.0

Please check the Fix Version/s of BREAK-5, or the target
branch of this pull request.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

one peer

/approve

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/1.0

Please check the status of the associated issue BREAK-5.
Goodbye rachedbenmustapha.

authors: RachedBenMustapha bert-e

repo: scality/breakbeat


text:
Update dynamodb to 2.17.73

Updates software.amazon.awssdk:dynamodb from 2.17.68 to 2.17.73.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk", artifactId = "dynamodb" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Superseded by #1259.

repo: scanamo/scanamo


text:
deleting realm do not delete accounts

when you delete a realm, If there are some users into database they will not be deleted, and also the subject table will not be update with deletion.

users are removed, but accounts may be left orphan in db due to the early removal of providers, which could trigger the removal of account services.

authors: gianpaolo-tndigit matteo-s

repo: scc-digitalhub/AAC


text:
Explicit import of Class

#3 The class is now explicitly imported for ease of use.

Thanks @bhillmann


text:
🛑 Rust Server is down

In b71dc35, Rust Server (https://rust-servers.net/server/165972/) was down:

HTTP code: 200
Response time: 436 ms

Resolved: Rust Server is back up in f6133b3.

repo: schalkburger/server-status


text:
TinySoundFont HTML5 MIDI Player doesn't work in Microsoft Edge

Hi, Mr. Bernhard Schelling .
When I tried your TinySoundFont HTML5 MIDI Player at https://schellingb.github.io/TinySoundFont/CustomSoundFont.html using Microsoft Edge, I cannot hear any sound from my browser. But when using another browser, it works perfectly.
Are there any issue that can be fixed there? Because I want to ask somebody to make HTML5 game script  that support MIDI and your library is the best for it and I want to use your HTML 5 MIDI Player as reference.
Thank you very much for your attention.

I am sorry to bump this topic again.

Thanks for the report.
Sorry for the delayed response but I got it working :-)
Just to make sure, this library has no specific HTML5 features and there is no generic HTML5 interface. For it to be used like the HTML5 MIDI player demo, TinySoundFont needs to be compiled from C or C++ to WebAssembly or asm.js with Emscripten or Clang.
Building a plug-and-play JavaScript library using TinySoundFont with a generic interface that can be used in any HTML5 website or game would not be that hard, but it involves more than just HTML5/JavaScript.

Hi Mr. @schellingb .
Thank you very much for your response and your advice.
I myself am not a programmer, but my initial plan is to ask my programmer to use your pre-compiled  library from your HTML5 website and interfacing it with Javascript to use it in RPG Maker MV. We have tried the similar approach with libopenmpt.js and chiptune2.js and it worked. Now we want to try it with your library to add MIDI codec in our game.
We will tell you if we finished the task.
Thanks.

authors: RyanBram schellingb

repo: schellingb/TinySoundFont


text:
Add method move() to class vcl::vect::VectorT<>

See title.

Finally, won't do. This is not yet identified as mandatory.

repo: schmouk/vcl


text:
Add a time manager

Log option
Report option
Exporting?

In the works: https://github.com/schollz/awwkoala/tree/projects

repo: schollz/awwkoala


text:
🛑 findabooktoread.com is down

In c9735f5, findabooktoread.com (https://findabooktoread.com/) was down:

HTTP code: 502
Response time: 131 ms

Resolved: findabooktoread.com is back up in 2faa542 after 9 minutes.

repo: schollz/upptime


text:
🛑 www.poetrygenerator.ninja is down

In 1b59581, www.poetrygenerator.ninja (https://www.poetrygenerator.ninja/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.poetrygenerator.ninja is back up in cd5c8e0 after 9 minutes.


text:
Need lazy evaluation when using attributes in resources

When using chef attributes as defaults in custom resources, you need lazy evaluation so attribute overrides, etc work correctly. See https://github.com/chef/chef/issues/6989

Thanks for the merge!

repo: schubergphilis/chef-acme


text:
[draft] Initial version of the Dart Analyzer plugin [#132]

Description
As outlined in #132 I want to editing experience for Jaspr to be similar to what Flutter provides. This PR implements the initial version.
Type of Change

[x] ✨ New feature or improvement
[x] 📝 Documentation

fixes #132

@fusion44 Hello, what is state of this PR?

Hi,
Unfortunately I can't work on this right now. I have some other commitments I have to complete first. Sorry.

I started looking into it and added some initial code assists. Lets collect some lints/assists in the issue and align on what should be included in the initial version.

@schultek I believe the most important features are:

Adding new components/widgets in the component/widget tree.
Removing components/widgets from the tree.
Creating new components (stateless, stateful, and inherited).

When I look into the code, I can see these features are already in place.
If everything works and you don’t plan to add any other features at the moment, we can merge it since these three are crucial for a great development experience.
During future development, we can add additional features as needed. Alternatively, you could create a very simple tutorial on how to create and add new lint/assist features to Jaspr. This way, anyone can add new lint/assist features in the future as needed.

I have mainly added the code assists. I will spend a bit more time on adding some lints.

@schultek
Exists something how can I mark review comment as resolved?
I do not see any button to mark it as resolved and hide it:

@schultek Exists something how can I mark review comment as resolved?
I do not see any button to mark it as resolved and hide it:
Strange I have that button

@schultek Exists something how can I mark review comment as resolved?
I do not see any button to mark it as resolved and hide it:

Strange I have that button

Maybe I do not have some permission?

Sadly I cannot set specific permissions since this is a personal repo.

authors: fusion44 mjablecnik schultek

repo: schultek/jaspr


text:
Adding a CHANGELOG file

The CHANGELOG is also shown in the documentation as the last entry in the manu. Also, we now have a template for new PRs with a small checklist.
The CHANGELOG is now at version 0.1.5. I also updated the version accordingly.
PR Checklist

[ ] Tests?
[ ] Docs?
[x] CHANGELOG updated?
[ ] Issue raised/referenced?

:books: Documentation preview :books:: https://scikit-matter--198.org.readthedocs.build/en/198/

Can we add the changelog with the text up to version 0.1.4 in one commit, and then update the version together with changes in the changelog in another commit? I find it confusing if we mark commit fe58c89 as v0.1.5 commit while the other commit increases the version.

Yes, good idea. I can change this.

It is done @agoscinski

Can you add to the pyproject.toml the changelog?
[project.urls]
homepage = "https://example.com"
documentation = "https://readthedocs.org"
repository = "https://github.com"
changelog = "https://github.com/me/spam/blob/master/CHANGELOG.md"

Source https://peps.python.org/pep-0621/

authors: PicoCentauri agoscinski

repo: scikit-learn-contrib/scikit-matter


text:
WIP - Adaptation to scilpy

Adapted to the recent modif in scilpy

@frheault can you send some data to test on please.

I do a test and merge if everything is fine

authors: GuillaumeTh alexjoa frheault

repo: scilus/bst-flow


text:
Remove KMS dependency for Rethink quoin

Rethink quoin currently depends on KMS. We need to remove this dependency so it can be used in regions where there is no KMS, e.g. China AWS.

Any feeling for how deep this story and #64 are in your backlog?

We're refining our backlog and taking care of some technical debt items, that is currently the priority. With that said, we're currently spiking k8s 1.7 & 1.8 upgrades which could change things in how we run our rethink cluster, which could make this issue a mute point.

authors: cfreiner dragan nicklathe

repo: scipian/quoins


text:
Is there any function to set the initial value for the Integer Linear Programming (ILP) problem?

To solve a very complicated ILP problem, I have to use a greedy method to work out an initial value set. How can I apply this initial value set to the Solver?
Thank you for your help.

You can add one or more starting points using something like this:
    Variable[] vars = …;
    double[] startPoint = …;
    Solution startSolution = scip.createSol();
    scip.setSolVals(startSolution, vars, startPoint);
    scip.addSolFree(startSolution);

but be warned that SCIP will do nothing with your solution if it is not feasible (at least to the tolerance).

You can add one or more starting points using something like this:
    Variable[] vars = …;
    double[] startPoint = …;
    Solution startSolution = scip.createSol();
    scip.setSolVals(startSolution, vars, startPoint);
    scip.addSolFree(startSolution);

but be warned that SCIP will do nothing with your solution if it is not feasible (at least to the tolerance).

It's my honour to get your support. Thank you.
The initial value is calculated by a greedy method that fully obeys the constraints. I can guarantee its feasibility. I will try your suggestion first.

authors: HuangGuanSteve kkofler

repo: scipopt/JSCIPOpt


text:
scipy.wavefile supports >2 channels !

the docs for write say only 1 and 2 channels are supported.  for read nothing is said regarding the number of channels.  but the simple test script below shows they both support at least 3.  is this by chance?  will it continue to work in future?  is it supported??  i hope so!!  and if so, maybe update the docs.
import scipy.io.wavfile
import numpy as np

d = np.random.randint(10, size=(10,3))
scipy.io.wavfile.write("foo.wav", 8000, d)
fs, dp = scipy.io.wavfile.read("foo.wav")
np.all(d==dp)

Yes, channels are supported, theoretically up to 65,535
https://github.com/scipy/scipy/blob/master/scipy/io/wavfile.py#L416
https://github.com/scipy/scipy/blob/master/scipy/io/wavfile.py#L693
The documentation says

To write multiple-channels, use a 2-D array of shape (Nsamples, Nchannels)

and it has said that for over a decade...
I'll add a line to the read() function about the shape of the data return

authors: bjarthur endolith

repo: scipy/scipy


text:
RFC: Use conditional compilation to make sf_error an optional include for special function compiled kernels.

Following up on https://github.com/scipy/scipy/issues/19404, we are moving forward with preliminary work that could lead to making an important subset of special a header only library of NVCC compatible code that could be included in other projects (and which may eventually find a home outside of the SciPy code base.
As discussed in the review comments for https://github.com/scipy/scipy/pull/19435, we use code from sf_error.c for error handling in special functions, which makes calls to the Python C API. While this is the case, any code which makes use of sf_error cannot be NVCC compatible. One solution is to use conditional compilation to make make the use of sf_error only occur when a compile time symbol such as USE_SF_ERROR is set. There are several ways this could be done, so I'm creating this RFC issue for discussion on how this could best be achieved.
One possibility would be to define a new header file with the following lines; defining sf_error to be a no-op if the symbol USE_SF_ERROR is not defined.
#ifdef USE_SF_ERROR
#include "sf_error.h"
#else
inline void sf_error(const char *func_name, sf_error_t code, const char *fmt, ...) {};
#endif

For any compiled kernel written in C++ where we want to make the use of sf_error optional , we could include this header instead of "sf_error.h". I think this would be would be simpler and less intrusive then modifying the current sf_error code directly, with the cost that we'd have to remember to include the right header instead of having things work seamlessly.
I'm happy to hear your thoughts everyone.

Thanks @izaid, I like that idea. I think I misunderstand something (sincerely)
In the following lines, it seems like SP_SPECFUN_NOERROR should correspond to the case where set_error does nothing. At least that's how I understand NOERROR.
#ifndef SP_SPECFUN_NOERROR
        void set_error(const char *func_name, int code, const char *fmt, ...) {
            // nothing
        }
#else
        void set_error(const char *func_name, int code, const char *fmt, ...);
#endif

In any case, I'll put together a PR implementing your idea. Plenty of time to bikeshed stuff like names.

@steppi Yes, I get you, probably SP_SPECFUN_NOERROR should be renamed SP_SPECFUN_ERROR. I think the important thing is that error is opt in, thus a library has to define something to not get the default empty implementation.

@izaid, this solution won't work for Cephes if we make it a header only C library, since it uses sf_error internally as well. Do you think it's fine to go full steam ahead with this approach for now, and sort Cephes out later, or should we rethink things in the context of Cephes?

@steppi Good find! I guess cephes didn't originally use sf_error, and that SciPy at some point just added it into cephes.
In that case, I think the cephes functions would need to move from sf_error to scipy::special::set_error as well.
I'm fine to leave cephes alone for now and go with this approach. We'll have to get cephes to hook into this at some point, but it doesn't need to be now. There are options.

authors: izaid steppi


text:
WIP, DOC: 1.7.0 release notes

add the draft author, issue, and PR lists (need to be checked/refreshed
just before merging/branching)

transcribe the release notes wiki entries into the release notes
proper (should check for new wiki entries before merging/branching)

manually check every single merged enhancement-labelled PR with 1.7.0
milestone and add entries that were not captured in the wiki (quite a
lot of them)

still not done:

[ ] check for errors in i.e., make html-scipyorg or similar (I usually
end up introducing a few when transcribing to rst, and so does the
issue/PR list script with some characters in GitHub titles)
[ ]  finalize highlights section (@WarrenWeckesser @mdhaber et al.; the number of improvements in stats is pretty staggering--if you'd like more highlights added let me know)
[ ] author list/.mailmap final cleanups...

@treverhines Any idea what is going on with the Windows CI failure related to rbf interpolator here? Hopefully fixed at branching time this evening.

@treverhines Any idea what is going on with the Windows CI failure related to rbf interpolator here? Hopefully fixed at branching time this evening.

@tylerjereddy Sorry I am not seeing the error you are referring to.

Refguide failure:
Checking tutorial files at doc/source/tutorial/*.rst:

===================
scipy.sparse.linalg
===================

scipy.sparse.linalg.lsqr
------------------------

File "build/testenv/lib/python3.8/site-packages/scipy/sparse/linalg/isolve/lsqr.py", line 264, in lsqr
Failed example:
    x, istop, itn, normr = lsqr(A, b)[:4]
Expected:
    The exact solution is  x = 0
Got nothing

@treverhines Any idea what is going on with the Windows CI failure related to rbf interpolator here? Hopefully fixed at branching time this evening.

@tylerjereddy Sorry I am not seeing the error you are referring to.

I'll have a look - there's a segfault, but not on Windows. Almost certainly because I forgot to update Pythran in one of the CI config files.

Oh no, it's not Pythran. You mean this right, @tylerjereddy:
Fatal Python error: Segmentation fault
...
SCIPY_USE_PYTHRAN=`test 3.9 != 3.9; echo $?` python -u runtests.py

scipy/sparse/linalg/eigen/arpack/tests/test_arpack.py .................. [ 54%]
.............                                                            [ 54%]
Fatal Python error: Segmentation fault

Current thread 0x0000000110b75dc0 (most recent call first):
  File "/Users/runner/work/scipy/scipy/build/testenv/lib/python3.9/site-packages/scipy/linalg/decomp.py", line 561 in eigh
  File "/Users/runner/work/scipy/scipy/build/testenv/lib/python3.9/site-packages/scipy/sparse/linalg/eigen/lobpcg/lobpcg.py", line 585 in lobpcg
  File "/Users/runner/work/scipy/scipy/build/testenv/lib/python3.9/site-packages/scipy/sparse/linalg/eigen/lobpcg/tests/test_lobpcg.py", line 224 in test_hermitian
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/python.py", line 183 in pytest_pyfunc_call
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/python.py", line 1641 in runtest
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 162 in pytest_runtest_call
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 255 in <lambda>
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 311 in from_call
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 254 in call_runtest_hook
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 215 in call_and_report
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 126 in runtestprotocol
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/runner.py", line 109 in pytest_runtest_protocol
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/main.py", line 348 in pytest_runtestloop
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/main.py", line 323 in _main
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/main.py", line 269 in wrap_session
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/main.py", line 316 in pytest_cmdline_main
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/Users/runner/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/_pytest/config/__init__.py", line 162 in main
  File "/Users/runner/work/scipy/scipy/build/testenv/lib/python3.9/site-packages/scipy/_lib/_testutils.py", line 67 in __call__
  File "/Users/runner/work/scipy/scipy/runtests.py", line 316 in main
  File "/Users/runner/work/scipy/scipy/runtests.py", line 565 in <module>
/Users/runner/work/_temp/98b2fa9b-e345-4449-9395-222d248ea288.sh: line 1:  2832 Segmentation fault: 11  SCIPY_USE_PYTHRAN=`test 3.9 != 3.9; echo $?` python -u runtests.py

The message is a little misleading, I thought it was Pythran at first when I saw it in another PR, but it's an ARPACK crash.

2021-05-26T03:54:48.3408854Z C:\hostedtoolcache\windows\Python\3.7.9\x64\lib\site-packages\scipy\interpolate\_rbfinterp.py:127: in _build_and_solve_system
2021-05-26T03:54:48.3410635Z     raise LinAlgError(msg)
2021-05-26T03:54:48.3411968Z E   numpy.linalg.LinAlgError: Singular matrix.

tylerjereddy/scipy#53 fixes the heading rendering issues. e.g.

is now nested correctly:

I mean the test failure below the fold involving a singular matrix (and at this link: https://dev.azure.com/scipy-org/df8ffb44-7275-43bc-90f9-aa5c93ef5c51/_apis/build/builds/12350/logs/213 ):

The matrix that is being solved in that test should be really close to singular. I am not sure what could have changed to cause the singular matrix error to be thrown.  Could it be using some version of lapack that has a different tolerance for when a matrix is considered singular? I can update the test to add a slight amount of smoothing to make it numerically stable, but I would first like to figure out what is different here that caused the error.

Refguide failure:

Checking tutorial files at doc/source/tutorial/*.rst:

===================

scipy.sparse.linalg

===================

scipy.sparse.linalg.lsqr

------------------------

File "build/testenv/lib/python3.8/site-packages/scipy/sparse/linalg/isolve/lsqr.py", line 264, in lsqr

Failed example:

    x, istop, itn, normr = lsqr(A, b)[:4]

Expected:

    The exact solution is  x = 0

Got nothing

Addressed in #14139 @tylerjereddy

I'm probably going to hack over these warnings with double backticks for now. The FFT hankel stuff was merged in recently I think...
/mnt/c/Users/treddy/github_projects/scipy/doc/source/tutorial/fft.rst:574: WARNING: py:func reference target not found: fht
/mnt/c/Users/treddy/github_projects/scipy/doc/source/tutorial/fft.rst:574: WARNING: py:func reference target not found: ifht
/mnt/c/Users/treddy/github_projects/scipy/doc/source/tutorial/fft.rst:597: WARNING: py:func reference target not found: fhtoffset

Ok, if CI is green I'm likely to proceed with a merge. The render of the release notes is pretty nice locally with latest version of this feature branch.
Some things that might still be improved during rc phase for example:

more mailmap updates: author list has some usernames instead of proper names (including for some people I know); this is pretty minor, but the author list always ends up with more fixes needed
there's an issue open for this, but as Evgeni notes, perhaps at least a backcompat section mention for the argsereduce stats change is justified?
some (transient?) CI failures noted above--the wheels repo usually has problems even when master is all green, so decent chance we may need to deal with those, but I guess we'll see..

Most other comments have been addressed, and Matt also made some nice formatting improvements beyond helping address stats-related comments.

CI is green, in it goes

@tylerjereddy in the template of the release notes, what about we remove the table of content (.. contents::)? With the new theme this is a bit of a duplicate. I can do a quick PR for that if you want.

authors: mdhaber rgommers treverhines tupui tylerjereddy


text:
CI: move macosx_arm64 from cirrus to GHA

Will make the cost of Cirrus cheaper.

Specifically this is for a general CI run, not wheel building.


text:
DOC: special.ellipj: fix order of parameters in docstring

The updates parameters to be in the order of the function signature. Double-checked against the definition in special_wrappers.h.

Also pushed changes to fix the use of backticks


text:
MAINT, TST: CuPy skip ndimage test

Fixes gh-21486

scipy/ndimage/tests/test_filters.py::TestNdimageFilters::test_correlate_convolve_axes was causing 240 test failures on main with CuPy backend because the CuPy ndimage equivalents of convolve and correlate don't have an axes kwarg, even in the latest stable release.

So, skip these tests with CuPy for now.

[skip cirrus] [skip circle]

Sounds like Lucas is happy here. The CI is as well. Given that this just skips a test on GPU/CuPy while we wait for upstream CuPy release with new feature, and avoids 240 CuPy-based test failures with a single test marker, the self-merge can be forgiven I think.


text:
MAINT: integrate: Avoid using variable l in quadrature, integrate._…

…ivp: Avoid using variable I in bdf,io.matlab: Avoid using variable O in mio4
fixed https://github.com/scipy/scipy/issues/8389

If you're going to the trouble of replacing the problematic single letters (which can look like numbers in some fonts), why not replace them with longer variables names rather than a different single letter?

It is only Python 3.5 which failed on TravisCI, and it looks like white space and rounding issues only - my hunch would be NumPy 1.14 related. The logs are a little odd here:
$ travis_retry pip install $NUMPYSPEC
You must give at least one requirement to install (see "pip help install")

Later on we see:
Successfully uninstalled numpy-1.14.0

This would seem to be a wider issue and not specific to your changes.

See #8279 for the NumPy 1.14 failure

the integer is represented as MOPT where M is the thousands digit, O is the hundreds digit, P is the tens digit, and T is the ones digit. Here you are changing O to different chars but the error message shouldn't change. It's still the O of MOPT.
I thought we were going to ignore this this PEP8 rule in one of those issues.

Similarly the change from I to K for an identity matrix is a bad idea. Something like id should be ok.

@person142 can I give it a name then like identity or anything else??

TBH, I don't believe that benefits here justify the code churn, and I think this PR should not be accepted.

-0 from me on PRs fixing variable names etc. minor style issues

If the SciPy team are on balance against these changes, should we close #8389 as a won't fix (and perhaps say so explicitly in the style checking configuration comments?)

I agree with @ev-br and @pv, so I'm going to close this. Thank you nevertheless @samyak0210 for attempting to address an open issue.

If the SciPy team are on balance against these changes, should we close #8389 as a won't fix (and perhaps say so explicitly in the style checking configuration comments?)

@peterjc good point. I'll comment on that issue.

authors: ev-br ilayn person142 peterjc pv rgommers samyak0210


text:
Interoperability test suite development tracker

Interoperability test suite preview with SCITT API Emulator using Postman
Long term goal:  https://w3c-ccg.github.io/traceability-interop/reports/interoperability/

[ ] Add a postman collection that can be run with newman that covers a single endpoint with tests.
[ ] Wire the reporter / renderer to CI, so the report is published

Don't worry about multivendor, focus only on conformance for the emulator first.

repo: scitt-community/scitt-api-emulator


text:
Add clean-hook variable

Also adds (unused by default) clean-versions rule that removes versioned directories
Required-by: https://github.com/sclorg/postgresql-container/pull/276
Closes: https://github.com/sclorg/container-common-scripts/issues/82

[test]

nice, thank you

authors: pkubatrh praiskup

repo: sclorg/container-common-scripts


text:
perceptional_loss in scale loop

https://github.com/sconlyshootery/FeatDepth/blob/db7344ae9d9cefafc92983fc8c5b30920751be68/mono/model/mono_fm_joint/net.py#L114-L121
https://github.com/sconlyshootery/FeatDepth/blob/db7344ae9d9cefafc92983fc8c5b30920751be68/mono/model/mono_fm_joint/net.py#L175-L178
perceptional_loss is only computed in scale [1] (1/2 w, 1/2 h),  but the code block is in the scale loop. So I think the loss is summed 5 times, and / len(self.opt.scales) at last.

Yes, the code written in this way is convenient for me to test perceptional loss' effect under different scale. I found it works best at largest scale, so I fixed scale here.

https://github.com/sconlyshootery/FeatDepth/issues/18#issuecomment-785796082
A similar issue I answered recently, you can refer to it.

I will close this issue now, if you have further question, please reopen it.

authors: Darknesszlx sconlyshootery

repo: sconlyshootery/FeatDepth


text:
Sagas

Implementing Sagas.  Sagas are how we are going to ensure all Tasks in a Job are completed.
Code

Saga Struct & Methods give users an interface to program against, backed by a SagaLog
SagaLog Interface allows us to implement the durable backend.
SagaState tracks SagaState.  Ensures messages added to a Saga are valid.  Currently not thread safe because there should be only One Go Routine updating an individual Saga at a time, this gives us thread safety and message ordering guarantees for free!
-InMemorySagaLog, A non-durable Implementation of a SagaLog for demo & unit testing code.

Tests

various test cases
introduced gomocks into the codebase for testing the Interface.  Checking in code generated code for now will add to build process in subsequent pull request

Demo

updated Demo code to use Sagas.
InMemory Saga prints received messages to the command line
run demo: go run sched/demo/main.go

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

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

@@             master        #10   diff @@
==========================================
  Files             3          8     +5
  Lines            52        279   +227
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits             38        195   +157
- Misses           14         84    +70
  Partials          0          0

Powered by Codecov. Last updated by [7667e75...e95399a][cc-compare]
[cc-base-branch]: https://codecov.io/gh/scootdev/scoot/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/scootdev/scoot/compare/7667e7576be45e71dd939f4388436cf22eedb054...e95399a84566bbdfba0a4b3e7eeaf36a1ddca85e
[cc-pull]: https://codecov.io/gh/scootdev/scoot/pull/10?src=pr

I think this is designed well in terms of minimizing testing verbosity, but is it accommodating testing too much? Otherwise, lgtm, it's easy enough to read and understand it as written

Refactored Saga methods to take in a SagaState and return a SagaState as discussed with Dan.
This is more functional, easier to test etc... Still has a side-effect of durably persisting the data to the SagaLog though.  SagaStates cannot be created outside the Saga package without calling Saga.StartSaga(...)
The next TODO piece after this implementation is the Recovery part.  Reading the Durable SagaLog to reconstruct a list of all in progress sagas and their state, and then hand it back to the caller to reschedule as necessary.
This also probably needs a pass tomorrow to re-evaluate if some of the SagaMessage functions still need to be exposed outside the package.  They probably do not.  SagaMessages should also have a default serialize/deserialize method provided for SagaLog Implementations to use to persist the data.

I thought the message factories were perhaps not needed and I wanted to know if you took that direction because it would facilitate testing, or because you tried a couple variations and this way was best, etc. I'm simply looking to reduce the lines of code where possible if it doesn't hurt readability.

@jasonbs10 back to the MakeMessage Methods (MessageFactoryMethods) I created them because I want to enforce stronger guarantees of what's in a message, what fields are set etc... than the Go Type System allows me to use.  If we were in a Strongly typed Language there would be

abstract class SagaMessage
case class StartSagaMessage extends SagaMessage
case class EndSagaMessage extends SagaMessage
abstract TaskMessage extends SagaMessage
case class StartTaskMessage extends TaskMessage
etc ...

While the code is more verbose, its more maintainable, if we choose to add data to a message, the compiler will enforce that all parameters necessary to initialize this object are provided.  If we just initialize based on the struct we are liable to miss updating things, since its not compile time enforced.

(Jumping in, so apologies if I'm missing context)
Will the factory methods ever be called from another package? It seems like in the current setup, they won't, and so we're trying to stop ourselves from doing something wrong.
I like it if it stops clients from doing the wrong thing, but I don't think it will. (sagaMessage isn't even exported, so they can't create a variable of that type)

I assume they will be called when users are testing their SagaLog implementations which will be in other packages.  The interface of LogMessage uses sagaMessages, which cannot be created directly.
Maybe this is just for testing, but I think its more readable code and a nice API for low overhead easy to maintain code.

Ah, I see. Yeah, in memory saga log is currently privileged because it lives in this package.
I think this is something where we need more experience and shouldn't bikeshed now.
I'm happy to trust your sense, but I want to make sure we don't ignore concerns and end up with too much code (which is my understanding of Jason's concerns).
I don't know what the best thing to do is. Maybe revisit this at some point to see what it's buying us as we have our second implementation of log?

Yes happy to have this evolve if it becomes burdensome.  @dbentley gave a verbal Ok to Check In @jasonbs10 anything outstanding before submitting?

Nope, nothing outstanding, feel free to merge.

repo: scootdev/scoot


text:
Fixed the init_test

Fixed the main_init_test.go
Description

The following TestInitWithProvisioners often fails , so by adding this new lines will help to check whether the expected provisioner URI is present in the provs collection of provisions or not..
What does this PR do?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New chore (expected functionality to be implemented)

Checklist:

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[x] I've signed off with an email address that matches the commit author.

here is test check by running it for 15 times

@astromechza, quick review on this one please? Thanks!

repo: score-spec/score-compose