Window that contains the passed file should have focus on restore

Testing #111420

window.restoreWindow: preserve
Have a couple of windows open, for example vscode-smoketest-express repo and some other
Exit vscode
Open vscode from the command line such that some file from the vscode-smoketest-express repo is passed as command line
The correct VS Code windows are restored, however the one that should be focused and in front should be the one containg the file just passed - thus the vscode-smoketest-express repo. However focus is on the window which had last focus before exiting.

Same if I pass a code-workspace file, that window should be in front and focused

I pushed https://github.com/microsoft/vscode/commit/c44732014de3bfe009d56b4eb7371ef7d2a4987c which will ensure that the window the files are open in get's focus. However, seeing https://github.com/microsoft/vscode/issues/111620 and https://github.com/microsoft/vscode/issues/111605, this may not be the window that is the parent of that file.

@isidorn maybe you could verify this (out of sources is fine too), I am not entirely sure I got your second comment right.

My second comment is: if I pass a code-workspace file to open a brand new workspace that window shuold be focused.
Sure I can verify this, adding label bug so I do not miss this

if I pass a code-workspace file to open a brand new workspace that window shuold be focused.

Hm interesting, while this seems to work for folders, it does not seem to work with workspace files. Is that what you saw? Passing a new folder correctly focusses that new folder even when other windows restore, but not when you pass a workspace file from the command line?

Correct. That is what I saw.

Ok will look into that separately.


Configure/install problem

I use openssl in sources. To install openssl under specific path I run:
./config --prefix=<specific_path>
Problem:
If specified path contains directory lib64, openssl components installed in <specific_path>/lib64
If specified path contains no directory lib64, openssl components installed in <specific_path>/lib
But dependent projects always try obtain openssl components from the same directory (lib). Problem localized in Perl script Configure. Confirmed in versions 1.1.0, 1.1.0f under Ubuntu 14.04.4 LTS
Workaround:
I patch final Makefile:
sed -i.back "s/^\(LIBDIR\|ENGINESDIR\)=\(.*\)lib64\(.*\)/\1=\2lib\3/" Makefile
results looks like:
diff Makefile.back Makefile
53,54c53,54
- LIBDIR=lib64
- ENGINESDIR=<specific_path>/lib64/engines-1.1
---
+ LIBDIR=lib
+ ENGINESDIR=<specific_path>/lib/engines-1.1

There's an easier workaround:
./config --prefix=<specific_path> --libdir=lib


Sometimes unable to change or rest password

In certain scenarios it seems that users cannot reset their password. They get an error stating that they must 'Accept terms and conditions' but there is not checkbox for that.
Also seeing issues where attempting to change the password on the profile page is not saving even though it says 'success' and in other situations it reports the 'Accept terms and conditions' error.
Issue is likely in the routing within the customizations to the users/passwords_controller.rb

Also need to change the edit profile page so that users who have connected via SSO do not need to provide their password to change their email address

Updated to address issues with editing password on the profile page and removed the password section entirely for user's who created their account via SSO

I'm a little confused.  Is this closed or in progress?  Or are those not mutually exclusive?
I am definitely seeing this bug today (26 Apr 2022).


Moving to sound null safety - Because flutter_form_builder 5.0.0-alpha.1 depends on signature ^3.2.1 and no versions of flutter_form_builder match >5.0.0-alpha.1 <6.0.0, flutter_form_builder ^5.0.0-alpha.1 requires signature ^3.2.1.

Hi, i tried to move to sound null safety.

signature: ^4.0.0-nullsafety
image: ^3.0.0-nullsafety.0
image_picker: ^0.7.2
flutter_form_builder: ^5.0.0-alpha.1

This still an issue?

Due to lack of response and an old error, I will close this issue.
If the bug still exists, feel free to open a new issue


OIDC Auth mode

I see lots of documentation in the code, and the command line arguments are documented already :+1: Is updating the documentation (docs/authorization.md) in scope for this PR?
Is there any manual testing you would like me to do? (I know we were talking about testing with Azure Active Directory.)
A PR description would be useful for passers by.

I see lots of documentation in the code, and the command line arguments are documented already  Is updating the documentation (docs/authorization.md) in scope for this PR?

Yes. I had mentioned to Santhosh that we need the docs.
I will address the frontend changes.

I have updated the frontend part for including the redux changes.
@ashu8912 when you got some bandwidth (can be in another PR), please make the theme related changes so the tests run with static class names as René mentioned.
We should make the theme provider affect the whole app and not just the header, BTW.

Thanks to everyone involved!
I have rebased and will merge now. Cheers!


Redesign hospital/clinic selection

Currently, persons go to the nearest medical facility when either visiting or being hospitalised. Sometimes these facilities are rather small, creating asymmetric effects.
My aim is to implement the following:

When at home: random chance to visit medical facility irrespective of type (some will visit hospitals, some clinics).
When hospitalised: exclude non-hospital medical facilities from selection.

Imran, what to do you think of this approach?

I agree with both points. For the first point: will it be based on nearest facility or simply the random selection?

First attempt at implementation here: b524400a3b8b0f821d50e0bc5f8b4bdb9d5a0147

Seems to work as intended.


megrate to flutter 2 -> null safety

Just opened a PR for that. https://github.com/Jim-Eckerlein/dart-angles/pull/3

Closed by #3


Unable to install Umap-learn

python3.9
windows 10
When I run the command:
pip3 install umap-learn
I get the following error:
Failed to build llvmlite
Installing collected packages: llvmlite, numba, umap-learn
Running setup.py install for llvmlite ... error
FileNotFoundError: [WinError 2] The system cannot find the file specified
error: command 'c:\scratch\python39\python.exe' failed with exit code 1
does anyone know how to overcome this?

Especially for windows I'd recommend using conda and installing umap-learn
from conda-forge.  In my somewhat limited experience with windows I've
historically had more luck using conda than pip.
Try something like:
conda install -c conda-forge umap-learn.
On Thu, Dec 10, 2020 at 8:19 PM nolzie<EMAIL_ADDRESS>wrote:

python3.9
windows 10
When I run the command:
pip3 install umap-learn
I get the following error:
Failed to build llvmlite Installing collected packages: llvmlite, numba,
umap-learn Running setup.py install for llvmlite ... error
FileNotFoundError: [WinError 2] The system cannot find the file specified
error: command 'c:\scratch\python39\python.exe' failed with exit code 1
does anyone know how to overcome this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lmcinnes/umap/issues/532, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3IUWQCZHU762OLB5IZJH3SUFXQ3ANCNFSM4UV3LQHQ
.

Python 3.9 is not currently supported -- since we make heavy use of numba which doesn't currently have a release that supports python 3.9

Python 3.9 is not currently supported -- since we make heavy use of numba which doesn't currently have a release that supports python 3.9

Hi,
As a big fan of UMAP, I am wondering if there are any (good) news about the possibility to use UMAP with Python3.9?
Tnaks

Version 0.53 of numba will provide python 3.9 support. Currently they are on the third release candidate of that version, so I would hope they will have a full release in the next month or so. You can always install the release candidate version ahead of time.

Whats the current status on this issue, Numba has been updated to version 0.53.1

I believe it should now work with python3.9 provided you have the recent enough numba version.

I can confirm this works now with dependencies installed with conda, and subsequent pip3 install umap-learn (conda would still complain about python=3.9).


instancetype: Rename mock_flavor to mock_instancetype

What this PR does / why we need it:
/area instancetype
This was missed during 4eb29b83bc52bfd25bd46922af8a8269f2b21913.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/retest

/retest

/lgtm


dm-lwm2m: ZmP v38 changes

Correct OpenThread / 802.15.4 check in Kconfig
Add OpenThread overlay
Enable GPIO explicitly now as some boards have had many defaults removed

Addressed comments (thanks!)


get null safety to work

Hi, I am trying to get null safety working in my Flutter project. Just not able to get it working.
I have tried with Dev/beta channel. It does not work. I always keep getting following error:
This requires the 'non-nullable' language feature to be enabled.
I tried adding analysis.options.yaml file as well in the root folder of the project. It does not work.
Appreciate any help for how to get null safety working in Flutter.
Thanks,
Srinivas

null-safety is not released yet


Add timeout to playpen requests

This adds a timeout of 2 seconds to all playpen requests. If playpen doesn't respond, assume it to be down.
Error message could be better phrased, maybe.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Right now the timeout on the playpen itself is 5 seconds, perhaps this could be bumped to maybe 6-8 seconds?

Fixed. Upped it to 6.


storagecluster: Update uninstall error as an events

Signed-off-by: Nitin Goyal<EMAIL_ADDRESS>

@raghavendra-talur This is the shortest way with minimum lines of change I can think of to update the last status of uninstall events. Let me know your thoughts on this.

Depends on https://github.com/openshift/ocs-operator/pull/1060. Pls do not merge this one before #1060

/cherrypick release-4.7


Registering/resolving with argument for protocol/concrete value

I have a class, let's call it SomeClass. It has an initializer that takes in a view controller; except I have added an arbitrary protocol that my view controllers implement to abstract things away so I can test SomeClass. So the initializer looks like:
init(viewController: ViewControllerType)
All my viewcontrollers implement ViewControllerType.
I want to register SomeClass with Swinject and then pass the view controller into it as an argument, so I did:
container.register(SomeClass.self) {
  r, viewController in
  return SomeClass(viewController: viewController)
}

Only, Swinject has taken the ViewControllerType and doesn't see that having been registered. It only sees concrete view controllers being registered I guess?
What I can do to fix this?

Hi @gbrhaz,
please add the code where you are resolving SomeClass - It is hard to tell what exactly is the problem only from register method.
Thanks 😉

Sure:
container.register(ConcreteViewController.self) {
  resolver, controller in

  return Controller(someClass: r.resolve(SomeClass.self, argument: controller)!
}

Seems to be inferring it just fine.

@jakubvano Could you please help me understand my situation: I am not using storyboards and just trying to register some Service with argument. But resolve with argument always return nil.
This is a bug or I am just doing something wrong?
My code below:
var model: Hero?
container.register(ProtocolOne.self) { (r, hero: Hero) in
    model = hero
    let vc = ViewController(withHero: hero)
    let helper = r.resolve(ProtocolTwo.self)!
    vc.helper = helper
    return vc
}
container.register(ProtocolTwo.self) { _ in
    Helper()
}
.initCompleted { (r, two) in
    let helper = two as? Helper
    helper!.controller = r.resolve(ProtocolOne.self, argument: model) // always nil
}

@gbrhaz Sorry, I mistook registerForStoryboard for register method - A it stands, you need to explicitly upcast controller (for more info see docs):
controller.someClass = r.resolve(SomeClass.self, argument: controller as ViewControllerType)!

@siggb r.resolve(ProtocolOne.self, argument: model) is passing argument of type Hero?, while your register methods expecs argument of type Hero. One way to solve this would be
r.resolve(ProtocolOne.self, argument: model!)

@jakubvano That fixed it. Thanks, I did see something with the registration key, it just didn't click :)

Glad to help 😄 v1.1.5 will include logging of resolution failure (#168)  which should help with debugging issues like these.


feat: added optional title prop

Closes #52
Users can also provide a full title which can be passed as prop else the default title with emoji will be rendered
Checklist:

[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

Superseded by #56


Widen the visibility of SpaceSaver.SSMany, SpaceSaver.SSOne

I need to serialize efficiently an instance of SpaceSaver.
For that, I need to access the inner fields capacity & counters, and the constructors of SSMany and SSOne.
The issue is both the classes & the constructors are private.
Would it be possible to have them as public?
I'm willing to do the PR for this.

Can we instead have a direct serialization method like HyperLogLog does?
Exposing inner classes like that makes binary and source compatibility harder.

It could be an option.
But the issue I see is that the counter in SpaceSaver is parametrize with T. So how can we encode those objects? Using the default Java serialization is not a good option IMHO.

you can pass something like an injection: T => Array[Byte], Array[Byte] => Try[T] and we call as needed.

Thanks for handling this!


NULL values from csv tables aren't recognized as NULL but 'NULL' strings

When reading flat files, NULL values are interpreted as strings instead of NULL. This throws a wrench when trying to export results or just copy-n-pasting from a resultset. Please, recognize ,NULL, as a NULL value for such column/row tuple.

In csv files every value between commas is a string, so you can only use empty string (,,) to represent null value.

Sadly that's not what happens:
ColA,ColB,ColC
NULL,2,
3,,NULL
,NULL,1

Null values should appear as grey [Null] values.

If I try to export the results, it converts everything to strings.

Well, by default all string literals in CSV are not null.
Generally this seems to be a duplicate of #1030

@serge-rider Then how do we get NULL values? Because neither literal NULL nor empty strings seems to be recognized as NULL. And from what I gathered, neither \N would. Is there no way that a value would be recognized as NULL?


docs: Automated Changelog Update for v5.0.0-beta5.36

copilot:all
Automated changes by create-pull-request GitHub action

🤖 Generated by lychee action
Summary

Status
Count

🔍 Total
1273

✅ Successful
368

⏳ Timeouts
0

🔀 Redirected
0

👻 Excluded
903

❓ Unknown
0

🚫 Errors
1

Errors per input
Errors in docs/4.0/docs/self-hosting/lifecycle-management/quick-start/deploy-kubernetes.md

[406] https://hub.docker.com/u/labring | Failed: Network error: Not Acceptable

Full action output
Full Github Actions output


feat(border): focus styles mechanism

feat(border): focus styles mechanism
BREAKING CHANGES MIGRATION STEPS
The following component variables have been removed from:

Attachment:
focusInnerBorderColor, focusOuterBorderColor

Button:
circularRadius, colorActive, borderColorActive, borderColorFocus, borderColorFocusIndicator, borderColorDisabled, borderWidth, primaryColorActive, primaryBorderColorActive, primaryBorderColorHover, primaryBorderColorFocus, primaryBorderColorFocusIndicator, primaryBorderWidth, primaryCircularBorderColorFocusIndicator , circularBorderColorActive, circularBorderColorFocusIndicator, borderRadiusFocused

RadioGroupItem:
focusInnerBorderColor, focusOuterBorderColor

These variables are deprecated and should not be used.

For the variables related to borders, Teams now have a unified way of displaying it that is consistent with the whole Teams theme => border styles should be unified, no custom border appearances.

For the other variables, they were either used in dead style objects or they do not match redline requirements => NO IMPACT

Description
This PR covers:

implementation of utility function that will be used for styling components on focus state (from keyboard): getBorderFocusStyles from getBorderFocusStyles.ts

integration of getBorderFocusStyles for border focus styles for following components:

Button
Attachment
RadioGroupItem

Screenshots for Button:
Regular Theme

Dark Theme

High Contrast Theme

We will adopt this mechanism for all other components in separate PR.

simplifying component variables and writing styles for border by:

moving generic border variables from component variables to siteVariables.ts
leveraging getBorderFocusStyles and generic border styles from siteVariables.ts

fix for Button outline styles overlapping issue in Grid:

BEFORE

AFTER

The focus border as originally implemented appears around the item, but in this PR it looks like it is within the item. Has the design changed to be more easily implemented?
Before:

After:

This is pretty subtle in normal themes, but in contrast the "focus border" was much thicker and would look distinctly different if drawn "inside" the button.

@bcalvery these changes are all part of the new design indeed

I had to squash my commits into one in order to be able to merge more easily the big amount of changes that got to master recently via #1069


[FLINK-29636] Add micro benchmarks module

In this PR, we add micro benchmarks module in flink table store. The module contains sets of micro benchmarks designed to run on a single machine to help flink table store developers assess performance implications of their changes. We add two benchmarks in this PR

Merge tree reader benchmark
To performance the scan operation in MergeTreeReader, we first write 50*50000 records by MergeTreeWriter and scan all the data by MergeTreeReader, then we collect the latency of each scan.
Merge tree writer benchmark
To performance the write operation in MergeTreeWriter, we statistics throughput of MergeTreeWriter.write with compaction.

We rename flink-table-store-benchmark to flink-table-store-cluster-benchmark and add new module named flink-table-store-micro-benchmarks

Hi @JingsongLi  I create flink-table-store-micro-benchmarks in flink-table-store and add MergeTreeReaderBenchmark and MergeTreeWriterBenchmark, can you help to review when you're free, thanks

👍🏻 I will take a look~

Can you create a separate PR for module refactor?
Then this pr is just to introduce micro benchmark.

Can you create a separate PR for module refactor? Then this pr is just to introduce micro benchmark.

Look good to me 👍


Vertical Carousel

Is it possible to make Vertical Carousel?

https://github.com/angular-ui/bootstrap#need-help


Reduce Hoxy dependencies (and do some updating)

Hoxy takes 17M as a dependency, which is pretty big. It looks like some dependencies aren't needed for my project, and other dependencies just stright-up aren't needed by hoxy! :wink:
Tests aren't running for me, and I bet that it's because I'm running Node 6. Hopefully I can reduce dependencies and keep tests passing.
  Load data as type
    ✓ should load request bodies (send)
    1) should load response bodies

  1 passing (94ms)
  1 failing

  1) Load data as type should load response bodies:
     Error: Parse Error
      at Error (native)
      at Socket.socketOnData (_http_client.js:359:20)
      at readableAddChunk (_stream_readable.js:172:18)
      at Socket.Readable.push (_stream_readable.js:130:10)
      at TCP.onread (net.js:542:20)

Change a single character so that I can make a PR, and travis will run

Derp, no travis

I figured out why the tests were failing, and I don't think that it is due to my Node version. Testing on 5.11 still failed should load response bodies.
It turns out that to in send.js is mad?  Maybe "head" is being written in two different places? Either way, out-of-scope for this PR. context
I'm not sure how to solve this problem, and the await/co()/promise shenanigans are a little too deep for me to wade in right now. On the bright side, I can remove a bunch of deps and manually test to see if the proxy still works

Just tested with James, still looks good, and we hit quite a few use-cases

This might be a little tricky to merge, and I'm not sure it's valuable anymore smile


Add syncset types.

SyncSet crd.

/test unit

@abutcher I would remove the unit test. Other than that, it looks great.

Also, rebase and make sure you run make crd to ensure the generated CRD is updated.

/lgtm


Install seemingly kills pi on install

at the same place every time the install kills the RPi 4....

pulling manually causes the same issue... tested other dockers, they work fine.

Hmm. It dies during this (the download) phase? That’s really, really odd. There is nothing fermentrack-specific that is taking place during that step.
It sounds cliche, but have you tried a different SD card?

64bit rpi install causes this


CM-175:Blazor WebAssembly Ahead of Time Compilation (AoT)

retest this please

retest this please

Retest this please

retest this please

retest this please

retest this please

retest this please

@asif-anwar - the build is failing as there is a workload that needs to be installed in the CI build. I have reached out to the CodeMaze support to get that issue addressed. Sorry for the trouble.


Make this Awesome!

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] Easter egg report (?)

Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
- [x] make-this-awesome

Versions
node --version
v10.14.1

npm --version
6.4.1

ng --version
Angular CLI: 7.1.3
Node: 10.14.1
OS: win32 x64
Angular: 7.1.3
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.11.3
@angular-devkit/build-angular     0.11.3
@angular-devkit/build-optimizer   0.11.3
@angular-devkit/build-webpack     0.11.3
@angular-devkit/core              7.1.3
@angular-devkit/schematics        7.1.3
@angular/cdk                      7.1.1
@angular/material                 7.1.1
@ngtools/webpack                  7.1.3
@schematics/angular               7.1.3
@schematics/update                0.11.3
rxjs                              6.3.3
typescript                        3.1.6
webpack                           4.23.1

Windows version:
Windows 10 64bit

Repro steps
Run the following command:
ng make-this-awesome

The log given by the failure
Let's take a look... nope, it's all good!

Desired functionality
I'd like to know what it does, when not everything is good.

I'd like to know what it does, when not everything is good.

Little digging...
https://github.com/angular/angular-cli/blob/master/packages/angular/cli/commands/easter-egg-impl.ts


added cob4-3

We should not forget to add the new scan_unifier introduced in https://github.com/ipa320/cob_robots/pull/364


Replace Gitter reference and add badge

I didn't realize we already had a badge on the https://github.com/ElanHasson/orleans/edit/main/README.md page.

I made one for this PR:

Which one did ya'll want to use? the traditional badge (in the second screenshot above) or the purple one from the code repo root README (first image)?
Happy to change either. Just let me know and I'll send PR for the purple one.
Also can synchronize the badges to include gitter (or remove), just let me know.

Docs Build status updates of commit 0df5038:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

src/blog/orleans-1.4-and-2.0-tech-preview-2-for-.net-core-released.md
:white_check_mark:Succeeded

src/blog/orleans-2.0-tech-preview-supporting-.net-core.md
:white_check_mark:Succeeded

src/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Port remaining sql integration tests from rust to sqllogictest

Is your feature request related to a problem or challenge?
As described in https://github.com/apache/arrow-datafusion/tree/main/datafusion/core/tests/sqllogictests DataFusion has many tests that use the sqllogictest framework which is easy to write and update compared to rust tests
We still have a non trivial number of old tests that are written in Rust and run in the sql integration test:
https://arrow.apache.org/datafusion/contributor-guide/index.html#rust-integration-tests
cargo test -p datafusion --test sql_integration

This ticket tracks the work to port the tests from rust to sqllogictests
Describe the solution you'd like
Port tests from datafusion/core/tests/sql to sqllogictests in datafusion/core/tests/sqllogictests/test_files
For each test, the goal is to:

Port as many tests as possiible (follow the example of https://github.com/apache/arrow-datafusion/pull/6158 or one of the other tests linked to https://github.com/apache/arrow-datafusion/issues/4495)

Then we can figure out what to do with the tests that can not be ported easily
Remaining items:

[x] https://github.com/apache/arrow-datafusion/issues/6208
[x] https://github.com/apache/arrow-datafusion/issues/6216
[x] https://github.com/apache/arrow-datafusion/issues/6210
[x] https://github.com/apache/arrow-datafusion/issues/6211
[x] https://github.com/apache/arrow-datafusion/issues/6212
[x] https://github.com/apache/arrow-datafusion/issues/6213
[x] https://github.com/apache/arrow-datafusion/issues/6214
[x] https://github.com/apache/arrow-datafusion/issues/6215
[x] #6233
[x] #6299
[x] #6298
[x] #6297
[x] #6300
[ ] #6301
[ ] #6302
[x] #6303

Describe alternatives you've considered
No response
Additional context
Follow on to https://github.com/apache/arrow-datafusion/issues/4495
Marking this as a good first issue as there are many examples and it will get people familiar with how to run tests and how to use datafusion as a library, while also helping the community

i'm start working on Port tests in joins.rs to sqllogictest #6302

Thank you to everyone who helped get this done!


Convert doc.rust-lang.org to intra-doc links

Similar to #17. I'd like these links:
tracing/src/lib.rs://! [fmt]: https://doc.rust-lang.org/std/fmt/#usage
tracing/src/lib.rs://! [`libstd`]: https://doc.rust-lang.org/std/index.html
tracing/src/lib.rs://! [`liballoc`]: https://doc.rust-lang.org/alloc/index.html

to be turned  into these:
tracing/src/lib.rs://! [fmt]: std::fmt#usage
tracing/src/lib.rs://! [`libstd`]: std
tracing/src/lib.rs://! [`liballoc`]: alloc

In an ideal world:

/nightly, /beta, and /stable would be stripped (e.g. https://doc.rust-lang.org/nightly/std/primitive.str.html)
leading paths that aren't crates would be ignored (e.g. https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/enum.TyKind.html or https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html#the-stack-and-the-heap)

leading paths that aren't crates would be ignored (e.g. https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/enum.TyKind.html ...

What isn't a valid crate here ? I can certainly extract rustc_hir::TyKind.

Hmm, I was thinking of this in the context of user programs, but I guess if you're linking to nightly-rustc it's likely you're already in the compiler source tree somewhere. So it would then make sense to convert this.

Do you know if there is a list of the possible urls for docs coming from https://doc.rust-lang.org/ somewhere (The leading parts, like nightly|stable|... and std|alloc|nightly-rustc|... ?

I don't know of an authoritative list, but the prefixes are nightly|stable|beta|1.xx.x and the crates are std|alloc|core|proc_macro|test. I think nightly-rustc is the only special case, you can treat any directory after that as a crate.

Should be fixed now. I'll publish a new version of intraconv when #18 and #21 are closed


Tinylog Writing-Thread

Hey,
is it possible to use the Writing-Thread with the option to let the Thread end when no new logs are incoming, so when the Application crash the last Logs get written to the file ?

If the JVM crashes, you will no longer be able to run any Java code. If your application only crashes due to an uncaught exception, the Writing-Thread should output all your log entries. Do you have a concrete example of losing log entries?


error: no such option: --no-parallel

I get this error every time I run node-gyp. Any ideas on how to fix it?
I'm in version v3.0.3 which seems to be the latest
{ [Error: Command failed: /bin/sh -c /home/maraoz/git/bitcorps/node_modules/nodegit/node_modules/.bin/node-gyp rebuild
Usage: gyp_main.py [options ...] [build_file ...]
gyp_main.py: error: no such option: --no-parallel
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 2
gyp ERR! stack     at ChildProcess.onCpExit (/home/maraoz/git/bitcorps/node_modules/nodegit/node_modules/node-gyp/lib/configure.js:355:16)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.16.0-51-generic
gyp ERR! command "/usr/local/bin/node" "/home/maraoz/git/bitcorps/node_modules/nodegit/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /home/maraoz/git/bitcorps/node_modules/nodegit
gyp ERR! node -v v5.0.0
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok

btw, I found a way around it, which is commenting this line: https://github.com/nodejs/node-gyp/blob/master/lib/configure.js#L326
But I wanted to notify you so you can fix it correctly :)

That error probably means node-gyp is picking up and old gyp version.  I've had similar reports from people that had gyp installed through their distro's package manager.

gyp_main.py: error: no such option: --no-parallel is something that seems to come back and bug everyone. Is there a real solution to this? Is there a way to determine which node-gyp is causing the problem? (one installed from OS package, or from local npm, or other?)


Have run configurations and tests use Gradle

Is your feature request related to a problem? Please describe.
I have a project that uses Gradle. The only way to successfully compile and run it is through Gradle. It would be better if the run configurations and tests would leverage Gradle. As it stands, I do not see a way to run individual tests when your project depends on Gradle other than via the command line.
The current alternative is to use the Gradle extension's task UI. You can choose to run or debug a task, or run it with command line args. This is fine for running pre-made tasks, but clumsy for running tests, and the task UI provides no customization options you can reuse. It also is not intuitive to anyone who is not familiar with Gradle or java projects, and are expecting the project to work like it would in any other language, since it requires ignoring the existing run and test features.
Describe the solution you'd like
We can create Gradle run configurations and also define test behavior. Note, also, different test directories in the same project may have different Gradle tasks. It's also worth calling out that Gradle supports watching file changes, which may be a useful mechanism for automatically running tests.
Describe alternatives you've considered
None.
Other info
The project defines class paths and does not appear to be misconfigured in any obvious way.

I'm also working in a project environment where the applications only successfully launch when executed with Gradle. (though compilation is successful either way)
In my case his is most certainly caused by some missing configuration that is done in the warp/init script deployed with the custom wrapper distribution that is used for the projects.
This is not a problem for IntelliJ IDEA because there it is actually the default behavior to run and test using the build tool in Gradle projects (not changeable in the community edition).
When setting IDEA to run using the IDE, the application produces the exact same error on launch as with VS Code.
Therefore I guess the solution would be to add a new setting to delegate build/run actions to Gradle which should also help with mixed source (Java/Groovy/Kotlin) projects.

To clarify, is this to support a gradle launch configuration in launch.json?

@Spitfire1900 I won't speak for the rest, but I would assume so. It would be helpful to have a launch type for gradle so one could, say, launch and kill a gradle run, perhaps also attaching a debugger. In my case I am running bnd and an OSGi service. I end up having to setup a preLaunchTask to run gradle then attach a debugger to that for instance. Not sure what this would entail.

@Spitfire1900 I won't speak for the rest, but I would assume so. It would be helpful to have a launch type for gradle so one could, say, launch and kill a gradle run, perhaps also attaching a debugger. In my case I am running bnd and an OSGi service. I end up having to setup a preLaunchTask to run gradle then attach a debugger to that for instance. Not sure what this would entail.

We support test delegation now. See https://github.com/microsoft/vscode-java-test/issues/1045#issuecomment-2268091927.
Please let me know if you this meet your requirements.

That's actually not exactly what I needed, but that is good to know!
In my case I run a web server through OSGi. Specifically I am using Bnd. It is often helpful when running that web server to set breakpoints to debug the launch of my application.
I would say that of the title of the issue "Have run configurations and tests use Gradle" the latter has been absolutely completed, but the former may not be complete, if that's what the original author meant be "run configurations".

Oh, I do see that I can use a preLaunchTask such as "gradle: project:run.bndrunfile" which probably sufficiently suits my purposes, though an launch configuration type certainly would be good I think anyways.
Thanks @jdneo !


fix(WEM-1816): added identifier column printformer product grid inste…

…ad of master id

@AlexanderTurchin please pr to release branch directly and we test there


added discord connector

Branching
Always branch off from the develop branch with a descriptive name that encapsulates your idea or fix. This practice helps ensure that our main branch remains stable.

Description

Added the discord connector
Related Issue(s)

#689
Testing and Validation

Tested this only on local system as the discord connector doesn't seem show up in the admin dashboard when using docker. Would require a test from others and verify.
Screenshots (if appropriate):

Documentation

Changes Include

[ ] Bugfix (non-breaking change that solves an issue)
[x] New Feature / Enhancement (non-breaking change that add or improves functionality)
[ ] New Feature (breaking change that is not backwards compatible and/or alters current functionality)
[ ] Documentation (change to product documentation or Readme.md only)

PR Checklist

[x] This PR targets the develop branch of the swirl-search repo.
[x] The above portion of this template is filled out completely.
[] This PR has been tested for correct functionality and validated not to break existing product code.

Hi, I've added a connector for Qdrant as mentioned in the issue #721 .

@SubramanyamChalla24 please make one final change:

Put the SearchProviders in SearchProviders/untested
Put the Connectors in swirl/connectors/untested

Omit changes to init.py for now. Thank you! I will merge immediately once these changes are made.

what is the status now, qdrant and discord? pending over a month now


Add PerfMsTracker

ci: merge workflows
feat: add perftracker

Fixes #32

Codecov Report

Merging #33 (ff7b993) into main (9bc9097) will decrease coverage by 0.73%.
The diff coverage is 91.66%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
- Coverage   95.61%   94.89%   -0.73%
==========================================
  Files           2        3       +1
  Lines         114      137      +23
==========================================
+ Hits          109      130      +21
- Misses          5        7       +2

Impacted Files
Coverage Δ

flask_matomo2/trackers.py
90.47% <90.47%> (ø)

flask_matomo2/__init__.py
100.00% <100.00%> (ø)

flask_matomo2/core.py
95.57% <100.00%> (+0.03%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix editing non-primitive fieldDef in preview panel issue

Ticket: CS-6243
Problem
Editing non-primitive FieldDef instances in the preview panel posed a challenge. Updates to these fields weren't reflected in the card editor, and auto-save wasn't triggered.
Solution
The issue stemmed from the component only subscribing to changes in the card instance. Consequently, updates to the field instance didn't notify the component. To address this, I've enhanced subscribeToChanges and unSubscribeToChanges to also subscribe to field instances of a card.
Before
https://github.com/cardstack/boxel/assets/12637010/911beb6e-ff84-4153-807c-d224671f9591
After
https://github.com/cardstack/boxel/assets/12637010/c14961dd-eec7-4825-b306-f916836a3fd9

@jurgenwerk @habdelra subscribeToChanges and unSubscribeToChange had been recursively through all fields values because these lines https://github.com/cardstack/boxel/pull/832/files#diff-abdbf2e4d24040dd1eea3fc9a720d36711a16847f57b97f8bb7522faccbe11e9R1905 and https://github.com/cardstack/boxel/pull/832/files#diff-abdbf2e4d24040dd1eea3fc9a720d36711a16847f57b97f8bb7522faccbe11e9R1927. However I didn't do the same on _updateFromSerialized so I made this changes c7e996e.

it just ocurred to me--let's update the notifySubscribers() in card-api.gts to also send the card instance to the subscriber callbacks. Right now we are only sending the field name and the field value in the callback because we are assuming that the subscriber knows the instance changing--but actually the instance changing might be an interior field value, so let's pass the
instance in the callback too.
so change:
function notifySubscribers(card: BaseDef, fieldName: string, value: any) {
  let changeSubscribers = subscribers.get(card);
  if (changeSubscribers) {
    for (let subscriber of changeSubscribers) {
      subscriber(fieldName, value);
    }
  }
}

to:
function notifySubscribers(card: BaseDef, fieldName: string, value: any) {
  let changeSubscribers = subscribers.get(card);
  if (changeSubscribers) {
    for (let subscriber of changeSubscribers) {
      subscriber(instance, fieldName, value);
    }
  }
}


[Design] Patient care plan

Figure out what happens after the patient gets the recommendation to get their blood pressure checked, what else goes into the care plan screens?

closing, this is a duplicate


Fix invalid JSON sample

Remove a comma that made the JSON invalid.

Current coverage is 79.16%

Merging #1672 into master will not affect coverage as of 388ef2b

@@            master   #1672   diff @@
======================================
  Files          539     539
  Stmts        31799   31799
  Branches      8928    8928
  Methods
======================================
- Hit          25175   25173     -2
- Partial       5178    5180     +2
  Missed        1446    1446

Review entire Coverage Diff as of 388ef2b

Powered by Codecov. Updated on successful CI builds.

:+1:


setup.py develop

I created my env with conda, py3.6.
When I run "python setup.py develop", after all the requirements are satisfied, this happens:
running develop
running egg_info
creating deeppavlov.egg-info
error: could not create 'deeppavlov.egg-info': Permission denied
how can i solve this problem?

I didn't git in my env. I clone DeepPavlov before i create the env. Is that the reason?

Can you provide the whole output? Somewhere in the message there should be more on what permissions are missing.

I run 'python setup.py develop', and there are many raw begin with 'requirement already satisfied....'
then I get this four output and below them there is another<EMAIL_ADDRESS>I delete the DeepPavlov and git clone it again in my env. And run 'python setup.py develop' successfully. There is no problem right now. THX.


Upgrade to Java8

Fixes #1053
This commit upgrades the AppEngine instance from Java7 to Java8
Taken from Java 8 Runtime Enviroment:
Note that existing App Engine applications currently using the Java 7 runtime will run in the Java 8 runtime simply by making that change.

In Makeroid, we have been using this sources under Java8 and there weren't any compatibility problems

Same here, we've been also using Java 8 for a while and all okay


Anno app fails on missing org name

If a genome annotation app is submitted without a scientific name (possible at the API level) we get a failure in the MLST code. Need to check early on.
Use of uninitialized value $cmd[6] in join or string at /disks/p3/deployment/lib/Bio/KBase/GenomeAnnotation/Service.pm line 820.
Error invoking method annotate_strain_type_MLST: undef passed at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 1266.
IPC::Run::_exec("/disks/p3/deployment/bin/assign_st_to_genome", "-s", 1, "-m", "/disks/patric-common/data/mlstdb-2015-1123", "--org", undef) called at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 2655
eval {...} called at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 2534
IPC::Run::_do_kid_and_exit(IPC::Run=HASH(0x9e7da88), HASH(0x9d99898)) called at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 1375
IPC::Run::_spawn(IPC::Run=HASH(0x9e7da88), HASH(0x9d99898)) called at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 2807
eval {...} called at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 2804
IPC::Run::start(ARRAY(0x90e9ef8), "<", "/disks/tmp/RHczNDArqV", ">", File::Temp=GLOB(0x9df5110), "2>", SCALAR(0x32d35c8)) called at /disks/patric-common/runtime/lib/perl5/site_perl/5.20.2/IPC/Run.pm line 1448
IPC::Run::run(ARRAY(0x90e9ef8), "<", "/disks/tmp/RHczNDArqV", ">", File::Temp=GLOB(0x9df5110), "2>", SCALAR(0x32d35c8)) called at /disks/p3/deployment/lib/Bio/KBase/GenomeAnnotation/GenomeAnnotationImpl.pm line 17543
Bio::KBase::GenomeAnnotation::GenomeAnnotationImpl::annotate_strain_type_MLST(Bio::KBase::GenomeAnnotation::GenomeAnnotationImpl=HASH(0x98b17d8), GenomeTypeObject=HASH(0x9a38090)) called at /disks/p3/deployment/lib/Bio/KBase/GenomeAnnotation/GenomeAnnotationImpl.pm line 22412
eval {...} called at /disks/p3/deployment/lib/Bio/KBase/GenomeAnnotation/GenomeAnnotationImpl.pm line 22411
Bio::KBase::GenomeAnnotation::GenomeAnnotationImpl::run_pipeline(Bio::KBase::GenomeAnnotation::GenomeAnnotationImpl=HASH(0x98b17d8), HASH(0x98e1cf0), HASH(0x9918980)) called at /disks/p3/deployment/lib/Bio/KBase/AppService/GenomeAnnotationCore.pm line 127
Bio::KBase::AppService::GenomeAnnotationCore::run_pipeline(Bio::KBase::AppService::GenomeAnnotationCore=HASH(0x93439c8), HASH(0x98e1cf0)) called at /disks/p3/deployment/plbin/App-GenomeAnnotation.pl line 122
main::process_genome(Bio::KBase::AppService::AppScript=HASH(0x10733a8), HASH(0x10738a0), HASH(0x1073888), HASH(0x2520488)) called at /disks/p3/deployment/lib/Bio/KBase/AppService/AppScript.pm line 242
Bio::KBase::AppService::AppScript::subproc_run(Bio::KBase::AppService::AppScript=HASH(0x10733a8), ARRAY(0x1073858)) called at /disks/p3/deployment/lib/Bio/KBase/AppService/AppScript.pm line 94
Bio::KBase::AppService::AppScript::run(Bio::KBase::AppService::AppScript=HASH(0x10733a8), ARRAY(0x1073858)) called at /disks/p3/deployment/plbin/App-GenomeAnnotation.pl line 23
at /disks/p3/deployment/lib/Bio/KBase/GenomeAnnotation/GenomeAnnotationImpl.pm line 17543.

Bob, Is this fixed already?

Hm. Unclear; I don't recall how this got triggered and if it is actually possible from the PATRIC site to submit without specifying a name.

In any event, I just pushed a fix for the pipeline to make attempts to run the pipeline with a missing scientific name not fail out in MLST.

Looks like this is fixed.


Enhance compatibility

Adding the path to 'data' folder, this is especailly useful for Mac OSX.
Then we can put the 'data' folder into 'MacOS' folder within 'labelImg.app'.

😎


Expo 49 installation issue

Environment

MacOS 13.5.2
Apple M2 Pro

Steps to reproduce

On a managed expo project:
Install @rnmapbox/maps
Add the @rnmapbox/maps plugin to app.config.ts:

  plugins: [
    [
      "expo-location",
      {
        locationAlwaysAndWhenInUsePermission: "This is so we can show you cool places near you!",
        isIosBackgroundLocationEnabled: true,
        isAndroidBackgroundLocationEnabled: true,
      },
    ],
    [
      "@rnmapbox/maps",
      {
        RNMapboxMapsImpl: "mapbox-gl",
        RNMapboxMapsVersion: "11.0.0",
        RNMapboxMapsDownloadToken: "<token>",
      },
    ],
  ]

run npx expo prebuild to generate new pods

Get error:

Command `pod install` failed.
└─ Cause: CocoaPods could not find compatible versions for pod "Mapbox-iOS-SDK":
  In Podfile:
    rnmapbox-maps (from `../../../node_modules/@rnmapbox/maps`) was resolved to 10.0.15, which depends on
      Mapbox-iOS-SDK (= 11.0.0)

None of your spec sources contain a spec satisfying the dependency: `Mapbox-iOS-SDK (= 11.0.0)`.

You have either:
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

pod exited with non-zero code: 31

The solution I found while browsing this was to run pod update MapboxMaps, but that isn't very helpful on an expo project 😅

No code example found in issue body - More info

Is there anything else I was supposed to provide?

Note that I did not need to specify a version. The token does need to be correct though, otherwise for some reason it cannot download the pod.
[
      "@rnmapbox/maps",
      {
        RNMapboxMapsImpl: "mapbox",
        RNMapboxMapsDownloadToken: "sk...w"
      }
    ]


Add ol tag to dt-article css rules

Ordered list wasn't following the article rules, which lead to alignment issues.
Closes #34.
Closes https://github.com/jppgks/distill-karpathy-nn/issues/4.

@shancarter @colah yarn build changed more than should have been changed (see 397bc72).
Maybe a kind of check in a CI tool of our choice can prevent such changes from not being included in a commit that modified source files (something along the lines of [ -z "$(git diff dist/template.*)" ]).
How are releases handled at the moment?

Thanks @jppgks.

yarn build changed more than should have been changed

Hm. Something strange is going on with this for me. If I rebuild after I merge your PR, I get lots of whitespace changes like:

The changes seem to be solely whitespace and nothing semantic.
Let's make an issue to talk about this.


iOS Error:  MissingPluginException

The package doesn't work on iOS platform
Error: Exception: Error while getting NSFW score: MissingPluginException(No implementation found for method getNSFWScore on channel com.blusterhub.flutter_nude_checker)

ios will be aded in comming update, currently androis is stable and has GPU support


Let Q be a PSDMatrix to remove the cholesky decompositions in each step

Codecov Report

Merging #6 (2338c44) into main (58d7021) will increase coverage by 0.18%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   87.62%   87.81%   +0.18%
==========================================
  Files          16       16
  Lines         598      599       +1
==========================================
+ Hits          524      526       +2
+ Misses         74       73       -1

Impacted Files
Coverage Δ

src/caches.jl
100.00% <ø> (ø)

src/ODEFilters.jl
62.50% <100.00%> (+9.16%)
:arrow_up:

src/diffusions.jl
98.88% <100.00%> (ø)

src/filtering.jl
63.63% <100.00%> (ø)

src/perform_step.jl
98.90% <100.00%> (ø)

src/priors.jl
100.00% <100.00%> (ø)

src/smoothing.jl
100.00% <100.00%> (ø)

src/solution.jl
88.03% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add GDAX symbol mapping based on symbol properties database

Description

Added new SymbolPropertiesDatabaseSymbolMapper
Updated GDAXBrokerage to use SymbolPropertiesDatabaseSymbolMapper
Fixed GDAXBrokerage unit tests
Included symbol properties database updates: #4708

Related Issue
Closes #4723
Replaces #4724
Motivation and Context

Support all available GDAX pairs

Requires Documentation Change
No.
How Has This Been Tested?

Brokerage unit tests

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Included by https://github.com/QuantConnect/Lean/pull/4888


No "Wow, no vulnerability was detected :)" on all project analysis

Hi,
I tried to use cobra to analysis for all project (dvwa, bwapp...), the result is alway "Wow, no vulnerability was detected :)".
Thanks!

By default Cobra does not integrate any scanning rules, so no vulnerabilities are detected.
You can refer to our default provides some scanning rules of the example, follow-up we have plans to open all of our private scanning rules.

thanks!


Use associated types for BinaryExpansion output

As there is always a single (the most efficient and the most correct) implementation of BinaryExpansion for an input type, I propose to turn the second parameter into an associated type. Most importantly, this way usage of Arithmetic a constraint does not force to turn on an UndecidableInstances language extension.

Sounds good to me.


Start of VizCLIMA docs

Added demos of using standalone VizCLIMA.jl scripts for common applications by users, as well as demos for end-to-end modelling with ClimateMachine.jl and VizCLIMA.jl (via slurm scripts).
Used Documenter.jl to create the docs.

bors r+

bors r+


Special attribute are not useful when using object syntax in v-bind, fix #5881

https://github.com/vuejs/vue/issues/5881

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

ah...
originally I wanted to change v-bind in compile-time, but  it will be a  breaken change.
because the attribute is need special treatment.
so I try to add a attribute (is) in VNodeData
can someone help me see to review it?
I will add unit tests tomorrow.
thx.

@yyx990803
the props test case is incomplete, I improve it in the code

I know it's a bit old, but the documentation recommend to add :key='item.someid' but doe to the fact that key is special it doesn't render to the dom. Is the any solution with that?
Thanks.


feat: index page development

close #7

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

我们的方案是css in js，不用写less的，可以参考 PR

close #7

close #7

close #7

rebase 和合并commit的逻辑不对，重新拉迭代merge你的分支代码吧。


GitHub publisher cannot find repository configuration

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
I'm trying to use GitHub publisher to publish releases to a private GitHub repo, however, eventhough I've the correct configuration, I get an error like this:
Electron forge was terminated:
In order to publish to github you must set the "github_repository.owner" and "github_repository.name" properties in your forge config. See the docs for more info

I'm using electron-forge v5.2.4. You can see my package.json and forge.config.js below. Could you please help me to identify and solve this problem? Thanks!

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Checking your system +0ms
  electron-forge:lifecycle Process Succeeded: Checking your system +361ms

What command line arguments are you passing?
electron-forge publish

What does your config.forge data in package.json look like?
config.forge.js:
module.exports = {
  packagerConfig: {
    "asar": true,
    "icon": "./resource/icon/icon.ico"
  },
  makers: [
    {
      name: "@electron-forge/maker-squirrel"
    },
    {
      name: "@electron-forge/maker-zip",
      platforms: ['darwin']
    }
  ],
  publishers: [
    {
      name: "@electron-forge/publisher-github",
      config: {
        repository: {
          owner: "owner",
          name: "name"
        },
        authToken: "authToken"
      }
    }
  ]
}

package.json:
{
  "name": "name",
  "productName": "productName",
  "version": "1.0.0",
  "description": "description",
  "main": "src/index.js",
  "scripts": {
    "start": "electron-forge start",
    "package": "electron-forge package",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "lint": "echo \"No linting configured\""
  },
  "keywords": [],
  "author": "author",
  "license": "UNLICENSED",
  "config": {
    "forge": "./forge.config.js"
  },
  "dependencies": {
    "electron-squirrel-startup": "^1.0.0"
  },
  "devDependencies": {
    "@electron-forge/cli": "6.0.0-beta.39",
    "@electron-forge/maker-squirrel": "6.0.0-beta.39",
    "@electron-forge/maker-zip": "6.0.0-beta.39",
    "@electron-forge/publisher-github": "^6.0.0-beta.39",
    "electron": "5.0.4",
    "electron-prebuilt-compile": "4.0.0"
  }
}

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.

It sounds to me like you're mixing Electron Forge v5 and Electron Forge v6. You should stick with Electron Forge v6 (and get rid of electron-prebuilt-compile from your devDependencies).


Feat multiplier tries to apply retroactively to companions

As the title says, when I level up my companions with the feat multiplier set higher than one, the game attempts to apply the multiplier to the levels the companion starts with. These additional feats/features do not appear on the character once level-up has concluded but it does effect the level up process itself, for example preventing options from being selected because the game thinks they have already been acquired (especially obvious when there is a selection from a small list of feats, like Lann when selecting bow specific feats). This can also result in being able to select options without meeting the prerequisites normally, like being able to select a wider selection of hexes for Camellia

Which version of Toybox are you using?

The last time I played using Toybox in 1.3.5 version, the same thing was happening to me when I set feat multiplier higher than one. Apparently from what I could verify, it is some problem related to the automatic selection of class recommended feats/abilities.

The reason I was asking is that was (supposed to be, anyway) fixed in 1.3.5 for companions recruited after that point.

I've started looking into it. I can confirm it's weird and retroactive.

Sorry, I was at work, this was on 1.3.7


Upgrade AFNetworking to 3 and up version to 0.1.0

The underlying implementation didn't need any changes. A simple upgrade of the AFNetworking pod was all that was needed

Any reason this hasn't been approved and merged?

I guess the maintainers were busy and didn't get a chance to look into this.
It's 2 yrs since I raised this PR. I ended up using my fork for the project that I was working on then.,


Some performance issues

I found some small performance issues.
disable log
if parol_runtime provide log/release_max_level_off feature like below, Rust compiler can remove trace! macro statically.
[features]
max_level_off   = ["log/max_level_off"]
max_level_error = ["log/max_level_error"]
max_level_warn  = ["log/max_level_warn"]
max_level_info  = ["log/max_level_info"]
max_level_debug = ["log/max_level_debug"]
max_level_trace = ["log/max_level_trace"]
release_max_level_off   = ["log/release_max_level_off"]
release_max_level_error = ["log/release_max_level_error"]
release_max_level_warn  = ["log/release_max_level_warn"]
release_max_level_info  = ["log/release_max_level_info"]
release_max_level_debug = ["log/release_max_level_debug"]
release_max_level_trace = ["log/release_max_level_trace"]

I got 6% performance gain.
throughput/parse        time:   [11.043 ms 11.056 ms 11.073 ms]
                        thrpt:  [1.3537 MiB/s 1.3558 MiB/s 1.3574 MiB/s]
                 change:
                        time:   [-7.8789% -5.9537% -4.3499%] (p = 0.00 < 0.05)
                        thrpt:  [+4.5478% +6.3307% +8.5528%]
                        Performance has improved.
Found 6 outliers among 100 measurements (6.00%)
  2 (2.00%) high mild
  4 (4.00%) high severe

remove is_empty before pop
VerylGrammarAuto::pop which is generated by parol has is_empty check.
It can be removed because pop will return None when the vec is empty.
fn pop(&mut self, context: &str) -> Option<ASTType> {
    //if !self.item_stack.is_empty() {
    let item = self.item_stack.pop();
    if let Some(ref item) = item {
        trace!("pop     {}: {:?}", context, item);
    }
    item
    //} else {
    //    None
    //}
}

I got 2% performance gain.
throughput/parse        time:   [10.867 ms 10.931 ms 11.023 ms]
                        thrpt:  [1.3599 MiB/s 1.3713 MiB/s 1.3793 MiB/s]
                 change:
                        time:   [-4.6804% -2.4878% -0.5493%] (p = 0.01 < 0.05)
                        thrpt:  [+0.5523% +2.5513% +4.9102%]
                        Change within noise threshold.
Found 14 outliers among 100 measurements (14.00%)
  5 (5.00%) high mild
  9 (9.00%) high severe

Thanks for your analysis.
Both are good points 👍
I will incorporate your suggestions in the next version.


Can't change to color of the 'dir' segment

Hi,
I've set POWERLEVEL9K_DIR_DEFAULT_FOREGROUND='white' in my .zshrc, but the color of the 'dir' segment is still black.
The only one that is working is POWERLEVEL9K_DIR_HOME_FOREGROUND='white', but it applies only the home dir.
What am I missing?
Thanks

Hi @gdalex !
In which folder did you try it? The default state does only affect folders outside of the home directory. For folders inside of your home directory, there is home_subfolder (POWERLEVEL9K_DIR_HOME_SUBFOLDER_FOREGROUND).. Any chance you tried in a subfolder of you home directory?

Hi dritter,
you're right, I tried it inside my home subfolders.
It works perfectly with POWERLEVEL9K_DIR_HOME_SUBFOLDER_FOREGROUND.
Cheers


Support discriminator in composition annotations

Union types can be described in OpenAPI with oneOf keyword.
But there is also very important oneOf property: discriminator.
Documentation
It allows to determine which type of union came in request/response and find a proper deserializer for it.
We use it in our specification and it works well with typescript openapi-generator which generates client code for our project.
But we still have to write this part of specification manually because it is not supported by openapi-annotation-processor.

As you can see in documentation, it is pretty complex property, and while propertyName is a pretty simple to implement with annotations, mapping is a bit more complex.
We use kotlinx.serialization in couple with sealed interfaces to produce that union types.
Considering you have a sealed interface like this:
@Serializable
sealed interface Union

@Serializable
data class A(val a: String) : Union

@Serializable
data class B(val b: String) : Union

If you serialize A or B  as Union kotlinx.serialization will add a property type with value A or B to the resulting json.
Json.encodeToString(Union.serializer(), A("a"))
// {"type":"A","a":"a"}

Names A or B can be changed with @SerialName annotation and default property name type can also be changed.
So in terms of OpenAPI Union type is oneOf(A, B) with discriminator "type" and mapping A to A and B to B.

It would be great to have an ability to generate this part of specification automatically.
I can suppose to add an optional property discriminator to oneOf annotation which will be used to generate discriminator property name and mapping.
And it would be great not to describe mapping inside it but to obtain it from subclasses annotations.

For sure we should support this, but because I'm not familiar with this part in general, could you prototype usage with OneOf annotation and example json output that you think would fit the best your use-case? :)

The minimal code that would satisfy our needs:
@OneOf(
    discriminator = Discriminator(
        propertyName = "type"
    )
)
sealed interface Union

@OneOfMappingName('class-a')
data class A(val a: Int) : Union

@OneOfMappingName('class-b')
data class B(val b: String) : Union

to produce following OpenApi spec:
{
  "schemas": {
    "Union": {
      "type": "object",
      "oneOf": [
        {
          "$ref": "#/components/schemas/A"
        },
        {
          "$ref": "#/components/schemas/B"
        }
      ],
      "discriminator": {
        "propertyName": "type",
        "mapping": {
          "class-a": "#/components/schemas/A",
          "class-b": "#/components/schemas/B"
        }
      }
    },
    "A": {
      "type": "object",
      "properties": {
        "a": {
          "type": "number"
        },
        "type": {
          "type": "string"
        }
      },
      "required": [
        "a",
        "type"
      ]
    },
    "B": {
      "type": "object",
      "properties": {
        "b": {
          "type": "string"
        },
        "type": {
          "type": "string"
        }
      },
      "required": [
        "b",
        "type"
      ]
    }
  }
}

Note that discriminator.propertyName ("type" in this case) field must be presented and required in all subclasses

Simple classes
We always use discriminator on a sealed classes/interfaces which allows to create mapping automatically because all subclasses of sealed class/interface are known at compile time, so it is possible to traverse all subclasses and get their @OpenApiMappingName (or throw an exception if it is not set?)
But your plugin is java compatible which means simple classes should be supported as well
So I would extend @OneOf from the sample above with autoMapping and mapping parameters:
// case one: sealed class/interface
@OneOf(
    discriminator = Discriminator(
        propertyName = "type",
        autoMapping = true // requires annotated class/interface to be sealed
    )
)
sealed interface Union

@OneOfMappingName('class-a')
data class A(val a: Int) : Union

@OneOfMappingName('class-b')
data class B(val b: String) : Union

// case two: simple class
@OneOf(
    discriminator = Discriminator(
        propertyName = "type",
        mapping = Mapping(
            ClassMapping("class-a", A::class.java),
            ClassMapping("class-b", B::class.java)
        )
    )
)
interface Union2

data class A2(val a: Int) : Union2
data class B2(val b: String) : Union2

You are right, discriminator can be used in AllOf but as I can see mapping property is not used in this case
In the examples I could find allOf.discriminator contains only propertyType property and mapping is made implicitly by component names (A and B in the sample above).

As far as I see in specification it's allowed to be used with each combinator:

~ https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.2.md#discriminatorObject
Not sure what's the use case, but I think I'll implement it like that. It'll be also easier to just the same annotations for each case.

Implementation with output:

https://github.com/javalin/javalin-openapi/pull/131

By default if you won't specify classes (for refs) or mappings, it'll automatically search for subclasses. If specified, the given ones are provided instead of subclasses.
I need to add 1-2 tests more, but I'll finish it tomorrow. In the meantime you can check if it makes sense for you.

Wow, cool, I'll try it in a few hours

I tried it and want to report some issues

automapping ignores @OpenApiName of subclasses, so discriminator.mapping references on class by it's simpleName while the class itself has name from @OpenApiName

according to OpenAPI documentation field with name from propertyName ("type" in our sample) must be presented in all models listed in oneOf and it must be required. Is it possible to add it if it is not present there already?

according to OpenAPI documentation field with name from propertyName ("type" in our sample) must be presented in all models listed in oneOf and it must be required. Is it possible to add it if it is not present there already?

This is slightly problematic, because we need to generate non-existing property for class definition 🤔 Don't you think that this property should be defined in class to fulfill serialization rules? It'd be quite strange to expect this property if it'd be present in those classes, so e.g. Jackson would need to throw exception as it doesn't allow by default to serialize entities with extra properties.

I'm afraid you are right :) Silent generation of non-existing property kinda smells.
From another hand that's exactly what our serialization library (kotlinx.serialization) does: it injects field with model name inside json. I understand that this magic with "type" field is rather problem of kotlinx.serializatoin and you don't have to make your plugin compatible with all serialization libraries.
I'm just trying to find a way to make them work together. I just checked: kotlinx.serialization explicitly forbids the models to have the field used as discrimintor to avoid conflicts.
What about adding something like autoInject boolean property to @Discriminator?
Of course it makes your product more complex which is not good but I don't see any other disadvantages.
I would implement it and propose a PR if only you agree for that.

I see, well kinda strange. Another issue I see is that we don't know the type of this discriminator property, I guess it's not always string? 🤔

Oh, I didn't ever think about it. And it looks like OpenAPI allows to have any type there. And it definitely make sense for enums for exapmle.

So maybe something like injectPropertyInMappings = DiscriminatorProperty(name = "type", type = String::class) 🤔

it would be great!
but how is it supposed to be combined with discriminator property of @OneOf?
@OneOf(
    disriminator = Discriminator(propertyName = "type"),
    injectPropertyInMappings = DiscriminatorProperty(name = "type", type = String::class)
)

is it correct?

I think it should be inside the @Discriminator() annotation as it's related to propertyName 🤔

like that?
@OneOf(
    disriminator = Discriminator(
       propertyName = "type",
       injectPropertyInMappings = DiscriminatorProperty(name = "type", type = String::class)
    )
)

in any case DiscriminatorProperty.name looks redundant because it must duplicate Discrimator.name
or you suppose to use injectPropertyInMappings without discriminator?

Regarding emiting property to scheme generator I understood you and really, I'm so embarrased to distract you on such minor things like support of  specific serialization libraries especially given the fact that it requires significant changes
I thougth I could add "type" fields with a script that post-processes OpenAPI spec as a json.
It is a hacky solution, but maybe it is fine since it is a support of kotlix.serialization magic and thus as any magic it doesn't have to have proper solution.

Yeah, we can reuse value from propertyName 😅

Btw, what would happen if you'd add this property directly to your subclasses? Also, which exactly kotlinx.serialization library do you mean, by default it just serializes data, so I guess you're using some extra generator to generate those typescript mappings?

We use https://github.com/Kotlin/kotlinx.serialization library as a serialization library on server side (and on both client/server sides when our different services communicates with each other).
It is not the most popular library, we chose it because it is offcical one and because it runs in compile time.
It also has very convinient support of polymorphism: https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/polymorphism.md#sealed-classes
It implicitly adds discriminator field to json and I found it very convinient because it keeps that field on serialization level and if you use kotlinx.serialization on both client and server sides (which we do communicating between services) you may not think about disciminator at all: it just works.
Later when our API grown and it became difficult to keep it conistent with documentation I started to search for an instrument that could help us with it and OpenAPI was an obvious candidate which we finally chosen. And I was very happy to discover that the way kotlinx.serializtion supports polymorphism (by discriminator field) is fully compatible with OpenAPI standard.
about the typescript mappings
We also tried to generate client API code for our typescript client and it works perfect. E.g. the sample of OpenAPI code above will produce TS code (I removed some code for short, just wanted to show the idea how it works):
interface A {
    a: number;
    type: string;
}
interface B {
    b: string;
    type: string;
}
type Union = { type: 'class-a' } & A | { type: 'class-b' } & B;

export function UnionFromJSONTyped(json: any, ignoreDiscriminator: boolean): Union {
    if ((json === undefined) || (json === null)) {
        return json;
    }
    switch (json['type']) {
        case 'class-a':
            return {...AFromJSONTyped(json, true), type: 'class-a'};
        case 'class-b':
            return {...BFromJSONTyped(json, true), type: 'class-b'};
        default:
            throw new Error(`No variant of Union exists with 'type=${json['type']}'`);
    }
}

you can see it uses discriminator field to find a proper deserializer for coming object

Thus, after you kindly close some issues from our side all our chain:
[Kotlin models] ===javalin-openapi===>>> [OpenAPI spec] ===openapi-generator===>>> [TS models]
works except that moment with injecting type field to OpenAPI models
That's why I wrote all this wall of text :)

Oh, in answer to your question if I add propertyName field to models kotlinx.serialization will throw an error which is understandable because if he don't, data in this field will be silenlty overwritten by serialization library which is not good.

Take a look on alpha.6, I think it should cover your use case:

https://github.com/javalin/javalin-openapi/releases/tag/5.3.0-alpha.6

Hi dzikoysk, I'm currently on Christmas break untill eraly January, I'll try it as soon as I get back to work.
Thank you very much!

Thank you very much, it works brilliantly
I just found one typo: you use "mappings" keyword instead of correct "mapping"
For your convinience I created PR (see above) where I renamed mappings to mapping (not only in generated json spec, but everywhere for consitency), use it if you think it fixes the problem in a right way.

Sure, it's merged and the change is available in the latest snapshot. Unfortunately I'm unable to release 5.3.0 due to several issues with Nexus & Maven Central atm with our community accounts.


Feature request - Support for Audi

The API's exposed by VW Group seem to be somehow aligned across the different brands (Skoda, VW, Audi).
Is there a way to make the integration more generic by supporting URL for the other brands (e.g. Audi) ?
This would enable new API's to be directly supported for all brands, rather than multiple integrations needing to retrofit in their own corner...

The API's exposed by VW Group seem to be somehow aligned across the different brands (Skoda, VW, Audi).
Is there a way to make the integration more generic by supporting URL for the other brands (e.g. Audi) ?
This would enable new API's to be directly supported for all brands, rather than multiple integrations needing to retrofit in their own corner...

Yes it's possible and I have started on a project to abstrakt the API and make it easier to build support for the different brands and models.
And make the code more pythonic.
I don't have nearly enough time, or experience, though to make it a reality.


[Bug]: Nonspecified Rx/Tx Closed Message

Commit Hash
31466a6
Steps to Reproduce?

Run Server
Run On-Box Node
Run Remote Node
Wait

Observed Behavior
We observe occasional Rx closed and Tx closed messages
Desired Behavior
We need more insight into which Rx and Tx are closed.
Component
On Box Sensor Node
Relevant Sensor Node log output
N/A

Relevant Sensor Node configuration
N/A

Relevant Server log output
2021-11-21 22:40:09,936 - root - ERROR - Failed to create server: Command '['git', 'rev-parse', '--short', 'HEAD']' returned non-zero exit status 128.
Traceback (most recent call last):
  File "/home/ntlhui/anaconda3/bin/runServer.py", line 48, in main
    server = Server(site_config)
  File "/home/ntlhui/anaconda3/lib/python3.8/site-packages/DataServer/server.py", line 231, in __init__
    self._log.info(f"Starting ASM Data Server v{DataServer.__version__}, {self.__getRevision()}")
  File "/home/ntlhui/anaconda3/lib/python3.8/site-packages/DataServer/server.py", line 223, in __getRevision
    git_rev_parse = subprocess.check_output(['git', 'rev-parse', '--short', 'HEAD']).decode('ascii').strip()
  File "/home/ntlhui/anaconda3/lib/python3.8/subprocess.py", line 415, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/home/ntlhui/anaconda3/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git', 'rev-parse', '--short', 'HEAD']' returned non-zero exit status 128.
2021-11-21 23:02:16,609 - Server - INFO - Starting ASM Data Server v<IP_ADDRESS>,  dirty
2021-11-21 23:02:16,611 - root - INFO - Discovered data_dir: /ayeayedata
2021-11-21 23:02:16,611 - root - INFO - Discovered port: 9000
2021-11-21 23:02:16,611 - root - INFO - Discovered server_uuid: 33cc5438-3d39-11ec-8957-378c22225c74
2021-11-21 23:02:16,611 - root - INFO - Discovered video_increment: 300
2021-11-21 23:02:16,611 - root - INFO - Discovered rtsp_port_block: [10000, 10100]
2021-11-21 23:02:16,611 - root - INFO - Data Directory: /ayeayedata
2021-11-21 23:02:16,614 - asyncio - DEBUG - Using selector: EpollSelector
2021-11-21 23:02:16,614 - Server - INFO - Connecting to :9000
2021-11-21 23:02:19,986 - Server - INFO - Starting ASM Data Server v<IP_ADDRESS>,  dirty
2021-11-21 23:02:19,987 - root - INFO - Discovered data_dir: /ayeayedata
2021-11-21 23:02:19,988 - root - INFO - Discovered port: 9000
2021-11-21 23:02:19,988 - root - INFO - Discovered server_uuid: 33cc5438-3d39-11ec-8957-378c22225c74
2021-11-21 23:02:19,988 - root - INFO - Discovered video_increment: 300
2021-11-21 23:02:19,988 - root - INFO - Discovered rtsp_port_block: [10000, 10100]
2021-11-21 23:02:19,988 - root - INFO - Data Directory: /ayeayedata
2021-11-21 23:02:19,990 - asyncio - DEBUG - Using selector: EpollSelector
2021-11-21 23:02:19,990 - Server - INFO - Connecting to :9000
2021-11-22 00:23:40,715 - ClientHandler - INFO - Getting client for uuid 8124cb7c-41ec-11ec-aaad-e45f015ed519
2021-11-22 00:23:40,716 - ClientHandler - INFO - Got heartbeat from 8124cb7c-41ec-11ec-aaad-e45f015ed519 (Auto-registered device) at 2021-11-22 00:23:40.712000
2021-11-22 00:24:07,578 - ClientHandler - INFO - Rx closed
2021-11-22 00:24:07,578 - ClientHandler - INFO - Tx closed
2021-11-22 00:35:14,329 - ClientHandler - INFO - Rx closed
2021-11-22 00:35:14,335 - ClientHandler - INFO - Tx closed
2021-11-22 00:35:34,502 - ClientHandler - INFO - Rx closed
2021-11-22 00:35:34,503 - ClientHandler - INFO - Tx closed
2021-11-22 00:36:03,380 - ClientHandler - INFO - Rx closed
2021-11-22 00:36:03,380 - ClientHandler - INFO - Tx closed
2021-11-22 00:36:23,549 - ClientHandler - INFO - Rx closed
2021-11-22 00:36:23,549 - ClientHandler - INFO - Tx closed
2021-11-22 00:36:43,720 - ClientHandler - INFO - Rx closed
2021-11-22 00:36:43,721 - ClientHandler - INFO - Tx closed
2021-11-22 00:37:03,890 - ClientHandler - INFO - Rx closed
2021-11-22 00:37:03,891 - ClientHandler - INFO - Tx closed
2021-11-22 00:37:24,080 - ClientHandler - INFO - Rx closed
2021-11-22 00:37:24,081 - ClientHandler - INFO - Tx closed
2021-11-22 04:46:42,234 - ClientHandler - INFO - Rx closed
2021-11-22 04:46:42,235 - ClientHandler - INFO - Tx closed
2021-11-22 07:47:25,603 - ClientHandler - INFO - Rx closed
2021-11-22 07:47:25,604 - ClientHandler - INFO - Tx closed
2021-11-22 08:06:47,558 - ClientHandler - INFO - Getting client for uuid a4a5090c-fc41-47d4-a180-e82cf8bfc899
2021-11-22 08:06:47,558 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:06:47.551000
2021-11-22 08:06:47,558 - ClientHandler - INFO - Got RTP Start Command
2021-11-22 08:06:47,558 - ClientHandler - INFO - Got port 10001
2021-11-22 08:06:47,559 - ClientHandler - INFO - Started ffmpeg with command: ffmpeg -i tcp://@:10001?listen -c copy -flags +global_header -f segment -segment_time 300 -strftime 1 -reset_timestamps 1 /ayeayedata/a4a5090c-fc41-47d4-a180-e82cf8bfc899/%Y.%m.%d.%H.%M.%S.mp4
2021-11-22 08:06:47,565 - ClientHandler - INFO - RTP Server on port 10001 started outputting to /ayeayedata/a4a5090c-fc41-47d4-a180-e82cf8bfc899
2021-11-22 08:07:47,549 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:07:47.551000
2021-11-22 08:08:47,548 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:08:47.552000
2021-11-22 08:09:47,550 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:09:47.553000
2021-11-22 08:10:23,540 - ClientHandler - INFO - Getting client for uuid a105a7ea-3eae-11ec-8446-a0afbd87594c
2021-11-22 08:10:23,540 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:10:23.533000
2021-11-22 08:10:23,541 - ClientHandler - INFO - Got RTP Start Command
2021-11-22 08:10:23,541 - ClientHandler - INFO - Got port 10002
2021-11-22 08:10:23,542 - ClientHandler - INFO - Started ffmpeg with command: ffmpeg -i tcp://@:10002?listen -c copy -flags +global_header -f segment -segment_time 300 -strftime 1 -reset_timestamps 1 /ayeayedata/a105a7ea-3eae-11ec-8446-a0afbd87594c/%Y.%m.%d.%H.%M.%S.mp4
2021-11-22 08:10:23,545 - ClientHandler - INFO - RTP Server on port 10002 started outputting to /ayeayedata/a105a7ea-3eae-11ec-8446-a0afbd87594c
2021-11-22 08:10:47,550 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:10:47.554000
2021-11-22 08:11:23,541 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:11:23.533000
2021-11-22 08:11:47,550 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:11:47.554000
2021-11-22 08:12:23,542 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:12:23.534000
2021-11-22 08:12:47,551 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:12:47.555000
2021-11-22 08:13:23,542 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:13:23.535000
2021-11-22 08:13:47,551 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:13:47.555000
2021-11-22 08:14:23,567 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:14:23.535000
2021-11-22 08:14:47,556 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:14:47.556000
2021-11-22 08:15:23,543 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:15:23.536000
2021-11-22 08:15:47,552 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:15:47.556000
2021-11-22 08:16:23,545 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:16:23.537000
2021-11-22 08:16:47,553 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:16:47.557000
2021-11-22 08:17:23,551 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:17:23.537000
2021-11-22 08:17:47,553 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:17:47.558000
2021-11-22 08:18:23,548 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:18:23.538000
2021-11-22 08:18:47,554 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:18:47.558000
2021-11-22 08:19:23,582 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:19:23.539000
2021-11-22 08:19:47,554 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:19:47.559000
2021-11-22 08:20:23,550 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:20:23.539000
2021-11-22 08:20:47,555 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:20:47.559000
2021-11-22 08:21:23,549 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:21:23.540000
2021-11-22 08:21:47,557 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:21:47.560000
2021-11-22 08:22:23,551 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:22:23.540000
2021-11-22 08:22:47,560 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:22:47.560000
2021-11-22 08:23:23,551 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:23:23.541000
2021-11-22 08:23:47,564 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:23:47.561000
2021-11-22 08:24:23,554 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:24:23.542000
2021-11-22 08:24:47,568 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:24:47.562000
2021-11-22 08:25:23,554 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:25:23.542000
2021-11-22 08:25:47,567 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:25:47.562000
2021-11-22 08:26:23,560 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:26:23.543000
2021-11-22 08:26:47,569 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:26:47.563000
2021-11-22 08:27:23,561 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:27:23.543000
2021-11-22 08:27:47,565 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:27:47.563000
2021-11-22 08:28:23,561 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:28:23.544000
2021-11-22 08:28:47,571 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:28:47.564000
2021-11-22 08:29:23,559 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:29:23.545000
2021-11-22 08:29:47,567 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:29:47.564000
2021-11-22 08:30:23,558 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:30:23.545000
2021-11-22 08:30:47,569 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:30:47.565000
2021-11-22 08:31:23,564 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:31:23.546000
2021-11-22 08:31:47,574 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:31:47.565000
2021-11-22 08:32:23,564 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:32:23.546000
2021-11-22 08:32:47,575 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:32:47.566000
2021-11-22 08:33:23,561 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:33:23.547000
2021-11-22 08:33:47,575 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:33:47.567000
2021-11-22 08:34:23,566 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:34:23.547000
2021-11-22 08:34:47,577 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:34:47.567000
2021-11-22 08:35:23,567 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:35:23.548000
2021-11-22 08:35:47,577 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:35:47.568000
2021-11-22 08:36:23,568 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:36:23.549000
2021-11-22 08:36:47,575 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:36:47.568000
2021-11-22 08:37:23,569 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:37:23.549000
2021-11-22 08:37:47,575 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:37:47.569000
2021-11-22 08:38:23,566 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:38:23.550000
2021-11-22 08:38:47,579 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:38:47.569000
2021-11-22 08:39:23,570 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:39:23.550000
2021-11-22 08:39:47,580 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:39:47.570000
2021-11-22 08:40:23,571 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:40:23.551000
2021-11-22 08:40:47,583 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:40:47.570000
2021-11-22 08:41:23,572 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:41:23.551000
2021-11-22 08:41:47,582 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:41:47.571000
2021-11-22 08:42:23,573 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:42:23.552000
2021-11-22 08:42:47,583 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:42:47.572000
2021-11-22 08:43:23,574 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:43:23.553000
2021-11-22 08:43:47,584 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:43:47.572000
2021-11-22 08:44:23,574 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:44:23.553000
2021-11-22 08:44:47,584 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:44:47.573000
2021-11-22 08:45:23,576 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:45:23.554000
2021-11-22 08:45:47,585 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:45:47.573000
2021-11-22 08:46:23,584 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:46:23.554000
2021-11-22 08:46:47,588 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:46:47.574000
2021-11-22 08:47:23,583 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:47:23.555000
2021-11-22 08:47:47,586 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:47:47.574000
2021-11-22 08:48:23,578 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:48:23.555000
2021-11-22 08:48:47,587 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:48:47.575000
2021-11-22 08:49:23,573 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:49:23.556000
2021-11-22 08:49:47,588 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:49:47.575000
2021-11-22 08:50:23,574 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:50:23.557000
2021-11-22 08:50:47,584 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:50:47.576000
2021-11-22 08:51:23,579 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:51:23.557000
2021-11-22 08:51:47,589 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:51:47.577000
2021-11-22 08:52:23,580 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:52:23.558000
2021-11-22 08:52:47,585 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:52:47.577000
2021-11-22 08:53:23,580 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:53:23.558000
2021-11-22 08:53:47,592 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:53:47.578000
2021-11-22 08:54:23,580 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:54:23.559000
2021-11-22 08:54:47,588 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:54:47.578000
2021-11-22 08:55:23,575 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:55:23.560000
2021-11-22 08:55:47,590 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:55:47.579000
2021-11-22 08:56:23,593 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:56:23.560000
2021-11-22 08:56:47,593 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:56:47.579000
2021-11-22 08:56:50,500 - ClientHandler - INFO - Rx closed
2021-11-22 08:56:50,501 - ClientHandler - INFO - Tx closed
2021-11-22 08:57:23,586 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:57:23.561000
2021-11-22 08:57:47,591 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:57:47.580000
2021-11-22 08:57:50,666 - ClientHandler - INFO - Rx closed
2021-11-22 08:57:50,667 - ClientHandler - INFO - Tx closed
2021-11-22 08:58:23,580 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:58:23.561000
2021-11-22 08:58:47,588 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:58:47.580000
2021-11-22 08:58:50,838 - ClientHandler - INFO - Rx closed
2021-11-22 08:58:50,838 - ClientHandler - INFO - Tx closed
2021-11-22 08:59:23,576 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 08:59:23.562000
2021-11-22 08:59:47,591 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 08:59:47.581000

Relevant Server configuration
# This is a sample configuration for the Aye-Aye Sleep Monitoring Data Server.
# Use this as a basis for configuring the data server for the specific server.

# Local path in which to store the data hierarchy
data_dir: /ayeayedata

# This is the primary port for the data server.
port: 9000

# Data Server UID
#
# This is the UUID that uniquely identifies this device.
server_uuid: '33cc5438-3d39-11ec-8957-378c22225c74'

# This is the maximum length of video data
video_increment: 300

# RTSP Server Port Block
#
# This is the block of ports that RTSP servers should use.
rtsp_port_block: [10000, 10100]

Relevant code is DataServer.server.ClientHandler.command_handler and DataServer.server.ClientHandler.response_sender in DataServer/server.py:118, DataServer/server.py:131

Fixing in #34