Streaming RTMPDisplay to twitter is broken

I am displaying Screen in portrait and resolution is 1284x2778.
on twitter its showing landscape and resolution is 640x480.
here is screenshot of issue. With Haishinkit its working fine.

Hello,
This is maybe related with no use metal to render image using always a landscape resolution and rotate image to simulate portrait resolution.
Also, this could be a problem with Twitter that doesn't support portrait reslution and rotate the image to fix it. Using the above way to solve it.
In this case, this could take time because I need develop a background metal render

Hello,
This is maybe related with no use metal to render image using always a landscape resolution and rotate image to simulate portrait resolution. Also, this could be a problem with Twitter that doesn't support portrait reslution and rotate the image to fix it. Using the above way to solve it.
In this case, this could take time because I need develop a background metal render

i forwarded rtmp stream to castr.com and forwarded it to twitter its working fine

This library to castr and then to twitter?
Anyway, I need to investigate it but for now I'm with the audio issue

This library to castr and then to twitter? Anyway, I need to investigate it but for now I'm with the audio issue

yes from Rootencoder to castr to twitter works.
thank you for your efforts @pedroSG94 .

issue with twitter

Hello,
Can you explain the issue in the last image?

Current encoder settings is not according to Twitter's recommended settings. I am trying manually setting these recommended settings its still not working.

Hello,
Can you explain the issue in the last image?

Current encoder settings is not according to Twitter's recommended settings. I am trying manually setting these recommended settings its still not working.

Hi @pedroSG94 any update on this?

I'm working on it

thank you, is there any update?

Hello,
I did a new release (0.0.6) that should fix encoder settings provided by twitter and fix the error in flv packet.

Hello,
I did a new release (0.0.6) that should fix encoder settings provided by twitter and fix the error in flv packet.

superb fixed


Fix/issue 61

Short Description
Fixes issue #61
Removed spaces in CSAR file name during the upload process.
File names passed to the private handleCsarUpload method will be checked for spaces and replaced with an empty string.
Proposed Changes
Fixes: #61
Tested with My Tiny Todo.

I'd prefer a replacement with "_".

One of the problems is that the CSAR filename is used often in ID's for variables in the generated BPEL Workflows and ID's normally are NCNames (https://www.w3.org/TR/REC-xml-names/#NT-NCName, https://stackoverflow.com/a/6159003), which basically doesn't allow to use spaces.
So a proper fix is either changing/removing spaces in CSAR Filenames or changing the ID generation, which will have to be fixed by a (possible) plethora of changes.
Additionally, we not just use the name for IDs, e.g., we copy many files unto VM's that are found by using the CSAR filename, I can't guarantee that this will not have side effects, that have to be fixed as well.

Is this PR then obsolete due to #75 ?

No, it's not. #75 is just the utility that will be used to fix this issue. Since we decided now what utility will be used, we can continue working on this issue.

If this PR is ready to review, please tag it with "needs review". Thanks.


PlotWidget: black image

Hello,
SILX versions:
Tested with SILX v1.0 and v1.1
Source code
Actions: we have a PlotWidget and we call: setData(array) to display a picture
Target computer
Here we have a Linux server running virtualization software: we are installing it on Windows (as usual)
But we had the same bug on other (unimportant) platforms.
We believe it is related to some computers and/or some configurations.
What we get
A black picture is displayed (instead of the test picture: I made it in the code and I'm 100% the array is correct)
We've been struggling on this bug: the image were not displayed (black screen).
It took me some time to track it down, but I'm pretty confident now, and to me it comes from SILX.
Urgency
I'm afraid this is an urgent request because we're installing on a customer's computer.
I'd like to discuss with you how we can go further (is there a way to have more logs? how can we understand what is wrong?)
I do speak french and english.
Ludo

It would be preferable to have a very small piece of code reproducing the issue.
Also, you should mention the backend used (matplotlib, OpenGL) nor the Qt binding module (PySide6, PySide2, PyQt5, PyQt6...)
To check if it comes from silx (or from matplotlib for instance) it should be very straightforward.
Have you tried to run one of the silx examples with different backends?
For instance:
https://github.com/silx-kit/silx/blob/master/examples/plotWidget.py
Specifying the OpenGL backend or the (default) matplotlib backend.
self._plot = PlotWidget(parent=self, backend="matplotlib")
self._plot = PlotWidget(parent=self, backend="opengl")

==> Is there a way to set the backend once and for all?

If you did nothing, the default backend is matplotlib.
It's up to you to choose what backend you want. In our own programs typically we allow the user to choose backend via a start parameter (--backend=opengl or --backend=matplotlib). That allows testing is something is wrong at the silx side or at the backend side.

Ok. That should be equivalent to "openg".
If you change it to "matplotlib", does anything get displayed? The visualization can be much slower, but it should confirm if there is a problem.

You should also test the file example I mentioned above.

Just in case it helps:
https://answers.microsoft.com/en-us/windows/forum/all/opengl-drivers/9b52324e-1083-44e1-83f7-ff2e35bf07a2

Making progress: with mpl, it shows black & white picture correctly (and it really works).
But, I get strange exceptions when using a color picture.
Basically, I've got a class GLPlotRGBAImageCustom that inherits from GLPlotItem and it says two methods are missing:
get_zorder and remove...
I'm a bit confused... Should I use another base class if not using GL? Or is there a general class that wouldn't be binded to a backend?
Can I have somebody on the phone?

Why don't provide a small piece of code showing the problem?

Can I have somebody on the phone?

I do not think that kind of support is to be expected according to the software license.
That would be really crossing a red-line. We can continue here on a good-will basis.
Please contact<EMAIL_ADDRESS>if you really want phone support and explain your issue.

Hi,
GLPlotItem is from the low level internal APIs and is only for use with the OpenGL backend (as the GL prefix stands), so it is "normal" that your GLPlotRGBAImageCustom does not work with the matplotlib backend.
The PlotWidget OpenGL backend requires OpenGL >= 2.0 (+ a few extensions that are available in OpenGL >=3).
You should probably investigate whether OpenGL is available or not and which version is available? This is what I would suspect first provided the virtualized environment.
E.g., is it working with another OpenGL based application?
There is also a function in silx to probe the availability of OpenGL. It is not catching all errors, but that can be a start: https://github.com/silx-kit/silx/blob/2c32c11068f3e411664f3a334fd948d5e763650d/src/silx/gui/utils/glutils/init.py#L92-L107
Do you get some error messages? Could you share code or make a small script to reproduce as @vasole suggested, that would help understanding the issue.

Or is there a general class that wouldn't be binded to a backend?

Yes, see the PlotWidget's item documentation

Ok, first, I checked on the machine, and... isOpenGLAvailable() says TRUE
But it doesn't work for some reason
This computer has absolutely no other piece of software. So no way to check other OpenGL apps.
I can send you an extract of the code, but it is quite obvious that we need OpenGL (that looks like the simplest option) or that we need to reimplement a bit of code for matplotlib or even better a generic version.
I'll dig deeper

Tested with SILX v1.0 and v1.1

Was it working with previous versions? or was it not tested?

A black picture is displayed

Is it only the image you display or also the axes?
How a simple code snippet such as the following using PlotWidget and OpenGL backend is behaving?
from silx.gui import qt
from silx.gui.plot import PlotWidget
import numpy

app = qt.QApplication([])

plot = PlotWidget(backend='gl')
plot.addImage(numpy.random.random(100).reshape(10, 10))

plot.show()
app.exec_()

If this is not working, does it work with commenting # plot.addImage... ?

First, thanks to your advice, I implemented a generic version of the OpenGL optimized class that we had. I have to say that it is much slower, but it works on my computer. We'll know if it works on the customer's computer on friday, but I'm pretty confident.
Then, I still have a question: how do I know if we need to unplug OpenGL optim. I've got the feeling that isOpenGLAvailable() is not working in our case. It says True, but I think it shouldn't.
Or should I use it with a (3, 0) version number as parameter? (it also says True and I think it shouldn't)
Thanks again, and... Crossing fingers for friday

Hi,

I implemented a generic version of the OpenGL optimized class that we had. I have to say that it is much slower, but it works on my computer.

Good to hear! This is why we have two backends: opengl for optimised display, matplotlib for making sure it works everywhere.
We don't have a 100% sure method to probe if OpenGL is available with the required version/extensions.
isOpenGLAvailable tries to open an OpenGL widget, but it is not checking that something is actually displayed there, only if an error is reported at some point. There are situations where this is not enough.
Maybe you can add a command line option when starting the application to enable/disable OpenGL? or a menu/button in the interface to toggle it at runtime?
For example in silx there is a QAction for it : https://github.com/silx-kit/silx/blob/2c32c11068f3e411664f3a334fd948d5e763650d/src/silx/gui/plot/actions/control.py#L621

That makes sense. FYI, I implemented it as an option that you can switch off.
The installation went well. Again thanks so much for your advice. I'm not sure I would have make it on my own. :-)

Please feel free to open it if a followup is needed.


Vue

@fforootd I have updated the readme and linked to the documentation now.

I still think we should setup a GH action as well as dependabot 😁


Block domain lapo.io

Perhaps the theft of ICO funds in 2018, since the active development stage ended almost 4 years ago. The project stopped showing signs of life after 2020.
https://foundico.com/person/luis-franceschi.html
https://icoholder.com/lapo-blockchain-19163
Funds raised: $7,373,914 or $40,257,067
lapo.io
The site was last updated in December 2021.
The roadmap for more than 4 years has been prescribing fake plans and values that change only year/percentage of progress once a year. Starting from 2020, nothing is being done at all.
https://web.archive.org/web/20190319014028/https://lapo.io/roadmap.html
https://web.archive.org/web/20200524191931/https://lapo.io/roadmap.html
https://web.archive.org/web/20210927222536/https://lapo.io/roadmap.html
https://web.archive.org/web/20220704154302/https://lapo.io/roadmap.html
https://web.archive.org/web/20230321211144/https://lapo.io/roadmap.html
https://medium.com/lapoblockchain
https://t.me/lapoblockchain
Closed to public viewing in the fall of 2019.

Theft of funds by developers when exchanging between XLM/BSC networks
#LAPO XLM/BSC Replacement machine
BSC Address Deposit
https://bscscan.com/address/0xc5017e37fb4ccb7ffd898caec0c43fb6dc55089a
List of deposits
https://bscscan.com/advanced-filter?tadd=0xc5017e37fb4ccb7ffd898caec0c43fb6dc55089a&txntype=2&tkn=0x082bb8716452Bf4E27E190ecf6efB89cCC7cd5C4
Total received 148607474.48412 LAPO BSC
Windraw XLM Address
https://stellar.expert/explorer/public/account/GAAXAMZCNLIT7YY6E4TDZZPYWLMCG7TSZUCOAU45FB4ZNAVGGOHE7KF5
Windraw XLM address 2
https://stellar.expert/explorer/public/account/GDKJ4YQ75DKPIC6FMR667GKAFXRKKTMAJ63UH4S7OMGVE4CXL26KVRET
Windraw List (Memo: Swap back)
https://stellar.expert/explorer/public/account/GAAXAMZCNLIT7YY6E4TDZZPYWLMCG7TSZUCOAU45FB4ZNAVGGOHE7KF5?account[]=GAAXAMZCNLIT7YY6E4TDZZPYWLMCG7TSZUCOAU45FB4ZNAVGGOHE7KF5&memo[]=Memo%3A %20 Swap%20back&type[]=payments
Sent 90552688 LAX XLM
Windraw 2 List (Memo: Swap back)
https://stellar.expert/explorer/public/account/GDKJ4YQ75DKPIC6FMR667GKAFXRKKTMAJ63UH4S7OMGVE4CXL26KVRET?account[]=GDKJ4YQ75DKPIC6FMR667GKAFXRKKTMAJ63UH4S7OMGVE4CXL26KVRET&memo[ ]=s wap&sort=id
Sent 32194529 LAX XLM
Total sent 122747217 LAX XLM
!!!Stolen by the developers:
148607474.48412 LAX BSC - 122747217 LAX XLM = -25860257.48412 LAPO BSC
The average price during that time period for 1 LAX = 0.00075/0.001 USD. (data from stellarterm and poocoin)
Stolen by developers in USD from 19395.2 USD to 25860.25 USD and removed from the liquidity of LAPO XLM (maybe more if you specify token rates)

Hello @broroduvce9p
Are you reporting that this token project is dead due to internal fraud or are you reporting something else? I would agree that it looks like the project is dead with there BEP-20 token and the XLM market looks like it is just some people unaware and/or just trying to get what little they can.
What was the "Swap Back"?
What kind of label are you suggesting?
As you know many token projects with good intitial intentions die due to poor execution. There are also DEVs that rug the project, not to be trusted DEVs that steal from the project or worse the customers directly, plain Ponzi schemes, out right pump and dumps, etc.
I have not dove into this much but initially it looks like a dead project that had devs (maybe just some bad actors) that drained the liquidity and killed it.
Your additional input is wanted. Can you clearly state what labels you think should be added to the Stellar Expert database?
Looking Towards The Future With You,
Rob

Exactly #unsafe label , from this dead dubious project the network will be better.
I think such a corpse is not even worth the time and how much xlm the developers stole. Only what was on the surface and can be checked through bsbscan and stellar.expert.

Hello @broroduvce9p
#unsafe dead is warrented, thank you for the report.
Do you know what they were doing with the "Swap Back"?
Looking Towards The Future With You
Rob

LAPO XLM / BSC Swap machine (turned off)
https://i.ibb.co/kXC7v2f/lapo1.jpg
https://i.ibb.co/fHK4fHt/lapo2.jpg
https://i.ibb.co/SQzD0Xw/lapo3.jpg
Transactions between the networks show the inconsistency in receiving/sending in favor of the developers for the last two years. Such manipulation could steal not only xlm, but also bnb.
Probably deserved the label #malicious and #unsafe.

Hello @broroduvce9p
I tend to personally think that is the case. But you can agree that it could also be seen as a failed bridging attempt that for some reason felt they needed to mint a new token to do this.
There are so many ill conceived projects that believe that minting a token will bring magic money to make their project work.
Rob

Hello @broroduvce9p
This issue is being closed. Please feel free to reopen it if you have new information.
Looking Towards The Future With You,
Rob


Can we remove sender in Vote, since signature in it

Both sender and signature in Vote:
https://github.com/cryptape/cita-proto/blob/b1409605bd4f7cf9b857d43fcad1b44b435df3a6/consensus.proto#L23-L27
And sender can be recovered from signature.
Ref:

CITA-Crypto-Trait
CITA-Secp256k1
CITA-ED25519
CITA-SM2

Sender is useless for signature?

sender in Vote

Sender is useless for signature?

sender can be recovered from signature.
And, we could not believe messages from network, so this sender can not be treated as a cache.
We have to calculate it from signature.
sender in SignedTransaction
The sender in SignedTransaction is redundant, too.
Because we can recover public key from UnverifiedTransaction.signature, then we can calculate address (sender) from public key.
But, this sender can be used as a cache (we trust the micro-services in the same node), so we could keep this sender.
https://github.com/cryptape/cita-proto/blob/b1409605bd4f7cf9b857d43fcad1b44b435df3a6/blockchain.proto#L64-L76

yeah.
I notice some codes like signature.recover(&message.crypt_hash()) and pubkey_to_address(&pubkey)  == sender. we check the sender from the signature, i'm not sure why do we need it at the beginning.


Add global/tenant notification audiences.

Add global and tenant notification audiences.
https://www.pivotaltracker.com/story/show/133200387

@gmcculloug Please review.

@bdunne Changes made.

@tinaafitz My comment was in reference to all of the allows, I didn't understand why they were allow instead of expect

@bdunne Thanks for catching that.


calendar_weeks table missing from Lake database

Question
Should I have a calendar_weeks table in my Lake database?
Screenshots

Additional context
I have some opendora devlake-go dora api queries returning zero values and I find the queries are referencing a calendar_weeks table not in my Lake database.  I see a calendar_months table but no calendar_weeks table.

With some help I see the calendar_weeks is a temporary, dynamic if you will, table.  The root of my problem appears to be that the the query is returning zeroes due to lake.cicd_deployment_commits table not having values in repo_id column. Not sure why that is.

@javaface Which version are you using? And only is field repo_id empty? If your datasouce has no deployment_commits , then cicd_deployment_commits will be empty.

cicd_deployments_commits is not empty. However, the repo_id column is not being populated.  Any idea why that would be?  Should have valued like github:GithubRepo:1:607853062.

@javaface  What's the version of DevLake you are using?

In my previous comment I indicated "I'm using v0.19.0 (latest)".  Is that what you're looking for?

Hi @javaface , we added the table calendar_months to simplify the SQL in the DORA dashboard. Since we don't have a weekly-level DORA metrics, we didn't add the calendar_weeks table.

Hello, I figured out that calendar_weeks has nothing to do with my issue.  The opendora team is working on it.  See  if interested.  Thanks.


functional-tester: run locally

Added support for launching etcd servers with separate ports and running the agent without root permissions. Includes a Procfile.
/cc @fanminshi @gyuho

LGTM. Thanks!

@heyitsanthony I don't see Procfile?

@gyuho good catch; forgot to add. All fixed.

LGTM. Thanks.

lgtm


Added useShortestSide property

I present my layouts in quite a personalized way, with overlays and popups using navigation and other tricks to avoid limitations of flutter and this library, so i use MediaQuery and max/min sizes to present a layout that uses heavily the shortest side of the screen in either landscape or portrait since i handle those cases internally.
The landscape breakpoints that this library provides are not fit for my use, and i would add a useShortestSide property that the user could try if they are in my position.
If you enable this property you don't need landscapeBreakpoints since all the breakpoints will be calculated on the normal breakpoints based on the shortest side, which might be the height or the width based on the rotation or screen size in the case of web.
It's optional for those who are comfortable with just letting this library do their job.

I would add that this would be useful mainly for apps that want to avoid scrolling screens and distribute their content based on width/height regardless of orientation.

Thank you for making this PR and contributing back to the repo!
Despite doing my best to implement landscape mode correctly, it's ironic that the "correct" way doesn't fit your use case.
I'll take some time this weekend to review. Meanwhile, do you think you'll be able to add some tests?

Yes I agree the approach that I take maybe is targeted to an specific mobile behaviour. Size units remain the same when the phone is in landscape mode or portrait mode, and only a few widgets change the hard coded size depending on the orientation, the rest of the widgets maintain their size but change the way they are displayed (ex: use listview in portrait and grid view on landscape, or use a side drawer on landscape and bottomappbar on portrait just to name a few)
This is a behaviour that I think fits with the material design guidelines and I used a heavily modified fork of responsibe_builder with language and theming support as an internal library until a better alternative was found or made , the drawback was that it used inherditedwidget and context to get the size unit per device since flutter still doesn't allow to change devicepixelratio successfully
So this library is just a better alternative but the expected behaviour is not there, as an example on a folded Galaxy fold the size unit change is really noticeable, the width is not proportional and an appbar takes almost half the screen on landscape and little to no space on portrait , but using the smallest size allows me to design my layout on landscape and just modify selective things to make it work on portrait. Really specific I know. But I guess one must take those things into account 😅
I will make tests in this week, since I don't know how this property will behave with normal and landscape breakpoints provided, maybe when enabled it should disable landscape breakpoints because it will calculate the breakpoints without taking orientation into account.
If I have time I will also post some screenshots to showcase how this changes the way normal breakpoints are handled 😁

3 tests have been added, one to verify that useShortestSide  doesn't break anything / is disabled by default, other to verify that the scaleFactor is the same on landscape or portrait using useShortestSide , and the third one to test a curious behaviour that i was expecting to implement by myself,  it turns out that when both breakpointsLandscape and breakpoints are provided, useShortestSide will keep measuring based on the shortest side , so landscape breakpoints will trigger on the same way but using the shortest side instead of the width. This is useful if you want to shrink a little bit the scaleFactor on landscape  to make better use of the available space. I will add images showing this behaviour

This is the new behaviour. useShortestSide  is true, and ONLY normal breakpoints are set, but it should be the same when landscape and portrait breakpoints match exactly

And this behaviour is triggered when useShortestSide  is true but the portrait and landscape methods are different, on portrait it gets smaller, completely the opossite of the default behaviour, but, again, it was something that i needed that came for free since the space can be managed now based on the shortest screen size, and orientation, independently

Thank you for the great work here!
Please give me a bit more time and bear with me.
There's a lot going on my end.

Thank you for the thorough tests and the very illustrative examples around the interaction between shortest side and landscape breakpoints. They addressed my concerns and made merging very easy.
I apologize again for the delay. Please email me at<EMAIL_ADDRESS>with your name and email so I can add you as a contributor to this project, if you wish.
To make up for the delay, I can also give you alpha access to Codelessly.


Disable mixed evaluations and optimize database calls

Disable mixed evaluations and remove c# processing of queries where possible. Will cause errors on mixed evaluations so be careful if merging it in.

https://docs.microsoft.com/en-us/ef/core/querying/client-eval#disabling-client-evaluation


Better: Use Alchemer API URLs by default

The goal of this PR is to switch to the Alchemer API URLs

LGTM


[Nuxt3-pinia-vuetify]: Add storybook

Add storybook for all the components

[ ] CounterExample
[ ] Fetch Example

There's no official way to implement storybook yet (see: https://github.com/nuxt-community/storybook/issues/330). Lets hold off until an official way for Nuxt 3 is out.


Logstream tree node

Fixes https://github.com/Microsoft/vscode-azureappservice/issues/567
Relies on this PR: https://github.com/Microsoft/vscode-azuretools/pull/296
I'd still like to add icons and possibly change the wording/behavior.  I figured it made the most sense to change it from connect -> disconnect, but please let me know if you disagree.

I'm running into an issue where the Log Streams node isn't the first child despite being the first element in the array.  Does VS Code's tree provider automatically sort children alphabetically or something?

Yes it's sorted by default but you can change that: https://github.com/Microsoft/vscode-azuretools/blob/master/ui/index.d.ts#L250

To help with all the edge cases, I might suggest using an Event pattern on ILogStream. Similar to what you did here:
https://github.com/Microsoft/vscode-azuretools/blob/master/ui/index.d.ts#L23
I imagine there would be an onDisconnect and onConnect event and you would just hook them both up to refresh the LogStreamTreeItem.

Yeah, I agree that the value seems very low for the amount of work needed to make sure that it handles all test cases.  I just had done some of the work for "Disconnect" and wanted to keep it... 😭
It's probably not worth waiting on an event for it.


Issues on https://learn.microsoft.com/en-us/microsoft-365/compliance/increase-the-recoverable-quota-for-mailboxes-on-hold

In the topic https://learn.microsoft.com/en-us/microsoft-365/compliance/increase-the-recoverable-quota-for-mailboxes-on-hold
Tip section under Step 1: Create a custom retention tag for the Recoverable Items folder has 2 issues.

The link "Change the deleted item retention period for a mailbox in Exchange Online" is broken, it jumps to the top page of www.microsoft.com
'defined by the AgeLimitForRetention parameter' is probably not accurate, parameter could be 'RetainDeletedItemsFor' instead of 'AgeLimitForRetension'. Please verify and update.

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

ID: d2e247ee-12d5-add4-756c-b8a8d4ebb7a3
Version Independent ID: 889ce47a-58f5-7bc1-2343-64dcd4bdac2a
Content: Increase the Recoverable Items quota for mailboxes on hold - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/increase-the-recoverable-quota-for-mailboxes-on-hold.md
Service: o365-seccomp
GitHub Login: @robmazz
Microsoft Alias: robmazz

@TadaoMachida Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10473
Once the author approves, the changes will be live.
For 2. the Statement seems to be accurate, MS recommends that the AgeLimitForRetention value matches the value set for RetainDeletedItemsFor parameter of the mailbox.
Hope this helps!
Thanks
Sri

@TadaoMachida Closing it as per author's comment in PR. Thanks


Remove sprint Python 3 sprint

The website's build process has already been ported!

Peter. Why have you not come to 'Spoons?


adjusted IsMale variable to updated GenderId to resolve TrainerRoad e…

…rror

adjusted missing variable to resolve sync error


Update monthly peak loads based on two-day peak load period.

The issue addressed in this PR has to do with the peak load analysis in particular. If a peak load is found to be on the first day of the month, then the 48-hour load profile created takes the previous months last day and the first day of the current month. An issue can arise when the current months maximum load is less than the maximum load found in the last day of the previous month. The result is that the two-day nominal load profile could produce a greater temperature difference than the peak load profile does.
closes #84
closes #88

The following items are left that I can think of right now:

[ ] Document the changes in change log

@mitchute  I realized I kind of like your check better for abs(diff) < tol since the maximum of the month should be in the 48-hour period so that only wouldn't be true when the max is from the first 24 hours that is the last day of the previous month (and would always be larger than the current months max if its the max of the 48-hour).


docs/vtpm: add aziot-edge use case

Update the docs to include the aziot-edge use case for vTPM, how to set it up and use it.

Oh, it's so satisfying to see tests not running for the PR that only update docs.


Firefox: Drag event hangs

I am using angular-ui-tree 2.6.0 with angular material. D&D in Chrome works great.
In Firefox I have the following issue:

I drag a node and try to move it.
I have to release the button to move it around
I can drag the node around

What could be the reason for this behavior ?

It also appears with 2.9.0 ....
ANY HELP URGENTLY APPRECIATED

It also happens to me on Firefox v 40.0.3 on Mac OSX v10.10.2. Any way to fix this bug?

I managed to solve the issue. In my case I was experiencing problems with ui-tree-handle applied the  tags. I turned my  tags into s and everything works fine now also on Firefox. I hope this can help you.

I tried it but the  does not solve the issues. Are you also using angular material ? Do you have any code snippet as an example ? Have you also customized callbacks ?

Have nailed it down to the following problem in FF:

the img object inhibits the FF drag and drop. If you click slightly outside the img where the ui-tree-handle div is placed D&D works fine too.
Workaround: Place the img a  background image in a CSS class !

I had the same problem. It seems like it's not about angular-ui-tree, it's just the way Firefox handles images and links dragging by default. Add draggable="false" attribute to your  or , it may help.

Closing this issue due to inactivity. See #815 for more information.
Please create a new issue is this still occurs with the current version of the component.


fix: should call config hook in idle callback

Checklist

[x] npm test passes
[x] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message follows commit guidelines

Affected core subsystem(s)

Description of change

config 的 lifecycle hook 是 loader 事件触发，当不存在 config 文件的时候不会触发 loader 的 before/after 事件，导致 config 的 lifecycle hook 也不会触发
所以在 loader 事件中加个 idle 事件，用于当某个 loader 没有被触发时回调，从而解决 config loader 没有使用时也能触发 configWillLoad 及 configDidLoad

Codecov Report
Base: 92.42% // Head: 92.64% // Increases project coverage by +0.22% :tada:

Coverage data is based on head (91db06c) compared to base (9f3b77c).
Patch coverage: 85.71% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #218      +/-   ##
==========================================
+ Coverage   92.42%   92.64%   +0.22%
==========================================
  Files          55       55
  Lines        1293     1306      +13
  Branches      218      220       +2
==========================================
+ Hits         1195     1210      +15
+ Misses         98       96       -2

Impacted Files
Coverage Δ

src/loader/factory.ts
93.06% <80.00%> (+0.36%)
:arrow_up:

src/loader/loader_event.ts
92.50% <83.33%> (+0.83%)
:arrow_up:

src/application.ts
91.42% <100.00%> (+0.51%)
:arrow_up:

src/scanner/scan.ts
95.89% <100.00%> (+1.36%)
:arrow_up:

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

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