asyncio RuntimeError stacktrace in SlackResponse, when getting paginated responses

Description
I'm trying to get paginated responses in users_list, by providing cursor and limit, but I'm getting a RuntimeError when doing so, because there's no existing asyncio loop in the thread:
https://github.com/slackapi/python-slackclient/blob/e06b4d7b415aac439ec9d5456ef756aaed4083e9/slack/web/slack_response.py#L135
Applying the same pattern that base client uses for getting an event loop fixes the issue:
https://github.com/slackapi/python-slackclient/blob/e06b4d7b415aac439ec9d5456ef756aaed4083e9/slack/web/base_client.py#L49-L56
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 2.5.0
python version: 3.x
OS version(s): Ubuntu bionic
Steps to reproduce:

Try to get a paginated response without generating an event loop (my code doesn't use asyncio)
Try to get a paginated response
Get a stacktrace

Expected result:
I expect to get paginated results.
Actual result:
I get a RuntimeError

Relevant part of the stacktrace:
  File "/srv/service_venv_python3.6/lib/python3.6/site-packages/slack/web/client.py", line 1615, in users_list
    return self.api_call("users.list", http_verb="GET", params=kwargs)
  File "/srv/service_venv_python3.6/lib/python3.6/site-packages/slack/web/base_client.py", line 171, in api_call
    return self._event_loop.run_until_complete(future)
  File "/usr/lib/python3.6/asyncio/base_events.py", line 454, in run_until_complete
    self.run_forever()
  File "/usr/lib/python3.6/asyncio/base_events.py", line 408, in run_forever
    raise RuntimeError('This event loop is already running')
RuntimeError: This event loop is already running

Hi @ryan-lane, thanks for taking the time to research and write this up.
I've tried reproducing the issue as you describe but the code seems to work as expected for me. Here is what I have:
import os
from slack import WebClient

token = os.environ.get("SLACK_BOT_TOKEN")
client = WebClient(token=token)

# Making a paginated Web API request
# Using a really low limit to artificially create the need for more than one request
for page in client.conversations_list(limit=5):
    print(page)

Note that I don't have asyncio or any event loops in my program. In a workspace with about 100 conversations, it paginated through the entire set as expected.
Looking a little closer at your error, it seems like the problem isn't about asyncio.get_event_loop() failing because there's no event loop running (in fact, the documentation says calling this function would just create one in that condition). Instead, it seems like your program has an event loop running: RuntimeError: This event loop is already running. Can you check this out?
This is still a bug we need to solve, but I'm trying to collect a little more information so we can come up with a good solution. I'm looking at your PR (#632) and I'm not quite sure if and how it fixes the problem. The call to get_event_loop() is not the one that throws the RuntimeError in your example - it's run_until_complete(future) that throws. As far as I can tell, with that patch applied the get_event_loop() method would just return your existing event loop and the except clause would never run. Therefore we'd be back in the same place.

Let me close this issue now as #662 resolved it.

👋 slackclient 2.6.0rc1 is out. The pre-release version contains fixes for your issue described here.
https://pypi.org/project/slackclient/2.6.0rc1/
One week later from now, we'll be releasing version 2.6.0 to PyPI.
If you have a chance, could you try the release candidate version out and let us know your feedback? Thank you very much for being patient with this issue.


Bump version number

The current stable version of selectrum has a slowdown issue when combined with marginalia. It has been fixed in development builds of selectrum, so an bump in version would be nice.

@clemera Feel free to take over the release process of Selectrum, if you like. As I've mentioned before, I make releases of all my packages every few months, but due to the active development happening on Selectrum it would probably be more appropriate to make more frequent releases. The process is simply:

create a commit updating the version numbers (I have been trying to follow semver)
publish a tag with the new version number
paste the relevant section of the changelog into the release, and delete some newlines so that it renders correctly (I just use M-^ and atomic-chrome; there's probably a smarter workflow)

Sometimes if I want to release only a subset of commits (because I think the more recent ones are not stable enough), I branch off a past commit to create the version number bumping commit, put the tag there, and then merge the new commit into master. It can be a little annoying to deal with merge conflicts in the changelog, but it has never been too bad.

@clemera Feel free to take over the release process of Selectrum, if you like. As I've mentioned before, I make releases of all my packages every few months, but due to the active development happening on Selectrum it would probably be more appropriate to make more frequent releases. The process is simply:

create a commit updating the version numbers (I have been trying to follow semver)
publish a tag with the new version number
paste the relevant section of the changelog into the release, and delete some newlines so that it renders correctly (I just use M-^ and atomic-chrome; there's probably a smarter workflow)

Sometimes if I want to release only a subset of commits (because I think the more recent ones are not stable enough), I branch off a past commit to create the version number bumping commit, put the tag there, and then merge the new commit into master. It can be a little annoying to deal with merge conflicts in the changelog, but it has never been too bad.

Sorry, it took a little while but 3.1 is published now.

It is a release with many significant changes and improvements. Great work, @clemera!

@minad Thank you also for your contributions, great help and discussions!


Cannot get push notification from Apple -Invalid Token ID

Hello there,
I am having some issues with the push notification. I have installed an app called ClickMobile through phonegap framework. It is a non-public app, only available to the partners of that software. Basically it schedules tasks to technicians and the technicians can send messages to the scheduler (very high level).
All the installations were done correctly and the app is actually working fine on iPad. It is able to communicate with the server as the tasks and messages can be recieved on iPad with alert when it is open but the push features is not working properly.
I did follow this guide: https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AddingCapabilities/AddingCapabilities.html#//apple_ref/doc/uid/TP40012582-CH26-SW6
I am only doing adhoc distribution, the APNs certificates were created for the developement environment. All the server ports are open thus it is not a security issue.
I have also run test on the .p12 file with PushSharp tool and I get error saying that the token id is invalid but as per the database, it is the correct one.
I have redone the excercises many times and the result is still the same. If someone can help me, it will be great.
Thanks,
Hemadri

Sorry to be a jerk but I'm now closing issues that don't follow the issue submission guidelines. This plugin takes a lot of work to maintain and I can't afford the time required to solicit the required info from everyone.
I'm closing this issue but please feel free to re-open the issue if you provide the requested details from the new issue submission guidelines.
https://github.com/phonegap/phonegap-plugin-push/blob/master/.github/ISSUE_TEMPLATE.md


Attempt to update to latest biny and newer gradle, loom, and StationAPI (alpha.3)

EDIT: Fixed the branch not working on StationAPI alpha.2.4, I redid my mappings migration and everything seems to work now

PR is ready. I finished the migration to StationAPI alpha.3


Github to FB sync

CI related change + update velox submodule

Landed as https://github.com/facebookresearch/torcharrow/commit/f8747bc26cfaba59db62a24c2885a2744c3ee1ff


Enhance Resource Constraints Validation Policy to Include InitContainers

Signed-off-by: nikhilmaheshwari24<EMAIL_ADDRESS>Related issue
https://github.com/kyverno/policies/issues/951

Proposed Changes
This PR updates the existing Kyverno policy to validate CPU and memory resource requests and limits for both containers and initContainers within Pods. This enhancement ensures comprehensive resource management across all container types in a Kubernetes cluster.

Checklist

[x] I have read the contributing guidelines.
[x] I have inspected the website preview for accuracy.
[x] I have signed off on my issue.

Hi, @realshuting
Please review & help with your approval. TIA

Done ✅ @realshuting

Is #951 relevant?

My bad. I have updated the comment.

@realshuting, @nikhilmaheshwari24:  changes should not have been made here as these Markdown files are rendered from the contents of the policy library (kyverno/policies). We run a rendering program to then convert to Markdown. These changes will be wiped unless the corresponding policies in the library are updated.

The changes made are also incorrect as without conditionals it will cause all Pods to fail if they don't have initContainers or ephemeralContainers.

changes should not have been made here as these Markdown files are rendered from the contents of the policy library (kyverno/policies). We run a rendering program to then convert to Markdown. These changes will be wiped unless the corresponding policies in the library are updated.
@chipzoller,

Should I revert the PR changes and raise a new PR in kyverno/policies to update the corresponding policy in the library?
Or should I fix the changes here as well and raise a new PR in kyverno/policies to update the corresponding policy in the library?

Policy Path - https://github.com/kyverno/policies/blob/main/best-practices/require-pod-requests-limits/require-pod-requests-limits.yaml

I'd just open the PR on kyverno/policies. We'll render policies for the website and pick up those changes.

If you haven't raised the PR, let me do it, I want to contribute.

@realshuting, @nikhilmaheshwari24: changes should not have been made here as these Markdown files are rendered from the contents of the policy library (kyverno/policies). We run a rendering program to then convert to Markdown. These changes will be wiped unless the corresponding policies in the library are updated.

I was not aware of that, thanks for pointing it out.
@nikhilmaheshwari24 - let's open a PR in kyverno/policies with the revised policy, thanks.

@realshuting - PR https://github.com/kyverno/policies/pull/1103


ControllerButtonHints not working for Oculus Touch (except Trigger and Grip)

Hello,
in my application the ControllerButtonHints script only works for the Trigger and Grip Button of Oculus Touch controllers? Is this a known issue or am I doing something wrong?
If there is a workaround to get the ControllerButtonHints script working for all Oculus Touch buttons i would appreciate the help.
I am using the latest Unity plugin 2.2.0.
Regards

@kisak-valve can you move this to the openvr repo?
Note for openvr repo people: This is likely an issue with GetOriginLocalizedName not returning correctly for oculus bindings.


Add warning if using both rotation and setting dataset_timestamp

Description
log rotation doesn't use a passed in dataset_timestamp, add warning to help identify the pitfall. Mitigation fix for #441
General Checklist

[ ] Tests added for this feature/bug
if it was a bug, test must cover it.
[ ] Conform by the style guides, by using formatter
[ ] Documentation updated
[ ] (optional) Please add a label to your PR

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.666%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/whylogs/app/logger.py
1
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
4967

Relevant Lines:
5844

💛  - Coveralls


Beacon Location font size issue V0.69

I think I may have accidentally stumbled upon a bug.  I believe what I did was mistakenly held the S1 button on my TTGO T display on the Beacon/Locations page.  Since then the font size has been larger.  No button presses seem to fix it, I have tried re-uploading to my board with no change. I uploaded an older version of the toolbox. (V0.60) and the font went back to smaller. Uploaded the V0.69 to it again and the problem returned.  I have even selected "erase all flash" during the uploads with no fix.  I did find that if I changed to a different font the size would go back to normal, but as soon as I went back to the original font the fault would return.
Fault occurred while using the basic font.

Could you tell me what version of the Arduino IDE you're using and what version of the TFT_eSPI library you have installed?
When you say the fault would return, would the font immediately become larger as soon as the TTGO powered up or do you mean that you were able to retrigger the bug on the Beacon/Locations page?
Thanks

Sure. I am running Arduino IDE 1.8.10, I know it's old I've just been sticking with what I know. From what I can tell I'm running TFT_eSPI V2.5.0.
What I'm meaning is the font is only larger on the Beacon/Locations page and no matter what I do (without even attempting to duplicate what I did to make the fault happen) when I open the Beacon/Locations page up again it is already in larger font, unless I run the older toolbox version or change the font type on the first page say to something like Aurebesh_English.

Maybe the font was always bigger on the Beacon/Location screen to begin with?
I went through the code and decided to change line 850 to "lists[LIST_LOCATIONS].render_options.text_size              = MENU_SELECT_TEXT_SIZE - 1;" and now it appears to be showing up in a font that correctly fits the screen.  I could have sworn though that it was this way when I was using the toolbox earlier today.
I have even removed the " - 1" from that line and re-uploaded and the font returned to larger with the font just overrunning the screen, with the "M" and the "e" about 1/3rd off screen on the Beacon/Location page .
I have even used Notepad++'s compare tool to compare my .ino copy with a fresh copy from the Github and the only difference between them is where I added my droids name and address and now the " - 1" i just added.
IDK if this is just a work around for the issue I am having or an issue maybe someone will see but it is working now.
Thanks for your help, and thanks for creating this toolbox and all the other things you have done!  I enjoy all the information you share and videos you create!
I will leave this as open in case you find a different/better solution to this issue.

This is a bug I introduced when I reworked how fonts are displayed when I introduced custom fonts. I merged the font menu settings I was using for the beacon menus with the other menus. I tested with a T-Display-S3, but not a T-Display and missed this. I've updated the code to resolve the issue and published release v0.70.
When you have a chance, can you try the new code and tell me if it works for you?
Thanks

Thanks for fixing it!  I have uploaded V0.70 to my T-display and it is working flawlessly.
Thank you so much for the fix!!

I also tested and did not see the issueSent from my iPhoneOn Jan 31, 2024, at 3:50 PM, Knucklebuster620 @.***> wrote:
Closed #3 as completed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Command Finished event

Command received is always emitted when there is an incoming one. This would be the "counter" event. However with both command executed and command failed it feels like an overkill.

What would be the situation if the command failed AND the exception is not caught?

If the command failed and the exception wasn't caught, it would bubble up and either be caught by the app's error handling (very common scenario) or it would just crash the script (which could also be intended behavior).
If your question is: should we ditch one or both of CommandExecuted/CommandFailed, I think it's worth keeping them since they target different use cases. Someone might want to push them out to separate logs or collecting stats on successes vs failures. It'd be tricky to accomplish either without having both events.

Yeah, I ended up with the same thoughts.


fix License link

The License link was wrong (not our LICENSE but official one)
https://go.microsoft.com/fwlink/?linkid=2028464
Fabio told me.

is this the license file of the assembly?
is it ok that the assembly and the github repo have different license files?
do the other extension repos have LICENSE files?

Hi @ryancrawcour  Sorry, it is lack of explanation.
As you find, the original license file is out of link. So I refer the SingalR repo. They make it their own LICENSE file.  I talk about it to the Fabio. He said that references the LICENSE file is wrong, he said that the eventgrid repo is just forget to update. and he said please follow the practice of web-jobs-sdk. Now you are looking at the same license file of the web-jobs-sdk.

Right, I was under the impression all MSFT OSS projects are released under MIT, and a LICENSE & CONTRIBUTION file must be in the repo.
The license url points to a different .NET license, not the MIT license which i understood we should use for MSFT OSS projects.
Refer to https://docs.opensource.microsoft.com/policies/release.html
License
All Microsoft open source code must be released under the MIT license. Where we are participating in existing community that does not use the MIT license, work with your business and legal contacts to determine the appropriate license. Our intention is to fit in with the existing community. We just need to confirm that the terms work for the business.
So i guess this gives us some flexibility to use a different license.
@fabiocav, how should we proceed?

Whatever we do, the license file in the repo should match the license file on the NuGet package.

Hi @fabiocav Could you answer @ryancrawcour 's question?

Hi @ryancrawcour  Sorry for late reply. I ask fabio why it happens.

Yes, that question has come up in the past and there was a reason for that. If I remember correctly, it was fine to apply that license file to the NuGet, and the LICENSE file in the repo applies to the Code, as opposed to the product
Essentially, that was the clarification we received and why things are currently setup that way.

I researched the repo web-jobs-sdk and it is the same structure.
https://github.com/Azure/azure-webjobs-sdk


"Content-length" for everest_update.yaml in http header

Hi, I'm trying to write a script to download celeste mod.
Thanks for your "everest_update.yaml", I can process mod dependencies.
But I didn't find "Content-length" in everest_update.yaml download response, it may useful to add "Content-length" to help check download is real complete ?

All APIs should now return a Content-Length (well, except the bundle-download one because the zip is written on the fly 😅)

Thank you very much ! 😄


MinimizeIntegerVariableWithLinearScan failure

I'm not sure if my usage is correct but when I attempt to use this method I get a failure:
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call

It seems that the solver is attempting to iterate over a list of heuristics which hasn't been populated.
The error is in on the function invokation on line 74 of integer_search.cc in the SequentialSearch method.
When I use MinimizeIntegerVariableWithLinearScanAndLazyEncoding and provide a "NextDecision" function, the solver runs as expected. I'm using default sat parameters.
I suppose my question is: what is the correct usage of this entry point to the solver? It currently isn't obvious how to load heuristics if they are required by this call into the solver and I couldn't find a sensible way to load heuristics to the solver through the model.Add api. I'm hoping this is a documentation issue it seems likely that it could be a bug.

Thanks for the response. I was getting acquainted with the new functionality that you've been building up on the SAT side so I was simply testing basic functions and doing some performance profiling.
I think what's perhaps a bit counter-intuitive to your audience (just based on the questions I've been seeing on the forums) is how the cp_model relates to SAT. So when you say "support static heuristics in the cp_model" - do you actually mean using the grammar of the cp framework you can access certain heuristics into a SAT model?
If this is the case, that would then answer my question on how to add heuristics into the SAT layer. I know this is very rude of me to ask, but perhaps a diagram explaining how the pieces of or-tools are currently related to one another, with the objects that are being used to switch between projections, might be a nice addition to the online introduction to or-tools?

Hi Laurent,
Thanks for the link and reply. I'll dig up the example I was working with at the time - I recall it just felt like an edge case that hadn't been handled (the edge case potentially being my usage too!).
But from what you're saying one should ideally steer away from using the SAT layer directly and rather go through the cp_model. I'll revert this week with a concrete example. :+1:

Yes, the direct SAT layer is not recommended.
The only usage we have is for very small online problems, where you have a few ms of time limit.
In that case, the setup of the cp_model API is killing you (copy, presolve, ...).
For any other usage, we recommend the cp_model API as it is simpler, and in fact faster, thanks to presolve, potential parallelism...

I will close this issue now.
Open a new one if you have new issues.


[Issue] Bump up geospatial version from 2.3 to 2.4 in cypress-workflow

Bump up geospatial version from 2.3 to 2.4 in cypress-workflow when 2.4 branch is cut for geospaital repo.
https://github.com/opensearch-project/dashboards-maps/blob/2.x/.github/workflows/cypress-workflow.yml#L33

There are other places where we still use 2.3 version for OS and OSD as 2.4 is not ready yet. We need to update them accordingly later.


Add preview ability.

Would be brilliant if it could render .GEDCOM files too.

I am planning to look at updating this plugin to support a language server for GEDCOM 7.0 specification. This in turn will allow rendering. No timeline just yet. Any contribution is very much welcome !


The application crashes when accessing the Rate/Vote giver list

Expected behavior
I should be able to access the Rate / Vote grantor list feature without experiencing a crash
Actual behavior
When I try to see the list of Giver Rate / Vote in one of the posts, suddenly the application crashes and exits by itself.
How to reproduce

Install and open the application
Login
Next, go to the Feed page
And click on the Giver Rate / Vote list in one of the posts.

Then you will find problems like mine.
Recording Of The Bug
https://youtu.be/634G_WfetDo
Logcat
03-03 19:08:25.900 21983 21983 E AndroidRuntime: FATAL EXCEPTION: main
03-03 19:08:25.900 21983 21983 E AndroidRuntime: Process: com.hapramp, PID: 21983
03-03 19:08:25.900 21983 21983 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.hapramp/com.hapramp.ui.activity.VotersListActivity}: java.lang.NumberFormatException: Invalid double: "0,002"
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2449)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2509)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.ActivityThread.access$1000(ActivityThread.java:153)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1373)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:5527)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:629)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: Caused by: java.lang.NumberFormatException: Invalid double: "0,002"
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at java.lang.StringToReal.invalidReal(StringToReal.java:63)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at java.lang.StringToReal.initialParse(StringToReal.java:164)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at java.lang.StringToReal.parseDouble(StringToReal.java:282)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at java.lang.Double.parseDouble(Double.java:301)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at com.hapramp.ui.activity.VotersListActivity.a(Unknown Source)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at com.hapramp.ui.activity.VotersListActivity.m(Unknown Source)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at com.hapramp.ui.activity.VotersListActivity.onCreate(Unknown Source)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.Activity.performCreate(Activity.java:6303)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1108)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2402)
03-03 19:08:25.900 21983 21983 E AndroidRuntime: 	... 9 more

Environment
Tested on 2 devices:

DeviceAndroid Version

Xiaomi Redmi 4XMarshmallow, 6.0.1 mmb29m (CPU: Octa-core Max 1.9 GHz, RAM: 2 GB)
Xiaomi Redmi Note 4Marshmallow, 6.0 mRA58K (DECA-CORE MAX 2,11GHz, RAM: 3 gb)

@ahyar92
Thanks for reporting the issue.
We regret the inconvenience.
FYI, let me clarify the reason.
App assumes all the vote values to be in x.xxxx (Dot is used) Format.
But the data received was in x,xxx (Comma is used) Format.
This issue will be with only few posts.
We will resolve the issue in the very next update. 😊

Nice to help you guys :)

@ahyar92
Since this is an issue due to the locale of the user, we would request you to verify whether the issue persists in the new apk with a patch or not.
Find the apk at: https://drive.google.com/file/d/11Wlzzyqd9P-p5AertNDTw6RKhG7wMFF-/view?usp=sharing

@bxute Hi, the problem has been solved :)
By the way, after I searched further, it turned out that the crash only happened if my smartphone was in a language other than English. When I change the settings of my smartphone into English, everything is fine.


Add new Phone number based authentication backend?

Description
Build on top of Django Allauth, a mobile-based authentication backend starting with Twilio.
Rationale
Everyone has mobiles these days and a whole lot more people in developing countries own phones than desktops. For such mobile users, a Phone number is the only thing they have in common. Most don't have emails and probably will never have one. The only way to reach such people would be to create a Phone number based authentication backend.
Use case(s) / visualization(s)
A person who wants to login into a mobile website can simply receive a One Time Password on their phone number and once they enter it correctly they get signed up and an associated user is created for them in the backend.

I completely agree, @arnav13081994. This consideration will definitely be in my next project build. Thanks for the issue.

I'm glad to hear that. I'll try to hack Django All auth's backend and see if I can add phone number as another authentication method.
A dirty way would be to create another model "Phone number" and link it to the users model and basically, whenever the user enters their number to log in, the backend actually gets their email or username and uses that to autheticate?
This way I'm guessing all existing functionality of All Auth can be preserved and shouldn't be a lot of work either.
What do you think @Afrowave?

 What happens now is that the phone is either used for 2FA or it is the only way to authenticate by SMS.
It would be an interesting addition to Django All Auth. I still have not figured out proper configuration with the current Facebook.

Ah, I see. I didn't think about 2FA. Good point.

Perhaps considering django-allauth-2fa?
https://github.com/valohai/django-allauth-2fa


Fix misc. Github Action warning

Summary
Some of the the referenced actions are already quite outdated and cause a lot of warnings emmited if you check the workflow runs:

bump actions/cache
Fixes:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

replace set-output with GITHUB_OUTPUT
Fixes:

The set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

bump codecov/codecov-action
Fixes

`The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

I checked the workflow and upload works, see https://github.com/PHP-Open-Source-Saver/jwt-auth/actions/runs/7986070882/job/21805731559?pr=232#step:11:50

bump actions/checkout
Fixes

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Notes

About the php-cs-fixer commit: this is unrelated to my changes, it simply wasn't run in a long time and php-cs-fixer evolved and therefore applies these changes.
They are still warnings emmited, but they're of different nature:

@mfn looks very good/nice to me. If you feel good about it I can merge it this weekend.
Thanks :)


Threard and quene for sendMessage?

Hello, tell me, please. How sendMessage worked? If I understand that is simple api_request without consist quene and second thread? It's correct?

Correct.

Do you have any reasons? Why was this not done yet?

What do you mean? sendMessage is there for you to use.

I mean why the queue and the separate thread for sending messages have not been done. Do you have any reasons, why was this not done yet?


Sparkfun & Waveshare configs: Add missing reverse defines

I was compiling firmware for my Pro Micro RP2040 & Waveshare Zero boards and these missing defines were causing the builds to fail. I assume its related to https://github.com/OpenStickFoundation/GP2040-CE/pull/101

Thank you for these!


UX

"Back" and "Next" button also at the bottom of the page
"Attitude générale", "Contact avec autrui", etc.. fixed at the top (so we can always know which section we are in)

closed by 94d33282c7fa9c9c9ec8e5787671153c4d5bc390


Upload database with commit SHA and branch name

Would it be possible to extend the CodeQL database upload/download API to contain the commit sha and branch name?
Having a database but not knowing which source code version it is belonging too, is not very useful.
This is code from src/database-upload.ts. Perfect place to pass the SHA and branch.
        `POST https://uploads.github.com/repos/:owner/:repo/code-scanning/codeql/databases/:language?name=:name`,
        {
          owner: repositoryNwo.owner,
          repo: repositoryNwo.repo,
          language,
          name: `${language}-database`,
          data: payload,
          headers: {
            authorization: `token ${apiDetails.auth}`,
            "Content-Type": "application/zip",
          },
        }

When calling the database list API:
https://api.github.com/repos/{repository full name}/code-scanning/codeql/databases
It would be nice to see the branch name and commit sha in the response.
[
{
    "id": 11071980,
    "name": "javascript-database",
    "language": "javascript",
    "uploader": {
            --- REMOVED TO REDUCE COMPLEXITY ---
    },
    "content_type": "application/zip",
    "size": 5680496,
    "created_at": "2022-11-28T14:19:59Z",
    "updated_at": "2022-11-28T14:19:59Z",
    "url": "https://api.github.com/repositories/553492177/code-scanning/codeql/databases/javascript"
  }
]

Thanks for your feedback. I think this information is already available, though perhaps not quite in an easily accessible format:

The SHA that the database was created from is available in the codeql-database.yml file inside the downloaded database in the creationMetadata.sha property.
The branch is always the repositories default branch.

Is this the information you are looking for? We can do better at exposing this information and we are discussing internally.

@aeisenberg, thank you for your response.

Ok, that is good to know, but it is forcing me to download the DB first and unzip it. Which is a bit cumbersome

I know that the branch SHOULD be always the default, but it's not a hard requirement, right? Nothing prevents the caller of the API to upload database from user branch, right?

It would be cool, if you could expose this information in the API response. We are working on some integration service and being able to quickly tell if the database contains same or different version of the source, would be extremely helpful.

Something to clarify here. The upload database request is not public API and is restricted to the default branch. We have no intention of changing that. The list databases request is public API and you will receive at most one database per language. When newer databases are uploaded for a language, the older one is no longer available.

@aeisenberg, it's good that only default branch can be upload but, I see the following check in src/database-upload.ts
  if (!(await actionsUtil.isAnalyzingDefaultBranch())) {
    // We only want to upload a database if we are analyzing the default branch.
    logger.debug("Not analyzing default branch. Skipping upload.");
    return;
  }

It looks like it is not the API restricting the user branch upload.
I know that only one database per language can be uploaded and I really like it.
But I still can't tell if the database changed from the API response. The created_at field will be different, but that doesn't mean the source code inside is different.
We have GitHubApp that checks for CodeQL databases and downloads them into our internal archive. Right now, it's hard to tell from the API response, if the database changed. Unless I download it and check the creationMetadata.sha

It looks like it is not the API restricting the user branch upload.

This is an internal, undocumented request. You should not be explicitly calling this request. I know the server side does some checking on the request data, but I am not sure exactly to what extent it checks.
Are you downloading databases from third party repos and concerned that they may be calling this API in the wrong way?

But I still can't tell if the database changed from the API response. The created_at field will be different, but that doesn't mean the source code inside is different.

We're discussing internally.

@aeisenberg, you are correct. We are downloading databases from accounts/repos in our Enterprise github. Basically, creating archive of databases. In case of security incident, we can easily query all of the databases for a specific code pattern.
The branch is not a big concern. The commit sha in the API response would be really nice, thou...

The commit SHA is now part of the API response, when getting CodeQL databases! Every database who is newly created will have the SHA. It will take some time until older databases - for which we hadn't stored the commit SHA - will be replaced by newer builds that include the SHA.

The codeql version used to create the database is available in the codeql-database.yml file. Is this sufficient for your purposes?


FirebaseApp has to define a valid projectId

Please include the following information for better support
The more context you provide around this issue the faster the community can help you
Did you follow all the instructions as specified in the Twilio Quickstart repositories? Yes
What version of React Native are you running? 0.61.2
What version of react-native-twilio-programmable-voice are you running? 3.21.3
What device are you using? (e.g iOS10 simulator, Android 7 device)? Simulator and Device
Is your app running in foreground, background or not running? foreground
Is there any relevant message in the log? Yes
If using iOS, which pod version are you using? N/A
Step to reproduce
Use TwilioVoice.initWithToken(token)
Advanced:
Have you tried adding break point using AndroidStudio or XCode and analyse the logs? Yes
can share a project with issue? No
Did you try to reinstall the pods completely? N/A
Everything was working for me before, but suddenly my app crashes once it gets toTwilioVoice.initWithToken(token). Here's what I get:

03-30 20:43:22.776  7622  7775 D RNTwilioVoice: initWithAccessToken ACTION_FCM_TOKEN
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: Exception in native call
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: java.lang.IllegalArgumentException: FirebaseApp has to define a valid projectId.
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.google.android.gms.common.internal.Preconditions.checkNotEmpty(Unknown Source:8)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.google.firebase.iid.FirebaseInstanceId.zza(com.google.firebase:firebase-iid@@20.1.4:51)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.google.firebase.iid.FirebaseInstanceId.getToken(com.google.firebase:firebase-iid@@20.1.4:87)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.hoxfon.react.RNTwilioVoice.TwilioVoiceModule.registerForCallInvites(TwilioVoiceModule.java:543)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.hoxfon.react.RNTwilioVoice.TwilioVoiceModule.initWithAccessToken(TwilioVoiceModule.java:507)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at java.lang.reflect.Method.invoke(Native Method)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:371)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:150)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at android.os.Handler.handleCallback(Handler.java:873)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at android.os.Handler.dispatchMessage(Handler.java:99)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at android.os.Looper.loop(Looper.java:193)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225)
03-30 20:43:22.782  7622  7775 E unknown:ReactNative: 	at java.lang.Thread.run(Thread.java:764)

Could this be because of a dependency update? I see com.google.firebase:firebase-iid@@20.1.4, but I don't believe that's been officially released. Any help would be greatly appreciated. This started happening today.

Here's a list of updates from just yesterday: https://firebase.google.com/support/release-notes/android#2020-03-30
This one specifically: https://firebase.google.com/support/release-notes/android#iid_v20-1-3

FirebaseApp now requires a non-empty project ID set in the corresponding FirebaseOptions.

It looks like this is causing the error.

Never mind. Fixed this by adding force = true in my build.gradle for firebase-messaging. Closing.


Add support for exporting AWS/Athena metrics

This adds support for exporting AWS/Athena prometheus metrics,
example configuration is as below:
discovery:
  jobs:
    - type: athena
      regions:
        - eu-central-1
      searchTags:
        - key: project
      enableMetricData: true
      metrics:
        - name: TotalExecutionTime
          statistics:
            - Sum
          period: 300
          length: 3600
        - name: EngineExecutionTime
          statistics:
            - Sum
          period: 300
          length: 3600
        - name: ProcessedBytes
          statistics:
            - Sum
          period: 300
          length: 3600
        - name: QueryPlanningTime
          statistics:
            - Sum
          period: 300
          length: 3600
        - name: QueryQueueTime
          statistics:
            - Sum
          period: 300
          length: 3600
        - name: ServiceProcessingTime
          statistics:
            - Sum
          period: 300
          length: 3600
        - name: TotalExecutionTime
          statistics:
            - Sum
          period: 300
          length: 3600

Thanks a lot :)


issue#12064: fix html escaping bug

bugfix for this issue12064

htmlentities doc : http://php.net/manual/en/function.htmlentities.php
before bugfix, code {{ "
<br>" }} in the view will be displayed as

.
after bugfix, code {{ "
<br>" }} in the view will be displayed as
<br>.

Is this not a breaking change?

Also, surely we set that parameter on purpose @taylorotwell?

You can define your own escaping function if you want to change the behavior.

Yes, this is breaking change.  @GrahamCampbell

Yes, this is breaking change. @GrahamCampbell

For that reason it cannot be merged.

I hope this gets fixed before 6.0, otherwise it would be a shame.


Switch to ReScript Apollo Client

[ ] switch repo name to reasonml-community/res-apollo-client

We're actually going with rescript-apollo-client and there's nothing actually useful on this branch so I'm gonna close this and just start fresh


⚠ ClamAV has degraded performance

In 9d015b5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 556 ms

Resolved: ClamAV performance has improved in bfe9157 after 5 minutes.


UTM Tracking

This is a simple utm tracking solution that requires no dependencies.

Only thing missing here is test cases. If you like the premise, I can write test cases in.

Wrote test cases. Not sure why that one is failing, it passes locally.


Scan containers running in K8s?

Short description
I was trying to scan the docker container running in K8s cluster.
How do I make sure dagda scans the images running on my cluster nodes without supplying container ids?

At the moment, Dagda only scans docker images and containers on a host thanks to the docker socket but if you want to contribute to this integration, it will be wonderful news.


Error downloading the board manager package in Arduino IDE 1.8.19

Hi there,
Following the instructions I fail at the point of searching in the board manager for the stm32duino as the following error occurs:
Error downloading https://github.com/stm32duino/BoardManagerFiles/raw/master/package_stmicroelectronics_index.json
Error downloading https://downloads.arduino.cc/packages/package_index.json
I made sure I don't have any proxy connection.
I would appreciate to receive help if the problem lies on my version of the Arduino IDE 1.8.19 or is a problem of other origin.
Thanks in advance.

I added the wrong error message. I also tried the new link but it doesn't work either.
Error downloading https://github.com/stm32duino/BoardManagerFiles/raw/main/package_stmicroelectronics_index.json
Error downloading https://downloads.arduino.cc/packages/package_index.json

Seems you have network issue as even the official arduino boards index could not be downloaded. Check your connection and network proxy configuration in the Arduino IDE preferences.


Is it possible for the layout of days untouched even if the CalendarWeekView height has changed?

I am trying to view the codes but even if logic inside the layoutSubview of CalendarWeekView is called based on a condition, the calendar days still gets displayed in a squished way when the height of a calendar is changed. Is it possible for the days not to be squished?

I quickly looked at this problem and I didn't find a solution.
But I think I will try to do this by default.
#182 https://camo.githubusercontent.com/77ab6b0f311cfaae19b093d6b6427e8071f8cb5f/687474703a2f2f69332e74696574756b752e636f6d2f353661323834656339646265353733662e676966

Ok I will test it out. How will the calendar know to scroll up to the nearest selected day when a view below that is moved?

You misunderstand, I will try to add this feature but currently there is nothing.

Oh. Thanks!
Sent from my iPhone

On Aug 9, 2015, at 2:52 AM, Jonathan Tribouharet<EMAIL_ADDRESS>wrote:
You misunderstand, I will try to add this feature but currently there is nothing.
—
Reply to this email directly or view it on GitHub.

Check out my take on it. https://github.com/franciszabala/calendarTest
I am using your classes to generate the calendar and added other codes to create the Sunset-like calendar view


PDF exports dont contain text or clickable links

Describe the Bug
Not sure if this is a bug or the way it was intended but the PDF export gives a PDF image, rather than rendered text. this means you cannot copy text from the file, or make links clickable. Unfortunately, this makes the tool pretty unusable for the real world.
Reproduction
Steps to reproduce the behaviour:

Create a CV with links/text in
Click on PDF download button center bottom
Open PDF in any PDF program
Realise you cannot click links or highlight text

Expected Behaviour
Text should be rendered as text to the PDF. suggest changing PDF export library being used, or adjusting the settings of the current one.
Desktop (please complete the following information):

OS: all of them
Browser: all of them

Additional Context
N/A

@mporam did you click the diskette icon or the printer icon? The diskette icon exports an image-like file in PDF like the one you described while the printer icon exports actual PDF files which has all characteristics of a PDF file... including what you desire.

However, do we need the diskette icon then? Ideally, the diskette icon would open a save dialogue and save the resume not as an image but as a rendered text (like via the print option).

Diskette has the ability to export an unconstrained pdf which is the advantage over print. However, not having selectable text and links is a major drawback that I only discovered after submitting an application. Are there major difficulties generating pdfs with actual text? 😃

just noticed that there is a info message when using the :floppy_disk: save.

This export method makes use of HTML canvas to convert the resume to an image and print it on a PDF, which means it will lose all selecting/parsing capabilities. If that is important to you, please try printing the resume instead, using Cmd/Ctrl + P or the print button below. The result may vary as the output is browser dependent, but it is known to work best on the latest version of Google Chrome.

i personally did not notice that when saving my resume (my bad! :sweat_smile:). maybe that warning could be bold or highlighted somehow?

maybe that warning could be bold or highlighted somehow?
Yes that would be nice. I'd even like a modal popped between the click event and the actual download.

Sorry only just seen the responses here. I see what you mean about using the print button. The UX of that is very confusing, as it's not printing it's saving that I want to achieve. The message in the save popup is quite technical and not clear or obvious especially for non-devs. Perhaps some tooptips to explain this would be better? Certainly some explanation is needed to show that the print icon is actually for saving as a rendered PDF

Just jumping in here to say that certain templates (Like Pikachu) don't render correctly with the print to pdf options, and when doing the microsoft print to pdf which does render correctly is still unclickable.

Closing this issue as Reactive Resume has been bumped up to v2.


Make clickable image areas more obvious in flow grid mode

First of all, a simple question:

Well, in fact, you don't know for certain. And this is bad, because this is unpredictable. GUI must be logical and predictable. And if you click far away from image, you are not expecting that this will open that image as result. All users, who used at least one of image-stored sites, know for sure that if you teoreticly draw in mind a squere frame around the image and make it on 5-10px bigger, you will get this image clickable area. And between images in normal grid exist some free space, clicking on it will not result opening any image. This space is really needed, it also prevent misclicks. And clickable image borders shouldn't be depending of number of images in a row(as in current version). It should be fixed constant value.
Btw, not obvious clickable image area also exist in wreview window, but I don't think that there it might cause a misclicks or another problems. So it's not a big deal.
Current clickable image areas

More obvious suggested clickable image areas

Actually there's space in the current version, so it's like:

Your suggestion is good for when there's a lot of blank space or when images are square, but what about landscape images?

With your suggestion, there's two solutions:

First has unnecessary white space, second is even more "unpredictable" than the current solution.
Since you suggested a new grid with fixed 150x150 images (issue #883), this will already be implemented as all images in "fixed grid mode" will have fixed size (and so it will do as in option 1).

With your wide image example, my original solution isn't look optimal amymore...
But anyway, I like your second variant:

First variant is not make sence, because it will be exectly fixed grid mode. But second varians is very obvious, as I think, and, more important, it solves main problem - misclicks. So it's anyway better then current one.

Since fixed grid mode was added, I'm using only it, so more obvious  image areas in flow grid mode is not actual for me now.
But! there is another place in Grabber, that need more obvious image areas in it's grid - favourites.


launching correct version of spyder

Hi all-
I've been using Spyder for a couple years.  I start up Anaconda Navigator, then i change the environment to python 2.7, and then i launch spyder.  The title of the spyder window says "python 2.7".  And all was good for a long time.
However, i did an update recently, and now things aren't working as before.  Now when i try to launch Spyder, it always launches as Python 3.7.  Even when i put the environment to 2.7, it still comes up as Python 3.7.  I hadn't done anything to change my environments, and they seem to still be installed, but i can't for the life of me figure out how to get python 2.7 inside of Spyder.
Here are the steps:
1: start anaconda navigator
2: change environment to python 2.7 (the Applications on dialog)
3: Launch Spyder 3.3.3 (according to Navigator)
Expected behavior:  Spyder 3.3.3 window running Python 2.7.
Actual behavior:  Spyder 4.1.4 window running Python 3.7.
Versions:
Anaconda Navigator: 1.9.12
Spyder:  4.1.4  ?
OS:  Linux Mint 20 (based on Ubuntu 20).
It's as though Navigator isn't acknowledging that it's in the 2.7 environment anymore.  As mentioned, all was fine before i did a recent update (conda update anaconda-navigator).
Hope someone can help.  Thanks!
-Fizz

Hi @Fizz04,
Are you trying to launch Spyder 4.1.4 or Spyder 3.3.3 in a python 2.7 environment?
Please note that we removed support for Python 2.7 a couple of months ago and we recommend to migrate all your code to Python 3 as soon as you can.

Hi steff456-
When i am in Navigator, i set my environment to python 2.7.  I see the Spyder icon which says "Spyder 3.3.3".  But when i click on the launch button, it actually launches 4.1.4.
Unfortunately, the code i am using involves a third party, and modifying it to python 3 is not an option.  So I need to be able to run python 2.7.
How can i run under 2.7?
-Fizz

Hi @Fizz04,
In this issue https://github.com/spyder-ide/spyder/issues/13510 we explain how you can run Python 2.7 in Spyder 4.1.4
Please let me know if this works for you

Hi steff456
I will check out that link.  But isn't there an issue when Navigator says it's 3.3.3 but it actually launches 4.1.4?
Chris

Hi steff456
Issue #13510 says i have 3 options.  The first is:
Create a conda environment with Spyder 3.3.6, which is the stable version for Spyder 3 that supports Python 2.
But i should already have this.  I've been running a Python 2.7 environment for a couple years.  But this update seems to have messed that up.  It's like Anaconda won't "engage" the 2.7 environment anymore.  It says it is, but it always launches the default apps, rather than the environment-specific ones.
-FIzz

Can you please try to run spyder from the terminal using the following commands,
conda activate your-env-py-2
sypder

Please note that in that environment you need to have Spyder 3.3.6 installed, you can check by searching the version after typing conda list. If you can see closely in the discussion, we recommend you to upgrade to Spyder 4 and change the kernel from the IPython console to use python 2.7. Let me know if that helps.

When i run it through the console, i am able to launch Spyder 3.3.3.  I never had to do that before.  Are you saying in order to launch it through Anaconda Navigator now i need 3.3.6?  What changed that 3.3.3 won't launch through Navigator anymore?
I have a second machine which is near-identical. On it i have updated to Spyder.  In Navigator, it says the version is Spyder 4.0.1.  But when i launch it, it's Spyder 4.1.4, which is what i have in my base environment.  So it's the same issue- regardless of which environment i set in Navigator, it launches the base environment version of Spyder.
So how can i get it to actually launch the correct version of Spyder from Navigator?  Why does Navigator always launch the base environment version?  It never behaved this way before the last update.
But if i have to use Spyder 4, how can i tell it to use python 2.7 via IPython?
-Fizz

When i run it through the console, i am able to launch Spyder 3.3.3. I've never had to launch through the console before. Are you saying in order to launch it through Anaconda Navigator now i need 3.3.6? What changed that 3.3.3 won't launch through Navigator anymore?

You can try to run Spyder 3.3.3 from the console as well, I thought you had installed Spyder 3.3.6.

I have a second machine which is near-identical. On it i have updated to Spyder. In Navigator, it says the Spyder version is 4.0.1. But when i launch it, it's Spyder 4.1.4, which is what i have in my base environment. So it's the same issue- regardless of which environment i set in Navigator, it launches the base environment version of Spyder.
So how can i get it to actually launch the correct version of Spyder from Navigator? Why does Navigator always launch the base environment version? It never behaved this way before the last update. I mean, what's the point of setting up separate environments if it's always going to launch the base environment?

I think this is an error from Anaconda Navigator rather than Spyder, so please go ahead and open an issue in https://github.com/conda/conda/issues

But if i have to use Spyder 4, how can i tell it to use python 2.7 via IPython?

For you to use Spyder 4 with a Python 2.7 kernel you have to first create an environment of Python 2.7
conda create -n py2 python=2.7
conda activate py2
pip install spyder-kernels

Then deactivate this environment and start Spyder 4 from your base environment
conda deactivate
spyder

Once Spyder 4 is opened, you go to Preferences > Python Interpreter > Python Interpreter and check the option to Use the following Python interpreter and search your python executable, in Linux you will find it inside the anaconda folder as something like this ~/anaconda3/envs/my-py2-env/bin/python. Then you will have a python 2 kernel for you to work with. If you want, this video will explain show you how to do this https://www.youtube.com/watch?v=Ul79ihg41Rs&t
Let me know if this helps

You can try to run Spyder 3.3.3 from the console as well, I thought you had installed Spyder 3.3.6.

That's what i mean- i can only get Spyder (any other than the base environment version) to work using the console.

I think this is an error from Anaconda Navigator rather than Spyder, so please go ahead and open an issue in https://github.com/conda/conda/issues

Yes, i think so too.  Guess i posted this in the wrong section.  I will post there too.
-Fizz

For you to use Spyder 4 with a Python 2.7 kernel you have to first create an environment of Python 2.7
conda create -n py2 python=2.7
conda activate py2
pip install spyder-kernels

Then deactivate this environment and start Spyder 4 from your base environment
conda deactivate
spyder

Once Spyder 4 is opened, you go to Preferences > Python Interpreter > Python Interpreter and check the option to Use the following Python interpreter and search your python executable, in Linux you will find it inside the anaconda folder as something like this ~/anaconda3/envs/my-py2-env/bin/python. Then you will have a python 2 kernel for you to work with. If you want, this video will explain show you how to do this https://www.youtube.com/watch?v=Ul79ihg41Rs&t

Ah, ok, I've actually tried this (though i already had the py27 environment installed).  It gives me a warning that running this version in conjunction with Spyder running 3.7 may cause issues.  So i'd prefer to keep things consistent as before.
Maybe i should go back to the previous version of anaconda.  Is there a way to that?
-Fizz

Maybe i should go back to the previous version of anaconda. Is there a way to that?

Please review in the anaconda site if that is possible

I posted the issue in the Anaconda Navigator, as you advised.  But i've seen no replies yet.  What else can i do?
-Fizz

Hi @Fizz04,

Ah, ok, I've actually tried this (though i already had the py27 environment installed). It gives me a warning that running this version in conjunction with Spyder running 3.7 may cause issues. So i'd prefer to keep things consistent as before.

This is a warning we added so people that don't know what's happening know that there's been an important change that may break things in Spyder. As long as you understand that your the kernel in the ipython console will be running in your newly py2 environment you can use it as I instructed before

I posted the issue in the Anaconda Navigator, as you advised. But i've seen no replies yet. What else can i do?

There's nothing more that I can do, the response in the issue tracker vary a lot among different projects so please be patient.

I'm closing this issue because there wasn't a follow-up response after more than a week. If your error persists please re-open this issue and reply with the requested information.
Thanks for reporting!

I haven't seen any reply from the Conda boards about this, it's been more than a month i think.  So the issue remains.   I'm not sure who to ask about any possible fix otherwise.  Thanks!
-Fizz

@Fizz04 maybe try to install in your base env anaconda-navigator 1.9.7 (the previous version). You should be able to do it by activating your base env and running conda install anaconda-navigator=1.9.7 from a terminal

@Fizz04 maybe try to install in your base env anaconda-navigator 1.9.7 (the previous version). You should be able to do it by activating your base env and running conda install anaconda-navigator=1.9.7 from a terminal

So, i have given this a try and it now launches the correct version of Spyder as expected.  But after Spyder launches, i get an Application Launch Error.  It reads:
libGL error: MESA-LOADER: failed to open radeonsi (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open radeonsi (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
libGL error: failed to load driver: swrast
I've never seen these before.  What are these about?
-Fizz

Hi @Fizz04 that messages seem related with the drivers of your graphics card. I think there is not much we can do to help you further, sorry :/
I'm closing this one since there is not much we can do from our side but if you manage to find more info regarding the issue feel free to post it here

Please do not close this thread.   This seems particular to something in Spyder itself.  The graphics drivers are from the kernel (no external 3rd party).  I did not have this error on earlier versions of Conda or Spyder, and i did not have this version on the latest version until this downgrade.  So i would like to get feedback from the community about possible causes.

Makes sense @Fizz04 will leave the issue open :+1:

Great!  Thanks much!

Hi, I do not have many insights about possible causes, but I would like to mention that I get similar Application Launch Error.
In my case, I have a clean installation of everything (Ubuntu, conda and spyder). When launching spyder I get the following:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
libGL error: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast

At the moment Spyder seems to work fine. I was just checking about these messages in the Spyder issues when I found this thread, so I decided to add it here in case it is useful.
If you think it is useful that I open a new issue, tell me please.

@Miguel-LlamasLanza, please open a terminal and run
sudo apt install libgl1-mesa-dri

That should fix that problem.

@ccordoba12
I tried also running sudo apt install --reinstall libgl1-mesa-dri, in case there was something wrong with the installation of this library. Still getting the same messages.
I have found out that the two files refered to in the message (swrast_dri.so and iris_dri.so) are actually stored in /usr/lib/x86_64-linux-gnu/dri/, instead of /usr/lib/dri/. This is the problably why spyder does not find it. Maybe you find it useful to know that I have Ubuntu 22.04.2 LTS and I am using  Spyder 5.4.2 (Python 3.10.10).

Are you using conda or conda-forge packages?

I only have one conda-forge package (statsmodels). All the ohers are conda packages.
Just to check, I created a new conda environment and installed only spyder with conda. Same messages appear.

Ok, please install Spyder from conda-forge and try again.

I tried from conda-forge. Those errors disappear, but these appear:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
fromIccProfile: failed minimal tag size sanity
/home/lmiguel/anaconda3/envs/test_env/lib/python3.11/site-packages/jupyter_client/threaded.py:73: RuntimeWarning: ZMQStream only supports the base zmq.Socket class.

                Use zmq.Socket(shadow=other_socket)
                or `ctx.socket(zmq.DEALER, socket_class=zmq.Socket)`
                to create a base zmq.Socket object,
                no matter what other kind of socket your Context creates.

  self.stream = zmqstream.ZMQStream(self.socket, self.ioloop)
/home/lmiguel/anaconda3/envs/test_env/lib/python3.11/site-packages/jupyter_client/threaded.py:73: RuntimeWarning: ZMQStream only supports the base zmq.Socket class.

                Use zmq.Socket(shadow=other_socket)
                or `ctx.socket(zmq.SUB, socket_class=zmq.Socket)`
                to create a base zmq.Socket object,
                no matter what other kind of socket your Context creates.

  self.stream = zmqstream.ZMQStream(self.socket, self.ioloop)

I'm going to close this issue because I consider it's solved thanks to Conda-forge and there's nothing we can do about it directly in Spyder.

I have just installed spyder through conda-forge in a new environment and the error messages are still there. Again, I have not yet encountered any issue within spyder, but I thought it is worth reporting since conda-forge does not seem to solve the issue in all cases. I don't know if it has to do with the versions, but just in case, in this environment I am using python 3.10, and spyder 5.4.3.


Add support for multiple .xctool-args

Thanks for working on this. Left several comments to your changes.

I updated the files with your comments.

The rebase did not worked

Looks like bad rebase: files changed: 124. Could you squash your commits and try rebasing again on top of master?

I'll closed this pull request and restart from your last commit

You can force push to your branch. git push --force

I restored it, finally!

I reset head and did a force push. Tell me if it's right for you.

I reset head and did a force push. Tell me if it's right for you.

2 last comments, thanks for working on this!
Could you squash all 4 commits into one? Also it would be awesome if you add a test to cover changes.

This is done for the commit. However I don't know where and how to make my test. Can you help me about this?

Regarding tests: there is XCToolTests.m file that have some tests around XCTool class. I would add sample custom.xctool-args file to xctool-tests/TestData folder and then add a test that passes path to that file to XCTool. In test we can then verify that xctool reads data from that file and it is read correctly. What do you think?
P.S. Thanks for squashing into one commit and fixing spaces things :+1:

Would be cool to das something to the Readme about that :)

Could i support you? Would be nice to get this into xctool

@x2on, I think the only missing part is tests?

@x2on @ExtremeMan Sorry for the late response. It's missing only the tests but I did not know where and how to write them, but I'm open if you want help me.

I'd like to get this PR merged, so I can write tests. Should I create a new pull request with tests?

@vitalys @ExtremeMan: I'm currently working again on the test to finish this PR.
@ExtremeMan: Can you just tell me how you run your test? Because when I run testCallingWithShowBuildSettingsPassesThroughToXcodebuild I get all the time a error...

I use xctool to run xctool tests :)

Thank you for your help! I added a unit test with custom.xctool-args file

Ready to push if you aren't going to address my comments. Just let me know what you think.

I think that is better. Multiple argument files can be confusing 😕
Will you fix that?

Nope; this is not a real problem

Nope; this is not a real problem.

Problem if someone supplies multiple .xctool-args =) But okay.

Thanks for your PR and adding tests! I highly appreciate that. Happy to merge.

Thank you @ExtremeMan! I'm glad to help you to enhance xctool 😉


Upgrade to Add-on 0.11.1: failed

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 07:26:35 (1 occurrences)
Last logged: 07:26:35

[140318071754320] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 168, in async_install
    await async_update_addon(self.hass, slug=self._addon_slug, backup=backup)
  File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 58, in _wrapper
    data = await funct(*argv, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 112, in async_update_addon
    return await hassio.send_command(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 541, in send_command
    raise HassioAPIError(error.get(ATTR_MESSAGE))
homeassistant.components.hassio.handler.HassioAPIError: Unknown error, see supervisor

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2761, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 154, in async_install
    await entity.async_install_with_progress(version, backup)
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 463, in async_install_with_progress
    await self.async_install(version, backup)
  File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 170, in async_install
    raise HomeAssistantError(f"Error updating {self.title}: {err}") from err
homeassistant.exceptions.HomeAssistantError: Error updating EMHASS: Unknown error, see supervisor

SolaX_Power_Network_Technology__Zhe_jiang__Co___Ltd___A1_Hybrid_7_0_US__240V_

What does the supervisor logger says?

2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_start_timesteps_of_each_deferrable_load' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_end_timesteps_of_each_deferrable_load' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_peak_hours_periods_start_hours' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_peak_hours_periods_end_hours' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_treat_deferrable_load_as_semi_cont' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_set_deferrable_load_single_constant' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_set_deferrable_startup_penalty' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'load_peak_hours_cost' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'load_offpeak_hours_cost' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'photovoltaic_production_sell_price' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_pv_module_model' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_pv_inverter_model' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_surface_tilt' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_surface_azimuth' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_modules_per_string' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'list_strings_per_inverter' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'inverter_is_hybrid' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'compute_curtailment' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'set_use_battery' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_nominal_energy_capacity' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'optimization_time_step' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'historic_days_to_retrieve' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'method_ts_round' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'lp_solver' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'lp_solver_path' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'set_battery_dynamic' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_dynamic_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_dynamic_min' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'weight_battery_discharge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'weight_battery_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'load_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_discharge_power_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_charge_power_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_discharge_efficiency' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_charge_efficiency' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_minimum_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_maximum_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'battery_target_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'production_price_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'set_zero_min' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'load_negative' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'load_cost_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'weather_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:41:06.448 WARNING (MainThread) [supervisor.addons.options] Option 'delta_forecast_daily' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'logging_level' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'costfun' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'sensor_power_photovoltaics' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'sensor_power_load_no_var_loads' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'set_total_pv_sell' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'set_nocharge_from_grid' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'set_nodischarge_to_grid' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'maximum_power_from_grid' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'maximum_power_to_grid' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'number_of_deferrable_loads' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_nominal_power_of_deferrable_loads' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_operating_hours_of_each_deferrable_load' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_start_timesteps_of_each_deferrable_load' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_end_timesteps_of_each_deferrable_load' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_peak_hours_periods_start_hours' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_peak_hours_periods_end_hours' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_treat_deferrable_load_as_semi_cont' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_set_deferrable_load_single_constant' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_set_deferrable_startup_penalty' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'load_peak_hours_cost' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'load_offpeak_hours_cost' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'photovoltaic_production_sell_price' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_pv_module_model' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_pv_inverter_model' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_surface_tilt' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_surface_azimuth' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_modules_per_string' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'list_strings_per_inverter' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'inverter_is_hybrid' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'compute_curtailment' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'set_use_battery' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_nominal_energy_capacity' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'optimization_time_step' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'historic_days_to_retrieve' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'method_ts_round' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'lp_solver' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'lp_solver_path' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'set_battery_dynamic' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_dynamic_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_dynamic_min' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'weight_battery_discharge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'weight_battery_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'load_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_discharge_power_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_charge_power_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_discharge_efficiency' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_charge_efficiency' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_minimum_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_maximum_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'battery_target_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'production_price_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'set_zero_min' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'load_negative' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'load_cost_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'weather_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-10-29 16:44:57.536 WARNING (MainThread) [supervisor.addons.options] Option 'delta_forecast_daily' does not exist in the schema for EMHASS (5b918bf2_emhass)

Hi, I just updated emhass and I see the same supervisor error logs. I did the config conversion.

Anyone else see these errors in supervisor after updating emhass to 0.11.2?
I tried to get rid of it but not succesfull up until now. The list keeps getting longer with the same errors.
I did the config conversion.
2024-11-10 15:55:44.535 WARNING (MainThread) [supervisor.addons.options] Option 'battery_dynamic_min' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.535 WARNING (MainThread) [supervisor.addons.options] Option 'weight_battery_discharge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.536 WARNING (MainThread) [supervisor.addons.options] Option 'weight_battery_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.536 WARNING (MainThread) [supervisor.addons.options] Option 'load_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_discharge_power_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_charge_power_max' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_discharge_efficiency' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_charge_efficiency' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_minimum_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_maximum_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'battery_target_state_of_charge' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.537 WARNING (MainThread) [supervisor.addons.options] Option 'delta_forecast_daily' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'weather_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'load_cost_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'set_zero_min' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'production_price_forecast_method' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'optional_solcast_api_key' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'optional_solar_forecast_kwp' does not exist in the schema for EMHASS (5b918bf2_emhass)
2024-11-10 15:55:44.538 WARNING (MainThread) [supervisor.addons.options] Option 'optional_solcast_rooftop_id' does not exist in the schema for EMHASS (5b918bf2_emhass)`

I was able to fix by deinstalling and reinstalling the addon.
However - the complete configuration procedure must be done afterwards.
Have MUST habe a backup of your YAML configuration available before the reinstallation!

However - the complete configuration procedure must be done afterwards.
You MUST have a backup of your YAML configuration available before the reinstallation!

This is a difficult step for many folks as you do the upgrade, then you realize you needed to save the configuration YAML from before the upgrade.
Is there a way the legacy configuration file can be saved and made available after the upgrade?
Can the upgrade from the legacy configuration to the new configuration be automatic?

@GeoDerp
Hey morning ...
I have had numerous attempts with upgrade and I get stuck each and every time...
Upgrade goes through but I cannot expand any buttons in you gui to paste the emhass settings info... and without it - the add on is failing.... done it with @purcell-lab and we both do not really know where it goes wrong... suggestions please?

@GeoDerp
Hey morning ...
I have had numerous attempts with upgrade and I get stuck each and every time... Upgrade goes through but I cannot expand any buttons in you gui to paste the emhass settings info... and without it - the add on is failing.... done it with @purcell-lab and we both do not really know where it goes wrong... suggestions please?
I cannot click any buttons see below:

nothing expands nothing is live cant put back my settings.... which I have saved out...

First off im sorry for the late reply.
One reason why nothing is working could be that javascript is disabled on your web browser. Try another web browser

@GeoDerp
Hey morning ...
I have had numerous attempts with upgrade and I get stuck each and every time... Upgrade goes through but I cannot expand any buttons in you gui to paste the emhass settings info... and without it - the add on is failing.... done it with @purcell-lab and we both do not really know where it goes wrong... suggestions please?
I cannot click any buttons see below:

nothing expands nothing is live cant put back my settings.... which I have saved out...

First off im sorry for the late reply. One reason why nothing is working could be that javascript is disabled on your web browser. Try another web browser. If that doesnt work we can look deeper into the issue.

hey @GeoDerp
Thank you so much for your reply first and foremost...
I just checked and my java script is enabled.
This has also happened both in Chrome as well as Edge.
Chrome snipped of settings below:

Any other ideas? Happy to chat on discord if you need to check anything else... (raf_t_aud)

Sure, mine is: geo_the_noodle

{
  "battery_charge_efficiency": 0.95,
  "battery_charge_power_max": 1000,
  "battery_discharge_efficiency": 0.95,
  "battery_discharge_power_max": 1000,
  "battery_dynamic_max": 0.9,
  "battery_dynamic_min": -0.9,
  "battery_maximum_state_of_charge": 0.9,
  "battery_minimum_state_of_charge": 0.3,
  "battery_nominal_energy_capacity": 5000,
  "battery_target_state_of_charge": 0.6,
  "compute_curtailment": false,
  "continual_publish": false,
  "costfun": "profit",
  "delta_forecast_daily": 1,
  "end_timesteps_of_each_deferrable_load": [
    0,
    0
  ],
  "historic_days_to_retrieve": 2,
  "inverter_is_hybrid": false,
  "load_cost_forecast_method": "hp_hc_periods",
  "load_forecast_method": "naive",
  "load_negative": false,
  "load_offpeak_hours_cost": 0.1419,
  "load_peak_hour_periods": {
    "period_hp_1": [
      {
        "start": "02:54"
      },
      {
        "end": "15:24"
      }
    ],
    "period_hp_2": [
      {
        "start": "17:24"
      },
      {
        "end": "20:24"
      }
    ]
  },
  "load_peak_hours_cost": 0.1907,
  "logging_level": "INFO",
  "lp_solver": "default",
  "lp_solver_path": "empty",
  "maximum_power_from_grid": 9000,
  "maximum_power_to_grid": 9000,
  "method_ts_round": "nearest",
  "modules_per_string": [
    16
  ],
  "nominal_power_of_deferrable_loads": [
    3000,
    750
  ],
  "number_of_deferrable_loads": 2,
  "operating_hours_of_each_deferrable_load": [
    4,
    0
  ],
  "optimization_time_step": 30,
  "photovoltaic_production_sell_price": 0.1419,
  "production_price_forecast_method": "constant",
  "pv_inverter_model": [
    "Fronius_International_GmbH__Fronius_Primo_5_0_1_208_240__240V_"
  ],
  "pv_module_model": [
    "CSUN_Eurasia_Energy_Systems_Industry_and_Trade_CSUN295_60M"
  ],
  "sensor_linear_interp": [
    "sensor.power_photovoltaics",
    "sensor.power_load_no_var_loads"
  ],
  "sensor_power_load_no_var_loads": "sensor.power_load_no_var_loads",
  "sensor_power_photovoltaics": "sensor.power_photovoltaics",
  "sensor_replace_zero": [
    "sensor.power_photovoltaics"
  ],
  "set_battery_dynamic": false,
  "set_deferrable_load_single_constant": [
    false,
    false
  ],
  "set_deferrable_startup_penalty": [
    0,
    0
  ],
  "set_nocharge_from_grid": false,
  "set_nodischarge_to_grid": true,
  "set_total_pv_sell": false,
  "set_use_battery": false,
  "set_zero_min": true,
  "start_timesteps_of_each_deferrable_load": [
    0,
    0
  ],
  "strings_per_inverter": [
    1
  ],
  "surface_azimuth": [
    205
  ],
  "surface_tilt": [
    30
  ],
  "treat_deferrable_load_as_semi_cont": [
    true,
    true
  ],
  "weather_forecast_method": "scrapper",
  "weight_battery_charge": 1,
  "weight_battery_discharge": 1
}