Error while building the project inside a Docker dev container

Describe your question
I am trying to build the project inside a Docker container with Ubuntu 20.04, .NET 5.0.300, Mono 6 and nuget CLI installed.
I get the following error when executing this command per the contribution guide msbuild Python\dirs.proj:
"/workspaces/PTVS/Python/dirs.proj" (default target) (1) ->
(_EnsureDependenciesInstalled target) ->
  /workspaces/PTVS/Build/Common.Build.settings(98,5): error MSB3073: The command "mono powershell.exe -ExecutionPolicy Bypass -File "/workspaces/PTVS/Build/PreBuild.ps1" -VsTarget 16.0" exited with code 2. [/workspaces/PTVS/Python/dirs.proj]

Is there something I could and I am not or is the project not compatible with development under Ubuntu ?

Sorry but you have to build on windows. Visual Studio only runs on windows. This extension to VS also only runs on windows.


Installing the kibana x-pack plugin can take a long time

Since installing the kibana x-pack plugin can take a long time and is resource intensive a warning in the documentation would be in order. For example by suggesting to set a higher timeout.

Does this belong in the puppet-kibana repo?

yes it does.


RenderlessPagination missing in 2.0.3

I'm trying to use the custom template option but RenderlessPagination is not included in the package installed from npm. I tried using 2.0.1 but it's not working with<EMAIL_ADDRESS>

I've upgraded the package to allow for a custom template. Please see README file. vue-tables-2 is using the latest version now,


Error thrown when the blur event happens during the time of opening the dropdown menu

if the data set is relatively large (my case is 1000 ~ 2000), the dropdown menu takes time to be shown, during the time, if click other elements (i.e. trigger the blur event), there is an error thrown from line 523 in uiSelectController.js due to empty set of choices, but I think the error should be silenced in case of "unfinished requests "
throw uiSelectMinErr('choices', "Expected multiple .ui-select-choices-row but got '{0}'.", choices.length);

Env:
angular #1.4.7
bootstrap #3.3.5
ui-select #0.13.2

#224

Closing as a duplicate.


Bump Ruby and Rails versions

Bump Ruby and Rails to latest versions
Ruby

2.5.7
2.6.5
2.7.0

Rails

5.2.4
6.0.2

Everything passes but 2.7.0 outputs a lot of warnings due to this change
spec/govuk_design_system_formbuilder/builder/configuration_spec.rb:15: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call

Rails also seems to output a load of warnings, the I'm ignoring them for the time being using this kludgey filter
be rspec spec/govuk_design_system_formbuilder/builder/configuration_spec.rb 2>&1 | ag -v 'i18n|active_model|action_view'


Handle Classification.Description field

Currently this information is discarded, need to capture it and figure out where it belongs in the analyzer-lsp

I am suggesting that this belongs as a description on the tagging rule.


Improve scrolling actions in the animation track editor

Follow-up to #48572.

Implement timeline scrobbling using Alt + Mouse wheel anywhere in the animation track editor.

Snap settings are followed, and precise snapping can be obtained by also holding down Shift.
This modifier wasn't used by anything in the animation editor.

Allow zooming by using Ctrl + Mouse wheel on the timeline itself.

Previously, this was only possible on the track area, not the timeline.

The diff is relatively large because I had to expose the track edit so it can be accessed from the timeline.

Thanks!


Update manifest: Microsoft.DotNet.SDK.8 version 8.0.401

What's changed

It seems it won't touch Windows Registry while upgrading
Try uninstall previous version before installing new one
Maybe this can prevent infinite upgrading loop

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
Resolve #168528

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Should the same change be applied for .NET 6 and 7 manifests?

Did you validate if this pull request can solve infinite upgrade loop? I can also help porting them to previous major versions.

yeah, it worked for .NET 8.


SamplerResult.quasi_dists should return QuasiDistributions

Describe the bug
Instead, it returns dicts.
Steps to reproduce
from qiskit import QuantumCircuit
from qiskit.primitives import Sampler as QuantumInfoSampler
from qiskit_ibm_runtime import Sampler as RuntimeSampler

bell = QuantumCircuit(2)
bell.h(0)
bell.cx(0, 1)
bell.measure_all()

sampler = QuantumInfoSampler()
job = sampler.run([bell])
result = job.result()
quasi_dists = result.quasi_dists
print(type(quasi_dists[0]))

sampler = RuntimeSampler(options={"backend": "ibmq_qasm_simulator"})
job = sampler.run([bell])
result = job.result()
quasi_dists = result.quasi_dists
print(type(quasi_dists[0]))

<class 'qiskit.result.distributions.quasi.QuasiDistribution'>
<class 'dict'>

Expected behavior
See title.
Suggested solutions
See title.
Additional Information

qiskit-ibm-runtime version: 59b715e6769d1307045a6f042ca584cd47e4ea5c
Python version: 3.9.13
Operating system: Arch Linux

I just noticed that this is a duplicate of https://github.com/Qiskit/qiskit-ibm-runtime/issues/362.

Closing since it's a duplicate.

It's a duplicate, but the duplicate got closed even though this won't actually be resolved until https://github.com/Qiskit/qiskit-ibm-runtime/pull/511 is merged, so this should be kept open until that is merged, right @jyu00 ?

It was resolved by #455 when using the Sampler class.

Ah ok, this seems to still be an issue when loading jobs from the service but I guess that is the Result issue which is separate.


No instruction available for Commerce SDK

The article is outdated. The document has only reference to how use it if you are using Retail SDK. Retail SDK is being phased out and we are already on Commerce SDK. Please add instructions on how to this if you are using Commerce SDK.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 38dea829-cc3f-2e72-8d57-5bc6d594b8b6
Version Independent ID: ee57daf0-88ae-e3fe-a469-8508e231490e
Content: Deployment guidelines for cash registers for India - Commerce | Dynamics 365
Content Source: articles/commerce/localizations/apac-ind-loc-deployment-guidelines.md
Service: dynamics-365-commerce
Product: ****
Technology: ****
GitHub Login: @AlexChern0v
Microsoft Alias: jiaqia

Thank you for your feedback. @AlexChern0v can you please review?

Because of limitations of the new independent packaging and extension model and the Commerce SDK, it can't currently be used for the GST integration for India. You must use the previous version of the Retail SDK on a developer virtual machine (VM) in Microsoft Dynamics Lifecycle Services (LCS). Support for the new independent packaging and extension model for Commerce localizations is planned for later versions.


Price annotation and candles get out of sync

Description
After some period of time the price annotation gets out of sync with the last candle. Additionally the decimal precision is lost.
Steps to Reproduce

Open a candle chart
Wait
Use market sim to try to increment time to try to reproduce this
Eventually notice that the price annotation does not align with the last price on a candle

Expected behavior
Price annotation should match the closing price of the latest candle
Screenshots

Additional context
https://vegaprotocol.slack.com/archives/C037STCKMGC/p1685903922105259

Cannot reproduce it. Possible, it was fixed in some other previous works. Can you QA guys can confirm it?

I can't recreate this using market-sim so far. I'm not sure if we want to close this issue or just icebox it for now? cc @JonRay15 , @mattrussell36

We cannot reproduce and think this likely will have been fixed by the change to use the last candle when Core changed their retention policy on the candles API.  Closing this.


Missing 1 Collar

We have 3 collars and 3 bases and all but one of the collars are showing.  I have removed and readded the account multiple times so I don't know what is going on.  Any help is greatly appreciated.

Hi @jphelli,
Can you enable debugging, restart HA and then send me the logs?
Thanks!

Enabled Degugging and restarted HA as requested, attached are the logs.  Thank you!
John

On Mar 10, 2023, at 9:52 AM, sbabcock23 @.***> wrote:
Hi @jphelli https://github.com/jphelli,
Can you enable debugging, restart HA and then send me the logs?
Thanks!
—
Reply to this email directly, view it on GitHub https://github.com/sbabcock23/hass-tryfi/issues/63#issuecomment-1464007418, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHLRDNBA2QCZQCQ2OE2J4JDW3NE2NANCNFSM6AAAAAAVWR5XLI.
You are receiving this because you were mentioned.

@jphelli - I do not see the attachment. Can you try again pls?

Attached through the web interface vs mail.
home-assistant_tryfi_2023-03-10T16-21-48.470Z.log

Hi @jphelli ,
It doesn't look like debug is enabled. I would expect to see something similar below in the logs:
2023-03-08 23:02:06.702 DEBUG (SyncWorker_11) [pytryfi.fiDevice] LedOffAt is None, returning current datetime in UTC 2023-03-08 23:02:06.702 DEBUG (SyncWorker_11) [pytryfi.fiDevice] getAccurateLedStatus: LED Status is False 2023-03-08 23:02:06.790 DEBUG (SyncWorker_11) [pytryfi.common.query] getCurrentPetLocation: {'data': {'pet': {'ongoingActivity': {'__typename': 'OngoingRest', 'start': '2023-03-05T01:42:43.333Z', 'presentUser': None, 'areaName': None, 'lastReportTimestamp': '2023-03-08T23:01:21.312Z', 'obfuscatedReason': 'HAS_ACCESS', 'totalSteps': 12610, 'uncertaintyInfo': None, 'position': {'__typename': 'Position', 'latitude': 37.206212602173895, 'longitude': -90.50874803215265}, 'place': {'__typename': 'Place', 'id': '297m0V1feLQEyShmxJ3E', 'name': 'Home', 'address': '90 Mist Place', 'position': {'__typename': 'Position', 'latitude': 37.206343280428385, 'longitude': -90.50876211374998}, 'radius': 18.648358533925276}}}}}
To enable debugging, go into your configuration.yaml file and add the following:
logger:   default: debug

FWIW, I experienced similar behavior over the past 24 hours. I have 2 collars and 4 bases and noticed 1 collar was missing and all 4 of my bases. Not sure if the issues are related (I looked through @jphelli's log and didn't see the same errors I was), but I dug into my particular issue. In my case, I believe the issue was related to a possible deprecated value (batteryHealth) in the pytryfi package. I opened an issue with full details here: https://github.com/sbabcock23/pytryfi/issues/26. Thought it would be helpful to crosspost in case the issues are connected.

So I see the collar in the TryFi app and I see the missing collar with our dog's name "Delilah" in the logs, just can't figure out why it's not adding it to HA.  I have removed and re-added the integration multiple times to HA and it never loads her collar.

I'm having this same issue post 2023.3 update.
@jldeen -- curious how you got that workaround to work in the other thread you mentioned.  I looked for that fiDevice.py file to try to do the same, but no success in finding it...

@ichrispod I manually edited the package file. In my case, I run HA in a docker container. I exec'd into the container and then changed to the the /usr/local/lib/python3.10/site-packages/pytryfi/ directory. From there, I used vi to edit the fiDevice.py file. I restarted Home Assistant after this change. The downside is, this isn't a persistent change at the moment; I did it as a troubleshooting step/quick fix.
I do have the fix/patch published to my own package on PyPi here: https://pypi.org/project/jldeenpytryfi/ but integrating that into your HA install is a little more... chaotic. LOL.

Looking at other issues here and wonder if the possible deprecation of batteryHeatlh as mentioned in my other issue on the pytryfi package is the root cause for issues like #62 and #61, both of which have similar behavior I was seeing. If anyone feels comfortable, I'm curious to know if the manual edit of the fiDevice.py file followed by a complete restart of HA resolves your issues like it did for me.
Also, @sbabcock23 happy to submit a PR (I have some other updates in my pytryfi fork, including debugging and devcontainer support) if it'll help you.

I agree with the analysis so far. I have made a change and updated the versions. Please give it a try and let me know if this issue can be closed.
@jldeen  - if you have enhancements, fixes, etc. feel free to submit a PR. Always open to help!

@sbabcock23 Confirmed. The latest change resolves the behavior I was seeing. Thanks for the speedy update!

The updated code didn't resolve my issue, the 3rd collar is still missing.  I need some assistant with enabling the debug logging for just the tryfi integration, enabling the log is not an option as it's not obscuring account information that's why I removed the log I previously uploaded.

@jphelli Two thoughts:

When I updated the TryFi integration, I had to completely remove it and the accompanying pytryfi package to ensure both were bumped to the proper 0.0.19 version. Could you try that? Remove the integration completely, remove the pytryfi package in the previously mentioned site-packages folder, restart HA, then re-add TryFi through HACS and see if your issue persists.
If you can, try the pytryfi package in a local python environment and see if you are able to see all pets and all bases. If you are, it sounds like there may be an issue between the pytryfi library and your hass-fi integration. This was what I did for my issue, and is what helped me pin down the error.

@jldeen
I performed step one as you suggested, deleted the integration, restarted HA, purged the directory and then copied the updated files.  For good measure I restarted HA before I reinstalled the integration and still the same thing.  Just note, since day one the 3rd collar has never populated and they are all the same version 2 collars.
I will try the second option but it will take me a bit of work to figure all that out, python is not my strong suit.
Thank you for all the suggestions.

@jphelli Interesting.... I think suggestion number 2 may be insightful since HA is only able to intake the pets/bases through the pytryfi package.
To help you with the 2nd suggestion, I have @sbabcock23's latest code in my own fork, along with a devcontainer and a login.py script already configured for pytryfi debugging to help. (I also opened PR for that today).
I updated the readme in my fork, but basically, you:

Open that repo in the supplied devcontainer using vscode, which will give you a python dev environment to use.
From there, launch a terminal session, and export two env variables<EMAIL_ADDRESS>and fi_pass=yoursecretpassword
Run the login.py: python login.py.

The script should complete and you should be able to read the json output to see if you see all 3 collars, or if you see any ERROR indicators.
The output is a little jumbled together, so you'll have to read it closely, but you should see debug entries for each pet and associated device like this:
DEBUG:pytryfi:Adding Pet: Delilah with Device: FCXXXXXXXXXXX

You'll also see Pets in Home: at the end of the output that should have Pet ID, Device ID, and other potentially helpful information.

@jldeen
I'm currently having this problem, I think, and the latest update hasn't fixed it. In my case, no functioning entities at all are being passed to HA upon re-adding the integration... no base, collar, anything... but I do have a reference to the "batteryHealth" value in my logs, which makes me think the cause might be the same as the one you encountered.
However, I'm running into a problem following your suggestion of removing the pytryfi site-packages folder: I can't seem to find it. I get as far as /usr/local/lib and then I don't have a python3.10 folder in that location, or python anything else. Sorry, I'm running HAOS on an ODROID N2+ and am not the least bit Python or Docker literate, so I'm probably doing something very foolish. In fact, I'd love to try helping out with the 2nd suggestion as in your last post, but my eyes immediately glaze over at "open that repo in the supplied devcontainer using vscode".
If there's something simple I'm missing re: finding the python3.10 folder and deleting the appropriate subfolder, could you please point me in the right direction? Thanks so much.

Adding more noise here and will give a few of the suggestions a try but 2 days ago TryFi stopped updating my steps. I deleted the integration and re-added in HACS. I can login successfully and my only dog/collar/base shows up but the only entities that come with it are light.collar_light and select.lost_mode.  The steps, location, battery level are no longer present. Again, this worked up until 2 days ago.

Doing some testing here,
I removed one of the bases and the tryfi in HA didn't see the change until I removed and readded  the integration.  I then unlinked Delilah's collar in the Fi app and readded it, virtually loosing all her data and pictures.  I then went back to HA, removed and readded the integration and now it sees Delilah's collar, all the bases but now Stanley and Keera's collar are missing.  I've been working with these collars for years and I notice Fi has made some recent changes to their app so likely this is all related to a code change.  I'm going to redo another collar and see what happens.
Example:
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/pytryfi/fiDevice.py", line xxx

This traceback should indicate where your python folder is. If it doesn't, or you don't see any reference to site-packages in your logs, you will need access to the container/instance ODROID N2+ where your HA/HAOS runs. Once logged in, you can run the following command:  python -m site and this should output the information you need. i.e.
sys.path = [
    '/usr/local/lib/python3.10/site-packages',
    '/usr/local/lib/python310.zip',
    '/usr/local/lib/python3.10',
    '/usr/local/lib/python3.10/lib-dynload',
    '/usr/src/homeassistant',
]

From there, you should be able to navigate to that location to find the site-packages directory, and subsequent pytryfi folder. Once you find the pytryfi folder - delete it AND the pytryfi-0.0.18.dist-info folder also in site-packages (if this pytryfi-0.0.18.dist-info` exists, it's also a good indicator you're not using the latest version of the pytryfi code). After you delete those folders, delete the tryfi integration from HACS, restart HA for good measure, and then reinstall HACS, restart again.
If the recent 0.0.19 update solves your issue, you will be able to add your Fi integration, sign in, and you should see all your collars/bases with all attributes.
@RichardD012 I suspect you are encountering the same issue many of us have over the past 2 days. Please also follow the steps above to remove the TryFi integration from HACS entirely, along with any reference to pytryfi in your python/site-packages folder (this folder location will vary depending on how you run HA).

@jphelli Thanks for the troubleshooting - I know it's frustrating to lose data and pictures through the steps you're taking. I looked over your logs a little more in detail last night (I still had them from before you removed them here, and I have deleted everything except the Fi specific data to help you troubleshoot as I know there is personal information there).
Anyway, I noticed your logs appear to have 2 house holds with a total of 6 dogs:

Keera
Stanley
Ascher*
Delilah
Wiley
Sadie

All dogs except Ascher have a device attached, Ascher does not have any device associated, and Delilah, the missing dog, appears right after Ascher in the list. I believe this is why @sbabcock23 made additional changes in his latest 0.0.19 update - where if there isn't a collar attached, the pytryfi package will continue on with the queries, report "PET_ID_HERE has no collar. Ignoring Pet!" instead of hanging.
Theoretically, you should see all 6 dogs in the output from pytryfi, and not just Keera, Stanley, and Delilah, as it should parse pets and bases from multiple households.
From your HA instance, if you can navigate to the site-packages/pytryfi folder again, can you look at line 3 of the const.py? That will contain the PYTRYFI_VERSION and it shoudl be equal to "0.0.19".

Posting here what I did to make this work. Removing TryFi from HACS and then going into the docker container and removing pytryfi caused an error when trying to add the TryFi integration in HA (successfully installed through HACS):
Config flow could not be loaded: {"message":"Invalid handler specified"}
This was shown instead of the login dialog.
Going back into the container I see that pytryfi is back in site-packages but it's version 0.0.18. To upgrade to 0.0.19 I had to update pip and then I could upgrade pytryfi. Once I did this, version 0.0.19 was installed in site-packages and when I added the TryFi integration in HA after a restart, it successfully showed the login dialog after adding the integration in HA. Everything works now and the sensors and bases are back with all the entities.

@jldeen thanks for the investigation, I already changes all my account details but I do have concerns that PW's are being captured in flat file.
Ascher is one of our dogs that past away several years ago, not sure why he's still in there.  Sadie and Wiley are my mother-in-laws dogs and they are only visible as a dog walker so they should not be in HA, I wouldn't think anyway.
So, I was finally able to get Delilah, Stanley and Keera's collars along with all our bases to show in HA.  It took multiple, multiple attempts unlinking and readding the collars in Fi in order for them all to show.  The Fi app collar adoption is extremely flaky with the series 2 collars, I had to reboot the base multiple times for the collar to adopt.  For now I think we're good, until Fi makes other app changes.

@RichardD012 Thank you for the update and the steps you took to resolve everything! I had seen the same error you did, Config flow could not be loaded: {"message":"Invalid handler specified"} and I'm sure it's helpful for others on here to hear different ways to resolve that. I noticed it happens when there is a mismatch between the TryFi HACS integration and the underlying package dependency. Glad you got it sorted and are back up and running!
@jphelli So glad you got everything sorted, definitely sounds like it was a pain. As for Sadie and Wiley, they may not need to appear in HA, but the pytryfi package simply sends a graphql query to the Fi API, so it makes sense why it would see data from Fi's servers, but like you said, you don't need that data in HA.
As for all the linking, unlinking, and re-adding the collars, I assume you lost each dog's data, including pictures. I do still have the Fi specifics of your log file, which contains links to each dog's pictures Fi's servers. I'm happy to email you all the links so you can re-add each dogs pictures, if that will help. I will delete the file after you no longer need any further data from it. :)
Pending a reply from @loafbutts, I think this issue is closed as it sounds like everyone's issue has been resolved.

@jldeen Thanks for the offer for the pictures but I'm fine.  I realized that every collar is retained in the drop-down menu along with all their historical details.  So, I plan to remove all the news ones along with Ascher and try reactivating the collars under those old/existing profiles.  I'll let you know how all this plays out, good practice to go through.

@jphelli Sounds good! Just confirming I have removed all logs pertaining to you / your Fi instance. Looking forward to the update after you reactivate under the existing profiles.

@jldeen
So I removed Ascher's profile and all the new ones that were created earlier today.  Went back to the original profiles and activated each collar successfully.
Went back into HA and removed and readded the integration and I'm happy to report all 3 of our dogs plus my mother-in-laws 2 dogs, and bases are all reporting in HA.  So, looks like you are correct, Ascher's profile was likely causing the issue.  Thank you so much for all your assistance, it's been educational.  😃

@jldeen Huh. I have no idea what kind of strangeness is going on with my HA installation. My traceback DOES refer to /usr/local/lib/python3.10/site-packages/pytryfi/fiDevice.py but I am unable to see or access any such directory. Like, "cd /usr/local/lib/python3.10/site-packages/pytryfi" gives me "bash: cd: /usr/local/lib/python3.10/site-packages/pytryfi: no such file or directory". On top of that, "python -m site" results in "bash: python: command not found".
This is from an ssh into my HA machine, root. If I'm in a wrong container/instance, I'm honestly not sure what that means or what to do from here. I just may not have the basic python/Docker(?) knowledge to work through this one, in which case, please don't hold up the issue on my account. Thanks for your efforts!

@jphelli Thanks for the update! That makes a lot of sense - I suspected Ascher's profile was causing the issues, and I believe @sbabcock23 did too, which is why he made the additional change in 0.0.19 to not include pets without a device attached to them. At any rate, I'm glad you got it all sorted! Thank you for your patience as you worked through this.
@loafbutts Hmm... that is very strange. I haven't used HAOS, only HA in Docker, but I'm happy to help you troubleshoot further. I agree this issue can be closed, but I can work with you directly to solve things on your end. Feel free to DM me on Twitter @jldeen and I'll see if/how I can help. :)

@jldeen Thank you so much for offering. I just created a Twitter account for this... I'm not a social media guy... and it's not convinced I'm a human yet, so I can only DM people who follow me. Can I trouble you for a follow back on homeexistant, and then I'll DM away? Thanks again!

I think I'm having the same issue your are @loafbutts with finding the /usr/local/lib/python3.10/site-packages folder, so if there's some way you could post the resolution publicly, I'd appreciate it.

@pdileonardo If we find one, I'll be happy to!

It may help others to know how your HA is setup. Mine is running in a docker container so the location of /usr/local/lib/python3.10/site-packages is inside the container not on the machine. For docker you need to get into the container and see the file system there.
I know @loafbutts said HAOS so it could be a custom location depending on how that works. I updated my message  above with some more commands and explicit troubleshooting steps for anyone else who may make it down here.

Thank you all for the assistance especially @jldeen. I did make the update to ignore pets without a collar. Its possible that HACS didn't update it and all the dependencies. If there are further issues please let me know or close this one.

I have 2 different instances of Home Assistant.  Both on 2023.3.3 and running  0.0.19 of tryfi.   One of them is running great while the other is only showing teh 2 collars, but not the bases.    the 2 is showing tracker and Collar Light, whiel the 3 is showing as unavailable.   I am going to see if I can spot differences, but if someone one has an idea to help me troubleshoot please pass it along
Broken one.

Working one

@RichardD012 If it's of any use, I installed HAOS on an ODROID N2+ according to the instructions at https://www.home-assistant.io/installation/odroid so my Python stuff is... in a container?... wherever that installation process normally drops it. The N2+ is completely dedicated to Home Assistant, nothing else running on it.
Unfortunately, if it's in a container, I'm a completely blank slate when it comes to Docker, and don't even know what one looks like or how to get into it if I find it. If you have any pointers that wouldn't be too much trouble to share, on that front, I'd be grateful and gladly do some hunting.

@loafbutts From an SSH session on your ODROID N2+, you can try to run docker ps to see if you have any containers running. If you do, you would see output similar to this:
CONTAINER ID   IMAGE                                          COMMAND                  CREATED        STATUS                    PORTS     NAMES
ff9d4fbf45cd   home-assistant   "/bin/sh -c 'echo Co…"   28 hours ago   Exited (0)  3 hours ago             musing_thompson

From there you can follow @RichardD012's guidance to exec into the container using the container name or the first 3 characters of the container ID. i.e.:
docker exec -it ff9 /bin/bash

From there, you should be able to run the other commands to find your python location and subsequent pytryfi and pytryfi-0.0.18.dist-info directory.
If the above commands do not work, and if you don't have docker available from your ODROID instance, I'll have to do some more digging.
@smarthomeaf Feel free to read all the suggestions in this thread and try the troubleshooting steps others have found helpful. I suspect the HA instance that isn't working correctly has an outdated version of hass-tryfi and is possibly using the older version of the underlying pytryfi package. Please update both following the instructions in this thread, both should be version 0.0.19. Once you do this, both your HA instances should work fine.
@pdileonardo Please try the suggestions regarding Docker and the other commands in this thread. Let us know if you still need help.
Thanks everyone! To confirm, this issue is effectively closed as the problem has been resolved in the latest 0.0.19 update. I will continue to help those here who are having trouble locating their python site-packages instance, but for anyone new who stumbles on this, please read all the suggestions here for upgrading hass-tryfi and the underlying pytryfi package to the latest 0.0.19 version as this should resolve issues of your collars/bases not showing or not showing all attributes. 😃

Since it's come up I thought it may be value to others. I'm running HAOS in a non-docker architecture on RPI4 with SSD and overall I have had very little issue with this setup.  Hope this helps.

VICTORY! It was a somewhat involved process, but definitely educational, and I've finally got all my entities again!
First off, accessing the homeassistant Docker container in HAOS via ssh can't be done with the official HA ssh add-on, named "Terminal & SSH". I don't know exactly why, but a community add-on called "SSH & Web Terminal" is required. It can be installed from the standard community add-on repository.
Once it's installed, it won't start successfully until a username/password or authorized key has been created. I followed this guide: https://www.tecmint.com/ssh-passwordless-login-using-ssh-keygen-in-5-easy-steps/ to create a key pair, though as recommended by the guide at https://community.home-assistant.io/t/sshing-from-a-command-line-sensor-or-shell-command/258731 I stored the keys in /config/.ssh rather than the default /root/.ssh. You can then paste the public key into the authorized_keys: section in the add-on's Configuration tab. On the Info tab, the "Protection mode" switch must be toggled off. It should then be possible to start the add-on.
Once SSH & Web Terminal is up and running, click "OPEN WEB UI" on the Info tab. Then enter "docker exec -it homeassistant bash". That gets you into the HA Docker container within HAOS. I was then able to navigate to /usr/local/lib/python3.10/site-packages just as @jldeen described. Finally! And yes, pytryfi was still version 0.0.18. So, from there I removed the TryFi integration, reboot HA, removed TryFi from HACS, reboot again, went back to ssh and did an rm -rf on pytryfi and pytryfi-0.0.18.dist-info, then one more reboot for good measure.
After that, I was able to download TryFi in HACS and re-add the integration to HA, and everything worked perfectly, just like it used to. I hope this helps any readers who have a HAOS configuration similar to mine, and a similar set of headaches getting the advice in this thread to work for them.
@jldeen @sbabcock23 @RichardD012
Thank you SO much for your advice and all the time and investigative work you've put into the issue and shared here. You've been very generous, way above and beyond the call of duty.

Indeed that nailed it!  Many, many thanks to all who contributed to the resolution.  My dogs will sleep more soundly now knowing that Home Assistant is watching over them once more.

@loafbutts and @pdileonardo So glad you got it all sorted out and huge thank you to @loafbutts for the excellent write up! Everything you described makes perfect sense and now that it's documented in this issue, it will help others who may have your same HAOS configuration.
@jphelli or @sbabcock23 Everyone here is back up and running, and we seem to have all the possible troubleshooting/fixes documented. I think this issue can safely be closed.

Agree.  Since I'm the one who opened the issue should I be the one to close it?

@jphelli Yes, as long as you feel the issue has been resolved. Thanks!


How to avoid duplicating Formatter Configuration

Hey team! Currently, I have the following config files (test and prod).
# config/dev.exs

config :logger, :default_formatter,
  truncate: :infinity,
  format: "$time $metadata[$level] $message\n",
  metadata: [
    :request_id,
    :trace_id,
    :span_id
    # ... even more keys
  ]

And
# config/prod.exs

config :logger, :default_handler,
  formatter:
    {LoggerJSON.Formatters.Basic,
     metadata: [
       :request_id,
       :trace_id,
       :span_id
       # ... even more keys
     ]}

Where I would duplicate the configuration in both config files, ideally, I wish to use config/config.exs only or be able to configure the :default_formatter metadata only to avoid forgetting to change all the required files to keep it in sync.
What would you suggest here to avoid duplication?

Hello 👋, the reason why it wasn't the issue for us is that for JSON we keep metadata: {:all_except, [:conn, :socket]} because we want to keep as much data as we can, while dev/test logs (from config.exs) are typically very minimal to keep readability.
I think what we can do is to either try to read config from [:logger, :default_formatter, :metadata] by default (but I think that might cause issues) or introduce a new syntax for metadata that would looks something like {:from_application_env, [:logger, :default_formatter, :metadata]}. WDYT?

{:from_application_env, [:logger, :default_formatter, :metadata]}

I think that would work; I was thinking something around those lines, maybe metadata: :default_formatter?
I am unsure of the technical details, so I trust your judgment!

I think it would be great if the metadata from the default formatter could somehow be inherited by LoggerJSON.
I currently do the following to avoid duplicating logger metadata config.
logger_metadata = [:request_id]

if Mix.env() == :prod do
  config :logger, :default_handler,
    formatter: {LoggerJSON.Formatters.Basic, [metadata: logger_metadata]}
else
  config :logger, :default_formatter,
    format: "$time $metadata[$level] $message\n",
    metadata: logger_metadata
end

Pushed this feature to the main, please give it a try. The obvious downside is that we will have to read from application env on every logged message (which is an :ets table) since there is no way to initialize and keep the state for the :logger_formatter behavior.

Feature will be released in 6.2.0.


Members: add veriphi

This PR adds Veriphi as an Optech member

ACK. Looks good. Thanks Schmidty! Go ahead and merge whenever you're ready.


Dont add to browser history on location change

Description

Changes the logic of writing to the hash so that for location changes we just replace the existing hash. This prevents moving the map from creating history items in browser history. Now we create history entries for all actions except map movement.

Closes #124
QA steps

[x] Open Maperture and see a browser history item
[x] Move the map around and expect no additional browser history items
[ ] Change other settings (eg view mode) and expect to see browser history items

Author checklist
Create the PR

[x] Fill out PR template
[x] Make sure you've added a CHANGELOG entry under "Unreleased"
[x] Request a review
[ ] Make any requested changes and get approval

After approval

[ ] Merge any changes from main into your branch, resolve any conflicts
[ ] Squash & merge changes into main
[ ] Delete branch

Ah, that's a good catch @ebrelsford ! I'll go ahead and open that followup issue after merging this then.


DigitalOcean driver hangs with PermitRootLogin no

Hey,
I tried creating a droplet with user-data.
It works fine until I specify PermitRootLogin no in the sshd_config and --digitalocean-ssh-user "my-user". The user exists and has passwordless sudo privileges. I can ssh my-user@droplet-ip into the machine and run stuff like sudo apt-get update.
The provisioning hangs at this point:
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Error creating machine: Error waiting for SSH: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded

docker-machine version 0.5.4, build 6643d0e on OS X 11.11.2
OpenSSH_7.1p1, OpenSSL 1.0.2e 3 Dec 2015
Am I missing anything?

Here the config to reproduce this:
droplet-config.yml:
#cloud-config
users:
  - name: foobar
    groups: sudo
    shell: /bin/bash
    sudo: ['ALL=(ALL) NOPASSWD:ALL']
    ssh-authorized-keys:
      - ssh-rsa my-user-key
write_files:
  - path: /etc/ssh/sshd_config
    content: |
      Port 22
      Protocol 2
      HostKey /etc/ssh/ssh_host_ed25519_key
      HostKey /etc/ssh/ssh_host_rsa_key
      KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
      Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
      MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-ripemd160-etm@openssh.com,umac-128-etm<EMAIL_ADDRESS>      UsePrivilegeSeparation yes
      KeyRegenerationInterval 3600
      ServerKeyBits 1024
      SyslogFacility AUTH
      LogLevel INFO
      LoginGraceTime 120
      PermitRootLogin no
      StrictModes yes
      RSAAuthentication yes
      PubkeyAuthentication yes
      IgnoreRhosts yes
      RhostsRSAAuthentication no
      HostbasedAuthentication no
      PermitEmptyPasswords no
      PasswordAuthentication no
      ChallengeResponseAuthentication no
      X11Forwarding yes
      X11DisplayOffset 10
      PrintMotd no
      PrintLastLog yes
      TCPKeepAlive yes
      AcceptEnv LANG LC_*
      Subsystem sftp /usr/lib/openssh/sftp-server
      UsePAM yes

docker-machine create --driver digitalocean \
                      --digitalocean-access-token "XYZ" \
                      --digitalocean-image "ubuntu-15-10-x64" \
                      --digitalocean-region "fra1" \
                      --digitalocean-ssh-user "foobar" \
                      --digitalocean-userdata "droplet-config.yml" \
                      docker-droplet

Am I missing anything?

The superuser account name for all DO droplets is "root". If you want Machine to connect to the host using another username you would also have to pass that account's SSH key to Machine. This is currently not possible.

root and the new user use the same ssh key in my case. Why is machine concerned with keys at all? Shouldn't SSH pick the right one?

@klaemo

root and the new user use the same ssh key in my case

I very much doubt that. The SSH key is dynamically created each time you docker-machine create a new instance. And thats the key Machine will use for its SSH connections even if you specify a different user with --digitalocean-ssh-user.

Okay, my bad. Then I misunderstood what machine does under the hood. I still think docker-machine create should be usable without root.

@klaemo +1

@klaemo NP, you might want to vote +1 for this: https://github.com/docker/machine/pull/1438 since this would allow you to do what you want.

this still fails for me, even with specifying my own fingerprint.
$ docker-machine create \
>  --driver digitalocean \
>  --digitalocean-ssh-user NON_ROOT_USER_HERE \
>  --digitalocean-access-token MY_DIGITAL_OCEAN_ACCESS_TOKEN_HERE \
>  --digitalocean-region nyc1 \
>  --digitalocean-image centos-7-x64 \
>  --digitalocean-ssh-key-fingerprint MY_FINGER_PRINT_HERE \
>  MY_NEW_DROPLET_NAME
Running pre-create checks...
Creating machine...
(do4) Creating SSH key...
(do4) Assuming Digital Ocean private SSH is located at ~/.ssh/id_rsa
(do4) Creating Digital Ocean droplet...
(do4) Waiting for IP address to be assigned to the Droplet...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
$

$ docker-machine --version
docker-machine version 0.12.2, build 9371605

$ docker --version
Docker version 17.06.1-ce, build 874a737

the only option left is to create it with root user and then manually change the user -- not ideal.


add test for notifying on inner arc handle updates

sorry for the confusion, it appears to be working, I must be doing something wrong in my non-test particles. but i figured, we could as well keep this test.

LGTM for the test itself. I'd prefer to inline the manifest and particle implementations via the StubLoader approach so all the relevant bits can be seen within the test code itself, rather than distributed over 4 files.

thanks for the recommendation, totally agree, this is much better - done!


Images not loading when initialData doesn't resolve immediately

Problem
When using excalidraw React component and passing a promise to initialData prop, images are not loading unless the promise is immediately resolved.
Why am I doing this?
I'm using excalidraw component on a personal app that fetches the initial scene data from a server, resolving the initialData promise once the server responds and I noticed that the excalidraw renders all the elements but only the placeholders are shown for the images:

In the beginning, I thought that the scenario data returned by the server might be corrupted, but if I pass the same data with Promise.resolve, it works with no issues. I also noticed that if the app window is resized, the images are immediately loaded, so maybe I'm missing a function call somewhere to force the image loading?
Example
Here's a small snippet to illustrate what I'm doing:
const initialData = {}; // let's imagine is a valid scene data

export default function App() {
  const initialStatePromiseRef = useRef({ promise: null });
  if (!initialStatePromiseRef.current.promise) {
    initialStatePromiseRef.current.promise = resolvablePromise();
  }

  useEffect(() => {
    // Simulating request
    function fetchData() {
      setTimeout(() => {
        initialStatePromiseRef.current.promise.resolve(initialData);
      }, 250);
    }
    fetchData();
  }, []);

  return (

 Excalidraw Example

        <Excalidraw initialData={initialStatePromiseRef.current.promise} />

  );
}

Codesandbox
Here's a functional example: https://codesandbox.io/s/excalidraw-forked-ts6s3s?file=/src/App.tsx

Thank you very much for this amazing tool! I'll be very happy to contribute if you think this would be a great first issue!

Hmm looks like a recent regression, the CSB example in readme is broken is a well, checking

I have same issue.
In my case it doesn't reload when I resize the window. But when I resize the image, it shows the image.
https://user-images.githubusercontent.com/44263972/215362321-544f0ff4-cea5-4482-ae9d-b888950e2924.mp4

@kobe651jp can you post an example code how to reproduce that (e.g. on codesandbox)? I can reproduce the original issue, but not yours.

This issue has been resolved. In my case it happens when the following processes are done at the same time.

Initialize
update Scene

If process updateScene after initialization completes, seems it will work.

Issue is resolved with this tiny code
excalidrawAPI.addFiles([   {     id: "pika",     dataURL: pikaDataURL,     mimeType: "image/jpeg",   }, ]);
Just pass the array of files in addFiles function from excalidrawAPI.
from https://codesandbox.io/p/sandbox/excalidraw-files-example-r7ophm?file=%2Fsrc%2FApp.js%3A83%2C29-89%2C32


Add location name to card and details and add filter

Rules for how the filter will work:
The locations filter will only appear if there are multiple locations
If there are multiple locations, then the location filter will only show once the user has selected a provider filter. For example, the user will only see locations for Growing Expert Teachers once they select Growing Expert Teachers.
If a user removes an organisation then any selected location filters for that organisation will be automatically removed.
For (2) we know there is a risk that a user with low-digital literacy/a first time user may not spot the appearance of the additional filter, but we will solve this when we look at onboarding users generally.
The reason for this is because:

we have extremely limited space to work in so we can’t simply nest the location checkboxes within the provider checkboxes AND present back that relationship in the selected filters area at the top
It’s potentially a lot of data to load and so we want to load more options as they become relevant

My concerns are:

the filter list is getting very long, I think we need to begin collapsing sections or rethink
after selecting an organisation to filter on, a user will focus on search results and not see the location filters – many won't find them, I think this will be more than just low-digital literacy/first time users


The syntax for making an API connection for use with a Managed Identity is incorrect.

The syntax for an ARM template to deploy an API connection that uses a Managed Identity is incorrect. The properties field needs to have:
"authenticatedUser": {}
"customParameterValues": {},
"alternativeParameterValues": {},
"parameterValueType": "Alternative",
"parameterValueSet":{},
Or it doesn't allow for Managed Identity use.
See example below.
Also you should have "apiVersion": "[providers('Microsoft.Web','connections').apiVersions[0]]" in the documentation to help people use the most recent API versions in templates without having to go find them/update them.
{ 	"type": "Microsoft.Web/connections", 	"apiVersion": "[providers('Microsoft.Web','connections').apiVersions[0]]", 	"name": "azurevm", 	"location": "[variables('location')]", 	"kind": "V1", 	"properties": { 		"displayName": "AzureVmConnection", 		"authenticatedUser": {}, 		"connectionState": "Enabled", 		"customParameterValues": {}, 		"alternativeParameterValues": {}, 		"parameterValueType": "Alternative", 		"parameterValueSet":{}, 		"api": { 			"name": "azurevm", 			"displayName": "Azure VM", 			"description": "Azure VM connector allows you to manage virtual machines.", 			"iconUri": "https://connectoricons-prod.azureedge.net/u/shgogna/globalperconnector-train1/1.0.1639.3310/azurevm/icon.png", 			"brandColor": "#FFFFFF", 			"category": "Standard", 			"id": "[concat('/subscriptions/',variables('subscriptionid'),'/providers/Microsoft.Web/locations/',variables('location'),'/managedApis/', 'azurevm')]", 			"type": "Microsoft.Web/locations/managedApis"		 		}, 		"testLinks": [] 	} }

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

ID: cdfb9148-5d81-f65e-3cb3-aa7c5eb5867b
Version Independent ID: 5051db4d-83d1-a230-6fcb-9238a384961d
Content: Authenticate connections with managed identities - Azure Logic Apps
Content Source: articles/logic-apps/create-managed-service-identity.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@AWheelwrightBLM
Thanks for your feedback! We will investigate and update as appropriate.


exclude any reference to log4j from demo project

log4j is too old and demo project should migrate to something actual like logback.
after fixing, please submit new ticket to generate carina archetype based on changes

requirements:

exclude old log4j 1.2.17 completely
declare latest slf4j interface and update all loggers declaration in demo classes
add logback dependency as modern logger implementation

ch.qos.logback
logback-classic
1.2.3

update logback.xml having default pattern instead of cyan
https://github.com/qaprosoft/carina-demo/blob/14f7f7a7c426b1c6d86768abddf4c6467b32b016/src/main/resources/logback.xml#L15

default log pattern is
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>

Execute api/web tests over carina-demo:
log messages displayed for INFO layer
no DEBUG messages
tests executed as usual

@ivansnytko could you please add carina-core_version= for verification this ticket?

Tested. Fixed.


[v2] ENUM Enhancement

I know you're busy releasing v2, so let's get this added after you release v2.
The problem with ENUM's right now is that, there is no way to go back from the underlying value to the ENUM key. We are using hacky ways to do this right now (looping through keys of Enum and checking equality). Maybe you have this implemented but due to lack of documentation I cannot be sure.
I think this should be part of the ENUM type, something like EnumType.getENUM(val). Let me know your thoughts.

When I was implementing ENUMs I was thinking about such feature but I've decided that it's not necessary. In most cases ENUMs are just for easier (more human) notation. You just write Status.OPENED instead 2 or something like that. In most cases you don't need key OPENED. Could you give me some example where it's necessary?

There are 2 cases where this comes in really handy.
Case 1 is where you have a ENUM type defined with alot of keys and whenever you make a retrieval from the DB, you have to make a comparison with each one to know which one it is. It ends up either being a really long else if or a switch block.
Case 2 is where you have another object that uses the same keys to specify some data. In that case you have to first loop to get the Keys from Enum.
Currently we are using a handy function for this sort of thing:
function getEnumKey(enumObj, val) {
  for (var i = 0, keys = Object.keys(enumObj), keysLength = keys.length; i < keysLength; i++) {
    if (enumObj.hasOwnProperty(keys[i]) && enumObj[keys[i]] === val)
      return keys[i];
  };
}

I think a few handy utilities in the ENUM type will be helpful in different cases. Like getIdentifiers() and getIdentifier(val) will go a long way. Let me know your thoughts on this.

Ok I will introduce such function to ENUM

I'm implementing it right now, but there is one more question about ENUMs and possible values. Right now ENUMs in Astronomy can have any value not only numbers which actually is not perfect, because it breaks base principle, values are enumerated. However, in most languages it's possible to assign the non successive numbers for each identifier. So I think about changing how syntax will look like.
const Status = Enum.create({
  name: 'Status',
  identifiers: ['OPENED', 'CLOSED', 'DONE', 'CANCELED']
});

so assigned values for each identifier will be:

OPENED = 0
CLOSED = 1
DONE = 2
CANCELED = 3
And if you want to provide non successive values then

const Status = Enum.create({
  name: 'Status',
  identifiers: {
    OPENED: 1,
    CLOSED: 2,
    DONE: 4,
    CANCELED: 8
  ]
});

What do you think?

That works, but I don't understand why would you want to hard bound them to integers. I think having any possible value for them is great. Do you wish to switch to numbers only so you can make use of Array functions?

Yes I'm thinking about limit it only to numbers which is how ENUMs work in every language https://en.wikipedia.org/wiki/Enumerated_type so I thing it's good to keep up with the standard

That works for me, however just wanted to clarify it is not required that ENUM keys equal to an integer, it's just that most languages implement them that way. The wiki page also states it as "often" not as a requirement.

I've made some fixes and allowed any values however numbers are default. I will describe more in a documentation.

I know you got this part done and its working great for me, except a few edge cases which when i researched online, people have been able to solve by use of ES6 symbols. I would like you to have a look at es6-enum and enumify
Perhaps you can use them internally in astro. The edge case i have currently is if i have 2 separate Enum Objects with the same final value, they will match each other even though the parent Enum is different altogether. This doesn't happen when Enums are implemented using Symbols as they have this intrinsic property to never overlap with another symbol.
Let me know your thoughts, we can perhaps get this in v2.1

Nice idea, I will probably add that feature in v2.1

I've started working on this feature and I have one problem with it. Using Symbols as values maybe is a fancy trick but it may cause also some problems. There may be situations where somebody wants to compare enum value to another raw value like post.status === 4 not just post.status === Status.OPENED. In such situations it would not work. There is also a problem with storing ENUM values  in a database, which looks like this
{
  "_k": "Symbol(Symbol.iterator)_6.13r9nd1y6xswcdi"
}

So I will have to prepare some converter on document save that will store it in more human readable way.

Storage is definitely going to require a bit of work. I'll do a bit of research on Symbols, i don't have experience using them either :).
I don't see a reason why someone would want to compare an ENUM with it's base value. It's goes against using ENUM in the first place.

Hi @jagi ,
How should i go about retrieving the value of the ENUM?
Thanks,

@chathuraa If you want to get value of the ENUM you just use this enum and identifier YourEnum.IDENTIFIER if you want to get identifier using value then YourEnum.getIdentifier(enumValue). Or you're talking about something else?
@talha-asad yes it will require a bit of work :)

Hi @jagi,
Apologies for not explaining it properly.
I was wondering given the Identifier how to get the underlying value.  ie. MyEnum.getValue(enumIdentifier).
Thanks,

Like that :)
MyEnum[enumIdentifier];

oh... feel dumb now. Thanks :)

@chathuraa no problem :) Don't feel bad, sometimes the easiest answers seems to be hard :)


TypeError in RTF format

(Original issue 1048 created by ymhuang0808 on 2014-10-28T02:46:34.327421+00:00)
An error occurs in PHP RTF format.
The error message is below:
*** Error while highlighting:
TypeError: ord() expected a character, but string of length 3 found
(file "/Library/Python/2.7/site-packages/pygments/formatters/rtf.py", line 77, in _escape_text)
{\cf2 'description'} {\cf4 =>} {\cf2
Do I show the target file?

(Original issue 1048 last updated on 2014-10-29T06:55:34.324090+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by ymhuang0808 on 2014-10-28T03:02:09.474466+00:00)
Hi,
I find the problem. Because the line contains Traditional Chinese, I change the Traditional Chinese into English. Does Pygments support Traditional Chinese?

(Original comment by birkenfeld on 2014-10-28T08:35:10.521629+00:00)
In principle all Unicode is supported, but this may be an issue with using a narrow-unicode build of Python and characters outside the BMP.
Can you attach a minimal example file that shows this error, and the command line you used for pygmentize? Also, which Pygments version is this?

(Original comment by ymhuang0808 on 2014-10-28T09:07:56.035110+00:00)
Pygments version is 1.6 .
The command is:
#!shell

$ pygmentize -f rtf EventTest.php

My example file:
#!php

<?php

class EvnetTest extends \PHPUnit_Framework_TestCase
{
    public function testSetAndGetEvent()
    {
        $event = new \PHPUnitEvent\Event();
        $eventArray1 = array(
            [
                'name' => 'PHPUnit',
                'start_date' => '2014-10-27 09:00',
                'end_date' => '2014-10-27 12:00',
                'description' => 'PHPUnit 教學 XD',
            ]
        );
        $event->setEvents($eventArray1);
        $this->assertCount(1, $event->getEvents());
    }
}

The error occurs in line 13.

(Original comment by birkenfeld on 2014-10-28T09:12:28.399900+00:00)
Please attach the file instead, when copying from the web page I can't be sure the encoding is preserved.

(Original comment by ymhuang0808 on 2014-10-28T09:14:01.086959+00:00)
The file link in Github: https://raw.githubusercontent.com/ymhuang0808/PHPUnit-Event-example/996094ed369efcf7a4c33b20648c714174a23274/tests/EventTest.php

(Original comment by birkenfeld on 2014-10-28T16:36:30.707942+00:00)
Thanks. I'll have a look.

(Original comment by birkenfeld on 2014-10-29T06:50:49.250474+00:00)
OK, this is likely already fixed in 2.0rc1, parts of the RTF handling code have been rewritten there. Thanks for the report!

(Original comment by ymhuang0808 on 2014-10-29T06:55:34.322280+00:00)
Thanks for your help :)


How can I change the port on which NFVO is running from 8080 to a different port ?

if you add the parameter (server.port=xxx) in the openbaton-nfvo properties file located in /etc/openbaton it should work.


CEF is not displaying anything

Research + fix. Currently it doesn't seem to work for everyone.
If you want to try it do this:

Start node.js (with inexor_node_unix or inexor_node_windows.bat)
Start Inexor
Type in the console: /subsystem_start cef

If somebody get something displayed let us know please.
CEF log on Windows: https://gist.github.com/Croydon/26956a04359aeece6c24

Works for me

This is fixed in karo+fohlen+hanack/fix_cef


[Feature]: Support compiler options: managedPaths and unmanagedPaths

What problem does this feature solve?
This allows for the modification of the source code of the packages inside node_modules using yalc or by manual means. It is particularly useful for debugging self-developed libraries.
What does the proposed API of configuration look like?
Same as in the webpack:

managedPaths
unmanagedPaths

Currently rspack will watch all files, including those inside "node_modules". And this should satisfy your request.
So I understand you want rspack to ignore certain changes in node_modules by supporting managedPath and unmanagedPath?

Currently rspack will watch all files, including those inside "node_modules". And this should satisfy your request.
So I guess you want rspack to ignore certain changes in node_modules by supporting managedPath and unmanagedPath?

Yes, watching all files inside node_modules is a heavy operation.

maybe you should use https://rspack.dev/config/watch#watchoptionsignored.

maybe you should use https://rspack.dev/config/watch#watchoptionsignored.

Snapshot managing is not associated in any way with the watching. Currently as I know rspack will rebuild when any change occurs. Initially I created the issue because I thought that rspack doesn't rebuild when dependencies inside node_modules are changed, but it does.
The option managedPaths, unmanagedPaths should be added only when the rspack will stop applying changes from the node_modules directory.


Pairing with Steel. mini Wireless

Looks like BT pairing profiles don't match between SMW gamepads and the operating system. https://stackoverflow.com/a/27573139/6663884
That caused MFGF to not use the BT stream.

Wired connection looks to detect the gamepad but it turns out to unknown device state
I tried out a specific Apple Airport bluetooth Mini pcie module from BCM... sadly Stratus bluetooth connection doesn't match the xinput driver unlike Nimbus
I may look closer to Windows Bluetooth registry settings at some point

Since stratus mo'i is an MFi accessory for WiAP (Wireless iPhone Accessory protocol} and not a macOS gamepad it's just about focusing on iphone Bluetooth specs.. It's always been using thz Bluetooth 4.0 at least

Bluetooth® Versions
Features and Specifications

Bluetooth® v1.0 to v1.08
Mandatory Bluetooth® hardware device and address

Bluetooth® v1.1
IEEE standard 802.15.1-2002

Bluetooth® v1.2
Faster connection

Bluetooth® v2.0+EDR
Enhanced data rate

Bluetooth® v2.1
Secure simple pairing

Bluetooth® v3.0
High-speed data transfer

Bluetooth® v4.0
Low energy consumption; recently in use in apple i- phone 4s

Bluetooth® v4.1
Incremental software update

Bluetooth® v4.2
New feature for Internet of Things (IoT)

Bluetooth® v5
Increased speed for Bluetooth® Low Energy (BLE)

Bluetooth® v5.1
New feature in Core Specification Addendum (CSA) 6

Bluetooth® v5.2
New features for LE


Client Teleporting Clarification

Changes
TeleportAsync Server-side only Warning modification to let readers know client-side alternative by utilizing Teleport() instead of TeleportAsync().
Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

Thanks a bunch @vq9o. I modified the language a bit to recommend the newer method, but this is good info -- appreciate the PR.


pkg/apis: unexport ApplyContainerReplacements

Changes
It is only used internally. This also removes the
container_replacements_test.go as the code is/should already be
covered by sidecar_replacements_test.go and
step_replacements_test.go.
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

/approve


Error reading s3 xlsx file to pandas dataframe in 1.4.1

Received a syntax error while reading a csv and xlsx file from s3 to a pandas dataframe after updating the version to 1.4.1.

had to downgrade back to version 1.4.0 to get things done...

We are aware that 1.4.1 is incompatible with py35, but have not yet decided what to do about this. ( ref #305 )

Thank you :)


Corrupted Pumpking and Beacon not shooting

Yeah; that's basically it. In creative I can shoot them just fine but in survival even with 200 levels of XP i cant shoot them at all.

Update: I can shoot them but they are kinda buggy

Will be more consistent in the next update, which will introduce soul mechanics and avoid XP depletion.


one CPU core goes to 100%  after few minutes than Insight hangs/crashs

As mentioned in the title, one insight instance (1 CPU core) goes to 100% and Insight become unresponsive until I kill it and restart it.

This looks like it's using an older version. The latest version is significantly different, so this issue may not be relevant.

Hello,
I checked the production tag when cloning, insight-API version v0.2.18 and this is the production version as well.
I tried to deploy the latest version but the bitcore-lib always fail to compile with this error:
    /usr/local/lib/node_modules/bitcore-node/libbitcoind
   ./autogen.sh
   configure.ac:25: installing 'build-aux/compile'
   configure.ac:5: installing 'build-aux/config.guess'
   configure.ac:5: installing 'build-aux/config.sub'
   configure.ac:9: installing 'build-aux/install-sh'
   configure.ac:9: installing 'build-aux/missing'
   Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
   Makefile.am:3:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
   Makefile.am:3:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
   Makefile.am:3:   If 'LT_INIT' is in 'configure.ac', make sure
   Makefile.am:3:   its definition is in aclocal's search path.
   Makefile.am: installing 'build-aux/depcomp'
   parallel-tests: installing 'build-aux/test-driver'
   autoreconf: automake failed with exit status: 1
   npm ERR! Linux 3.19.0-33-generic
   npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "bitcore-node@latest"
   npm ERR! node v0.10.40
   npm ERR! npm  v2.14.9
   npm ERR! code ELIFECYCLE

   npm ERR<EMAIL_ADDRESS>install: `./bin/install`
   npm ERR! Exit status 255
   npm ERR!
   npm ERR! Failed at the<EMAIL_ADDRESS>install script './bin/install'.
   npm ERR! This is most likely a problem with the bitcore-node package,
   npm ERR! not with npm itself.
   npm ERR! Tell the author that this fails on your system:
   npm ERR!     ./bin/install
   npm ERR! You can get their info via:
   npm ERR!     npm owner ls bitcore-node
   npm ERR! There is likely additional logging output above.

I can't get Copay to work with insight being unstable.

I suspect your culprit is here, (haven't recreated the error but recalling from memory)
npm ERR! node v0.10.40
I had a similar error that was resolved on machines that had node.js v 0.12.x & 4.2.x, i recommend trying to update your nodejs and trying again.

Yep, bitcore-node currently supports Node.js v0.12 and Node.js v4.2

More details here: https://bitcore.io/guides/full-node

Will try it over weekend, and report.

Issue solved, problem caused by the coin daemon.


auto_register: add spec_import kwarg

Expanding on https://github.com/googlefonts/fontbakery/pull/1887, I added an explicit spec_import kwarg to auto_register. I suspect sniffing globals will make testing more error-prone.

The tests fail now because:

opentype.py doesn't include loca
The filtered checks are still registered?!

2.The filtered checks are still registered?!

see https://github.com/googlefonts/fontbakery/issues/1886#issuecomment-392563638

Oh, so I need to use auto_register's filter_func?

Yes, when you don't want to (auto) register the checks.
check_filter is after registering when the spec is executed, just before the check is called.

This is confusing from an API standpoint...

This is confusing from an API standpoint...

The names?

Ok. So we add a docstring, and we call it set_check_skip_filter ?

Kay :)
Maybe even make it a @property so we can drop the set_.

@felipesanches merge?


Working example please

Could you please add a working example.
I tried the code with MetaMask which fails silently and TrustWallet which says "An unknown error occured." and stalls in "Connecting..." phase.

@numerized Would love to get an example Unity starter project with this library and Nethereum!

Hey there, any updates here?
Tried to run the example but it throws an error on connect.
Also tried to convert the version for Unit. Meta Mask Pops up but no connection request is made (where you can agree or reject). Trust wallet also pops an unknown error message.

the current example doesn't work, calling ex: var walletConnectData = await walletConnect.Connect(); just hangs.
Is there anything besides doing steps 1-4 that will work. I tried the Netherium console example and attempted to integrate into a blazor server, but it hangs exactly the same.
Any help would be appreciated, if you like I can write up a tutorial once I get it working locally


manage.py runjob not compatible with apps that use AppConfig in INSTALLED_APPS

Same issue as #641, presumably the same fix as https://github.com/django-extensions/django-extensions/pull/644/files

Thanks for reporting the issue ! please test the fix :-)


in CI, don't specify full scala version

makes CI maintenance easier
the sbt files have the full scala versions specified

looks like the build needs full scala versions


ci: update actions, widen version coverage

This is intended to help debug and catch regressions across Node.js versions, as well as making    future major upgrades easier.

Read single-version CI job versions from .nvmrc

Set to currently used version 16

Update all external action versions
Test all supported major Node.js versions in CI

If this seems excessive, proposed alternative: [14.x, 18.x, 20.x] (oldest supported, LTS, newest supported)

@legobeat In 1 or 2 months, jest v30 will be released and it will drop node 14. Maybe we should just drop it too.

Hey there! Since Node 14 is out of the picture, I just removed it. I don't think it's a breaking change because the test-runner uses Storybook 7 and it doesn't support Node 14, so I don't think this ever worked. I changed it to test just with Node 16 and 18 on the basic action and node 20 on the extended action. Thanks a lot for this contribution!


Broken Typescript typings

The default typings that were recently added make supporting apexcharts with Typescript near impossible. Many of the options are not nullable by default (end in a ?). For example, the radar option in plotOptions was added but is not nullable. That means in order for Typescript to not complain, I have to define radar options even if that isn't my intended chart type.
I propose that all options be made optional.

Thank you for the suggestions. Honestly, I have zero experience with Typescript and many of the typings were provided by different users.
I will try to make the "required" typings optional if it is not required. I think, 95% of the typings are not required, so the majority of it will need the ? to be removed.
The only ones which are mandatory are
series
type
A Pull Request is welcome.


DS-3306. Create-administrator CLI

Prints help information and adds error handling for create-administrator cli.
Is now up to date with Apache Commons CLI v. 1.3.1
Fixes #6661

@J4bbi : This seems like something we could easily add into 7.x if you have the chance to port to main.  I also closed & reopened to see if this is still valid for 6.x


Update 1ce.toml for tesntet-15

Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

previous prs merged - https://github.com/anoma/namada-testnets/pull/703


Transfer test cases (Travis CI) of AB4 to Main

Complete adding checkstyle for Main and Test code- Pull requests #242 , #235


DCP - Moving Domain?

Our particle example data moves its domain across time.  I believe the domain should remain static...but maybe not?
To reproduce:

Generate demo particle data with share/examples/generateExampleDCP.py
load the generated .nc files into vapor
Without creating a renderer, animate forward through time.  The domain does not move.
Create a Particle renderer, enable it, and animate.  The domain will slightly move with each timestep.

In the current state of DCP, this is not a bug.  Might revisit later, but rejecting for now.


Imported components report an error if they have a reference to a .css style file

If you are reporting a bug or requesting support, start here:
Bug or support request summary
Please provide issue details here - What did you expect to happen? What happened instead?
Steps to reproduce
Please provide necessary steps for reproduction of this issue. Describe the exact steps a maintainer has to take to make the problem occur. If the problem is non-trivial to reproduce, please link a repository or provide some code snippets.
(A screencast can be useful for visual bugs, but it is not a substitute for a textual description.)
Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/react x.x.x
@storybook/addon-something x.x.x

Affected platforms

If UI related, please indicate browser, OS, and version
If dependency related, please include relevant version numbers
If developer tooling related, please include the platform information

Screenshots / Screencast / Code Snippets (Optional)
// code here

End bug report support request - delete the rest below
If you are creating a issue to track work to be completed, start here:
Work summary
Please provide a description of the work to be completed here - Include some context as to why something needs to be done and link any related tickets.
Where to start
Please list the file(s) a contributor needs to figure out where to start work and include any docs or tutorials that may be applicable.
Acceptance criteria
Please include a checklist of the requirements necessary to close this ticket. The work should be narrowly scoped and limited to a few hours worth by an experienced developer at the most.
Who to contact
Add yourself and/or people who are familiar with the code changes and requirements. These people should be able to review the completed code.
End work issue - please tag this issue with the correct status and type labels

Hey @DonChengCheng, 我自己用Storybook沒有遇到這個错, 你可以提供我們一個重复的例子同你的Storybook版本嗎?

Hey DonChengCheng, I haven't encountered this problem before when using Storybook myself, could you provide us a reproducible example and your storybook version?


Make scripts and shaders embedded in .tscn be more readable and diffable

Operating system or device - Godot version:
Win 7 32 bit Pro; Linux Ubuntu 16.04 64 bit.
Godot 2.1 in both cases.
My project is stored in a Git repo (hosted on Bitbucket).
Issue description (what happened, and what was expected):
The files are saved in a format that (1) doesn't let humans easily study them, nor (2) let automatic diff tools understand them.
Personally I think the .tscn file should be split up into a parent folder and individual files underneath it.
Steps to reproduce:

have a Godot project with GDScript files in it.
make changes.
Expected: to be able to see the individual diffs in a diff tool. Also to be able to ready or edit the file manually easily.
Actual: Things are not diffable because (1) too many things are stored in a single .tscn file; (2) whitespace inside GDScripts are saved as excape characters. So the diffs become entire giant chunks of entire GDScripts.

Link to minimal example project (optional but very welcome):
See screen shot.

Personally I think the .tscn file should be split up into a parent folder and individual files underneath it. Putting the entire scene with all the various GDScripts into one file is poor ux.

So... what are you using a built-in script instead of saving your script to a file? :)

I think .tscn is actually human readable.
I can read files and diffs easily (saving scripts to a separate file).

The only problem TSCN has IMO is this: https://github.com/godotengine/godot/issues/6527
Other than that, I find it human readable and easily diffable.

@akien-mga because that is what Godot does out of the box, maybe? Are you trying to tell me that I have to learn and perform yet another customization of the system to get it to not do things that are actively breaking basic software engineering principles, tools, and habits?
Thanks for the tip, I will try to go learn about it and set it up. Although I believe it is still a bad UX.

Anyway, if this isn't a problem for scripts (as @akien-mga said, since embedding the script in the scene is optional and off by default), it is a also problem for shaders (which get embedded in the same ugly way).
I think I would retitle the issue though, since it currently looks as if diff and cat both crash when they open the file... :laughing:

because that is what Godot does out of the box, maybe? Are you trying to tell me that I have to learn and perform yet another customization of the system to get it to not do things that are actively breaking basic software engineering principles, tools, and habits?

Ah?

I see "Built-In Script" as set to OFF by default personally.

But sure, the code embedded in tscn files could of course be made a bit more readable. But the real solution is still to write your scripts in .gd files and not in .tscn, unless it's just a two-liner shader.

@aiken-mga there is more than one way to create a script in godot. One is as you have shown. The other is clicking on a node in the tree, going down in the list of its properties in the Inspector panel, and seeing the "New GDScript" command.
guess where that puts the new script? :-) :-(

@raould in the scene, as every other resource in Godot that is created from the inspector. And every resource created this way can still be made a file if you click the right arrow on it and click "Save as". But I find myself script addition could get some improvements.

hi,
If there is any way that by default (as in the least number of clicks, the default values for commands or menus along the way) a file is kept inside the tscn file, then that fits what I am talking about.
so i guess the changes i'd like to see are:
(1) make the tscn file not use escapes for whitespace. as i said (buried by now) above in the thread.
(2) there is no #2.
:-)

Right I had forgotten about the way to create a script in the inspector, I never use that. IMO all ways to create a script should default to external files, and only create embedded scripts when users actively request it.

I also use built-in scripts a lot and diffs are useless. (For shaders too.)
I've proposed #7002 to try to improve the state of things.

Closing since #7002 was merged.


Refactoring data store

Refactored code to allow for more extensibility (New tie breakers, new ways of generating rounds, new ways of exporting the files, etc)
Added 5 new tie-breakers: Buchholz, Median Buchholz, Buchholz -1, Buchholz -2 and Cumulative
Changed output and input files to standard YAML to simplify parsing
Added a command line interface as API to run the code
Split steps in four different commands: create-tournament, generate_standings, generate_new_round and process_results
Added unit tests for all elements

I didn't remove your existing generate.py file, just in case you want to still use it.

Fixed all comments


Update CrUX docs

update documentation to clarify initial release offerings and dataset name

Target Live Date: 2017-12-14
R: @petele

Whoops!
There were 2 critical errors that broke the build and prevented it from being automatically deployed.
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
ERRORS
src/content/en/tools/chrome-user-experience-report/getting-started.md - No 'wf_blink_components' found, see https://goo.gl/VXmg9e
src/content/en/tools/chrome-user-experience-report/index.md - No 'wf_blink_components' found, see https://goo.gl/VXmg9e
WARNINGS
src/content/en/tools/chrome-user-experience-report/getting-started.md#L53 - Line must be at most 100 characters
src/content/en/tools/chrome-user-experience-report/getting-started.md#L127 - Line must be at most 100 characters
src/content/en/tools/chrome-user-experience-report/getting-started.md#L284 - Line must be at most 100 characters

@rviscomi - I added {# wf_blink_components: N/A #}, please be sure to run gulp test before submitting your PRs or check the output of the test results from Travis.

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-user-experience-report/getting-started.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-user-experience-report/getting-started.md#L128 - Line must be at most 100 characters
src/content/en/tools/chrome-user-experience-report/getting-started.md#L285 - Line must be at most 100 characters

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-user-experience-report/getting-started.md#L54 - Line must be at most 100 characters
src/content/en/tools/chrome-user-experience-report/getting-started.md#L128 - Line must be at most 100 characters
src/content/en/tools/chrome-user-experience-report/getting-started.md#L285 - Line must be at most 100 characters

@petele ah sorry I assumed that was an unrelated warning, thanks for fixing. I think this is good to merge now (and deploy on 12/14). 🙌


Add critical-section feature.

Depends on https://github.com/rust-embedded/svd2rust/pull/651.

Any reason not to add critical-section to the default features here? In fact I wonder if it shouldn't even be optional in svd2rust for cortex-m targets.
I guess the main question is: if you don't use take() but still have the feature enabled, and don't provide a critical-section impl, do you get a linker error (because it can't find the impl) or not (because the call is optimised out)? If there's no error in that case then I don't think there's any need to even have it as an optional feature; if there is then at least we might consider making it default since the majority of users are likely to need it and it's unlikely a dependency accidentally enables it (same deal as rt).

Yeah, I guess it can be a default feature here since most likely you want to use take rather than steal.
I think it should still stay optional in svd2rust though, mainly because it can be made optional. The PAC crate can then decide if it should be enabled by default.

0.26 is released

@burrbull, thanks, rebased.
@adamgreig, this should be good to go.


fix failing tests on windows

[x] assertion of posix file permissions should not be done on non-posix (aka Windows^^) file system.
[x] replaceText fails with CRLF
[ ] handle path separator \

Yes plz, I don't have Windows, I can't test this kind of thing :-(

I thought it should be enough ? https://github.com/jhipster/jhipster-lite/blob/main/src/test/java/tech/jhipster/lite/common/domain/FileUtilsTest.java#L497-L511
Maybe it's not related to this code ?

you're properly checking that you're on posix before setting execution permission, but the problem is that https://github.com/jhipster/jhipster-lite/blob/deb0d8be2d279ae15483c136b6481db73f6371ac/src/test/java/tech/jhipster/lite/generator/buildtool/maven/application/MavenAssertFiles.java#L29 tries to check that execution permission is set, without checking we're on posix.

https://opencollective.com/generator-jhipster/expenses/61424

@pblanchardie : approved


Import path does not work in v0.3.1?

With recent changes in Ember beta, looks like those imports from README.md don't work any more:
import {
  Checkbox,
  LinkComponent,
  TextArea,
  TextField
} from '@ember/legacy-built-in-components';

The test app itself uses imports like
export { default } from '@ember/legacy-built-in-components/components/checkbox';

The problem comes from the addon/index.js file having this snippet:
export const Checkbox = macroCondition(
  dependencySatisfies('ember-source', '>= 3.27.0-beta.1')
)
  ? Ember._LegacyCheckbox.extend()
  : Ember.Checkbox;

Unless I'm missing something, Ember._Legacy* have been removed in https://github.com/emberjs/ember.js/commit/5d24ae7480aae886d7a526d15332f53fe5b1689c, specifically those lines
// Expose a non-deprecated version for tests and the @ember/legacy-built-in-components addon
Ember[`_Legacy${name}`] = value;

@mixonic @chancancode what do you think would be the right fix here? I'm thinking of two options:

replace README.md import example to (breaking change to addon contract)

export Checkbox from '@ember/legacy-built-in-components/components/checkbox';

Fix code in addon/index.js to be smth like:

macroCondition(dependencySatisfies('ember-source', '>= 3.27.0-beta.1'))
  ? macroCondition(dependencySatisfies('ember-source', '< v4.0.0-beta.9'))
    ? Ember._LegacyCheckbox.extend()
    : importSync('@ember/legacy-built-in-components/components/checkbox')
  : Ember.Checkbox;

Released in v0.4.0


Disable authenticaton

Is there a way to disable the authentication requirement, so that users don't have to login to use the UI?
Maybe having the admin user authenticating once and then disabling it?
If this entailed chats not being saved that would be alright too.

Hi, Thanks for the suggestion! For security reasons, we do not plan on adding an option to remove the login feature in the near future, so I'll close this issue as not planned for now. However, https://github.com/ollama-webui/ollama-webui-lite provides with the option to use the webui without any of the additional backend functionalities (including auth)!

@tjbck I think this is still needed as an option.
A good example of where Ollama Web UI authentication needs to be disabled is when you're already running the application runs behind another internal authentication service such as Authentik / Okta etc...
This is what I (and a few others I know) do with all our apps for a secure and unified approach but with Ollama Web UI this means logging in twice with two sets of credentials - one of which is no centrally managed.

How will you have chat histories and settings then? This method would need a way to pass some sort of authentication header so that WebUI knows which user to log into.

In my case like I suspect a lot of self-hosters, I just have a single user.
However the standard approach with OAuth2/OpenID (which includes things like Google Workspaces, AzureAD, Authentik, Okta, Auth0 etc...) is to pass an identity token / URL / header to applications after successful authentication. You can also have it redirect to a specific URL path (e.g<EMAIL_ADDRESS>etc...

https://goauthentik.io/docs/providers/proxy/header_authentication
https://goauthentik.io/docs/providers/proxy/custom_headers

Hi, can you detail the steps to disable auth please?

Yeah this is really needed, unfortunately this issue remains closed :(

The exact same issue is open here: #929
Again, we want to emphasise that this is a community project, we encourage you to make a PR!

maybe something like https://github.com/open-webui/open-webui/compare/main...sammcj:open-webui:main

This is really cool, I'll check it out thanks @sammcj!

Update @sammcj : Still showing the /auth page :(
I tired removing the route in layout.svelte but it keeps bouncing back to auth...

Ohh security... for f**** sake...
Yes, i get why a login is good for security measures.
But it makes zero sense when running it as a self-hosted service with the intent to just freaking play with ollama.
Somehow so many projects just force down the authentication option where it's clearly intended to be run local for just 1 user (like portainer and grafana, to name a few). And somehow giving the option to disable it is more difficult then to implement an authentication system...

The intent of this whole project is to run locally so authentication has no place in that.
Sorry for the rant.

Blah blah blah yadda yadda yadda

@markg85: https://github.com/ollama-webui/ollama-webui-lite


Feature Plan: support Hexo and Hugo themes

[x] Hexo
[ ] Hugo
[ ] Gatsby

Hugo and Gatsby may be delayed since their template system is much different from Jekyll (Liquid).


PREVIEW FILES WITH QUICK LOOK

Description
So I've been using Quick Look for a while so that I can enjoy the feature of previewing before opening, I've noticed that it works on your software however when you hold the space bar and then release after previewing, it doesn't disappear like the way the built-in Windows explorer does it. Instead, it stays there, so you have to press on the space bar to close it. I'm not sure if it's something that be done on your part or Quick looks part. I'm not sure if this is a bug or a feature to be added in the near future.
Also noticed your thing to copy the File Apps version or windows doesn't copy, checked my clipboard nothing there.
https://github.com/files-community/Files/assets/117542049/42eed681-7c48-4c7f-ada4-9da60f487efe
Steps To Reproduce

Get Quick Look
Go to Windows Explorer
Hold the space bar for it to preview.
Then release when you've seen enough and it'll close itself.
Do the same with the Files App.

Requirements
— Fix Hot key function that occurs when using Quick Look.
Files Version
<IP_ADDRESS>
Windows Version
23H2 - 22631.3447
Log File
debug.log

Thank you for your feedback, we're happy to see you taking advantage of this integration. Can you confirm if it's the same as this report #6620?

It's somewhat close, he's more of an issue, while mine is more of it should work when you are holding the space bar and previewing it then release the Space bar automatically closes the preview.

In any event they both refer to the same request, so I think we can continue tracking in #6620

@SKU003 You can comment on that issue about problem you concern and idea you have there.
For further news, you can click Subscribe in the right side panel of the issue's page.


About the agent updating and initialization

I have two questions about the nice paper "Learn to Augment: Joint Data Augmentation and Network Optimization
for Text Recognition":
1.  In LIne 9 of the Algorithm 1, why the Agent network update towards -S'? I don't understand why -S' is a harder moving state.
2. As for the agent initialization, what is the initialization direction of the 2*(N+1) fiducial points?

Note that S == -S'. The S' decrease the difficulty, so we use S (-S') to update the agent.

The direction is randomly initialized.


Webview unable to load local assets or from CDNs along with window.postMessage not working in iOS release build

[X] Review the documentation: https://facebook.github.io/react-native
[X] Search for existing issues: https://github.com/facebook/react-native/issues
[X] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.5
CPU: x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
Memory: 310.16 MB / 8.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 8.11.1 - /usr/local/bin/node
Yarn: 1.5.1 - /usr/local/bin/yarn
npm: 5.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
Android SDK:
Build Tools: 26.0.3, 27.0.3
API Levels: 26, 27
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
react: 16.4.1 => 16.4.1
react-native: ^0.56.0 => 0.56.0
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
Description
I am using webview to display chart for my app using chartjs and jquery library I am able to view charts fine in iOS debug mode but in release config, all I get is a white screen,  I tried to check if atleast window.postMessage was working using setinterval code in my .html file, but I dont get any response from webview.
To check for window.postMessage I have also tried to possible solution from issue , still its not working
I have tried to inject the complete html code as well instead of serving the html as local asset file, still not success.
This issue is only present in iOS, works perfectly fine for android.

I've got the same problem when trying to render a local HTML file in a WebView. When building an iOS release, I get a blank white screen. It works perfectly fine on the iOS Simulator.
I'm running React Native 0.56. I have another project running 0.55.4 and it this problem does not exist.
I added onLoadStart and onLoadEnd props to check that the WebView had in fact starting to load (at minimum), none of the callbacks were called.
Reproducible:

import content from './index.html';
<WebView
source={content}
scalesPageToFit={Platform.select({
ios: true,
android: false,
})}
startInLoadingState
renderLoading={() => }
/>
The HTML file can contain anything.
It never resolves from startInLoadingState.

I also faced a similar problem and this https://github.com/facebook/react-native/issues/19986#issuecomment-401685826 resolved it. Not sure what the issue is.

@echo8795 Thanks for the update, this is working fine.
But, since I have bit more of the html and i wanted to serve html other JS assets locally, if by some way I could do that it would really be helpful.

@sja1n I think I understand your use case, I had a similar requirement where I was creating a stringified html document for webviews and i had to include js libraries from inside the app bundle. So I added my js and css and font files inside my bundles by adding it /ios and android/app/src/main/assets/_folder_name_.
I then used react-native-fs library to refer the assets folder inside my js.
To include those files inside a webview you first need to provide the path of the assets folder as the baseUrl of the 'source' prop of webview.
`
const RNFS = require( 'react-native-fs' );
let html = getHTMLToDisplay();
let htmlSource = { html: html };
if ( Platform.OS == Constants.Platform.ANDROID ) {
htmlSource.baseUrl = "file:///android_asset";
} else {
htmlSource.baseUrl = RNFS.MainBundlePath;
}
return ( <WebView originWhitelist={[ '*' ]} source={htmlSource} /> )
`
and the html went something like this
`js
function getHTMLToDisplay() {
if ( Platform.OS == Constants.Platform.ANDROID ) {
this.mathQuillJSPath = "file:///android_asset/js/mathquill.js";
} else {
this.mathQuillJSPath = RNFS.MainBundlePath + "/mathquill.js";
}
return '''
<!DOCTYPE html>
	<html>
		<head>
			<style type="text/css">
                                  // For android(ios automatically adds the fonts in bundles to webviews)
                                 @font-face {
				font-family: 'Quicksand';
				src: url("file:///android_asset/fonts/Quicksand.ttf")
			    }
			</style>
			<script type='text/javascript' src='${this.mathQuillJSPath}'></script>
		</head>

		<body>
		</body>
	</html>
''';

}
`

Yeah I think maybe I all I needed was to know how to give proper path for html file in ios, Thanks @echo8795  for the info, I'll definitely try this and update.

@echo8795 the solution in #19986 worked for me when loading local html files in ios

Migrated to https://github.com/react-native-community/react-native-webview/issues/21 and can be closed here.


Shadow Crash

Shadow Crash for Shadow Priests are not being made as a ground macro

Hey @Drixxia is this still an issue? I see you closed it


Allow for better scale dependant styling in vector tiles

Consider the following situation.  Vector Tiles  up to L15 are generated and the features are being displayed via vector renderType.  If a feature is suppose to only show up at level 19 it will be in the level 15 tile and the styling information for the layer will show it as as having a certain (minScale).  The problem is that the style function of the vector source is not being hit when you zoom past level 15 (I'm assuming the style function is the place where you decide whether or not to show the feature).  Therefore we must either show the feature at L15 and below or not show it at all

For now, you have to configure your ol.layer.VectorTile instance with renderMode: 'vector' to get the desired result.
In the future, pre-rendered images will be generated for all zoom levels - even those that are not provided by the source.

I'm not sure this solves the issue.  The issue is that I have features that are only suppose to be shown at L17, L18, and L19.  My tiles only go from 0-15.  The features are in the L15 tile.  So far so good.
The layer has a minzoom=17 so my thought here is to limit the extent of the feature in the style function.  Here I can check the resolution and decide whether or not the map is at the correct scale to display the feature.  So at L15 the style function determines not to show this feature.  However, the style function doesn't get hit again when I zoom down to L16 or L17 or deeper,
Is there another way where I can achieve what i want?

By the way, renderMode is already set to vector.

@cmortazavi What you are seeing is another issue that will be fixed with the planned improvements.

Oh ok I see.  Thank you.  We could greatly benefit from this improvement.


Add an interceptor to support AuthenticationManagerResolver

This proposal introduces the AuthenticationManagerResolver<GrpcServerRequest> to Spring's gRPC authentication framework. This provides a flexible mechanism for implementing dynamic authentication based on your specific needs.
The Problem:

Traditional Spring gRPC authentication relies on fixed configuration of authentication providers, limiting flexibility.
Changing authentication mechanisms requires code modifications and redeployments.

The Solution:

Introduce AuthenticationManagerResolver:

Allows dynamic selection of the AuthenticationManager based on the gRPC request.
Enables fine-grained control over authentication based on request headers, payload, or other criteria.

Nice suggestion, I'm currently quite busy so I might be slow to respond.

We moved some files. Could you please fix the merge conflicts?

I haven't tested this myself and I'm unsure about the change in condition regarding when the security config is enabled.
Other than that, it looks good to me.

If on of the interceptors condition met, then it will be registered. On the other hand if both conditions met then the first one will be registered according to the priority.
According to existing GrpcServerSecurityAutoConfiguration Conditions, if GrpcAuthenticationReader is not registered, I think it will probably encounter error. So all the configuration depends on GrpcAuthenticationReader.
If you have any other situation to consider, please let me know.


Async don't reload templates + static

Description
Make async reloading much more efficient by only reloading Python files. No template/static file should be reloaded. Fixes #3093 (doesn't implement what was proposed but the general idea is done)
Checklist:

[X] I've made sure that tests/test_cookiecutter_generation.py is updated accordingly (especially if adding or updating a template option)
[X] I've updated the documentation or confirm that my change doesn't require any updates

Rationale
Watchgod doesn't need to check HTML, CSS, JS etc. files. Like the Django statreloader, we only need to reload the Python files. These other files are automatically changed because Django is just loading files. This makes fixing HTML, CSS, and JS files much faster to fix since you don't have to wait for the server to finish reloading.

Latest uvicorn has a CLI option for excluding. Closing.