fix(UI): anchor the tool panel buttons at the bottom

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

This PR was opened to anchor the tool panel buttons at the bottom of viewport in mobile device in the Challenges/Steps.
The original issue was described in this comment, and this PR makes tool panel buttons anchored at the bottom of viewport not only when any challenges is opened but also when viewport height is changed by swiping down/up on mobile device, as shown in the image below.

Affected pages are:

Legacy Responsive Web Design
(New) Responsive Web Design
JavaScript Algorithms and Data Structures
Front End Development Libraries
Data Visualization
Coding Interview Prep

The code was tested on android studio emulator (Pixel 6 PRO/android OS 11.0/Chrome) and mobile simulator extention of Chrome and Firefox PC browser locally, but not tested in real mobile device because I don't have the one which can preview the fixed fCC curriculum (I actually need help).
And also the test have done in Chrome, Firefox, Edge, and Brave PC browsers with windows 11 PC.

In the fixed code, const vh = String(window.innerHeight - 1); contains -1 to avoid appearing vertical scrollbar of body when changing the height of viewport of Chrome PC browser as shown in video below.

The double vertical scrollbar was appeared because html and decendant elements overflow from viewport.
window.innerHeight is Integer, so when viewport's height is float such as 633.6px, this value is rounded and window.innerHeight become 634px, therefore this causes the overflow.

@mmatsumoto1026, Thank you for your follow up pull request.  I tried the current live version of the Responsive Web Design step 1 using my iphone 11 max pro with firefox and opera, but didn't run into the issue.
You can see the preview of your pull request on your mobile phone using gitpod. (Click on the first comment with the gitpod comment from your phone)
I am also tagging @Sboonny who has more experience with Gitpod than me to assist you in case you are facing issues on gitpod.
Also, a CSS solution is preferred if that is possible.

@Sboonny I believe the only way you can "force" the keyboard to stay open is by setting the focus on an element that triggers it. When you click the Run button then focus is moved to that button and thus the keyboard disappears. So we would need to programmatically move the focus back to the editor input after clicking the button, but I'm not sure that would be the best for accessibility. Personally, I think we should leave it as is, but if this is something that people want to consider I will be happy to look into the accessibility issue further.

Ya the best option as I see it, is to not use focus somehow to display the keyboard that handles user inputs and find a 2nd way I have searched for a long while, and to be honest I couldn't find one, so I think maybe it isn't possible. anyway I will open an issue if we want to discuss this further, and maybe we can think of 2nd way, or not implement it.

@Sboonny I'm not sure I completely understand your idea for keeping the keyboard open when running the tests. Perhaps you should open a new issue for this and explain in more detail.

Hello reviewers, Thanks for checking the current live version and fixed version code in your mobile device.
@ahmadabdolsaheb, I can now see not only the preview of my pull request using gitpod but also of current live version, after updating the OS of my iPhone SE (iOS 14 => 15.7.1).
So I also tried the current live version of the Responsive Web Design step 1 and Basic JavaScript under JavaScript Algorithms and Data Structures: Comment Your JavaScript Code using my iPhone SE with Chrome, Firefox, Safari and Opera browser, and didn't run into the issue.
It seems that the issue may only occur in android mobile device.
Unfortunately, after trying some ideas out, I couldn't find out the CSS solution.
But in the future, we may be able to solve the issue using new CSS viewport units like svh or dvh, which is not supported by Chrome for Android and Opera Mobile now.
@Sboonny, I agree with your idea that is not only stopping the keyboard from closing, when campers press "Run" or "Help", but also copying the clear icon in our search bar.
But in this pull request, I will focus on solving the original issue. (I will read the article about Parkinson, during study about accessibility fundamentals)
@bbsmooth, thanks, it's owing to detailed description which you shared in the comment.

I'm still trying to find out how to solve the issue with CSS.
Test environment is:

Pixel 6 Pro (in android studio emulator)
OS: android 12.0
browser: Chrome

Test page using Gitpod are:

(New) Responsive Web Design: Learn HTML by Building a Cat Photo App (Step 1)
JavaScript Algorithms and Data Structures: Basic JavaScript: Comment Your JavaScript Code

The height of the root element (<html> element) is now set to height: 100%; in global.css, but on android mobile devices height: 100%; is the height of the viewport when the address bar is displayed.
It seems that this is what is causing the "tool panel buttons not anchored to the bottom of the viewport" issue.
If we set height: 100vh; on the html and body elements, the tools panel buttons will appear at the bottom when the address bar is not visible, but then if we swipe down, the top address bar will appear and the tools panel buttons are pushed downwards and disappear (not anchored at the bottom).
The challenge I'm facing here seems to be that we should find out a way to detect changes in viewport height on android mobile devices via CSS.
First, height: -webkit-fill-available; was tested to set for html and body element's height, but it did not expand the root element when the addressbar is not displayed (same behavior of height: 100%;).
Then, height: 100dvh; and height: 100svh; were tested to set for html element's height, but it seems to be invalid in android Chrome now, and height: auto was applied as default value, and they did not anchor the tool panel buttons at the viewport's bottom.

Then, height: 100dvh; and height: 100svh; were tested to set for html element's height, but it seems to be invalid in android Chrome now

Yep, Chrome on Android does not support these units yet, which is ironic, because that's where they would come in handy. I'm not sure there is a pure CSS solution for this right now.

@Sboonny,
I've read this article and I realized that it seems we can use PostCSS in the areas of CSS4 features. (Actually, I have barely been able to understand about PostCSS.)
To find out the CSS solution, Now I need study PostCSS with referencing the URL you provided.
Thanks for informing it!

@mmatsumoto1026, thanks for doing the due diligence. I am open to using the JS solution and optimizing the solution in another pr.
Since I don't have an android device, I would defer the review to @Sboonny, and @bbsmooth.

The second video of the above comment seems to contain two issues, they are:

When keyboard are displayed (in Step curriculum), tool panel buttons are not anchored at the viewport's bottom (immediately above of keyboard). It can also be reproduced in iPhone SE like below image. And It seems to also be occured in Challenge (first video).

When keyboard are displayed (in Step curriculum), If user swipes up, the viewport itself appears to be completely floating since universal navbar and bread crumb are pushed upwards. (It seems to also be occured in Challenge and
reproduced in iPhone SE.)

These issues are not reproduced in android studio emulator.
So they may be iOS/ColorOS specific issues.

Sorry, @Sboonny. I read PostCSS's PostCSS Preset Env features document, but I could not find out the way to load svh or dvh of new CSS viewport units with the plugin or feature.
Alternatively, I persued JavaScript solution for issues which are described in original issue comment and the comment I mentioned above.
The code was tested on android studio emulator (Pixel 3a XL/android OS 12.0/Chrome) and my iPhone SE with Chrome, Firefox, Safari and Opera browser.
I think OPPO A55's user agents contains Android, So the issue of not anchored the tool panel buttons at the bottom of viewport and floating window issue when virtual keyboard is displayed might be solved.
Also, the code was tested in Chrome, Firefox, Edge, and Brave PC browsers with windows 11 PC both locally and using gitpod.

Now this PR is ready for review. Thanks.

Works 👍, found two issues:

The spacing can break when campers try to scroll.

https://user-images.githubusercontent.com/88248797/208252193-13f91941-4ae9-44f8-81bf-8ccabba82ae9.mp4

white area is shown when the keyboard is closed

https://user-images.githubusercontent.com/88248797/208252204-bb790a95-3b6f-41a5-8531-fd126ba386d7.mp4

Thanks for sharing issues!

The spacing can break when campers try to scroll.

It seems that I overlooked to prevent touchmove event for window scrolling in monaco editor.
But at the same time, the editor's contents should be scrollable.
I will try to implement this to always anchor the tool panel buttons at the bottom of viewport and avoid window scrolling or floating.

white area is shown when the keyboard is closed

Sorry, this is because the html element's height is changed when virtual keyboard is closed.
Since It seems that toggling the keyboard can fire the visualViewport?.addEventListener resize event, I will try only moving the buttons when toggling the keyboard and not change the html element's height.

We are officially on Node.js 18 now. We have changed the merge requirements accordingly.
You will need to rebase this PR against the main branch OR Click the "Update branch" button to get the new checks going.
Thanks for your contribution.

Now original and shared issues in this PR are solved and all checks passed so the code is ready for review.

Found two issue, in the old JS course
https://user-images.githubusercontent.com/88248797/208667448-aec325c3-5015-4f7e-aaed-9d156a8d5bb5.mp4
https://user-images.githubusercontent.com/88248797/208667336-e48f5e7d-223b-4fa1-884b-1cb6a009ae84.mp4

I just noticed Bruce PR that removes this in new RWD (thanks to Murgush messages) https://github.com/freeCodeCamp/freeCodeCamp/pull/47683, if it helps you can ignore the new RWD styled courses and focus on the old curriculum layout

Thanks again for sharing issues!
After confirming two new videos above, I noticed it seems that space breaking issue which occured when campers try to scroll is solved, but tool panel buttons are not properly positioned or disappeared when virtual keyboard is displayed, with using Brave browser in ColorOS.
According to the first video, it seems that the virtual keyboard is opened in the step below.

When instructions pane is displayed, address bar is not displayed at the top of viewport, while the tool panel buttons are displayed and anchored at the bottom.
Then with tapping "Code" tab, address bar appear and push the buttons down from the viewport and they will finally disappear.
After (or in the middle of) 2. virtual keyboard appear but "resize" event will not properly position the buttons at the bottom of viewport which is immediately above of the keyboard or even not display them.

And according to the second video, it seems that the virtual keyboard is opened in the step below.

When editor pane is displayed, address bar is displayed at the top of viewport, and also the tool panel buttons are displayed and anchored at the bottom.
Then with tapping editor textarea, the buttons immediately disappeared.
After 2. virtual keyboard appear but "resize" event will not properly position the buttons at the bottom of viewport.

These behavior is not reproduced in android studio emulator(Pixel 3a XL, android 12 OS, Chrome) and iPhone SE with browsers which include Brave.
After investigating the two videos, I thought that two event listeners might be in conflict, so css setting order
will perhaps be reverse, or during conflicting, window.innerHeight and visualViewport?.height might not be properly read in visualViewport resize event listener in ColorOS.
To avoid this conflict, I pushed the code which simply delay the timing of setting the CSS after the visualViewport event listener fired. The code was tested in android studio emulator in the video shown below.
https://user-images.githubusercontent.com/44451585/208928086-5eff6631-4123-4520-b7a4-c125057353f0.mp4

I just noticed Bruce PR that removes this in new RWD (thanks to Murgush messages) #47683, if it helps you can ignore the new RWD styled courses and focus on the old curriculum layout

Thanks for notifying about the PR so I can focus on the positioning of tool panel buttons in the old curriculum.

@Sboonny, I tested the code without position: relative; in #mobile-layout .tab-content selector in classic.css using gitpod.
In android studio emulator, it didn't run into issues without the CSS property, but in PC browsers (windows 11, Chrome, Edge and Brave), it displayed vertical scroll bar of body in mobile layout. In Firefox PC browser, the scroll bar did not appear without the css property.
The scroll bar was removed with the CSS property in #48231.

Here are few useful links I came across that we could use as a reference:

https://stackoverflow.com/questions/39392169/footer-is-pushed-up-when-keyboard-is-open-html-css
https://developer.mozilla.org/en-US/docs/Web/API/VisualViewport#simulating_position_device-fixed

Sorry didn't mean to close it.

Here is a video about the bahaivor
https://user-images.githubusercontent.com/88248797/211818325-2e333fcf-3afd-4065-8826-b6050a1aad48.mp4

Thanks for your review @ahmadabdolsaheb and description about hiding (and showing) address bar with video @Sboonny.

I was not able to hide the address bar on the Android studio emulator or my iPhone. :/

I also could not hide the address bar in my iPhone SE. But with referencing @Sboonny's video that shows how to hide and show the top address bar and bottom menu bar, it seems that if we can hide the bars, we will able to offer more real estate to read instructions and write code.

If opening and closing the top address bar changes the visualViewport.height, can't one logic to handle both scenarios?

Opening and closing the top address bar will changes the visualViewport.height, but so far It seems that we can't hide the address bar because after opening the address bar, the height of the html element (and its descendant elements)  is fixed to window.innerheight, and the element has no height needed to close (or hide) the address bar again.
I've tackled to improve the code so that the address bar can be opened and closed freely with setting the height of html or body element in the conponentDidMount and the event listener , but so far I could not achieve the feature.

I've tested the code with my iPhone and android studio emulator with using ngrok. Thank you @ahmadabdolsaheb.

Took a look a look with @Sboonny, and removing the scroll related function did not change the general behaviour.
Let us know if you have further considerations. Other than that, LGMT. Thanks for the hard work.

Thanks for cleaning up the code and review, @ahmadabdolsaheb.
I've not told you about the scroll related function avoidWindowScrolling and the touchmove event listener, but this is for solving this comment's issue when editor pane is opened in mobile phone.
And also, document.documentElement.style.height = String(window.innerHeight) + 'px'; in componentDidMount has the purpose to prevent the height of the html element from being smaller than the window.innerHeight when the challenge is opened with the address bar is not opened as shown in below image.

Besides, document.documentElement.style.height = String(window.innerHeight) + 'px'; in else statement in setToolPanelPosition prevents from to keep the height of the html element expanded when the address bar is opened, after opening the challenge which is explained in original issue as shown in below image.

@ahmadabdolsaheb and @Sboonny,
I've tried to make address bar be able to opening and closing as shown in below video.
The branch of the prototype code is here.
https://user-images.githubusercontent.com/44451585/216021795-ca45a5cb-e6c7-47fc-adc0-df2c0ac9a574.mp4

You have allowing the camper to scroll past the content, then reduce it height. 🤔
https://user-images.githubusercontent.com/88248797/216033551-f4f4369a-e81b-4d81-a88f-92e0cc536fc4.mp4

Thanks for the explanation.
I could not replicate the https://github.com/freeCodeCamp/freeCodeCamp/pull/48586#issuecomment-1356329327 on the Android studio (Pixel Pro 6 API 33) and my personal iPhone.
@Sboonny, could you double check if the issue is still around?
Also, I came across the following issue when going around the tabs on the new Responsive Web Design challenges. The issue does not happen consistently and I could not replicate it on my phone.

@mmatsumoto1026, the next context isn't the issue, but I think you deserve to know, because you have been the one working the hardest here, I was hoping to get this merged, because of your hard work and this provides a fix for an issue, but the fix is fixing a side effect not the real problem.

In my opinion, the issue is we are trying to solve a side effect. If you look at this video, you will notice an issue in the freeCodeCamp production repo, the context inside the step isn't scrollable. This is related to this PR.
https://user-images.githubusercontent.com/88248797/216382071-64cafa63-9401-4cf0-b538-787a6e70919b.mp4
How does this affect the PR, when you tried to solve the issue in this comment, you made it possible to scroll through these content which is good, but you made it possible to do the default, I.e. browser shouldn't stop campers from scrolling through these content like shown in the previous video, and there is something in the codebase that stops the browser from doing the default behavior.
Fixing this cased this bug, the ability to scrol,l while the context is stopping the scrolling, which cases the height to increase
https://user-images.githubusercontent.com/88248797/216387928-bc55e954-591c-4ed9-94ba-edb3a96cebf8.mp4
There is something that ask the browser to stop the scrolling behavior, push the buttons out of the viewport in the new RWD, forces you to add height then remove it to have a functional experience in the pages.
Similar to how Bruce need to add height: auto, which is the default behavior for the height, in this PR https://github.com/freeCodeCamp/freeCodeCamp/pull/49096.

Why am I bringing this up? because https://github.com/freeCodeCamp/freeCodeCamp/pull/48586/commits/f059bebc1124b9ba22213661f8aa315b634c5236 and https://github.com/mmatsumoto1026/freeCodeCamp/tree/test/anchor-the-tool-panel-buttons-at-bottom solve the issue but not the cause, and both of them provide their own issues, mostly the need to remove the added height which cause flickering and slow connections not loading the JavaScript fast enough.

For this to be trully solved:

The browser should be able to scroll throught the context without he need to add logic to do so, but remove the cause for it to not do so, so you won't have the issue in the context of RWD or scrolling through the hints in the old JavaScript.
The container that carry the instruction shouldn't relay on height to position the buttons.
After remove the code that cause the two previous issues, you will find adding logic to position the button about the keyboard is easier than the current implementation.

@Sboonny.
This PR was intended to anchor the tool panel button at the bottom, but I apologize for that I had not understood of real problem.
I hope that our issue-solving effort will contribute to the codebase.

@Sboonny

If you look at this video, you will notice an issue in the freeCodeCamp production repo, the context inside the step isn't scrollable. This is related to this PR.

This is actually caused by monaco and not this PR. The monaco editor steals the touch events over the widgets that contain the instructions and the buttons/feedback. There is no solving that issue, it's a defect in monaco. That's why I added a scroll gutter over the line numbers as a workaround to this problem so that there would always be a place to scroll.
Sorry I did not comment on this sooner. I have been waiting quite a while for this PR to merge so that we can remove the tool panel buttons from the mobile layout for the steps. Since this scrolling issue isn't something we need to worry about, is the PR ready to be merged or are there other issues that need to be addressed?


[BUG] Empty logs in RKE2 clusters

Rancher Server Setup

Rancher version: 2.6.8
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2

Proxy/Cert Details: none

Information about the Cluster

Kubernetes version: v1.24.4+rke2r1
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin

Describe the bug
Then I want to see logs in Rancher of any resource, logs are empty
To Reproduce

Result
Expected Result
I want to see logs in Rancher like it work in rke1. Also in rke1 clusters feature of view logs in rancher is still work.
Screenshots

Additional context

Ticket 39313 - Test Results
With Docker on a single-node instance:
Verified on rancher v2.6.9-rc6:

Fresh install of rancher v2.6.9-rc6
Provision a downstream AWS Node driver cluster w/ k8s v1.24.4+rke2r1
From Cluster Explorer > Pods > All namespaces, observe logs from any resource
Verified - fleet-agent logs found
Verified - cattle-cluster-agent logs found
Verified - rke2-metrics-server logs found

Additional Comments:
Unable to reproduce; All attempts to view resource logs via Rancher UI resulted in the logs being accurately provided

It seems this issue was reported using HA Helm w/ RKE2 local.  Re-testing, as above scenario may not be applicable.

Ticket #39313 - Test Results [pt. 2]
With HA Helm:
Verified on rancher v2.6.9-rc4:

Fresh install of rancher v2.6.9-rc4 w/ RKE2 local - [ v1.24.4+rke2r1 ]
Provision a downstream RKE2 AWS Node driver cluster w/ k8s v1.24.4+rke2r1
From Cluster Explorer > Pods > All namespaces, observe logs from any resource
Verified - fleet-agent logs found
Verified - cattle-cluster-agent logs found
Verified - rke2-metrics-server logs found
Verified - system-upgrade-controller logs found

Additional Comments:
Still unable to reproduce; All attempts to view resource logs via Rancher UI resulted in the logs being accurately provided


chore: automated node runtime deprecation warnings

This changes how the node release support information is modeled so that
the end-of-life dates are configured, so that @jsii/check-node can
automatically start warning a month ahead of a runtime's EOL date, so we
can drop support right on EOL day if needed wihtout taking users by
surprise.
This also includes tweaks of the messages that get printed out to STDERR
when an unsupported/untested/deprecated/end-of-life version is being
used, to increase clarity of provide more information about migration
options.
Finally, this adds node 18 (initial release 2022-04-19) to the test
matrix.

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

ℹ Note
With these changes, we will issue messaging that we may stop supporting Node 12 on the first release after 2022-04-30, however since we won't have had a warning up for at least 30 days, we'd effectively not drop Node 12 support before 2022-05-30 (or later, depending on when this change gets released, and unless we are required to drop that release on security reasons).
I still decided to keep the post-EOL messaging as-is: once a release is EOL, it is no longer supported (although it might still work) as we may be required to pull it without warning in case a severe CVE is discovered within our intended 30 days notice period.


Ensure tests pass typescript compilation and bump jest and ts-jest

The newest ts-jest compiles your tests and will fail by default if your
tests don't pass typescript compilation.
So that upgrade is smooth whenever you want to do that, lets ensure the tests compile successfully.

Rebase and merge :)


Create a doc to explain how to use explorer

Minifabric can be easily used to watch activities happening on Fabric network. Need a doc to explain how to easily do this.

I can Pick this Up, Thanks


Fixed tesselation issues.

Original pull request by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

SbTesselator uses a wrong algorithm for the calculation of the circle center for its Delaunay triangulation algorithm. The center was not calculated in the triangulation plane. Therefore triangles were missing in the output shape. Some other algorithms used in the tessellator were carefully examined and replaced with algorithms from comp.graphics.algorithms FAQ.
Fixed errors in Coin tessellator leading to missing triangles. Issue #177 and no. 213 from old Coin/docs/BUGS.txt.
We should thoroughly test this fix for performance issues and side effects!
Comments on PR are very welcome.

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

Impressive digging!
For pointOnEdge, you document The point is on the edge if its distance is less than epsilon. But looking at the code it seems that you compare the square of the distance to epsilon, which may be too loose a tolerance. You may want to add epsilon2 defined as sqr(epsilon) and compare against that instead. Note I have not done any testing.
Cheers, Bastiaan.

Original comment by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

Thanks for the valuable feedback, Bastiaan. I changed the comparison statement to compare now against square epsilon and tested again. Committed some test files for the tessellation of common edge cases. Cheers, Volker

Original comment by Mark Goldberg (Bitbucket: MarkGoldberg, GitHub: MarkGoldberg).

FYI: I replied to the original issue.


PGP-Key: Problem with leading zero

Hello Guys,
i ran into a problem with PGP-Keys. After i've added my Key to Gitea and made my first signed commit it says that theres no matching key. I compared the key showed in the commit with my configured key and found out, that the leading zero of my key is missing in the commit-view.
Maybe there's a bug related to leading zeros in PGP-Keys?
Account -> PGP-Keys

Commit

Installation Data

Gitea version: 1.14.4 and 1.15.0+RC3

Database:

[x] MySQL

On 1.15.0-rc3 the key tells you which identities it matches - that is the email addresses that were activated when the key was installed - does the commit you are trying to verify have match one of those identities?
On 1.15.0-rc3 you can verify the key to match any of your user's activated email addresses. Have you verified the key?

Also, have you tried re-adding the key? If the key was added a long time ago - it's possible that it was affected by a previous bug that has been fixed.
If this genuinely is a bug it would be helpful to see an example of a commit on try.gitea.io with the key. If you'd prefer to not to make that public contact me on discord directly with details so that I can replicate.

@zeripath thank you so much!

On 1.15.0-rc3 the key tells you which identities it matches - that is the email addresses that were activated when the key was installed - does the commit you are trying to verify have match one of those identities?

the keys mail adresses where already activated before adding the key. so i've thought it would be enough just to add the key.

On 1.15.0-rc3 you can verify the key to match any of your user's activated email addresses. Have you verified the key?

That's it! After verifying the key everythink works like expected. Is this a new feature or have i just been blind in 1.14.4?

Also, have you tried re-adding the key? If the key was added a long time ago - it's possible that it was affected by a previous bug that has been fixed.

It was a new key added in 1.14.4, but i remembered the bugfix for this old problem so i've guessed it could be the same reason in my case too.

If this genuinely is a bug it would be helpful to see an example of a commit on try.gitea.io with the key. If you'd prefer to not to make that public contact me on discord directly with details so that I can replicate.

b.t.w. i've created a small script for download and updating gitea a long time ago. Maybe it could be usefull for lazy bones like me ;-)
https://entwicklung.hq.tosit.de/Snck3rs/Gitea-Updater

@zeripath thank you so much!

On 1.15.0-rc3 the key tells you which identities it matches - that is the email addresses that were activated when the key was installed - does the commit you are trying to verify have match one of those identities?

the keys mail adresses where already activated before adding the key. so i've thought it would be enough just to add the key.

It should be - I guess the key has to have the email address in it too.

On 1.15.0-rc3 you can verify the key to match any of your user's activated email addresses. Have you verified the key?

That's it! After verifying the key everythink works like expected. Is this a new feature or have i just been blind in 1.14.4?

Yes - new feature in 1.15 - see #14054

@zeripath thank you so much!

On 1.15.0-rc3 the key tells you which identities it matches - that is the email addresses that were activated when the key was installed - does the commit you are trying to verify have match one of those identities?

the keys mail adresses where already activated before adding the key. so i've thought it would be enough just to add the key.

It should be - I guess the key has to have the email address in it too.

that's strange. my key should have the mail address in it. plus a second identity with another email address. Both mail addresses have been configured in my gitea account before adding the key itself. if you want to dig deeper into that case i could provide you the informations you need.

On 1.15.0-rc3 you can verify the key to match any of your user's activated email addresses. Have you verified the key?

That's it! After verifying the key everythink works like expected. Is this a new feature or have i just been blind in 1.14.4?

Yes - new feature in 1.15 - see #14054

I think it would be useful to see an example commit that isn't verifying on try or elsewhere.


Allow checkboxes in the floating quest window to be checked

Currently, the floating quest window is just for viewing but I think it would be helpful to allow the checkboxes to be checked on/off and have the status on the quest log updated too. The floating quest window would be an easy way to update the completion status of an objective.

Discussed 30-06-2021, still needs to be scoped

related to #59

There is a major improvement to the QuestTracker incoming with my final big feature PR that solves #59, but I'll leave the idea of interacting with the task / objectives from the QuestTracker to RCOS.

Released with 0.7.6 which is available now.


Add ability to change popup styling, and create bridge popups

Fixes #296
This adds the ability to change (slightly) the style of markup in popups, including the background color, font name, font size, font color, and link font color. The documentation will be updated for this feature before it is committed.
Two popups have been added to "link" the Mesoamerican study with the (default) Modern North America study, exhibiting some of the popup style features (to use a red background).

In the process I found a bug that's been in the timeline slider since day one, whereby it starts the time at "startdatestr" and then updates to "curdatestr". This has the effect of "using up" any popups at startdate when the user overrides the "curdatestr" to something outside of its range.

The documentation has been updated, merging.


Pentest - Group N

Group N tried to pentest your application but we were not able to access it (both earlier today and now). You are more than welcome to let us know whenever it is available and we will try to provide you with some feedback.

Our droplet ran out of disk space, so we have been down most of the day. It should be up and running now


Release rest level client for mgmt appservice

Packages impacted by this PR
Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/22017
Describe the problem that is addressed by this PR
As it would take a lot of efforts to refactor the mgmt plane libraries to support tree-shaking to make the bundle size smaller. We will try to generate a new rest level client package for this customer to have a try.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

@joheredi @xirzec @bterlson Can you also take a look at this PR ? As this is the first time we release a mgmt plane rest level package. I wonder if you guys have any comments about it ?

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-rest-arm-appservice


SRVLOGIC-282: Move main-sync CI to kie-ci repository

Jira: https://issues.redhat.com/browse/SRVLOGIC-282
Description:
Move main-sync CI to kie-ci repository to make it reusable from other midstream repositories
Required PR:
https://github.com/kiegroup/kie-ci/pull/1552
Example PR:
An example of a Sync PR is here: https://github.com/fantonangeli/incubator-kie-kogito-examples/pull/2

@rgdoliveira this error should not be related to my new GH workflow, should I merge this PR or wait for the green check?

you can merge it


Is it possible to downgrade compileSdkVersion to 30 at flutter module?

Steps to Reproduce
I'm trying to produce my flutter application as aar to the customer, and customer requires to set compileSdkVersion to 30 because of there own application issue.
But, when I tried to downgrade compileSdkVersion to 30, it fails.
First, since flutter android module cannot customize build.gradle because all the .android/ directory will be autogenerated, so I temporally fix flutter sdk itself. At pacages/flutter_tools/templates/module/android/host_app_common/app.tmpl/build.gradle.tmpl, I changed ths gradle template into, like below,

Gradle template fix
def flutterPluginVersion = 'managed'

apply plugin: 'com.android.application'

android {
    compileSdkVersion 30

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    defaultConfig {
        applicationId "{{androidIdentifier}}.host"
        minSdkVersion 16
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"
    }

    buildTypes {
        profile {
            initWith debug
        }
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }

}
buildDir = new File(rootProject.projectDir, "../build/host")
dependencies {
    implementation project(':flutter')
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'androidx.appcompat:appcompat:1.0.2'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
}

So, in that case, autogenerated gradle file also can be set to compileSdkVersion 30.
But, after that, when building sample application which uses our aar with compileSdkVersion 30, the error shows like,
Dependency 'androidx.window:window-java:1.0.0-beta04' requires 'compileSdkVersion' to be set to 31 or higher.
Compilation target for module ':app' is 'android-30'

But in case of this androidx.window:window-java:1.0.0-beta04, i cannot find any references at flutter sdk too.
Questions

Are there any way to properly downgrade compileSdkVersion into 30?
If not, are there any temporal way to fix flutter sdk to downgrade compileSdkVersion at least..?

Flutter 3.0 has dependencies that require 31 (as you have discovered). If you want to remove that dependency you would need to build a custom Flutter engine, removing both that dependency any anything using it.
If you don't want to build a custom engine, you would need to use an earlier version of Flutter.

@stuartmorgan Yes, I also think for custom engine as temporal solution (because eventually, we need to update to SDK 31). Can u give a hint to remove window-java:1.0.0-beta04 dependency from custom engine..?

https://github.com/flutter/flutter/wiki/Compiling-the-engine explains how to build the engine.


Monlog log broke due to broken code..

An issue with log_malformed_data should now be corrected. Username -> username.
Since change of datetime import, datetime.datetime.now() became datetime.now().
Please verify and accept patch

Holy wow. Maybe we shouldn't merge every branch into eachother as much as we do. I mean, this pull request doesn't really have changes from monlog_log only...


Using asyncprops

My jsonx looks something like this...
const config = {
  component: "Card",
  children: [
    {
      component: "CardHeader",
      props: {
        title: "Test Header"
      }
    },
    {
      component: "CardContent",
      children: [
        {
          component: "AttributeTable",
          asyncprops: {
            data: ["attributes"]
          }
        }
      ]
    }
  ]
}

Above I have specified asyncprops on the AttributeTable component.
My traverseObject looks like this...
const data = {
  attributes: [
    {label: "test label 1", value: "test value 1"},
    {label: "test label 2", value: "test value 2"},
    {label: "test label 3", value: "test value 3"}
  ]
}

There is an "attributes" object which matches to the value specified in the asyncprops array.
The code looks like this...
const JSONXP = jsonx._jsonxProps.getJSONXProps({ jsonx: config, traverseObject: data });
When I inspect the result of JSONXP, it's just an empty object.

Hi, @akonieczka  I just realized why you're seeing an empty object.
 jsonx._jsonxProps.getJSONXProps returns the computed props property of the jsonx object passed to the function.
In your config jsonx object, getJSONXProps  returns an empty object because you passed:
{
  component: "Card",
//There is no computed props property
  children:[]
}

It returns an empty object by default: https://github.com/repetere/jsonx/blob/master/src/props.js#L102
export function getJSONXProps(options = {}) {
  let { jsonx = {}, propName = 'asyncprops', traverseObject = {}, } = options;
  return (jsonx[ propName ] && typeof jsonx[ propName ] === 'object')
    ? utilities.traverse(jsonx[ propName ], traverseObject)
    : {};
}

Do you mind letting me know how you're looking to use jsonx?
If you want the rendered React Component then I believe you should be looking at jsonx.getReactElementFromJSONX  (https://github.com/repetere/jsonx/blob/master/src/main.js#L72)
Most people are using JSONX to actually render components, but if you're looking to get all the props, then there are other options to output JSX, JSONX, or plain JSON.
As a quick reference:
jsonx.outputHTML // Takes a JSONX JS object and outputs an HTML string ( Use ReactDOMServer.renderToString to render html from JSONX)
jsonx.outputJSX // Takes a JSONX JS object and outputs an JSX string ( used to typically write files)
jsonx.outputJSON // Takes a JSONX JS Object and outputs Plain JSON in the form of the arguments used for React.createElement. e.g. {type,props,children}
jsonx.getReactElement // Takes JSON JS Object and returns ReactElement using React.createElement

question: from @akonieczka "So it sounds like it only works for the top most parent component but doesn't work when defined on children components. The example shows it being used on a child component. Is that a mistake?"
answer: ah good catch, the example is incorrect.
Can you explain how you're attempting to use JSONX are you using it actually render components, or just to resolve props?
If you just want the props and not the actual react element then using jsonx.outputJSON will recursively give you what you want.
If you want the actual react element then jsonx.getReactElement will give you what you want.
jsonx.getReactElement({ compoennt:'div', children:'hello world', }) //equals
React.createElement('div',null,'hello world') // equals
<div> hello world </div> // equals

Yes I am using getReactElement to render components and that part is working great.
Any chance to get an enhancement done so that you can use asyncprops on children?

@akonieczka check out https://github.com/repetere/jsonx/blob/master/manual/examples/resourceprops_asyncprops.html for a full working example.
It should look like this:

I'm using a component library called Spectre for UI but other than that, it's an example for resource props.
here are some selected highlights:
const exampleComponent = {
  component: 'Spectre.Grid.Grid',
  children: [
    {
      component: 'div',
      children: [
        {
          component: 'Spectre.Typography.H4',
          children: 'Testing Deep Nested resourceprops (asyncprops)'
        },
        {
          component: 'Spectre.Form.FormGroup',
          children: [
            {
              component: 'label',
              props: {
                className: 'form-label',
                htmlFor: 'input-1'
              },
              children: 'Form Input from resourceprops/asyncprops',
            },
            {
              component: 'Spectre.Form.Input',
              props: {
                id: 'input-1'
              },
              resourceprops: {
                defaultValue: [ 'deep', 'nested' ]
              }
            }
          ]
        },
      ],
    },
    {
      component: 'p',
      asyncprops: {
        children: [ 'deep', 'under' ],
      }
    }
  ]
};

jsons.getReactElement({
  jsonx: exampleComponent,
  resources: {
    deep:{
      nested:'some data',
      under:'works with resourceprops or asyncprops(alias)'
    }
});

Thank you it's working now for me. Much appreciated!


div height 100% whit

the problem is when I try to occupy a div height 100% when I have the <! doctype html>.
When I remove the <! Doctype html> and respects me up to 100%.
As you can solve this problem without removing the <! Doctype html>

This question would be better asked on Stack Overflow as it has nothing to do with the framework


Support videoclip with newer version of dependencies

🚀 Feature Request
I hope there could be a code base for videoclip with newer version of dependencies (such as python, pytorch, transformers, diffusers, etc)
Motivation
Recently I am working on a project trying to combine videoclip with diffusion model, but found the denpendencies for videoclip (MMPT) in this repository confilict with modern diffusion models, As the modern diffusion models require newer version of diffusers, transformers and other dependencies.
Pitch
Would you please provide support for videoclip models with newer version of dependencies such as diffusers, transformers, tokenizers, etc?

Hi, I have adapted videoCLIP for a higher version of transformers  for 4.37.2 from these two commits:

https://github.com/MarkChenYutian/fairseq_SpaceQADepend/commit/8f0926631554933cfa899acec4f1184f4b4ac581
https://github.com/MarkChenYutian/fairseq_SpaceQADepend/commit/7cfc3e28f2d5be18047c8142b6270afaffa1203c


Fix a typo in a comment in the ApplicationInsights.config file

This is a very minor change which fixes a typo in a comment in the ApplicationInsights.config file installed in a project when adding/updating the Microsot.ApplicationInsights.Web NuGet package
Changes
Remove individual fields collected here by adding them to the ApplicationInsighs.HeartbeatProvider
to
Remove individual fields collected here by adding them to the ApplicationInsights.HeartbeatProvider

@PatrickMcDonald haha, this has been here for years and no one noticed. Thank you :)

Thanks for the fix!

@PatrickMcDonald haha, this has been here for years and no one noticed. Thank you :)

When you see it, you can't understand it! Thanks for accepting the change. 😀


Select column using an alias for output prisma orm

Problem
Select column using an alias for output prisma orm

Can you please give an example of what you are trying to describe?

How can we define an alias in a select query?
SELECT column_name AS alias_name FROM table_name;

You can alias your result in your code:
  const { column_name: alias_name } = await prisma.test.findMany();

Can you please tell me why you need SQL level aliasing in Prisma?

Closing in favour of https://github.com/prisma/prisma/issues/8151

For my case, we have an a lot of relations on one "item" table.

For example colorFinish, paintType, sheenType these tables all have [id , name , createdAt, updatedAt]columns . In the Item table these are related by an id.
So instead of get the ids I want the name to return in one call just the name of these types instead of the id, let alone the full Object.
In knex I did something like this:
_let filterItems = knex.queryBuilder().from("items")
.select([
"items.*",
"sheenTypes.name AS sheenType",
"paintTypes.name AS paintType",
"materialTypes.name AS materialType",
"carpetTypes.name AS carpetType",
"colorFinishes.name AS colorFinish",
"speciesTypes.name AS speciesType",
"constructionTypes.name AS constructionType",
"vinylFloorTypes.name AS vinylFloorType"
])
.leftOuterJoin('sheenTypes', 'items.sheenTypeId', '=', 'sheenTypes.id')
.leftOuterJoin('paintTypes', 'items.paintTypeId', '=', 'paintTypes.id')
.leftOuterJoin('materialTypes', 'items.materialTypeId', '=', 'materialTypes.id')
.leftOuterJoin('carpetTypes', 'items.carpetTypeId', '=', 'carpetTypes.id')
.leftOuterJoin('colorFinishes', 'items.colorFinishId', '=', 'colorFinishes.id')
.leftOuterJoin('speciesTypes', 'items.speciesTypeId', '=', 'speciesTypes.id')
.leftOuterJoin('constructionTypes', 'items.constructionTypeId', '=', 'constructionTypes.id')
.leftOuterJoin('vinylFloorTypes', 'items.vinylFloorTypeId', '=', 'vinylFloorTypes.id')
.then((res) => {
console.log(res)
return res
}).catch(e => { console._log(e) })
So on the leftOuterJoin I only return the name of the types so when returned I get a more organized call.
Is this possible to do in prisma?

Please turn that into a GitHub discussion, here in a closed issue no one should reply to such a question. Thanks.


fix: upgrade to version 3.0.482

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jenkins-x-labs-bot
You can assign the PR to them by writing /assign @jenkins-x-labs-bot in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
68546b31830506b9e837aa9533961c401a862a01
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


PSR-513 receiving scheme name

https://jira.tools.tax.service.gov.uk/browse/PSR-513

tests are happy


Update opentelemetry-to-lgtm-stack.md

closing curly brace missing in loki write example

PR Description
Which issue(s) this PR fixes

Notes to the Reviewer
PR Checklist

[ x] Documentation added

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


Add Bsky for Silvia

Hi @spcanelon,
I'm working on adding a Bluesky integration for the R-Ladies bot and saw that you're also on Bluesky. Please let me know

if you agree to add your handle here as well so that the bot can use it to tag you when posting about your posts
if you're also OK to be featured in an R-Ladies starter pack

Thank you ☺

Hi @cosimameyer! Thank you for reaching out. Yes, I agree for my Bluesky handle (@ silviacanelon.com) to be added, and I'm ok with being featured in an R-Ladies starter pack. 😊


Adds proof harnesses for aws_byte_cursor_eq_c_str* functions

Description of changes:

Updates implementation of aws_byte_cursor_eq_c_str* functions with pre- and post-conditions;
Adds proof harnesses for aws_byte_cursor_eq_c_str* functions;

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

@tautschnig @karkhaz @angelhof @danielsn @markrtuttle could you review the proof harnesses?

@JonathanHenson @ColdenCullen @justinboswell @bretambrose could you review the changes in byte_buf.h and byte_buf.c?


Does tree shaking works on CommonJS modules?

I have a lot of Node.js(CommonJS) modules that I want a load with rollup-plugin-commonjs plugin.
Does rollup tree shaking is applied to that modules?
I open an issue because can't find the answer anywhere in the docs.
If no - do you have plans to support that?
You also will be glad to see your comment on that question on StackOverflow

Hey folks (this is a canned reply, but we mean it!). Thanks to everyone who participated in this issue. We're getting ready to move this plugin to a new home at https://github.com/rollup/plugins, and we have to do some spring cleaning of the issues to make that happen. We're going to close this one, but it doesn't mean that it's not still valid.
We've got some time yet before the move while we resolve pending Pull Requests, so if this issue is still relevant, please @ me and I'll make sure it gets reopened and transferred to the new repo. :beer:

See https://github.com/eight04/rollup-plugin-cjs-es#comparing-to-rollup-plugin-commonjs


Loading entire lodash library

My script is huge and analysis shows that vue-mc and the validation library both include the entire lodash library. which is around 527 KB.  This is by far the biggest library in my script. Could you please load just the functions that are actually used?

How are you building your script?

Webpack
Op do 15 nov. 2018 05:52 schreef Rudi Theunissen<EMAIL_ADDRESS>
How are you building your script?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-438916940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvL_JPC0bJFP2m_tnLcMFyPzfc_ya9ks5uvPMNgaJpZM4YbRLQ
.

This should now be improved in 0.5.0, please report so we can close if fixed.

line 9 of vue-mc.js still says
var lodash = require('lodash')
The impact on the size is huge:

What tool did you use to generate that image? 😮

webpack-bundle-analyzer

If you use import instead of require, does it use the vue-mc.es.js file? If I use `import method from 'lodash/method', it appears to inline that dependency, which is not what we want either, as you may be including that elsewhere in your library and I'm not sure if webpack can be aware of that.
I'm noticing that the validation component is also quite large, is that vue-mc validation?

Yes, that's vue-mc validation. I find that strange, because I only load a
few validation functions
Op vr 16 nov. 2018 18:52 schreef Rudi Theunissen<EMAIL_ADDRESS>
If you use import instead of require, does it use the vue-mc.es.js file?
If I use `import method from 'lodash/method', it appears to inline that
dependency, which is not what we want either, as you may be including that
elsewhere in your library and I'm not sure if webpack can be aware of that.
I'm noticing that the validation component is also quite large, is that
vue-mc validation?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-439473540,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvL61-BPVVW9NpuPWRXulF9yDN06umks5uvvtZgaJpZM4YbRLQ
.

I always use import
Op vr 16 nov. 2018 19:29 schreef Arjen Haayman<EMAIL_ADDRESS>
Yes, that's vue-mc validation. I find that strange, because I only load a
few validation functions
Op vr 16 nov. 2018 18:52 schreef Rudi Theunissen<EMAIL_ADDRESS>:

If you use import instead of require, does it use the vue-mc.es.js file?
If I use `import method from 'lodash/method', it appears to inline that
dependency, which is not what we want either, as you may be including that
elsewhere in your library and I'm not sure if webpack can be aware of that.
I'm noticing that the validation component is also quite large, is that
vue-mc validation?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-439473540,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvL61-BPVVW9NpuPWRXulF9yDN06umks5uvvtZgaJpZM4YbRLQ
.

As an experiment, can you swap your vue-mc.es.js and vue-mc.js files? I'm curious to see what happens when you try to import from that file instead. I'm setting up a little test to debug this further in the meantime.

It'll take a few days before I'll have that opportunity
Op vr 16 nov. 2018 20:05 schreef Rudi Theunissen<EMAIL_ADDRESS>
As an experiment, can you swap your vue-mc.es.js and vue-mc.js files? I'm
curious to see what happens when you try to import from that file instead.
I'm setting up a little test to debug this further in the meantime.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-439494463,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvLzb3RNUz8JVmlUAjJTGKliDkOr-mks5uvwx7gaJpZM4YbRLQ
.

Happens for me as well:

Same issue as @haayman. at line 6 there is that big require statement for lodash.

Couple of things that may be useful here -

The webpack build analyzer is already available to you if you're using the Vue CLI - you can run ./node_modules/.bin/vue-cli-service build --report (among other ways) to generate a report.html which you can then open in the browser.

In order for vue-mc.es to import lodash and actually make use of the tree-shaking to only get what it needs, apparently it must import lodash-es. I guess vanilla lodash does not support tree-shaking.

It appears that vue is not a peer dependency of vue-mc as the repo stands right now. I have never dealt with publishing to npm so I don't quite understand what's going on, but vue-mc has vue inside its own node_modules folder and is pulling it in from there.

What my build looks like in current state - note the doubling-up on vue.runtime.esm:

This is 330.30 KiB parsed size.
What happens if I delete vue from vue-mc's internal node_modules folder:

269.54 KiB parsed size.
Now if I switch the imports in my own code from vue-mc to vue-mc/vue-mc.es nothing changes; but after doing that, if I go into vue-mc.es and change the import from lodash to lodash-es I get this:

221.67 KiB parsed size. Note the difference in my own lodash-es imports from the previous image; webpack is now sharing those with the ones from vue-mc.
So it seems there are two things to do here -

Make vue actually a peer dependency. Fix whatever is happening with npm.
Change the lodash import to lodash-es in vue-mc.es - I'm not sure what the ramifications of doing this are. It will probably break a bunch of peoples' builds, so I doubt this is something you can just decide to do on a whim.

Isn't it a lot better to just import the lodash function that is actually
used instead of the entire library? Lodash supports this. Shouldn't be too
hard to determine.
On Sat, Mar 2, 2019 at 2:15 AM Daniel Smedema<EMAIL_ADDRESS>wrote:

Couple of things that may be useful here -

The webpack build analyzer is already available to you if you're using
the Vue CLI - you can run ./node_modules/.bin/vue-cli-service build
--report (among other ways
https://cli.vuejs.org/guide/cli-service.html) to generate a
report.html which you can then open in the browser.
2.
In order for vue-mc.es to import lodash and actually make use of the
tree-shaking to only get what it needs, apparently it must import
lodash-es. I guess vanilla lodash does not support tree-shaking.
3.
It appears that vue is not a peer dependency of vue-mc as the repo
stands right now. I have never dealt with publishing to npm so I don't
quite understand what's going on, but vue-mc has vue inside its own
node_modules folder and is pulling it in from there.
What my build looks like in current state - note the doubling-up on
vue.runtime.esm:
[image: current_state]
https://user-images.githubusercontent.com/7870631/53674569-d46bc080-3c5c-11e9-9539-56e3daac6e6a.png
This is 330.30 KiB parsed size.
What happens if I delete vue from vue-mc's internal node_modules folder:
[image: no_double_vue]
https://user-images.githubusercontent.com/7870631/53674657-6ecc0400-3c5d-11e9-92df-a2b4f2e2580c.png
269.54 KiB parsed size.
Now if I switch the imports in my own code from vue-mc to vue-mc/vue-mc.es
nothing changes; but after doing that, if I go into vue-mc.es and change
the import from lodash to lodash-es I get this:
[image: final]
https://user-images.githubusercontent.com/7870631/53674744-177a6380-3c5e-11e9-9023-42ef2a0395b3.png
221.67 KiB parsed size. Note the difference in my own lodash-es imports
from the previous image; webpack is now sharing those with the ones from
vue-mc.
So it seems there are two things to do here -

Make vue actually a peer dependency. Fix whatever is happening with
npm.
Change the lodash import to lodash-es in vue-mc.es - I'm not sure
what the ramifications of doing this are. It will probably break a bunch of
peoples' builds, so I doubt this is something you can just decide to do on
a whim.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-468865217,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvL7UbmhcmlgM_sJvCc6azC2a546tBks5vSdDHgaJpZM4YbRLQ
.

Ah, I think you’re right. I got caught up in the tree-shaking and somehow the “you might break everyone’s projects” bit didn’t cause me to take a step back and reconsider.
You’re saying to do imports like import cloneDeep from “lodash/cloneDeep” rather than import { cloneDeep } from “lodash” right?
Do you have any insight on the other thing, where I’m seeing vue.runtime.esm twice? It looks like that’s not happening for you, maybe I’m just doing something wrong here?

I'm afraid that doesn't happen here
Op di 5 mrt. 2019 05:58 schreef Daniel Smedema<EMAIL_ADDRESS>
Ah, I think you’re right. I got caught up in the tree-shaking and somehow
the “you might break everyone’s projects” bit didn’t cause me to take a
step back and reconsider.
You’re saying to do imports like import cloneDeep from “lodash/cloneDeep”
rather than import { cloneDeep } from “lodash” right?
Do you have any insight on the other thing, where I’m seeing
vue.runtime.esm twice? It looks like that’s not happening for you, maybe
I’m just doing something wrong here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-469537838,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvLzHCcqzLDxvZCW2BEJqe7sNXAVNTks5vTflagaJpZM4YbRLQ
.

You’re saying to do imports like import cloneDeep from “lodash/cloneDeep” rather than import { cloneDeep } from “lodash” right?

Yes, this is what I mean. This will have no negative side-effects

i'm seeing the same as you @djsmedes with double up on vue.js, meaning huge size compared to what it should be :S

I have an idea for a fix there actually, perhaps in vue-mc's package.json, switching vue from a dependency to a peerDependency + devDependency (and for that matter, lodash and axios as well). I will test that out when I get a chance and see if it resolves the issue.
Out of curiosity, @AndreasHerss and @haayman - are you using yarn or npm for the project that is making use of vue-mc? I'm wondering if there's some odd interaction since vue-mc uses yarn but I am using vanilla npm.

@djsmedes i'm using yarn :)

I'm quite puzzled why you wouldn't implement my suggestion to just load the
functions that are actually used? It will take you at most an hour to
implement?
I'm using npm. But that's just for installing, not for building?
On Wed, Mar 27, 2019 at 3:19 PM Daniel Smedema<EMAIL_ADDRESS>wrote:

I have an idea for a fix there actually, perhaps in vue-mc's package.json,
switching vue from a dependency to a peerDependency + devDependency (and
for that matter, lodash and axios as well). I will test that out when I get
a chance and see if it resolves the issue.
Out of curiosity, @AndreasHerss https://github.com/AndreasHerss and
@haayman https://github.com/haayman - are you using yarn or npm for the
project that is making use of vue-mc? I'm wondering if there's some odd
interaction since vue-mc uses yarn but I am using vanilla npm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FiguredLimited/vue-mc/issues/89#issuecomment-477176725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApvL9WdaPlPe_RmPIchgBuqP5ldsOgRks5va33bgaJpZM4YbRLQ
.

@haayman - sorry, I should probably open up another issue for the other issue I'm seeing (that it seems not everyone is). For the lodash import issue, I have already submitted a PR doing exactly as you suggested.
@rtheunissen - when you get a chance could you take a quick look at #104? Thanks!

This has been fixed and released as part of v0.6.0.


Finish writing application review end-to-end browser test

We are migrating our end-to-end browser tests from using Java with Selenium to using TypeScript with Playwright. Please see our wiki section on browser testing before proceeding.
This test should do the following (not that steps 1 and 2 are already complete in application_review.test.ts, this issue is to extend that test):

login as admin
create a question
create a program
add the question to the program
log in as applicant
complete the program created in step 3
login as admin
view applications for the program created in step 3
view the application submitted in step 6
assert that the answer to the question is the same as submitted in step 6

I think I can take this as I am going to add a browser test for my recent PR.


invalid use false and use true on rule-detail page

false and true should not be imported.
-use false;
-use true;

Handled at https://github.com/rectorphp/getrector-com/pull/2431/commits/3ec42379c4b336a6a3101f0ba661fdb128e612eb


DOC: improved animation of heat equation

While working on operator-splitting techniques for the unsteady Navier–Stokes equation #240, I found it would be helpful to have a better idiom for animating transient solutions.  This documents them for the simpler example of the heat equation, ex19.
I've also taken the opportunity to make a number of other improvements to the example:

Optionally save an animated GIF and include this in the docs.
This optional behaviour is governed by a command-line flag via argparse from the Python Standard Library.

The default behaviour is as before to display the solution as it's being simulated.
No duplication of code between the two modes is needed.
This parameterization of an example might also be useful in other cases:

type and order of meshes & elements #241 #244 #248
fineness of mesh or time-step or tolerance, or degree of nonlinearity, or time to run an unsteady simulation, e.g. to make a test quicker but an example run live at the terminal richer
just about any other aspect of a finite element problem

Animation is sped up using matplotlib.animation.FuncAnimation. (I haven't actually measured this.)
MeshQuad in place of MeshTri: more natural for the geometry and also gives another ElementQuad1 example #248.
The mesh is generated with MeshQuad.init_tensor instead of using the product of two MeshLines.
The solution is generated in the script rather than only when __name__ == '__main__', or at least a generator evolve is written.  This makes ex19 more like the other examples that can have the solutions imported into tests.test_examples. This example still can't be tested as it relies on sksparse, but it does demonstrate an idiom for making future unsteady examples testable.

Looking good https://kinnala.github.io/scikit-fem-docs/examples/ex19.html


update build status badge for github actions

I followed https://docs.github.com/en/actions/managing-workflow-runs/adding-a-workflow-status-badge

Than you!


Make equal-width flexbox extend grid-column

Fixed equal-width flexbox columns, so now they will act like normal columns as they break.

A col-fill would be a great feature too, but I'm looking for more real world examples before adding it.
.col-fill {
  flex: 1 1 auto;
}

What does this fix exactly? I don't see the benefit of this without a JS Bin or demo showing the before and after.

These equal-width flexbox classes aren't breaking as normal columns do. When they were supposed to break, they just don't break, making the breakpoints useless on them. It happens because they were not extending %grid-column.
Here's an example: https://jsbin.com/baqoriqagu/edit?html,css,output
Just change the $equal-width-flex-extend-grid-column to see the difference.

Gotcha. Okay, I took a look and cleaned some things up in #20829. Thanks!


dce removes variables it shouldn't in JSX

Describe the bug
dce removes variables it shouldn't when they're used as part of a JSX element.
This is when dce is used programmatically in Rust, not as part of a full SWC transform.
PR with failing test: #4203
Input code
function A() { return 'a'; }
const b = 'b';
const c = 'c';
export function d() {
    return {c};
}

Config
n/a
Playground link
No response
Expected behavior
A, b and c are all used within the exported function and should not be considered dead code. Output should be same as input.
Actual behavior
After dce:
const b = 'b';
const c = 'c';
export function d() {
    return {c};
}

b and c have been retained correctly, but A has been erroneously shaken out.
Version
1.2.161
Additional context
Generally, this doesn't become apparent as usually dead code removal occurs after JSX->JS transform. However, if you use dce in a custom pass, the problem can occur.
I noticed this behavior first in next-swc's shake-exports pass (https://github.com/vercel/next.js/issues/35734), which does exactly this.

I'd be happy to attempt a fix, if you could give me any pointers. I'm confused why the JSXOpeningElement identifier isn't being visited in the Analyzer, as the other children of the JSXElement are.


fix: handle transfer-encoding and content-lenght headers clash

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

v1.20.1
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Drop google analytics?

For privacy reasons?
Maybe we can use http://keen.io/ instead ?

don't really care about that, do whatever you guys want

We need a cookies Popin, because of analytics ..
I don't know keen.io, so hard to make my decision.

It's just that google is evil, and keen (that as been recommended to me on twitter a few weeks ago) seems a nice alternative.
For the poop(in), I think I heard that the law is going to change again, but I might be saying pure shit.
Another solution is to completely remove any sort of analytics, but that's kind of brutal...

It's just that google is evil, and keen (that as been recommended to me on twitter a few weeks ago) seems a nice alternative.

Ok ok. So why not.  We can make some test

Another solution is to completely remove any sort of analytics, but that's kind of brutal...

yeah, it's cool to have some information about visitors. So no ?

Anyone opposed to this? Any thoughts?

Btw, I just saw that analytics are broken since we merged statinamic... Weird cause I don't have this issue on other projects using it. Will double check.

FYI, analytics should work now, the UA wasn't set :D

Any thoughts on http://piwik.org/?

Require a server. And their hosted offer is expensive.


Support static position of button?

Hello. Thanks for this great repo. It helps me so much.
One day, I have a project which design like this:

So, is there any plan to support static position of button? Thanks! :beers:

What happens when you tap on the button in your project? If it just calls a function, then I would suggest to build this FAB yourself. Its just an Icon wrapped inside a Touchable. No need for an extra dependency in your project 😊
On Sun, Dec 11, 2016 at 12:51 PM +0100, "Pewh Gosh"<EMAIL_ADDRESS>wrote:
Hello. Thanks for this great repo. It helps me so much.
One day, I have a project which design like this:
So, is there any plan to support static position of button? Thanks! 🍻
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


The core configuration of this Telescope extension is setup incorrectly

@lyz-code fyi the actual core structure and architecture of this telescope extension is setup in correctly in several ways. Maybe a couple years ago things were done differently but it definitely does not adhere to the specs of today for creating telescope extensions.
This issue will represent re-structuring the extension to today's standards / requirements for the telescope extensions API.
I will try to do a PR this weekend when I have some time.

That would be lovely, thank you so much <3

@GitMurf Any news on this?

@GitMurf Any news on this?

No I am sorry but orgmode ended up not being something that stuck for me. I am back to taking all my notes in Obsidian and Notion.
If I ever come back to using orgmode I will take a deeper look.

@GitMurf I was just wondering what you meant with your statement:

the actual core structure and architecture of this telescope extension is setup in correctly in several ways.

I never wrote an Telescope extension myself, but I have several ideas and actually requirements regarding Orgmode and to get started, I worked through Telescopes development.md.
If I compare this to the plugin code, I actually don't see pressing issues. One might complain, that the meat of the code is actually living directly in the telescope/_extensions folder. But besides that, I can't see, how the Telescope API is used fundamentally wrong. But as I said, I don't have real experience in developing Telescope plugins.
Would you mind to point me to the biggest issues you see in the architecture and in the code of this plugin? And do you have a good example to learn from? The Telescope tutorial is too small and the telescope-fzf-native plugin they're referring to is actually too big.
I would actually love to do some refactoring on my own, but would appreciate your help in getting the structure right to the current standards.

@lyz-code I created a PR #15, what do you think? @GitMurf Would you mind to take a look, if the structure is now more according to what you imagined?

Because we had a major refactoring, which should fix most of the architectural problems, I will close this issue.

@seflue i did a quick review of your work and it looks great! This is what i envisioned. Nice work!


PlayerView not appropriately sizing content to size of container

In the last few months, I have started an effort migrating our player to use the media3 version of ExoPlayer instead of the legacy version.  Almost everything is complete.  However, I am noticing with the new player, the contents of the PlayerView does not seem to appropriately constrain itself to the size of it's parent container.
When a user is viewing content with an adaptive resolution, we give them the option to allow the content to adapt as normal (the default value) based on the network bandwidth.  The user can also select a specific resolution if they want it to be fixed.  If the user starts at the lowest resolution and changes the resolution to be higher and higher, the container is filled as expected  eg. 360p -> 720p -> 1080p.
However, if the user starts at the higher end of the resolution range and goes down, you can see these ghosted looking images of the previous resolutions and the size of the content gets smaller and smaller.  See the image below.  eg. 1080p -> 720p -> 360p.

Does anyone know why this could be happening and what the potential fix is?  I've provided a resize_mode="fit" param to the PlayerView in the XML and that didn't seem to work.  I have also tried setVideoScalingMode(VIDEO_SCALING_MODE_SCALE_TO_FIT) when building my ExoPlayer instance and that also did not make a difference.
The container is fixed to a 16:9 aspect ratio.  I cannot reproduce this with the old version of the player.
Any help would be appreciated.

Hi @vfutia,
Thanks for reporting the issue!

I cannot reproduce this with the old version of the player.

Could you please let us know what is the version of ExoPlayer library you previously used, and the version of media3 library you're currently using?

@tianyif We are currently using version 1.3.1 of the media3 library.  Previously, we were using Exoplayer 2.18.2.

@tianyif @oceanjules you can close this.  I had an epiphany this morning.  If I constrain the resolution of the video by updating the track selection parameters, the video appears to be scaled appropriately.
private fun updateQuality(quality: VideoQuality?) {
        //If the quality is null, we're in auto so reset the parameters back to default,
        //otherwise, constrain the height and width to the desired resolution
        quality?.let {
            val size = quality.toSize()
            player.trackSelectionParameters = TrackSelectionParameters.Builder(applicationContext())
                .setMaxVideoSize(size.width, size.height)
                .setMinVideoSize(size.width, size.height)
                .build()
        } ?: run {
            player.trackSelectionParameters = TrackSelectionParameters.getDefaults(
                applicationContext()
            )
        }
    }

Appreciate you taking the time to get back to me.

One other piece of information, it seems like this is only happening with HLS.  I cannot reproduce it with DASH.

Another thing...
When I change tracks from 1080p to 360p, I see that the track selection parameters are set to 640 for width and 360 for height, as I would expect.  But when the onVideoSizeChanged() callback gets triggered, the video width and height are 1920 and 1080, respectively.

@oceanjules any news here?

I didn't managed to reproduce this issue on my side with Media3 1.4.0-alpha02.
@vfutia can you check on your side too?

I still get this issue on from the new release 1.4.0, any workarounds?

@vfutia, as @MGaetan89 mentioned, could you please check the behaviour on the most recent release version?
If it does indeed persist, could you confirm that you used to use StyledPlayerView? What was the behaviour of the 1080->720->360 scaling down before? was the outer container scaling back with the background being black?

exo2
media3

PlayerControlView
LegacyPlayerControlView

StyledPlayerControlView
PlayerControlView

StyledPlayerView
PlayerView

In your current situation, do the ghost images remain as the last frame before the scale down? Or are those actually old surfaceViews that still have access to the Player? How do you ensure that the old container is actually destroyed/set to invisible? Rather than just a new one being redrawn on top?


[Bug]: Cosine Similarity: Unusual Negative Distance in Same Sentence Search

What happened?
I am getting a negative distance when searching for the same sentence (-4.76837158203125e-07)
Taking into account that it is cosine similarity, I understand that this should be a value between -1 and 0.
In this case it should be a value equal to 0 as it is the same phrase.
Is there anything I should keep in mind? Is this a mistake?
__import__('pysqlite3')
import sys
sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')
import chromadb
client = chromadb.EphemeralClient()
collection = client.create_collection(
            name="doc_analyzer", metadata={"hnsw:space": "cosine"}
        )
sentences = ["This is a test sentence"]
ids = ["test_id"]
collection.add(
            documents=sentences,
            ids=ids,
        )
#insertion works fine
question = "This is a test sentence"
response = collection.query(
            query_texts = [question],
            n_results=10,
)
for doc, sim in zip(response["documents"][0], response["distances"][0]):
            print(sim, doc)
#Here it returns the l2 distance not the cosine distance

Versions
0.4.22
ubuntu 22
python3.10
Relevant log output
{'ids': [['test_id']], 'distances': [[-4.76837158203125e-07]], 'metadatas': [[None]], 'embeddings': None, 'documents': [['This is a test sentence']]}

Hey @davidmartinrius your value is correct.
-4.76837158203125e-07 is basically 0.0 when you convert the scientific notation to decimal format.
The "cosine" distance function is actually "cosine distance" and not "cosine similarity". This is what Chroma uses when you pass metadata={"hnsw:space": "cosine"}
Cosine distance is simply 1-cosine similarity. So with similarity 1.0 would be exact match but with distance 0.0 would be exact match.
Your result is correct.

Thank you! Got it!


Remove lua and use fastcgi to render errors

This change removes lua as dependency of the ingress controller and also allows adding arm64 platform

This change is

Coverage decreased (-0.2%) to 43.782% when pulling cb16bf9249e7a442f3a4c76540597dd6b0217a57 on aledbf:rem-lua into faf80ad89a1e49113cc9791f0137e2f5a542487a on kubernetes:master.

Coverage decreased (-0.2%) to 43.743% when pulling db93664406d4f893309bc3a299a270a4e9191f26 on aledbf:rem-lua into faf80ad89a1e49113cc9791f0137e2f5a542487a on kubernetes:master.

Coverage decreased (-0.2%) to 43.739% when pulling db93664406d4f893309bc3a299a270a4e9191f26 on aledbf:rem-lua into faf80ad89a1e49113cc9791f0137e2f5a542487a on kubernetes:master.

Coverage decreased (-0.2%) to 43.752% when pulling 69e766e042ed8fe7702a40efa7bb36e8ce8e30e3 on aledbf:rem-lua into 0fad23af258c7c824b7bc8326a6fbf88c61d1d64 on kubernetes:master.


fix(amplify-provider-awscloudformation): fixed deletion for large bucket

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #3656 into master will decrease coverage by 1.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3656      +/-   ##
==========================================
- Coverage   59.72%   58.67%   -1.05%
==========================================
  Files         285      287       +2
  Lines       13206    13441     +235
  Branches     2507     2542      +35
==========================================
  Hits         7887     7887
- Misses       4912     5147     +235
  Partials      407      407

Impacted Files
Coverage Δ

packages/amplify-util-mock/src/utils/git-ignore.ts

...kages/amplify-util-mock/src/__e2e__/utils/index.ts

...plify-util-mock/src/__e2e__/utils/lambda-helper.ts

packages/amplify-util-mock/src/mockAll.ts
0% <0%> (ø)

...ages/amplify-util-mock/src/amplify-plugin-index.ts
0% <0%> (ø)

packages/amplify-util-mock/src/api/api.ts
0% <0%> (ø)

...ges/amplify-util-mock/src/utils/config-override.ts
0% <0%> (ø)

...es/amplify-util-mock/src/api/resolver-overrides.ts
0% <0%> (ø)

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 4694834...d4a1098. Read the comment docs.


Empty msgid with msgctxt throws error

Hi there,
Parser is not working as it should according to POedit (https://github.com/vslavik/poedit/issues/97).
This po file should be valid (can be opened and edit in POedit):
msgid ""
msgstr ""
"Content-Transfer-Encoding: 8bit\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Language: en_US\n"
"Project-Id-Version: \n"
"POT-Creation-Date: \n"
"PO-Revision-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"X-Generator: Poedit 3.0\n"
msgctxt "EmailTemplateLanguage_SurveyURL_1"
msgid ""
msgstr "SurveyUrl Update Test"
msgctxt "EmailTemplateLanguage_Subject_1"
msgid "TEST"
msgstr "Subject Update Test"
msgctxt "EmailTemplateLanguage_Content_1"
msgid "TEST"
msgstr "Content Update Test"
Still parser throws:
Entry beginning at {0} must not have an empty id.
Can you help me with this?
Thank you very much!

https://github.com/adams85/po/pull/15
Fixed with PR 15

Hi!
First of all, thank you for pointing this edge case out. POEdit accepts this input indeed, however, I noticed some weird behavior: if you treat this as a PO template and create a new translation file from it (File / New from POT/PO file...), you get this result:

As you can see, the entry with the empty id and non-empty context is there but somehow it gets mixed up with the header entry, whose contents are displayed in the Translation column. It seems that POEdit itself has some issues getting this edge case right, thus, I don't think it's a good idea to pursue this unusual use case...
Apart from this, of course, we can (and probably should fix) this in the lib but I'm afraid it's not that simple as your PR suggests it.

The issue is fixed by commit https://github.com/adams85/po/commit/bc33caef8c37e204dfdb98f9c6fb8de19b52281e and the fix will be released soon in v1.8.0.
From now on only the msgid "", missing msgid_plural and missing msgctxt combination (which corresponds to new POKey(string.Empty, null, null)) is treated as a special key (reserved for header entry), every other combination with an empty id is accepted after the header entry.

FYI, v1.8.0 has been released.


feat: make stream not found error a variable

Currently having to compare on string value which is not the best developer experience in my opinion.

whoops, didn't see there was an errors package, would this error also be better in that? https://github.com/EventStore/EventStore-Client-Go/blob/master/errors/errors.go

changed it for consistency

@YoEight if you have time can you review the changes I made since your review.

@bweston92 my bad, I thought I already approved it.

@YoEight you did, I changed it since you had. Thanks for the merge.


made_navBar_alignment_in_mobile_viewport

Related Issue

Closes: #299 ]
Description of Changes

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

Please provide any necessary screenshots to illustrate the changes made.

Could you please let me know status, @sourabhsikarwar


Heating Times

HI @antibill51
Many thanks for your great work to see the RIKA Domo in HA.
You told me that you do not use heating times  from the stove as you bypassed it by an external Sensor.
My Stove is in the cloud and I also have an external Temperaturesensor where I can manage the heating times
But how is your setting in the internal heating times from the stove? You are not running the "Automatic" Mode of the Stove?
How do you manage that?
Wud you be so kind and share your "add on"
Many thanks
Helmut

Hi,
The stove is set to manual mode. The heating power is calculated by PID on HA, and sent to the stove. Then, your imagination does the rest (temperature setpoint according to my geolocation, the outside temperature, etc.)
But if you're just starting out with HA, learn with simpler things, otherwise you'll get discouraged.
Examples are in HA config folder. (lovelace / automations / ...)

Ok many thanks for your answer.
I feel good with HA its really good (I came from FHEM)


fix(aik-route-config): Fixes hoisting for routes not using the global Astro variable

When an Astro component doesn't use the Astro variable anywhere the $$createAstro call is not emmited in the compiled source (https://github.com/withastro/compiler/commit/e8b6cdfc89f940a411304787632efd8140535feb). In that case use the $$createComponent call as hoisting anchor instead.

Woot!


Data replication in case of gameserver container crashed

Hi,
I have a scenario where multiple player joined a room (GameServer) and during playing game server get crashed. Is there any way to migrate their old game state of all user to new container(GameServer).

Unfortunately, there is no in built memory replication facilities in Agones, or Kubernetes as a whole.
There is an ongoing issue re: Pod migration, but it's a pretty complicated issue with a variety of edge cases.

Going to close this, since I think this answers the question. Please re-open if you have follow up :+1:


Running Get-RscMssqlAvailabilityGroup for a specific, known good ID returns no results and no error

Running Get-RscMssqlAvailabilityGroup for a specific, known good ID returns no results and no error.

I get the same results (no results!) here.
It works with Get-RscMssqlAvailabilityGroup -AvailabilityGroupName
I have installed version 1.0.

I have a fix submitted to address this.

It works fine in 1.1 👍🏼
Thanks!

Installed 1.1 this morning.
This works Get-RscMssqlAvailabilityGroup -AvailabilityGroupName
This dosen't Get-RscMssqlAvailabilityGroup -Id

Confirmed this is resolved in 1.3 as it works in 7.4.2


Plural Function not found for locale: ru

Getting an error message "Plural Function not found for locale: ru"
I have looked into the repo of messageformat.js but can't find any plural functions for various locales there. Do I have to create one myself? Is there an example I can base it on?
Thanks!

@akatasonov  Does this question related to angular-translate, or are you faced with this issue with MessageFormat.js only? :)

I'm trying to make angular-translate work, so yes - this question is related to angular-translate :)

Well, we only support a bridge into MessageFormat.js which you have to configure on your own.
See more details here.

That's what this question is about. From the doc Note: Please make sure to embed a corresponding locale file provided by MessageFormat. These files provide locale rules for a specific locale this is required to get proper pluralization!
Please look into the repo of MessageFormat. There are no locale files provided, as far as I can see.
Does the documentation need to be updated? Am I supposed to write that local file myself?
Thank you.

Hm, looks like they have changed something vor 0.3. In 0.2 there was a subfolder locale/.

@knalli yup, looks like that... they're changing the module more often than I change some other things in life... d'oh
Please use the latest stable I would suggest... instead of the 0.3 non-stable...  https://github.com/SlexAxton/messageformat.js/tree/0.2.2/locale

@tspaeth Thanks! I will give it a try


Side Key functionality

Bit of a question/idea.
I use side key 1 for Monitor and side key 2 for Scan on/off. Unfortunately Quansheng forgot the off bit! Press SK2, sure enough it scans, press it again it does zilch. Wonder if thats fixable?
While on the subject of scanning and I'm guessing this is far more of a reach. But unless the scan stops on a carrier, the mem channel always reverts to the initial starting point when manually stopped with Exit. This is quite unusual even for Chinese HTs - any ideas?
By the way no need to apologise for bugs, pretty sure we are all thankful for your efforts and afterall we are your beta testers haha

I had that problem too. Try it now, I've made a side key and scanner change, hopefully not broke either.

While on the subject of scanning and I'm guessing this is far more of a reach. But unless the scan stops on a carrier, the mem channel always reverts to the initial starting point when manually stopped with Exit. This is quite unusual even for Chinese HTs - any ideas?

I like that actually, but it depends when you press the exit key I think. If you press the exit key while it's stopped on a RX'ed signal it will remain on that channel/freq, but if you press the exit key while it's scanning it reverts back to the original channel/freq.

By the way no need to apologise for bugs, pretty sure we are all thankful for your efforts and afterall we are your beta testers haha

I had that problem too. Try it now, I've made a side key and scanner change, hopefully not broke either.

Wow you are super quick at fixes, lunch finished and a proper off button to return to, thank you very much.  So far so good not noticed anything awry you'll be pleased to know ;-)


added Commit messages check and Base branch name check

Added the pull request format checks from this issue. Added a test for the base branch name check. Commit message check test Coming soon

We will need tests for this in a followup PR. You will have an example how to do this soon :).


SMS and MMS

Any solutions would be great. https://www.twilio.com/ looks promising but I am not picky.

Here is a minimal but functional Twilio extension. It requires a Twilio account, of course, and depends on the dispatch:twilio meteor package, which does the heavy lifting. Note that if you are using the free, trial account on Twilio, you have to whitelist any phone # you send messages to in the Twilio dashboard. Also, if you treat this as a local package, be sure to add it to your .meteor/packages file.
file: package.js
Package.describe({
  summary: "Add Twilio medium to Herald",
  version: "0.1.0",
  name: "herald-twilio"
});

Package.onUse(function(api) {
  api.versionsFrom('METEOR@0.9.2');
  api.use('underscore');
  api.use('kestanous:herald@1.2.0');
<EMAIL_ADDRESS>'server');
  api.addFiles('lib/herald-twilio.js');
});

file: lib/herald-twilio.js
Herald.addRunner({
  name: 'twilio',
  where: ['server'],
  check: function() {
    if (Meteor.settings.TWILIO === undefined ||
        Meteor.settings.TWILIO.FROM === null || Meteor.settings.TWILIO.FROM === undefined ||
        Meteor.settings.TWILIO.SID === null || Meteor.settings.TWILIO.SID === undefined ||
        Meteor.settings.TWILIO.TOKEN === null || Meteor.settings.TWILIO.TOKEN === undefined) {
      throw new Error("Twilio 'FROM', 'SID' and 'TOKEN' must be defined in Meteor.settings");
    }
  },
  run: function(notification, user) {
    console.log('SMS RUN:', notification);
    var cfg = {
      from: Meteor.settings.TWILIO.FROM,
      sid: Meteor.settings.TWILIO.SID,
      token: Meteor.settings.TWILIO.TOKEN
    };
    var client = new Twilio(cfg);
    var params = {
      to: '+1' + user.phone,
      body: notification.message()
    };
    client.sendSMS(params, function(err, res) {
      if (err) {
        console.log('SMS ERR:', err);
        throw new Meteor.Error(err.status, err.message);
      }
    });
  }
});

In your app:
file: myNotification.coffee
Herald.addCourier 'myNotification',
  media:
    onsite: {}
    twilio: {}  # This is the only line you need to get the Twilio medium
    email:     # You do not need an email medium for Twilio to work but I am including my email setup here anyway
      emailRunner: (user) ->
        html = @message()
        Email.send
          from<EMAIL_ADDRESS>          replyTo<EMAIL_ADDRESS>          to: user.emails[0].address
          subject: 'Test Notification Email'
          html: html
          text: html.replace /<(?:.|\n)*?>/gm, ''

  message: ->
    "This is a notification with data<EMAIL_ADDRESS>

Very nice! Do you want to set this up as its own published package? I know it is not a lot of code but it does make things easier for people to set up. It also gives a place for specific issues.
Finally I am looking to hand herald off to someone else. I will say on board to help out but I don't have time for proper support. Interested? I don't use Herald anymore, that app fell though, so supporting it is very hard to justify. I may use it in the future and Telescope use it so I don't want to see it die.


Placeholder text in topic/subtopic edit view

To give users a sense of what to write there.

@colleencotter @phae reasonable?


Fix typos and translate docs to english

Fixed typos of README for proper naming.
Translated some parts of the documentation to english so documentation can work perfectly for all users

Hi @CholexMax ...
Great job.
Thanks

Hi CholexMax !!
Great job !!

@CholexMax feel free to keep this translation if necessary

Thanks now I currently focus on to improve examples or new updates and concepts


vCheck unable to detect when datastore alarm is disabled

Hi Friends,
We are using the great vCheck script in our environment and noticed that from the report it shows only host with alarms disabled and unable to display the datastore with alarms disabled.
Could you kindly advise if there are any plugins to pull datastore with alarms disabled.
Please advise.
Thanks,

Hi Sneddo,
Im awaiting for your reply. It will be very helpful any information.
Can vCheck pull datastore with alarms disabled ?
Please advise,
Thanks,
AK

AK,
I don't think we are currently pulling this but we have marked this issue as an enhancement and will include it in a future version. Please stay tuned to new releases; we will close this issue once it's implemented. Thanks!

It's a simple enough plugin, effectively the same as the host alarms but using $Datastores instead.
I'll try to get to it tomorrow unless someone beats me to it.

Hi Sneddo,
Thanks, Let us know once the host alarm plugin is modified to check for datastore alarms.
It will be really helpful.
Thanks,
AK

Hey sorry, been a busy week. Give this a try, should do what you want:
# Start of Settings
# End of Settings

$Datastores | where {!$_.ExtensionData.AlarmActionsEnabled} | Select Name, @{n='AlarmActionsEnabled'; e={$_.ExtensionData.AlarmActionsEnabled}}

$Title = "Datastores with Alarms Disabled"
$Header = "Datastores with Alarms Disabled"
$Comments = "Datastores with Alarms Disabled"
$Display = "Table"
$Author = "John Sneddon"
$PluginVersion = 1.0
$PluginCategory = "vSphere"