text:
BUG: adding Buhring's analytic continuation method to special.hyp2f1; #8054

Overview
This pull request adds a new method of calculating the hypergeometric function hyp2f1 in the region where the standard transformation formulas for hyp2f1 fail. This method is based on the analytic continuation series given in W. Buhring, An Analytic Continuation of the Hypergeometric Series, SIAM J. Math. Anal., Vol. 18, No. 3, May 1987.
This new method is applied to the region of the complex plane given by:
0.9 <= |z| <= 1.1 and Re(z) >= 0.0 and |z-1.0| >= 0.75
Summary of what methods are used in each region of the complex plane
|z| > 1.1  ............................................................................  1/z transformation
|z| <= 1.1 and Re(z) < 0.0  ................................................  z/(z-1) transformation
|z| < 0.9 and Re(z) >= 0.0 .................................................  defining Taylor series for hyp2f1
0.9 <= |z| <= 1.1 and |z-1.0| < 0.75  .................................. 1-z transformation
0.9 <= |z| <= 1.1 and Re(z) >= 0.0 and |z-1.0| >= 0.75  ....  Buhring's analytic continuation series
Note that the transformations for hyp2f1 discussed above are given here. (They're also listed in Handbook of Mathematical Functions, M. Abramowitz and I. Stegun)
Expanded region that uses 1-z and z/(z-1) transformations
Besides implementing Buhring's series in the region where hyp2f1 was failing, I also slightly extended the region where the 1-z and z/(z-1) transformations are used so that both transformations are now used (in their appropriate regions) when |z| <= 1.1 instead of when |z| <= 1.0
My main motivation for this small expansion is the fact that the three methods that would get used in the ring 1.0 < |z| < 1.1 (i.e., Buhring's series, the 1-z and z/(z-1) transformations, see previous summary) all converge much sooner and are much faster than the 1/z transformation.
The only potential (but ultimately fixable) downside that I could find with the expansion of the 1-z region is related to the values we return for hyp2f1 on the branch cut (1, inf).  Specifically, on the branch cut of hyp2f1, the 1-z transformation converges to a different branch of hyp2f1 than the 1/z transformation does.
From a mathematical point of view this is okay since hyp2f1 is essentially multi-valued on the branch cut but it does mean that if one were to plot the real/imaginary parts of hyp2f1 on the real axis (1,inf), one would see a discontinuity at x=1.1.  To fix this, I've also added some code to the 1-z method so that it converges to the same branch of hyp2f1 that the 1/z transformation converges to (when z is on the branch cut).  This amounts to multiplying some prefactors in the method by a constant complex value.  I can give more details about this as needed.
Related issues
Closes #8054
Closes #8083

Note that the failure associated with the Travis CI checks is NOT related to my development. It involves some code with 'test_ndimage.py' and/or possibly Numpy deprecation warnings that were added recently...

Excuse my butting in, but is there anything in particular keeping this request from being pulled? I ran into this bug myself earlier today.

@brsr nothing in particular, it just needs reviewing. @FormerPhysicist apologies that we didn't get to this PR. The issue seems to be that this is quite technical code with only a few of the maintainers having the background (Fortran skills + special functions math) to review this.
I'll mark it for the next release, so we will at least revisit it before then. @person142 any chance you can have a look at this?

I’ll give it my best shot. Definitely not in the next week though so further pings might be needed...

@rgommers @person142 No worries about the delay; I keep an eye out over the next view weeks for any new comments/questions and try to respond to any new concerns you guys have.

Former@physicist.net

This looks fun! ping @person142 any chance this gets reviewed before we branch in 6 days?

@person142 What do you think? Do I need to bump the milestone again?

Unfortunately yes.

@FormerPhysicist @person142 No review activity in the last 6 months--I'm going to have to bump the milestone soon given branching in ~1 week unless you tell me otherwise.
My Fortran skills are improving but probably not strong enough to review this with confidence yet.

@FormerPhysicist @person142 No activity here in about a year--I'll probably have to bump the milestone?

Trying my hand at carrying this PR in #13310

To avoid this PR slipping another release, could we have some (re-)review?

To avoid this PR slipping another release, could we have some (re-)review?

Ping @person142 @tylerjereddy

@FormerPhysicist, @h-vetinari, @person142, @tylerjereddy
It's sad to see this languish so long. I'm a former mathematician and think I'm qualified to help review this. I can only spend 1-2 hours per week, but would it be helpful if I combed through and produced a technical report detailing the workings of the code that could aid a maintainer in their review process? At the rate of 1-2 hours per week I think I could have something in a couple months. I've been using some of my free time to brush up on my math anyway and had already begun diving back into complex analysis.

@steppi I suspect any help would be appreciated yeah. As Ralf noted, the combination of Fortran and very specialized math make this a big tricky for the current maintainer team.

As I start I can see if I'll have time this weekend or next to read Buhring's paper and write a clean and well documented reference implementation in pure python.

Bumping the milestone on this PR for the usual reasons--if activity does suddenly pick up here in the next few weeks feel free to ping me for milestone adjustment.

@FormerPhysicist, @h-vetinari, @person142, @tylerjereddy
I started looking into this. I think ideally it could be split into three pull requests to make review more manageable. One to address #8083, one to expand the regions where the (1-z) and z/(1-z) transformations are used, and one to address #8054. These are independent of each other and some are easier to review than others.
Also I propose instead of using Buhring's analytic continuation series to use the series from this paper by José Luis López, and Nico M. Temme. It doesn't require special handling when b - a is an integer, making it simpler to understand in my opinion, and it also appears to have better convergence in general. Instead of implementing in Fortran, I think it could be implemented in Cython and dispatched in _hypergeometric.pxd similar to what's being done currently with hyp1f1. I imagine there would be a (slight?) performance impact but I think it's worth it in terms of the gain in ease of review and maintenance.
Thoughts?

Thoughts?

Generally anything involving less Fortran 77 code is good; that's why you're seeing this somewhat in-progress movement of hypergeometric functions into Cython.

@person142 Yeah, that makes a lot of sense. I'll take a crack at putting together a Cython implementation of the series from the paper I linked when I have free time over the weekends.

I'll also note that any PRs moving the existing hypergeometric code into Cython (in small chunks at a time) will be gladly approved.

Cool. I'd be happy to chip away at that in my spare time.

I'll bump the milestone here again--my impression is that we're actually going to favor the effort by @steppi to avoid Fortran stuff anyway? So not sure if we can just drop the milestone entirely?

Yes, I think this has been superseded at this point so I'm going to close. Please correct me if wrong.

authors: FormerPhysicist brsr h-vetinari person142 rgommers steppi tylerjereddy


text:
Use quay.io/centos/centos:centos7 base image instead of mirrors.centos.org

Let's use quay.io/centos/centos:centos7 base image instead of mirrors.centos.org
pulling image from mirrors.centos.org is failing with this reason:
-> Version core: building image from 'Dockerfile' ...
-> Pulling image registry.centos.org/centos/centos:7 before building image from Dockerfile.
Get https://registry.centos.org/v1/_ping: dial tcp: lookup registry.centos.org on 172.31.0.2:53: no such host
Pulling image registry.centos.org/centos/centos:7 failed.
Let's wait 5 seconds and try again.
Get https://registry.centos.org/v1/_ping: dial tcp: lookup registry.centos.org on 172.31.0.2:53: no such host
Pulling image regis

Quay.io should be more stable

[test]

I have asked on CentOS container pipeline repository. Let's see.
https://github.com/CentOS/container-pipeline-service/issues/694

Peto, could you please add yum update to the Dockerfile? The image from quay.io is quite old.

After a discussion with team members we came to conclusion to stop support centos7 images and therefore this PR is not needed anymore.
Further action will take place in other Pull Requests.

source: gharchive/pull-request

authors: phracek zmiklank

license_type: permissive

license_source: bigquery


text:
Replace SAS s-mark file

Summary
This pull request suggests updating the version of the SAS "s-mark" file with one featuring a more visible registered trademark indicator.
Testing
Unfortunately, I am unsure how to test this change. I will need to ask for @scnwwu's help with this.

Closing with feedback from @scnwwu:

The logo is also used in the VS Code software and marketplace.
Are you suggesting changing the logo at all places or using a different one for documentation?
Using your new image by itself won't solve the problem.

We won't be attempting to swap the logo in all these locations, and for the sake of simplicity will maintain the current S-mark.

repo: scnwwu/vscode-sas-extension

license_source: github-api


text:
Improve the UI(user interface)

=>The library should be specifically explained what does it and what is it for...
=>The snap folder which we download should be a bit more organised
=>Should definitely improve the ui/ux of the website
=>Everything is too messed up in snap folder after we download it
=>Some components are missing in the algorithms like headerfiles are wrong,etc

Hey @kunalbhatia18
SNAP ( Stanford Network Analysis Platform ) is a graph mining library which serves as a pre-requisite to run BellyDynamic. SNAP is maintained by STANFORD and its development is maintained here - https://github.com/snap-stanford.

The SNAP library is well explained here - http://snap.stanford.edu/snap/
2 - 4 ) Development is maintained by Stanford
Can you point out which Algorithm are you talking about?
Can you please create an issue specific to BellyDynamic

source: gharchive/issue

repo: scorelab/BellyDynamic


text:
"Back to Project" button in the labeller

Is your feature request related to a problem? Please describe.
The labeller does not seem to have a button to go back to the project. I currently have to either change the URL or press the back button in the browser which can take multiple presses if more than one image was labelled.

Describe the solution you'd like
A "Back to Project" button in the labeller which takes the user back to the project which is being labelled.
Describe alternatives you've considered
The current "Back" button can also go back to the project if the current image is the first in the list.
Additional context
I am unsure if this feature doesn't exist or if there is a problem in my system due to which I am unable to see the button. If someone can confirm that this feature doesn't exist, I will work on implementing it.

@laksh22 my labeller page is just showing a blank white screen i dont know why.

Hi @mayursamnani36, your error should be fixed once PR #185 is accepted.

repo: scorelab/LabelLab


text:
upadate packages and paths

This PR updates npm packages and paths which caused errors while setting up the project

Could you please review this @charithccmc sir?

repo: scorelab/Webiu

license: MIT


text:
When opening Ribbon workbench from XRMtoolbox  no sollutions are shown

Hi,
When I open de Ribbon workbench from the XRMtoolbox there are no sollutions there. When I do the same within CRM then the sollutions are shown. DO I have to do something extra. No error Message is shown

The Ribbon Workbench will only show unmanaged solutions - do you have any unmanaged solutions?

This will happen when you have the OrgDbSetting SkipGettingRecordCountForPaging set to true
https://support.microsoft.com/en-us/topic/orgdborgsettings-tool-for-microsoft-dynamics-crm-20a10f46-2a24-a156-7144-365d49b842ba

authors: erwinsanders scottdurow

repo: scottdurow/RibbonWorkbench

license: mit


text:
Cannot extend custom SchemaObject and print not working properly

According to documentation, the following minimal code should be able to run and print the equivalente to the "toObject" output on the console:
main.js
let SchemaObject = require('schema-object');
let A = new SchemaObject({
	foo: String
});
let a = new A({
	foo: "Foo"
});
console.log( a );

let B = A.extend({
	bar: Number
});
let b = new B({
	foo: "Bar",
	bar: 10
});
console.log( b );

The following command is producing this error: node ./main.js
SchemaObjectInstance { foo: 'Foo' }
/home/bruno/Documents/Workspace/Html/minimal/node_modules/schema-object/dist/schemaobject.js:823
                                throw _iteratorError;
                                ^

TypeError: Cannot read property 'constructors' of undefined
    at _loop (/home/bruno/Documents/Workspace/Html/minimal/node_modules/schema-object/dist/schemaobject.js:786:84)
    at Function.extend (/home/bruno/Documents/Workspace/Html/minimal/node_modules/schema-object/dist/schemaobject.js:811:29)
    at Object.<anonymous> (/home/bruno/Documents/Workspace/Html/minimal/main.js:13:11)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:422:7)`

I am using npm 4.1.2 and node v7.6.0, on a linux mint (17.3) system, with schema-object version schema-object@4.0.10 extraneous
I am not sure if this is a configuration problem on my end, but I think it is correctly configured. I am new to this whole node, npm and Javascript thing, but I have a background that goes way back in programming.
My guess is that this is a problem related to Proxy, although I've no idea about what it does. Maybe a problem with it's interfacing (function calling).
According to the main page, since I am using a newer version, I don't have to use the harmony flag option. Even using it, these errors occur.

Ok, so here is a fix for this:
on line 765:
value: function extend(extendSchema, extendOptions) {
add the following code: extendOptions = extendOptions || {};
This will avoid the error from the previous post.
Unfortunately, the prints are still like this:
SchemaObjectInstance { foo: 'Foo' }
SchemaObjectInstance { foo: 'Bar', bar: 10 }
in roder to avoid the SchemaObjectInstance from appearing, if I use ...
console.log( a.toObject() );
console.log( b.toObject() );
... the output will be:
{ foo: 'Foo' }
{ foo: 'Bar', bar: 10 }
According to the documentation on the github page, this should be the default behavior, even for the case where I don't use the toObject method.
Anyway, I think this matter is mostly solved.

Ah, it's just that you aren't providing options and there isn't a default. I'll fix it and add a test for that behavior. Thanks for the report.
PS: The SchemaObjectInstance is just the way the console.log works, it's not actually having an impact on the serialization of the object.

I see. Thanks for the reply Scott.

@brunocanella FYI the new version is up on NPM now: 4.0.11

Just tested. It is working now. Thanks o/

authors: brunocanella scotthovestadt

repo: scotthovestadt/schema-object


text:
Is it possible for a WeMos D1 ?

Hi and hello!
i´m searching to use audio-reactive with my WeMos but all i tried seems not working...
maybe helpful...
Boot Vers: 31
CPU: 80
SDK: 2.1.0(deb1901)
Chip ID: 8073493
Flash ID: 1454108

Yes it's possible, that's the device I used for testing as well as a nodemcu

repo: scottlawsonbc/audio-reactive-led-strip


text:
Image causes text to be off-center

If you have two text fields one on top of the other with one being a regular EditText field and the other of this custom type and both have a gravity of center; then the text will not line up once the show/hide image appears.

Hey @ThomasSunderland thanks for raising this, do you have code/layout and/or screen shot of this issue.

Yes, it's a little hard to see in this one, but you can see that the text in the ShowHidePasswordEditText field is not centered with the text in the EditText field above it despite both of the fields being in line with one another and both having a gravity of center.

I guess a quick fix would be to add padding to the left of passsword edit text?

I think I had tried that and it moved the hide/show icon over as well, but I could be wrong

authors: ThomasSunderland scottyab

repo: scottyab/showhidepasswordedittext


text:
Splash is not rendering a pure JS page

I have used the following LUA code, it appears that it is not loading the page at all even if I increase the delay
function main(splash)
    splash.private_mode_enabled = false
    assert(splash:go(splash.args.url))
    splash:wait(10)
    assert(splash:runjs("document.getElementById('menu-item-expertises').nextSibling.click();"))
    splash:wait(30)
    return {
        html = splash:html(),
        png = splash:png(),
    }
end

I alway get a PNG with an empty page.
The URL in question is the following link
https://www.mandarine-gestion.com/
This website is pure VueJS file

I Think This can solve your problem.

authors: anvaari arunjoseph

repo: scrapinghub/splash


text:
fix tests for webengine request and add a invalid engine name test

The travis tests for #867  are failed with
E   AssertionError: 400 != 200 : (400,
'{"info": {"message": "Lua error: AttributeError(\\"\'QtImageRenderer\' object has no attribute
\'qimage_to_pil_image\'\\",)", "type": "LUA_ERROR"}, "description": "Error happened while executing Lua script",
"error": 400, "type": "ScriptError"}',
 'http://localhost:44451/execute?url=http%3A%2F%2Flocalhost%3A49991%2Fvery-long-green-page&viewport=50x1024&render_all=1&engine=webkit&lua_source=main+%3D+require%28%22emulation%22%29.render_png&wait=0.01')

https://travis-ci.org/scrapinghub/splash/builds/496767326
I also add a test for invalid engine name.

Thanks @lucywang000!


text:
A few small fixes

Hi team - Great library, we've enjoyed using it for a while now! Wanted to contribute back some fixes we've applied to our fork.

In RedisCluster, pass the tcpSendBufferSizeHint and tcpReceiveBufferSizeHint arguments through correctly.
Reduce the maxHashMisses in ClusterConnection before refreshing node info. The old value of 100 can lead to significant time with stale info.
ClusterConnection.delayed() was ignoring the delay argument passed in.
When a cluster is in the middle of migrating a slot, on the source node the slot info might look like [1129->-0af60d4b8d978d56f1d2b9f2f7ceb20fc43ecf01] (i.e. a MIGRATING state) and on the destination like [1129-<-0d704fe2d201af3c44ca23b0aef99a2dd5fd9222] (i.e. an IMPORTING state). This is instead of the typical valid number or range of numbers. This breaks ClusterRequests.parseClusterNode() when it does s.toLong. I believe the right thing to do here is to ignore any slot that is in an IMPORTING state but still consider a slot in a MIGRATING state as part of the node. The code reflects that now.

Those are very good catches, thanks for contributing!
could you try expose private val maxHashMisses as configuration parameter with default value 10?
If it causes any problems for current users it will only be a matter of changing configuration and no need to do additional release.
Other changes look good :+1:

Makes perfect sense. maxHashMisses is now exposed as a configuration parameter with default value 10.

Looking good, thanks!

Should be available in 2.3.4 version (needs a while to sync to mvn central)

authors: avistramer kpbochenek

repo: scredis/scredis


text:
🛑 Material Tetris is down

In c0338a8, Material Tetris (https://tetris.atanas.info) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Material Tetris is back up in eb42cfd.

repo: scriptex/uptime


text:
URIs for NALT are wrong - using 010/016 for URI generation

The example record (source xml, target rdf) gets the URI http://lod.nal.usda.gov/nalt/142 rather than the correct http://lod.nal.usda.gov/nalt/1396
Seems like vocabularies.yml must be updated to use the value of the 016 field rather than the 001 field.. My guess is that 010 or 016, if present, could always take precedence over 001 when it comes to URI generation, but I could be wrong here..

Not sure if this solution is general enough, but until we have a counterexample…

license: unlicense


text:
Typo in readme

The readme file has these lines:
" Align line-wise comment delimiters flush left instead of following code indentation
let g:NERDDefaultAlign = 'left'

But I think that 'left' should actually be replaced with 'start'.

Key @KidA424 thanks for the suggestion. The documentation could probably be clearer on this point, but this isn't actually a typo. The left and start modes are different in that both of them align left without following code indentation, the difference is one starts at the current indentation and the other is hard wired to start at the beginning of the line. Both should end up left aligned as described.

Thanks for letting me know!

repo: scrooloose/nerdcommenter


text:
error when clicked on markdown generated link

🐞 Bug report
Description
I have a link (/home/blog)  in my markdown  blog-post to blog-post-lust-view as shown below
When I click the link, site-map I am getting following error
libs-home-src-lib-home-module-es2015.js:902 problem during parsing static scully content TypeError: Cannot read property 'split' of undefined

Markdown blog
---
title: blog 1
description: This is the first demo blog in this sample.
---

# blog 1

## its a wild world after all

Related information [blog-2](/home/blog/blog-2)

[site-map](/home/blog)

🔬 Minimal Reproduction

💻Your Environment
Angular Version:

Scully Version:

🔥 Exception or Error
I think the error is caused at

https://github.com/scullyio/scully/blob/master/projects/scullyio/ng-lib/src/lib/scully-content/scully-content.component.ts#L75

Can you provide a repo that reproduces this? I seem unable to reproduce this scenario

https://github.com/xmlking/yeti

I will look at this tomorrow.

@xmlking

It works for me. I'm not sure what happens on your system?

Click site-map and see console logs

Ok, now I'm seeing the error.
It does not make sense, the error is on a page that doesn't (or at least should not) contain the scully-content component. yet the error is raised from there.
Can you provide more pointers on how this could happen?

@xmlking I found the root of the issue. Building a fix right now.

I still get error after going to blog page https://ngx-starter-kit.firebaseapp.com/home/blog/blog-4
then clicking on YETI  on the header

Are you sure you updated to the latest @scullyio/ng-lib ?

yes I am using 0.0.8.
how to reproduce.:
clone https://github.com/xmlking/yeti
yarn run scully:all
or
npx run scully:all

clicking links in blog posts works fine. even the site-map , but from block post, if you click YETI home link on the left, then you will see this error.

I also notices other problem, maybe related....
in the same repo run only angular ng serve
ng serve

then click blog post and then click , home. you will see scullyio-ng-lib.js:402 problem during loading static scully content  error
I dont have any scullyio in home(landing) page. why I do see this error when clicking /home linkk?

@xmlking That would be the same bug/reason. It looks like it regressed back somehow. going to check.

I looked into it. It isn't exactly the same bug, but closely related. Looking for a fix. Might take a day or 2.

I addressed this issue. I don't recall the exact PR, but it will be fixed when we drop the new version.
You can expect this to be later today. closing this now.
When you find any new regressions, please open a new issue, and refer this one.

authors: SanderElias aaronfrost xmlking

repo: scullyio/scully


text:
Cache doesn't work on multiple projects

🐞 Bug report
Description
🔬 Minimal Reproduction
💻Your Environment
Angular Version:

Scully Version:

🔥 Exception or Error

this is fixed by now

this is fixed by now


text:
fix(scully): tart background serer correctly in a non-angular app

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

@SanderElias Can you resolve the confflict?

authors: SanderElias jorgeucano


text:
Broken pytest with 8.3.4 only on Azure

I am unable to reproduce but our azure runners broke with the latest pytest:
https://dev.azure.com/scverse/anndata/_build/results?buildId=8969&view=logs&j=5ea502cf-d418-510c-3b5f-c4ba606ae534&t=13a40d21-d359-5a41-b91d-835dd35380e7&l=23328

did you report this upstream?

I made this as a reminder because I couldn't put together a reproducer ATM (it wasn't happening locally).  Happy to try again.

authors: flying-sheep ilan-gold

repo: scverse/anndata


text:
(feat): add methods for changing settings

[x] Towards #890 - solving the issue will simply require calling settings.register for the needed variable
[x] Tests added
[x] Release note added (or unnecessary)

I am aware this was not your top choice @flying-sheep but you also didn't seem so jazzed about scanpy's solution either.  So I finished this up. If we want something different, we can go for it.  I think the best option might be something shared between scanpy and anndata.  What do you think?  Short of that, despite the unpythonic nature of this, it is quite simple IMO which is a big plus.

@flying-sheep I'm fine with imitating scanpy.  You sounded fairly negative about it, so I guess it didn't seem like it mattered if we used one "bad" solution or another.  Do you think this should be built with scanpy in mind i.e., migrating scanpy to whatever we do here (in some capacity)?

Wow ok @flying-sheep, I finally did it.  __signature__ was the key - __annotations__ did not really help with the tab completion but __signature__ did (and you can see that even that was not so straightforward).  If you want to test out tab completion here is something:
import anndata as ad

test_option_doc = "doc string!"
test_option_env_var = "ANNDATA_TEST_VAR"
test_option = "test_var"
default_val = False
test_doc = f"""\
{test_option}: bool
    My doc string!
"""

test_option_doc_2 = "doc string 2!"
test_option_env_var_2 = "ANNDATA_TEST_VAR 2"
test_option_2 = "test_var_2"
default_val_2 = False
test_doc_2 = f"""\
{test_option_2}: bool
    My doc string 2!
"""

def validate_bool(val, option):
    assert val in [True, False], f"{val} not valid boolean for option {option}."

ad.settings.register(
    test_option, default_val, test_doc, lambda v: validate_bool(v, test_option)
)

ad.settings.register(
    test_option_2, default_val_2, test_doc_2, lambda v: validate_bool(v, test_option_2)
)

Have a look!  Now that I'm writing this, I would like to get the docstring working as well.  Will do.

From meeting: make some sort of freeze method so that downstream users can't edit the underlying object.

List of features that might be enabled by this branch:

https://github.com/scverse/anndata/issues/610
https://github.com/scverse/anndata/issues/890
https://github.com/scverse/anndata/issues/1112

I think these are all pretty advanced use-cases.
Other things I could see us moving into some sort of settings:

If/when we transition to xarray, assuming we stick with the same AnnData object, a variable for using the "experimental" xarray implementation (instead of releasing via experimental)
io engines (rust or tensorstore or the like for zarr?)
mutability behavior (see https://github.com/scverse/anndata/issues/742)

Honestly, though, these first two potential use-cases should probably not be set via an environment variable and is far as the third should, it would be under the "only if you know what you're doing" banner.  But not sure it's an env variable situation anyway.
At the end of the day, most of pandas and xarray's settings are about display and/or dependencies and we just don't do either too much at the moment (and in so far as we do external dependencies, this has been handled differently).  Furthermore, display only really matters in IPython settings, where autocomplete is present as things stand.  So I guess I really only see this as being "do this if you know what you're doing" as far as VSCode audience goes.  I'd be fine leaving things as is especially given the numerous advantages of the current approach (it's extendable, has deprecation warnings, and is very clean).

List of features that might be enabled by this branch:

I would also include the path towards:

https://github.com/scverse/anndata/issues/746

For controlling if we auto convert to these, which we should do eventually.

pandas and xarray's settings are about display and/or dependencies and we just don't do either too much at the moment

Pandas does do feature flags for upcoming behaviour with settings flags. For example, copy on write.

I would still describe these as "advanced use-cases."  We don't have arguments like N_PCS from scanpy or the like which are important and could be oft used.

In that case, I fully agree with

So I guess I really only see this as being "do this if you know what you're doing" as far as VSCode audience goes.

and like the current design. Maybe we should document that it’s only for advanced use cases.

@flying-sheep @ivirshup I addressed your comments and cleaned up the docs a bit.  Please see https://github.com/scverse/anndata/pull/1340 for the first "implementation" if it will help with the review here.  I am happy with the state of things and am ready to merge.

authors: flying-sheep ilan-gold ivirshup


text:
Got AttributeError: Can only use .str accessor with string values! when initiating solo model

[x] I have checked that this issue has not already been reported.
[x] I have confirmed this bug exists on the latest version of scanpy.
[ ] (optional) I have confirmed this bug exists on the master branch of scanpy.

I did create model with adata
import scvi
scvi.model.SCVI.setup_anndata(adata)
vae = scvi.model.SCVI(adata)
vae.train()

initialize the model using the scvi.model.SCVI object
solo = scvi.external.SOLO.from_scvi_model(vae)

And I got AttributeError
AttributeError                            Traceback (most recent call last)
Cell In[29], line 1
----> 1 solo = scvi.external.SOLO.from_scvi_model(vae)

File ~/miniconda3/envs/scanpy/lib/python3.10/site-packages/scvi/external/solo/_model.py:204, in SOLO.from_scvi_model(cls, scvi_model, adata, restrict_to_batch, doublet_ratio, **classifier_kwargs)
    199     doublet_adata = AnnData(
    200         np.concatenate([doublet_latent_rep, np.log(doublet_lib_size)], axis=1)
    201     )
    202     doublet_adata.obs[LABELS_KEY] = "doublet"
--> 204     full_adata = latent_adata.concatenate(doublet_adata)
    205     cls.setup_anndata(full_adata, labels_key=LABELS_KEY)
    206 return cls(full_adata, **classifier_kwargs)

File ~/miniconda3/envs/scanpy/lib/python3.10/site-packages/anndata/_core/anndata.py:1808, in AnnData.concatenate(self, join, batch_key, batch_categories, uns_merge, index_unique, fill_value, *adatas)
   1799 pat = rf"-({'|'.join(batch_categories)})$"
   1800 out.var = merge_dataframes(
   1801     [a.var for a in all_adatas],
   1802     out.var_names,
   1803     partial(merge_outer, batch_keys=batch_categories, merge=merge_same),
   1804 )
   1805 out.var = out.var.iloc[
   1806     :,
   1807     (
-> 1808         out.var.columns.str.extract(pat, expand=False)
   1809         .fillna("")
   1810         .argsort(kind="stable")
   1811     ),
   1812 ]
   1814 return out

File ~/miniconda3/envs/scanpy/lib/python3.10/site-packages/pandas/core/accessor.py:224, in CachedAccessor.__get__(self, obj, cls)
    221 if obj is None:
    222     # we're accessing the attribute of the class, i.e., Dataset.geo
    223     return self._accessor
--> 224 accessor_obj = self._accessor(obj)
    225 # Replace the property with the accessor object. Inspired by:
    226 # https://www.pydanny.com/cached-property.html
    227 # We need to use object.__setattr__ because we overwrite __setattr__ on
    228 # NDFrame
    229 object.__setattr__(obj, self._name, accessor_obj)

File ~/miniconda3/envs/scanpy/lib/python3.10/site-packages/pandas/core/strings/accessor.py:181, in StringMethods.__init__(self, data)
    178 def __init__(self, data) -> None:
    179     from pandas.core.arrays.string_ import StringDtype
--> 181     self._inferred_dtype = self._validate(data)
    182     self._is_categorical = is_categorical_dtype(data.dtype)
    183     self._is_string = isinstance(data.dtype, StringDtype)

File ~/miniconda3/envs/scanpy/lib/python3.10/site-packages/pandas/core/strings/accessor.py:235, in StringMethods._validate(data)
    232 inferred_dtype = lib.infer_dtype(values, skipna=True)
    234 if inferred_dtype not in allowed_types:
--> 235     raise AttributeError("Can only use .str accessor with string values!")
    236 return inferred_dtype

AttributeError: Can only use .str accessor with string values!

I did try to eleminate empty cells, but it didn't work
Versions

anndata     0.9.1
scanpy      1.9.3
PIL                         9.4.0
absl                        NA
asttokens                   NA
attr                        22.1.0
backcall                    0.2.0
beta_ufunc                  NA
binom_ufunc                 NA
brotli                      NA
certifi                     2022.12.07
cffi                        1.15.1
charset_normalizer          2.0.4
chex                        0.1.7
colorama                    0.4.6
comm                        0.1.2
contextlib2                 NA
cycler                      0.10.0
cython_runtime              NA
dateutil                    2.8.2
debugpy                     1.5.1
decorator                   5.1.1
defusedxml                  0.7.1
docrep                      0.3.2
executing                   0.8.3
flax                        0.6.1
fsspec                      2023.4.0
gmpy2                       2.1.2
h5py                        3.8.0
hypergeom_ufunc             NA
idna                        3.4
igraph                      0.10.3
invgauss_ufunc              NA
ipykernel                   6.19.2
ipython_genutils            0.2.0
ipywidgets                  8.0.4
jax                         0.4.8
jaxlib                      0.4.7
jedi                        0.18.1
joblib                      1.2.0
jupyter_server              1.23.4
kiwisolver                  1.4.4
leidenalg                   0.9.1
lightning_fabric            1.9.4
lightning_utilities         0.8.0
llvmlite                    0.39.1
matplotlib                  3.7.1
matplotlib_inline           0.1.6
mkl                         2.4.0
ml_collections              NA
ml_dtypes                   0.1.0
mpl_toolkits                NA
mpmath                      1.2.1
msgpack                     1.0.5
mudata                      0.2.2
multipledispatch            0.6.0
natsort                     8.3.1
nbinom_ufunc                NA
ncf_ufunc                   NA
nct_ufunc                   NA
ncx2_ufunc                  NA
numba                       0.56.4
numpy                       1.23.5
numpyro                     0.11.0
nvfuser                     NA
opt_einsum                  v3.3.0
optax                       0.1.5
packaging                   23.1
pandas                      2.0.1
parso                       0.8.3
pexpect                     4.8.0
pickleshare                 0.7.5
pkg_resources               NA
platformdirs                3.2.0
prompt_toolkit              3.0.36
psutil                      5.9.0
ptyprocess                  0.7.0
pure_eval                   0.2.2
pydev_ipython               NA
pydevconsole                NA
pydevd                      2.6.0
pydevd_concurrency_analyser NA
pydevd_file_utils           NA
pydevd_plugins              NA
pydevd_tracing              NA
pygments                    2.15.1
pyparsing                   3.0.9
pyro                        1.8.4+9ed468d
pytorch_lightning           1.9.4
pytz                        2023.3
requests                    2.28.1
rich                        NA
scipy                       1.10.1
scvi                        0.20.3
seaborn                     0.12.2
session_info                1.0.0
setuptools                  66.0.0
six                         1.16.0
skewnorm_ufunc              NA
sklearn                     1.2.2
skmisc                      0.1.4
socks                       1.7.1
stack_data                  0.2.0
statsmodels                 0.13.5
sympy                       1.11.1
texttable                   1.6.7
threadpoolctl               3.1.0
toolz                       0.12.0
torch                       2.0.0
torchmetrics                0.11.4
torchvision                 0.15.0
tornado                     6.2
tqdm                        4.65.0
traitlets                   5.7.1
tree                        0.1.7
typing_extensions           NA
unicodedata2                NA
urllib3                     1.26.15
wcwidth                     0.2.5
yaml                        6.0
zmq                         23.2.0
zoneinfo                    NA
IPython             8.12.0
jupyter_client      8.1.0
jupyter_core        5.3.0
jupyterlab          3.5.3
notebook            6.5.4
Python 3.10.10 | packaged by conda-forge | (main, Mar 24 2023, 20:08:06) [GCC 11.3.0]
Linux-5.19.0-40-generic-x86_64-with-glibc2.35
Session information updated at 2023-04-26 05:02

Thanks for your help

Hi @lconan, thank you raising this issue. Looks like it has already been fixed via #2013, it should be available with the next version release, or you can reinstall scvi again from the main branch if needed.

sorry I didn't realize they were the same. Will try soon

repo: scverse/scvi-tools


text:
Mixed usage of n_samples_overall in get_normalized_expression

In TOTALVI.get_normalized_expression, MULTIVI.get_normalized_expression, and ContrastiveVI.get_normalized_expression, n_samples_overall just downsamples indices, while in RNASeqMixin.get_normalized_expression, it's used for the number of MC inference samples. This might be confusing for users who expect the argument to mean and do the same thing across methods.

@PierreBoyeau  Currently this means that these other function don't use importance weighting? I assume it would make sense to add it to these models as well?

I think we can improve the naming as well (but that's styling and I would stick to n_samples_overall for number of mc_samples and n_samples to number of samples for a single input cell in a forward pass.


text:
Remove datastax auth providers from driver

For auth classes that are exposed int the api, move them to ./datastax folder.
For unit tests for those classes, move them to ./deprecated folder

Why base-dse-authenticator.js is removed, but base-dse-authenticator.js is moved to datastax/deprecated?

You asking for the same file.
But if I understand that question correctly, those files moved to ./datastax directory are exposed in the API, while the deleted file is not.


text:
IndexOutOfBoundsException

For breaking error #111
Reproduce using ArticleController#setResourceSpecificProperties

Not a serious patch, but perhaps time saver for others that encounter this issue.

repo: sdaschner/jaxrs-analyzer


text:
Change request - NAM Trainer GUI - Add a button that will interrupt training and complete process (deliver a .nam file)

Can we somehow add a button to this that would stop the trainer at the next possible Epoch completion and then proceed to finalize the process from there (and deliver the ESR graph and .nam file)?
The use case would be when you set up a 1,000 Epoch training session and at some point you see your Checkpoints reporting a super low ESR already, so you just want to end it.

Resolved by #118

Aw heck yea!
On Tue, Mar 7, 2023 at 8:13 PM Steven Atkinson @.***>
wrote:

Closed #117 https://github.com/sdatkinson/neural-amp-modeler/issues/117
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/sdatkinson/neural-amp-modeler/issues/117#event-8692312891,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4VWJOYJRQRFIOEG66USBSDW27TNTANCNFSM6AAAAAAVP5OCIU
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

repo: sdatkinson/neural-amp-modeler


text:
[FEATURE] NPU support

I'm planning to upgrade my laptop and I'm curious is NPU support is planned for Neural Amp Modeller?
Thank you

I'll have the trainer will support any accelerator that's supported by PyTorch Lightning.
As far as running real-time models, that's NeuralAmpModelerCore's scope, and I haven't looked into NPU support there. At a glance, it doesn't seem worth it to me--the typical model for NAM is super-tiny.

authors: novikov-alexander sdatkinson


text:
picker初始化后，调用setValue来设置默认值，不生效。

picker初始化后，调用setValue来设置默认值，不生效。

请详细描述你的问题！

我遇到同样的问题,就是当picker初始化之后,调用setValue方法不工作. 除非你展开picker一次之后setValue才工作

详细描述就是如何设置默认值!!!!!!!!!!!!!!!!!!!!!!!!!!!!

authors: virtuecai wangbagang weiming8202 wggCode

repo: sdc-alibaba/SUI-Mobile


text:
GRIP 3.c.1

Currently the data used in the GIF (old and new) is from the Canadian Institute for Health Information (CIHI) but during a meeting last week, it was mentioned there might be a better source for this information?

Look into LFS or Census please

LFS has an annual table, update with

[ ] Statistics Canada. Table 14-10-0202-01  Employment by industry, annual

using official metadata for calculations

authors: MaiaPelletier catherinemichaud


text:
Add a link for deploying with Pulumi

This links to Pulumi's actions repo. GitHub Actions plus Pulumi deploys any app to any cloud, including Kubernetes, and previews changes in the PR flow before actually deploying them. That repo contains the actions definitions, in addition to listing lots of handy getting started information, including

Intro Blog Post
Rails App from GitHub Universe Keynote
Getting Started Guide
Other articles and videos for how to have fun with Actions!

Great, thank you!

authors: joeduffy sdras

repo: sdras/awesome-actions


text:
Comments not appearing for any files other than READMEexample

Can't supply my store.js as that'd be revealing confidential information, but I'm wanting to use this internally for a presentation. I'll probably miss my chance today but oh well.
The issue is that I can't add comments to any files other than READMEexample. I can change the contents of that comment, but supplying any path, whether that's any of:
project-name/app/models/model.rb
project-name/app/models/model
app/models/model.rb
app/models/model
model
model.rb

will not result in a comment being added for that file in the view.
I've also tried renaming the project to projectname rather than project-name.
Feel free to drop this if it can't be replicated.

Hi there- it's hard for me to debug because I don't know your project structure, but there is a working example of how it should be set up here: https://github.com/sdras/vue-directory-tree/blob/master/src/store.js, maybe you could use that example to guide you? Thanks.

authors: boardfish sdras

repo: sdras/project-explorer


text:
create a help page

This is a relatively simple PR. There is a new file help.vue which corresponds to ``https://politicry.com/help`.
The page has two variants, depending on where the extension is installed or not. If the extension is installed, we don't need to show the installation section.
This PR updates the "help" link in the extension popup to point to the new help website. The extension will append #/ to the end of the URL when it opens it. The website checks if the URL ends with #/ and if so, it hides the installation section. This is the easiest way to check if the extension is installed. Alternative solutions are more complex and would further decrease the maintainability of this codebase, with very little benefit.
Todo

[x] Create https://politicry.com/help
[x] Write tests for https://politicry.com/help
[x] Update the extension popup to open https://politicry.com/help when it's first installed
[x]  Update the extension popup to link to the help page
[x] Write tests for the automatic page opening
[x] Hide the installation section of the help page if the extension is already installed

This works because the extension will always append #/ to the help URL before opening it. The website can detect this.

[x] Unrelated: change the version number to 2.0.0 for Assignment 3 and reduce the number of places where the version number is duplicated, by loading the version number from the manifest.json file.

Motivation
The UI might be intimidating for new users since there are lots of options but no exaplanation of how anything works.
Attached GitHub issue
Closes #106
Checklist
Documentation

[x] Updated the readme documents (README.md etc.)
[x] New functions and methods have additional comments added to document their usage

Local Build

[x] Ran all pre-commit hooks pre-commit run --all-files
[x] Extension has been tested to build correctly cd extension && yarn && yarn build
[x] Backend has been tested to build correctly cd backend && docker-compose build
[x] Extension test suite has been run locally cd extension && yarn && yarn test
[x] Backend test suite has been run locally cd backend && python3 -m unittest

GitHub

[x] Target branch has been set correctly
[x] PR has been rebased onto target branch
[x] PR has been assigned an owner
[x] Author has performed a self-review of the code
[x] Removed the WIP message from the top of this PR

@Destiny-02 done


text:
rethinking of module id in libs

这个问题不简单，参考之前的思考 #100
需求可整理成：

可以多版本共存
支持 combo
模块代码可内嵌到页面
尽量能支持直接 require('jquery/1.6.4/jquery')

方案一
jquery/1.6.4/jquery.js:
define('jquery', ...)

main.js:
seajs.config({
  alias: {
    'jquery': 'jquery/1.6.4/jquery'
  }
});

define(function(require) {
  var $ = require('jquery');
});

fn-define.js 中，对 define 参数中的 id 不 parseAlias

方案二
jquery/1.6.4/jquery.js:
define('jquery', [], factory)

main.js:
seajs.config({
  alias: {
    'jquery': 'jquery/1.6.4/jquery'
  }
});

define(function(require) {
  var $ = require('jquery');
});

fn-define.js 中，对 define 参数中的 id 不 parseAlias
不足

由于对 define 中的 id 不 parseAlias，意味着内嵌模块的写法很严格，不能有 alias. 在实际应用中不方便。
memoize 模块时的 id 和 require 时的 id 不一致，要对应上的话，内部实现会很麻烦，特别考虑 combo 情况时。

方案三
jquery/1.6.4/jquery.js:
define('#jquery/1.6.4/jquery', [], factory)

main.js:
seajs.config({
  alias: {
    'jq162': 'jquery/1.6.2/jquery',
    'jq164': 'jquery/1.6.4/jquery'
  }
});

define(function(require) {
  var jq162 = require('jq162');
  var jq164 = require('jq164');
});

fn-define.js 中，对 define 参数中的 id 会 parseAlias
好处

由于使用了 top-level id, 意味着可以 combo 和内嵌到页面中。
有 top-level id, 意味着可多版本并存。
没有 alias 时，可以直接用 require('jquery/1.6.4/jquery') 来获取。

不足

增加一个约定：id 前的 # 表示不需要 parseAlias

repo: seajs/seajs


text:
循环引用，不提示错误，也不运行：

循环引用，不提示错误，也不运行：
a.js
define('a',function(require,exports,module){
var b = require('./b');
b.say()
exports.say = function(){
alert('hello a')
}
});
b.js
define('b', function(require, exports, module) {
var a = require('./a');
a.say('a')
exports.say = function(){
alert('hello b')
}
});
sea.html

确实比较坑,当没有发现是循环引用的问题时,没有任何提示.找了很久也不知道原因所在.支持重构解决循环依赖的问题,不过要是有插件能发现就不会掉进去出不来了.

建议假如有循环依赖还是可以执行,执行到循环依赖处再停止会比较好

建议假如有循环依赖还是可以执行,执行到循环依赖处再停止会比较好

authors: ericktang zdjray


text:
Get template version schema by versionId

Is your enhancement related to a problem? Please describe.

Describe the solution you'd like

Now get the schema of all template versions in one request.
There may actually be hundreds of versions of a template，resulting in too much data for an request.

Describe alternatives you've considered

Get one version schema, in one request.

Additional context

Added support to get version schema by versionID

authors: aiwantaozi hibig

repo: seal-io/walrus


text:
[Request] 后台指令测试界面可以完善一些？

譬如，除了模拟一对一的对话，还可以模拟群组聊天。
我设想的是，用户可以选择不同的身份（群主/管理员/邀请人/骰主/普通人/黑名单）与骰子私聊或者群聊，这样可以减少必须注册多个账号测试骰子的繁琐性以及由此导致的封号风险。

加假人之后, 就更需要给每个假人使用不同的头像了! 哪怕是用序号生成一个只有数字的图片也行.
另外, 由于用户可以轮流控制多个假人, UI聊天记录的展示方式或许也要调整. 比如把所有气泡都靠左, 或者按照当前假人重新排列左对齐和右对齐.
Ref #99

目前一个简单的构想是这样的

先做了一个初步的支持，测试功能中约定如下：
1xxx 由用户使用，用户统一 ID 以 UI: 开头，如目前 UI:1001 模拟私聊用户，UI:1002 模拟群聊群主。
2xxx 由群组使用，群组统一 ID 以 UI-Group: 开头，如 UI-Group:2001 为目前模拟的唯一群聊（群主为 UI:1002）。

authors: JustAnotherID Verplitic Xiangze-Li

repo: sealdice/sealdice-core


text:
feat: PLS-431

Details

Updated dependencies
Used seal-node:oss-module-update

Breaking Changes
References
https://jira.sealsystems.de/jira/browse/PLS-431
Introduction to Pull Requests

Please read before submitting your first pull request!

Thank you for creating a pull request. We really appreciate your effort!
Here is some information to help you integrate your changes as easily as possible into the next release.
Title Field
The title is one of the most important aspects of a pull request. The content is shown in CHANGELOG.md and release notes. Therefore, be sure to summarize your changes in a short but catchy sentence. Others should be able to easily get an idea of your changes.
By adding keywords at the beginning of the title, you can control the process of merging and releasing your pull request. Here is the list of all available keywords:

WIP:
It is highly recommended to open a pull request as soon as possible. This allows discussions during code development and not just criticism after work is done.
Please start a new pull request with the prefix WIP:. This signals to others that is is not yet ready to be merged into the master branch. It also prevents our bot from merging. (See section "Merging into Master" below)
After the changes and the pull request description have been completed, remove this prefix. In this case, review requests may be automatically generated to ensure, e.g., the compatibility of your description with our release notes format.

feat:
A pull request with this prefix in its title is marked as a new feature. In general this creates a minor release when merging the pull request into the master branch. A label with the expected release type is added to the pull request.

fix:
A pull request with this prefix in its title is marked as a bugfix. In general this creates a patch release when merging the pull request into the master branch. A label with the expected release type is added to the pull request.

chore:
A pull request with this prefix in its title is marked as a maintenance change. In general this creates a patch release when merging the pull request into the master branch. A label with the expected release type is added to the pull request. Only CHANGELOG.md, but not our release notes, will be updated with information about the pull request.

You can specify the kind of pull request when you create a new one. But do not forget to prefix it with WIP:. Here is an example title for such a pull request:
WIP: feat: My super cool new feature

After finishing the work, you can simply remove WIP:.
Please do not format the Title field with Markdown.
Description Field
Besides this introduction, the description field also contains sections with the following headings which contribute to CHANGELOG.md and release notes:

Details
Sometimes it is not possible to explain a change with a single short line in the Title field. In this case, you can add a more detailed description in the Details section.
You may add several paragraphs if needed and unlike the Title field, you can format the content with Markdown.

Breaking Changes
Please fill out this section if and only if your changes affect the public Interface. This creates a major release when merging the pull request into the master branch. Breaking changes are shown in an additional section of CHANGELOG.md and release notes. So two headings will be created: One for the bugfix/feature itself and one for the breaking changes.
All information for the Details section also applies here, with one important exception:
In contrast to the Details section, the first line is used as a title for the breaking change. Therefore, please add a short description first and append paragraphs for more information if needed. Do not start with a large paragraph and do not format the first line.
Here is an example of a longer text for a breaking change:

This is a brief description of the breaking change (without a punctuation mark and formatting)
In another paragraph, I add detailed information of steps needed to adapt to the new interface. I can also format this paragraph using Markdown.
I can add as many paragraphs as needed.

The first line is shown as a heading and the following paragraphs as normal text.
Use this section only to describe the changes to the interface and how to adapt to the new version. Use the Details section to provide information about the bugfix/feature itself.

References
Here you can enter links to Jira oder Github. This allows you to provide more information about the background of your code changes.
Add one link per line without any other text.

Please make sure that you leave a blank line between the headings and the beginning and end of your text.
Merging into Master
After all reviews have been successfully completed, you are ready to merge your pull request into the master branch. This is only possible if all required automated tests pass.
You cannot use the green "Merge" button. Instead you must add a special comment containing only the following command:
/merge

This causes our merge bot to merge the pull request using a commit message consisting of the various pieces of information in the Title and Description fields.
The branch is automatically deleted after a successful merge. If you do not have permissions to commit to the repository, a comment containing an error message is created.

/merge

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: comgit seal-mbo

repo: sealsystems/node-mongo


text:
Bad protocol version

I'm getting an error i have never seen before, this used to work just last week.
Accessing the site via Firefox or through curl still works fine
OS: macOS Sonoma Dev Beta 3 (updated from Ventura to try to solve this issue)
Arch: aarch64
Error (api key removed from error message):
Error: reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("jf.radical.fun")), port: None, path: "/Sessions", query: Some("api_key="), fragment: None }, source: hyper::Error(Connect, Error { code: -9836, message: "bad protocol version" }) }

Code:
&reqwest::get(format!(
    "{}/Sessions?api_key={}",
    config.jellyfin.url.trim_end_matches('/'),
    config.jellyfin.api_key
))
.await?
.text()
.await?

Entire rust file
Cargo.toml:
[package]
name = "jellyfin-rpc"
version = "0.14.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
discord-rich-presence = "0.2"
colored = "2.0"
retry = "2.0"

[dependencies.clap]
features = ["derive"]
version = "4.1"

[dependencies.reqwest]
features = ["default", "default-tls", "hyper-tls", "native-tls-crate", "tokio-native-tls", "json"]
version = "0.11"

[dependencies.tokio]
features = ["full"]
version = "1"

I'm sorry if this is not related to reqwest but I cant find much about this online

I think that's because native-tls is using macOS' security-framework for TLS. I found that the error code -9836 matched the bad protocol version. So, that makes me think it's complaining about a TLS version from the server.
I don't have a Mac, so I can't check more. But hopefully that helps you narrow down the problem more. And I dont think it's related to reqwest.

It sounds weird that macOS would be complaining about TLS v1.3

After rebooting to linux the issue disappears, nice one apple..

authors: Radiicall seanmonstar

repo: seanmonstar/reqwest


text:
Enviroment Proposal

Hello, we are using a lot overnight and it is fantastic, we miss a more sophisticated environment management, I have a library that does environment management (https://www.npmjs.com/package/roit-environment) is Possible agent to partner and incorporate this management into the overnight?

Hmm, what's wrong with using dotenv? That's what I use and it's pretty easy, straightforward.

Here in our work, we had some limitations with dotenv, mainly in controlling different environments, we could find this model with roit-environment, which is very simple to configure, and standardizes the management of the environment, besides having the ease of annotation of the .yaml file, finally, I understand that it can add a lot.

I use an extremely small/simple index.js script in an env/ folder. Just -r the the folder and pass in an argument. You can see an example of it here, https://github.com/seanpmaxwell/InHouseDbMigrationHandler/blob/master/env/index.js. Sorry I know I'm being stubborn but seems a lot easier than creating a whole new module.

Thanks for listening, in our applications we will continue to use the combination of overnight + roit-enviroment, which is working very well!

authors: jeremiassantos seanpmaxwell

repo: seanpmaxwell/overnight


text:
Query Parameters with urlRoot

The UrlTranslator should support a urlRoot with query or hash parameters, however, in practice this is not working as expected.
In the Autocomplete controller for example, the action config option can be used to overwrite the form action - and it should support query parameter additions (for example: action: './?results=products'). It sort of works, except the param is repeated in the URLs generated (for example terms, and facet options).

This is a bigger issue that we will need to pair on to resolve.

This came up when working with Bigcommerce theme preview functionality with a ctk query parameter being added to the form action and then breaking URLs in autocomplete.

repo: searchspring/snap


text:
Must each table include primary keys?

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
Must each table include primary keys?

@fanjiekong yes.

thanks

authors: fanjiekong slievrly

repo: seata/seata


text:
installing package using npm doesn't include buildPlan method

Hi,
The bug described in the title occurred on version 0.0.5.
Thanks in advance,
Reuven

PR merged

That's great, thanks!
Still, the problem occurs, the last method in /lib/bamboo is getAllPlans.
Maybe increasing the version might help?

@sebarmeli Please let me know if it's possible to fix this soon.
Thanks in adavance,
Reuven

Hey, @Reuvenc , I just reviewing the code and buildPlan method will even not work, there an error in the code and also no tests.
I will fix it and create PR, then @sebarmeli can review it.

@Reuvenc created PR https://github.com/sebarmeli/bamboo-api/pull/16 , fixed buildPlan method.

@pvoznenko Thanks for your fix.

@Reuvenc , try to get 0.0.7 version , buildPlan should be there. @sebarmeli published update.

authors: Reuvenc pvoznenko sebarmeli

repo: sebarmeli/bamboo-api


text:
Issue about the curve parameters

Dear Sebastian,
I'm new to the pyrelic. I have a problem with the group G1, G2, and GT.  How can I choose the pairing-friendly curve parameters, like the "BLS12-455" and other curves?

You can't. You get whichever curve your relic installation has enabled.

Thanks for your quick response. I get it.

authors: Vageous sebastinas

repo: sebastinas/pyrelic


text:
impl send sync to world to use it with specs

This PR is not ready yet. just to show you what I am working on
this implementation allow me to use nphysics with specs. I do that in https://github.com/thiolliere/pepe
I have nphysics::world::World as a resource and RigidBody(usize) component with method to get reference to the actual rigid body with borrowing the nphysics world resource.
(examples have not been updated)
The whole point was not to use Rc<RefCell<_>> for rigid bodies, sensor
and joint and instead use a storage and an index to handle them.
The storage must be efficient index_vector is my implementation:
it uses a vector to store the data and never move the position of the
elements in the vector. So the index of the vector always point to the
same element.
We use an offset in order to make sensor and rigid_bodies index
different.
still issue:

fitler data is difficult to use as we can't send a tuple of
reference to storage because it would imply a use of lifetime that the
compiler can't handle (or it's me). I wanted `FilterData = (&'a
RigidBodyStorage, &'a SensorStorage) but I couldn't impl it.
I think the filter things could be different like instead of register
callbacks in collision world. callbacks would be stored in world and
collision_world.perform_broad_phase would have a unique callback
argument. By doing so all the reference lifetimes would be in the in the
function and so it should be OK.
the only drawback of this is that it is to the world to ensure to call
broad_phase.deferred_recompute_all_proximities();

use my fork of ncollide

still todo:

documentation
maybe wrap sensor, joint and rigid_body index in a struct(usize) so user
can't missuse them.
API
also I don't know about performance

I find this interesting, as I am also looking to integrate nphysics with specs.
@sebcrozet: What is the general opinion on this PR or a similar effort?

This is usable but there is two things that are not very handy:
I use the following body component:
// Rigid body handle and whereas it has been deleted
pub struct PhysicBody {
    handle: usize,
    removed: bool,
}

impl ::specs::Component for PhysicBody {
    type Storage = ::specs::VecStorage<Self>;
}

impl Drop for PhysicBody {
    fn drop(&mut self) {
        if !self.removed {
            // debug_assert!(eprintln!("physic body hasn't been removed from physic world") == ());
        }
    }
}

impl PhysicBody {
    pub fn entity(body: &::nphysics::object::RigidBody<f32>) -> ::specs::Entity {

        let entity = body.user_data().unwrap();
        let entity = unsafe { ::std::mem::transmute::<&Box<_>, &Box<Any>>(entity) };
        entity.downcast_ref::<::specs::Entity>().unwrap().clone()
    }

    pub fn add<'a>(
        entity: ::specs::Entity,
        mut body: ::nphysics::object::RigidBody<f32>,
        bodies: &mut ::specs::WriteStorage<'a, ::component::PhysicBody>,
        physic_world: &mut ::specs::FetchMut<'a, ::resource::PhysicWorld>,
    ) {
        body.set_user_data(Some(Box::new(entity)));
        let bodyhandle = physic_world.add_rigid_body(body);
        bodies.insert(
            entity,
            PhysicBody {
                handle: bodyhandle,
                removed: false,
            },
        );
    }

    #[inline]
    pub fn ball_in_socket(
        &mut self,
        physic_world: &mut ::resource::PhysicWorld,
        position: ::na::Point3<f32>,
    ) {
        physic_world.add_ball_in_socket(joint::BallInSocket::new(
            joint::Anchor::new(None, position),
            joint::Anchor::new(
                Some(self.handle),
                ::na::Point3::new(0.0, 0.0, 0.0),
            ),
        ));
    }

    #[inline]
    pub fn get<'a>(
        &'a self,
        physic_world: &'a ::resource::PhysicWorld,
    ) -> &'a ::nphysics::object::RigidBody<f32> {
        physic_world.rigid_body(self.handle)
    }

    #[inline]
    pub fn get_mut<'a>(
        &'a mut self,
        physic_world: &'a mut ::resource::PhysicWorld,
    ) -> &'a mut ::nphysics::object::RigidBody<f32> {
        physic_world.mut_rigid_body(self.handle)
    }

    pub fn remove(&mut self, physic_world: &mut ::resource::PhysicWorld) {
        if self.removed {
            panic!("physic body already removed from physic world");
        }
        physic_world.remove_rigid_body(self.handle);
        self.removed = true;
    }
}

1- each time I really want to access body component I have to use the physic world resource borrow it like that.

let body = body.get_mut(&mut physic_world);

2- but worse when I want to remove an entity I have to explicitly remove it from physic_world resource like that:

if let Some(body) = bodies.get_mut(entity) {
    body.remove(&mut physic_world);
}
entities.delete(entity).unwrap();

To solve 1 we can externalise storage of bodies and sensors and joints. and give storages when you want to update world and do things.
Solve 2 is more difficult. I don't know how I can access deleted and created entities without having to store all entites with body component and a system that at each specs_world.maintain find created and deleted by comparing with the copy.
Accessing created and deleted entities can be wanted by other there may be a feature that is missing from specs here.
It would be cool to have a callback that is called with resource for each entity deleted and created.

@dkushner sebcrozet is making a full rewrite with Send Sync world #101 and you can see his plan on https://www.patreon.com/sebcrozet
also to solve 2 a new storage appeared in specs master: trackedstorage that track insert modified, removed entities on storage. This can be used to automatically remove deleted entities from physic world.
There is so an inconsistence between entities in specs world and entities in physics world: deleted entities remain in physic world until next trackedstorage maintain.

Thanks a lot for all your work here @thiolliere!
This gave ideas for the redesign of nphysics. I'm closing this since the newest vesion of nphysics defines a Send + Sync world.

authors: dkushner sebcrozet thiolliere

repo: sebcrozet/nphysics


text:
Is there a way to bring this into HomeKit using HA?

As far as I can tell, it isn't currently possible to bring the climate entity for the grill into HomeKit using the native HomeKit integration. Is this something that could be added in the future?
I'm honestly uncertain why it's not being brought over to HomeKit. I wonder if it has to do with the entity type?
Thanks for any help

@AerioGit Great question! i'm not really sure. This may be a home assistant question, i'm not sure of any reason why this integration wouldn't just transfer.

@sebirdman Thanks for the response! Yeah, it seems like it should just work, but the devices never show up. Will try to do a bit more research and see what I can find. Cheers

+1 for HomeKit support in Home Assistant. Looking over the logs, I have some logs for you @sebirdman!
2022-01-30 15:04:34 ERROR (MainThread) [homeassistant.components.homekit] Failed to create a HomeKit accessory for climate.682719aec577_climate Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/components/homekit/__init__.py", line 615, in add_bridge_accessory     acc = get_accessory(self.hass, self.driver, state, aid, conf)   File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 222, in get_accessory     return TYPES[a_type](hass, driver, name, state.entity_id, aid, config)   File "/usr/src/homeassistant/homeassistant/components/homekit/type_thermostats.py", line 139, in __init__     super().__init__(*args, category=CATEGORY_THERMOSTAT)   File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 277, in __init__     model=model[:MAX_MODEL_LENGTH], TypeError: 'int' object is not subscriptable 2022-01-30 15:04:34 ERROR (MainThread) [homeassistant.components.homekit] Failed to create a HomeKit accessory for sensor.682719aec577_ambient_temperature Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/components/homekit/__init__.py", line 615, in add_bridge_accessory     acc = get_accessory(self.hass, self.driver, state, aid, conf)   File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 222, in get_accessory     return TYPES[a_type](hass, driver, name, state.entity_id, aid, config)   File "/usr/src/homeassistant/homeassistant/components/homekit/type_sensors.py", line 104, in __init__     super().__init__(*args, category=CATEGORY_SENSOR)   File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 277, in __init__     model=model[:MAX_MODEL_LENGTH], TypeError: 'int' object is not subscriptable
I tried to add 2 items (internal ambient temp and the thermostat or "climate" accessory)
Really any devices will return this error, but these are the two I would think would give some good information as to what home assistant is saying.
HW config: Raspberry Pi 4B 4gb running bullseye and a home assistant supervised install running core 2021.12.10

For me, bringing the Climate Entities to HomeKit works fine. The sensors on the other hand, were a little odd. Ambient came in but refused to show on the iPhone main screen but, digging into the accessories it is indeed there. The Pellet Level % doesn't come in, presumably because it isn't supported by HomeKit unless it's % humidity.
I'd suggest just bringing in the Climate and forgetting about .Ambient as it isn't nearly as accurate on the grills as .Climate.

@PaRkThEcAr i was having a similar issue a long while ago, i just got some time to sit down and look at it and...it's working fine on the latest HA like @njobrien1006's is.
i think the bug was that the model for traeger is a number. feel free to re-open this issue if it's still broken for you on the latest HA

Ah yes! I've ran the latest for a hot minute and it seems to work! Thanks for the help!

authors: AerioGit PaRkThEcAr njobrien1006 sebirdman


text:
What if we export two component in runtime?

I guess this will trigger a bug that wit_import_object conflict

Since user should not merge two .wit definitions in such case

repo: second-state/witc


text:
need help

Hi again :)
My OS is Linux kali 4.14.0-kali3-amd64 #1 SMP Debian 4.14.17-1kali1 (2018-02-16) x86_64 GNU/Linux
King Phisher version: 1.7.1 python version: 3.6.5 and is install from kali linux repository
when i start king-phisher i got this
systemctl start king-phisher.service
Job for king-phisher.service failed because a timeout was exceeded.
See "systemctl status king-phisher.service" and "journalctl -xe" for details.
the info fom systemctl status king-phisher.service and journalctl -xe is here
https://pastebin.com/kXVQNbfZ
how to fix this issue
Thank you :)
Issue Description
I get a stack trace when I...
Reproduction Steps

Start King Phisher
Do something to trigger the crash

Environment Details

Host OS: Ubuntu 15.10 GNOME, Kali 2, etc.
King Phisher Version: x.y.z
Error Details / Stack Trace

If you are opening an issue regarding the client, copy text from the "Error
Details" of the error dialog in the client here. If you are opening an issue
regarding the server copy the relevant lines from the logs here.

There doesn't look like there is any useful information in the log file. Something is causing it to hang on startup so the service is timing out. Try starting the server in the foreground with the following command, wait a few seconds and then post the entire output for us to take a look.
./KingPhisherServer --foreground -L DEBUG server_config.yml

sudo ./KingPhisherServer --foreground -L DEBUG server_config.yml
DEBUG    king phisher version: 1.7.1 python version: 3.6.5
INFO     listening on 0.0.0.0:80
INFO     serving files has been enabled
INFO     initializing database connection with driver postgresql
DEBUG    postgresql-setup was not found
DEBUG    postgresql service is already running via systemctl
DEBUG    current database schema version: 7 (latest)
DEBUG    connected to postgresql database: toor
INFO     restored 0 valid sessions and skipped 0 expired sessions from the database
DEBUG    use pam service 'sshd' for authentication
DEBUG    forked an authenticating process with pid: 1749
INFO     the job manager has been started
INFO     adding new job with id: 24f474d8-35cc-4a37-9ebc-8595efdad0a4 and callback function: ping_all
WARNING  the geoip database is older than 90 days
INFO     including 4 custom http headers
INFO     server running in process: 1713 main tid: 0x7f95390a0740
INFO     dropped privileges to the king-phisher account
DEBUG    executing job with id: 24f474d8-35cc-4a37-9ebc-8595efdad0a4 and callback function: ping_all
DEBUG    executing job with id: 24f474d8-35cc-4a37-9ebc-8595efdad0a4 and callback function: ping_all
DEBUG    executing job with id: 24f474d8-35cc-4a37-9ebc-8595efdad0a4 and callback function: ping_all

That looks like a successful startup. You are a few versions behind though. Can you update to 1.10 and see if the issue persists?

authors: wermaxta zeroSteiner

repo: securestate/king-phisher


text:
Problem with Scan

Hi! I am having some issues while using gattacker. The problem is - after running the "node scan"command on the host, it doesn't scan anything. I wanted to do my experiment with a smartband, but it is not being scanned. I do not have any idea what's going on and how to fix this. Would you please help me?
(P.S. - I faced problem while installing gattacker, as per suggestions on the internet, I tried with node 8, but node 8 didn't work for me. So, I changed every dependency version to "latest" and installed gattacker using node 18.10. I was having issues with blutooth-hci-socket, I learned that the project is not being maintained. So, I replaced it with https://www.npmjs.com/package/@abandonware/bluetooth-hci-socket - this one. I am not sure what is causing the problem. I need your help.)
Thanks for your time! May God bless you!

I felt your pain....In terms of getting past the dependency installation issues (using Node 20.18.1), I have the following package.json
{
  "dependencies": {
    "bleno": "abandonware/noble#master",
    "noble": "abandonware/noble#master",
    "gattacker": "treble37/gattacker#hci-socket"
  }
}

Then once that's installed, I go to ~/node_modules/gattacker and I have the dependencies in package.json  set up as such:
"dependencies": {
"async": "^2.0.1",
"@abandonware/bluetooth-hci-socket": "0.5.3-12",
"bplist-parser": "^0.0.6",
"colors": "^1.1.2",
"debug": "^2.6.9",
"env2": "^2.1.0",
"glob": "^7.0.5",
"ws": "^8.18.0",
"node-getopt" : "treble37/node-getopt#package-update"
}
(In my fork of gattacker I'm going to try and edit the above dependencies shortly so they get installed with my forked branch instead of manually editing).

repo: securing/gattacker


text:
[ARM-277 ] | [ARM-285] Add endpoint to sentry issue title & Clear/update user on each rust request

I've removed the middleware which used to check the body of the response searching for a "success" equals false.
Now we explicitly log the error to sentry when an error occurs locally on a handler.
This prevents other calls to add a wrong user to its sentry scope since we add the user strictly only when an error occurs.
Also, I've manually added the current handler endpoint on each sentry message title.
Example:
get_connection(storage)
        .and_then(|mut conn| {
          ...
        })
        .map_err(|err| {
            log_api_err(
                &format!("GET /v1/emergency/{}/telemetry?{}&{}", username, start_time, end_time),
                &err,
                Some(&auth_info),
            );
            APIJsonResponse::api_error_with_internal_error(err, &auth_info.language)
        })

On rocket_sentry_logger v0.4.0 the stack trace is only sent if the error is FATAL, so that ticket is also resolved

repo: security-union/armore-server


text:
[RFC] Add Jest.preset helper

This concatenates array options, unlike Jest's built-in preset support which discards the original array elements.

I like the idea but I think the name is non-obvious. Would something like Jest.mergePreset make sense?

repo: seek-oss/skuba


text:
My godness! No any response any more!

Today early the code run normally. But become no response any more later! I wait for several hours! No any repsonse from the console.
I doubt it is the website block my IP. But to my strange no any response or error print at all!

Really interesting！I change another HEADER , and it could be worked normally again! Maybe the default have been used by large people all round the world, thus it is blocked by the NBA.com!

What change did you do? Same thing for me

Having the same issue here

confirms it works when you change the user-agent header in init.py

i'm a big noob in this, but could you comment how you managed to fix it? I tried changing user agent headers but with no luck.

I cloned the git repo, changed the line for user_agent in init.py to 'customagent', and then installed the package by doing pip install . inside the git folder with the changed init.py
That's pretty much it.

doesn't fix for me when i change the HEADERS variable to 'customagent'

It looks like this?
HEADERS = {     'user-agent': ('customheader'),  # noqa: E501     'Dnt': ('1'),     'Accept-Encoding': ('gzip, deflate, sdch'),     'Accept-Language': ('en'),     'origin': ('http://stats.nba.com')     }
That's literally the only change I made. Make sure you install the package after you edit it too...

thanks! realized part of my problem was working with an older version of the init file, updated to most recent version and fixed the agent. all working again :) thanks for your help!

Will we ever see a fix by @seemethere ?

I've tried contacting @seemethere on here and via Twitter with no response. If nothing changes shortly before the NBA season starts back up I will fork it and handle a good amount of these issues. I'm interested in becoming a shared owner of this project so all of that isn't required but we'll see..

@rneu31 if you fork this project let me know. I maintain a JS client very similar to this one. I had some ideas about trying to standardize clients across languages using some sort of shared JSON configuration – it'd make maintenance much easier – and I began that work here: https://github.com/bttmly/nba-client-template
We could consider creating a github organization to manage NBA client library projects.

@rneu31  and @bttmly
Please let me know if you need any help. I would love to contribute more.

@GeorgePaul24  Yeah , I change the Header to another one and delete *.pyc files. And it work normally.
But now I write a loop to scrape all the player's shot detail type stats, it comes out again.
Perhaps , time out and no response. When I rerun the code,it start again, but stop at sometime.  I try to have a idea to retry the code by itself.

@bttmly I pulled as many endpoints as I could find from various NBA API clients as well as the stats.nba.com website. I wanted to have good starting list of endpoints to run my analysis script. Thankfully, this process made creating the documentation and API client much simpler. Similar to what you are accomplishing in nba-client-template. I wanted to ensure that this works so that I can regularly update the API client during the NBA Season or whenever new endpoints are discovered.
I completely agree with having a separate repo with markdown and a json file. Not sure on how the best way to proceed would be. I am open to hearing any thoughts you might have on this as we could potentially use most of the parameter and endpoint documentation I created in nba_api.

Sorry I'm late to the party here, but I've been having the same issue as above. The change to 'user-agent' worked to an extent - it stopped the endless running of the code - but now I get a '400 client error' that stats.nba.com/stats does not exist. And indeed, it doesn't, when I try to go in my browser. Is this package too outdated now?

Aaaand it was a syntax error. I was requesting '2018-2019' instead of '2018-19'. I'll show myself out now.

I tested by using "print(nba_py.Scoreboard(month=2, day=21, year=2015))"
But get error: ConnectionError: ('Connection aborted.', OSError("(60, 'ETIMEDOUT')",))
Is this package still working?

It looks like this?
HEADERS = { 'user-agent': ('customheader'), # noqa: E501 'Dnt': ('1'), 'Accept-Encoding': ('gzip, deflate, sdch'), 'Accept-Language': ('en'), 'origin': ('http://stats.nba.com') }
That's literally the only change I made. Make sure you install the package after you edit it too...

谢谢


text:
Categories API payload is not in order as a list

Is your feature request related to a problem? Please describe.

Category API payload content order is changing every time because it's not in type list

Describe the solution you'd like

Make the Category API payload content as a list

Fixed in https://github.com/sef-global/sef-core/pull/52

authors: YohanAvishke anjula-sack

repo: sef-global/sef-core


text:
--since default value is unintuitive

It's taking several minutes to get any logs back. This makes the tool pretty unusable, as I can stumble around the CloudWatch's clunky UI more quickly than that.
∴ time aws-vault exec prod -- cwlogs fetch integration-drip-v1
^C
real	2m24.997s
user	0m8.905s
sys	0m0.771s

Is there anything we can do to improve performance here?

The command you posted tries to fetch all logs ever produced by that service.  The most effective ways to speed up the search are:

Search for logs for a specific task (you can see the list with cwlogs list integration-drip-v1, then search for a specific task using cwlogs fetch integration-drip-v1 -t <task id>
Search for a smaller time window using --since/--until (for example, cwlogs fetch integration-drip-v1 --since 1h for the last hour of logs)

Besides narrowing your search, there's not a whole lot we can do, its just the speed of the AWS API's.

After posting this, I remembered I wrote a node version of this awhile back. It does not have the same performance problems and requires no additional configuration. Just do --group integration-drip-v1 and it'll output what you expect.
If we're going to be migrating away from our (Segment's) default tooling for reading logs, IMO, we shouldn't make it any more complicated than what we had previously. Is there any way we can make the default behavior here a little more user-friendly?

I disagree that the linked version's use of hardcoded time windows is better.  It may output what you expect, but doesn't output what I would expect.
I agree that setting a default start time would be useful, but could be a bit misleading if logs you are looking for are outside of the default window.  It's also doesn't work well for the case where you want to dump all logs for a given task run (which is an operation that the warehouses team does often).  I'm open to a PR to set a default start time, I think we'd have to make it obvious what the default window is some way.
A workaround for you right now would be to set --since in your alias so you don't have to type it each time, and that is the behavior that works best for you.  You're also free to use whatever tool you'd like, if your node version works better for you, then there is no reason not to use it.

I agree with @stephenmathieson that it's rare that you want to get logs from the beginning of time. I also think it's rare that you want to see logs from exactly 1 hour ago though.
Maybe we should make --since required or at least, provide a warning if you don't supply --since?

Alright, I've made two changes which should help out with the issues raised here:

Before, the tool would try to grab all the events before outputting.  This made larger queries harder to distinguish between not working and just taking a long time.  https://github.com/segmentio/cwlogs/pull/8 changes it so that events are streamed immediately to the output as we receive them, and will warn you to try a smaller time window if events start to take longer to load (because of aws-sdk-go's exponential backoff).

I added a default value of 1h to since.  You can still specify "all", for instance if you want to grab all the logs for a given task.

I think that these two changes together make the tool feel more responsive, and give you better feedback when things aren't working well.

Awesome, thanks @dfuentes!

authors: dfuentes stephenmathieson tejasmanohar

repo: segmentio/cwlogs


text:
[Content]:  Mobile Push Onboarding - SwiftUI

What article on segment.com/docs is affected?
https://segment.com/docs/engage/campaigns/mobile-push/
What part(s) of the article would you like to see updated?
We are currently researching implementing Mobile Push Notifications into our iOS app. Currently all the of the docs are for using Swift and UIKit.
here is an example from the documentation that would not work for SwiftUI
To start receiving and handling mobile push notifications, add or modify the following methods in your AppDelegate:

   func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

    //Add the following:

        let center  = UNUserNotificationCenter.current()
        center.delegate = self
        center.requestAuthorization(options: [.sound, .alert, .badge]) { (granted, error) in
            guard granted else {
                Analytics.main.declinedRemoteNotifications()
                Tab1ViewController.addPush(s: "User Declined Notifications")
                return
            }
            DispatchQueue.main.async {
                UIApplication.shared.registerForRemoteNotifications()
            }
        }

        // The following conditional statement is necessary to handle remote notifications in older versions of iOS.
        if let notification = launchOptions?[UIApplication.LaunchOptionsKey.remoteNotification] as? [String: Codable] {
            Tab1ViewController.addPush(s: "App Launched via Notification \(notification)")
            Analytics.main.receivedRemoteNotification(userInfo: notification)
        }

        ...

        return true
}

func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
    // Segment event to register for remote notifications
    Analytics.main.registeredForRemoteNotifications(deviceToken: deviceToken)
}

func application(_ application: UIApplication, didFailToRegisterForRemoteNotificationsWithError error: Error) {
    // Segment event for failure to register for remote notifications
    Analytics.main.failedToRegisterForRemoteNotification(error: error)
}

func application(_ application: UIApplication, didReceiveRemoteNotification userInfo: [AnyHashable : Any]) async -> UIBackgroundFetchResult {
    // Segment event for receiving a remote notification
    Analytics.main.receivedRemoteNotification(userInfo: userInfo)

    // TODO: Customize notification handling based on the received userInfo.
    // Implement actions or UI updates based on the notification content.

    return .noData
}

func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse) async {
    let userInfo = response.notification.request.content.userInfo
    //Segment event for receiving a remote notification
    Analytics.main.receivedRemoteNotification(userInfo: userInfo)

    // TODO: Customize notification response handling based on the received userInfo.
    // Implement actions based on the user's response to the notification.
    // Example: Navigate to a specific screen or perform an action based on the notification.

}

The app.delegate file does not exist in SwiftUI applications.
Perhaps you already have an update in the works, but just wanted to surface this as SwiftUI is the newest development framework released.
Additional information
No response

@bf2344 here is how I implemented it within a SwiftUI app. Although there is no App Delegate file we can create a class called AppDelegate that conforms to  NSObject, UIApplicationDelegate, and UNUserNotifcationCenterDelegate protocols
class AppDelegate: NSObject, UIApplicationDelegate, UNUserNotificationCenterDelegate {
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

        //Add the following:

            let center  = UNUserNotificationCenter.current()
            center.delegate = self
            center.requestAuthorization(options: [.sound, .alert, .badge]) { (granted, error) in
                guard granted else {
                    Analytics.main.declinedRemoteNotifications()
                   // Tab1ViewController.addPush(s: "User Declined Notifications")
                    return
                }
                DispatchQueue.main.async {
                    UIApplication.shared.registerForRemoteNotifications()
                }
            }

            // The following conditional statement is necessary to handle remote notifications in older versions of iOS.
            if let notification = launchOptions?[UIApplication.LaunchOptionsKey.remoteNotification] as? [String: Codable] {
                //Tab1ViewController.addPush(s: "App Launched via Notification \(notification)")
                Analytics.main.receivedRemoteNotification(userInfo: notification)
            }

            return true
    }

    func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
        // Segment event to register for remote notifications
        Analytics.main.registeredForRemoteNotifications(deviceToken: deviceToken)
    }

    func application(_ application: UIApplication, didFailToRegisterForRemoteNotificationsWithError error: Error) {
        // Segment event for failure to register for remote notifications
        Analytics.main.failedToRegisterForRemoteNotification(error: error)
    }

    func application(_ application: UIApplication, didReceiveRemoteNotification userInfo: [AnyHashable : Any]) async -> UIBackgroundFetchResult {
        // Segment event for receiving a remote notification
        Analytics.main.receivedRemoteNotification(userInfo: userInfo)

        // TODO: Customize notification handling based on the received userInfo.
        // Implement actions or UI updates based on the notification content.

        return .noData
    }

    func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse) async {
        let userInfo = response.notification.request.content.userInfo
        //Segment event for receiving a remote notification
        Analytics.main.receivedRemoteNotification(userInfo: userInfo)

        // TODO: Customize notification response handling based on the received userInfo.
        // Implement actions based on the user's response to the notification.
        // Example: Navigate to a specific screen or perform an action based on the notification.

    }
}

This class can be created in the App file of a SwiftUI project. We also need to add the delegate so place @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate in the App file as well.

repo: segmentio/segment-docs


text:
feat: Enable ICA

Description
Stride requires new hostzones to be ICA host enabled because several ICA accounts should be created on host chains for providing liquid staking feature fully.
This PR is for enabling ICA on sei network.

@antstalepresh did you mean to point this to master branch?

Is this still needed? closing out b/c it's stale but feel free to reopen

authors: BrandonWeng antstalepresh philipsu522

repo: sei-protocol/sei-chain


text:
Confirming module settings

Hi @seigneur, wanted to confirm how the module's settings mapped to recently obtained test credentials.
I received:

User Name (in the form of a business name)
User Email
User ID (in the form of 286510VB-73D0-4C30-A6D9-64B2A4956B14)
API Client
API Secret

Am I correct in assuming walletID is the User ID, and clientId is the User Name? Thanks in advance.

Hi @naconner,
The client ID is the user ID and the wallet ID is a particular wallet within your Itbit account. They have this concept of having multiple wallets within the same account. It is something like "axxxxxxx-7xx-xxx8-6xxa-xxxxxxxxxxx0", all lowercase.  :-)
Thanks

Thank you, @seigneur !

authors: naconner seigneur

repo: seigneur/lamassu-itbit


text:
Input type="text" doesn't show content

Verified on FF/Chrome for Linux and Chrome for Mac using http://seiyria.com/dos-strap/examples/signin/

You'll have to submit a pull request if you want this fixed. I no longer
maintain this.
On Fri, Mar 10, 2017, 11:44 Sam Rowe notifications@github.com wrote:

Verified on FF/Chrome for Linux and Chrome for Mac using
http://seiyria.com/dos-strap/examples/signin/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/seiyria/dos-strap/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAum2bODHllkjkqSZOyPRZx4Rz1rBcYgks5rkYwUgaJpZM4MZqxi
.

authors: riddley seiyria

repo: seiyria/dos-strap


text:
Introduce Predicate and AndroidElement factories

Summary:
Non-native android views sometimes require specific behaviours.
This diff introduce factories for predicates and android elements, allowing test
developers to extend them in order to setup specific behaviours at bootstrap.
Test Plan: Ran with custom views and checked using custom factories worked.
Differential Revision: https://reviews.facebook.net/D33639

ping @DominikDary
This change allows you to set custom factories for AndroidNativeElements and Predicates in a bootstrap class.

Apart from the naming I'm :+1: .

repo: selendroid/selendroid


text:
Should TemporalRelation be a modeling pattern rather than a class?

@DanCarey404 raised the question of whether gist:TemporalRelation should be a modeling pattern instead of a class. We came to this conclusion in discussing a possible superclass ComplexRelation; see #424.

@DanCarey404 @rjyounes
After a careful read of #424, I don't see there is anything more to consider.
I recommend we close this issue.

Agreed - closing.

authors: rjyounes uscholdm

repo: semanticarts/gist


text:
Change qualifiedCardinality and someValuesFrom restrictions on units of measure to allValuesFrom

See discussion and examples in PRs #847 and #856. The gist of it is that each ratio unit must have exactly one numerator and denominator (this would be handled by issue #857), and any value must be of the type stated. Using someValuesFrom or qualifiedCardinality implies that there could be more numerators and denominators and of different types for a given unit.

DEFERRED: until there is a revision to units and magnitudes in a future major release. #697


text:
Curriculum Review: Day 3 Code Documentation

First off, A+ memes.
I am curious what all the files sphinx-quickstart makes are. I remember having trouble with Sphinx last year, and I wonder if more knowledge of how it's doing things (so it's less of a black box) could help with that. I could be totally wrong, maybe it's a Pandora's box situation. Also, step 10 doesn't feel abundantly clear to me now, and that is also where I remember getting lost as a participant.

Yes, very helpful! This looks awesome and answers many questions I had. Also, now I see the screenshots -- sorry, they weren't loading when I was on the very very bad AAS conference wifi :)
I do still have one question about toctree though. It would be helpful, at least for me to understand how things are working, exactly what maxdepth & caption mean in that command.
Also, I feel like I am still a bit confused exactly on the formatting of the index.rst file — e.g. the ..(command):: structure, what marking words with `` does. I'm not super familiar with rst files, and I think it may be worth mentioning that this is essentially a sort of text file, and maybe linking to something with more info for those who want to learn more.

Sounds good! I've added more information in the "Tips and Tricks" section with details regarding the different sphinx commands used in the example, which hopefully addresses your questions (merged into main 6/20). This section also includes a link to a cheatsheet on how to format rst files (I'll say what rst files are verbally during the lesson). I don't think I'll walk through this "Tips and Tricks" section during the lesson for the sake of time, but I'll point it out to participants so they can reference it as they wish.
Let me know if this falls in-line with what you were thinking. Thanks again!

Fantastic! Thanks so much

authors: briley-lewis mwhosek

repo: semaphoreP/codeastro


text:
Publish helm reference chart and new deployment instructions

Now that the server is launching k8s jobs, people will likely need to deploy Sematic on k8s. This PR provides a reference helm chart for how to do this, as well as new deployment instructions.
Testing
Deployed this chart to the cluster backing dev.sematic.cloud and executed some pipelines. Tried with authentication on and off.

Codecov Report
Base: 87.61% // Head: 87.63% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (cc1981d) compared to base (30032be).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #145      +/-   ##
==========================================
+ Coverage   87.61%   87.63%   +0.01%
==========================================
  Files         135      135
  Lines       10659    10673      +14
==========================================
+ Hits         9339     9353      +14
  Misses       1320     1320

Impacted Files
Coverage Δ

sematic/tests/test_versions.py
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: augray codecov-commenter

repo: sematic-ai/sematic