timeseries plugin

Hi pyatyispyatil,
I just wanted to give you visibility of my fork

I have converted the examples to typescript
enforced prettier on the whole code-base (including examples and config outside of /src/
introduced a new plugin for rendering time-series data
refactored to the example to have explicit usage there there it is explicit which plugins are configured an enabled
demonstrated the use of multiple instances of the same plugin type.
I have struggled to .ts convert the test-data code fully - i have some typings and it is better - but therea re still some any[] there - which i haven't fully typed.

I can spend a few ours changing this to your liking...
James

It would be nicer if you could separate prettier changes to its own PR
that would make timeseries plugin isolated to its own PR and easier to review

It would be nicer if you could separate prettier changes to its own PR that would make timeseries plugin isolated to its own PR and easier to review

Agreed; This has conflated into to heaps of things....
I started off breaking off branches & PRs - It just has an overhead maintaining them.

Man, very cool pr, but unfortunately it seems that the feature is a little incomplete - in chrome under macOS, something strange happened to the flame chart for some reason.

It would be nicer if you could separate prettier changes to its own PR that would make timeseries plugin isolated to its own PR and easier to review

Agreed; This has conflated into to heaps of things....
I started off breaking off branches & PRs - It just has an overhead maintaining them.

yeah I think it could be separated as following:
PR for example conversion to TS
PR for prettier changes
PR for timeseries plugin

When scrolling, a glitch is noticeable: the extreme points seem to be attached to the edge of the screen, and because of this, the graph seems to change slightly. Apparently, you need to render part of the graph behind the screen (last and first points).

https://github.com/pyatyispyatil/flame-chart-js/pull/44#issuecomment-1366194472 This happens if the screen is not very large. And if you try to move the toggle plugin, then for some reason more additional plugins will be resized.

When scrolling, a glitch is noticeable: the extreme points seem to be attached to the edge of the screen, and because of this, the graph seems to change slightly. Apparently, you need to render part of the graph behind the screen (last and first points).

thank-you - will try and fix - and let you know.

It would be nicer if you could separate prettier changes to its own PR that would make timeseries plugin isolated to its own PR and easier to review

Agreed; This has conflated into to heaps of things....
I started off breaking off branches & PRs - It just has an overhead maintaining them.

yeah I think it could be separated as following: PR for example conversion to TS PR for prettier changes PR for timeseries

Man, very cool pr, but unfortunately it seems that the feature is a little incomplete - in chrome under macOS, something strange happened to the flame chart for some reason.

let me dig.

@jburrow It looks like most of the code style updates are already in the master. Can you update this PR so that we can start reviewing it?)

@jburrow It looks like most of the code style updates are already in the master. Can you update this PR so that we can start reviewing it?)

I have thrown away most of the stuff i had and gone back to master.

Overall, it looks good, but it needs to be finished a little more.)

The code is dirty, with a lot of commented-out code - this should not be.
It is better to leave the default flame chart in the example that was before this pull request and add your new plugin to it.
The visual part does not look very good - when scrolling, the extreme value disappears and an empty area is obtained on the chart.
A little earlier in this pull request there was a broken line instead of a stepped graph - maybe do both and add the ability to configure this in the parameters? It would also be cool to add smooth lines, but this can be added later.
For some reason, when hovering, I don’t get a tooltip, although I see that you described it in the code.
It would be very cool to be able to render several charts in one timeseries plugin and pass the color not as the second argument of the plugin constructor, but in the data itself.

Agreed. 100%
Will work thru this points shortly.

Overall, it looks good, but it needs to be finished a little more.)

The code is dirty, with a lot of commented-out code - this should not be.
Agreed - This is just a draft right now - i will address before finalizing
It is better to leave the default flame chart in the example that was before this pull request and add your new plugin to it.
**Agreed - But I think we could improve how the default behavior works; Either with a FlameChart Factory method can build a flame chart from data - that then leaving the class constructor to be super clean with just plugins passed in.

In addition - i wonder if the plugins should have "supports toggle" boolean - so that there isn't the boilerplate for the toggle behaviour - what do you think?**

The visual part does not look very good - when scrolling, the extreme value disappears and an empty area is obtained on the chart.
Yes - i am now fixing this stuff up.

A little earlier in this pull request there was a broken line instead of a stepped graph - maybe do both and add the ability to configure this in the parameters? It would also be cool to add smooth lines, but this can be added later.
Yes - an option to toggle between the line-chart style would be good idea

For some reason, when hovering, I don’t get a tooltip, although I see that you described it in the code.
** Yes - will fix - just modifying the internals of the render atm"

It would be very cool to be able to render several charts in one timeseries plugin and pass the color not as the second argument of the plugin constructor, but in the data itself.
** Maybe? - Why not just have multiple instances of the plugin? -- just same smae but different? **

I think it is ready for review - let me know

I think it is ready for review - let me know @pyatyispyatil ty

It would be great if you resolved the conflicts first.)

I think it is ready for review - let me know @pyatyispyatil ty

It would be great if you resolve the conflicts first.)

done - i noticed you hadn't run "npm run pretty" before your last merge. Would it be possible to put that as a commit hook?

@pyatyispyatil  what you think? I think there is a big introduced in where packaged. JSON is pointing to wing location in first folder... Now tsc is generating in dist/src

I have address the issue identified ^ with the commit above  https://github.com/pyatyispyatil/flame-chart-js/pull/44/commits/599429e13d67aec61073c62d6ab5393079188ef4

By the way, I did not understand the meaning of the numbers on the left of the graph at all. I didn't specifically look at the code to understand UX. Maybe add at least the designation min max?

done - i noticed you hadn't run "npm run pretty" before your last merge. Would it be possible to put that as a commit hook?

I think we should change the npm run lint command to check for all missing files and readme.md.

By the way, I did not understand the meaning of the numbers on the left of the graph at all. I didn't specifically look at the code to understand UX. Maybe add at least the designation min max?

TBH - I am not sure I like it either you suggestion the word "min value" "max value" post fix the number value ${max} max value
TBH - I would happily hide the feature behind a setting....

@pyatyispyatil - You have given a lot of feedback on this PR - some of this is programming style, some of it is bug's i introduced because i don't know better! [sorry for that]
Given you have strong vision for your project from functionality and code style - would you like to take ownership and just change this code to your liking?

Given you have strong vision for your project from functionality and code style - would you like to take ownership and just change this code to your liking?
Unfortunately no. If you have already taken up something, then be kind to bring it to the end.)

Let

Given you have strong vision for your project from functionality and code style - would you like to take ownership and just change this code to your liking?

Unfortunately no. If you have already taken up something, then be kind to bring it to the end.)

Understood - I have reverted everything.
Issues I have not addressed;

Support multiple time-series in a plugin - is this a deal breaker? if so please tell me now.
Refactored internal implementation of render - There are still 2 enumerations, one to find the right data and one to render; My implementation requires this in-order to correct handle the data-points either side of the selected range. There might be a better algo - but i couldn't think of it. I did profile this and it looked ok. Can you give more guidance around performance acceptations criteria?

I think there is a problem with the rollup config - possibly due to the use of the builtins() - Which confuses the typechecking not know if it is browser or node? I am not an expert - but here is example
REPO : npm start

What Nikolay says, I agree with
Writing a plugin should not require changing a bunch of other unrelated stuff
If there is a bug we should first open an issue and try to fix it in a separate PR
Then the new plugin PR should be very clear and only care about the plugin functionality itself

I think there is a problem with the rollup config - possibly due to the use of the builtins() - Which confuses the typechecking not know if it is browser or node? I am not an expert - but here is example
REPO : npm start
Well, as I see it, this bug is not reproducible on the master branch.

You can try deleting the node_modules folder and running npm i. Maybe this will help you.)

I think there is a problem with the rollup config - possibly due to the use of the builtins() - Which confuses the typechecking not know if it is browser or node? I am not an expert - but here is example
REPO : npm start

Well, as I see it, this bug is not reproducible on the master branch.
You can try deleting the node_modules folder and running npm i. Maybe this will help you.)

npm i
FIXED: thank-you and sorry for false report

Support multiple time-series in a plugin - is this a deal breaker? if so please tell me now.

No, you can only remove redundant creating of several plugins and keep possibility to add only one chart. I will add possibility for creating several charts later.

Refactored internal implementation of render - There are still 2 enumerations, one to find the right data and one to render; My implementation requires this in-order to correct handle the data-points either side of the selected range. There might be a better algo - but i couldn't think of it. I did profile this and it looked ok. Can you give more guidance around performance acceptations criteria?

I added a comment above about this https://github.com/pyatyispyatil/flame-chart-js/pull/44#discussion_r1064683060.
You can profile rendering while zooming in/out and scrolling left/right. You should set CPU throttle x4-x6 and try to render 100k-1000k points. I think this plugin should not take more than 0.1ms to render. The requirements may be too high, but still I would like to get as close as possible to this value.

I believe i have addressed you previous comments - please consider this PR

Be great if we could close and merge this PR

@jburrow There are a few minor fixes left and I'll be ready to push the merge button.) You did a good job on the pull request, but there are still a couple of things that need to be fixed to improve the code and performance. Please don't think I'm being too picky - graphs and charts are actually very demanding, and creating unnecessary entities (objects, arrays) ends up having a big impact on framerate.

And tooltip still broken.(

I think have done everything you asked now;
Please note - if you tooltip over the flame-chart first the tooltip is broken... but as long as you don't it works just fine...
I think this is a bug somewhere else in the render engine? or a lack of undertanding on my part.

Please can you run "npm run pretty" on master :)

i am at a loss now - just merged your latest changes which re-writes the example app :( - i could support timeseries there but tbh - given you have a strong opinion on how this should work - maybe you should take it from here?

Please can you run "npm run pretty" on master :)

Why is this needed? On the master, everything is fine with linting, but at the same time, your branch contains many problems.

i am at a loss now - just merged your latest changes which re-writes the example app :( - i could support timeseries there but tbh - given you have a strong opinion on how this should work - maybe you should take it from here?

Okay, I'll add.)

Please can you run "npm run pretty" on master :)

Why is this needed? On the master, everything is fine with linting, but at the same time, your branch contains many problems.

I was referring to the fact the configs in the route of your project haven't be formatted - anyhow - leaving it to you.

I have removed everthing but the plugin - as you can choose how to use - in the default|customized route etc.
Please let me know if you can merge this or not.

I have removed everthing but the plugin - as you can choose how to use - in the default|customized route etc.
Please let me know if you can merge this or not.

I can’t merge yet, because  you still need to fix the bug with the tooltip from this thread https://github.com/pyatyispyatil/flame-chart-js/pull/44#discussion_r1083460210

And you have linting problems that are marked on CI.

And you have linting problems that are marked on CI.

I don't understand - I have ran npm run pretty - it doesn't update test-data.ts - ... it does update 5 files in teh route of the project thought.
How do i repro what vercel is doing....

I have removed everthing but the plugin - as you can choose how to use - in the default|customized route etc.
Please let me know if you can merge this or not.

I can’t merge yet, because you still need to fix the bug with the tooltip from this thread #44 (comment)

I have no development harness now - because it was removed when you re-wrote the app to be typescript.
I would need to re-write the a development harness - but i feel that whatever i do won't be aligned to your expectations.
What do you recommend i do?

And you have linting problems that are marked on CI.

I don't understand - I have ran npm run pretty - it doesn't update test-data.ts - ... it does update 5 files in teh route of the project thought.
How do i repro what vercel is doing....

npm run lint:fix

I have removed everthing but the plugin - as you can choose how to use - in the default|customized route etc.
Please let me know if you can merge this or not.

I can’t merge yet, because you still need to fix the bug with the tooltip from this thread #44 (comment)

I have no development harness now - because it was removed when you re-wrote the app to be react. I would need to re-write the a development harness - but i feel that whatever i do won't be aligned to your expectations.
What do you recommend i do?

Dude, I just want the code in the project to work well (without major bugs), and that it does not lead to unnecessary performance costs and passes all the checks in the pipeline. This package is already used by several projects and I would not like to ship something low-quality to them.)
Many of the comments were simply unfixed by you, which is why this pull request stuck in this status for so long.(
You can add initialization of your plugin to the new example to check how it works. And after that fix the bug that was described in the comments.


Problem  when calling the ListObjectsV2 operation: Access Denied

aws s3 sync --request-payer requester s3://public-blockchain-snapshots/bsc/erigon-snapshots-folder-latest/ /erigon/data/bsc/snapshots/
fatal error: An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied

This is most often the case when the computer you are running the command on does not have an AWS account configured.
Run aws configure or give the node a role.

I ready add below permission to my account
"aws-portal:ModifyBilling",
"aws-portal:ViewPaymentMethods",
"aws-portal:ModifyAccount",
"aws-portal:ViewAccount",
"aws-portal:ModifyPaymentMethods",
"aws-portal:ViewBilling",
"aws-portal:ViewUsage"
And other permission I need ？

You need S3 permissions, as your account will be billed for your requests.


Delete contract annotations

Port of https://github.com/dotnet/coreclr/pull/14136 to CoreRT

@dotnet-bot test OSX10.12 Release please


Notify bot owners if bot tries to send to a stream it does not have access to

They get a message if the stream does not exist; it would be good to also give them a message if the stream exists but access to it is denied.

This likely just involves catching the right errors and extending the send_pm_if_empty_stream code path to support additional cases.  It's possible what we actually want to do is rework that system somewhat to replace the validate_stream_id_with_pm_notification bundle of functions with raising a subclass of JsonableError with a few data attributes attached, and trigger the PMs via catching that exception?  I'm not sure, we'll need to play with it to see what works well.

@alexmv can you help me understand under what conditions we can restrict a bot access to a stream ?
Does that stream need to be private or there are some other conditions ?


Update routes

Codecov Report

Merging #343 (f8bf30b) into main (b62611f) will decrease coverage by 0.17%.
The diff coverage is 44.59%.

@@            Coverage Diff             @@
##             main     #343      +/-   ##
==========================================
- Coverage   70.27%   70.10%   -0.18%
==========================================
  Files         182      184       +2
  Lines        7616     7669      +53
  Branches      595      603       +8
==========================================
+ Hits         5352     5376      +24
- Misses       2131     2160      +29
  Partials      133      133

Impacted Files
Coverage Δ

pyEX/platform/platform.py
23.43% <0.00%> (-0.19%)
:arrow_down:

pyEX/tests/test_api.py
100.00% <ø> (ø)

pyEX/common/urls.py
34.34% <29.41%> (-0.78%)
:arrow_down:

pyEX/account/watchlist.py
37.03% <37.03%> (ø)

pyEX/account/account.py
52.45% <52.45%> (ø)

pyEX/client.py
63.63% <62.50%> (-0.03%)
:arrow_down:

pyEX/account/__init__.py
100.00% <100.00%> (+47.54%)
:arrow_up:

pyEX/tests/test_api_client.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Decorators - Question 2

I implemented it using a global variable, which will keep track on the amount of calls to the function so far.
Is this the correct way to implement?
02.txt

Could you paste your solution to https://gist.github.com/ please and then paste the link here? That makes it a lot easier to review.

https://gist.github.com/tomag/25737fa6c18521137fa0e76b8feeb01a

Does this work for you? I get
NameError: global name 'counter' is not defined

The trick is that scalar variables - where you need to assign to them in order to update them won't work well here, but if you used a list or a dictionary, then you can update one of the values in the internal function as well. Try that and paste it again.

You can also find a full explained solution in the video tab next to the exercise (showing what @szabgab suggested)


Merge in "stutter" type directory layout

Summary: Want to break this into modules, and be able to use Astra-Sim as a library.
Thus, want to be able to include a header file like this: #include "astra-sim/system/Sys.hh"
Stutter directory layout makes that easier when writing a Makefile
Also updated build.sh to reflect new directory structure

Accepting my own PR :)


Multiauth documentation is missing

Looks like the docs don't have any details about multiauth. Could be useful dropping some example configs into the documentation

It's in progress: https://github.com/tumblr/collins/pull/391 :)
I just need to extract some example data for firehose events other than asset_update and then it should be good to go.

@defect awesome! Ty!

Fixed by #391


Support °F as well as °C

Per https://github.com/adafruit/Wippersnapper_Protobuf/issues/109, we'd like components to be able to support a selectable ambient or object temperature of °F. This would be considered as a new "unit".

I think we need to add some calculated fields/outputs per sensor type. That's what *F is, so then any existing temp sensor gets *F, and a fusion device (like one providing temp+humidty) can provide VPD(vapour pressure deficit) / Dew-point solving #71 and other future needs based off of calculations from the fusion sensor/device. I think custom options at the are probably too much work, as you can take the data if needed out of adafruit IO, but common needs for the sensor / data type make sense.

@tyeth That's what we're doing in https://github.com/adafruit/Wippersnapper_Components/pull/75.
VPD is not on my high priority list right now, but, we can add additional types for VPD/sensor fusion in the future, in the same method that we're adding *F.

Thank you, I shall follow it keenly :) I care little right now for VPD, but it's on my greenhouse priority list (way down there)

Resolved in https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/pull/324, please use Beta 51 and up for this functionality to appear!


Changed bind() to use <IP_ADDRESS> in NAT diagnosis

Unblocks freedomjs/freedom-for-firefox#68.

:+1:


add dockerfile for easy testing

Wow, this takes a long time to build!
Also, for those coming from Windows, I've made improvements.  Also, I had errors when trying to find ./run-tests.sh, so I was explicit on the path and using /bin/bash.


Feature/landing

#15

Coverage decreased (-6.5%) to 79.235% when pulling 30f413ead6ac76de8a457a4a180135d9ce7b47cc on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.5%) to 79.235% when pulling beffa407e37c535b9be8d639c620d151055adbe1 on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.5%) to 79.235% when pulling ce6aee83f0f5d58ba4bd854b15c81b052e6ab432 on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.5%) to 79.235% when pulling 7e57af8d6d2778455d475b7d7c0e85ed51d2440a on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.03%) to 79.688% when pulling dab062b9d5e14be18ee85672eacbca6794b0315b on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.1%) to 79.581% when pulling 4b694ec2a297cf2da4757acc0dfee860e6db941d on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.1%) to 79.581% when pulling 7dd43a21987a799c328bc66381b80d05f9a52143 on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-6.03%) to 79.688% when pulling b339dbe4cd58217da99d55e8c12be3123eeab1c7 on feature/landing into 057f9efad4a91feb3e5c5fc4d3e1dc6a62090347 on develop.

Coverage decreased (-5.9%) to 79.787% when pulling 971adca613f8bff38c32320abbc90ae2fc72b069 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.03%) to 79.688% when pulling c8f06d6642191fca117d1fca259e47ac96e74957 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.03%) to 79.688% when pulling ad1205ae6557905664ea2db1d6242cd9eee9a169 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.03%) to 79.688% when pulling 0a3915bbd39c741e1191b795afd04f24d64b84fe on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.03%) to 79.688% when pulling 5e50a948c24a1708afaaea8cc031e9851f1da358 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-7.7%) to 78.0% when pulling 56637c4ba5e1ce638f724a5e8ce597438ea32be6 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.2%) to 79.524% when pulling 4e112a136599828db12edf3a2d1397ae8e4fc0d7 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.2%) to 79.524% when pulling 5f07c937d3926c2885de244b0ac50479d2d8ca25 on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.

Coverage decreased (-6.2%) to 79.524% when pulling 283d34c269b34d221124e83d1a22ddfbc53a2fce on feature/landing into fc3fe36c405e400691a91caac897236eda853a55 on develop.


[POC] ha agent distributed

What does this PR do?
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/integrate --deploy


ported CC 23 to processing

for https://github.com/CodingTrain/website/issues/267

Looks great, thank you!!!


install on Arch prevents for upgrade

I can't do Arch Linux upgrade because of watson. I very like this app and dont't want to remove it as use it in daily life.
error: failed to prepare transaction (could not satisfy dependencies)
:: installing python-arrow (0.15.7-1) breaks dependency 'python-arrow<0.15.6' required by watson

Question, can be watson upgraded to newer version for python-arrow?

It was done in https://github.com/TailorDev/Watson/pull/380, but it has not been released yet.

We'll make a new release soon!

Thanks @k4nar for info. How often is releasing new versions? From release page I see that is about each half year. Lats was month ago. Is it possible that new version will arrive earlier?

Arch already waiting for 106 updates that could be applied only after watson new version

If watson is the only package depending on python-arrow on your system, maybe just exclude the package from the upgrade for now. That being said, partial upgrades are unsupported, so be sure about it and be aware what you're doing :)
To check what packages depend on python-arrow:
pactree -r python-arrow
# output when only watson depends on it:
# python-arrow
# └─watson

To exclude python-arrow from upgrades:
sudo pacman -Syu --ignore='python-arrow'

Alternatively, you could try to install the latest development version from git, see https://tailordev.github.io/Watson/#development-version

thanks @ybc37 will do upgrade after main work

Expect a new release this week. :tada: :rocket:

There it is: https://github.com/TailorDev/Watson/releases/tag/1.10.0

AUR package updated :clinking_glasses:


Typo "Jupyter notebook"→"Jupyter Notebook"

https://docs.microsoft.com/en-us/azure/cognitive-services/computer-vision/quickstarts/python-analyze

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 Thanks for contributing to the documentation. This editorial revision isn't correct, so we'll close the PR. Because Jupyter Notebook is the name of an application, referring to "a Jupyter Notebook," or example, isn't correct. Thanks.


Create new image 9.0.71-jdk11-openjdk

Hello,
Could you generate a image for the latest version of tomcat 9.0.71, with openjdk11?
Regards

The bot has already picked up the change for the Dockerfiles: https://github.com/docker-library/tomcat/commit/2fe063250eb12b5a1a49e91dbb8e69f4a4127e45
The rest of the steps for it to appear on Docker Hub are linked in the readme: https://github.com/docker-library/tomcat/tree/2fe063250eb12b5a1a49e91dbb8e69f4a4127e45#see-a-change-merged-here-that-doesnt-show-up-on-docker-hub-yet


create Dimension2IO

Dimension2IO us need in FEL, and does not exist yet.  To be patterned off of Vector2.Vector2IO.
Dimension2 also needs to be converted to TypeScript.

Lucky me again... Dimension2 needs to be converted to TypeScript.

In the above commits, I converted Dimension2 to TypeScript, then implemented Dimension2IO using the same pattern as Vector2IO and RangeIO.
Dimension2IO is not used in FEL yet, but will be very soon. I tested by temporarily adding this to FEL Magnet.ts:
    const sizeProperty = new Property( new Dimension2( 0, 0 ), {
      tandem: options.tandem.createTandem( 'sizeProperty' ),
      phetioValueType: Dimension2.Dimension2IO
    } );
    sizeProperty.link( size => console.log( `size=${sizeProperty.value}` ) );

Then in Studio, I verified that I could get and set faradaysElectromagneticLab.barMagnetScreen.model.barMagnet.sizeProperty, and that it had type PropertyIO<Dimension2IO>.
@samreid or @zepumph care to do a quick review? Close if OK.

Do we need to support infinity here? I know we did for Bounds2. I am happy to keep it even if there are not current usages of inifinte Dimension2 values. I kinda felt that that an infinite dimension goes beyond the scope of the class (in practice though not necessarily in theory). Do you have an opinion?
I like the pattern of having a prototype toStateObject even though there are no usages of it yet. I think this pattern should extend to common-code, data-type IOType types, and should not be used by sim specific types, where most often you can just utilize the default toStateObject serialization from providing the stateSchema. Greenhouse does a good job of showing the simplicity of using the default serialization pattern. Does that sound good to you?
Minor doc update committed above.

Do we need to support infinity here? ...

I don't know.  But supporting infinity (initially) seemed safest.  Assigning to @jonathanolson to chime in -- should Dimension2IO support Infinity and -Infinity?

I like the pattern of having a prototype toStateObject ... Does that sound good to you?

Me too, and yes.   Improving the "how to" IOType documentation would also help. The current state of affairs is that developers create new IOTypes by copying and modifying an existing IOType.  And since there is no documented pattern for implementing IOTypes, the implementations are all over the place.   I prefer the pattern where the IOType delegates to the core type as much as possible (for toStateObject, fromStateObject, etc.)

Minor doc update committed above.

That doc was based on RangeIO, so I fixed that doc too in the above commit.

I think it sounds safest to include support for infinite values. We might include "slices" of Bounds2 objects, and those could be empty.

Thanks @jonathanolson.  Since Dimension2 supports infinity, Dimension2IO must support it.  So no change needed to Dimension2IO.
Back to @zepumph in case he wants to create an issue related to "IOType patterns" as described in https://github.com/phetsims/dot/issues/123#issuecomment-1791284520.  Feel free to close when you're done.

Right thanks. I added the patterns we discussed into the technical guide. Any other IOType patterns that you can think of for me to update?

I can't think of anything else to update at the moment. So... closing.


Can WebsiteAgent's change detection ignore certain keys in json?

I'm using Website Agent to monitor changes in the json and create rough events for the new content, which are then sent to a downstream agent for next processing. In the normal case this works well
original json:
[{
        "sub_time": 123,
        "sub_user": "xxx",
        "content_node": {
            "text": ".....",
            "video": {
                "play": 123123
            }
            ...
        }
    },
    {
        "sub_time": 456,
        "sub_user": "xxx",
        "content_node": {
            "text": ".....",
            ...
        }
    },
    ...]

events extracted:
{ "sub_time": "123", "content":{ content_node... } }
{ "sub_time": "456", "content":{ content_node... } }
However, in some content, there are nested values that change frequently. For example, in the following json, the value of "play" changes often, which causes WebsiteAgent to create a new event each time it changes. This results in duplicate events for the same content.
"video": {
    "play": 123456
}

I’ve tried using special JSONPath filtering syntax or set hidden to true  filter out these changes, but it doesn’t seem to be effective.
Since I'm not very familiar with Agent, is there a better solution, thanks!

You might not want to use the Website Agent for change detection for this very reason.  Maybe run the events output through an Attribute Difference Agent or a Change Detector Agent and have it look for the different values.

The only thing you would have to pass to a Change Detector Agent would be a JSONpath to the value you're interested in.  It would look something like this:
{
    "property": "{{ $.*.*.video.play }}",
    "expected_update_period_in_days": 31
}

I had to fix up your sample event so that it looked like this so I could mess around with it.  I hope it's illustrative of the real thing:
[
    {
        "sub_time": 123,
        "sub_user": "xxx",
        "content_node": {
            "text": ".....",
            "video": {
                "play": 123123
            }
        }
    },
    {
        "sub_time": 456,
        "sub_user": "xxx",
        "content_node": {
            "text": ".....",
            "video": {
                "play": 234234
            }
        }
    }
]

JS Agent would definitely do it.


Recent transactions contain all transactions after opening the list of transactions

this is a side effect of this workaround: https://github.com/aeternity/superhero-wallet/pull/883/files#diff-42c781502dd0badc5c59da2f8253cdbee661a4cb9ec87b7ad4703bad7fb0f4b3R125

How would you do it instead?

In the Base aepp we had a reactive variable returning an actual list of transactions with ability to request it to load next page. We can reuse it adding persistance to localStorage and accepting the amount of transactions to show. Then we will be able to use it in both transaction list and recent transactions.
https://github.com/aeternity/aepp-base/blob/92b4235bb3ae521a8b30956780d9880869e5c3be/src/store/plugins/ui/observables.js#L224-L336

In the short term you can rename updateLatestTransactions to general setTransactions and slice from there the necessary amount to show in the recent transaction list.


please add colab

please add colab inference

Hi, thank you for your interest.
We are now preparing colab inference.

@submission6378 thanks, can the colab also be updated to have a option to use cpu?


HL-865: Can't remove drafts as handler

Description :sparkles:
Once again, the applicant endpoint was used instead of the handler endpoint. Over-aggressive mocking prevented catching this in the development environment.

Codecov Report

Merging #2154 (56534e5) into develop (36b198d) will decrease coverage by 15.20%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop    #2154       +/-   ##
============================================
- Coverage    27.00%   11.80%   -15.20%
============================================
  Files          722      160      -562
  Lines        14701     4463    -10238
  Branches      3336     1114     -2222
============================================
- Hits          3970      527     -3443
+ Misses       10206     3767     -6439
+ Partials       525      169      -356

Impacted Files
Coverage Δ

...fit/handler/src/hooks/useDeleteApplicationQuery.ts
0.00% <ø> (ø)

... and 562 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Can I serve single-spa Sub Application both as normal and in root app using single dist build?

Question
Hello,
I am using angular 8 for my Sub application and it works well with root app using single-spa. But, my question is can a single dist build serve as both a normal application(runs independently in browser) as well as a Single-spa sub app?
Please suggest me how it can be done. I need to run in both ways (host Sub-app independently as well as accessible from Root-app as well)

I believe this is a duplicate of #92 and the answer remains the same. So I'll close this for now but feel free to ask additional questions.


Update cache-manager to latest to support refreshThreshold

Information
Is your feature request related to a problem? Please describe.
When using the "memory" cache and the @UseCache decorator, the refreshThreshold option does not work because cache-manager@^4 does not have a ttl method. cache-manager@^5 does have the ttl method.
Describe the solution you'd like
Update the dependencies of @tsed/platform-cache to include cache-manager@^5 instead of cache-manager@^4, so that the "memory" cache store works with the refreshThreshold option of @UseCache.
Describe alternatives you've considered
Suggest in the documentation an alternative memory cache package to use that satisfies the above requirements.
Acceptance criteria

[ ]  The "memory" cache store works with the refreshThreshold option of @UseCache.

Hello @petermenkeepsilon
Thanks for your Issue :)
PR is welcome. I think the change will be on the package.json here :
https://github.com/tsedio/tsed/blob/production/packages/platform/platform-cache/package.json#L25
The change isn't a breaking change so it could be integrated on the v7 release :)
See you
Romain

PR ready

:tada: This issue has been resolved in version 7.3.0 :tada:
The release is available on:

v7.3.0
GitHub release

Your semantic-release bot :package::rocket:

Thanks you @Romakita!


add navsettings to settings screen

I started to integrate the notifications page but realized we need to actually make the settings nav work in the app. this is the first step towards that. it doesn't have any badging or errors or anything like that plumbed through. Just loading up the tabs when you click on the sub nav.
if tabs have sub content in them we'll have to expand this to work with that. i didn't need that and didn't want to continue to add more of this stuff w/o talking to @MarcoPolo

@keybase/react-hackers

this is fine for now, we should think more about routing


Allow post-processing of HttpResponseMessages

Sometimes, it is beneficiary to be able to process the HttpResponseMessage even when the return type of API call defines more specific class, e.g. because an API you are interfacing with is defining some important run-time state in response header and there was no other way to access such information than by explicitly returning HttpResponseMessage and then taking care of DeserializeObject manually.
That brings two nasty issues:

the interface is not as clear, as it could be - the result value is replaced by HttpResponseMessage
it is error prone and more complicated to do so

My proposed solution introduces IHttpResponseMessagePostProcessor with only a single method void PostProcessHttpResponseMessage(HttpResponseMessage message), that in style of Spring/NET IContextAware allows implementing entity to work with the message. There is no cascading to related entities, only a deserialized object is checked, so the performance is not much affected and it is called post-processor to avoid clients thinking they should store the message in their structure somewhere.
I hope you will not consider it edge case and will merge it to the main branch.

.NET already has a standard way to intercept requests (DelegatingHandler).
I'm not sure what this provides that DelegatingHandler doesn't?

@bennor: Yes, but DelegatingHandler works with HttpResponseMessage directly, before the JSON deserialization, or am I mistaken? The point of my patch is able to let Refit deserialize the JSON content and then apply some additional post-processing to deserialized instance, so you don't have to handle deserialization yourself.
The other option would be to know the actual type of the content of Message and somehow inject the values there from DelegatingHandler, so it is there when deserializing.
To give an example usage:
public class APIResponse
	: IHttpResponseMessagePostProcessor
{
	private const string X_SERVER_TIMESTAMP_HEADER = "X-Server-Timestamp";
	private const string X_TOTAL_COUNT_HEADER = "X-Total-Count";

	[JsonProperty(PropertyName = "error")]
	public ErrorDataObject Error { get; set; }
	public int ServerTimestamp { get; set; }
	public int TotalCount { get; set; }

	public void ThrowExceptionOnError()
	{
		if (Error != null)
		{
			throw RemoteAPICallException.FromDataObject(Error);
		}
	}

	public void PostProcessHttpResponseMessage(HttpResponseMessage message)
	{
		if (message.Headers.Contains(X_SERVER_TIMESTAMP_HEADER))
		{
			ServerTimestamp = int.Parse(message.Headers.GetValues(X_SERVER_TIMESTAMP_HEADER).First());
		}
		if (message.Headers.Contains(X_TOTAL_COUNT_HEADER))
		{
			TotalCount = int.Parse(message.Headers.GetValues(X_TOTAL_COUNT_HEADER).First());
		}
	}
}

Interesting. I can see the value, but I wonder if some of those specific examples could be better served by materialising properties on the response directly? e.g. with a header attribute to indicate where the value should come from.

I mean it would be nice if you could just do:
[Header("Date")]
public DateTimeOffset ServerTimestamp { get; set; }

And have the property value set for you by Refit automatically.

Yes, I was thinking about that as well.
I went with this simpler approach because of few things:

there is no real overhead when deserializing the response, if the interface serves as a marker and only then it is processed (contrary to - i suppose - some kind of reflection, as currently the only thing that is accessing the resulting instance is JSON deserializer); but I have to say, I did not have time to dive into Refit too deeply, so there can possibly be some other magic during the auto-generation phase, but from what I saw, it's only JSON deserializer called on Content and handling internal structure of result;
implementing it this way gives you much higher amount of flexibility with other custom processing of the message if such needed;
time constraints... as mentioned before, I am under some time constraints and needed a working solution for the API I am interfacing with (and as I like Refit, I did not wanted to change the library)

Maybe the most complete solution would be the combination of two, if the performance hit is not that big with automatic discovery.

Is there something new regarding this pull request?

@enscope The argument "I went for a simpler approach" seems to contradict with what @bennor suggests, or it depends on the point of view. From the developers perspective it would be easier just to annotate properties, with the header they want it to be populated from. While the other class allows for more post processing.
This is a personal opinion, but I prefer the annotations compared to the custom postprocessor class.

I think both can be useful. This approach pretty much allows you to do anything, while the attribute approach limits you somewhat. Being able to use a custom attribute (derived from a base attribute or implementing a specific interface) with a similar method to PostProcessHttpResponseMessage but intended to only parse the single value would be as flexible as this approach, but in some cases this approach might still be preferable. For instance, this approach would allow you to handle scenarios where the body isn't JSON fairly easily. Add in a class level attribute that let you control the serialization completely and you'd get a completely flexible system that could handle any payload.
[XmlContent]
public class APIResponse
{
	private const string X_SERVER_TIMESTAMP_HEADER = "X-Server-Timestamp";
	private const string X_TOTAL_COUNT_HEADER = "X-Total-Count";

	public ErrorDataObject Error { get; set; }

        [Header(X_SERVER_TIMESTAMP_HEADER)]
	public int ServerTimestamp { get; set; }

        [XmlContentIgnore]
	public int TotalCount { get; set; }

	public void ThrowExceptionOnError()
	{
		if (Error != null)
		{
			throw RemoteAPICallException.FromDataObject(Error);
		}
	}

	public void PostProcessHttpResponseMessage(HttpResponseMessage message)
	{
		if (message.Headers.Contains(X_TOTAL_COUNT_HEADER))
		{
			TotalCount = int.Parse(message.Headers.GetValues(X_TOTAL_COUNT_HEADER).First());
		}
	}
}

Throw in the ability to use a base class with these concepts to handle metadata included in every response and you'd further simplify some cases.


Animations in JavaScript

Description
JavaScript animations are done by programming gradual changes in an element's style. The changes are called by a timer. When the timer interval is small, the animation looks continuous.
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign


OK, let's build thru VS2015! Opened solution dlangui-msvc.sln has missing projects dmdbug and dwindow-visuald. Again bad surprise.

DUB requires inet access to get dependencies. There is some DUB command to specify local package location, but I never used it. I believe it could help of deps/ packages are registered in DUB.
X11 is not needed for windows, but DUB by some reason fetches all dependencies.
I've removed dmdbug and dwindow from solution. Now visuald build should work.

My guess is that dub downloads dependencies for all configurations. x11 configuration is listed without platform restrictions, so it's downloaded too. Maybe specifying "platforms" property will help.
See Configurations format

Does this issue still exist with latest DUB?

please reopen if problem still exists


Parsing error

I have a string

const char xung = "http://wikipedia.org";
struct kao {

and after parsing it looks like
const char xung = "http:struct kao {

This is one of the reasons for my work on the refactor so that it doesn't make mistakes on parsing. It was originally done custom and fast as I had a deadline for the project. Now that I have the time I'm working on a implementing a proper lexer that will fix these errors.
It's known and being worked on though I'm very busy so I wont be able to fix it just yet.


Without this access modifier I can not reference 'afAuth' in the logi…

…n and logout method.

Checklist
Well, I'm only changing a readme here :)
Description
Fixed readme (angular 4)
Code sample

I signed it!

Hey @IncognitoCore. Thanks for taking the time to send a PR!
The template in this example does not reference the private properties.
@Component({
  selector: 'my-app',
  template: `
    <div> {{ (items | async)? | json }} </div>
    <div> {{ (user | async)? | json }} </div>
    <button (click)="login()">Login</button>
    <button (click)="logout()">Logout</button>
  `
})

Therefore, I don't think removing their access modifiers makes sense in this example.


Init ladder queue time

Fixes #1466

No, see issue for required server changes.

Works on test.

@Askaholic did we deployed the needed server change for this

@axel1200 No it is not deployed yet. It's commit https://github.com/FAForever/server/commit/cc8030143a24b335d3682fa5a0cf69207454738b

Is it still deployed with all this everting back to old versions

You're right. It has been rolled back. I'll comment again when I fix the server issues for good.

Fixed merge conflicts.

BTW this is deployed now, although I think ideally we would send the message after login and the client would just not throw it away. Leave it sitting in a message queue somewhere until the ladder tab is opened.

So should I test or merge or not?

I think this being implemented as a request (like it is right now) is more flexible and, less complex and less error prone.  For example it would allow the client to close & unload the ladder tab and then resend the request to recreate it when needed instead of it always existing.
I see no reason why this information being sent should be specifically bound to login time.

The thing is I'm not a big fan of adding server (and protocol) complexity just for convenience in the client implementation. I'd rather send it at login so it works just like the game list and just like the player list. The client can load and unload the ladder tab all it wants, the queue pop time will be the same until the server sends a new info message.
It feels like we're letting the client implementation intrude into the protocol by doing this. We're not adding this message because it makes sense for the protocol. Obviously it's not a huge complexity, but it's something that will build up over time, and once it's added it gets very hard to remove.

With "unloading" i mean forgetting everything about ladder state and having to reinitialize that information from the server.
I guess that I just dislike the general protocol architecture then (im used to web world, where generally the client requests what it wants and the server is mostly just a dumb state store, which works generally very well). But it makes sense that you want to keep the protocol consistent.

ok an this means for me ?

Deploy. Can still be changed later if somebody wants to build a message queue.

Merging if test run through


added thumbnail

What does this PR do?
I added OpenGraph/ Twitter Card support to the docs to create nice social thumbnails.

To be able to add these I needed to install sphinxext-opengraph. I came across this issue on the readthedocs repo saying that since someone has built this plugin they are not integrating and providing documentation to it. That's why I added it for creating the documentation. The repository can be found here.
P.S. It seemed that make style never ran for docs/ i hope the changes are okay otherwise I'll revert it.
I tested with the datasets image since the accelerate is not yet released. This branch can be merged after this PR is merged

FYI the moon-landing PR has been merged and deployed :)


Framerate testing and investigation to remove stutters

Duplicate of https://github.com/V-Sekai/V-Sekai.github.io/issues/434.


feat: Factor out generators

Rather than computing all of this stuff manually, we could just include the generator step in the call to StructuredPolynomials::batch() -> (Self::BatchedPolynomials, Self::Generators)


Dangling leases problem

I think yesterday my provider pod restarted and then I lost all my current leases. They were gone from the provider, but they're still
active on the chain and the new leases work fine, but the old leases are gone from my provider and they are dangling leases on the chain.
Please look at the number of leases on the screenshot.

The graph shows 30 and on the top value shows 15. 15 is the number of leases I currently have on my provider - which means I have them as pods. The 30 is the number of leases there are currently on the chain. Which means 30-15 = 15 - there is 15 dangling leases on the chain on my provider. I checked on akashdash and it shows 30.
and they won't close when they will run out of $
they will only close when you withdraw - manually or automatically, and there is no more $ on the lease then it will close
but when you setup like big withdrawal time like 100h for example to get paid once a week
they will be active all the time. The only problem is they lock your 0.5 akt deposit bid fee.
The lease will stay active and the $ wont be paid untill withdrawal time.
I just ran manual withdrawal for all these leases, and few of them got closed right after.
dunno when it excatly happened, but I know the pod restarted for some reason and then after that I had no leases on my provider
I don't know how to excatly reproduce this. I know that it happened right after the pod restarted. It happened before occasionaly - maybe I had like 2-3 dangle leases in past 6 months, but it's never been like that where all the leases were just gone.
I noticed it happens also on other providers, whenever there's a difference in these two numbers then 100% there are some dangling leases on the chain and Im pretty sure this happens during the restart of the provider pod

@TormenTeDx - have you attempted to heal the dangling leases by executing the script referenced in this doc:
https://akash.network/docs/providers/provider-faq-and-guide/#dangling-deployments
While the title of this section is "Dangling Deployments" it actually cures both dangling deployments (I..e when a lease has been closed but the deployment in K8s remains) and dangling leases (I.e. when the lease on chain is active but no deployment exists in K8s.).
This is a direct link to the suggested script to cure both scenarios:
https://gist.github.com/andy108369/f211bf6c06f2a6e3635b20bdfb9f0fca
While this is not a permanent fix - it should cure the current issue and close out all stale leases for your provider on the blockchain.
And within that script this is the section that address dangling leases.  Run the script as is and in it's entirety.  Just isolating this section below for knowledge of the relevant section.
## 4) delete orphaned leases
####

# active leases without actual deployments

PROVIDER="$(kubectl -n akash-services exec -i $(kubectl -n akash-services get pods -l app=akash-provider --output jsonpath='{.items[0].metadata.name}') -- sh -c "echo \$AKASH_FROM")"

LEASEDATA="$(provider-services query market lease list --provider $PROVIDER --gseq 0 --oseq 0 --page 1 --limit 10000 --state active -o json)"
NSDATA="$(kubectl get ns -o json)"
echo "$LEASEDATA" | jq -r '.leases[].lease.lease_id | [.owner, .dseq, .gseq, .oseq, .provider] | @tsv' | while read owner dseq gseq oseq provider; do
  IS_EMPTY=$(echo "$NSDATA" | jq --arg dseq $dseq --arg oseq $oseq --arg gseq $gseq --arg owner $owner --arg provider $provider -r '.items[] | select(.metadata.labels."akash.network/lease.id.dseq"==$dseq and .metadata.labels."akash.network/lease.id.gseq"==$gseq and .metadata.labels."akash.network/lease.id.oseq"==$oseq and .metadata.labels."akash.network/lease.id.owner"==$owner and .metadata.labels."akash.network/lease.id.provider"==$provider) | length' | wc -l);

  if [[ $IS_EMPTY -eq 0 ]]; then
    echo "=== Found orphaned lease ==="
    #echo kubectl get ns -l akash.network/lease.id.dseq=$dseq,akash.network/lease.id.gseq=$gseq,akash.network/lease.id.oseq=$oseq,akash.network/lease.id.owner=$owner,akash.network/lease.id.provider=$provider
    #echo kubectl -n lease get manifest -l akash.network/lease.id.dseq=$dseq,akash.network/lease.id.gseq=$gseq,akash.network/lease.id.oseq=$oseq,akash.network/lease.id.owner=$owner,akash.network/lease.id.provider=$provider
    ns=$(provider-services show-cluster-ns --dseq $dseq --owner $owner --provider $provider)
    echo kubectl -n $ns get all
    echo "ACTION: close this lease if you can't find it is really running on your K8s cluster:"
    echo kubectl -n akash-services exec -i $(kubectl -n akash-services get pods -l app=akash-provider --output jsonpath='{.items[0].metadata.name}') -- bash -c \"provider-services tx market bid close --owner $owner --dseq $dseq --gseq $gseq --oseq $oseq --from $provider\"
    echo "NOTE: However, executing an action from the provider address will cause the \`account sequence mismatch\` afterwards. Make sure to restart akash-provider service once done with running the \`tx market bid close\` command! Ideally, make sure akash-provider services is stopped first."
  fi
done

Yes, it found  orphaned leases. I closed all of them. My numbers look good now

OK here is some extra info. 100% it happens when restarting the pod.
Also I noticed 2 things. Sometimes when the pod is restarting, the endpoint via curl or grpcurl won't work. When you type the command it just stalls and you wait and it won't show. After a minute pod will restart automatically and after the restart it started to work fine. Dunno why it happens, but it's only sometimes.
Next thing I noticed is - I was lucky enough that I checked my provider when this was happening. I noticed my pod restarting very frequently in the last 15-20 minutes or so. I checked the endpoint - it was unresponsive, the pod restarted one more time, after around 20-30 sec of running I ran the grpcurl command and it worked, but I noticed there is no leases. All leases were removed on my provider, but they're still on the blockchain. Which means, the leases are removed from the provider when your pod is restarting, and sometimes after a restart your pod might not be fully working right, the pod will show its running, but grpcurl won't work. And when this happens pod will restart itself after a while and then leases are gone. Dunno if it helps but yeah I noticed this.

@TormenTeDx - could you provide precise, ordered steps to re-create the issue?  And please confirm the Akash provider version active on provider.
For example:
Step 1 - launch a number of deployments using XYZ SDL (provide link to SDL)
Step 2 - restart the provider pod
Step 3 - observed behavior has been the deployments are now closed but lease remain on chain
Believe above steps capture those that should be used to reproduce the issue.  But wanted to ensure.  And also want to ensure provider version and SDL used.  As I believe there was a thought prior that this could be related to specific SDL/deployment types.  Want to first focus on provider functionality and can later focus on reporting issues if need be.

pod restart and all leases lost...
can see no rim or reason why it happened.
running triple control planes and triple etcd on individual servers
version v1.28.6 as most providers do and the latest of the recommended charts and such.
if memory serves, then in the past this issue was sometimes caused by rpc nodes or control planes if they was immediately lost.
but that was a long time ago, not sure if it ever got really fixed tho...
my provider pod didn't restart excessively....
tho its possible that it restarted twice in a row, but no more than that...
deleting the dangling is hardly a real fix... it can take months for providers to accumulate customers.
if we imagine 3 months to fill a provider, then this happens and one had to start over.
that would half the earnings in the that period assuming a similar progression of customers...
and thats not considering the customers there would be permanently done with a provider or even akash.
due to such an event.
i'm not currently aware of any obvious path to creating dangling leases.
but i know that leases can be lost so easily, is a bad look for akash and providers.

there are actually 2 ways it can happen.

The pod just restarts twice in a row and it will drop all current leases and they will all be dangling.
when you scale down/up the provider, some of the leases will go dangling.

I dont know why it happens. It's just sometimes it happens. One day I scaled down/up provider just to check something and like 80% of leases went dangling. I tried doing the same thing 1h later but nothing happened.

Small update
Recently I changed IP on my master node, then my provider went down, couldn't make it work, so I had to recreate a cluster.
I noticed that the leases that were working fine - before I broke the cluster. After I came back with recreated cluster they were in dangling state on the chain


fix: Update rendering of preamble and usage

Adds settings_preamble to the plugins page
Adds it to render right after the settings header
Moves the usage block below the Settings which was it's original place.

Duplicate of #911. Sorry about that @tayloramurphy 😅. Happy to review this one and close my own, though.

Duplicate of #911. Sorry about that @tayloramurphy 😅. Happy to review this one and close my own, though.

I think I'm the one who should apologize, I think I made more work for you haha! Plus I moved some stuff around in this PR too 😅


Expose prometheus metrics for local volume provisioner

Expose prometheus metrics for local volume provisioner. Then we can monitor its internal, actions running, finished, and latency, etc.

cc @msau42 @ianchakeres

@dhirajh - this PR touches stuff that is in your open PR - https://github.com/kubernetes-incubator/external-storage/pull/711. Please feel free to chime in.

FYI: @jpisaac

/assign
/assign @dhirajh

Sorry this fell off my radar. Will try to take a look today

Would it be useful to create an example Service spec, so that users can easily hook up the Endpoints into a monitoring pipeline?

I will add examples and update README.

@msau42 @dhirajh
I've rebased on latest master and made a few changes, please take a look at again.
List of changes:

Remove PersistentVolumeProvision(Total|Latency).
Add PersistentVolumeDiscoveryTotal and PersistentVolumeDiscoveryLatency for discovery.
Add PersistentVolumeDeleteTotal and PersistentVolumeDeleteLatency for delete.
Rename PersistentVolumeCleanupFailedTotal to PersistentVolumeDeleteFailedTotal.
Add type for PersistentVolumeDelete(Total|FailedTotal|Latency) metrics.

type can be process or job (https://github.com/kubernetes-incubator/external-storage/pull/711).

Add capacity, cleanup_command for PersistentVolumeDeleteLatency metric as @msau42 suggested.

capacity is broke down by 500G.

Update CleanupStatus.RemoveStatus() to return startTime for metrics.
Update provisioner/REDME.md and add a example service yaml file.

See docs for all metrics: https://github.com/cofyc/external-storage/blob/6c86c3f1d2fa959bba41372ac8a283afc19751f1/local-volume/provisioner/README.md#prometheus-metrics

@msau42 Build failure fixed (forgot to update metric variables in cmd) and squashed.

/lgtm
/assign @childsb

/area local-volume


Improve Signed API and airnode-feed monitoring

Setup additional alerts for Signed API and airnode-feed
To monitor errors in the Signed API and airnode-feed Grafana logs, directives should be given related to what to specifically look for in the logs to avoid being overwhelmed by airnode-feed API call errors when investigating an issue.
The monitoring guidelines might need to be updated to include the new directives once defined.

Alerts are sent to https://api3workspace.slack.com/archives/C06QTTM722H and https://api3workspace.slack.com/archives/C06RKPATH6U
Tasks documentation has been updated, with the exception on WHO is responsible for these and how the on-call works for these. Burak had a good point about this on todays call, that this should be formalized. For now I am going to handle all of them across all channels.


Inference time?

Can you give an idea of what length of time is required for inference? Also, do you plan to share the code on GitHub?

Hi, I'm very sorry for the delay. Code has been released, please have a test.

Thank you, your paper is very interesting I look forward to testing it.

Sorry for closing this issue, please feel free to raise again.


B31974: Gaps in Checkout form

Had to create global css rule, saying labels have no margin bottom. This fixes it. Checked the app, have not found any issues with label anywhere.

Closing this one, as CH3 is using shadow dom by default, so this is not needed anymore.


Legacy mode layout settings broken

I check "use legacy console". I require the console window size (and buffer size) to stay fixed at a size I set,  normally width 80 and height 42.  I uncheck "let system position window". When I load a text file into a new console window, the console opens with the specified size. As soon as I drag the window to another position, the size changes, typically the width shrinks to 78 columns and height anywhere from 32 to 40. This has been consistenly happening with the new version of the console.   (Font is set to Lucida Console 24).
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7a3244ed-e1a9-4e16-0a60-246f679c9afe
Version Independent ID: 6715591d-2458-9008-edbe-eaed47051f72
Content: Legacy Console Mode – Windows Desktop - Windows Console
Content Source: docs/legacymode.md
Product: console
GitHub Login: @miniksa
Microsoft Alias: miniksa

Since you cannot just “load a text file” into the console, you must be using some additional software. Would you mind sharing what that is? It is difficult to troubleshoot when we have to guess.

Closing stale issue.


Sync function/source/sink configdata to pod when updated.

resolve: https://github.com/streamnative/function-mesh/issues/216
Add a annotation for hash of applied configdata to compare diff of applied config and current config, update pod if hash doesn't match.

@MarvinCai  could you please rebase your branch with the current master branch?

@MarvinCai and @freeznet , can we prioritize this issue to unblock cloud team?

To your original comment, we're not trying to sync annotation to statefulset, just need to use that as a flag to indicate if statefulset need to be updated.
But after discussion with Yangyang offline, there's no need to do that as for function configs directly applied to statefulset command, so we can simply compare desired statefulset spec with current statefulset spec to determine if statefulset need to be update.


fix: React plugin live query improvements, and export types

@msfstef this works, I'm using it in the new Linearline PR, but its failing test. Any idea why? I'm can't work it out...


Maintenance/Update MOM6

This PR adjusts CMakeLists.txt to be able to work with updates from https://github.com/mom-ocean/MOM6/pull/1603
To do:

✅ @sanAkel: once https://github.com/mom-ocean/MOM6/pull/1603 has been merged submit this PR.
[x] @mathomp4 and/or @tclune: https://github.com/orgs/GEOS-ESM/teams/cmake-team review this PR.
[x] @mathomp4: please update our fork: https://github.com/GEOS-ESM/MOM6

@sanAkel I've updated the MOM6 fork and approved this.
Next up would be tags of both MOM6

@mathomp4 ⬆ is ✅ https://github.com/GEOS-ESM/MOM6/releases/tag/geos%2Fv2.2.1
and Ocean so we can get the tags up to GEOSgcm so the CI here can work again.


Release artifacts for release v0.1.8

Description of changes:

release artifacts for release v0.1.8

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

/lgtm


Added sourcemaps

This closes #87 ie. adds source maps
The maps, by default, are added as separate files but can be configured to be in a ./map directory or inline. Let me know what you think!

@tom-sherman Thanks for contributing!
We've added them in v1.1, sorry for not catching up. But you're right about there being too many maps that could perhaps use a separate directory. Will be glad if you could hook that up :)


Validate of smart-flank-gcs-path to not override different results type

Author the user story for this feature
As a flank user, I want to be informed when flank can override JUnitResult configured in smart-flank-gcs-path with a different type in the current run so I can easily avoid situations like that
Is your feature request related to a problem? Please describe.
If the test is flaky, flank removing stack traces from JUnitResult, FullJunitResult keeps stack traces.
Describe the solution you'd like
Fast fail when Flank can potentially override JUnitResult with different report type.

Just for my understanding. Now flank will upload to a bucket only if types match? (by types I understand full and normal results)
example:
I run my test suite with flank and received JUnitResult. But I am not glad about the info I received and want to have FullJUnitResult. So now, I need to manually remove a file from the bucket and after that, I am able to run flank with the new config?

Sorry, it's just too many sources of information for this issue 😄
Based on https://github.com/Flank/flank/issues/936 and implementation in https://github.com/Flank/flank/pull/1056 I am trying to understand the actual case.

For now, we can run smart flank without set --full-junit-result and --legacy-junit-result but if we use FullJUnitResult in gcs path and current run don't have set flag --full-junit-result flank override full junit result by junit result it's can be little confusing

If I get it correctly it means that currently flank will try to upload FullJUnitResult to thew bucket but actually this file won't be produced because --full-junit-result was not used and JUnitResult is created instead. So flank will upload JUnitResult but rename it to FullJUnitResult Am I correct?

If user set different XML name in smart-flank-gcs-path flank shouldn't validate type.

Basically means - ah, yeah, you changed the name so probably you know what you are doing (no validation)
Thanks for understanding and patience :)

So 😄

If we set smart-flank-gcs-path to .../FullJUnitResult.xml and we have turned on flag --full-junit-result file from smart-flank-gcs-path path will be overridden by JUnitResult.xml. We want to avoid that case.
There is a small exception mentioned by you on my pr, about turn off validation when --smart-flank-disable-upload set. Thanks!

About different XML names - right, if the name is changed by the user we don't validate the type. The user probably knows what he doing.


Placeholder width bug with multiselect2

In the lastest version of select2, If a select is not visible when select2 init it, the select2 will not have the width of the select but will have always 100% and the placeholder will always have 100px. Why ?
Also, i'm able to reproduce it on your website, in the examples section.

I wasn't able to reproduce this in the examples page, but I also may have misinterpreted the issue.

Can you expand upon the issue you are facing by adding a few more pieces of information to your bug report?

What steps can be used to reproduce the issue?
What is the bug and what is the expected outcome?
What browser(s) and Operating System have you tested with?
Does the bug happen consistently across all tested browsers?
Can you reproduce this issue on the examples page?
What version of jQuery are you using? And what version of Select2?
Are you using Select2 with other plugins?

The contributing guide contains a useful section with a few questions which can help us track down the bug and speed up the process of finding a fix for it.  The creation of an isolated test case would also be useful.

Here is your jsfiddle:
https://jsfiddle.net/km1adzaq/
The second field-set doesn't shows full placeholder

Yes, I saw this problem too. An example is put a select2 control in a tab which is initially not active, and then when activate that tab, you see the select2 placeholder only partially displayed.
Is there any fix or workaround available?
Thanks

Here is a simple example of the problem http://jsfiddle.net/say2rwmt/4/ using bootstrap tabs to initially hide the select2.  When you click the second tab, you'll see the placeholder is truncated.
Note: as soon as you enter text, and backspace, the placeholder resets to it's correct size.
A workaround for this specific instance is to hook into the tab shown event and (re)initialize select2:
$('a').on('shown.bs.tab', function(){ $(".s2").select2(); });

Found a possible fix (lines 2009-2011 in select2.js, or 2005-2007 in select2.min.js reproduced below).
Originial fiddle with problem: http://jsfiddle.net/say2rwmt/4/
Updated fiddle with fix:  http://jsfiddle.net/br917x0b/1/
Change:
if (this.$search.attr('placeholder') !== '') {
    width = this.$selection.find('.select2-selection__rendered').innerWidth();
} else {

to:
if (this.$search.attr('placeholder') !== '') {
    width = this.$element.innerWidth();
} else {

Small issue in that if the placeholder is longer than the available width, there is no nice padding at the end, it just gets cut off when the element ends:

Haven't had time for much testing but possible fix/workaround around line 2005 (in select2.min.js):
Original fiddle (with problem): http://jsfiddle.net/say2rwmt/4/
Updated fiddle: http://jsfiddle.net/br917x0b/3/
Original:
if (this.$search.attr('placeholder') !== '') {
    width = this.$selection.find('.select2-selection__rendered').innerWidth();
} else {

changed to:
if (this.$search.attr('placeholder') !== '') {
    width = this.$element.width() === 1 ? this.$selection.width() : this.$element.width();
} else {

$('a').on('shown.bs.tab', function(){ $(".s2").select2(); });
this workaround works while
if (this.$search.attr('placeholder') !== '') {     width = this.$element.width() === 1 ? this.$selection.width() : this.$element.width(); } else {
dose not work.

I've come across the same issue too, except I'm drawing the select2 elements on page load.
I've noticed also that even if you replace the placeholder's length of 100px with 100% it still doesn't display correctly since the wrapping li doesn't span the whole line (specifically the li with the select2-search select2-search--inline which requires the following class in the CSS to have width:100% applied .select2-container .select2-search--inline).
The remaining issue then is that the final input box inside of the above li is being set to 100px via inline styling and thus can't be overwritten in the CSS file. I'll look to see if I can spot where it's being applied to the input.

Also worth noting that If you select a value then remove it, then the correct width does get applied to the placeholder instead of the 100px.
Could it be that the width is being gotten before the select box has been drawn on the DOM leading to a default value being used instead? So that when the values are changed and then blanked, the select box is present and a correct width can then be applied? Just a hunch at any rate.
Finally as a side note, I tried seeing exactly where the placeholder triggers the width value functions (of which there are a few) but the only one that default to 'px' weren't being triggered. Quite confusing really.

Same issue, my css solution:
.select2-search__field { 	width: 100% !important; }

Thanks @dellch , i fixed this in my end by your code.
Thank you

@Cruiser13 's solution worked for me, but I also had to include the li element:
.select2-search--inline, .select2-search__field { width: 100% !important; }

There is a better discussion of this problem in #4513, so I am closing this discussion.


OADP-5362: Create or update CredentialsRequests to prevent oudated roleArn

Signed-off-by: Tiger Kaovilai<EMAIL_ADDRESS>Why the changes were made

Previously, Uninstalling operator, installing again with corrected role arn creates operator subscription with corrected rolearn but the credentialRequests in the cluster still contains outdated roleArn
This fixes the prior behavior by adding update calls to credentialsRequest
How to test the changes made

/cc @shubham-pampattiwar

/cherry-pick oadp-1.4

/retest


Changing API annotation for Power Automate from Production to Preview

This PR changes x-ms-api-annotation from Production to Preview, as the Production tag has requirements that could delay release.

If you haven't already let's also go ahead and make the same change in our source control as well.


Make generated test suite reusable

As discussed in this blog, it would be useful to make generated test suite reusable.
As of now, JCUnit has "Recorder" and "Replayer" mechanism , but

The documentation about it is not sufficient.
It requires code change on record/replay.
How it should behave when the test suite definition (what factors the test class has, what levels each factor has, etc.) is changed isn't defined.
How to detect those changes (or a user should be responsible for it) is not defined.

At least JCUnit needs documented best practice for this.

Made sure Recorder/Replayer mechanism can do it. But not documented enough.
And we lack tests for this feature to ensure it can work with FSM tests.


when I set enableLocationRequest(true) there are tree options in the popup but only one resolves

Hi,
When I set enableLocationRequest(true) on iOS there are tree options in the popup but only one resolves the other two get rejected.

When I tap on the Always Allow it resolves and I can set the location immediately
but if I choose Only while using the App it get rejected but the location is available if I tap again on the get location button.
Finally, if I choose Don't allow it get rejected also.
this is how I use it

getLocation() {

        isEnabled().then(isLocationEnabled => {
            if (isLocationEnabled) {
                this.useLocationService();
            } else {
                enableLocationRequest(true).then(() => {
                    this.useLocationService();
                },(err)=>{
                    console.log(err);
                });
            }
        }, function (e) {
            console.log("Location error received: " + (e.message || e));
        });
    }

useLocationService(){

        getCurrentLocation({
            desiredAccuracy: Accuracy.high,
            timeout: 5000
        })
            .then(location => {

                console.log(location.longitude, location.latitude);
            }).catch(error => {
                 console.log('Location ERROR: ');
                 console.log(error);
                 console.log(localize('cant_update_the_location'));
            });
    }

So my question is, how can I tell the difference between the two rejection?
Which platform(s) does your issue occur on?

iOS
emulator and device

Please, provide the following version numbers that your issue occurs with:
version: "4.3.1",

Fix is available in the latest release of<EMAIL_ADDRESS>


Websocket port for frontend

Would be awesome to have separate port option in case if goaccess websocket server runs behind a proxy. I have EC2 instance with nginx that passes requests from /goaccess/websocket directly to localhost:9879.

Are you looking to have an option to specify the port to which the WebSocket constructor accepts on the client side and different to the one the server listens on? e.g.,
Server
goaccess -f access.log --real-time-html ws-url=http://site.com --port=7890 --client-port=9999

Client
ws://site.com:9999

Yes indeed.

This has been added. Now you can specify the port within --ws-url. For instance,
goaccess -f access.log --real-time-html --ws-url=host:9999 --port=7890

Feel free to build from development, otherwise it will be pushed out in the upcoming release.

Closing this. Thanks.

Amazing! Thank you! 👍

Hey -  which version is this in?
With 1.0.2 I see if I launch with:
--ws-url=analytics.test.com:7891 --port 7890
The JavaScript reads:
{"url": "analytics.test.com:7891","port": 7890}
Which as far as I can tell uses the 'port' value rather than the URL.
Thanks

@madpsy, it's on v1.0.2. On the client-side, it should use 7891 and
7890 is used on the server-side.
On Mon, Aug 22, 2016 at 5:46 AM, madpsy<EMAIL_ADDRESS>wrote:

Hey - which version is this in?
With 1.0.2 I see if I launch with:
--ws-url=analytics.test.com:7891 --port 7890
The JavaScript reads:
{"url": "analytics.test.com:7891","port": 7890}
Which as far as I can tell uses the 'port' value rather than the URL.
Thanks
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


FAQs Page

Description
This PR fixes #10
Notes for Reviewers

@Sanseet
There's some homework left

[ ] Give relevant commit messages instead of updates - ,
[ ] Follow file structure guidelines
[ ] Your component can't be viewed because of fixed positioning, Tweak that.
[ ] Make the whole question clickable instead of just the + icon
[ ] Ensure Responsiveness ( See image )
[ ] Prefer tailwind, you are affecting the styles written by other people, use specific classnames and IDs if writing vanilla css ( Like aliceblue text here )

Thanks @Sanseet 🚀


GPS data reads as 0

Hi,
Thanks for the awesome repo first of all.
I have attached a USB GPS to the nano. I don't get any speed values updated on the UI. It always remains at 0.
I can see the output using cpgs command on the terminal and also see the socket NMEA string using
echo '?WATCH={"enable":true,"json":true};' | nc <IP_ADDRESS> 2947 .
I have made changes to car_gps_reader.cpp
this->;socket_port = 50000;    this->;socket_server = "<IP_ADDRESS>"; to replace my socket port and IP
On /src/configs/config.h
#define DISABLE_GPS_READER  commented this line out.

#define USE_CAN_BUS_FOR_SIMULATION_DATA true changed true to false

Still I receive 0 for all values when I print these variables.
signal_status = kSignalNormal;     longitude = gps->fix.longitude;     latitude = gps->fix.latitude;     car_speed = gps->fix.speed;
What am I missing?
TIA.

I used this program  https://github.com/ckgt/NemaTode/tree/master/src to get a good TCP socket for the GPS coordinates.
/src/sensors/test_car_gps_reader.cpp gives prints the speed and lat, long
But the car_gps_reader throws an error even though both call the same function.

I haven't touch GPS reader for a long time. Can you fix fit and contribute back to this repository? Thank you very much!


question/bug/feature: set undo break before trigering the snippet

First of all thank everybody for such a  great plugin!
It happens relatively often that I would like to undo the triggered snippet. It would be nice to add the option to set an undo break before the snippet is triggered like you would do with i_CTRL_G u.
What I would like is smth like this:
s({ trig = "trig", snippetType = "autosnippet" }, t [[some other text]),
Example:
Here is  trig -> Here is some other text
After pressing undo
Here is some other text  -> Here is trig
What I tried so far is to use feedkeys but without success. What I tried is
local function tt(text)
return f(function()
vim.api.nvim_input("u")
return text
end)
end
s({ trig = "trig", snippetType = "autosnippet" }, tt[[some other text]),
It works with snippetType = "snippet"

Did not notice that <c-g> is formated by markdown/github. The tt function in the text above should have been
local function tt(text)
  return f(function()
    vim.api.nvim_input("<C-G>u")
    return text
  end)
end


Sharing environments globally?

Is there a chance to share the dedicated environments globally between different VS-editors?
Thx

Hi! Not sure what you mean.
Only one profile can be active at the same time,  so if you have several VSCode instances open,    once you reload them, the same profle will be applied (it comes from the fact that vscode reads extensions from the single folder). Until the reload,  however,  the old extensions set will remain,  since it is already loaded in memory,  but this situation can potentionally lead to errors so always reload all windows on profile change.

@cyberbiont thx for the response:
I want to know if I the environment with the name RUST will be synchronized with the visual code editor on a different platform. It would be nice if it is possible?

Yes,  you can do this using SettingsSync extension. Please refer to the corresponding chapter in Readme on how to setup vscode-profles with settingssync.

Thx a lot!!


erros when building under linux

two fatal errors occur when building in the manjaro!
building tools: cmake and make

/home/cl/codes/my/SPlisHSPlasH/extern/Catch2/catch.hpp:8223:45: error: size of array ‘altStackMem’ is not an integral constant-expression
8223 |     char FatalConditionHandler::altStackMem[sigStackSize] = {};

/home/cl/codes/my/SPlisHSPlasH/extern/Catch2/catch.hpp:8164:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’
8164 |     constexpr static std::size_t sigStackSize = 32768 >= MINSIGSTKSZ ? 32768 : MINSIGSTKSZ;
|                                                          ^~~~~~~~~~~

Hi, thanks for reporting this issue. It seems that this can be fixed by simply upgrading the version of Catch2. If you want a quick fix, just exchange the header extern/Catch2/catch.hpp with a more recent version and everything should work fine. We're working on pushing a fix soon.

Hi, thanks for reporting this issue. It seems that this can be fixed by simply upgrading the version of Catch2. If you want a quick fix, just exchange the header extern/Catch2/catch.hpp with a more recent version and everything should work fine. We're working on pushing a fix soon.

thanks！


text-align not behaving as expected

On Linux Mint
package main

import (
	"github.com/goki/gi/gi"
	"github.com/goki/gi/gimain"
	"github.com/goki/ki/ki"
)

func main() {
	gimain.Main(func() {
		mainWin := gi.NewMainWindow("my-window", "My App", 1024, 768)

		vp := mainWin.WinViewport2D()
		updt := vp.UpdateStart()

		mainFrame := mainWin.SetMainFrame()
		mainFrame.SetStretchMaxWidth()

		lbl := gi.AddNewLabel(mainFrame, "lbl", "dummy text")
		lbl.SetProps(ki.Props{
			"text-align":   "center",
			"border-width": 1,
			"width":        500,
		}, false)

		mainWin.SetCloseCleanFunc(func(w *gi.Window) {
			go gi.Quit()
		})

		vp.UpdateEndNoSig(updt)
		mainWin.StartEventLoop()
	})
}

Expected the text to be centered within the width of the label, but instead it is right-aligned. Setting text-align: right moves the text outside of the label altogether.

This had me puzzled for a bit, but I think I've figured out what the issue is.  Basically, the Label layout code is not properly handling the case of a specified "width" property, in relation to its own computed positioning and width.  If you set the label max-width to -1 (stretch) then it centers it fully, and the box takes up the whole area, but specifying a fixed width produces some improper amalgam of its own computed alignment-based layout and width, and the specified width.  This Label layout code handles iterative resizing to fit constraints, so it is a bit complex, and that case was not properly tested.  Will look at it later when I get a chance -- I've updated the basic.go example to demonstrate the issue.
Also, technically you should need to specify "align": "center" too but that doesn't seem to make a diff.. not sure if it falls back on text-align or what.

Probably related, but I'm having trouble achieving a particular effect. I need a fixed width horizontal Layout with two labels. The left label's text should be left aligned. The right label's text should be right-aligned, and the right label itself should be aligned to the right side of the parent. Something like

From the docs, my initial thoughts were to try
row := gi.AddNewFrame(mainFrame, "row", gi.LayoutHoriz)
row.SetProps(ki.Props{"width": 750, "horizontal-align": "center"}, false)
gi.AddNewLabel(row, "leftBox", "this text should be left-aligned")
gi.AddNewStretch(row, "stretch")
rightBox := gi.AddNewLabel(row, "rightBox", "this should be right-aligned")
rightBox.SetProps(ki.Props{"text-align": "right"}, false)

Which gives me

I then thought to insert additional sized vertical layouts and set the horizontal-align property of the labels. So I tried this, with varying flavors of CSS.
row := gi.AddNewFrame(mainFrame, "row", gi.LayoutHoriz)
row.SetProps(ki.Props{"width": 800, "horizontal-align": "center", "overflow": "visible", "margin": 0, "padding": 0}, false)
leftLyt := gi.AddNewFrame(row, "leftLyt", gi.LayoutVert)
leftLyt.SetProps(ki.Props{"width": 400, "margin": 0, "padding": 0}, false)
leftLbl := gi.AddNewLabel(leftLyt, "leftLbl", "this text should be left-aligned")
leftLbl.SetProps(ki.Props{"horizontal-align": "left", "margin": 0, "padding": 0}, false)
rightLyt := gi.AddNewFrame(row, "rightLyt", gi.LayoutVert)
rightLyt.SetProp("width", 400)
rightLbl := gi.AddNewLabel(rightLyt, "rightLbl", "this should be right-aligned")
rightLbl.SetProps(ki.Props{"horizontal-align": "right", "margin": 0, "padding": 0}, false)

Which gave me

Which might be close. I can't tell, Shouldn't overflow: visible; remove scroll bars?

try the first version without right alignment?  The stretch will achieve the right align anyway.  There are clearly conflicts between the text-level alignment and the layout-level arrangement of items -- I'll see if there are ways of making that work more sensibly.

yeah it was pretty broken!  was not updated once text alignment happened separately in text layout mechanism, and the widget-level and text-level alignment settings were linked which is not good..  see the new align example for new correct behavior, and hopefully your cases now work -- please update this if not.
I still need to do more testing and look for existing text-align settings etc and also add vertical test cases to align.

if latest is working for you now, you can close this issue, or update with further details on what isn't working.  It looks good to me in my tests.


Error popup

Hi @abulghoor1 this issue is already fixed in version 2.1.4. Please update the app to the latest version in Microsoft Store to solve this problem.
Closing, duplicated with issue #25.


Enhancement: add electoral college votes

All this does is add the number of electoral college votes each state is worth. I thought this would be useful information and would save me having to remember them or flick to a different tab :)

Please do not change the HTML directly, it'll just be overridden the next time the data is updated. You need to change print-battleground-state-changes

Oops yeah, just looked again at my changes and missed this. Will fix :)

Will PR again, it'll be easier


Fix: Documentation on Method Overloading in Java

Description 📜
Added documentation on method overloading
Fixes # 2091

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Java_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

gh pr checkout 2719


Getting errors when publishing

When I try to publish a piece of content from the preview API, I get alternating errors:
ContentfulModel.use_preview_api = true
comment = Comment.find_by(id: params[:id]).load.first
ContentfulModel.use_preview_api = false
comment.publish
#=> undefined method `version=' for nil:NilClass
comment.publish
#=> undefined method `name' for nil:NilClass

The request that gets logged is as follows:
{:request=>{:url=>"https://cdn.contentful.com/spaces/7swdj0fkojyi/environments/test/entries", :query=>{:"sys.id"=>"3fgQjb9uekKeuw6EYQiucU"}, :header=>{"X-Contentful-User-Agent"=>"sdk contentful.rb/2.8.0; integration contentful_model/1.0.0; platform ruby/2.5.0; os macOS/17;", "Authorization"=>"Bearer 79f8543d1515fd5e50fb432729237fe799678a1cacc5006a062e72dd5172f219", "Content-Type"=>"application/vnd.contentful.delivery.v1+json", "Accept-Encoding"=>"gzip"}}}

Any ideas where I'm going wrong?

This is still an issue. It seems to be occurring randomly. Users have reported it to me, but when I've gone into the console and tried it myself it works.

Hey @pezholio,
Try doing the following:
comment.to_management.publish

It should not be required, but in some very edge cases, it may incur in a race condition. Using this method should partially mitigate that race condition, though it doesn't ensure it, as the Manageable module which exposes the publish method is already doing it under the hood. But manually triggering it may affect the ordering in which it happens, making it more predictable in some cases.
Hope this helps,
Cheers

Cool. I'll give it a try. Thanks!


Not receiving 'remote-seek' event when triggering from headphones

Does this support seeking using headphone commands, one short then press and hold? I'm listening to the event through another library so I know it's coming through but TrackPlayer is not firing remote-seek.
It doesn't appear to be registered in index.js, not sure if that's intentional.
 const events = [             'playback-state',             'playback-error',             'playback-queue-ended',             'playback-track-changed',             'remote-play',             'remote-pause',             'remote-stop',             'remote-next',             'remote-previous',             'remote-jump-forward',             'remote-jump-backward', ];

'remote-seek' is it supported to iOS?


Split up integration tests per database adapter

Ignore tests in test/rpc

This is done for Redshift, Snowflake, and BigQuery. Still left to do:

Remove Presto tests (hah!) from test/integration
Move the remainder of test/integration under plugins/postgres/tests...? I could go either way on this one. We're leaving the dbt-postgres codebase colocated with the dbt-core codebase because it's so essential to our testing today. At the same time, we should continue to aspire and work toward decoupling them more.

This is done, enough to be serviceable for the time being. Our integration testing scaffolds badly need an overhaul. That's going to be a significant project for next year.


fix: reanimated crashes fix pt2

This PR resolves []
Description
Fixed the reanimated crashes weirdness

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

reanimated crashes - gkartalis

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

First I will merge the updated palette with this fix and when this is merged no more issues hopefully 🙏


Add Privacy Manifest

Hello,
I am an employee of Monstarlab company. I have a question about the Privacy Manifest.
At WWDC23 Apple is requiring all api calls that fall under this ruleset https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api#4278394
be added to a privacy manifest file.
Does SwifterSwift need to include this manifest?
Please let me know about your upcoming plans to apply the privacy manifest.
Thank you!!!

Hello，
I find that “Userdefaults API” is used, please add  a privacy manifest file.
Thank you!!!


Readme typo issue

Neither's Delight -> Nether's Delight
unexcepted -> unexpected

will be fixed soon

fixed


Log llama.cpp commit hash when installing using --verbose

See https://github.com/abetlen/llama-cpp-python/issues/223#issuecomment-1556207716
A bug looks to be with libllama, but in order to log the bug with llama.cpp we ideally need to specify which commit hash of libllama the bug occurs in for the upstream devs to isolate the regression.

Makes sense, there should be a build-info.h file generated inside the vendor/llama.cpp folder so we should be able to use that, I'll write a get_version function in the llama_cpp.py file to pull that in.


☂ some extra issue for using native helm code

[x] update website kubebb/website#15
[x] #113
[x] #114
[x] #93
[ ] #115
[x] #89

closed as we track in different issue