Error with --nolamda option enabled

Greetings,
I am facing some troubles when I am using --nolamda option:
macs2 callpeak -t CB9TUACXX_OATAC_TAS_17s005511-1-1_lane6_1_sequence.dup.bed -f BED --nomodel --nolambda --keep-dup all --shift 37 --extsize 73 -n peak_calling/nolambda_out
...
INFO  @ Wed, 15 Nov 2017 14:44:10:  50000000
INFO  @ Wed, 15 Nov 2017 14:44:12:  51000000
INFO  @ Wed, 15 Nov 2017 14:44:14:  52000000
INFO  @ Wed, 15 Nov 2017 14:44:16:  53000000
INFO  @ Wed, 15 Nov 2017 14:44:19:  54000000
INFO  @ Wed, 15 Nov 2017 14:44:21:  55000000
INFO  @ Wed, 15 Nov 2017 14:44:23:  56000000
INFO  @ Wed, 15 Nov 2017 14:44:26: #1 tag size is determined as 49 bps
INFO  @ Wed, 15 Nov 2017 14:44:26: #1 tag size = 49
INFO  @ Wed, 15 Nov 2017 14:44:26: #1  total tags in treatment: 56122595
INFO  @ Wed, 15 Nov 2017 14:44:26: #1 finished!
INFO  @ Wed, 15 Nov 2017 14:44:26: #2 Build Peak Model...
INFO  @ Wed, 15 Nov 2017 14:44:26: #2 Skipped...
INFO  @ Wed, 15 Nov 2017 14:44:26: #2 Sequencing ends will be shifted towards 3' by 37 bp(s)
INFO  @ Wed, 15 Nov 2017 14:44:26: #2 Use 73 as fragment length
INFO  @ Wed, 15 Nov 2017 14:44:26: #3 Call peaks...
INFO  @ Wed, 15 Nov 2017 14:44:26: # local lambda is disabled!
INFO  @ Wed, 15 Nov 2017 14:44:26: #3 !!!! DYNAMIC LAMBDA IS DISABLED !!!!
INFO  @ Wed, 15 Nov 2017 14:44:26: #3 Pre-compute pvalue-qvalue table...
Traceback (most recent call last):
File "/usr/local/bin/macs2", line 614, in
main()
File "/usr/local/bin/macs2", line 56, in main
run( args )
File "/usr/local/lib/python2.7/dist-packages/MACS2/callpeak_cmd.py", line 261, in run
peakdetect.call_peaks()
File "MACS2/PeakDetect.pyx", line 110, in MACS2.PeakDetect.PeakDetect.call_peaks (MACS2/PeakDetect.c:1665)
File "MACS2/PeakDetect.pyx", line 364, in MACS2.PeakDetect.PeakDetect.__call_peaks_wo_control (MACS2/PeakDetect.c:4714)
File "MACS2/IO/CallPeakUnit.pyx", line 858, in MACS2.IO.CallPeakUnit.CallerFromAlignments.call_peaks (MACS2/IO/CallPeakUnit.c:12340)
File "MACS2/IO/CallPeakUnit.pyx", line 883, in MACS2.IO.CallPeakUnit.CallerFromAlignments.call_peaks (MACS2/IO/CallPeakUnit.c:11717)
File "MACS2/IO/CallPeakUnit.pyx", line 653, in MACS2.IO.CallPeakUnit.CallerFromAlignments.__cal_pvalue_qvalue_table (MACS2/IO/CallPeakUnit.c:9065)
File "MACS2/IO/CallPeakUnit.pyx", line 496, in MACS2.IO.CallPeakUnit.CallerFromAlignments.__pileup_treat_ctrl_a_chromosome (MACS2/IO/CallPeakUnit.c:7329)
TypeError: 'float' object cannot be interpreted as an index
while when I do not enable it, the program is run with no errors.
Any help would be appreciated.

I meet the same problem in MACS2-<IP_ADDRESS>50420

I've also encountered this problem. Is there a known solution?

Not yet from my side..
2018-07-11 23:52 GMT+03:00 OscarBrock<EMAIL_ADDRESS>
I've also encountered this problem. Is there a known solution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/taoliu/MACS/issues/221#issuecomment-404305397, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ae8nwCLgfM88A-ex1Wbvbj9EEMawN_Uaks5uFmV-gaJpZM4Qe9rX
.

Hi all,
I get the same error on MACS2. From looking around the web, this seems an obscure issue from numpy - many people reported fixing it by changing to different python/numpy/numerical libraries installation.
In my case this happened in a cluster environment with system-installed libraries.
I then used conda with python 3.7 and macs2 from bioconda and it worked.

@Heroico Right. This is one of the major updates in recent macs2 releases -- to test under different environments. To install macs2 from bioconda definitely will make life easier/happier.


Localize git infrastructure.

OSX hopefully fixed by https://github.com/microsoft/vcpkg-tool/pull/915


doc(database): Document off-cluster db configuration

Complements https://github.com/deis/charts/pull/286
cc @bacongobbler

I think this is safe to merge now that we are going through the release process and going to be releasing a v2.1.0 chart hopefully today, but it's your call @krancour. :)


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=363298464
https://github.com/Azure/azure-cli-extensions/commit/a0b24e846c3a9d74a5deddac5289753d5187869b

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


where can I find the ncnn yolox.bin file

Thanks for your suggestion. #6 has already fixed this issue.


Crash on email link fix

What
Fixed crash caused when user tapped email link on Project Updates.
How
The app was treating links with url scheme mailto: as a safari link, instead of email. Because the WebView couldn't handle this kind of url, the app crashed.

 [ZD] [iOS] App crashes when you tap on an email link


python310Packages.google-cloud-bigtable: 2.17.0 -> 2.18.1

Changelog: https://github.com/googleapis/python-bigtable/blob/v2.18.1/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 233289 run on x86_64-linux 1

4 packages built:

python310Packages.google-cloud-bigtable
python310Packages.google-cloud-bigtable.dist
python311Packages.google-cloud-bigtable
python311Packages.google-cloud-bigtable.dist


Leaflet.Snap - How to remove snap editing points from polyline

Hello,
I have started using the 'Leaflet.Snap' and drawing editable polygons.
I use this to create my polygon and add it on my map:
var polygonSpanZoneHandler ;
var polygonSpanZone;
polygonSpanZone = L.polyline( fiCoords, //points coordinates
{color: 'red', fillColor: '#f03', fillOpacity: 0.5, opacity: 1.0}).addTo(map2);
			polygonSpanZoneHandler = polygonSpanZone.snapediting;
			polygonSpanZoneHandler = new L.Handler.PolylineSnap(map2,  polygonSpanZone);
	        polygonSpanZoneHandler.enable();

After that, I use another function to remove the layer from my map:
map2.removeLayer(polygonSpanZone);
And the layer is removed successfully from the map.
The problem is that the editing snap points of the polygon are not removed.
I tried this:
polygonSpanZoneHandler.disable();
but I had no luck removing them from the map.
Is there some other way I could use in order to have the editing points removed too?
Thank you very much for your help!

You can find attached an issue in order for the issue to be more clear:

On the top you can see that the polyline layer has been removed but the points remain on the map.

Nice bug!
I personally can't spend time on this library anymore :( but if you look at the code you should be able to track down the faulty piece of code. Don't hesitate to open a pull-request though :)
Good luck!

Hi @ckar2006 !
I just commited a8b87a6 that should fix this bug. Could you please check if the snapping points are now succesfully removed in your case?

Hello,
The problem seems that has been resolved!
Thank you very much for your help!


Fix docker volume mounting in README.

By mounting scala-steward directory into /opt/docker inside of the container, you overwrite all of the existing files including /opt/docker/bin/scala-steward and all the jars in /opt/docker/lib/ which makes the container fail on startup (as the entry point script can no longer be executed).
I've updated the README to address this by mounting $STEWARD_DIR into /opt/scala-steward instead.

@all-contributors please add @mwz for doc


Option to disable TLS support at run-time

I have a project where reqwest is used both with and without TLS support. The compile flag can't be used in a cargo workspace, as the dependencies are conflated and it always has tls in the end (if I understand how that works right).
I suspect there's some overhead when using Https Connector. So I'd like to switch it off in my ClientBuilder.
My proposed solution is to add enum option TlsBackend::None, and the corresponding branch here: https://github.com/seanmonstar/reqwest/blob/master/src/async_impl/client.rs#L134
I'll make a PR implementing this, but I'd like to hear the opinion of someone more familiar with the codebase - if this is a good idea, can it work like this, and if there really is an overhead?
Thanks

There isn't going to be much overhead that the TLS connector is enabled. It's pretty much just an if url.scheme() == "https" check. If the scheme isn't HTTPS, then just a basic TCP stream is used and nothing more.
The purpose of the compile flags is to allow removing the dependencies completely, perhaps to reduce binary size, or to compile on an environment with no TLS capability.


EnumField

a field that converts to an int behind the scenes, but allows the live object to have a set of values, so you could do something like:
class Foo(Orm):
  bar = EnumField("a", "b", "c", "d")

f = Foo()
f.bar = ["a", "b"]
f.save() # bar will save into the db as 3

f2 = f.query.get_pk(f.pk)
f2.bar # ["a", "b"]

So the enum field will set the appropriate field setters to make sure the the live orm always has a set of values, and that the db always gets the int, when it creates the field it takes the values you passed into it and sets their values in the order they are passed in, doubling the value as it goes, so
EnumField("a", "b", "c", "d")
a = 1
b = 2
c = 4
d = 8

I think this is actually superceded by extras.config.Field's enum support


[EOSi Frontend] #8 Replace with text that I will...

Replace with text that I will add to this issue.
Source url: https://eosi-frontend.netlify.app/product-template.html
Reported by: Chris ()
Reported at: 06 Jul at 16:38 UTC
Type: Feedback
Location: US, Massachusetts, Buzzards Bay
Browser: Firefox 102.0
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Firefox/102.0
OS: macOS 10.15
Screen: 2560x1440
Viewport: 1447x743
Referrer: https://eosi-frontend.netlify.app/product-template.html
Screenshot:

For more details please visit report page on Ybug:
https://ybug.io/dashboard/reports/detail/78fxrrrkrcw1msqkxga0

I got this one

Fixed on https://github.com/dative/eosi-frontend-mix/pull/28


Test and integrate model cards from Hub library

With the new release of huggingface_hub (https://github.com/huggingface/huggingface_hub/releases/tag/v0.10.0), model cards have been completely integrated there and modelcards is deprecated.
From the skops side, we should ensure that everything works with the new hub version and write code to transition to using it instead of modelcards.

we can migrate to using modelcards from huggingface_hub, and move the dependency up. I think we can do it since we still don't have many users.


Extend HooksBaseProps from SpringProps

Currently, the typings for useTransition cause an error when declaring onRest and onFrame. This seems to be caused by a chain dependencies that result in:
export interface HooksBaseProps extends Pick<SpringBaseProps, Exclude<keyof SpringBaseProps, 'config'>> {

SpringBaseProps looks like:
export interface SpringBaseProps {
  config?: SpringConfig | ((key: string) => SpringConfig)
  native?: boolean
  reset?: boolean
  immediate?: boolean | ((key: string) => boolean)
  delay?: number
  reverse?: boolean
  onStart?(): void
}

The SpringProps interface declares the missing props and extends SpringBaseProps, so I think the solution is for HooksBaseProps to extend SpringProps instead of SpringBaseProps directly.

Thanks for contributing! But it's unlikely that this will be merged, because Paul doesn't know TypeScript and I'm focusing solely on v9. Sorry!


Change FixedVariableComposite to handle non-blocking child samplers

Codecov Report

Merging #555 into master will increase coverage by <.01%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master     #555      +/-   ##
==========================================
+ Coverage   93.33%   93.33%   +<.01%
==========================================
  Files          52       52
  Lines        3555     3557       +2
==========================================
+ Hits         3318     3320       +2
  Misses        237      237

Impacted Files
Coverage Δ

dimod/reference/composites/fixedvariable.py
96.66% <85.71%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

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


ActiveDirectoryProperties is not set for storage account 'mystor1' in resource group 'myresourcegrp"

[Enter feedback here]
I have followed the instructions for Enabling AD DS authentication using Option 1 with a ServiceLogonAccount. I have been unsuccessful in resolving these issues. The Service Account has been created, but I received the following error after the Join-AZStorageAccount:
Warning: Module ActiveDirectory is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck syntax.
Set-AzStorageAccount; Cannot validate argument on parameter 'ActiveDirectoryDomainSid'. The argument is null or empty. Provide an argument theta is not null or empty, and then try the command again.
Running Debug uncovered the following problems that I have also not been able to resolve:
Issues found:
---- CheckADObject ----
ActiveDirectoryProperties is not set for storage account 'mystor1' in resource group 'myresourcegrp'. To set the properties, please use cmdlet Set-AzStorageAccount if the account is already associated with an Active Directory, or use cmdlet Join-AzStorageAccountForAuth to join the account to an Active Directory (https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-enable)
---- CheckUserRbacAssignment ----
Index operation failed; the array index evaluated to null.
---- CheckADObjectPasswordIsCorrect ----
ActiveDirectoryProperties is not set for storage account 'ctgstor1' in resource group 'myresourcegrp'. To set the properties, please use cmdlet Set-AzStorageAccount if the account is already associated with an Active Directory, or use cmdlet Join-AzStorageAccountForAuth to join the account to an Active Directory (https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-enable)
---- CheckStorageAccountDomainJoined ----
ActiveDirectoryProperties is not set for storage account 'mystor1' in resource group 'myresourcegrp'. To set the properties, please use cmdlet Set-AzStorageAccount if the account is already associated with an Active Directory, or use cmdlet Join-AzStorageAccountForAuth to join the account to an Active Directory (https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-enable)
I tried running both PS commandlets but received no output from either
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7a1a9f3d-5733-012a-a0d7-c00ec21b9232
Version Independent ID: 1e70ab95-9488-5aa3-b8ef-e58b3e0067bb
Content: Enable AD DS authentication to Azure file shares
Content Source: articles/storage/files/storage-files-identity-ad-ds-enable.md
Service: storage
Sub-service: files
GitHub Login: @khdownie
Microsoft Alias: kendownie

@rickakey Thanks for the question! We are investigating and will update you shortly.

#reassign: @khdownie

Not enough information to verify cause. Since we haven't gotten any similar reports, I'm going to close this as it seems like a support issue.

#please-close

I've got the same issues, after calling the command Join-AzStorageAccount I get this error: Set-AzStorageAccount; Cannot validate argument on parameter 'ActiveDirectoryDomainSid'. The argument is null or empty.
I've solved removing ".Value" in the script AzFilesHybrid.psm1 at lines 3771 and 3775:
$azureStorageSid = $azureStorageIdentity.SID[.Value]
$domainSid = $domainInformation.DomainSID[.Value]

#reopen

@gamon73 were you using PowerShell 7 or PowerShell 5?

The issue for DomainSID is known for powershell7 and the fix will be in the next release of AzFilesHybrid module.
I haven’t heard any report on $azureStorageIdentity.SID[.Value] but we will include it in the validation for the new release on powershell7.

@khdownie the powershell version is 7.2.6
$PSVersionTable
Name                           Value

PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.14393
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0


flutter_gallery_ios32__transition_perf 90th_percentile_frame_rasterizer_time_millis and flutter_gallery_ios__transition_perf 90th_percentile_frame_rasterizer_time_millis regression

Pretty clear jump at https://github.com/flutter/flutter/pull/45130 for both.
Update on 03/02/2020 thanks to some discussions in https://github.com/flutter/flutter/pull/51791:
The actual regression is that between 3c65463 and d189b94 (11/18/2019 - 01/21/2020), a commit has regressed the iOS rasterization time if more than one layer tree gets rasterized per VSync.
Before 3c65463 and after d189b94, Flutter has a pipeline depth greater than 1 which allows multiple-rasterizations-per-vsync. Between those two commits, the pipeline depth is restricted to 1 so the regression isn't revealed until d189b94.
The next step should be to bisect between 3c65463 and d189b94 . For each commit X in the middle, do the following

git checkout X
git revert 3c65463 or git cherry-pick d189b94 to set the pipeline depth above 1.
Run flutter_gallery_ios__transition_perf locally to see if the commits up until X already has the regression.

Not clear why this was closed - the revert PR is what caused to performance regression.

Between those two commits, the pipeline depth is restricted to 1 so the regression isn't revealed until d189b94.

Where do you get that the depth was restricted to 1?
I don't remember ever seeing the depth reduction committed to the repo. It's a hack that lets us see if vsync locking is causing a problem, but since its down side is magnifying the lag on complex scenes we've never committed that change to the repo ever. We've been investigating how to fix the vsync lock problem without reducing the depth instead, but we don't have a solution.

@amirh first brought the pipeline depth up so I think Amir may have the answer.

Where do you get that the depth was restricted to 1?

The code here: https://github.com/flutter/engine/blob/63bdf3e1be12c8bfe26f3c4a63f44f922817c492/shell/common/animator.cc#L37 resulted in a pipeline depth of 1 when platform views are enabled. I overlooked that when enabling platform views for the Gallery app. The next time we enabled platform views with thread merging the pipeline depth would not be special cased.

There's actually no regression. The benchmark today is on par with the benchmark in November 2019 before https://github.com/flutter/flutter/commit/3c65463f890636ce687bbbaf5bcd19dee930cce6.

https://github.com/flutter/flutter/commit/3c65463f890636ce687bbbaf5bcd19dee930cce6 improved the benchmark significantly because it sets the pipeline depth to 1. That's problematic and we don't want that.
So this seemingly severe regression is the manifest of two other issues:

iOS apps on OpenGL can sometimes get blocked while rendering frames (https://github.com/flutter/flutter/issues/51809) and setting pipeline depth to 1 dramatically reduces such blocking time. We'll figure out a better way to reduce that blocking time without setting the pipeline depth to 1.

Our performance dashboard isn't very good at viewing metrics that span across multiple months, so it takes us quite some time to see that we're actually just back to the level 4 months ago. We'll track the improvement of our performance dashboard in https://github.com/flutter/flutter/issues/37434

Closing this issue.


[CSL-10] Fix onNewSlotWhenLeader

@gromak
wait $ for (slotDuration - networkDiameter) is not the best way to find time to create block, because onNewSlotWhenLeader may trigger not at the beginning of the slot (e. g. if we launch application in the middle of slot). Better solution is to add slotBeginning :: MonadSlots m => SlotId -> Timestamp function and replace wait for with wait till.

@gromak
Also Pos.Slotting.onNewSlotDo looks suspicious:

let timeToWait = slotDuration - curTime mod slotDuration

I will change both places soon.


IBFT PoS Unstaking

Description
This PR introduces the unstaking handler for the PoS implementation, while modifying Account state.
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
As stated in the PR #69, the current implementation modifies parts of the codebase that pertain to how Account state is kept and marshaled in the world trie.
Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[x] I have tested this code
[ ] I have updated the README and other relevant documents (guides...)
[x] I have added sufficient documentation both in code, as well as in the READMEs

@lazartravica @Vuksan @Kourin1996
The only difference that exists between this and the ibft-pos-staking branch is in this commit.
There is no need to check other files again, just the linked commit is fine.


Tidy up System Tests #644

Fixes #644, also fixes #642
There are some areas of code in system tests that have minor bugs and
code issues. For e.g. AddressBookSystemTest's header comments is
outdated and TestApp#getModel() is returning the wrong model.

Let's fix these minor issues.

Marking this with critical priority because it involves slight architectural changes that will affect the other PRs concerning system tests.

@yamgent changes requested made :P


Autocomplete: Context management

Insert a mechanism to combine multiple context sources and find a way to rank completions. Make sure to dedupe ranges etc.

@philipp-spiess what do you mean by multiple context sources? Do you have any documentation about this?

@ramsey-coding We want to have multiple retrieval methods that we can use at the same time and need a way to rank the results relative to each other :) There's not more documentation at this point, this is pretty early right now.

@ramsey-coding Sure take a look at this function which is currently the main entry point for autocomplete retrieval https://sourcegraph.com/github.com/sourcegraph/cody/-/blob/vscode/src/completions/context/context.ts?L36

@philipp-spiess does this work need to be collaborated with @rishabhmehrotra?

Going to close this out for some smaller, more specific issues


App Insights debugging: Add code blocks and fix doc issue

Replaces quote blocks with code blocks for code sections and fixes one typo: the enableDebug section should contain .js as the extension (as the documentation states itself), but the code snippet was still using .min.js.

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

#label:"aq-pr-triaged"


etcdserver: use PreVote so majority partition's leader isn't forced to step down

If a cluster is partitioned then connectivity is fixed, the minority partition can trigger a new election that will cause the majority partition's leader to step down and disrupt availability. The fix, as described in 9.6 of the raft disseration, is PreVote.

I have found the implementation in etcd. Do I miss important point?

@shenlanse: it isn't as stable/battle tested as yet, see https://github.com/coreos/etcd/issues/8501, https://github.com/coreos/etcd/issues/8498 and the issues linked therein. We (cockroachdb/cockroach) have run into issues enabling it as it stands today.

@irfansharif Ohh，thanks, I will see it

Will be enabled by default in v3.5. Has been testing pre-vote in functional testing for several months, and seems stable.


adding Crud for Entity Package

adding Crud for Entity Package,  test, migrations, exceptions and mappers

I reviewed the changes made - everything seems very well done. Models are fine, methods work as they should, tests pass, exceptions catch errors correctly. Approved!


Update README.rst

There's a small typo in the first example, replacing self by Test

Thanks @glyg!!

Thanks for the great tool!! Went like a charm on my repo :100:


Better way of porting dependencies

Currently, ones has to setup deps.sh for each experiment if there are dependencies needed for the runtime eg the Hippodrome benchmark. This can be made more optimal by having a single point which defines this for the whole benchmark.

After some experience with this problem, I see that it does not make a lot of sense, when simple copy-pasting is enough


[CONTROLLER/RECORDER] supports org in pubsub

This PR is for:

Server

supports org in pubsub
Checklist

[ ] Added unit test.

Backport to branches

main

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


MAINT: Allow None tolerances in least_squares

Fixes #7632
The tolerance logic was changes as follows:

None is accepted and it is converted to 0.
Tolerances are not bounded by EPS. But a warning is issued when it is less that EPS, unless None was passed (we consider this as a clear intent and don't warn about disabled tolerance check).

@rgommers --- thanks, the test was added.

the test is failing because of RuntimeWarning: invalid value encountered in true_divide

I tried to fix the problem, but I'm not very happy with the solution. There was a good reason to require each tolerance to be higher than EPS. Considering that the tests are strong I think my changes are safe and disabling 1 or 2 tolerances will work as expected.

I tried to fix the problem, but I'm not very happy with the solution. There was a good reason to require each tolerance to be higher than EPS. Considering that the tests are strong I think my changes are safe and disabling 1 or 2 tolerances will work as expected. However, disabling all 3 creates potentially too many pathological situations and I'm quite certain it's best not to allow it.

However, disabling all 3 creates potentially too many pathological situations and I'm quite certain it's best not to allow it.

Yes that makes sense. Optimization completely without any tolerances is a bit too weird.

Almost there, one docstring related failure:
/home/travis/build/scipy/scipy/tools/../doc/source/tutorial/optimize.rst
------------------------------------------------------------------------
File "doc/source/tutorial/optimize.rst", line 797, in /home/travis/build/scipy/scipy/tools/../doc/source/tutorial/optimize.rst
Failed example:
    res = least_squares(fun, x0, jac=jac, bounds=(0, 100), args=(u, y), verbose=1)
Expected:
    `ftol` termination condition is satisfied.
    Function evaluations 130, initial cost 4.4383e+00, final cost 1.5375e-04, first-order optimality 4.92e-08.
Got:
    `ftol` termination condition is satisfied.
    Function evaluations 131, initial cost 4.4383e+00, final cost 1.5375e-04, first-order optimality 4.52e-08.

the PyPy failure is unrelated

The refguide-check failure shows that the verbose=True output is meant for a human user, hence a bit too brittle for the automated checking.
I suggest to just add a # may vary comment to disable that particular check.

okay all happy with the #may vary except for the unrelated PyPy failure, merging. thanks @nmayorov, @ev-br

@rgommers @ev-br thanks for helping to finish this.


启动webui后，点击任何按钮都报超时错误

执行python3 webui.py --port 9886 --model_dir speech_tts/CosyVoice-300M后，在webui上点击任何按钮都会报超时错误，如下图

控制台报错信息如下。该怎么解决啊
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/type_adapter.py", line 210, in init
core_schema = _getattr_no_parents(type, 'pydantic_core_schema')
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/type_adapter.py", line 98, in _getattr_no_parents
raise AttributeError(attribute)
AttributeError: pydantic_core_schema
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/uvicorn/protocols/http/h11_impl.py", line 406, in run_asgi
result = await app(  # type: ignore[func-returns-value]
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in call
return await self.app(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/applications.py", line 1054, in call
await super().call(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/applications.py", line 113, in call
await self.middleware_stack(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/middleware/errors.py", line 187, in call
raise exc
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/middleware/errors.py", line 165, in call
await self.app(scope, receive, _send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/gradio/route_utils.py", line 720, in call
await self.simple_response(scope, receive, send, request_headers=headers)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/gradio/route_utils.py", line 736, in simple_response
await self.app(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 62, in call
await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
raise exc
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
await app(scope, receive, sender)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/routing.py", line 715, in call
await self.middleware_stack(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/routing.py", line 735, in app
await route.handle(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/routing.py", line 288, in handle
await self.app(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/routing.py", line 76, in app
await wrap_app_handling_exceptions(app, request)(scope, receive, send)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
raise exc
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/exception_handler.py", line 51, in wrapped_app
await app(scope, receive, sender)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/starlette/routing.py", line 73, in app
response = await f(request)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/routing.py", line 291, in app
solved_result = await solve_dependencies(
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/dependencies/utils.py", line 639, in solve_dependencies
) = await request_body_to_args(  # body_params checked above
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/dependencies/utils.py", line 813, in request_body_to_args
fields_to_extract = get_model_fields(first_field.type)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/_compat.py", line 283, in get_model_fields
return [
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/_compat.py", line 284, in
ModelField(field_info=field_info, name=name)
File "", line 6, in init
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/fastapi/_compat.py", line 109, in post_init
self._type_adapter: TypeAdapter[Any] = TypeAdapter(
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/type_adapter.py", line 212, in init
core_schema = _get_schema(type, config_wrapper, parent_depth=_parent_depth + 1)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/type_adapter.py", line 81, in get_schema
schema = gen.generate_schema(type)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 499, in generate_schema
schema = self._generate_schema_inner(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 734, in _generate_schema_inner
return self._annotated_schema(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 1749, in _annotated_schema
schema = self._apply_annotations(source_type, annotations)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 1817, in _apply_annotations
schema = get_inner_schema(source_type)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in call
schema = self._handler(source_type)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 1899, in new_handler
schema = metadata_get_schema(source, get_inner_schema)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 1895, in
lambda source, handler: handler(source)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in call
schema = self._handler(source_type)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 1798, in inner_handler
schema = self._generate_schema_inner(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 755, in _generate_schema_inner
return self.match_type(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 837, in match_type
return self._match_generic_type(obj, origin)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 861, in _match_generic_type
return self._union_schema(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 1149, in _union_schema
choices.append(self.generate_schema(arg))
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 499, in generate_schema
schema = self._generate_schema_inner(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 755, in _generate_schema_inner
return self.match_type(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 841, in match_type
return self._unknown_type_schema(obj)
File "/opt/anaconda3/envs/cosyvoice/lib/python3.8/site-packages/pydantic/_internal/_generate_schema.py", line 402, in _unknown_type_schema
raise PydanticSchemaGenerationError(
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'starlette.requests.Request'>. Set arbitrary_types_allowed=True in the model_config to ignore this error or implement __get_pydantic_core_schema__ on your type to fully support it.
If you got this error by calling handler() within __get_pydantic_core_schema__ then you likely need to call handler.generate_schema(<some type>) since we do not call __get_pydantic_core_schema__ on <some type> otherwise to avoid infinite recursion.
For further information visit https://errors.pydantic.dev/2.7/u/schema-for-unknown-type

Same issue, any solutions?

looks like a gradio problem, never seen it

可能是一些依赖包版本问题，可以试试修改成这样:
pydantic==2.8.2
pydantic-core==2.20.1
fastapi==0.112.4
我这改完后就好了。
参考:  https://github.com/oobabooga/text-generation-webui/issues/6367#issuecomment-2333704584

可能是一些依赖包版本问题，可以试试修改成这样: pydantic==2.8.2 pydantic-core==2.20.1 fastapi==0.112.4
我这改完后就好了。
参考: oobabooga/text-generation-webui#6367 (comment)

感谢，把fastapi降级到0.112.4好了


fix: Blurry QR image have made sharpen

Metamask Wallet UI QR image is blurry and some mobile devices can't scan easily. Blurry QR image have made sharpen.

LGTM, thanks!


Populate Tasks on Task Board via Firebase

Link the Task Board view to firebase so that the tasks are populated via Firebase instead of being being written manually in a separate file.

Depends on #180


Error in parameter checking  in cdfbin.f

Reference issue

I don't think there is a related issue yet.
What does this implement/fix?

Fixes an error in the logic of parameter checking for the which parameter in the CDFBIN subroutine.
Additional information

Someone clearly made a typo and when trying to check that the which parameter should not be smaller than 1 and not larger than 4, accidentally put
(.NOT. ((which.LT.1).AND. (which.GT.4)))

which is always true instead of the correct expression
(.NOT. ((which.LT.1).OR. (which.GT.4)))

This is of not too much consequence as long as CDFBIN is called with legal which parameters in {1,2,3,4} but should nevertheless be corrected.

Thanks @tnowotny, good catch. Just checking: you just spotted this as a potential issue right, you did not get incorrect behavior from calling a Python function in the scipy.special API?

Yes, correct. We were looking into the code to compare what scipy does to our own code and I noticed this bug while reading the fortran code.


typerror for max_body

Using dockers, I get below error:

Traceback (most recent call last):
File "./egcurl", line 402, in
sys.exit(main())
File "./egcurl", line 387, in main
config = parse_configuration(host)
File "./egcurl", line 335, in parse_configuration
config["max-body"] = int(config["max-body"])
TypeError: int() argument must be a string or a number, not 'NoneType'

cat ~/.egcurl
[default]
host:xyz.akamaiapis.net
client_token:ak...
access_token:ak...
max-body:2048

The format for ~/.egcurl calls for all the credential bits to be on one really long line. This is really just a badly explained section parsing error. This should be explained better by recent changes in the code.
Also note that I just merged pull request #19 which provides support for ~/.edgerc. This is the INI file format supported by various other Akamai OPEN signing libraries in various languages.
I'm closing because I think this is either outright resolved or at least explained better in more recent versions.


Feature/keyword search snippets

Feature #31

adds convenience methods to local solr query object to provide access to expanded & highlighting results
adds custom templatetag for getting a dict item from a variable key, to simplify templates for expanded results and highlights
adds view logic to query solr for pages with highlighted terms; currently requesting 3 snippets, but we can revisit
basic template display of page images and text snippets
does not include page label included in Zeplin mockup because we don't have access to that in the current import/index

Codecov Report

Merging #43 into develop will increase coverage by 0.01%.
The diff coverage is 98.8%.

@@             Coverage Diff             @@
##           develop      #43      +/-   ##
===========================================
+ Coverage    98.38%   98.39%   +0.01%
===========================================
  Files           36       38       +2
  Lines         1609     1684      +75
===========================================
+ Hits          1583     1657      +74
- Misses          26       27       +1

Impacted Files
Coverage Δ

ppa/archive/tests/test_templatetags.py
100% <100%> (ø)

ppa/archive/tests/test_solr.py
100% <100%> (ø)
:arrow_up:

ppa/archive/templatetags/ppa_tags.py
100% <100%> (ø)

ppa/archive/solr.py
97.34% <100%> (+0.2%)
:arrow_up:

ppa/archive/tests/test_views.py
100% <100%> (ø)
:arrow_up:

ppa/archive/views.py
96.96% <93.75%> (-0.58%)
:arrow_down:

Continue to review full report at Codecov.

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

A couple things occurred to me about this code:

image url is pretty hathi specific; any ideas how to make it easier to generalize later?
I don't think I wrote any tests for the template logic, and probably should before this is complete


clash-nyanpasu: 1.4.5 -> 1.5.1

Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/324928
Switched to AppImage because 'result/bin/clash-nyanpasu' terminated by signal SIGSEGV (Address boundary error) and I had no idea whats happening.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 324968 run on x86_64-linux 1

1 package built:

clash-nyanpasu


QueryCheckerTool creates LLMChain object, does not allow manual specification of openai_api_key

Summary
The QueryCheckerTool function currently creates an LLMChain object internally but does not provide a way to specify the openai_api_key manually via supplied arguments. This can cause issues for users who do not want to place their API key in environment variables.
Steps to Reproduce
Run this code
from langchain.agents import create_sql_agent
from langchain.agents.agent_toolkits import SQLDatabaseToolkit
from langchain.sql_database import SQLDatabase
from langchain.llms.openai import OpenAI
from langchain.agents import AgentExecutor

import sqlite3
with sqlite3.connect("data.db") as conn:
    pass

db = SQLDatabase.from_uri("sqlite:///data.db")
toolkit = SQLDatabaseToolkit(db=db)
llm = OpenAI(temperature=0, openai_api_key="your key here")

agent_executor = create_sql_agent(
    llm=llm,
    toolkit=toolkit,
    verbose=True
)

while True:
    prompt = input("> ")
    response = agent_executor.run(prompt)
    print(response)

Expected Behavior
create_sql_agent should not require me to supply an OpenAI API key, nor should it require me to have this stored in an environment variable.
Actual Behavior
create_sql_agent generates an error when I call it without first setting the OPENAI_API_KEY environment variable.
Obvious Solution
create_sql_agent should supply its argument llm to functions it calls, obviously. In particular, this line https://github.com/hwchase17/langchain/blob/b83e8265102514d1722b2fb1aad29763c5cad62a/langchain/tools/sql_database/tool.py#L85 is the source of the error.
Environment

LangChain version: 0.0.123
Python version: 3.9.16
Operating System: Windows 10

try this way
import os
os.environ['OPENAI_API_KEY'] = "yuor open api key"

and it works for me in your case

I assume that works, thanks. But it makes the use of the kwarg a little silly. Might be worth looking into deprecating the kwarg?


issue in using ng grid in custom directive

ng grid is not displaying the data when I am trying to use in my custom directive. Please find my plunker at http://plnkr.co/edit/Ofa9YhfHQJg92TOjBZQZ?p=preview.

Hi c0bra, I am not clear about the status of this issue (added to this 2.x.next milestone). Is there any mistake I am doing or ng grid can't be used the way I am trying to use?

In general 2.x doesn't have a lot of support, none of the original 2.x team remain as part of the project, the newer members are all more familiar with 3.0.  It probably indicates that we're waiting for someone who knows something about 2.x to provide some advice - and that what you're doing doesn't have a simple answer.  You could consider upgrading to 3.0, which tends to have better support.

I'm closing this since we're not supporting 2.x anymore. Anyone wiiling to take on from here, feel free to fork.


Compatibility with VehicleControl

Since the last FiveM update, FRFfuel needs to be restarted when connected to run, the error is :
fx::TestScriptHost::InvokeNative: execution failed: Error executing native 0x5a039bb0bca604b6 at address 0x1409ccfd2.
Failed to instantiate instance of script FRFuel.FRFuel: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentException: Value does not fall within the expected range.

Cannot reproduce. Are you using latest server version and latest (0.0.9) FRFuel version?

Yes i downloaded the latest version here and I get this :
[     29422] fx::TestScriptHost::InvokeNative: execution failed: Error executing native 0x5a039bb0bca604b6 at address 0x1409ccfd2.
[     29422] Failed to instantiate instance of script FRFuel.FRFuel: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentException: Value does not fall within the expected range.

[     29437]   at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (System.Reflection.MonoCMethod,object,object[],System.Exception&)

[     29437]   at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) [0x00002] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29437]    --- End of inner exception stack trace ---

[     29437]   at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) [0x00014] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29437]   at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic) [0x000a8] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29437]   at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) [0x00009] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29453]   at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) [0x00027] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29453]   at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x00020] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29453]   at System.Activator.CreateInstance (System.Type type) [0x00000] in <a4e3abdd630b4c98a9d6f31a99197de6>:0

[     29453]   at CitizenFX.Core.InternalManager.CreateAssemblyInternal (System.Byte[] assemblyData, System.Byte[] symbolData) [0x00053] in <30ec4c26fbcd44a68adbda4223c19e58>:0 ```

There're some incompatibility issues with https://github.com/pongo1231/VehicleControl


Display neotree and magit toggle overlay buttons

Hello there,
I'm a huge fan of doom-one, and really hope that the light version will come out soon :-) The solaire-mode is awesome and the coloration of the modeline is so beautiful.
Since the theme is inspired by Atom, I've given it a try and if nothing will make me quit emacs, I've liked some features, especially the toggle buttons on the left and the right hand sides of the app, respectively for source tree display (neotree in emacs) and git status (magit in emacs).
This is more a feature request than an issue.
I'm trying to contribute a doom-themes-neotree-handle-config, that will display images whenever the moue cursor is on the current frame's left edge and right edge. Once clicked, they will toggle either neotree or magit-status buffers.
I can easily get pixel coordinates for a window, but I do not find how to map these to frame coordinates. Here's what I've got so far, inspired by follow-mouse.el.
;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; UI functions
;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

(defvar prolusion--doom-themes-track-mouse nil)

(defun prolusion//doom-themes-neotree-handle-callback (event)
  ""
  (interactive "e")
  (let ((p_x_w (car (posn-x-y (event-start event)))))
    (if (and (< p_x_w 10)) ;; (not (get-buffer " *NeoTree*")))
        (neotree-toggle)))
  (setq unread-command-events (nconc unread-command-events (list event))))

(defun prolusion/doom-themes-neotree-handle-config ()
  ""
  (interactive)
  (cond ((setq prolusion--doom-themes-track-mouse (not prolusion--doom-themes-track-mouse))
         (put 'prolusion--doom-themes-track-mouse 'track-mouse track-mouse)
         (setq track-mouse t)
         (put 'prolusion--doom-themes-track-mouse 'mouse-movement
              (lookup-key special-event-map [mouse-movement]))
         (define-key special-event-map [mouse-movement]
           'prolusion//doom-themes-neotree-handle-callback))
        (t
         (setq track-mouse (get 'prolusion--doom-themes-track-mouse 'track-mouse))
         (define-key special-event-map [mouse-movement]
           (get 'prolusion--doom-themes-track-mouse 'mouse-movement))))
  (message "Prolusion doom themes mouse tracking is %s"
           (if prolusion--doom-themes-track-mouse "enabled" "disabled"))
  prolusion--doom-themes-track-mouse)

So in order to keep going, I have two questions:

how do I map window pixel coordinates to the frame ones ?
how do I display an image overlay (not in the sense of emacs' overlays) but really on top of everything ?

Many thanks !

That would be cool!
Perhaps frame-position or frame-edges could help? The former returns the pixel coordinates of the top-left of the current frame. The latter will give you (LEFT TOP RIGHT BOTTOM) in pixels.
As for displaying an image overlay at an arbitrary position, that's a tough one. You could go the hacky route and seek out the foremost top left and right windows and draw image buttons in the corners.
Or maybe x-show-tip will work (only available on linux distros running x server):
(defvar my-overlay-keymap (make-sparse-keymap))
(define-key my-overlay-keymap [down-mouse-1] #'neotree-toggle)

(x-show-tip (propertize " " 'display (create-image "button-image.png")
                        'keymap my-overlay-keymap)
            (selected-frame)
            `((left . ,(car (frame-position)))
              (top  . ,(cdr (frame-position))))
            tooltip-hide-delay
            tooltip-x-offset
            tooltip-y-offset)

I've had some success with this, but I can't get the tooltip to stay open. Perhaps you'll have better luck.
Other than that, you could exploit dynamic modules in Emacs 25.1+. i.e. write an overlay api in C/C++ that interfaces with the window system (e.g. GTK), compile it to a shared library (e.g. my-overlay.so), and load it into Emacs: (load "my-overlay.so"). Perhaps this blog post talking about using dynamic modules may help?
Unfortunately, that's all I can think of.

Many thanks @hlissner for the prompt answer !
That makes already some elements for investigation. However:

if I use linux based systems on a daily basis, my main machines are Macs, so the Xorg API is not an option
rather than using bitmap images, I'd like to build an SVG image from elisp (thus handling retina support), but the API is so poor, I does not even provides quadrics or cubics
I'm much more proficient in C/C++ but I was not aware of dynamic loading by emacs, that is good news ! The drawback is if I follow this path, I'll have to setup CI machines and provides yet another patch to e.g. homebrew emacs-plus formulae, but what about other platforms ?

I'll let you know !


output bed header

Hi @kleinertp,
Thanks a lot for developing CADD-SV.
While I was checking the output bed file for CADD-scores, I noticed the number of the header fields (136) did not match the number of the data fields (137).
"raw-score-combined" is present in scoring.R but missing in the annotations/header_final.txt
I checked the column annotations in v1.0 and v1.1 (https://kircherlab.bihealth.org/download/CADD-SV/) and 'raw-score-combined' was not present in either version.
Just want to double check if it's intentional to leave out "raw-score-combine" in the header?
Thanks!

Hi Zi-Hua Fang,
Thanks for pointing this out. This is not intentional.
I will update the header annotations,
Thank you!


fix: update devpreview to beta

Change alpha to beta that will happen in the next release (with announcement)

FYI - documentation will change - we move to beta as the other services/api states


add tsm model and unitest

Codecov Report

Merging #1138 (b8da6f1) into main (81fee2a) will decrease coverage by 12.04%.
The diff coverage is 25.70%.

@@             Coverage Diff             @@
##             main    #1138       +/-   ##
===========================================
- Coverage   70.10%   58.06%   -12.05%
===========================================
  Files         213      232       +19
  Lines        9407    11209     +1802
  Branches     1552     1818      +266
===========================================
- Hits         6595     6508       -87
- Misses       2362     4237     +1875
- Partials      450      464       +14

Impacted Files
Coverage Δ

towhee/models/tsm/bn_inception.py
6.25% <6.25%> (ø)

towhee/models/tsm/mobilenet_v2.py
21.42% <21.42%> (ø)

towhee/models/tsm/tsm.py
33.50% <33.50%> (ø)

towhee/models/tsm/temporal_shift.py
50.45% <50.45%> (ø)

towhee/models/tsm/non_local.py
75.60% <75.60%> (ø)

towhee/models/tsm/basic_ops.py
80.00% <80.00%> (ø)

towhee/engine/operator_pool.py
36.84% <0.00%> (-63.16%)
:arrow_down:

towhee/hub/operator_manager.py
20.73% <0.00%> (-60.52%)
:arrow_down:

towhee/engine/operator_runner/generator_runner.py
31.81% <0.00%> (-59.10%)
:arrow_down:

towhee/engine/operator_runner/window_runner.py
37.50% <0.00%> (-54.17%)
:arrow_down:

... and 98 more

Continue to review full report at Codecov.

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

@gexy185 Please combine all commits into one.


Release proposal: standard v6

The goal of this release is to make standard faster to install and faster to run.

[x] Remove standard-format (#340 #397)

Eliminates 250 packages, cuts install time in half w/ npm2 (20sec -> 10sec)

[x] Improve test suite to test rule changes against every package on npm

For sanity, limiting to packages with at least 4 dependents. Around ~400 packages.

[x] Lock to specific version of eslint

In the past, the eslint version was decided by the standard-engine dependency

[x] Upgrade eslint to v2 (stable release is imminent)

There may be slight behavior changes to existing rules that cause breakage. Let's bundle them into this major release.

[ ] Enable new rules:

[ ] "keyword-spacing": 2
[ ] "no-empty-pattern": 2
[ ] "no-path-concat": 2
[ ] "no-new-require": 2

\o/

:sparkles:

Merged the v6 branch into master, so merging PRs for v6 is easier.

Going to try to get a beta release out on npm tomorrow.

standard 6.0.0 is released!
Changelog here: https://github.com/feross/standard/blob/master/CHANGELOG.md#600---2016-02-05

Standard is by far one of my favorite projects and I think it has really helped to improve the code quality in the JavaScript ecosystem. @feross I thank you for all of your hard work put into it.
With that being said, I'm concerned that enabling standard to be configurable https://github.com/feross/standard/blob/master/CHANGELOG.md#expose-eslint-configuration-via-command-line-options-and-packagejson was a mistake. See https://github.com/feross/standard#can-you-make-rule-x-configurable:

No. The point of standard is to save you time by picking reasonable rules so you can spend your time solving actual problems. If you really do want to configure hundreds of eslint rules individually, you can always use eslint directly.

If you just want to tweak a couple rules, consider using this shareable config and layering your changes on top.

Pro tip: Just use standard and move on. There are actual real problems that you could spend your time solving! :P

I understand that we as developers need to evolve projects, take risks, listen to feedback, and iterate. However, this change feels antithetical to what standard was stood for and what made it great. It seems entirely possible that I'm misunderstanding these changes or the importance of these changes and what they entail. My fear now is that I'll open up a package.json and see standard with a bunch of different config options which brings it all back to everyone's custom eslint configuration. Before, I could open up a project's package.json and if I saw standard, I knew what to expect and that's part of what made standard great.
@feross I respect and understand that standard is your project. I just wish maybe you would have sought a bit more feedback on that change (perhaps I missed it?).
I will definitely upgrade to Standard v6, continue to use and promote Standard, I just wanted to share this perspective.
Thanks again for your hard work on this!

Crap, I fully missed this - I was moving cities the last couple of days and somewhere this slipped. I agree with @jprichardson, I feel like this can be, and thus will be abused fully
{
  "standard": {
    "rules": {
      "semi": [2, "always"]
    }
  }
}

If someone does the above, then saying that a project uses standard becomes meaningless - I feel this is different from having react / jsx / mocha support as external packages. If configuring those is painful, they should be resolved in their respective packages. Perhaps config should only be accepted for the rules they touch - the default standard shouldn't be messed with I reckon, if you want to do that it should be done from a new package.
I kind of like being grumpy old farts that curate the one way to do things and if you don't like it configure your own. This doesn't feel right to me.

agree with last two comments. leave it up to other modules to add
configuration
On Saturday, February 6, 2016, Yoshua Wuyts<EMAIL_ADDRESS>wrote:

Crap, I fully missed this - I was moving cities the last couple of days
and somewhere this slipped. I agree with @jprichardson
https://github.com/jprichardson, I feel like this can be, and thus will
be abused fully
{
"standard": {
"rules": {
"semi": [2, "always"]
}
}
}
If someone does the above, then saying that a project uses standard
becomes meaningless - I feel this is different from having react / jsx /
mocha support as external packages. If configuring those is painful, they
should be resolved in their respective packages. Perhaps config should only
be accepted for the rules they touch - the default standard shouldn't be
messed with I reckon, if you want to do that it should be done from a new
package.
I kind of like being grumpy old farts that curate the one way to do
things and if you don't like it configure your own. This doesn't feel
right to me.
—
Reply to this email directly or view it on GitHub
https://github.com/feross/standard/issues/399#issuecomment-180766452.

--
Sent from my phone

Thanks for the feedback guys. Better late than never, I suppose.
This whole thing got me thinking about why people use and like standard in the first place. I think there are two main reasons like it:

Eliminates need to add .eslintrc files and keep them in sync across all projects
Tells you what to think, eliminates bikeshedding

I originally made standard solely for reason 1, to enforce style on the various WebTorrent repos. But I think most people use it for reason 2.
Adding a way for the super-obsessed to set an eslint plugin for whatever flavor-of-the-week JS thing they're using doesn't really affect my use case (reason 1). But it definitely affects reason 2, and makes "this project uses standard" mean way less. And that's not cool.
I think ya'll are right. I done flubbed it up.
There were issues about this in https://github.com/feross/standard/issues/386, https://github.com/feross/standard/issues/367, and https://github.com/feross/standard/issues/371, for plugins, rules, and env configs, respectively. Wish we could have bikeshed this before I released v6! Oh well.
So, just to recap.
The reason I added rules was so folks like @rstacruz and @HenrikJoreteg could have an easier time using React alternatives like deku and virtual-dom. But, now that the React rules are removed in v6, there is no need to globally disable specific rules. Let's remove this in v7.
The reason for adding plugins was so that folks wouldn't need to create/use a standard fork just so they can pass a simple option like { plugins: ["flowtype"] } into eslint. And we already allow passing through the { parser: "babel-eslint" } option to eslint, and this seemed along the same lines as that.
For env, I figured that folks writing code for an environment like mongo or mocha, where there are assumed global variables could turn this on. It doesn't change any rules – just makes some errors about using an undefined variable go away. But honestly, making mocha users explicitly add /* eslint-env mocha */ is fine, and it's good documentation anyway since they're not writing require('mocha').
So, I'm :+1: to doing a quick v7 release to remove rules and env. Any thoughts on keeping/removing plugins?

Could folks please chime in with feedback on the standard v7 release proposal: https://github.com/feross/standard/issues/404

IMHO a release that removes rules would be a patch.  Not a new 7.0.0.
This is the sole reason I use standard,  no configuration.  I know what to expect.

:stuck_out_tongue_winking_eye:

+1 for keeping plugins! :grin:

sounds cool.
if anyone disagrees, they're always free to drop down to eslint + eslint-config-standard.

if anyone disagrees, they're always free to drop down to eslint + eslint-config-standard.

At which point,  the intention is clear as day and their not using standard, but their own concoction anyway.

I just want to chime in this quickly as I've recently switched our project to Standard. I believe Standard is great if you are starting a project from scratch. But moving an existing codebase to it, it gets daunting as you will instantly get thousands of errors from the get go. Nobody wants to spend their days/weeks fixing lint errors (and nobody wants to fix these errors blindly either).
This is where rules/globals/env really help as it helped me move from one class of errors to another one and making small wins in the process. Also, some of Standard's defaults are debatable within a team setting (e.g. semi and indentation level) and something that probably would slow a team down if introduced straightaway without some discussion. Again this is where 'rules' help as I can introduce these features slowly over time to the team without any friction or useless debates about style.
I hope that sheds some light on some of the use-cases of rules, at least. globals - not everyone uses a module bundler and not all projects are in the npm registry, so globals help there.
Cheers.

I'm with @rstacruz on this keep standard strict. You can always customize with eslint + eslint-config-standard if you want a non-standard, standard (see how silly that sounds :stuck_out_tongue_winking_eye:).
Anyway, all the good feels: https://twitter.com/HenrikJoreteg/status/697294740480352256


Fix Potential Double Delete Bug

This fixes a double free bug that periodically causes the stream manager to crash if other stream managers or are killed at the right time.
In this case opkt has the potential to be freed twice in the event of a failed packet sent in both InternalSendResponse and conn->sendPacket(opkt)

We can merge it
Sent from my iPhone

On May 17, 2018, at 7:54 AM, Andrew Jorgensen<EMAIL_ADDRESS>wrote:
It's an improvement I think since there is a potential for a double free bug here if packets fail to send but I haven't seen a crash in production related to this yet
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@nlu90 fixed. Is there a bazel command just run checkstyle?

@ajorgensen - here it is
bazel build --config=darwin

@kramasamy  Oh interesting... the checkstyles never run for me during a normal build. For example if I introduce the same checkstyle issue and run
 bazel build //heron/common/src/cpp/..
It builds successfully. Its not until I run the scripts/packages directive that the checkstyle actually fires.

@nwangtw It's been a while, but is this still something that should be merged in?


Add checkpoint_format to unify all current/future saved weight formats

Core reason for PR:
Unify the concept of model weight format since repo already have coding for 3 weight formats: gptq, marlin, and awq_gemm with 4th pending in #559. Without this PR, existing properties of different weight formats are fragmented and not forward compatible with new formats such as pending #559 which will require another property field. Have one single format field to unify them all.
Changes:

MAJOR format unifies is_marlin_format,  awq_qemm, and pending gptq_v2 format in pr #559
format defaults to gptq
MAJOR gptq_method remapped to method
MAJOR compat: pinned transformers to < 4.39.0 due to #604
fix _validate_marlin_device_support() returns false for ada/hopper
fix  json arg normalization comparisons did not use lowercased keys and string values
block awq gemm from participating in quantization: inference only
added compat for some hf models using quant_method=marlin for marlin models using other gptq quantizers
load quant method into  BaseQuantizeConfig. Previously this was ignored, not read from json.
auto set use_marlin to True when model weight format is marlin.
renamed marlin cache file from  autogptq_model.safetensors to more explicit  autogptq_model_marlin.safetensors

Reason for the naming changes. format means checkpoint format and method means quant method but as both properties are specific to BaseQuantizeConfig, there is no need to append quant to method and similarly format is clear and non-conflicting.
Backward Compatibility

autogptq loading pre-pr quantized models marlin/non-marlin have been tested
third party using new quantized models will need compat update: i.e. vllm/sglang.

This is breaking change for downstream users of models quantized by autogptq that do not use the autogptq inference engine.  To mitigate impact, I will parallel pr compat changes to vllm/sglang repos once this is ready to merge.
TEST Results:
[PASS] Pre-PR: Both marlin and non-marlin load
[PASS] PR: Both marlin and non-marlin load
[PASS] test_quantizataion.py
[PASS] test_serialization.py
[PASS] test_q4.py
[PASS] test_shared_loading.py
[PASS] test_awq_compatibility_generation.py
Failed tests but these tests also failed on main:
[FAIL] test_triton.py
[FAIL] test_peft.py
[FAIL] test_repacking.py

@fxmarty @PanQiWei  On second review of the PR something did not pass the smell test: awq_gemm. Why is awq_gemm quantization in autogptq? Aren't they different quant methods?
I need clarification on this as I am unsure relevant awq code should be removed entirely.
In this PR:

quantize using format=awq_gemm on Yi 9B works
loading the quantized format=awq_gemm using autogptq fails:

 INFO - The layer lm_head is not quantized.
INFO - Loading an AWQ model. This requires repacking the weights, and no repacking cached weight was found. Grab a coffee!
  0%|                                              | 0/224 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/root/python/quantx/gptq_test.py", line 15, in <module>
    model_q = AutoGPTQForCausalLM.from_quantized(model_path, device="cuda:0", use_safetensors=True)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/AutoGPTQ/auto_gptq/modeling/auto.py", line 140, in from_quantized
    return quant_func(
           ^^^^^^^^^^^
  File "/root/AutoGPTQ/auto_gptq/modeling/_base.py", line 1185, in from_quantized
    unpacked_qweight, unpacked_qzeros = unpack_awq(
                                        ^^^^^^^^^^^
  File "/root/AutoGPTQ/auto_gptq/modeling/_utils.py", line 594, in unpack_awq
    qdq_weight_T = weight * scale_mat - scale_zeros_mat.half()
                   ~~~~~~~^~~~~~~~~~~
RuntimeError: The size of tensor a (32768) must match the size of tensor b (4096) at non-singleton dimension 1

@fxmarty  based on https://github.com/AutoGPTQ/AutoGPTQ/pull/484 You added awq_gemm load/inference code which are compatible with the autogptq kernels. My question is:

Packing of awq_gemm is supported so quantize to format=awq_gemm is fully supported? My previous message shows quantize success but load failed. Unsure if failure is due to packing or loading.

Based on feedback I may need to refractor code as it appears autogptq supports two quant methods "gptq" and "awq" and I need to move "gemm" away from gptq method.

@casper-hansen  Pulling you into the conversation since I am also prepping code to the create same unifying quant method/format PR into autoawq as well, once everything is agreed upon. It will be good if the two major autoquant repos share a compatible quant method/format language spec. This is really helpful downstream when vllm/sglang repos load quants and need to map quant to framework on json load.
Let's all agree on the naming. Currently my proposal in this PR replaces/unifies:
AutoGPTQ:

quant_method => method
is_marlin_format => format
awq_gemm_checkpoint => format

AutoAWQ:

quant_method => method (no self-identifying in json)
version => format

This will help vllm/sglang cleanup qunat loading code moving forward.

@Qubitium I would prefer we call it version rather than format since that’s already implemented in AutoAWQ. That means no breaking change is required, which we just went through in 0.2.0. This is also something that would have to be phased out over months of time with plenty of warnings, if it were to be considered.
Other than that, I don’t see a reason to rename quant_method to method since that would be another breaking change.

@casper-hansen  Fair. I see how this is more painful to autoawq since the need does not exceed the breaking compat benefits.
I see this is almost necessary for autogptq going forward though since keeping adding properties is not the answer and since this is a breaking change, might as well cram two breaking changes into one migration step.
@fxmarty  since format and quant_method are two breaking changes  merged into one, the impact is still one breaking change. I can parallel pr to all the major downsteam inference engines such as vllm/sglang, etc. to mitigate the impact.
While I am breaking things, might as well think about adding more things that will make quality of life easier for downstream users.
How about a tooling version into quant_config? such as quant_config.producer == "autogptq:0.0.31" as example. This would help with debugging future quants. Everyone quants but most of time we don't even know which tool/version they used.

@fxmarty Ready for re-review but not merge since test is passing due to failing tests as result of #610. It passed before I rebased to main. Once that issue is fixed I will rebase and re-test.
Changes since review:

quant_method name retained.
checkpoint_format name used.
fixed quantize_config pass as dict (weak) to from_quantized(): internal code path is now full strongly typed BaseQuantizeConfig
checkpoint_format hint arg added to from_quantized(): will error if same arg is passed in from both json and from_quantized()
marlin_utils type hint of BaseQuantizeConfig added so var cfg abbrev is clear
separatation of marlin_compatible and marlin_optimized in cuda device marlin detection: log.info if used but not optimized(*) (hopper)
BaseQuantizeConfig and quant data types/values are moved from /modeling/_base.py to quantization/config.py
test_quantization modified so it will test for both weak dict passing of quantize_config and is_marlin_format compat

The remaining issue not fixed from review is diff in intepretation of dasl/marlin note of hopper not optimized. My interpretation is that hopper is suboptimal for marlin in relation to hopper's full capability and not in relation to ada/ampere: it will be just as fast as ada/ampere and but may not be as fast as what hopper is capable of. Hopper has everything Ampere/Ada has with even more sm cores/cache so I don't see how it can be slow. Unfortuantely I have don't have Hopper to test. Can you test this with hf resources?
https://github.com/IST-DASLab/marlin?tab=readme-ov-file#requirements
NVIDIA GPU with compute capability >= 8.0 (Ampere or Ada, Marlin is not yet optimized for Hopper)

@fxmarty  rebased to main and now all relevant tests are passing (minus the broken ones that never passed even on main)

[WIP] Not ready for merge/rev-review. AWQ cache tests is failing.
Changes since last review:

MAJOR quant cache file moved from static to dynamic: based on quant_method + checkpoint_format. cache file generation moved to BaseQuantizeConfig.get_cache_file(). Now marlin and awq cache codes are unified.
updated requested error/warning strings and GEMM  => AWQ_GEMM var name

After testing, this PR also fixed a bug on tip/main where cache file collision happened between marlin/awq code paths. If I set use_marlin=True to True and then switch to awq_gemm_checkpoint=True,  the awq code path (and marlin vice versa) would think it has a good cache and load fail. So it is very important the cache files names are pinned to quant_method and checkpoint_format.
As note before, there is still a hidden bug in the cache system where if user manually update the weights, the cache files are not invalidated. Personally, I think the caching should be done outside the scope of autogptq as cache management  is cumbersome and prone to state errors as mentioned.


Add extra font sizes for interface list and tooltips

I found the font size options for the inventory/bank item list to be either way too small or just a little too big when playing on my TV, so I went ahead and made an extra option for a size between the setting being on or off.
What I've done is I've changed the setting under BetterUI (General Interface) -> "Use bigger font size in the UI item lists" (aka the biggerSkin setting) to a dropdown list. The options are now Default, Bigger, and Biggest.

Default is what used to be the default option, which was when biggerSkin was set to false.
Biggest is what used to be the option when biggerSkin was set to true.
Bigger is between Biggest and Default and is a 6pt font reduction across the board compared to Biggest. I've also adjusted the icons for the font change in the list.

I've tested it for the inventory and banking lists, switched settings, etc. and it works great.

Oh, one thing I forgot/wasn't sure how to do is add a check to convert any existing biggerSkin saved variable from the true/false boolean to their corresponding Default/Biggest setting.
Currently it works just fine if you load it with existing saved data, but if it was set to true it'll revert to the default setting. A user will just need to go back into the settings and choose either Big or Biggest to change their UI to the increase version again.

I added tooltip size options as well. Now there's three options for tooltip sizes plus the "default" size, which is the largest of them all.
I also changed biggerSkin to just skinSize and changed the sizes to Default, Medium, Large, with Default being the smallest.
The default option for both settings are exactly the same as what the default originally was before this pull request.

The UI lists font sizes I feel are at a good place at this point. The tooltips font sizes probably need a bit of tweaking to get that "perfect" look, but there's no visual bugs or glitches with the text that I've found so it's good to go.
Also, since the settings variables were changed from a boolean to an array/list, anyone who would download this update would revert back to the default list and tooltip sizes. It can be fixed by just going back to the addon settings and selecting whatever you want from the dropdown list, but it's worth noting.
There might be a way to convert their existing saved variables to the drop down list variables, but I haven't dug into it.

Made a minor change but everything looks good. Thanks for the contribution, these features will go out in the next release.


Describe technique for providing Scala 2 and Scala 3 macros in the same artifact

Describe the technique in the metaprogramming guide.

Also compare with duplicated source technique


Write output without cog source

Is it possible to write the generator code without the cog python source code embedded in it.
I don't think it would be too hard to parse the output myself and remove all cog statements however I'd prefer to use the libraries functionality if I can.

My first thought is, why use cog if you only want the generated output? That sounds like a Python program with print statements.  Can you say more about why it would be useful?

Thanks for the quick reply Ned.
Reasons
I want to have the cog source in 1 repo which will be shared across projects.
Each project will generate a different file based off of a config file which will be stored in each projects repo.
I don't want the generated code in the shared repo because it is different per project.
I don't want the cog source in the project repo because then it is duplicated & other smaller reasons.
What Cog gives me
With Cog I can write a template .cpp/.h file.
It is clear what remains constant and what changes.     <--- The main reason
I get some wee bonuses like Output line suffixes if I want.
Without Cog I could replace each cog.outl call with a print or write to file command. I would also have to call print/write for all the constant bits of code.
After writing this I'm beginging to wonder if Cog isn't the right tool for me.

I think i'm going to use jinja instead.


Allow editing of ProDOS DIR aux type

Apparently ProLine used the aux type field on subdirectories to hold extended file permissions.
Right now, ProDOS_FileEntry ignores attempts to update the aux type for directories.  I don't remember there being a reason for this other than that it's a bit weird to do it.  The CLI app will try to update it, the GUI disables the edit field.
We don't normally display the DIR aux type.  The CLI displays the aux type in "wide" catalog listings and in set-attr output, and it's visible in the GUI edit-attributes dialog.  I'm not sure we need more than that.

Available in v1.0.1.


Training issue.

 Could you tell me how to fix this bug?
Here is the output.
"distributed_backend=nccl
All distributed processes registered. Starting with 2 processes
micl-libyws6:2583202:2583202 [2] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0> [1]enxb03af2b6059f:<IP_ADDRESS><0>
micl-libyws6:2583202:2583202 [2] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so), using internal implementation
micl-libyws6:2583202:2583202 [2] misc/ibvwrap.cc:63 NCCL WARN Failed to open libibverbs.so[.1]
micl-libyws6:2583202:2583202 [2] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0> [1]enxb03af2b6059f:<IP_ADDRESS><0>
micl-libyws6:2583202:2583202 [2] NCCL INFO Using network Socket
NCCL version 2.7.8+cuda10.2
micl-libyws6:2583381:2583381 [3] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0> [1]enxb03af2b6059f:<IP_ADDRESS><0>
micl-libyws6:2583381:2583381 [3] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so), using internal implementation
micl-libyws6:2583381:2583381 [3] misc/ibvwrap.cc:63 NCCL WARN Failed to open libibverbs.so[.1]
micl-libyws6:2583381:2583381 [3] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0> [1]enxb03af2b6059f:<IP_ADDRESS><0>
micl-libyws6:2583381:2583381 [3] NCCL INFO Using network Socket
micl-libyws6:2583202:2587764 [2] NCCL INFO Channel 00/02 :    0   1
micl-libyws6:2583381:2587765 [3] NCCL INFO threadThresholds 8/8/64 | 16/8/64 | 8/8/64
micl-libyws6:2583202:2587764 [2] NCCL INFO Channel 01/02 :    0   1
micl-libyws6:2583381:2587765 [3] NCCL INFO Trees [0] -1/-1/-1->1->0|0->1->-1/-1/-1 [1] -1/-1/-1->1->0|0->1->-1/-1/-1
micl-libyws6:2583202:2587764 [2] NCCL INFO threadThresholds 8/8/64 | 16/8/64 | 8/8/64
micl-libyws6:2583202:2587764 [2] NCCL INFO Trees [0] 1/-1/-1->0->-1|-1->0->1/-1/-1 [1] 1/-1/-1->0->-1|-1->0->1/-1/-1
micl-libyws6:2583381:2587765 [3] NCCL INFO Channel 00 : 1[43000] -> 0[41000] via P2P/IPC
micl-libyws6:2583202:2587764 [2] NCCL INFO Channel 00 : 0[41000] -> 1[43000] via P2P/IPC
micl-libyws6:2583381:2587765 [3] NCCL INFO Channel 01 : 1[43000] -> 0[41000] via P2P/IPC
micl-libyws6:2583202:2587764 [2] NCCL INFO Channel 01 : 0[41000] -> 1[43000] via P2P/IPC
micl-libyws6:2583381:2587765 [3] NCCL INFO 2 coll channels, 2 p2p channels, 2 p2p channels per peer
micl-libyws6:2583381:2587765 [3] NCCL INFO comm 0x7f96640010d0 rank 1 nranks 2 cudaDev 3 busId 43000 - Init COMPLETE
micl-libyws6:2583202:2587764 [2] NCCL INFO 2 coll channels, 2 p2p channels, 2 p2p channels per peer
micl-libyws6:2583202:2587764 [2] NCCL INFO comm 0x7fe9a00010d0 rank 0 nranks 2 cudaDev 2 busId 41000 - Init COMPLETE
micl-libyws6:2583202:2583202 [2] NCCL INFO Launch mode Parallel
micl-libyws6:2583381:2583381 [3] enqueue.cc:215 NCCL WARN Cuda failure 'invalid device function'
micl-libyws6:2583381:2583381 [3] NCCL INFO group.cc:282 -> 1
micl-libyws6:2583202:2583202 [2] enqueue.cc:215 NCCL WARN Cuda failure 'invalid device function'
micl-libyws6:2583202:2583202 [2] NCCL INFO group.cc:282 -> 1
Error executing job with overrides: []
Traceback (most recent call last):
File "/home/houyi/projects/ARLDM/main.py", line 489, in
main()
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/main.py", line 94, in decorated_main
_run_hydra(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
_run_app(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 457, in _run_app
run_and_report(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
raise ex
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
return func()
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 458, in
lambda: hydra.run(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/hydra.py", line 132, in run
_ = ret.return_value
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/core/utils.py", line 260, in return_value
raise self._return_value
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/core/utils.py", line 186, in run_job
ret.return_value = task_function(task_cfg)
File "/home/houyi/projects/ARLDM/main.py", line 482, in main
train(args)
File "/home/houyi/projects/ARLDM/main.py", line 437, in train
trainer.fit(model, dataloader, ckpt_path=args.train_model_file)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 770, in fit
self._call_and_handle_interrupt(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 723, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 811, in _fit_impl
results = self._run(model, ckpt_path=self.ckpt_path)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1172, in _run
self.__setup_profiler()
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1797, in __setup_profiler
self.profiler.setup(stage=self.state.fn._setup_fn, local_rank=local_rank, log_dir=self.log_dir)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 2249, in log_dir
dirpath = self.strategy.broadcast(dirpath)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/strategies/ddp.py", line 319, in broadcast
torch.distributed.broadcast_object_list(obj, src, group=_group.WORLD)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 1681, in broadcast_object_list
broadcast(object_sizes_tensor, src=src, group=group)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 1039, in broadcast
Error executing job with overrides: []
Traceback (most recent call last):
File "main.py", line 489, in
work = default_pg.broadcast([tensor], opts)
RuntimeError: NCCL error in: /opt/conda/conda-bld/pytorch_1627336343171/work/torch/lib/c10d/ProcessGroupNCCL.cpp:33, unhandled cuda error, NCCL version 2.7.8
ncclUnhandledCudaError: Call to CUDA function failed.
main()
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/main.py", line 94, in decorated_main
_run_hydra(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
_run_app(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 457, in _run_app
run_and_report(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
raise ex
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
return func()
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/utils.py", line 458, in
lambda: hydra.run(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/_internal/hydra.py", line 132, in run
_ = ret.return_value
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/core/utils.py", line 260, in return_value
raise self._return_value
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/hydra/core/utils.py", line 186, in run_job
ret.return_value = task_function(task_cfg)
File "main.py", line 482, in main
train(args)
File "main.py", line 437, in train
trainer.fit(model, dataloader, ckpt_path=args.train_model_file)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 770, in fit
self._call_and_handle_interrupt(
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 721, in _call_and_handle_interrupt
return self.strategy.launcher.launch(trainer_fn, *args, trainer=self, **kwargs)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/strategies/launchers/subprocess_script.py", line 93, in launch
return function(*args, **kwargs)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 811, in _fit_impl
results = self._run(model, ckpt_path=self.ckpt_path)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1172, in _run
self.__setup_profiler()
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1797, in __setup_profiler
self.profiler.setup(stage=self.state.fn._setup_fn, local_rank=local_rank, log_dir=self.log_dir)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 2249, in log_dir
dirpath = self.strategy.broadcast(dirpath)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/pytorch_lightning/strategies/ddp.py", line 319, in broadcast
torch.distributed.broadcast_object_list(obj, src, group=_group.WORLD)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 1681, in broadcast_object_list
broadcast(object_sizes_tensor, src=src, group=group)
File "/home/houyi/anaconda3/envs/arldm2/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 1039, in broadcast
work = default_pg.broadcast([tensor], opts)
RuntimeError: NCCL error in: /opt/conda/conda-bld/pytorch_1627336343171/work/torch/lib/c10d/ProcessGroupNCCL.cpp:33, unhandled cuda error, NCCL version 2.7.8
ncclUnhandledCudaError: Call to CUDA function failed."

Hi @skywalker00001 , it seems to be a cuda error, it this issue similar to yours? https://github.com/Lightning-AI/lightning/discussions/12219

您好，我是侯翼，您的邮件已收到，祝您生活愉快~

Hi @skywalker00001 , it seems to be a cuda error, it this issue similar to yours? Lightning-AI/lightning#12219

Yeah, thank you. I changed my environment to my previously conda env and it succeed. I think maybe my GPU A6000 and the CUDA version are not compatible.


Disallow to install NuGet packages on FW 4.0

See https://github.com/NuGet/Home/issues/6268#issuecomment-353682834.
Currently all NuGet packages can be installed on applications targeting FW 4.0. Need to disallow this to avoid customer's confusion

@SergeyKanzhelev the 2.5.0 release restricts the packages to Net 4.5 or greater.
I tested this in a Net 40 project and Visual Studio allows the "install" of the logging packages.
These packages get added to the packages.config but are never referenced by the project.
I think we have effectively blocked the install, but the experience could still be misleading to a customer.
Do you have any further guidance or can we mark this as resolved?

Nuget team said it's because of content files (xdt transformations) placement. See the discussion in the link above. So experiment is required to move content files into the proper place and file an issue if this doesn't work. Ultimately it's on NuGet team to tell what's the right way for us to effectively block net 40 deployment


add french translation

Changes

add french translation
novy400 test site

add translating.md ==>  process to add a new language translating

? contributing.md ? to remove contributors list  ?

Checklist

[X] have tested my change
[ ] updated relevant documentation
[ ] Remove any/all console.logs I added
[ ] eslint is not complaining

Cool I'm going to finish the french translating today.
@worksofliam  Do you have any idea for contributing.md and translating.md ?

@novy400 your translating.md file is excellent. Yes, keep going with your PR and we can merge when you are ready.

I think it's ok now ! for the french translation..

Hello I've added the line in the side bar and also the structure.md file.


Does codepush can get along with Detox?

Description
I got no fact base for this claim - but its seems that Im reducing the flakiness factor in my tests if I disable codepush.
Also stumble into this StackOverflow Answer.
Is it a known issue?
What is your recommendation regarding using codepush with Detox?
Your environment
Detox version: 19.10.0
React Native version: 0.66.4
Node version: 14.19.1
Device model: Iphone 13
OS:
Test-runner (select one): jest-circus / jest+jasmine / mocha / other

Not aware of this problem TBH

Thanks @d4vidi for responding - one more thing to consider:
When an app has a codepush version to download then there will be this extra blink and restart that caused during the replacement of the bundle - do you think it might disrupt and fail a detox test?

I think it might disrupt Detox, because it assumes the bundle loading takes place inherently during app launch. Nevertheless, that doesn't mean that Detox cannot fundamentally work with codepush; It sounds like the blindspots are mainly around the use cases where a new bundle is loaded.

Right exactly - this important point to take into consideration while running the tests - Thanks!


feat: add explicit BSP export error

As a followup to today's conversation about custom exception classes, while a bunch of little exception classes within a particular Rails app might be discouraged, core Ruby suggests it for libraries.

A good practice is for a library to create a single “generic” exception class (typically a subclass of StandardError or RuntimeError) and have its other exception classes derive from that class. This allows the user to rescue the generic exception, thus catching all exceptions the library may raise even if future versions of the library add new exception subclasses.

So, 👍🏻 👍🏻


Android - Chat - App crashes after creating different chats back to back

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.51-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Issue reported by: Applause Internal Team
Action Performed:

Open the Expensify app.
Tap on the FAB.
Tap on "Start Chat"
Create a new chat (Group, individual, room).
Repeat steps a few more times.
Verify all the new chats are created properly and the app keeps working smoothly.

Expected Result:
The app should continue to work smoothly while the user creates new chats back to back.
Actual Result:
The app crashes after the user creates a few chats back to back.
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
1910_2.txt
https://github.com/user-attachments/assets/b9b3a8a6-1c3d-4f6b-aad3-643ac767dd28

View all open jobs on GitHub

We think that this bug might be related to #wave-collect - Release 1

This is not related to #wave-collect but the app crashing is worrying, so we should look into this one.

So far I can't reproduce on the standalone app, going to test with HybridApp.

Still trying to build HybridApp in dev, it's extremely slow and I keep running into different errors...
In the meantime I found you can reproduce by just opening and closing the new chat menu multiple times in a row, no need to actually create chats.
So far the diff of recent changes doesn't help understand why the app freezes like this.

Closing: https://expensify.slack.com/archives/C9YU7BX5M/p1729557218232369?thread_ts=1729554748.866629&cid=C9YU7BX5M


Add function(s) to load stellar template library

Functions to load stellar template libraries that can be loaded with ppxf.ppxf_util are added through #25.

@martin-millon, I have also added a function Pipeline.make_template_from_array() in #25 to process a template from libraries such as the XSL (that are not provided as libraries to be loaded with ppxf.ppxf_util.

OK, I also had an implementation of that in the TemplateLibrary class but let's stick to your implementation


⚠ Fetchers has degraded performance

In 687d7c2, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 250 ms

Resolved: Fetchers performance has improved in ae6c16e.


Error any time an Attack is rolled

Strikes:

Spell Attack:

Modifiers Matter is the only active module, pf2e 4.10.4, foundry 10.291

Fixed in v1.7.1


[FLINK-16550][s3] Force namespace parsing in XmlResponsesSaxParser.

What is the purpose of the change
This commit explicitly enables Sax' NAMESPACES_FEATURE (default true) in JAXP (default false), such that multi part uploads to S3 actually work.
Brief change log
Explicitly enables Sax' NAMESPACES_FEATURE (default true) in JAXP (default false).
Verifying this change
Covered by e2e only executed on nightly.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Shall I merge the PR, or would you feel more comfortable with another review? (I haven't looked deeply into the cause + fix. I just trust CI in this case)

Shall I merge the PR, or would you feel more comfortable with another review? (I haven't looked deeply into the cause + fix. I just trust CI in this case)

I'm comfortable with you merging it.