OpenSSL maintenance 2024/09

Description of changes
This PR combines the usual OpenSSL version bump with some maintenance:

OpenSSL now releases only on Github -> switch to URLs on Github for all versions
Revisit if we can use the latest OpenSSL version as the default now (set it to openssl_3_3).
Bump all OpenSSL packages to the latest available version for CVE fixes.

Fixed CVEs:

Fixed possible denial of service in X.509 name checks. (CVE-2024-6119)
Fixed possible buffer overread in SSL_select_next_proto(). (CVE-2024-5535)

Changelog(s):
The changes are the same for all updated OpenSSL versions. See changelog.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Happy with the general approach here as discussed on Matrix, but I’m −1 on introducing 3.1 as yet another version, when we’ll already have 3.0, 3.1, and 3.3. Ideally we’d only have one version of OpenSSL; Arch, Alpine, and Void ship 3.3 and 1.1, and Fedora ships only 3.2.
I think that we should rename openssl_3 to openssl_3_0 if it’s no longer going to be the default, though that might be unnecessary churn if we can hopefully remove it after the 24.11 release.

Happy with the general approach here as discussed on Matrix, but I’m −1 on introducing 3.1 as yet another version, when we’ll already have 3.0, 3.2, and 3.3. Ideally we’d only have one version of OpenSSL; Arch, Alpine, and Void ship 3.3 and 1.1, and Fedora ships only 3.2.
I think that we should rename openssl_3 to openssl_3_0 if it’s no longer going to be the default, though that might be unnecessary churn if we can hopefully remove it after the 24.11 release.

Fair, reduce to 3_3, 3_0, 1_1 for 24.11?

I'm currently testing if some important packages like systemd still build with OpenSSL 3.3. Therefore some more patches are included. I needed to bump ibm-sw-tpm2 and use a better maintained swtpm for tests in tpm2-tss to work.

Fair, reduce to 3_3, 3_0, 1_1 for 24.11?

Sounds good to me! I’d also be okay with leaving 3.2 in and just dropping the other versions in bulk after the release if everything goes well; whatever your preference is.

After some issues in the past, where e.g. systemd failed to build with a recent OpenSSL version, I  tried to fix these.
Older discussions about updating OpenSSL default:

https://github.com/NixOS/nixpkgs/pull/244893
https://github.com/NixOS/nixpkgs/pull/221206

OpenSSL 3.x is supposed to be API- and ABI-stable. If a package pins the version, that’s a problem with the package. If OpenSSL breaks API, that’s an upstream bug. I’m all for doing what every other package ecosystem seemingly does, which is ship the latest OpenSSL by default. Both MacPorts and Homebrew ship OpenSSL 3.3. Homebrew also offers OpenSSL 3.0 as a separate package in case something really needs it.
https://openssl-library.org/policies/technical/stable-release-updates/

This needs rebasing for conflicts, but I’m otherwise minded to merge.

@emilazy: Rebased.

After discussion on Matrix I think we have consensus to ignore the LTS releases and just package and track the latest stable releases going forward. Thank you for your work on this!

Bisect says 7932bf565673e9192a18dcc4f23ad1c69644e437 openssl: set default to openssl_3_3 broke mumble in staging as:
$ nix build --no-link github:NixOS/nixpkgs/staging#mumble -L
...
mumble> [ 97%] Built target mumble_autogen
mumble> make[2]: *** No rule to make target '/nix/store/kdazpap3bnl355f3nv7p01dpwad8c90w-openssl-3.3.2-dev/lib/libcrypto.so', needed by 'mumble'.  Stop.
mumble> make[2]: *** Waiting for unfinished jobs....

@trofi I looked into this, but have not found the root cause yet. In this error message, somehow the dev-Output got used to provide the lib folder. While it technically contains a lib folder, only the pkg-config and cmake-Files are there. The "useful" lib folder is in the out-Output.

Something like this will probably fix it (builds still in progress):
diff --git a/pkgs/development/libraries/openssl/default.nix b/pkgs/development/libraries/openssl/default.nix
index 0313841dce30..951505d1fd08 100644
--- a/pkgs/development/libraries/openssl/default.nix
+++ b/pkgs/development/libraries/openssl/default.nix
@@ -233,6 +233,10 @@ let
         echo "Found an erroneous dependency on perl ^^^" >&2
         exit 1
       fi
+    '' + lib.optionalString (lib.versionAtLeast version "3.3.0") ''
+      # cleanup cmake helpers for now (for OpenSSL >= 3.3), only rely on pkg-config.
+      # pkg-config gets its paths fixed correctly
+      rm -r $dev/lib/cmake
     '';

     passthru.tests.pkg-config = testers.testMetaPkgConfig finalAttrs.finalPackage;

When I have more time, I'll may also patch the CMake-Scripts and don't delete them.


How to creat  .hic and .assembly files ?

hi,
I have generated a BAM genomic-alignment file of my Hi-C reads and the ordering and orientation final.fasta file. Now I want to load .hic and .assembly files to correct assembly errors by Juicebox Assembly Tools.  What should I do to creat .hic and .assembly files?
Thanks

Hi wlhCNU,
Please see Genome Assembly Cookbook for a comprehensive guide on how to work with our tools:
https://www.dnazoo.org/methods
Best,
Olga


enh: Do not rely on discovery.etcd.io, use AWS metadata to bootstrap

Inspired from https://github.com/MonsantoCo/etcd-aws-cluster/blob/develop/etcd-aws-cluster
We use the following cloud-init to provision our etcd clusters and we find it much better to rely on AWS metadata rather than a public service with no guarantees on.
#cloud-config

coreos:
  etcd2:
    advertise-client-urls: http://$private_ipv4:2379
    initial-advertise-peer-urls: http://$private_ipv4:2380
    listen-client-urls: http://<IP_ADDRESS>:2379
    listen-peer-urls: http://$private_ipv4:2380
  fleet:
    public-ip: $private_ipv4
    etcd_servers: "${peers}"
  update:
    group: ${channel}
    reboot-strategy: ${reboot-strategy}
  units:
    - name: docker.service
      runtime: true
      command: start

    # etcd and fleet are initially stopped. We'll start them when the peers have been calculated
    - name: etcd2.service
      command: stop
    - name: fleet.service
      command: stop

    - name: etcd-peers.service
      command: start
      content: |
        [Unit]
        Description=Write a file with the etcd peers that we should bootstrap to
        After=docker.service
        [Service]
        Restart=on-failure
        RestartSec=10
        EnvironmentFile=/etc/environment
        ExecStartPre=/usr/bin/docker pull peopleperhour/etcd-aws-cluster:latest
        ExecStartPre=/usr/bin/docker run --rm=true -v /etc/sysconfig/:/etc/sysconfig/ peopleperhour/etcd-aws-cluster:latest
        ExecStart=/usr/bin/systemctl start etcd2

    # Query AWS metadata service when this EC2 instance starts to get info about instance's self. e.g. IP address.
    - name: fleet-metadata.service
      runtime: true
      command: start
      content: |-
        [Unit]
        Description=Inject EC2 Metadata into Fleet
        After=docker.service
        [Service]
        Type=oneshot
        EnvironmentFile=/etc/environment
        ExecStartPre=/usr/bin/docker pull peopleperhour/ec2-metadata
        ExecStart=/usr/bin/bash -c '\
          mkdir -p /run/systemd/system/fleet.service.d; \
          conf_file=/run/systemd/system/fleet.service.d/666-ec2-metadata.conf; \
          zone=$(docker run --rm peopleperhour/ec2-metadata -z   | sed "s/: /=/g"); \
          id=$(docker run --rm peopleperhour/ec2-metadata -i     | sed "s/: /=/g"); \
          ip=$(docker run --rm peopleperhour/ec2-metadata -v     | sed "s/: /=/g" | sed "s/ /_/g"); \
          type=$(docker run --rm peopleperhour/ec2-metadata -t   | sed "s/: /=/g"); \
          echo "[Service]" > $conf_file; \
          echo "Environment=FLEET_METADATA=role=${role},$ip,$id,$type,$zone"  >> $conf_file;'

    - name: fleet-reloaded.service
      command: start
      content: |
        [Unit]
        Description=Ensure fleet starts with updated metadata
        After=docker.service
        After=fleet-metadata.service
        [Service]
        Restart=on-failure
        RestartSec=10
        EnvironmentFile=/etc/environment
        ExecStartPre=/usr/bin/systemctl daemon-reload
        ExecStart=/usr/bin/systemctl start fleet
write_files:
    # Pre-configure the core user with authentication to our private Docker Hub repo (as the pphrobot hub user).
    - path: /home/core/.dockercfg
      owner: core:core
      permissions: 0644
      content: |
<EMAIL_ADDRESS>    - path: /etc/systemd/system/etcd2.service.d/30-etcd_peers.conf
      permissions: 0644
      content: |
        [Service]
        EnvironmentFile=/etc/sysconfig/etcd-peers

users:
  - name: pmoust
    coreos-ssh-import-github: pmoust
    groups:
      - sudo
      - docker
      - wheel
  - name: core
    coreos-ssh-import-github-users:
      - pmoust

manage_etc_hosts: localhost

output:
 ~  fleetctl --endpoint=http://etcd.prod.peopleperhour.com:2379 list-machines -l | wc -l
      21
 ~  fleetctl --endpoint=http://etcd.prod.peopleperhour.com:2379 list-machines -l | grep etcd
19a78c198fb84df1ba3f4a70ef61ec38	<IP_ADDRESS>	instance-id=i-59a88fa0,instance-type=t2.micro,placement=us-east-1a,public-ipv4=not_available,role=etcd
1d0f278b67054fcb8639395ec5c37c59	<IP_ADDRESS>	instance-id=i-dbe0e25b,instance-type=t2.micro,placement=us-east-1e,public-ipv4=not_available,role=etcd
aff38657419e45e4ae3d90ea3e41a044	<IP_ADDRESS>	instance-id=i-9b06f01f,instance-type=t2.micro,placement=us-east-1b,public-ipv4=not_available,role=etcd
b889ecb26a4a4a8ebe8b2380ac98b015	<IP_ADDRESS> 	instance-id=i-07d9db87,instance-type=t2.micro,placement=us-east-1e,public-ipv4=not_available,role=etcd
f6e554e1bbab4bb79f7d9049cd3f9f79	<IP_ADDRESS> 	instance-id=i-bd18ee39,instance-type=t2.micro,placement=us-east-1b,public-ipv4=not_available,role=etcd

Thats indeed a nice idea. Thanks for showing us a working example :)
Are you by any chance open-sourcing those images?

Sure, will do within the day

@zeisss we basically run your stack in production, as far as I can tell we 've created very similar architecture and tooling (minus bare metal stuff), so we developed this inhouse at the same time as you did, just not as a product.
What's the best way getting in touch with you to plan on contributing to your FOSS efforts?

What's the best way getting in touch with you to plan on contributing to your FOSS efforts?

We have a Mailinglist and an IRC channel (https://github.com/giantswarm/kocho#contact) although currently rather empty. For future efforts we need to do some planing soon - if you are interested we could do a hangout to have a short chat about usage etc.


Allow configuring the cache file path

Fixes #16
This PR does a few things

Allow configuring the name of the cache file so your tests can have a different file from your development
Give Webdrivers::Cache a delete method to delete the cache
Clear out the test cache after the specs run

Now to figure out why this breaks windows


Cells with Left/Right margin show swipe content in the margin

The library probably wasn't intended to be used in this way, but I figured you'd want to know about it.

Oh, adding the cells to the list was incidental, I forgot about iOS's desire to render things outside a view's bounds. The real fix was adding:  removeClippedSubviews={true} to the cell

solution above is working, in addition, if you have marginHorintal in your view, just add overflow: 'hidden' in style.


pythonPackages.pymupdf: init at 1.16.2

python bindings for mupdf. Provides the fitz module for
https://github.com/dsanson/termpdf.py that I am trying to package.
NB: when packaging termpdf.py (https://github.com/teto/home/blob/master/config/nixpkgs/overlays/pkgs/termpdf/default.nix), it can't import fitz
and looking at the .termpdf.py wrapper, I found the addition (sys.argv[0]...), is that normal ?
import sys;import site;import functools;sys.argv[0] = '/nix/store/j7aifx4jh1crvj90l93khrzk7llwzqrr-termpdf.py-0.1.1/bin/termpdf.py';functools.reduce(lambda k, p: site.addsitedir(p, k), ['/nix/store/j7aifx4jh1crvj90l93khrzk7llwzqrr-termpdf.py-0.1.1/lib/python3.7/site-packages','/nix/store/i50wf0cg1l46y4l7x41waypliiapfmry-python3.7-setuptools-41.0.1/lib/python3.7/site-packages'], site._init_pathinfo());
__version__ = "0.1.1"
__license__ = "MIT"

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@jonringer I authorize you to test your new superpowers (once and if you get them) on this PR ;)

@GrahamcOfBorg build pythonPackages.pymudpf

unfortunately still no super powers :(

@GrahamcOfBorg build pythonPackages.pymupdf

@GrahamcOfBorg build pythonPackages.pymupdf


When cache is destroyed there is no hint

Hint is not showing up notifying players about the cache being destroyed.

derp hint system is based off of a public event handler and what that means is that public event handlers only work when ran on a dedicated box.


Use NullPointerException instead of IllegalStateException for null inputs

The current implementation throws an IllegalStateException for null inputs, which is not consistent with Java standards. Update the API to throw a NullPointerException when null inputs are encountered.

495c5e065a47f7ffbe117b194c39a40c9f2197ab


Update the direct upload endpoint to attach uploaded files to NeetoEditor::Asset model

Update the default direct upload endpoint such that the file will be attached to the NeetoEditor::Asset model. This will prevent it from being purged by the NeetoCommonsBackend::PurgeUnattachedFilesWorker worker.

@AbhayVAshokan _a

Released beta version: 1.27.0-beta.1


Fix for Issue #94

Body data is grep only for today, but if there is no data for today, the values getting to unknown.
I changed it to grep the body data from the last 7 days an use the last values.
Not the best fix but it works

@kruemelro thanks a lot, will merge and do update work this weekend!

@kruemelro Thanks a lot for this PR, sorry for the delays!


wavtap 0.3.0 does not install correctly

$ brew cask install wavtap
==> Downloading https://github.com/pje/WavTap/releases/download/0.3.0/WavTap.0.3.0.pkg
Already downloaded: /Library/Caches/Homebrew/wavtap-0.3.0.pkg
==> Running installer for wavtap; your password may be necessary.
==> Package installers may write to any location; options such as --appdir are ignored.
Error: pkg source file not found: '/opt/homebrew-cask/Caskroom/wavtap/0.3.0/WavTap 0.3.0.pkg'

/cc @johnhamelink

Hmm, there's a space in the last line instead of a dot. I will check this out over the weekend if possible!


Platform Agnosticization

Makes DateRangeHLSStream platform agnostic by replacing bash os calls with python native tools

Use shutil to copy files
Use TempDirectory to store temporary downloaded files

Thank you! That calls for the need to setup automatic code style checking.


Implement did:dht

Swift will need did:dht. Implement it!

Resolution implemented here: https://github.com/TBD54566975/web5-swift/pull/15


0.9.x is not compatible to 0.4.x

Describe the bug

MINOR version when you add functionality in a backwards-compatible manner, and

via https://semver.org/
As far as I can judge from the changelog, OutlineButton was refactored to a parameter on Button. This is a great change many welcome, however it's not backward-compatible according to semver.
Expected behavior
Expected would be that OutlineButton remains existing until version 1.0.0 is released, I guess.

Looking into this. Thanks for raising @TimDaub!


ci: relax commit message format restrictions

There were unnecessary restrictions on the commit message format which were never used.

We discussed offline that it's better to leave these in place for now.


community[minor]: Add support for pebblo server and client version

Description:
PebbloSafeLoader: Add support for pebblo server and client version
Documentation: NA
Unit test: NA
Issue: NA
Dependencies:  None

CC: @baskaryan


AMCFOC – Refactor the Supervisor motor-independent part

Following up on the excellent work done on the dictionary (see #54), we need to deal with the motor-independent part of the Supervisor.

[!important]
It's true that we aim to address the AMCFOC, but it's essential to keep in mind that at a certain time we'll have also to integrate the AMCBLDC CAN handler and 4 motors (AMC4DC) instead of 2.

At the moment, the motor-independent part of the architectural model needs to send out the following data:

ReceivedEvent

EventType
Limits struct
MotorConfig struct
Targets struct
PID struct

So all the possible data is passed at once and depending on the event type the related struct is read.
A motor-independent block could implement different dispatching functionalities depending on the input (which is the output of the CAN Decoder in the AMCBLDC).

Let's also remember that we need to check with a Sequence Diagram the timing of the interactions within the Supervisor.

Will do!

A motor-independent block could implement different dispatching functionalities depending on the input

Something along these lines:

The decoding part can be an interface to the inter-core communication, since I am not sure if it's convenient to send directly via ICC a N number of ReceivedEvent structures.
It could be necessary to add a specialized decoding logic in that "Decoding" block above, similar to the CAN one.
If not needed, we could most likely use the entry points of this new architectural model to attach to the communication logic and the rest of the firmware.
Maybe we could align in a meeting @pattacini @marcoaccame

My hunch is that we can get away without the Decoding block in the new architecture, meaning that one input to the main model will be represented by Events itself.
Therefore, we should make sure that this approach is fine for the AMCFOC and the AMC4DC.
For the AMCBLDC, either we will drop the CAN codec or we refactor it to make it compatible with the Events signal. Probably, the latter still has value since for a CAN board it could be useful to keep communication and control altogether in the mode.

My hunch is that we can get away without the Decoding block in the new architecture, meaning that one input to the main model will be represented by the signal Events itself.

I guess the only limit is the size of the ICC buffer, I can check the size of the ReceivedEvents struct at the moment to have a first approximation of the needed quantity.

I guess the only limit is the size of the ICC buffer, I can check the size of the ReceivedEvents struct at the moment to have a first approximation of the needed quantity.

In my mind, between the data traveling over ICC and Events, there can be a further intermediate stage, which is fully FW-based, i.e., no model. Thus, compression can be still there.

The number of bytes seems quite high. However, optimizing now could be counterproductive. We will get back to this later.
Does this structure deal with a single motor or two motors?

Sending the motor configuration every step and reading it only when needed might not be efficient, but we can change the behavior in the future if desired/needed.

Just for clarification, we don't send motor configuration every step. Nonetheless, memory allocation is persistent.

If that's the case, we can then proceed to the other parts of the motor-independent supervision for the AMCFOC. I do not think much has changed since the original sketch of the architecture:

The next important component to tackle will then be the Kinematic Controller, tasked with implementing Position/Velocity control at the joint level.
Ideally, it would not be too dissimilar from the Control_Outer which is already implemented. The bare minimum changes would, I think, involve the reading of the joint encoder instead of the motor, and some state-machine to handle the joint control mode.

We agreed that the control of the joint will be inherited as done now in EMS/AMC, that is hand-coded.
Later, we will evaluate the possibility of extending MBD to cover this part as well.
As of now, we will be dealing just with the control of the motor per se, as done in the AMCBLDC>

Ok 👍 This is a huge simplification, then!
So to recap, the supervisor-rx had these two components that would be considered motor independent:

State handler
Can message handler

I implicitly ignored them in this issue, because I think the new version of the motor-specific supervisor already has those blocks' features included, in some form.
State handler
The state handler is made by:

board state handler
fault handler
can messsages for loop

board state handler

This FSM is already embedded in the Control Mode handler, and contains placeholders.
fault handler
The fault handler was part of the motor-specific supervisor and was moved inside it.
can messages for loop
This FSM is used for iterating over the 4 elements of the decoded can messages. This function is already implemented by the ForEach subsystem
Can message handler

We are not really talking about can messaging at this stage, but the array of decoded messages, with the contents put in the proper structs. The FSM takes the array of structs and depending on the can messages for loop sends the data to the rest of the blocks.
This is handled in the new supervisor by this:

Each subchart basically sets the outputs of the supervisor and that's it, the rest of the motion controller reads them.

So in the end, I don't think we are missing important parts of the supervisor behaviour, what is needed is:

restore the custom code calls
create proper test to verify if all conditions turn out as expected

Closing in favor of #72.


error with FAWE when i type /mine reset minename

error: https://mclo.gs/Jw94U9C
realmines version: 1.8.2
FAWE version: 2.8.1
Server Version: git-Paper-794 (MC: 1.16.5)

It's not an error from RealMines. It's an error from FAWE.


Got a random test failure in Travis for Scala 2.12

Log message:
[info] ! Java 8 Generators.arbitrary generation with a granularity generates appropriate ZonedDateTimes: Falsified after 58167 passed tests.
[info] > Labels of failing property:
[info] Hours: +45746443-09-27T04:00+13:45[NZ-CHAT]
[info] > ARG_0: (com.fortysevendeg.scalacheck.datetime.jdk8.granularity.package$$anon$3@2c86bf85,com.fortysevendeg.scalacheck.datetime.jdk8.GenJdk8Properties$$$Lambda$2144/1142872265@35fcbed8)
[info] > ARG_1: +45746443-09-27T04:00+13:45[NZ-CHAT]

Also seen here https://travis-ci.org/47deg/scalacheck-toolbox/jobs/268091917#L1680 in #56

Also in #67
[info] ! Java 8 Generators.genZonedDateTime with a granularity generates appropriate ZonedDateTimes: Falsified after 13487 passed tests.
[info] > Labels of failing property:
[info] Hours: +171884780-09-28T04:00+13:45[NZ-CHAT]
[info] > ARG_0: (com.fortysevendeg.scalacheck.datetime.jdk8.granularity.package$$anon$3@4ecbac6a,com.fortysevendeg.scalacheck.datetime.jdk8.GenJdk8Properties$$$Lambda$7798/1684101346@3db07e15)
[info] > ARG_1: +171884780-09-28T04:00+13:45[NZ-CHAT]

Also in #315 (with other failures in other tests in that suite)


The results are inconsistent with using pytorch directly

System Info
accelerate version: 0.20.3

Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[X] My own task or dataset (give details below)

Reproduction
# Results using pytorch directly
input_mean:   tensor(0.1748, device='cuda:2') tensor(0.1748, device='cuda:2')
input_mean:   tensor(0.1760, device='cuda:2') tensor(0.1760, device='cuda:2')
ddp_test - Iter [2] Epoch(train) [1]/[1] [2/2]  lr: 1.000e-04, eta: 0:00:00, time: 0.273, data_time: 0.057, memory: 197MB, loss: 0.00728, grad_norm: 0.10437
ddp_test - Iter [2] Epoch(test) [1]/[1] [10/10]  PSNR: 23.86963

# Results accelerate launch  my_script.py
input_mean:   tensor(0.1748, device='cuda:2') tensor(0.1748, device='cuda:2')
input_mean:   tensor(0.1760, device='cuda:2') tensor(0.1760, device='cuda:2')
ddp_test - Iter [2] Epoch(train) [1]/[1] [2/2]  lr: 1.000e-04, eta: 0:00:00, time: 0.219, data_time: 0.012, memory: 100MB, loss: 0.00729, grad_norm: 0.10437
ddp_test - Iter [2] Epoch(test) [1]/[1] [20/20] PSNR: 23.86795

The difference is in the following code. I don't know what Accelerator.prepare is doing since the input data is the same in both cases.
model = accelerator.prepare(model)

Expected behavior
Check the results and make the results the same as pytorch. If possible, please tell me what happens in accelerator.prepare(model) of a model.

Please provide us all your code, we can’t know anything otherwise


Solution restore

Fix for #72
Find all the solution files and issue a nuget restore or dotnet restore against them.
Could do with review
In general, the testability is poor.

In general, tests and testability are an issue, which means isolating large parts of the app that deal with file system, git or GitHub api.

Not necessarily... can always (and probably should) require the developer to grab their own access tokens for testing - we can also dump a token into environment variables in travis to run the tests over there


prometheus: add optional path with additional manifests

What type of PR is this?
/kind feature
What this PR does / why we need it:
In the past, we added all service/pod monitors directly into manifests directory within cl2/prometheus. This is not really scalable solution if one wants to test other components. Let's add option to allow to specify additional monitors from different path.
Special notes for your reviewer:
Example use-case: https://github.com/marseel/perf-tests/commit/11075f78427c079801fb7b6ed53041dbad05a763
Example command:
CL2_PROMETHEUS_PVC_ENABLED=false go run ./cmd/clusterloader.go             -v=4             --testconfig=./testing/dns/config.yaml             --provider=kind             --enable-prometheus-server             --tear-down-prometheus-server=false             --nodes=2             --report-dir=./report                     --kubeconfig=$HOME/.kube/config --prometheus-additional-monitors-path=./testing/dns/manifests/ --prometheus-apiserver-scrape-port=6443

/lgtm


ImageJ Viewer

I  still prefer the ImageJ Viewer than the BDV viewer; it is more intuitive and friendly (for old school Fiji people..). It would be ideal if by default it would be opened

This is unfortunately too much work. But I can try to make BDV more user friendly.
What is the main thing that you would like to see there?

I m getting familiar with BDV..However,  what I like in FIJI viewer is: the Auto display in the B/C control window, the fact you can do (for some files) Z-projections and use basic FIJI options (such as make measures).

Great, very useful the Hypersatck viewer! It seems that is even faster sometimes than the BDViewer....


Support for hdf5 visibilities integration

The task is to integrate visibilities from hdf5 formats to karabo pipeline,

The data structure is the following.
/index_map/freq <HDF5 dataset "freq": shape (16,), type "|V16">
/index_map/pixel <HDF5 dataset "pixel": shape (3145728,), type "<i8">
/index_map/pol <HDF5 dataset "pol": shape (4,), type "|O">
/map <HDF5 dataset "map": shape (16, 4, 3145728), type "<f8">

Add unit tests for this functionality


Running Laravel with workerman

Hello,
Is it possible to have workerman running laravel framework and serving all its requests?
What should be done to do so?

Hi @cayolblake
Here is a repo may help you.
https://github.com/JieAnthony/laravel-octane-workerman

After trying it, it seems quite unstable, got memory leaks and leans bad performance against other Octane packages.
I'll read through the code and hopefully might be able to mimic what's been done there in a simpler way.
Thanks for pointing me to this package :)

@cayolblake Maybe now you can try laravel-octane-workerman

@mouyong you mean this https://github.com/JieAnthony/laravel-octane-workerman

@cayolblake yes.

I only use the websocket client on my server , workerman is a perfect option.


Kitchen tests are all failing with gem conflicts on main now that it is 18.x

Probably has something to do with the gems not being pushed to rubygems, but it looks like they're all installed correctly and the error message from bundler is nonsense.

fixed by chef/appbundle-updater#100


Generate an actual RPM spec instead of converting the .deb

Generate an actual RPM spec file instead of building a .deb and using alien.

So why isn't it in upstream?
Is is that hard to provide RPMs for end users?

if you look at my spec file it is really simple


Move sprite objects to the game_sprites file

#127
moving all in-game sprite classes to game_sprites.py. And improving the code of them.

the feature is still in progress, so there may be errors.


Add explainer text to account home page

People were confused in some rounds of usability testing. Add some
explainer text to help them understand what the account is for.
Trello

New page (details closed):

Details open:

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

I have a ✅   from Rose on the layout and content


gRPC pre 1.0 packages

We need pre-1.0 packages for grpcio and grpcio-tools for:

[ ] Ruby
[ ] Python
[ ] Node.js
[ ] C#
[x] Obj-C
[x] PHP

This is a tracking issue for the packages.

I was just thinking of releasing on Monday for other reasons...

PHP package version 1.0.0RC1 has been released

Objective-C 1.0.0-pre1 is released: https://github.com/grpc/grpc/releases/tag/objective-c-v1.0.0-pre1

I have kicked off an artifact build here: https://grpc-testing.appspot.com/view/Artifacts/job/gRPC_build_artifacts/1325/

Ruby artifacts building failed - fix is in #7461.

Python is released.

C# Packages released.
The Visual Studio Nuget client sees the updated packages from the Nuget v2 and v3 feeds, so they should be ready.
Waiting for full 1.0 version though to update API docs and GRPC package versions in greeter and route guide examples.

Looks like no tasks remain for this issue! @hsaliak are you going to use this issue to springboard into another one or is it closin' time?

Good question -- @nicolasnoble I think it may be worth sending a mail to grpc-users asking people to try it and report issues... what do you think?

Yes, that's sensible to announce that we've pushed 1.0.0-pre1.
On Thu, Jul 21, 2016 at 12:10 PM, Kailash Sethuraman <
<EMAIL_ADDRESS>wrote:

Good question -- @nicolasnoble https://github.com/nicolasnoble I think
it may be worth sending a mail to grpc-users asking people to try it and
report issues... what do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/7423#issuecomment-234353449, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG8bpoKWuEBPLK5O98ophXpdeWzHEz1Lks5qX8QvgaJpZM4JN5M3
.

This has now been announced. Thanks everyone for doing this.


ngrok AuthToken added to build pipeline

Added ngrok AuthToken to the build Pipeline to support running Android smoke tests.

To get the actions to run successfully you have to open the PR from a branch of bc-wallet-mobile, not from a fork


Use pre-commit ci

The pre-commit team now offer a CI service. In addition to running
the linters against pull requests, the service will automatically apply
the changes to the PR and update the hook versions.

pre-commit.ci doesn't allow network access at runtime. Without it, the pip-tools jobs that ensure all requirements files are up-to-date will always fail. We can revisit this idea if they ever change that.


Documentation issue

I'm not sure if this was intended but in the Usage section, more specifically under the One file with optional custom attributes paragraph in all the three examples the closing brackets and the semicolons are missing.
assets_css('example.css', array('media' => 'screen')
should be
assets_css('example.css', array('media' => 'screen'));
and so on. Same issue but only with the semicolons in the section above.

thank you!
if you want to improve the documentation,  I will like to see a pull-request made by you

Thank you, I'd really love to! I'll make a pull-request in the next following days then


Enhance version catalogs' public API to support tooling

Hello!
Context

We at JetBrains are interested in supporting version catalogs in a more helpful way than it is done now. For this to be done, we need your help in exposing some implementation details in the Gradle API.
Particularly, we'd like to get more information about version catalogs' structure after the project configuration.
Expected Behavior

It would be really helpful to get some sort of mapping from the version catalog's name to the toml file it uses. Certainly, there are other ways to specify version catalog structure (like using DSL in settings.gradle), but it looks like toml files are a much more popular format.
Current Behavior

There is no such API.

@knisht
What are the use cases that you have in mind? What API would you need for that?
When a TOML file is imported, some of its entries might be overridden in scripts. How would you handle that?

@h0tk3y Hello!
The main issue I am trying to solve is https://youtrack.jetbrains.com/issue/IDEA-279603.
I expect some kind of a listener which is invoked when the version catalogs machinery accesses some *.toml file. It also may be some class that provides a Map from version catalog name to a *.toml.
Regarding overriding in scripts, this is a problem indeed. I cannot think of a way how to solve it reliably, but it doesn't mean that we should decline this feature.

A TOML fle can be imported from a local file or a remote one (e.g https://melix.github.io/blog/2022/02/micronaut-version-catalog.html). It's only used to generate accessors. If the file didn't change, it won't even be read, so "accessing the TOML file" isn't the right thing either. The TOML file is just one source for the catalog.
There is a similar need for automating dependency upgrades (see what we do for Micronaut: https://github.com/micronaut-projects/micronaut-build/blob/ec7d227d1e1b263b94f1b2ecc8ac91f36bd63225/src/main/java/io/micronaut/build/catalogs/MicronautVersionCatalogUpdatePlugin.java#L17).
Basically there are I think a couple requirements:

accessing the "model" of a catalog, before it's actually realized
adding some "source" to the model, so that tooling can do things like link to the source files

As a side note, the generated accessors contain some comments linking to the source catalog file, but it's a poor man's solution since it doesn't quite make sense for external catalogs.

IDEA needs an access to a model of version catalogues to provide better navigation. For now, it is only possible to navigate to generated accessors. Which is useless for most of our users. They expect IDEA to go to alias definitions: in settings.gradle or toml files. Former is hard to handle (Groovy/KTS), but latter syntax is not dynamic and we can start with it.
related ticket  https://youtrack.jetbrains.com/issue/IDEA-282725/Navigate-from-versionCatalogs-alias-to-settingsgradle


Failed assertion: line 201 pos 12: '!_debugDuringDeviceUpdate': is not true.

Failed assertion: line 201 pos 12: '!_debugDuringDeviceUpdate': is not true.
return Stack(children: viewContent);

Hi @Li-00
When opening an issue, please try to provide all or some of the information indicated in the template so that we can address this issue properly.
More specifically, please provide the information indicated below:

A completed and minimal reproducible code sample that can reproduce this issue
The complete stack trace
The output of flutter doctor -v
Which environment did this issue happen in? (Android/iOS/Web/MacOS/Windows/Linux)

May be similar: https://github.com/flutter/flutter/issues/84241


useMutation refetchQueries not working when passing a GQL DocumentNode

Describe the bug
Passing a DocumentNode to refetchQueries as parameter does not trigger an update for the query, whereas passing the name of the query does. As shown here both should be supported.
To Reproduce
Given the example component below:
If you call someMutation(), while passing the query name in refetchQueries, the console will show the useQuery triggered message. Whereas when {query: EXAMPLE_QUERY} is passed the console will not show the message.
Example component:
<script>
const EXAMPLE_QUERY = gql`
    query example_query {
        doSomething {
            id
            name
        }
    }`;

export default {
    name: "test",
    mounted() {
        const { onResult } = useQuery(EXAMPLE_QUERY);
        onResult((result) => {
            console.log("useQuery triggered");
        });
    },
    methods: {
        someMutation() {
            const { mutate: mutationCallback } = useMutation(MUTATION_QUERY, {
                refetchQueries: [
                    // THIS DOES NOT WORK
                    // {query: EXAMPLE_QUERY}

                    // THIS WORKS
                    'example_query'
                ]
            });

            mutationCallback().then(() => {
                console.log("mutation executed");
            });
        }
    }
}
</script>

Expected behavior
Both the query name and DocumentNode should trigger useQuery to update.
Versions
vue: 3.2.41
@vue/apollo-composable: 4.0.0-beta.1
@apollo/client: 3.7.1

After some more searching around I found this issue #1326
Are there any plans on updating the dependency version of apollo ?

I have the same issue in my react project:
Versions
React: 17.0.2
@apollo/client: 3.8.6


Add IsComputed  helper for field

Could you please add tests?
Could you also add more of a description to the PR? I'm struggling to figure out what this is for or how it would be useful.

Added a better commit message and a test. The only real use case is so that I can use Unpack for structs that have computed fields. Unpack lives in the other repo - and we're currently not able to skip over copying fields that are computed since that information is encapsulated.

@pratikprasad you can't skip by specifying ws:"-"?

nvm @alexandrinaw explained to me that this is in the other conversion direction. let ws do its thing basically, chuck the struct's value.


Delete to_ibis parameter from make_users_data and make_sessions_data

…data`

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (f004f8e) to head (d67d0d7).
Report is 48 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #103   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           13        13
  Lines          999       996    -3
=========================================
- Hits           999       996    -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix: next curriculum rebased

This was a joint effort between myself and @ahmadabdolsaheb.
Outstanding issues:

[x] Editor tabs appear on small screens, even with SHOW_UPCOMING_CHANGES=false
[x] upcoming challenges break the build, despite develop being fine.

I had to reinstate the explicit schema customisation for Gatsby, but the React challenges bug seems not to have appeared this time around.  I don't quite understand what the difference is, but it does seem to be working.

One thing could use cleaning up: the PropTypes are complaining.  It shouldn't matter, but I'll fix that tomorrow.

When I came to fix the PropType problems, I couldn't reproduce them.  If anyone encounters some, let me know.


Fix hardcoded rmw_gid_t length

This fixes the following build failure on rolling:
  error[E0308]: mismatched types
     --> src/subscription/message_info.rs:120:19
      |
  120 |             data: rmw_message_info.publisher_gid.data,
      |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected an array with a fixed size of 24 elements, found one with 16 elements

Thanks @esteve!

@nnmm thank you for fixing this bug!


Auto convert reals to ints and vice versa.

Allow real outputs to send data to int inputs
Allow int outputs to send data to real outputs

Yeah sure it's possible each node add a function that dictates whether or not a certain type is allowed as input.
But I'm not sure what you mean by not all real nodes will have integer input support, the pr doesn't actually pass an array of integers, it converts the array to a real array (by chopping off the fraction) and passes that so it's impossible for a node to not support it.


Updating peer dependencies.

Some dependencies are out of date, after yarn add material-ui-next-responsive-table I get this errors.
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "material-ui-next@npm:material-ui@next".
I have installed "@material-ui/icons": "^1.0.0-beta.43" and "material-ui": "^1.0.0-beta.40", in my project, which should be latest.
This PR should fix this issues.


edbrowse: 3.5.2 -> <IP_ADDRESS>

This update also fixes javascript support by installing the edbrowse-js binary and replacing the path in the exec("edbrowse-js") call with the nix store path.

Built locally thanks.


[BEAM-7923] An indicator of progress in notebooks

The problem: when an intended blocking call such as show, collect
or head is invoked, the user sometimes doesn't realize the code is
still running and blocking. Also, the * prompts in notebooks are
easily ignored and sometimes buggy. We need an obvious progress
indicator to tell the user that the data/pipeline is being processed
and potentially expose more metrics about running pipelines through
the mechanism.
Added a ProgressIndicator class that functions as a context manager
to display/remove a spinner on entering/exiting a blocking code
execution.
Added a progress_indicated decorator to make any callable adapt the
ProgressIndicator.
When in notebooks, a spinner is displayed. When in ipython but
without frontends, texts will be displayed on entering/exiting.
Otherwise, NOOP.

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @aaltay
R: @davidyan74
R: @rohdesamuel
PTAL, thx!

retest this please


OMPL with continuous joint state spaces

This adds support for continuous joint state spaces at the expense of some performance. It represents the state space as a compound state of several real vectored states and SO2 state spaces concatenated together

Would it make sense to maintain two implementations of RobotStateSpace, and use the faster RealVectorStateSpace if no joints are continuous?

@cdellin yes probably.

Several of the tests on Travis failed. Travis was having reliability issues earlier today, so I restarted the tests in case this was related.

I re-ran tests on this pull request and on master. It looks like these changes did indeed break something.
@mklingen Can you run the tests locally and try to figure out what's going on?

Ok. Looks like all the planners failed. Not really sure what state this branch was in.

Actually all the RRT planners succeeded and SBL/KPIECE both failed...

@mkoval  most of my plans are failing because of this:
[StateSpace.cpp:715] No default projection is set. Perhaps setup() needs to be called
[OMPLPlanner.cpp:338 PlanPath] Planning failed: No projection evaluator specified

So I need to create a custom projector for the compound state space, yeah?

I think the bug is actually the first line:
[StateSpace.cpp:715] No default projection is set. Perhaps setup() needs to be called

This is the same bug as #34. I'll fix this and see if the issue goes away.

I get the same warning after @mkoval's merge

Where are we on this? @mklingen, can you work on this during the hackathon today?

We know that a projection function has to be created for the state space. Not sure who was going to do this, but I can look at it this morning.

I pushed a custom projection evaluator. It fixes the "no default projection evaluator" problem, but KPIECE still fails to find plans. I think I am not implementing it properly.

The [ompl documentation][(http://ompl.kavrakilab.org/projections.html) says that:

Most planning algorithms use a data structure (in addition to the tree/graph of motions) for guiding the exploration of the space. In many cases, this data structure is in the form of a discretization of the state space. For practical purposes, discretizing the state space itself is not feasible, due to its high dimensionality. An approach taken by many algorithms is to use projections from the state space to a low dimensional Euclidean space (Rk, k usually around 2 or 3), and discretize that Euclidean space instead. This includes algorithms such as ompl::geometric::EST, ompl::geometric::SBL, ompl::geometric::KPIECE1. This projection can also be thought of as a hash function that maps states to cells in a low dimensional Euclidean space.

My suspicion is that simply returning the vector of projections results in a state space that is too large (e.g. 6 dimensions on ADA) to discretize. Planning SEGFAULTs when it attempts to allocate memory for that grid.

Yeah you're right about that Mike. I'll look at ways of projecting it down to 2 or 3 dimensions instead. I can likely just copy what's going on in RealVectorStateSpace and assume the continuous joints are just real-vectors with limits at -PI to PI. That would make it return suboptimal solutions with a planner like KPIECE but still manage the continuous joints with planners like RRT which don't require a projection to a low-dimensional space.

tests are now passing locally!

RRT fails some percentage of time now because its too slow... otherwise tests are passing

I upped the time limit for the tests and they're now passing on Travis.


Scrollbar Styling

In this issue, I will propose styling the scrollbars on SkyCrypt
The Problem
the problem with unstyled scrollbars is that they are white on most browsers which clashes with the dark esthetic of the site.

notice how the scrollbars are the same contrast as the text drawing attention away from the content to the scrollbars.
My Solution
add styling to the scrollbars with ::-webkit-scrollbar and scrollbar-color
however ::-webkit-scrollbar also affects mobile which looks weird because on mobile people expect to have the auto-hide zero-width scrollbar that comes by default.
The solution is to detect whether the scrollbar has a width in javascript when the page first loads and if it does then add the styles.
// checks if the scrollbar has a width should be true with desktop style scrollbars
if (window.innerWidth > document.documentElement.clientWidth) {
  document.documentElement.classList.add('style-scrollbar');
} else {
  document.documentElement.classList.remove('style-scrollbar');
}

.style-scrollbar {
    scrollbar-color: var(--icon-hex) #323232;
}

.style-scrollbar *::-webkit-scrollbar-track
{
    border-radius: 12px;
    background-color: rgba(60,60,60,0.5);
}

.style-scrollbar *::-webkit-scrollbar
{
    width: 12px;
    height: 12px;
}

.style-scrollbar *::-webkit-scrollbar-thumb
{
    border-radius: 12px;
    background-color: var(--icon-hex);
}

.style-scrollbar body::-webkit-scrollbar
{
    background-color: #282828;
}

@media (max-width: 900px){
    .style-scrollbar #nav_bar_line {
        bottom: 9px;
    }
    .style-scrollbar #nav_items_container {
        padding-bottom: 10px;
    }
}

.style-scrollbar #nav_items_container::-webkit-scrollbar-track
{
    background-color: transparent;
}

.style-scrollbar #nav_items_container::-webkit-scrollbar
{
    height: 8px;
}

here is what it looks like on Chrome (WebKit).

and here is what it looks like on Firefox (non-WebKit).

Could you make a PR potentially for this? You seem to have already put alot of work into coding this.

Could you make a PR potentially for this? You seem to have already put alot of work into coding this.

I have a good understanding of Javascript and CSS but not MongoDB or Redis. because this I haven't made a PR. If someone can take the code I wrote and make a PR from it that would be great if not then I will try to find some time to learn how.

I'll try to write this up soon. FYI, you don't need mongo or redis experience to add design stuff like this in, you just need to install them to run the site.

I've added your code, but it does not seem to be fixing the issue.

You can look at it on the metalcupcake5-scrollbars branch, js code is at the bottom of public/resources/js/stats.js, and css code is in the middle of public/resources/css/index.css

I can't figure out how to install Redis on Windows and MongoDB wants me to make an account or something. so I cant run the site on my local PC.
I played around with injecting public/resources/js/stats.js and public/resources/css/index.css into the live site and I'm fairly certain the problem your encountering is that the javascript is run before the HTML flow this can be fixed by using load instead of DOMContentLoaded
#88 should fix this problem

Ok, I'll merge this and test it later when I have time.

I have made an error by attaching the load listener to the wrong object please accept #89

It works!

Added with #90

oops forgot to close


chore: Python Dependencies -- Requirements.txt

Add requirements.txt so that the Python dependencies for the project can be easily installed on a "fresh" machine.

#cdec4a4d5bcee1b11fa322580fe700bb241b8bc6


Why does csbindgen convert CString to sbyte?

They don't even have the same size, and CString is not ffi safe.

My expectation is that it should be passed by pointer.
It can be converted to a String in C# using new string(sbyte* value).
I chose sbyte for the convenience it provides.


add foreign key for dbsbuffer_file

@amaltaro, Alan please review (Just found the missing constraint while investigating the issue #7006) But this doesn't fix the issue though.

Changes look good Seangchan.

test this please


[Config] Add input file dialog

This will get input file path and send it to webview content.
ONE-vscode-DCO-1.0-Signed-off-by: Yeseo Kang<EMAIL_ADDRESS>

from Issue #58
from Draft #117


View Code not working in Chrome browsers

Selecting "Code" from the View menu does nothing in Chrome browsers on Mac.
The annotation view works as intended.
Looking at the code, the #sg-code-container DIV is not modified to be shown onscreen in Chrome, but just sits outside view. Also, If I modify the placement, so it becomes visible, the tabs still doesn't actually show the code.
Works well if I switch to Safari for example.

@bjornwang What version of Chrome are you running? I'm using Version 44.0.2403.130 (64-bit) on Yosemite and have no issues with Chrome, Firefox or Safari.

Version 44.0.2403.130 (64-bit). Same as you. Haven't made the leap to Yosemite yet, though.
Might be a local thing, but I'm not experiencing trouble with other websites.
I should mention that this only applies when viewing one element. The code panes do become visible when viewing "all" alements.
Could this be some access issue caused by opening the generated Pattern Lab site from file, possibly? The old --allow-file-access-from-files flag didn't do the trick, though ...

Yeah, it's totally because you're opening the site from a file. It throws a XMLHttpRequest request when it tries to load the page into codeviewer.js. I would just run it through the OS X built-in Apache and be done with it.

My bad then, sorry to be wasting your time. Wasn't aware of the different security models for Chrome and other browsers. Thanks for clearing that up.


Timeout of 40000ms exceeded. For async tests and hooks, ensure "done()" is called

I am receiving this error again and again even after including
mocha: {
timeout: 500000, // 500 seconds max for running tests
}

mostly bcoz performUpkeep is never called i tried with 1000 sec too but its not working. Even when i use chainlink subscription id mentioned in gitrepo

I am receiving this error again and again even after including mocha: { timeout: 500000, // 500 seconds max for running tests }

I think you are testing locally and added blockConfirmation of value 5. If its the case, its happening because of that. Because on local host its it wait for more blocks to mine but in actuall no blocks are mined. So you can make it 1 for localhost and 5 or whatever for testnet and it will work

Share your repo

I am facing the same issue and have not found any solution yet.
const { network, ethers } = require("hardhat")
const { developmentChains, networkConfig } = require("../helper-hardhat-config")
const { assert, expect } = require("chai")
!developmentChains.includes(network.name)
? describe.skip
: describe("Raffle Unit Tests", async () => {
let raffle, vrfCoordinatorV2Mock, chainId
chainId = network.config.chainId
      beforeEach(async function ({ getNamedAccounts, deployments }) {
          const { deployer } = getNamedAccounts()
          await deployments.fixture(["all"])
          raffle = await ethers.getContract("Raffle", deployer)
          vrfCoordinatorV2Mock = await ethers.getContract("VRFCoordinatorV2Mock", deployer)
      })

      describe("constructor", async function () {
          it("Initializes the constructor correctly .. ", async function () {
              //Ideally we should only have 1 assert per it statement.
              const raffleState = await raffle.getRaffleState()
              const interval = await raffle.getInterval()
              assert.equal(raffleState.toString(), "0")
              assert.equal(interval.toString(), networkConfig[chainId]["interval"])
          })
      })
  })


update packages + fixed support for TypeScript 2.4

removed build files (commonjs and bundle) from git as it's only useful in npm package.

I've been afraid to update this libraries deps so I won't break compatibility with older angular2 versions. Where and what was the issue with typescript 2.4? I have a project using it (and I recently updated to typescript 2.4 although disabled lib check since rxjs had an issue with "lift" and I think angular itself had another...) maybe it's better to just fix the typescript 2.4 issue and keep the deps old as long as it can support all the old versions along with the latest ones?

rxjs has fixed the lift issue in 5.4.2 also updating packages doesn't means we drop the support of angular2 (to be verified).

I'm not 100% sure that angular 2.x accepts AOT complied metadata of 4.x so I'll have to verify it before merging this pull request.
Anyway, thanks for the pull request! much appreciated.

Ok as you like, let me know if you want keep the old deps ;).
For typescript 2.4 the solved issue is in oauth.service
Type 'Oauth1Service | Oauth2Service' is not assignable to type '{ open(options?: IOauth1Options, userData?: any): Observable<Response>; }'.

Maybe I'll just add a notice and bump the major version. I think most people who care about using the up-to-date version also updated the angular version itself.


Add activated to loadState

So when the script has loaded is one thing,
when it's run it's loaded function it needs an activated state so nothing re-runs the loaded function again.
There is a script area which highlights any re-runs of code,  you can see it's output in the console.

Don't need to worry about this now.  The code now checks if the script is loaded before running it's init function.


feat: added support for MariaDB

Added support for MariaDB and added related tests

@fretz12 this looks great! Thank you :)


Need more control on when the client side of the stream is closed

Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker?
Create new issues for bugs and feature requests. An issue needs to be actionable. General gRPC discussions and usage questions belong to:

grpc.io mailing list
StackOverflow, with grpc tag

Please don't double post your questions in more locations; we are monitoring both channels, and the time spent de-duplicating questions is better spent answering more user questions.
What version of gRPC and what language are you using?
Python / gRPC 1.7.1
What operating system (Linux, Windows, …) and version?
MacOS High Sierra
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.6
What did you do?
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
Currently, on the client side, after the generator completes it sends a close for the client's send channel. This is perfectly legal, however, it seems to cause some issues with with a gRPC server in Java, or perhaps it's how it's been implemented in this particular case. In this case, the server assumes, when it receives a half close from the client, that the client is done and no longer interested in receiving events from the server.
There seems to be no issues using go or node clients with this particular server.
What did you expect to see?
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?

Could you provide small code snippits with this particular use case? That would be help us push forward

I agree with @ncteisen about needing to see sample code. I'm also confused about the request - applications should have complete control over when the request stream is closed, although they may have to implement their own iterator object.


Remove publish_rate parameter

It was removed https://github.com/ros-controls/ros2_controllers/pull/468

CI is failing, the service_msgs package was added 3 weeks ago https://github.com/ros2/rcl_interfaces/commits/rolling/service_msgs and it was released last week, maybe a package that uses this dependency is not released yet and that's why is failing?

just to clarify, are you asking me the question? :smile:

@bmagyar or @destogl can you relaunch the Github actions ?

just to clarify, because that's unrelated to my PR, are you asking me the question? smile

This was not a question, it was a clarification, but for some reason I added ?.  Let's relaunch CI


GFPGAN executing fine for 1 image at a time, but OOM when using -n parameter, is there method to clear memory in between ?

I read about GFPGAN needing more GPU memory, however I always manage to get it working with 1 generation for example for img2img, it produces a double resolution correctly, however if I used -n2 or anything higher, the next generation fails due to a Out of memory error. Is it possible to clear the memory between generations as for example, the rtx 3060 ti seems to be able to always execute it correctly for only 1 image but not in batch?
Thank you, awesome project with insanely fast developments !!

I read about GFPGAN needing more GPU memory, however I always manage to get it working with 1 generation for example for img2img, it produces a double resolution correctly, however if I used -n2 or anything higher, the next generation fails due to a Out of memory error. Is it possible to clear the memory between generations as for example, the rtx 3060 ti seems to be able to always execute it correctly for only 1 image but not in batch?
Thank you, awesome project with insanely fast developments !!

This error is precisely why I made the changes I did. @lstein If you were looking for a reference. My PR  #102 solves this issue too.

I think we're really close. Just need to slow down the pulling into main
until the dust settles!
Lincoln
On Fri, Aug 26, 2022 at 12:23 PM blessedcoolant @.***>
wrote:

I read about GFPGAN needing more GPU memory, however I always manage to
get it working with 1 generation for example for img2img, it produces a
double resolution correctly, however if I used -n2 or anything higher, the
next generation fails due to a Out of memory error. Is it possible to clear
the memory between generations as for example, the rtx 3060 ti seems to be
able to always execute it correctly for only 1 image but not in batch?
Thank you, awesome project with insanely fast developments !!
This error is precisely why I made the changes I did. @lstein
https://github.com/lstein If you were looking for a reference. My PR
#102 https://github.com/lstein/stable-diffusion/pull/102 solves this
issue too.
—
Reply to this email directly, view it on GitHub
https://github.com/lstein/stable-diffusion/issues/112#issuecomment-1228692780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3EVKJNMW2WKPVZ23RRPLV3DVQLANCNFSM57XHYHZA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Lincoln Stein
Head, Adaptive Oncology, OICR
Senior Principal Investigator, OICR
Professor, Department of Molecular Genetics, University of Toronto
Tel:<PHONE_NUMBER>
Cell:<PHONE_NUMBER>
@.***
E**xecutive Assistant
Michelle Xin
Tel:<PHONE_NUMBER>
@.*** @.**>
Ontario Institute for Cancer Research
MaRS Centre, 661 University Avenue, Suite 510, Toronto, Ontario, Canada M5G
0A3
@OICR_news
https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Foicr_news&data=04|01|Michelle.Xin%40oicr.on.ca|9fa8636ff38b4a60ff5a08d926dd2113|9df949f8a6eb419d9caa1f8c83db674f|0|0|637583553462287559|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=PS9KzggzFoecbbt%2BZQyhkWkQo9D0hHiiujsbP7Idv4s%3D&reserved=0
| www.oicr.on.ca
Collaborate. Translate. Change lives.
This message and any attachments may contain confidential and/or privileged
information for the sole use of the intended recipient. Any review or
distribution by anyone other than the person for whom it was originally
intended is strictly prohibited. If you have received this message in
error, please contact the sender and delete all copies. Opinions,
conclusions or other information contained in this message may not be that
of the organization.

Yeah having the discussions of tradeoffs of memory and processing time! :)
Just to capture it, on the main branch, on my config, immediately after dream loads, the difference in directly GPU memory allocation of the python process is following with --gfpgan and not gfpgan.
metrics are pretty stable across multiple startups/runs, which is encouraging, so - 'cause I'm lazy - I'm not going to compute an average across runs for now.
After Startup:
Without GFPGAN:  4,976,196
With GFPGAN:       5,551,696
after I give it a prompt, memory shoots up, I use the following prompt, and specify -G1 for the with GFPGAN
a man wearing a pineapple hat -S1

T1:
Without GFPGAN: 9,207,408
With GFPGAN:      9,811,572
T2:
Without GFPGAN: 9,207,408
With GFPGAN:      9,811,572
T3:
Without GFPGAN: 9,209,456
With GFPGAN:      9,811,572
T4:
Without GFPGAN: 9,209,456
With GFPGAN:      9,811,572
T5:
Without GFPGAN: 9,209,456
With GFPGAN:      9,813,620
so pretty stable, but a little bit of allocation after the fact
So at least on my box, GFPGAN increases VRAM util by ~600MB
Keep in mind that other things on your desktop system use dedicated VRAM, so if you have a bunch of tabs open, or open up photoshop to load an image after it's done, those are going to change how much free VRAM you have available.

More Data:
a man wearing a pineapple hat -S1 -n2

No-GFPGAN
|===========================================================================|
|                  PyTorch CUDA memory summary, device ID 0                 |
|---------------------------------------------------------------------------|
|            CUDA OOMs: 0            |        cudaMalloc retries: 0         |
|===========================================================================|
|        Metric         | Cur Usage  | Peak Usage | Tot Alloc  | Tot Freed  |
|---------------------------------------------------------------------------|
| Allocated memory      |    4085 MB |    6199 MB |    2079 GB |    2075 GB |
|       from large pool |    4039 MB |    6152 MB |    2063 GB |    2059 GB |
|       from small pool |      45 MB |      52 MB |      15 GB |      15 GB |
|---------------------------------------------------------------------------|
| Active memory         |    4085 MB |    6199 MB |    2079 GB |    2075 GB |
|       from large pool |    4039 MB |    6152 MB |    2063 GB |    2059 GB |
|       from small pool |      45 MB |      52 MB |      15 GB |      15 GB |
|---------------------------------------------------------------------------|
| GPU reserved memory   |    7348 MB |    7348 MB |    7348 MB |       0 B  |
|       from large pool |    7294 MB |    7294 MB |    7294 MB |       0 B  |
|       from small pool |      54 MB |      54 MB |      54 MB |       0 B  |
|---------------------------------------------------------------------------|
| Non-releasable memory |  113503 KB |    1518 MB |    3475 GB |    3475 GB |
|       from large pool |  111232 KB |    1516 MB |    3454 GB |    3453 GB |
|       from small pool |    2271 KB |       4 MB |      21 GB |      21 GB |
|---------------------------------------------------------------------------|
| Allocations           |    1150    |    1195    |  220511    |  219361    |
|       from large pool |     344    |     363    |  118388    |  118044    |
|       from small pool |     806    |     842    |  102123    |  101317    |
|---------------------------------------------------------------------------|
| Active allocs         |    1150    |    1195    |  220511    |  219361    |
|       from large pool |     344    |     363    |  118388    |  118044    |
|       from small pool |     806    |     842    |  102123    |  101317    |
|---------------------------------------------------------------------------|
| GPU reserved segments |     162    |     162    |     162    |       0    |
|       from large pool |     135    |     135    |     135    |       0    |
|       from small pool |      27    |      27    |      27    |       0    |
|---------------------------------------------------------------------------|
| Non-releasable allocs |      69    |      80    |  124656    |  124587    |
|       from large pool |      63    |      71    |   81797    |   81734    |
|       from small pool |       6    |      15    |   42859    |   42853    |
|---------------------------------------------------------------------------|
| Oversize allocations  |       0    |       0    |       0    |       0    |
|---------------------------------------------------------------------------|
| Oversize GPU segments |       0    |       0    |       0    |       0    |
|===========================================================================|

GFPGAN
|===========================================================================|
|                  PyTorch CUDA memory summary, device ID 0                 |
|---------------------------------------------------------------------------|
|            CUDA OOMs: 0            |        cudaMalloc retries: 0         |
|===========================================================================|
|        Metric         | Cur Usage  | Peak Usage | Tot Alloc  | Tot Freed  |
|---------------------------------------------------------------------------|
| Allocated memory      |    4647 MB |    7009 MB |    2134 GB |    2129 GB |
|       from large pool |    4507 MB |    6836 MB |    2116 GB |    2112 GB |
|       from small pool |     139 MB |     178 MB |      17 GB |      17 GB |
|---------------------------------------------------------------------------|
| Active memory         |    4647 MB |    7009 MB |    2134 GB |    2129 GB |
|       from large pool |    4507 MB |    6836 MB |    2116 GB |    2112 GB |
|       from small pool |     139 MB |     178 MB |      17 GB |      17 GB |
|---------------------------------------------------------------------------|
| GPU reserved memory   |    7944 MB |    7944 MB |    7944 MB |       0 B  |
|       from large pool |    7762 MB |    7762 MB |    7762 MB |       0 B  |
|       from small pool |     182 MB |     182 MB |     182 MB |       0 B  |
|---------------------------------------------------------------------------|
| Non-releasable memory |  158609 KB |    1524 MB |    2338 GB |    2338 GB |
|       from large pool |  151678 KB |    1524 MB |    2318 GB |    2318 GB |
|       from small pool |    6931 KB |      30 MB |      20 GB |      20 GB |
|---------------------------------------------------------------------------|
| Allocations           |    2836    |    3208    |  234750    |  231914    |
|       from large pool |     455    |     564    |  126294    |  125839    |
|       from small pool |    2381    |    2659    |  108456    |  106075    |
|---------------------------------------------------------------------------|
| Active allocs         |    2836    |    3208    |  234750    |  231914    |
|       from large pool |     455    |     564    |  126294    |  125839    |
|       from small pool |    2381    |    2659    |  108456    |  106075    |
|---------------------------------------------------------------------------|
| GPU reserved segments |     244    |     244    |     244    |       0    |
|       from large pool |     153    |     153    |     153    |       0    |
|       from small pool |      91    |      91    |      91    |       0    |
|---------------------------------------------------------------------------|
| Non-releasable allocs |      77    |     108    |  113366    |  113289    |
|       from large pool |      67    |      71    |   74087    |   74020    |
|       from small pool |      10    |      50    |   39279    |   39269    |
|---------------------------------------------------------------------------|
| Oversize allocations  |       0    |       0    |       0    |       0    |
|---------------------------------------------------------------------------|
| Oversize GPU segments |       0    |       0    |       0    |       0    |
|===========================================================================|

Adding torch.cuda.empty_cache() after image processing is complete
No-GFPGAN
|===========================================================================|
|                  PyTorch CUDA memory summary, device ID 0                 |
|---------------------------------------------------------------------------|
|            CUDA OOMs: 0            |        cudaMalloc retries: 0         |
|===========================================================================|
|        Metric         | Cur Usage  | Peak Usage | Tot Alloc  | Tot Freed  |
|---------------------------------------------------------------------------|
| Allocated memory      |    4085 MB |    6199 MB |    2079 GB |    2075 GB |
|       from large pool |    4039 MB |    6152 MB |    2063 GB |    2059 GB |
|       from small pool |      45 MB |      52 MB |      15 GB |      15 GB |
|---------------------------------------------------------------------------|
| Active memory         |    4085 MB |    6199 MB |    2079 GB |    2075 GB |
|       from large pool |    4039 MB |    6152 MB |    2063 GB |    2059 GB |
|       from small pool |      45 MB |      52 MB |      15 GB |      15 GB |
|---------------------------------------------------------------------------|
| GPU reserved memory   |    4196 MB |    7348 MB |   10500 MB |    6304 MB |
|       from large pool |    4148 MB |    7294 MB |   10440 MB |    6292 MB |
|       from small pool |      48 MB |      54 MB |      60 MB |      12 MB |
|---------------------------------------------------------------------------|
| Non-releasable memory |  113503 KB |    1518 MB |    3474 GB |    3474 GB |
|       from large pool |  111232 KB |    1516 MB |    3452 GB |    3452 GB |
|       from small pool |    2271 KB |       4 MB |      21 GB |      21 GB |
|---------------------------------------------------------------------------|
| Allocations           |    1150    |    1195    |  220511    |  219361    |
|       from large pool |     344    |     363    |  118388    |  118044    |
|       from small pool |     806    |     842    |  102123    |  101317    |
|---------------------------------------------------------------------------|
| Active allocs         |    1150    |    1195    |  220511    |  219361    |
|       from large pool |     344    |     363    |  118388    |  118044    |
|       from small pool |     806    |     842    |  102123    |  101317    |
|---------------------------------------------------------------------------|
| GPU reserved segments |     150    |     162    |     174    |      24    |
|       from large pool |     126    |     135    |     144    |      18    |
|       from small pool |      24    |      27    |      30    |       6    |
|---------------------------------------------------------------------------|
| Non-releasable allocs |      69    |      80    |  124674    |  124605    |
|       from large pool |      63    |      71    |   81815    |   81752    |
|       from small pool |       6    |      15    |   42859    |   42853    |
|---------------------------------------------------------------------------|
| Oversize allocations  |       0    |       0    |       0    |       0    |
|---------------------------------------------------------------------------|
| Oversize GPU segments |       0    |       0    |       0    |       0    |
|===========================================================================|

GFPGAN:
|===========================================================================|
|                  PyTorch CUDA memory summary, device ID 0                 |
|---------------------------------------------------------------------------|
|            CUDA OOMs: 0            |        cudaMalloc retries: 0         |
|===========================================================================|
|        Metric         | Cur Usage  | Peak Usage | Tot Alloc  | Tot Freed  |
|---------------------------------------------------------------------------|
| Allocated memory      |    4647 MB |    7009 MB |    2134 GB |    2129 GB |
|       from large pool |    4507 MB |    6836 MB |    2116 GB |    2112 GB |
|       from small pool |     139 MB |     178 MB |      17 GB |      17 GB |
|---------------------------------------------------------------------------|
| Active memory         |    4647 MB |    7009 MB |    2134 GB |    2129 GB |
|       from large pool |    4507 MB |    6836 MB |    2116 GB |    2112 GB |
|       from small pool |     139 MB |     178 MB |      17 GB |      17 GB |
|---------------------------------------------------------------------------|
| GPU reserved memory   |    5366 MB |    7938 MB |    9994 MB |    4628 MB |
|       from large pool |    5192 MB |    7762 MB |    9810 MB |    4618 MB |
|       from small pool |     174 MB |     182 MB |     184 MB |      10 MB |
|---------------------------------------------------------------------------|
| Non-releasable memory |  158609 KB |    1524 MB |    2213 GB |    2213 GB |
|       from large pool |  151678 KB |    1524 MB |    2192 GB |    2192 GB |
|       from small pool |    6931 KB |      30 MB |      20 GB |      20 GB |
|---------------------------------------------------------------------------|
| Allocations           |    2836    |    3208    |  234750    |  231914    |
|       from large pool |     455    |     564    |  126294    |  125839    |
|       from small pool |    2381    |    2659    |  108456    |  106075    |
|---------------------------------------------------------------------------|
| Active allocs         |    2836    |    3208    |  234750    |  231914    |
|       from large pool |     455    |     564    |  126294    |  125839    |
|       from small pool |    2381    |    2659    |  108456    |  106075    |
|---------------------------------------------------------------------------|
| GPU reserved segments |     236    |     244    |     248    |      12    |
|       from large pool |     149    |     153    |     156    |       7    |
|       from small pool |      87    |      91    |      92    |       5    |
|---------------------------------------------------------------------------|
| Non-releasable allocs |      77    |     104    |  113111    |  113034    |
|       from large pool |      67    |      71    |   73837    |   73770    |
|       from small pool |      10    |      44    |   39274    |   39264    |
|---------------------------------------------------------------------------|
| Oversize allocations  |       0    |       0    |       0    |       0    |
|---------------------------------------------------------------------------|
| Oversize GPU segments |       0    |       0    |       0    |       0    |
|===========================================================================|

Reported timings:
-n2:
Before Cache Clear:
Non-GFPGAN: 2 images generated in 12.19s
GFPGAN: 2 images generated in 15.10s
After Cache Clear:
Non-GFPGAN: 2 images generated in 12.29s
GFPGAN: 2 images generated in 14.64s
-n10:
Before Cache Clear:
Non-GFPGAN: 10 images generated in 52.17s
GFPGAN: 10 images generated in 54.34s
After Cache Clear:
Non-GFPGAN: 10 images generated in 54.72s
GFPGAN 10 images generated in 55.07s

Does it no longer OOM for -n2,3,4,5,... ?
Was it a lot of code changes?

@smoke2007 Are you able to test PR #122 and see if it helps with OOM? Much appreciated

Really small changes - if you could test it that would be great as I don't get OOM in my circumstance with testing up to 300 iterations through gfpgan on a RTX3080 w/24gb

print(torch.cuda.memory_summary)
sounds like you're in an awful predicament -- I'm sure one or two of the community here will be happy to help relieve you of your troubles

Since you're so resource poor, could you jam up a sweet self-hosted github action runner that runs a set of regression tests on PR? (That sounds too much like work even as I type it)

Which is the key VRAM utilisation column? Is it Peak Usage or Total Allocated?

I may not be smoke, but this PR did not solve the issue for me - 1st generation runs fine, subsequent generations in -n batch hits OOM (provided there was a face present in the 1st generation).
Hitting up and re-running the same prompt will still do the 1st generation fine, so the VRAM must get cleared at some point.

No it didn't solve it entirely either for me, situationally it sometimes continues, but it doesn't seem to help all the time

@blessedcoolant
@lstein
blessedcoolant's solution is perfect, been trying it out, I'm not getting OOM's in batch like this, with Upscaling as posteffect after the fact.

Latest also seems to be working for me

Moving the iteration loop outside of prompt2image solved the issue for me, and I prefer this as it upscales as it goes so if I cancel it after 50 images out of a 100 batch I have the upscaled results of those 50:
diff --git a/scripts/dream.py b/scripts/dream.py
index 552f42b..3fb786f 100755
--- a/scripts/dream.py
+++ b/scripts/dream.py
@@ -177,7 +177,9 @@ def main_loop(t2i, outdir, parser, infile):
         try:
             file_writer = PngWriter(current_outdir, normalized_prompt, opt.batch_size)
             callback    = file_writer.write_image if individual_images else None
-            image_list  = t2i.prompt2image(image_callback=callback, **vars(opt))
+            image_list  = []
+            for i in range(opt.N):
+                image_list += t2i.prompt2image(image_callback=callback, **vars(opt))
             results = (
                 file_writer.files_written if individual_images else image_list
             )
@@ -389,6 +391,12 @@ def create_cmd_parser():
         default=1,
         help='Number of samplings to perform (slower, but will provide seeds for individual images)',
     )
+    parser.add_argument(
+        '-N',
+        type=int,
+        default=1,
+        help='Number of images to generate (less likely for GFPGAN to fail in batches compared to -n)',
+    )
     parser.add_argument(
         '-b',
         '--batch_size',

@DarkStarSword Are you using batches? As in -b ?? That's very unstable. It causes massive memory overload. I highly recommend using iterations instead -n.

No, I was using -n


Merge 0.14.x into master

This merge was done manually via https://github.com/lonelyplanet/rizzo-next/commit/8a9b20f55efa9fbc7a129ea83446810bd34a0778.


Fix ICU syntax.

I'll update the UI strings in Crowdin once this is merged. It should be the only change.


Could not find user admin@sample when both set  --auth and  --replSet

Could not find user admin@sample when both set  --auth and  --replSet ,  mongo:4.0.4

Can you give all the commands you ran and any relevant contextual information or files for reproducing the issue

Can you give all the commands you ran and any relevant contextual information or files for reproducing the issue

k8s yaml
     terminationGracePeriodSeconds: 10
     containers:
       - name: mongo
         image:  mongo
         command:
           - mongod
           - "--auth"
           - "--replSet"
           - rs0
           - "--smallfiles"
           - "--noprealloc"
           - "--bind_ip_all"
         ports:
           - containerPort: 27017
         volumeMounts:
           - name: mongo-persistent-storage
             mountPath: /data/db
         env:
            - name: MONGO_INITDB_ROOT_USERNAME
              value: admin
            - name: MONGO_INITDB_ROOT_PASSWORD
              value: comteck2020
            - name: MONGO_INITDB_DATABASE
              value: admin

errors
2019-07-02T15:46:00.287+0800 I NETWORK  [conn69] received client metadata from <IP_ADDRESS>:53474 conn69: { driver: { name: "nodejs", version: "2.2.36" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "3.10.0-957.el7.x86_64" }, platform: "Node.js v11.2.0, LE, mongodb-core: 2.1.20" }
2019-07-02T15:46:00.287+0800 I ACCESS   [conn69] SASL SCRAM-SHA-1 authentication failed for admin on admin from client <IP_ADDRESS>:53474 ; UserNotFound: Could not find user admin@admin
2019-07-02T15:46:05.303+0800 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:53482 #70 (70 connections now open)

Your parameters work fine for me, is your persistent-volume empty on initialization?
$ docker run -d --rm --network=mongo --name mongo \
-e MONGO_INITDB_ROOT_USERNAME=admin \
-e MONGO_INITDB_ROOT_PASSWORD=pass \
-e MONGO_INITDB_DATABASE=admin \
mongo \
--auth \
--replSet rs0 \
--smallfiles \
--noprealloc \
--bind_ip_all
146b50f653ccffc4ee025d269b65d778ff32a7a0791ad5ccd3a3e91f7d5bc1ca

$ docker run -it --rm --network mongo mongo bash

root@c974f3af4775:/# mongo --host mongo -u admin -p pass --authenticationDatabase admin admin
MongoDB shell version v4.0.10
connecting to: mongodb://mongo:27017/admin?authSource=admin&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("ebe6b91a-9094-4d05-9695-5c65f6d3583a") }
MongoDB server version: 4.0.10
Welcome to the MongoDB shell.
For interactive help, type "help".
For more comprehensive documentation, see
        http://docs.mongodb.org/
Questions? Try the support group
        http://groups.google.com/group/mongodb-user
Server has startup warnings:
2019-07-02T00:20:11.254+0000 I STORAGE  [initandlisten]
2019-07-02T00:20:11.254+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2019-07-02T00:20:11.254+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).

The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.

For interactive help, type "help".
For more comprehensive documentation, see
        http://docs.mongodb.org/
Questions? Try the support group
        http://groups.google.com/group/mongodb-user
Server has startup warnings:
2019-07-02T00:20:11.254+0000 I STORAGE  [initandlisten]
2019-07-02T00:20:11.254+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2019-07-02T00:20:11.254+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).

The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.

To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---

> db.getName();
admin

Yes, I delete all files in this volume before initialization , if i remove
           - "--replSet"
           - rs0

it works  fine.

The issue seems like a configuration or environmental issue since I wasn't able to reproduce any error with your initialization configuration
I'd recommend asking over at the Docker Community Forums, the Docker Community Slack, or Stack Overflow.
Since these repositories are for issues with the image and not necessarily for questions of usability


SSR stuff

Been wasting way too much time playing with this... I just stumbled across ReactDOMServer.renderToString() and it looked so deceptively simple. But of course, all the fuckery is in driving Create React App, babel, webpack, and the concoction they've taped together to make react somewhat pleasant to use for newbies like me.
I'm by no means suggesting we merge this, but it might be of interest and I wanted to share.
I originally typed a bunch of other things here, but thought I better move it into an issue (#1760) since it's better to keep the conversation about if/how we should approach SSR there.

This complains a lot about useLayoutEffect:
Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client. See https://reactjs.org/link/uselayouteffect-ssr for common fixes.

Yeah I believe certain hooks can't be run (like useLayoutEffect) in a server rendered environment, and so any components that uses this hook and needs to be whacked on the server side will need to be re-designed slightly for things to work.

Closing in favour of #1965 for now


Separate date formatter from JSON

Right now we need NSDateFormatter located in JSON in other places too.
I think NSDictionary extension is not the best place for this and I propose moving this to somewhere else... Maybe NSDateFormatter extension? So we'd have this class func called xcsFormatter or something.
I'm opened for proposals - for naming and also for location.
And Yes, I can implement this 😉

Why not a NSDate class extension? So you'd call NSDate.dateFromBlah(blah).

NSDate.dateFromXCSString("")?
I'm also thinking about using this in JSON and it seems it'll work this way.

:+1:

Just waiting for a new tag so the Podfile can download a new version 😉

Done, 0.0.7: https://cocoapods.org/pods/BuildaUtils


Completed/updated Dutch translation

Finished Dutch translation on Crowdin and updated existing translated strings to make them consistent in terms of grammatical tense, syntax and terminology.

That's nice, but where can we find these updates?

Nevermind, found it...

@poisdeux It's still active yes, though i don't actively look into it...
I'll fetch this translation and incorporate it.

@poisdeux by the way, i've made you manager of the crowdin project.
We really need to change to transifex to keep it coherent with Kodi...


HTTP Server frontend powered by HTTP4S and Circe

Summary
Adds a web server frontend for interacting with debug trees. This is powered by http4s enhanced with circe (for JSON-related interactions).
This frontend also benefits from json-info's CJson type class so that the frontend will be able to give downloadable JSON information of the debug trees as one interacts with them on a site.
This is still work-in-progress.

I guess I can merge it now, and just hope that if the API is pants, someone will complain?


Remove custom slippage from THORSwap streaming swaps

Overview
As the THOR protocol will extract an affiliate fee from a trade in the first block of a streaming swap, this fee will be paid by the user regardless of if the trade completes.
Therefore, we should not let the user specify a tight custom slippage, as it creates the opportunity for a mostly unfulfilled swap where the user still pays the full affiliate fee as if it was 100% fulfilled (something that was meant to help might actually harm).
The comment from leena below gives a potential path forward, whereby we could disable slippage/limit protection for streaming swaps and rely on the protocol to protect the user.
We'll need appropriate UI to explain this.
References and additional details
[09:14]leena:
- currently the affiliate fee is taken out of the start of the swap, so it's the full amount, not filled amount cc @Son of Odin

- did the user actually want 60BPS lock-in to a set price for a full 24hours, or did they "think" they wanted it? Eg, they may have thought they were locking in a max of 60BPS slippage protection for the duration of trade; TC auto-stream guarantees 5BPS fees and generally hits close to 5-50 BPS slippage (from arb performance). It's not possible to guarantee the second part.

Often users don't know what they want; for a long streaming swap, a user generally prefers full execution. TC will guarantee 5BPS fee and in practice, the user will get 5-50 BPS slippage (sometimes up to 100). Our recommendation is

1) Always use `0/1/0` for L1 streamers, (fastest auto 5BPS stream, tightest to starting market price, guaranteed full-execution)
2) If the "health" drops to below 90%, use `0/3/0` (volatile)
3) If dealing with large trades (more than 10% of pool depth), increase up to `0/5/0` (up to 30 secs for arbs to restock synths)

See https://viewblock.io/thorchain/tx/EC37EB94BCA188FCB72CECFE7E3A7C7EB6407F7AF5DFC2CF692A341FA3A483AE
and https://discord.com/channels/838986635756044328/1166265575941619742
Acceptance Criteria

No ability to set slippage on THORSwap streaming swaps
UI explaining the potential market movement impacts (TODO)
Stream params in the memo dynamically calculated as per the suggestions above

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

adjust params for streaming swaps to adjust for loss prevention
remove limit from streaming swaps in general
add tooltip to highlight mini receive amount (guarantee) is not there. highlighting different ones etc. @reallybeard

@twblack88 followed up with thorchain team to find out if this has been addressed.

@0xean FYI this has been tackled by @kaladinlight in https://github.com/shapeshift/web/pull/5748, though UI changes will be coming up as as follow-up, it is still possible to set a default/custom (both wrong) slippage for THORChain streaming swaps currently, but setting them is a no-op, and the amount we display in the custom slippage component also is.

closing in pref of #5764


Consider package-json-to-readme

https://github.com/zeke/package-json-to-readme

Nope. Too simplistic


Including PR and Issue templates to repo

Suggestion:
I think that as this repo grows, it could use formatted ways to handle issues and PRs. I'd like to work on including templates to implement this functionality. Examples of templates: circuitverse

I would like to make these templates, can you assign it to me?

Hi @iamrajiv, @OmkarPh ,
Thanks for your work on this!  We are trying to determine our requirements for handling PRs as part of our strategy for what information to include when releasing new versions.  We should have something in the next week or so that will be aligned with that strategy.
I'm closing this issue for now.  Please let us know on https://app.slack.com/client/T013V60QY06/C01APUNTSGH if you need help finding some other issues.
Thanks!

Sure @arielshaqed
We'll have eyes on the repo and work with some other issues.
Anyways, Happy Hacktoberfest 🎉


feat: Fetch upstream, remove Desmos GraphQL [DEV-1239]

Description

Checklist

[ ] Ran Linting
[ ] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Added an entry to the CHANGELOG.md file.
[ ] Re-reviewed Files changed in the Github PR explorer.

Task linked: DEV-1239 Refactor BigDipper Explorer code to run faster and more performantly


[PE-D][Tester C] Doesn't accept phone number with country code

Valid phone number with country code (e.g. +65) is not acceped

Labels: severity.VeryLow type.FeatureFlaw
original: hazzle23/ped#9

Context of the app is NUS Students, most users should therefore not need country code. if needed, they can just input<PHONE_NUMBER>


setProcessor not working

Hey, I am trying to implement this library into our project but I'm having some issues with an error appearing while trying to use the examples provided, the error is attached to this ticket.
Is something that I did not do or there's something different happening in there

Thanks!

there was a problem with the version being hardcoded as a string. does the error still happen to you on v0.1.2 ?

the logs you posted are from v0.1.1,  maybe you need to clear your node_modules?

hmm. something was weird with the dist folder, I re-released, can you try again with 0.1.3?

Yes, but I don't know why but I keep getting now when importing the module
Cannot find module '@livekit/track-processors' or its corresponding type declarations.
for import {BackgroundBlur, VirtualBackground} from '@livekit/track-processors';

@lukasIO So there's a issue with the latest release, check please the below screen shoots added:
v0.1.2

and v0.1.3

thanks! just realised it, fixed in the latest version. sorry again!

Thanks, @lukasIO, works now with the v0.1.4.