Download Zip and Build

First all, thanks for your hard work on this project. It sounds great.
When I download the Zip file on a virgin machine, unzip and load the project, it comes up with 61 errors and 7 warnings when built.
It would be even more awesome to be able to download an install without having to do a build, but if that isn't the case, then it would be good if the build would work on a virgin machine.

What kind of errors are this?  There shouldn't be any (maybe you've forgotten to perfrom the nuget restore step - see https://github.com/xmlunit/xmlunit.net#building).  If it'sd not "just run nuget", then please attach the error output here so we can fix them.
nuget packages of XMLUnit will become available once the code is ready for the first alpha release, which shouldn't be too far away (but I know my time constraints too well to promise anything).
If you follow the Appveyor link from the homepage and click through to the latest build, there'll be an "Artifacts" link that allows you to download nuget packages of the current code base.  I'll state this more prominently on start page.

I assume the problem no longer exists.  If you still can't build from a fresh copy, please open a new issue and provide more details about the errors.


How to make bot.on not called when bot.onText is called ?

I want to make a bot, when user type in any message, it reply "Meow meow meow meow".
But when user type /help, it should reply "type anything to read cat sound" without reply "Meow meow meow meow". However, my bot running by the code below reply both "Meow meow meow meow" and "type anything to read cat meow" when user type /help
Here is my code

'use strict';

var TelegramBot = require('node-telegram-bot-api');

var TOKEN = 'my telegram ID';
var USER = 'i have no idea what is this';

var bot = new TelegramBot(TOKEN,{polling:true});
console.log("bot is running");

// Matches /echo [whatever]
bot.onText(/\/help/, function (msg, match) {
  var fromId = msg.from.id;
  var resp = match[1];

  bot.sendMessage(fromId, "type anything to read cat sound");
});

// reply to any message
bot.on('message',function(msg){
    var chatId = msg.chat.id;
    var bot_response = "Meow meow meow meow";
    console.log(msg);
    bot.sendMessage(chatId,bot_response);
});

The "message" event is always fired when an update of Message type is received. Therefore, even if a regexp in bot.onText() is matched, the event is still fired. See the method that processes each update.
Therefore, you may need to do sth like:
bot.on('message', function(msg) {
    let text = msg.text;
    // Stop, if the message is for a '/help' command.
    // You may want to use a proper regexp
    // but for the sake of brevity... :)
    if (text && text === "/help") return;

    // ... snip ...
});

It's better to use not if (text && text === "/help") return;
but if (msg.entities) return;

Your issue has been addressed above. It's a design issue that should be addressed in your application.


Lambda merge

Merge main functions for transforming backend requests to ES queries into web service. The AWS Lambda now acts more like a proxy with less data wrangling. In the future, many of these util functions should probably go somewhere other than frameworks-drivers.

Opened PR on wrong repo - sorry!


Missing published javadocs for 1.45.0

They are now available here: https://googleapis.dev/java/gax/1.45.0/


Use Embed.timestamp for the !remind command

Description
This PR makes it so that when you the use !remind command, the success embed sends the date in the embed's timestamp, and not in the footer. This is so that the time can update how discord formats it, and so that it will convert to your local timezone. This closes #1536.

Here is the current output:

I think that's pretty good, if grammatically a little awkward. I think the original wording ~

~ reads somewhat better to me, but maybe it's not as direct in what it's trying to convey. What do you think?

I wasn't sure if Due •10/20/21, but now thinking about it, it looks fine.

Yeah, perhaps what you have will be the easiest to understand. I don't feel strongly either way.


#78 TIPMIP: Add experiment set

Added the 6 experiments defined in #78:

esm-up2p0
esm-up2p0-gwl2p0
esm-up2p0-gwl2p0-50y-dn2p0
esm-up2p0-gwl4p0
esm-up2p0-gwl4p0-50y-dn2p0
esm-up2p0-gwl4p0-50y-dn2p0-gwl2p0

@zklaus, @jprb-walton  if you have a moment could you check that I've transcribed the information from the table in #78 correctly

Thanks @matthew-mizielinski , looks good to me.

@wolfiex. I think the jsonld branch matches the information here.


Add dynamic programming solution for word wrap problem

What does the program do ?
The program is a solution to the word wrap problem using dynamic programming.
In what programming language it is written?
C++

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


switch GCR -> Artifact-Registry

GCR has been deprecated [0] in favour of Artifact-Registry.
Thus, change push-targets for OCI-Images:

europe-docker.pkg.dev/gardener-project/snapshots for snapshots
europe-docker.pkg.dev/gardener-project/releases for releases
europe-docker.pkg.dev/gardener-project/public for combined view of snapshots + releases

[0]
https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr
Release note:
Change OCI Image Registry from GCR (`eu.gcr.io/gardener-project`) to Artifact-Registry (`europe-docker.pkg.dev/gardener-project/releases`). Users should update their references.

This PR proposes changes that would break the pipeline definition:
ext-authz-server-gcr-to-ar: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/concourse/replicator.py", line 141, in render
    definition_descriptor = self._render(definition_descriptor)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/concourse/replicator.py", line 185, in _render
    'definition': factory.create_pipeline_definition(),
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/concourse/factory.py", line 108, in create_pipeline_definition
    validator.validate()
  File "/usr/lib/python3.11/site-packages/concourse/validator.py", line 29, in validate
    self._validate_variant(variant)
  File "/usr/lib/python3.11/site-packages/concourse/validator.py", line 34, in _validate_variant
    self._validate_element(variant)
  File "/usr/lib/python3.11/site-packages/concourse/validator.py", line 39, in _validate_element
    element.validate()
  File "/usr/lib/python3.11/site-packages/model/base.py", line 44, in validate
    self._validate_known_attributes()
  File "/usr/lib/python3.11/site-packages/model/base.py", line 73, in _validate_known_attributes
    raise ModelValidationError(
model.base.ModelValidationError: JobVariant:<unknown>: The following attributes are unknown: component_descriptor.

The pipeline-definition has been fixed.

/hold
Waiting for https://github.com/gardener/ext-authz-server/pull/26 to be merged first to fix the tests. This change should be rebased on top of https://github.com/gardener/ext-authz-server/pull/26 afterwards.

/unhold
Please rebase now that https://github.com/gardener/ext-authz-server/pull/26 is merged. The tests should then succeed.


Upgrade helm to v3.2.1

We've moved up the Helm version to remove the dependency on Tiller.

Codecov Report

Merging #468 into master will increase coverage by 0.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #468      +/-   ##
==========================================
+ Coverage   76.21%   76.71%   +0.50%
==========================================
  Files          45       45
  Lines        2766     2766
==========================================
+ Hits         2108     2122      +14
+ Misses        658      644      -14

Impacted Files
Coverage Δ

opwen_email_client/webapp/mkwvconf.py
100.00% <0.00%> (+38.88%)
: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 ce1b398...1ee6330. Read the comment docs.

@mtotoWamkwe Note that the live integration tests are currently failing since the pull request is coming from a fork. Given that you're a member of the Ascoderu organization, you should have push access to this repository. In the future, please push branches to the lokole repository (instead of a fork) and submit your PR from that branch so that the full test suite runs. Thanks!


Trained models not working in Python 3.6+

Loading model files gives error SystemError: unknown opcode.
This is the issue with Keras.
Please provide the models trained on python 3.6.

The models can be loaded in the version of python used while creating them. Keras has this issue. Try downgrading python 3.6 to python 3.5, it worked for me.

Yeah it worked on my local machine after downgrading the local version of python. But in Google Colab there is no way to downgrade Python 3 version, so it cannot be used there,

Just convert the npy weights with your desired keras/python Version. You’ll be fine.

Yeah it worked on my local machine after downgrading the local version of python. But in Google Colab there is no way to downgrade Python 3 version, so it cannot be used there,

Totally right, so I am going to train it on ADE20K again🤯

@jmtatsch What npy weights? I thought we only used keras weights

just search the issues you may find something.


Add array tail function

Hey, thanks for the PR! Looks good, but could you write a test for:

An empty list.
A list with one item.

In both cases, an empty list should be returned.

@filipdanic Sure thing.


Some linalg functions are not well-defined

The functions eigh, svd, qr and lstsq are not well-defined as written.
Uniqueness lstsq
linalg.lstsq docs currently read:
“Returns the least-squares solution to a linear matrix equation”
but the solution needn't be unique whenever A has non-trivial kernel (e.g. A = 0).
Proposed solution:

Rewrite it as "Returns a least-square solution [...]"
Perhaps we want to add a note on how to handle these cases (e.g. the solution with smallest norm is chosen) so that this function is well-defined for every input matrix. Note that this would not allow for the implementation of this function via faster but less robust algorithms such as LAPACK's gels, which assumes that A is full-rank and performs a QR decomposition.

Uniqueness eigh and svd:

Eigenvectors (resp. singular vectors) of a generic matrix are only defined up to sign in the real case and multiplication by a scalar of norm 1 in the complex case
When the matrix has repeated eigenvalues (resp. singular values) the associated eigenvectors are just defined up to multiplication by a rotation (or multiplication by a unitary matrix in the complex case).

Proposed solution:

Change the wording from "Returns the eigenvalues and eigenvectors of a symmetric matrix" to "Returns an eigendecomposition of a symmetric matrix".
Change the wording of linalg.svd as well.

QR decomposition cannot be defined
The qr decomposition is just well-defined whenever the matrix has full column rank. In the singular case pivoting is necessary.
Proposed solution: The behaviour of this function should be marked as unspecified whenever the input matrix does not have full column rank.
cc @rgommers @mruberry

Thanks for the detailed review @Lezcano. Your proposed solutions for eigh, svd and qr all sound good to me, as does the first bullet for lstsq.

Perhaps we want to add a note on how to handle these cases (e.g. the solution with smallest norm is chosen) so that this function is well-defined for every input matrix. Note that this would not allow for the implementation of this function via faster but less robust algorithms such as LAPACK's gels, which assumes that A is full-rank and performs a QR decomposition.

I don't think we should add such a note. One principle we'd tried to adhere to in the API design is "don't make decisions that limit implementers in how they optimize for performance". So taking a decision on performance-robustness tradeoffs for lstsq doesn't sound optimal.
Pointing out the issue is good though - but I'd do it as a note like "if the solution is not unique, implementations may return different results".

For what is worth, I do not know of any implementation of lstsq that does not return the minimum norm solution. For example, all the LAPACK implementations do so. Note that even gels falls in this category as well, albeit under the assumption that the matrix is full-rank.
On a similar decision to this one, see the OP of the PR for linalg.matrix_rank. The OP says that, even though some implementations provide an hermitian boolean flag, this is not included in the specification because it denotes an optional optimisation. In the same way, the behaviour of gels could also be provided by the libraries via an optional flag full_rank=False or similar.


Bravus Team 👟🏃🏻♂

Hello @DMSilvaVerse , is there anything particular that we can help you with? Nice 👟 running shoe emoji.

close pr. reason: no issue given


[BUG] Incorrect Kafka SASL mechanisms

#. Bug Description
https://docs.min.io/minio/baremetal/reference/minio-mc-admin/mc-admin.config.html#mc-conf.notify_kafka.sasl_mechanism lists SCRAM as a valid mechanism. Based on our code it looks more like we just support sha256 and sha512 mechs.
#. Resolution
Update the section to contain correct mechanisms.

https://github.com/minio/docs/commit/06500dcba3f406a227ac1772d9ae92cb69c65105 fixed


translocation test cases

@abolia @BrettKennedy @ryanabo,
I'm very close to adding translocation support to WHAM-GRAPHENING.  I'm trying to round up some test cases in BAM format.  Do you have any to share?

Hi Zev,
Sure, I can send you some. Would you like me to upload them to GNomEx or
somewhere else. Let me know.
Thanks,
Ashini
On Wed, Apr 13, 2016 at 9:39 AM, Zev Kronenberg<EMAIL_ADDRESS>wrote:

@abolia https://github.com/abolia @BrettKennedy
https://github.com/BrettKennedy @ryanabo https://github.com/ryanabo,
I'm very close to adding translocation support to WHAM-GRAPHENING. I'm
trying to round up some test cases in BAM format. Do you have any to share?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/zeeev/wham/issues/31

--
Kind Regards,
Ashini Bolia

Hey Zev,
I have uploaded 2 bams on GNomEx:
https://hci-bio-app.hci.utah.edu/gnomex/gnomexFlex.jsp?analysisNumber=A3484
Sample SP-14-15849
True Positive: ALK gene chr2:29415639-30144477
Supected Partner: EML4 gene chr2:42396477-42559688
Sample SP-14-20579
True Positive: EWSR1 gene chr22:29663997-29686672
Supected Partner: WT1 gene chr11:32409321-32457081
Let me know if you need more BAM's.
Thanks,
Ashini
On Thu, Apr 14, 2016 at 12:41 PM, Ashini Bolia<EMAIL_ADDRESS>wrote:

Hi Zev,
Sure, I can send you some. Would you like me to upload them to GNomEx or
somewhere else. Let me know.
Thanks,
Ashini
On Wed, Apr 13, 2016 at 9:39 AM, Zev Kronenberg<EMAIL_ADDRESS>wrote:

@abolia https://github.com/abolia @BrettKennedy
https://github.com/BrettKennedy @ryanabo https://github.com/ryanabo,
I'm very close to adding translocation support to WHAM-GRAPHENING. I'm
trying to round up some test cases in BAM format. Do you have any to share?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/zeeev/wham/issues/31

--
Kind Regards,
Ashini Bolia

@abolia Thank you.  I'm trying them out now.

What reference genome was used?  HG19?

Yes, hg19 was used.
Thanks,
Ashini
On Fri, Apr 15, 2016 at 9:04 AM, Zev Kronenberg<EMAIL_ADDRESS>wrote:

What reference genome was used? HG19?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/zeeev/wham/issues/31#issuecomment-210496782

--
Kind Regards,
Ashini Bolia

@abolia Looks like it is a custom reference genome.  I will need your reference.

Oh yeah, sorry I forgot to mention that. It is custom reference that
contains the phiX and adapter sponges. I uploaded the fasta, index and dict
files to GNomEx under the same analysis.
Thanks,
Ashini
On Fri, Apr 15, 2016 at 9:10 AM, Zev Kronenberg<EMAIL_ADDRESS>wrote:

@abolia https://github.com/abolia Looks like it is a custom reference
genome. I will need your reference.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/zeeev/wham/issues/31#issuecomment-210498838

--
Kind Regards,
Ashini Bolia

Hi @abolia @BrettKennedy ,
WHAM-G, on the devel branch, calls BNDs (inter-chromosomal events).  If you'd be interested in trying it follow the steps below. Otherwise I will let you know when a do a full release. Any feedback is welcome.
cd wham
checkout devel
make graphDebug

Here is an example of how to run it:
WHAM-GRAPHENING -e Y,MT,GL000207.1,GL000226.1,GL000229.1,GL000231.1,GL000210.1,GL000239.1,GL000235.1,GL000201.1,GL000247.1,GL000245.1,GL000197.1,GL000203.1,GL000246.1,GL000249.1,GL000196.1,GL000248.1,GL000244.1,GL000238.1,GL000202.1,GL000234.1,GL000232.1,GL000206.1,GL000240.1,GL000236.1,GL000241.1,GL000243.1,GL000242.1,GL000230.1,GL000237.1,GL000233.1,GL000204.1,GL000198.1,GL000208.1,GL000191.1,GL000227.1,GL000228.1,GL000214.1,GL000221.1,GL000209.1,GL000218.1,GL000220.1,GL000213.1,GL000211.1,GL000199.1,GL000217.1,GL000216.1,GL000215.1,GL000205.1,GL000219.1,GL000224.1,GL000223.1,GL000195.1,GL000212.1,GL000222.1,GL000200.1,GL000193.1,GL000194.1,GL000225.1,GL000192.1,NC_007605 -x 10 -a ~/shared_resources/gatk-resouces/human_g1k_v37.fasta -f CHM1_1.bam -x 5 > test 2> wham.err

After looking at you data I would highly recommend pre-trimming the reads to remove the high rate of N's.  That will improve both WHAM and Delly calls.

Hi,
I was wondering what the status is on implementing translocation detection.
regards,
Tjitske

@Tjitskedv Currently, I don't have time time implement the translocation functionality. I'de be happy if someone was interested in helping.


Replace sets for repeatability

Following yesterday's "fix" (spoiler: it didn't work). I traced the other instances of sets which could contribute to the Scheduler distributing the messages in a non-repeatable way.
These were:

the set used in get_mail_recipients in MailingList
the set used in the defaultdict(dict) of MailingList.directory which is used in get_subscriber_list
the set used in clients_to_wake_up in Clock which is used on release_alarm_messages

The remaining sets in MailingList.topics() and MailingList.subscriptions don't appear to be used in a way where non-repeatable orders will be problematic.

Looks good!


Bad encoding in Vim

Vim doesn't show language specific chars properly. I think the encoding should be utf-8. I managed to fix the problem inside Vim by adding this line to _vimrc :
set encoding=utf-8
but the problem persists when I use i.e. vim --help. Here the output still has bad encoding, even after $PSDefaultParameterValues['*:Encoding'] = 'utf8'

Do you use vim in Windows terminal?
The Windows terminal is old and can't display unicode very well.
It will somewhat work, but it is not as good as in gvim.
To display unicode characters on windows terminal, you need your os, the terminal emulator, the shell(cmd.exe) or terminal program, and the font all works properly, which is sometimes quite difficult.
What windows version are you using? The unicode support is much improved in the latest version of Windows 10.

This issue belongs in the Main bucket. Unfortunately, we cannot move this issue on this end, so it is being closed.
If this is still an issue, please create a new issue in the Main bucket via https://github.com/ScoopInstaller/Main/issues/new?body=Moved+from+https%3A%2F%2Fgithub.com%2Flukesampson%2Fscoop%2Fissues%2F3039


fix: more adjustments to eslint config

This adds the import plugins and also better sets up stuff to make the use strict stuff not required.

Want to fix up 1 last thing. Apologies. Will re-open in a bit

I'm really hating the new eslint config stuff. It's so unnecessarily complicated. I think this does all the stuff I want now.


[Testing] Flakey integration tests (in-memory network)

Objective
Capture unique instances of flakey integration tests, which by definition are using the in-memory cosmos network integration (see #290).
Origin Document

TestListGateway:

Goals

Enumerate flakey tests which are likely attributable to issues in the in-memory cosmos network integration as such observations will:

Contribute describing the failure mode(s) present
Establish a comprehensive and robust baseline sufficient for confirming the elimination of failure mode(s)

Deliverables

[ ] Accumulate failure results in this issue until it is prioritized, categorizing failure modes as they become apparent.
[ ] A PR targeting each failure mode.

Non-goals / Non-deliverables

Refactoring the in-memory cosmos network integration beyond the scope of this issue's goals.

General deliverables

[ ] Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
[ ] Testing: Add new tests (unit and/or E2E) to the test suite.
[ ] Makefile: Add new targets to the Makefile to make the new functionality easier to use.
[ ] Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.

Creator: @bryanchriswhite
Co-Owners:

Looks like we'll have to deal with some race conditions...

Tests have undergone many iterations so this is stale.


Update demo1.md

Learn Build status updates of commit 784e89e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/4283/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


[Bug] Animated.ScrollView : "scrollTo" is not a function.

[ ] I have reviewed the documentation
YES
[ ] I have searched existing issues
YES
[ ] I am using the latest React Native version
YES

Animated.ScrollView : "scrollTo" is not a function, but ScrollView works well.(iOS & Android & Simulator)
Environment
Environment:
OS: macOS High Sierra 10.13.4
Node: 10.0.0
Yarn: 1.6.0
npm: 5.6.0
Watchman: 4.9.0
Xcode: Not Found
Android Studio: 3.1 AI-173.4720617
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4
Steps to Reproduce
Code:
<Animated.ScrollView
    ref={ref=>(this.scrollView=ref)}
    />

action = ()=>{
    this.scrollView.scrollTo({x:100,y:100, animated:false});
}

Expected Behavior
Animated module does not export method scrollTo.
Actual Behavior
Getting an error on all platform devices and simulators:
"_this2.scrollView.scrollTo is not a function"

If scrollTo is disabled, how can I change the offset of the scrollview by code.

@ATShiTou I ran into this problem as well after changing an existing ScrollView to an Animated.ScrollView. You can access the underlying ScrollView with this.scrollView.getNode().
Your action would then be: this.scrollView.getNode().scrollTo({x:100,y:100, animated:false});

Thank you very much.

It works only in iOS. For Android, I am still having issue with "scrollTo". Any suggestion?

For Android, I set the top margin in my style. I didn't find any workaround with "ScrollTo" option.

Can't get this working in iOS neither Android using React.createRef(). After refering and trying to call this.scroll.getNode().scrollTo({ ... }) I still getting scrollTo is not a function

@marquesm91 In my case I get "getNode is not a function".

Bug still exist.

Bug still exist. React.createRef() It is not working in Animated.ScrollView and working in ScrollView

U are right @rendomnet, at a later time I was able to use create.Ref, but it is no longer working on Animated.ScrollView. Could you report the solution found?

i find that safari on macbook mini ".scrollTo" is not a function.

i find that safari on macbook mini ".scrollTo" is not a function.

support:
https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollTo

@RafaelFeiten no. No solution.

For me, this answer seems to work out. I am using expo 32.0.0, react 16.5.0, and react-native v0.57.1.

Any findings on this? I can't get ref.current.scrollTo() or ref.getNode().scrollTo() to work on iOS (haven't tried Android. I'm sure it's not working either.)

Not working, read about React Memo. It can help u...


feat: format PoorError to mirror Geth's TxPool Error messages

Fixes #1131

Codecov Report

Merging #1156 (873aefc) into main (a55e7fd) will increase coverage by 0.42%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1156      +/-   ##
==========================================
+ Coverage   74.75%   75.18%   +0.42%
==========================================
  Files         333      335       +2
  Lines       35442    36359     +917
==========================================
+ Hits        26495    27335     +840
- Misses       8947     9024      +77

Flag
Coverage Δ

unit-tests
75.18% <0.00%> (+0.42%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/rpc/rpc/src/eth/error.rs
0.00% <0.00%> (ø)

crates/transaction-pool/src/test_utils/mock.rs
51.77% <0.00%> (-6.74%)
:arrow_down:

crates/net/eth-wire/src/types/version.rs
77.77% <0.00%> (-2.23%)
:arrow_down:

crates/executor/src/revm_wrap.rs
38.21% <0.00%> (-1.79%)
:arrow_down:

crates/net/network/src/session/active.rs
85.90% <0.00%> (-1.00%)
:arrow_down:

crates/stages/src/stages/bodies.rs
92.46% <0.00%> (-0.67%)
:arrow_down:

crates/primitives/src/transaction/mod.rs
89.29% <0.00%> (-0.54%)
:arrow_down:

crates/transaction-pool/src/pool/txpool.rs
58.82% <0.00%> (-0.51%)
:arrow_down:

crates/stages/src/stages/execution.rs
92.04% <0.00%> (-0.14%)
:arrow_down:

crates/executor/src/executor.rs
93.76% <0.00%> (-0.13%)
:arrow_down:

... and 21 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


How to reload all or a single script

mod im using keeps getting aborted as soon as a error comes, is there a way to restart it thru console or other means? as i have to continually restart the whole game just to reload 1 script when a certain npc isnt in range

You can reload all scripts from the menu with the command Reload()

You can reload all scripts from the console using the command Reload()

thank you!


allow custom output filename

Currently webpack configs that specify a custom output filename will break this plugin. This fixes that.

however if the handler first part does not correspond to the bundle filename, AWS lambda itself would not find the function handler right?
In that case having the simulator fail would be the correct behavior I'd say. Probably a better error report would make sense.
can you give an example of what situation this fix would solve?

Good point, I didn't think of that. In that case, yes a better error would be useful.
I was just testing this plugin out and I was trying to use my old webpack config which had a custom output filename.
But what you say makes sense, so you can close this PR.

Closing it then. However if you could come up with a better error about that case it would be great. Maybe we should also update the readme to make that handle naming thing more clear.


Correlated stats.norm.rvs when passed

I would expect that if I pass an array of N loc values into rvs, it would sample the values independently. Instead, rvs returns an N-array of the same random number, shifted and scaled according to the corresponding value in the loc array. For example:
from scipy import arange, zeros, __version__
from scipy.stats import norm

print(__version__)
print(norm.rvs(size=3))
print(norm.rvs(zeros(3)))
print(norm.rvs(arange(3)))

will output
0.17.1
[-0.44117927 -2.20215922  0.52281674]
[ 0.21769148  0.21769148  0.21769148]
[-0.02990758  0.97009242  1.97009242]

The first printed array is the behavior I expect: the numbers are uncorrelated. The other two arrays are clearly correlated. I don't observe a similar problem in scipy.stats.poisson.rvs:
from scipy import array
from scipy.stats import poisson

print(poisson.rvs(array((10, 10, 20, 20))))

will output

[10  6 28 26]

Thanks for reporting the problem.  This is a known bug: https://github.com/scipy/scipy/issues/2069


External hyper:// link doesn't open properly when opened in Beaker

Describe the Bug
When opening a hyper:// link from another browser such as Chrome or Firefox the link will use file associations to launch Beaker but once opened the link has been abbreviated and doesn't function. Copy/paste the link to Beaker works fine.
To Reproduce

Visit a sample webpage in Chrome or FF

<!DOCTYPE html>

  A Hyperlink hyper-link

Click the link
Browser asks if I want to open in Beaker, click yes
Beaker Opens the link but, I get a 500 status in the browser
Clicking on the URL bar displays the link as hyper://6946..a4/

Expected Behavior
Beaker should open the associated link and display the hyperdrive page as usual.
Screenshots
I can provide if needed.
Environment

OS: Windows 10
Beaker Version: 1.0 Beta 7

Additional Context
Checking in the General Logs the following 2 lines are logged:
warn | hyper | hyper-scheme | Failed to open drive undefined
info | browser | init | Second instance opened

I mentioned the issue to Paul on discord, I just wanted to get the bug logged and tracked.

I'm not seemingly able to open a hypedrive in Edge or Brave, When I create an .html file from the code you posted (I think that's what you intended?) and then open it in Edge or Brave and click the link.... nothing happens at all. I'm not sure how to reproduce having Brave/Edge ask me if I want to open the link in Beaker. I have a lot to learn!

That might be due to configuration , in the Beaker Settings there is a section under general called "Browser Settings"  in there is the options to "Set Beaker as the default browser for:"  with http | hyper | dat as options . I'm guessing they are not selected?
If they are selected then there might be another bug there. Oh thinks for mentioning Edge.. I totally forgot to test in Edge!

I'm not seemingly able to open a hypedrive in Edge or Brave, When I create an .html file from the code you posted (I think that's what you intended?) and then open it in Edge or Brave and click the link.... nothing happens at all. I'm not sure how to reproduce having Brave/Edge ask me if I want to open the link in Beaker. I have a lot to learn!

Thanks for reporting, @leeclarke. We'll add it to the queue.

I'll take a look at the code and try to see if I can figure it out. I'm new to Electron so no promises but untill someone else takes it up it can't hurt to try!


AVCaptureDeviceInput with wrong definition

From @dartmann on February 12, 2018 19:7
Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?
Yes, nothing helpful found.
Tell us about the problem
The AVCaptureDeviceInput class has a wrong method definition for deviceInputWithDeviceError.
Which platform(s) does your issue occur on?
iOS
Please provide the following version numbers that your issue occurs with:

CLI: 3.4.1
Cross-platform modules: 3.4.0
Runtime(s): 3.4.0
Plugin(s):

Please tell us how to recreate the issue in as much detail as possible.
While trying to implement a barcode scanning logic in my {N} plugin I stumbled across the deviceInputWithDeviceError method of the AVCaptureDeviceInput class. Given the method name, I thought that it should take two parameters: the device and an error reference. But with the current definition it only takes the device.
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
The nativescript method definition:
static deviceInputWithDeviceError(device: AVCaptureDevice): AVCaptureDeviceInput;

The Objective-C method definition (taken from the Apple docs):
+ (instancetype)deviceInputWithDevice:(AVCaptureDevice *)device
                                error:(NSError * _Nullable *)outError;

Copied from original issue: NativeScript/NativeScript#5414

@dartmann thanks for reporting this one. Confirming this as an unexpected definition.
The method should accept two arguments as done here.

Hi @dartmann,
I wasn't able to find any official docs stating that deviceInputWithDeviceError behavior has changed for Objective-C but it looks like there is a change in the Swift API since XCode 7 (https://stackoverflow.com/questions/30949154/how-do-i-fix-the-error-deviceinputwithdevice-is-unavailable). This is why I tried wrapping the AVCaptureDeviceInput initialization in try-catch statement instead of passing an NSError reference and it worked. For example:
var videoDeviceInput;
let device = AVCaptureDevice.new();
try {
    videoDeviceInput = AVCaptureDeviceInput.deviceInputWithDeviceError(device);
}
catch(err) {
    console.log(err); //prints NSErrorWrapper: Cannot use Unknown Device
}

Hi @tdermendjiev and @Nicklliev,
thank you for your answers. I'll follow your try-catch suggestion.
Best regards, David

Sorry for the late reply. This question is not related to the iOS Runtime and we don't have resources to dive into it.


Fix Sample Date in Integration Test

Error didn't crop up until the private API PR was merged. Re: https://github.com/biocore/microsetta-interface/actions/runs/7054261612/job/19202813632#step:6:375

Moving this fix into #301 since it's blocking merge on that PR.


Keep a manifest of loaded plugins.

This would help like cleaning and reference checking when starting a new prompt.
Right now old plugins are left behind, even when removed from .zshrc.
It doesn't have to be intelligent, could just be purging the plugins folder and fetching everything again.

Yeah but my suggestion was it could be self-managed.
or something alongside znap plugins reload that would purge and reinstall, that way it would remove plugins no longer listed in e.g  `.plugins.zsh" instead of manually having to delete them.

Ah, now I understand it. Yes, that’s a nice idea. 👍🏽

I gave this some more thought and decided against it. I manage many non-plugin repos with znap and I wouldn't want those to get auto-removed. Besides, it is fairly straightforward to remove a plugin yourself:

Type ls ~znap to see which repos are managed by Znap.
Type znap uninstall <repo> to remove one.


what is "has_cookies_for_current_website" method in driver object?

when i execute Upload.upload,
occur error in upload.py line 95
elif self.driver.has_cookies_for_current_website():
AttributeError: 'Firefox' object has no attribute 'has_cookies_for_current_website'
what is "has_cookies_for_current_website" method in driver object?
and also i can not found "load_cookies" method in 96 line

pls  ignore these codes ,i double checked , it has no point at all
'''
elif self.driver.has_cookies_for_current_website():
...
self.driver.refresh()
'''


[Storage] Added support for VNet ACL

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Can one of the admins verify this patch?

@alvadb Comments are addressed.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-storage/2017-06-01/swagger/storage.json
Number of linter errors/warnings before the PR: 13
Number of linter errors/warnings after the PR: 18
Thanks for your co-operation.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-storage/2017-06-01/swagger/storage.json
Number of linter errors/warnings before the PR: 13
Number of linter errors/warnings after the PR: 12
Thanks for your co-operation.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-storage/2017-06-01/swagger/storage.json
Number of linter errors/warnings before the PR: 13
Number of linter errors/warnings after the PR: 11
Thanks for your co-operation.

@alvadb Ping :)

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-storage/2017-06-01/swagger/storage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 0
Thanks for your co-operation.

@alvadb Ping:)

No modification for Ruby

No modification for Python

No modification for NodeJS


Have you tried working with Modal dialogs with CSS transitions?

Stumbled upon your repo hoping someone can point me on how to do this in F# Fable with TailWindCSS. I'm trying to create a modal dialog that uses the TailWindCSS class names, but it looks like it requires additional work to make it work?

You could use the Modal component from daisyUI: https://daisyui.com/components/modal/.


Print() and Assert() from TLC module does not work

While verify a raft tla spec using Apalanche, I found two problem:

The Printf() from TLC module does not print anything in the console
The Assert() from TLC module also seems not work, eg. typing /\ Assert(FALSE, "violation meet") in the spec does making Apalanche to report error as expected

So does these two functions supported in Apalanceh? How can we make theses two functions work, they are so useful when debuging a spec.
Apalache version: 0.30.1

They are not supported and will never be supported, because Apalache, unlike TLC, does not explore traces one-by-one, but creates a constraint representation of all n-step reachable states. In the constraint encoding, printing/asserting isn't really well defined.

If you find yourself needing assert, you can check out Quint. It's an alternative input language to TLA+, which will eventually become supported as input for Apalache. It has an assert, and a simulator you can experiment with, which should help with your debugging.

@Kukovec got it, thanks a lot, and so I'm going to close this issue.


Set date & time service

Describe the feature you want
Hello, I've been using this component but alas, it's no longer working due to migration to myvaillant. One very useful service it had, that is missing from this component, is one to set time date in the system. It was superbly useful, considering frequent blackouts in Ukraine (I had an automation in HA to set it to current time on HA launch). Would it be possible to add such a service to this component?

Unfortunately I never found a way to set this in the app or over the API. If you discover a way to update date & time, send some screenshots please!


Providing stub files or solution setup guide for JavaScript track

I’m fairly new to Exercism and am making my way through the JavaScript track. I’ve found it to be extremely useful so far, but one of the biggest pain points for me is setting up solutions for the tests. Whenever a slightly more complicated test structure comes up, I usually hit a roadblock and have to copy someone else’s setup before I can even get started solving the problem itself.
Except for the first two problems, it looks like no stub files are provided for this track. Yet the tests require a variety of setups, which may not be obvious to beginners or people unfamiliar with testing frameworks. After posting an issue about this in exercism/discussions, I discovered that some other tracks do provide stub files, but I haven’t been able to find a discussion about this for the JavaScript track.
Is there a rationale for not providing stub files? One reason I can imagine is that there are multiple ways a given solution could be set up (eg. with classes or prototypes). Perhaps an alternative would be to provide a guide at the beginning of the track that covers the various test structures that users will encounter and provides example setups for these. Another possibility would be to provide partial stub files that define exports and offer hints about the setup.

@exercism/javascript I strongly suggest adding solution placeholders for each exercise

@a-dpq thanks for your feedback, especially since it's delivered in a very thoughtful way.  Thanks also to @m-a-ge for your input.
We don't mostly provide stub files, it's true, and your speculation about why is more or less accurate.  A couple of years ago we did have a discussion around this, in which it was decided that the first dozen exercises would have a consistent interface with the test suites, and after that, all bets were off.  This was intentional, to push the user and make them wrestle with the possibilities.  Having said that, I'm not opposed to changing it, and I would be curious to hear what the rest of the maintainers think.
Most of these solutions can be implemented using ES5-style object prototype extension, ES6 classes, or even pure functions.  We intentionally leave that up to the user.
Now, it may be the case that our original intention has been thwarted by the new exercise ordering structure that was implemented recently, and the first twelve are no longer consistent in their interface style.  Whatever the outcome of this discussion, an investigation of that possibility seems warranted.
@exercism/ecmascripts -- any thoughts on this?

I am not this track maintainer, but I think ES6 classes are preferable way of doing this, just saying 😄

@m-a-ge yes, but this track is explicitly focused on ES5 features.  We want to give people the option, but I'm not sure we want to push them in that direction.
At some point we have to decide to pull those features in to this track as well, but that feels like a separate piece of work to me.

Thanks for your response, @matthewmorgan. For what it's worth, the two exercises that posed the biggest challenge for me so far in setting up the solution for the test suite were clock and circular-buffer. (I've only made it about halfway through the track.) I always try to figure things out on my own, but I don't think I would have been able to get the structure for these exercises right without either a general guide or (in this case) copying someone else's setup, which feels a little defeating.

@a-dpq that's not a good feeling!  Maybe we need to have a look at those APIs and see if they are particularly strange.  It might make sense to either address API problems exercise-by-exercise, or if the API is intentional, to provide stubs in (some?) tough cases.

Hmm...taking a look at clock, I actually think the API is a good lesson-- a fluent, chainable API.  But, I admit that it might not be clear how to set that up in JavaScript, or at all, if you're new to OOP.
Perhaps a stub like this would help:
exports.at = at;

function at(hours, minutes) {
  var clock = {};

  clock.valueOf = function () {
  };

  clock.toString = function () {
  };

  clock.plus = function (minutes) {
  };

  clock.minus = function (minutes) {
  };

  clock.equals = function (other) {
  };

  return Object.create(clock);
}

This defines the shape of the public API, and the module structure.

I guess this illustrates the difficulty of providing a stub with just one approach, since the approach I ended up using (object prototype extension) looks quite different but does the same job. And I agree that problems like this should ideally be a learning opportunity. Still, as a beginner/intermediate learner, I felt especially lost as I was trying to set up these two exercises. Perhaps a better approach would be to provide more general guidance on the setup (either for the track overall or on a per-exercise basis) where this could be helpful. It would be good to hear feedback from other learners, since this is just based on my own experience with the track.

Stubs have always seemed useful to me for the first few exercises to help people truly new to the language to gain their footing. Especially if TIMTOWTDI or the track has a strong preference one way or another. The barrier for entry for the first few exercises should be IMO fairly low.
Of course it would be important to document where stubs end and give a good explanation for that first stubless exercies that it is time to start from scratch in crafting solutions! Suddenly having stubs pulled away could be jarring. A user may think they are missing something.

It seems obvious that more stubs are needed. And I completely agree with @tleen about stubs should not  disapear suddenly.
I have a couple of ideas, maybe, a mix of both will be the better option:

Add stubs for the first ten or twelve exercises
Add stubs for those exercises marked as core, as they will be the first users will work on the next version of exercism

For nextercism because it is possible to take multiple paths you should identify the possible first no-stub exercises in the core path and via unlocks. I would make a note in the core solution and link to it from the first no-stub unlock.

So, for Nextercism, all core exercises could have a stub, and non-core exercises could have a note or hint pointing to the exercise that unlocks them. Makes sense.

@rchavarria I wouldn't think all core exercises should have stubs, there should be a point where the users should be encouraged to stand on their own a bit more. Where this is could vary per track.
Also any note concerning stubs would be redundant. I figure the first core exercise should have a good explanation of where the stubs went, and how to start without them. The first non-core exercise without stubs that the user could encounter should point to the core exercise to avoid duplication.

Only hello-world and leap have stubs. All core exercises appear at the beginning of the config.json file, so all core exercises are currently the first to be proposed to new exercism users (some of the core exercises are hard to solve for beginners I think).
So, if we add stubs at least to all core exercises we wil add stubs to the first set of exercises. Then, we can decide if we add links or stubs to other exercises.

@alexch, yeah, I see your point. Sometimes it's hard to find this balance

btw I have forged ahead on my own fork with a few experiments... check out https://github.com/alexch/javascript if you're interested in any of the following:

remove xit and recommend --fail-fast=true
remove redundant setup instructions
run node . to launch a local trivial web server that lists the exercises in config.json order, and renders their READMEs in-browser, so users can clone this repo and run or edit the exercises in any order instead of being required to use the exercism command-line tool to fetch the next one

(I'm not suggesting to merge that last one into master, but I find it a helpful option when teaching a roomful of students in person)

@alexch we're going to be deprecating this track, and replacing it in Exercism v2 with the EcmaScript track per #556.
Thanks for your comments and work here, you are more than welcome to jump in on that track if you like.  I expect we would hold off on any change like the ones you are proposing until after the migration.


Support loop and block parameters

Steps to reproduce:

Open https://wingolog.org/pub/ in firefox nightly
Open a debugger for the newly opened tab
Open a console and type:

async function loadWasm(url, imports) {
  let {module, instance} = await WebAssembly.instantiateStreaming(fetch(url), imports);
  return instance.exports.run;
}
var sum = await loadWasm("https://wingolog.org/pub/sum.wasm");

Go to the "sum.wasm" page in the sources tab

Expected behavior: I see wasm disassembly
Actual behavior: blank page; error on the command-line:
console.error: (new Error("Unexpected type 1", "resource://devtools/client/shared/vendor/WasmDis.js", 40))
console.warn: "Action loadSourceText had an exception:" (new Error("Unexpected type 1", "resource://devtools/client/shared/vendor/WasmDis.js", 40))

See https://bugzilla.mozilla.org/show_bug.cgi?id=1628352.

Here is the wasm2wat on that file:
(module
  (type (;0;) (func (result i32)))
  (type (;1;) (func (param i32 i32) (result i32)))
  (type (;2;) (func (param i32) (result i32)))
  (func (;0;) (type 0) (result i32)
    (local i32)
    i32.const 0
    i32.const 10
    loop (param i32 i32) (result i32)  ;; label = @1
      local.tee 0
      i32.add
      local.get 0
      i32.const 1
      i32.sub
      local.tee 0
      i32.eqz
      if (param i32) (result i32)  ;; label = @2
      else
        local.get 0
        br 1 (;@1;)
      end
    end)
  (export "run" (func 0)))

thank you!

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


More intuitive priority cycling

I'm not sure if it's bound by emacs orgmode behavior, but current priority increase and decrease is a bit counterintuitive.

increase cycle

none (default priority) -> [#C] (low priority) ->  [#B] (default priority) ->  [#A] (high priority) -> none.

decrease cycle

none (default priority) -> [#A] (high priority) ->  [#B] (default priority) ->  [#C] (low priority) -> none.

Thus, the first press actually decreases priority, and then sets it to the initial state, and only then actually increases priority. The reverse is true for decrease - one needs to press 3 times to actually reduce priority.
In other words to give [#A] priority to a task with no priority, the fastest way to do it is by pressing decrease priority.
This PR modifies the cycle as follows:

increase cycle

none (default priority) -> [#A] (high priority) -> none
[#C] (low priority) ->  [#B] (default priority) -> [#A] (high priority) -> none

decrease cycle

none (default priority) -> [#C] (low priority) -> none
[#A] (high priority) ->  [#B] (default priority) -> [#C] (low priority) -> none

While it breaks the cycle starting with none, the increase and decrease reflect the change in priority.

This code seems to completely break the cycle.

Yes it does ... but it does consistently increase (decrease) priority. We could have it loop, i.e. none -> A -> C -> none -> A, but then the B is missing.
Maybe it would make sense to have a separate cycle up/down command that would do what increase and decrease do atm. But it all ties back to how it's done in emacs.
btw - great work on the Clocking summary table :sunglasses:

In other words to give [#A] priority to a task with no priority, the fastest way to do it is by pressing decrease priority.
There is a binding for changing the priority to any state (iirc it's <leader>o, by default). I would say that's the fastest way to get to the highest priority.

Good tip! but you still need to write in the priority, so that's 4 keys. Currently I use reduce priority to mark tasks as important - it's one key in the agenda - and 3 in the org file cir :slightly_smiling_face:

Hmm :thinking: maybe a toggle function would be convenient? e.g. toggle_high_priority() for [#A] and toggle_low_priority() for [#C], imo [#B] is not that useful.

My previous suggestion is now possible by using the new treesitter functions. Here's an example.
local Headline = require('orgmode.treesitter.headline')
local tree_utils = require('orgmode.utils.treesitter')

vim.keymap.set('n', '<some-keymap>', function()
  local headline = Headline:new(tree_utils.closest_headline())
  headline:set_priority('A')
end)

This PR is quite old, but I thought about the problem and want to propose another solution - because the current behavior remains to be unintuitive.
The priority settings allow to define a assumed priority for unprioritized headlines (which is [#B] by default). If we take this priority as baseline, increase would cycle to [#A] -> [#C] -> [#B] and decrease would cycle to [#C] -> [#A] -> [#B]. It would not cycle through none, because none actually has an implicit priority. This would be also somehow consistent with the behavior for todo states, because there is no "no todo" state I can cycle through. If the user really want's to remove the priority, he can either remove it by hand or with the "set priority" feature. Also a separate toggle mapping could be implemented, which would remove the current priority or set the default priority. But the main use cases for increase and decrease would then behave more intuitive for all cases.
@kristijanhusak What do you think?

@seflue I prefer having it work as Emacs orgmode does. I'm not 100% sure how it works there from top of my head, but that would be the end goal.

I agree with @seflue although sticking to Emacs is a good approach to keep consistency.
Otherwise, maybe it makes even more sense to remove [#B] altoghether. So to cycle up none -> [#A] -> [#C] -> none and cycle down none -> [#C] -> [#A] -> none.
Also at some point I was thinking about just having a toggle_high_priority() and toggle_low_priority(). If it is something that could be integrated I can make a PR.
Anyways, I'm already used to the current shortcuts but in my mind Ctr-r is set high priority and Ctr-R is set low priority.

@seflue I prefer having it work as Emacs orgmode does. I'm not 100% sure how it works there from top of my head, but that would be the end goal.

So I actually installed emacs and checked. The Emacs behavior is close to what I described, but has a little quirk.
When you move the cursor into a headline without a todo it works like:
none -> [#B] (or whatever is configured as default prio) -> [#A] (or default + 1) -> none -> [#C] -> [#B] -> [#A] -> none
So if you don't move the cursor, it will move from the highest priority into none and then cycle up from the lowest prio. But as soon as you move the cursor on a headline with no explicit priority, it will first set the default priority explicitly and then increase from there. Which is close to the behavior as I just described. Decrease works the same, but the other way around. Start with default ([#B]) -> [#C] -> none -> [#A] -> [#B] -> [#C] -> ...
I don't know, if it is possible how to detect in Neovim, that the cursor didn't move. So the simplified version would be, what I formerly proposed. The current implementation in nvim-orgmode is obviously not, how Emacs orgmode works, especially, if you just want to increase or decrease the priority of an empty headline.

@seflue thanks for testing. We can go with your proposed solution.

@gerazov: I wouldn't remove the default priority altogether from the cycle, because when someone is increasing or decreasing it, one can assume, they actually care about it and it is more surprising, if it just vanishes completely. And if someone wants to remove it again, they have already a convenient way with org_priority.
Would you be motivated to adjust your implementation to the behavior I described, or should we create a new PR?

Uff this is an old merge request - should be rebased 2 years in the future :sweat_smile:
Maybe I'll start one anew?

@gerazov I tested to rebase the branch locally and had no issues, because there were no code changes in the last 2 years. 😉

@kristijanhusak The merge actually introduced an old bug I fixed in the past with a bigger refactoring of the priority_state class. Because of that adjusting the tests to the new behavior was not trivial anymore, so I sat down myself to implement the improvement and created a new PR: #817
So this PR is now obsolete and can be closed. Sorry for the inconvenience.


Add dataset separation option

Modify the ASAP TDT conversion pipeline to allow specifying the dataset conversion mode (dataset_mode) which can be either "public" or "embargo":
The public dataset is a subset of the full dataset that only contains the data from the GPi channels.
The general metadata for the public dataset can be edited by modifying the yaml file at src/turner_lab_to_nwb/asap_tdt/metadata/public_metadata.yaml.
The embargo dataset is the full dataset that contains the data from all channels but is not going to be published publicly.
The general metadata for the embargo dataset can be edited by modifying the yaml file at src/turner_lab_to_nwb/asap_tdt/metadata/embargo_metadata.yaml.

Created folders embargo/ and public/ that should contain 2-2 example files of the two modes


unable to import or require 0.7.1 under -r esm

All of the agoric-sdk code is still using -r esm (we use import and export as if we were writing modules, but the package.json do not declare them as such, and we rely upon -r esm to let us load module-ish code anyways).
I tried to import ses as usual, and got an error which I don't know how to work around. The minimal test case looks like:
warner@turing:/tmp$ mkdir t
warner@turing:/tmp$ cd t
warner@turing:/tmp/t$ yarn add<EMAIL_ADDRESS>esm
yarn add v1.22.0
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 3 new dependencies.
info Direct dependencies
├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 0.39s.
warner@turing:/tmp/t$ cat >t.js
import { lockdown } from 'ses';
warner@turing:/tmp/t$ node -r esm t.js
/tmp/t/node_modules/ses/src/lockdown-shim.js:1
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /tmp/t/node_modules/ses/src/lockdown-shim.js
require() of ES modules is not supported.
require() of /tmp/t/node_modules/ses/src/lockdown-shim.js from /tmp/t/t.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename lockdown-shim.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /tmp/t/node_modules/ses/package.json.

    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1167:13) {
  code: 'ERR_REQUIRE_ESM'
}

I know that -r esm is a crutch, and that it doesn't play nicely with real modules: I compiled a list of rules in https://github.com/Agoric/agoric-sdk/issues/527#issuecomment-587246535 , and I think we're running afoul of at least one of them here. But I'm not prepared to change all of agoric-sdk yet, it's a big project. I was hoping the boundary between agoric-sdk and SES-shim would let me avoid doing that.
I think esm is rewriting my t.js into CommonJS format, into something like const { lockdown } = require('ses');. If I write that into t2.js, I get a slightly different error:
warner@turing:/tmp/t$ cat >t2.js
const { lockdown } = require('ses');
warner@turing:/tmp/t$ node t2.js
internal/modules/cjs/loader.js:1167
      throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
      ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /tmp/t/node_modules/ses/dist/ses.cjs.js
require() of ES modules is not supported.
require() of /tmp/t/node_modules/ses/dist/ses.cjs.js from /tmp/t/t2.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename ses.cjs.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /tmp/t/node_modules/ses/package.json.

    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1167:13)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Module.require (internal/modules/cjs/loader.js:1040:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/tmp/t/t2.js:1:22)
    at Module._compile (internal/modules/cjs/loader.js:1151:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14) {
  code: 'ERR_REQUIRE_ESM'
}

Note that t.js failed as it tried to require ses/src/lockdown-shim.js (which is listed in ses 's package.json as both main: and exports.import), while t2.js failed as it tried to require dist/ses.cjs.js (which is listed as exports.require).
If I run node -r esm t2.js, I get the same error as node -r esm t.js: unable to require src/lockdown-shim.js.
Any ideas?

Interesting: if I rename node_modules/ses/dist/ses.cjs.js to ses.cjs.cjs, and update the exports.require key in node_modules/ses/package.json to match, then node t2.js works without problems. I think having it be named *.js in a package with type: 'module' tells node to treat it as a module, when it's clearly CommonJS format.
This doesn't help me use module-style imports yet, though.

Changing SES's package.json to say main: './dist/ses.cjs.cjs' and leaving exports.require alone (and leaving it at type: 'module') enables me to run node -r esm t.js (the form that does import { lockdown } from 'ses').

My best situation so far is when SES's package.json says:
type: 'module',
main: './dist/ses.cjs.cjs',
exports: {
 import: './src/lockdown-shim.js',
 require: './dist/ses/cjs.cjs',
 browser: './dist/ses.umd.js',
}

in which case:

node t2.js (the all-CJS case) works, with a warning about "Conditional exports is an experimental feature", including a call to lockdown()
node -r esm t.js (i.e. import 'ses') works without any warnings, including a call to lockdown()
node t.mjs (same code but different suffix) loads, warns about both ESM loader and conditional exports, but actually using lockdown() runs into #213

For reference, https://github.com/nodejs/node/blob/master/doc/api/esm.md#conditional-exports describes how exports is supposed to work. I wonder if -r esm only pays attention to main and not to exports.import.

Fixing with #217

We’ve addressed this issue with a cocktail of adjustments to how leaves on the dependency graph provide hybrid support for CJS, RESM, and ESM.
rollup config:

generate a dist .cjs file. The extension must be .cjs, not .cjs.js. RESM switches on the extension.
generate a dist .umd.js file.

package.json:

"type" is "module" (so Node.js will treat .js as .mjs rather than .cjs)
"main" must point to dist/name.cjs (so older versions of Node.js see CommonJS)
"module" must point to src/main.js (so tools like RESM use this instead of main)
"browser" must point to dist/name.umd.js (so tools like Rollup use this instead of main)
"exports.import" must point to src/main.js (so new Node.js versions use the ESM form)
"exports.require" must point to dist/name.cjs
"exports.browser" must point to dist/name.umd.js

This seems to cover all the bases.


Working Webpack/Angular2 example

Is it possible to get an example of this working with Webpack and possibly also Angular2?
I'm trying to import the built file in the vendor.js file with the following:
import 'node_modules/politespace/dist/politespace.js

And am triggering the enhance event on document every time the page changes in an Angular2 project like so:
export class AppComponent {
  constructor (private router: Router) {
    router.events.subscribe((val) => {
      $(document).trigger("enhance");
    });
  }
}

But I get an error on https://github.com/filamentgroup/politespace/blob/master/dist/politespace.js#L314 that Politespace is not defined.
Tracing the code to where Politespace is supposed to be defined, I can see that on https://github.com/filamentgroup/politespace/blob/master/dist/politespace.js#L189 in the demo code in this project, w is the Window object, whereas in Webpack, it seems to be an empty object, which is why line 314 above isn't recognizing Politespace.

Politespace is now using UMD with 1.0. It should work correctly.


Move symbol to new file isn't opening the new file

 Environment data

Language Server version: 2024.3.102
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda): Poetry, Python 3.12
python.analysis.indexing: true
python.analysis.typeCheckingMode: basic

 Code Snippet

class TypeToMove:
    pass

 Repro Steps

1.Hover on TypeToMove, click the light bulb and select "Move to new file"
 Expected behavior
The symbol moves to a new file with the symbol name, and the file opens in the editor
 Actual behavior
The file is successfully created but it doesn't open in the editor, so it seems as if it failed when it didn't
 Logs

pylance28032024logs.txt

From our perspective this is by design. See https://github.com/microsoft/pylance-release/issues/5217.
If you believe this is the wrong behavior, it would be an issue for vscode.

I thought that was the case only when auto save was enabled? in case it's disabled it'd still make sense to open the editor? 🤔

I thought that was the case only when auto save was enabled? in case it's disabled it'd still make sense to open the editor? 🤔

Yes, that's correct. Do you have files.refactoring.autoSave set to false? It's true by default.

Ah, I see. I was confusing it with the files.autoSave setting. Thank you :)


Rewrite V2G interval data generation process

As a developer of the genetics portal pipelines I want a reasonable v2g interval data, the structure of the current implementation is quite inefficient as @JarrodBaker  has pointed out.
Tasks

[ ] Review the existing codebase (genetics-v2g-data)
[ ] Test run existing implementation
[ ] Change output so the output files won't contain study level metadata required downstream.

TODOS:

Review The list of comments under the PR -> Apply modification on the etl repo if necessary.
Close PR on V2G.
Adding documentation to etl repo for the interval parser.


avoid use of undocumented custom source field in parsed uri

Trying to determine the origin of this field and if we can get rid of it:
https://github.com/Automattic/socket.io-client/blob/master/lib/index.js#L45
/cc @rase- @kevin-roark @rauchg
This field is non-standard for parsed URIs and causes confusing when debugging the parsed uri object.
Related to debugging invalid url parsing when a full url string is passed to io constructor and the incorrect port is detected.
Related PR to start fixing related issue: https://github.com/Automattic/socket.io-client/pull/797

Source started to be used here:
https://github.com/Automattic/socket.io-client/commit/99bfc07b9d9486b361b7a2046c096e2fd8fa43b2#diff-6d186b954a58d5bb740f73d84fe39073R59
But I am unclear on what was the underlying bug that this commit needed to fix.

Closed due to inactivity, please reopen if needed.


yew/scheduler: batch component update scheduling

Description
Micro optimization that removes the need to obtain refcell locks, clone Rcs and match update enums when scheduling a vector of component updates.
Checklist:

[x] I have run ./ci/run_stable_checks.sh
[x] I have reviewed my own code
[ ] I have added tests

[x] I have opened a PR against https://github.com/yewstack/js-framework-benchmark: https://github.com/yewstack/js-framework-benchmark/pull/11/checks?check_run_id=955329393

Looks great, thanks!


Detected blocking call to open inside the event loop (HA 2024.6)

Did you read the instructions?

[X] I have read the README, including the known-limitations section.

The problem
Got a lot of warnings on 2024.6 beta (600+ lines):

Detected blocking call to open inside the event loop by custom integration 'knmi' at custom_components/knmi/coordinator.py, line 90: timezone = pytz.timezone(API_TIMEZONE) (offender: /usr/local/lib/python3.12/site-packages/pytz/init.py, line 108: return open(filename, 'rb')), please create a bug report at https://github.com/golles/ha-knmi/issues

This might be related:
https://developers.home-assistant.io/blog/2024/05/19/fix_zoneinfo_blocking_io/
Integration version
2.1.0
Home Assistant version
core-2024.6.0b4
Python version
3.12.2
Home Assistant log
No response
Diagnostics
No response
Additional information
No response

beta 5 geeft nog meer info in de foutmelding:

Detected blocking call to open inside the event loop by custom integration 'knmi' at custom_components/knmi/coordinator.py, line 90: timezone = pytz.timezone(API_TIMEZONE) (offender: /usr/local/lib/python3.12/site-packages/pytz/init.py, line 108: return open(filename, 'rb')), please create a bug report at https://github.com/golles/ha-knmi/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 188, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self.args) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/knmi/init.py", line 75, in async_setup_entry await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2032, in async_forward_entry_setups await asyncio.gather( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2034, in  create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2081, in _async_forward_entry_setup await entry.async_setup(self.hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/binary_sensor/init.py", line 234, in async_setup_entry return await component.async_setup_entry(entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 196, in async_setup_entry return await self._platforms[key].async_setup_entry(config_entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 333, in async_setup_entry return await self._async_setup_platform(async_create_setup_awaitable) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 363, in async_setup_platform awaitable = create_eager_task(awaitable, loop=hass.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/knmi/binary_sensor.py", line 74, in async_setup_entry async_add_entities(entities) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 515, in async_schedule_add_entities_for_entry task = self.config_entry.async_create_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1134, in async_create_task task = hass.async_create_task_internal( File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 649, in async_add_entities await add_func(coros, entities, timeout) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 600, in _async_add_entities await coro File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 914, in _async_add_entity await entity.add_to_platform_finish() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1355, in add_to_platform_finish self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1000, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state state, attr, capabilities, shadowed_attr = self.__async_calculate_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1065, in __async_calculate_state if extra_state_attributes := self.extra_state_attributes: File "/config/custom_components/knmi/binary_sensor.py", line 108, in extra_state_attributes return self.entity_description.attr_fn(self.coordinator) File "/config/custom_components/knmi/binary_sensor.py", line 33, in  "timestamp": coordinator.get_value_datetime( File "/config/custom_components/knmi/coordinator.py", line 90, in get_value_datetime timezone = pytz.timezone(API_TIMEZONE)

I saw the blog post when it was published, but I thought it wouldn't affect this component since it is using pytz.timezone which wasn't mentioned. So thank you for reporting beta feedback!
The linked PR has a fix on top of 2024.6.0b6

Made a pre-release 2.2.0-b1 containing the fix

2.2.0 has been released containing a fix for this issue
https://github.com/golles/ha-knmi/releases/tag/2.2.0


API queue 1 for Hindiusm

Hindiusm is not a large site, but has a large number of troll answers that SD is sometimes slow to detect because of the queue.
Trailing comma per PEP8

Coverage remained the same at 65.795% when pulling 42a921b4e5cba604ded38a85411f0b0f4d24ef1b on normalhuman:patch-5 into 1ec4d24126a69790dc6a1241cbb9c8ef6f9c923a on Charcoal-SE:master.

We both did this at the same time. 8c7a56338acf9b30cf1930bdb3aed897a74bc768


BlobStoreTimeoutError should be supported for GCP

Unfortunately GCP does not provide straightforward timeout/retry configurations analogous to boto.
However, google.cloud.storage requests are forwarded all the way to the stdlib method requests.Session().request, which accepts a timeout keyword argument. Usage would look like:
import google.auth
import google.auth.transport.requests

connect_timeout = 1.0
read_timeout = 1.0
class Session(google.auth.transport.requests.AuthorizedSession):
    def request(self, *args, **kwargs):
        kwargs['timeout'] = (connect_timeout, read_timeout)
        return super().request(*args, **kwargs)

credentials, _ = google.auth.default()
gcp_client = Client(
    _http=Session(credentials)
)

The problem with this approach is Google may pull the rug out from under us by changing the _http argument:

:param _http: (Optional) HTTP object to make requests. Can be any object
that defines request() with the same interface as
:meth:requests.Session.request. If not passed, an
_http object is created that is bound to the
credentials for the current object.
This parameter should be considered private, and could
change in the future.

Things are a bit more promising for retry behavior, which appears configurable through a global:
import google.resumable_media.common
google.resumable_media.common.MAX_CUMULATIVE_RETRY = 2

@ttung thoughts?

For tests, I think you can pass in a _http object that sets timeout, but then proxies to the normal requests library.
Catching the exception should be relatively straightforward, no?

Yes, it's straightforward. I just wanted to make sure we're comfortable with using the private _http parameter.


" SAVE CHATGPT AS PDF " New Version NOV 12, 2024: Error message in Chrome browser

Hi PDFcrowd Team,
Like your CHROME extension:
" SAVE CHATGPT AS PDF " very much.
Good job!.
But suddenly,
the new version:
1.23 - Nov1 12, 2024 ,
has been automatically DEactivated
by my Chrome browser,
( latest version under LINUX ).
Chrome Error message at top right of Browser:
" Extension can Read and Change your Data on chat.com...".
[ ACCEPT ] or  [REMOVE ]  new Permissions buttons
Could you please,
clarify / confirm if all is OK, (or not),
to REactivate this wonderful extension? .
Why is Chrome DEactivating your Extension?.
Thanks! / Díky!
SFd99
San Francisco.
==============

Hi,
Thank you for reaching out.
OpenAI has purchased the domain chat.com and plans to move chatgpt.com to
chat.com, so our extension now supports both domains.
Please accept the new permissions to enable the extension.
If you like our extension, would you mind rating it with the link below? We
would appreciate that. Thanks!
https://chromewebstore.google.com/detail/save-chatgpt-as-pdf/ccjfggejcoobknjolglgmfhoeneafhhm/reviews?hl=en
Regards,
Pavel Mádr
pdfcrowd.com
{#HS:2762334912-15412#}
On Wed, Nov 13, 2024 at 20:15:08 CET, Pdfcrowd/save-Chatgpt-As-Pdf <
@.***> wrote:

Hi PDFcrowd Team,
Like your CHROME extension:
" SAVE CHATGPT AS PDF " very much.
Good job!.
But suddenly,
the new version:
1.23 - Nov1 12, 2024 ,
has been automatically DEactivated
by my Chrome browser,
( latest version under LINUX ).
Chrome Error message at top right of Browser:
" Extension can Read and Change your Data on chat.com...". [ ACCEPT ] or
[REMOVE ] new Permissions buttons
Could you please,
clarify / confirm if all is OK, (or not),
to REactivate this wonderful extension? .
Thanks!
SFd99 San Francisco. ==============

Reply to this email directly, view it on GitHub
https://github.com/pdfcrowd/save-chatgpt-as-pdf/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFYGNIYTYEOS5CDGXGHHUT2AOQLDAVCNFSM6AAAAABRXG5336VHI2DSMVQWIX3LMV43ASLTON2WKOZSGY2TMNJRGA2TMNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ok, Pavel.
1) Reactivated the extension.
2) Left a 5-Star review and Comment in Chrome Ext. Store.
Thanks for the quick response!.
If I may ask:
suppose a have a chatGPT Conversation
with 4 Messages,
(where each Message = my Question and the corresponding AI answer).
Can you please clearly describe, step-by-step,
how to:
a) save in the PDF,
ALL the Messages in a Conversation ?
VS
b)  save in the PDF
ONLY the 1st and 3rd Messages in a Conversation ?.
thanks!
RAY
San Francisco

Hi Ray,
Thank you for your review.
Here’s how you can save your messages in a PDF format for both scenarios:
a) Save ALL messages in the conversation to PDF:

Press the "Save As PDF" button.
Download the PDF file, which will contain all messages in the
conversation.

b) Save ONLY the 1st and 3rd messages in the conversation to PDF:

Select a portion of the 1st message using your mouse (for example,
the last word of your question and the first word of the AI's response).
Press the "Save As PDF" button and download the resulting PDF.
Repeat steps 1 and 2 for the 3rd message.
Go to our PDF merge tool at https://pdfcrowd.com/combine-files-pdf/.
Drag and drop the two PDF files (from steps 2 and 3) into the drop
zone.
Click the "Combine" button and download the final PDF file containing
only the 1st and 3rd messages.

Regards,
Pavel Mádr
pdfcrowd.com
{#HS:2762538673-15414#}
On Wed, Nov 13, 2024 at 23:56:33 CET, Pdfcrowd/save-Chatgpt-As-Pdf <
@.***> wrote:

Ok, Pavel.
1) Reactivated the extension.
2) Left a 5-Star review and Comment in Chrome Ext. Store.
Thanks for the quick response!.
If I may ask:
suppose a have a chatGPT Conversation
with 4 Messages,
(where each Message = my Question and the corresponding AI answer).
Can you please clearly describe, step-by-step,
how to:
a) save in the PDF,
ALL the Messages in a Conversation ?
VS
b) save in the PDF
ONLY the 1st and 3rd Messages in a Conversation ?.
thanks!
RAY San Francisco

Reply to this email directly, view it on GitHub
https://github.com/pdfcrowd/save-chatgpt-as-pdf/issues/1#issuecomment-2474991098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFYGNK5SQSQXEOMSFDZPFD2APKJJAVCNFSM6AAAAABRXG5336VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUHE4TCMBZHA
.
You are receiving this because you commented.Message ID:
@.***>

Very clear explanation.
Easy suggestion:
Add your explanation (above),
to the text extension "Description"
in the Chrome Web Store.
It will help many other users,
and make " SAVE CHAT AS PDF "
even more popular!. :-)
Thank you, Pavel
and have a very nice day.
RAY
San Francisco.


Roll engine 8df3eb80574e..0d60e1a324c8 (3 commits)

git@github.com:flutter/engine.git/compare/8df3eb80574e...0d60e1a324c8
git log 8df3eb80574e..0d60e1a324c8 --no-merges --oneline
2019-11-22<EMAIL_ADDRESS>Do not default to downstream affinity on iOS insertText (#13852)
2019-11-22<EMAIL_ADDRESS>Added auto-reviewer config file (#13962)
2019-11-22<EMAIL_ADDRESS>Roll src/third_party/dart 029e06b8d9..5b5f34f2e6 (10 commits) (#13982)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Auto-roller completed checks. About to merge.


Error: got an unexpected keyword argument 'max_new_tokens'

Seem to be getting a new error recently, not sure if it's because of the recent commit
Traceback (most recent call last):
  File "/root/whisper-diarization/diarize.py", line 97, in <module>
    whisper_results, language = transcribe_batched(
  File "/root/whisper-diarization/transcription_helpers.py", line 63, in transcribe_batched
    whisper_model = whisperx.load_model(
  File "/usr/local/lib/python3.10/dist-packages/whisperx/asr.py", line 334, in load_model
    default_asr_options = faster_whisper.transcribe.TranscriptionOptions(**default_asr_options)
TypeError: TranscriptionOptions.__new__() got an unexpected keyword argument 'max_new_tokens'

OS: ubuntu22.04
Python: Python 3.10.12

It's due to the version of whisperx referenced in requirements.txt. You can resolve the issue by updating the whisperx line in requirements.txt from
git+https://github.com/m-bain/whisperX.git@d6562c26da467ca49866a4173c0e723f3837f367
to
git+https://github.com/m-bain/whisperX.git
https://github.com/MahmoudAshraf97/whisper-diarization/issues/165

Thanks, that works.


Run in Stage 1 Mode

Great work. However I can not for the life of me figure out how to get Stage 1 Features (need decorators) working. I've been trying to import plugins manually in the configuration for most of the day now, and finally had to give up on it. Admittedly I am new to systemjs and babel. Any way you could add Stage 1 or maybe point me in the right direction?

This plugin does not come with stage 1 features as they are unstable and changing.
To add stage one with jspm you can do:
jspm install npm:babel-preset-stage-1

And then set:
System.config({
  babelOptions: {
    presets: ['babel-preset-stage-1']
  }
});

Thanks, I'll give that a go. Is there a certain directory that needs to be done from within?

No directory needed just the standard jspm install. If you're not using jspm, I'll see if I can get some docs together for that case as well. I posted https://github.com/systemjs/plugin-babel/issues/6 to track the documentation of this further.

@guybedford Thanks much! I truly appreciate it.


[Cosmos v4] evaluate possible NPE in GoneAndRetryWithRetryPolicy when accessing request

https://github.com/Azure/azure-sdk-for-java/blob/3e9b51beb5f5bc96f3e262445f256cea11108b8b/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/directconnectivity/GoneAndRetryWithRetryPolicy.java#L157
The code access request already without any null check then another null check later seems confusing.

This is fixed now.


publish @derekstride/tree-sitter-sql npm package

fixes #195
This sets up a workflow to publish to npm when PRs are merged into main.
I have a few open questions that anyone who has experience publishing to npm can help with:

Will we need to continually bump the version number in order to publish?
Should we instead use git tags to publish dedicated versions instead on every change?

cc// @rien

Will we need to continually bump the version number in order to publish?

yes, you can't republish the same version number

Should we instead use git tags to publish dedicated versions instead on every change?

I think this is a good idea! Especially because we don't have a way to control semver (there are things like conventional commit with npm plugins but they do require some discipline to use)

I've updated the PR to publish to npm on publish instead of during push to main. This will mean we need to publish an new release on Github before it get's pushed to NPM.
@dmfay @matthias-Q I'm all for adopting conventional commits & semantic versioning and starting to track breaking changes to the schema if both of you are on board as well. We can unofficially start now but should start ourselves & asking other contributors to follow the guidelines after this PR lands and we publish our first release.
I've also added a CONTRIBUTING.md file & included a section on commit messages to encourage the use of conventional commits as suggested. The file also explains how to run tests, run the github pages server, and prepare a release. I'd appreciate feedback & suggestions on the document as I want it to reflect a consensus on our thoughts for the project.

Any final comment or should I ship 🚢 this PR and publish our first release! 🎉

I say go for it.
(Tip: I have set up a pre-commit hook in my machine to check for conventional commits)

Published 🎉  https://www.npmjs.com/package/@derekstride/tree-sitter-sql


Segment fault while downloading vcpkg-glibc

Describe the bug
Hello I am trying to use vcpkg as my package manager.But when bootstrap-vcpkg.sh is run, I am getting Segmentation fault:
Environment

OS: ubuntu22.04

To Reproduce
$ ./vcpkg/bootstrap-vcpkg.sh
Downloading vcpkg-glibc...
Segmentation fault

Expected behavior
vcpkg-glibc should be downloaded successfully.
Failure logs
Segmentation fault

You can try to clone a vcpkg again, then run the ./bootstrap-vcpkg.bat command in the vcpkg directory and check the results.

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.


Add few simple search tests to mango

Overview
There are no functional changes, only additions to tests.
Testing recommendations
make mango-test MANGO_TEST_OPTS="26-test_query.TestQuery"

Related Issues or Pull Requests

Checklist

[ ] Code is written and works correctly
[x] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] Documentation changes were made in the src/docs folder
[ ] Documentation changes were backported (separated PR) to affected branches

I changed my mind. The shape of the tests in this PR is too different than other files in the test suite. Especially self.db.recreate() part.

I changed my mind. The shape of the tests in this PR is too different than other files in the test suite. Especially self.db.recreate() part.

Wonder if https://github.com/apache/couchdb/blob/main/test/elixir/test/search_test.exs would be a better place? Not a big deal I think if we had some mango tests in there as well, I think.


Possibility to patch object from yaml file

What problem are you facing?

I would like to install an operator with provider-kubernetes but the yaml is too long and complex to copy+paste it. This raw yaml file is available online on GitHub.
How could Crossplane help solve your problem?

It would be great if provider-kubernetes could allow patching from online yaml files.

Is this the same as https://github.com/crossplane-contrib/provider-kubernetes/issues/33 ?

Actually it is! I will close this one, thanks @bobh66


Maintain File Permissions when Copying Directories/Files on Linux and MacOS

When copying a directory or file in the file tree on Linux and MacOS, all of the file permissions in the destination file/directory get reset to 644.
VS Code should maintain file permissions.

@joaomoreno I am quite sure this code [1] is still from you from the old days ;). Maybe you could have a look and also apply it to the pipeFs() method where no mode is set.
[1] https://github.com/Microsoft/vscode/blob/master/src/vs/base/node/extfs.ts#L107

@bpasero the & 511 is mine: it just truncates the permissions but doesn't set them to 644. Something else is doing that.