Inventory Feature

As a user, I want to save items that I pick up from each room.
Acceptance Criteria:

It is done when the user can click a button to view their inventory and see the items they have picked up from each room.


CSS files served as text/plain

This is, I think, similar to #373, but I'm using standalone mode with jetty.
Static CSS files are served as plain/text. This is a problem. There are two changes needed:

[ ] Automatically add Content-Type header when statically serving CSS files, as it's common sense
[ ] Allow before and after filters to work for static file requests, as people may need to do things depending on the served file. For example here this would allow adding the Content-Type for CSS, but there are a lot of use cases.

Please also note that this is a high priority issue, as it completely breaks internet explorer support.

Ok I just noticed this commit https://github.com/perwendel/spark/commit/4a2b982b39d279350663e6ff926ea4ee26aafdd3
You may want to close this issue once it's completely implemented/tested (if it isn't yet), hopefully this will get released ASAP!

This should work!


[NTR/gene] MYH7-related skeletal myopathy

Preferred gene-related syndrome label
MYH7-related skeletal myopathy
Synonyms
Myosin storage myopathy
Laing distal myopathy
Definition (free text, please give PubMed ID, if applicable, in format PMID:#######)
MYH7 related myopathy with scapuloperoneal, distal or limb-girdle muscle weakness and involving the skeletal system.
PMID:22918376
PMID:24664454
PMID:22918376
Parent term (use OLS, or your favorite ontology browser)
Congenital Myopathy, MONDO:0019952
Children terms (if applicable) Should any existing terms be re-classified as children underneath this new proposed term?
Your nano-attribution (ORCID) or URL for a working group
@nicolevasilevsky This MonDO ID request is coming from the ClinGen Congenital Myopathy Gene Curation Expert Panel. Let me know if I can provide any other info. Thanks!

I added this as MONDO_0100149
There is a pending pull request, but this should be available in the next release - end of July/early Aug

@brookepalus I have a question -
There is an existing term for Laing distal myopathy (MONDO_0008050 'Laing early-onset distal myopathy')
Are these the same terms?
Or should Laing distal myopathy be a related synonym?

@nicolevasilevsky Laing distal myopathy should be a synonym for MYH7-related skeletal myopathy. I do not think that it should be a subclass/subtype.
Thanks!

thanks @brookepalus. See the comments on: https://github.com/monarch-initiative/mondo/pull/1771
Based on your's and Chris' comments, it seems this is best added as a synonym to the existing class MONDO_0008050 Laing distal myopathy

Hi @nicolevasilevsky, I want to follow up with this previous request for MYH7-related skeletal myopathy. I understand that  MYH7-related skeletal myopathy and Laing distal myopathy are now synonyms, but is there any way that MYH7-related skeletal myopathy could be used as the primary Mondo term? This is at request from the experts of the ClinGen Congenital Myopathies GCEP. Please let me know if you have any questions and many thanks for your help!
Best,
Brooke

Of course @brookepalus, no problem at all. This will be updated in the next release in early March.


Updates/fixes for rendering CICD workflows

Fixes | Closes | Resolves #

Please remove anything marked as optional that you don't need to fill in. Choose one of the keywords preceding to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666). If there is no issue, remove the line. Remove this note after reading.

Changes:

Additions and fixes related to #1068

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[x] Yes
[ ] No

In case you checked yes, did you write tests?

[ ] Yes
[ ] No

Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

Testing completed for: ci-provider==

[ ] github-actions
[ ] gitlab-ci


User is no longer prompted to send ACRA crash reports

Summary:
ACRA crash report prompt has disappeared.
Steps to reproduce:
Generate a crash
Expected behavior:
In prior versions (not sure how long ago), the user used to be prompted to send crash reports to ACRA (our mailing list) whenever the app crashes. This allows us to see the logs of a crash alongside the user's comments, which is important for debugging.
Observed behavior:
No prompt to send crash report.
Device and Android version:
Samsung Galaxy S7, Android 6.0.1
Commons app version:
2.7.0
Would you like to work on the issue?
Preferably not, but I'll pick it up if no one wants it

I will start working on it and also update ACRA to the latest version available.

Cool, thanks @tanvidadu ! :) Please submit your PR to 2.7.x-release branch.


SUGGESTION: Making it easire to "try it" with Dockerfile / devcontainer / etc.

I, like many others, wanted to try out crewAI and generally the first thing I do is run sometihng in Docker or a devcontainer (which is Docker behind the scenes). This can be as simple as clicking the "Code" green button in GitHub and opening in CodeSpaces (online / on their servers).
In looking at the repo and the README it appeared I didn't need to clone this repo, just set up the basic things you said - As such instead of a PR (which I'm perfectly willing to make) I just made a new repo with the example in the README - https://github.com/bitshop/crewai-devcontainer
Generally I'd do a PR instead of a distinct repo - Do you think there's some good way to merge this somewhere? Perhaps a second repo like crewAI-example or such? I'm obviously happy to keep the repo myself but this is a trivial amount of work and contributing it is fine.

The way I use crewAI with dev containers is by having dev containers start with the requirements file loading in all the crewAI, no need for a docker file as using a Python base image build, this works perfectly as if I need anything extra I add it to the requirements.txt file, I will be migrating to poetry with the Python poetry base image

Thank you and I agree there's no need for Dockerfile but I was thinking this can be a fork or copy/paste as a template for new devs / projects - Those often will want a Dockerfile to add apt installs to. I'll change to requirements.txt for the same reason, thanks for that tip.
My assumption is more and more people will be developing in containers and remote, so trying to make something easier for those devs.
For simpler projects (like this demo) I do agree the format of post install commands and base python image works very well.


[hw,uart] noise filter issue with CDC instrumentation

Description
With CDC enabled, the primt_flop_2sync module introduces a random delay of 1 cycle.
https://github.com/lowRISC/opentitan/blob/3bf9d8741d1cf4369d3b34cba477718c22065946/hw/ip/uart/rtl/uart_core.sv#L230-L239
Due to this, a pulse of one cycle will randomly

produce a pulse of two cycles
miss the pulse
passthrough the pulse

The noise filter in uart module filters glitches of up to one cycle.

@msfschaffner please note.
I don't think this should be considered a bug, the sync module here being used to synchronize an async input rather than being used in CDC. The RTL is implementing what the spec asks for.
A separate question is whether the specified noise filter is sufficient, at a 25 MHz clock you'll filter any pulse at under 40ns. Seems OK though there may be an expectation that UART lines can handle more noise.

Agreed, I don't think that should be treated as a bug.
It is also questionable whether that noise filter spec is meaningful, given that it can only filter very short noise pulses (as you already pointed out).

Is there anything left in this issue that needs doing? (@msfschaffner / @GregAC)

Does this still lead to test failures or was this just an observation?
If it is the latter, I think this is "working as intended".

As far as I can see, this is working as intended either way. DV fixes might be needed, but this issue doesn't describe them :-)
Let's close this and worry about any future problems if they arise.


Automated tests : tasks sequence

Below is a list of tasks in order to automate cluster deployment tests :

[x] Test on the main linux distribs :

[ ] Fedora
[x] Centos 7
[x] RedHat 7
[x] Ubuntu 1404
[x] Ubuntu 1510
[x] Debian 8
[ ] Debian 7

[x] One test per network plugin
[x] Idealy a cluster will be composed of

a master (master components only)
a master with node components (handles workloads)
a node

Test sequence:

[x] Cluster deployment
[x] Check all nodes ready
[x] Run a replica controller composed of 2 pods

kubectl run test --image=busybox --replicas=2 --command -- tail -f /dev/null
replicationcontroller "test" created

[ ] Check that pods ip addresses are in the configured subnet

kubectl describe po test-34ozs | grep ^IP
IP:             <IP_ADDRESS>

kubectl exec test-34ozs -- ip a show dev eth0
8: eth0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1450 qdisc noqueue
    link/ether 02:42:0a:e9:2b:03 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global eth0

[x] Ping between pods
[ ] Deploy the kubedns app and browse the kubernetes api using the service name as follows

kubectl exec test-f31yx -- curl -k -u kube:changeme https://kubernetes

This is what I'm doing with Digital Rebar.  Or trying to get to run.  I'm mostly there.

@galthaus Can you describe a little what your trying to do ?
From our side we would like to check at least once per day all deploy options:

6/7 OS:  (Ubuntu 14.04|16.04), Centos 7, RH, Fedora 23, CoreOS, Debian Jessie
2 container engine: docker, rkt
3/4 overlay network:  flannel, calico, weave, opencontrail
Ansible release: 2.x, 1.9.x

which give around 100 differents setup/jobs.

Sorry - missed this.
We are looking to use DigitalRebar to drive kubernetes deployments across bare metal, cloud infrastructures and hosters.  (Kubernetes is one of many workloads to drive).
Much like you have listed, I have started importing this playbook into digital rebar.
We can spin up nodes in google, AWS, packet, and bare metal (we have our on provisioner components as part of digital rebar).  We can then layer configuration options through our attribute system to choose the other options that you mention.
So, I'm getting close to being able to launch a digital rebar admin node in google and then drive most of those combinations, test them, and run them concurrently.

@jcsirot i think there's only one task missing :

Deploy the kubedns app and browse the kubernetes api using the service name as follows

i've open an issue for CoreOS CI tests #211

Maybe it is time to update this ticket's content

We need to implement last item :

check that kubedns is working
check https://kubernetes.default.svc.cluster.local  is ok on each nodes

We should verify resolution and connectivity to https://kubernetes.default.svc.cluster.local. It tests: dnsmasq, kubedns, proxy via kube-proxy to kube-apiserver. It can be done from the host itself. What's really important is to run this test on a non-master node.

It seems implemented with the netchecker app


In the Flow we have 900 Minutes, that are 15 hours

Learn Build status updates of commit 7a42b9a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

power-platform/guidance/coe/setup-core-components.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 learn.microsoft.com contributor guidesPost your question in the Learn support channel


make sure addon.xml meets all requirements

This pull request includes the following changes to addon.xml:

added standalone directive to xml declaration
edit addon element attributes order
added required summary element
clean up spacing

Codecov Report

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

@@           Coverage Diff           @@
##           master     #148   +/-   ##
=======================================
  Coverage   73.62%   73.62%
=======================================
  Files          20       20
  Lines        1274     1274
  Branches      245      245
=======================================
  Hits          938      938
  Misses        225      225
  Partials      111      111

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 861bdea...22dcc4e. Read the comment docs.

You may want to add the About dialog from @horstle if you plan on releasing a new version.
I think it is already quite useful.

Okay, I'll take a look at that, but there will be only a release if first https://github.com/emilsvennesson/script.module.inputstreamhelper/issues/146 is fixed.


Feature request: Reusable content

When using DGTE with Umbraco 7 we typically solved this by using the same doc types to create content in a content area (ex. "Shared Content Elements") and then adding a picker to dgte. Problably a fairly commen approach..
We could do the same in U8. As the doctypes used for dtge are elements we just add and extra step of creating a wrapper doctype that uses the element doctype as composition. And then we're back on track.
But it would be far more elegant if DTGE suppported this somehow?  Anyone givin this much thought?

There was a package for v7 https://our.umbraco.com/packages/backoffice-extensions/doctype-grid-editor-reusable-content-extension/#package-gallery-2
But that would probably run into the same problem as you are, since Elements cant be created as content.

Forgot all about that package. We didnt use it for reasons I cannot remember .. but now its incompatible for sure.

I have marked this as "Up for grabs", so if anyone wants to try and make this feature, you are welcome.
It's not on my priority list, but I'll be happy to accept a PR enabling this :)

Achieving this using compositions.
ModelBase - has all the properties and is an element
ModelContent- composed of ModelBase and is normal content you can create in the tree
ModelBlock - composed of ModelBase is an element and used directly in the grid.
We then have a block picker DTGE for selected the content versions.
Views use the interface created by Models builder and the global picker routes the pages are required.

Closing this, as I think the effort should be done in the new core Block Editor in stead. Would love to see this feature there!


Add point negation to go binding

I was trying to support removal of a signature from an aggregated signature in a downstream repository. But, I ended up getting blocked on negation support. Let me know if there is anything else that would need to be done to consider adding this functionality to the go bindings. Thanks in advance!

It sounds like Sub and SubAssign would be a better choice... I mean given that there are Add and AddAssign... And it would also be possible to minimize the amount of Cgo transitions. Point is that those are expensive. In other words, #135 is suggested as an alternative solution :-)

Closing in favor of #135


add destvi

Submission type

[ ] This submission adds a new dataset
[x] This submission adds a new method
[ ] This submission adds a new metric
[ ] This submission adds a new task
[ ] This submission adds a new Docker image
[ ] This submission fixes a bug (link to related issue: )
[ ] This submission adds a new feature not listed above

Testing

[x] This submission was written on a forked copy of SingleCellOpenProblems
[ ] GitHub Actions "Run Benchmark" tests are passing on this base branch of this pull
request (include link to passed test: )
[ ] If this pull request is not ready for review (including passing the "Run
Benchmark" tests), I will open this PR as a draft (click on the down arrow next to the
"Create Pull Request" button)

Submission guidelines

[x] This submission follows the guidelines in our
Contributing document
[x] I have checked to ensure there aren't other open Pull Requests for the
same update/change

PR review checklist
This PR will be evaluated on the basis of the following checks:

[x] The task addresses a valid open problem in single-cell analysis
[x] The latest version of master is merged and tested
[ ] The methods/metrics are imported to __init__.py and were tested in the pipeline
[ ] Method and metric decorators are annotated with paper title, year, author, code
version, and date
[ ] The README gives an outline of the methods, metrics and datasets in the folder
[ ] The README provides a satisfactory task explanation (for new tasks)
[ ] The sample test data is appropriate to test implementation of all methods and
metrics (for new tasks)

Marking as draft until CI passes on fork

hi @scottgigante-immunai apologies for rushing, I incorporated the comments and now tests and benchmark pass in fork. One thing, do I need to annotate the method with params? cause I've seen standard is kind of mixed around.

Great work @giovp !


Fail to connect to the bluetooth device. device XX:XX:XX:XX:XX:XX cannot be found.

Hi, trying to run the code after compiling against latest pull of libgatt, no success.
have the same issue on ubuntu and on debian buster :
root@blacknuc:/home/ouinouin/jbdtool# ./jbdtool -t bt:A4:C1:38:1B:16:29 -d 9
main.c(853) main: transport: 0x7ffd0a2618d0, target: 0x7ffd0a2618d3
main.c(879) main: transport: bt
module.c(51) mybmm_load_module: NOT found.
module.c(72) mybmm_load_module: init: 0x5623856b0474
module.c(79) mybmm_load_module: adding module: bt
main.c(882) main: tp: 0x5623856bdcc0
module.c(45) mybmm_load_module: mp->name: bt, mp->type: 2
module.c(51) mybmm_load_module: NOT found.
module.c(72) mybmm_load_module: init: 0x5623856a5709
module.c(79) mybmm_load_module: adding module: jbd
main.c(885) main: cp: 0x5623856bdac0
jbd.c(415) jbd_new: transport: bt
jbd.c(424) jbd_new: pp->target: A4:C1:38:1B:16:29, pp->opts:
bt.c(48) bt_new: target: A4:C1:38:1B:16:29, topts:
bt.c(61) bt_new: target: A4:C1:38:1B:16:29, topts:
main.c(897) main: charge: -1, discharge: -1
main.c(921) main: mqtt: (nil)
main.c(971) main: outfp: 0x5623875ce260
jbd.c(435) jbd_open: opening...
bt.c(86) bt_open: connecting to: A4:C1:38:1B:16:29
Device 'A4:C1:38:1B:16:29' cannot be found
error: Fail to connect to the bluetooth device.
root@blacknuc:/home/ouinouin/jbdtool#

despite being able to scan and see the JBD device :
ouinouin@blacknuc:~/jbdtool$ sudo hcitool lescan
LE Scan ...
A4:C1:38:1B:16:29 LH-SP20S005
A4:C1:38:1B:16:29 (unknown)

Getting a similar error with my 16s JBD 100A bms with Bluetooth module.
$ sudo hcitool lescan
LE Scan ...
CC:18:5C:C9:FB:8F (unknown)
A4:C1:37:00:29:64 xiaoxiang BMS
...

$ ./jbdtool -t bt:A4:C1:37:00:29:64 -d 9
main.c(861) main: transport: 0x7ffed36705, target: 0x7ffed36708
main.c(887) main: transport: bt
module.c(51) mybmm_load_module: NOT found.
module.c(72) mybmm_load_module: init: 0x555f057ae0
module.c(79) mybmm_load_module: adding module: bt
main.c(890) main: tp: 0x555f073c68
module.c(45) mybmm_load_module: mp->name: bt, mp->type: 2
module.c(51) mybmm_load_module: NOT found.
module.c(72) mybmm_load_module: init: 0x555f04bdb0
module.c(79) mybmm_load_module: adding module: jbd
main.c(893) main: cp: 0x555f073ab0
jbd.c(416) jbd_new: transport: bt
jbd.c(425) jbd_new: pp->target: A4:C1:37:00:29:64, pp->opts:
bt.c(48) bt_new: target: A4:C1:37:00:29:64, topts:
bt.c(61) bt_new: target: A4:C1:37:00:29:64, topts:
main.c(905) main: charge: -1, discharge: -1
main.c(928) main: reset: 0
main.c(944) main: mqtt: (nil)
main.c(994) main: outfp: 0x5584e802a0
jbd.c(436) jbd_open: opening...
bt.c(86) bt_open: connecting to: A4:C1:37:00:29:64
error: Fail to connect to the bluetooth device.

Using latest gattlib.

Also getting the above error on debian bullseye amd64. Is there a fix/workaround for this problem?

Debian bullseye:
root@rpi4-8gb:/home/pi/gattlib/build/examples/ble_scan# ./ble_scan
Discovered B0:7E:11:F9:BC:C1 - 'ID92931903101926      '
Discovered A4:C1:38:8E:76:3A - 'LH-SP20S005'
root@rpi4-8gb:/home/pi/jbdtool# ./jbdtool -t bt:A4:C1:38:8E:76:3A -d 3
main.c(861) main: transport: 0x7fd355679b, target: 0x7fd355679e
main.c(887) main: transport: bt
module.c(51) mybmm_load_module: NOT found.
module.c(72) mybmm_load_module: init: 0x555e927ae0
module.c(79) mybmm_load_module: adding module: bt
main.c(890) main: tp: 0x555e943c68
module.c(45) mybmm_load_module: mp->name: bt, mp->type: 2
module.c(51) mybmm_load_module: NOT found.
module.c(72) mybmm_load_module: init: 0x555e91bdb0
module.c(79) mybmm_load_module: adding module: jbd
main.c(893) main: cp: 0x555e943ab0
jbd.c(416) jbd_new: transport: bt
jbd.c(425) jbd_new: pp->target: A4:C1:38:8E:76:3A, pp->opts:
main.c(905) main: charge: -1, discharge: -1
main.c(928) main: reset: 0
main.c(944) main: mqtt: (nil)
main.c(994) main: outfp: 0x55750152a0
jbd.c(436) jbd_open: opening...
bt.c(86) bt_open: connecting to: A4:C1:38:8E:76:3A
error: Fail to connect to the bluetooth device.

I just got a JBD bluetooth adapter so I'll finally be able to test using it.
I know for a fact it works with one of these:
MLT-BT05
Give me a few days to mess with it.
Also, I dont use blutooth at all on the JBDs in my powerwall - all of my packs use a Wifi adapter:
https://diysolarforum.com/threads/jbd-bms-wi-fi-module.17252/

@sshoecraft thank you for looking into this! If you need someone to test stuff, let me know.

Any update on this?  I get the same connection error using BT.

Couldn't get this to work, spend too much time on it already.
However, for what its worth, this did work for me:
Install https://github.com/Jakeler/ble-serial with pip install ble-serial. Run ble-scan to identify BMS:
$ ble-scan
Started BLE scan

A4:C1:38:19:9A:A2 (RSSI=-54): 16S10AH-LIGHT
A4:C1:38:F0:86:0D (RSSI=-91): 16S20AH50A

then run:
$ ble-serial -d A4:C1:38:F0:86:0D

Should get the following output:
21:34:19.750 | INFO | linux_pty.py: Slave created on /tmp/ttyBLE -> /dev/pts/0
21:34:19.750 | INFO | ble_interface.py: Receiver set up
21:34:19.913 | INFO | ble_interface.py: Trying to connect with A4:C1:38:F0:86:0D: 16S20AH50A
21:34:22.252 | INFO | ble_interface.py: Device A4:C1:38:F0:86:0D connected
21:34:22.253 | INFO | ble_interface.py: Found write characteristic 0000ff02-0000-1000-8000-00805f9b34fb (H. 20)
21:34:22.253 | INFO | ble_interface.py: Found notify characteristic 0000ff01-0000-1000-8000-00805f9b34fb (H. 16)
21:34:22.622 | INFO | main.py: Running main loop!

Now you can use jbdtool to connect to the serial port mentioned:
jbdtool -t serial:/dev/pts/0
Voltage                   53.400
Current                   0.000
DesignCapacity            20.000
RemainingCapacity         19.990
PercentCapacity           100
CycleCount                14
Probes                    3
Strings                   16
Temps                     19.0,19.0,19.1
Cells                     3.337,3.336,3.336,3.337,3.341,3.338,3.339,3.337,3.339,3.335,3.339,3.337,3.339,3.337,3.339,3.335
Balance<PHONE_NUMBER>000000
CellTotal                 53.401
CellMin                   3.335
CellMax                   3.341
CellDiff                  0.006
CellAvg                   3.338
DeviceName                SP20S020A-L16S-50A-50A-B-U
ManufactureDate           20211101
Version                   12.9
FET                       Charge,Discharge

ok now thats cool.  I'll check out ble-serial!
I finally got a JBD BT adapter and will start testing it in the next couple of weeks.

I can confirm, that the solution from @mav- with  https://github.com/Jakeler/ble-serial  works fine. Buildin bt support with libgatt does not work for me , i get the same error as posted above (debian 12 amd64).
But with ble-serial i am fine :)


add is empty to json

is "true"/"false" are the value for this isempty?  did you validatethe schema? you can use ajv for this

ajv tested and passed


Skp

Did you ever workout how to convert a skp to a dae.
Trying to make a basic game for my kid to learn from.

I’m not familiar with skp files, but this turned up from googling https://blender.stackexchange.com/questions/2342/import-sketchup-skp-files

I did some research.
Trimble have a c api for exporting data from a skp.
Will put it up in my repo and do a golang wrapper
On Fri, Feb 16, 2018, 11:01 PM Glen Kelley<EMAIL_ADDRESS>wrote:

I’m not familiar with skp files, but this turned up from googling
https://blender.stackexchange.com/questions/2342/import-sketchup-skp-files
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GlenKelley/go-collada/issues/2#issuecomment-366371047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATuCwu7kfkSddaWxXUpfE9fKPPOVaVpBks5tVfqwgaJpZM4SIXrl
.


Enrichments: City by coordinates

We could have some way to enrich city, state, country by coordinates? IP lockup with GeoCity it's too bad, even with premium account in large cities!

MaxMind is famously pretty inaccurate in Brazil... Maybe take a look at https://geocoder.opencagedata.com/ ?

Cool!

Migrated to https://github.com/snowplow/enrich/issues/141


Feedback for Service 10.2.8 update

Screenshot used in this part is misleading for the customers:

The variables used in the screenshot are not possible to use in request signature.

Document Details
⚠ Do not edit this section. It is required for docs.superOffice.com ➟ Docs Team processing.

Content Source: news-service-10.2.8

Add service variables to the screenshot and upload to github

@kirstiaa The page in question is about system signature. Please use the same dialog as in the original. Consider resizing the image to show less white-space. That will make the text in the screenshot easier to read.

@digitaldiina Yes, the screenshot will not look like above, just an image gotten from Karolina 😉 to show the service variables used in the dialog.
I will update the image when 10.2.11 release notes is written.


Latest docker image outdated?

On a fresh C2M with docker run --rm --privileged multiarch/qemu-user-static:register done I get this error /build/qemu-Ee59aw/qemu-2.0.0+dfsg/tcg/optimize.c:362: tcg fatal error (qemu bug for sure) but it seems the version is 2.0.0 and not 2.5.0

docker run --rm --privileged multiarch/qemu-user-static:register won't use qemu, it will only register (configure) the binfmt,
did you ran another image after this to get this error ?

oops my fault. I got it fixed with an older build of npm.

ok :)


feat: add CRD chart to be later used as a dependency

Fixes #
Description
Add CRD chart that publishes to GHCR
How was this change tested?

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

this is a great idea.
makes the CRDs updates much nicer than most other current approaches

Hello, just asking if you're willing to reconsider this (with all the new features since June btw)
https://github.com/aws/karpenter/pull/1956

Hi, I'm wondering why not all CRDs are included here (i.e. Provisioner's CRD) as opposed to Karpenter's Helm chart.


[BUG] Default data directory in the default-settings is still /var/lib/rancher/longhorn

We've updated it to /var/lib/longhorn already in the code.

Validation: PASSED
Steps:

Deploy Longhorn
in Settings page, Default Data Path should be set to /var/lib/longhorn/
Create a volume, attach it to a node,
Verify replica path is prefixed to /var/lib/longhorn/ for all nodes


Consider adding an endpoint exposing the database size, or information

From: https://github.com/trustification/trustify/pull/841#discussion_r1771079325

maybe useful to add database size ?
untested
async fn get_database_size(db: &DatabaseConnection) -> Result<String, DbErr> {
    let query = "SELECT pg_size_pretty(pg_database_size('trustify'))";

    let result: Option<(String,)> = sqlx::query_as(query)
        .fetch_one(db)
        .await
        .map_err(|e| DbErr::Query(e.to_string()))?;

    Ok(result.map(|(size,)| size).unwrap_or_else(|| "0".to_string()))
}

Closed by https://github.com/trustification/trustify/pull/841


[ENG-5013] Link preprint contributors

Ticket: ENG-5013
Feature flag: n/a

Purpose

Link to contributor pages for preprint contributors

Summary of Changes

Update ContributorList component invocation

Screenshot(s)

On the preprint detail page, registered contributors names should be links

Side Effects

QA Notes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 69.061%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
6068

Relevant Lines:
8537

💛  - Coveralls


[Feature] Add Compound Governor

Feature Description
For initial BitDAO governance on mainnet, it's decided to use tried and audited Compound GovernorAlpha solution, which was adopted, developed and audited by OpenZeppelin, compound governor https://github.com/OpenZeppelin/openzeppelin contracts/blob/master/contracts/governance/extensions/GovernorTimelockCompound.sol. Add it as a separate Governor.sol contract and add a separate test suite to test flow.
Additional Information

After extensive OZ governance contact and compound governance contracts reasearch and comparison, I decided to still use https://github.com/compound-finance/compound-protocol/blob/master/contracts/Governance/GovernorAlpha.sol as our vanilla governance version as OZ contracts functionality is scattered among several modules like https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/governance/extensions/GovernorTimelockCompound.sol, https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/governance/extensions/GovernorVotesComp.sol and https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/governance/extensions/GovernorSettings.sol, partially all of those required for our Governor, but will require making new contract inheriting all of those, overring many methods and overriding quorum proposalThreshold and some other methods with code, which makes implementation less secure and unaudited. I had to do similar thing when developing our own Governance.sol governance version in the repo, but that was fine as we needed to add a number of Windranger special governance functionality like Roles. The only strong advantage it has over https://github.com/compound-finance/compound-protocol/blob/master/contracts/Governance/GovernorAlpha.sol is that is 0.8.0 solidity version, but updating it for GovernorAlpha is easy and doesn't break security, other things like changing constants are easier in GovernorAlpha and GovernorAlpha solution is actually more tried by other protocols for now. So I will rely on GovernorAlpha from Compound.


messageWriter: don't ignore error in writeString

fixes #30

Since WriteTo returns the w.err after using writeString() it should be updated.


improvement(ng-mobx-export):export module name as default

export module name as default so that caller no longer need to care about the real module name

@adamkleingit could u check the pr ?

@kuitos merged - thanks!

maybe u need a new version publishing for it 😀

Yes will be published soon with a few other things
On Mon, Sep 4, 2017 at 4:55 AM, Kuitos<EMAIL_ADDRESS>wrote:

maybe u need a new version publishing for it 😀
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NgMobx/ng1-mobx/pull/7#issuecomment-326849293, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACUsQ8wCc07YNW0KDzXmwd61Rz-hf3L5ks5se1ihgaJpZM4PJ3In
.

--
Adam Klein
Chief Technology Officer
Tel.   +972-52-7475633 <+972527475633>
Web 500tech.com http://www.500tech.com/ | github.com/500tech |
@adamklein500
http://twitter.com/adamklein500

@adamkleingit I haven`t see the new version published, would you do it lately？


[5.0] Use clang's effective llvm triple for IR generation

Instead of using the target that was passed to the driver. Use the target from
the clang importer that might have been changed by clang (i.e armv7 to thumbv7
on darwin)
rdar://32599805

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 8328a031f5aa2eb0d51d4e14c7ff14736438d9db

Build failed
Swift Test Linux Platform
Git Sha - 8328a031f5aa2eb0d51d4e14c7ff14736438d9db

Same failure as on the incremental bot without this change:
https://ci.swift.org/view/swift-5.0-branch/job/oss-swift-5.0-incremental-RA-linux-ubuntu-16_10/224/consoleFull#-11440285893122a513-f36a-4c87-8ed7-cbc36a1ec144

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 8328a031f5aa2eb0d51d4e14c7ff14736438d9db

@aschwaighofer There is a known issue with Linux + 5.0 branch which this hits, do you want me to force merge this changes?


QOS

Can we give all portal submitted jobs elevated QOS, ie they have the ability to use all of the microvolution licenses at once and higher priority for their jobs, when they submit jobs via the portal. but if they submit jobs via command line, they only get their regular QOS level as determined by their institutes QOS level, ie: they paid for some of Wiener.

is there anything tricky we could do with groups on slurm?
I like nicks idea of slurm only running jobs that include IPP in the title at a certain QOS level etc

If it's not possible for the IPP to elevate the QOS of job, then we need to show each user their QOS level and what resources they can access per job etc. And have a link to how they can request more resources easily

link to other issue on quota displays
any capability to allow more quota for short term jobs?
have temporary scratch? DA: /tmp folder can be used for life of job
investigate if portal can use /tmp instead of user scratch
Separate issue:
IMB cache disappearing? need replacement for local scratch/cache volume for IMB use, latest cameras run >8GB/sec
can bunya access IMB cache storage
ME to report back on strategy


Server flag block-gas-target not used

Server flag block-gas-target set but not used
Description
As the summary said, the flag is not used yet.
Proposed solution
Use the flag in block building limitation.

The PR #65 fixed this.


disable other stuff when uploadin

Description
Still need to test out a bit more but should get some feedback on implementation
When uploading files, disable other parts of the object list page

"v2" mocks from here https://apps.nrs.gov.bc.ca/int/jira/browse/SHOWCASE-2913?
Move indicator that uploading is open to state. This allows it to be known accross any sibling or child components, and will support any refactoring/moving of existing components, or adding new components.
Disable buttons. No global disable for datatable so use the usual no-click, opacity css trick.

Types of changes

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

isUploadOpen feels more like an application state, let's move this to the app store?
Do we want the upload pane to remain active when navigating away then coming back? Might want to set this to false in OnUnmounted in ObjectList.

@kamorel yeah I can move it to that store. I did set it to false in onMounted there but somehow lost that change... adding it back.

I'm not absolutely convinced isUploadOpen should be moved to the appStore because this would only apply in the application context where you would be wanting to upload a file. In this case, it would only ever show up under the /list/objects route, so at least for me, it makes sense that this state would reside more on either the associated component or view (I'm slightly leaning towards view as I'd like to eventually change it so that when that dialog shows up, it also invokes an address bar change)

@kamorel yeah I can move it to that store. I did set it to false in onMounted there but somehow lost that change... adding it back.

I'm not absolutely convinced isUploadOpen should be moved to the appStore because this would only apply in the application context where you would be wanting to upload a file. In this case, it would only ever show up under the /list/objects route, so at least for me, it makes sense that this state would reside more on either the associated component or view (I'm slightly leaning towards view as I'd like to eventually change it so that when that dialog shows up, it also invokes an address bar change)

Another option would be to keep it in the local state and add an additional prop to DeleteObjectButton and DownloadObjectButton for disabled

I'd used the local var and passed down at first, but then looking at the component and thinking about what else could go in that page in the future I saw some refactoring possible down the line. Including maybe needing to block things that aren't direct children, so did the store state to accommodate that.
Could work as local with props to children at this time though yeah. I think the state would be good for flexibility but if we'd rather have local I can go back to that. The scope and lifecycle are a little cleaner in that case.


webpubsub, add ServiceMethod annotation to method with request

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
Review feedback.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API changes have been detected in com.azure:azure-messaging-webpubsub. You can review API changes here
API changes
+         public Mono<WebPubSubClientAccessToken> getClientAccessToken(GetClientAccessTokenOptions options)
-         // Non-Service Methods:
-         public Mono<WebPubSubClientAccessToken> getClientAccessToken(GetClientAccessTokenOptions options)
+         public WebPubSubClientAccessToken getClientAccessToken(GetClientAccessTokenOptions options)
-         // Non-Service Methods:
-         public WebPubSubClientAccessToken getClientAccessToken(GetClientAccessTokenOptions options)


String length

It's needed to define a min and max length for a string.
const schema = new Config({
  port: Config.string({ coerce: true, min: 3, max: 6 }),
});

expect(() => schema.parse({ port: '3' })).toThrow(new ValidationError('Invalid configuration: The "port" expected to have at least "3" characters but it has "1" characters'));

expect(() => schema.parse({ port: '123456789' })).toThrow(new ValidationError('Invalid configuration: The "port" expected to have at most "5" characters but it has "9" characters'));

can i make changes to the code by PR

Of course, I'll assign it to you. feel free to open a PR.

ok i will start work on this issue

class ValidationError extends Error {
  constructor(message) {
    super(message);
    this.name = 'ValidationError';
  }
}

class Config {
  constructor(schema) {
    this.schema = schema;
  }

  parse(data) {
    for (const key in this.schema) {
      const field = this.schema[key];

      if (field.min !== undefined && data[key].length < field.min) {
        throw new ValidationError(`Invalid configuration: The "${key}" expected to have at least "${field.min}" characters but it has "${data[key].length}" characters`);
      }

      if (field.max !== undefined && data[key].length > field.max) {
        throw new ValidationError(`Invalid configuration: The "${key}" expected to have at most "${field.max}" characters but it has "${data[key].length}" characters`);
      }
    }
  }
}

const schema = new Config({
  port: { min: 3, max: 6 },
});

try {
  schema.parse({ port: '3' });
} catch (error) {
  if (error instanceof ValidationError) {
    console.error(error.message);
  }
}

try {
  schema.parse({ port: '123456789' });
} catch (error) {
  if (error instanceof ValidationError) {
    console.error(error.message);
  }
}

this is my approach.. if it'ok.. could you please tell me how can i set project locally.. and raise a PR with these code changes

Hey, it works but it's not extendable.
This validation is the StringSchema concern,
As you can find in the code we have a Guard concept and each schema has an array of guards here, we'll add guards based on the input and schema configuration. and on the validation method, we run all the guards against the value here.
So, you'll need to implement these methods within the StringSchema class.

Done


Invalid loading of segmentation with cropped in-plane data

Bug Report
Describe the Bug
I am the author of pydicom-seg, a library for reading and writing DICOM-SEG in Python, and currently try to track down errors in using the generated DICOM-SEGs in OHIF/Viewer (https://github.com/razorx89/pydicom-seg/issues/20).
Currently, OHIF viewer does not correctly load DICOM-SEG data, which was cropped in-plane. The CT image has an in-plane resolution of 512x512, while the cropped segmentation has a resolution of 272x224. As you can see below, the 512x512 is shown correctly while the 272x224 is distorted. Cropping is intended to reduce the generated DICOM size, since for small segmented objects most of the frame data is only zeros.

It seems like an error in accessing the allocated segmentation buffer and thus assigning to the wrong voxels. In order to correctly assign the voxels, the PlanePositionSequence[0].ImagePositionPatient attribute in the PerFrameFunctionalGroupSequence as well as the Rows and Columns need to be used for computing the correct buffer indices.
Loading the DICOM-SEG using my package or via the conversion tool segimage2itkimage from  QIICR/dcmqi, followed by resampling to the original CT image grid using SimpleITK, displays the correct segmentation in ITKSnap.
What steps can we follow to reproduce the bug?
Data credits go to: QIICR/dcmqi
I prepared the ct-3slice scan,  from dcmqi's repository, with the corresponding liver.dcm segmentation as example.zip. The liver-nocrop.dcm is exported using my package without in-plane cropping, the liver-cropped.dcm is exported with cropped segmentation data.

Thanks for the detailed report 👍
Can you try one quick experiment?  Click the 2D MPR button and see if it displays correctly on the other planes.  If it does, then this is something to do with how OHIF cornerstone handles the different grids.  If the MPR is also wrong then it's something with the SEG parsing in dcmjs.

Sure!

It is hard to see since the CT image only contains three slices, but it is also broken in MPR.

Interesting - a bit off-topic for this issue, but I tried to replicate this using OHIF against google's dicomweb and I get the message below about it being an invalid instance.  I guess google doesn't support a value of 1 for BitsAllocated.  But this is not correct according to the standard.  FYI @fedorov I guess I'll report this as a bug to the google folks.
https://healthcare.googleapis.com/v1beta1/projects/idc-sandbox-000/locations/us-central1/datasets/sdp-dev/dicomStores/cropped-seg/dicomWeb/studies/1.2.392.200103.20080913.113635.0.2<IP_ADDRESS>.43.10.22941.1/series/1.2.8<IP_ADDRESS>80043.8.498.71167181430473953726005125072372749258/instances/1.2.8<IP_ADDRESS>80043.8.498.88983434253411987964922722856183426978

generic::invalid_argument: error while transcoding from 1.2.840.10<IP_ADDRESS> to application/dicom; transfer-syntax=1.2.840.10<IP_ADDRESS>: invalid Pixeldata macro attributes: Rows/Columns/SamplesPerPixel must be set and BitsAllocated must be a multiple of 8, cause (internal only): generic::invalid_argument: invalid Pixeldata macro attributes: Rows/Columns/SamplesPerPixel must be set and BitsAllocated must be a multiple of 8
com.google.apps.framework.request.StatusException: <eye3 title='INVALID_ARGUMENT'/> generic::INVALID_ARGUMENT: invalid Pixeldata macro attributes: Rows/Columns/SamplesPerPixel must be set and BitsAllocated must be a multiple of 8

Hm, could you please check if this liver.dcm is working on Google's implementation? Just to sort out any issues in pydicom-seg.
When using dcmdump there is a warning about an odd PixelData length, if Rows*Columns*NumberOfFrames != 8 (not in this liver example though). This comes from numpy.packbits, which pads bits to a multiple of 8. But I think that this should be correct, according to the implementation in DCMTK.

There is also this odd-sized sample dataset in dcmqi that we tested against BrainLab and I believe confirmed the encoding is correct (that is the one that we used to debug encoding bug in DCMTK): https://github.com/QIICR/dcmqi/tree/master/data/segmentations/24x38x3.

Interesting - liver.dcm from qiicr works on google+OHIF, but liver-full.dcm (from pydicom_seg) does not.

liver.dcm from qiicr is not cropped, so it does not have that issue. Did you try the odd-sized sample I mentioned above?

liver.dcm from qiicr is not cropped, so it does not have that issue.

Both liver.dcm and liver-full.dcm are 512x512 with BitsAllocated of 1, but only the pydicom-seg one generates the error from google.

oh, sorry - I forgot there are two separate issues now being investigated.

Yes, 24x38x3 works

Getting back to the original issue, it would be good to set up a test in dcmjs to track down which versions of the files unpack correctly and which do not.

liver.dcm from qiicr is not cropped, so it does not have that issue.

Both liver.dcm and liver-full.dcm are 512x512 with BitsAllocated of 1, but only the pydicom-seg one generates the error from google.

I made a diff of both files and spotted two differences in the FileMeta header (and smaller differences in the actual DICOM, which should not cause any DicomWeb issues). pydicom overrode my specified TransferSyntaxUID from ExplicitVRLittleEndian to ExplicitVRBigEndian and the FileMetaInformationGroupLength is 12 Bytes longer using pydicom's serialization (I don't know why, but more bytes shouldn't be a problem). Maybe ExplicitVRBigEndian and bit packing is not supported? Below are new DICOM-SEGs with only differences in UIDs and Strings.
example-fix.zip

Sure, the change required is at the dcmjs level. We currently only support segmentations with the same size as the source data, as implementation for SEG support has thusfar been a "most common up" approach, but this shouldn't be too hard to change if you would like to submit a pull request.

@razorx89 yes, confirmed that example-fix.zip work on google's dicomweb and also has the same behavior as in your original screenshot, so it looks like your analysis is correct.  Do you think the original example.zip files were actually valid also and we should report the issue to google?
Regarding supporting cropped seg in dcmjs/ohif I agree with @JamesAPetts that we'd accept a PR but don't have a clear use case ourselves at the moment.  Is this something in the critical path, or just experimentation?

@razorx89 yes, confirmed that example-fix.zip work on google's dicomweb and also has the same behavior as in your original screenshot, so it looks like your analysis is correct. Do you think the original example.zip files were actually valid also and we should report the issue to google?

Great to hear! I think there shouldn't be a limitation according to the standard. DCMTK also allows writing with ExplicitVRBigEndian (source). The only problem i can think of with example.zip is that the bits were packed via np.packbits in little instead of big endian order. But that should only cause an invalid decoding of the segmentation, not an issue when transferring the data.

Regarding supporting cropped seg in dcmjs/ohif I agree with @JamesAPetts that we'd accept a PR but don't have a clear use case ourselves at the moment. Is this something in the critical path, or just experimentation?

Currently, it is nothing critical, I can disable it and add a warning in the documentation until we have a PR for this. I haven't looked much into dcmjs yet, but I will try to implement this functionality. In my opinion this feature would be an easy way to save storage space in a PACS with automatically generated AI reports. For pure research projects the cohort sizes might not cause issues in storage space, for clinical deployment it matters if the segmentation is a few MB or few KB (for thousands of studies).

@razorx89 you might want to consider if the savings in size are worth the various risks related to the complicated usage of the resulting objects.
Even such simple things as skipping empty slices apparently cause a lot of headaches for some presumably technically savvy imaging researchers, and took some time before it was supportedin BrainLab and OHIF.

I agree with @fedorov that there none of the implementation are sure to be feature-complete with respect to the standard and may not have the resources to be fully fleshed out.
Regarding file sizes, the thing that came up in both Slicer and OHIF was that labelmap-stye indexed segmentations save a lot of memory in the common case of non-overlapping segments but are not in the standard.

Thank you for your opinion on this. I agree, the support will be a problem not only in OHIF although it is standard conformant. Maybe I should deactivate this option by default and mark it as an experimental serialization feature.
At first it was only an idea to save some storage space when I was implementing the first version of the writer class. Now I got SurfaceSegmentationStorage DICOM-SEGs from one of our research partners and I am implementing a conversion script from SurfaceSegmentationStorage to SegmentationStorage via voxelization of the polygonal mesh (will be available in pydicom-seg soon). The voxelized mesh is not of the same size as the image, but I think I will just resample it to the referenced image series to make things simple outside of my package.

Now I got SurfaceSegmentationStorage DICOM-SEGs from one of our research partners

This is great - is read/write of DICOM surface segmentations going to be included in pydicom-seg?

Just to close the loop, Google got back to me and said it's a known issue they hope to fix.
On the topic of surface seg, there's a prototype slicer reader, but it would be cool to think about doing a more complete implementation.

Yes, I wrote a first simple conversion script and am able to generate SegmentationStorage DICOMs from a SurfaceSegmentationStorage (and display it in OHIF Viewer :+1:). Next step will be to get more examples to test it for robustness and refactor the code for inclusion in pydicom-seg. For writing I have also something in mind. But especially for round-trip conversions it is not straight forward, since IMO SurfaceSegmentationStorage DICOMs not only represent semantic segmentation, but also instance segmentation and thus we would require an additional indexing dimension when writing SegmentationStorage DICOMs. And then we are already back on the topic of compatibility with other frameworks/viewers. Without the additional indexing dimension, the individual surfaces per segment could be fused, but then the round-trip wouldn't work.
Maybe we should continue the discussion on SurfaceSegmentationStorage in https://github.com/razorx89/pydicom-seg/issues/18.

Sounds good.  Would be nice to have better support for surfaces but it's not in my critical path right now and not too common yet in the wild.

@razorx89, I would strongly advise never using ExplicitVRBigEndian.
We retired it from the standard ages ago (2006) to discourage its use (Sup 98 and CP-1549)
It should never be the default output from a toolkit.
It is good to test that it works though, since reading ExplicitVRBigEndian is supported by most toolkits.
David
PS. I had no trouble displaying either of your cropped segmentations (big or little endian VR), and validation of the file showed just a few errors that will not affect use of the PixelData;
% dciodvfy example-fix/liver-cropped.dcm                                                       Warning - Value dubious for this VR - (0x0010,0x0010) PN Patient's Name  PN [0] =  - Retired Person Name form
Warning - Value dubious for this VR - (0x0070,0x0084) PN Content Creator's Name  PN [0] = <pydicom_seg> - Retired Person Name form
Segmentation
Error - Missing attribute Type 1 Required Element= Module=
Warning - Coding Scheme Designator is deprecated - attribute  =
Warning - Coding Scheme Designator is deprecated - attribute  =
Error - Empty attribute (no value) Type 1C Conditional Element= Module=

Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing
Please try and re-open if the issue persists


Fixes #906
Signed-off-by: Fazlul Shahriar<EMAIL_ADDRESS>

Thanks!


feat: support admin version

Fix #17

Revamped options UI will collapsable areas
Added new area for development features (incl. "test sidekick locally")

:tada: This PR is included in version 4.1.0 :tada:
The release is available on:

GitHub release
v4.1.0

Your semantic-release bot :package::rocket:


Add test support for aarch64_windows

@gdams can you please close this draft PR, and recreate it using a developer branch?  We do not want branches created directly off of master.


Show only changed columns does not include non-common columns

Would it make sense for the "show only changed" option to include also columns which are not present across all selected experiments? The value for an experiment which did not use this column would be NaN, which is different from the value of an experiment which has a value in this added column. Hence, it would classify as "changed" between experiments with this definition.

Actually, after I queued another experiment and hid another set of columns, the column I was looking for showed up.


Introduce Continue Button

This PR introduces the continue button.
The button will direct the user to their current progress for the current chapter.

This PR introduces a new common function to make this button functional.

@benalleng
Finally did it! 🚀
Please have a look at my implementation.

Updated from 17e27d332600dc8623b3593a68300fb1159e2dff to fa8222836f73ee29c5380cf5c3bba791e8641420 (pr477.01 -> pr477.02, diff)
Addressed @benalleng comment

Used keysMeta[progress].path to set the href.
Updated isBetweenChapter logic to be true only for the current chapter.
Removed the redundant progressChapterMetaMapper.tsx file.

However, we would need to include some logic to allow quitting the game to save progress at the end screen.

This is one hurdle we need to figure out before allowing skipping outros.
Only after saving progress at the CH1OUT2, we shall logically be allowed to progress to CH2INT1. But skipping outros will create contradictory logic here.

technically speaking their progress is still in CH2 CH2OUT1 so we either need to
Allow any action on the end screen saves to the next chapter; quitting, saving, and continuing
*This is most likely the easiest solution and the most straightforward, circumstantially it will also address the comment i quoted above
make sure outro progress is not tracked, I am still directed to the page but the progress goes as such, CH2MIN1 -> CH3INT1

Both seem reasonable approaches to go forward with. However, though solution-1 might be easier to implement, I prefer solution-2 for its logical simplicity.
As far as I can plan logic in my head, always skipping the last lesson of every chapter while tracking progress will not create any logical overhead for the rest of the codebase.

Updated from fa8222836f73ee29c5380cf5c3bba791e8641420 to bac8dd5e6e4f29eb6dff0ef11089a84dcec48383 (pr477.02 -> pr477.03, diff)
Addressed @benalleng comment
Update:

Removed the following logic.

isBetweenChapter = ... && progress !== chapterLessons.pop() && ...

Updated from bac8dd5e6e4f29eb6dff0ef11089a84dcec48383 to 74a06b5660ba978939db00ba84a08f027d820bd0 (pr477.03 -> pr477.04, diff)
Addressed @benalleng comment
Changes:

Updated isBetweenChapter logic to be false when the player is at the very last lesson in the game.

@benalleng

...continue button on the very last lesson but I think that is an optional add.

Well if an optional add makes this PR better, I will always be glad to include it.
Thanks a lot, @benalleng, for your thorough review! 🙌

tACK! I tried going back and from from chapters overview page to various challenges and event intro/outro. Worked like a charm. Great work!
Let's address the continue button on last challenge separately because I believe that is being discussed #480.


Automate testing

fixes #9
Automates testing cross windows and linux with nextest a library that offers faster testing operations than cargo test among other cool features like identifying leaky, nondetermistic, etc tests. Here for benchmarking comp
Couldn't get code coverage to work quickly with the new compiler functionality so that will be in a separate PR. Lots of unnecessary commits here so you can squash and merge it.

results can be seen here
I have just updated it to only run on PR's instead on every push.

this looks great! thanks a lot
i'm going to go ahead and merge it


Typo "a Azure"→"an Azure"

Describe the bug
https://learn.microsoft.com/en-us/cli/azure/postgres?view=azure-cli-latest

Related command
nothing
Errors
nothing
Issue script & Debug output
nothing
Expected behavior
nothing
Environment Summary
nothing
Additional context
No response

Thank you for opening this issue, we will look into it.

Fixed in 7702.
@yonzhan Please close this one as resolved. Thanks!


Make batch version of aria2_helper

It would be great if anyone can help with this. This would give Windows users a better download experience.

Closing because obsolete


Scalable version queries

Summary
Querying for an application version is currently unsupported (during handshakes). My initial thoughts indicate that there are two solutions:

modifying the module interface to return the supported versions
supporting gRPC routes for every application version

Both have their draw backs and (2) isn't scalable. I'd like to give this some more thought to determine if there's a way we could abstract it so that it can scale without introducing more constraints required for IBC execution

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

To close this issue, we should modify the application module interface by adding another function. This function should perform application version negotiation and return the version to be used in the OpenTry step.
The relayer will choose the initial version in the OpenInit step, this will likely be chosen by the user controlling the relayer or by the application which triggers the OpenInit step (interchain accounts)
The version submitted in the OpenInit step will be submitted as an argument to the function being adding to the module interface. The function should look at the version selected in OpenInit and return the matching version to be used for OpenTry. Applications may choose to implement this in however fashion they choose.
ICS20 would simply return the "ics20-1" or perhaps an error if the counterparty version is unsupported. Assuming a second version of ICS20 eventually arises, we may expect this negotiation only to return a valid version if the counterparty version is supported. So if the counterparty used "ics20-1" in OpenInit, it returns "ics20-1". The same would be true if it used "ics20-2". If the counterparty used an unsupported version, say "ics20-5", then an error should be returned
ICS27 would have similar version negotiation. Assuming ICS27 also decides to interject the host chain account address into the version, then we would expect this function to generate interchain account adddress using the counterparty port ID and append this to the existing version (or use the associated protobuf version)
This function signature may look something like:
func NegotiateAppVersion(ctx sdk.Context, portID string, counterparty channeltypes.Counterparty, counterpartyVersion string) (version string, err error)

The name may be different (I haven't given it to much thought atm). I left off channelID in the function signature since it may not be known in advance by a relayer, but the portID should be known. I'm unsure if we should include the connection hops as well
We should assume some applications may return versions based on current state and thus access to the context may be useful

wdyt about adding this to the interchain-accounts milestone?

wdyt about adding this to the interchain-accounts milestone?

No preference, but this change should be made to the main branch

@damiannolan the version string passed into OnChannelOpenTry will look like ics27-1-<interchain-account-address>

I'll include the ICS27 version negotiation as part of #378 targeted for the interchain-accounts branch


chore: add @kocoa/core project

Codecov Report

:exclamation: No coverage uploaded for pull request base (next@028d03e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next      #54   +/-   ##
=======================================
  Coverage        ?   94.98%
=======================================
  Files           ?       20
  Lines           ?      837
  Branches        ?       50
=======================================
  Hits            ?      795
  Misses          ?       38
  Partials        ?        4

Flag
Coverage Δ

Packages
97.27% <0.00%> (?)

Samples
78.84% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 028d03e...e9cd3c2. Read the comment docs.


[T4A4][T10-A4]ZavierOng

Ready for review

Some comments added. Feel free to comment if you have any questions. Once done, you may the PR after reading comments.


Ensure app-operator and chart-operator in the MC are installed from the release

Currently app-operator and chart-operator in the MC are installed using app collections. In WCs they are installed from the release. We need to align the approach in MC.

[ ] Install app-operator and chart-operator from release in the MC
[ ] Remove app-operator and chart-operator form openstack-app-collection

Not an issue:
https://gigantic.slack.com/archives/C01BYMF6RN0/p1639137132242800?thread_ts=1639071375.217600&cid=C01BYMF6RN0
Thomas Fussell  1 hour ago
I'm not sure that's right. There is one MC app-operator for MC apps. Then there's one MC app-operator for each WC running in the MC. And it installs chart-operator in the WC. To the best of my knowledge we're doing it right.

pawel  7 minutes ago
Yes and this is not right in the current setup. We should install app/chart-operator the same way in both

pawel  6 minutes ago
I'm wondering now how we could make another WC an MC with all of that
New

Thomas Fussell  4 minutes ago
Oh, so this is towards making the MC more like a WC? I will have to think through it a bit more.

Thomas Fussell  1 minute ago
I think app-operator should be installed by the app-collection as it is an MC thing. chart-operator should be installed by app-operator as in a WC. Not sure about the order when bootstrapping though.

pawel  1 minute ago
If that's the case than I'll close this issue

pawel  < 1 minute ago
Possibly when turning WC into a MC we should "disconnect" it first from the original MC (edited)


Add support for offline and online methods to the external object on Android

Fixed IDE external object definition: Changed parameter access types of External Object to 'in'.
Refactor: renamed methodActivityAdd to methodActivityAddNumbersWithUI.
Add support for online and offline method AddNumbers.
Add support for offline method printMessage.

@luis-villagra-genexus Please check this commit.
I had to change the access types of some parameters to ensure the offline implementation of the new methods works.
Thanks.


created as a charity for hacktoberfest

@hacktoberfest

hey can i work on this issue?

hey can i work on this issue?

sure you can, then what is your contribution?


SeaportValidator tests

🚧
Just a foothold, needs better test abstractions.
TODO:

Add custom matcher for ErrorsAndWarnings (assert expected length and error order)
Add builder for expected ErrorsAndWarnings (create a nice API for setting up errors)
Extract and abstract order setup.

Codecov Report
Patch coverage has no change and project coverage change: -0.01 :warning:

Comparison is base (ad44d0d) 99.96% compared to head (c9c457b) 99.95%.

:exclamation: Current head c9c457b differs from pull request most recent head d629ead. Consider uploading reports for the commit d629ead to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1212      +/-   ##
==========================================
- Coverage   99.96%   99.95%   -0.01%
==========================================
  Files          47       47
  Lines        2653     2415     -238
  Branches      396      354      -42
==========================================
- Hits         2652     2414     -238
  Misses          1        1

Flag
Coverage Δ

foundry
?

production
99.91% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 29 files with indirect coverage changes

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


Add floating widget

I'm a strong enthusiast user of your work.
Can you implement, like Juggluco, the floating widget with colors in rage, out, ecc, value, etc?
I use this widget on my android radio (not android auto), over Agama and user radio interfaces (like google maps, etc)
Thanks for your hard work

Hi,
as this is part of Juggluco, I´m not sure, if it is really needed.
But you are right, the colors and delta you do not have in the Juggluco version.
At the moment, there is not much time and I´m on holiday for the next time.
So it will take some time...

Thanks for the reply, good holiday!

Hi,
can you give me some more information, you have a android radio (not android automotive OS?).
How Agama and the user radio interface are working? What can you access from the mobile phone? Also notifications?
Or only the floating widget?
Thank you!
Regards, Michael

Android radio: atoto s8 premium
Android 12
Can install juggluco for mirror, and apk Glucodatahandler.
Agama its a Launcher
Il ven 1 set 2023, 10:37 pachi81 @.***> ha scritto:

Hi,
can you give me some more information, you have a android radio (not
android automotive OS?).
How Agama and the user radio interface are working? What can you access
from the mobile phone? Also notifications?
Or only the floating widget?
Thank you!
Regards, Michael
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1702381497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSAA62KOIEHZTUMISLXYGNEXANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, this means, you install Juggluco and GlucoDataHandler on the radio. Juggluco receives the values from the phone app and send them to GlucoDataHandler. Correct!?
What about the notifications in Juggluco and GlucoDataHandler? GlucoDataHandler also have normal widgets, can you access them? Or is the floating widget the only possibility?

Normale widget can't be access on Android radio.
Not only with Agama or other Launcher, but when you drive and you have for
example gmaps or other, you can't have a widget overlay, for example
Il ven 1 set 2023, 11:17 pachi81 @.***> ha scritto:

Ok, this means, you install Juggluco and GlucoDataHandler on the radio.
Juggluco receives the values from the phone app and send them to
GlucoDataHandler. Correct!?
What about the notifications in Juggluco and GlucoDataHandler?
GlucoDataHandler also have normal widgets, can you access them? Or is the
floating widget the only possibility?
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1702436371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QTNMTBKC34QPHQJESLXYGR4DANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

And notifications are also not possible!?
But I have checked an example for the floating widget, and it seems to be similar to the normal widgets.
So maybe I can use the most of the code and layout from the normal widgets for that, which make it easier for me.

And popup notifications, like when you are receiving a new message from other apps. But yes, I also think, that the floating widget is the better solution...

Popup notification can't display over Launcher or over some apps
Widget floating must be the best thing, for all android stock  car dashboard
Il ven 1 set 2023, 11:40 pachi81 @.***> ha scritto:

And popup notifications, like when you are receiving a new message from
other apps. But yes, I also think, that the floating widget is the better
solution...
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1702468768,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QWG2ZQI7WL2WN2BXUTXYGURLANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, thank you for the information. As soon, I have time, I will try to implement it.

Here ist the first try...
You can activate in settings in the notification section.
On the first activation, you have to set the permission and go back. If it does not appear after setting the permission, disable and enable the setting in GlucoDataHandler again.
I know, it is a little bit small at the moment, but it should work...
GlucoDataHandler_<IP_ADDRESS>.zip

On my Phone work, only i have two fix for suggest :

Press long 5 sec to dismiss, like juggluco

Press normally and launch Glucodatahandler or juggluco

in my phone with normal text size, house, second and delta its half cut
maybe a settings for size of carachter?

Next hour, After my phisioterapy for cistica fibrosis, i can test on the
radio.
Great work you are a magic!
Il ven 1 set 2023, 17:29 pachi81 @.***> ha scritto:

Here ist the first try...
You can activate in settings in the notification section.
On the first activation, you have to set the permission and go back. If it
does not appear after setting the permission, disable and enable the
setting in GlucoDataHandler again.
I know, it is a little bit small at the moment, but it should work...
GlucoDataHandler_<IP_ADDRESS>.zip
https://github.com/pachi81/GlucoDataHandler/files/12499465/GlucoDataHandler_<IP_ADDRESS>.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1702935100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QTNTJVD2HMYBSHPLDTXYH5OTANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi,
thank you for the feedback! I increased the size. For me, it is nearly to big, now. I have to find a good way...
But the bigger one is maybe better for car...
At the moment, I don´t know, how to implement the on-click event for calling the app or closing the widget, because at the moment I´m using the touch event for moving the widget around...
I have to check, maybe I find the way, how Juggluco have implemented it.
GlucoDataHandler_<IP_ADDRESS>.apk.zip

Please also try this version for checking cut off the time...
Thank you!
GlucoDataHandler_<IP_ADDRESS>.zip

On phone its cut, see attachments
Il ven 1 set 2023, 22:20 pachi81 @.***> ha scritto:

Please also try this version for checking cut off the time...
Thank you!
GlucoDataHandler_<IP_ADDRESS>.zip
https://github.com/pachi81/GlucoDataHandler/files/12501288/GlucoDataHandler_<IP_ADDRESS>.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1703278646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSI23PLL26HSFVPXH3XYI7PLANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Cant reply with attachments, too big for github
Il ven 1 set 2023, 22:20 pachi81 @.***> ha scritto:

Please also try this version for checking cut off the time...
Thank you!
GlucoDataHandler_<IP_ADDRESS>.zip
https://github.com/pachi81/GlucoDataHandler/files/12501288/GlucoDataHandler_<IP_ADDRESS>.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1703278646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSI23PLL26HSFVPXH3XYI7PLANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Also with the <IP_ADDRESS> version?

Il ven 1 set 2023, 22:20 pachi81 @.***> ha scritto:

Please also try this version for checking cut off the time...
Thank you!
GlucoDataHandler_<IP_ADDRESS>.zip
https://github.com/pachi81/GlucoDataHandler/files/12501288/GlucoDataHandler_<IP_ADDRESS>.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1703278646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSI23PLL26HSFVPXH3XYI7PLANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

What kind of phone do you have? Maybe I can reproduce it in an emulator.

Oppo Find X2 pro.do you have an email for Send attachments?
It.s 5Mb , 7.5mb, etc
Il sab 2 set 2023, 14:56 pachi81 @.***> ha scritto:

What kind of phone do you have? Maybe I can reproduce it in an emulator.
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1703825954,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QUNDRLHZFXVTMAF56LXYMUJDANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

If the files are so big, so better upload it here:
https://1drv.ms/f/s!AvqtWFwQmBjwi2GueEaUdaIS-Ess
If it does not work, my mail<EMAIL_ADDRESS>

New version with fixed size, so nothing should be cut...
I also add short click to open Juggluco and long click (4s) to close the floating widget (both only works, if you do not move the widget...).
GlucoDataHandler_<IP_ADDRESS>.apk.zip

Tested, not fix the cut.
Touch and launch juggluco work perfectly.
Press long and hide not work, Hide and  After 1 sec restart, sometimes work
and hide
Il lun 4 set 2023, 16:33 pachi81 @.***> ha scritto:

New version with fixed size, so nothing should be cut...
I also add short click to open Juggluco and long click (4s) to close the
floating widget (both only works, if you do not move the widget...).
GlucoDataHandler_<IP_ADDRESS>.apk.zip
https://github.com/pachi81/GlucoDataHandler/files/12514603/GlucoDataHandler_<IP_ADDRESS>.apk.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1705370567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSCSDNMLCLWTBDFAYLXYXRBZANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

.6 its very small and cut on the radio
Il mar 5 set 2023, 01:58 Lost Boy @.***> ha scritto:

Tested, not fix the cut.
Touch and launch juggluco work perfectly.
Press long and hide not work, Hide and  After 1 sec restart, sometimes
work and hide
Il lun 4 set 2023, 16:33 pachi81 @.***> ha scritto:

New version with fixed size, so nothing should be cut...
I also add short click to open Juggluco and long click (4s) to close the
floating widget (both only works, if you do not move the widget...).
GlucoDataHandler_<IP_ADDRESS>.apk.zip
https://github.com/pachi81/GlucoDataHandler/files/12514603/GlucoDataHandler_<IP_ADDRESS>.apk.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1705370567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSCSDNMLCLWTBDFAYLXYXRBZANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

It is cut in width or height?
To close it, you have to touch at least for 4s and do not move it...
Maybe the movement detection is too sensitive, but it is hard to decide either the user want to move or want to close... And I don´t want to add a close button...

Width and height.
I send in the previous message the collage screenshots
Il mar 5 set 2023, 09:45 pachi81 @.***> ha scritto:

It is cut in width or height?
To close it, you have to touch at least for 4s and do not move it...
Maybe the movement detection is too sensitive, but it is hard to decide
either the user want to move or want to close... And I don´t want to add a
close button...
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1706109215,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QWBCTEOHU6GFD63Q4LXY3KC7ANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Which Android version your Oppo phone have?

So, next try...
I changed the layout completely...
I added also a resize slider in the settings, so you can increase the widget size.
Also improved the long click to close...
GlucoDataHandler_<IP_ADDRESS>.zip

A 13 on phone, A12 on Android car radio atoto
Il mar 5 set 2023, 19:52 pachi81 @.***> ha scritto:

Which Android version your Oppo phone have?
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1707052033,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QQ2YRNR6C2Y22YZHXTXY5RELANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank, unfortunately I could not reproduce the problem in emulator.
But the new version .7 should work, now. (I hope...)

I test many and many hours on phone and also in a road trip of 8 hours on
android radio.
For me it seems latest version fix all problem, sometimes not
stay persistent overlay on the agama launcher or, in the phone, but it's a
minor problem.
Il giorno mer 6 set 2023 alle ore 09:36 pachi81 @.***>
ha scritto:

Thank, unfortunately I could not reproduce the problem in emulator.
But the new version .7 should work, now. (I hope...)
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1707826333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QRAXCN4C6QHYEAE34DXZARZJANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

sometimes not stay persistent overlay on the agama launcher or, in the phone, but it's a minor problem.

What do you mean? Don't really understand.
But good to know, that it works, now :-)

I mean this :
Sometimes the widget disappear when i launch some apps, and reappear After,
or stay on background
Il gio 7 set 2023, 22:54 pachi81 @.***> ha scritto:

sometimes not stay persistent overlay on the agama launcher or, in the
phone, but it's a minor problem.
What do you mean? Don't really understand.
But good to know, that it works, now :-)
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1710758386,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QWZWQU6RJWTP37ATR3XZIX67ANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

That is really strange! I have not recognized on my phone, yet.
Do you have any Logreader App, like this one ?
If possible can you activate logging for my app and when it dissappears send the log to me. Maybe I will see anything, which causes this problem.

One more question, does it always happen, when you launch the same app or is it more a sporadic issue?

More sporadic issue
Il giorno ven 8 set 2023 alle ore 08:15 pachi81 @.***>
ha scritto:

One more question, does it always happen, when you launch the same app or
is it more a sporadic issue?
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1711132641,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QUSSQGCS3JW7DKHL2LXZKZXNANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

:-( Ok, if it will be reproduceable, it is fixable :-D
Have you activated Play Protect in the Google Play Store? If yes, try to deactivate it, because the Play Protect like to close apps, which are not coming from Play Store...
And it sound like, that my app is closed and on new value it is re-started (in the background). Otherwise I have to create a foreground service, which will not closed such often...
One more thought: are you using the notification of GlucoDataHandler? If not, can you activate it and check, if it improves the problem?
Thank you very much for you testing and help!!!

And one more thing. I think, I have the same problem. In the version, where the last pos of the widget was not saved, it happens, that it re-appears in the center (sounds like a restart). So maybe I can test and log it on my device.
I will have a look.

No play protect
Yes notification firm on notification center
Il ven 8 set 2023, 10:03 pachi81 @.***> ha scritto:

And one more thing. I think, I have the same problem. In the version,
where the last pos of the widget was not saved, it happens, that it
re-appears in the center (sounds like a restart). So maybe I can test and
log it on my device.
I will have a look.
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1711250165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSJMCWSXFO56SB2V6DXZLGOBANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

If i Remember correctly, same for me
Il ven 8 set 2023, 10:03 pachi81 @.***> ha scritto:

And one more thing. I think, I have the same problem. In the version,
where the last pos of the widget was not saved, it happens, that it
re-appears in the center (sounds like a restart). So maybe I can test and
log it on my device.
I will have a look.
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1711250165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSJMCWSXFO56SB2V6DXZLGOBANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks! Great news
Il giorno ven 8 set 2023 alle ore 14:23 pachi81 @.***>
ha scritto:

So, I have checked with the old version, where the widget always starts in
the center and check the logcat. The app restarts from time to time (don´t
know why, maybe some android optimizations).
If I have time, I will make the notification as foreground-notification,
so the app should not be killed (I hope).
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1711586289,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QR7UGPISPQTUVBWTT3XZME3ZANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi,
here is a new version with foreground service (Notification must be activated).
In the emulator, the notification gets colored background which looks strange, but on my phone I had not problems. So it is hopefully only a emulator problem...
GlucoDataHandler_<IP_ADDRESS>.apk.zip

I have a strange colour notification on the notification center, on dark
night mode
Others bug seems fixed, congrats, well done
I test tomorrow on the radio
Il lun 11 set 2023, 13:06 pachi81 @.***> ha scritto:

Hi,
here is a new version with foreground service (Notification must be
activated).
In the emulator, the notification gets colored background which looks
strange, but on my phone I had not problems. So it is hopefully only a
emulator problem...
GlucoDataHandler_<IP_ADDRESS>.apk.zip
https://github.com/pachi81/GlucoDataHandler/files/12575245/GlucoDataHandler_<IP_ADDRESS>.apk.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1713660655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QR6EZA2TOQSYWILXDDXZ3WBHANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Il lun 11 set 2023, 13:06 pachi81 @.***> ha scritto:

Hi,
here is a new version with foreground service (Notification must be
activated).
In the emulator, the notification gets colored background which looks
strange, but on my phone I had not problems. So it is hopefully only a
emulator problem...
GlucoDataHandler_<IP_ADDRESS>.apk.zip
https://github.com/pachi81/GlucoDataHandler/files/12575245/GlucoDataHandler_<IP_ADDRESS>.apk.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1713660655,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QR6EZA2TOQSYWILXDDXZ3WBHANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have a strange colour notification on the notification center, on dark night mode

Can you make a screenshot?

also send this night in the previous mail
Il giorno mar 12 set 2023 alle ore 07:14 pachi81 @.***>
ha scritto:

I have a strange colour notification on the notification center, on dark
night mode
Can you make a screenshot?
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1714984710,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QX6GPYNS7F65IOH4KLXZ7VTZANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please send direct to my mail (pachi81@web.de). It seems to be removed from GitHub, because there is no attachement.

All seems fixed. Today i test more on the Road with radio.
Il mar 12 set 2023, 13:54 pachi81 @.***> ha scritto:

Please try this version. It also add Tasker support for de-/activating the
widget.
GlucoDataHandler_<IP_ADDRESS>.zip
https://github.com/pachi81/GlucoDataHandler/files/12586052/GlucoDataHandler_<IP_ADDRESS>.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1715581903,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QQGK2STNMBR27FBA6TX2BEPHANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Tested on radio, there is some strange thing :
slider to adjust the size of the widget  : not adjust the dimension of the
entire widget, only the text
Il giorno mer 13 set 2023 alle ore 02:56 Lost Boy <
@.***> ha scritto:

All seems fixed. Today i test more on the Road with radio.
Il mar 12 set 2023, 13:54 pachi81 @.***> ha scritto:

Please try this version. It also add Tasker support for de-/activating
the widget.
GlucoDataHandler_<IP_ADDRESS>.zip
https://github.com/pachi81/GlucoDataHandler/files/12586052/GlucoDataHandler_<IP_ADDRESS>.zip
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1715581903,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QQGK2STNMBR27FBA6TX2BEPHANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, the slider only adjust the text-size, but the widget should be updated...
So, the text will be cut after resize? What happens, if a new value will be there?
If you disable and enable after resizing, does the dimensions are correct?

I create a new version, where I also had to do some changes on the layout (hopefully you will not recognize it).
I also added an option to change the style of the floating widget.
And for you problem on the radio, I remove and re-add the view on changes to the settings.
Please try, if this solves the problem on the radio.
GlucoDataHandler_<IP_ADDRESS>.apk.zip

The size its the same on radio only text was adjust with slider
on smartphone adjust size and text
This evening test the new version and report.
Thanks a lot for the hard work
Il giorno mer 13 set 2023 alle ore 12:06 pachi81 @.***>
ha scritto:

Ok, the slider only adjust the text-size, but the widget should be
updated...
So, the text will be cut after resize? What happens, if a new value will
be there?
If you disable and enable after resizing, does the dimensions are correct?
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1717333419,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QUD5I5P37IZJWIQ77DX2GAQTANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

With latest version, all work on phone and radio.
Style of widget, size variable, on-top of the apps, etc.
You can release the latest version, work very good!
Il mer 13 set 2023, 13:03 Lost Boy @.***> ha
scritto:

The size its the same on radio only text was adjust with slider
on smartphone adjust size and text
This evening test the new version and report.
Thanks a lot for the hard work
Il giorno mer 13 set 2023 alle ore 12:06 pachi81 @.***>
ha scritto:

Ok, the slider only adjust the text-size, but the widget should be
updated...
So, the text will be cut after resize? What happens, if a new value will
be there?
If you disable and enable after resizing, does the dimensions are correct?
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1717333419,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QUD5I5P37IZJWIQ77DX2GAQTANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Great news! Thank you for your feedback!
I haven't expected, that it takes so much time...
Just one more question, you are coming from Italy? Do you like to translate the app into italian?
Regards, Michael

Yes coming From Trento, how i can translate?
Il dom 17 set 2023, 10:49 pachi81 @.***> ha scritto:

Great news! Thank you for your feedback!
I haven't expected, that it takes so much time...
Just one more question, you are coming from Italy? Do you like to
translate the app into italian?
Regards, Michael
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1722427610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSJ7N67XJNCNLDDWNTX222SRANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Another questione :
Juggluco mirror Is very bad function for me, becauss ip of device change
every time on radio, with tethering.
You able to send value over ble From Glucodatahandler instance on One
device and another device with Glucodatahandler?
Same you act between phone and wear with Glucodatahandler.
This happens with every mirror, phone mother change ip on network home,
radio change ip when tethering phone ON, etc.
It's a wastw of time adjust ip on mirror every time, for example if i turn
on and off my car six times on a Road trip, i have to adjust the mirror ip
on radio because also tethering phone change ip phone
Same
Il dom 17 set 2023, 10:50 Lost Boy @.***> ha
scritto:

Yes coming From Trento, how i can translate?
Il dom 17 set 2023, 10:49 pachi81 @.***> ha scritto:

Great news! Thank you for your feedback!
I haven't expected, that it takes so much time...
Just one more question, you are coming from Italy? Do you like to
translate the app into italian?
Regards, Michael
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1722427610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QSJ7N67XJNCNLDDWNTX222SRANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I had a quick look and there seems to be a solution for bluetooth connection.
But not sure, when I can spend some time for playing around.
Dor translation, I will send you a file, when I'm ready.

Thank you wait for the file
Il dom 17 set 2023, 12:15 pachi81 @.***> ha scritto:

I had a quick look and there seems to be a solution for bluetooth
connection.
But not sure, when I can spend some time for playing around.
Dor translation, I will send you a file, when I'm ready.
—
Reply to this email directly, view it on GitHub
https://github.com/pachi81/GlucoDataHandler/issues/85#issuecomment-1722443791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJMW5QUS7MH2ZZQBSUHBGE3X23EV3ANCNFSM6AAAAAA3DZNMJ4
.
You are receiving this because you authored the thread.Message ID:
@.***>


flet publish broken

Description
Using flet publish does not create a functioning static web site. The web server runs successfully, however, now contents of the page is displayed.
With the minimum working example:
import flet as ft

def main(page: ft.Page):
    page.add(ft.Text("Simple App"))

    page.update()

if __name__ == "__main__":
    ft.app(target=main)

the application can be run using the desktop as well as the web browser version. However, after running
flet publish simple_app.py
the web site located in the dist directory. Running python -m http.server --directory dist launches the web server. But loading the site in the browser hangs indefinitely. The log produces is shown below:
Serving HTTP on <IP_ADDRESS> port 8000 (http://<IP_ADDRESS>:8000/) ...
<IP_ADDRESS> - - [14/Jul/2023 22:13:47] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:47] "GET /flutter_service_worker.js?v=1209606426 HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:47] "GET /main.dart.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:47] "GET /assets/AssetManifest.json HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:47] "GET /index.html HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:47] "GET /assets/FontManifest.json HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:48] "GET /flutter_service_worker.js?v=1209606426 HTTP/1.1" 304 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:48] "GET /flutter_service_worker.js?v=1209606426 HTTP/1.1" 304 -
<IP_ADDRESS> - - [14/Jul/2023 22:13:50] "GET /app.tar.gz HTTP/1.1" 200 -

Describe the results you expected:
I expect to see the web site, when loading it in the browser.
Additional information you deem important (e.g. issue happens only occasionally):
Flet version (pip show flet):
Name: flet
Version: 0.8.2
Summary: Flet for Python - easily build interactive multi-platform apps in Python
Home-page:
Author: Appveyor Systems Inc.
Author-email<EMAIL_ADDRESS>License: Apache-2.0
Location: /data/niklas/PycharmProjects/pythonProject/venv/lib/python3.10/site-packages
Requires: copier, flet-runtime, packaging, pydantic, qrcode, watchdog, websocket-client, websockets
Required-by:

Operating system:

Additional environment details:

Try removing if __name__ == "__main__": condition.

Just from facing thesame issue and Feodor's suggestion fixed it.
Thanks Feodor.

I can confirm, that this fixes the issue. I now only have the remaining problem that my actual application does not appear to work with flet publish. But this would then be a separate ticket.
Thank you for the quick help!

I can confirm, that this fixes the issue. I now only have the remaining problem that my actual application does not appear to work with flet publish. But this would then be a separate ticket.
Thank you for the quick help!