Documentation is outdated

The last build for Read the Docs was almost a year ago.
Possibly due to the project repository still being https://github.com/isagalaev/highlight.js.

@Harmon758, would you be willing to help do another rebuild?

oh, it's new to all of us, as the project has a whole new bunch of maintainers.
Anyone done it before?

I assumed that it just wasn't automatically being built anymore because of the Read the Docs configuration/setup not being updated after the migration.
I'm not sure, but it's likely the webhook needs to be reconfigured through the Read the Docs project settings and/or the GitHub repository settings.
The Read the Docs project page still references https://github.com/isagalaev/highlight.js as the repository, so there might be other project settings that need to be updated as well.

@isagalaev Can you help us get this updated and perhaps we can get this building docs again?

@isagalaev Can you help us get this updated and perhaps we can get this building docs again? Or perhaps add admin rights to one of the other maintainers so we could fix this?

@isagalaev Repository is already changed to https://github.com/highlightjs/highlight.js, but still someone from maintainers should be able to make a build. My account is https://readthedocs.org/profiles/egorius/

@egor-rogov added you as a maintainer. @yyyc514 do you have account on readthedocs?
It shouldn't require manual intervention though. I can see the last build was done over two months ago, looking into it right now.

So apparently readthedocs was hooked to GitHub via a deprecated GitHub API ("Services"), so I now recreated it via a generic webhook manually, as suggested by the docs on readthedocs. Hopefully it will start building automatically again. If not, feel free to ping me again or fiddle with the settings on both sides.

When?  After next release?

@isagalaev Thanks!

When? After next release?

We shall see. As for now, the docs are up-to-date.

It actually builds for every push to master (I never defined any versions besides latest). You can see the commit SHA in the footer of the index page at https://highlightjs.readthedocs.io/en/latest/, it should be the same as the last commit in master.

Oh. Nice. Thanks.


Single cell copy from Instruction Info window does not copy to clipboard

Describe the bug
When using the context menu to navigate to the Instruction Info... window in any disassembly, the context menu that allows copying the text of a single cell appears to be broken. The hotkey ctrl+c for this command also does not work. The other functions such as Copy Current Column and Copy Columns... work as intended (as well as the Export options).
To Reproduce
Steps to reproduce the behavior:
See above description, as instructions are listed to describe the bug itself.
Expected behavior
The single selected cell's contents should copy to the clipboard.
Screenshots
N/A
Attachments
N/A
Environment (please complete the following information):

OS: openSUSE 20220905 x86_64 Linux 5.19.2-1-default
Java Version: 11.0.16
Ghidra Version: 10.1.5
Ghidra Origin: official GitHub distro

Additional context
N/A
Notes
I apologize in advance if this is a duplicate submission. I tried to comb through the issues searching copy and instruction info but did not see anything like this.
EDIT: Upon hitting that submit button a thought occurred that I had not tested this behavior in my other Ghidra builds (all official). This behavior is seen in 10.0.1 and 9.1.2. I could have tested more but I have a funny kind of feeling that the results will be the same.
EDIT2: To confirm that this wasn't a fluke with my own OS setup, I spun up a fresh OpenSUSE TW virtual machine and ran 10.1.5 on it and the behavior was replicated exactly.
EDIT3: Booted up my Win10 VM and surprise, nothing in the clipboard.

OS: Win10 Pro 10.0.19044 Build 19044
Java Version: 11.0.15
Ghidra Version: 10.1.2
Ghidra Origin: official GitHub distro

I confirmed this is broken.  The issue is that the table currently does not allow row selections, which interferes with the copy action.  This should be an easy fix.

How long has this gone unnoticed? :laughing:

It's been a while, but I'm just now revisiting this. Single cell copy still appears to be broken, the entire row is copied from the context menu.

It looks like the fix made it into the 10.2.2 build.  Which version of Ghidra are you testing this on?

It looks like the fix made it into the 10.2.2 build. Which version of Ghidra are you testing this on?

10.2.2, the adjustment removed the opTable.setRowSelectionAllowed(false); line, but I don't think single cells were ever implemented in the first place.
There's another issue here at play too. Going to the Instruction Info... and right clicking first to try to bring up the context menu on any cells won't work. You must first highlight any cell with left click, then right click on any cell will bring up the context menu. However, after this, right clicking on various cells seems to give a 50/50 chance of the context menu actually coming up.
The following is an example of the copy command in the context menu, it puts the entire row converted to html into the clipboard, just just the selected cell as plaintext.
<html>
<body>

Op-Objects | RCX, const:0x20 | const:0x1
-- | -- | --

</body>
</html>

Oh... it seems I've discovered the issue while writing this, and perhaps why  opTable.setRowSelectionAllowed(false);  was in the code in the first place. Copy current column... now copies the individual cell's contents, while Copy columns... seems to give an identical result:
<html>
<body>

dword ptr [RCX + 0x20]
--

</body>
</html>

Going back to 10.1.5, Copy current column... functions as I believe it was intended: (A true column, not a row)
(Operand-1 column)
<html>
<body>

dword ptr [RCX + 0x20]
--
dword ptr [RCX + 0x20]

RCX, const:0x20
00000000 00000111 11111111 00000000 00000000 00000000 00000000
00000000 00000001 00100000 00000000 00000000 00000000 00000000

</body>
</html>

As well as  Copy columns...
<html>
<body>

Operand | dword ptr [RCX + 0x20] | 0x1
-- | -- | --
Labeled | dword ptr [RCX + 0x20] | 0x1
Type |   | SCAL
Scalar |   | 0x1
Address |   |
Register |   |
Op-Objects | RCX, const:0x20 | const:0x1
Operand Mask | 00000000 00000111 11111111 00000000 00000000 00000000 00000000 | 00000000 00000000 00000000 11111111 11111111 11111111 11111111
Masked Value | 00000000 00000001 00100000 00000000 00000000 00000000 00000000 | 00000000 00000000 00000000 00000001 00000000 00000000 00000000

</body>
</html>

I just tried this in my Ghidra and all seems to be working as expected.
Copy copies the entire row.  With multiple rows selected, all rows are copied.
Copy Current Column copies just the selected cell when an single row is selected.  With multiple rows selected, only cells in the selected column for each row are copied.
Major Caveat: If you do not have column / cell selected when you execute the action, then the behavior may not work as expected.

Okay, so the trick here now is all cells/rows need highlighting before the copy command, whereas in prior versions of ghidra, the context menu command did that for you. That's fair enough.
I still think the labels need renaming , however.
Copy -> Copy Highlighted/Selected Row
Copy Current Column -> Copy Selected Cells
However Copy Columns is just Copy Rows without selecting which columns you want to include by highlighting them, where previously it was a Copy All Selected where Selected was each check mark per column.
However this is all semantics at this point, considering prior to this, individual row/cell copying was not possible and now it is.

However this is all semantics at this point

You just described most of my Ghidra career.


Doc update

A few updates to make things easier for new users to get going on sonar:

Removed claudia.json file - resolves #3
Added documentation
fixed naming of bot to index in npm scripts

Very helpful - thanks!


Copying in Fortran order

The following script fails to compile:
import numpy as np

#pythran export f(float[:, :])
def f(matrix):
    matrix_f = np.copy(matrix, order='f')
    return matrix_f.sum()

In my application, the memory access is much more suitable for Fortran order. What can we do about it? Is Pythran smart enough to recognise and do the transformation on its own, or should I rewrite the algorithm?

If the memory order of the input array is in Fortran style, Pythran represents that using a transposed matrix (this may not be a nice choice). We don't dont do anything smart on your case, but we should, as the default behavior of np.copy is to match the original data layout. I'll check that.

@Dapid does #810 somehow fixes your issue? It's not possible to support the order argument in Pythran, but as of now, np.copy at least respect original memory order.

Not quite. I want to change the order of the array. I have adapted the code to use the transpose outside of Pythran.
Any chance changing the alignment will be supported in the future? Otherwise, I think it would be good to document it as a limitation.


It shows wrong thumbnail but correct full image when there are multiple images with same name

Describe the bug
It shows wrong thumbnail but correct full image when there are multiple images with same name.
To Reproduce
Steps to reproduce the behavior:

Import a photo of Tree with name photo.jpg into Photok
Open any file manager app and rename a file sky.jpg to photo.jpg
Now import that photo.jpg into Photok again. Note that it's now the picture of Sky.
The photok would display the thumbnails of both images as Tree. But when you click on them it would display correct images, Tree and Sky.

Expected behavior
If by clicking the thumbnails the photok shows correct images with same file names. The same should be case with the thumbnails too. It should display correct thumbnails of multiple files with same names.
Screenshots
N/A
Smartphone:

Device: Pixel 7a
OS: 14
Browser: N/A
Version Any version

Additional context
N/A

Will try to reproduce asap

Could not reproduce with 1.7.0. What version did you use?

closing for now, since it cannot be reproduced


feat(cache): Add option to provide a cache instance.

This change adds an option to DBOptions to provide an external cache instance. This cache instance must implement InMemoryCache. If the option is provided, the block_cache_options are ignored when the DB is initialized.
This PR should be a fix for #226, but I'm opening it as a draft because it's my first contribution and I'd like to get feedback to make sure this is the direction that people had in mind.
/cc @rodesai

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

Those comments make sense @criccomini, thanks for the review. Something else that I was thinking is that it might not make sense to compile both, MokaCache and FoyerCache. It's unlikely that people will want to use both, unless it's for comparison. I can create feature flags to make them optional, so in production environments, you only need to bring the dependencies that you need and exclude the additional cache implementation.

BTW, I personally think it is a bad design to warp the Option in Entry. Especially when the Entry is an enum.
Just use Option<Entry> looks good enough. When returning from a cache, you can simply use Option<Entry> as it may return a cache miss result. When holding an entry that must exist, such as, got from the main volume after a cache miss, you can use Entry directly.
Otherwise, it would be too complicated when the entry is guaranteed to exist. You need extra mechanism to make sure the Entry wrapping an Option is Some not None.

I think I agree with you @MrCroxx. Let me do a cleanup, I think a trait for the CachedEntry is not right.

I think I agree with you @MrCroxx. Let me do a cleanup, I think a trait for the CachedEntry is not right.

Either a CachedEntry or just an enum is okay for me. I only disagree with wrapping an Option in it. 🥰 What do you think?

@calavera Really sorry about the merge conflict. I just merged in the rename from #234. Kinda blew up the naming in this PR. 😭

@calavera Really sorry about the merge conflict. I just merged in the rename from #234. Kinda blew up the naming in this PR. 😭

no worries. I'll deal with the changes, it should not be hard.

Ok, this turned into a bigger PR than I expected. There are a couple of major changes since the last review:

Moka and Foyer are behind feature flags. Moka is enabled in the default features.
The DbCache trait has changed to receive and return the same objects. This allows us to keep the implementation opaque, and the cache implementation is more simple.

Please, let me know what you think.

Thanks for the review @rodesai. I've made the changes that you suggested.
While I was working on a trait implementation example, I realized that SsTableId was not public. Without making it public, it's not possible to implement the DbCache trait outside Slatedb, so I made it public. I reviewed the db_state module to ensure that nothing else was made public. There are new docs that show how to implement the DdCache if someone wants to create their own implementation outside Slatedb.


🐛 [cloud_firestore] Stream error: 'Unavailable: failed to connect to all addresses

Bug report
Describe the bug
Not sure what happened, but started getting this error
Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds. This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
Stream error: 'Unavailable: failed to connect to all addresses; last error: UNKNOWN: ipv6:%5B2a00:***:443: No route to host

UPD: No issues when using another VPN. This is insane!!!
Steps to reproduce
Steps to reproduce the behavior:
I'm not sure how to reproduce, but nefore getting the errors I've updated to firebase_auth: ^4.11.0, then got the 'PigeonParser.h' file not found in iOS. Then downgraded back, so the Pigeon error gone, but started getting the errors above. Tried with wifi, vpn and mobile internet. Also tried on different devices, platforms and emulator. All of them has the issue. But my colleague tried the project and got no issues.
Expected behavior
It should work

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 3.13.8, on macOS 13.5.1 22G90 darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.1.4
Flutter SDK 3.13.8
frontstage 1.7.2+31

dependencies:
- algolia 1.1.2 [meta http uuid universal_io]
- app_settings 5.1.1 [flutter plugin_platform_interface]
- async 2.11.0 [collection meta]
- audioplayers 5.2.0 [audioplayers_android audioplayers_darwin audioplayers_linux audioplayers_platform_interface audioplayers_web audioplayers_windows file flutter http meta path_provider synchronized uuid]
- badges 3.1.2 [flutter]
- cached_network_image 3.3.0 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- cloud_firestore 4.11.0 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- collection 1.17.2
- connectivity_plus 5.0.1 [flutter flutter_web_plugins connectivity_plus_platform_interface js meta nm]
- country_codes 2.2.0 [flutter]
- crypto 3.0.3 [typed_data]
- dio 5.3.3 [async http_parser meta path]
- easy_image_viewer 1.2.1 [flutter]
- easy_localization 3.0.3 [flutter shared_preferences intl args path easy_logger flutter_localizations]
- email_validator 2.1.17
- enum_to_string 2.0.1
- expandable_text 2.3.0 [flutter]
- firebase_analytics 10.6.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.11.1 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.19.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.4.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 5.4.1 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_messaging 14.7.1 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 4.3.1 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- firebase_storage 11.3.1 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math web sky_engine]
- flutter_app_badger 1.5.0 [flutter]
- flutter_branch_sdk 6.9.0 [flutter flutter_web_plugins plugin_platform_interface js]
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_flavor 3.1.3 [flutter]
- flutter_local_notifications 16.1.0 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_riverpod 2.4.4 [collection flutter meta riverpod state_notifier]
- flutter_screenutil 5.9.0 [flutter]
- flutter_sim_country_code 0.1.2 [flutter]
- flutter_sticky_header 0.6.5 [flutter value_layout_builder]
- flutter_styled_toast 2.2.1 [flutter flutter_localizations]
- flutter_svg 2.0.7 [flutter vector_graphics vector_graphics_codec vector_graphics_compiler]
- flutter_widget_from_html_core 0.14.3 [csslib flutter html logging]
- freezed 2.4.5 [analyzer build build_config collection meta source_gen freezed_annotation json_annotation]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- geocoding 2.1.1 [flutter geocoding_platform_interface geocoding_android geocoding_ios]
- geolocator 8.2.1 [flutter geolocator_platform_interface geolocator_android geolocator_apple geolocator_web geolocator_windows]
- google_sign_in 6.1.5 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- hive 2.2.3 [meta crypto]
- image 4.0.17 [archive meta xml]
- image_picker 1.0.4 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- infinite_scroll_pagination 4.0.0 [flutter flutter_staggered_grid_view sliver_tools]
- json_annotation 4.8.1 [meta]
- json_schema2 2.0.4+9 [args collection logging meta path rest_client uri yaon]
- json_serializable 6.7.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- just_the_tooltip 0.0.12 [flutter]
- logger 2.0.2+1
- map_launcher 3.0.1 [flutter]
- mapbox_gl 0.16.0 [flutter mapbox_gl_platform_interface mapbox_gl_web collection]
- maps_launcher 2.2.0 [flutter flutter_web_plugins url_launcher]
- open_mail_app 0.4.5 [platform url_launcher flutter]
- package_info_plus 4.2.0 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface win32]
- page_view_dot_indicator 2.3.0 [flutter]
- path_provider 2.1.1 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- percent_indicator 4.2.3 [flutter]
- photo_view 0.14.0 [flutter]
- retry 3.1.2
- rxdart 0.27.7
- share_plus 7.2.1 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- shimmer 3.0.0 [flutter]
- showcaseview 2.0.3 [flutter]
- sign_in_with_apple 5.0.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- spotify 0.11.0 [http json_annotation oauth2 pedantic]
- timezone 0.9.2 [path]
- url_launcher 6.1.14 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.7 [crypto]
- version 3.0.2
- webview_flutter 4.4.1 [flutter webview_flutter_android webview_flutter_platform_interface webview_flutter_wkwebview]

dev dependencies:
- build_runner 2.4.6 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_lints 2.0.3 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math async boolean_selector characters collection material_color_utilities meta source_span stream_channel string_scanner term_glyph web]
- integration_test 0.0.0 [flutter flutter_driver flutter_test path vm_service async boolean_selector characters clock collection fake_async file matcher material_color_utilities meta source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api vector_math web webdriver]

dependency overrides:
- webview_flutter_wkwebview 3.5.0 [flutter path webview_flutter_platform_interface]

transitive dependencies:
- _fe_analyzer_shared 64.0.0 [meta]
- _flutterfire_internals 1.3.9 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 6.2.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.3.7 [crypto path pointycastle]
- args 2.4.2
- audioplayers_android 4.0.2 [audioplayers_platform_interface flutter]
- audioplayers_darwin 5.0.2 [audioplayers_platform_interface flutter]
- audioplayers_linux 3.1.0 [audioplayers_platform_interface flutter]
- audioplayers_platform_interface 6.1.0 [flutter meta plugin_platform_interface]
- audioplayers_web 4.1.0 [audioplayers_platform_interface flutter flutter_web_plugins js]
- audioplayers_windows 3.1.0 [audioplayers_platform_interface flutter]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.1 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.2.1 [analyzer async build collection crypto graphs logging package_config path pool pub_semver stream_transform yaml]
- build_runner_core 7.2.10 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta package_config path pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.6.2 [built_collection collection fixnum meta]
- cached_network_image_platform_interface 3.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.0 [cached_network_image_platform_interface flutter flutter_cache_manager]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- clock 1.1.1
- cloud_firestore_platform_interface 6.0.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.8.1 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.5.0 [built_collection built_value collection matcher meta]
- connectivity_plus_platform_interface 1.2.4 [flutter meta plugin_platform_interface]
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+4 [js meta]
- csslib 1.0.0 [source_span]
- dart_style 2.3.2 [analyzer args path pub_semver source_span]
- dbus 0.7.8 [args ffi meta xml]
- easy_logger 0.0.2 [flutter]
- fake_async 1.3.1 [clock collection]
- ffi 2.1.0
- file 6.1.4 [meta path]
- file_selector_linux 0.9.2 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3+1 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.0 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3 [cross_file file_selector_platform_interface flutter]
- firebase_analytics_platform_interface 3.7.3 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.5+3 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 7.0.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.8.4 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.8.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.6.9 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.6+9 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.10 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.5.10 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_remote_config_platform_interface 1.4.9 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.4.9 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- firebase_storage_platform_interface 4.4.9 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.6.10 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.1.0
- flutter_driver 0.0.0 [file flutter flutter_test fuchsia_remote_debug_protocol path meta vm_service webdriver async boolean_selector characters clock collection matcher material_color_utilities platform process source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api vector_math web]
- flutter_local_notifications_linux 4.0.0+1 [dbus ffi flutter flutter_local_notifications_platform_interface path xdg_directories]
- flutter_local_notifications_platform_interface 7.0.0+1 [flutter plugin_platform_interface]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math web]
- flutter_plugin_android_lifecycle 2.0.15 [flutter]
- flutter_staggered_grid_view 0.7.0 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math web]
- frontend_server_client 3.2.0 [async path]
- fuchsia_remote_debug_protocol 0.0.0 [process vm_service file meta path platform]
- geocoding_android 2.1.2 [flutter geocoding_platform_interface]
- geocoding_ios 2.1.0 [flutter geocoding_platform_interface]
- geocoding_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- geolocator_android 3.2.1 [flutter geolocator_platform_interface]
- geolocator_apple 2.2.7 [flutter geolocator_platform_interface]
- geolocator_platform_interface 4.0.7 [flutter plugin_platform_interface vector_math meta]
- geolocator_web 2.1.6 [flutter flutter_web_plugins geolocator_platform_interface]
- geolocator_windows 0.1.3 [flutter geolocator_platform_interface]
- glob 2.1.2 [async collection file path string_scanner]
- google_identity_services_web 0.2.1 [js meta]
- google_sign_in_android 6.1.18 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.6.2 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.4.1 [flutter plugin_platform_interface quiver]
- google_sign_in_web 0.12.0+3 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http js]
- graphs 2.3.1 [collection]
- html 0.15.4 [csslib source_span]
- http 0.13.6 [async http_parser meta]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image_picker_android 0.8.7+4 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 3.0.0 [flutter flutter_web_plugins image_picker_platform_interface mime]
- image_picker_ios 0.8.8+1 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.9.0 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- intl 0.18.1 [clock meta path]
- io 1.0.4 [meta path string_scanner]
- js 0.6.7 [meta]
- json_class 2.2.2+1 [intl logging meta]
- lints 2.1.1
- logging 1.2.0
- mapbox_gl_dart 0.2.1 [js]
- mapbox_gl_platform_interface 0.16.0 [flutter meta]
- mapbox_gl_web 0.16.0 [flutter flutter_web_plugins meta mapbox_gl_platform_interface mapbox_gl_dart image]
- matcher 0.12.16 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.5.0 [collection]
- meta 1.9.1
- mime 1.0.4
- nm 0.5.0 [dbus]
- oauth2 2.0.2 [collection crypto http http_parser]
- octo_image 2.0.0 [flutter]
- package_config 2.1.0 [path]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path 1.8.3
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.1.0 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.0 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.0 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.0 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.0 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 5.4.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.5 [meta]
- pointycastle 3.7.3 [collection convert js]
- pool 1.5.1 [async stack_trace]
- process 4.2.4 [file path platform]
- pub_semver 2.1.4 [collection meta]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.2.1 [matcher]
- rest_client 2.2.1+11 [http intl json_class logging meta uuid]
- riverpod 2.4.4 [meta stack_trace state_notifier]
- share_plus_platform_interface 3.3.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences 2.2.0 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- shared_preferences_android 2.2.0 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.3.3 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.0 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.0 [flutter plugin_platform_interface]
- shared_preferences_web 2.2.0 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.3.0 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- sky_engine 0.0.99
- sliver_tools 0.2.12 [flutter]
- source_gen 1.4.0 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.4 [analyzer collection source_gen]
- source_span 1.10.0 [collection path term_glyph]
- sqflite 2.3.0 [flutter sqflite_common path]
- sqflite_common 2.5.0 [synchronized path meta]
- stack_trace 1.11.0 [path]
- state_notifier 1.0.0 [meta]
- stream_channel 2.1.1 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- sync_http 0.3.1
- synchronized 3.1.0
- term_glyph 1.2.1
- test_api 0.6.0 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- timing 1.0.1 [json_annotation]
- typed_data 1.3.2 [collection]
- universal_io 2.2.2 [collection meta typed_data]
- uri 1.0.0 [matcher quiver]
- url_launcher_android 6.0.38 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.4 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.5 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.6 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.3 [flutter plugin_platform_interface]
- url_launcher_web 2.0.18 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.7 [flutter url_launcher_platform_interface]
- value_layout_builder 0.3.1 [flutter]
- vector_graphics 1.1.7 [flutter vector_graphics_codec]
- vector_graphics_codec 1.1.7
- vector_graphics_compiler 1.1.7 [args meta path_parsing xml vector_graphics_codec]
- vector_math 2.1.4
- vm_service 11.7.1
- watcher 1.1.0 [async path]
- web 0.1.4-beta
- web_socket_channel 2.4.0 [async crypto stream_channel]
- webdriver 3.0.2 [matcher path stack_trace sync_http]
- webview_flutter_android 3.12.0 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 2.6.0 [flutter meta plugin_platform_interface]
- win32 5.0.7 [ffi]
- xdg_directories 1.0.2 [meta path]
- xml 6.3.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]
- yaon 1.1.2+3 [logging yaml]

I have the same issue.
Yesterday, to avoid this issue pigeonParser.h file not found, I changed my .yaml with older version and everything work fine. Without to change my code, this afternoon I have this new message :
10.15.0 - [FirebaseFirestore][I-FST000001] WriteStream (139de2c18) Stream error: 'Unavailable: failed to connect to all addresses; last error: UNKNOWN: ipv6:%5B2a00:1450:4010:c02::5f%5D:443: No route to host'
I updated all new plugin version of firebase (published 3h ago), but I still have the same issue.

I have the same issue.
Yesterday, to avoid this issue pigeonParser.h file not found, I changed my .yaml with older version and everything work fine. Without to change my code, this afternoon I have this new message :
10.15.0 - [FirebaseFirestore][I-FST000001] WriteStream (139de2c18) Stream error: 'Unavailable: failed to connect to all addresses; last error: UNKNOWN: ipv6:%5B2a00:1450:4010:c02::5f%5D:443: No route to host'
I updated all new plugin version of firebase (published 3h ago), but I still have the same issue.

Just to continue working use vpn, until they fix this. But not the VPNProxyMaster.

Just to continue working use vpn, until they fix this. But not the VPNProxyMaster.

Thanks @nzackoya for this temporary solution, it's work with Planet VPN

@Kinomad np, just to have a whole picture, from which country are you trying to connect without VPN? I also reported a bug to google, need a list of countries in where the firestore is not working to tell them there as well

@nzackoya I'm currently now in Russia (but it's worked fine till yesterday evening without VPN)

@Kinomad same. If firestore is banned for russia, this is really insane

@nzackoya Agree and I hope no...

https://github.com/firebase/firebase-js-sdk/issues/7710#issuecomment-1771628183

@nzackoya I'm currently now in Russia for few days, but it's worked fine till yesterday evening without VPN

Hi @nzackoya, Could u mention where was you yesterday in Russia (the location/area)? and the  where you was when the issue happened (the location/area)?.
because I believe that from my test and reviewing the users who had the issue that the FireStore has issue on some ares on Russia not all of it.

@nzackoya I'm currently now in Russia for few days, but it's worked fine till yesterday evening without VPN

Hi @nzackoya, Could u mention where was you yesterday in Russia (the location/area)? and the  where you was when the issue happened (the location/area)?.
because I believe that from my test and reviewing the users who had the issue that the FireStore has issue on some ares on Russia not all of it.

Hi all! My clients in Russia (Moscow, Novosibirsk) also had problems working with the Firestore service.
Error: 10.16.0 - [FirebaseFirestore][I-FST000001] WriteStream (7f9651519118) Stream error: 'Unavailable: failed to connect to all addresses; last error: UNKNOWN: No route to host'

@AbdElrahman-Rafaat-Amer  in Krasnodar. @aazorin says it happens in Moscow as well, so I guess it is allover the Russia if it happens in Moscow. Is some developers/users don't face any issues in russia, I suppose it could be because of persistent cache.
Hey @darshankawar I guess this issue needs a close attention(hope this mentioning notifies)

@AbdElrahman-Rafaat-Amer in Krasnodar. @aazorin says it happens in Moscow as well, so I guess it is allover the Russia if it happens in Moscow. Is some developers/users don't face any issues in russia, I suppose it could be because of persistent cache. Hey @darshankawar I guess this issue needs a close attention(hope this mentioning notifies)

What I thought was that the issue was in all of Russia but after reviewing the users and checking their data I found that some users had no problems and the app worked fine(can write/read from FireStore) WITHOUT USING VPN but the others did not and all users in Russia.

For me, I’m in Vologda

@AbdElrahman-Rafaat-Amer in Krasnodar. @aazorin says it happens in Moscow as well, so I guess it is allover the Russia if it happens in Moscow. Is some developers/users don't face any issues in russia, I suppose it could be because of persistent cache. Hey @darshankawar I guess this issue needs a close attention(hope this mentioning notifies)

What I thought was that the issue was in all of Russia but after reviewing the users and checking their data I found that some users had no problems and the app worked fine(can write/read from FireStore) WITHOUT USING VPN but the others did not and all users in Russia.
Note:
I am using native apps(Android/iOS). and I think you saw the issue I opened also

@nzackoya and everyone facing this issue.
Looking at the error log, it seems to be related to network connection and not a bug in cloud_firestore plugin. Network related issues are not in control of flutterfire, as they are a thin wrapper around native Firebase SDKs to send data to and fro through Dart.
You'll probably need to raise this with Firebase support for further resolution.

@darshankawar might be not only the server side of the firestore, but also the plugin that is outdated because of a change in server side. Could you please put this issue for investigation anyway.
Already reported a bug to Firebase support, they don't respond for already 2 days, which for this like bug and so many developers and users is really a huge stopper.

@aazorin @AbdElrahman-Rafaat-Amer @Kinomad guys I have already reported this bug to [Firebase support](https://firebase.google.com/support). Please do same to upvote this bug, so google team notice this issue in case they haven't already.

@nzackoya I already reported it yesterday and am waiting for a response from them.

@nzackoya I reported it too and I'm also waiting a response from them

I've the same issue in Thailand ... sometimes it works, sometimes not ... quite annoying -_-

Hello, nobody have news about this issue when we are connected from Russia or Thailand?

It looks like this is a Network issue not directly related to FlutterFire. Based on similar reports I'll close this one. If you are having this issue, I suggest trying to use a VPN to go around specific network restrictions.
Feel free to open a new issue if you think this is not related to network.


UX: Bundle settlement reports in UI

User need
As a datahub user
I want the choice to easily bundle settlement reports
So that I don’t need to highlight and combine multiple processes
Notes

Energy suppliers and actors should default to download per month
Prepare the mockups for user testing (energy supplier)
Edge case: Warn user if there is 2+ processes run on the same day within the month/period, AND give them a choice of which proces to include in the report

ACs

Present to an energy supplier

The last accept criteria will not be implemented for now, as PO and SMI have agreed on only the last executed balance fixing will be bundled per month.


Set up homepage

What does this PR do?
This PR set up a template for the homepage. create folder for UI, css, javascript and Image
Description of Task to be completed

Create folder needed
Add index.html, script.js, and style.css to the template

How should this be manually tested

Fork this Repo
checkout to this branch ft-create-homepage

##branch
ft-create-homepage
Screenshot

Thansk @samador


Reports: Improve error reporting

================================================================================
2015-08-06 06:33:07                                         315s elapsed
---- ApiMappping ------------------------------------------------------
[#####################################################################-----] 93%
          waiting: 0      / active: 348    / done:5427
---- Requests ------------------------------------------------------------------
> Global                                                   (OK=4013   KO=8644  )
> Get /version/                                            (OK=1455   KO=4320  )
> Get /version/?version=15.7.4&                            (OK=1356   KO=99    )
> Main / /api/v1/mapp/employees/                           (OK=1202   KO=4225  )
---- Errors --------------------------------------------------------------------
> java.util.concurrent.TimeoutException: Request timed out to pe   4905 (56.74%)
rf-peopledoc.qualif.novapost.net/<IP_ADDRESS>:443 of 60000 ms
> status.find.in(200), but actually found 500                      2072 (23.97%)
> status.find.is(200), but actually found 500                      1667 (19.29%)
================================================================================

When reading the report on stdout sometimes I see this case, 2 lines about status with same error (here not attended return code), this is great but on which URL ? If here it's not possible to know on which url the nb of error is 1667 or 2072, what about just repport one line with the sum of tow of them ?
Second solution imporve the report to identify the query, something like numbering url :
================================================================================
2015-08-06 06:33:07                                         315s elapsed
---- ApiMappping ------------------------------------------------------
[#####################################################################-----] 93%
          waiting: 0      / active: 348    / done:5427
---- Requests ------------------------------------------------------------------
> Global                                                   (OK=4013   KO=8644  )
> 1. Get /version/                                            (OK=1455   KO=4320  )
> 2. Get /version/?version=15.7.4&                            (OK=1356   KO=99    )
> 3. Main / /api/v1/mapp/employees/                           (OK=1202   KO=4225  )
---- Errors --------------------------------------------------------------------
> java.util.concurrent.TimeoutException: Request timed out to pe   4905 (56.74%)
rf-peopledoc.qualif.novapost.net/<IP_ADDRESS>:443 of 60000 ms
> 2. status.find.in(200), but actually found 500                      2072 (23.97%)
> 3. status.find.is(200), but actually found 500                      1667 (19.29%)
================================================================================

Thanks

Which version do you use?
I have no idea how such a duplicate entry could happen: errors are stored in a Map and are handle by an Actor (ie thread-safe).

Lol. There's no duplicate: check the messages properly: "is" vs "in".

Ok my bad, sorry


? re GO:0060296 - regulation of cilium beat frequency involved in ciliary motility

Hi Paola,
I was looking at this term:
GO:0060296 - regulation of cilium beat frequency involved in ciliary motility

I am wondering why it doesn't seem to have a direct relationship to this term:
GO:0003356 - regulation of cilium beat frequency

It seems that GO:0060296 should be is_a GO:0003356

I also noticed that GO:0003356 is a direct child of this:
GO:0060295 - regulation of cilium movement involved in cell motility

and I am wondering if it should be called

"regulation of cilium beat frequency involved in cell motility"
instead of
"regulation of cilium beat frequency involved in ciliary motility"

thanks,
-Karen
Reported by: krchristie
Original Ticket: geneontology/ontology-requests/11667

Mentioning @krchristie as this ticket was ported over from SourceForge, so she can receive notifications.

Hi Karen,
I added the link:
GO:0060296 - regulation of cilium beat frequency involved in ciliary motility
is_a
GO:0003356 - regulation of cilium beat frequency
As for renaming ‘regulation of cilium beat frequency involved in ciliary motility’ as ‘regulation of cilium beat frequency involved in cell motility’, I’m unsure because, from a quick glance at the current experimental annotations to this term, it seems some of them refer to motile cilia in non-motile cells (e.g. airway epithelium). I suspect that, where annotations refer to motile cilia in motile cells, they should be to (renamed) ‘regulation of cilium beat frequency involved in cell motility’, while where they refer to motile cilia in non-motile cells they should simply be to ‘regulation of cilium beat frequency’.
I think the entire node of cilium movement needs work. One underlying question is - how does a cilium move other than by beating? @JohnvanDam Then of course, a moving/beating cilium may or may not cause the entire cell to move, depending on the (unicellular) organism and on the cell/tissue type.

My first thought is that the term "regulation of cilium beat frequency involved in ciliary motility" contains a form of pleonasm in that cilium beating implies that the cilium is motile. Cilia/flagella movements are used for two things: 1) propelling the cell, 2) moving liquids (partially) surrounding a stationary cell. Many processes involved in ciliary beating will also be involved in both cases, with likely few exceptions. I tend to say "regulation of cilium beat frequency involved in cell motility" and have another term like "regulation of cilium beat frequency involved in fluid or mucal displacement" or somesuch. Those genes annotated for beat frequency in lung epithelial cells should then be reassigned to the new term. However I am not sure whether the distinction biologically will be relevant since I suspect beat frequency regulation in both cases will likely be caused by the same agents.
Note that in the human body only the sperm cell actually uses the flagellum for locomotion (that I know of), all others that use motile cilia are themselves stationary (e.g. fallopian tube epithelium, lung epithelial cells) and are moving liquids, mucus and other cells (the ovum). Cells that use cilia instead of flagella for locomotion are organisms like Paramecium aka "ciliates".
Flagella tend to have a more "rotating" beat while cilia tend to have a "stroke". There are some nice gifs that show the distinction in movement quite well. From my head the movements of both types are referred to as "beating". The difference in movement however suggests that there are differences in the proteins involved in flagellar beating vs. ciliary beating. The academic question then is whether this is caused by a difference in regulation or a difference in the underlying structure and organisation of force generating components.
So in conclusion I think that the term "regulation of cilium beat frequency involved in ciliary/cell motility" could be dropped in favour of "regulation of cilium beat frequency" or we keep it in the hope that the term becomes more relevant later in time but then add the additional term.
It all depends on the intention of the original definition of this term, i.e. "ciliary" vs. "cell" motility. In the former case it is a pleonasm and thus redundant, in the latter we need an additional term for cilia beat frequency in stationary cells.

Thanks John for the great info on the difference in how sperm flagella and motile cilia on stationary multicilated epithelial cells beat. I hadn't picked up on that before.
LIke John, I am also under the impression that the sperm is the only cell in the human body that uses a flagellum for cellular motility. Sperm are a topic of a great deal of study however, so as an annotator, I have encountered papers where researchers studying sperm determined that a defect in beat frequency is a cause of a defect in sperm motility, so my perception is that this term is useful. Since the term "regulation of cilium beat frequency involved in ciliary motility"  is an is_a child of "regulation of cilium movement involved in cell motility", I think the intent of this term has been to indicate regulation of cilium beat frequency involved in cell motility.

GO:0003352 - regulation of cilium movement
-- is_a GO:0060295 - regulation of cilium-dependent cell motility
--- is_a GO:0060295 - regulation of cilium movement involved in cell motility
---- is_a GO:0060296 - regulation of cilium beat frequency involved in ciliary motility
-- is_a GO:0003356 - regulation of cilium beat frequency

However, with respect to John's comments about the difference in how epithelial, and other, motile cilia on stationary cells beat versus how the flagellum beat, it seems to me that we really might be dealing with two different kinds of beating on stationary cells just in mammals. John already mentioned multiciliated epithelial cells. However, there are also the motile primary cilia on the cells of the node during embryonic development. From the talks I've heard at meetings, these also have more of a rotating beat than a stroke. So, even for motile cilia on non-motile cells, it seems that there a couple different types of movement that might be worth distinguishing.
I tend to think that it might be useful to add another specific term or terms to distinguish the different processes or types of movement, however, I wonder how these terms will correlate across diverse species. So in mammals, multiciliated cells are typically epithelial cells that beat with a stroke, while sperm flagella have a rotating beat. What kind of beat do the cilia on multiciliated protozoa have?
Would we need to make distinctions based on whether the cell has a single motile cilium (aka flagellum like in the sperm), is multiciliated, or has a motile primary cilium?
So, I lean towards making more specific terms, but think we need to think carefully about how to do it.
-Karen

Hi Karen,
I forgot about the nodal cilia! You are right, they make regular circular motions.
To give you an idea of how a typical motile cilium makes a "beat", checkout this gif:

I couldn't find one for flagella unfortunately, but I have found a very enlightening youtube video on how different organisms use their flagella/cilia for locomotion (I understand that I am risking turning this post into a biology lesson):
https://www.youtube.com/watch?v=QGAm6hMysTA
We can safely assume that there are more ways of "beating" a cilium/flagellum. wiggling versus propellor comes to mind for flagella, circular versus the power stroke-recovery stroke for cilia. But for the ciliates I can imagine it might be different because they need to change direction in a moments notice, human cells rarely have to.
To come back to the discussion at hand: I would say that cilia/flagella beating for cell motility will be more dynamically regulated to account for speed, reverse direction etc. compared to producing fluid flows for stationary cells. I suggest two distinct terms at this level, one for ciliary beating for cell motility and one for producing fluid flows (stationary cells). We could then easily attach organism specific terms to those (I am not sure if that is how it is supposed to work in GO).
Cheers,
John

A note to add: There are also cilia on "stationary cells" that are used for locomotion of entire multicellular organisms. For instance the planarian Schmidtea mediterranea
http://ciliajournal.biomedcentral.com/articles/10.1186/s13630-016-0037-1
But also Trichoplax adhearens. Need to figure out if locomotion of organism is caused by fluid displacement or by actually produce force along substrate. If the latter is the case this would not be covered by the two terms I suggested at the end of the previous post.

Hi @krchristie  and @JohnvanDam ,
I reviewed this thread. While the biology behind how ciliated cells move is fascinating :-) I’m afraid that I’ll need to take the discussion back into the GO realm, and focus on what is within scope for GO, given our limited resources. For this reason, I think that at this time we may simply keep both terms, ‘regulation of cilium beat frequency involved in ciliary motility’ as well as its parent ‘regulation of cilium movement involved in cell motility’. The differences may be subtle depending on what wordings a paper uses. This said, if Karen or others have examples of papers that they’d want to annotate to a ‘regulation of cilium beat frequency’ term that is NOT involved in motility of the cilium, we may revisit the subject. But for now, I’ll close this ticket and focus on more pressing issues. Thanks for your patience and feedback, I learnt a lot!


i18n(fr): update guides/components.mdx

Description
This PR updates the French version of the guides/components.mdx page with the changes of #1862.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
guides/components.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Add db client installation guide

#1093
This basically expands the getting started guide's direction to install database client libraries "using the usual way to do this depending on your operating system".
I tested all of these except OS X commands which I got from @sgrif . apt-get I tested on Debian. yum I tested on CentOS. Of course, it would be nice to add Windows.
I'm a little concerned that sudo apt-get install postgresql-server-dev-all is installing way more than necessary and there might be a skinnier package that would work. Not sure how big a deal that is.

This looks great! This will be perfect to link to from the getting started guide as well. I'll leave this open for the rest of the team to leave feedback on if they have any, otherwise I'll deploy this to the website tomorrow.

LGTM 👍

@killercup thanks for your suggestions. I have made those edits.


About the ray direction

Hi, thanks for your great work. I noticed that in dvr.cu , only setp>0 will be considered as the next voxel border. Will this be okay since in the Lidar axis, there are 360 directions which also contains the negative directions of rays? Looking forward to your help.
        // Distance along the ray to the next voxel border from the current position (tMaxX, tMaxY, tMaxZ).
        const double next_voxel_boundary_x = vx + (stepX < 0 ? 0 : 1);
        const double next_voxel_boundary_y = vy + (stepY < 0 ? 0 : 1);
        const double next_voxel_boundary_z = vz + (stepZ < 0 ? 0 : 1);

Hi, thanks for diving into our work! Hopefully the diagram below answers your doubt.

First of all, you can think of next_voxel_boundary as an intermediate quantity to computing tMax values. tMax is just storing the time to hit the next voxel boundaries in the x, y, z directions. "Time" is referred to as  distance in the code. When you mark the voxel indices and the boundary values as in the figure above, the following observations are clear:

For a ray moving in the positive x/y/z direction, the next x/y/z voxel boundary lies at an incremented voxel index
For a ray moving in the negative x/y/z direction, the next x/y/z voxel boundary lies at the voxel index it is already at.

I think the confusing part is that we are conflating the indexing of voxels with the indexing of the voxel boundaries. For more in-depth understanding, I usually find this blogpost helpful: https://github.com/cgyurgyik/fast-voxel-traversal-algorithm/blob/master/overview/FastVoxelTraversalOverview.md. Let me know if something is not clear!

Many thanks! I understand it. next_voxel_boundary is just an intermediate quantity used to calculate tMax, and has nothing to do with the voxel index (vx, vy, vz) that the ray will reach. I just figured it out. Thanks for your kindly help again!


How to compare the accuracy for task 1?

In task 1 it is said to compare the accuracies (how many digits are correct) and efficiencies (how many steps does it take to reach a given accuracy). How are we supposed to take the accuracy value. Should we take adaptive trapezoid method as reference or any approximate value of true integral to compare the accuracy?

@Pranjal-Srivastava-2023 is doing task 1, maybe he has some ideas.

@pratibha77118 I guess accuracy is just the number of steps it takes for each function to arrive at an acceptable answer.


JavaScript infer types from usage inserts jsdoc in wrong location for const arrow function

TypeScript Version:  3.3.0-dev.20181214

Search Terms:

javascript
jsdocs
quick fix
infer types from usage

Code
For the JavaScript:
// @ts-check

const a = (x) => x.y + 1;

Run the infer types from usage quick fix on x

Expected behavior:
// @ts-check

/**
 * @param {{ y: number; }} x
 */
const a =  (x) => x.y + 1;

Actual behavior:
// @ts-check

const a = /**
 * @param {{ y: number; }} x
 */
 (x) => x.y + 1;

Playground Link:
Related Issues:

Ok, working on this :)

I'm interested in working on this!


Support the Clojure nREPL CIDER debugger

Does what it says on the tin. Let's have debugger support, should probably just a pass through nREPL and support the newer features, so probably involves doing #137 too! Maybe #139 as well.

https://github.com/puremourning/vimspector seems like a promising frontend for the debugger! Implementing the UI is kinda out of scope I think, unless I can think of a good text based log buffer interface... so I think this could be a great shortcut to a great debugger experience.

Thank you to @dharrigan for prompting my interest in this 😄

I think debugging functionalities is beyond the scope of this plugin. Maybe we can add good interaction with vimspector though.

Agreed, still a sizeable chunk of work to design that interface for each client to implement though. I also worry only very few clients transports / implementations will be powerful enough to allow it.

@Olical or @glyh do you know if there are any docs on how the nREPL handles debug request/responses? My thinking is that there would need to be a shim between those messages and the DAP specification so that plugins like nvim-dap can handle the ui and client stuff.

I'm not sure of any documentation right now although I'm away on holiday at
the moment so haven't had time to look it up. I'm sure some exists! I will
be digging into this as part of my Clojurist Together funding in April
however ☺
On Mon, 7 Mar 2022, 18:45 Aaron Walker, @.***> wrote:

@Olical https://github.com/Olical or @glyh https://github.com/glyh do
you know if there are any docs on how the nREPL handles debug
request/responses? My thinking is that there would need to be a shim
between those messages and the DAP
https://microsoft.github.io/debug-adapter-protocol/specification
specification so that plugins like nvim-dap
https://github.com/mfussenegger/nvim-dap can handle the ui and client
stuff.
—
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/issues/182#issuecomment-1060955408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACM6XJWQX2ZIJ5NPRXJZH3U6Y6DFANCNFSM4YLDGUAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Please let me know if I can be of any assistance, I'm happy to start looking for docs, etc. now!
I'm just starting my Clojure journey but have some experience with DAP and would love to make debugging a first class workflow for conjure users. Enjoy the rest of your holiday and hopefully hear from you again in April.

I guess you need to look through nREPL and CIDER websites?
And maybe the best way to understand nREPL is to read through some nREPL servers' source codes.

We now have some CIDER debugger support with plans for a standalone tool that will allow you to connect any DAP client (in any editor, including Neovim) to a CIDER nREPL to drive it's debugger tolling with clever GUIs.
See here for information about Conjure's built in debugger tooling but I hope to supersede it with the standalone tooling https://github.com/Olical/conjure/wiki/Clojure-nREPL-CIDER-debugger


[DevOps] Config and start prd server on Vscale with new OS version, fix deply

[DevOps] Config and start prd server on Vscale with new OS version, fix deploy
https://vds.selectel.ru/
ask creds Lena https://t.me/ElenaLovesSpb

Little action plan:

[ ] Create new server brain-up-new on vds.selectel.ru
[ ] Install docker/docker-compose
[ ] Install github self-hosted runner
[ ] look how to copy db from old instance
[ ] register new domain name
[ ] create configuration for new domain name
[ ] create pipelines to deploy into new instance
[ ] check if all works fine

started app without certs on new instance here: http://<IP_ADDRESS>/

certificates copied, frontend with tls was started and dns records changed from old to new instance
So now https://brainup.site/ should point to new instance

hm, after merge PR #2618 there are some errors:
https://github.com/Brain-up/brn/actions/runs/11163834931/job/31031943111
ERROR: for brn  'ContainerConfig'

fixed by stopping locally front and backend containers and deploying it via pipeline
https://github.com/Brain-up/brn/actions/runs/11163834931/job/31033549957

about brief documentation:
scripts used during this new instance creation and moving data from old one
# login as root and update all packages and kernels
apt update
apt upgrade

reboot

# install docker from the doc https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-22-04

apt install apt-transport-https ca-certificates curl software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null
apt update

apt install docker-ce
systemctl status docker

# install docker-compose
apt install docker-compose

# create user for github-runner

useradd github-runner
mkdir /home/github-runner
chown github-runner:github-runner /home/github-runner

su - github-runner

# install github-runner from documentation described on page https://github.com/Brain-up/brn/settings/actions/runners/new
mkdir actions-runner && cd actions-runner
curl -o actions-runner-linux-x64-2.319.1.tar.gz -L https://github.com/actions/runner/releases/download/v2.319.1/actions-runner-linux-x64-2.319.1.tar.gz
echo "3f6efb7488a183e291fc2c62876e14c9ee732864173734facc85a1bfb1744464  actions-runner-linux-x64-2.319.1.tar.gz" | shasum -a 256 -c
tar xzf ./actions-runner-linux-x64-2.319.1.tar.gz
./config.sh --url https://github.com/Brain-up/brn --token AAXXXXXX # taken from https://github.com/Brain-up/brn/settings/actions/runners/new

# to create backup from volumes on old system
for i in brn_dbdata brn_certbot-etc brn_certbot-var brn_web-root-for-certbot; do echo $i; docker run --rm -v ${i}:/data -v $(pwd):/backup busybox tar czf /backup/backup_${i}.tar.gz /data; done

# then copy backup.tar.gz file
scp -r root@<IP_ADDRESS>:/root/backup ./
scp -r backup root@<IP_ADDRESS>:/root/

# restore backup to volume with db
docker run --rm -v brn_dbdata:/dest -v $(pwd):/source busybox tar xvzf "/source/backup.tar.gz" -C /dest

# install git for checkout process
apt install git

# provide access to docker from github-runner
usermod -aG docker github-runner

# add swap with 1GB
dd if=/dev/zero of=/swapfile bs=1024 count=1048576
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
echo "/swapfile swap swap defaults 0 0">>/etc/fstab

# start db from github-runner
docker-compose up -d --no-deps db_brn

So this issue can be closed


Deep indentation of lists does not work.

A markdown that has more than one level of indent in lists triggers an error:
* list
    * twice nested list

Problem here is that the AST handles this only through the position, start, end attributes - something that was not necessary to calculate so far.

Has this bug been fixed?

I'm working on a chat application with this markdown editor, seems to have no issue:

This works, but not if you jump from level 1 to level 3 with no in-between.

Is there any progress / plans on fixing this issue? or is there a workaround available to simply prevent this from happening?


[BUG] can't get the input devices when the program start

when i start the program download from realsase(the latest),it said
2023-08-03 14:01:35,349 ERROR   - Something went wrong while trying to get the input devices (mic). (Record.py:56) [MainThread]
2023-08-03 14:01:35,350 ERROR   - 'utf-8' codec can't decode byte 0xc2 in position 6: invalid continuation byte (Record.py:57)

the program should recognize my mic,it's useable in other applications and it's fine in windows.
Buzz and whisper-desktop can recognize my mic and it's useable.

OS: windows 11 22H2
cpu 7840s with 4060
a laptop with the mic bulit in

seems to be related with the sounddevice library. Maybe i'll switch the device querying to pyaudio or add it as a fallback option

seems to be related with the sounddevice library. Maybe i'll switch the device querying to pyaudio or add it as a fallback option

thank you，I will waiting for the new release.

@Dadangdut33 I tried dev version ,now it is working well ,this bug fixed.


Disabled Open SparkUI link after rebuild

Hi,
I rebuild in ubuntu 18.10 cosmic, JDK8 with
sbt -D"spark.version"="2.3.2" -D"hadoop.version"="2.7.7" -D"jets3t.version"="0.7.1" -Dmesos.version="0.26.0"
and works fine and spark jobs can be accessed via http://mylocal:4040/jobs/ but the link is disabled!

Hi,
that's a known issue with spark 2.3+ only - in spark 2.3 there's no spark jobs monitoring implemented (due to a changed spark API, see https://github.com/spark-notebook/spark-notebook/issues/953 )
on the other hand spark 2.2 would have the spark ui and job tracking...


Propagate either feature and enable by default from the facade

Is this primarily for streams and sinks? Because we can no longer implement Future for Either.

I didn’t actually check what it enabled, I just noticed it wasn’t propagated when looking at the compact stuff.
Maybe it would be better to just drop the either stuff now that it can’t be implemented for Future, that was @MajorBreakfast’s sentiment on #1152

I still think that some form or another of the either stuff is still needed so long as we don't have async/await like syntax for writing Streams or Sinks that delegate to one of several possible children.

We could introduce a Coalesce enum generated via a macro (like Join)
Coalesce, Coalesce3, Coalesce4, Coalesce5
e.g.
enum Coalesce3<T1, T2, T3> {
    Variant1(T1),
    Variant2(T2),
    Variant3(T3),
}

That enum would be local to our crate. We can add a correct Unpin impl
impl<T1: Unpin, T2: Unpin, T3: Unpin> Unpin for Coalesce3 {}

and Future and Stream impls
The main advantage is of course that we can add support more than two variants. I'd say five, like we have for Join, should be enough.

@MajorBreakfast I have a macro that does this in fuchsia already. However, I realized that it is unsafe under 0.3, since there's nothing stopping the user from implementing Unpin for the resulting type unconditionally. In the 0.3 branch I renamed the macro to unsafe_many_futures and noted that it was unsound to implement Unpin or Drop for the resulting type. However, you're right that we could force the issue by implementing Unpin and Drop ourselves, preventing the user from implementing either. However, that potentially becomes unsound if https://github.com/rust-lang/rust/issues/29864 ever becomes stable, as it would allow overlapping impls of Unpin (permitting the user to write an unconditional impl). I don't know how much we should concern ourselves with this particular case, though. WDTY?

@MajorBreakfast okay! yeah, in that case you can just drag-and-drop https://fuchsia.googlesource.com/garnet/+/sandbox/cramertj/asyncing/public/rust/crates/fuchsia-async/src/lib.rs#46 (although you'd want to change the PinMut and Future references to $crate::core_reexport:...-- the PinMuts in that version that are unprefixed).

I'd prefer to remove the either dependency entirely because we can't implement it consistently for all traits. Also, offering two solutions for the same thing seems weird.
Also, I suggest to not add any combinator methods. If we added methods for Coalesce to Coalesce5, we would need to add 14 methods. We could of course only add the two methods for Coalesce, bit IMO the Coalesce::Variant1(future) notation is nice enough.


Or and And predicates only accept a single property

Since updating to use the Koryphe functions library in version 0.7.0 the Or and And Predicates now only work with a single property.
For example you can select a property (e.g count) and pass that same property value to multiple predicates:
new View.Builder()
        .edge("RedEdge", new ViewElementDefinition.Builder()
                .preAggregationFilter(new ElementFilter.Builder()
                                .select("count")
                                .execute(new Or<>(new IsLessThan(2L), new IsMoreThan(10L)))
                                .build())
                .build())
        .build()

Prior to 0.7.0 you could select multiple properties then within the Or function you could do select which properties to pass to which functions, it was complicated to write but it used to work like this:
new View.Builder()
        .edge("RedEdge", new ViewElementDefinition.Builder()
                .preAggregationFilter(new ElementFilter.Builder()
                                .select("count", "average")
                                .execute( new Or(new ConsumerFunctionContext.Builder<Integer, FilterFunction>()
                                                .select(0) // select first property
                                                .execute(new IsLessThan(2))
                                                .build(),
                                        new ConsumerFunctionContext.Builder<Integer, FilterFunction>()
                                                .select(1) // select second property
                                                .execute(new IsMoreThan(5.1))
                                                .build())))
                                .build())
                .build())
        .build()

The issue was actually mainly around the validation of the Or and And predicates. This has now been fixed in Koryphe 0.1.1. So to fix this issue we will need to update to Koryphe 0.1.1.

Merged into develop.


Non helpful error message when started in clientonly mode

If the client is started with the commandline node clientonly --address <IP_ADDRESS> --port 8080, it returns the error Usage: 'node clientonly --address <IP_ADDRESS> --port 8080 [--use-tls]', which is very confusing, because it is exactly what the user did just then.
This is due to the fact that in clientonly/index.js:123 function fail() is called without arguments, causing it to return exactly this default error message:
if (["localhost", "<IP_ADDRESS>", "::1", "::ffff:<IP_ADDRESS>", undefined].indexOf(config.address) === -1) { [snipsnip] 	} else { 		fail(); 	}
Suggestion: put an actual error message into the call to fail();

Come to think about it: Is there a logical reason to block localhost? I stumbled upon it when trying to split my PM2 config into two, so I could restart the frontend and backend individually.

in general there is no need to use client on the same machine
just use a browser on the docker host

But is it actually problematic? In my opinion, restrictions should not exist unless absolutely necessary. You might not see any use case right now, but somebody else might.
Look at my use case: I am running and will always run the frontend and backend on the same machine, but if I run them separately, I can change the config and restart the backend without the user even noticing the disruption, and much quicker too. There is no need to restart the frontend for a minimal config change.
My current workaround is to simply attach to the external IP of the device, but with what I currently know, I feel the restriction could be dropped completely with no ill effects whatsoever.

three is no a
guarantee thatbthe front end will recover when the backend is restarted.

I noticed that sometimes it will get out of sync. For my testing setup, that is no big issue. When I deploy it for real, I'll most likely go back to running it as a single task for now.
That still doesn't explain why localhost needs to be blocked in my mind, because it would be true whether you ran client and server on the same machine or on separate ones.

well, if you are going to run it on the same machine, then we recommend using the  single instance execution
npm start
vs
npm run server
AND
npm run client


S3WritableByteChannel tries another upload on second close() call

When using the library (version 2.0.1), we experienced FileNotFoundExceptions when writing data.
When further investigating, we found out that the S3WritableByteChannel.close() method does not behave as specified: On a second call to an already closed channel, the implementation tries to upload the temp file again, which has been deleted at this time already, of course.
IMHO, this is a violation of the contract of the Channel.close() method.
I'm prepared to deliver a fix if desired.
Environment:

Windows
Java Temurin 21
Library version 2.0.1

closed by #454


Add support for CA directories.

This enables support for directories of CAs in urllib3. These are usually used for efficiency purposes, as they allow lazy-lookup of certificate authorities in response to the specific certificates needed for a given connection.
This is a precursor bit of work to kennethreitz/requests#2659.

I'm always sad to add more params to an already-param-heavy init, but not sure how avoidable this is.
Would it be feasible to have something like **cert_kw and just pass the args all the way down the pipe?

I don't think you can mix **conn_kw with **cert_kw.

Yea, but I mean it can travel along as **conn_kw for a while, then somewhere down the pipe, the leftover args will become **cert_kw. Or is this an empty fantasy?

@shazow Regardless of whether this is an empty fantasy or not, I can certainly refactor this change to use **conn_kw and pop the argument off if you prefer that approach. It's easy enough to do!

@Lukasa If it doesn't look a lot worse, I think that might be better. I'm only +0.5 to this, so feel free to override. :)

ceterum censeo you should support a custom SSLContext object or a wrap_socket_object_in_ssl_socket(socket, hostname) callback. You don't want to have options and flags for all SSLContext features ;)

We have an open pull request for that, @tiran, but unfortunately it's gotten bogged down because this turns out to be a somewhat tricky problem. In the short term, this is an easy enough thing for us to add, and it resolves a known user complaint.

@shazow Actually I think I lied. Conceptually the SSL arguments are connection arguments, but weirdly they are managed by the connection pool. Arguably we want a refactor there, but...is that refactor in scope for this change?

You're right, we may as well include it part of a larger refactor which combines all the cert-related keywords (and other groups too).

is there a good reason to keep this a separate argument, as opposed to, say:
if os.path.isdir(ca_certs):
  context.load_verify_locations(None, ca_certs)
else:
  context.load_verify_locations(ca_certs)

?

@matejcik I think at the urllib3 level users should be explicit: it doesn't hurt and catches subtle bugs. I think that logic will definitely happen at the requests level.

ISTM that the file/directory distinction is purely an artifact of openssl's way of handling certificate files? and that pushing it ever-upwards is a bad idea, so stopping it as early as possible (ideally right in python ssl) is desirable?
i mean, it hurts a little bit: forces the user of the library to think about format of their cert store, and also adds a parameter to an already parameter-heavy method.
but i'm not sure about my premise, so that's what i'm asking, basically: are there cases where being explicit about this is a tangible benefit?

@matejcik You're entirely right, this is an artefact of OpenSSL, and you're entirely right that at some point we should stop propagating the distinction. However, there are costs to doing it lower in the stack, and those costs are discoverability.
Additionally, we are not really abstracting away OpenSSL here. Having a bundle of PEMs in a file is a valid input for OpenSSL, but not necessarily for other SSL libs, and the 'certificate directory' is very OpenSSL specific, with a format and layout that is generated directly by OpenSSL itself. We cannot pretend that either of these things has no relationship to OpenSSL, so pasting them together and claiming they have no relationship to OpenSSL is a little disingenuous.
In this case, I think some users should be thinking about the format of their cert store. In either case, I believe this to be an interim solution to this problem, where the SSLContext solution will be the final way to deal with this.


Allow turning off value and timestamp interpolation for non-aggregated queries

See https://github.com/prometheus/prometheus/issues/570

#1006 made non-interpolation the default so this is resolved, though we may want to allow for interpolation again in the future for some use cases.


WIP: fix prompt for region when errors w/ location

fixes #408: It appears using the simulator the app does not properly prompt you for your region which then results in errors.
Steps to test:

Open simulator & set location to None
Delete app
Install & run app

[x] prompt for region when app runs with no region set and location cannot be aquired
[x] do not prompt for region on subsequent app launches if region is set and location cannot be aquired
[ ] fix bug introduced where on first run it always asks for user to select a region
[ ] Merge https://github.com/OneBusAway/onebusaway-iphone/pull/410

Seems this now always prompts for the user to select a region which also is not desired.

@aaronbrethorst ready for further review. One issue that I could use your help on is that it now always asks the user what region they want to use on first run whereas before I believe it just assumed they wanted the nearby region. I believe this is because setNearestRegion is called before the user has had a chance to approve or deny the location access prompt. Any ideas on how to address?

Let's move the call for setNearestRegion into a delegate method that gets called by OBALocationManager. The delegate method is called immediately after location manager initialization if the user's location setting is something other than unknown, and called after it's set if the user has yet to choose to authorize or deny location services.

issue has been addressed


[Remote Store] Add remote segment upload backpressure integ tests

Description
[Describe what this change achieves]
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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.

Seeing flaky tests - https://github.com/opensearch-project/OpenSearch/issues/8059, https://github.com/opensearch-project/OpenSearch/issues/5957, https://github.com/opensearch-project/OpenSearch/issues/5031 & https://github.com/opensearch-project/OpenSearch/issues/8213

Build failed due to lucene version tests failing. Unrelated to this PR. Seeing similar failures in other PR builds as well - https://build.ci.opensearch.org/job/gradle-check/18436/
REPRODUCE WITH: ./gradlew ':qa:verify-version-constants:v2.9.0#integTest' --tests "org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT.testLuceneVersionConstant" -Dtests.seed=4F5BE3F1B1D72CEF -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=vi-VN -Dtests.timezone=Europe/Warsaw -Druntime.java=20

org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT > testLuceneVersionConstant FAILED
    java.lang.AssertionError:
    Expected: <9.7.0>
         but: was <9.6.0>
        at __randomizedtesting.SeedInfo.seed([4F5BE3F1B1D72CEF:C23EDEAD96DFEFA6]:0)
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
        at org.junit.Assert.assertThat(Assert.java:964)
        at org.junit.Assert.assertThat(Assert.java:930)
        at org.opensearch.qa.verify_version_constants.VerifyVersionConstantsIT.testLuceneVersionConstant(VerifyVersionConstantsIT.java:56)

Backport was merged.


[Global/JetBrains] add support for Rider and nested projects

In newer versions of the IntelliJ platform (such as the one used for Rider), the .idea files are now placed in a subdirectory of the same, named after the current project (such as ".idea/.idea.Everlook/.idea/workspace.xml"). Adding a double-star pattern to these folder rules will also ignore these new files and maintain backwards compatibility with previous revisions of this file.

cc @citizenmatt for :eyes: and :thumbsup:

Sorry for the delay folks, chasing this down internally.
It's a change specifically for Rider, and doesn't affect other IntelliJ based products. It means that multiple solution files in a single folder will get separate settings folders. This doesn't affect other IntelliJ based products as they are essentially folder based, rather than based on a single project.
The double star pattern is good in that it will continue working not only with current IntelliJ products, as well as Rider.

@citizenmatt thanks for the :thumbsup:, and thanks for the contribution @Nihlus!


Adapt to Documenter 0.28 (master branch)

Cf. #9

Superseded by https://github.com/JuliaDocs/DocumenterCitations.jl/pull/3


Allow selection of the audio format

Also need this, this is the only blocker for me to move from librespot-org/librespot-golang


Verify at least one page reads data from the database

Add Listing, Edit Listing Pages both write to database.  View Listings and View Listings Admin both read from the database.


the ReconLayer.pretrain() function hard coded visualize.W shape to be 28*28

The ReconLayer.pretrain() function has hard coded visualize.W() shape to be 28*28, so if we change the training data shape it will crash.
This shape should be drawn from the input data.

the default visualization of ReconLayer is for MNIST dataset, if you want to modify the pretrain function, please have a look at the following tutorial on our website:
http://tensorlayer.readthedocs.io/en/latest/modules/layers.html#modifying-pre-train-behaviour
However, if you change the training data shape it will NOT crash, as pretrain function uses try as follow.
if save:
      try:
            visualize.W(self.train_params[0].eval(), second=10, saveable=True, shape=[28,28], name=save_name+str(epoch+1), fig_idx=2012)
            files.save_npz([self.all_params[0]] , name=save_name+str(epoch+1)+'.npz')
      except:
            raise Exception("You should change visualize.W(), if you want to save the feature images for different dataset")

We primarily use github issues to track bugs and installation issues. This is a question better suited for StackOverflow. Please ask it there and tag it with the tensorlayer tag. Thanks!


MeshDB.writeBlock is not safe in the event of the crash

Description
To provide safety if crash happens write must be atomic. Leveldb guarantee atomicity of the write if write batch is used.
The issue exists because we are writing block first and then updating mapping between layer id and blocks in two different databases. This operation has to happen using single database.
Proposed changes:

introduce different buckets for blocks, layers, etc using single database. bucket needs to have constant number of bytes (e.g. 2 will be enough, 0x0001 for blocks, 0x0002 for layers)
each current database should be refactored to work on its own isolated bucket.
writing a block should write a block the same way it does now, and then create mapping using key 0x00020BLOCK_ID
query for blocks ids should use range scan

Steps To Reproduce

crash node after write a block, but before updating layers index

Expected Behavior
writeBlock must use batch write to guarantee atomicity of the write.
Environment
any

Thanks for bringing up this important point!
In the past when I suggested this solution @antonlerner raised the point that we're using separate databases because we want separate caches for each database. Is there a way to achieve this with buckets? I'm not familiar with the concept.
If this can't be achieved with leveldb's built in primitives, perhaps we must resort to having our own caches instead of leveldb's, but this obviously makes this change more complex/expensive.
Just to be clear: I think there's absolutely no choice and we must make this change, even if it's very complex. My point is only that it's not as "low hanging" as it seems.
Would love to hear your thoughts.

The bucket is just a prefix for a key. I don't know what caches leveldb maintains but I don't expect them to have separate caches based on prefix. I always thought that leveldb actually doesn't maintain internal cache, but relies on os page buffer. Would like to double check it. But besides that, we maintain lru caches for some types anyway, so we can generalize it.
I noticed that there are other places where this pattern is used, I think this absolutely needs to be refactored before mainnet. It will be a source of problems in which people will have to resync the mesh. Maybe we should plan to address it systematically in the future sprints?  (cc @antonlerner)

blocks were designed to be written bottom up - in a way that interrupting the write should not affect node behaviour. we first write the block itself and then update the block in the layer, if the first fails than there is no actual corruption because we don't have any dangling pointers
Later we update layer hash - this may be not up to date but I'm not sure it can corrupt database
That being said, although we might lose internal levelDB cache management I think we can definitely merge databases, but this needs to be well designed - as we see there are at least 3 types of data affected by new blocks (block, layer, layerhash)

If we fail after the block is written, but before the block in the layer is updated - then we a have corrupted state (I don't mean actual physical corruption on dusk, but a violation of consistency). The next query for LayerBlockIds will not return the block that was written, but GetBlock will.

we access blockIDs only from layer prespective, simply storing a block in the DB won't affect the layer, layer hash and eventually state. node will sync on the block again when booting back up so that state will be consistent with others

Are you sure that it will sync? In the code AddBlock will fail if the block exists in blocks database, even if the block id is not added to the layers database. I can't find other places where block id can be added to the list.

@dshulyak close to be followed by https://github.com/spacemeshos/go-spacemesh/issues/2918?

Yes this is one of the issues that will be closed by implementing recommendations from https://github.com/spacemeshos/go-spacemesh/issues/2918


"Proposed API is only available when..." after updating to Insiders 1.50

Issue Type: Bug
No steps, this happens after update to VSCode Insiders 1.50
Extension version: 10.2.2
VS Code version: Code - Insiders 1.50.0-insider (bc38b0accb3c62180317c63dbe7323200977db0f, 2020-09-11T12:48:20.764Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.15.0-112-generic

Hi @anatolyburakov ,
But based on this report https://github.com/microsoft/vscode/issues/106499 in VS Code repo, It appears to be a VS Code issue.
Hope this helps

Works now, apparently. Thanks!


[Bug][Master] execute ComplementProcess  exception

This will cause the process definition to be empty，An error is reported later when the process definition is retrieved

This issue had been fixed.


Update to latest crossplane-runtime and add max-reconcile-rate

Signed-off-by: Bob Haddleton<EMAIL_ADDRESS>Description of your changes
Updated to the latest crossplane-runtime and added the --max-reconcile-rate option to allow for up to 10 (by default) concurrent reconciliations.
Fixes #125
I have:

[X] Read and followed Crossplane's contribution process.
[X] Run make reviewable to ensure this PR is ready for review.

How has this code been tested
This has been running in our dev/test environment with no issues.

@turkenh - any suggestions for how to debug the failing e2e test?  I can reproduce it locally but I don't know where to look for the problem.   Thanks

@turkenh - any suggestions for how to debug the failing e2e test? I can reproduce it locally but I don't know where to look for the problem. Thanks

@bobh66 error message indicates that provider-helm package is not being healthy after deployment:
>>>>>>> installing provider-helm into "crossplane-system" namespace
provider.pkg.crossplane.io/provider-helm created

>>>>>>> check kind node cache dir contents
total 100
drwxr-xr-x 2 1001  116  4096 Jul 29 07:31 .
drwxr-xr-x 1 root root  4096 Jul 29 07:31 ..
-rw-r--r-- 1 1001  116 [92](https://github.com/crossplane-contrib/provider-helm/runs/7574598919?check_suite_focus=true#step:12:93)160 Jul 29 07:30 provider-helm.xpkg

>>>>>>> waiting for provider to be installed
error: timed out waiting for the condition on providers/provider-helm

So, I would expect you should see the problem with:
make e2e

# in another terminal, while it is "waiting for provider to be installed"
kubectl describe providers.pkg
kubectl describe providerrevisions.pkg


Missing obvious question and answer!

Can we turn this feature off, or is it locked to the app version on the phone?
Yes we saw a popup indicating a change....but most people are more concerned at the time in getting access to whatever resource is MFA'd than reading an change in the app.
We have many VIPs that don't like un-notified change and what they perceive as additional friction. This could fall into that category 110%.

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

ID: a46313f6-ce23-85a7-19c3-21152a3cc401
Version Independent ID: 6c09429c-4de0-3bbe-41bc-b0c41ed333bc
Content: Questions & answers about Microsoft Authenticator app - Azure AD
Content Source: articles/active-directory/user-help/user-help-auth-app-faq.md
Service: active-directory
Sub-service: user-help
GitHub Login: @curtand
Microsoft Alias: curtand

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

@wobblewobble which feature are you referring to? App updates, change notifications, or something else?

Marilee
Looks like my MFA auth app was corrupt as it was not showing push
notifications and I had to go into the app to see a push notification.
I've reinstalled the MFA app and it is showing push notifications as well
as an option to turn off biometric.
Is there an organisation option in Intune to disable the biometrics on the
App as we have biometrics on the phone already with a quick lock time.
Regards
Joe McGlynn
P:<PHONE_NUMBER>
E<EMAIL_ADDRESS>On Tue, 6 Oct 2020 at 21:01, Marilee Turscak - MSFT <
<EMAIL_ADDRESS>wrote:

@wobblewobble https://github.com/wobblewobble which feature are you
referring to? App updates, change notifications, or something else?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/63848#issuecomment-704521057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALBXIETL5XHY6BDIIHTC5LSJNZSFANCNFSM4SFJGUUQ
.

Right now individual users can disable app lock. App lock is enabled by default, and it requires either biometric or PIN. https://techcommunity.microsoft.com/t5/azure-active-directory-identity/microsoft-authenticator-app-lock-now-enabled-by-default/ba-p/1257368
Currently it is not possible to do this at the organizational level, but you can make a feature request on User Voice to add this capability: https://feedback.azure.com/
If you share the request with me I can bubble it up to the product team.
Let me know if this helps! If you have further questions feel free to tag me in the comments or reach out over email -<EMAIL_ADDRESS>


Add acend to Support & Training

Thanks for this PR. We currently only list English resources.
@juliusv thoughts?

Thanks for this PR. We currently only list English resources.
@juliusv thoughts?

We list https://www.puzzle.ch/de/prometheus which is in German, this is fine to me.

@roidelapluie good point
@Tobi-Tr whichever you prefer then; I would make certain that it's really obvious that you offer both languages at that landing page.
Do I assume correctly that you will move to the Courses section?


*: make TestBalance of hot-write-region scheduler stable

What problem does this PR solve?
Closes #1496.
What is changed and how it works?
Currently, there is very little probability that TestBalance in hot-write-region scheduler will panic due to balanceHotRetryLimit. Because we only want to check the result of balanceByLeader, but we use a random way to decide it. Unfortunately, if we call balanceByPeer ten times, the test will finally panic.
Check List
Tests

Unit test

Codecov Report

Merging #1503 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #1503      +/-   ##
=========================================
+ Coverage   67.45%   67.5%   +0.05%
=========================================
  Files         158     158
  Lines       15518   15518
=========================================
+ Hits        10467   10476       +9
+ Misses       4109    4095      -14
- Partials      942     947       +5

Impacted Files
Coverage Δ

server/schedulers/hot_region.go
76.83% <100%> (ø)
:arrow_up:

server/etcd_kv.go
63.63% <0%> (-7.28%)
:arrow_down:

server/leader.go
81.09% <0%> (-3.79%)
:arrow_down:

server/util.go
75% <0%> (-2.71%)
:arrow_down:

server/cluster.go
75.06% <0%> (-0.55%)
:arrow_down:

client/client.go
68.06% <0%> (-0.47%)
:arrow_down:

server/grpc_service.go
51.22% <0%> (+0.44%)
:arrow_up:

server/tso.go
72.72% <0%> (+3.4%)
:arrow_up:

server/region_syncer/server.go
81.89% <0%> (+3.44%)
:arrow_up:

server/schedule/basic_cluster.go
92.45% <0%> (+3.77%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


ERROR: Starting in sqlfluff version 0.7.0 the dbt templater is distributed as a separate python package. Please pip install sqlfluff-templater-dbt to use it.

Although I installed (and reinstalled) SQLFLuff with pip install sqlfluff-templater-dbt, I keep getting this SQLFluff error in VS Code.
SQLFluff is working fine in the terminal and I am in the correct Python environment

Adding the path seems to have fixed this

Adding the path seems to have fixed this


Error while installing rbac-manager using helm

We have mistakenly delete namespace where rbac-manager is installed which delete all pods. Now when i am trying to install rbac-manager using helm chart it is throwing below error.
helm install rbac-manager ./rbac-manager --namespace rbac-manager
Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: namespace: , name: rbac-manager, existing_kind: rbac.authorization.k8s.io/v1beta1, Kind=ClusterRole, new_kind: rbac.authorization.k8s.io/v1beta1, Kind=ClusterRole

Hi Varun,
You can try kubectl delete clusterrole rbac-manager and kubectl delete clusterrolebinding rbac-manager. That should clean everything up

Thank you that helped.