ScrollToTop FAB Added

Related to Issue#277
Added Scroll To Top Button is a Floating Action Button, and it triggers when the page offset is greater than 400.

Advantages:
No need to add a separate ScrollToTop button on every page.

Good change! I would suggest making a fab button offset above the bottom navbar.

@adarsh-technocrat done☺.

Hey, @Abhijay007 thanks for reviewing.

In your first suggestion, I found it amazing and have removed the previous scroll to top button from the following pages:

Home Page
Course Page
Wish List
Peer Discussion Page

While doing this, I found on Routes Page that the routes of terms-and-conditions, about and faq are repeated as shown in the picture.

So, I have removed it.

As in your second suggestion, since we are making an app, I think so we are not focussing on that how it looks on the web. That's totally my view but if you want then I can implement it, but the problem is that I have added the following lines for making it fixed on the right bottom, so if I changed it then it will also impact mobile view.

right: "10px",
bottom: "65px",

If we removed the height issue, then I have done it in a way that if page offset is greater than 400 then it will show, else it will not.

Sorry if I am not able to understand what you are trying to say.

@Abhishek-kumar09 Please look into this Pr.

We are gonna remove the scroll to top button in the future version of app. Currently, the scroll to top is looking with center aligned and full color opacity.


feat: sign up [DO NOT MERGE]

to be merged after #364

converted login activity into fragment
created new module home to contain login and signup
added sign up feature

fixes #341

@iamareebjamal
getting unsupported media type 415 error. please check the code.

The logs show what request body is being sent to the server, please check that. You can also use stetho

@iamareebjamal please review

Also, add an option to set name, not only email and password. The person can leave it blank if he wants to

keep the color tone consistent with the app

@iamareebjamal I didn't get this.

@iamareebjamal please review.

@iamareebjamal please review.

Please resolve merge conflicts.

@iamareebjamal please do test on a device before review. I am moving to my college from mumbai to varanasi. So won't be available for two days.


Add NFC transport layer

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Larry Tsai seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


manual symlink

I had to create a symlink /lib/libmimalloc.so.1.0 -> /lib/mimalloc-1.0/libmimalloc.so.1.0 manually to make a build process work, that had no issues with earlier (pre 1.1.0) mimalloc versions. Does that need to be fixed on your end?

Yes, I changed things it the CMakeLists.txt to set a symlink -- I wonder why it does not work though?
Before I made a copy but that is not ideal either

If anyone has an idea what is wrong it the cmake file with the symlink creation, let me know :-)

Ignore 5433dbb.
b41183e has the fix for this issue. I tested it on macOS.

Please close this issue.


[MinGW] Disable GCC warning about using MS format specifiers in ISO C conformant code

-Wno-pedantic-ms-format was introduced in GCC 4.5 for MinGW, so we don't need to test if that is supported as minimum we support is GCC 4.8.

I kind of think we should change the printf statements to use inttypes.h.

inttypes.h

ll format specifier isn't supported on Windows, so using inttypes.h doesn't fix anything.

Looks like we already do use inttypes.h. Here are the warnings.
zlib-ng/test/infcover.c: In function ‘mem_used’:
zlib-ng/test/infcover.c:1[83](https://github.com/zlib-ng/zlib-ng/actions/runs/3289136191/jobs/5420314359#step:11:84):21: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]
  183 |     fprintf(stderr, "%s: %" PRIu64 " allocated\n", prefix, (uint64_t)zone->total);
      |                     ^~~~~~~
zlib-ng/test/infcover.c:183:21: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]
zlib-ng/test/infcover.c: In function ‘mem_high’:
zlib-ng/test/infcover.c:190:21: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]
  190 |     fprintf(stderr, "%s: %" PRIu64 " high water mark\n", prefix, (uint64_t)zone->highwater);
      |                     ^~~~~~~
zlib-ng/test/infcover.c:190:21: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]
zlib-ng/test/infcover.c: In function ‘mem_done’:
zlib-ng/test/infcover.c:214:25: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]
  214 |         fprintf(stderr, "** %s: %" PRIu64 " bytes in %d blocks not freed\n",
      |                         ^~~~~~~~~~
zlib-ng/test/infcover.c:214:25: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]

zlib-ng/tools/makecrct.c: In function ‘write_table64’:
zlib-ng/tools/makecrct.c:143:16: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]
  143 |         printf("%s0x%016" PRIx64 "%s", n == 0 || n % 3 ? "" : "    ",
      |                ^~~~~~~~~~
zlib-ng/tools/makecrct.c:143:16: warning: ISO C does not support the ‘I64’ ms_printf length modifier [-Wformat=]

Looks good. I'm not so sure we need the -D_POSIX_C_SOURCE=200809L on the CFLAGS anymore - looks like we already have it in zbuild.h.

Looks good. I'm not so sure we need the -D_POSIX_C_SOURCE=200809L on the CFLAGS anymore - looks like we already have it in zbuild.h. But that's a separate issue..

We should only need to specify values on command-line that are higher than the defaults we assume in headers. The most common reason is when one operating system or toolset requires higher version than others, as we need to make sure the definition is correct before including any system headers. I try to make cleanup related pull requests once in a while so we have as little warnings emitted as possible when we are preparing a new release.
My main focus has been VC++, MinGW, MSYS and Cygwin since the early days, but I will also participate in some arch-dependent issues and features.


changed the go installer gist to include aarch64 (arm 64)

Please check if bor make command needs to change, I changed it as I was getting this error earlier:
TASK [install-bor : Build Bor]
***********************************************************************************************************************************************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": ["make", "bor-all"],
"delta": "0:00:00.002775", "end": "2021-02-23 10:33:48.167754", "msg": "non-zero return code", "rc": 2, "start": "2021-02-23 10:33:48.164979",
"stderr": "make: *** No rule to make target 'bor-all'.  Stop.", "stderr_lines": ["make: *** No rule to make target 'bor-all'.  Stop."], "stdout": "", "stdout_lines": []}

Getting the same error

@LogvinovLeon ignore the above comment. It is make bor-all in the latest versions.


Added missing HOSTING print column for HypershiftDeployment

Signed-off-by: Joshua Packer<EMAIL_ADDRESS>Pull reference: https://github.com/stolostron/hypershift-deployment-controller/pull/54
Issue Reference:

/cc @JakobGray


Equality operator and some additions

Changelist:

equality operator for tinygltf::Model and types contained by it
double comparison
initialize some variables for operator==() reliabiltiy
change some floats to doubles
intellisense define
serialize accessor.name
dont serialize some names if they're empty
return false if writing gltf file fails

Discussion:

Double comparison method is perhaps not necessary as the json serializer writes/reads the bytes from/into memory directly. I think my previous issue came from the fact that some variables were saved in memory as float, but serialized as double. Thoughts?
Necessary to reformat for consistency, perhaps you want to do that yourself?

Potential issues in current state as mentioned in #94, related to PR:

Comparing pre-serialization and post-serialization model data will not work for the buffer property and has to be handled separately if the user wants to verify it, because currently the buffer.uri property is coded to copy the gltf file name and replace the extension instead of keeping the previous buffer uri.
Comparing pre-serialization and post-serialization model data will not work for neither buffers nor images if they are embedded, because for obvious reasons the uri changes. This has to be handled separately by the user.

Potential issues in current state as mentioned in #94, unrelated to PR:

Looking at the code, loading embedded buffers seems to take up more memory/cpu, which can be significant for large models. The embedded data is completely stored in the buffer.uri property and then duplicated in the buffer.data property, but for external buffers it's only loaded into buffer.data directly.
Every buffer is saved with the same filename, which should either overwrite the previously written buffer or generate an exception.

And perhaps unrelated; i see you have merged some more changes into the devel branch a while back. Wasn't it obsolete?

Thanks!

Double comparison method is perhaps not necessary as the json serializer writes/reads the bytes from/into memory directly. I think my previous issue came from the fact that some variables were saved in memory as float, but serialized as double. Thoughts?

clang emit warning when using == for floating point comparison.
Also there may be precision loss when loading/storing fp value from/to memory on different CPU architecture, so using fp comparator is much safer.

And perhaps unrelated; i see you have merged some more changes into the devel branch a while back. Wasn't it obsolete?

Oh, I've merged this https://github.com/syoyo/tinygltf/commit/098dfee98209aa1a447c7f7f65123f7e53b4d0c3 to master

Necessary to reformat for consistency, perhaps you want to do that yourself?

Suppressed some clang warnings and applied clang-format:
https://github.com/syoyo/tinygltf/commit/641b3ccf8c3549f8f45f8da02cf8ac49a1c1149c


Improve documentation on value type in Python API

As of today most methods in the Python API does not provide any type hints, and does not provide any comments either. Taking the example below it is difficult to deduce what types are allowed for "value".  At least if using websocket/VISS API, the value must be a JSOn object: str, bytes or bytearray. Trying to use a Python int or bool will give an error.
I do not know if we as of now expect it to be called with bytes/bytearray as input, or if we always expect a string? If so we could possibly use str as type hint.
https://github.com/eclipse/kuksa.val/blob/master/kuksa-client/kuksa_client/__init__.py#L70
    # Set value to a given path
    def setValue(self, path, value, attribute="value", timeout=5):
        return self.backend.setValue(path, value, attribute, timeout)

# Update Meta Data of a given path
    def updateMetaData(self, path, jsonStr, timeout=5):
        return self.backend.updateMetaData(path, jsonStr, timeout)

This could be a good example we named this variable jsonStr but it accepts Any type in function call.

solved by #529


Release/v7.9.0

Changes

Changes:

https://github.com/IPG-Automotive-UK/react-ui/pull/881

Dependencies

UI/UX

Testing notes

[ ] https://github.com/IPG-Automotive-UK/react-ui/pull/881

Author checklist before assigning a reviewer

[ ] Reviewed my own code-diff.
[ ] Branch has been run in docker.
[ ] PR assigned to me or an appropriate delegate.
[ ] Relevant labels added to the PR.
[ ] Appropriate tests have been added.
[ ] Lint and test workflows pass.

TD-2799 Uploader incorrect error messages #881

Is there anything else planned for this release? Because if it's just this item then really this should be a bug fix not minor release.


remove test/.rnd on make clean

Neither "make clean" nor "make distclean" removes the file "test/.rnd".
This patch removes this temporary file on make clean.
This patch should work on master/OpenSSL_1_1_0-stable.

122fa08 on master; d715533 on 1.1.0
Thank you!


python3Packages.aioftp: 0.19.0 -> 0.20.0

Motivation for this change
https://github.com/aio-libs/aioftp/blob/master/history.rst#0200-27-12-2021
Enable tests
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 152386 run on x86_64-linux 1

8 packages built:

python38Packages.aioftp
python38Packages.parfive
python38Packages.siosocks
python38Packages.sunpy
python39Packages.aioftp
python39Packages.parfive
python39Packages.siosocks
python39Packages.sunpy


Add doap file

As mentioned by @Neustradamus in #191  a doap file would be beneficial.
@Neustradamus can work on that while working on #114 and #115 as there is a big overlap.

.doap file is important but there is no progress from me :/


Duplicate generated annotation classes in Eclipse

Since updating the plugin to 0.16, the generated .classpath file for Eclipse often contains a wrong source-directory entry, resulting in duplicated generated classes in Eclipse.
We use Gradle 4.8 and Eclipse 4.7.3a. I use Buildship 3.0.0.v20180607, but my colleagues have this issue without using Buildship (just using "gradlew eclipse" on the command line).
I don't know the exact steps to reproduce this problem, but these steps often work:

Have an Eclipse project with annotation processing enabled (after executing the tasks "eclipseFactorypath" and "eclipseJdtApt").
Everything works, because the generated classes are present under ".apt_generated" folder.
Build the project on the command line (doesn't always seem necessary for reproducing the issue) by using "gradlew compileJava".
Use "Refresh Gradle project" in the context menu of the Eclipse project.
Result: There is an added source folder with the name "build/generated/source/apt/main", containing the same files as ".apt_generated".

The wrongly added source folder can be seen inside the .classpath file (third classpathentry):
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" output="bin/main" path="src">
		<attributes>
			<attribute name="gradle_scope" value="main"/>
			<attribute name="gradle_used_by_scope" value="main,test"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="src" output="bin/test" path="test">
		<attributes>
			<attribute name="gradle_scope" value="test"/>
			<attribute name="gradle_used_by_scope" value="test"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="src" output="bin/main" path="build/generated/source/apt/main">
		<attributes>
			<attribute name="gradle_scope" value="main"/>
			<attribute name="gradle_used_by_scope" value="main,test"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="con" path="org.eclipse.buildship.core.gradleclasspathcontainer">
		<attributes>
			<attribute name="annotationpath" value="/MyProject/annotations"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
	<classpathentry kind="src" path=".apt_generated">
		<attributes>
			<attribute name="optional" value="true"/>
		</attributes>
	</classpathentry>
	<classpathentry kind="output" path="bin/default"/>
</classpath>

Downgrading to 0.15 solves this issue.

You might try excluding the build/generated/source/apt folder (and/or subfolders) using a resourceFilter: https://docs.gradle.org/current/dsl/org.gradle.plugins.ide.eclipse.model.EclipseProject.html
If that doesn't work, then just stick to 0.15 for now :man_shrugging: (besides internal cleanup, adding the generated sources directories to the source sets' allSource and allJava is the real change in 0.16)

Thanks! We will just stick to 0.15 for now.

Fwiw, I reverted that change and released v0.17 (which is, functionally, the same as v0.15)


Field 'isDraft' doesn't exist on type 'PullRequest'

I am getting the following error message:

run check step: run check step: check: resource script '/opt/resource/check []' failed: exit status 1
stderr:
2020/10/22 14:07:27 check failed: failed to get last commits: Field 'isDraft' doesn't exist on type 'PullRequest'
Our GHE version is: GitHub Enterprise Server 2.20.16. These checks used to work perfectly well, so I believe this failure is due to GHE upgrade. The GHE server is maintained by our IT team so we don't have an option to rollback our GHE.
I suspect this issue is related to:
https://github.com/shurcooL/githubv4/issues/66
Is anyone else seeing this issue and any tips how to workaround this. Our pull-request pipelines are completely broken due to this.

On further investigation, I found out that:
(a) our GHE was not upgraded recently but few months back,
(b) our pull requests were working until Oct 20th, and
(c) there was a new release of this project (v0.22.0) on Oct 21st.
So I modified my pipeline to explicitly use v0.21.0 and my pipelines have started working again. This looks like a regression bug to me. Let me know if you need any additional details to help resolve this issue.

It looks like to get this working in GHE, we'd need to implement something to re-write the requests to enable this preview functionality?

yes, I guess you need to use http.RoundTripper (ex: https://lanre.wtf/blog/2017/07/24/roundtripper-go/). If you need any help in validating the fix, let me know.

I'd bet upgrading GHE solved the problem. Can we close this issue?
If anything similar appears, it will be sweet to provide feedback to the new maintained repo, thanks!

@schmurfy maybe?


"Could not find addon." How are things going over here?

Excited to try out this add-on but CLI says it can't be found. What your status over there? : )
$: ember install ember-cli-image
Installed packages for tooling via npm.
Install failed. Could not find addon with name: ember-cli-image

npm install ember-cli-image should work to install it.  This project is unmaintained at this point - use at your own risk.


ImportError: cannot import name 'TypeAlias' from 'typing' on macOS

After following the steps in README-Mac-MPS.md I get the following error:
(ldm) richelmes@M1mini:~/various/stable-diffusion
main 16:05 $ python scripts/dream.py --full_precision
* Initializing, be patient...

Traceback (most recent call last):
  File "/Users/richelmes/various/stable-diffusion/scripts/dream.py", line 553, in <module>
    main()
  File "/Users/richelmes/various/stable-diffusion/scripts/dream.py", line 41, in main
    from ldm.simplet2i import T2I
  File "/Users/richelmes/various/stable-diffusion/ldm/simplet2i.py", line 29, in <module>
    from ldm.models.diffusion.ksampler import KSampler
  File "/Users/richelmes/various/stable-diffusion/ldm/models/diffusion/ksampler.py", line 2, in <module>
    import k_diffusion as K
  File "/Users/richelmes/various/stable-diffusion/src/k-diffusion/k_diffusion/__init__.py", line 1, in <module>
    from . import augmentation, config, evaluation, external, gns, layers, models, sampling, utils
  File "/Users/richelmes/various/stable-diffusion/src/k-diffusion/k_diffusion/external.py", line 6, in <module>
    from . import sampling, utils
  File "/Users/richelmes/various/stable-diffusion/src/k-diffusion/k_diffusion/sampling.py", line 10, in <module>
    from typing import Optional, Callable, TypeAlias
ImportError: cannot import name 'TypeAlias' from 'typing' (/opt/homebrew/anaconda3/envs/ldm/lib/python3.9/typing.py)

I tried:
pip uninstall typing_extensions
pip install typing_extensions==4.0.0
Found existing installation: typing_extensions 4.3.0
Uninstalling typing_extensions-4.3.0:
  Would remove:
    /opt/homebrew/anaconda3/envs/ldm/lib/python3.9/site-packages/typing_extensions-4.3.0.dist-info/*
    /opt/homebrew/anaconda3/envs/ldm/lib/python3.9/site-packages/typing_extensions.py
Proceed (Y/n)? y
  Successfully uninstalled typing_extensions-4.3.0
Collecting typing_extensions==4.0.0
  Using cached typing_extensions-4.0.0-py3-none-any.whl (22 kB)
Installing collected packages: typing_extensions
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
qudida 0.0.4 requires opencv-python-headless>=4.0.1, which is not installed.
albumentations 1.2.1 requires opencv-python-headless>=4.1.1, which is not installed.
Successfully installed typing_extensions-4.0.0

but still get the same error.
This was all working for me before pulling the latest version today, but I removed the ldm anaconda environment to be sure that everything was up to date and ran into problems, so I nuked everything and tried to install from scratch.

I'm also having this issue

I worked around this by upgrading to python 3.10.
diff --git a/environment-mac.yaml b/environment-mac.yaml
index 44cd1ef..6742a1f 100644
--- a/environment-mac.yaml
+++ b/environment-mac.yaml
@@ -1,11 +1,11 @@
-name: ldm
+name: ldm310
 channels:
   - pytorch-nightly
   - conda-forge
 dependencies:
-  - python==3.9.13
-  - pip==22.2.2
-
+  - python=3.10
+  - pip
+
   # pytorch-nightly, left unpinned
   - pytorch
   - torchmetrics
(END)

TypeAlias is only supported as of python 3.10: https://docs.python.org/3/whatsnew/3.10.html (search in page for 'TypeAlias')
So I think this is was caused by the project reverting to python 3.9, which occurred here: https://github.com/lstein/stable-diffusion/pull/283
A new PR is pending to move back to 3.10: https://github.com/lstein/stable-diffusion/pull/301

This is an error on a different repo. This patch will fix it temporarily (I hope the code I'm pasting works right).
patch -u src/k-diffusion/k_diffusion/sampling.py
--- sampling.py-orig	2022-09-02 07:01:41.000000000 -0600
+++ sampling.py	2022-09-02 07:02:13.000000000 -0600
@@ -7,7 +7,11 @@
 from torch import Tensor
 from torchdiffeq import odeint
 from tqdm.auto import trange, tqdm
-from typing import Optional, Callable, TypeAlias
+from typing import Optional, Callable
+try:
+    from typing import TypeAlias
+except ImportError:
+    from typing_extensions import TypeAlias

 from . import utils

This bug was first noticed in this issue.

@jnordberg your version changes the env name to ldm310, which will probably confuse people. For a minute I thought that was my comment so I edited to fix it, but after saving the fix I realized it was someone else's comment! Sorry for that, I've restored it to the way you had it.

@magnusviri Ah ok, I was wondering what was going on there 😂
FWIW I'm not seeing any performance regression on python 3.10 on a 16g M1 MacBook Air
With 3.9 and the typing_extensions patch: 3.94s/it
With 3.10: 3.84s/it


vite-plugin uploads sourcemaps when building for development

Environment
@sentry/react: 7.112.1
@sentry/vite-plugin: 2.16.1
vite: 5.1.4
react: 18.2.0
The documentation says:

The Sentry Vite plugin doesn't upload source maps in watch-mode/development-mode. We recommend running a production build to test your configuration.

However when I build with tsc && vite build --mode development source maps are generated and uploaded.

Thanks! Closing because it is a duplicate of: https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/520


Analysis workflow for IMC data after segmentation in HALO

Hello!
We currently have CODEX data  after segmentation in HALO. I was curios, if there is a way to use this segmentated dataset  for further downstream analysis at the IMC data analysis workflow , for instance starting from the chapter 5 (read in the data). As far as I understood, it should be in the steinbock format for further process in current pipeline. Do you know if there is a way to integrate it, or I should perform resegmentation of the data in the steinbock ?
Thank you
Best regards
Alexey

@alexeykb
Your question concerns a different package IMCDataAnalysis, please submit your issue over there.


Too long DHCP discovery

Hello!
I use the latest esp-wifi revision (https://github.com/esp-rs/esp-wifi/commit/55782663e71e1891da106d040cdfadf1bd466c13) att the moment. I run the examples dhcp.rs and embassy_dhcp.rs for ESP32 (ESP32-WROOM-32 DevkitC board).
Most of the times DHCP discovery takes more than 9 seconds, sometimes even up to 30 seconds. Sometimes, however, it  takes no time and the MCU immediately gets static IP.
But that happens rarely, about 1 in 10 times. In other times I have to wait ~10 seconds.
Although, the wifi connection and transmission/reception speed is ok (at least for MQTT), no significant delays.
Wifi connection takes almost no time, at most a few seconds.
I used two access points to connect: my home wifi and an access point created by my laptop.
With both of them I observe the same problem. The laptop and therefore the access point are located less than a meter away from the ESP32, so I think the signal quality should be great.
I measured the time it takes for the MCU to send the DHCP discovery packet with wireshark:

(<IP_ADDRESS> is the DHCP server, the IP of the laptop's interface, <IP_ADDRESS> is the leased IP for the
I see that both the discovery and request packets are sent twice. Is that expected behavior?
I need to clarify that the first DHCP discovery packet is usually delayed for ~10 seconds AFTER I see the Wait to get an ip address debug line (source), for both embassy async and blocking versions.

Thanks!

https://github.com/embassy-rs/embassy/pull/2104

embassy-rs/embassy#2104

Thank you. That helped.
Indeed, following the pull request, resetting the DHCP socket after STA is connected solves the problem and DHCP discovery happens almost immediately.
However, I found that I also need to add a little delay of about 300 ms before resetting the socket. Otherwise, the problem stays.
So the code working for me (blocking version):
....
    println!("{:?}", controller.is_connected());

    let wait_end = current_millis() + 200;
    while current_millis() < wait_end {}
    wifi_stack.reset();

    // wait for getting an ip address
    println!("Wait to get an ip address");
....


Multiplicador

Se comienza a implementar multiplicador.
Se agregan pruebas integradas en RespuestaTest

Codecov Report

Merging #37 into V1.0 will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               V1.0      #37      +/-   ##
============================================
+ Coverage     92.67%   92.78%   +0.11%
- Complexity       69       70       +1
============================================
  Files            16       16
  Lines           191      194       +3
  Branches          8        8
============================================
+ Hits            177      180       +3
  Misses           14       14

Impacted Files
Coverage Δ
Complexity Δ

...va/edu/fiuba/algo3/modelo/Respuesta/Respuesta.java
82.60% <100.00%> (+2.60%)
7.00 <2.00> (+1.00)

Continue to review full report at Codecov.

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


Use as library without clicking context

I want to use goss with packer.io but I don't think that I need additional dep for cli parsing.
Does it possible to use goss with another tool without cli.Context

It's been on my mental to do list but I haven't gotten around to it yet. Out of curiosity which part of goss are you looking to leverage got packer?

I want to write provisioner that checks builded running vm image with
precreated goss.yaml file and if all tests success, continue..
23 Июл 2016 г. 20:32 пользователь "Ahmed Elsabbahy" <
<EMAIL_ADDRESS>написал:

It's been on my mental to do list but I haven't gotten around to it yet.
Out of curiosity which part of goss are you looking to leverage got packer?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aelsabbahy/goss/issues/112#issuecomment-234730260,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdYG6jBGDnIJWs2Q3bhd6CML9XWnKRHks5qYlA5gaJpZM4JTZx7
.

Ah, very cool.
I've marked this as a development facing enhancement, but I can't make any promises on when I'll be able to complete this ticket.
That said, I do wonder if leveraging the goss libraries directly for this could lead to a fragile implementation, ex: If I make a major refactor to goss.
Looking at the chef-solo provider, I wonder if a similar approach would be better and more resilient to goss internal changes?
https://github.com/mitchellh/packer/blob/master/provisioner/chef-solo/provisioner.go

In case of chef-solo like you need to have binary installed,this is not
portable and can have some problems...
Does it possible to check external system via SSH for example?
23 Июл 2016 г. 20:48 пользователь "Ahmed Elsabbahy" <
<EMAIL_ADDRESS>написал:

Ah, very cool.
I've marked this as a development facing enhancement, but I can't make any
promises on when I'll be able to complete this ticket.
That said, I do wonder if leveraging the goss libraries directly for this
could lead to a fragile implementation, ex: If I make a major refactor to
goss.
Looking at the chef-solo provider, I wonder if a similar approach would be
better and more resilient to goss internal changes?
https://github.com/mitchellh/packer/blob/master/provisioner/chef-solo/provisioner.go
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aelsabbahy/goss/issues/112#issuecomment-234731003,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdYG_01_NXKEe8MsuDJ8U4Gmt0UdUYIks5qYlPQgaJpZM4JTZx7
.

goss only runs locally on the machine under test as it does not rely on external commands for most tests so no goss over ssh, unless you pipe the yaml file over ssh like cat goss.yaml | ssh host 'goss validate
You'd basically have to have the provisioner do the equivalent of this:
http://www.unixdaemon.net/puppet/puppet-integration-tests-in-seven-minutes/
OR have the goss library code somehow run directly in the machine under test.

Serverspec able to test via SSH as I know...
I'm try to fork and do some changes ,and recheck...
23 Июл 2016 г. 21:12 пользователь "Ahmed Elsabbahy" <
<EMAIL_ADDRESS>написал:
goss only runs locally on the machine under test as it does not rely on
external commands for most tests so no goss over ssh, unless you pipe the
yaml file over ssh like cat goss.yaml | ssh host 'goss validate
You'd basically have to have the provisioner do the equivalent of this:
http://www.unixdaemon.net/puppet/puppet-integration-tests-in-seven-minutes/
OR have the goss library code somehow run directly in the machine under
test.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aelsabbahy/goss/issues/112#issuecomment-234732156, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdYG-ukzYK0JuBdCYQ8-dn460thllbAks5qYllxgaJpZM4JTZx7
.

After some checking, goss can handle external hosts via simple way:
you need to able to wrap util.NewCommand using ssh for example.
So if user specify target via ip:port to connect via go to that server via ssh and run provided command.
What do you think

The problem goss works differently than serverspec and testinfra in that it tries to rely as little as possible on external commands, this is how it's able to achieve extremely fast speeds, see benchmarks
Most checks don't use util.NewCommand, for example take a look at:

https://github.com/aelsabbahy/goss/blob/master/system/file.go

The only ones that use external commands are the ones where I couldn't get around that limitation, services and packages basically.

Yes, i'm understand. but if this ability can exists, it will be fine =). thanks for help.


Android developers would like an easy onboard to Flutter, and map their knowledge to Flutter

Developers with a lot of Android development experience would like to know how to map their current understanding/knowledge to Flutter.
What concepts are similar? Different? What's new in Flutter? If they knew how to do X in Android, how do they do it in Flutter?

See SO question on wrap_content and match_parent.

Questions from our mailing list:

How to work with equivalent of "ressources", different device size, ...
How to create a RecyclerListe from a Provider which the data are saved in sqlite from a json get by an http request.
How to get/cached images like Glide
How to sync data with a job scheduler
How to work with notifications
How to work with settings
How to work with Broadcast

Flutter for Android devs was launched some time ago. Closing.


RevealJs - to create web presentations

@RodrigoMastache, please split the resources into separate PRs. Thanks!


[SuperEditor] Add toggleable headers (Resolves #2276)

[SuperEditor] Add toggleable headers. Resolves #2276
This PR adds the ability to group nodes together under header nodes or list item nodes, where each group can be collapsed/expanded by tapping on a button near it.
The groups are created upon initialization, when adding or removing a node, and when changing a node that couldn’t start a group to a node that can start a group. For example, typing "# " at the beginning of a paragraph converts it to a header node and creates a new group.
Navigating using the arrow keys skips nodes inside a collapsed group. For example, pressing ARROW DOWN skips nodes that are inside a collapsed group.
The user cannot start or end a selection inside a collapsed group. Also, if the selection starts or ends within a group and the user collapses the group, the selection is adjusted to avoid starting or ending inside the collapsed group.
Node grouping is customizable and apps can implement their own grouping logic, if desirable.
Implementation
A GroupBuilder interface was added with the methods required to grouping nodes:
canStartGroup: to signal the document layout that the current node can start a group, for example, when it is a level one header.
canAddToGroup: to signal the document layout that a node can be added to an existing group.
build: to create the widget for this group.
SuperEditor will take a list of GroupBuilders as a constructor parameter.
Previously, all components were organized into a vertical list of components inside the SingleColumnDocumentLayout. Now, whenever a GroupBuilder returns true for  canStartGroup, the document layout will call canAddToGroup to each node below it, until canAddToGroup returns false. After gathering all nodes that are part of the group, SingleColumnDocumentLayout calls build on the GroupBuilder to create a widget subtree for that group.
To handle the key navigation, at the current state of this PR, it was added an isComponentVisible method to the DocumentLayout interface, so the layout can report that a component is not currently visible. This is yet subject to change, depending on how we expose an API to programmatically collapse/expand/check state of a group.
This PR adds HeaderGroupBuilder and ListItemGroupBuilder with default behavior for headers and list items. All customization can be done using constructor parameters for these builders. For example, customizing the toggle button, restricting the maximum number of children of a group, etc.
ToggleableGroup is the default widget used for headers and list items, which includes a default button that fades in when the mouse enters, fades out when the mouse leaves, animates upon tap. It also includes a vertical line below the button, that also fades in/out. The widget can optionally animate the expanding/collapsing of a group.
A change that might be regrettable is that I changed _SingleColumnDocumentLayoutState to be public, so I can access information about groups inside tests. Once we figure out a public API for  that this can be reverted.
Remaining work

Define a public API to allow apps to expand/collapse groups programmatically and obtain information about the groups.
Modify the behavior for when the user presses enter at the end of the header of a collapsed group. This action should expand the group. This change depends of the API to expand/collapse groups.
Add mobile support. On mobile we might not have enough room to display a button near the content, so we need to find another way for that. Also, on mobile the buttons must be always visible (or at least when the caret sits within the node) because, of course, there is no mouse to hover over the button to make it appear.

https://github.com/user-attachments/assets/2cb80bb1-da27-4394-a4d5-0e53faa93e88

@matthew-carroll I still haven't figured out an ideal API to expand/collapse groups, but can you do a first pass review on this PR?

@angelosilvestre do you think we should hold off on this work until we figure out tree based documents? Or do you think most of the work would be interchangeable and it's worth the effort right now?
https://github.com/superlistapp/super_editor/discussions/2403

@matthew-carroll I'm not entirely sure.

We also want to make it possible for clients to create the concept of "banners", which are decorated boxes that contain any number of other nodes.

We could probably find a way to implement that with the API introduced by this PR. This PR is basically a way to extract trees from the list of nodes. This probably won't work for tables, but for more simpler requirements this might work.
Also, the ToggleableGroup widget introduced by this PR would be also usable with a tree structure. I guess it would worth to move this PR forward.


Removal of the facility feild in graypy logs

Presently the GLEF facility field is deprecated. As stated in their docs: http://docs.graylog.org/en/2.4/pages/gelf.html#gelf-payload-specification
We could either drop sending this field or send it as additional field _facility.

This is also similar to line and file fields


ImproveUse commons-lang3 uniformly and refactor PatternGenerator#generateTypePattern

Proposed changes
Issue Number: close #xxx
Problem summary
commons-lang (1and2) is no longer maintained since 2011, and the official recommendation is commons-lang3, which can be smoothly upgraded to be compatible with commons-lang.
We use both dependencies in fe, which can be completely unified.
PatternGenerator#generateTypePattern has many meaningless loops, and IntegerRange is introduced for, which is unnecessary. So I refactored it.
Describe your changes.

Use commons-lang3 uniformly
Add the check that prohibits commons-lang in checkstyle
Refactor PatternGenerator#generateTypePattern to reduce meaningless method loops

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

todo add UT

run buildall

The multiple loop in the PatternGenerator#generateTypePattern is for readability, this function will invoke in the compile time so is not the hot point.
Maybe we should use java.util.stream.IntStream.range() to replace it

The multiple loop in the PatternGenerator#generateTypePattern is for readability, this function will invoke in the compile time so is not the hot point.↳
I know, I just replace IntegerRange,but even with the current approach, I don't think it has increased the complexity of the code. right?
Maybe we should use java.util.stream.IntStream.rangeClosed() to replace the IntRange↳

I know, I just replace IntegerRange,but even with the current approach, I don't think it has increased the complexity of the code. right?

ok

run buildall


collect player salaries

For the psicoTSI like tool, maybe we should also collect the player salaries in addition of TSI

I think already we have in jsonobject...

I think already we have in jsonobject...

would makes things easier ...

hello @mistermax80 any news on this one ?

Not yet, but it is need only server activities.
I will try in 2 or 3 days

Ok cool !
Sent with GitHawk

Done by 76d7eaade8871520a28b0a1af65cca743e2cc07b


update homepage to the demo

github repo page has readme to tell how to use it. and demo page has no server for uploading, so point the homepage to github repo page


Set input files using Rust's build plan support in order to not always invoke cargo build

Rust writes Make .d files and also exposes a build-plan.  If we set input files -- dynamically, using an incremental task, I assume -- then maybe we can improve our cargo build story.  This has interesting properties for native builds/external NDK integration.

This has interesting properties for native builds/external NDK integration.

Would you have an example in mind? I have difficulties imagining what this accomplishes.

This has interesting properties for native builds/external NDK integration.

Would you have an example in mind? I have difficulties imagining what this accomplishes.

Sure: my team(s) are all working in Android Studio.  That works well for Kotlin and Java, but not well for Rust.  There's no reason we can't expose the Rust code to the IDE.  I investigated that for https://github.com/mozilla/gecko-dev and concluded the best way to do this (for C/C++ code, in this case) was to have a dummy CMake project and use the external NDK build mechanism.  We could do the same for Rust code, possibly with the same external NDK build mechanism, and get a little integration into the editor.  Maybe we don't get Rust syntax highlighting/code completion in Android Studio, but at least we could browse and search and replace.
Is that more clear?

Also, the real reason is to not invoke cargo build every time we invoke Gradle -- sometimes we can know that we don't need to invoke.

That's perfectly clear now, and I do like the idea! Would this also integrate the error reporting of Rust/cargo better into IntelliJ/Android Studio? Because that's very confusing for my co-workers: "Ruben, I have this cargo build error again" (while it's always a different error, of course).

That's perfectly clear now, and I do like the idea! Would this also integrate the error reporting of Rust/cargo better into IntelliJ/Android Studio? Because that's very confusing for my co-workers: "Ruben, I have this cargo build error again" (while it's always a different error, of course).

Without first-class IDE support (which exists, but is incompatible with using the Android support in IJ and AS, AFAIK) I doubt it will really help.  I noticed (when building on Windows) that Cargo output is interleaved into the terminal updates and I've filed https://github.com/ncalexan/rust-android-gradle/issues/28 to improve that (and potentially get warnings and errors surfaced into the IDE).
Help wanted!


Is Unirest-net being actively developed?

I find no comprehensive examples and I can't even set the content-type for a unirest.post!

NullReferenceException when using this header.
I know its old and unmantained. this comment is just to warn newcomers.


Change font, if possible, on sign in screen to increase accessibility

The current font is awful in terms of distinguishing capital letters from lowercase.

An alternative might be to see if it's feasible to make slot name matching case-insensitive in AP, since HK is not the only game that lacks clearly distinguishable lower and uppercase.

I would leave things as-is in Archipelago serverside and see if there's an easy fix on the HK side first. Changing the font should not be overtly difficult.
Find a font that the game has cached and use CanvasUtil.GetFont() to get it then set it on the TextInputs, not too bad.


Only bulk sign recent firefox files (bug 1157444)

Fixes bug 1157444

Code looks good to me.

Looks good to me. I like the comprehensive tests.

Updated with constants and values 4 and 37 for the firefox versions. @robhudson? @kmaglione?

Good naming idea ;) Updated

Thanks @kmaglione for the original code ;)


Implement loss function for multi label classification tasks

This implements the loss function from this paper:
Min-Ling Zhang and Zhi-Hua Zhou, "Multilabel Neural Networks with Applications to Functional Genomics and Text Categorization," in IEEE Transactions on Knowledge and Data Engineering, vol. 18, no. 10, pp. 1338-1351, Oct. 2006.
It is useful as a loss function for multi label classification tasks.

@sshepel Did you set some commands to force Jenkins to rebuild the branch without having to push new commits?

@sshepel Did you set some commands to force Jenkins to rebuild the branch without having to push new commits?
There is a button in Jenkins UI to do that, I have already provided @treo with all required info, no additional forcing logic where added.


Port retry package from kubergrunt

This DRYs the retry package from kubergrunt so that it can be reused across CLIs (e.g., most recent use case is cloud-nuke: https://github.com/gruntwork-io/cloud-nuke/pull/183)

These are exactly the same as the terratest functions (the E flavors). I only ported the things that we need to avoid adding and maintaining code we don't use.

Hm, wouldn't that be more confusing? That is, if we port all the retry functions, then we can remove them from all the other places right away. Whereas if we port only a few, then when someone goes to update the other locations, some items will be missing, and it won't be obvious if that's intentional or not, or if there are other differences, and we might never migrate over...

That is, if we port all the retry functions, then we can remove them from all the other places right away.

This is where I am confused. AFAIK we don't have these functions outside of kubergrunt (which was why it was copied over there), and I decided to move the kubergrunt functions here because of https://github.com/gruntwork-io/cloud-nuke/pull/183.

By the way, the reason I am pushing back on this is that it is some amount of non-zero effort to port the functions over from terratest, since we have to sanitize the logging and the t object. Vs copying over from kubergrunt, which already sanitized these, is much easier.
I don't quite have the time or effort to do more than what's here before I am off and I didn't want to block the cloud-nuke PR, which was why I did the minimal effort here.
Just wanted to provide the context. Happy to keep this PR open until we've sanitized and ported all the functions from terratest if you feel strongly, just that that might make this PR linger.

Thanks for review and sharing the concerns and sanity check! Going to merge and release this now.


Include story source filename in core output for failed stories

Proposed changes:
Include story source filename in the story name in the failed stories output to help find the failed story more easily (see #3419).
Passed the source filename starting from the StoryFileReader to a StoryStep.
Besides the story block names the source filename is included in the tracker events which are used for outputting the failed stories.
Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for submitting a pull request 🚀 @TyDunn will take a look at it as soon as possible ✨

Thanks for the PR 👍
I've left few comments. Also I think that the PR is missing a unit test that would actually check that for a failed story now prints the story name. 🙂

Give me some time to write a unit test and to be able to run it. I wasn't able to do it yet on my environment. Any guidance would be helpful. I'm using a Docker environment.

@degiz I just noticed two failing tests because of my changes:

test_persist_and_read_test_story_graph
test_persist_and_read_test_story

Because I've made changes in the tracker's sender_id in TrainingDataGenerator the assert fails now because the test is asserting on story files in different locations but the tracker contents should still be the same (except for the sender_id).
Do you think my changes are valid and we need to change the test asserts?
Or do you want me to add the story file path only when printing failed stories?

Hey @cheemingli

Give me some time to write a unit test and to be able to run it

So the idea of the change as I understand it is the following:

for each story block we keep the source file name (which is not the original story file, but a tmp copy of it)
in case some story block training fails, we can print the message that would contain the file name

I think the test should try to train a story with incorrect block, and check the stdout/stderr for the messages.

we need to change the test asserts

I think it's fine to change the asserts in mentioned tests cases.
I also see now why originally you wanted to strip _ from the tmp filenames.


SyntaxError in plugin "gulp-notify"

Bug Report
I've updated the config file and when I runnpm start everything seems to run ok the first time (and compiles SASS)... but then when it reaches the end (after STYLES - completed! I get the error and the task doesn't seem to continue watching/compiling files:
Message:
    Unexpected token { in JSON at position 129
[12:42:20] gulp-notify: [Error in notifier] SyntaxError in plugin "gulp-notify"
Message:
    Unexpected token { in JSON at position 129

I'm on OSX Mojave 10.14.5 and using a Docker container.
I've installed notify-send in the project with npm install notify-send but this has made no difference. I've also installed libnotify globally on my system with brew install libnotify but this has also not fixed the issue.
I've also tried adding double quotes around the properties as mentioned in https://github.com/mikaelbr/gulp-notify/issues/129

node -v: v10.16.0
npm -v: 6.9.0.

Your configuration might have a syntax error. Did you check that?

Hmmm I think it's all ok...
/**
 * WPGulp Configuration File
 *
 * 1. Edit the variables as per your project requirements.
 * 2. In paths you can add <<glob or array of globs>>.
 *
 * @package WPGulp
 */

module.exports = {

	// Project options.
	projectURL: '<IP_ADDRESS>:8080', // Local project URL of your already running WordPress site. Could be something like wpgulp.local or localhost:3000 depending upon your local WordPress setup.
	productURL: './', // Theme/Plugin URL. Leave it like it is, since our gulpfile.js lives in the root folder.
	browserAutoOpen: false,
	injectChanges: true,

	// Style options.
	styleSRC: './assets/sass/style.scss', // Path to main .scss file.
	styleDestination: './assets/css', // Path to place the compiled CSS file. Default set to root folder.
	outputStyle: 'compact', // Available options → 'compact' or 'compressed' or 'nested' or 'expanded'
	errLogToConsole: true,
	precision: 10,

	// JS Vendor options.
	jsVendorSRC: './assets/js/vendor/*.js', // Path to JS vendor folder.
	jsVendorDestination: './assets/js/', // Path to place the compiled JS vendors file.
	jsVendorFile: 'vendor', // Compiled JS vendors file name. Default set to vendors i.e. vendors.js.

	// JS Custom options.
	jsCustomSRC: './assets/js/custom/*.js', // Path to JS custom scripts folder.
	jsCustomDestination: './assets/js/', // Path to place the compiled JS custom scripts file.
	jsCustomFile: 'custom', // Compiled JS custom file name. Default set to custom i.e. custom.js.

	// Images options.
	imgSRC: './assets/img/raw/**/*', // Source folder of images which should be optimized and watched. You can also specify types e.g. raw/**.{png,jpg,gif} in the glob.
	imgDST: './assets/img/', // Destination folder of optimized images. Must be different from the imagesSRC folder.

	// Translation options.
	textDomain: 'mysocialnetwork', // Your textdomain here.
	translationFile: 'mysocialnetwork.pot', // Name of the translation file.
	translationDestination: './languages', // Where to save the translation files.
	packageName: 'mysocialnetwork', // Package name.
	bugReport: 'https://TomHay.es', // Where can users report bugs.
	lastTranslator: 'Tom Hayes<EMAIL_ADDRESS>// Last translator Email ID.
	team: 'Tom Hayes<EMAIL_ADDRESS>// Team's Email ID.

	// Browsers you care about for autoprefixing. Browserlist https://github.com/ai/browserslist
	// The following list is set as per WordPress requirements. Though, Feel free to change.
	BROWSERS_LIST: [
		'last 2 version',
		'> 1%',
		'ie >= 11',
		'last 1 Android versions',
		'last 1 ChromeAndroid versions',
		'last 2 Chrome versions',
		'last 2 Firefox versions',
		'last 2 Safari versions',
		'last 2 iOS versions',
		'last 2 Edge versions',
		'last 2 Opera versions'
	]
};

The error you're getting and the fact you made config changes makes me think this is a config issue, but your config looks fine and the config file isn't JSON (which the error points to).
If you go back to the default config file, do you still have the issue?

Changed back to the default config file and still getting the same issue!

As it seems to be a issue with the notification system, is there a way I can just disable this? messages in the command line are enough for me!

Feel free to contribute a setting that is checked when writing messages.
Your contributions are welcomed.


Add test for foldBlocks

Creating this draft pull request in relation to the foldBlocks issue here https://github.com/input-output-hk/cardano-node/issues/4624.
Due to adding genesis hashes to node config file (72e601764f875c6457468c9a8e32e7b1d24df689) cardano-testnet now does start (without adding the hashes it exceptioned out as described in the issue), but foldBlocks still doesn't receive ledger states and hangs indefinitely.
(Should I break out the 72e601764f875c6457468c9a8e32e7b1d24df689 to a separate PR so we could merge that?)

Cardano testnet now succesfully starts and foldBlocks test (occasionally) succeeds.
I say occasionally because the test is flaky: testnet nodes do start but quite frequently in the test runs they don't start posting anything to the local chain sync protocol and the test fails with a timeout.
The good thing is that the config files now allow the testnet to start, but why the socket is not written to remains to be researched.
Another thing that might be good to pursue is that while monitoring linux processes, the cardano node's start relatively early in the test, but the local chainsync socket starts to receive updates ~20 seconds in -- is that time required, e.g spending it on reaching consensus, or could it be cut much shorter? It would greatly benefit the convenience of testing if that time could be cut shorter.

This PR is now ready for review.
In addition to amending the node configuration file, there were two other issues that made this test flaky:

foldBlocks doesn't fold received blocks forever but returns when current block (or error) is reached. Sometimes this happened before any permanent blocks => permanent ledger states have been created (foldBlocks only emits permanent ledger states). We run foldBlocks in a loop to overcome this.
The chain is not extended fast enough for the two node/one pool testnet configuration that is created by default, changing the activeSlotsCoeff from 0.2 to 0.9 fixes this.

Closing this PR in favor of this one: https://github.com/input-output-hk/cardano-node/pull/4679


unsupported operand type(s) line 835 in rfb.py with Python 3.6

Hi,
I've just installed the new version of vncdotool and get this error when trying to capture screen :
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 835, in setKey
    if bsrc & (1 << i):
builtins.TypeError: unsupported operand type(s) for &: 'str' and 'int'

The complete listing is at the end of this message.
04/17/2020 EDIT : I remove vncdotool 1.0.0 and rebuild 0.12 version : it works fine. I retry with 1.0.0 (from pip), I get the error.
Thanks for your help.
Alain

VNC server and version : UltraVNC <IP_ADDRESS> on Windows Server 2016 64bits
vncdotool version : vncdotool 1.0.0 (installed by PIP)
Python version : 3.6
OS : Linux CentOS 7 up to date
steps to reproduce : command = vncdotool -p pwd -s <IP_ADDRESS>::5900 -v capture capture.png 2>&1

# vncdotool -p pwd -s <IP_ADDRESS>::5900 -v capture capture.png 2>&1
INFO:root:connecting to <IP_ADDRESS>:5900
INFO:twisted:Starting factory <vncdotool.command.VNCDoCLIFactory object at 0x7f769c669898>
INFO:twisted:Using protocol version 3.800
Unhandled Error
Traceback (most recent call last):
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/log.py", line 103, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/log.py", line 86, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/context.py", line 122, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/context.py", line 85, in callWithContext
    return func(*args,**kw)
--- <exception caught here> ---
  File "/usr/local/lib64/python3.6/site-packages/twisted/internet/posixbase.py", line 614, in _doReadOrWrite
    why = selectable.doRead()
  File "/usr/local/lib64/python3.6/site-packages/twisted/internet/tcp.py", line 243, in doRead
    return self._dataReceived(data)
  File "/usr/local/lib64/python3.6/site-packages/twisted/internet/tcp.py", line 249, in _dataReceived
    rval = self.protocol.dataReceived(data)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 685, in dataReceived
    self._handler()
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 694, in _handleExpected
    self._expected_handler(block, *self._expected_args, **self._expected_kwargs)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 255, in _handleVNCAuth
    self.vncRequestPassword()
  File "/usr/local/lib/python3.6/site-packages/vncdotool/command.py", line 52, in vncRequestPassword
    self.sendPassword(self.factory.password)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 261, in sendPassword
    des = RFBDes(pw)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/pyDes.py", line 410, in __init__
    self.setKey(key)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 835, in setKey
    if bsrc & (1 << i):
builtins.TypeError: unsupported operand type(s) for &: 'str' and 'int'

CRITICAL:twisted:Unhandled Error
Traceback (most recent call last):
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/log.py", line 103, in callWithLogger
    return callWithContext({"system": lp}, func, *args, **kw)
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/log.py", line 86, in callWithContext
    return context.call({ILogContext: newCtx}, func, *args, **kw)
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/context.py", line 122, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File "/usr/local/lib64/python3.6/site-packages/twisted/python/context.py", line 85, in callWithContext
    return func(*args,**kw)
--- <exception caught here> ---
  File "/usr/local/lib64/python3.6/site-packages/twisted/internet/posixbase.py", line 614, in _doReadOrWrite
    why = selectable.doRead()
  File "/usr/local/lib64/python3.6/site-packages/twisted/internet/tcp.py", line 243, in doRead
    return self._dataReceived(data)
  File "/usr/local/lib64/python3.6/site-packages/twisted/internet/tcp.py", line 249, in _dataReceived
    rval = self.protocol.dataReceived(data)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 685, in dataReceived
    self._handler()
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 694, in _handleExpected
    self._expected_handler(block, *self._expected_args, **self._expected_kwargs)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 255, in _handleVNCAuth
    self.vncRequestPassword()
  File "/usr/local/lib/python3.6/site-packages/vncdotool/command.py", line 52, in vncRequestPassword
    self.sendPassword(self.factory.password)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 261, in sendPassword
    des = RFBDes(pw)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/pyDes.py", line 410, in __init__
    self.setKey(key)
  File "/usr/local/lib/python3.6/site-packages/vncdotool/rfb.py", line 835, in setKey
    if bsrc & (1 << i):
builtins.TypeError: unsupported operand type(s) for &: 'str' and 'int'

CRITICAL:root:unsupported operand type(s) for &: 'str' and 'int'
INFO:twisted:Stopping factory <vncdotool.command.VNCDoCLIFactory object at 0x7f769c669898>
INFO:twisted:Main loop terminated.

@sibson now you can close this issue

Hello there. Is there an official workaround or something like that for this case? It's still valid, at least for v1.0.0 .

Nevermind.
For folks who struggle with the same issue - just use a latest stable version instead of 1.0.0 from pip repo, in my case it's 0.12.0 which worked like a charm.

thanks, @alex-romanov!
worked like a charm with 0.13


Update f1-standings extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

🚀🏎


Add java doc generation for heron api

Signed-off-by: Ali Ahmed<EMAIL_ADDRESS>

Can we generate javadocs for the entire codebase?
I plan to do that in the future.

How are javadocs currently being generated for the website?
Currently a release script is run separately which generates googles docs outside the build process.

Also when would you expect to trigger this? As part of CI and the website build, or just some other time?
As part of CI process , the website script should be able to gather the artifacts and publish them as needed.

We should not have 2 different ways to generate javadocs. Can you change this patch to replace the existing approach with this one?

@billonahill I've been discussing this with Ali. The intention, from both of our perspectivces, is absolutely to have a single Javadoc generation process (which could also be utilized by the website build process) and not multiple. I'll discuss further with him and see if there's a workable approach that can be included with this PR.

@billonahill @lucperkins
I have update the review without the java version tag and enabled it for the three public projects that are published to maven , the website script generates a unified java doc for everything that is not needed for maven publications , we will keep it for now and decide on it's future later.

@billonahill @kramasamy I have addressed the comments

Can we instead have one javadoc build for everything, and include that in the maven releases?

@billonahill we are trying to avoid building a single doc archive to upload to maven , since it will have more classes then required for the individual jars , for the website it's fine to have a unified doc collection and we do that already.

@billonahill - we can enable it for the whole repo in the next PR if needed. Merging it.


Is there an error in the luhn test cases?

Hello, maybe my understanding of the test case is wrong
{
	"a simple valid SIN that becomes invalid if reversed",
	"59",
	true,
}

Shouldn't the expected result be false in this case?

It is valid via the Luhn formula:

double every second digit, starting from the right
59
(10)9
if doubling the number results in a number greater than 9 then subtract 9 from the product.
(10-9)9
(1)9
19
sum the digits
1 + 9 = 10
if sum is evenly divisible by 10 it passes
10/10 = 1r0

Thanks, the description of the test case threw me off.
Cheers
Kevin
On 20 Dec 2017 12:57 am, "Tom Leen"<EMAIL_ADDRESS>wrote:

It is valid via the Luhn formula:
double every second digit, starting from the right
59
(10)9
if doubling the number results in a number greater than 9 then subtract 9
from the product.
(10-9)9
(1)9
19
sum the digits
1 + 9 = 10
if sum is evenly divisible by 10 it passes
10/10 = 1r0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/exercism/go/issues/972#issuecomment-352932953, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH2MW4Kb82YleFzIpTeWZNtjf-8UkRDjks5tCFuPgaJpZM4RHfLq
.

It's my bad, thinking too much.
Closing

{
        "a valid Canadian SIN",
        "055 444 285",
        true,
    }

The sum is 35. Correct me if I am wrong.
If thats the case can someone explain how this becomes valid?
Thanks. (Sorry if my question is silly)


~/build-dir/zencash-swing-wallet-ui$ ant -buildfile  issue

user@ubuntu:~/build-dir/zencash-swing-wallet-ui$ ant -buildfile ./src/build/build.xml
result: error: package javax.xml.bind is not visible I am using a mac with java-9, google search shows that is due to java-9, any workaround here? i guess there must be some mac users who tried the same wallet setup. Thanks!

This is fixed in the latest Git/master branch.


fix: Transaction nav link to history instead of queue

What it solves
Redirect the user to transaction history instead of transaction queue when clicking the transaction link in the sidebar navigation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 35.417%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3597

Relevant Lines:
9210

💛  - Coveralls


[Feature] Add forecast datasets and pre-commit

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.tangshiyu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add support for port isolation

It's been suggested that we should add a new security feature to LXD managed bridges.
This should be a new security.port_isolation boolean defaulting to false and where when set to true will turn on the isolated port feature for all ports.
There should be an exception for external interfaces and for tunnel devices when the system itself isn't a router (so where the tunnel will be used as an uplink).

I'd like to try and implement this if it's still available.

Yep, definitely still available. Assigned it to you.
@tomponline should be able to give you more details on what's needed here.

I believe the original suggestion came from here:
https://discuss.linuxcontainers.org/t/support-for-port-isolation-on-bridge-interfaces/9036
It has examples and explanation of what is trying to be achieved and why.
Looking at this file is the place to start: https://github.com/lxc/lxd/blob/master/lxd/device/nic_bridged.go
It contains the bridge NIC driver implementation, and is where the veth/tap pair is created to connect the container/VM to the bridge.

Validation for the config keys is done here: https://github.com/lxc/lxd/blob/master/lxd/device/nic_bridged.go#L43-L203
And the actual setup of the port is done here: https://github.com/lxc/lxd/blob/master/lxd/device/nic_bridged.go#L236-L346

If you can add support initially for native bridging using the examples in the forum post, then we can explore adding OVS support after that.

I've been mulling over the code now for some time. I believe I have gotten the validation part down, but I'm a little lost as to how to use the bridge commands (from the linked post) in the Start() function. Any advice would be greatly appreciated!

@matthewa150 please can you put up a draft PR of what you have so far so we can see it. With regard to the bridge commands I believe there was an example in the first reference https://discuss.linuxcontainers.org/t/support-for-port-isolation-on-bridge-interfaces/9036?u=tomp
I would suggest setting up a normal bridge using lxc network create <net name> and then manually trying those commands and checking they do indeed achieve the isolation desired.

Sorry for delay, I've made a preliminary pull request ( #8234 )


Put files in S3

Implements #126
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Running integration tests

Integration tests passed.


Mixed Precision missquantization

While training object detection model through hawq config, I realized there are much more int8 activation quantizations then int8 weight quantizations. According to netron some convolutions take int8 activations and int4 weights. I suppose that's not how things should be. What do you think?

@ljaljushkin the activation FakeQuantize acts as an input to two convolutions - one with INT8 quantized weights, another one with INT4. So the bitwidth for this activation quantizer is not defined properly (or there should be requantization). I guess both convs. that share an input activation FQ should have the same bitwidth for weights during precision selection for the layers?

Same problem has been located on resnet50 and squeezenet mixed precision hawq torch checkpoints from README.md
ResNet-50(link)

SqueezeNet V1.1 (link)

Looks like for this case to work we will have to track the node/nodes affected by a propagating quantizer (in addition to the HW configurations). This will require some changes to the QuantizerPropagationStateGraph, PropagatingQuantizer, QuantizerPropagationSolver - basically some additional info has to be gathered and the return values should be extended.

I would comment that having different bitdepth of activation and weight going into a convolution is  exactly what I do want - there is nothing constraining hardware generally to requite them to match.

I would comment that having different bitdepth of activation and weight going into a convolution is exactly what I do want - there is nothing constraining hardware generally to requite them to match.

@RikAllen, right. We need a special option for FPGA in HW config to allow different bit-width. The current behavior is the default for the existing hardware: VPU, CPU, GPU.


Google Event Ticket Logo as Base64 string

I don't have a URL for logo that is publically available. Is there any possibility that I can use base64 string for logo.

Hello,
I apologize, but this repository is being archived and replaced by google-pay/wallet-samples going forward. If you still have a question, please open a new issue in that repository.
Thank you!


Change the tests for Download KubeCtl

This PR fixex the issue https://github.com/alexellis/arkade/issues/423
Signed-off-by: Engin Diri<EMAIL_ADDRESS>
Description

Motivation and Context

[x] I have raised an issue to propose this change ([required] (https://github.com/openfaas/faas/blob/master/CONTRIBUTING.md))

https://github.com/alexellis/arkade/issues/423
How Has This Been Tested?

I run the tests in my IDE

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

LGTM too. I just sent a private note on Slack about reformatting the commit message. Could you take a look @dirien ?

Just FYI, please use Fixes: #423 instead of Fixes: 423 in future so that the GitHub UI can create a hyperlink and recognise it as closing the issue.


tldr --update output is displayed by pager

When a pager is configured, e.g. less, the output of tldr --update is displayed in it.
Info messages should be displayed as typical output, like STDERR, regardless of pager config.

@tranzystorek-io can you include more information about your environment and the issue. I cannot replicate this by setting export PAGER="less".
However in the code we are printing the "Successfully updated cache." message to stdout. @niklasmohrin or @dbrgn should we just change this to an eprintln!() since it is just a progress message?

Sorry, i meant configuring use_pager in config.toml

@dmaahs2017  As this concerns the use_pager setting, your fix is ineffective - tldr still first checks for pager in main and creates a pipe to the pager.

@tranzystorek-io You are right, the problem is that we spawn the pager process "too early". I think this part of the code could just be moved further down. Still, what @dmaahs2017 proposes is probably a good thing to do (and also part of making this problem go away).

I tried moving the configure_pager block down, but the problem still remains because the cache update logic doesn't necessarily exit the process afterwards. Maybe the -u flag should be treated as a "subcommand"?

Ah, yes. I guess to stay consistent with the current behavior, the pager should be spawned in that case too. Actually, to really stay consistent, the pager should also be configured if the pages are listed. To avoid spawning it twice, maybe this block should be before the three big ifs at the end of main, something like
if (args.flag_render.is_some() || args.flag_list || args.command.is_some()) && (args.flag_pager || config.display.use_pager) {
    configure_pager();
}

Maybe it should even stay where it is right now and just be guarded with the extra condition. What do you think?

We need a working fix, so either of your ideas is fine. But this shouldn't mask the fact that all the logic in the main function feels stitched together. Maybe once tealdeer switches over to clap, it could be organized better.

Yeah, maybe it would make sense to finish #108 first, and then take another look at the pager logic?
I can try to give that PR another try soon.

@tranzystorek-io by the way, #108 is now merged!

Alright, so we can now try to rearrange/rethink the pager setup.
From the discussion so far the pager needs to be set up for rendering either cached or local page files.
The order now is:

Configure pager
Render local page and exit, if selected
Do cache maintenance as needed: clear, update, including automatic cache update based on update interval
Render requested page from cache

My proposal:

Separate manual cache update from the automatic one
Move local render logic near the cache render or group them together
Configure the pager just before render

Rough order afterwards:

Do any manual cache actions
Prepare pager
Render local page if requested
Alternatively, autoupdate cache if needed and render requested cached page

Hm, I feel like splitting the manual and automatic updates is not the right move. I don't think there is any reason to allow for updating the online cache when rendering a local page (I might be wrong though :D), so the two update methods can stay in one place. How about something like
if render_local_page {
  configure_pager();
  render_the_page();
  exit();
}

if should_update() {
  do_the_update();
}

if should_render_from_cache {
  configure_pager();
  do_the_thing();
}

Alternatively, yesterday we had some ideas about encapsulating arguments like enable_styles and quietly into some sort of OutputManager or so. This one could also provide an interface for the main output which could then lazily spawn the pager on the first write. We are not planning on implementing this refactor before the next release though, so another approach is needed for now. What do you think?

Hm, I feel like splitting the manual and automatic updates is not the right move. I don't think there is any reason to allow for updating the online cache when rendering a local page

Since we provide the --update and --render flags anyway, nothing stops a user from running tldr --update --render mypage.md.
Otherwise, in my proposal the local vs cached render happens as the last step in the program (pseudocode example):
if update_flag {
    update_cache();
}

if pager_flag_or_config {
    configure_pager();
}

if render_flag() {
    render_local_file();
} else {
    if should_autoupdate() {
        update_cache();
    }

    render_cached();
}

Regarding the wrapper proposal: it seems neat but I'd assume it's not easy to design and implement as quickly as either of our initial ideas.

By the way, I removed the 1.5.0 milestone, this issue can also be fixed in a patch release. But it shouldn't be a blocker.

@niklasmohrin Nevermind, in my proposal the pager is still configured unconditionally, so the problem remains. Seems like we need to only configure pager conditionally and in the specific render points, like you suggested.

Since we provide the --update and --render flags anyway, nothing stops a user from running tldr --update --render mypage.md.

Exactly, I wonder if this is useful though. I feel like --update is its own operation and it may be better if it could only be used alone.


Actor reminder perf test: reduce wait time

The current actor_reminder perf test has a time.Sleep(10 * time.Minute) which is meant to let reminders be executed and capture errors.
That is a very long wait time that makes the tests take a lot of time, but has no impact on perf. In fact, perf is measured only while reminders are being created or updated before that.
Its purpose seems only to make sure that reminders execute without error, and that's something that should be done in an E2E test and not perf.
So, this PR reduces the wait time from 10m to 90s, to make the tests quicker to run.

/ok-to-perf

/ok-to-perf

The perf test seems to be failing @ItalyPaleAle

@mukundansundar yes but it’s unrelated. You can see if fails on master too.

/ok-to-perf

/ok-to-perf

/ok-to-perf

/ok-to-perf

Currently the actor reminder registration perf is continuously failing. Once that is fixed, this PR can be reassessed and then merged.

Uhm something's off. Now the test is expecting a QPS of 500. 🤔

@ItalyPaleAle both seem to be failing in line 197 which is

assert.Equal(t, 0, daprResult.RetCodes.Num400)

/ok-to-perf actor_reminder

/ok-to-perf actor_reminder

@mukundansundar looks like GHA was just "drunk". Because the test said it failed with condition not true, but that line did not have an "assert.True".
Anyways, tests are passing now

/ok-to-perf

/ok-to-perf

/ok-to-perf


Task may have uninterpolated variables in BuildSpec

Expected Behavior
A Task would fail validation if it tries to define a BuildSpec that has variables which would not be interpolated due to missing inputs or outputs. Having this error on validation would shorten the loop when trying to write a Pipeline as errors with Tasks would be caught much sooner.
Actual Behavior
The Task will create the Build with the uninterpolated variable
Steps to Reproduce the Problem

Add a variable ${inputs.params.thisdoesnotexist} to part of a BuildSpec

Good call, thanks for opening this @tanner-bruce !

So, if I'm understanding correctly (which is always an open question!), this would entail traversing the BuildSpec to find any fields in it that have ${input.params.whatever} and erroring for any cases where whatever isn't a defined parameter?

@abayer Yup. I wrote a quick PoC in pkg/apis/pipeline/v1alpha1/task_validation.go last night doing exactly that. I'm going to clean it up later tonight and make a PR.
${inputs.resources.whatever} also needs to be considered
/assign tanner-bruce

@tanner-bruce - gotcha! Will watch for your PR and won't bother trying to do it myself. =)

@tanner-bruce - just checking if you're still going to open that PR - I'm trying to find a small chunk of work to use as my first code contribution and wanna make sure this isn't a good option. =)


feat: add ap-southeast-1 Singapore

Describe the feature you'd like to request
add ap-southeast-1 Singapore
Describe the solution you'd like to see
add ap-southeast-1 Singapore
Additional information
No response
👨👧👦 Contributing

[ ] 🙋♂ Yes, I'd be down to file a PR implementing this feature!

Closing in favor of #840


Why design latent kernel structure

Thank you for sharing this wonderful work.
In my opinion, the AGD module is used to select low-level features in the encoder to enhance the feature (encoder output), perform spatial and channel attention will be enough. Why design latent kernel mechanism, what is the motivation and actual improvement using latent kernel?

Projecting a feature to latent space is often better than using the feature directly in practice. It is not our novelty, and we don't talk about it a lot.


Timezone - Dropdown is selectable when the "Set my time zone" bottom checkbox is checked

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Dropdown should be disabled if the bottom checkbox is checked
Actual Result:
Dropdown is selectable when the "Set my time zone" bottom checkbox is checked
Action Performed:

Go to https://staging.expensify.cash
Log in with any account
Go to Setting - Profile
Scroll down to Time zone field
Set my time zone automatically should be selected
Try to chose other time zone

Workaround:
Unknown
Platform:
Where is this issue occurring?
Web ✔
iOS
Android
Desktop App
Mobile Web
Version Number: 1.0.42-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

https://user-images.githubusercontent.com/44479856/117885489-e9502f80-b27b-11eb-8ebd-1405afa99e69.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @Dal-Papa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @marklouisdeshaun (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Upwork job posting

Triggered auto assignment to @marcaaron (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

While I can see that you pass disabled prop to Picker in src/pages/settings/Profile/ProfilePage.js, you don't actually pass it to RNPickerSelect in src/components/Picker/index.js.
So the fix is simply to add disabled to the list of destructed props of Picker component and pass it to RNPickerSelect.

Nice catch @dklymenk. Can we please also update the propTypes here so that it's clear we are passing this prop -> https://github.com/Expensify/Expensify.cash/blob/3fad8d181165842897e7259ecfbfe591976cf381/src/components/Picker/PickerPropTypes.js#L3

@marklouisdeshaun the solution from @dklymenk LGTM

It seems to be fine, but it isn't the correct way to fix. I think that there is not need to do so.
There is more simple way to fix it.

While I can see that you pass disabled prop to Picker in src/pages/settings/Profile/ProfilePage.js, you don't actually pass it to RNPickerSelect in src/components/Picker/index.js.
So the fix is simply to add disabled to the list of destructed props of Picker component and pass it to RNPickerSelect.

If it is a correct solution, why the issue occur on only Web? Is it okay on iOS and Android?

Actually reproduced the issue on both web and android, so the issue is not web only.
I submitted a draft PR with a fix #2824 , I'll test tomorrow for regressions on iOS and desktop app and remove draft label.
Thank you.

Confirm the fix works on all platforms. PR is ready for review


Modify class inheritance implemetation.

Coverage decreased (-0.01%) to 98.993% when pulling 2a388a54e137ab7dbdcd7ccdbbb30f0b75de24ec on develop into 851704e6638d2b2954ec185c42e702b3b07980d7 on master.

Coverage decreased (-0.01%) to 98.993% when pulling 2a388a54e137ab7dbdcd7ccdbbb30f0b75de24ec on develop into 851704e6638d2b2954ec185c42e702b3b07980d7 on master.


Pub/Sub subscription push endpoint

Any consideration to have this API implemented?
gcloud alpha pubsub topics create [your-topic-name]
gcloud alpha pubsub subscriptions create [your-subscription-name] \
--topic [your-topic-name] \
--push-endpoint \
https://[your-app-id].appspot.com/pubsub/push?token=[your-token] \
--ack-deadline 30

Hm - seems like you can't set a push-endpoint for a subscription (at least according to our docs: https://googlecloudplatform.github.io/google-cloud-node/#/docs/google-cloud/0.43.0/pubsub/topic?method=subscribe)
We should probably allow this even though it wouldn't be a typical subscription you can listen on (since the requests will be going to the endpoint required)

Yes, this is a case of poor docs on our part. You can indeed get the push endpoint through:
var topic = pubsub.topic('[your-topic-name]')

topic.subscribe('[your-subscription-name]', {
  ackDeadlineSeconds: 30,
  pushConfig: {
    pushEndpoint: 'https://[your-app-id].appspot.com/pubsub/push?token=[your-token]'
  }
}, function (err, subscription) {})

Please let me know if that works!

This works - thanks :)

I have a requirement of one topic and many push subscription.
Do every Subscriber have their own end points?


Ensure the manpage location is correct.

For some reason the manpage is installed in the root directory as /man1.
I am still learning Cmake so if this is not good then don't merge but after testing it i can at least confirm it works.

i just used
cmake -B build
cmake --build build

I don't really mind the application being installed in /usr/local/bin
it helps differentiate it from any potential system packages.
I just saw a manpage installed on my root and thought that can't be right.


[NESTED] guide: Exp implementation details, naming into Overview

Per https://github.com/iterative/dvc.org/pull/2909#discussion_r743028065

@jorgeorpinel let's merge this, to then review the main one. It's hard otherwise. Probably not the best case to use nesting (it's better when changes do not overlap much / independent by their nature - not when they both change the same files for the same reason).

let's merge this, to then review the main one

Are you sure? It's going to make reviewing https://github.com/iterative/dvc.org/pull/2909 harder. We could leave this unmerged until the main one is approved instead.
Agree that so far nesting hasn't been helpful. I'll stop trying 😓


nuspell: 3.1.2 -> 4.0.0, fix license

Motivation for this change
This change updates nuspell to the latest version and corrects its license metadata that was GPL-3.0-only but actually LGPL-3.0-or-later.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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.

Fails to build on darwin:
checking whether CFLAGS is valid... yes
checking whether LDFLAGS is valid... no
configure: error: something wrong with LDFLAGS=""
builder for '/nix/store/ppbkqkmvzmy5z391xm5g3f95945h1fl9-ruby-2.6.6.drv' failed with exit code 1

@SuperSandro2000 That's just ruby failing to build, take a look at https://github.com/NixOS/nixpkgs/issues/101330. I'll give this a go with my hacky -Wl,-w workaround for ruby.

@SuperSandro2000 That's just ruby failing to build, take a look at #101330. I'll give this a go with my hacky -Wl,-w workaround for ruby.

Oh yeah, we need to fix ruby asap.

Thanks!


In your implementation of Mean teacher, isn't the student model and the teacher model the same?

In the Mean Teacher paper, teacher model weights are EMA of student model's weights. In your implementation of Mean Teacher is the student model and teacher model have exactly the same weights?

Closing this issue as a duplicate of https://github.com/google-research/fixmatch/issues/74. We can re-open it if it turns out it's an actual issue.


Documentation is incorrectly generated for methods using 'scoped' keyword in its params.

It appears the doc generation fails to take 'scoped' keyword for method arguments into account, and then incorrectly splits the first param into multiple prams. This seem to appear wherever scoped is used as keyword for param.

Mby you alrdy noticed this, just curious where the problem is.

Yes, there are many issues with documentation rendering because of DocFX. This is not the only one.

After Yufei's comment i actually went to build the doc myself and I was not able to preproduce this problem on .NET Core SDK 6.0.408 and DocFx 2.67.3

No, not yet. If want you can make a PR and modify azure-pipelines.yml accordingly.

Same but with GitHub Actions: https://www.jamescroft.co.uk/building-net-project-docs-with-docfx-on-github-pages/

A new documentation has been deployed.


psutil error

I just have scanpy 0.2.7 and am trying to produce bpmc3 results. BUT right at the beginning (sc.read()) the following error! I will appreciate your help.
thanks
`--------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
 in ()
2 filename_genes = '/ifs/projects/proj077/backup/public_data/scanpy_tutorials_data/PBMC3K/filtered_gene_bc_matrices/hg19/genes.tsv'
3 filename_barcodes = '/ifs/projects/proj077/backup/public_data/scanpy_tutorials_data/PBMC3K/filtered_gene_bc_matrices/hg19/barcodes.tsv'
----> 4 adata = sc.read(filename_data, cache=True).transpose()
5 adata.var_names = np.genfromtxt(filename_genes, dtype=str)[:, 1]
6 adata.smp_names = np.genfromtxt(filename_barcodes, dtype=str)
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/readwrite.py in read(filename_or_filekey, sheet, ext, delimiter, first_column_names, backup_url, return_dict, cache)
73     if is_filename(filename_or_filekey):
74         data = read_file(filename_or_filekey, sheet, ext, delimiter,
---> 75                       first_column_names, backup_url, cache)
76         if isinstance(data, dict):
77             return data if return_dict else AnnData(data)
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/readwrite.py in read_file(filename, sheet, ext, delimiter, first_column_names, backup_url, cache)
364                 os.makedirs(os.path.dirname(filename_cache))
365             # write for faster reading when calling the next time
--> 366             write_dict_to_file(filename_cache, ddata, sett.file_format_data)
367     return ddata
368
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/readwrite.py in write_dict_to_file(filename, d, ext)
771             d_write[key] = value
772     # now open the file
--> 773     wait_until_file_unused(filename)  # thread-safe writing
774     if ext == 'h5':
775         with h5py.File(filename, 'w') as f:
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/readwrite.py in wait_until_file_unused(filename)
935
936 def wait_until_file_unused(filename):
--> 937     while (filename in get_used_files()):
938         time.sleep(1)
939
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/readwrite.py in get_used_files()
919 def get_used_files():
920     """Get files used by processes with name scanpy."""
--> 921     loop_over_scanpy_processes = (proc for proc in psutil.process_iter()
922                                   if proc.name() == 'scanpy')
923     filenames = []
AttributeError: module 'psutil' has no attribute 'process_iter'
`

That is evidently a problem of psutil; do you have an old version of it? I have tested with 5.2.2 and 5.1.2. Earlier, the function was called differently.

Does running pip install psutil --upgrade help?

Hm, I researched a bit more. psutil doesn't seem to cause problems and also, this has not been a problem within Scanpy for any user up to now. If you start a terminal with python and type
import psutil
psutil.process_iter()

does this throw an error? I'd really like to know what's going on.
If you want a quick fix; you can simply comment out line 773 in your file /ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/readwrite.py; this should cause no problem for your applications.

Btw: Scanpy now has an initial documentation at https://scanpy.readthedocs.io.

Hi Alex,
The psutil issue by updating it  has apparently gone away, however later on when I call sc.tl.louvain(adata_corrected, n_neighbors=10, resolution=1.3, recompute_graph=True)
, I get the following error. The igraph I am using is V 0.1.11.
Many thanks
Hashem
`DeprecationWarning                        Traceback (most recent call last)
 in ()
1
----> 2 sc.tl.louvain(adata_corrected, n_neighbors=10, resolution=1.3, recompute_graph=True)
3
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/tools/louvain.py in louvain(adata, n_neighbors, resolution, n_pcs, random_state, flavor, directed, recompute_pca, recompute_distances, recompute_graph, n_dcs, n_jobs, copy)
78             directed = False
79         if not directed: logg.m('    using the undirected graph', v=4)
---> 80         g = utils.get_igraph_from_adjacency(adjacency, directed=directed)
81         if flavor == 'vtraag':
82             import louvain
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/scanpy/utils.py in get_igraph_from_adjacency(adjacency, directed)
41 def get_igraph_from_adjacency(adjacency, directed=None):
42     """Get igraph graph from adjacency matrix."""
---> 43     import igraph as ig
44     sources, targets = adjacency.nonzero()
45     weights = adjacency[sources, targets]
/ifs/devel/hashem/sw-v1/conda/lib/python3.6/site-packages/igraph/init.py in ()
6 license = "MIT"
7
----> 8 raise DeprecationWarning("To avoid name collision with the igraph project, "
9                          "this visualization library has been renamed to "
10                          "'jgraph'. Please upgrade when convenient.")
DeprecationWarning: To avoid name collision with the igraph project, this visualization library has been renamed to 'jgraph'. Please upgrade when convenient.`

This is again a configuration problem. You don't have http://igraph.org/python/ installed. That's a library with thousands of users and citations. It has a very powerful and fast C++ core that allows treating dataset sizes with a million cells.
I realize that I misspecified this Scanpy's automatic installation in the requirements file. I just updated this and will push it to the master branch.
You simply need to type pip install python-igraph and then everything should work.

I think I have the most recent version of python-graph installed ( python-igraph 0.7.1.post6 ).
pip install python-igraph doesnt solve the issue since it is already updated.

I think this was happening because of confusion between igraph and  python-igraph, by un-installing both and reinstalling just python-igraph, the issue was solved. Interesting enough installation with conda didnt work, only installation with pip worked.
thanks again.

Sorry for being offline for a few hours and great that you could resolve it. In the next version, this confusion will not appear again.
Even though, obviously, any Scanpy release reproduces all examples on https://github.com/theislab/scanpy_usage, we're still at an early stage in the package. Things are progressing very fast and structure and maintenance of the package are becoming more and more professional. Also, soon, many new features and examples where other Python packages are used will be added.
Thank you for a bit of patience at this stage.
Alex
PS: We now have an initial version of the documentation: https://scanpy.readthedocs.io.

No worries and thank you for usually very prompt suggestions.
The idea that scanpy can handle many cells efficiently is great and therefore I have been trying it in a computing cluster (and not my local machine) for the future usage. This in turn makes configuration just a bit more difficult.
Looking forward to a more stable version with more added function.
Thank you
Hashem


feat: positivity extension for Real.rpow

This PR introduces a positivity extension for Real.rpow. It is located at the same place as the mathlib3 version, namely in Analysis/SpecialFunctions/Pow/Real.lean.
Note that the two tests I left commented out fail, but due to coercions from ℝ≥0∞ not working yet.

bors merge


Edit "pfSense-repo-245.conf" to enable upstream pkg repositories on 2.4.5-RELEASE-p1

Hello,
I am running 2.4.5-RELEASE-p1 and I had to edit another file to enable the upstream pkg repositories.
I did edit the files as instructed. But the file "/usr/local/etc/pkg/repos/pfSense.conf" links to "/usr/local/share/pfSense/pkg/repos/pfSense-repo-245.conf" which contains "FreeBSD: { enabled: no }" too.
After changing this from "no" to "yes" I was able to search and install packages from the FreeBSD repository.
One other thing: I was able to download "pfSense-pkg-zeek-0.1.1.txz" directly by issuing the following command: curl -O "https://raw.githubusercontent.com/shadonet/pfSense-pkg-zeek/master/data/pfSense-pkg-zeek-0.1.1.txz"
Kind regards,
Bouke

Thanks for pointing this out, I will update the docs.
The package has been added to the pfSense official package list from version 2.5.1, so you can install it from the package manager UI


Added a '/test custom' hook to the repo

/cc @kpouget

seems good, thanks @omertuc
/lgtm
/approve