Fix WhatsApp count

Pre-flight Checklist
Please ensure you've completed all of the following.

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.

Description of Change
See https://github.com/ferdium/ferdium-app/issues/1182#issuecomment-1596060470

I’m changing the fix though, as I figured out another issue whilst testing (chat.muteExpiration) doesn’t always exist. Then I’ll bump the version number

Finally I will stick to chat.archive, it’s not outdated, it just doesn’t exist on some chats (as with chat.muteExpiration for that matter), and chat.isAutoMuted doesn’t tell the archived state of a chat. However I changed the condition so it won’t be a problem if one is undefined.

Finally I will stick to chat.archive, it’s not outdated, it just doesn’t exist on some chats (as with chat.muteExpiration for that matter), and chat.isAutoMuted doesn’t tell the archived state of a chat. However I changed the condition so it won’t be a problem if one is undefined.

@victorbnl
What happened to this? The code isn't using chat.archive anymore, and I have 6000+ unreads now 😂

That’s a lot! Could you go to the service developer console (by pressing Alt+Ctrl+Shift+I) into the “Application” tab, then expand “IndexedDB”, then “model-storage”, then “chat”, and look at some entries to see if they have muteExpiration and isAutoMuted attributes and check their values?

No problem.
I'm looking at some of the muted/archive groups I have and I see
{
  archive: true,
  //...
  isAutoMuted: false,
  muteExpiration: -1,
  //...
  unreadCount: 3123,
}

I think the muteExpiration: -1 is "infinite", i.e. when you tell it to never turn back on.
Perhaps the condition should be chat.muteExpiration !== 0

Yes, that has been dealt with in: https://github.com/ferdium/ferdium-recipes/pull/408 (recipe version 3.5.2).

Oh, perfect, thanks!


Add react-native support

RNAsyncStorage.js would not be necessary except for a bug discussed here (https://github.com/facebook/react-native/issues/9743) with AsynStorage

I think I'm going to try your branch in React native project.
Any specific things that I should do differently to make redux actions work? Any config changes, usage different than in readme, etc?

I can confirm that your branch works nicely in React Native. I might post some code snippets presenting usage if someone needs.
@Derenge However, I think that you should make react-native a peerDependency instead of a regular one. Listing it as peerDependency should prevent this bug: https://stackoverflow.com/questions/38689885/react-native-duplicate-module-naming-collision

Tengo ese problema con el repositorio de @Derenge
Ya intenté de todo pero no logré nada.
¿Me podrían ayudar?

@kylecorbelli - could you pls review and approve? Thanks


Redefinition of Modules compile error in Xcode 11.2

I'm getting compile errors when trying to build in Xcode 11.2, has anyone experienced this issue?

Hi @nschucky,
I'm not sure that we experienced such issue, will try and report back soon 😉

Hi, actually the current master is not compilable at least from different reason in Xcode 11.2, in Cartfile.resolved we depend on ReactiveCococa 10.0.0 which is not compilable with Carthage. I'll start a dependency update branch and close this issue when it is ready

Well after merging #37 which also contains Xcode version update, current master seems to work just fine.
git clone git@github.com:AckeeCZ/iOS-MVVM-ProjectTemplate
bundle install
bundle exec pod install
carthage bootstrap --platform iOS --cache-builds

The project seems to be compilable just fine.
Let us know if you run into any more issues 😎


make bot leave guild with id ""

i cant find something like this in the discord + docs. Maybe add something like this

Added


Created README.md

Please do not merge the pull request yourself but wait until the next class!

I will definitely try that game! I also like Mirvdijks idea, maybe you can move up and down levels depending on how you are doing and the score is depicted on the screen. When would the game be lost / won? Do you have a set number of lives or do you loose the game as soon as you got it wrong once?
In terms of your folder structure, maybe add an example.py file, that was a suggestion to me for people to check that they successfully installed your package. You are also currenlty missing an init.py and a setup.py file in your main folder.


feat(knn_config): support knn config in 2.x indices

Description

Adds support for knn configuration in index resource
Allows for other boolean settings in index resource

It appears from the test suite that other boolean settings such as load_fixed_bitset_filters_eagerly would also see issue without this feature. Please review for golang best practices/style as well. Thank you!
Issues Resolved
Closes: https://github.com/opensearch-project/terraform-provider-opensearch/issues/75
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Sorry, I was having some trouble with the linting but I think I got it

Hey @macohen the unit tests fail, can you please take a look ?
Error Unexpected differences in acceptance test HCL content formatting., AFAIK this error should fix when ran terrafmt fmt .
Ref: https://github.com/opensearch-project/terraform-provider-opensearch/blob/main/script/test-terraform-fmt
@bbarani

Hi @prudhvigodithi . Is there any action required on my part for now? The terramt fmt should be resolved from the maintainers' side?

Hey @mcarroll1 the fix should be part of the PR, can you please take a look at the error?
Unexpected differences in acceptance test HCL content formatting.
To see the full differences, run: terrafmt diff ./provider --pattern '*_test.go'
Error: Process completed with exit code 1.

Hi @prudhvigodithi . Is there any action required on my part for now? The terramt fmt should be resolved from the maintainers' side?

Hey @mcarroll1 the fix should be part of the PR, can you please take a look at the error?
Unexpected differences in acceptance test HCL content formatting.
To see the full differences, run: terrafmt diff ./provider --pattern '*_test.go'
Error: Process completed with exit code 1.

Ok, I believe I have resolved the terraform formatting issue

Hi @prudhvigodithi . Is there anything else that needs to be done for this PR?

Thanks @mcarroll1 LGTM, one qq, as shown in the example https://opensearch.org/docs/latest/search-plugins/knn/approximate-knn/#get-started-with-approximate-k-nn can we not configure the K-NN settings via the body example https://github.com/opensearch-project/terraform-provider-opensearch/blob/main/provider/resource_opensearch_index_test.go#L198-L212?  If so adding settings like index_knn_algo_param_ef_search and "knn.algo_param.ef_search" inside the body does it have a race condition? Just want to ensure the user just uses the direct terraform key-value pairs.
Thank you
Adding @bbarani @rblcoder @peterzhuamazon

@prudhvigodithi From the opensearch docs:

Settings and mappings that you specify directly in the create index request override any settings or mappings specified in an index template and its component templates.

I believe this should handle this case. Is this something we can create a test for?

Thanks @mcarroll1, I'm good, merging now.

This feature should be now in the v2.2.0 https://registry.terraform.io/providers/opensearch-project/opensearch/2.2.0, please check, thanks @mcarroll1 for you contribution.


WIP: iDRAC rescue after check-boot

UNTESTED
TASK [shared-labs-prep : Wait for iDrac to be responsive (check via --check-boot for Dell)]
task path: JetSki/ansible-ipi-install/roles/shared-labs-prep/tasks/main.yml:176
Thursday 14 January 2021  14:28:45 -0500 (0:00:03.000)       0:01:25.103 ******
FAILED - RETRYING: Wait for iDrac to be responsive (check via --check-boot for Dell) (20 retries left).
FAILED - RETRYING: Wait for iDrac to be responsive (check via --check-boot for Dell) (19 retries left).
changed: [scalelab.redhat.com] => (item=scalelab.redhat.com) => {"ansible_loop_var": "item", "attempts": 3, "changed": true, "cmd": "source /tmp/ansible.vp3iqpg8/.venv/bin/activate\n./src/badfish/badfish.py -u user -p  -i config/idrac_interfaces.yml -H mgmt-scalelab.redhat.com --check-boot\n", "delta": "0:00:02.771431", "end": "2021-01-14 19:29:55.600399", "item": "scalelab.redhat.com", "rc": 0, "start": "2021-01-14 19:29:52.828968", "stderr": "- WARNING  - Current boot order is set to: director.", "stderr_lines": ["- WARNING  - Current boot order is set to: director."], "stdout": "", "stdout_lines": []}
FAILED - RETRYING: Wait for iDrac to be responsive (check via --check-boot for Dell) (20 retries left).
FAILED - RETRYING: Wait for iDrac to be responsive (check via --check-boot for Dell) (19 retries left).
...
FAILED - RETRYING: Wait for iDrac to be responsive (check via --check-boot for Dell) (1 retries left).
failed: [scalelab.redhat.com] (item=scalelab.redhat.com) => {"ansible_loop_var": "item", "attempts": 20, "changed": true, "cmd": "source /tmp/ansible.vp3iqpg8/.venv/bin/activate\n./src/badfish/badfish.py -u user -p  -i config/idrac_interfaces.yml -H mgmt-scalelab.redhat.com --check-boot\n", "delta": "0:00:00.409627", "end": "2021-01-14 19:40:29.246018", "item": "scalelab.redhat.com", "msg": "non-zero return code", "rc": 1, "start": "2021-01-14 19:40:28.836391", "stderr": "- ERROR    - Failed to communicate with mgmt-scalelab.redhat.com\n- ERROR    - There was something wrong executing Badfish", "stderr_lines": ["- ERROR    - Failed to communicate with mgmt-scalelab.redhat.com", "- ERROR    - There was something wrong executing Badfish"], "stdout": "", "stdout_lines": []}
changed: [scalelab.redhat.com] => (item=scalelab.redhat.com) => {"ansible_loop_var": "item", "attempts": 1, "changed": true, "cmd": "source /tmp/ansible.vp3iqpg8/.venv/bin/activate\n./src/badfish/badfish.py -u user -p  -i config/idrac_interfaces.yml -H mgmt-scalelab.redhat.com --check-boot\n", "delta": "0:00:01.432019", "end": "2021-01-14 19:40:31.647463", "item": "scalelab.redhat.com", "rc": 0, "start": "2021-01-14 19:40:30.215444", "stderr": "- WARNING  - Current boot order is set to: director.", "stderr_lines": ["- WARNING  - Current boot order is set to: director."], "stdout": "", "stdout_lines": []}
changed: [scalelab.redhat.com] => (item=scalelab.redhat.com) => {"ansible_loop_var": "item", "attempts": 1, "changed": true, "cmd": "source /tmp/ansible.vp3iqpg8/.venv/bin/activate\n./src/badfish/badfish.py -u user -p  -i config/idrac_interfaces.yml -H mgmt-scalelab.redhat.com --check-boot\n", "delta": "0:00:01.264880", "end": "2021-01-14 19:40:33.894045", "item": "scalelab.redhat.com", "rc": 0, "start": "2021-01-14 19:40:32.629165", "stderr": "- WARNING  - Current boot order is set to: director.", "stderr_lines": ["- WARNING  - Current boot order is set to: director."], "stdout": "", "stdout_lines": []}
changed: [scalelab.redhat.com] => (item=scalelab.redhat.com) => {"ansible_loop_var": "item", "attempts": 1, "changed": true, "cmd": "source /tmp/ansible.vp3iqpg8/.venv/bin/activate\n./src/badfish/badfish.py -u user -p  -i config/idrac_interfaces.yml -H mgmt-scalelab.redhat.com --check-boot\n", "delta": "0:00:01.195218", "end": "2021-01-14 19:40:36.092651", "item": "scalelab.redhat.com", "rc": 0, "start": "2021-01-14 19:40:34.897433", "stderr": "- WARNING  - Current boot order is set to: director.", "stderr_lines": ["- WARNING  - Current boot order is set to: director."], "stdout": "", "stdout_lines": []}

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please select the appropiate options:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration:

Versions:
Hardware:

Checklist

[ ] I have performed a self-review of my own code
[ ] If a change is adding a feature, it should require a change to the README.md and the review should catch this.
[ ] If the change is a fix, it should have an issue. The review should make sure the comments state the issue (not just the number) and it should use the keywords that will close the issue on merge.
[ ] A change should not being merged unless it passes CI or there is a comment/update saying what testing was passed.
[ ] PRs should not be merged unless positively reviewed.

Does this fix the issue? You would still need to wait in some way for the node to be available after a racrest for the subsequent tasks isn't it?

Does this fix the issue? You would still need to wait in some way for the node to be available after a racrest for the subsequent tasks isn't it?

Dd all of these nodes that failed successfully get their redfish queues cleared in the previous task or was a racrest performed in 10_redfish_queues.yml?

Dd all of these nodes that failed successfully get their redfish queues cleared in the previous task or was a racrest performed in 10_redfish_queues.yml?

I ended up just temporarily disabling the clear job queue task 10_redfish_queue.yml
I'm not able to test this anymore, so you can close this.
diff --git a/ansible-ipi-install/roles/shared-labs-prep/tasks/main.yml b/ansible-ipi-install/roles/shared-labs-prep/tasks/main.yml
index 46f6c33..340f9fd 100644
--- a/ansible-ipi-install/roles/shared-labs-prep/tasks/main.yml
+++ b/ansible-ipi-install/roles/shared-labs-prep/tasks/main.yml
@@ -169,9 +169,9 @@

 - name: Dell Boot Order tasks (Dell)
   block:
-    - include_tasks: 10_redfish_queue.yml
-      with_items:
-        - "{{ dell_nodes }}"
+#    - include_tasks: 10_redfish_queue.yml
+#      with_items:
+#        - "{{ dell_nodes }}"


test/k8s: keep configmap across upgrade test

Since we have new options set for new Cilium installations those
might brake the connectivity when doing upgrades.
To ideally test an upgrade, we should keep the existing ConfigMap
from the previous the version.
Signed-off-by: André Martins<EMAIL_ADDRESS>

test-me-please

Coverage decreased (-0.01%) to 37.023% when pulling 0a6cd59ee741ad92aad7c137b0335c0de9ac4975 on pr/fix-upgrade-config-map into 7cfe6f238c5668ecf405ddeadeed52f67a3c9431 on master.

test-missed-k8s

test-focus K8sUpdates

test-focus K8sUpdates

test-focus K8sUpdates

test-focus K8sUpdates

test-me-please

Travis hit #11955

test-focus K8sUpdates

test-focus K8sUpdates

test-focus K8sUpdates

test-me-please

no need to re-rerun the CI since all tests have passed before pushing again to fix some typos.


Cannot reshape array

I'm trying to run a synthetic control model with my data and I'm getting the error message below. Can someone help me, please?
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\lib\site-packages\SyntheticControlMethods\main.py", line 333, in init
original_checked_input = self._process_input_data(
File "C:\ProgramData\Anaconda3\lib\site-packages\SyntheticControlMethods\main.py", line 175, in _process_input_data
control_outcome_all, control_outcome, unscaled_control_covariates = self._process_control_data(
File "C:\ProgramData\Anaconda3\lib\site-packages\SyntheticControlMethods\main.py", line 243, in _process_control_data
control_outcome_all = np.array(control_data_all[outcome_var]).reshape(n_controls, periods_all).T #All outcomes
ValueError: cannot reshape array of size 773 into shape (43,18)

The data I'm using has all the same length, so I don't have idea how to solve this.

I had the same issue, you should check that you have a record for each combination of unit and time period. If you have a unit without a record for a given time period, you'll get this.
Mine weren't complete, once I removed those units, it fully run


Suddenly stopped working

Was working fine a few hours ago to queue up some sells then I tried to go and put some buys in and check holdings and I get this output:

Reinstalled the Chase API and had the same result.

And now it spontaneously works again, so seems to be intermittent.

Can you get me a screenshot of what the browser looks like when it errors.
Aug 15, 2024 8:48:30 PM Akagui @.***>:

Was working fine a few hours ago to queue up some sells then I tried to go and put some buys in and check holdings and I get this output:
error.png (view on web)[https://github.com/user-attachments/assets/d28e4a19-0961-4725-8ebf-867925999cfe]
—
Reply to this email directly, view it on GitHub[https://github.com/MaxxRK/chaseinvest-api/issues/46], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AKZTL4QZKV5KWUC3K66TIQLZRVK65AVCNFSM6AAAAABMTGU7MKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3DSMRXGI3DKMA].
You are receiving this because you are subscribed to this thread.
[Tracking image][https://github.com/notifications/beacon/AKZTL4RKBI6RL43SHZAITHTZRVK65A5CNFSM6AAAAABMTGU7MKWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHJGLQ4JI.gif]

There is a problem where chase detects something and stops the website from loading for awhile in playwright. It will pop up and say something like. "this part of our website is not working right now." After a few hours, sometimes a day,  it will start working again. I have found that if I move to another computer it will usually work and then come back to the one I was on after awhile it will start working again. I do not really have a solution for this currently, and I am not sure how to come up with one.

It's odd because it seems to happen on certain accounts and not others. I'm trying to use it with 3 different user accounts. Now I got it to where it connects but it is spitting this error if I use a different account:

However if I use my primary account it seems to work as expected. So it seems like it may be something specific to the account itself.

I need a screenshot of the actual browser if possible.
Aug 16, 2024 5:59:39 PM Akagui @.***>:

It's odd because it seems to happen on certain accounts and not others. I'm trying to use it with 3 different user accounts. Now I got it to where it connects but it is spitting this error if I use a different account:
image.png (view on web)[https://github.com/user-attachments/assets/bea8de48-5ef2-45ff-bff4-feb15e97f24f]
However if I use my primary account it seems to work as expected. So it seems like it may be something specific to the account itself.
—
Reply to this email directly, view it on GitHub[https://github.com/MaxxRK/chaseinvest-api/issues/46#issuecomment-2294421715], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AKZTL4R6SO64SUDAJRITVXDZRZ75XAVCNFSM6AAAAABMTGU7MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGQZDCNZRGU].
You are receiving this because you commented.
[Tracking image][https://github.com/notifications/beacon/AKZTL4RCZHGTB5DNEKSSEG3ZRZ75XA5CNFSM6AAAAABMTGU7MKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUIYIMNG.gif]

Ok looks like it's the page that is rejecting it for that specific account. I have 3 accounts I'm using and 2 of them are working currently.

It is the correct credentials though because they work with the app and on the chase.com site when I type them in manually myself. Apparently python has some weird escape characters so it might be something like it is not pulling the whole password for some reason.

Hi, I'm having this issue as well and I'm curious if you found any escape characters that may be causing issues with the passwords? I'm not a python guy but I looked into it a bit and I can't discern much info out that is helpful to me.
I'm getting this error as seen in the Original Issue:
Logging in to Chase...
Error logging in to Chase: 'NoneType' object has no attribute 'keys'
Traceback (most recent call last):
  File "C:\Users\mark1\OneDrive\Documents\Dev\auto-rsa-main\chaseAPI.py", line 114, in chase_init
    account_ids = list(all_accounts.account_connectors.keys())
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'keys'

This worked one time for me yesterday, randomly and on a whim. I did get a push notif to my phone asking if I was trying to log in to Chase, I haven't received another one since.
Let me know if there is anything else I can provide you with to help. Thanks!

Looks like the problem was with the account. The credential were valid, however that particular web portal for Chase would reject them whereas the Chase.com main site and app would take them. I had 2 other accounts I was using and they were able to log in fine. Once I reset the password for the account then I was able to log in with it. It does seem to have a different authentication prompt though than the other 2 accounts and the bot doesn't recognize it so it has to be selected manually with the headless option disabled so you can see it in the browser.
It looks like this:

Whereas the prompt on the other 2 accounts appears like this:


avoid output directory on build.gradle

https://docs.gradle.org/4.0/release-notes.html#deprecations

it looks totally perfect :smile:


[wip] full connectivity driver

One significant change would be to use multiaddress instead libp2ppeer.ID in this PR as libp2p peer id cannot be used to connect to it, the whole multiaddress is needed. This also makes implementations in this PR not dependent on libp2p, just multiaddress.

So if I understand correctly you mean that the multiaddress should be communicated through discovery, thus it must be added to the address book too, right?


Full front-end date localization using  tags and moment.js.

Should fix #732.
I had to update the daterangepicker with a version that does not embed an old version of moment.js.
I added a PHPCI\Helper\Lang::formatDateTime method to create the  tags but I am not sure it belongs to that class. This helper creates the tag with a default text and the required attributes so it can get reformated with moment.js on DOMReady.
I think there is still an issue with locale and AJAX (i.e. when the project view is refreshed) but this is not specifically related to dates.

Please add test to check the tag creation function.


[FEATURE] Pull down on HomeScreen to refresh stats

Currently the stats are fetched automatically in a fixed interval. It will be nice if data can ve refreshed after pulling down action on HomeScreen.

For anyone who visits this issue in future, we are using this - https://reactnative.dev/docs/refreshcontrol


Build(deps): Bump @patternfly/react-tokens from 4.76.1 to 4.83.8 (#3896)

Pull request opened by the merge tool on behalf of #3896

Merged in 6308746ccc916901e3b790ffd8b57446eb54f9a0


Fluentd pod crashing on Zookeeper configuration update

Rancher versions:  05/03 master
Steps to Reproduce:
Intermittent issue. Configure a kafka logging target and save it. Next, try to update the settings and check the fluentd container logs
Results:
Fluentd logs:
2018-03-05 14:31:01 +0000 [error]: #0 unexpected error error_class=Zookeeper::Exceptions::ContinuationTimeoutError error="response for meth: :get_children, args: [0, \"/brokers/ids\", nil, nil], not received within 30 seconds"
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/zookeeper-1.4.11/lib/zookeeper/continuation.rb:117:in `block in value'
  2018-03-05 14:31:01 +0000 [error]: #0 /usr/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/zookeeper-1.4.11/lib/zookeeper/continuation.rb:107:in `value'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/zookeeper-1.4.11/ext/c_zookeeper.rb:231:in `submit_and_block'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/zookeeper-1.4.11/ext/c_zookeeper.rb:40:in `get_children'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/zookeeper-1.4.11/lib/zookeeper/client_methods.rb:69:in `get_children'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluent-plugin-kafka-0.6.6/lib/fluent/plugin/out_kafka_buffered.rb:112:in `refresh_client'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluent-plugin-kafka-0.6.6/lib/fluent/plugin/out_kafka_buffered.rb:189:in `start'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/compat/call_super_mixin.rb:42:in `start'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:165:in `block in start'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:154:in `block (2 levels) in lifecycle'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:153:in `each'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:153:in `block in lifecycle'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:140:in `each'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:140:in `lifecycle'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/root_agent.rb:164:in `start'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/engine.rb:274:in `start'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/engine.rb:219:in `run'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/supervisor.rb:774:in `run_engine'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/supervisor.rb:523:in `block in run_worker'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/supervisor.rb:699:in `main_process'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/supervisor.rb:518:in `run_worker'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/lib/fluent/command/fluentd.rb:316:in `<top (required)>'
  2018-03-05 14:31:01 +0000 [error]: #0 /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  2018-03-05 14:31:01 +0000 [error]: #0 /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  2018-03-05 14:31:01 +0000 [error]: #0 /var/lib/gems/2.3.0/gems/fluentd-0.14.25/bin/fluentd:8:in `<top (required)>'
  2018-03-05 14:31:01 +0000 [error]: #0 /usr/local/bin/fluentd:22:in `load'
  2018-03-05 14:31:01 +0000 [error]: #0 /usr/local/bin/fluentd:22:in `<main>'
2018-03-05 14:31:01 +0000 [error]: #0 unexpected error error_class=Zookeeper::Exceptions::ContinuationTimeoutError error="response for meth: :get_children, args: [0, \"/brokers/ids\", nil, nil], not received within 30 seconds"
  2018-03-05 14:31:01 +0000 [error]: #0 suppressed same stacktrace

Unable to validate due to #12366.

@moelsayed have you check the kafka you config before? You could use the kafka I send you yesterday. Just let me know if you need any help.

After reviewing the logging server configuration with @aiwantaozi, I was able to validate the fix and confirm logging target working as expected.


question about the page of A-Larger-App

In the following page
https://github.com/Day8/re-frame/wiki/A-Larger-App
It said to navigate

Your app-db could have :active-panel key containing an id for the panel being displayed.

But all panel has it's own db.cljs, such as panel1/db.cljs,  panel2/db.cljs,... panelN/db.cljs.
Then where should I put app-db? Should I create a key value for :active-panel on each panelN/db.cljs?

@wqhhust  you can't ask these sorts of questions here.  This is for issues.  Please ask your questions in one of the help forums. We have had this discussion before.

sorry, I have thought the wiki could be more clear to understand and raise it as an issue. Ok I will ask on some forum.

I want to ask this question too. And, Is there any forum for specially discussing re-frame?

@lhrkkk here's a list:  https://github.com/Day8/re-frame/blob/master/CONTRIBUTING.md#support-questions


Feat/virtual joystick

New feature added: Basic Virtual Joystick
Hi, I decide implement this feature because it appears to be in high demand. Hope you find interesting.
Description:

Joystick can be activated by button on bottom (see picture)
For resolutions less than 650px wide it's active by default
When resolution ir less than 650px and chat is active, joystick is hidden because it interferes with the chat

For implement this, I use this component: https://github.com/elmarti/react-joystick-component
Note: This feature will conflict with this PR:  #.62
I can take care of resolving conflicts
Related issues:

#.23
#.60

Hi there,
Firstly, I'd like to commend you on the initiative to add a virtual joystick feature to the SkyOffice project. This is a thoughtful addition, especially considering the demand for better mobile interaction and the challenges of navigating virtual spaces on smaller screens. Your effort to enhance user experience is much appreciated.
After reviewing the pull request, here are my thoughts and suggestions:
Code Organization and Clarity

The new files and components (Joystick.jsx and MobileVirtualJoystick.tsx) are well-organized and serve clear purposes. However, I noticed that Joystick.jsx is a .jsx file while the rest of the project seems to be using TypeScript (.tsx). For consistency and type safety, consider converting this to a .tsx file and adding appropriate type annotations.
The handleJoystickMovement method in MyPlayer.ts is a good addition. Ensure that it is well-documented so that future contributors understand how joystick movements are translated into player movements.

Consistency with Existing Codebase

It's great to see that you've integrated the joystick feature with existing components like MyPlayer and PlayerSelector. However, make sure that the joystick input is well-integrated with any existing input handling systems to avoid conflicts or unexpected behavior.

Responsiveness and UI/UX

The feature's responsiveness, activating by default on resolutions less than 650px wide, is a smart approach. However, it would be beneficial to test this across a range of devices to ensure a smooth user experience.
Regarding the UI, the joystick activation button's placement needs clarification. The PR description mentions a button at the bottom, but the code suggests it's part of the HelperButtonGroup. Please provide a screenshot or further details on the button's placement for a better understanding.

Potential Conflicts

You've noted that this feature may conflict with PR #.62. It's important to identify the specific areas of conflict and propose a strategy for resolution. If possible, rebase your branch onto the latest main branch and resolve any conflicts that arise. This proactive approach will facilitate a smoother merge process.

Dependency Management

The addition of react-joystick-component to package.json is noted. Ensure that this dependency is well-maintained and compatible with the project's existing dependencies. Also, consider if there are any potential security implications with this new dependency.

Testing

I encourage you to write unit tests for the new components and integration tests to ensure that the joystick feature interacts correctly with the existing game logic. This will help prevent regressions in the future.
Manual testing should also be conducted, especially to assess the feature's impact on the user interface and overall user experience.

Documentation

Update the readme.md file to include information about the new virtual joystick feature, how to enable/disable it, and any other relevant user instructions.
In-code documentation is crucial. Ensure that all new methods and components are well-commented, explaining their purpose and functionality.

Accessibility

Consider the accessibility implications of this feature. Ensure that users who cannot use the joystick due to accessibility reasons still have a way to navigate the virtual space effectively.

In summary, the virtual joystick is a valuable addition to the SkyOffice project. With some adjustments for consistency, thorough testing, and careful consideration of UI/UX and accessibility, this feature will significantly enhance the mobile user experience. Keep up the good work, and I look forward to seeing the refined implementation.
Best regards,
[Your Name]

test


Collision RectangularShape and RayShape don't work as expected

Godot version:
3.2
OS/device including version:
Windows 10, GLES3
Issue description:
If a Rayshape inside a KinematicBody is rotated even if by 1 degree it speeds up the KinematicBody for no reason
A Rectangular Collision Shape inside KinematicBody will not work properly with slide on slope, in this case this was tested colliding with a treadmill (staticbody with constant_linear_velocity set)
A Rectangular Collision Shape inside KinematicBody will not move with constant_linear_velocity set if we set stop on slope to true...
I have supplied a sample project with some combinations of raycast and rectangular shape interacting with a treadmill, both at 0 degree and at an angle, note that what I was hopping to achieve was a working collision using a rectangular shape
Any insight on how to workaround this issue?
Minimal reproduction project:
TestProject.zip

@Dr4kzor Please report one problem per issue. That been said, as far as I can see, everything is working as designed.

If a Rayshape inside a KinematicBody is rotated even if by 1 degree it speeds up the KinematicBody for no reason

RayShapes are designed to provide a collision normal in the opposite direction to the RayShape; instead of the normal of the surface it's colliding with. When you tilt the RayShape you create the same effect as a slope. You're KinematicBody is accelerating down this "slope".

A Rectangular Collision Shape inside KinematicBody will not work properly with slide on slope, in this case this was tested colliding with a treadmill (staticbody with constant_linear_velocity set)

When the KinematicBody collides with the tilted "Treadmill" it slides up. However, you're adding a large downward velocity on each step; so on the next iteration it will slide down, collide with the horizontal "Treadmill" and then slide along it. Note: The velocity of the "Treadmill" is subtracted from the velocity of the KinematicBody, but since it is less than the velocity of the "KinematicBody" it continues to move along it in the opposite direction, just slower.

A Rectangular Collision Shape inside KinematicBody will not move with constant_linear_velocity set if we set stop on slope to true...

You're specifically telling it not to slide on the "Treadmill"; so it doesn't. Note: stop_on_slope has no effect on RayShapes.
The only real issue is that stop_on_slope is not intuitive, but that is not a new issue.

Any insight on how to workaround this issue?

Please ask this question on one of the community channels.


Daemon status issue?

When i run god status, i see that all the daemons are up. However, for each of the daemons, I need to do a bundle exec command for them to actually work. For example, in order to get deposits working on an address, I had to run:
bundle exec ruby lib/daemons/amqp_daemon.rb deposit_coin
on a seperate ssh instance. I feel like this should not be required. Is there some better way of going about this, and is there a better way of ensuring these are being run properly besides god status, as that seems to tell me the all the daemons are up even when they do not seem to be functioning properly (like I said, deposits only work when I have the above command running separately)

Are you running on production env, or development env?
I had strage issues also, everything goes well when I develop on development mode except for withdraw. After I move to production env, I can't get deposit_address. It's so strage. There is specific command that I should to do?
Thanks

@zohair are u  run all  daemon in 1 server ? I mean all blockchain in 1 server ? If yes u need to separated some of them. Some of daemons wont works when other damons is active

If god status outputs «up» it means daemon works. If it works but nothing happens (like for deposit address) – check you configuration and do everything manually first. god works stable now and we use it in production more than 5 months so it seems like problem in your environment.
@candrawahyudi everything can run on single machine. I don't see any reasons for this not to work.
Double-check you configs please!


Code rewrite and update

Hello all, I would like to talk to one of the project maintainers.  I have some updated code I would like to share and discuss if wanted.  Its based upon this work, but i would like to show and discuss.

Typically wouldn't you just open a PR if you've already written the code?

Typically wouldn't you just open a PR if you've already written the code?

Typically I would, but I rewrote the whole thing from the ground using the lockmanager as a guide.  I didnt want to pr it, unless I actually had a conversation with someone as it may be quite difficult to read, and I am 99% done with the backend, but need to work on the frontend.  I didnt know if anyone was interested in a helping hand.  If you would like me to make a brach and pr it not a problem.  Thoughts?

Typically I would, but I rewrote the whole thing from the ground using the lockmanager as a guide.  I didnt want to pr it, unless I actually had a conversation with someone as it may be quite difficult to read, and I am 99% done with the backend, but need to work on the frontend.  I didnt know if anyone was interested in a helping hand.  If you would like me to make a brach and pr it not a problem.  Thoughts?

Oh I'm not a maintainer of this project, was just looking through the issues to try to find out why he moved to this repo from the old lock-manager repo if I could and saw this.

Oh I'm not a maintainer of this project, was just looking through the issues to try to find out why he moved to this repo from the old lock-manager repo if I could and saw this.

@ccsliinc hit me up on discord and I'll add you: raman325#4076

@ccsliinc hit me up on discord and I'll add you: raman325#4076

Oh I'm not a maintainer of this project, was just looking through the issues to try to find out why he moved to this repo from the old lock-manager repo if I could and saw this.

the latest version of HA does not support lock-manager because of the name. The project was renamed so it could continue to work. Functionally they achieve the same thing although there have been a lot of changes in the migration to make things more efficient

Oh I'm not a maintainer of this project, was just looking through the issues to try to find out why he moved to this repo from the old lock-manager repo if I could and saw this.

the latest version of HA does not support lock-manager because of the name. The project was renamed so it could continue to work. Functionally they achieve the same thing although there have been a lot of changes in the migration to make things more efficient

Thanks for that info @raman325! IMO it probably makes sense to put that in the readme of both repos

Thanks for that info @raman325! IMO it probably makes sense to put that in the readme of both repos


fix webmercator

Update ArcMap and Pro Addin in specific cases of checking for web mercator coordinates when all other types fail during parsing.

@dhagens please review and merge

Looks good


[HOTFIX] fix(openapi): fix the env of openAPI lint plugin

What changes were proposed in this pull request?

update redocly/cli version from 1.5.0 to 1.23.1
fixed the node version to 21.6.1
fixed the npm version to 10.2.4

Why are the changes needed?
redocly/cli failed at version 1.5.0
Does this PR introduce any user-facing change?
no
How was this patch tested?
build CI passed

I'm going to merge it first, to see if it works or not. We can have a follow-up fix if we figure out a root cause.


Storing module reference in module causes resolve to stack overflow (500USD Bounty)

From the maintainer Li Haoyi: I'm putting a 500USD bounty on this issue, payable by bank transfer on a merged PR implementing this.
The task is to appropriately detect module cycles during task resolution time, report a nice user-friendly error, and direct the user towards use of ModuleRef to fix the issue. This should be covered by unit tests, and we should verify that the module cycles in the code sample below gets properly recognized and handled.

I'm trying to work out a pattern that would allow the consumer of a foreign module swap out dependencies of modules.  Given the following module definition:
import mill._, scalalib._

trait CommonModule extends ScalaModule {
  def scalaVersion = "2.13.12"
  def m1 = mym1
  def m2 = mym2
}

object mym1 extends M1
trait M1 extends CommonModule

object mym2 extends M2
trait M2 extends CommonModule {
  override def moduleDeps = super.moduleDeps ++ Agg(m1)
}

One can then define another build.sc, import the above, instantiate new M1 and M2 (for example with new Scala versions), and then have the newly instantiated M2 depend on M1:
import mill._, scalalib._
import $file.dep.build

trait MyModules {
  def m1 = newm1
  def m2 = newm2
}
object newm1 extends dep.build.M1 with MyModules
object newm2 extends dep.build.M2 with MyModules

However this breaks resolve with a stack overflow error:
$ mill resolve __
No mill version specified.
You should provide a version via '.mill-version' file or --mill-version option.
Using mill version 0.11.12
[1/1] resolve
Exception in thread "MillServerActionRunner" java.lang.StackOverflowError
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.base/java.lang.Class.getClasses(Class.java:1752)
        at mill.define.Reflect$.reflectNestedObjects0(Reflect.scala:77)
        at mill.resolve.ResolveCore$.resolveDirectChildren0(ResolveCore.scala:349)
        at mill.resolve.ResolveCore$.$anonfun$resolveDirectChildren$3(ResolveCore.scala:300)
        at scala.util.Either.flatMap(Either.scala:360)
        at mill.resolve.ResolveCore$.resolveDirectChildren(ResolveCore.scala:295)
        at mill.resolve.ResolveCore$.resolveTransitiveChildren(ResolveCore.scala:223)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:229)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:228)
        at scala.collection.StrictOptimizedIterableOps.collect(StrictOptimizedIterableOps.scala:151)
        at scala.collection.StrictOptimizedIterableOps.collect$(StrictOptimizedIterableOps.scala:136)
        at scala.collection.immutable.HashSet.collect(HashSet.scala:34)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$2(ResolveCore.scala:228)
        at scala.util.Either.map(Either.scala:390)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$1(ResolveCore.scala:226)
        at scala.util.Either.flatMap(Either.scala:360)
        at mill.resolve.ResolveCore$.resolveTransitiveChildren(ResolveCore.scala:224)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:229)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:228)
        at scala.collection.StrictOptimizedIterableOps.collect(StrictOptimizedIterableOps.scala:151)
        at scala.collection.StrictOptimizedIterableOps.collect$(StrictOptimizedIterableOps.scala:136)
        at scala.collection.immutable.HashSet.collect(HashSet.scala:34)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$2(ResolveCore.scala:228)
        at scala.util.Either.map(Either.scala:390)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$1(ResolveCore.scala:226)
        at scala.util.Either.flatMap(Either.scala:360)
        at mill.resolve.ResolveCore$.resolveTransitiveChildren(ResolveCore.scala:224)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:229)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:228)
        at scala.collection.StrictOptimizedIterableOps.collect(StrictOptimizedIterableOps.scala:151)
        at scala.collection.StrictOptimizedIterableOps.collect$(StrictOptimizedIterableOps.scala:136)
        at scala.collection.immutable.HashSet.collect(HashSet.scala:34)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$2(ResolveCore.scala:228)
        at scala.util.Either.map(Either.scala:390)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$1(ResolveCore.scala:226)
        at scala.util.Either.flatMap(Either.scala:360)
        at mill.resolve.ResolveCore$.resolveTransitiveChildren(ResolveCore.scala:224)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:229)
        at mill.resolve.ResolveCore$$anonfun$1.applyOrElse(ResolveCore.scala:228)
        at scala.collection.StrictOptimizedIterableOps.collect(StrictOptimizedIterableOps.scala:151)
        at scala.collection.StrictOptimizedIterableOps.collect$(StrictOptimizedIterableOps.scala:136)
        at scala.collection.immutable.HashSet.collect(HashSet.scala:34)
        at mill.resolve.ResolveCore$.$anonfun$resolveTransitiveChildren$2(ResolveCore.scala:228)
        at scala.util.Either.map(Either.scala:390)
[...]

After experimenting around a bit, it seems like the def m1 and def m2 module references are somehow picked up as submodules and thus resulted in an infinite loop.  Wrapping the module references in Some(..) works just ok, however it's quite cumbersome to write and feels hacky.  Can this be fixed somehow?

Thanks for the report. This is expected but not ideal. The way to work around this is to wrap the reference in a ModuleRef, and we should try to detect these infinite recursions and provide a proper error message suggesting that

The proper way to refer to already existing modules is to use ModuleRef.
import mill._, scalalib._

trait CommonModule extends ScalaModule {
  def scalaVersion = "2.13.12"
  def m1 = ModuleRef(mym1)
  def m2 = ModuleRef(mym2)
}

object mym1 extends M1
trait M1 extends CommonModule

object mym2 extends M2
trait M2 extends CommonModule {
  override def moduleDeps = super.moduleDeps ++ Agg(m1())
}

@lihaoyi We already try to detect cycles in moduleDeps. Also detecting them for module references looks like the right thing to do. I assume, the resolver could maintain just a list of already seen/references modules and report when it detect a second reference.

Added a 500USD bounty if anyone wants to dig into this

I'm taking a crack at this.

I wrote the starts of two rudimentary tests. Although, I haven't made it much further. I was hoping to build something like ModuleUtils does but there's a pretty big fundamental difference.  For ModuleUtils's recursive method, there's an equality check that can be used between the dependencies to see if it's been seen before or not.
I could be wrong, but I think as ResolveCore is walking the graph, it's creating new objects through reflection.  Which raises a question I don't know how to answer:
How can I check if two of these modules are the same and not just named the same and the same class?

@myyk This is exactly the point where I stopped to investigate. Since this is reflection land, we can't know for sure whether the instance is meant to be a singleton.
So, best is to always stick to the rule to use a ModuleRef whenever we want to keep a reference to another modules and only hold it directly, if it is meant to be a real child object.

We could try to look for patterns though. E.g. whenever we instantiate a module, we could look into the chain of parents. E.g. if we find the the same types in a loop multiple times (e.g. 3x), we should at least print a warning. So when we later run into a StackOverflowError, it's last message Mill printed and should be as good as a good exception message.

I think during module resolution, if the recursion "stack" contains the same module class twice, that's probably a good enough signal that we should error. Note that most modules are singleton objects, so they have a more specific class than JavaModule, and basically all of them should be unique subclasses
Like @lefou suggests, we can probably say that all references to modules except their "primary" definition should be via ModuleRef, and therefore if during recursion we bump into the same exact class twice that should be grounds for raising an error

If I'm not mistaken, we also do materialize the concrete module objects as well at some point after traversing their classes/method-names. But this only happens after the stackoverflow has already occurred, and so it would not be useful for us to report errors at this stage

We do have objects in trait sometimes, which are valid child modules. So we need to be careful with errorring out just on heuristics.

We do have objects in trait sometimes, which are valid child modules. So we need to be careful with errorring out just on heuristics. I know we had it in ScoverageModule but changed to lazy val to be overrideable, but I seen it now and then in Mill and external projects.

Shouldn't those be wrapping those objects in ModuleRef?

We do have objects in trait sometimes, which are valid child modules. So we need to be careful with errorring out just on heuristics. I know we had it in ScoverageModule but changed to lazy val to be overrideable, but I seen it now and then in Mill and external projects.

Shouldn't those traits be wrapping those objects in ModuleRef?

Not if they meant to be concrete sub modules. object in traits are only singletons inside that scope. (Can't tell if they count as path dependent types, but kind of.)

We do have objects in trait sometimes, which are valid child modules. So we need to be careful with errorring out just on heuristics. I know we had it in ScoverageModule (inner scoverage data holder module) but changed to lazy val to be overrideable, but I seen it now and then in Mill and external projects. Bloop had some implicit inner object of the same type, and so on.

Ah good point, that makes it a bit trickier since they will have the exact same class even if they are different instances.
But even in that case, if the exact same class appears twice in the module stack during resolution, that is an indication that there is a loop in the resolution module graph, which is opens up the possibility of a stackoverflow. I think we should be able to safely disallow that and request that people use ModuleRef for such cases if they need references that do not convey a parent-child relationship

I've caught some of the cyclic graphs but I'm not sure if my changes catches all of them. I added these test graphs:
  object CyclicModuleRefInitError extends TestBaseModule {
    import mill.Agg

    // See issue: https://github.com/com-lihaoyi/mill/issues/3715
    trait CommonModule extends TestBaseModule {
      def moduleDeps: Seq[CommonModule] = Seq.empty
      def a = myA
      def b = myB
    }

    object myA extends A
    trait A extends CommonModule
    object myB extends B
    trait B extends CommonModule {
      override def moduleDeps = super.moduleDeps ++ Agg(a)
    }
  }

  object CyclicModuleRefInitError2 extends TestBaseModule {
    // The cycle is in the child
    def A = CyclicModuleRefInitError
  }

  object CyclicModuleRefInitError3 extends TestBaseModule {
    // The cycle is in directly here
    object A extends Module {
      def b = B
    }
    object B extends Module {
      def a = A
    }
  }

  object CrossedCyclicModuleRefInitError extends TestBaseModule {
    object cross extends mill.Cross[Cross]("210", "211", "212")
    trait Cross extends Cross.Module[String] {
      def suffix = Task { crossValue }
      def c2 = cross2
    }

    object cross2 extends mill.Cross[Cross2]("210", "211", "212")
    trait Cross2 extends Cross.Module[String] {
      override def millSourcePath = super.millSourcePath / crossValue
      def suffix = Task { crossValue }
      def c1 = cross
    }
  }

Can any of you think of any more test cases with cycles you'd like to see covered?

@myyk I think that looks great. You covered the three major cases I can think of: "vanilla" circular references, circular references through inherited traits, and circular references through Cross[T] modules


Impossible to implement certmagic.Storage interface while vendored

1. Which version of Caddy are you using (caddy -version)?

Building from source on 396d8e989ffdca4bb5aac2d01d5f4f48c44a6291
2. What are you trying to do?

I'm working on a Cluster plugin for etcd at caddy-etcd.  I can't build it with a vendored dependence on certmagic.  It's impossible to implement the certmagic.Storage interface because caddy main is referencing the vendored version which I cannot import.  This is likely related to #1697.
3. What is your Caddyfile?
paste entire Caddyfile here - DO NOT REDACT ANYTHING (except credentials)

N/A

4.

Add plugin import to run.go
Add to httpserver/plugin.go
Attempt to build
Throws /cluster.go:16:33: cannot use NewCluster (type func() ("github.com/mholt/certmagic".Storage, error)) as type caddytls.ClusterPluginConstructor in argument to caddytls.RegisterClusterPlugin
Delete vendored dependencies
Run go get -u
Build is successful when there is no vendored certmagic dependency

5. Please paste any relevant HTTP request(s) here.

N/A
6. What did you expect to see?

Successful build
7. What did you see instead (give full error messages and/or log)?

/cluster.go:16:33: cannot use NewCluster (type func() ("github.com/mholt/certmagic".Storage, error)) as type caddytls.ClusterPluginConstructor in argument to caddytls.RegisterClusterPlugin
8. Why is this a bug, and how do you think this should be fixed?

It's impossible for anyone to write a ClusterPlugin.  My etcd plugin works fine when I build without vendored dependencies.  I can do that for myself, but no one will be able to use it from the caddy buildserver.
9. What are you doing to work around the problem in the meantime?

There are a couple of possible fixes:

Re-export the certmagic.Storage interface in the caddytls package.  This doesn't work because the definition of the interface still references certmagic.KeyInfo which  if you re-export the KeyInfo in caddytls doesn't work.  It will always point at the vendored dependency.

Declare a new caddytls.Storage interface with a caddytls.KeyInfo with associated type aliases to the certmagic package.  That might work? I haven't tried it. (edit: thought of another option - change the certmagic.Storage interface to only return other interfaces instead of concrete types.  In other words, Stat should return an interface rather than a concrete type KeyInfo.  You could then re-export both interfaces in caddytls and it would probably work.)

Throw out vendoring and move to modules.  I was able to build caddy with modules but it requires at least one other package (quic-go) to move to modules or vendor that one dependency and do a mod replace.  It's complicated and might break a lot of other plugins.

10. Please link to any related issues, pull requests, and/or discussion.

#1697
Bonus: What do you use Caddy for? Why did you choose Caddy?

Using it for a side project and having etcd clustering is the first step towards the possibility of using it more easily with kubernetes as an ingress controller.  Right now I have it running under kubernetes as a proxy to my istio ingress controllers.

Honestly I'm leaning toward option 3 -- getting rid of the vendor folder and moving to modules -- to fix this and several other issues.
Unfortunately I won't be ready to do that today or tomorrow or next week, but it'll happen, hopefully right after the Go 1.12 release I'll get around to it. It'll require updating our build server, too, which is the main reason I can't do it right now...

No need to throw out vendor :-)
This works fine using vendor folder generated by go modules (using go1.11.5, no GOPATH set!)
$ git clone https://github.com/mholt/caddy
$ cd caddy
$ go mod init
$ vim caddy/caddymain/run.go # add _ "github.com/BTBurke/caddy-etcd" to run.go
$ go get<EMAIL_ADDRESS>$ go mod vendor
$ go build -mod vendor

The bifurcation is needed because of https://github.com/lucas-clemente/quic-go/issues/1788 (regardless of building with vendor or modules)

@42wim Awesome! Thanks for looking into that. That should buy us some time then. :)

Thanks @42wim.  That's one thing I didn't try.  I'll give it a shot and see if it works for me.  I guess that still doesn't solve the issue of publishing it as a public plugin, but I'll hold off on that until the build server works with modules.

(We no longer use vendor, so, closing.)


⚠ Bofrost.be has degraded performance

In 9cf575f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2371 ms

Resolved: Bofrost.be performance has improved in c0815b3.


Request for detailed instructions for submitting evaluation results to the leaderboard

Hi,
Thank you so much for your efforts in putting together the comprehensive benchmarks!
Could you provide detailed instructions for submitting the evaluation results? I obtained 16 *eval_results.json after evaluating through all the dimensions. But it seems that I cannot submit these individual json file to the leaderboard.
Thanks,
Jiachen

Hi, thank you for your interest in our work. Simply package the JSON file generated by VBench into a zip file and upload it directly.

Hi Yinan,
Thank you for your response. I tried your suggestion, but I'm still unable to upload the .zip file. Specifically, I zip all *eval_results.json into a .zip file before uploading it.
Can you look into the issue?

Hi Yinan,
Thank you for your response. I tried your suggestion, but I'm still unable to upload the .zip file. Specifically, I zip all *eval_results.json into a .zip file before uploading it.
Can you look into the issue?

Hi Yinan,
Thank you for your response. I tried your suggestion, but I'm still unable to upload the .zip file. Specifically, I zip all *eval_results.json into a .zip file before uploading it.
Can you look into the issue?

I apologize, we have just inspected the server and found that there was an issue with our processing logic. The problem has been fixed now, thank you for your feedback! Please note that you need to upload a zip file, and the first-level directory inside the zip should contain all the *result.json files. Do not modify the JSON content outputted by vbench. Don't worry about extra files in the zip, they will not be counted in the Leaderboard.

I just had another try, but I still failed to upload any files to the leaderboard. Could you take another look?

I just had another try, but I still failed to upload any files to the leaderboard. Could you take another look?

@Ji4chenLi  I noticed that T2V-Turbo (VC2) has been successfully submitted to the leaderboard, but only some dimensions have been submitted, is that correct?

The submission is actually not expected. I submitted one or two JSON files for debugging purposes but still failed to submit the entire zip file. If you have time, could you jump into a quick chat and fix the bugs? Or I can directly send you my zip file.

@ziqihuangg has  shared your zip file in the email. I have made the necessary code adjustments to accommodate this situation. Could you please try again?

Thank you, Yinan! My submission seems successful, but the Total Score, Quality Score, and Semantic Score are different from my calculation. I will look into it.

I might have found the bugs. The leaderboard somehow flips scores of aesthetic quality and dynamic degree of my model. As the dynamic degree uses a different weight (0.5) to calculate the Quality Score, my results end up to be lower than expected.
Could you please help me fix that? My model T2V-Turbo (VC2) should aesthetic quality = 63.04 and dynamic degree = 49.17.

Hi @Ji4chenLi , our calculation of total scores applies per-dimension normalisation and weighting. These constant parameters can be found here: https://huggingface.co/spaces/Vchitect/VBench_Leaderboard/blob/main/constants.py

Hi Ziqi,
I understand it. I have carefully followed your codes to do the calculation. The thing is that currently the aesthetic quality  and dynamic degree  of my model get flipped on the leaderboard, leading to worse Quality Score and Total Score of my model T2V-Turbo (VC2).

We've swapped the values of these two dimensions. Could you help check again, whether it's consistent with your results? Thanks!

It resolves my issue! Thank you!


Support waitFor and waitForTimeout

Adds support for waitFor and waitForTimeout:
htmlToPdf({
    waitFor: 'return window.pageLoaded === true;',
    waitForTimeout: 10000
});

waitFor is passed in as a string as it later gets JSON.stringified (and so passing in a function doesn't work).
Same improvement would need to be reflected in standalone script before release.

i think that waitForTimeout don't have so much sense since the process of rendering the pdf has a timeout.. two configurations for timeout is confusing (at least to me)
i have in mind another approach which don't relies in page.evaluate (so it don't evaluate the page each x time)
i will add my approach tomorrow and we can discuss with @pofider what will be the best way to handle this.

I figured it would be useful to have a separate timeout that doesn't take page load time into consideration. But happy for it to be removed.. simplifies things for now.
Would love to strip out the page.evaluate but didn't want to hack around with your code too much to achieve it :)

i sent my implementation.. would love to see your feedback

Closing - fails tests and #15 has an alternative implementation that meets our needs.
The polling approach used in this PR may be preferable for an 3rd party site (whereby you can't amend the JS directly).


generic type flutter problem

class MyController  extends GetxController {
static MyController  get go => Get.put(Hare2());
}
error-
Static members can't reference type parameters of the class.
Try removing the reference to the type parameter, or making the member an instance member.dart(type_parameter_referenced_by_static)

static MyController get go => Get.put(Hare2());
Everything is wrong, you are trying to insert a class that is not MyController as if it were MyController, you are using a getter to inject dependency. I am closing this issue because in addition to not being related to the package, it violates the main principles of OOP and dart conventions.
Please follow the documentation and make sure you saw a bug before opening an issue. Community channels are the ideal place for you to ask questions and learn from others. This space is only intended for bug reports.

please tell me can I achieve it any other way?


Example contains a missing path for the Get() decorator - causes a type error

Example should be updated to add a path string as an argument to the Get() decorator to avoid a type error:
import { Controller, Get, decorators } from "elysia-decorators";
import { Elysia } from "elysia";

// /users prefix
@Controller("/users/")
class UsersController {
  @Get("")
  index() {
    return "Hello World";
  }
}

const app = new Elysia();

app.use(
  decorators({
    controllers: [UsersController],
  })
);

app.listen(3000);

Additionally, the user will need to make sure to set "experimentalDecorators": true, in their tsconfig.json compilerOptions object to avoid a type error on the Controller() decorator argument.

Hi! sorry for the late response. Please open a PR

Can you open a PR for this?

Fixed


type: string doesn't work

plugins.env({
      file: '.env.json',
      type: string,
      vars: {}
    });

[11:49:18] Starting 'set-env'...
error with set-env:  ReferenceError: string is not defined

Documentation seems to be a liar, because supported types seem to only include .ini and .json


Add more filtering methods

By method:

Shake
Stirred
Build

By serving:

Up
Crushed ice

Would it be possible for filtering by primary alcohol (eg. Gin, Vodka, etc.). The only problem is that ingredients would then have to be able to be marked accordingly

Yeah, this is something I was thinking about. It's also possible to use cocktail_ingredient sort attribute and take the first ingredient as primary ingredient. I'll do some testing.
Thanks for contributing!


hlo_pb2

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf2.8
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
My program relies on a file such as hlo_pb2, which is imported from tensorflow.compiler.xla.service import hlo_pb2. This brings up a problem, I need to install tensorflow. But I don’t want to install the entire tensorflow when deploying. Is there any way to get hlo_pb2 by compiling certain files in xla?
Standalone code to reproduce the issue
I don't know how to do it, please help

Relevant log output
No response

Hi @never-to-never ,
You can use bazel build command some thing like bazel build //<target_file> then include it in your project. Please refer bazel documentation for more details.
Hope it helps. Thanks!


Modernize usage of attrs

I first established patterns to use with attrs in early 2020 using v19.3.0.  Since then, they've published a new, simplified interface and have changed their recommended design patterns.  This PR modernizes the code to follow the new recommendations when using v21.4.0.  (See the changelog.)
I followed the pattern established for apologies in PR #37.  The big lesson learned there is that we need to switch from cattrs.Converter to cattrs.GenConverter due to  PEP 563 (deferred) annotations.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

114 of 114 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 98.12%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
860

Relevant Lines:
871

💛  - Coveralls


Rename delete to deleteByBlah to align with getByBlahs

This is a continuation of #1235.

does this introduce breaking changes from beta3?
If so, pls use the compat-breaks tag and list the exact API changes in the PR comments.
For example, see: https://github.com/Azure/azure-sdk-for-java/pull/1140


[core] Aspect ratio is broken when drawing in 3d mode inside a RenderTexture2D

I use a RenderTexture2D to draw sphere and sprite at the same time.
BeginTextureMode(frameBuffer);
{
    ClearBackground(BLANK);
    DrawTexture(bg, 0, 0, WHITE);
    BeginMode3D(camera);
    {
        DrawSphereWires( sphereCenter1, 16, 8, 8,  (Color){80,104,155,255} );
        DrawSphereWires( sphereCenter2, 16, 8, 8,  (Color){80,104,155,255} );
        DrawSphereWires( sphereCenter3, 16, 8, 8,  (Color){80,104,155,255} );
    }
    EndMode3D();

    DrawTexturePro( ball,
        (Rectangle) {0,0,30,30},
        (Rectangle) {320+cos(2*sine)*192, 240+sin(2*sine)*192,30,30},
        (Vector2) { 15, 15},
        0, WHITE
   );
}
EndTextureMode();

All is correct.

But if i resize window and RenderTexture , i get this

The problem is : BeginMode3D()/EndMode3D() use screen size ratio instead of RenderTexture

@anatagawa This issue should be corrected with commit https://github.com/raysan5/raylib/commit/c200642887a8a5a4fd38168aee224dc9fc9906ab. Please, let me know if it works.

nice, it works fine now, thks :)

Nice! Closing the issue! :)


Deprecation request: RSpec::Matchers#be with no arguments

https://github.com/rspec/rspec-expectations/blob/master/lib/rspec/matchers.rb#L320-L322
https://github.com/rspec/rspec-expectations/blob/master/lib/rspec/matchers/built_in/be.rb#L104-L106
I think that the following:
expect(foo).to be

Should be deprecated, in favour of:
expect(foo).to be_truthy

The existence of the former has just caused me some pain, since someone had written the following test:
expect(json.size).to be      ## (they forgot to specify a number!!!)

- And the test was silently passing, despite testing nothing of any use! (They could have used eq rather than be, which would have immediately highlighted the problem, but oh well.)
Is there a genuine use case I've not thought of, or can we get rid of this argument-free signature of the method?

I've personally never been a fan of be w/ no args.  I think I'd be ok deprecating it (particularly if more people say they are in favor of this), but after going through the 2.14 -> 2.99 -> 3.0 release sequence and getting user feedback about the way we did deprecations, we're generally planning to hold off on issuing deprecation warnings until 3.99.  That's a long ways off so there's nothing to do here yet.
What do other @rspec/rspec devs think about this?

Strongly in favour of deprecation/removal of be with no args.

I'm also in favor of deprecating this. truthy seems like the way to go now.

I mentioned above that we need to hold off on issuing the deprecation warning until 3.99, which is true, but in the meantime we can update the docs to mention that this is deprecated.
@tom-lord -- want to take a stab at that?

@myronmarston sure, I'll put something together tomorrow :)

I'm on board with this, however I'm pondering if we should deprecate this in code, but have a config option that enables those deprecations e.g. config.verbose_deprecation which defaults to false, so that all we do in 3.99 is turn this to true by default for that release..

I'm on board with this, however I'm pondering if we should deprecate this in code, but have a config option that enables those deprecations e.g. config.verbose_deprecation which defaults to false, so that all we do in 3.99 is turn this to true by default for that release..

I think I'd be against adding that config -- after all, we already have 2 config options for deprecations:

deprecation_out can be used to pipe deprecations into a file (essentially enabling a non-verbose mode -- so this can be used as the inverse of your proposed option)
raise_errors_for_deprecations! -- this is like config.verbose_deprecation on steroids.  It makes deprecations really verbose.

Adding a 3rd way of controlling deprecation verbosity is overkill and confusing, IMO.

I was more thinking it'd be for our own benefit, we can work on deprecating things without bothering users until 3.99

Agree with Myron.

I agree with deprecating be. I'm on the fence about providing a method to show deprecations early.

I was more thinking it'd be for our own benefit, we can work on deprecating things without bothering users until 3.99

Honestly, seems like less work for us to simply punt on issuing deprecation warnings for now.  The YARD doc will have a @deprecated tag so when 3.99 comes around it'll be easy enough to simply search for all instances of deprecated to find what needs a warning.


contrib.batch_norm fails on float16 input

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
I have found a bunch of old issues dated from the initial implementation of float16, but nothing relevant.
Environment info
Operating System: FC21
Installed version of CUDA and cuDNN: CUDA8, CuDNN 5.1
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
/cuda8_cudnn5_1/lib64/libcudadevrt.a
/cuda8_cudnn5_1/lib64/libcudart.so -> libcudart.so.8.0
/cuda8_cudnn5_1/lib64/libcudart.so.8.0 -> libcudart.so.8.0.44
/cuda8_cudnn5_1/lib64/libcudart.so.8.0.44
/cuda8_cudnn5_1/lib64/libcudart_static.a
/cuda8_cudnn5_1/lib64/libcudnn.so -> libcudnn.so.5
/cuda8_cudnn5_1/lib64/libcudnn.so.5 -> libcudnn.so.5.1.5
/cuda8_cudnn5_1/lib64/libcudnn.so.5.1.5
/cuda8_cudnn5_1/lib64/libcudnn_static.a

If installed from binary pip package, provide:

A link to the pip package you installed: today nightly build
https://ci.tensorflow.org/view/Nightly/job/nightly-matrix-linux-gpu/TF_BUILD_IS_OPT=OPT,TF_BUILD_IS_PIP=PIP,TF_BUILD_PYTHON_VERSION=PYTHON3,label=gpu-linux/lastSuccessfulBuild/artifact/pip_test/whl/tensorflow_gpu-0.12.1-cp34-cp34m-linux_x86_64.whl
The output from python -c "import tensorflow; print(tensorflow.__version__)".

>tf.__version__
'0.12.head'
>tf.__git_version__
'0.12.1-2263-g4cc0d1e-dirty'

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
p16 = tf.placeholder(tf.float16, (4, 16, 16, 3))
bn16 = tf.contrib.layers.batch_norm(p16)

It fails with float32 to float16 conversion error deep inside BN op. Traceback is below.
What other attempted solutions have you tried?
For now working with float32. I tried to track where exactly it fails, but I couldn't. It looks like computed mean value is float32 by default although the variable itself should be inputs.dtype.base_dtype and tf.nn.moments returns float16 with corresponding input.
Logs or other output that would be helpful
ValueError                                Traceback (most recent call last)
<ipython-input-5-e659548f8d6c> in <module>()
----> 1 bn16 = tf.contrib.layers.batch_norm(p16)

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/contrib/framework/python/ops/arg_scope.py in func_with_args(*args, **kwargs)
    175       current_args = current_scope[key_func].copy()
    176       current_args.update(kwargs)
--> 177     return func(*args, **current_args)
    178   _add_op(func)
    179   setattr(func_with_args, '_key_op', _key_op(func))

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/contrib/layers/python/layers/layers.py in batch_norm(inputs, decay, center, scale, epsilon, activation_fn, param_initializers, updates_collections, is_training, reuse, variables_collections, outputs_collections, trainable, batch_weights, fused, data_format, zero_debias_moving_mean, scope)
    516           _scope=sc,
    517           _reuse=reuse)
--> 518       outputs = layer.apply(inputs, training=is_training)
    519
    520       # Add variables to collections.

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/layers/base.py in apply(self, inputs, **kwargs)
    301       Output tensor(s).
    302     """
--> 303     return self.__call__(inputs, **kwargs)
    304
    305

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/layers/base.py in __call__(self, inputs, **kwargs)
    271             self.build(input_shapes)
    272           self._built = True
--> 273         outputs = self.call(inputs, **kwargs)
    274
    275         # Apply activity regularization.

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/layers/normalization.py in call(self, inputs, training)
    191       if not self.updates:
    192         mean_update = moving_averages.assign_moving_average(
--> 193             self.moving_mean, mean, self.momentum, zero_debias=False)
    194         variance_update = moving_averages.assign_moving_average(
    195             self.moving_variance, variance, self.momentum, zero_debias=False)

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/training/moving_averages.py in assign_moving_average(variable, value, decay, zero_debias, name)
     70         update_delta = _zero_debias(variable, value, decay)
     71       else:
---> 72         update_delta = (variable - value) * decay
     73       return state_ops.assign_sub(variable, update_delta, name=scope)
     74

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/ops/variables.py in _run_op(a, *args)
    704     def _run_op(a, *args):
    705       # pylint: disable=protected-access
--> 706       return getattr(ops.Tensor, operator)(a._AsTensor(), *args)
    707     # Propagate __doc__ to wrapper
    708     try:

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/ops/math_ops.py in binary_op_wrapper(x, y)
    885     with ops.name_scope(None, op_name, [x, y]) as name:
    886       if not isinstance(y, sparse_tensor.SparseTensor):
--> 887         y = ops.convert_to_tensor(y, dtype=x.dtype.base_dtype, name="y")
    888       return func(x, y, name=name)
    889

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/framework/ops.py in convert_to_tensor(value, dtype, name, preferred_dtype)
    649       name=name,
    650       preferred_dtype=preferred_dtype,
--> 651       as_ref=False)
    652
    653

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/framework/ops.py in internal_convert_to_tensor(value, dtype, name, as_ref, preferred_dtype)
    714
    715         if ret is None:
--> 716           ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
    717
    718         if ret is NotImplemented:

/home/konstantin/.local/lib/python3.4/site-packages/tensorflow/python/framework/ops.py in _TensorTensorConversionFunction(t, dtype, name, as_ref)
    587     raise ValueError(
    588         "Tensor conversion requested dtype %s for Tensor with dtype %s: %r"
--> 589         % (dtype.name, t.dtype.name, str(t)))
    590   return t
    591

ValueError: Tensor conversion requested dtype float32 for Tensor with dtype float16: 'Tensor("BatchNorm/Reshape_1:0", shape=(3,), dtype=float16)'

Can confirm with CPU version too.

Well, I found a workaround for that one. I just modified BatchNormalization layer get_variable() calls to use dtype from passed initializers. Ugly, but worked. Btw, it is a regression from 0.12.0. I found a machine with that version that doesn't have this bug on python side.
However, the problem is much worse. Even when I make everything float16, it messes up somewhere deep in C++ code.
import tensorflow as tf
import numpy as np

slim = tf.contrib.slim

dtype = tf.float16
shape = (4, 16, 16, 3)

inpt = tf.placeholder(dtype, shape, name='input')
net = slim.conv2d(inpt, 16, [3, 3], scope='conv')
init = {'beta': tf.zeros_initializer(dtype), 'moving_mean': tf.zeros_initializer(dtype), 'gamma': tf.ones_initializer(dtype), 'moving_variance': tf.ones_initializer(dtype)}
net = tf.contrib.layers.batch_norm(net, param_initializers=init)

loss = tf.reduce_mean(net)
opt = tf.train.AdamOptimizer(1e-3)
train_op = slim.learning.create_train_op(loss, opt)

with tf.Session() as sess:
    sess.run(tf.global_variables_initializer())
    for i in range(2):
        val = np.random.randn(*shape)
        print(sess.run(train_op, feed_dict={inpt: val}))

with output
-0.00072765
Traceback (most recent call last):
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1022, in _do_call
    return fn(*args)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1004, in _run_fn
    status, run_metadata)
  File "/usr/lib/python3.5/contextlib.py", line 66, in __exit__
    next(self.gen)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/framework/errors_impl.py", line 469, in raise_exception_on_not_ok_status
    pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.InvalidArgumentError: LossTensor is inf or nan : Tensor had NaN values
         [[Node: train_op/CheckNumerics = CheckNumerics[T=DT_HALF, message="LossTensor is inf or nan", _device="/job:localhost/replica:0/task:0/cpu:0"](control_dependency)]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "test_bn.py", line 22, in <module>
    print(sess.run(train_op, feed_dict={inpt: val}))
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 767, in run
    run_metadata_ptr)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 965, in _run
    feed_dict_string, options, run_metadata)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1015, in _do_run
    target_list, options, run_metadata)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1035, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: LossTensor is inf or nan : Tensor had NaN values
         [[Node: train_op/CheckNumerics = CheckNumerics[T=DT_HALF, message="LossTensor is inf or nan", _device="/job:localhost/replica:0/task:0/cpu:0"](control_dependency)]]

Caused by op 'train_op/CheckNumerics', defined at:
  File "test_bn.py", line 16, in <module>
    train_op = slim.learning.create_train_op(loss, opt)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/contrib/slim/python/slim/learning.py", line 472, in create_train_op
    'LossTensor is inf or nan')
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/ops/gen_array_ops.py", line 433, in check_numerics
    message=message, name=name)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/framework/op_def_library.py", line 768, in apply_op
    op_def=op_def)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 2402, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/home/lear/kshmelko/.local/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1264, in __init__
    self._traceback = _extract_stack()

InvalidArgumentError (see above for traceback): LossTensor is inf or nan : Tensor had NaN values
         [[Node: train_op/CheckNumerics = CheckNumerics[T=DT_HALF, message="LossTensor is inf or nan", _device="/job:localhost/replica:0/task:0/cpu:0"](control_dependency)]]

So basically it breaks on the second step of SGD because loss is NaN. If I change dtype in float32, it works. If I remove conv2d call, it works. It should have nothing to do with CUDA because I tested it on the machine with old GPU it can not use.

close this one as it is resubmitted as another issue.

I resumbitted another thing that I detailed in the second message and then edited out. When I fixed this issue with BN (by manually editing my TF installation as I explained above in an unelegant way) I discovered another problem that firstly I thought also related to float16 and BN, but in C code. It turned out it wasn't linked to BN, so I resumbitted it in #7226.
Please reopen this one as it is still stands.

This indeed still stands, but it appears it's being addressed in https://github.com/tensorflow/tensorflow/issues/8535.


Migrate to staert

Hi everybody,
Here a PR to migrate from viper/cobra to staert/flaeg, tow very new golang packages to easily load and merge program configuration structures.
Flaeg uses StructTags and StructFields names to build a complete CLI. It loads values from command line flags into the configuration structure thank's to reflection. It handles initialized configuration structure, default value on pointers and sub-commands. For more information, please visit https://github.com/containous/flaeg
Staert is another package which allows to merge configuration structures from several sources like a Toml file or the Flaeg package. It handles all flaeg features.

Wating for https://github.com/containous/flaeg/issues/21
/cc @vdemeester can you review this one ?

Great job @cocap10 :+1:
LGTM!
/cc @vdemeester

LGTM 🐯
ETOOMUCHCOMMITS but I'll do :see_no_evil: for this one :joy_cat:


Fix MISSING REFLECTIONS

I think this is what is now wanted.  I guess this makes sense.  Seems a bit like unnecessary overhead to me.

coverage: 94.401%. remained the same
when pulling<PHONE_NUMBER>e9c656ed93278228481f161215ff3a on njw-missing-reflections
into dfa9ac66dac2e48134d911e0b50aae281c73cdb0 on main.

Actually, check_for_broken_references looks for belongs_to reflections.
For example, field slips must belong to a project and a user?  (Sorry, I've
been out doing fieldwork and haven't been able to keep up with your recent
work on field slips!)
At some point in the relatively recent past Nimmo added all of the missing
associations for all of the other models.  He can probably provide a better
defense of the policy.  But I think they are pretty lazy these days, and if
they aren't used, they incur very little cost.
But if you would prefer, feel free to alter check_for_broken_references.  I
think all we'd need to do is add these two associations  to the reflections
hash around lines 26-40, since they won't be picked up automatically by
searching for belongs_to relationships.  My intent here was to make it
automatically pick up new associations without requiring us to remember to
do anything.
On Sun, Mar 31, 2024 at 4:53 PM Nathan Wilson @.***>
wrote:

I think this is what is now wanted. I guess this makes sense. Seems a bit
like unnecessary overhead to me.
You can view, comment on, or merge this pull request online at:
https://github.com/MushroomObserver/mushroom-observer/pull/2083
Commit Summary

6174001
https://github.com/MushroomObserver/mushroom-observer/pull/2083/commits/6174001419e9c656ed93278228481f161215ff3a
Fix MISSING REFLECTIONS

File Changes
(3 files
https://github.com/MushroomObserver/mushroom-observer/pull/2083/files)

M app/models/project.rb
https://github.com/MushroomObserver/mushroom-observer/pull/2083/files#diff-611e7045e8b0212d101cd856c335296959519af63b80129f51c246a7bbfe7b91
(1)
M app/models/user.rb
https://github.com/MushroomObserver/mushroom-observer/pull/2083/files#diff-9802ca3c9c4cf89904fd44bc114e35ebdf2c5dd3d5b645491e2b253e1afef29b
(1)
M script/check_for_broken_references
https://github.com/MushroomObserver/mushroom-observer/pull/2083/files#diff-d0e2880c173d7bf9b32337714f4ab5cf8bdcd911c7ec973da02b89415f687f9a
(3)

Patch Links:

https://github.com/MushroomObserver/mushroom-observer/pull/2083.patch
https://github.com/MushroomObserver/mushroom-observer/pull/2083.diff

—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/2083, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNKRSTDVPKJ2EYBOXSLY3BZWBAVCNFSM6AAAAABFQWITS6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTOMJXHA2TOMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

It already had the belongs_to relationships.  I added the corresponding has_manys (although nothing uses them), but that didn't fix the issue.  I finally got them to go away by adding the rows to script/check_for_broken_references.  I don't understand the purpose here well enough to have more opinion about it.

@JoeCohen Thanks for pointing that case out.  I think I've fixed it up so it will work better in that case.  As you suggest I would want the field slip to continue to work.


fixed MD to SHA-256 and RSA-2048 Pubkey; Fixed log delimiter char to .

This patch fixes the Message Digest to SHA-256, a requirement for modern browsers.
It also ups the keysize to 2048, as some systems will require this larger key size to be considered secure.
It also includes a str replace function that modifies the : (which is an invalid char on windows) to a . allowing the log files to be readable from any OS.

This pull request is bad ;-( It introduces a memory leak in strdup :-(

closing pull until i can fix memory leaks

closing

Can you make your changes against the develop branch? I believe that some of your changes are already implemented there. Also, please submit separate pull requests for each functionally independent changeset, that makes it easier to process them.

Hi Daniel!
No problem! The match message digest functionality exists in develop ( i
have started to use this myself ) so no need to change this.
I notice that the : char is already changed to , in develop too -- this
helps with non unix filesystems.
Currently the app hardcodes the RSA keysize to 1024 bit, I will have a play
to make this a command line argument as many bumping examples require
larger keysize.
Original this patch was for some functionality I needed last year, im happy
to help contribute to develop.
Thank you for your project, it has made life much easier!
Thanks,
Philip


Let blockquote float right with 100% width

This fixes logos overlapping the blockquote box.

I just realized that this change crumbles the last paragraph. I'll fix this asap.

I moved the latter paragraph "The complete statement..." up and set a cumulative width for the block-quote on desktop screens (so that we don't generate unnecessary white-space.)

Next to our home page, the press release (/News/pr20210713.html.(en|de)) also uses block quotes -- please double check that these continue to look reasonable. Thanks in advance!

Next to our home page, the press release (/News/pr20210713.html.(en|de)) also uses block quotes -- please double check that these continue to look reasonable. Thanks in advance!

Thanks for the hint! As the width is fixed to 100% (beside the classes quote-gaia-x and quote-bmwi on desktop screens), the new style definitions don't change anything to the look of the press release.

Thanks for checking!


Add -V|-version to print sbtVersion.

Closes https://github.com/sbt/sbt/issues/4833
Add -V|-version as a shortcut print sbtVersion.
It will print the single line [info] 1.2.8 or similar.
Not tested yet due to #275.

Integration tests can be written here - https://github.com/sbt/sbt-launcher-package/blob/master/integration-test/src/test/scala/RunnerTest.scala

Travis/Appveyor does not report 🤔

https://travis-ci.org/sbt/sbt-launcher-package/jobs/560760471


Unable to login on HTC One X

Hi,
I am using my HTC One X with Android 4.0.3 installed to connect to the website but I am unable to login as the BrowserID popover dissapears ubove the top of the screen and I am unable to click on the BrowserID button to login.
Let me know how I can help debug this.

Closing as I don't use this anymore


Testing filter section (left panel) on gene-expression

Write test to verify the filter functionality for  Dataset, Disease, Self-Reported Ethnicity and Sex.
Test details:
https://docs.google.com/spreadsheets/d/1Ckv8741Ygxj-mcmDN1NosfmYvZWD3T1e6p1Y0CY--tA/edit#gid=0

Thanks for the headsup, Alec!
I just added test details link to the description, I think Victor will likely just add more test steps in our existing tests to match what products do, so they don't have to manually test anymore!


postgres case insensitive column names

Postgres columns always seem to be created in lowercase. Saving the data works without any problems. But when reading you get the column names in lowercase.
Example:
recordedOn => recordedon
There is then an error when accessing the array. Another field is also affected: aggregateId.
The solution would be to create the columns in lowersnakecase. But that would be a BC break because you would have to adapt the scheme.
Otherwise you would have to fix the data in the store so that the data can be loaded from Postgres.

Since this is a bug i wouldnt mind having a bc but the should first check if the get this fixed without bc

looks like we can fix this with adding this condition in normalizeResult
        if (isset($result['aggregateid']) && isset($result['recordedon'])) {
            $result['aggregateId'] = $result['aggregateid'];
            $result['recordedOn'] = $result['recordedon'];

            unset($result['aggregateid'], $result['recordedon']);
        }

for the 2.x release, we should change the schema to snakecase


Vitepress dependency outdated

I noticed when loading a page like https://alfred-skyblue.github.io/vue-draggable-plus/en/ the page does not load properly, even though that is the correct url, which can you get to by switching to English using the language switcher.
I was able to resolve the issue locally by simply upgrading vitepress to 1.0.0-rc.20 and vue to 3.3.4. However, the website seems a bit broken, the language switcher at the top right no longer exists, seemingly because the vitepress i18n api changed: https://vitepress.dev/guide/i18n#internationalization. I could not fix those because vitepress was still sort of using an older version, since @ruabick/md-demo-plugins also depends on an older vitepress version: https://github.com/dewfall123/ruabick/issues/36.

https://github.com/Alfred-Skyblue/vue-draggable-plus/issues/59#issuecomment-1822330517


[BUG]The temperature tuning in the openAI LLM node with the arrow button can't stop

Describe the bug
The temperature tuning in the openAI LLM node with the arrow button can't stop
To Reproduce

Create an open LLM node
click the arrow button in the temperature attribute
The increasing/decreasing of the temperature can't stop

Expected behavior
The temperature will be increased or decreased by a small value and stop.
Screenshots
https://github.com/FlowiseAI/Flowise/assets/61750044/66be8261-5176-4f5b-8130-3539492707f3
Flow
The number of temperature increases/decreases by 0.1 per click
Setup

Installation without docker
Flowise Version 1.2.12
OS: macOS
Browser chrome

Additional context

wow that's quite a bug! thanks for spotting that, will put up a fix!

issue now fixed and pushed to v1.2.14