text:
Remove documentation warning on EntityCommands::insert that is no longer necessary

Objective

Removes warning about accidently inserting bundles with EntityCommands::insert, but since a component now needs to implement Component it is unnecessary.

There's a link just above too promising more details in EntityMut::insert but there's nothing more to be found there.

Should I remove that too? I assume it's planned to add documentation there though.

Should I remove that too? I assume it's planned to add documentation there though.

Please remove that here too; we can re-add it later as we add more details :)

bors r+

authors: IsseW alice-i-cecile rparrett


text:
Improve debugging tools for change detection

Objective

Previously, the change_tick and last_change_tick fields on SystemChangeTick were pub.

This was actively misleading, as while this can be fetched as a SystemParam, a copy is returned instead

This information could be useful for debugging, but there was no way to investigate when data was changed.
There were no docs!

Solution

Move these to a getter method.
Add last_changed method to the DetectChanges trait to enable inspection of when data was last changed.
Add docs.

Changelog
SystemChangeTick now provides getter methods for the current and previous change tick, rather than public fields.
This can be combined with DetectChanges::last_changed() to debug the timing of changes.
Migration guide
The change_tick and last_change_tick fields on SystemChangeTick are now private, use the corresponding getter method instead.

bors try

bors r+

source: gharchive/pull-request

repo: bevyengine/bevy

license_type: permissive

license_source: github-api


text:
Only insert or remove input if needed

Objective
We are currently inserting an input into pressed even if it is already pressed. This also applies to releasing an input. This is not a big deal, but since we are already checking if the input is pressed or not we might as well remove the cost of the value update caused by the pressed.insert method.
Related to #4209
Solution
Only insert or remove input if needed.

I'll do you one better:
pub fn press(&mut self, input: T) {
    // see https://doc.rust-lang.org/stable/std/collections/struct.HashSet.html#method.insert
    if self.pressed.insert(input) {
        self.just_pressed.insert(input);
    }
}

pub fn release(&mut self, input: T) {
    // see https://doc.rust-lang.org/stable/std/collections/struct.HashSet.html#method.remove
    if self.pressed.remove(&input) {
        self.just_released.insert(input);
    }
}

Only one hash table access for self.pressed regardless of the branch
Heh, I thought of this when I first saw https://github.com/bevyengine/bevy/pull/4209 and was waiting for it to be merged
I find it cool that HashSet::{insert,remove} provide this functionality (as I understand it, it's basically free from the hash table lookup); more power to the programmer :)
Admittedly, I have qualms about the side effects and the confusable return values (there's even a discussion on that[^1]); perhaps comments (not doc-comments) are in order?
[^1]: https://internals.rust-lang.org/t/hashset-insert-considered-harmful/7257

Oh that's actually really cool. I think it's worth switching to this instead and adding a simple comment like:
// Returns `true` if the `input` wasn't pressed before.

bors r+

authors: KDecay mockersf vacuus


text:
Added minimum players option to $splitlobby

$splitlobby command can now be used with a minimum number of players.
Examples:

$splitlobby 4
Will pass only if at least 4 people agreed to split to the new lobby.
$splitlobby
Works as before (sets minimum number to 1).

In addition to this, fixed a bug where the person who calls  $splitlobby would always be moved to a new lobby even if no one else voted to move.

Minus the relatively small issues I've flagged up this is a really nice fix. I look forwards to merging it :)

authors: L-e-x-o-n Teifion

repo: beyond-all-reason/teiserver

license: MIT


text:
[Feature Request] Payload Inspector in the Debug Dashboard

It would be great and mighty useful to be able to inspect the payload in the dashboard when broadcasting a message for example. Similar to how you can inspect the payload on Pusher

is this being added finally? is this why you closed the issue @canhkieu ?

source: gharchive/issue

repo: beyondcode/laravel-websockets


text:
Suggestion

I suggest because if you are in application as admin, already exists the dropdown menu of the user, to delete the Dashboard and Admin Panel entries from the left slide-in panel. It can be confusing somehow.
Also is not clear for me what is the benefit for showing the administrative pages in new window/tab?
I will try this changes tomorrow and I will provide a link to take a look and evaluate.
I found to be a little confusing the way to be displayed the administrative sections (also are named identically but seems to be different, e.g. we have dashboard that displays statistics, but also dashboard from popup menu that displays profile related info's such as orders, transactions etc.)

Thanks. We will take that into consideration.

thanks. we will take that into consideration.

repo: beyourmarket/beyourmarket

license: mit

license_source: bigquery


text:
MGDCTRS-535 Define processors properties for connector type descriptors

https://issues.redhat.com/browse/MGDCTRS-535

superseeded by #28


text:
Updates for Ubuntu 14.10 and 15.04

Adding attributes for Ubuntu 14.10 plus systemd-specific changes for Ubuntu 15.04
tested on Ubuntu 15.04 beta3.  overlayfs woohoo!

LGTM

authors: irvingpop tduffield

repo: bflad/chef-docker


text:
ed25519.cosi: Public key cancellation

Draft of paper "Schnorr Multisignatures for Bitcoin" paper (chapter 2.3) by Pieter Wuille suggest the following change to avoid public key cancellation.
We change the computation of si in the original multisigning scheme
from
si ← ki − xie
to
si ← ki − H(C || Pi) xie
and the resulting combined public key
from
P = sum1..m[ Pi ]
to
P = sum1..m[ H(C || Pi) Pi ]
where C is a key set commitment C = H(P1 || ... || Pn) and H is a random oracle (i.e. hash function).
I suggest reading the whole chapter 2.3 for more thorough explanation.

Thanks Pavol.  We're completely open to potential refinements like this to increase robustness to related-key (or key-cancellation) attacks.  I seem to recall that refinements like these were discussed on the CFRG list back in the work leading up to RFC 8032, but weren't adopted in that context for reasons I don't remember well - perhaps simply because the focus then was on individual rather than collective signatures.  Can anyone else remember exactly when that discussion occurred or find the relevant messages in the CFRG list archive?
At any rate, our Internet-Draft on collective signing is intended to be just a first draft, not by any means a final specification.  Our immediate goal is to get a critical mass of support within CFRG for standardizing collective signing as a working group item.  Once we get to that point, then we can begin the process of (collectively) figuring out exactly what that signing scheme should look like, including which particular hardening refinements such as this it should include.  So what would be ideal at the moment is if you could post to the CFRG mailing list an E-mail stating (a) that you support the CFRG working on specifying some kind of collective signing scheme as a working group item, and (b) a list of issues or changes such as the above that you'd like to see considered in the context of that work.  Thanks again!

authors: bford prusnak

repo: bford/golang-x-crypto


text:
Trac parser problems

The trac parser has some issues:

The optional ='s at the end of a header are not ignored but parsed as text.
Lists items are prematurely terminated without parsing any list item contents under some circumstances.
The parser sometimes fails when (I think) it shouldn't.
On some inputs, the parser ends up in an infinite loop.

Sounds quite reasonable to me!

authors: bgamari tdammers

repo: bgamari/trac-to-remarkup


text:
Galaxy tours are needed

[ ] Vienna-RNA
[ ] mirDeep
[ ] RNA-seq

A few tours can be found here: https://github.com/galaxyproject/galaxy-tours

@jfallmann started to work on it. Help probably welcome.

@bgruening I just started the docker instance and do not find RNAplfold in the tools list, is there something wrong on my side?

@bgruening  @s-will Ich hab mal eine mini tour durch ein paar VRNA tools gestartet, momentan fold, alifold und plot.
Eigentlich wuerd sichs ja anbieten in die Tour auch gleich Carna und co und noch mehr VRNA tools mitzunehmen, ich frag mich nur gerade ob es vielleicht mehr Sinn macht die Touren  eher tool-spezifisch zu machen. Die werden schon recht lang sonst kann ich mir vorstellen, Was sagt ihr?

@jfallmann kleine tours sind immer gut, eine große kann auch nicht schaden, ich glaube sobald wir eine große haben können wir viele kleine spezifische anbieten, der code bleibt ja gleich gell?

Ja das stimmt am Code sollt sich nichts mehr aendern, kleine sind halt insofern einfacher als man nicht ueberlegen muss wie man die tools miteinander verknuepfen muss das es noch halbwegs Sinn macht.
Aber im Prinzip koennt ma natuerlich eine grosse fuer die ganze suite machen und daraus kleine fuer die einzelnen tools die vielleicht auch ein paar mehr optionen der tools einbauen

Hi @jfallmann, sehr cool! Entschuldige die vermutliche Blindheit, aber wo hast du denn die Tours? Mir fielen da schon sinnvolle Kombinationen (mit und ohne LocARNA)  ein:)

@s-will, liegt nicht an dir, die sind noch in meinem branch, ich mach einen PR auf sobald ich getestet hab ;)

Super cool! Wie schwer findest du die Dinger @jfallmann?

@bgruening  Also die tour dich ich da hab ist relativ simpel, da kann man definitiv in jeder hinsicht noch nachlegen, also sowohl mehr options der benutzen tools einbauen als auch mehr tools ganz allgemein.
Vielleicht machts Sinn die tours auch nach topics zu gestalten, also sowas wie ncRNA prediction, interaction, usw. aber das braucht vor Allem Zeit, vielleicht Baustelle fuer Jannuar?

Ja im Januar können wir noch viel machen, ich denke eine schöne Tool die wir auf der Startseite verlinken wäre notwendig, alles andere ist Bonus.

Weil ich dich grad hier hab, gibts einen einfachen Weg die tour yamls zu linten und zu testen? Meine galaxy instanz mag die tour noch immer nicht anzeigen, die drei core tours gehen aber nach docker neustart

Bis auf sowas hier, noch nicht: http://www.yamllint.com/

Working on an RNA-Seq tour based on the training workflow, on the road, so internet is rare, will commit asap

Both tours are awesome and are hopefully enough for the initial submission. A mirdeep tour would be cool for January/February.

More is always better, but we have two nice ones, thanks to @jfallmann!

authors: bgruening jfallmann s-will

repo: bgruening/galaxy-rna-workbench


text:
Free energy calculation with mean-field constrain encounters a MethodError

Find with @bartvanerp. I am trying to calculate the Free energy for a linear Gaussian dynamical system:
@model function ssm(n, As,  B::ConstVariable, R::ConstVariable)
    x = randomvar(n)
    y = datavar(Vector{Float64}, n)
    Q = randomvar()

    x_prior_mean = zeros(3)
    x_prior_cov  = Matrix(Diagonal(ones(3)))
    Q ~ Wishart(4, Matrix(Diagonal(ones(3)*10)))
    x[1] ~ MvNormalMeanCovariance(x_prior_mean, x_prior_cov)
    # Define the constrain like  q = q(mean,out)q(cov) doesn't work, but q = q(mean)q(out)q(cov) do.
    y[1] ~ MvNormalMeanCovariance(B * x[1], R) where { q = q(mean,out)q(cov) }
    # y[1] ~ MvNormalMeanCovariance(B * x[1], R) where { q = q(mean)q(out)q(cov) }
    for i in 2:n
        x[i] ~ MvNormalMeanPrecision(As[i - 1] * x[i - 1], Q) where { q = q(mean,out)q(precision) }
        y[i] ~ MvNormalMeanCovariance(B * x[i], R) where { q = q(mean)q(out)q(cov) }
    end

    return x, y, Q
end

Automatic inference, shown as below:
result = inference(
    model = Model(ssm, n, AS,B,R),
    data  = (y = data, ),
    initmarginals = ( Q = Wishart(4, diageye(3)),),
    returnvars = (x = KeepLast(),Q=KeepEach() ),
    free_energy = true
)

where AS,B,R are known matrix, and data is the observation. It should not have led to an error:
MethodError: no method matching ndims(::NamedTuple{(:out, :μ), Tuple{PointMass{Vector{Float64}}, MvNormalWeightedMeanPrecision{Float64, Vector{Float64}, Matrix{Float64}}}})

Thanks @Chengfeng-Jia ! Fixed in the https://github.com/biaslab/ReactiveMP.jl/commit/de54c3f28fca0883dbd9779105ea0d6a6a048759

authors: Chengfeng-Jia bvdmitri


text:
App language request

There is a Scribe (duvemeister) user who requested for new App Languages

Arabic
Persian (Farsi)
Turkish
Urdu (India)
Urdu (Pakistan)

Update: The files were shared with (duvemeister) for proofreading in the following languages. Folder links are given on the file name. (Common Urdu used in translation)

Arabic - ar.js and ar.json
Persian (Farsi) - fa.js and fa.json
Turkish - tr.js and tr.json
Urdu - ur.js and ur.json


text:
Fail to capture all EEG files and wrong number of subjects

Only capture the raw data, channel and event file. Misses the JSON files.
Also, there are only 2 subjects (with 3 sessions each). Yet the program think there are 6 subjects

hey @arnodelorme
Try to use bids.query to access specific pieces of information of the layout. This is how the whole thing has been designed. :wink:
I still need to write some sort of official doc on this but in the mean time you can look at test_bids_query as a source of unofficial doc.
In your case, what do the following give you?
bids.query(res, 'subjects')
bids.query(res, 'data', 'sub', '01')

Also I am pretty sure that JSON files are not "indexed". Am I right @gllmflndn?
If you want to get the content of some JSON file you would need to do something like this:
bids.query(res, 'metadata', 'sub', '01', 'task', 'Experiment')

Why not load it all?

Not sure why that initial decision was made though I suspect that this in part related to dealing with the inheritance principle which implies that the metadata about a given file could be spread in several JSON, so this is dealt with on the fly when metadata is requested.

hey @arnodelorme
PR #47 should be able to index the json files that are in any "modality" folder a subject if you ask for a schema-less layout.
use_schema = true();
BIDS = bids.layout(fullfile(pth_bids_example, 'eeg_rishikesh'), use_schema);
bids.query(BIDS, 'data', 'sub', '001', 'ses', '01')

ans =

  3×1 cell array

    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_channels.tsv'
    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_eeg.bdf'
    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_events.tsv'

%%
use_schema = false();
BIDS = bids.layout(fullfile(pth_bids_example, 'eeg_rishikesh'), use_schema);
bids.query(BIDS, 'data', 'sub', '001', 'ses', '01')

ans =

  4×1 cell array

    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_channels.tsv'
    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_eeg.bdf'
    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_eeg.json'
    'bids-examples/eeg_rishikesh/sub-001/ses-01/eeg/sub-001_ses-01_task-meditation_events.tsv'

I have shortened the full path in the copy-paste to make it easier to read.
Will merge the PR in the dev branch

Thank you

authors: Remi-Gau arnodelorme

repo: bids-standard/bids-matlab


text:
Problem with export

Hi everyone;
When i want to export a simple excel file I get this error:
java.lang.NoClassDefFoundError: Failed resolution of: Ljavax/xml/stream/XMLStreamReader;         at org.apache.xmlbeans.XmlBeans.buildStreamToNodeMethod(XmlBeans.java:247)         at org.apache.xmlbeans.XmlBeans.<clinit>(XmlBeans.java:134)         at org.apache.xmlbeans.XmlBeans.typeLoaderForClassLoader(XmlBeans.java:715)         at org.openxmlformats.schemas.spreadsheetml.x2006.main.CTWorkbook$Factory.getTypeLoader(Unknown Source:25)         at org.openxmlformats.schemas.spreadsheetml.x2006.main.CTWorkbook$Factory.newInstance(Unknown Source:0)         at org.apache.poi.xssf.usermodel.XSSFWorkbook.onWorkbookCreate(XSSFWorkbook.java:460)         at org.apache.poi.xssf.usermodel.XSSFWorkbook.<init>(XSSFWorkbook.java:263)         at org.apache.poi.xssf.usermodel.XSSFWorkbook.<init>(XSSFWorkbook.java:257)         at org.apache.poi.xssf.usermodel.XSSFWorkbook.<init>(XSSFWorkbook.java:245)         at org.apache.poi.xssf.streaming.SXSSFWorkbook.<init>(SXSSFWorkbook.java:243)         at org.apache.poi.xssf.streaming.SXSSFWorkbook.<init>(SXSSFWorkbook.java:213)         at org.apache.poi.xssf.streaming.SXSSFWorkbook.<init>(SXSSFWorkbook.java:188)         at org.apache.poi.xssf.streaming.SXSSFWorkbook.<init>(SXSSFWorkbook.java:274)         at io.github.biezhi.excel.plus.writer.WriterWith2007.writeSheet(WriterWith2007.java:48)         at io.github.biezhi.excel.plus.Writer.to(Writer.java:284)         at io.github.biezhi.excel.plus.Writer.to(Writer.java:267)         at tools.ActivityExcelExporter.onCreate(ActivityExcelExporter.java:34)         at android.app.Activity.performCreate(Activity.java:7327)         at android.app.Activity.performCreate(Activity.java:7318)         at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1275)         at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3095)         at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3258)         at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)         at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)         at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)         at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1955)         at android.os.Handler.dispatchMessage(Handler.java:106)         at android.os.Looper.loop(Looper.java:214)         at android.app.ActivityThread.main(ActivityThread.java:7058)         at java.lang.reflect.Method.invoke(Native Method)         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:965)      Caused by: java.lang.ClassNotFoundException: Didn't find class "javax.xml.stream.XMLStreamReader" on path: DexPathList[[zip file "/data/app/ir.adinapp.supermarket-rusFzlLBnp2BrQKogUvP3g==/base.apk"],nativeLibraryDirectories=[/data/app/ir.adinapp.supermarket-rusFzlLBnp2BrQKogUvP3g==/lib/arm64, /system/lib64]]
anybody can help me? tanx

it might be the poi version is not correct
is there has already existed poi dependency in your project?

no other dependency added.
and still the problem is not resolved.

authors: maysamrasoli xkcoding

repo: biezhi/excel-plus


text:
Add an error prop to highlight error state

Add an error prop for fixed menu editor (ref: https://github.com/bigbinary/neeto-desk-web/issues/11327#issuecomment-1001529408).

When the prop is set, highlight an error state for the editor and display the passed message.

Snippet for reference: https://github.com/bigbinary/neeto-editor/blob/master/lib/index.js#L23-L31

Address these concerns after merge: https://github.com/bigbinary/neeto-desk-web/issues/11327#issuecomment-1000470579, neeto-kb-web#653 (review).

enhancement _t discussion _t

@mohit-s96 _a please take it up.

repo: bigbinary/neeto-editor-tiptap


text:
Removed date conversion to UTC

Fixes: #2

@jenipharachel _a: Please review and merge.

@sangameshsomawar LGTM.

authors: jenipharachel sangameshsomawar

repo: bigbinary/react-native-calendars


text:
Remove references to PTXQC

Description of the bug
These two configuration parameters are not used in the workflow:
 // PTXQC
    enable_qc           = false
    ptxqc_report_layout = null

PTXQC was removed from the pipeline.
Command used and terminal output
No response
Relevant files
No response
System information
No response

Ok makes sense. We should however make sure that we provide a similar feature set in the long term or do some comparisons.

authors: jpfeuffer ypriverol

repo: bigbio/quantms


text:
Update GenomicDataset.scala

Add documentation for ClassTag in saveAvro method

Thank you for your contribution, @hannahbarfield, this change looks reasonable and useful!
I hope to get a version 1.0.2 release ready in the near future, and this change will be in it.
See Milestone 1.0.2

authors: hannahbarfield heuermh

repo: bigdatagenomics/adam


text:
[ADAM-634] Remove bdg-utils-parquet

This removes the Parquet code that is no longer used, and moves the general I/O utilities from bdg-utils-parquet to a new module called bdg-utils-io. See https://github.com/bigdatagenomics/adam/issues/634.
Once this is removed and a new release of bdg-utils is made, ADAM should be updated to use the new bdg-utils-io module: https://github.com/bigdatagenomics/adam/compare/master...tomwhite:remove-parquet-utils-part2

Can one of the admins verify this patch?

Jenkins, add to whitelist and test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/bdg-utils-prb/35/
Test PASSed.

Thanks @tomwhite!

Thanks for merging this @fnothaft. Do you know when the next bdg-utils release will be? Once there's a new release I'll submit https://github.com/bigdatagenomics/adam/compare/master...tomwhite:remove-parquet-utils-part2 as a PR.

No problem! I'd been hoping to get that cleaned up for a while, so thank you for taking care of that! As for a release, I'll merge in #31 (which is just moving code) and see if I can figure out the remaining issues on #18. Once I've got those taken care of, I can cut a release. Let me spend some time on that either today or tomorrow.

Sounds good.

authors: AmplabJenkins fnothaft tomwhite

repo: bigdatagenomics/bdg-utils


text:
Update google cloud documentation

Add billing account instructions, and minor fixes

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/630/
Test PASSed.

Thanks @Georgehe4 !

repo: bigdatagenomics/mango


text:
Throw better error message when redefining a property

It's not obvious that there are default properties on an interactor like isVisible. If you set a property on an interactor with the same key you'll get an error like:
Uncaught Error: cannot redefine existing property "isVisible"

In an ideal world we should throw an error saying something like "Interactor already has a property named isVisible, please choose a new name"
Or something that says that interactor provides this. I spent ~5 mins looking for a duplicate until I realized what was going on.

Can this be closed with the updated property name restrictions? Or should we still address the new "reserved property name" error?

Going to assume this can be closed with the new error

Yea that makes sense

repo: bigtestjs/interactor


text:
🛑 Breeze Medical Invoicing is down

In cd2c7ad, Breeze Medical Invoicing (https://breezemedicalinvoicing.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Breeze Medical Invoicing is back up in 54f3604.

repo: bigupjeff/my-site-uptime-monitor


text:
Migrate case list and details to Vue.js

Is your feature request related to a problem? Please describe.
We have made good progress converting the variant filtration to use Vue.js. However, case lists and details are still static HTML.
Describe the solution you'd like
Migrate the case list and details view to Vue.js. We should create a new app cases for the views and the vueapp. Migrating the models to the app can be done later.
Describe alternatives you've considered
N/A
Additional context
N/A

Second iteration, allowing modification.

Reopen again for implementation of editing.

Reopen one more time, annotated variants.

repo: bihealth/varfish-server


text:
compatibility with Vue 3?

I was testing this with Vue 3 and adding
import VueElementLoading from 'vue-element-loading'
and
<vue-element-loading :active="isActive" spinner="bar-fade-scale" color="#FF6700"/>
in my component is giving all sorts of errors.
Property "isActive" was accessed during render but is not defined on instance.
TypeError: selfHook.call is not a function
Uncaught (in promise) TypeError: Cannot read property 'parentNode' of null

and so on..
Any fixes as Vue 3 is coming out soon..

Hi @biigpongsatorn,
The new version of vue 3 has already been released, are there plans to make this plugin compatible?

Same here, vue3 support would be appreciated.

Hi, @maharzan
Thank you for your issue, We're working on it. 😁

Hello guys, I added pull request with vue 3 support https://github.com/biigpongsatorn/vue-element-loading/pull/38

Hello guys, I added pull request with vue 3 support https://github.com/biigpongsatorn/vue-element-loading/pull/38

@Sitronik I have left some comments!

@Sitronik I have left some comments!

@Sitronik I have left some comments!

Ok Thanks. I changed everything as you wrote

@Sitronik I have left some comments!

Ok Thanks. I changed everything as you wrote

Hi, @Sitronik
Thank you, for your contributing. That would be priceless PR for us. 😁
So, I will review now and it would be some comments.
Thank you again 😂 🙏

Hi, @Sitronik
Thank you, for your contributing. That would be priceless PR for us. 😁
So, I will review now and it would be some comments.
Thank you again 😂 🙏

Hi, @Sitronik
Thank you, for your contributing. That would be priceless PR for us. 😁
So, I will review now and it would be some comments.
Thank you again 😂 🙏

Hi @runyasak
Ok, you are always welcome 😁

Hi, @Sitronik
Thank you, for your contributing. That would be priceless PR for us. 😁
So, I will review now and it would be some comments.
Thank you again 😂 🙏

Hi @runyasak
Ok, you are always welcome 😁

Hi everyone who has access to npm publishing?  As I understand it, the repository owner is very busy. If you have access please make a publication with the tag next version 2.0.0 thanks in advance.  Anyone who already needs to use a module with vue 3 support in their projects can use npm i vue3-element-loading

Hi everyone who has access to npm publishing?  As I understand it, the repository owner is very busy. If you have access please make a publication with the tag next version 2.0.0 thanks in advance.  Anyone who already needs to use a module with vue 3 support in their projects can use npm i vue3-element-loading

I see that the demo is broken: https://vue-element-loading.netlify.app/

I see that the demo is broken: https://vue-element-loading.netlify.app/

I see that the demo is broken: https://vue-element-loading.netlify.app/

I also saw that there is such a problem, can you make a demo of the module on codeopen and post a link to the demo in the readme?

I see that the demo is broken: https://vue-element-loading.netlify.app/

I also saw that there is such a problem, can you make a demo of the module on codeopen and post a link to the demo in the readme?

Thank you all. @Sitronik  @dacoto97 @runyasak  @maharzan
It is already fixed you can install it as npm i vue-element-loading@next for Vue3 compatibility and the demo page is already working.

Thank you all. @Sitronik  @dacoto97 @runyasak  @maharzan
It is already fixed you can install it as npm i vue-element-loading@next for Vue3 compatibility and the demo page is already working.

authors: Sitronik biigpongsatorn borasusmaz dacoto97 maharzan runyasak

repo: biigpongsatorn/vue-element-loading


text:
Ask user if they really want to STOP sharing

...as maybe the button was touched by mistake.

Good idea. Will add this with an option to turn it off for a settings entry in #74

Added a prompt that shows by default, with an option to dismiss forever.

Do apply this to the list of active shares below. ;)

Oh, forgot about those! Will add.

Added for the share list as well :-)

Thaks

Please reopen, stopping from notification does not respect the setting, there's no confirmation dialogue.

I will look into how this can be done feasibly. How easy is it to accidentally stop sharing from the notification, given that you have to swipe down to access it in the first place?


text:
BinanceApiException: API-key format invalid.

Hi there, I have been using this library for a couple of months now. Recently, although I'm not sure when (probably a couple of weeks ago), I've been unable to authenticate using the normal method of:
BinanceApiClientFactory.newInstance("API KEY", "SECRET KEY");

I get this error:
Exception in thread "main" com.binance.api.client.exception.BinanceApiException: API-key format invalid.
    at com.binance.api.client.impl.BinanceApiServiceGenerator.executeSync(BinanceApiServiceGenerator.java:57)
    at com.binance.api.client.impl.BinanceApiRestClientImpl.startUserDataStream(BinanceApiRestClientImpl.java:213)

Aside from pulling in this repo's changes, I had not changed anything remotely related to these classes whatsoever. I have also checked on Binance that my API key was still valid; it was. I generated a new api key anyways and that didn't help. I am completely stuck and would appreciate some help. Thanks!
EDIT: I have done 'mvn clean install' and that didn't help. The normal unauthenticated factory instance still works, I just can't get any user data from that.

Hi @FuG , please double-check the values you are copying from Binance for the API-key, and make sure that pair is active.

Hi,
I'm facing exactly the same issue. I double checked key and secret and I also checked that the key is active. Any ideas on how to solve this issue?

I have the same issue. I anyone tell me how to fix it ?

Hi,
my problem was that I was connecting with the same key multiple times in parallel.
Did you check that keys are correct and you don't have any IP restrictions?

Hello, yes problem was parallel connection, if you open on webpage or mobile with same account it gives error.

same issue: binance.exceptions.BinanceAPIException: APIError(code=-2014): API-key format invalid.
any suggestion?

I don't know if thats what happend to those guys but i ran into the same problem and its was just a rookie mistake lol
I had created an enum class to hold my keys and then when I was instantiating the client I was doing
Credentials.API_KEY.toString()
But I didn't had override toString method...
I doubt that was the problem to them, but I hope its helps some noob dev like me haha

how was solved??????

Most likely API_KEY or SECRET_KEY are wrong or have the wrong format. I had the same problem because the keys were stored as environmental variables in the .env file with quotes
API_KEY="xxxxxxxxxxxxxxxx"

and after removing quotes, it worked.
API_KEY=xxxxxxxxxxxxxxxx

authors: 361Sepehr AxelRocha FuG eneszv joaopsilva mfatihdr okieven phuphamkdm senpaicryptos

repo: binance-exchange/binance-java-api


text:
Release 3.0.0

Release 3.0.0

Implement HTTP Proxy

Bump pom.xml Version to 3.0.0

Adding HTTP Proxy examples

@aisling-2 Can you please support with the merge of rc-3.0.0 to the main branch?

Hi @jonte-z, @bnbot,
Do you know how long will take, until version 3.0.0 will be available on Maven Artifactory?
Yet not present to:

https://repo1.maven.org/maven2/io/github/binance/binance-futures-connector-java/
https://s01.oss.sonatype.org/content/repositories/public/io/github/binance/binance-futures-connector-java/

Hi @linuradu it's available now, please have a new look. Thank you.

@aisling-2 Many thanks, for publishing the new version. Already tested it and is working perfectly!

repo: binance/binance-futures-connector-java


text:
[Recent Active Tasks] says “Internal Server Error 500” When there are more than one project in Python3

I've tried in python 2.7 with VirtualEnv，everything is fine.
But,when switched to python3 (3.4.2,which is. ),
Recent Active Tasks says “Internal Server Error 500” When there are more than one project
here is the error information
[E 150726 22:47:55 app:1423] Exception on /tasks [GET]
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.4/dist-packages/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.4/dist-packages/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/local/lib/python3.4/dist-packages/flask/_compat.py", line 33, in reraise
    raise value
  File "/usr/local/lib/python3.4/dist-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.4/dist-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/local/lib/python3.4/dist-packages/pyspider/webui/task.py", line 41, in tasks
    updatetime_tasks = rpc.get_active_tasks(project, limit)
  File "/usr/lib/python3.4/xmlrpc/client.py", line 1089, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python3.4/xmlrpc/client.py", line 1419, in __request
    verbose=self.__verbose
  File "/usr/lib/python3.4/xmlrpc/client.py", line 1131, in request
    return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib/python3.4/xmlrpc/client.py", line 1147, in single_request
    return self.parse_response(resp)
  File "/usr/lib/python3.4/xmlrpc/client.py", line 1318, in parse_response
    return u.close()
  File "/usr/lib/python3.4/xmlrpc/client.py", line 656, in close
    raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault 1: "<class 'TypeError'>:unorderable types: NoneType() > tuple()">

all the tests are in pure envirement made by virtualenv.

Thanks for reporting this issue!
"unorderable types: NoneType() > tuple()" has told the reason, which I didn't take notice of. I would add some test for this issue and fix it. thank you.

authors: binux ihipop

repo: binux/pyspider


text:
join(how="left") error: "TypeError: '(slice(None, None, None), 'Feature')' is an invalid key"

Hi Endre,
I've come across this quirky error when trying to specify how for the join function. Weirdly, I could reproduce it for certain combinations of example objects in pr.data but not all...
e.g. using cpg and exons, specifying how = "left" or how = "right" works as expected and doesn't throw an error
import pyranges as pr
cpg = pr.data.cpg()
exons = pr.data.exons()

cpg.join(exons, how="left")
+--------------+-----------+-----------+-----------+-----------+-----------+----------------------------------------+-----------+--------------+
| Chromosome   | Start     | End       | CpG       | Start_b   | End_b     | Name                                   | Score     | Strand       |
| (category)   | (int32)   | (int32)   | (int64)   | (int32)   | (int32)   | (object)                               | (int64)   | (category)   |
|--------------+-----------+-----------+-----------+-----------+-----------+----------------------------------------+-----------+--------------|
| chrX         | 584563    | 585326    | 66        | 585078    | 585337    | NM_000451_exon_0_0_chrX_585079_f       | 0         | +            |
| chrX         | 10094050  | 10094406  | 26        | 10094153  | 10094346  | NM_015691_exon_14_0_chrX_10094154_f    | 0         | +            |
| chrX         | 13587648  | 13588221  | 49        | 13587693  | 13588054  | NM_001167890_exon_0_0_chrX_13587694_f  | 0         | +            |
| chrX         | 17755053  | 17756648  | 117       | 17755568  | 17755800  | NM_001037535_exon_0_0_chrX_17755569_f  | 0         | +            |
| ...          | ...       | ...       | ...       | ...       | ...       | ...                                    | ...       | ...          |
| chrY         | 15591259  | 15591720  | 33        | 15591393  | 15592550  | NR_047610_exon_27_0_chrY_15591394_r    | 0         | -            |
| chrY         | 15591259  | 15591720  | 33        | 15591393  | 15592550  | NR_047607_exon_29_0_chrY_15591394_r    | 0         | -            |
| chrY         | 15591259  | 15591720  | 33        | 15591393  | 15592550  | NM_001258269_exon_29_0_chrY_15591394_r | 0         | -            |
| chrY         | 15591259  | 15591720  | 33        | 15591393  | 15592550  | NR_047599_exon_28_0_chrY_15591394_r    | 0         | -            |
+--------------+-----------+-----------+-----------+-----------+-----------+----------------------------------------+-----------+--------------+
Stranded PyRanges object has 1,084 rows and 9 columns from 2 chromosomes.
For printing, the PyRanges was sorted on Chromosome and Strand.

cpg.join(exons, how="right")
+--------------+-----------+-----------+-----------+-----------+-----------+----------------------------------------+-----------+--------------+
| Chromosome   | Start     | End       | CpG       | Start_b   | End_b     | Name                                   | Score     | Strand       |
| (category)   | (int32)   | (int32)   | (int64)   | (int32)   | (int32)   | (object)                               | (int64)   | (category)   |
|--------------+-----------+-----------+-----------+-----------+-----------+----------------------------------------+-----------+--------------|
| chrX         | 584563    | 585326    | 66        | 585078    | 585337    | NM_000451_exon_0_0_chrX_585079_f       | 0         | +            |
| chrX         | 10094050  | 10094406  | 26        | 10094153  | 10094346  | NM_015691_exon_14_0_chrX_10094154_f    | 0         | +            |
| chrX         | 13587648  | 13588221  | 49        | 13587693  | 13588054  | NM_001167890_exon_0_0_chrX_13587694_f  | 0         | +            |
| chrX         | 17755053  | 17756648  | 117       | 17755568  | 17755800  | NM_001037535_exon_0_0_chrX_17755569_f  | 0         | +            |
| ...          | ...       | ...       | ...       | ...       | ...       | ...                                    | ...       | ...          |
| chrY         | -1        | -1        | -1        | 15409586  | 15409728  | NR_047633_exon_3_0_chrY_15409587_r     | 0         | -            |
| chrY         | -1        | -1        | -1        | 15478146  | 15478273  | NR_047634_exon_18_0_chrY_15478147_r    | 0         | -            |
| chrY         | -1        | -1        | -1        | 15360258  | 15361762  | NR_047601_exon_0_0_chrY_15360259_r     | 0         | -            |
| chrY         | -1        | -1        | -1        | 15467254  | 15467278  | NM_001258270_exon_13_0_chrY_15467255_r | 0         | -            |
+--------------+-----------+-----------+-----------+-----------+-----------+----------------------------------------+-----------+--------------+
Stranded PyRanges object has 1,001 rows and 9 columns from 2 chromosomes.
For printing, the PyRanges was sorted on Chromosome and Strand.

If I use gencode_gtf and chipseq, default join (i.e. how = None) works as intended, but specifying how = "left" or how = "right" produces the following error (same  error I got in my own use case with object derived from a full GENCODE GTF file).
gencode_gtf = pr.data.gencode_gtf()
chipseq = pr.data.chipseq()

#join with default settings works fine
gencode_gtf.join(chipseq)
+--------------+------------+--------------+-----------+-----------+------------+--------------+------------+-------------------+----------------+-------------+------------+----------------------+-------+
| Chromosome   | Source     | Feature      |     Start |       End | Score      | Strand       | Frame      | gene_id           | gene_type      | gene_name   |      level | havana_gene          | +16   |
| (category)   | (object)   | (category)   |   (int32) |   (int32) | (object)   | (category)   | (object)   | (object)          | (object)       | (object)    |   (object) | (object)             | ...   |
|--------------+------------+--------------+-----------+-----------+------------+--------------+------------+-------------------+----------------+-------------+------------+----------------------+-------|
| chr1         | HAVANA     | gene         |   1324755 |   1328897 | .          | +            | .          | ENSG00000224051.6 | protein_coding | CPTP        |          2 | OTTHUMG00000003171.3 | ...   |
| chr1         | HAVANA     | transcript   |   1324755 |   1327994 | .          | +            | .          | ENSG00000224051.6 | protein_coding | CPTP        |          2 | OTTHUMG00000003171.3 | ...   |
| chr1         | HAVANA     | transcript   |   1324766 |   1328897 | .          | +            | .          | ENSG00000224051.6 | protein_coding | CPTP        |          2 | OTTHUMG00000003171.3 | ...   |
| chr1         | HAVANA     | transcript   |   1325240 |   1327471 | .          | +            | .          | ENSG00000224051.6 | protein_coding | CPTP        |          2 | OTTHUMG00000003171.3 | ...   |
| chr1         | HAVANA     | exon         |   1325240 |   1325595 | .          | +            | .          | ENSG00000224051.6 | protein_coding | CPTP        |          2 | OTTHUMG00000003171.3 | ...   |
| chr1         | HAVANA     | UTR          |   1325240 |   1325595 | .          | +            | .          | ENSG00000224051.6 | protein_coding | CPTP        |          2 | OTTHUMG00000003171.3 | ...   |
+--------------+------------+--------------+-----------+-----------+------------+--------------+------------+-------------------+----------------+-------------+------------+----------------------+-------+
Stranded PyRanges object has 6 rows and 29 columns from 1 chromosomes.
For printing, the PyRanges was sorted on Chromosome and Strand.
16 hidden columns: transcript_id, transcript_type, transcript_name, transcript_support_level, tag, havana_transcript, exon_number, exon_id, ont, protein_id, ccdsid, Start_b, End_b, Name, Score_b, Strand_b

gencode_gtf.join(chipseq, how = "left")

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pyranges/pyranges.py", line 2144, in join
    dfs = pyrange_apply(_write_both, self, other, **kwargs)
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pyranges/multithreaded.py", line 291, in pyrange_apply
    result = call_f(function, nparams, df, odf, kwargs)
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pyranges/multithreaded.py", line 23, in call_f
    return f.remote(df, odf, **kwargs)
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pyranges/methods/join.py", line 127, in _write_both
    scdf, ocdf = _both_dfs(scdf, ocdf, how=how)
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pyranges/methods/join.py", line 80, in _both_dfs
    sh = null_types(scdf.head(1))
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pyranges/methods/join.py", line 66, in null_types
    h2.loc[:, n] = h2[:, n].cat.add_categories("-1")
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pandas/core/frame.py", line 2902, in __getitem__
    indexer = self.columns.get_loc(key)
  File "/home/sam/miniconda3/envs/single_utrs/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 2895, in get_loc
    return self._engine.get_loc(casted_key)
  File "pandas/_libs/index.pyx", line 70, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 75, in pandas._libs.index.IndexEngine.get_loc
TypeError: '(slice(None, None, None), 'Feature')' is an invalid key

#using how="right" returns same error

Any ideas for solving this? If it helps, in my own use case, I'm using a pyranges object from a gencode GTF (read in with read_gtf).
For current project, I'm using using a conda environment with following versions (Happy to share environment YAML file if you want it):
python 3.8.6
pyranges 0.0.86
pandas 1.1.3
(For what it's worth, I had a conda environment from a previous project with python 3.6.10, pyranges 0.0.77 & pandas 1.0.3 and the behaviour was exactly the same, perhaps a pandas 1.x problem?)
Thanks for your time and for developing the package, it's great (along with plyranges in R, integrating genomics operations with existing data science ecosystems is so handy!).
Cheers,
Sam

Thanks for reporting this!
I doubt it is a pandas 1.0-issue. I suspect that these options have not been much used and hence might contain a few bugs.
I will have to look at join right and left. I'll try to make a reproducible example.

I found the bug and will upload a fix after the tests have passed.
This reminded me of another thing: most functionality in pyranges is tested thoroughly by comparing it with bedtools, but join with left/right is currently not tested. I should find the relevant functions in bedtools and add the appropriate tests for join left/right.

Amazing thanks for the speedy response and fix!

Now it should be out on pypi :) I fear there are more bugs in the left/right-options. I will try to add a test for them soon :)

Now 0.0.87 should be out on pypi :) I fear there are more bugs in the left/right-options. I will try to add a test for them soon :)

authors: SamBryce-Smith endrebak

repo: biocore-ntnu/pyranges


text:
read_bedlike

The current read_bed is very strict. I'd like a method which reads any table where the three first columns are Chromosome, Start and End and the optional strand can be anywhere else. This would lessen the need for
gr = pr.PyRanges(pd.read_table("bla"))
# pr.read_bedlike("bla") much more convenient

Thanks for developing this excellent resource.
On this point, I'm happy with the current solution posted on readthedocs: pr.PyRanges(pandas.read_table(f)) , however, in terms of being 'too strict', using this appreach did give me the following error message:

The dataframe does not have all the columns Chromosome, Start and End

Which surprised me, until I realized that the columns were "chrom", "start", and "end" (lower-case), and didn't match. The pr.read_bed function was much more forgiving for variations on these names.
Of course I can manually change these  to match the needed "Chromosome", "Start"/"End"(capitalized), but "chrom/start/end" are the standard output from bedtools functions like unionbedg, etc.
With the current solution based on pr.PyRanges(pandas.read_table(f))  is there a way to accommodate column labels like this?  In the long run, it would be ideal if the read_bedlike (or whatever) could allow for 'chrom'='Chromosome' and not be case-sensitive on 'Start'='start'/'End'='end' so that it could work smoothly together with bedtools (which is pretty important for anyone working with bed-like files).
Thanks again for this project, it looks really promising.

DataFrames can only have one name per column. Therefore I cannot allow "chrom" and "Chromosome" to refer to the same column.
If I allowed pyranges to have aliases for column names (start and Start) code that used the dataframes underlying the pyranges would break since no aliasing-code is implemented in pandas.
One possibility is to write a function to read bedtools-like data:
def read_bedtools(f):
    df = pd.read_table(f)
    df = df.rename(columns={"chrom": "Chromosome", "start": "Start", "end": "End", "strand": "Strand"})
    return pr.PyRanges(df)

# the opposite for write_bedtools

Thanks for the question and the kind words btw.

authors: Blosberg endrebak


text:
bugfix/unpin-fsspec

remove pin of fsspec as dependency has resolved issue

resolves #12

repo: bioio-devs/bioio-sldy


text:
allow option to define relationship type in /goterm//genes/ endpoint

Fix for #138.
Note: This is a temporary fix until https://github.com/geneontology/amigo/pull/469 and https://github.com/owlcollab/owltools/issues/241 are implemented.

@cmungall Added suggested changes

repo: biolink/biolink-api


text:
chore: improve vscode extension debug dx

Summary
This PR introduces a VS Code configuration that aims to improve the development experience of the Biome extension.

[x] Adds a debug launch configuration
[x] Adds a watch task that the debug launch depends on

https://github.com/biomejs/biome/assets/649677/302c8639-291c-49c8-a372-57ca4ef4a5ff

Do you plan to update the documentation of the extension?

Yes, I do.

repo: biomejs/biome


text:
Expand and update FAQs

[x] Licenses -- the license for each project is noted for each project
[x] Update schedule -- how frequently content is pulled from primary repositories
[x] Various other info

:tada: This issue has been resolved in version 6.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: biosimulations-daemon jonrkarr

repo: biosimulations/biosimulations


text:
Retry run publication following completion in CompeteProcessor

As discussed in #3811, some runs aren't being published. Publication needs to be retried.

:tada: This issue has been resolved in version 8.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
Submit tellurium 2.2.0

id: tellurium
version: 2.2.0
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_tellurium/492ef082b4dd3060d61b03cc6f0c24a2ae022ff5/biosimulators.json
specificationsPatch:
version: 2.2.0
image:
url: ghcr.io/biosimulators/biosimulators_tellurium/tellurium:2.2.0
validateImage: true
commitSimulator: true

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

Summary of tests

Executed 57 test cases

Passed 27 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 30 test cases:

log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges

Warnings
cli.CliDescribesSupportedEnvironmentVariablesInline (13.2 s)
Test that the inline help for a command-line interface describes the environment variables that the simulator supports.
Warnings:
The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

docker_image.DeclaresSupportedEnvironmentVariables (1.7 s)
Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

The Docker image does not declare the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be declared in the Dockerfile for the Docker image for the simulator.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log:

docker_image.HasBioContainersLabels (0.6 s)
Test that a Docker image has BioContainers labels with metadata about the image
Warnings:
The Docker image should have the following BioContainers labels:
  extra.identifiers.biotools

Log:

The image for your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of tellurium to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.

repo: biosimulators/Biosimulators


text:
doc links not working on github's view of readme

All links such as `file:`Dockerfile` are not working when clicking on them from github's ui view in the README.
This can be fixed by replacing them with references in the .rst (resolves on github side) and providing the root path of the repo to the conf.py to preserve resolution during building docs on readthedocs and in shell.
You can check  https://github.com/ouranosinc/magpie 's README.rst and docs/conf.py files for a working setup with above description.

This has been rendered obsolete by modern changes to the template.

authors: Zeitsperre fmigneault

repo: bird-house/cookiecutter-birdhouse


text:
Docker Container

Hi,
I am developing a docker container for Prime. You can take a look over here astzweig/docker-primecms.
As soon as issue #117 is resolved, I can finish and publish it on Docker Hub. Would you like to reference that project in the documentation somehow?

Published with 0.3.3-beta.8 👍

authors: birkir rqelibari

repo: birkir/prime


text:
really secure?!

Hello
Are dnscrypt proxies truly secure?
Because when I do a dnsleak test, I don't like to see too many host names: /
a thing that i see in all the proposed proxies here.
Thank you for enlightening me on this subject
And how can i send you proxies (i have some premium ones)

DNSCrypt only effects info transfer on DNS recursive query to prevent DNS spoofing. It is NOT designed to be an online security tool though DNS pollution can be a plausible online attack.

@Ghostboy-287 the results of a dnsleak test reflect the DNS resolver's host names.
i.e. if you choose cisco, dnscrypt.eu-nl and many others the dnsleak test will show one host, but other resolvers such as adguard-dns-ns1, adguard-dns-ns2 and several others will show several hosts because those resolvers delegate their search to other resolvers (Google, Yandex, OpenDNS...). It's up to the user to choose the resolver, as you know.

@zymase That's what I mean actually. DNSCrypt will only ensure you get proper DNS response. It comes with NO security assurance.

Does DNSCrypt also ensure that nobody is eavesdropping on the communication between the DNS and the Resolver? With the new law from US, it could be a useful feature :P

authors: EMLVIRUS Ghostboy-287 Themercee zymase

repo: bitbeans/SimpleDnsCrypt


text:
New Changes Make issue in Account Switcher

@lazynina new changes of this PR make an issue for Open Account Switcher
https://github.com/bitclout/frontend/pull/284

It work's fine in Chrome, but in other browsers it makes an issue.

Thanks @harpreet9629 -- looking into it now.

repo: bitclout/frontend


text:
Content Suggestion: Bitcoinheiros

Link to Content: https://bitcoinheiros.com/
Briefly Describe Content: Brazilian Portuguese Podcast/Channel all about Bitcoin
Suggested Section: PODCASTS

Thanks, merged

repo: bitcoin-only/bitcoin-only


text:
Fix many compiler warnings.

This removes about 60 compile warnings on Mac with clang.
2 others which I'll leave for Tom as I'm not sure what he wants to do:
test/script_tests.cpp:920:58: warning: variable 'amount' is uninitialized when used here [-Wuninitialized]
uint256 hash1 = SignatureHash(scriptPubKey, txTo, 0, amount, SIGHASH_ALL);
^~~~~~
streaming/MessageBuilder.cpp:49:21: warning: comparison of constant 8 with expression of type 'Streaming::ValueType' is always true [-Wtautological-constant-out-of-range-compare]
assert(type < 8);
~~~~ ^ ~

test/script_tests.cpp:920:58: warning: variable 'amount' is uninitialized when used here

Good find :)
I directly blame upstream for being so sloppy with their naming. Using the leading "C" in "CAmount" would lead you to believe it is a class, as CSomething is used that way everywhere. In this case, CAmount is a simple typedef to a int64_t.
The main difference between those two is that one needs to be initialized, the other does not...
Thanks for these, I'll merge it when Teamcity give the All Ok.

authors: kyuupichan zander

repo: bitcoinclassic/bitcoinclassic


text:
Allow configuring replace-by-fee

I see that a lot of people don't like RBF, let's go ahead and make it fully configurable so the users can choose what they want.

Thanks James.
I suspect the preference of users is to remove it completely, in order to make it as hard as possible to double-spend or do RBF. We can't make RBF impossible, but we can make it so that at least would-be RBF miners would have to patch the code and recompile in order to make it happen.
That question is probably best asked on http;//bitcoinclassic.consider.it. One of us should make a pull request page there for people to weigh in.
Do you have a link to the Core PR from which this comes?

Note I am planning to rewrite this shortly to use comma-separated strings or something rather than a bitfield. I think.

@jtoomim Since RBF is strictly local policy and not a consensus rule I don't see any reason not to make it optional, I think users should have the freedom to choose local policy options.  This is the original pull request.

I suspect the preference of users is to remove it completely, in order to make it as hard as possible to double-spend or do RBF.

Double spending is already relatively easy to pull off due to minrelaytxfee differences which is also local policy and not consensus, unless you are going to try and force everyone to have the same policy there it won't make much of a difference.

We can't make RBF impossible, but we can make it so that at least would-be RBF miners would have to patch the code and recompile in order to make it happen.

Miners already patch the code so it won't make a difference.

I think we should remove RBF completely. It is not freedom to let senders do RBF and let receivers handle total uncertainty. To have freedom all parties must be free to choose.

@jameshilliard By that logic we should also make it optional for nodes to corrupt transactions as they are relayed, or maybe have a --dos switch where they attack any node which connects to them?
Just because it is possible, doesn't mean it should be encouraged :)

Some of us support Bitcoin Classic thinking it is a "one-feature patch", but other things are being modified, like RBF. Please keep it simple and about a moderate block size increase so we can continue supporting it. Thanks.

@sandakersmann This really has very little to do with senders and receivers, bitcoin is a decentralized network based on consensus rules, unless you can come up with a way for 0-conf to be a consensus rule then I don't see why it shouldn't be changeable(note we have proof of work because otherwise there is no way to get consensus on transaction ordering). The first version of Bitcoin supported replaceable transactions so I see no reason why RBF should not be allowed. From a practical standpoint 0-conf is already unusable under adversarial conditions.
@chriswheeler I think you are talking about transaction malleability DOS attacks which was mitigated with local policy changes by disabling relaying of certain types of signatures, if there was a valid use case for having different forms of signatures then it would be a good idea to have that as an option. There are many valid reasons for RBF so I think it needs to be an option. We need to discourage people from relying on 0-conf because it encourages services like blockcypher to dos the network by mass connecting to nodes for double spend tracking(this is also privacy invading) by attempting to support 0-conf transactions we would only be encouraging this sort of behavior.

@jameshilliard

This really has very little to do with senders and receivers

This has all to do with senders and receivers. Unless you send coins to yourself, all transactions involve a receiver.

From a practical standpoint 0-conf is already unusable under adversarial conditions.

Yes and with RBF it will be unusable under normal conditions too.

@sandakersmann

This has all to do with senders and receivers. Unless you send coins to yourself, all transactions involve a receiver.

RBF is in regards to transaction confirmations meaning it is the miner not the sender or receiver that creates the confirmation and determines transaction ordering. Miners have complete control over which unconfirmed transactions they mine.

Yes and with RBF it will be unusable under normal conditions too.

In what way? If someone want's to double spend it won't make a practical difference. Normal conditions is where the sender is not trying to double spend.

@jameshilliard Given that you NACKd support for Bitcoin Classic, are you saying you would support it if it had optional RBF? If not what is your motivation for this PR?

@chriswheeler I NACKd a specific pull request, not the project itself.

@jameshilliard

RBF is in regards to transaction confirmations meaning it is the miner not the sender or receiver that creates the confirmation and determines transaction ordering. Miners have complete control over which unconfirmed transactions they mine.

Miners should mine the first transaction they receive. It is in their own interest since a currency that can be used in real life will have a bigger market cap. Because of this it should also be hard for people to send double-spend transactions on the network and the nodes should not relay them. Bitcoin Classic should encourage healthy policies and not make it easy to run bad ones.

In what way? If someone want's to double spend it won't make a practical difference. Normal conditions is where the sender is not trying to double spend.

It is much harder to double-spend today than it will be with RBF implemented throughout the network. This is a fact.

@jameshilliard you NACKd the issue "Show Your Support for BitcoinClassic Here"

@sandakersmann

Miners should mine the first transaction they receive.

If the transaction fee is too low then what do you expect to happen? It is not realistically possible to mine every transaction sent or keep them in the miner's mempool indefinitely. Without RBF it would be difficult for users to adjust fees so that their transactions can be processed reliably since a fee market would not be possible. 0-conf requires all transactions to be eventually confirmed which is not realistically possible if someone floods the network with spam.
@chriswheeler the NACK was specifically in reference to attempting to activate a controversial hard fork and its specific activation parameters as a follow up to a previous thread on a different pull request. If activation was done appropriately and with industry wide consensus then I might support it.

The preference now is against RBF:
https://bitcoinclassic.consider.it/keep-0-conf-working-as-well-as-possible?results=true
https://bitcoinclassic.consider.it/revert-opt-in-rbf?results=true
Maybe it will change in the future, but now it seems out of question.

@HostFat Would the recommendation be to change it to off by default then? I don't think trying to take options away from users would be a good idea however.

@jameshilliard

If the transaction fee is too low then what do you expect to happen? It is not realistically possible to mine every transaction sent or keep them in the miner's mempool indefinitely.

The transaction will be dropped from the mempool after some days.

Without RBF it would be difficult for users to adjust fees so that their transactions can be processed reliably since a fee market would not be possible.

If they don't include a sufficient fee they can wait for the transaction to be dropped from the mempool.

0-conf requires all transactions to be eventually confirmed which is not realistically possible if someone floods the network with spam.

No it doesn't. 0-conf transactions is not about 100% certainty. It is about managing risk.

@jameshilliard If you go to the links @HostFat provided, you can see that the users don't want this option.

@sandakersmann

The transaction will be dropped from the mempool after some days.

Do you not see the problem with that? That makes the transactions very unreliable, you can't have payments indefinitely stuck in limbo in a functional payment system.

If they don't include a sufficient fee they can wait for the transaction to be dropped from the mempool.

Well you can double spend it at that point anyways.

0-conf transactions is not about 100% certainty. It is about managing risk.

At what point does the cost of trying to maintain 0-conf security outweigh the benefits? The negative effects from 0-conf are getting pretty bad, we have privacy invasion in addition to unreliable confirmations, it's time we allow transaction replacements as Satoshi intended from the start.

If you go to the links @HostFat provided, you can see that the users don't want this option.

That's why it's an option, if they don't want it they can disable it, but outright removing local policy configuration options is not a good idea as it would create a bad precedent.

@jameshilliard

Do you not see the problem with that? That makes the transactions very unreliable, you can't have payments indefinitely stuck in limbo in a functional payment system.

Bitcoin will not be a functional payment system with RBF.

Well you can double spend it at that point anyways.

We are talking days later.

At what point does the cost of trying to maintain 0-conf security outweigh the benefits? The negative effects from 0-conf are getting pretty bad, we have privacy invasion in addition to unreliable confirmations, it's time we allow transaction replacements as Satoshi intended from the start.

Satoshi also intended Bitcoin to have no blocksize limit from the start. Do you support that?

That's why it's an option, if they don't want it they can disable it, but outright removing local policy configuration options is not a good idea as it would create a bad precedent.

The precedent it will set is that Bitcoin Classic developers implement what users want. You should push these pull requests that users do not want over at Bitcoin Core. They implement stuff that users vehemently oppose all the time.

@sandakersmann

Bitcoin will not be a functional payment system with RBF.

This makes no sense since RBF is needed for reliable transactions and quick confirmations.

We are talking days later.

And you can double spend days later then, I don't see that helping much.

Satoshi also intended Bitcoin to have no blocksize limit from the start. Do you support that?

Source?

The precedent it will set is that Bitcoin Classic developers implement what users want. You should push these pull requests that users do not want over at Bitcoin Core. They implement stuff that users vehemently oppose all the time.

So you are against giving the users freedom of choice for local policy via config options?

@jameshilliard

So you are against giving the users freedom of choice for local policy via config options?

I support giving users freedom of choice through the Bitcoin Classic decision mechanism over at: https://bitcoinclassic.consider.it/

@sandakersmann

I support giving users freedom of choice through the Bitcoin Classic decision mechanism over at: https://bitcoinclassic.consider.it/

So you don't think users should have individual freedoms for local policy changes then, they should all be forced to follow the majority no matter what?

@jameshilliard

So you don't think users should have individual freedoms for local policy changes then, they should all be forced to follow the majority no matter what?

Last time i checked Bitcoin was open source. People can do whatever they want.

@sandakersmann

@sandakersmann

Last time i checked Bitcoin was open source. People can do whatever they want.

So you want to make it as difficult as possible for users to make their own local policy choices?

@jameshilliard

So you want to make it as difficult as possible for users to make their own local policy choices?

Since RBF affects more people than the local node operator, I'm happy with the decision being made here: https://bitcoinclassic.consider.it/

@sandakersmann

Since RBF affects more people than the local node operator, I'm happy with the decision being made here: https://bitcoinclassic.consider.it/

So cripple bitcoin and make sure there is no individual choice all in the name of trying to preserve security on something that was never designed to be secure, got it.

@jameshilliard

So cripple bitcoin and make sure there is no individual choice all in the name of trying to preserve security on something that was never designed to be secure, got it.

As I said, it is open source. Don't like this implementation, go to the next one.

So cripple bitcoin and make sure there is no individual choice all in the name of trying to preserve security on something that was never designed to be secure, got it.

It doesn't cripple anything. You could submit a fss-rbf patch that would provide miners with the same fee revenue, allow fee bumps, and still preserve zeroconf. The fact is zeroconf has proven reliable enough for small value transactions and the utility would be missed.

@cpacia

You could submit a fss-rbf patch that would provide miners with the same fee revenue, allow fee bumps, and still preserve zeroconf.

Unfortunately there are multiple downsides to FSS-RBF such as privacy issues, added complexity and in general not being flexible enough.

The fact is zeroconf has proven reliable enough for small value transactions and the utility would be missed.

This perception is incorrect, the only reason they are reliable enough is because most people making transactions aren't trying to double spend, RBF doesn't change that at all.

@jameshilliard again, RBF, as it is now, it will be completely removed, deal with it.
The good thing is that the community is starting to learn that they can install what ever node they prefer, so if RBF is a most wanted feature (I think not), then they will install the fork the support it.
Make it, or wait for Bitcoin Core.

@HostFat What percentage of hashpower do you think needs to run Full-RBF for 0-conf to be useless?

I don't know, but they will need to use something else then Bitcoin Classic, or patch it locally to support it.
Anyway, I'll be curious to know how much is wanted this feature by the miners.

@jameshilliard It's probably a very low percentage but I've always been skeptical of the inevitability of that happening.

Miners have not shown any desire to run it in the entire history of bitcoin. The only pressure to run it has come mainly from developers.

They wont earn any additional fees from it vs just running fss-rbf or cpfp.

It's very likely to reduce the utility of bitcoin (and hence price and mining revenue) so they will likely earn less over the life of their mining investment.

So I'm not sure a rational miner would run it voluntarily and that may explain why none have so far.
Of course I could be wrong, but the bulk of the evidence doesn't suggest so at this point.

@HostFat It's hard to say exactly how many support it but I know a few operators who are considering it.
@cpacia

Miners have not shown any desire to run it in the entire history of bitcoin.

It was only coded fairly recently.

They wont earn any additional fees from it vs just running fss-rbf or cpfp.

I'm not sure about this one since fss-rbf and cpfp use up significantly more block space.

It's very likely to reduce the utility of bitcoin (and hence price and mining revenue) so they will likely earn less over the life of their mining investment.

This is false, 0-conf is already insecure and RBF has plenty of valid use cases that improve utility in general.

I feel that double-spend mitigation and risk are some things that are (and should be) assessed and assumed by the payment processors; and/or by a new form of insurance company that provides double-spend coverage for businesses that accept bitcoin directly. As long as the risks of zero-conf are known, and accepted/assumed, there is absolutely no reason to push for anything that completely nukes zero-conf transactions.  RBF is a solution in search of a problem that doesn't exist -- or that doesn't exist to the extant that a pervasive network-wide "fix" is necessary.

@opetruzel

I feel that double-spend mitigation and risk are some things that are (and should be) assessed and assumed by the payment processors; and/or by a new form of insurance company that provides double-spend coverage for businesses that accept bitcoin directly.

One issue is that this encourages privacy invasion by companies such as blockcypher who mass connect to nodes for double spend tracking.

As long as the risks of zero-conf are known

IMO they aren't known right now to the majority of people.

NACK. Everyone has made it clear on consider.it that they would rather RBF is not implemented. If users wish to mod their clients, no one stops them, but there is no reason whatever why we should make it easier or enable a feature which many believe causes active harm to bitcoin.

@Aquentus Consensus is normally only required for consensus code changes not local policy config options. Also consider.it is not an accurate representation of the community by any means.

Can someone open a consider.it page for this, and take the time to clearly explain what this PR implements, so that people can vote on the issue?
This seems like a borderline reasonable PR, so I don't want to unceremoniously close it without some sort of vote.

@jameshilliard I wasn't talking about consensus. I think that RBF actively harms bitcoin therefore we should not make it easier for individuals to actively harm bitcoin by offering RBF as ANY option. If people want to mod their clients then fine, but there is no reason whatever why we should in any way assist anyone who wishes to actively harm bitcoin.

@Aquentus The opinion that RBF actively harms bitcoin is not shared by everyone, many think it is needed for bitcoin's success and since it is strictly a local policy option and not a consensus rule it should IMO be fully configurable. At the same time those that don't want it should be free to disable it for their node, attempting to centrally control local policy and make it harder for users to make their own policy choices is a slippery slope to centralization. You could argue that the default should be different and but outright removing the choice would not set a good precedent. Anybody using bitcoin should already be aware that RBF is strictly local policy and that the network makes no guarantees of 0-conf security at the consensus level.

How about taking the political discussion to consider.it and leaving github for the code review?

Jameshilliard you are a fairly transparent troll!

This is not the place to debate politics. This is a conversation about source code. You are really jamming the progress. We need to get a release ready. Just merge and move on. That can't be so difficult

You convinced me. RBF should really be a user choice.
There are apps out there for easy double spending already on the existing protocol. For secure trustless instant transaction confirmation we need to wait for lightening networks. No sound wallet app would ever (mis)use RBF to provide a double spend button. That wouldn't make sense. Wallets will use the protocol feature to adjust fees. How else is the fee market supposed to function?

@jameshilliard " since it is strictly a local policy option and not a consensus rule "
It is very much a consensus rule as everyone needs to not use RBF. If some people do then that breaches the current policy of First Seen Safe and places 0conf in the whole network in danger. If those individuals wish to actively try and harm bitcoin by modding their clients then that's their choice, but we should not in any way make it easier for potential attackers to breach a policy that has been in place for 7 years and arguably is part of the social contract.
Some people do disagree, you are right, but as we can see they are a very very tiny minority https://bitcoinclassic.consider.it/revert-opt-in-rbf?results=true probably less than 5%. If those individuals wish to remain unpersuaded despite the impeccable logic provided by Satoshi some 7 years ago that First Seen Safe makes 0conf transactions pretty safe then they can mod their own client or keep running core. No reason whatever for us in any way to aid them.
As others have said however we do need some forum or mailing list in regards to these discussions, but it's a NACK on my part especially since F2Pool has come out to state they do not support any RBF or the concept of "fee market". We prefer free market here.

NACK. Sneaky troll.
Adds a new "default-to-the-default" feature, then uses that feature to cause the default to be ALWAYS allow RBF.  Screen shot for easy reference in case he changes it.

@Aquentus Do you know what a consensus rule vs local policy is? From this statement here it sounds like you don't.

It is very much a consensus rule as everyone needs to not use RBF.

A consensus rules is something that changes the definition of if a block is valid or if a block is not valid, since RBF certainly has no affect on block validity it is thus not a consensus rule at all, you can't just go making up definitions like that. I think there is a big misunderstanding among what are and what aren't consensus rules.
@dgenr8 I didn't change the default from the original commits. This can be changed of course.

Thank you for disabling this by default RBF makes our double spend tracking more difficult.

@cointracker It really shouldn't make a difference since you can just check to see if a transaction is marked as replaceable.

Blocksize growth cancels need for rbf or fee concerns. NACK

@jtoomim why was this closed? opt-in RBF is disabled by default in this pull request

@jameshilliard If you look at the consider.it page, the proposal to "Leave opt-in RBF code in, but disabled by default" has very low support. Basically, you got voted down.

@jtoomim I'm curious, is there anything to prevent a Sybil attack on consider.it?

@jameshilliard: Verified users.

@jojva so from the looks of it this decision was made by a random 7 people on consider.it who verified identify at one point in time, good to know that's all it takes to make decisions here.

It's your job to convince users that your proposal is worth it. When you feel like your proposal has enough traction to get positive votes, feel free to post it again.

What jojva said above is accurate, but since you might want to hear it from me, I'll put it in my own words.
@jameshilliard If the support on consider.it changes, the pull request can be reopened. In the absence of support on consider.it, maintainers (i.e. me and Ahmed for now) are free to close a pull request at their will.
The burden of proof is on the PR submitter to show support. If you don't show support, I may close it summarily without giving reason. If you do show support, and I close it or leave it closed anyway, and I do not have another justification afforded to me by our rules, then I am acting outside of bounds and should be criticized, censured, or replaced, depending on the severity of the occurrence.

authors: Aquentus HostFat SouperNerd chriswheeler cointracker cpacia dgenr8 dskloet eleuteromaniaco jameshilliard jojva jtoomim luke-jr opetruzel orangeman sandakersmann surg0r


text:
Allow use of Signet and Regtest networks

I think this issue pairs well with #4. When creating a wallet, the user should be able to choose a network to use, including:

Any signet they want
Local regtest networks if they have a valid esplora/electrum/rpc enpoint they can point a client to

Because there might be many different version of each of those, they probably need some sort of user-defined name for display and debugging.

Done!

repo: bitcoindevkit/bdk-kotlin-example-wallet


text:
Newsletters: add 201 (2022-05-25)

[ ] Update releases/RCs and add topic links @harding
[x] Bitcoin Stack Exchange section @bitschmidty

helpful link: https://pleb.fi/transcripts/2021/miami/tarun/

@Xekyo

It could perhaps be a bit shorter on describing Ethereum's issues and perhaps elaborate on how recursive covenants would create more opportunity for MEV on Bitcoin, if there is more information in that regard.

Sorry, I don't really have more information about that.  @JeremyRubin mentioned in the meeting something called "bitmatrix" that claimed it would implement some sort of defi thing on covenants on Liquid, but it appeared to be a dead project and I didn't have time to really dig into it.  It did seem credible to me that recursive covenants would allow you to build account-like structures on Bitcoin and so you could, in theory, replicate some of these problematic things from Ethereum.  I thought it would be better to explain what MEV meant for a audience of Bitcoin developers who, like me, maybe never really heard the term before and so they could realize that it's a potential problem and start thinking about what (if anything) to do about it.

It's not dead, it's actively being developed. https://www.youtube.com/watch?v=wxtGDmM7uJU explains how the current design works in detail, pretty approachably.

@JeremyRubin

It's not dead, it's actively being developed.

Ok.  I guess I was confused by https://medium.com/bit-matrix/introducing-bitmatrix-bd8306740afe saying "Our team is working to roll out the initial version around Q4 2021." and pointing to a dead URL https://bitmatrix.app/
I didn't watch the video.

Edits pushed for all feedback (except where I replied), thanks @glozow @JeremyRubin @Xekyo @shesek !  Also added/updated releases and RCs and added topic links.  Additionally added a "special thanks" section for Jeremy providing detailed info about MEV concerns.  Reviewed B.SE section (thanks @bitschmidty !).
Thanks everyone!

ACK 6e4c5adc8341d227fe440d6e727511bca49f5a64
Squashed and merged. Thanks @harding @JeremyRubin @Xekyo @glozow @shesek for contributing to newsletter 201! 🚀

pointing to a dead URL https://bitmatrix.app/

It's live at https://beta.bitmatrix.app/. They should probably redirect to it from the root domain, I'll mention this on their telegram channel.

authors: JeremyRubin bitschmidty harding shesek


text:
Bug: PTZ speed broken on BirdDog P200A2_A3 5.5.114

We recently upgraded the BirdDog P200 firmware to latest (5.5.114) as well as upgrading Companion from 3.1-ish to 3.4.3. Some - but not all - of our PTZ buttons in Companion 3.4.3 started panning super super slowly (like, 1 pixel per second). However, some were fine.
Looking in the JSON for the buttons I see:
Working Button:
"options": {
	"val": "left",
	"posPan": "0000",
	"posTilt": "0000",
	"override": true,
	**"panSpeed": 11,**
	**"tiltSpeed": 9,**
	"value": 88
},

Not working button:
"options": {
	"val": "right",
	"posPan": "0000",
	"posTilt": "0000",
	"override": true,
	"value": 89
},

I think - but cannot verify - that a "working button" was a button we created at some point in the past?
The non-working button is one created with v3.4.3. I wonder if the "value" parameter is either gone or otherwise doesn't do anything?
Also note in the BirdDog Camera Control UI the Pan Speed is a value from 0-21. In Companion, the "Speed Override" control is a value from 0-255, which seems like a mismatch.
It's also possible it had an issue with the Module Model being set to Auto-Detect, I changed it to P200 A2_A3 but that didn't seem to make difference.
Thanks!
--
Matt

@MattRogish I think I found the issue with the pan/tilt speed override not working, and that should be fixed for new buttons in the latest beta. Let me know if creating a new button still results in issues.
In regards to the speed values, the module should recognize the speed mode (either 0-21 or 0-255) set by the camera but it sounds like it's possibly not doing that. I will look into that more.

authors: MattRogish bryce-seifert

repo: bitfocus/companion-module-birddog-ptz


text:
Module not connecting to discord

Describe the bug
When adding the discord module and entering the Client ID/Secret the status stays on "conencting"
upon adding the module i do get the discord prompt to allow access to bifcous but approving this doesnt change the connecting state and bitfocus does not appear in the list of authorised apps.
Have included the logs below
Screenshots

System (please complete the following information):
Win 11 - 21H2
Companion 2.4.1

Just to check, you're logged in to Discord as the same account that was used to create the app and get the credentials?

Yep, just checked to be sure it is the same account

unsure if its signficant but if i force close companion, when i reopen it always prompts for the discorcd external application prompt.

tried adding this on a mac but had the same results,

I'll Have another look at this while I'm working on updating the module for Companion v3, but right now I'm not sure what the issue you're experiencing is as none of our testers can reproduce it.

@James-Brittain do check that you are using the "Client Secret" from here:

I had the same 'symptoms' as you... and only after I cloned the Companion source code could I better debug why I was stuck 😅

Hi @navhaxs, yeah that was the secret i was using, i deleted everything and started from scratch and it seems to be working now - im not sure if i did anything different here or if there was an update?
Either way thank you and @thedist for looking into this!

authors: James-Brittain navhaxs thedist

repo: bitfocus/companion-module-discord-api


text:
Adding multiple roles in a middleware

Hi,
How can I add multiple roles in a middleware i.e:
Route::group([
    'prefix'     => '/brands',
    'middleware' => ['role:super-admin, admin']
    ], function(){
    Route::get('/', 'Admin\BrandController@index')->name('brand.index');
});

This is possible in the blade files like so @admin('emails,super-admin'), but I don't seem to be able to recreate in the routes.
Any help is much appreciated.
Thanks in advance.

You mean multiple role in route middleware ?

Yes! I've tried everything but I don't seem to find a solution without assigning the roles to the user - I would rather assign multiple roles to the route if that's possible.
Thank you so much.

Solved in new version 3.0.0 :)

authors: newtowebdevelopment sarthaksavvy

repo: bitfumes/laravel-multiauth


text:
Balance reflected in watch only wallet should get updated when app is closed and reopened the next time.

Our app should look for any transactions that may have been made in the wallet being watched in another app and show it the next time the app showing the watch only wallet is reopened.

By default, the wallets are fetched by pull-down to refresh. So users will anyways go inside and fetch the transaction.
Why do we need to fetch them before hand?

As discussed this can only be picked once we figure out the background refresh and its not that important to fetch the transaction for watch only before hand.
Putting this in backog

authors: ASN-BitHyve pratyakxx

repo: bithyve/bitcoin-keeper


text:
IP address is null on first run

Almost always, the IP Address of the new VM will not be set at the end of the Terraform run, causing the subsequent Ansible run to fail. When manually checking the machine or re-running the Action, or pulling state locally, it will be set by then.
So it's most likely a wait-for-it scenario.

for TF or for Ansible?  would the "wait for it" pattern be helpful here?
example: https://github.com/bitovi/bitops/blob/main/docs/examples/bitops%2Bterraform%2Bansible%2Bstackstorm-blog/st2-bitops-test/ansible/bitops.before-deploy.d/my-before-script.sh#L3

It's actually not that the VM is not getting the IP, it's just not coming out in the tf output. It's appears to be present in the state data at the time of output, but it's not getting set. Def the first thing i'm looking at now that it's at v1.0.0.

Synced to Jira: https://bitovi.atlassian.net/browse/DEVOPS-821

The existing "wait for it" examples are feel pretty heavyweight for the needs here. I'm going to create my own and it can be enhanced if needed in the future.

created operations/deployment/terraform/bitops.after-deploy.d/inventory_wait.sh


text:
add support for visibility in LambdaTest Upload

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[ ] I will not move an already shared step version's tag to another commit
[ ] I read the Step Development Guideline
[ ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[ ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[ ] I read and accept the Abandoned Step policy

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: rohithmone-lt:x: anurag-lambdatestYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant rohithmone-lt

repo: bitrise-io/bitrise-steplib


text:
Update sbt-avrohugger to 2.7.0

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

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

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

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:1

Superseded by #137.

repo: bitrockteam/kafka-dvs-avro-schemas


text:
🛑 Luogu Ti is down

In 8f54d69, Luogu Ti (https://ti.luogu.com.cn/problemset) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Luogu Ti is back up in 78eaed2 after 11 minutes.

repo: bitsstdcheee/luogu-status


text:
Play 360 degree video in Portal

Hi, How can we play 360 degree video in this portal?

Good question,
Were you able to play 360 video in this portal?

Thanks for your reply, i have created a portal which is like a room having walls and a door same like in your video, now i want to play 360 degree video inside the portal so that it should give user an experience that he/she is inside that video. How this can be done, can u guide please or if you have any link for this?

You need to set the 360 video as material of a sphere.

On 11 Oct 2018, at 19:39, Hamza Imran notifications@github.com wrote:
Thanks for your reply, i have created a portal which is like a room having walls and a door same like in your video, now i want to play 360 degree video inside the portal so that it should give user an experience that he/she is inside that video. How this can be done, can u guide please or if you have any link for this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

https://stackoverflow.com/questions/46423415/how-to-apply-360-video-as-a-texture-in-arkit
Hi Guys, I was struggling to build AR 360 video portal with setting the 360 video as material of a sphere refering the link above, but failed. hope you help out me. thanks in advance.

Yeah, I believe that 3d video is supposed to mapped on the inside of a sphere. Now to combine that with a portal (using the masking technique) you probably need to split the sphere in two so that they can be "masked" individually. I haven't rendered 3d video yet, but I do have another (non-public) project with a portal that provides a 360 degrees world inside the portal where you can walk around the portal inside and outside of the portal space while staying in/out of the portal etc. This could be modified to render 3d video inside of the portal. I dunno if/when I might get the time to do so however:/

Thank @bjarnel i will try for it and if you got this done please let me know it would be great to take guidedence under you.

Hi bjarnel, thanks for your reply. so is that possible to render 360 video inside of portal and apply mask tech? I was trying to integrate this link into your project, but problem is how to archieve mask the sphere.
https://stackoverflow.com/questions/46423415/how-to-apply-360-video-as-a-texture-in-arkit
I will appreciate if you update this asap, ;(

With the masking technique I used in this (old) demo and (with more complexity, such as tracking whether you're inside portal or outside portal and in which half of portal you're in) in the non-public demo I have on my bitbucket account, as I said, the sphere would need to split in half to mask each inner-side individually. I do believe SceneKit allows you to texture the inside and render it invisible from the outside, but I would need some time to refresh my memory on their SDK. The bigger problem is that with SceneKit primitives you cannot create half a sphere, so you would probably need to generate the geometry for one using the equation for a sphere and calculate all texture coordinates yourself (taking into account one half of video should be in one of half the sphere and the other half should be in the other half of the sphere) - which can be time consuming (and would also be for me, not having worked with SceneKit for a while). Maybe I will have a bit of time next week:-)

Bruce, to mask the sphere, add another one that is just 1mm bigger and make sure its rendering order is lower than the video one. Then pass an empty array as the colorBufferMask to make it invisible.
Hope this helps.

On 12 Oct 2018, at 11:26, Bruce0418 notifications@github.com wrote:
qinglong0418@gmail.com mailto:qinglong0418@gmail.com that's my email and skype id. can we chat there when you have some time? I would like to keep better communication with you. thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/bjarnel/arkit-portal/issues/3#issuecomment-429280236, or mute the thread https://github.com/notifications/unsubscribe-auth/ATEpnt7etrfL5W851C3h5OZLsMJ6I1C9ks5ukG5QgaJpZM4WCk0J.

repo: bjarnel/arkit-portal