text:
Add a simple EntityMapper struct for use in networking

          That's the behaviour I'd prefer to have for networking, as I don't want/need the complexities associated with the existing EntityMapper. (Having to use `EntityMapper::world_scope()` and needing access to `&mut World`)

I will remove this from the PR as users can implement it themselves
Originally posted by @cBournhonesque in https://github.com/bevyengine/bevy/pull/11428#discussion_r1467883777

I'm not sure if it's possible to have a general enough struct for networking.
In replicon I have different mapper for events and components, for example. Since it's just a few lines of code, I would left it for libraries to implement.

Mhmm. Might be more useful as an example? It's hard to say: networking is a nasty beast.

Yes, an example would be good. But maybe worth to put into rustdoc to the trait description?

Yeah, I like this a lot as a doc test.

authors: Shatur alice-i-cecile

repo: bevyengine/bevy


text:
Add support for letterboxing

What problem does this solve or what need does it fill?
Cutting off segments of the game screen using black bars (a letterbox) is a common technique for both cinematic cutscenes and for supporting unusual aspect ratios, particularly for pixel art.
What solution would you like?
Expose a simple setting that sets the letterboxing mode, probably to Window or cameras.
What alternative(s) have you considered?
Add an example demonstrating how to set this up manually, probably using render targets.
Additional context
Discussed on Discord in the context of pixel art games. Prompted by the closure of #14153.

Cart's demo: https://gist.github.com/cart/87c0215aa650170f09164fcffc252139

Disclaimers: the demo is two years old now, so it would need porting. I think there is room for an simpler upstream solution. I think we could probably also come up with a Camera-level letterboxing API that doesn't rely on Bevy UI.

I do hope you don't mind me chiming in on this. That being said, I've been giving some thought to this over the past few days, and while I definitely don't have the knowledge to implement this, I do have some ideas at the very least that could be helpful.
I think letterboxing should be done on the camera, and not necessarily on the window -- if it's possible. I think it would fit better with the APIs that the Camera has, and it would be (in my opinion) a bit more intuitive to look to the Camera for the settings for this rather than the Window. As an example, when it comes to setting the background color of areas that have nothing rendered to them, you set the color on the Camera (The clear-color should also probably be used for the letterboxing, which could be useful for artistic purposes).
Additionally, at least for certain classes of games those games would likely want to letterbox at specific resolutions, or at resolutions where the output would be scaled by a non-integer amount. This would be useful for things like 2D Games which use Pixel Art, like I tend to do. My assets and game is designed at 360p (16:9) so that it can be scaled to most other 16:9 displays (720p, 1080p, etc). if it is played on a resolution outside of 16:9 then I need to letterbox or just not support those resolutions whole-cloth. I'm already having to set scaling mode on the Camera as well to get behavior that I want, and in these circumstances it would be more intuitive to have it be on the Camera, than on the window.
If letterboxing is done on the Window specifically, then it would feel a bit weird to setup, at least for me, as if you wanted to enable/disable it then you'd have to go to the Window to do so, which for things like Cutscenes would likely be a bit weird.
I also searched the Bevy discord for letterboxing, and I noticed that most people are looking at the Camera to see if there's a letterbox implementation, with some expecting Scaling modes to letterbox automatically (specifically for Camera2D at least).

I fully agree that this should be a camera setting and not a window setting.

Hello. I actually created something to do this today, but I named it "bevy_fixed_viewport", as it directly impacts the camera's viewport:
https://github.com/Jaso333/bevy_fixed_viewport
It would be nice to get this integrated into the engine.

source: gharchive/issue

authors: Jaso333 Sapein alice-i-cecile cart

license_type: permissive

license_source: github-api


text:
Release v1.0.1

cache Laravel version check for 1 hour

looks like this project is abandoned
will continue a fork, happy to merge if needed

source: gharchive/pull-request

repo: beyondcode/nova-laravel-update-card

license: MIT


text:
Can someone add a license for the repository?

Thank you guys so much for providing this resource.
Can one of the maintainers/project owners add a license?  I would like to explore building with this, but I don't want to override any permissions in doing so.

Heya.
The license is MIT.
If this doesn't work for you, please let me know and I'll consider other options.

That works @antony, just wanted to make sure.  Thanks so much for the quick response on this!

authors: antony sbutler-gh

repo: beyonk-adventures/svelte-mapbox


text:
Strimzi upgrade 0.32.0

relates to #468

@lburgazzoli Test are finally green :sweat:

@lburgazzoli  I've updated to Quarkus Operator SDK 5.0.0 now which comes with Java Operator SDK 4.2.0 which I also updated in the PR. Mind having a look?

@rinaldodev mind having a look ?


text:
package-lxc-ubuntu-1404 fails kitchen test with lxc-start error

[2014-07-07T20:17:03+00:00] INFO: Processing docker_image[docker_image_build_1] action build (docker_test::image_lwrp line 16)

================================================================================
Error executing action `build` on resource 'docker_image[docker_image_build_1]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of docker build  --tag="docker_image_build_1:docker_image_build_1_tag" - < /tmp/docker_image_build.dockerfile ----
STDOUT: Step 0 : FROM busybox
        ---> a9eb17255234
       Step 1 : RUN /bin/echo 'hello from docker_image_build_1'
        ---> Running in daf716e55ca6
       lxc-start: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblxc.so.1: undefined symbol: cgmanager_get_pid_cgroup_abs_sync

       STDERR: Sending build context to Docker daemon 2.048 kB
       Sending build context to Docker daemon
       2014/07/07 20:17:03 The command [/bin/sh -c /bin/echo 'hello from docker_image_build_1'] returned a non-zero code: 127
       ---- End output of docker build  --tag="docker_image_build_1:docker_image_build_1_tag" - < /tmp/docker_image_build.dockerfile ----
       Ran docker build  --tag="docker_image_build_1:docker_image_build_1_tag" - < /tmp/docker_image_build.dockerfile returned 1

       Cookbook Trace:

       ---------------
       /tmp/kitchen/cache/cookbooks/docker/libraries/helpers.rb:272:in `execute_cmd!'
       /tmp/kitchen/cache/cookbooks/docker/libraries/helpers.rb:265:in `docker_cmd!'
       /tmp/kitchen/cache/cookbooks/docker/providers/image.rb:127:in `build'
       /tmp/kitchen/cache/cookbooks/docker/providers/image.rb:25:in `block in class_from_file'

       Resource Declaration:
       ---------------------
       # In /tmp/kitchen/cache/cookbooks/docker_test/recipes/image_lwrp.rb

        16: docker_image 'docker_image_build_1' do
        17:   tag 'docker_image_build_1_tag'
        18:   source docker_image_build_1_file
        19:   action [:build, :remove]
        20: end
        21:
        22: docker_image_build_2_dir = '/tmp/docker_image_build_2'
        23:
        24: directory docker_image_build_2_dir
        25:
        26: file "#{docker_image_build_2_dir}/foo.txt" do
        27:   content 'Dockerfile_2 contains ADD for this file'
        28: end
        29:
        30: cookbook_file "#{docker_image_build_2_dir}/Dockerfile" do
        31:   source 'Dockerfile_2'
        32: end
        33:
        34: docker_image 'docker_image_build_2' do
        35:   source docker_image_build_2_dir
        36:   action :build
        37: end

       Compiled Resource:
       ------------------
       # Declared in /tmp/kitchen/cache/cookbooks/docker_test/recipes/image_lwrp.rb:16:in `from_file'

       docker_image("docker_image_build_1") do
         action [:build, :remove]
         retries 0
         retry_delay 2
         guard_interpreter :default
         cookbook_name "docker_test"
         recipe_name "image_lwrp"
         tag "docker_image_build_1_tag"
         source "/tmp/docker_image_build.dockerfile"
         cmd_timeout 300
         image_name "docker_image_build_1"
       end

[2014-07-07T20:17:03+00:00] INFO: Running queued delayed notifications before re-raising exception
[2014-07-07T20:17:03+00:00] INFO: template[/etc/default/lxc] sending restart action to service[lxc-net] (delayed)
Recipe: lxc::default
  * service[lxc-net] action restart[2014-07-07T20:17:03+00:00] INFO: Processing service[lxc-net] action restart (lxc::default line 90)
       [2014-07-07T20:17:03+00:00] INFO: service[lxc-net] restarted

           - restart service service[lxc-net]

       Running handlers:
       [2014-07-07T20:17:03+00:00] ERROR: Running exception handlers
       Running handlers complete

       [2014-07-07T20:17:03+00:00] ERROR: Exception handlers complete
       [2014-07-07T20:17:03+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
       Chef Client failed. 39 resources updated in 378.320975494 seconds
[2014-07-07T20:17:04+00:00] ERROR: docker_image[docker_image_build_1] (docker_test::image_lwrp line 16) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of docker build  --tag="docker_image_build_1:docker_image_build_1_tag" - < /tmp/docker_image_build.dockerfile ----
STDOUT: Step 0 : FROM busybox
 ---> a9eb17255234
Step 1 : RUN /bin/echo 'hello from docker_image_build_1'
 ---> Running in daf716e55ca6
lxc-start: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblxc.so.1: undefined symbol: cgmanager_get_pid_cgroup_abs_sync

       STDERR: Sending build context to Docker daemon 2.048 kB
       Sending build context to Docker daemon
       2014/07/07 20:17:03 The command [/bin/sh -c /bin/echo 'hello from docker_image_build_1'] returned a non-zero code: 127
       ---- End output of docker build  --tag="docker_image_build_1:docker_image_build_1_tag" - < /tmp/docker_image_build.dockerfile ----
       Ran docker build  --tag="docker_image_build_1:docker_image_build_1_tag" - < /tmp/docker_image_build.dockerfile returned 1
[2014-07-07T20:17:04+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
>>>>>> Converge failed on instance <package-lxc-ubuntu-1404>.

Any updates on this?  I'm getting similar errors:
$ lxs-create
No command 'lxs-create' found, did you mean:
Command 'lxc-create' from package 'lxc' (main)
lxs-create: command not found
john@openstack1:~/.cloud-install$ lxc-create
lxc-create: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblxc.so.1: undefined symbol: cgmanager_get_pid_cgroup_abs_sync
john@openstack1:~/.cloud-install$ lxc=ls
john@openstack1:~/.cloud-install$ lxc-ls
Traceback (most recent call last):
File "/usr/bin/lxc-ls", line 31, in
import lxc
File "/usr/lib/python3/dist-packages/lxc/init.py", line 26, in
import _lxc
ImportError: /usr/lib/x86_64-linux-gnu/liblxc.so.1: undefined symbol: cgmanager_get_pid_cgroup_abs_sync
This is on an Ubuntu 14.04 w/all updates as of today.
Thanks.

Package installs deprecated as of 0.40.x

authors: bplunkert john3exonets someara

repo: bflad/chef-docker


text:
planemo forgets steps

Hi,
$ docker run -v `pwd`:/export planemo conda_init
$ docker run -v `pwd`:/export planemo conda_install .
Conda not configured - run planemo conda_init' or pass --conda_auto_init to continue.

What would be the best way do use planemo docker together with Atom IDE on Mac OS X?
Thank you in advance.
Mic

Oh, @mictadlo this docker image is not really maintained. Do you really need a Docker for it?
pip install planemo works usually well enough.

Will I run in any problems using Mac OS X rather than Linux?

I hope not.

authors: bgruening mictadlo

repo: bgruening/docker-recipes

license: mit

license_source: bigquery


text:
background is rectangle

background of AnimatedCircularProgress is rectangle ? can it style to circle ? I want to fill background with color , but it is rectangle and I just want a circle background
can you help me ? what can i do with this
thanks

@Nasirilahi Could you attach the code you have for the component or a screenshot? + are you testing on android or ios?
On 1 Feb 2018 17:33, Nasir Husain notifications@github.com wrote:
@dancherbhttps://github.com/dancherb i tried your way but it didn't work for me?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/bgryszko/react-native-circular-progress/issues/110#issuecomment-362302309, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AeyOOZXQt9yiQgRJA_srk2uHB7MQluZWks5tQdk3gaJpZM4RXOuF.

Since the merging of #83 the background should be circular by default. If somebody is able to validate that would be great.

Closing for inactivity. Please re-open if this issue is not resolved.

authors: Jacse JeckChou dancherb

repo: bgryszko/react-native-circular-progress


text:
Add type hints

It would be great if this module had type hints, so that it could be used in type-checked projects.

Sounds like a great idea. It's not too hard. Do you want to open a PR or shall I make one?

I do not have the bandwidth to take this on right now, if you are able to do it, go for it!

It's actually almost fully type hinted. Do you have an issue during usage?

Oh I think py.typed is missing because it's a single module package

That sounds right, mypy is giving me this error:
error: Skipping analyzing "asynciolimiter": module is installed, but missing library stubs or py.typed marker  [import]

Please check now. 1.1.0 released

I'm guessing this is done :-)

authors: bharel vectro

repo: bharel/asynciolimiter


text:
Syntax error: is it possible to get the file name where is it throwing?

Hi,
I'm trying to improve an old library (at work) for emails and not sure which file is generating the error
[14:23:52] SyntaxError in plugin "gulp-prettier"
Message:
    Unexpected closing tag "p". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags (85:25)
  83 |

  84 |

> 85 |

     |                         ^
  86 |

  87 |
  88 |

SCREEN NOW

Details:
    loc: [object Object]
    codeFrame:   83 |

  84 |

> 85 |

     |                         ^
  86 |

  87 |
  88 |

SCREEN NOW

    domainEmitter: [object Object]
    domainThrown: false

[14:23:52] 'build' errored after 5.54 s
[14:23:52] 'default' errored after 5.54 s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It tells me the line where it's throwing, but since it's an array of html files, I have no idea which file is actually broken.
function prettify() {
  const htmlPath = 'dist/pages';
  return gulp.src(htmlPath + '/*.html')
      .pipe($.prettier({ parser: 'html' }))
      .pipe(gulp.dest(htmlPath))
}

Is it possible to find which file is generating the error?

That is indeed a helpful addition. Fixed in 565f3d3. The error now contains a fileName line.

authors: TheDancingCode minuz

repo: bhargavrpatel/gulp-prettier


text:
POWERLEVEL9K_DIR_BACKGROUND no longer working

Hi
Is it possible that POWERLEVEL9K_DIR_BACKGROUND is no longer working? I've updated the theme and now I get the default blue prompt :/
Cheers
Domi

Yep. That is correct. I added state to this segment, so the variable name changed depending on the state the segment is in. I documented the change in the changelog.
Now it is something like:
POWERLEVEL9K_DIR_HOME_BACKGROUND='blue'
POWERLEVEL9K_DIR_HOME_SUBFOLDER_BACKGROUND='cyan'
POWERLEVEL9K_DIR_DEFAULT_BACKGROUND='yellow'

You can read more about states in the wiki.

@domibarton Did this work for you?

Hi
Yep it worked, looks fine now :)
https://github.com/domibarton/config/blob/master/roles/zsh/templates/custom.zshrc.j2
Oops sorry I forgot to close the issue :( my fault!
Thanks & Cheers
D

On 11 Mar 2016, at 23:16, Dominik Ritter notifications@github.com wrote:
@domibarton Did this work for you?
—
Reply to this email directly or view it on GitHub.

Hi!
I've added these variables and nothin happens. Can you help me?
POWERLEVEL9K_DIR_HOME_BACKGROUND='blue'
POWERLEVEL9K_DIR_HOME_SUBFOLDER_BACKGROUND='cyan'
POWERLEVEL9K_DIR_DEFAULT_BACKGROUND='yellow'

@GlaciErrDev could you provide a screenshot? And on which version of powerlevel9k are you?

@dritter I've already fixed it. I don't know why, but after restarting iTerm2 it works well.

Great to hear!
Yes, you have to source your ~/.zshrc after setting variables in there.

authors: GlaciErrDev domibarton dritter


text:
Fixes for #10 and #11

Fixes #10 and #11.

Looks like it should be fine, you've tested this and it all works?

I did really simple tests with get_threads and different pages which all worked. Fetching board metadata through any of the Board's properties works too. You might want to look at this, it's how I determine if SSL should be used or not. This is a problem when functions outside of the Board class attempt to use _fetch_board_metadata, you end up having to create a dummy URL generator instance without a valid board name (which does work).

Cool, I've tested with BASC-Archiver and it all seems to work fine.
Thanks a bunch for the fixes, I've pulled this in (with some rebasing to avoid messy merge commits), your code's in master now! I'll try to push an update to pypi with it tonight.

Great, sounds awesome.

Actually I just noticed. I'm sorry, I wasn't entirely clear on why you did something in the previous code. You want to re-add the line: if not _metadata: here.

authors: DanielOaks irlittz

license: WTFPL


text:
Enable static methods :D

Enable static methods:
class Math {
	static square(n) {
		return n * n;
	}
}
writeln(Math.square(10));

Having static methods will become pretty handy for creating standard libraries in the future.

repo: bichanna/slap


text:
build: TypeScript / ESLint / Prettier対応

Closes #1

マージされたときにコミット署名が消えてしまったので復旧


text:
URI link broken in BIDS microscopy

The link to the URI in the BIDS Microscopy metadata field is broken.
It should be resolved if in the specifications-schema-metadata file the link in line 264 is changed to refer to https://bids-specification.readthedocs.io/en/stable/02-common-principles.html#uniform-resource-indicator.
https://github.com/bids-standard/bids-specification/blob/24dbe58010d96c0ce4d4c775230cef94605c6068/src/schema/objects/metadata.yaml#L264

Have you tried in the latest version of the bids spec? I.e., the unreleased "development" version?
https://bids-specification.readthedocs.io/en/latest/99-appendices/14-glossary.html#bodypartdetailsontology-metadata
I think we fixed this bug in #1056

Sorry, I missed that one. Works on the dev version.

authors: JuliusWelzel sappelhoff

repo: bids-standard/bids-specification


text:
Establish the resource of sample DICOMs + target conversions

IIRC the benefit of having such a resource was initially suggested by @neurolabusc in a conversation with the BIDS Steering group. I have ran the idea by DICOM WG-16 (ref: #1515) who agreed that it might be useful but it would be for us to establish it but it might benefit/relate to ongoing IHE SHARAZONE  (see a publication providing initial feedback on taking part in it).
Also I was told that @neurolabusc and @francopestilli (please chime in) are working on https://brainlife.io/ezbids/ and establishing already some collection for its validation etc. May be it could be generalized (for different converters etc) and serve as a beginning for such a community/shared resource.

@yarikoptic we have 32 dcm_qa_* repositories. These are each designed to exhibit edge cases for conversion, and is useful for regression testing. Hopefully, other tools should provide similar fields for the BIDS tags, but note that dcm2niix also includes some fields that are not in BIDS, so a cross-conversion validation tool would need to have a dictionary of which fields are included in BIDS.

True, we would need to accompany with the spec on what fields we expect conversion to have etc.
Well -- we might want a "golden target" and then let tools to require to match it and then possibly to add extra if they would desire to add more fields (like dcm2niix adds its own version, and we do the same in heudiconv and also extract more metadata from dicoms etc).  Among those 32 do you have any which has a full fledged BIDS dataset(s) as output or just niftis + json sidecars?
Because, I guess, for BIDS conversion tools/targets it would be needed to ensure that we are getting valid BIDS datasets. Well, we might need to do some composition there since often we might want multiple protocols together (e.g., fmap + func) to actually establish some pragmatically useful use case.

authors: neurolabusc yarikoptic


text:
[FIX] Define a metadata table for TB1EPI

This PR resolves #1351 by drawing the TotalReadoutTime and MixingTime definitions from the schema. I followed the table in https://bids-specification.readthedocs.io/en/latest/appendices/qmri.html#field-maps to determine the required metadata.

Before

After

@effigies it looks good to me as well. It aligns with fmriprep definitions, which also documents issues around Phillips. Maybe providing a hyperlink would make it clearer: https://fmriprep.org/en/1.0.0/sdc.html

authors: agahkarakuzu effigies


text:
fix links for BEPS

On this page: https://bids.neuroimaging.io/get_involved.html
Completed BEPs should link to a page in the spec or to whatever website hosts the final version of that BEP.
Also check that the link to each BEP points the relevant PR if the BEP has left the google doc stage.

probably a better way to keep track of this would be to add the relevant link in the yaml files for the different BEPS:
https://github.com/bids-standard/bids-website/tree/gh-pages/_data

Hello, @Remi-Gau I am interested in participating in GSOD can you please share some community links like Slack or anything else and what is the process?

Hi @MeenuyD - Please note as of April 15 this Google Season of Docs project is fully staffed and we unfortunately can't invite further applicants.
Thank you for your interest in our GSOD project and contributions to the BIDS initiative, we are always looking to welcome new members to our open-source community.
on behalf of the BIDS GSOD mentors

@Remi-Gau can this go next?  Can i move it to to-do / next project board column ?

Yes I would say this is high priority.

authors: MeenuyD Remi-Gau christinerogers

repo: bids-standard/bids-website


text:
Update session_controller.ex

fix claims bug

Thanks for the PR, good catch!

authors: bigardone ionull

repo: bigardone/phoenix-trello


text:
PXD014414 problems

Description of the bug
@daichengxin I have reanalyzed again the dataset PXD014414, if you see the volcano plots almost no proteins are differentially expressed. I was checking the notebooks we have for the same datasets and the results are quite different, Can you take a look.
URL: http://ftp.pride.ebi.ac.uk/pub/databases/pride/resources/proteomes/differential-expression/PXD014414/
Command used and terminal output
No response
Relevant files
No response
System information
No response

@daichengxin The dataset PXD020248 has almost not proteins quantified, when running the automatic pipeline in quantms. However, I see a lot of proteins in our benchmark paper. Can you take a look.

Hi @ypriverol , I checked the PXD014414, It should be normal. In the notebooks, we using p-value<0.05 to show differential expressed proteins. But the volcano plots were draw based on adjusted p-value <0.01. So there are some difference bwteen two results.

Can we draw all the results at 0.05 p-value.

Do you mean add a parameter to select the threshold type for the plots in bin/R script?  We can do that.

Yes, and default values should be 0.1.

So default parametes are p-value and 0.1 for the plots, right?

authors: daichengxin ypriverol

repo: bigbio/quantms


text:
What to do when a node creates another Genesis block?

Any node can at any time write a new Genesis Block. AFAIK this is wrong but it doesn't affect the correct behavior of the system.
Possible solutions are:

delete the additional Genesis Block (but we want the bigchain table to be append only)
remove the concept of Genesis Block and assume that the first block is the one with no previous_block_id in the voting table

Ideas?

We can't allow for deletions from the bigchain table. Special cases are exploit opportunities.
When a node comes back after a crash, it doesn't have any idea what the "previous block" was (in its view of the bigchain table's changefeed), but that's no reason to conclude that the first block it sees is a Genesis block.
There can only be one valid Genesis block. We could use that fact. Any time a node is asked to vote on a Genesis block, it can query to see if there is any other existing valid Genesis block. If yes, then the new Genesis block can be voted invalid.
Why do we need a Genesis block, again?

Why do we need a Genesis block, again?

I'm still figuring out how the code works in general, but it appears to me that there's has to be a mechanism to identify a _singular_first block, whether or not it be created especially for the purpose of being the genesis block. Otherwise, since there's no block height, what would stop nodes from creating and working on multiple independent chains?
If this problem could be solved, then the code could be simplified considerably. Most of the logic related to genesis would be encapsulated in the selection of the first block. Valid transaction operations would be CREATE and TRANSFER, and this too could be removed since a CREATE transaction can then be identified by the presence of an asset / lack of conditions.

Returning to this, do we still have an issue here?
It appears to me that there is an issue, but the issue is that we do not verify vote signatures in Bigchain.get_last_voted_block.
This method is only called at startup to know which block to resume from. So a node could be tricked into working on the wrong chain.
I'm going to suggest that we handle this issue using the firewall:

Blocks invalid votes
Block duplicate genesis block

Thoughts?

At this point validation of data by the firewall is out of scope.
One way to solve this would be to update the transaction validation so that when a there is a genesis transaction it checks that it doens't already exist in the bigchain. If one already exists then the block is invalid.

Currently the genesis block doesn't get voted on. So, either:

Genesis block has fixed ID, so DB will reject dupe

or

Vote on GENESIS block and check there's only one

thoughts?

Genesis block has fixed ID, so DB will reject dupe

That seems like a nice idea, as it leverages the backend database's auto-deduping "feature," but I wonder how much code would have to change? (Today, we have a different way of identifying the Genesis block.) I suspect it might not be a lot of code; a grep -ri "genesis" could find all the relevant code quite fast.

I'm wondering if there any issue with malleability. But on the other hand. I'm still not sure what the genesis block is for. Why not just point to '0' * 64 if no block exists?

authors: libscott r-marques ttmc vrde

repo: bigchaindb/bigchaindb


text:
Is Metadata.id neccesary?

Do we need transaction metadata id? Is there a use case for it that can't be served by using [txid].metadata?

What do you mean by [txid].metadata?

I mean, that you can use the transaction id to refer to the metadata, since they have a 1:1 relationship and the transaction contains the metada. So, [txid] gets you the transaction, and .metadata deferences the metadata inside the transaction:
def get_metadata_by_txid(bigchain, txid):
    tx = bigchain.get_transaction(txid)
    return tx.metadata

I mentioned this in person, but for the record:
What if someone wants to find all transactions with some particular metadata? For example, maybe someone sets the metadata data to "Submitted by Alex P. Goodwin of Beaverton." in every transaction that they submit. Now they want to find all transactions with that particular metadata data.
Admittedly, we don't have that today: the current metadata.id is random per transaction. It's not a hash of the metadata data. Is it possible to index the metadata data? AFAIK we allow arbitrary (nested) JSON in the metadata data so maybe indexing that isn't practical (or is it)?

There's a related question:
If we do get rid of the metadata id, then what's the point of having "metadata data" --- why not just have "metadata"?

Yep, that follows: https://github.com/bigchaindb/bigchaindb/commit/005ad5a93add96da9821c91790b9e13ae40c20c2

authors: libscott ttmc


text:
Bump version 0.1.2 => 0.2.0

TODO:

[ ] resolve Content-Type header issue
[ ] Write upgrade guide to close #58
[ ] Test readme.md examples against current bdb v1.0.0rc1
[ ] Change docker image

Codecov Report

Merging #62 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   74.28%   74.28%
=======================================
  Files          21       21
  Lines         280      280
=======================================
  Hits          208      208
  Misses         72       72

Continue to review full report at Codecov.

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

authors: TimDaub codecov-io

repo: bigchaindb/js-bigchaindb-driver


text:
saveAsBed writes missing score values as '.' instead of '0'

When using ADAMContext.saveAsBed to write a GenomicRDD to a bed file, if the score is unset, it writes the '.' character as the score instead of '0'. Trying to convert that bed file to a bigBed file, I get:
pass1 - making usageList (17 chroms): 1 millis
Trailing characters parsing signed integer in field 5 line 1 of /data/seqdata/analysis/fakereads/S288C_reference_genome_R64-2-1_20150113/saccharomyces_cerevisiae_R64-2-1_20150113.genes.gff3.sorted.bed, got .

The '.' character is not a valid score in the BED format, unlike GFF. The score value must be set. A sensible default would be '0' or '1000'.

Thank you for submitting this issue, @benwbooth!
We follow the bedtools2 convention with regards to the score column in BED format:

score - The UCSC definition requires that a BED score range from 0 to 1000, inclusive. However, bedtools allows any string to be stored in this field in order to allow greater flexibility in annotation features. For example, strings allow scientific notation for p-values, mean enrichment values, etc. It should be noted that this flexibility could prevent such annotations from being correctly displayed on the UCSC browser.
Any string can be used. For example, 7.31E-05 (p-value), 0.33456 (mean enrichment value), “up”, “down”, etc.
This column is optional.

https://bedtools.readthedocs.io/en/latest/content/general-usage.html
That said, we could add an option to restrict the score field to the UCSC convention on save.  What do you think?

I don't mind if the score value is stored as a string, but right now in org.bdgenomics.adam.sql.Feature it's stored as an Option[Double]:
https://static.javadoc.io/org.bdgenomics.adam/adam-core-spark2_2.11/0.24.0/index.html#org.bdgenomics.adam.sql.Feature
Is there any way the schema can be changed to store the option value as an Option[String]? That way I could format the score as an integer. Right now the score value always includes the decimal point because of how Doubles get converted to String, so the BED files are always incompatible with UCSC.

No, we don't want to change the schema, as it represents the model across all feature formats.
There is a chart documenting the mappings here
https://github.com/heuermh/bdg-formats/blob/docs/docs/source/features.md
The issue is only with saving to text files in BED format, so we might include a method that given a minimum and maximum value, interpolates the Option[Double] score to an integer between 0 and 1000 (with 0 for missing values) and writes that out.

authors: benwbooth heuermh

repo: bigdatagenomics/adam


text:
adam-submit buildinfo is confused

On 0.18.2 release distribution tarball, the buildinfo command seems to be describing a commit to the utils repository
$ ./adam-distribution_2.10-0.18.2/bin/adam-submit buildinfo
Using ADAM_MAIN=org.bdgenomics.adam.cli.ADAMMain
Using SPARK_SUBMIT=/usr/local/bin/spark-submit
Build information:
git.commit.id.abbrev: a27af8f
git.commit.message.full: [maven-release-plugin] prepare release utils-parent_2.10-0.2.3

git.commit.id: a27af8f0c60343b98d187d05dcb06258fbab4b1d
git.commit.message.short: [maven-release-plugin] prepare release utils-parent_2.10-0.2.3
git.commit.id.describe: utils-parent_2.10-0.2.3
git.branch: a27af8f0c60343b98d187d05dcb06258fbab4b1d
git.commit.time: 23.08.2015 @ 09:07:48 PDT
git.remote.origin.url: git@github.com:bigdatagenomics/utils.git
git.build.time: 23.08.2015 @ 09:11:53 PDT

Closed by #888.

If we're fixing this by using --version instead, the buildinfo command should probably be removed.

Oh, sorry, I thought this was completely resolved. I would +1 your suggestion.

+1

authors: fnothaft heuermh massie


text:
[support]

vanilla glass and copper

Do i still need to install other mod to work like description's image

having the same issue

 vanilla glass and copper

having the same issue

check without other mods, maybe something changes the render

it is definitely other mods causing it but unsure which one

To find the problem you need a specific mod that breaks the render, if you manage to find it, open a new issue

authors: Mysticpasta1 POCKET-CATTT bigenergy

repo: bigenergy/windowlogging-renewed


text:
Basic getting started needed

If this is going to be a self-guided repo/tutorial - the front page readme must tell someone with no experience what to do to get hold of the files - at the minute if you have never used git hub you would not have a clue where to start or how to download the files etc.

Agreed, this would also link to #101, all the setup & installations should be straightforward and with a familiar pattern.

Should all be there wish the setup.md instructions. It probably still needs refinement (especially considering that we could direct folks to just use the github.io), but I'm closing this one as done.

authors: IAlibay philbiggin

repo: bigginlab/OxCompBio


text:
Add apex and gsa-crawler to list of BOTS

Would go great with biggora/express-useragent#71.
Thanks for your work!

@biggora any chances you can take a look at this one and #71 and publish a new release 🍻

@jpreynat you should rebase your Pr so that @biggora can easily merge it.

Done.

authors: SamyPesse jpreynat

repo: biggora/express-useragent


text:
Add ability to take a photo of the receipt upon delivery

The photo should be saved to the device for the time being. A subsequent enhancement would make it possible to upload this .

This has been done

This has been done

repo: bigpanther/shipanther


text:
🛑 Jefferson Real is down

In 850f9ab, Jefferson Real (https://jeffersonreal.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jefferson Real is back up in 5c56320.

repo: bigupjeff/my-site-uptime-monitor


text:
🛑 Jefferson Real is down

In 1647973, Jefferson Real (https://jeffersonreal.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jefferson Real is back up in ab8149c.


text:
Listener State Not Listening

I'm running Windows 10 Home. I installed RDPWrap v1.5 and updated the rdpwrap.ini file.
When I restarted rdpwinst I get a couple of StartService error (code 1056) in the CMD window and in the RDP Wrapper Configuration the Listener state is Not Listening.
This is my first time working with RDPWrap and I'm not too knowledgeable with this type of installation. Any help would be greatly appreciated.

Duplicate issue of https://github.com/binarymaster/rdpwrap/issues/40

authors: binarymaster hirolash

repo: binarymaster/rdpwrap


text:
Added documentation on how to add compatibility tests

Rendered

https://gist.github.com/Yush08/a35de1de33c0f9fcc5dc7319c281261b
Here's a few grammatical edits.

repo: bincode-org/bincode


text:
WebDav and 405: Method on allowed

Hi there,
I'm trying to make WebDav working on my instance of pyspider, without success...
If I fire my browser at https://path.to.my.pyspider/dav I correctly see the list of scrapers, and I'm able to navigate through them.
I can even PUT my files with curl:
curl -XPUT https://path.to.my.pyspider/dav/scraper.py --data-binary @scraper.py

But I can't manage to make any WebDav client to work, not on MacOS nor on Linux. What I continuously get is a 405: Method on allowed:
In: c = easywebdav.connect('path.to.my.pyspider', port=5001, path='/dav')
In: c.ls()

OperationFailed: Failed to list directory ".".
  Operation     :  PROPFIND .
  Expected code :  207 UNKNOWN, 301 Moved Permanently
  Actual code   :  405 Method Not Allowed

I tried this both on https, http, or even by skipping the NGINX in front of pyspider, without success.
I wonder if this ever happened to you as well.
Thanks!

try easywebdav.connect('path.to.my.pyspider', port=5001, path='dav')

No luck, unfortunately:
In [1]: import easywebdav

In [2]: c = easywebdav.connect('127.0.0.1', port=5001, path='dav')

In [3]: c.ls()
[stacktrace of easywebdav omitted]

OperationFailed: Failed to list directory ".".
  Operation     :  PROPFIND .
  Expected code :  207 UNKNOWN, 301 Moved Permanently
  Actual code   :  405 Method Not Allowed

And the path is correct, as if I curl I see my scrapers on curl http://127.0.0.1:5001/dav.
Could it be the WsgiDAV (version 2.1.0) is trying to create some files locally? I'm running pyspider inside docker, and I'm not mounting any volume but config.json. The folders inside docker are owned by root, and the user running pyspider does not have write permission on them. I tried investigating in this direction, but I can't really understand whether WsgiDAV needs write permission on anything, and if this is the case, on which folder.

authors: armisael binux

repo: binux/pyspider


text:
sheets stop showing

after changing the parent of a view from NavigationView to NavigationStackView sheets no longer work inside its children eg:
struct ChildView: View {
    @State var showPopup = false
    var body: some View {
        Text("test")
            .onTapGesture { self.showPopup = true }
            .onAppear { self.showPopup = true }
            .sheet(isPresented: self.$showPopup) { Text("popup") }
    }
}

popup is never shown, if I revert back to NavigationView it works fine.

Hi @valexa. The problem is related to the onAppear. The child onAppear is called immediately as soon as the transition animation starts (and not when the transition animation ends). See this other linked issue https://github.com/biobeats/swiftui-navigation-stack/issues/19 basically you are showing the sheet during a transition and this breaks the sheet somehow. Take a look at this snippet here below without the onAppear (I've just added some colours to better see the difference between the pages). Everything it works as expected:
import SwiftUI
import NavigationStack

struct Root: View {
    var body: some View {
        NavigationStackView {
            ZStack {
                Color.green.edgesIgnoringSafeArea(.all)
                PushView(destination: ChildView()) {
                    Text("PUSH")
                }
            }
        }
    }
}

struct ChildView: View {
    @State var showPopup = false
    var body: some View {
        ZStack {
            Color.yellow.edgesIgnoringSafeArea(.all)
            Text("test")
                .onTapGesture { self.showPopup = true }
                .sheet(isPresented: self.$showPopup) { Text("popup") }
        }
    }
}

struct Transition_Previews: PreviewProvider {
    static var previews: some View {
        Root()
    }
}

The result is:

At the moment, unfortunately, the only workaround to show the sheet onAppear is something like (I've just modified the ChildView):
struct ChildView: View {
    private let transitionDuration = 0.2 //<-- this is the default transition duration for the navigation stack
    @State var showPopup = false
    var body: some View {
        ZStack {
            Color.yellow.edgesIgnoringSafeArea(.all)
            Text("test")
                .onTapGesture { self.showPopup = true }
                .onAppear {
                    DispatchQueue.main.asyncAfter(deadline: .now()+self.transitionDuration) { //<-- dispatch after here
                        self.showPopup = true
                    }
                }
                .sheet(isPresented: self.$showPopup) { Text("popup") }
        }
    }
}

You'll get this:

Or, if you specify a custom transition for your navigation stack:
import SwiftUI
import NavigationStack

struct Root: View {
    private let transitionDuration = 2.0 //<-- custom transition duration
    var body: some View {
        NavigationStackView(transitionType: .custom(AnyTransition.opacity), easing: .easeOut(duration: transitionDuration)) { //<-- custom transition
            ZStack {
                Color.green.edgesIgnoringSafeArea(.all)
                PushView(destination: ChildView(transitionDuration: transitionDuration)) {
                    Text("PUSH")
                }
            }
        }
    }
}

struct ChildView: View {
    let transitionDuration: Double
    @State var showPopup = false
    var body: some View {
        ZStack {
            Color.yellow.edgesIgnoringSafeArea(.all)
            Text("test")
                .onTapGesture { self.showPopup = true }
                .onAppear {
                    DispatchQueue.main.asyncAfter(deadline: .now()+self.transitionDuration) {
                        self.showPopup = true
                    }
                }
                .sheet(isPresented: self.$showPopup) { Text("popup") }
        }
    }
}

struct Transition_Previews: PreviewProvider {
    static var previews: some View {
        Root()
    }
}

That did the trick, thanks

authors: matteopuc valexa

repo: biobeats/swiftui-navigation-stack


text:
Validation error- PD review date

validation solved after inputting "2022-04-01T18:26:25.598Z" in field, however this field isn't marked as required

Double checked schema- datetime not required
https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/provenance_domain.json
"review": {
            "type": "array",
            "description": "Description of the current verification status of an object in the review process. The unreviewed flag indicates that the object has been submitted, but no further evaluation or verification has occurred. The in-review flag indicates that verification is underway. The approved flag indicates that the IEEE-2791 Object has been verified and reviewed. The suspended flag indicates an object that was once valid is no longer considered valid. The rejected flag indicates that an error or inconsistency was detected in the IEEE-2791 Object, and it has been removed or rejected. The fields from the contributor object (described in section 2.1.10) is inherited to populate the reviewer section.",
            "items": {
                "type": "object",
                "required": [
                    "status",
                    "reviewer"
                ],
                "additionalProperties": false,
                "properties": {
                    "date": {
                        "type": "string",
                        "format": "date-time"
                    },
                    "reviewer": {
                        "$ref": "2791object.json#/definitions/contributor",
                        "description": "Contributer that assigns IEEE-2791 review status."
                    },
                    "reviewer_comment": {
                        "type": "string",
                        "description": "Optional free text comment by reviewer",
                        "examples": [
                            "Approved by research institution staff. Waiting for approval from regulator"
                        ]
                    },
                    "status": {
                        "type": "string",
                        "enum": [
                            "unreviewed",
                            "in-review",
                            "approved",
                            "rejected",
                            "suspended"
                        ],
                        "description": "Current verification status of the IEEE-2791 Object",
                        "default": "unreviewed"
                    }
                }
            }
        },

Same issue with


text:
Performing the robust Aitchison transformation prior to interpretative multivariate analysis (db-RDA)

Dear @cameronmartino  Cameron,
The RPCA tool inside Gemelli performs these two steps:

Compositional preprocessing using the centered log ratio transform on only the non-zero values of the data (no pseudo count)
Dimensionality reduction through Robust PCA on only the non-zero values of the data ( matrix completion).

I can also perform Step 1 using the decostand() function from the R package vegan with the method rclr.
However, for the second step of creating the PCA using only non-zero values (as Gemelli creates a PCA), I would like to know if any R package could perform this second step to graph a db-RDA. I was not capable to found one R package.
The function cmdscale allows me to use the robust Aitchison method, but I'm unsure if it performs Step 2 as Gemelli does. That's why I'm asking you.
Thank you again,
Magi

Hi @magibc,
There is an RPCA function (step 2) in the works for R (will be in vegan) but it is not ready yet and won't match Gemelli, hopefully it will be soon. To my knowledge there is no working version in R anywhere else yet. For now I advise relying on the python version and I can report back here when the R version of step 2 (RPCA) is done.
Thanks!
Cameron

Thank you very much,
Ok, for the moment I will use your robust.aitchison method included in vegan package and I will find Robust PCA in another R Package. Yes, keep me informed when it is implemented in Gemelli. Thanks again.
Magí.

Ok Cameron. Yes I will try to defend the reviewer comments received because I have tried the function fill.OptSpace() of filling R package but I get an error that I am not capable to solve it. Thanks again.

Hi @magibc,
The R OptSpace function also does not replicate this package exactly. There have been alterations and bug fixes over the years in this implementation that are not reflected in the OptSpace R package. I am working on making sure that is reflected in the vegan implementation but that is not done yet. For now, stick to this Python package.

authors: cameronmartino magibc

repo: biocore/gemelli


text:
Configuration file

We need a configuration file to host all of the URLs, filepaths and what not in a single place.

I would like to help in this issue.How do I start?

Thanks for volunteering to help, @souravsingh ! To start, I recommend to read the contribution guideline (https://github.com/biocore/micronota/blob/master/CONTRIBUTING.md) -->  then think about the framework/data structure of how to refactor this before writing any code --> write the skeleton code, issue a pull request and get feedback from people --> finally, complete the code. Does it make sense? don't hesitate to let us know if you have any questions!

authors: RNAer mortonjt souravsingh

repo: biocore/micronota


text:
Proposal for missing category tags warning

Hi!
I have been confused in the past about what the "Missing tags for categories: [{..}]" meant, since it was not clear from the warning that the tags and categories were the same than those used in "Tags and Filters" in the website.
Here is a proposal to make it clearer to consumers what is meant by replacing:
"Missing tags for categories"
by
"Missing tags corresponding to bioimage.io categories"
I am not convinced this is the most eloquent way to phrase it, but I wanted to open the conversation. :)

Great input! Thanks!

I am not convinced this is the most eloquent way to phrase it, but I wanted to open the conversation. :)

me neither, but I like this more than what we had! 👍
Failing tests are unrelated:
Run tox
  tox
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.8.16/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.8.16/x64/lib
py38: install_deps> python -I -m pip install 'setuptools>=40.[2](https://github.com/bioimage-io/spec-bioimage-io/actions/runs/4106218217/jobs/7086664831#step:5:2)'
py38: freeze> python -m pip freeze --all
py38: pip==23.0,setuptools==67.1.0,wheel==0.38.4
tox: py[3](https://github.com/bioimage-io/spec-bioimage-io/actions/runs/4106218217/jobs/7086664831#step:5:3)8
  py38: commands[0]> pytest
  py38: exit 2 (0.00 seconds) /home/runner/work/spec-bioimage-io/spec-bioimage-io> pytest
  py38: FAIL code 2 (1.[6](https://github.com/bioimage-io/spec-bioimage-io/actions/runs/4106218217/jobs/7086664831#step:5:6)[7](https://github.com/bioimage-io/spec-bioimage-io/actions/runs/4106218217/jobs/7086664831#step:5:8)=setup[1.67]+cmd[0.00] seconds)
  evaluation failed :( (1.76 seconds)
Error: Process completed with exit code 2.

I'm a bit puzzled what's going wrong there...
@constantinpape have you maybe seen this before?
or maybe @k-dominik sees where this goes wrong?

authors: FynnBe jdeschamps

repo: bioimage-io/spec-bioimage-io


text:
Hotfix/Add Admin ARN

Background
Link to issue
https://this-is-biomage.slack.com/archives/C0250TDU1PF/p1623843117020800
Link to staging deployment URL
Links to any Pull Requests related to this
Anything else the reviewers should know about the changes here

Added marcell@biomage.net's ARN as admin for production.

Changes
Code changes
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[ ] Unit tests written
[ ] Tested locally with Inframock (with latest production data downloaded with biomage experiment pull)
[ ] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[ ] Relevant Github READMEs updated
[ ] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[ ] Photo of a cute animal attached to this PR

Should have branched off master

repo: biomage-ltd/api


text:
little confused about train_cf.py

Hi, sir,thanks for the implementation! I'd think it is a great work!
I am little confused with specific counterfactual training steps. It seems that the network in "train_cf.py" only take single counterfactual parent into account during training. But there are actually multi counterfactual parents when infering(Like the case shown in Hugging Face).
So should I run the "train_cf.py" for every counterfactual parent (thickness->intensity->digit) one by one during training ?

Hi,
Thanks for your message.
So the counterfactual training setup we used involves interventions on a single parent at once, that is, for each batch element we randomly select which parent we would like to randomly intervene on. This intervention is then used to compute all the counterfactual parents depending on the associated causal graph.
It is of course possible to intervene on more than one parent at once, although we didn't observe any advantage in doing so in our experiments.
Best,
Fabio

repo: biomedia-mira/causal-gen


text:
🐛 ✖ processing panicked: no entry found for key

Environment information
CLI:
  Version:                      1.7.2
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.18.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "bun/1.0.30"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?
bunx @biomejs/biome check --apply src
Biome encountered an unexpected error
This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:
Source Location: crates/biome_js_semantic/src/semantic_model/scope.rs:115:33
Thread Name: biome::worker_10
Message: no entry found for key
src/types/supabase.ts internalError/panic  INTERNAL  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ processing panicked: no entry found for key
⚠ This diagnostic was derived from an internal Biome error. Potential bug, please report it if necessary.
Expected result
it should not throw error
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Duplicate of https://github.com/biomejs/biome/issues/2683

authors: ematipico ttizze

repo: biomejs/biome


text:
💅 Missing option for lint/suspicious/noMisleadingCharacterClass

Environment information
CLI:
  Version:                      1.9.4
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.17.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.12.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Linter:
  JavaScript enabled:           true
  JSON enabled:                 true
  CSS enabled:                  true
  GraphQL enabled:              false
  Recommended:                  true
  All:                          false
  Enabled rules:
  performance/noDelete
  suspicious/noCatchAssign
  suspicious/noUnsafeNegation
  complexity/useLiteralKeys
  style/useImportType
  complexity/noMultipleSpacesInRegularExpressionLiterals
  a11y/useValidLang
  complexity/noUselessEmptyExport
  suspicious/useNamespaceKeyword
  suspicious/useValidTypeof
  a11y/useValidAriaRole
  correctness/noConstantCondition
  a11y/useAriaActivedescendantWithTabindex
  suspicious/noAssignInExpressions
  style/useDefaultParameterLast
  complexity/noEmptyTypeParameters
  correctness/noConstructorReturn
  style/useSelfClosingElements
  suspicious/noDuplicateParameters
  suspicious/noDuplicateSelectorsKeyframeBlock
  correctness/noUnknownProperty
  style/useTemplate
  correctness/noUnusedLabels
  complexity/noUselessTernary
  correctness/noUnreachableSuper
  suspicious/noCompareNegZero
  correctness/noSwitchDeclarations
  a11y/noAutofocus
  correctness/noUnsafeOptionalChaining
  correctness/noConstAssign
  suspicious/noControlCharactersInRegex
  complexity/noUselessTypeConstraint
  style/noVar
  suspicious/noDoubleEquals
  suspicious/noRedundantUseStrict
  style/useLiteralEnumMembers
  suspicious/noGlobalIsNan
  suspicious/noEmptyInterface
  suspicious/noConstEnum
  suspicious/noMisleadingCharacterClass
  correctness/noPrecisionLoss
  a11y/noLabelWithoutControl
  suspicious/noRedeclare
  correctness/noStringCaseMismatch
  correctness/noSetterReturn
  correctness/noInvalidConstructorSuper
  suspicious/noImplicitAnyLet
  suspicious/noDuplicateObjectKeys
  suspicious/noUnsafeDeclarationMerging
  correctness/noUnreachable
  suspicious/noFallthroughSwitchClause
  complexity/noUselessThisAlias
  complexity/noThisInStatic
  complexity/useOptionalChain
  correctness/noInnerDeclarations
  style/noParameterAssign
  suspicious/noDuplicateCase
  a11y/useValidAnchor
  complexity/useRegexLiterals
  correctness/noSelfAssign
  correctness/noInvalidBuiltinInstantiation
  style/noUselessElse
  style/useShorthandFunctionType
  suspicious/noShadowRestrictedNames
  correctness/noInvalidDirectionInLinearGradient
  suspicious/noImportantInKeyframe
  a11y/useMediaCaption
  complexity/noUselessLabel
  complexity/noUselessCatch
  correctness/noUnsafeFinally
  a11y/useAriaPropsForRole
  correctness/noNonoctalDecimalEscape
  style/useEnumInitializers
  a11y/useHtmlLang
  suspicious/noDuplicateTestHooks
  complexity/noStaticOnlyClass
  style/useWhile
  complexity/useArrowFunction
  style/noInferrableTypes
  a11y/noNoninteractiveTabindex
  complexity/useSimpleNumberKeys
  correctness/useYield
  a11y/noInteractiveElementToNoninteractiveRole
  style/useNumericLiterals
  correctness/noUnnecessaryContinue
  suspicious/noApproximativeNumericConstant
  suspicious/noImportAssign
  suspicious/noLabelVar
  correctness/noGlobalObjectCalls
  suspicious/useDefaultSwitchClauseLast
  a11y/useAltText
  correctness/noEmptyCharacterClassInRegex
  correctness/noUnknownUnit
  suspicious/noSparseArray
  a11y/useIframeTitle
  complexity/noBannedTypes
  a11y/noSvgWithoutTitle
  correctness/noVoidElementsWithChildren
  style/useAsConstAssertion
  correctness/useJsxKeyInIterable
  style/useExportType
  suspicious/noDebugger
  complexity/noUselessLoneBlockStatements
  style/noArguments
  a11y/useValidAriaValues
  suspicious/noCommentText
  a11y/useFocusableInteractive
  correctness/noUnmatchableAnbSelector
  suspicious/noMisleadingInstantiator
  suspicious/noDuplicateJsxProps
  suspicious/noGlobalAssign
  a11y/noPositiveTabindex
  correctness/noEmptyPattern
  complexity/noExcessiveNestedTestSuites
  security/noDangerouslySetInnerHtmlWithChildren
  a11y/useKeyWithMouseEvents
  suspicious/noExtraNonNullAssertion
  suspicious/noPrototypeBuiltins
  correctness/noRenderReturnValue
  security/noGlobalEval
  style/useConst
  style/noNonNullAssertion
  a11y/noRedundantRoles
  complexity/useFlatMap
  correctness/useIsNan
  suspicious/noGlobalIsFinite
  suspicious/noSelfCompare
  suspicious/noShorthandPropertyOverrides
  suspicious/noThenProperty
  suspicious/noAsyncPromiseExecutor
  suspicious/noDuplicateFontNames
  suspicious/useGetterReturn
  security/noDangerouslySetInnerHtml
  style/useNodejsImportProtocol
  a11y/noDistractingElements
  suspicious/noArrayIndexKey
  complexity/noWith
  suspicious/noDuplicateClassMembers
  complexity/noExtraBooleanCast
  performance/noAccumulatingSpread
  a11y/useValidAriaProps
  a11y/noRedundantAlt
  correctness/noChildrenProp
  correctness/noUnknownFunction
  correctness/noInvalidPositionAtImportRule
  suspicious/noConfusingLabels
  suspicious/noSuspiciousSemicolonInJsx
  suspicious/noConfusingVoidType
  suspicious/noFocusedTests
  a11y/useButtonType
  a11y/useSemanticElements
  a11y/noAriaUnsupportedElements
  correctness/noInvalidGridAreas
  correctness/noFlatMapIdentity
  a11y/noBlankTarget
  a11y/useHeadingContent
  correctness/useValidForDirection
  correctness/noVoidTypeReturn
  correctness/noInvalidUseBeforeDeclaration
  a11y/noAriaHiddenOnFocusable
  a11y/useGenericFontNames
  correctness/noUnknownMediaFeatureName
  a11y/useAnchorContent
  complexity/noUselessRename
  style/useNumberNamespace
  complexity/noUselessConstructor
  a11y/noAccessKey
  style/useExponentiationOperator
  style/noUnusedTemplateLiteral
  complexity/noUselessSwitchCase
  style/useSingleVarDeclarator
  suspicious/noExportsInTest
  a11y/noNoninteractiveElementToInteractiveRole
  style/noCommaOperator
  suspicious/noDuplicateAtImportRules
  suspicious/useIsArray
  a11y/noHeaderScope
  complexity/noUselessFragments
  suspicious/noMisrefactoredShorthandAssign
  complexity/noForEach
  suspicious/noClassAssign
  suspicious/noEmptyBlock
  suspicious/noFunctionAssign

Workspace:
  Open Documents:               0

Rule name
lint/suspicious/noMisleadingCharacterClass
Playground link
https://biomejs.dev/playground/?code=YwBvAG4AcwB0ACAAdABlAHgAdAAgAD0AIAAiAGMAdQBzAHQAbwBtAHMAdAByACIALgByAGUAcABsAGEAYwBlAEEAbABsACgALwBbAFwAdQAwADMAMAAwAC0AXAB1ADAAMwA2AGYAXQAvAGcALAAgACcAJwApADsACgA%3D
Expected result
Either be able to use the escape syntax for unicode range representation in regex or add an option like allowEscape in eslint config
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

A missing option isn't definitely a bug but an enhancement 😅
I move this into a discussion


text:
delta-ag7648: make sure i2c-i801 is loaded before creating devices

The order in which the modules must be loaded is super fragile: i2c-i801 must be loaded before instantiating the devices.
Neither i2c-ismt nor any of the cpld drivers may be loaded before creating the devices, else only a subset of devices may be created, or the module may hang in init.
We cannot request modules to be unloaded or not loaded, but we can at least make sure that i2c-i801 is loaded and ready.
Signed-off-by: Jonas Gorski jonas.gorski@bisdn.de

So important I said it thrice.

repo: bisdn/meta-open-network-linux


text:
Initial Template for Request Payment page

These commits introduce the Request Payment flow. This view is available under the "Receive" tab on the Desktop Wallets main navigation view.
The Request Payment form itself currently only includes fields currently supported by the Qt wallet (label, message, and amount). Follow up PR will add support for local notes.
The Amount field in the Request form takes only valid Satoshi/Bitcoin amounts and supports flipping the units with the associated button toggle.
When the Continue button is pressed the Request Confirmation page gets pushed to the stack will eventually reflect the fields inputted in the previous form backed by the output of the WalletModel result. In its current implemention it just has statically defined properties to check the visual layout. The page also contains an address field with the copy icon that can be used to move the address into your clipboard.
Ubuntu screenshots

The piece I'm most concerned about this form is the Amount input field and how to properly sanitize and convert the field. The current object backing it doesnt quite feel right but I am limited by the ability to extend the actual TextInput class.

The piece I'm most concerned about this form is the Amount input field and how to properly sanitize and convert the field. The current object backing it doesnt quite feel right but I am limited by the inability to extend the actual TextInput class.

yeah there are a couple weird things:

decimals when having sats as unit
unnecessary leading zeroes when switching between sats en BTC. i.e. it can display things like 000100 sats

From  from 1b869eb to adff8f

Rebased with main and used PageStack in RequestPayment.qml
Fixed lint issue
Fixed mac build issue with missing bitcoinamount.h in Makefile

Looking good. I know we talked about this before, that the basic concept of the receive page has changed a bit. Away from the two separate pages, and towards creating the QR code directly on the page. Just realized I already implemented this in the web prototype here (note the differences in responsive layouts).
The amount input logic, which you bring up, is not properly implemented in the web prototype. There definitely has to be some sanitation. Something to look out for is that when I type 5000 sats and switch to ₿, it should then show 0.00 005 000 ₿ and not 5000 ₿. There should be a conversion happening. If this is too messy right now, I'd just come back to it in a separate PR.
In a web prototype update I am working on, I am tying the unit toggle to the application setting. So when you switch the unit in the amount input, the wallet balance display in the top left also changes. Wonder if that is intuitive or not. What do you think? In the send page, that unit setting should at least live on a user flow level. So when you toggle, the unit in the amount input, but also the fee selector changes, as well as the unit in the review screen.
Small thing about the input and amount fields is that I can enter unlimited characters (and emoji). Should probs be restricted in some way.

Looking good. I know we talked about this before, that the basic concept of the receive page has changed a bit. Away from the two separate pages, and towards creating the QR code directly on the page. Just realized I already implemented this in the web prototype here (note the differences in responsive layouts).

I will remove the confirmation page and get the request page in alignment with the latest. I won't be able to get QR codes functioning in this PR as that will have to be a follow up once the requests are working end-to-end.

Small thing about the input and amount fields is that I can enter unlimited characters (and emoji). Should probs be restricted in some way.

I'll double check this. I've made some improvements with the amount but I havent tried emojis

Looks great. I know you want to exclude various interaction details and handle those in follow-ups, so I won't comment on those. Just one question about the layout. Does this already include the mobile one where the QR code is inline and the buttons are static at the bottom?

authors: GBKS MarnixCroes johnny9

repo: bitcoin-core/gui-qml


text:
use scenario filenames in list scenarios when using a remote scenario

Fixes #393

I like this overall and it works well with #384: https://github.com/mplsgrant/warnet/actions/runs/9844946239/job/27179455585#step:8:365
However, I'll need to rerun with the logging changes to be sure.

I like this overall and it works well with #384: mplsgrant/warnet/actions/runs/9844946239/job/27179455585#step:8:361
However, I'll need to rerun with the logging changes to be sure.

Great thanks! I was just trying to address your comment when I spotted that we duplicated most of the code in our two scenario run functions, so refactored that in the push I just made:
https://github.com/bitcoin-dev-project/warnet/compare/0c66be68ec2f75393ba33712df03c3eac9771f0f..55e4411062f5daaf991e482da0b2830a0bb25099

post-merge ACK, nice looks good
(.venv) --> warcli scenarios run miner_std
Running scenario miner_std with PID 9231 in the background...
(.venv) --> warcli scenarios active
┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━┓
┃ Active ┃ Cmd        ┃ Network ┃ Pid  ┃
┡━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━┩
│ True   │ miner_std  │ warnet  │ 9231 │
└────────┴────────────┴─────────┴──────┘
(.venv) --> warcli scenarios run --name miner2 miner_std --allnodes
-32000: Scenario --name not found at /root/warnet/src/scenarios/--name.py.
(.venv) --> warcli scenarios run-file src/scenarios/tx_flood.py
Running scenario tx_flood with PID 9337 in the background...
(.venv) --> warcli scenarios active
┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━┓
┃ Active ┃ Cmd        ┃ Network ┃ Pid  ┃
┡━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━┩
│ True   │ miner_std  │ warnet  │ 9231 │
│ True   │ tx_flood   │ warnet  │ 9337 │
└────────┴────────────┴─────────┴──────┘
(.venv) --> warcli scenarios run miner_std --allnodes --interval=1 --mature
Running scenario miner_std with PID 9400 in the background...
(.venv) --> warcli scenarios active
┏━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━┓
┃ Active ┃ Cmd                                        ┃ Network ┃ Pid  ┃
┡━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━┩
│ True   │ miner_std                                  │ warnet  │ 9231 │
│ True   │ tx_flood                                   │ warnet  │ 9337 │
│ True   │ miner_std --allnodes --interval=1 --mature │ warnet  │ 9400 │
└────────┴────────────────────────────────────────────┴─────────┴──────┘

authors: mplsgrant pinheadmz willcl-ark

repo: bitcoin-dev-project/warnet


text:
Remove bloom thin blocks

XT was first to implement thin blocks and did so using backwards compatible protocol calls - merkleblocks.
This protocol has its downsides and has been superseeded by now widely deployed xthin and compact blocks.
It's time to remove bloom thin blocks to reduce code maintenance.

The big diff in ProcessMessage->tx is just indentation change after removing the tryMempool variable.

Pushed a commit to fallback to full block download when re-requesting compact/xthin transactions does not provide all the transcations we're missing. Regression was caught by extended rpc tests.

ACK

repo: bitcoinxt/bitcoinxt


text:
Update default datacarriersize to 220 bytes

https://github.com/Bitcoin-ABC/bitcoin-abc/pull/41
Build on top of #359

Hi there,
a variation of the original patch was merged. The related commits are:
https://github.com/Bitcoin-ABC/bitcoin-abc/commit/40979c5717cca614eb0f52a8e321a62ba3436b8a
https://github.com/Bitcoin-ABC/bitcoin-abc/commit/cbaa7fe447d2b838ff7b14e243093cbb4f602247 (style only)
https://github.com/Bitcoin-ABC/bitcoin-abc/commit/cbf4410912f6512e481f15270329683d4d4378d4
https://github.com/Bitcoin-ABC/bitcoin-abc/commit/0d1b49c9f37f8549540521e6e02a27c261c6da5a
However, you don't necessarily need an activation for this, given it's just a policy/default value update anyway.

Did you review this cherry-pick @dexX7 ?

However, you don't necessarily need an activation for this, given it's just a policy/default value update anyway.

Right, I figured that if someone wants to fill XT's mempool with high fee OP_RETURN transactions, some miner is willing to bump their  -datacarriersize and eat those fees before the fork.

Hey @dagurval, on the first glimpse it looks good!

Rebased. ACK.


text:
[#251] typography management

Fixes #251
The following changes are contained in this pull request:

Replaced the multiple variables specifying font-sizes with a single map.
Added mixins & functions to use that map.
Removed the uneccessary duplication of font-family when the specified webfont is the same as the base font (avoids increased specificity unless necessary).
Fixed a bug whereby base font-size at larger screensizes was incorrectly set.
Bugfix resulted in changed appearance for many elements at larger screensizes — PR also updates reference images for those elements/objects

Changes to objects & trumps

[x] Styleguide documentation has been updated.
[x] npm run test:build script has been sucessfully run and new/changed images committed
[x] npm run stats script run and updated stats/css.json commited

Linting and testing

[x] npm run checks script has been run without errors

Could you re-check the tests? 63 failing for me

I’ve rebased to master.
@RRorg all tests pass for me, which fail for you?

See comment on #258 before merging: https://github.com/bitcrowd/bitstyles/issues/258#issuecomment-272838888

@planktonic working now!

@RRorg great!
As per comments in #258 I’ve updated the styleguide config when running for tests:
npm run styleguide:test
This disables the anti-aliasing and should fix issues with having font-smoothing enabled/disabled on macOS (please check that!). Could also fix similar issues between platforms (windows/linux) but I haven't been able to test that.
Sadly this change means we’re generating a 'special' version of the styleguide just for testing purposes — ideally we test the live system, not some version altered to pass tests — but I see no way around that except to make the styleguide useless as an example of bitstyles’ output.

Can you give me 24 hours to see if there is a better way to get around the AA testing issue? I'm not yet willing to accept that this has to be the best way 😞

Yup, please do!

Please hold off on merging this for now, I am currently working on a way to make the BackstopJS font rendering consistent across devices.

the new commit fixes #258 by forcing the anti-aliasing option to be off across all setups and operation systems
it also increases the misMatchThreshold to 0.15 from 0.1 to better account for slight OS differences
when creating new Backstop scripts, please remember to require('./onLoad.js') and initialize it with the Casper object (see current scripts)

I’ve rebased this to master & made a small fix for background-colour on the styleguide fullscreen pages.
I also regenerated the VRT reference images — @RRorg the images in your last commit wouldn’t validate for me regardless of whether font-smoothing was on or off! Can you pull & run the tests again on your machine?

Yes, this is the good stuff!! Everything working fine now, independent of font smoothing settings!
Full testing satisfaction achieved. 👌
Sorry, I have no idea, something had to have been flakey with my VRT images, although they ran fine on my machine.
Another small improvement I suggest regarding the way test tasks are run: currently we're chaining them with &&, which means the tests won't continue when one of them failed. I suggest changing the chaining to use ;, so all tests run through even if one of them failed and one has a complete overview of what needs fixing.

@RRorg phew! great. I think at one point you mentioned using imageoptim of similar to optimise the images, did you do that with your new images? I recall it giving me problems with image comparison…
If this PR is good to go I’d like to merge this now and look at the test running (&& vs ;) in a separate PR — could you add an issue for that please?

authors: RRorg planktonic

repo: bitcrowd/bitstyles

license: isc


text:
[#500] Generate grid classes

Fixes #500
The following changes are contained in this pull request:

Adds a non-directional class generator, uses that for the grid-template-column classes
Breaks out the col-span and col-start classes, using the generator
Improved docs & examples for these grid-related utility classes

Delete if not applicable:

[x] Storybook documentation has been updated
[x] Your changes have been added to the unreleased section of CHANGELOG.md

I’ll merge and make any of the improvements to docs in another PR :)


text:
3.0版本问题

离线状态下，获取图像会出现崩溃

擦。。忘了修复这个问题了。。
下个版本一定解决！

可以看下 v3.3 有木有解决你的问题

authors: MNevin bitdust

repo: bitdust/EarthLiveSharp


text:
revise Korean translation (2019-03-02)

Hello!
I update my Korean translation.
Although my translation skill is not good, I want to do my best.

@steelbear thank you very much!

authors: bitemyapp steelbear

repo: bitemyapp/learnhaskell


text:
[BUG REPORT]

An error occurred while using and syncing for the very first time.
WORKER:ERROR [2023-08-05T08:42:55.231Z] PROGRESS:SYNC: Error: HTTP code 500 Internal Server Error
    at Proxy._apiError (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/lib/rest2.js:159:17)
    at /Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:51:19
    at BfxApiRouter.route (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/bfx.api.router/index.js:69:14)
    at _route (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:49:23)
    at Object.apply (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:121:27)
    at Proxy._request (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/lib/rest2.js:148:26)
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _getResAndParams (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/prepare-response/index.js:52:18)
    at async FrameworkReportService._prepareApiResponse (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/prepare-response/index.js:150:19)
    at async ApiMiddleware.request (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/api.middleware/index.js:32:20)
    at async DataInserter.getDataFromApi (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-data-from-api.js:93:15)
    at async DataInserter._insertApiDataArrObjTypeToDb (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/index.js:544:11)
    at async DataInserter._insertApiData (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/index.js:461:7)

Debug info

Version
4.9.2

Commit Hash
c6dca30e88b31b00e0963d6ce1f0ba1c1bda5df3

Commit Date
2023-08-02T09:24:10Z

Electron
21.3.3

Chrome
106.0.5249.199

Node.js
16.16.0

V8
10.6.194.26-electron.0

OS version
Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:53 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6020

OS release
Darwin x64 22.6.0

CPUs
Apple M2 Pro x 10

RAM
32GB (0.09GB free)

App RAM limit
4095.75Mb (11.43MB used)

Is BFX API Staging used
No

Main log
    at async _asyncApplyHook
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _getResAndParams (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/prepare-response/index.js:52:18)
    at async FrameworkReportService._prepareApiResponse (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/prepare-response/index.js:150:19)
    at async ApiMiddleware.request (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/api.middleware/index.js:32:20)
    at async DataInserter.getDataFromApi (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-data-from-api.js:93:15)
    at async DataInserter._insertApiDataArrObjTypeToDb (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/index.js:544:11)
    at async DataInserter._insertApiData (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/index.js:461:7)

Worker errors
    at async _asyncApplyHook
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _asyncApplyHook (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-rest.js:65:21)
    at async _getResAndParams (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/prepare-response/index.js:52:18)
    at async FrameworkReportService._prepareApiResponse (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/prepare-response/index.js:150:19)
    at async ApiMiddleware.request (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/api.middleware/index.js:32:20)
    at async DataInserter.getDataFromApi (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-report/workers/loc.api/helpers/get-data-from-api.js:93:15)
    at async DataInserter._insertApiDataArrObjTypeToDb (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/index.js:544:11)
    at async DataInserter._insertApiData (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/workers/loc.api/sync/data.inserter/index.js:461:7)

Worker exceptions
Empty

The issue was opened from the electron app

thanks for reporting, we are investigating how we can fix it

we've sent a patch
could you try the latest version of the app
https://github.com/bitfinexcom/bfx-report-electron/releases/tag/v4.9.3

Thx the sync now worked, but something different seems to be broken. I open another ticker

repo: bitfinexcom/bfx-report-electron


text:
LoadError: cannot load such file -- bitfinex-api-rb

Hi,
I installed bitfinex-api-rb with bundle successfully, after adding it to Gemsfile. Now I'm trying to load the the bitfinex-api-rb into my application in an initializer but get error when trying to start application:

LoadError: cannot load such file -- bitfinex-api-rb

This is the initializer i'm using:
require 'bitfinex-api-rb'

Bitfinex::Client.configure do |config|
  config.key = GLOBAL[:bitfinex_key]
  config.secret = GLOBAL[:bitfinex_secret]
  config.websocket_api_endpoint = "wss://api.bitfinex.com/ws"
end

Any suggestion why?
Thanks.

You need to use
require 'bitfinex'
which is not clear.

Yes, I already figured it out. Thanks anyway.

authors: BeastOfBodmin Bitim

repo: bitfinexcom/bitfinex-api-rb


text:
Select Camera Request

Hello, thanks for making this Companion module. Is there any way to select which camera you want to control via Companion. It would be great if we can cut to a camera on vMix that also selects the camera on the PTZ controller. Cheers!

This module interacts directly with the cameras, not any controllers. So that would be outside the scope of this module.

authors: AOHarness josephdadams

repo: bitfocus/companion-module-canon-ptz


text:
No WOL when generic-ping activated

Hi, companions Wake on LAN is working fine in my network as long as I activate the gerneric-ping. Do you have any idea why this is happening?

Did you mean when generic ping is deactivated?

Im sorry, WOL only works when generic ping is deactivated.

authors: josephdadams magdatev

repo: bitfocus/companion-module-generic-ping


text:
Change default value of AutoToggleScroll in BitModal and BitDialog (#9041)

closes #9041

@coderabbitai review

repo: bitfoundation/bitplatform


text:
App crashes when add google account for backup

It happens when adding google account which is not signed in to google drive.

Tried following scenarios to reproduce the issue

Create new account in the app while selecting account
Created new account outside the app and then use that account
Using account which is not logged in before in mobile and don't have drive access
Previously used account which already have json file uploaded but not currently logged in the app

I did not get any crash, tried on different simulator and physical devices
The app gets restart once, while testing but no crash

Closing this issue on Dev app v1.7.0 (288) as it is not reproducible.

authors: cakesoft-devika cakesoft-rohit

repo: bithyve/hexa


text:
error redeeming code missing code (ErrorPage 500 Internal Error)

We are testing the following config: NGINX -> OAUTH2 -> RUNDECK
Everything works well so far, but... when logging off we get the following error message:
127.0.0.1 - XXXXXXXXXXX@ABCDEF.de [18/Apr/2017:09:51:10 +0000] rundeck-test-1.XXXXXXXXXXX.com GET - "/oauth2/auth" HTTP/1.0 "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36" 202 0 0.000
127.0.0.1 - XXXXXXXXXXX@ABCDEF.de [18/Apr/2017:09:51:10 +0000] 127.0.0.1:4180 GET 127.0.0.1:4440 "/user/logout" HTTP/1.0 "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36" 302 0 0.003
127.0.0.1 - XXXXXXXXXXX@ABCDEF.de [18/Apr/2017:09:51:10 +0000] rundeck-test-1.XXXXXXXXXXX.com GET - "/oauth2/auth" HTTP/1.0 "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36" 202 0 0.000
127.0.0.1 - XXXXXXXXXXX@ABCDEF.de [18/Apr/2017:09:51:10 +0000] 127.0.0.1:4180 GET 127.0.0.1:4440 "/user/loggedout" HTTP/1.0 "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36" 302 0 0.003
2017/04/18 09:51:10 oauthproxy.go:478: 127.0.0.1:27048 error redeeming code missing code
2017/04/18 09:51:10 oauthproxy.go:319: ErrorPage 500 Internal Error Internal Error
127.0.0.1 - - [18/Apr/2017:09:51:10 +0000] rundeck-test-1.XXXXXXXXXXX.com GET - "/oauth2/callback" HTTP/1.0 "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36" 500 331 0.000}}

Any idea? I don't want to rule out any configuration or user error but I already double checked everything and maybe someone could point me to the correct destination.

oauth_1      | 172.18.0.1 - - [14/Jul/2017:08:48:48 +0000] demo.pl GET - "/oauth2/callback" HTTP/1.0 "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0" 500 331 0.000
proxy_1      | 172.18.0.1 - - [14/Jul/2017:08:48:48 +0000] "GET / HTTP/2.0" 500 193 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0" "-"
oauth_1      | 2017/07/14 08:48:57 oauthproxy.go:527: 172.18.0.4:38162 ("172.18.0.1") error redeeming code missing code
oauth_1      | 2017/07/14 08:48:57 oauthproxy.go:349: ErrorPage 500 Internal Error Internal Error
oauth_1      | 172.18.0.1 - - [14/Jul/2017:08:48:57 +0000] demo.pl GET - "/oauth2/callback" HTTP/1.0 "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0" 500 331 0.000
I think same error. Ngix + auth_request

Same story here, but I face it during after entering credentials to github

authors: netflash orlra spommerening


text:
BWC versions?

Hello!
Copay 2.6.0 requires BWC 2.11.0, but there is no such release/tag in this repo. I wonder how to get the required version? And how to submit PRs against that version on BWC (if any) ?
Thanks

Sorry, we forgot to tag in Github.
You can check NPM or
https://github.com/bitpay/bitcore-wallet-client/commits/master/package.json
2.11 is bded7572002fa756243b0aaabb51a4af0e6acf54
We just tagged 4.2
thanks.
On Tue, Sep 6, 2016 at 7:16 AM, Kosta Korenkov notifications@github.com
wrote:

Hello!
Copay 2.6.0 requires BWC 2.11.0, but there is no such release/tag in this
repo. I wonder how to get the required version? And how to submit PRs
against that version on BWC (if any) ?
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bitpay/bitcore-wallet-client/issues/327, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAGCHPMo0qNqLvImwitjLaFRGniHKuugks5qnT1ogaJpZM4J1rfV
.

--
BitPay.com

authors: matiu troggy

repo: bitpay/bitcore-wallet-client


text:
Bitcoin transferred from copay to blockchain wallet yet to receive till now.

It has been almost 3 month now. And the issue is not resolve. The ticket was close without a solution. The last message mentioned by you guys saying that you will get back to us after your system glitch. And you didn’t get back to us. The recipient is making hell of a noise at us because of copay transfer we’re stuck. Our reputation is at stack. This is going out of hand now. We need a response from you guys.

Can we get back the Btc ? It’s been 5 months now. What’s wrong with the network ? We are running a business here. The recipient that we sent to has not received the Btc.

Hello,
Are you still experiencing this issue?
We look forward to hearing from you.
Regards

Yes we are still yet to receive the bitcoin that was send out from copay wallet. It’s been more than 4 months now. The recipient was very angry at us. Please resolve this issue ASAP

Hello @QuestBit  We are sorry you have had this bad experience.
So we can further help, please provide as many of the following details as you can:

Current device used
Current operating system for the device
Current version of the wallet used
Any log files containing error details
Error screenshot
Steps to replicate
BitPay Wallet ID - To get your Wallet ID, open your BitPay application, then go to Settings > Wallets & Integrations > More Options > Wallet Information.

Regards

Current device used- iPhone 7
Current operating system for the device - iOS
Current version of the wallet used - v4.2.0
Any log files containing error details - It was written transaction was not found.
Error screenshot - (2 bitcoin missing)
https://insight.bitpay.com/tx/4c37091528a48b64505bcc293b62005e32b414b57dd7c32e84aa57dd3e79e080
(0.39 bitcoin missing)
https://insight.bitpay.com/tx/03b018698f1f82ca933bba80790971c45470089d5151d19441570842da65fdfb
BitPay Wallet ID - f0c1d277-4f73-4f0f-8afc-0e5ed5d90496

Hello @QuestBit
Thanks for reaching out to us.
As you can see:

https://insight.bitpay.com/tx/4c37091528a48b64505bcc293b62005e32b414b57dd7c32e84aa57dd3e79e080

has 29342 confirmations and the funds are already spent (that is the "S" in parentheses).

https://insight.bitpay.com/tx/03b018698f1f82ca933bba80790971c45470089d5151d19441570842da65fdfb

same as the first transaction, and has 21684 confirmations.

You have sent those funds using a Copay/Bitpay wallet.
The funds have reached the destination address.
They have been successfully confirmed (typically a transaction is considered confirmed with 6+ confirmations, your transactions have 21600+ confirmations).

Whoever owns the destination/destinations addresses, has already spent the funds, so they cannot tell you they did not receive the funds.
On our end, everything is OK, funds were in a Copay wallet, they were sent, and they were successfully received.
If you have sent the funds to a wrong address, unfortunately, there is nothing we can do.
Here is the wallet report, as you can see, the first and 3rd transactions are the ones you mention:
* Wallet info
  ID: f0c1d277-4f73-4f0f-8afc-0e5ed5d90496 Coin: btc
  LIVENET 1-of-1 [BIP44 P2PKH] wallet (status: complete)
  Created on: Mon Aug 21 2017 02:15:52 GMT-0300

* Balance
  Total: 0.00000000 btc (0.00000000 btc locked)
  Confirmed: 0.00000000 btc (0.00000000 btc locked)
  Available: 0.00000000 btc (0.00000000 btc confirmed / 0.00000000 btc unconfirmed)

* No pending tx proposals.

* Main addresses (not including change addresses)
  [Mon Aug 21 2017 02:50:52 GMT-0300] 1Dg4XALCH4rKHuUoh6hbtjagzsRMtQ4MVj (m/0/0)
  [Thu Aug 24 2017 23:49:28 GMT-0300] 1GcmWUNNpMBY6zPRyJbATRAo2WjGa9Zsm2 (m/0/1)
  [Thu Aug 24 2017 23:55:26 GMT-0300] 1KcxqXVKYijC3JCHmAbnytTDcExzLvfTzz (m/0/2)
  [Thu Aug 31 2017 06:49:37 GMT-0300] 199YChdKpx8kddMWkqvMKQbZKpJwV8cgo7 (m/0/3)
  [Thu Aug 31 2017 06:53:10 GMT-0300] 1CfSfTtJK3NHPNBg2A6gEJtwscvC5QiJj (m/0/4)
  [Sat Sep 09 2017 13:04:33 GMT-0300] 19u9JELZswfBKjtqPUqfvwL4HnK3fWyfbh (m/0/5)

* Tx history
  [Tue Jan 16 2018 05:17:47 GMT-0300] 03b018698f1f82ca933bba80790971c45470089d5151d19441570842da65fdfb => sent 0.40098788 btc (fee/kb 0.00225445 btc) (21683 confirmations)
  [Mon Jan 15 2018 01:46:56 GMT-0300] b29015ccb6ae53edba917145b381469f47660ea7bda37c2251179e6852d514c1 => sent 0.10000000 btc (fee/kb 0.00424174 btc) (21862 confirmations)
  [Thu Nov 30 2017 00:45:32 GMT-0300] 4c37091528a48b64505bcc293b62005e32b414b57dd7c32e84aa57dd3e79e080 => sent 2.00000000 btc (fee/kb 0.00162322 btc) (29342 confirmations)

Please let us know if you have any additional questions.
Kind regards.

Hi there,
The wallet address is correct. The address of recipient would not go wrong because the earlier transaction went through and after few minutes another transaction took place to the same address but the bitcoin was not received. I can show you the recipient wallet account. This is the recipient’s wallet ID:
650a6640-25d7-4023-b70c-51bdd793350a
In fact, I’ve contacted blockchain wallet as well. But there’s no reply from their end. How do we suppose to resolve this ?
Thank you.
Regards,
QuestBit
On Tuesday, June 5, 2018, 9:39 PM, BGalliotti notifications@github.com wrote:
Hello @QuestBit
Thanks for reaching out to us.
As you can see:

https://insight.bitpay.com/tx/4c37091528a48b64505bcc293b62005e32b414b57dd7c32e84aa57dd3e79e080

has 29342 confirmations and the funds are already spent (that is the "S" in parentheses).

https://insight.bitpay.com/tx/03b018698f1f82ca933bba80790971c45470089d5151d19441570842da65fdfb

same as the first transaction, and has 21684 confirmations.

You have sent those funds using a Copay/Bitpay wallet.
The funds have reached the destination address.
They have been successfully confirmed (typically a transaction is considered confirmed with 6+ confirmations, your transactions have 21600+ confirmations).

Whoever owns the destination/destinations addresses, has already spent the funds, so they cannot tell you they did not receive the funds.
On our end, everything is OK, funds were in a Copay wallet, they were sent, and they were successfully received.
If you have sent the funds to a wrong address, unfortunately, there is nothing we can do.
Here is the wallet report, as you can see, the first and 3rd transactions are the ones you mention:

Wallet info
ID: f0c1d277-4f73-4f0f-8afc-0e5ed5d90496 Coin: btc
LIVENET 1-of-1 [BIP44 P2PKH] wallet (status: complete)
Created on: Mon Aug 21 2017 02:15:52 GMT-0300

Balance
Total: 0.00000000 btc (0.00000000 btc locked)
Confirmed: 0.00000000 btc (0.00000000 btc locked)
Available: 0.00000000 btc (0.00000000 btc confirmed / 0.00000000 btc unconfirmed)

No pending tx proposals.

Main addresses (not including change addresses)
[Mon Aug 21 2017 02:50:52 GMT-0300] 1Dg4XALCH4rKHuUoh6hbtjagzsRMtQ4MVj (m/0/0)
[Thu Aug 24 2017 23:49:28 GMT-0300] 1GcmWUNNpMBY6zPRyJbATRAo2WjGa9Zsm2 (m/0/1)
[Thu Aug 24 2017 23:55:26 GMT-0300] 1KcxqXVKYijC3JCHmAbnytTDcExzLvfTzz (m/0/2)
[Thu Aug 31 2017 06:49:37 GMT-0300] 199YChdKpx8kddMWkqvMKQbZKpJwV8cgo7 (m/0/3)
[Thu Aug 31 2017 06:53:10 GMT-0300] 1CfSfTtJK3NHPNBg2A6gEJtwscvC5QiJj (m/0/4)
[Sat Sep 09 2017 13:04:33 GMT-0300] 19u9JELZswfBKjtqPUqfvwL4HnK3fWyfbh (m/0/5)

Tx history
[Tue Jan 16 2018 05:17:47 GMT-0300] 03b018698f1f82ca933bba80790971c45470089d5151d19441570842da65fdfb => sent 0.40098788 btc (fee/kb 0.00225445 btc) (21683 confirmations)
[Mon Jan 15 2018 01:46:56 GMT-0300] b29015ccb6ae53edba917145b381469f47660ea7bda37c2251179e6852d514c1 => sent 0.10000000 btc (fee/kb 0.00424174 btc) (21862 confirmations)
[Thu Nov 30 2017 00:45:32 GMT-0300] 4c37091528a48b64505bcc293b62005e32b414b57dd7c32e84aa57dd3e79e080 => sent 2.00000000 btc (fee/kb 0.00162322 btc) (29342 confirmations)

Please let us know if you have any additional questions.
Kind regards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hello @QuestBit
Thanks for reaching out to us.
We cannot check that wallet ID since it is not a Bitpay wallet.
The transaction has properly gone through, and if the destination address is right, they have received the funds, and there is nothing to argue about.
We have provided you with enough evidence, that should be more than sufficient.
If there is something else we can do for you, please let us know.
Kind regards.

Hood funds please hacked emote os
On Wed, Jul 11, 2018, 12:25 AM QuestBit notifications@github.com wrote:

Hello,
Thanks for the prompt reply.
So, how do i check the wallet ID ? Check with blockchain wallet ? The
address is definitely right as what I've told but the recipient has not
received the funds. We have even checked the wallet, the fund was not
received. What are the other ways to locate the funds ? By the way, you
guys are very sure that the fund is not with copay wallet still ?
Thanks.
Regards,
QuestBit
On Wednesday, July 11, 2018, 2:41:47 AM GMT+8, BGalliotti <
notifications@github.com> wrote:
Hello @QuestBit
Thanks for reaching out to us.
We cannot check that wallet ID since it is not a Bitpay wallet.
The transaction has properly gone through, and if the destination address
is right, they have received the funds, and there is nothing to argue about.
We have provided you with enough evidence, that should be more than
sufficient.
If there is something else we can do for you, please let us know.
Kind regards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bitpay/copay/issues/8023#issuecomment-404049103, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYPEsz2eRS6_Xc7zb7USzUdiZ7cYyj4-ks5uFYxkgaJpZM4SDHsX
.

@jamesscookk  Please explain your inquiry

Hood funds please hacked emote os

I can recover your wallet if you want need help send me email : anywalletrecovery@gmail.com

authors: BGalliotti QuestBit Ronarkdel jamesscookk

repo: bitpay/wallet


text:
Web + API structure?

If #89 is merged, it means that when user runs the forum:install command, he will receive both Web & API routes.. i'm not sure if this should be expected behaviour or not since a user might not want both web & api routes. Thoughts?

Maybe add a second command to install api routes? Like forum:api:install or something like that

We can add an optional tag such as --with-api.

authors: AndreasElia Dylan-DPC NowNewStart

repo: bitporch/laravel-forum


text:
🛑 Plex is down

In 30cfe05, Plex (https://plex.bitpushr.net/web/index.html#!/) was down:

HTTP code: 530
Response time: 55 ms

Resolved: Plex is back up in 973b26b.

repo: bitpushr/upptime