Duplicate output in log file

Rasa version:
1.1.8, commit e3ae94995d
Python version:
3.7 (I have to check once I get home)
Operating system (windows, osx, ...):
Observed on Ubuntu and Mac OS X
Issue:
Both rasa train and rasa test tend to write output twice for no reason. This happens on my Ubuntu desktop and on Vova's MacBook, but not on my MacBook.
Error (including full traceback):
There is no error message generated. Here are a few lines of example output:
I0726 08:59:29.732669<PHONE_NUMBER>59296 test.py:537] Evaluation Results on CONVERSATION level:
2019-07-26 08:59:29 INFO     rasa.core.test  - Evaluation Results on CONVERSATION level:
I0726 08:59:29.732778<PHONE_NUMBER>59296 test.py:539] 	Correct:          83 / 250
2019-07-26 08:59:29 INFO     rasa.core.test  - 	Correct:          83 / 250

or
I0726 08:06:45.822660<PHONE_NUMBER>84544 generator.py:318] Finished phase (250 training samples found).
2019-07-26 08:06:45 DEBUG    rasa.core.training.generator  - Finished phase (250 training samples found).

Command or request that led to error:
rasa test core \
	--stories data/train \
	--out results/train \
	-vv &> test-train.out

or
rasa train core \
	--stories data/train \
	--domain domain.yml \
	--config config.yml \
	--fixed-model-name transformer \
	-vv &> train.out

I have the same on my Mac:
I0726 17:29:45.722398<PHONE_NUMBER> featurizers.py:649] Created 1441 action examples.
2019-07-26 17:29:45 DEBUG    rasa.core.featurizers  - Created 1441 action examples.
I0726 17:29:45.728195<PHONE_NUMBER> memoization.py:160] Memorized 30 unique examples.
2019-07-26 17:29:45 DEBUG    rasa.core.policies.memoization  - Memorized 30 unique examples.
I0726 17:29:48.772770<PHONE_NUMBER> agent.py:797] Persisted model to '/var/folders/k6/6hbz34d90fl1s5ywp6srmsg80000gn/T/tmppk3t7rj2/core'
2019-07-26 17:29:48 INFO     rasa.core.agent  - Persisted model to '/var/folders/k6/6hbz34d90fl1s5ywp6srmsg80000gn/T/tmppk3t7rj2/core'

@dakshvar22 welcome to the club

@tmbo any ideas about this problem?

@Ghostvv I couldn't reproduce this locally when I tried to yesterday. I used the master branch and py 3.6
So the only difference is the python version I guess. @JEM-Mosig can you try this on your machine with a python 3.6 please?

@tmbo I think it appears on refactor-tf branch

@dakshvar22 fixed this in 1.3 🚀


SIP-33: Allow inactive StakedSui objects to be redeemed immediately

This looks simple/reasonable enough to me, but I cannot remember the context for why we have the `stake_activation_epoch(&staked_sui) <= ctx.epoch().
@emmazzz, was it to make the amount of new stake that will become active in the next epoch for a given validator more predictable (i.e., because you could do a big request_add_stake early in the epoch and then pull it at the last second without this assertion)? This doesn't seem like a significant protection (particularly because you can already churn stake by withdrawing existing stake at the last second), but I might be forgetting the reasoning or missing something.

This looks simple/reasonable enough to me, but I cannot remember the context for why we have the `stake_activation_epoch(&staked_sui) <= ctx.epoch().
@emmazzz, was it to make the amount of new stake that will become active in the next epoch for a given validator more predictable (i.e., because you could do a big request_add_stake early in the epoch and then pull it at the last second without this assertion)? This doesn't seem like a significant protection (particularly because you can already churn stake by withdrawing existing stake at the last second), but I might be forgetting the reasoning or missing something.

I also don't remember the exact context. I think it might be related to potentially adding unbonding period, but bonding period can certainly still be implemented without this assertion too. So I'm cool with this change too.

This has been implemented and merged in https://github.com/MystenLabs/sui/pull/18265
Closing as accepted and merged.

I thought final SIPs were supposed to be merged in, instead of closed? @hyd628


doesnt work on ninjahax 2.0

will open and try to install but says
Install failed!
Could not initalize AM service
Press Start to continue.
And whenyou press select to Install MSET ROP and try to install anything it says
ROP installation failed!
Raw Error: 0xd8e06406
Module: MODULE_NN_SRV (0x19)
Level: LEVEL_PERMANENT (0x1b)
Summary: SUMMARY_INVALID_ARGUMENT (0x7)
Dsescription: DESCRIPTION_ACCESS_DENIED (0x6)
Press Start to continue.
I am running ninjahax 2.0 on firmware <IP_ADDRESS>u

Well, you wouldn't be believe ;). You know that Ninjhax 2.0 doesn't have the same capabilities that Ninjhax 1.x has? There's no way you can install CIAs on a FW bigger than 9.2.0, sorry.

As I've stated in multiple places, FBI cannot work with Ninjhax 2.0 as I can't gain access to the needed services.


spam "wifi:Haven't to connect to a suitable AP now!" when using 4G or ethernet

Hi, i am learning about esp-insights. I want to add this into my project using 4G/Ethernet/Wifi.
When i config my project using Wifi, my device runs normally, but if 4G/Ethernet this spams "wifi:Haven't to connect to a suitable AP now!".
What should i do to fix this !

Hi @TiDiChi ,
This warning print Haven't to connect to a suitable AP now! is displayed when esp_wifi_sta_get_ap_info(wifi_ap_record_t *ap_info) is called before esp_wifi_connect(void).
You can ignore this message as application (esp-insights in this case) uses this API just to check whether station is connected to Wi-Fi or not.
cc: @vikramdattu

Hi @TiDiChi ,
This warning print Haven't to connect to a suitable AP now! is displayed when esp_wifi_sta_get_ap_info(wifi_ap_record_t *ap_info) is called before esp_wifi_connect(void).
You can ignore this message as application (esp-insights in this case) uses this API just to check whether station is connected to Wi-Fi or not.
cc: @vikramdattu

Thank you very much. I did it and this spam did not appear!

@TiDiChi if you're using interface other than Wi-Fi, it is better to use the netif APIs to query if that particular interface is connected or not. That would be much cleaner.
e.g., for ethernet
     esp_netif_t *esp_netif = esp_netif_get_handle_from_ifkey("ETH_DEF"); // ethernet handle
     if (esp_netif_is_netif_up(esp_netif) && esp_netif_get_ip_info(esp_netif, &ip_info) == ESP_OK) {
         // Do your stuff here
     }

Do check esp_netif.h.


ARTEMIS-3574 multiple bindings for embedded webserver

Add BindingDTO to allow configuring multiple addresses to listen on
Start a new ServerConnector for each binding and deploy the corresponding web-applications
Update documentation and tests

In general I like this idea since the underlying Jetty server supports this kind of behavior natively. I was concerned at first that supporting this would require creating two instances of Jetty, but that is not the case. This is good work, @MM53!
The problem is that there is no backwards compatibility with the previous configuration. Using the previous configuration results in an NPE, i.e.:
java.lang.NullPointerException
        at org.apache.activemq.artemis.dto.WebServerDTO.getBindings(WebServerDTO.java:96)
        at org.apache.activemq.artemis.component.WebServerComponent.configure(WebServerComponent.java:87)
        at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:125)
        at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:157)
        at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:105)
        at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:132)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:134)
        at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:50)

This is a breaking change and we cannot introduce it in a minor release. It would need to wait until the next major release.
Alternatively you could provide backwards compatibility and then I think this could be merged and used in the next minor release.

FWIW, there are a handful of checkstyle violations. I recommend you run mvn compile -Pdev and inspect the results locally or check out the results of the automated PR builds.

@jbertram, thanks for your response. My plan was to keep backwards compatibility but I forgot to check for null instead I only checked if the list contains some bindings. I will fix this issue and test the code with some previous configurations to see if there are more problems.

@MM53, that's good news. It would probably be worth leaving some tests for the old style configuration and creating new tests for the new config. That way the test-suite will exercise both options and problems like this would be detected automatically.

I updated my changes to work properly with the old style configuration and added some tests to verify both formats. I also resolved the checkstyle violations. Hope everything is fine now.

@MM53, there's a conflict now. It's a simple change from c502e94ade9e050849a2d7fd2431c28ea77f4f0a. Once you resolve the conflict I'll merge the PR. Thanks!

@jbertram / @MM53 what's the status on this?
I'm going to release today, but this is a big change to include right before the release... I will leave it out for now..

I believe the status on this PR is good. I was going to merge it as soon as the PR builds finished. I'm testing manually now to confirm it doesn't break upgrades for existing installs.

I just verified that these changes don't break existing/upgrading users.

@clebertsuconic, do you mind if I merge this?

@jbertram / @MM53 I am reverting this... there's a failure from org.apache.activemq.artemis.tests.smoke.console.ConsoleMutualSSLTest that looks real to me
I would rather defer the change now than break the release..
Can one of you send a new PR with the fix later please?
Thanks

The failing test-case was already noted - org.apache.activemq.artemis.tests.smoke.console.ConsoleMutualSSLTest. It fails for me when I run it in my IDE.

I will have a look at it and create a new PR.

@MM53 an easy way to reproduce it if you don't want to try on the IDE is by running the following command from the ./smoke-tests directory:
cd activemq-artemis/tests/smoke-tests
../../one-test.sh ConsoleMutualSSLTest

if you don't like using the one-test.sh (which is a script I added because I am not good to remember the actual command when I need it fast:
cd activemq-artemis/tests/smoke-tests
mvn -Ptests -DfailIfNoTests=false -Ptests-retry -Ptests-CI -Pextra-tests -DskipStyleCheck=true -DskipPerformanceTests=false -Dtest=ConsoleMutualSSLTest test

(you will probably understand why I committed one-test.sh)

@clebertsuconic thanks, I will try to fix the problem before you build the actual release

@clebertsuconic there was a bug while generating the configuration for a new server which mixed up the old and new configuration style. Therefore the keyStore and trustStore parameters were ignored. I fixed this and created a new PR: #3882 containing all changes.
Not sure why the maven build didn't fail because of this but now everything should work as expected.


Tpwdcee 308

Coverage remained the same at 100.0% when pulling df7b7587300c5685025f4f72debb39f21e5a830f on TPWDCEE-308 into 8f6e43bff6b4bae1c78d019c0115bee7be7dc10a on master.

Coverage remained the same at 100.0% when pulling b0d46df0f60df4688487680f79ae7e3ba3b55012 on TPWDCEE-308 into 8f6e43bff6b4bae1c78d019c0115bee7be7dc10a on master.

Coverage remained the same at 100.0% when pulling 3197d202467d07aa0ef7c4040ed1a6fa9f2e8447 on TPWDCEE-308 into 8f6e43bff6b4bae1c78d019c0115bee7be7dc10a on master.

Coverage remained the same at 100.0% when pulling c5625009186fd410c3ea5dec7d300e2ff8be1c1c on TPWDCEE-308 into 8f6e43bff6b4bae1c78d019c0115bee7be7dc10a on master.


plutus-pab: Adds Swagger support for web-server API

This change adds a support for swagger using servant-openapi that generates an OpenAPI spec for PAB API with descriptions to provide a non-technical information for how endpoints behave and what they expect in requests and responses.
The swagger-ui is accessible through swagger/swagger-ui/index.html
The example of UI:

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[x] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Hey @j-mueller the servant-openapi adds support for Sum types by using oneOf construction. I've fired up Uniswap PAB instance with these changes, here's how the model looks like in swagger-ui:

There's also an issue with representing tuple types in swagger. For example for txRedeemers in Tx type it represented like this:

The simple solution could be to declare the ToSchema instance manually instead of using the generic deriviation. Let me know if this is critical here.

The oneOf construct looks nice, so I'm happy to merge this now.

issue with representing tuple types in swagger

Sorry what is the issue exactly? That the types of the elements of the list aren't specified? In general, encoding a tuple as a heterogeneous list with a fixed length is fine (that is what a tuple is, and that's the default encoding that aeson uses)

This PR adds package dependencies to plutus-ledger which are not used, and that's what Hydra complains about: https://github.com/input-output-hk/plutus/pull/3807/files#diff-cb3369701745e982609f4dfe004aa53507b8570ddc9841d1aa4f186109c32725R122-R123

I don't think we should add a dependency on openapi to the packages below plutus-ledger-api. Those are depended on by the node, and I don't think we want this in the dependency tree for that. You could put them in your orphans module, perhaps.

This PR adds package dependencies to plutus-ledger which are not used, and that's what Hydra complains about: https://github.com/input-output-hk/plutus/pull/3807/files#diff-cb3369701745e982609f4dfe004aa53507b8570ddc9841d1aa4f186109c32725R122-R123

But they're used in these module:
https://github.com/input-output-hk/plutus/pull/3807/files#diff-3792e47803463e7e1b312bd15a54ff370e386fb431ac1d03fb3f68b8bb65c648
https://github.com/input-output-hk/plutus/pull/3807/files#diff-dad89552434f03995ef455b89ec062dd4cc79caf69faf09aeb2ab70d1417cb7b
Is there some other way to include dependencies to packages?

No they aren't. You added freer-simple, semigroups, and openapi3, and you're only using openapi3. Which is exactly what the error message said.

No they aren't. You added freer-simple, semigroups, and openapi3, and you're only using openapi3. Which is exactly what the error message said.

My bad, didn't notice it mentioned the other two. Removed them as well.

@j-mueller @michaelpj I've added the changes for orphan instances: put them on plutus-ledger package and removed openapi3 dependency from plutus-ledger-api and plutus-core.

I think the merging of this PR has taken enough time.
I'm stuck at ToSchema not accepting Sum types. This PR seems to be the only block standing in my way ;(

Hey @kelizarov - All looks great; just one final thing - If you can rebase to master and squish a few of the commits down so the history is a bit cleaner that would be perfect!

@silky you can also just do a squash-merge if you like

Ah thanks @michaelpj ; I looked at 'rebase and merge; only :)
I'll do that!

Hi @michaelpj
May I ask how this affects the developers waiting to make use of the solutions in this PR? I, for one, have been stuck for like a week waiting for it to be merged.

It shouldn't affect you. I have generously decided not to revert it and instead to let it be fixed in a subsequent PR :)

Kindly incorporate ASAP into next plutus-starter-devcontainer: v1.0.10


When set Retryable's option, UnexpectedError occurred.

I tried to use gem_rbs_collection w/ this code,
then UnexpectedError happened on Retryable steep check in this code

If I did Retryable configuration w/
Retryable.configure do |config|
  config.sleep = 1
end

Retryable.retryable do
  results = FizzBuzz.run(Date.today.day)
  puts results
end

it worked.
Do you have any idea to avoid this  Diagnostic ID: Ruby::UnexpectedError?

Probably it's this problem.
https://github.com/soutaro/steep/issues/429

I see.
Now I close this issue.
Thank you to let me know.


ModuleNotFoundError: No module named 'twitter'

I have twitter package installed as the result of conda list | grep twitter results in
python-twitter            3.5                        py_0    conda-forge twitter                   1.18.0                   pypi_0    pypi.
But if I try to import twitter in my jupyter notebook using import twitter it gives an ModuleNotFoundError: No module named 'twitter' error.
What am I doing wrong?

Sorry, I posted this here.


Allow movement of Bays in SLD via sxy coordinates

It's possibly a little premature but the good work in #455 of allowing coordinate movements in the SLD editor made me want to (at least prototype) the possibility of changing bay coordinates to shift bays around. It seemed like the same kind of thing.
Why? I have sometimes hand-crafted an ssd file to replicate bays and after this I wish to move them apart graphically but I find it tedious to modify sxy coordinates.
I'd like to do this by clicking on the bay and setting coordinates on it.
Then, within the bay the coordinates should be relative to the bay object according to the standard (they are nested and relative according to IEC 61850-6 Ed 2.1, Annex C).

If coordinates are defined at different SCL tag hierarchy levels, then each level contains
coordinates relative to the higher level. The absolute coordinate of a lower level is thus
calculated by summing up all higher level coordinates, and the object coordinates themselves.
If there are no coordinates defined at a higher level, then (x,y) = (0,0) is assumed.

Prototyping PR coming up momentarily.
I have a limited amount of SSD files which work in the SLD editor at the moment (possibly due to unrelated reasons or poor constructions of the SSD or some kind of looping condition in the logic with open-scd's rendering, I have not investigated yet). My example for examining this is the attached:
HRP.ssd.txt

@danyill is this still relevant?


Deleting freehand drawing paths

How would one delete a freehand drawing path? For example, I just drew a path, realized its not were I want it, now I want to delete it.

You should be able to tap on an existing line with the tool and then press delete.

Ha. That definitely works.
If you're using the grabcuts dashboard, you have to make sure you have the CORRECT freehand drawing tool selected :)

If you're using the grabcuts dashboard, you have to make sure you have the CORRECT freehand drawing tool selected :)

That certainly makes things difficult, I'm working on making tools distinguishable as soon as I'm back on Wednesday.


Models aren't loaded yet.

Hello! I'm using django-fcm 0.1.1 with Django 1.10. When I've imported DeviceSerializer in my models.py file, I've got the error "django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.". The problem was resolved by moving import statement from the top of models.py to the method. Maybe, it isn't an issue, but there are no similar problems with other serializers.
Traceback (most recent call last):
File "C:\Source\hospital\env\lib\site-packages\django\utils\autoreload.py", line 226, in wrapper
fn(args, **kwargs)
File "C:\Source\hospital\env\lib\site-packages\django\core\management\commands\runserver.py", line 109, in inner_run
autoreload.raise_last_exception()
File "C:\Source\hospital\env\lib\site-packages\django\utils\autoreload.py", line 249, in raise_last_exception
six.reraise(exception)
File "C:\Source\hospital\env\lib\site-packages\django\utils\autoreload.py", line 226, in wrapper
fn(*args, **kwargs)
File "C:\Source\hospital\env\lib\site-packages\django_init.py", line 18, in setup
apps.populate(settings.INSTALLED_APPS)
File "C:\Source\hospital\env\lib\site-packages\django\apps\registry.py", line 108, in populate
app_config.import_models(all_models)
File "C:\Source\hospital\env\lib\site-packages\django\apps\config.py", line 202, in import_models
self.models_module = import_module(models_module_name)
File "C:\Python27\Lib\importlib_init_.py", line 37, in import_module
import(name)
File "C:\Source\hospital\hospital\models.py", line 15, in
from fcm.serializers import DeviceSerializer
File "C:\Source\hospital\env\lib\site-packages\fcm\serializers.py", line 3, in
Device = get_device_model()
File "C:\Source\hospital\env\lib\site-packages\fcm\utils.py", line 15, in get_device_model
return apps.get_model(model)
File "C:\Source\hospital\env\lib\site-packages\django\apps\registry.py", line 194, in get_model
self.check_models_ready()
File "C:\Source\hospital\env\lib\site-packages\django\apps\registry.py", line 131, in check_models_ready
raise AppRegistryNotReady("Models aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.

Hello @dvkovner you can try
DeviceModel = apps.get_model('<app_name>', '<model_name>')
to import the mode instead of importing directly

The problen isn't in the model. It is in the serializer. When I try to import DeviceSerializer on the top of my models.py file, I get the error: "django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.".
When this row of code is placed on the top of models.py, I can't run my app: "from fcm.serializers import DeviceSerializer". I've resolved it by moving this import to the method inside my class in models.py.


Internal Server Error

SQLAlchemy is trying to execute an INSERT query on the users table, but the table hasn't been created in the database.

deleted alembic and run the docker compose execute fast api alembic upgrade head and refresh and the user table showed up with the updated info and there is no more error.
issue was entirely related to the missing database migration, and now that refreshed Alembic and properly executed the upgrade head command, everything is in sync. The users table being present confirms that the migrations were successfully applied, and a pi now has the required database schema


[D1] Adding info on wrangler d1 insights

Summary

Documenting the full list of available options in a table, as of Wrangler 3.95.0
Adding in actual responses from the example d1 insight commands.
Adding a note to define/explain queryEfficiency.
Updating examples to use --limit rather than the outdated --count.

Screenshots (optional)

Documentation checklist

[ ] The documentation style guide has been adhered to.
[ ] If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
[ ] Files which have changed name or location have been allocated redirects.

@rozenmd could you review here too


Handle spaces in Accept-Language header

thank you
published in<EMAIL_ADDRESS>If you like this module don’t forget to star this repo. Make a tweet, share the word or have a look at our https://locize.com to support the devs of this project -> there are many ways to help this project :pray:


error: '"None of [Index([''sequence'', ''score'', ''decoy''], dtype=''object'')] are   in the [columns]"'

Describe the bug
Error - 1
I am getting the following error - error: '"None of [Index([''sequence'', ''score'', ''decoy''], dtype=''object'')] are
in the [columns]"'
I am trying to analyze some Bruker Impact II QTOF data. Does alphapept only process timstof data or data from other Bruker TOFs?
Error-2
I am also getting the following error in the results tab
AttributeError: 'DataFrame' object has no attribute 'px_fit_results'
Traceback:
File "streamlit\script_runner.py", line 337, in _run_script
exec(code, module.dict)
File "C:\Program Files (x86)\AlphaPept\alphapept\webui.py", line 46, in
sidebarmenu
File "alphapept\gui\results.py", line 331, in results
parse_file_and_display(file)
File "alphapept\gui\results.py", line 231, in parse_file_and_display
scatter_plot(file, options)
File "alphapept\gui\results.py", line 209, in scatter_plot
st.code(results.px_fit_results.iloc[0].summary())
File "pandas\core\generic.py", line 5462, in getattr
return object.getattribute(self, name)
Version (please complete the following information):

OS: Windows 10 Enterprise N
Version 0.3.26
Installation Type - One-Click Installer

Hi,
thanks for reporting.
So far, only timsTOF data tested. Do you mind sharing a file so the pipeline can be tested?

Hi,
Thanks for the reply. Please find the zip folder here (https://fz-juelich.sciebo.de/s/mScfGdyrQgV8z4w) containing two impact-II .d files. These are DDA shotgun runs of trypsin digested Arabidopsis leaf proteome (120 min run with 90 mins of effective separation). Please let me know if you need more info or measurements from other organisms.

Hi,
Thanks for uploading the dataset - I was now able to investigate a little bit more. The file type is .baf and would require another Bruker sdk to be read. Apparently, the .baf filetype will be replaced by .tsf-format. Feature finding on these files with the Bruker feature finder seems to work, however, it produces an mgf file.
For now, there will be no support for QTOF data unless an external contributor steps in (Happy to guide through the codebase in case). Nevertheless, feel free to upvote on the discussions page so that we can track what features are considered relevant by the community: https://github.com/MannLabs/alphapept/discussions/314. If this will be requested by a lot of people, we can potentially prioritize it.
I will also note this on the compatibility in the Readme.
Thanks.


Fix Werror specification and fix unused variable.

Is there an equivalent of --per_file_copt=-external/.*@-Werror that we can use for CMake?

Thanks! I don't know how I missed this. I definitely had it working at some point and then must have accidentally deleted the "@"

Is there an equivalent of --per_file_copt=-external/.*@-Werror that we can use for CMake?

Yeah I think there is: https://stackoverflow.com/q/15133332

In file included from external/org_tensorflow/tensorflow/core/platform/logging.h:27:
external/org_tensorflow/tensorflow/core/platform/default/logging.h:392:9: error: 'CHECK_OP_LOG' macro redefined [-Werror,-Wmacro-redefined]
#define CHECK_OP_LOG(name, op, val1, val2)                     \
        ^
./iree/base/internal/logging.h:261:9: note: previous definition is here
#define CHECK_OP_LOG(name, op, val1, val2)                      \
        ^

oh :/

In file included from external/org_tensorflow/tensorflow/core/platform/logging.h:27:
external/org_tensorflow/tensorflow/core/platform/default/logging.h:392:9: error: 'CHECK_OP_LOG' macro redefined [-Werror,-Wmacro-redefined]
#define CHECK_OP_LOG(name, op, val1, val2)                     \
        ^
./iree/base/internal/logging.h:261:9: note: previous definition is here
#define CHECK_OP_LOG(name, op, val1, val2)                      \
        ^

oh :/

ARGH Tensorflow! Set -Wnomacro-redefined with an issue to fix this?

In file included from external/org_tensorflow/tensorflow/core/platform/logging.h:27:
external/org_tensorflow/tensorflow/core/platform/default/logging.h:392:9: error: 'CHECK_OP_LOG' macro redefined [-Werror,-Wmacro-redefined]
#define CHECK_OP_LOG(name, op, val1, val2)                     \
        ^
./iree/base/internal/logging.h:261:9: note: previous definition is here
#define CHECK_OP_LOG(name, op, val1, val2)                      \
        ^

oh :/

ARGH Tensorflow! Set -Wnomacro-redefined with an issue to fix this?

Done. Gets further in the build on my machine. We'll see if the CI is also happy.


ENH: stats.nbinom: consider n=0 to be in the domain

Describe your issue.
The negative binomial distribution with parameters n and p fails to calculate the pmf or cdf for the corner case when n=0.
The pmf is defined recursively as
$P(k+1) = \frac{(1-p) P(k) (n+k)}{k+1}$ where  $P(0) = p^n$
Thus if n=0 the pmf should give $P(0)=1$ and $P(k)=0$ for $k>0$ whereas
the scipy.stats implementation only returns NaNs.
Reproducing Code Example
import scipy.stats as ss
import numpy as np

ss.nbinom(n=0, p=1).pmf(np.arange(3))
ss.nbinom(n=0, p=0.5).pmf(np.arange(3))
ss.nbinom(n=0, p=0.1).cdf(np.arange(3))

Error message
array([nan, nan, nan])

SciPy/NumPy/Python version and system information
1.10.0 1.23.5 sys.version_info(major=3, minor=10, micro=9, releaselevel='final', serial=0)
lapack_mkl_info:
    libraries = ['mkl_rt']
    library_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\include']
lapack_opt_info:
    libraries = ['mkl_rt']
    library_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\include']
blas_mkl_info:
    libraries = ['mkl_rt']
    library_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\include']
blas_opt_info:
    libraries = ['mkl_rt']
    library_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\lib']
    define_macros = [('SCIPY_MKL_H', None), ('HAVE_CBLAS', None)]
    include_dirs = ['C:/Users/pab/AppData/Local/anaconda3_2023\\Library\\include']
Supported SIMD extensions in this NumPy install:
    baseline = SSE,SSE2,SSE3
    found = SSSE3,SSE41,POPCNT,SSE42,AVX,F16C,FMA3,AVX2
    not found = AVX512F,AVX512CD,AVX512_SKX,AVX512_CLX,AVX512_CNL

I looked at a few references. Do you have one in mind? Since this is an edge case and others have thought carefully about it, I think we should follow the recommendations of those who have thought more carefully about it.
Some define the distribution only for $n > 0$. SciPy's nbinom relies on Boost, which extends the definition to strictly positive $n$. This generalization is referred to as the Polya distribution. It looks like it can be extended to $n = 0$, and Mathematica does, although it is not totally consistent about it.

You can see that the PDF defined below has $P(X = x) = 0$ for $x \geq 0$, yet the plot shows that the value is $1$ at $x=0$.
![image](https://github.com/scipy/scipy/assets/6570539/ff05ed2f-cba5-4f49-9734-71920bc5fc81)
https://www.wolframalpha.com/input?i=NegativeBinomialDistribution[0%2C+0.5]
Also from their documentation of NegativeBinomialDistribution, they exclude the possibility of $n=0$:

My guess is that Boost chose not to provide a definition for $n = 0$. We can ask them to reconsider it, but it's not immediately obvious that it is incorrect not to define this distribution for $n=0$, so I'd consider this an enhancement (and maybe documentation) issue.

Most references seems to define the negative binomial distribution for $n>0$.
However, the moment generating function (MGF) for the negative binomial distribution is
$M_X(t) = \left(\frac{p}{1-(1-p) e^t}\right)^n$ for $t< -\log(1-p) $
and the MGF for the Poisson distribution is $M_Y(t) = e^{\lambda(e^{t}-1)}$
Now since $\lim_{n \to 0} M_X(t) = \lim_{n \to 0} \left(\frac{p}{1-(1-p) e^t}\right)^n = 1$ is equal to $M_Y(t)|_{\lambda=0} = e^{0}=1$
would suggest that the Poisson distribution with $\lambda=0$ is the limiting distribution of the negative binomial distribution as $n$ approaches zero. The pmf for the Poisson distribution with $\lambda=0$ is $P(0)=1$ and $P(k)=0$ for $k>0$

@rkern do you have an opinion about whether $n=0$ should be considered to be in the domain of the negative binomial/Polya distribution?

If we think about the definition in terms of successes and failures, we can get into trouble. For instance, MathWorld's definition, which leads to the formula given in SciPy's documentation, is:  You can see why it is problematic to talk about the probability of −1 successes in 0 trials and success on the 0th trial.

I don't see this as problematic. If you have zero ($x+r-1=0$) trials, you have zero ($x=0$) failures  and zero ($r-1=0$) successes , so logically the negative binomial distribution should give  $P(0)=1$ and $P(x)=0$ for $x>0$.

does scipy already have other distributions that allow for  parameters that result in degenerate (single masspoint) distribution?
binom ?
For discrete distributions it might be ok because we already have masspoints.
However, var -> 0 and skew and kurtosis divide by zero.
same if p -> 1

@pbrod The situation of 0 success and 0 failures in 0 trials makes sense. That corresponds with $r=1$; the success is on the first trial. That's not what my comment was about.
If you plug in $r=0$ and $x=0$, this corresponds with -1 successes in -1 trials, and success on the zeroth trial. How is that not problematic?

nbinom is defined by using gamma function and not choose.
We have an extension to continuous parameters.
n -> 0 works for n > 0, just plugging into current code (I'm currently still on scipy 1.7.3)

Yes, we're aware. The statement is about interpretation in terms of integer successes in failures.

that interpretation also doesn't work if we have e.g. n=1.5 or n = 10.8750674865375

But those are defined in a reference. $r=0$ is not, or if it is, that hasn't been presented yet.

I just did a google search and did not find anything for the degenerate case.
to the interpretation
wikipedia https://en.wikipedia.org/wiki/Negative_binomial_distribution#Alternative_formulations
has several interpretations
from nbinom docstring
"Negative binomial distribution describes a sequence of i.i.d. Bernoulli trials, repeated until a predefined, non-random number of successes occurs."
n is the required number of successes
if n=0, we stop after finding zero successes, i.e. we stop immediately, and then the number of failures k is also 0, i.e. single masspoint at zero.
the problem is that if both n->0 and p->0, then they go in opposite direction and it is not clear whether it collapses to the masspoint at zero, but p > 0 is required in code and docstring.

OK, I can see it making some sense according to that wording, although I would usually trust what I find on Mathworld more than SciPy documentation. Perhaps @ev-br has an opinion based on https://github.com/scipy/scipy/pull/6562? I don't mean to get in the way of others submitting/reviewing/merging PRs on this topic.

I don't think I've anything useful to say here, sorry.

Experimenting with the nbinom also indicates that the this is the correct limiting behavior of the negative binomial distribution as shown here:
>>> import scipy.stats as ss
>>> import numpy as np

>>> ss.nbinom(n=0.1, p=0.5).pmf(np.arange(3))
array([0.93303299, 0.04665165, 0.0128292 ])
>>> ss.nbinom(n=1e-10, p=0.5).pmf(np.arange(3))
array([1.00e+00, 5.00e-11, 1.25e-11])
>>> ss.nbinom(n=1e-250, p=0.5).pmf(np.arange(3))
array([1.00e+000, 5.00e-251, 1.25e-251])

>>> ss.nbinom(n=0.1, p=0.01).pmf(np.arange(3))
array([0.63095734, 0.06246478, 0.03401207])
>>> ss.nbinom(n=1e-10, p=0.01).pmf(np.arange(3))
array([1.0000e+00, 9.9000e-11, 4.9005e-11])
>>> ss.nbinom(n=1e-250, p=0.01).pmf(np.arange(3))
array([1.0000e+000, 9.9000e-251, 4.9005e-251])

>>> ss.nbinom(n=1e-250, p=1e-250).pmf(np.arange(3))
array([1.e+000, 1.e-250, 5.e-251])

>>> ss.nbinom(n=0.1, p=1).pmf(np.arange(3))
array([1., 0., 0.])
>>> ss.nbinom(n=1e-250, p=1).pmf(np.arange(3))
array([1., 0., 0.])

The negative binomial distribution is a special case of the Katz distribution. Commonly also known as the Panjer or
(a,b,0) class of distributions.
Katz studied the system of discrete distributions that satisfy the relationship
$P_K(k+1) / P_K(k) = \frac{\alpha + \beta k}{k+1}  \quad \text{for} \quad k = 0, 1, 2, \ldots \qquad (1)$
where  $P_K(0)=(1-\beta)^\frac{\alpha}{\beta}$, $\alpha \ge 0$ and $\beta<1$ and showed that there are only three solutions to Eq.1:
$\text{NegativeBinomial}(n=\alpha/\beta, p = 1-\beta) \quad \text{for} \quad 0< \beta < 1$,
$\text{Poisson}(\lambda=\alpha) \quad \text{for} \quad \beta = 0 $
or
$\text{Binomial}(n=-\alpha/\beta, p = \beta/(\beta-1)) \quad \text{for} \quad \beta < 0 $.
Katz originally truncated $P_K(k+j)$ to zero whenever  $\alpha + \beta k<0$. However Washburn (1996, 2006)) recognized that $-\alpha/\beta$
actually must be an integer greater or equal to zero for the Binomial case.
The moment generating function (MGF) for the Katz distribution is $M_X(t) = \left(\frac{1-\beta}{1-\beta e^t}\right)^{\alpha/\beta}$ for $t< -\log(\max(\beta, 0))$.
For $\beta \to 0$ it is interpreted as $\lim_{\beta \to 0}M_X(t)  = e^{\alpha(e^t-1)}$
Now for $\beta \ne 0$ the limit of the MGF as $\alpha$ goes to zero is $\lim_{\alpha \to 0} M_X(t) = \lim_{\alpha \to 0} \left(\frac{1-\beta}{1-\beta e^t}\right)^{\alpha/\beta} = 1$
For $\beta = 0$ the limit of the MGF as $\alpha$ goes to zero is $\lim_{\alpha \to 0, \beta=0} M_X(t) = \lim_{\alpha \to 0}  e^{\alpha(e^t-1)}=e^0= 1$
This result proves that the Katz distribution as $\alpha \xrightarrow[]{} 0$ is the same regardless of what the value of $\beta$ is.
Thus the pmf of the Katz distribution with $\alpha=0$  is $P_K(0)=1$ and $P_K(k)=0$ for $k>0$.
Consequently the negative binomial distribution for $n=0$ should have the same pmf, which supports the conclusion in
https://github.com/scipy/scipy/issues/18974#issuecomment-1655357122.

I thought I'd take another look here. The trouble before was the difference in the English definition of the distribution beween Mathematica, which I was citing, and SciPy.

Mathematica insists that the last trial is a success explicilty, and it phrases everything in terms of the number of trials $n-1$ before the last, so with $n = 0$ we start having to think about negative trials.
In SciPy's definition, the last trial is implicitly a success if trials are performed, but I don't think there is a problem if zero trials are performed.

I think SciPy's definition is valid, too, so I suppose I should roll with it rather than referring to Mathematica's.
With SciPy's wording, I think it makes sense that the number of failures before zero trials are performed is always zero and never a positive number; i.e. the PMF is a point mass with probability 1 at zero. Also, the limit of the PMF as n -> 0 seems to be defined and agree, and there is precedent for this behavior in R nbinom as mentioned in https://github.com/scipy/scipy/issues/18974#issuecomment-1653969196.
So I would be happpy to change the requirement that n > 0 to n >= 0 in the argcheck function so n = 0 would be included in the domain.
That said, there would be no immediate change in behavior because our PMF relies on Boost, and Boost's negative binomial PDF returns NaN at n=0. So if we wanted to see a change in behavior now, we'd need to make exceptions. We can do that within stats using _lazywhere, but that would introduce additional overhead in the calculation.
@steppi This issue proposes to define the PMF of the negative binomial distribtion with $n = 0$ successes as a point mass with probability 1 at $k = 0$ failures. I think this holds even for probability of success $p = 0$. Do you think this is something we would want to adjust in the wrappers, would you ask Boost for the change, or neither?

@steppi This issue proposes to define the PMF of the negative binomial distribtion with n = 0 successes as a point mass with probability 1 at k = 0 failures. I think this holds even for probability of success p = 0 . Do you think this is something we would want to adjust in the wrappers, would you ask Boost for the change, or neither?

If this is worth doing, my vote is for adjusting it in the wrappers. There's nothing wrong with Boost's convention, and it matches their documentation.
"For k + r Bernoulli trials each with success fraction p, the negative_binomial distribution gives the probability of observing k failures and r successes with success on the last trial. The negative_binomial distribution assumes that success_fraction p is fixed for all (k + r) trials."
It's also a lot easier in general for Boost users to write their own wrappers if they care about the r = 0 case, compared to adjusting a scipy distribution.

Right, I know that their documentation currently mentions that the trial ends with a success, and so the change would not be consistent with it as written. Of course, the existing documentation does not support non-integer n, either.
Ok, so we should not trouble Boost with this. I can say that I do not think it's worth changing in stats because it would add overhead in all cases to support this edge case. Your call @steppi whether it should be done in special.


[ERROR] CatalogController system-library [catalog] failed with : Clone failed: Cloning into 'management-state/catalog-cache/'... fatal: unable to access 'https://git.rancher.io/system-charts/': Received HTTP code 407 from proxy after CONNECT

What kind of request is this (question/bug/enhancement/feature request):
Steps to reproduce (least amount of steps as possible):
I'm trying to install rancher behind a proxy with authentication and SSL offloading and when I ran the command to deploy rancher on a RKE cluster I notice this errors in some of rancher containers:
helm command to install rancher:
./helm install rancher-latest/rancher
--name rancher
--namespace cattle-system
--set hostname=rancher-dev.icbc.net
--set ingress.tls.source=secret
--set proxy="proxystring"
--set noProxy="<IP_ADDRESS>/8,<IP_ADDRESS>/8,<IP_ADDRESS>/16,<IP_ADDRESS>/16"
--set tls=external
--set privateCA=true
Result:
Error found in some rancher container logs:
2019/06/19 16:02:42 [ERROR] CatalogController system-library [catalog] failed with : Clone failed: Cloning into 'management-state/catalog-cache/2284e9d6c1e82c5a56a5cb7c1d5c0144835734b1b66da6f75122d99c7989618f'...
fatal: unable to access 'https://git.rancher.io/system-charts/': Received HTTP code 407 from proxy after CONNECT
: exit status 128
Other details that may be helpful:
When I enter in the container I notice the variables are set:
root@rancher-7794977df8-wwhzn:/var/lib/rancher# env  | grep _PROXY
HTTP_PROXY=proxystring
NO_PROXY=<IP_ADDRESS>/8,<IP_ADDRESS>/8,<IP_ADDRESS>/16,<IP_ADDRESS>/16
HTTPS_PROXY=proxystring
But git is not working:
root@rancher-7794977df8-wwhzn:~# git ls-remote https://git.rancher.io/charts/
fatal: unable to access 'https://git.rancher.io/charts/': Received HTTP code 407 from proxy after CONNECT
Eventually the rancher console never get started and the installation keep stuck.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (HA):

docker.io/rancher/rancher                                   v2.2.4

Cluster information

Cluster type (Hosted):
Machine type (VM) and specifications (4 CPU/8GB RAM):
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-96.gitb2f74b2.el7.x86_64
 Go version:      go1.10.8
 Git commit:      b2f74b2/1.13.1
 Built:           Tue Apr  2 21:01:07 2019
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-96.gitb2f74b2.el7.x86_64
 Go version:      go1.10.8
 Git commit:      b2f74b2/1.13.1
 Built:           Tue Apr  2 21:01:07 2019
 OS/Arch:         linux/amd64
 Experimental:    false

Hi, try setting http_proxy and https_proxy info also for the nodes. It worked for me.

Hi there, yes the proxy is set on nodes too. I think this was a bug in version v2.2.3, mostly because I installed the version v2.2.4 and the problem is gone.

@gknepper Did you have this problem in the v2.2.4,I also have in this error during my installation for v2.2.4. Could you pls share me some info

I try to install the rancher(2.2.4) in HA。
However the cluster cannot be starting up.
The error logs below:
2019/07/22 10:27:47 [DEBUG] REST UPDATE apis/management.cattle.io/v3//catalogs/system-library
2019/07/22 10:27:47 [ERROR] CatalogController system-library [catalog] failed with : Clone failed: Cloning into 'management-state/catalog-cache/2284e9d6c1e82c5a56a5cb7c1d5c0144835734b1b66da6f75122d99c7989618f'...
fatal: unable to access 'https://git.rancher.io/system-charts/': Could not resolve host: git.rancher.io
: exit status 128
2019/07/22 10:27:49 [INFO] Received SIGTERM, cancelling
2019/07/22 10:27:49 [FATAL] leaderelection lost for cattle-controllers

@nuaaparnec Your error it is not the same as mine. Your's look more like a DNS/proxy networking issue. Mine was solved in the version 2.2.4.


can I only set one language in  SingleDateAndTimePicker ?

first of all, thank you very much for this great library.
I need to force to only use one language (only in Indonesian, not in English, french or etc) to be shown as day in the SingleDateAndTimePicker. I know the the language follows the language setting of the Android phone. but I need to only use one language in my app, no matter what the language of the user setting in their phone
can I do that ?
if I can set it using string.xml what is the name of the xml to access the month and day ?
Thanks in advance :)

case closed, if someone in the future need the solution,here is the answer for this: https://stackoverflow.com/questions/58705864/can-i-change-the-text-of-month-and-day-text-from-android-system


Provided Examples Not Working

Hi,
I downloaded the source files and ran the example/index.html locally and it did not load the menu at all when pressing the toggle button. Same thing happened when I tried the test/index.html example. The only example that actually works is the following hosted example: http://iamphill.github.io/Bootstrap-Offcanvas/example.html. Is there anything special happening with the hosted example?
Thank you very much for your help!

@alenb are there are errors in the console?

@alenb Did you also run bower install ?

I had this issue to.  It has to do with an incorrect path for loading jquery:
http://goo.gl/uAv0XQ

In that case, to run the example, you'll need to run bower install


No sensor data visible added for integration

Hi, hope this is the right place to ask questions about how to get this integration working...
Added all code files under custom_components/deltasol, restarted HA and added the -platform: deltasol sensor with ip, username and password.
In my traces I can see that communication with the KM2 is successfull and data is being retrieved:

However, I cannot find this data anywhere within HA.
When searching for entities containing 'deltasol' or even '0010', nothing shows up.
When looking into the integrations, deltasol is not visible. When I choose 'add integration' and select 'Resol KM1/KM2...', I get a popup 'This device cannot be added from the UI. You can add this device by adding it to your configuration.yaml'. Which I have done, otherwise it would not show up in the traces.
How do I get this data to show up in sensors/entities? What am I missing?

@ankohanse I suggest - unless done already - you enable logging to debug:
logger:
  default: warn
  logs:
    custom_components.deltasol: debug

and post your full logs filter over [custom_components.deltasol] this will permit to look into those logs.
On a side note, I used this plugin and it worked perfectly fine. I have re-written the module from scratch to work with UI based setup and I am in the process of publishing it to HACS. You can load manually and see if this works for you:
https://github.com/evercape/hass-resol-KM2
Good luck

@ankohanse go to settings in Home Assistant and select devices and entities, select entities and type deltasol in the search box. All your sensors will be shown there.
@evercape why forking and re-releasing instead of contributing here?

@evercape why forking and re-releasing instead of contributing here?

Didn’t fork. Used a different init method as I wanted to use UI and not YAML to setup.
So cannot do pull request.
Also I don’t have any devices other than KM2 to test. Have put all in documentation.
First time using python and GitHub so if you have any suggestions pls let me know. Was more like a learning project for me.
Thanks

You can also try to bring your improvements as pull requests 1 by 1. just as an idea. If you want to.

You can also try to bring your improvements as pull requests 1 by 1. just as an idea. If you want to.

Thanks, good idea. Will do that - but not all of them will work.
You opted for YAML setup, which is fine and works well, but I wanted to try devices. One of your users commented on this setup. I initially forked your complete project, and setup devices, but they are not supported unless you use config_flow. I posted a bit around this in community groups, big learning experienced for me.
The "improvements" that I point out in my documentation are as follows:

Setup via custom_flow using multiple steps
--> not possible to fork, as completely separate init method

Add port as connection detail
--> that I can add. Happy if I do?

Combine KM2 specific sensors into devices as suggested by https://github.com/dm82m/hass-Deltasol-KM2/issues/24
--> according to what I read in documentation and community groups, only works with custom_flow setup, not with YAML

Group sensors into 'useful' device sensors and less important diagnostics sensors
--> only works with devices, and they don't work with YAML setup.

Each sensor entity_id incorporate unique device name, yet presents friendly sensor name
--> that I can add. Happy if I do? Basically introduce the serial number of the device into sensor entity_id

Update of the full dataset of all sensors belonging to a KM2 device with single API call
--> I am not 100% sure if you do multiple API calls per sensor or not. When I re-wrote the component I first had too many calls. Can you pls confirm?

Sensors that are disabled are skipped for updates, same with sensors where the state value has not changed
--> Can do. Happy if I do a PR?

Present additional device specific attributes on each sensor
--> Can do, it's a minor thing on attributes. Happy if I do a PR on this?

Extensive debug logging (hopefully helpful to anyone going through the same learning curve as myself)
--> Maybe not that important as it was only relevant with the rather complex config_flow setup. I struggle at first, also first time doing python.

Adding translations
--> Want me to add that? I am German (but live in South Africa) and could happily add German as a language.

thanks for your feedback.
M

Thank you! Found them under Settings->Entities. I had been searching via Developer Tools->States and did not have a hit there. They got lost in the 500+ sensors in the list there and I must have completely overlooked them when scrolling through the list.
Part of the issue was that I was expecting sensors/entities to have 'deltasol' in their name, as that was what I configured in the 'Name' field in the config. However, it seems that that name is only used for the 'integration' field of the entities.
Problem of not using a prefix for each sensor is that they get lost and there is a huge chance of getting name conflicts on their sensor unique id with other integrations. For my system, I adapted your code so that each sensor is now prefixed with the name:
name=self.prefix + "_" + field["name"].replace(" ", "_").lower(),

with config.get(CONF_NAME) passed into DeltasolApi as self.prefix

No need for it. Unique id is a combination of ids the km2 provided. The naming of the sensor can be changed within Home Assistant.

The one thing I suggest looking into it is to maybe have the entity_id of the sensor incorporate the serial number of the device (and the unique_id as well).
Reason is that when you have multiple Resol devices in the network and within the same Home Assistance instance, there might be an issue with those IDs.
Possibly a use case scenario not relevant for most users that only have one Resol device, but for anyone with more than one such as an installer monitoring multiple client devices this could be helpful.
@dm82m let me know if you want me to do a pull request on this:

API: unique_id = self.device['serial'] + "_" + header["id"] + "__" + field["id"]
#CONF_SERIAL_IN_ENTITY: false as a configuration flag
If CONF_SERIAL_IN_ENTITY == True then Sensor Entity ID: serial+name


Added context to the plugin options

An unforeseen issue occurs when your webpack context has no JS files, needed to add an option to allow you to set your scss context separately.

:ok_hand:


Configurable TLS. closes #109

info in README

This looks great. I made some edits to the README text in ecd19257 let me know if there's any problems.

I saw your draft release notes, but they imply the current default version is PROTOCOL_SSLv23, but from the code it looks to me like it defaults to PROTOCOL_TLSv1 (I added something to that effect to the README as well).

The highest version can be enabled by settings METHOD_SSLv23. I explaind the setting instead of qoute it


Store keys in environment variables

To enhance security and maintainability, we need to store sensitive information such as API keys, database credentials, and other configuration secrets in environment variables instead of hardcoding them in the codebase.

@xeroxzen good call. Do you have specific hardcoded secrets in mind?

@terrameijar the one in the settings.py file or it's not important. Can't we use something like decouple or env variables to have it hidden?

@xeroxzen we can and we should! Please create a PR for it.


Update application dependencies

Compile against the Android API 23
Update grade tools to the version ‘1.3.1’
Update Android build tools to the version ’23.0.2’
Update Android support repository to the version ’23.1.0’

Merged


Automerge Pull Request via automated update from auto push

Scheduled updates from auto push

I've cleaned up the environments to remove the issue with the failing VRT tests. Closing this and we'll see if we can have the source op pick up the change tonight


Add Geo IP lookup based proximity matching

Would allow detecting possible alts on new cable connections

Not sure if this is a good use of our time. We should instead be looking at updating civ mods to our current server version.

It's at the lowest possible priority in our issue tracking https://github.com/orgs/CivClassic/projects/4


Logo competition

design and run the logo competition; obtain assignment of logo

CC Korea team has been planning to make a short announcement about the logo competition on its local  GS website (to be published tomorrow) with dates (May 11 to May 30) and without details about the process and prize. As Nanshil suggested earlier, our original plan is to use the process of the previous competitions and to add a public voting component to it.
But @janeatcc threw in a good idea about tying in MOMA and NP in the brainstorming doc. We'd happy to hold the announcement until we agree on the details.

Why don't you write to Jane and Jay to see if they have any specific ideas - I like the idea, but I can't think of anything more significant than mentioning them in the announcement.
We can copy whatever you put together on the HQ GS website - we should coordinate those two, to make sure they have the same information. Have you talked to Matt about what you're doing with your site?
Also - I'm assuming as well as publishing you were going to publicise to the affiliates? They need to be kept up with everything - normally we'd tell them in advance.

@jayaw what do you think?
I think mentioning them at the very least is important.
Maybe if we encourage them to do something akin to the NP's icon? or get build on that? Don't want to be too constraining though. Whatever guidelines @jayaw and @peterspdx develop should guide derivations in this competition

@jessicacoates Yes, our developer Youngtaek contacted Matt to see how the local GS website can be tied to HQ GS website and how we can coordinate the two.
The local GS site basically has only two features - email update sign-up and a notice that a logo competition will come up soon. We want to launch the website sooner than later to raise interest in public. How about locking down the application dates (say May 11 to June 1) now and deciding competition policies and rules by next week?

@janeatcc +1 to we should be careful not to be too constraining.

FYI, here's the original plan copied and revised from the last summit:

Application period: May 1 to May 31
1st round: GS organising team (HQ + CC Korea) select 10 designs
2nd round: CC affiliates select 5 designs
3rd round: Public voting
Prize: 500 USD

@jessicacoates did we use any voting tool in the past? CC Korea is looking into ways to incorporate a voting system into the Korean GS website (and attaching it to HQ GS website), and we won't have to if there is a tool we've used before.

Hi @soohyunpae @janeatcc @jessicacoates  - just speaking frankly from the get-go (and understand that I'm really not versed in the history of Global Summit organizing), based on my experience with logo competitions they don't usually operate efficiently or quickly, and sadly they're never really fair to good design or designers. They are definitely an option - so I'm not suggesting you rule them out - and in some situations they work well, for example when there is a large pool of folks interested in design or people who generally work on logos pretty regularly (this was the case in the Wikimedia space, where lots of people volunteers liked to design/sketch in that manner). If there's confidence that this kind of a community is standing by, then I'd say it's worth a shot, but given short timelines I'm not sure it would get you exactly what you need.
Another option is to reach out to one person who has interest/time/experience in visual identity/design who is within the community and ask them if they'd like to present an overall visual identity (because ultimately the logo is just one part of the system). They could make a few sketches, the committee could narrow it down, offer notes, and then get to a final design that works. This could be pro-bono work for any designer if they'd like a fun and meaningful way to build their portfolio. You could invite any interested parties to offer some rough sketch/idea rather than a final design (Which is more common in logo competitions).
Just wanted to share those perspectives at this stage if it's helpful. I'm happy to elaborate.
Either way, yes, you could mention the recent work from MOMA (Which is really just a recognition of the wonderful double-c logo and its associates) and Noun Project (which was their effort to develop a great concept that celebrates the CC logo). I suppose it could be something like "Creative Commons has a globally recognized and celebrated visual identity, and this is your opportunity to bring your creativity and skill to help us produce a unique identity for the global summit." And from there you could point to Noun Project's work as an example of a great exploration of the CC identity.
I know with Wikimania (Wikimedia's annual event) there is always an effort to create some kind of locally significant mark (http://commons.wikimedia.org/wiki/Category:SVG_Wikimania_logos). But not sure if that's the norm for the global summit. Certainly I can see how designers would be excited to tie together the locale and the CC identity.
I know that's a lot to process - hope it's useful, and forgive me if I'm stumbling over anything important.

Yeah, see nospec.com

@jayaw I think we've always seen the logo competition as a community development/involvement opportunity in the past, rather than being too worried about getting the best logo possible. We've usually got less than 20 entries (off the top of my head), most of which aren't great (there are some very different aesthetics around the world), but have been very happy with what we've ended up with (see the logos for the last Summits). I'd love to keep it unless we are particularly rushed or concerned about quality. Happy to be overruled by others, especially about the importance of getting just the right logo - does @ryanmerkley have an opinion?
@soohyunpae - assuming it does go ahead, I'm happy with the same process we did before. Though I'm surprised at the order of the voting - did we really do it that way? Who knew! I'm happy for you to work out the process - this one is your thing. For voting tools in the past, Chiaki set it up through her website the first year, and I'm sure there was something fairly easy online that Val etc found last year - maybe just facebook and email if you're not on that?

The logo competition website will be launched by the end of this week.
Here's a draft announcement for the website: https://docs.google.com/document/d/1L1uW30olOTa6MCZTdZcHya9DDuivuyfueOAgSJ4CGQ8/edit
Feel free to edit the text or add comments if you have any suggestion!

I edited and left a comment.  We have always required that all rights in the winning logo be assigned to Creative Commons, in consideration for the cash prize.  I don't see any reason to change that here.  Using copyright licenses for trademarks and logos (especially one that will almost assuredly use one of our protected logos such as the double-c in a circle logo) is not a good practice.  Let me know if you have questions or if you'd like to see the form assignments we've used in years past.

I appreciate that to some this make appear heavy handed, but it isn't, and nobody has objected but instead appreciate that logos are brand identifiers.  It should be treated as such.  We have liberal policies for reuse of the logos on our /policies page, and one item in the queue from our collaboration with jw has been to get these special logos up on a page somewhere with specific reuse permissions associated with them.  That's still a to-do.
And as for the difference and why that's relevant, see this FAQ:  https://wiki.creativecommons.org/FAQ#Could_I_use_a_CC_license_to_share_my_logo_or_trademark.3F

Ah, I see, thanks for the clarification Diane.
Paul
On Wed, Jun 3, 2015 at 6:15 AM, Diane Peters<EMAIL_ADDRESS>wrote:

I appreciate that to some this make appear heavy handed, but it isn't, and
nobody has objected but instead appreciate that logos are brand
identifiers. It should be treated as such. We have liberal policies for
reuse of the logos on our /policies page, and one item in the queue from
our collaboration with jw has been to get these special logos up on a page
somewhere with specific reuse permissions associated with them. That's
still a to-do.
And as for the difference and why that's relevant, see this FAQ:
https://wiki.creativecommons.org/FAQ#Could_I_use_a_CC_license_to_share_my_logo_or_trademark.3F
—
Reply to this email directly or view it on GitHub
https://github.com/creativecommons/global-summit-/issues/20#issuecomment-108402092
.

--
Paul Stacey
Associate Director of Global Learning
Creative Commons
<EMAIL_ADDRESS>State of the Commons Report https://stateof.creativecommons.org/report/
Get Creative Commons Updates http://bit.ly/commonsnews

Thanks @peterspdx
I revised the text as suggested. Can you please have a look at my comments in the document regarding the license/copyright agreement?
@mattl we're currently developing the logo competition website and hope to launch it by the end of this week (the competition starts on Monday, Jun 7 and ends on Jun 30 UTC.)
Please expect a pull request from @mozodev tonight and let us know whether it can be done by Friday. If it can't be done in time, we'd like to put it under CCKorea's domain. And a short announcement with a link to the logo competition webpage before Monday would be great.

@soohyunpae I checked the language in the document, and responded to your comment there.  To reiterate, I would prefer the logos that are not the winning logos be posted on our website or on CC Korea's website rather than to Flickr under a CC license.  See above response to pgstacey for why applying a (c) license to a logo is suboptimal.  I suppose that to the extent the logo doesn't include one of CC's protected marks, it's fine.  But I would strongly prefer any logos using ours not be CC-licensed for the reasons stated.

@mattl Can you add an announcement and a link to the logo competition page (http://logo.cckorea.org) to the summit website? Thanks!

Can we make some changes to that page?
First, let's not ask people to submit a JPEG, when a logo would look awful
in that format. A PNG will be better.
Second, let's not assume the world uses proprietary software. Let's ask for
submissions in an open format, like SVG.
Finally, we need to get that page under HTTPS. Happy to talk to whomever we
need to make that happen.

@mattl please review my PR https://github.com/creativecommons/global-summit-/pull/31
and done with https://logo.cckorea.org! Thanks!

All set and it's up on the site :)

Matt Lee
Creative Commons
Boston, MA, USA
On Wed, Jun 17, 2015 at 11:19 AM, Yeongtaek Hong<EMAIL_ADDRESS>wrote:

@mattl https://github.com/mattl please review my PR #31
https://github.com/creativecommons/global-summit-/pull/31
and done with https://logo.cckorea.org! Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/creativecommons/global-summit-/issues/20#issuecomment-112841853
.

I shared on Twitter (https://twitter.com/creativecommons/status/611585606083194881) and Facebook.


guestPolicy in create not passing to URL?

I've added the hooks to both the official bbb api and this to allow guestPolicy settings to be passed during the Create Room method.
Since it requires an update to the BBB api, should I just include the changes here for reference or make a pull request that can be merged when the API is updated? I haven't made a pull request there yet.
Thanks,
Dwayne

@code-by-dwayne pl make a pull request here

will do. Watch for it over the next week; have a bit of clean up to do, and I hadn't pulled since you did a commit the other day.


Christmas is Over

About the PR

Removes christmas stuff.
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl:

remove: Removed pirasmas, it's so over.

I thought christmas will end in 2025... We didn't celebrate New Year yet 😢

BUT THE NEW YEAR...

I couldn't stand my own update


nixos/mmsd-tng: init

Motivation for this change
mmsd-tng facilitates the sending and receiving of MMS messages through ModemManager and ofono stacks. It currently works with the chatty messaging application through the org.ofono.mms DBus service name. This PR adds a package for mmsd-tng, as well as a module that adds a DBus service definition and a user service.
Tested with chatty on a PinePhone Pro with mobile-nixos.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Closing, addressed by 15046139d5475a5fe285575f998698045c65cc06 and acac950ef6a5f74db4ff602d234676e644a48c32


Update Posts “a-post-with-figures-and-video”

Automatically generated by Netlify CMS

👷 Deploy Preview for wonderful-visvesvaraya-545eaf processing.
🔨 Explore the source changes: 5d609c3f6b94802b2bcf3414561591cda55218d9
🔍 Inspect the deploy log: https://app.netlify.com/sites/wonderful-visvesvaraya-545eaf/deploys/61608ecbaed9b6000781e22c


chore(i18n): fix and update CLDR to v30.0.1

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix, i18n update.
What is the current behavior? (You can also link to an open issue here)
Locale files based on CLDR 29 and broken i18n/ scripts.
What is the new behavior (if this is a feature change)?
Locale files based on CLDR 30.0.1 and working i18n/ scripts.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
Fixes #15976.

Do you know why the scripts broke? Because they must have worked before.
Could you also add the instructions for updating the CLDR files to the contributing.md?

I don't know why or when the scripts/tests broke. It is possible that someone run the node scripts directly from inside the i18n/ directory, instead of running the i18n/generate.sh script (which runs the tests and the node scripts).
There is a README.md inside i18n/ that explains what each script and directory is for.


Remove extra allOf keys in schema

Change Summary

The current implementation of schema returns multiple allOfs inside anyOf when Union is used in combination with Field. It will work fine with no Union which is what is currently included in all the tests.
To address the issue I only collect the referenced object when the schema is generated for a case with multiple sub-fileds and overwrite is True.
See #1209 for a more detailed explanation of the problem.
Related issue number
resolves #1209
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

thanks so much, great PR.

Thank you @samuelcolvin for merging the PR. Do you have any idea when will you package a new release with this fix? I'm wondering if we need to create a workaround on our side or if there will be a new release soon. Cheers. 😀

This doesn't really count as a patch to v1.5 since it's been this way for a long time.
I wouldn't normally create the next minor release for a month or so since v1.5 just came out.
So probably best to create your own work around using schema_extra. Let me know if that doesn't work for you.

That should work. We can have a workaround to post-process the generated OpenAPI file. We used schema_extra for simple cases but now we are dealing with more complex objects. We can remove the workaround once you release 1.5.2. Thank you for the quick response.


Font families: multi-variant font files are ignored

This is a bug with the new font families implementation in #879. If a font contains more than one variant (as is supported in newer versions of OpenType and TrueType), we only render the normal variant [1].
It's not really a bug with my implementation, but rather an oversight in the code that's existed for a while and only really became evident with this.
(Mostly) @bryphe and I did some investigation and found that, in reason-skia, we hardcode 0 as the index for all fonts, as seen here:
https://github.com/revery-ui/revery/blob/a525e7f07d1417791c6ac2b574ed7fb9e68ceaeb/src/Font/FontCache.re#L68
The documentation on that function is sort of iffy, but I think it refers to a VariationIndex in OpenType fonts, at least:
https://docs.microsoft.com/en-us/typography/opentype/spec/chapter2#device-and-variationindex-tables
I don't think reason-font-manager gives us the index, so we might have to either patch it in to do that, or ditch it entirely.
[1]: This is only kind of true: it's whatever variant is at index 0, since we hardcode that.

So cool that this works now!


Cache program output

As we don't allow networking or file writes, pretty much anything could be cached. We might of course search for exception (e.g. time if we can't fix this like on the GoTour, see below). The reason for this is obvious, most of the time the user directly click on run without changing the file, so spawning a new docker container and compiling the file just takes unnecessary time.
Btw citing from the GoTour.

In the playground the time begins at 2009-11-10 23:00:00 UTC (determining the significance of this date is an exercise for the reader). This makes it easier to cache programs by giving them deterministic output.

There already is a caching algorithm implemented for this purpose. I creates a hash of the source code and checks whether we already have compiled and run the example. But still, I'll leave this issue open because it is just a quick hack and should be re-visited and reviewed before a final release.


[LiveComponent] circular reference exception with nested component

Hi,
Since this commit, one of my nested component is not working anymore with a circular reference exception.
My nested component is called like this:
{{ component('article-list-item',{
    article: article
}) }}

'article' is build in the parent component and is an entity.
I configured the liveprops attributes like this :
    #[LiveProp(useSerializerForHydration: true, serializationContext: ['groups'=> ['article-list']], updateFromParent: true)]
    public Article $article;

The group 'article-list' is defined in my entity to avoid circular reference, but when debugging, the context seems to be ignored on calling AddLiveAttributesSubscriber->getLiveAttributes().
The exception stack trace
Symfony\Component\Serializer\Exception\
CircularReferenceException
A circular reference has been detected when serializing the object of class "App\Entity\Article" (configured limit: 1).

in vendor/symfony/serializer/Normalizer/AbstractNormalizer.php (line 200)
in vendor/symfony/serializer/Normalizer/AbstractObjectNormalizer.php -> handleCircularReference (line 155)
in vendor/symfony/serializer/Debug/TraceableNormalizer.php -> normalize (line 45)
in vendor/symfony/serializer/Serializer.php -> normalize (line 152)
in vendor/symfony/serializer/Serializer.php -> normalize (line 170)
in vendor/symfony/serializer/Normalizer/AbstractObjectNormalizer.php -> normalize (line 216)
in vendor/symfony/serializer/Debug/TraceableNormalizer.php -> normalize (line 45)
in vendor/symfony/serializer/Serializer.php -> normalize (line 152)
in vendor/symfony/serializer/Normalizer/AbstractObjectNormalizer.php -> normalize (line 216)
in vendor/symfony/serializer/Debug/TraceableNormalizer.php -> normalize (line 45)
in vendor/symfony/serializer/Serializer.php -> normalize (line 152)
in vendor/symfony/serializer/Serializer.php -> normalize (line 170)
in vendor/symfony/serializer/Debug/TraceableSerializer.php -> normalize (line 76)
in vendor/symfony/ux-live-component/src/Util/FingerprintCalculator.php -> normalize (line 49)
in vendor/symfony/ux-live-component/src/Util/LiveControllerAttributesCreator.php -> calculateFingerprint (line 80)
in vendor/symfony/ux-live-component/src/EventListener/AddLiveAttributesSubscriber.php -> attributesForRendering (line 89)
in vendor/symfony/ux-live-component/src/EventListener/AddLiveAttributesSubscriber.php -> getLiveAttributes (line 55)
in vendor/symfony/event-dispatcher/Debug/WrappedListener.php -> onPreRender (line 116)
in vendor/symfony/event-dispatcher/EventDispatcher.php -> __invoke (line 206)
in vendor/symfony/event-dispatcher/EventDispatcher.php -> callListeners (line 56)
in vendor/symfony/event-dispatcher/Debug/TraceableEventDispatcher.php -> dispatch (line 127)
in vendor/symfony/ux-twig-component/src/ComponentRenderer.php -> dispatch (line 105)
in vendor/symfony/ux-twig-component/src/ComponentRenderer.php -> preRender (line 58)
in vendor/symfony/ux-twig-component/src/ComponentRenderer.php -> render (line 51)
in vendor/symfony/ux-twig-component/src/Twig/ComponentExtension.php -> createAndRender (line 58)
in var/cache/dev/twig/84/8490c051c83aa9f0658111f825fb52ce.php -> render (line 74)
in vendor/twig/twig/src/Template.php -> doDisplay (line 394)
in vendor/twig/twig/src/Template.php -> displayWithErrorHandling (line 367)
in vendor/twig/twig/src/Template.php -> display (line 379)
in vendor/twig/twig/src/TemplateWrapper.php -> render (line 40)
in vendor/twig/twig/src/Environment.php -> render (line 280)
in vendor/symfony/ux-twig-component/src/ComponentRenderer.php -> render (line 61)
in vendor/symfony/ux-twig-component/src/ComponentRenderer.php -> render (line 51)
in vendor/symfony/ux-twig-component/src/Twig/ComponentExtension.php -> createAndRender (line 58)
in var/cache/dev/twig/e3/e38e0e52e30f6c3ad0aea4a4ca64d737.php -> render (line 91)
in vendor/twig/twig/src/Template.php -> block_main (line 171)
in var/cache/dev/twig/a4/a4677bb6829e0dc73909cbd81f897b4d.php -> displayBlock (line 82)
in vendor/twig/twig/src/Template.php -> block_body (line 171)
in var/cache/dev/twig/2b/2b5176e928a44eb9b7c91030db1285e2.php -> displayBlock (line 84)
in vendor/twig/twig/src/Template.php -> doDisplay (line 394)
in vendor/twig/twig/src/Template.php -> displayWithErrorHandling (line 367)
in var/cache/dev/twig/a4/a4677bb6829e0dc73909cbd81f897b4d.php -> display (line 49)
in vendor/twig/twig/src/Template.php -> doDisplay (line 394)
in vendor/twig/twig/src/Template.php -> displayWithErrorHandling (line 367)
in var/cache/dev/twig/e3/e38e0e52e30f6c3ad0aea4a4ca64d737.php -> display (line 48)
in vendor/twig/twig/src/Template.php -> doDisplay (line 394)
in vendor/twig/twig/src/Template.php -> displayWithErrorHandling (line 367)
in vendor/twig/twig/src/Template.php -> display (line 379)
in vendor/twig/twig/src/TemplateWrapper.php -> render (line 40)
in vendor/twig/twig/src/Environment.php -> render (line 280)
in vendor/symfony/framework-bundle/Controller/AbstractController.php -> render (line 242)
in vendor/symfony/framework-bundle/Controller/AbstractController.php -> renderView (line 253)
AbstractController->render('default/index.html.twig', array())
in src/Controller/IndexController.php (line 30)
in vendor/symfony/http-kernel/HttpKernel.php -> indexLocale (line 163)
in vendor/symfony/http-kernel/HttpKernel.php -> handleRaw (line 74)
in vendor/symfony/http-kernel/Kernel.php -> handle (line 184)
in vendor/symfony/runtime/Runner/Symfony/HttpKernelRunner.php -> handle (line 35)
in vendor/autoload_runtime.php -> run (line 29)

Am I doing something wrong or is it a bug ?

Hi there!
I expect to see a good number of messages similar to this for 2.8. In 2.8, we're a bit more restrictive about what you can have as LiveProps. That being said, you found the useSerializerForHydration stuff, which "nearly" gives you the 2.7 behavior. So, you're doing the right thing! Unrelated to this, I WOULD recommend storing scalar values whenever possible on LiveProp (or persisted entities) - e.g. passing the individual pieces of data into your embedded component instead of an unpersisted entity. But I don't really see a big problem with what you're doing.
About the bad behavior, indeed, looks like a bug - we actually serialize when trying to determine the "fingerprint" https://github.com/symfony/ux/blob/2.x/src/LiveComponent/src/Util/FingerprintCalculator.php#L49 - and that is new code. Let me check into fixing that.
Btw, do you need the updateFromParent? Removing that would fix this. You only need that if, when the parent changes the article object in some way, you want to force the child to re-render. If you tell me a bit more, there may be a better way to solve what you're trying. I have a similar parent-child component relationship for a ux.symfony.com demo - https://github.com/symfony/ux/blob/2.x/ux.symfony.com/src/Twig/InvoiceCreator.php
Cheers!

Ok, let's see! When you call:
{{ component('article-list-item',{
    article: article
}) }}

Are that article ALWAYS persisted? Or is it sometimes unpersisted? I realized I had thought that sometimes these were unpersisted. But re-reading your message, I'm not sure that's the case anymore.
If they ARE always persisted, then you shouldn't need to use the serializer at all your $article LiveProp is a persisted entity... so you can "do nothing" and LiveComponents will dehydrate this to its id for you.

The boxes are re-rendered when the sorting change on the list (doesn't work without updateFromParent). I could again use a scalar value between the list and the boxes, but I'm not sure it would change the result.

I'm not sure I totally understand the situation (are "boxes" referring to each "article list item" or are these form checkboxes?). But if the idea is that you need to "re-render" the article list when the sorting changes, then this should happen out-of-the-box. However, there is a 99% likelihood that you need to pass a key prop into each component:
{{ component('article-list-item',{
    article: article:
    key: article.id
}) }}

Ref: https://symfony.com/bundles/ux-live-component/current/index.html#rendering-quirks-with-list-of-embedded-components
What's likely happening is that LiveComponents can't tell the difference between the "first" and "second" articles in the list without this key. So when your list re-renders, live components thinks "Hmm, I see a first and second article, but children should render in isolation, so I will not overwrite what's already on the page". By adding the key, it will now see, for example, that "article id 5" was removed, so that child should be removed. And "article id 7" is new, so it should render that fresh.

@weaverryan
ok ! I updated to last commit, removed `updateFromParent, added the 'key' (didn't saw that last time I checked the doc) and it works fine now 🥳
Thanks for the help and quick fix.


Restrict scope of RDO above low speed levels

Transform types and prediction modes are currently all tested at all speed levels, which slows down every speed level considerably. With this change, speed levels 0-3 will test all prediction modes and transform types exhaustively, while higher levels will default to a smaller set of prediction modes and DCT transforms.

Encoding time (Q80): 1.205 -> 0.523

Please rebase.


Add More Default Values

When creating new buildings default values should be populated as follows:

Column
Default

addressable
Y

alteration year
NULL

condo flag
No or autopopulate based on BBLs

construction year
NULL

feature code
Building

geom source
Other(manual)

ground elevation
NULL

last status type
constructed

mappluto bbl
NULL

name
NULL

We can create complex attribute rules like the condo_flags if/then decision based another attribute using ESRI's Arcade scripting language.  However this requires editing in ArcGIS Pro and branch versioning, so this option will not work for us.
https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-attribute-rules.htm
We can also create defaults from templates in the desktop editing environment.  This requires maintenance by users, not in the database from what I can tell.  So not ideal.
https://desktop.arcgis.com/en/arcmap/10.7/manage-data/creating-new-features/setting-the-default-attribute-values-of-a-feature-template.htm
Standard attribute domains are the best option:
https://desktop.arcgis.com/en/arcmap/10.7/manage-data/geodatabases/associating-default-values-and-domains-with-tables.htm

Implement domain management code to allow a complete domain refresh like:

For each domain requested in this schema ("workspace")

For each domain expected on the feature class
Delete any existing domain of the same name
Create the domain as defined

For a given attribute on the feature class

"Remove Domain From Field" (this may have to happen before delete domain above)
"Assign Domain To Field"


Merge TLS certs

Describe the bug
The websocket reports the api.fdgt.dev cert when it should be reporting the irc.fdgt.dev cert.
Additional context
Add any other context about the problem here.
From Discord:

I'm also running into some SNI issue with the websocket library when trying to add support for this, will try to resolve tomo com.neovisionaries.ws.client.HostnameUnverifiedException: The certificate of the peer (CN=api.fdgt.dev) does not match the expected hostname (irc.fdgt.dev) - @Prodigy

Can confirm that this has been fixed

Hey @all-contributors, please add @iProdigy for reporting bugs.


Attachments improperly handling markdown files

When putting .md files into either a page.files folder or a files folder, they do not properly list or populate .md files despite useing pattern=".*" or pattern=".md"
Some specs:

Running on a mac high sierra OS
git clone https://github.com/vjeantet/hugo-theme-docdock.git themes/docdock on 5-23 to insure I'm updated to most recent changes.

I'm not expecting the md attachment to be rendered - but just to be reachable for download

Hi @aeckard87,
This sounds like a some mac OS feature? I am not sure what is page.files folder, but in generla in the Hugo enviroment you put .md files inside the content and build result is on the public directories.
I am guessing this is not really the docdock issue unless Hugo builds with this theme is somewhat inconsistend with other Hugo themes.

For files folder, and if it is a folder with _index.html you can have a look at my proposed patch here : https://github.com/vjeantet/hugo-theme-docdock/pull/162
And syntax should be : `{{%attachments title="foo" pattern=".*pdf"/%}}

I tested with some .md files (we are not using them for download). And everything is fine except you can't download them if they are .md. Works fine if you rename them .txtfor example.
I guess hugo makes a special case of .md files


Add jimm's components

Coverage remained the same at 28.334% when pulling d91c15c62d0a00babe00176a916833cedffd5d24 on calixteman:jimm into 2d3e77d3b8dd9d55bc87873c90a1d521ea2babd2 on mozilla:master.

@jmathies @overholt enabling the triage tools for you (Jim) would mean about 30 need info for all the components you are triage owner
maybe we should start with less components (or do delegate some of this work?)

@jmathies, we implemented a round robin for some components handled by Selena:
https://github.com/mozilla/relman-auto-nag/blob/master/auto_nag/scripts/configs/necko_round_robin.json
So we could do the same.

@calixteman could you please ignore widget gtk ?


Signing Up for Bento

Personally I think it's rude to require one to have a Google or Facebook account, or, for that matter, ANY account with another site to signup for a membership to a site.  I have a Google account, but if I signup using it, NOW GOOGLE KNOWS one other thing about me.  I don't have a Facebook account, but it's the same issue.  Why is Bento asking me to tell these organizations more about myself when IT'S NONE OF THEIR BUSINESS!  Please allow another way to sign up for Bento.

Is this a request for some other type of authentication? (OpenID/Verisign/other) Or is this a request for Bento to implement its own user and login system?


Allow custom calibration of angle

Hello sir hope you are well ! Sir I have an observation about your app in that it gives an offset of about 4 degrees from 0 while the watch is on a clearly horizontal and level surface. Knowing that readings may difer from watch to watch , how about you add an option for "Set as 0"? You place the watch on any surface and press this button and it reads that position as 0 and would then make all measurements relative to that, helpful for when you need to take measurements from awkward angles.
Hope you can think about this, thanks for all your good work!

tactix Delta

Thanks for the quick reply. Allow me to attach a short video to you where you can see how the slide leaning on the floor and left stationary behaves. The values also vary by one degree. Is there any way to calibrate it?
Thanks again

forerunner 935

Great app! Simple but effective. I had been waiting for it for 3 years. Is it possible to do the calibration? Thanks and congratulations


Add asyncio packager

This brings in the code from minecart, since the two share a fair amount
of code. The packager has been reworked to use asyncio.

Changes Unknown when pulling cad1dd877fc82ca54e7b48ef06847aeae26a80d0 on minecart into ** on master**.


add pattern descriptions and examples

I'm not sure we want to add this to the output directly, given that it will clutter it more than necessary.
Closes #12.

I guess it could be added to the output in case a --verbose flag is used. Or what were you thinking @hiqua ?

In that case I would add the information to the pattern classes directly, and remove the files I've added in the previous commit, so that we have all the information only once in the repo (and we don't parse the description json to export it again). Fine for you?

Done, see the new flag, and the output when you enable it.
Note that 05632895d6b0dc15c9ec284bb877020ce225f5cc is not really related to this PR, but it's small, and some of the tests that had to be updated for this PR wouldn't have required update if this commit had taken place earlier.

Can we omit the catIdToName part from the output?

Done.

I know that they are in the --help but sometimes it can still be helpful to add them to the README from my perspective.

I agree that we should list the main features in the README, however I don't think we should try and have the exhaustive list of options there, because it is bound to become outdated at one point, so it's better to refer to --help. I always prefer to have the information in one place, for many things, for this reason.
Either a potential user is looking into what's feasible, and then having a high-level description is better, either the user already has Securify running, in which case it's simpler to run with --help.


[SPARK-28357][CORE][TEST] Fix Flaky Test - FileAppenderSuite.rollingfile appender - size-based rolling compressed

What changes were proposed in this pull request?
SizeBasedRollingPolicy.shouldRollover returns false when the size is equal to rolloverSizeBytes.
  /** Should rollover if the next set of bytes is going to exceed the size limit */
  def shouldRollover(bytesToBeWritten: Long): Boolean = {
    logDebug(s"$bytesToBeWritten + $bytesWrittenSinceRollover > $rolloverSizeBytes")
    bytesToBeWritten + bytesWrittenSinceRollover > rolloverSizeBytes
  }

https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/107553/testReport/org.apache.spark.util/FileAppenderSuite/rolling_file_appender___size_based_rolling__compressed_/

org.scalatest.exceptions.TestFailedException: 1000 was not less than 1000

How was this patch tested?
Pass the Jenkins with the updated test.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12682/
Test PASSed.

Test build #107558 has started for PR 25125 at commit 46a29fe.

Test build #107558 has finished for PR 25125 at commit 46a29fe.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107558/
Test PASSed.

Merged to master, branch-2.4 and branch-2.3.

Thank you!


Add pump to SpringController / Pneumatic Spring plugin

Addresses #44 Pump command
Test with:
ros2 service call /pump_command buoy_msgs/srv/PumpCommand duration_sec:\ 10
Can turn off pump with:
ros2 service call /pump_command buoy_msgs/srv/PumpCommand duration_sec:\ 0
piston retracts ~2 inches per minute

[x] Add command service to SpringController
[x] Model pump in Pneumatic Spring plugin

@hamilton8415 I wasn't sure how much pressure the pump creates (I can see in some of the schematics, it's a linear actuator pump like a bicycle pump), so I picked a value above what I think the max pressure would be in the lower chamber, and then tuned the retraction to 2 inches per minute using the absement.


Support curly braces for defining "chunk options" in fenced code blocks of markdown documents

Rmarkdown (http://rmarkdown.rstudio.com/) enables creation of reproducible documents using R. The main deviation of Rmarkdown from CommonMark is the use of curly braces in the header of fenced code blocks to define options related to the rendering of the figure/table described in the chunk. It would be nice if VS Code does proper syntax highlighting of code blocks in Rmarkdown documents.

VSCode Version: 1.1.3

Example code block:

```{r include=FALSE, pdf.width=100px}
ggplot(foo, aes(x=bar, y=baz)) + geom_boxplot()
```

There are two parts to this:

Syntax highlighting of the codeblock in the editor
Correct rendering of the fenced code block in the markdown preview

I believe that both components should come from an extension rather than the core markdown extension.
For the syntax highlighting, take a look at https://github.com/mjbvz/vscode-fenced-code-block-grammar-injection-example
For the preview rendering, take a look at https://github.com/Microsoft/vscode/issues/22916


Register Form

Add in Register form Password comfirmation. many poeple talke me please confirme my password have write fast password.

Issue #2 is a feature to reset password which will roundabout solve not only this issue but also when users forget their passwords.


update CODEOWNERS, rename UsingMyGet.md to dailyBuilds.md

Description

Update CODEOWNERS for botframework-config, fix typo, add code owners
Rename UsingMyGet.md to dailyBuilds.md

Update it to reflect that npm has the daily builds under the next tag.

Pull Request Test Coverage Report for Build 169617

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.378%

Totals

Change from base Build 169605:
0.0%

Covered Lines:
15584

Relevant Lines:
17775

💛  - Coveralls


Update the values and functional iteration BBEs

Purpose
This PR updates the following BBEs:

values
functional iteration

Fixes https://github.com/ballerina-platform/ballerina-lang/issues/10840

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-0.990.0@f63c590). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             release-0.990.0   #12851   +/-   ##
==================================================
  Coverage                   ?   60.02%
  Complexity                 ?      659
==================================================
  Files                      ?     2068
  Lines                      ?   101741
  Branches                   ?    12953
==================================================
  Hits                       ?    61073
  Misses                     ?    35478
  Partials                   ?     5190

Continue to review full report at Codecov.

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


chroot: move to clap from getopts

Hey @sylvestre, implemented the basic structure with clap, however still need tests etc. I'll ping when you when it is ready to review.
Closes #1732

The clap part works fine and compatible with GNU's chroot, but i'm quite not sure how to properly test this.

did you try this?
it should simplify the code

Hmmm, sure, i can merge that with this line, since we have the exact logic below :+1:
    let newroot: &Path = match matches.value_of(options::NEWROOT) {
        Some(v) => Path::new(v),
        None => crash!(1, "chroot: missing operand"),
    };

Any changes needed on this @sylvestre?

Excellent, thanks :)


Fix Unity UI touchable "greedy" activation.

Physics-based touchables now have a broadphase that limits the number of
touchables that need to be examined for finding the closest one.
Unity UI touchables don't have such a broadphase test, so distances needs
to be checked against the touch distance as well, otherwise any UnityUI
touchable will activate if no other touchable is closer.

Fixes: #5217

/azp run


Add date field to published timeline item record

Add date field to published timeline item record

Added date field to item index record template


HSEARCH-4725 @ObjectProjection filtering (includeDepth, includePaths, excludePaths) to apply projection constructors down to a certain depth

https://hibernate.atlassian.net/browse/HSEARCH-4725
@marko-bekhta This will most likely conflict with the changes you're working on for https://hibernate.atlassian.net/browse/HSEARCH-4876 . Feel free to wait until your PR for HSEARCH-4876 has been merged before you review this; I'll rebase and handle conflicts.

Thanks! I addressed your comments and force-pushed.

So +3,401 −1,461 turned out not as scary as it seemed

Yes, turns out I was able to reuse most of the filtering we already had for @IndexedEmbedded. Which means that the implementation is much simpler, but also that I needed very little tests.

Merging 🎉