rilling#119: allow user to view and update DoB, Gender and Leaderboard Settings

Describe the pull request
Allow user to view and update DoB, Gender and Leaderboard Settings
Link to the issue
https://github.com/rilling/OpenTracks-Winter-SOEN-6431_2024/issues/119

Everything looks good @jaedusandoval. I will merge the code into main branch.


Email and phone: validity check

For email and phone, addressBook still accepts even though it's not valid domain and country code (@example.com and +11 is still accepted)

checking for valid country code is not in scope.
This is mentioned in UG.
PHONE

Checking for valid country code is not in scope.


Tail tasks queue: configure separately from tasks queue

IO transports (primarily epoll, but this also applies to kqueue, nio) cant be configured with separate tail tasks queue factory -
instead single queue factory is used for both normal tasks and tail tasks.
Their parent SingleThreadEventLoop does have constructor accepting both taskQueue and tailTaskQueue.
I use SingleThreadEventLoop.executeAfterEventLoopIteration(Runnable) for internal tasks executed strictly from eventloop,
and would prefer to configure queue other than MPSC.

@mostroverkhov SGTM, would you like to send a PR?


Add Dollar Markdown Emoji to the setting item when there is a keyword like 'paid' in the description

Add Dollar Icon to setting item when there is a keyword like 'paid' in the description

Refer to this https://gist.github.com/rxaviers/7360908
There are many icons there. You can use their names
💰 :moneybag:
💴 :yen:
💵 :dollar:
💷 :pound:
💶 :euro:
💳 :credit_card:
💸 :money_with_wings:

So, as an example:

Setting
Type
Default
Description

sort
string
"default"
How to sort items in a table.

===>

Setting
Type
Default
Description

💲 sort
string
"default"
How to sort items in a table (paid).

Amazing !


Mention invalid input in exception message

close #222
Added sentence to parse exception message mentioning which section in command was invalid:

Instead of changing the parser as recommended by reviewer, just indicate which section was wrong.
This will also give troubleshooting feedback to the user.

Codecov Report
Base: 59.89% // Head: 59.92% // Increases project coverage by +0.03% :tada:

Coverage data is based on head (f1d3753) compared to base (704b97a).
Patch coverage: 66.66% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #293      +/-   ##
============================================
+ Coverage     59.89%   59.92%   +0.03%
- Complexity      614      615       +1
============================================
  Files           113      113
  Lines          2254     2256       +2
  Branches        249      249
============================================
+ Hits           1350     1352       +2
  Misses          821      821
  Partials         83       83

Impacted Files
Coverage Δ

...in/java/seedu/address/logic/parser/ParserUtil.java
64.81% <60.00%> (ø)

...ddress/logic/parser/exceptions/ParseException.java
100.00% <100.00%> (ø)

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

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


Matrix

new branch for matrix question

it is giving me an Error "Uncaught TypeError: Cannot read properties of undefined (reading '0')".

this program is showing Nan at console.


Frames in video viewer doesn't refresh when dragging video_trimmer circles on iOS

Hello @sbis04 , thank you for video_trimmer, it is awesome!
With iOS devices the video_player does not refresh the frame on onChangeEnd of the TrimEditor, this will be fixed with a little work around as @jakub suggest in the PR 11dba946f9bbedf36bca3724ce53bd1b2e216dc2 , can you please check?

Just tried to implement @jakub 's solution, but didn't work properly, still the bug on iOS devices remains.

Happened to me too...

It's an issue with the video_player, track it here: https://github.com/flutter/flutter/issues/78998


Need to enable fault filter per v1alpha3 specs in LDS

The existing LDS code implements fault filter per v1alpha1 specs. We need to augment the generated filters to use the right set of match conditions based on upstreams, headers, and order of routes.
refer to https://github.com/istio/api/pull/405 for the semantics.

I disagree that LDS code should be affected by fault filters for HTTP routes.
I think we need to move fault filter config into RDS instead of replicating RDS conditions in LDS.

I have talked to Louis, and we're ok omitting faults for now. Why can't
this be done with route metadata?
On Tue, Mar 13, 2018 at 1:20 PM Shriram Rajagopalan <
<EMAIL_ADDRESS>wrote:

I do agree. But that is more of a convenience feature. It is not a
correctness issue with the API. There are several things that need to move
to RDS, and lots more that need to move into LDS. We have to work within
the bounds.
Route-local filter stacks is a bigger design discussion in Envoy per
Harvey. So, while I have kick started it, its going to take a while (and I
am not sure we will get that done in 0.8 timeline). It would be remiss of
us to release envoy v2 support, with v1alpha3, and have feature regressions
like these.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/4238#issuecomment-372804666, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxgyS7LFmcy4atNiReBqzz9I1af4Zks5teCn-gaJpZM4SpXgz
.

Folks, is this supposed to be release blocking for 0.7.0?

No, v1alpha3 is still alpha in this release.
On Wed, Mar 21, 2018 at 1:53 PM Andy Lai<EMAIL_ADDRESS>wrote:

Folks, is this supposed to be release blocking for 0.7.0?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/4238#issuecomment-375091652, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxlMlb_Ar-NJ9OOTB2qKk2-dtvQ5Zks5tgr2ugaJpZM4SpXgz
.

Is this still release blocking? If so, is anyone working on this?

See #5055 . It’s not release blocking.


glib: Pick GVariant security patches

Description of changes
https://discourse.gnome.org/t/multiple-fixes-for-gvariant-normalisation-issues-in-glib/12835

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/)
23.05 Release Notes (or backporting 22.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.

I'm not sure about the current staging-next iteration.  The slowest path is *-darwin and that's around 50% rebuilt at this point already.


Fix acts_as_list scope on category

In previous version, category.{higher,lower}_item may return other
site's category.

:shipit:


ng-sortable: doesn't recognize "item in filteredItems" ngRepeat syntax

ng-sortable doesn't appear to recognize the non-standard, item in filteredItems = (items | filter...) ng-repeat syntax:
http://jsbin.com/podiqesoki/1/edit?js,output
Example jsbin comparing the item in filteredItems vs item in items as filteredItems:
http://jsbin.com/fivinigoco/1/edit?html,js,output

I have no idea how to fix it, in my opinion, so to do badly.


Shamelessly stolen from https://github.com/Laximas/vue3-steppy

A minimum of attribution or just contributing to the original project which is still active would have been the right thing to do
https://github.com/Laximas/vue3-steppy

Sorry you didnt see this.


React Webpack Boilerplate v.2

React Webpack Boilerplate v.2 will introduce some long needed features and optimizations. All new commits will be done to the v.2 branch, leaving the master branch intact and ready for use as it is.

[x] Implement unit tests (#9)
[x] CI and badges (#10 and #11)
[x] Git pre-commit hook (#27)
[x] Issue templates
[x] Improve documentation

The dependencies will be updated on both v.2 and master branches.

All milestone changes are implemented and merged to master. Happy v.2 !! :tada: :star: :tada:


Issue in adding authorization_manager and realm_manager configurations in deployment.toml

The configuration changes are not reflected in user-mgt.xml, to add properties to authorization_manager configuration, if we add following property to deployment.toml,
[authorization_manager.properties]
PreserveCaseForResources = false

This is because, the default value has been defined as set of object - [1]. This needs to be changed as follows until https://github.com/wso2/config-mapper/issues/11 is fixed. Same issue observed with realm_manager as well.
"authorization_manager.class": "org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager",
"authorization_manager.properties.AdminRoleManagementPermissions": "/permission",
"authorization_manager.properties.AuthorizationCacheEnabled": "true",
"authorization_manager.properties.GetAllRolesOfUserEnabled": "false",

[1] https://github.com/wso2/carbon-kernel/blob/4.5.x/distribution/kernel/carbon-home/repository/resources/conf/default.json#L9

fixed with https://github.com/wso2/carbon-kernel/pull/2457


Extend translation support

Fixes #64

Coverage increased (+0.0009%) to 99.611% when pulling e16ba8277b25234d3acb2cf409e2e567958a6cd0 on 64-some-translated-strings-not-working into 298621bec8c456ea878e41bb47865f2fbb5bde33 on master.


Don't send a Gift Card email if the user is already authenticated

In the future, maybe we will send an email, but it needs to be a different template

Coverage increased (+0.02%) to 69.859% when pulling e6d94d550d57dfb99c0db0e799f8aadece529225 on fix/gift-card-email into 25baa7f2b78dc47dfed993fa71f3d1485c94c110 on master.


Don’t cache bust urls that already have [chunkhash/hash] specified in webpack builds

Related to https://github.com/GoogleChrome/workbox/pull/808#pullrequestreview-64684918 We should omit the revision property of webpack assets if the asset is already using it's own filename cache busting.

One thing that bears mentioning: as an optimization, the precache() function will not append a cache-busting query parameter when populating its caches if the revision field is not present.

That's the same behavior that in sw-precache-webpack-plugin was defined by the dontCacheBustUrlsMatching configuration option, for which we recommended using a RegExp that matches URLs that contained hashes in them already.

I'm not sure exactly how, but is there any indication at this point in the build process whether filePath contains a versioning hash in it? (I'd assume it wouldn't for HTML files, but would for most other assets.) If you can safely infer the presence of a hash, then you can leave out revision and get optimal behavior without developers needing to use dontCacheBustUrlsMatching.

Note: we should sitill honor dontCacheBustUrlsMatching if specified.

@goldhand if the url has a hash in the revision I don't think we cache bust because the expectation is that that it'll be revisioned already.

Yes, I guess I wasn't very clear but that is what I meant :)

One way to do this would be to check if [chunkhash] is specified in the config.output but some plugins / loaders will disregard this param.
I dug up webpack's regex incase we want to use it: https://github.com/webpack/webpack/blob/ab2270263e9af5b0dd83e454c20ab3aa1797424a/lib/TemplatedPathPlugin.js#L7-L13
Another way is to use a regex to determine if there is a chunkhash in the asset filename. I'm a little concerned about this because its regex and there's a lot of ways to configure webpack filenames using chunkhash eg [name].[chunkhash].js, [name].output.[chunkhash:8].js, or maybe something silly like 12345.[name].js that would get picked up by the regex as being a hash when really its just a weird string.
I'm thinking the best way will be to check the config, then use the config to try to find the hash in asset filenames.
eg:
if the config.output.filename is: [name].output.[chunkhash:8].js
then we can use a regex like: /\w+?\.output\.\w{8}\./ but I'm not sure how I feel about this approach either...

@TheLarkInn graciously volunteered to be looped in to questions that came up regarding Webpack internals.
Sean, is there any "official" way for a Webpack plugin to determine whether a given asset contains [hash] or [chunkhash] in it, given that there are a lot of flexibility when it comes to configuring names?
Is using the RegExps at https://github.com/webpack/webpack/blob/ab2270263e9af5b0dd83e454c20ab3aa1797424a/lib/TemplatedPathPlugin.js#L7-L13 the best bet?

Stupid question, is the chunkhash string the same as what would be used in the filename?
If so, we can just check if the string is used in the filename, if it's different or short, it may be that we include revision information with filename for now until there is an API in webpack to reliably know if the revision info is in the filename or not.

Sorry have been catching up with GitHub mail debt. Let me find this out. I think you are on the right path with that plugin because it essentially provides the "across the board" templating.

I've got a potential approach in #1042 if folks want to weigh in on how hack-y that is.


cannot execute binary file: Exec format error

After installing azure CLI on Azure IOT Edge terminal
Using az command leads to the following error:
/usr/bin/az: line 2: /opt/az/bin/python3: cannot execute binary file: Exec format error

should be caused by arch. @VidithAgarwal could you pls share more aobut the Azure IOT Edge Terminal? @fengzhou-msft to help confirm.

Our installer packages do not support ARM64 yet. Please try az installed with pip install azure-cli and let us know if it works.

Thank you for the guidance @fengzhou-msft. Looks like pip3 install azure-cli is working for me.

@fengzhou-msft is it already supported or not yet?

@fengzhou-msft Feng Zhou FTE is it already supported or not yet?

This is tracked by https://github.com/Azure/azure-cli/issues/7368.

Maybe this should be added to the installation documentation.

@dustindortch  ARM64 support is added in #24180, we'll release official package later.


gdrdrv.ko silently crashing

gdrdrv.ko seems to be silently crashing in our system.
Initially, MPIs were failing when attempting to use gdrcopy. Reloading the driver made them work again, but it crashes again without obvious triggers or errors in the logs.
The sanity check also fails, which shows that the problem is unrelated to MPI. When a node is having problems with gdrdrv, we can't see an entry in /proc/devices. However, lsmod keeps showing the module as loaded.
The output for the sanity check is:
$ GDRCOPY_ENABLE_LOGGING=1 GDRCOPY_LOG_LEVEL=1 ./sanity -v
Running suite(s): Sanity
&&&& RUNNING basic
buffer size: 327680
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:181
&&&& FAILED basic
&&&& RUNNING basic_with_tokens
buffer size: 327680
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:218
&&&& FAILED basic_with_tokens
&&&& RUNNING basic_unaligned_mapping
First allocation: d_fa=0x2b50ffa00000, size=4
Second allocation: d_A=0x2b50ffa10200, size=65540, GPU-page-boundary 0x2b50ffa10000
d_A is unaligned
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:276
&&&& FAILED basic_unaligned_mapping
&&&& RUNNING data_validation
buffer size: 327680
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:358
&&&& FAILED data_validation
&&&& RUNNING invalidation_access_after_gdr_close
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:471
&&&& FAILED invalidation_access_after_gdr_close
&&&& RUNNING invalidation_access_after_cumemfree
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:547
&&&& FAILED invalidation_access_after_cumemfree
&&&& RUNNING invalidation_two_mappings
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:626
&&&& FAILED invalidation_two_mappings
&&&& RUNNING invalidation_fork_access_after_cumemfree
parent: Start
child: Start
child: waiting for cont signal from parent
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:772
Assertion "(read(read_fd, &cont, sizeof(int))) == (sizeof(int))" failed at sanity.cpp:740
&&&& FAILED invalidation_fork_access_after_cumemfree
&&&& RUNNING invalidation_fork_after_gdr_map
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:881
&&&& FAILED invalidation_fork_after_gdr_map
&&&& RUNNING invalidation_fork_child_gdr_map_parent
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1021
&&&& FAILED invalidation_fork_child_gdr_map_parent
&&&& RUNNING invalidation_fork_map_and_free
parent: Start
child: Start
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1134
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1134
&&&& FAILED invalidation_fork_map_and_free
&&&& RUNNING invalidation_unix_sock_shared_fd_gdr_pin_buffer
parent: Start
child: Start
child: Receiving fd from parent via unix socket
parent: Calling gdr_open
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1264
&&&& FAILED invalidation_unix_sock_shared_fd_gdr_pin_buffer
&&&& RUNNING invalidation_unix_sock_shared_fd_gdr_map
parent: Start
child: Start
child: Receiving fd from parent via unix socket
parent: Calling gdr_open
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1388
&&&& FAILED invalidation_unix_sock_shared_fd_gdr_map
&&&& RUNNING invalidation_fork_child_gdr_pin_parent_with_tokens
parent: Start
child: Start
ERR:  Error getting the gdrdrv driver version with ioctl error (errno=22). gdrdrv might be too old.
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1470
parent: CUDA generated tokens.p2pToken 0, tokens.vaSpaceToken 65024
&&&& FAILED invalidation_fork_child_gdr_pin_parent_with_tokens
100%: Checks: 14, Failures: 0, Errors: 0

Note that there might be a bug in the sanity check, where it reports 0 failures and errors, even though all the tests have failed.
The major device number reported in dmesg is the same as the device number of /dev/gdrdrv
We are in touch with some NVIDIA colleagues. They recommended opening a new issue here. At the moment it is not very clear how to proceed, since we can't reliably reproduce the problem once the driver has been reloaded. However, after waiting with the nodes online, gdrdrv ends up silently crashing again. The GPUs work fine though.

BTW: our driver version is 418.87.00-1, and we have gdrcopy-2.0-3

A kernel module crash dump should show up in the kernel log somehow.
Can you attach the output of 'dmesg -H', or simply 'dmesg' if -H is not supported on your system:

after a clean boot
after a crash event, if the machine is still alive
If it is not alive after the crash, can you set up a netconsole to capture the crash dump?

The machine is pretty much alive and even usable after a gdrdrv crash. I am not even sure if that can be qualified as crash. The system just acts as if the driver is not loaded, but lsmod lists it as loaded.
I have sent an email with the output of dmesg -H in 2 nodes (one freshly booted and healthy, and another one with gdrdrv unresponsive), and with the output of nvidia-bug-report.sh

The logs do not show anything interesting. As you said I exclude a crash of the kernel-mode driver component.

The system just acts as if the driver is not loaded, but lsmod lists it as loaded.

I suspect that for some reason, /dev/gdrdrv is either deleted or recreated with the wrong major number.
When the problem happens, can you double check that :

lsmod shows gdrdrv
/proc/devices shows gdrdrv with major number X, e.g.
$ grep gdrdrv /proc/devices
509 gdrdrv
/dev/gdrdrv is a char inode with matching major X
[drossetti@pwr04 ~]$ ls -l /dev/gdrdrv
crw-rw-rw-. 1 root root 509, 0 Feb 28 10:14 /dev/gdrdrv

BTW I'd love to see a debug tracing activated on your nodes.
That would print a kernel log in the gdrdrv_release() function to show that when the driver is  unloaded.
To do that, you need to pass an extra params when loading the kernel module:
$ /sbin/insmod src/gdrdrv/gdrdrv.ko dbg_enabled=1 info_enabled=1

I'll need the kernel log to be captured and uploaded.
please clean the kernel log before loading the driver with 'dmesg -c'
capture the log after the error shows up with 'dmesg >/tmp/kernel.log'

I mentioned it on the 1st post, but here it is summarized:
$ ./sanity
Running suite(s): Sanity
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:181
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:218
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:276
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:358
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:471
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:547
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:626
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:772
Assertion "(read(read_fd, &cont, sizeof(int))) == (sizeof(int))" failed at sanity.cpp:740
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:881
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1021
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1134
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1134
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1264
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1388
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1470
100%: Checks: 14, Failures: 0, Errors: 0
$ lsmod | grep gdr
gdrdrv                 17279  0
nvidia              18202459  94 nv_peer_mem,gdrdrv,nvidia_modeset,nvidia_uvm
$ grep gdr /proc/devices
$ ls -la /dev/gdrdrv
crw-rw-rw- 1 root root 226, 0 Mar  4 09:53 /dev/gdrdrv
$ dmesg -T | grep gdr
[Wed Mar  4 09:53:21 2020] gdrdrv:device registered with major number 226
[Wed Mar  4 09:53:21 2020] gdrdrv:dbg traces disabled, info traces disabled

I could enable debug tracing. The problem though, is that we can't reliably reproduce the problem. So I would have to enable the debug tracing everywhere and wait for it to crash. I am unsure of the overhead that could cause for users. For the time being, I have done that in a single node. I'll report back once the driver misbehaves again. If it takes too long, I'll enable debugging on other nodes to speed up the process.

I'm puzzled.
Is it really a bare-metal use-case, i.e. no containers, no virtualization stuff whatsoever ?
Is there some kind of background daemon which could possibly do something on our backs?

Can you create a reserved debug partition and submit the reproducer there?

Someone suggested that major==226 is used by nvidia_drm.
I don't see DRM being loaded there, but it could be somehow related.
Next time you reproduce, could you please attach the content of /proc/devices for more analysis ?

There are no containers or VMs of any kind involved.
The node where I have loaded the module with dbg_enabled=1 info_enabled=1 has not have the problem again yet. We do have 4 other nodes where the driver is loaded but not present in /proc/devices:
$ clush -bw jwc09n[030,033,108,141] "/sbin/lsmod | grep gdr" > gdrdrv_issues
---------------
jwc09n[030,033,108] (3)
---------------
gdrdrv                 17279  0
nvidia              18202459  94 nv_peer_mem,gdrdrv,nvidia_modeset,nvidia_uvm
---------------
jwc09n141
---------------
gdrdrv                 17279  0
nvidia              18202459  997 nv_peer_mem,gdrdrv,nvidia_modeset,nvidia_uvm

$ clush -bw jwc09n[030,033,108,141] "cat /proc/devices" >> gdrdrv_issues
---------------
jwc09n[108,141] (2)
---------------
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
 10 misc
 13 input
 29 fb
128 ptm
136 pts
162 raw
180 usb
188 ttyUSB
189 usb_device
195 nvidia-frontend
202 cpu/msr
203 cpu/cpuid
221 ss
222 kdump
223 trace
224 aux
225 mei
226 drm
227 nvidia-uvm
228 nvidia-nvswitch
229 nvidia-nvlink
230 infiniband_cm
231 infiniband_mad
231 infiniband_verbs
231 infiniband_cm
232 infiniband_mad
233 infiniband_verbs
234 sep4_1_u
235 sep4_1_b
236 sep4_1_s
237 sep4_1
238 socperf2_0
239 pax
240 rapl
241 ipmidev
242 ptp
243 pps
244 dimmctl
245 ndctl
246 hidraw
247 usbmon
248 bsg
249 hmm_device
250 watchdog
251 iio
252 rtc
253 dax
254 tpm

Block devices:
259 blkext
  9 md
254 mdp
---------------
jwc09n030
---------------
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
 10 misc
 13 input
 29 fb
128 ptm
136 pts
162 raw
180 usb
188 ttyUSB
189 usb_device
195 nvidia-frontend
202 cpu/msr
203 cpu/cpuid
221 ss
222 kdump
223 trace
224 aux
225 mei
226 drm
227 nvidia-uvm
228 nvidia-nvswitch
229 nvidia-nvlink
230 infiniband_cm
231 infiniband_mad
231 infiniband_verbs
231 infiniband_cm
232 infiniband_mad
233 sep4_1_u
234 sep4_1_b
235 sep4_1_s
236 sep4_1
237 socperf2_0
238 pax
239 infiniband_verbs
240 rapl
241 ipmidev
242 ptp
243 pps
244 dimmctl
245 ndctl
246 hidraw
247 usbmon
248 bsg
249 hmm_device
250 watchdog
251 iio
252 rtc
253 dax
254 tpm

Block devices:
259 blkext
  9 md
254 mdp
---------------
jwc09n033
---------------
Character devices:
  1 mem
  4 /dev/vc/0
  4 tty
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
  7 vcs
 10 misc
 13 input
 29 fb
128 ptm
136 pts
162 raw
180 usb
188 ttyUSB
189 usb_device
195 nvidia-frontend
202 cpu/msr
203 cpu/cpuid
221 ss
222 kdump
223 trace
224 aux
225 mei
226 drm
227 nvidia-uvm
228 nvidia-nvswitch
229 nvidia-nvlink
230 infiniband_cm
231 infiniband_mad
231 infiniband_verbs
231 infiniband_cm
232 infiniband_mad
233 sep4_1_u
234 sep4_1_b
235 sep4_1_s
236 sep4_1
237 infiniband_verbs
238 socperf2_0
239 pax
240 rapl
241 ipmidev
242 ptp
243 pps
244 dimmctl
245 ndctl
246 hidraw
247 usbmon
248 bsg
249 hmm_device
250 watchdog
251 iio
252 rtc
253 dax
254 tpm

Block devices:
259 blkext
  9 md
254 mdp

$ clush -bw jwc09n[030,033,108,141] "ls -la /dev/gdrdrv" >> gdrdrv_issues
---------------
jwc09n030
---------------
crw-rw-rw- 1 root root 226, 0 Mar  3 09:19 /dev/gdrdrv
---------------
jwc09n033
---------------
crw-rw-rw- 1 root root 226, 0 Feb  7 14:05 /dev/gdrdrv
---------------
jwc09n108
---------------
crw-rw-rw- 1 root root 226, 0 Feb 21 11:23 /dev/gdrdrv
---------------
jwc09n141
---------------
crw-rw-rw- 1 root root 226, 0 Feb 20 08:57 /dev/gdrdrv

Unfortunately, these nodes do not have the debugging options enabled.
Regarding a possible daemon doing things behind our backs....... I guess it is possible, but doing what? Are you aware of this being a side effect of any particular operation/command/check?
Regarding creating a debug partition and submit a reproducer...... I could, but we don't have a reproducer. Once the driver is reloaded, we can't reliably make it break again.
Maybe our best chance is to "brute force" it and enable debugging in all the nodes, to maximize the chances to catch the issue.

@damianam the problem is clear... drm module has major 226, which is what gdrdrv was supposed to have been assigned, judging from /dev/gdrdrv.
It looks like when drm is loaded, it overrides gdrdrv.
I suspect the service script which is used to load gdrdrv.
Can you copy yours here ?
If different, can you switch to the one which comes with the RPM (packages/rhel/init.d/gdrcopy) ? That scripts makes sure that nvidia.ko is loaded before gdrdrv.ko is loaded. That could be good enough to change the module loading order and work around the problem.

in addition, in your service script, you could explicitly load the drm module before gdrdrv.

but, you know why is drm loaded in the first place?

looking at the kernel code https://elixir.bootlin.com/linux/v3.10.108/source/fs/char_dev.c#L95, it seems there can be cases where a dynamic-major character device driver might get assigned a major, then later a fixed-major driver can steal it.
In practice, the major reservation would not enforced for gdrdrv.

@damianam I'll go ahead and close this bug. Feel free to reopen it in case of further problems.

Thanks for your help. We'll make sure the module is loaded at the end, and report back if we see the problem reoccurring.


How to add new button in any tab on drag field and listen in component ? [Custom Components]

anyone has any idea about it

Could we get any more information/context about what you are trying to do?

Agent Lane Doughtie linked Freshdesk ticket 45965 for this issue.


Serverless warmup multiple function attachment

How to attach multiple warmer functions for the same lambda.
I.e. Lambda Name - Test-Lambda
Test-Lambda:
    warmup:
      enabled: true

warmup:
    officeHoursWarmer:
      enabled: true
      events:
        - schedule: 'cron(0/5 10-11 ? * * *)'
      concurrency: 5
    outOfOfficeHoursWarmer:
      enabled: true
      events:
        schedule: 'cron(0/5 4-6 ? * * *)'
      concurrency: 3

I wanted to ping Test-Lambda as per officeHoursWarmer  and outOfOfficeHoursWarmer

This is a duplicate of #213.
The feature has been released in version 5.
It's documented in the readme and it works exactly as your example config

This is a duplicate of #213.
The feature has been released in version 5.
It's documented in the readme and it works exactly as your example config


Problem with new version (2.0) of connectivity plugin

Hello,
I'm using your plugin inside my xamarin Forms app.
When I call the CrossConnectivity.Current.IsConnected
I get this error:
System.NotImplementedExceptionThis functionality is not implemented in the portable version of this assembly. You should reference the NuGet package from your main application project in order to reference the platform-specific implementation.

Did you upgrade all of your NuGets to version 2.0? inside your PCL as well.
Also, which project type?

yes I do, thank you.
I'm discovering that with new version (I just upgraded also Visual
studio 2015 to the new SP1) my app crash at startup with debugging
enabling, and Xamarin Insight tell me that the problem is related to
your plugin:

Message:
This functionality is not implemented in the portable version of this
assembly. You should reference the NuGet package from your main
application project in order to reference the platform-specific
implementation.
Stack Trace:
Plugin.Geolocator.CrossGeolocator.get_Current()

however if I launch it in release mode, without debugging, it works.
I think it's something related to this:
https://forums.xamarin.com/discussion/50195/release-build-doesnt-work-aot-module-errors
(only inverted), obviously I already rebooted machine, removed the app
from device
Il 02/12/2015 18.45, James Montemagno ha scritto:

Did you upgrade all of your NuGets to version 2.0? inside your PCL as
well.
Also, which project type?
—
Reply to this email directly or view it on GitHub
https://github.com/jamesmontemagno/Xamarin.Plugins/issues/148#issuecomment-161377591.

What type of app are you trying? Is it Android? iOS?Windows?
Also this says Geolocator, not the connectivity. Did you install the Geolocator in all of your projects?

I am having absolutely no issues at all here in debug mode.

Hi,
I have also faced this issue , when i call CrossConnectivity.Current.IsConnected from my PCL Project in debug mode..i am debugging though genymotion android vm

@syedabidali , I also faced this exact error when calling ..IsConnected. Even after referencing the Connectivity plugin in the main project. After a Solution->Clean all, the error went away. This was on Xamarin Studio (v6) on a Mac, which is known for being a bit quirky, when everything else fails-> Clean All...

I too am getting this error.  Clean All, delete obj/bin folders...does not work.  All packages are up to date.  Anyone else having this issue?

I am having this exact issue. Cleaning project did not help. My packages are updated.

Doe anyone have a stacktrace of the error? you could put it on gist.github.com

It is error from my side, was not importing the connectivity packages separately in IOS and android folder. So it is fixed now. Thanks.

@jamesmontemagno
I had the same problem.   Once I cleaned the solution and Rebuilt all projects it is working now.
The error was
System.NotImplementedException:
This functionality is not implemented in the portable version of this assembly.
You should reference the NuGet package from your main application
project in order to reference the platform-specific implementation.
at at (wrapper dynamic-method) System.Object:3c9d8ea9-d4ba-4288-8249-b6cfa1d3f9f6 (intptr,intptr,intptr)
at at (wrapper native-to-managed) System.Object:3c9d8ea9-d4ba-4288-8249-b6cfa1d3f9f6 (intptr,intptr,intptr)

This issue seems due to this snippet of code:
 static IMedia CreateMedia()         { #if PORTABLE             return null; #else             return new MediaImplementation(); #endif         }
CreateMedia() is called by the Current property. I'm knocking my head against this issue, too.

@dottorp you must install the NuGet into all projects.

Hi James,
I also have the same issue...

I started a new project (only Droid, UW, W8.1).
I added Nuget Package: Xam.Plugin.Connectivity (v2.2.12) in all projects (Portable, Droid, UW, W8.1)
Windows is working fine.... But Droid gives me the following stack trace

11-09 10:49:53.976 D/Mono    ( 3843): Assembly Ref addref HelloWorld[0xada16ac0] -> Plugin.Connectivity.Abstractions[0xada16280]: 3
Unhandled Exception:
System.NotImplementedException: This functionality is not implemented in the portable version of this assembly.  You should reference the NuGet package from your main application project in order to reference the platform-specific implementation.
11-09 10:50:00.852 D/Mono    ( 3843): DllImport attempting to load: '/system/lib/liblog.so'.
11-09 10:50:00.852 D/Mono    ( 3843): DllImport loaded library '/system/lib/liblog.so'.
11-09 10:50:00.852 D/Mono    ( 3843): DllImport searching in: '/system/lib/liblog.so' ('/system/lib/liblog.so').
11-09 10:50:00.852 D/Mono    ( 3843): Searching for '__android_log_print'.
11-09 10:50:00.852 D/Mono    ( 3843): Probing '__android_log_print'.
11-09 10:50:00.852 D/Mono    ( 3843): Found as '_android_log_print'.
11-09 10:50:00.857 I/MonoDroid( 3843): UNHANDLED EXCEPTION:
11-09 10:50:00.861 I/MonoDroid( 3843): System.NotImplementedException: This functionality is not implemented in the portable version of this assembly.  You should reference the NuGet package from your main application project in order to reference the platform-specific implementation.
11-09 10:50:00.861 I/MonoDroid( 3843):   at Plugin.Connectivity.CrossConnectivity.get_Current () [0x0000d] in C:\projects\connectivityplugin\src\Connectivity.Plugin\CrossConnectivity.cs:23
11-09 10:50:00.861 I/MonoDroid( 3843):   at HelloWorld.MainPage.updateLabel () [0x00001] in D:\Xamarin\Nov2016\HelloWorld\HelloWorld\HelloWorld\MainPage.xaml.cs:21
11-09 10:50:00.861 I/MonoDroid( 3843):   at HelloWorld.MainPage..ctor () [0x0000f] in D:\Xamarin\Nov2016\HelloWorld\HelloWorld\HelloWorld\MainPage.xaml.cs:16
11-09 10:50:00.861 I/MonoDroid( 3843):   at HelloWorld.App..ctor () [0x0000f] in D:\Xamarin\Nov2016\HelloWorld\HelloWorld\HelloWorld\App.xaml.cs:16
11-09 10:50:00.861 I/MonoDroid( 3843):   at HelloWorld.Droid.MainActivity.OnCreate (Android.OS.Bundle bundle) [0x00027] in D:\Xamarin\Nov2016\HelloWorld\HelloWorld\HelloWorld.Droid\MainActivity.cs:23
11-09 10:50:00.861 I/MonoDroid( 3843):   at Android.Support.V4.App.FragmentActivity.n_OnCreate_Landroid_os_Bundle (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x00011] in <27c17fe440cf491ba8255bcefade6e02>:0
11-09 10:50:00.861 I/MonoDroid( 3843):   at (wrapper dynamic-method) System.Object:bc9eb942-7ae8-48fd-a2b3-16d8d28d4b30 (intptr,intptr,intptr)
11-09 10:50:00.872 W/art     ( 3843): JNI RegisterNativeMethods: attempt to register 0 native methods for android.runtime.JavaProxyThrowable
11-09 10:50:00.876 D/Mono    ( 3843): DllImport searching in: '__Internal' ('(null)').
11-09 10:50:00.876 D/Mono    ( 3843): Searching for 'java_interop_jnienv_throw'.
11-09 10:50:00.876 D/Mono    ( 3843): Probing 'java_interop_jnienv_throw'.
11-09 10:50:00.876 D/Mono    ( 3843): Found as 'java_interop_jnienv_throw'.
An unhandled exception occured.

Hope this will help you identify and fix the issue...

By the way, I had to check the following options in the manifest manually
ACCESS_NETWORK_STATE & ACCESS_WIFI_STATE

I re-tested it with a <<Blank App (Xamarin.Forms Portable) project>> and it works fine.
I tested it with <<Blank XAML App (Xamarin.forms Portable) and I get the error describe above.
Hope this can help you :-)

Sorry,
I just see that my text is not as I expected.
-1- I tested with a Blank App (Xamarin.Forms Portable) project and it works fine
-2- I tested with a Blank XAML App (Xamarin.Forms Portable) and I have the error

Also running into this problem. Its a bit odd, didnt work in debug mode at all then tried release and it worked for a little bit but now back to not working.
Not really sure what to do with this haha. Any news on this?

I don't answer responses on here, you need to go to the new repo, you probably need to clean and rebuild.

Also running into this problem. But i rechecked all the projects if the plugin is added in all. Then i clean the Droid(Specific Project) and then clean all. It  worked for me.
Thanks to @MagnusJohansson

Got my project working with this solution:

Install the latest version of Xam.Plugin.Geolocator
Clean
Rebuild

Done.


Define sex to proband when loading from URLs

If you load from URLs there is no way to define the sex  of the proband. With the latest changes you get a diamond because sex is not defined

We could pretty easily add a male/female dropdown option for proband in the file loading menu

Agreed, but not a high priority


Not creating config.ini

When you first run the docker it errors out that the config.ini doesn't exist. I had to just create an empty file then it would launch. The app instead of complaining that the config.ini doesn't exist it should just create it.

Good morning everyone,
I know I'm coming to the party late, but, I'm having a heck of a time trying to get this to run in docker for me. I'm new to docker(and loving it) I'm also running portainer as a front end on Ubuntu 22.10 with a few dockers running.
I used the docker-compose.yml that @Protektor-Desura had written up and I still can't get this working.
Can someone please help me with this?
I JUST found this app yesterday and I had a: "Where have you been all my life???" moment when I saw the absolute genius behind this script. I would love to get this running.
Thank you and have a nice day.

fixed.  Now creates config.ini


Allow CLI to override arbitrary options

It should be useful to have a way to override arbitrary YAML (sim. config) options using the command line interface (CLI). We should be able to have a way to override any parameter. Specifically, useful for overriding the zero-based old_ligand_index and new_ligand_index options.

Closed via #972


Create Dockerfile for Service

As a:
Developer
I want:
A dockerfile for every new service created in my mono-repo, including the services initialized in spk project init.
So that:
I can build my services as container images and push them to my container registry
Describe the solution you'd like:

spk project init should create dockerfiles for all services if they do not have one
spk service create should create dockerfiles for the new service if it does not exist

Describe alternatives you've considered:
None!
Additional context:
In order to automate HLD configuration, we need docker images for services
Does this require updates to documentation?:
Absolutely!

@mtarng

what should be included in the dockerfile?
What base image should we use?

alpine
ubunu
something else?

what default dependencies do we want to include?

Comments from @bnookala and Myself:

hm, i’m thinking that we could just copy a basic Dockerfile for something like node? Obviously whatever we place into that directory will never work with the application code, but it’s mostly for scaffolding and telling users that they need a Dockerfile for builds.

Any simple “hello world” http server container image should be good enough for the task…


TextInput's content is not center vertical

Hi, I found the TextInput's content is not center vertical (in some android devices like HUAWEI),when the TextInput's parent sytle is{flexDirection: 'row'},
It looks like the baseline is center,and text is more upper.

I fixed the bug,this is because TextInput has default padding,
My solution is add paddingTop: 0,paddingBottom: 0,to the TextInput style.

why paddingVertical not useful

I've just encountered this bug again. The placeholders of my TextInputs where on the emulator perfectly centered, but not on my device. Adding paddingTop: 0, paddingBottom: 0 to the TextInput styles solved the problem - now, the placeholders are centered vertically on both, emulator and device.
Interesting, though, that this bug still occures (RN 0.54.2) and that setting textAlignVertical: 'center', does not help at all.


pie chart subplots

pie chart subplots are created slightly differently than cartesion subplots - they use the domain property inside the traces. Here is an example: https://plot.ly/python/pie-charts/#pie-chart-subplots
would be cool if this were supported. my attempt was something along the lines of:
cf.tools.subplots([df.iplot(kind='pie', labels='a', values=c, asFigure=True) for c in ['a', 'b', 'c', 'd']])

You can now try
pies=[cf.datagen.pie().figure(kind='pie',values='values',labels='labels') for _ in list(range(4))]
cf.iplot(cf.subplots(pies))

I just tried this command, and seems like the error still persist. (version 0.8.2). Is this issue be resolved?


post-upgrade - no such column: django_q_schedule

Hello,
I am getting the following error after upgrading my system
no such column: django_q_schedule.cluster

python 3.8.5 to 3.9.6
django 3.1.1 to 3.2.6
django-q 1.3.5 to 1.3.9

I have made no other code changes. When trying to open the Scheduled Tasks from the admin panel, I get the error above. The qcluster console shows the error every 30s, in the shell, trying to run
from django_q.models import * Schedule.objects.all()
sqlite3.OperationalError: no such column: django_q_schedule.cluster
It stopped working after my upgrades but I did them all together (rookie mistake) so I am not sure which is the cause. Wondering if I need to roll back of if there's an easy solution.
Thank you!

I downgraded django-q back to 1.3.5 and everything is working again. Not sure what the issue is exactly.

PR #555 includes a migration file. After updating to the latest version, did you run ./manage.py migrate?
@youri-ds if you're having a problem during migrate, it's possibly due to trying to use the schedule() function or Schedule model during import time. Try moving that code to run later, for example during a custom qcluster management command. Here's an example I just wrote for a project:
from django_q.management.commands.qcluster import Command as BaseCommand
from django_q.models import Schedule

from example import tasks

class Command(BaseCommand):
    def handle(self, *args, **kwargs):
        ensure_schedule_updated()
        super().handle(*args, **kwargs)

def ensure_schedule_updated():
    def path(func):
        return f"{func.__module__}.{func.__name__}"

    Schedule.objects.update_or_create(
        name="run_debug_print",
        defaults={
            "func": path(tasks.debug_print),
            "schedule_type": Schedule.MINUTES,
            "minutes": 5,
        },
    )

@youri-ds if you're having a problem during migrate, it's possibly due to trying to use the schedule() function or Schedule model during import time. Try moving that code to run later, for example during a custom qcluster management command. Here's an example I just wrote for a project:

Hi Adam, I think your are right because I have some initialization code.
I will upgrade and test your code when I have the time.
Thank you.


HWKALERTS-40 Tenant integration

This long PR has following highlights:

Introduce tenant concept backend.

Updated API with tenant.
Re-arrange C* schema and queries to be partitioned by tenant.

Integration with accounts

Use of injected Persona in REST endpoint.
Link of Persona as Tenant for definitions and alerts

Actions definitions based on tenant + action Plugin + action Id

Instead of only actionId

Testing

Use of hawkular-dist on optional -Prest to run alerts integration tests on hawkular with all components

Minor things

A little bit of cleaning old code.

After this PR, I guess that having master and wintermute branches have not much sense as we have versioning now, so I vote to move to master and works with versioning for releasing.
We can use branches for major features/experimental paths.

After this PR, I guess that having master and wintermute branches have not much sense as we have versioning now, so I vote to move to master and works with versioning for releasing.
We can use branches for major features/experimental paths.

+1, after release of 0.0.3 we should not need the wintermute  staging branch.

There are a few things to deal with before we can merge this and release 0.0.3.  But overall, excellent job on this large task!

Thx for your review Jay.
I've fixed some missing javadocs and consolidated REST errorcodes.
I'm going to merge on wintermute and if everything goes well, rebase to consolidate into master.


BUG: data.history does not work for panel minute data

With minute panel data now supported thanks to 9103516 I tried a simple example algo which fetches daily data through data.history.
However, this gives me the following error:
data_portal.py, line 1094, in _get_daily_window_for_sids
AttributeError: 'DataPortal' object has no attribute '_equity_history_loader'
Below the code to reproduce this issue:
from zipline import run_algorithm
from datetime import datetime
from pytz import UTC
from zipline.data.loader import load_from_yahoo
from zipline.api import order, symbol, record, sid
import pandas as pd
import numpy as np
from zipline.utils.calendars import get_calendar

# Taken from zipline/tests/test_algorithm
def create_minute_df_for_asset(trading_calendar,
                               start_dt,
                               end_dt,
                               interval=1,
                               start_val=1,
                               minute_blacklist=None):

    asset_minutes = trading_calendar.minutes_for_sessions_in_range(
        start_dt, end_dt
    )
    minutes_count = len(asset_minutes)
    minutes_arr = np.array(range(start_val, start_val + minutes_count))

    df = pd.DataFrame(
        {
            "open": minutes_arr + 1,
            "high": minutes_arr + 2,
            "low": minutes_arr - 1,
            "close": minutes_arr,
            "volume": 100 * minutes_arr,
        },
        index=asset_minutes,
    )

    if interval > 1:
        counter = 0
        while counter < len(minutes_arr):
            df[counter:(counter + interval - 1)] = 0
            counter += interval

    if minute_blacklist is not None:
        for minute in minute_blacklist:
            df.loc[minute] = 0

    return df

def initialize(context):
    context.security = sid(1)

def handle_data(context, data):
    price_history = data.history(context.security, "price", 200, "1d")
    order(sid(1), 10)

if __name__ == '__main__':
    start = datetime(2009, 1, 1, tzinfo=UTC)
    end = datetime(2016, 1, 1, tzinfo=UTC)
    capital_base = 100000

    trading_calendar = get_calendar('NYSE')
    dt_transform = trading_calendar.minute_to_session_label

    data = create_minute_df_for_asset(get_calendar('NYSE'), datetime(1999, 1, 4), datetime(2016, 7, 29))
    dfs = {1 : data }
    panel = pd.Panel(dfs)

    results = run_algorithm(
                  start,
                  end,
                  initialize,
                  capital_base,
                  handle_data=handle_data,
                  data=panel,
                  data_frequency='minute',
                  bundle=None,
                  default_extension=False,
                  )

Best,
Mario

@nathanwolfe this is happening because we're now only passing a minutely reader if the user is running minutely, so daily-frequency history calls don't work.  We either need to have the minutely panel reader able to do daily aggregation on the fly, or we need to take the input data, aggregate it once, and then wrap that up in a daily bar reader so that we can still service daily data queries.

@ssanderson: Which method do you think would be better? Personally I think aggregating it once would be better, since people using Panel data probably pass in data for the few equities that they are interested in, so there would be less loss in doing the aggregation for equities that don't have data.history called on them.

@nathanwolfe I think upfront aggregation makes sense here.
The real win from a performance perspective that we don't end up re-doing the aggregation over any given period more than once. (If we did it on the fly, then we'd end up calculating OHLCV aggregations on the same day over and over if you called history() once per day.)  The challenge is that we need to make sure we're using the user's calendar to bucket minutes into days.  The naive implementation of just taking the date of each day only works for NYSE.
cc @jbredeche I think to support this correctly we need a fast vectorized minute_to_session_label that can take an array/datetimeindex of minutes and convert to their session labels.

PR: https://github.com/quantopian/zipline/pull/1407
Just the fast minute_to_session_label for large DatetimeIndexes of minutes is done so far.


Unable to reproduce published PTv3 performance on ScanNet

I use the released pretrained weights on huggingface to test on ScanNetv2. It only gives a 73.6 mIoU, which is much lower than the published 77.9 mIoU.  However, running validation with TTA gives the exact same 77.57 val mIoU that the exp record shows.
Is there any suggestions on how to correctly reproduce the results?

Hi, discussion here might be helpful (https://github.com/Pointcept/Pointcept/issues/284#issuecomment-2188177675). As the release model is trained with v1.5.1


Proxy two different ports of the same container (Nexus Registry setup)

Hi,
I am facing the problem of proxing different ports to the same container.
This is the case of Nexus Registry setup, where the nexus container exposes 8081 for nexus and a different one (i.e. 18444) for docker registry.
I have defined two sub-domain:

nexus.mydomain.com
docker.nexus.mydomain.com
Both of them need to use letsencrypt.

I cannot see any good solution for proxying the request coming from "nexus.mydomain.com" to 8081 and the one coming to "docker.nexus.mydomain.com" to 18444 of the same container using this proxy-companion.
I searched a bit and the only two possibile solutions could be:

Adding an extra nginx just to have a different container that prox all request to 18444 exposed by nexus container.
Change the nginx template in order to parse the VIRTUAL_HOST env property in order to support something like: VIRTUAL_HOSTS="nexus.mydomain.com:8081,docker.nexus.mydomain.com:18444"

The first one seems bad to me because I am introducing an extra (not wanted) nginx.
The second one seems better, but am not so confident in changing your template because I am not familiar with that syntax.
Can you give me an advice for solving my problem?
There is any possibility to support this kind of configuration in the future?

Hi.
This project (JrCs/docker-letsencrypt-nginx-proxy-companion) "only" purpose is to:

enable the automatic creation of certificates from containers env var.
put them in the right place with the right name so they can be used by nginx-proxy docker-gen template.
reload the nginx proxy when needed (cert creation or renewal).

What you want to achieve depends entirely on the jwilder/nginx-proxy project, which does the actual proxying and is maintained by different peoples.
We only deal with issues related to letsencrypt-nginx-proxy-companion, so please submit your nginx-proxy issues directly to the nginx-proxy repo.


Fix code scanning alert - CVE-2022-27191

Tracking issue for:

[ ] https://github.com/vertica/vertica-kubernetes/security/code-scanning/3

The package golang.org/x/crypto is used indirectly in the operator.
$ go mod why -m golang.org/x/crypto
# golang.org/x/crypto
github.com/vertica/vertica-kubernetes/cmd/operator
k8s.io/client-go/plugin/pkg/client/auth
k8s.io/client-go/plugin/pkg/client/auth/azure
github.com/Azure/go-autorest/autorest/adal
golang.org/x/crypto/pkcs12

It comes from k8s.io/client-go. We are currently using v0.24.0 of client-go. We can only update this once the operator-sdk is updated though. Leaving this open until we move up the operator-sdk to a version that fixes this.
This vulnerability doesn't look like it could be exploited in the operator.  The vulnerability seems to occur when you use the golang.ord/x/crypto/ssh package to implement an ssh server.  We only use this package as client authentication into the k8s apiserver. For more information, this google group post seemed to provide a good description of how the vulnerability can be exploited.

We upgraded the operator-sdk to v1.23.0, which changed the client-go tto v0.24.2.  The vulnerability is still an issue in that version.  Waiting for the next operator-sdk release.


20s delay before meterpreter commands return

In a demonstration setup, we have a physical laptop running up to date Kali (rolling), connected via a switch to another laptop running Win10 and finally, within a VirtualBox Win7. The virtual machine is set up with a bridge to the lan adapter.
Connecting to the victim system using meterpreter tcp works. Armitage however seems to need quite some thinking to execute meterpreter commands — whether from the embedded console or e.g. by listing directories. CPU and RAM don't show intensive activities, it just seems to idle. Working with msfconsole, the commands execute quickly as expected (<1s for getuid, while armitage needs 21s).
Can you help me debug this problem? I cloned this repo to put some old fashioned print statements in to debug where the most time is spent and dug around just a bit so far:
Apparently, from pressing [Enter] to the MeterpreterSession.processCommand() call alone two seconds pass. From there, the for loop is reached almost immediately, while the response is always delayed by ~20s. I followed through to RpcConnectionImpl.exec(), but didn't put time into understanding that and finding the code that then reports the result yet. But maybe this is already known, or you know only one place this could come from.
However, I don't know whether I'll be quickly called off this task in the following days, then I may not be able to properly help out.

For the record, I get the impression that this might not be a problem in armitage but in msfrpcd. I looked into their logs in /root/.msf4/logs/framework.log, and though there are errors, they do not occour when armitage issues commands but on startup of the server... I'm reluctant of opening an issue on rapid7/metasploit-framework though because I expect I will not be able to follow through after posting for more information etc.

This is a problem most likely introduced with metasploit-framework 5.x.x - we fixed it now by manually installing version 4.17.72, so I'll be closing this.

Yes I have the same issue, currently with version 6.0.40 of metasploit. I notice at the start of armitage i can run commands relatively fine, but after maybe getting a meterpreter session or running a few commands i start receiving significant delay for any command or module i try to run.
I used the msgrpc plugin from metasploit and connected armitage to the server, and same as you - running commands from the normal terminal msf console was instant, while using any part of armitage that has to gather or send data from msf was very very slow. It leads me to believe that there is maybe some communication issue between armitage and the RPC server


Add additional data feed categories and information

@dwightjl this is the view I have when I check
https://documentation-git-fork-dwightjl-dwightjl-i-196ad4-chainlinklabs.vercel.app/docs/ethereum-addresses/

Rebased to selecting-feeds


Width and top bar erroneous after color bulk update

I bulk updated the color and on the local installation it all looks good.
However top bar and width are distorted on live site.

Hello, As we can see on the screenshot, Status :404 Not found for some of the files , specifically the vendor files.

The files are there and were not changed. Not sure, where is the error. Please help and make a PR to fix it.  Cheers.

On my local machine it is working fine but I think that live site is not updated because "http://pslab.fossasia.org/vendor/bootstrap/css/bootstrap.min.css" shows that "The site configured at this address does not contain the requested file. " and it shows "Jquery is not defined" .Kindly check it once more if the files are updated. If that doesn't solve the issue what about using CDN's?

@Achint08 I am still unclear, what is the cause of this issue. I think the CDN should have been updated by now. Below a screenshot of the issue. Let's see if anyone would like to take it on and dive in deeper.

@mariobehling Is the website extracting data directly from this repository? In that case, There were bugs like there was no ending  tag at the end of the index.html. Problem can also be on server side also. Try to push again the files on the server.
There have been people gone through these issues http://stackoverflow.com/questions/11577147/how-to-fix-page-404-on-github-page . I can't see a issue on our side. If that doesn't work also , I am making a pull request which is using CDN for bootstrap , font-awesome and jquery. Merge it if nothing works. But most probably , issue is on server side as I have gone through.


[ZF3] issue #398 fix

This pull request also contain fix for #414

Coverage remained the same at 37.537% when pulling f10ce2a8807b10985bf73cc0794e41a917bd82b7 on kilip:feature/ZF3 into d2748e6bd2b2295c5bc8e565da3d81e5259ae8fd on cross-solution:feature/ZF3.

Coverage decreased (-0.02%) to 37.502% when pulling 6d40c2f69708264a6fd92a134390aa68850a648b on kilip:feature/ZF3 into e360b05f846c04bc867730874df88a7756e47960 on cross-solution:feature/ZF3.

Coverage decreased (-0.02%) to 37.502% when pulling 2e7028f93b89b751812aebab93f6cb47147f1a28 on kilip:feature/ZF3 into e360b05f846c04bc867730874df88a7756e47960 on cross-solution:feature/ZF3.

Coverage decreased (-0.02%) to 37.502% when pulling 50d8d1b5a1d38eb2e9912b06f2a0ace50dfbf8b0 on kilip:feature/ZF3 into e360b05f846c04bc867730874df88a7756e47960 on cross-solution:feature/ZF3.

Coverage decreased (-0.02%) to 37.502% when pulling fbab0439ae20b81edae35c481cea2f3f4221e044 on kilip:feature/ZF3 into e360b05f846c04bc867730874df88a7756e47960 on cross-solution:feature/ZF3.

Coverage decreased (-0.02%) to 37.507% when pulling 438fd9b4ddcd40086d8ca8fde2c5942ed1d0ea59 on kilip:feature/ZF3 into e360b05f846c04bc867730874df88a7756e47960 on cross-solution:feature/ZF3.


Add Watercolor for the background as an option

https://observablehq.com/@veltman/watercolor by @veltman
Or maybe as the default for the solid

Suggested options

People like it: https://twitter.com/excalidraw/status/1267100853715992576

Would be nice. Those options are way too flexible. Just up to three preset options work for me. I'm fine with solid too, but some would want the current Architect+solid.

Forth option would not be a big issue.. but of course we have to be very careful with that..

While we are discussing alternatives to solid fill, using broad fill strokes horizontally or vertically  could be an option. Looks like felt pen filling

Live: https://glitch.com/~broad-stroke-fill

Forth option would not be a big issue.. but of course we have to be very careful with that..

Yeah, it'd be ok if it's just one addition. This is hard. How about splitting into "Stroke sloppiness" and "Fill sloppiness"?


ImportError: cannot import name 'OmegleClient' from 'pyomegle' (C:\Users----\AppData\Roaming\Python\Python37\site-packages\pyomegle_init_.py)

Im using python 3 as I heard that it is now supported due to Mechanise now supporting python 3. The issue also occurs with OmegleHandler. Previously, the issue could be fixed by using IDLE as my editor but after reinstalling python (for other reasons) this fix no longer works.

The library as been updated to use the latest version of Mechanise just recently so is now compatible with Python3. Try again and open a new issue if it doesn't work.


How fastlmm deal with "NA" in covariate file?

Hello: This is not really an issue, but I'm not sure how fastlmm deals with samples with missing covariates? Are the samples still included in the calculation but the missing covariate values are filled in as mean/median of all samples (or through imputation)? Or the samples are dropped out of the analysis?
Thank you!

Baolichang,
Thanks for using FaSTLMM. Great question and one that I did not know the answer to until I looked into it.

how fastlmm deals with samples with missing covariates?

It doesn't!  Specifically, when I looked at single_snp and single_snp_scale, I  found that any NaN's will end up producing a NaN in the final output.
Work around: Fill missing with the column mean as a pre-processing step
Generate some sample data
import numpy as np
from pysnptools.snpreader import SnpData
#Create a SnpReader for the covariate. Here it is an in-memory SnpData, but could be something like
covar = Pheno(filename)
np.random.seed(92392)
covar = SnpData(iid=[('f0','iid0'),('f0','iid2'),('f0','iid3')],
sid = ['height','weight'],
val = np.random.random((3,2)))
covar.val[0,0] = np.nan
covar.val[2,1] = np.nan
covar.val
array([[       nan, 0.17374433],
   [0.54600136, 0.52250945],

   [0.87375742,        nan]])

The actual work around that fills in missing
#Assumes covar is a SnpReader, e.g. covar = Pheno(filename)
covar = covar.read(view_ok=True) #Turn the covariate into an in-memory SnpData
#Fill columns with mean
See https://stackoverflow.com/questions/18689235/numpy-array-replace-nan-values-with-average-of-columns
inds = np.where(np.isnan(covar.val))
covar.val[inds] = np.take(np.nanmean(covar.val, axis=0), inds[1])
covar.val
array([[0.70987939, 0.17374433],
   [0.54600136, 0.52250945],

   [0.87375742, 0.34812689]])

In contrast, for SNP data, any missing values are filled in with the mean.
For a single phenotype, any individuals with missing values are remove.
single_snp_scale also supports multiple phenotypes. If there are multiple phenotypes and any missing value, it raise an error.
Do you think we should change the code do fill in missing covariates automatically? Or is it safer to just have users to this preprocessing step as needed?
Carl
Carl Kadie, Ph.D.
FaST-LMM & PySnpTools Team
(Microsoft Research, retired)
Join the FaST-LMM user discussion and announcement list via emailmailto:fastlmm-user-join@python.org?subject=Subscribe (or use web sign uphttps://mail.python.org/mailman3/lists/fastlmm-user.python.org)

From: baolichang<EMAIL_ADDRESS>Sent: Tuesday, February 18, 2020 7:42:26 AM
To: fastlmm/FaST-LMM<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [fastlmm/FaST-LMM] How fastlmm deal with "NA" in covariate file? (#4)
Hello: This is not really an issue, but I'm not sure how fastlmm deals with samples with missing covariates? Are the samples still included in the calculation but the missing covariate values are filled in as mean/median of all samples (or through imputation)? Or the samples are dropped out of the analysis?
Thank you!

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffastlmm%2FFaST-LMM%2Fissues%2F4%3Femail_source%3Dnotifications%26email_token%3DABR65PZ2ZIQL2NIJ6MLILWLRDP6WFA5CNFSM4KXHBRU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOLN35A&data=02|01||b5a738b528cd442055a608d7b48927df|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637176373472067700&sdata=AwetHAPa%2F5xXfDs7zP7rP8o%2Bz8%2FmrxaNgg%2FzxlIz7ZU%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABR65P6VEWYT5FQTJ4X4HGTRDP6WFANCNFSM4KXHBRUQ&data=02|01||b5a738b528cd442055a608d7b48927df|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637176373472077705&sdata=Lw5plkWrevkncY9pQcx7CCTSVSqvLcobDrIGXKeOrcM%3D&reserved=0.

Hi Carl:
Thank you so much for the detailed reply!
It may make more sense to have the users to decide what to do with the missing values in the covariate file. In addition to filling in with the mean, some may prefer imputation or simply ignore the samples with missing covariates (a waste, but if bias may be introduced by mean/imputation it’s better not to use).
Thanks again for your help!
Bao-Li
From: Carl Kadie<EMAIL_ADDRESS>Sent: Tuesday, February 18, 2020 3:36 PM
To: fastlmm/FaST-LMM<EMAIL_ADDRESS>Cc: Chang, Bao-Li<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [External] Re: [fastlmm/FaST-LMM] How fastlmm deal with "NA" in covariate file? (#4)
Baolichang,
Thanks for using FaSTLMM. Great question and one that I did not know the answer to until I looked into it.

how fastlmm deals with samples with missing covariates?

It doesn't! Specifically, when I looked at single_snp and single_snp_scale, I found that any NaN's will end up producing a NaN in the final output.
Work around: Fill missing with the column mean as a pre-processing step
Generate some sample data
import numpy as np
from pysnptools.snpreader import SnpData
#Create a SnpReader for the covariate. Here it is an in-memory SnpData, but could be something like
covar = Pheno(filename)
np.random.seed(92392)
covar = SnpData(iid=[('f0','iid0'),('f0','iid2'),('f0','iid3')],
sid = ['height','weight'],
val = np.random.random((3,2)))
covar.val[0,0] = np.nan
covar.val[2,1] = np.nan
covar.val
array([[ nan, 0.17374433],
[0.54600136, 0.52250945],
[0.87375742, nan]])
The actual work around that fills in missing
#Assumes covar is a SnpReader, e.g. covar = Pheno(filename)
covar = covar.read(view_ok=True) #Turn the covariate into an in-memory SnpData
#Fill columns with mean
See https://stackoverflow.com/questions/18689235/numpy-array-replace-nan-values-with-average-of-columns
inds = np.where(np.isnan(covar.val))
covar.val[inds] = np.take(np.nanmean(covar.val, axis=0), inds[1])
covar.val
array([[0.70987939, 0.17374433],
[0.54600136, 0.52250945],
[0.87375742, 0.34812689]])
In contrast, for SNP data, any missing values are filled in with the mean.
For a single phenotype, any individuals with missing values are remove.
single_snp_scale also supports multiple phenotypes. If there are multiple phenotypes and any missing value, it raise an error.
Do you think we should change the code do fill in missing covariates automatically? Or is it safer to just have users to this preprocessing step as needed?
Carl
Carl Kadie, Ph.D.
FaST-LMM & PySnpTools Team
(Microsoft Research, retired)
Join the FaST-LMM user discussion and announcement list via emailmailto:fastlmm-user-join@python.org?subject=Subscribe (or use web sign uphttps://mail.python.org/mailman3/lists/fastlmm-user.python.org)

From: baolichang <notifications<EMAIL_ADDRESS>Sent: Tuesday, February 18, 2020 7:42:26 AM
To: fastlmm/FaST-LMM <FaST-LMM<EMAIL_ADDRESS>Cc: Subscribed <subscribed<EMAIL_ADDRESS>Subject: [fastlmm/FaST-LMM] How fastlmm deal with "NA" in covariate file? (#4)
Hello: This is not really an issue, but I'm not sure how fastlmm deals with samples with missing covariates? Are the samples still included in the calculation but the missing covariate values are filled in as mean/median of all samples (or through imputation)? Or the samples are dropped out of the analysis?
Thank you!

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffastlmm%2FFaST-LMM%2Fissues%2F4%3Femail_source%3Dnotifications%26email_token%3DABR65PZ2ZIQL2NIJ6MLILWLRDP6WFA5CNFSM4KXHBRU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOLN35A&data=02|01||b5a738b528cd442055a608d7b48927df|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637176373472067700&sdata=AwetHAPa%2F5xXfDs7zP7rP8o%2Bz8%2FmrxaNgg%2FzxlIz7ZU%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABR65P6VEWYT5FQTJ4X4HGTRDP6WFANCNFSM4KXHBRUQ&data=02|01||b5a738b528cd442055a608d7b48927df|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637176373472077705&sdata=Lw5plkWrevkncY9pQcx7CCTSVSqvLcobDrIGXKeOrcM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/fastlmm/FaST-LMM/issues/4?email_source=notifications&email_token=AI24KU6W3S4RMIBY6CV4L7TRDRBBVA5CNFSM4KXHBRU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMES2LY#issuecomment-587803951, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI24KU527JLM55IHH2TZMKLRDRBBVANCNFSM4KXHBRUQ.

Bao-Li,
Excellent suggestions.
At the very least I’ll add check for missing values and raise a clear error (in single_snp and single_snp_scale).

Carl

From<EMAIL_ADDRESS>Sent: Thursday, February 20, 2020 10:50 AM
To<EMAIL_ADDRESS>Cc: Carl<EMAIL_ADDRESS>State<EMAIL_ADDRESS>Subject: Re: [fastlmm/FaST-LMM] How fastlmm deal with "NA" in covariate file? (#4)
Hi Carl:
Thank you so much for the detailed reply!
It may make more sense to have the users to decide what to do with the missing values in the covariate file. In addition to filling in with the mean, some may prefer imputation or simply ignore the samples with missing covariates (a waste, but if bias may be introduced by mean/imputation it’s better not to use).
Thanks again for your help!
Bao-Li
From: Carl Kadie<EMAIL_ADDRESS>Sent: Tuesday, February 18, 2020 3:36 PM
To: fastlmm/FaST-LMM<EMAIL_ADDRESS>Cc: Chang, Bao-Li<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [External] Re: [fastlmm/FaST-LMM] How fastlmm deal with "NA" in covariate file? (#4)
Baolichang,
Thanks for using FaSTLMM. Great question and one that I did not know the answer to until I looked into it.

how fastlmm deals with samples with missing covariates?

It doesn't! Specifically, when I looked at single_snp and single_snp_scale, I found that any NaN's will end up producing a NaN in the final output.
Work around: Fill missing with the column mean as a pre-processing step
Generate some sample data
import numpy as np
from pysnptools.snpreader import SnpData
#Create a SnpReader for the covariate. Here it is an in-memory SnpData, but could be something like
covar = Pheno(filename)
np.random.seed(92392)
covar = SnpData(iid=[('f0','iid0'),('f0','iid2'),('f0','iid3')],
sid = ['height','weight'],
val = np.random.random((3,2)))
covar.val[0,0] = np.nan
covar.val[2,1] = np.nan
covar.val
array([[ nan, 0.17374433],
[0.54600136, 0.52250945],
[0.87375742, nan]])
The actual work around that fills in missing
#Assumes covar is a SnpReader, e.g. covar = Pheno(filename)
covar = covar.read(view_ok=True) #Turn the covariate into an in-memory SnpData
#Fill columns with mean
See https://stackoverflow.com/questions/18689235/numpy-array-replace-nan-values-with-average-of-columns
inds = np.where(np.isnan(covar.val))
covar.val[inds] = np.take(np.nanmean(covar.val, axis=0), inds[1])
covar.val
array([[0.70987939, 0.17374433],
[0.54600136, 0.52250945],
[0.87375742, 0.34812689]])
In contrast, for SNP data, any missing values are filled in with the mean.
For a single phenotype, any individuals with missing values are remove.
single_snp_scale also supports multiple phenotypes. If there are multiple phenotypes and any missing value, it raise an error.
Do you think we should change the code do fill in missing covariates automatically? Or is it safer to just have users to this preprocessing step as needed?
Carl
Carl Kadie, Ph.D.
FaST-LMM & PySnpTools Team
(Microsoft Research, retired)
Join the FaST-LMM user discussion and announcement list via emailmailto:fastlmm-user-join@python.org?subject=Subscribe (or use web sign uphttps://mail.python.org/mailman3/lists/fastlmm-user.python.org)

From: baolichang <notifications<EMAIL_ADDRESS>Sent: Tuesday, February 18, 2020 7:42:26 AM
To: fastlmm/FaST-LMM <FaST-LMM<EMAIL_ADDRESS>Cc: Subscribed <subscribed<EMAIL_ADDRESS>Subject: [fastlmm/FaST-LMM] How fastlmm deal with "NA" in covariate file? (#4)
Hello: This is not really an issue, but I'm not sure how fastlmm deals with samples with missing covariates? Are the samples still included in the calculation but the missing covariate values are filled in as mean/median of all samples (or through imputation)? Or the samples are dropped out of the analysis?
Thank you!

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffastlmm%2FFaST-LMM%2Fissues%2F4%3Femail_source%3Dnotifications%26email_token%3DABR65PZ2ZIQL2NIJ6MLILWLRDP6WFA5CNFSM4KXHBRU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOLN35A&data=02|01||b5a738b528cd442055a608d7b48927df|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637176373472067700&sdata=AwetHAPa%2F5xXfDs7zP7rP8o%2Bz8%2FmrxaNgg%2FzxlIz7ZU%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABR65P6VEWYT5FQTJ4X4HGTRDP6WFANCNFSM4KXHBRUQ&data=02|01||b5a738b528cd442055a608d7b48927df|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637176373472077705&sdata=Lw5plkWrevkncY9pQcx7CCTSVSqvLcobDrIGXKeOrcM%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/fastlmm/FaST-LMM/issues/4?email_source=notifications&email_token=AI24KU6W3S4RMIBY6CV4L7TRDRBBVA5CNFSM4KXHBRU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMES2LY#issuecomment-587803951, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI24KU527JLM55IHH2TZMKLRDRBBVANCNFSM4KXHBRUQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffastlmm%2FFaST-LMM%2Fissues%2F4%3Femail_source%3Dnotifications%26email_token%3DABR65P4CUSJVA4JI24XXTILRD3GGDA5CNFSM4KXHBRU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMPTVCY%23issuecomment-589249163&data=02|01||b728bfc6f52146489f9e08d7b635b66f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637178214113900649&sdata=6Q4PjGeL3L5bVGEPnGiuRlyOeSUWwM%2FD6OGDnHA07lk%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABR65P7YDY3O5K3RE4ITVT3RD3GGDANCNFSM4KXHBRUQ&data=02|01||b728bfc6f52146489f9e08d7b635b66f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637178214113910636&sdata=QLk1Mt3Vl52PrPP0Ck1pUF2WZI%2BpHxwO%2BX46XBrhwtk%3D&reserved=0.


Removed Android service

This PR removes the Android service in favor of the in-app playback.
Pros

Fixes #473
Fixes #391
Fixes #732
Fixes #813
Fixes #812
Fixes #524
Fixes #343
Might fix #620
Closer behavior of both platforms
Possibly Expokit support

Cons

Android may possibly kill the app while playing in order to reduce system resource usage. We'll have to figure out how frequently it happens and how to prevent that from happening.
The player won't be able to play while the app is closed. This is a feature that is usually disabled through the stopWithApp option by the majority of the apps anyway.
This was a big differential from other music modules, as it was closer to a native music app, but I figured that react-native doesn't work properly with services nor the community wants to work with native behavior like this.

As this is a big change on Android, I'd love to see testing here from all sorts of apps.

I would be happy to test this out on some Android phones to see how long it takes for the app to be killed.
However, I do wonder if this is the right direction. For a music player having music stop at random moments feels like a more existential issue than intermittent crashes for a small subset of users. (0.8% in our radio-player case)
Our use-case is a radio app, where I know users can listen to a station for up to 8 hours at a time - the chance that the app would be killed by the system during that time is pretty high.. and for a user it is not a nice experience to have to wonder why their music stopped playing.
Here is a related issue about background-audio on expo, where users report apps being killed after several minutes in the background: https://github.com/expo/expo/issues/4850

@puckey i will love to try your radio app, also i will also be testing the online streaming. i would like to know does your app streams hls content or not as its more prominent on hls (m3u8) links

@ashishfeels here you go: https://play.google.com/store/apps/details?id=com.jonathanpuckey.radiogarden&hl=nl  We don't support HLS content right now, but it is on our roadmap.

@Guichaguri can we make the error reporting better. i mean the type of error we get while playing the audio. like i was trying to play an hls content and it was giving me liveBehindWindow Error , but on js side it was only giving me playback error. that will help the issue in debugging the problems.

@ashishfeels we definitely should, but that's for another PR.

yes @Guichaguri that's just an idea as i tried to fix in my fork i don't know its correct or not but it works :P

Happy to test this as well 👍

OMG guys isn't this the exact opposite of the correct direction?

This was a big differential from other music modules, as it was closer to a native music app, but I figured that react-native doesn't work properly with services nor the community wants to work with native behaviour like this.

Are you feeling ok? People have been screaming at you on Canny since 2017 for proper background audio support and now you want to strip it out entirely because your implementation is crappy and theres a bunch of issues around it.
I opened this issue a year ago. It literally took me around 8 hours after ejecting to code up a proper foreground service myself that has worked flawlessly on Android ever since. While I can't share my code directly I did include a similar implementation by someone else that should work well AND a video from the ExoPlayer team describing exactly how it should be done properly.

Sorry but seriously I'm getting a bit fed up of all the unfulfilled promises. Warning to anyone thinking of making an audio player app in Expo: DO NOT DO IT FOR GOD SAKE!

Sorry left a bit of a snarky message thinking this was the Expo repo lol.

This was a big differential from other music modules, as it was closer to a native music app, but I figured that react-native doesn't work properly with services nor the community wants to work with native behavior like this.

I'm not sure I agree with this and would definitely advise pushing on for full background audio. Expo has been dallying for 3 years on this subject much to everyone's dismay. I created this issue a year ago but ended up just ejecting from Expo and coding the foreground service myself following this example and video.
Our background playback has been working flawlessly since.

@samkuhn any chance you could delete your earlier message? It would be nice to keep the tone friendly and encouraging here..

@samkuhn any chance you could delete your earlier message? It would be nice to keep the tone friendly and encouraging here..

Yes I did delete it? I've been through the wars with Expo and I mistakenly thought that this was a pull request for that repo. I apologise.

@samkuhn it would be better if you read the repo name correctly next time. expo repos initials generally starts with the word "expo".

@samkuhn Removing the Android service doesn't mean background mode won't work anymore, it will still play while the app is open and minimized, but it will stop as soon as the app is swiped from the task list (basically the same behavior as having the old stopWithApp option enabled)

Hi Guichaguri, Wouldn't the audio intermittently cut out while minimized though? That is what I found in my experience with no foreground service running to keep the audio alive (as per ExoPlayer team recommendations).
I'd also like to apologise again for my tone this morning I totally thought this was a different repo and I've been a bit scarred with my android background audio experience there. But even so it was wrong to go in so hard and not my normal style. And definitely wasn't targeted at you @Guichaguri! Good luck with the implementation.

open pulling

How stable is this branch? Should we try shipping it to users from the commit and monitor?

@kyleclegg  i am unfortunately not able to test this , but you can really test it by doing an A/B Test may be as the sample size will be quite bigger and if anything comes up up we can fix that before making the changes available to everyone. but its totally your choice. But this will helpful for devs & maintainers.

@Guichaguri
We used a rather similar approach to this at the start of our development cycle, however, Android used to be very aggressive with killing the app so we decided to go with your previous implementation. and so far ( after some minor tweaks) we haven't received any crash reports related to this library in months.
If you got any free time, please checkout my fork, it may provide some context to this comment. ( all of our media endpoints are mp3 files on s3, so this has not been tested for any other media types.)

Hi @Guichaguri! For us these changes would mean that we would have to stick to some old version or fork forever, as it seems as there is no way to get tracks to reliably play in background if not using service approach. As you have pointed out, it is a big differential from other music modules and it was actually the main (or even the single) reason, why we started using react-native-track-player in the first place - the other solutions just did could not provide reliable background playback.

Happy to test this.
I already set stopWithApp=true since when the user kills the app, we need to kill audio as it seams the right thing to do...so not too worried about that.

I am getting the following error whey trying to play a track.
com.facebook.react.bridge.ReadableNativeMap cannot be cast to com.facebook.react.bridge.JavaOnlyMap

@Guichaguri Is the notification capabilities still working? As mentioned in the android docs, MediaButtonReceiver needs a service to receive ACTION_MEDIA_BUTTON intents.

@Guichaguri Is the notification capabilities still working? As mentioned in the android docs, MediaButtonReceiver needs a service to receive ACTION_MEDIA_BUTTON intents.

I will close this for now.. at the moment I don't believe the future of this library should be to disable the service.
Overall this is what allows us to build applications that can work in the background and not be killed by the system.. if there's such a need in the future, we'll re-evaluate.


MSC2716 federation changes

MSC2716 federation changes

Unskip the rest of the federation tests
Refactor batchSendHistoricalMessages to be able to compose state and message events
Add test to ensure it is possible to batch send in a private room
Add test to ensure we only pass back state_events that we passed in via ?state_events_at_start, https://github.com/matrix-org/synapse/pull/10552

Dev notes
COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh TestBackfillingHistory

messagesResAsdf := alice.MustDoFunc(t, "GET", []string{"_matrix", "client", "r0", "rooms", roomID, "messages"}, client.WithContentType("application/json"), client.WithQueries(url.Values{
	"dir":   []string{"b"},
	"limit": []string{"100"},
}))
messagesResAsdfBody := client.ParseJSON(t, messagesResAsdf)
eventDebugStringsFromResponseAsdf := getRelevantEventDebugStringsFromMessagesResponse(t, messagesResAsdfBody)
logrus.WithFields(logrus.Fields{
	"eventDebugStringsFromResponseAsdf": eventDebugStringsFromResponseAsdf,
}).Error("see messages")

Todo

[x] Should work with private room where the state_events_before includes invitations and join events
[ ] Redacting an insertion, chunk, marker so remove it from our new tracking tables

https://github.com/matrix-org/synapse/issues/10521
https://github.com/matrix-org/synapse/pull/10538

[ ] Two insertion events with the same next_chunk_id will reject. ((room_id, next_chunk_id) should be unique))

Marked as TODO tests for another iteration

[ ] What happens when two chunks try to point at the same insertion event?

Marked as TODO tests for another iteration

Thanks for the review @kegsay and catching the Python patterns that slipped in 🐆


configurable supervisor log filename

For the storm-on-mesos project there are multiple Storm Supervisors on
every worker host. Each of these Supervisors is dedicated to a
particular topology. A challenge with this design is that the shared
supervisor log file contains logs from every single topology that
has run on a particular host. We instead want the option to have
separate supervisor log files for each topology, so that topology owners
can more easily debug their own problems.
This change allows having configurable log files for every launch of
the Supervisor, since we will be able to embed the topology ID into the
supervisor log filename.
Notably, storm-0.10 already includes a similar change for the worker
log filenames (came in with Yahoo!'s multi-tenant changes).

Seems the 0.9.x-branch isn't set up for travis (above failure is because we don't have a .travis.yml, and no Rakefile).
I'm assuming that this means I shouldn't be doing PRs for commits into the 0.9.x-branch.

Yah, this is not the proper process.  Closing it.


Update zest checkpoint

Update checkpoint

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 9b364a21a12b80439e20f0b93e7996b48e7168ca. Your contribution is still credited to you.


added missing dependencies for illegal transitive dependency check

I am closing this one, because the changes for kie-server modules are already there and kie-camel was moved to different repo.


[ENH] Geometry optimization

Is your feature request related to a problem? Please describe.
I would like to optimize the geometry of a molecule from an initial configuration. This would then allow me to compute vibrational frequencies and IR spectra at a local minimum of the potential energy surface.
Describe the solution you'd like
In PySCF I can use their geometry_optimizer to optimize the geometry of a molecule, for example something like
from pyscf import gto
from pyscf.geomopt.geometric_solver import optimize as geometric_opt

mol = gto.Mole(atom=atom, basis = 'sto-3g') # atom is some initial starting description of the molecule
rhf = scf.RHF(mol)
mol_opt = geometric_opt(rhf)

I would like to do something similar in dqc, for example something like
import dqc

mol = dqc.Mol(moldesc=moldesc, basis="sto-3g") # moldesc is some initial starting description of the molecule
mol.atompos.requires_grad_()
hf = dqc.HF(mol).run()
mol_opt = dqc.optimize_geometry(hf) # new proposed function

Describe alternatives you've considered
Alternatively this would have to be implemented outside of dqc.
Additional context
I know there are many algorithms possible for geometry optimization and I am very open to whichever is recommended.

You can couple it with xitorch (like scipy for pytorch) with a few additional lines as shown here: https://github.com/diffqc/dqc/blob/master/examples/01-equil-pos.py.
I have a slight disfavor on having it specially implemented in dqc as it would be just a very thin wrapper of xitorch.optimize.minimize.

You can couple it with xitorch (like scipy for pytorch) with a few additional lines as shown here: https://github.com/diffqc/dqc/blob/master/examples/01-equil-pos.py.

Ah great - somehow I missed that example, maybe it could be more prominently added to the documentation.

I have a slight disfavor on having it specially implemented in dqc as it would be just a very thin wrapper of xitorch.optimize.minimize.

I can understand that. I have given that example try now and I can confirm that it appears to work for me, though I havn't done any rigorous testing.
Having just given it a try, my personal preference would still be to add it to dqc as a single function call. The main reason is that I have to define my own function get_ene and then handle the passing of the initial atompos and creation of a new molecule with the optimized atompos. All in all I have to touch quite a few different parts of the API, and import a function xitorch.optimize from another library (which I love!) but which a new dqc reader might now be so familiar with.
All of this could be wrapt inside a single mol_opt = dqc.optimize_geometry(hf) call, which would be much more robust and convenient. If you like I can try to implement this and submit a PR, but also fine if you don't want to expand the API or if you'd rather do it yourself.
Thanks again for the prompt and helpful reply.

I think it can be put in the API along side with other properties: https://github.com/diffqc/dqc/blob/master/dqc/api/properties.py
One thing that I don't know yet is: should it returns the tensor of atom position or the molecule object. The other API properties returns tensor(s), so if it returns a molecule object, it would be the odd one out (a very good way to confuse new users). But I can see clunkiness of having to reconstruct the molecule object with a new position (especially if you have a lot of parameters such as efield etc). What do you think?

Hmm - that's a good call out. I could imagine that sometimes people might just want the optimized positions and I can see how it is much more in keeping with the design on the overall API to return a tensor and favor two calls to get the molecule back. I also tend not to like APIs that change return type based on a flag, so I think you have to go with one or the other. Even though it's slightly less convenient for me the following might be fine
mol = dqc.Mol(moldesc=moldesc, basis="sto-3g") # moldesc is some initial starting description of the molecule
mol.atompos.requires_grad_()
hf = dqc.HF(mol).run()
geo_opt = dqc.optimimal_geometry(hf) # new proposed function
mol_opt = dqc.Mol(moldesc=(mol.atomzs, geo_opt), basis=mol.basis) # NOTE: mol.basis doesn't actually exist
# OR
mol.atompos = geo_opt # NOTE: attribute can't be set right now but update in place might be nice

I will call out that mol.basis doesn't exist - but some nice way to get the basis might be convenient.
I will also call out that mol.atompos isn't settable, but with an optimimal_geometry function it could be very nice to just call mol.atompos = dqc.optimimal_geometry(hf). I'm curious what you think about that / if you foresee potential problems?
Finally I suggested the name optimimal_geometry now as what is returned is a "geometry" (i.e. atompos) whereas optimize_geometry to me suggests more on an inplace operation/ operation that returns a full molecule, but maybe that is just me.
Curious what you think next step should be?

Hmm - that's a good call out. I could imagine that sometimes people might just want the optimized positions and I can see how it is much more in keeping with the design on the overall API to return a tensor and favor two calls to get the molecule back.

Returning the tensor also works better if one wants to train a ML system that matches the atom positions to experimental data.

I will also call out that mol.atompos isn't settable, but with an optimimal_geometry function it could be very nice to just call mol.atompos = dqc.optimimal_geometry(hf). I'm curious what you think about that / if you foresee potential problems?

mol.atomposs = something is quite tricky, because it's basically reinitialize everything. It appears simple from the outside, but requires a lot of computation, e.g. basis integrals, in the background. I also avoid to use .build() like in PySCF because it adds some unclarity (e.g. it is unclear for new users if some parameters are assigned, do we need to do .build() or not?)
A solution that I can think of is to add a new method, say Mol.make_copy(**kwargs) where the new parameters are set in kwargs, e.g. for the above example: mol_opt = mol.make_copy(atomposs=geo_opt)

Finally I suggested the name optimimal_geometry now as what is returned is a "geometry" (i.e. atompos) whereas optimize_geometry to me suggests more on an inplace operation/ operation that returns a full molecule, but maybe that is just me.

Is there a special reason why it is optimimal_geometry instead of optimal_geometry?


Fixes issues with random number generation

@adrian-carro This PR will eventually fix issue #51.  So far I have simply created a private instance of a MersenneTwister random number generator in the Model class which I then pass into the constructor of any object in the model that needs a source of randomness.
There are still a few issues in the data/Demographics.java file that I need to address.  But I need to understand what this class is doing before making necessary changes.

Hi @davidrpugh, yes, the Results/*/Output-run1.csv files are the ones to compare. Thanks for solving this! I'll soon review and merge it.

@adrian-carro I fixed the outstanding issues with the data/Demographics.java file.
I looked at the model runs from the code in the master branch and could not find an example of where the output files were different.  I haven't exhaustively looked through the files yet. Can you provide an example of a file where the model runs are generating different output for using the same random seed?
It would be ideal to have an example of the bug that we can convert into a test case...

@davidrpugh I detected the problem on a different branch, ML-calibration, and I added a general issue just to remind myself to check this in the near future. It did surprise me as it shouldn't happen and, indeed, I though I had solved this in the past, as checking this was one of the first things I did when I took over the model. So I am tempted to think this was due to some of the (small) changes I introduced within the ML-calibration branch, where some parameter values stop being read from the config file so as to be introduced via command line. In any case, the changes you introduced make very much sense to me and I am happy to keep them. Regarding the problem within the ML-calibration branch, I can have a look at what's causing the problem at some point next week and commit a solution (I really think it must be related to the command line entering of parameter values).

@adrian-carro OK. Sounds good in which case feel free to merge this PR.


Strikethrough processing is faulty

>>> mistune.Markdown()('~~ABC~~')  # OK
'
ABC
\n'
>>> mistune.Markdown()('~~A~~')  # Not OK
'
~~A~~
\n'
>>> mistune.Markdown()('~~A~~ B ~~C~~')  # Also not OK
'
A~~ B ~~C
\n'
>>>

@vsajip Thanks for your feedback. It should be fixed by https://github.com/lepture/mistune/commit/9c15c0f8d76e9d0fca8b2f41de214e43ee16c732

I'm not sure your change is the ideal fix. For example, you now allow a space between the ~~ and the word, which AFAIK is not as per previous behaviour - and I'm not sure it conforms to other Markdown implementations. I used ~~(?=\S)([\s\S]*?\S)~~, which I think is better - it just makes the inner search non-greedy.

@vsajip a pr is welcome


An option to re-enable toasts

💡 The Idea.
Methane disables toasts without mentioning it anywhere here.
There should be an option to allow toasts to function back properly, as they're pretty useful for:

Custom toasts. (Custom mods showing toasts)
Large advancement data packs with chat notifications disabled. (like this one, chat notifications there can be disabled via settings)
Custom servers removing the text title of advancement via resource packs and using the advancement name as a message content field.
Custom servers abusing compliance requirements feature to show periodical notifications. (don't know if possible now, but deffo was possible a year ago with server resource packs)

🤔 How should it be accomplished?
An option to re-enable the toasts back.
📝 Anything else.
If option to re-enable toasts is not desired, then it'd be nice to mention the removal of toasts on the mod's page.
The way I found it right now is -Dmixin.debug.export=true resulting in this:

Decompiled mixin export (click to open)

I can totally make toast behavior configurable, but the config stuff is starting to get messy. I'll push this with Methane 3.2.0 (3.1.0 is not on modrinth due to a handful of bugs.).

github just closed this issue because i said "should fix #75" :facepalm:, I'll close once this is on modrinth.

now this issue is fixed.


Update Composer dependencies (2020-10-26-00-14)

Visual regression test passed!
View the visual regression test report


Converting a m3u file

Converting a m3u file containing y-dl supported urls to a playlist with metadata.
is this possible with y-dl?
thanks

Not possible.