This code chooses best model on test set instead of validation set.

At utils/train.py, the train process returns the best MRR and HIT on TEST SET, RESPECTIVELY:
def train(self, epochs, log_interval=100):
    # ...
    for epoch in range(epochs):
        self.model.train()
        for batch in self.train_loader:
        # ...
        mrr, hit = evaluate(self.model, self.test_loader, self.device)  # mrr and hit on test set
        # ...
        max_mrr = max(max_mrr, mrr)  # best mrr on test set
        max_hit = max(max_hit, hit)  # best hit on test set
        self.epoch += 1
    return max_mrr, max_hit  # <- It's NOT OK to return best mrr and hit on TEST SET, RESPECTIVELY

I believe this code is not the final version, please update it to the code used in your paper.

This is actually a common practice in session-based recommendation. The same setting was adopted in some previous works such as STAMP, SR-GNN, and FGNN, and in some recently published works such as DHCN and TAGNN. We could even find the same setting in other fields of recommender systems, such as LightGCN and NGCF.
Despite the popularity of our setting, I agree with you that in principle, we should choose the best model on the validation set and evaluate the model on the test set. The common approach is to first extract a most recent fraction of the data as the test set, and then extract a most recent fraction of the remaining data as the validation set. But this approach may also have a problem, i.e., the distributions of the validation set and the test set are different because their collection times are different, so the performance on the validation set does not reveal the true performance on the test set. I guess this is part of the reason some existing methods did not adopt the correct-in-principle approach. I think a better approach is to first extract a most recent fraction of the data and then randomly split it into the validation and test sets. But I did not think of this approach when we published this work.
In conclusion, I think our setting is OK because it is very common. Besides, it is used for all models in our experiments. The comparison of models' performance is fair.
You could update our code to use the validation set to select the best model. It should be quite easy. However, we would not update our code to make it consistent with our paper.

This is actually a common practice in session-based recommendation. The same setting was adopted in some previous works such as STAMP, SR-GNN, and FGNN, and in some recently published works such as DHCN and TAGNN. We could even find the same setting in other fields of recommender systems, such as LightGCN and NGCF.
Despite the popularity of our setting, I agree with you that in principle, we should choose the best model on the validation set and evaluate the model on the test set. The common approach is to first extract a most recent fraction of the data as the test set, and then extract a most recent fraction of the remaining data as the validation set. But this approach may also have a problem, i.e., the distributions of the validation set and the test set are different because their collection times are different, so the performance on the validation set does not reveal the true performance on the test set. I guess this is part of the reason some existing methods did not adopt the correct-in-principle approach. I think a better approach is to first extract a most recent fraction of the data and then randomly split it into the validation and test sets. But I did not think of this approach when we published this work.
In conclusion, I think our setting is OK because it is very common. Besides, it is used for all models in our experiments. The comparison of models' performance is fair.
You could update our code to use the validation set to select the best model. It should be quite easy. However, we would not update our code to make it consistent with our paper.

Still confused by this common practice, but thanks for your reply.

Still confused by this common practice, but thanks for your reply.


Upload fails on files larger than ChunkSize

I use google Api with UWP project
Nugets(Google.Apis 1.31.0-beta01, Google.Apis.Auth 1.31.0-beta01, Google.Apis.Drive.v3 <IP_ADDRESS>4) were installed.
I try upload file on google drive.
public async UploadAsync(string parentId, string fileName, IStorageFile inputFile, CancellationToken ct)
{
    var body = new Google.Apis.Drive.v3.Data.File() {
        Name = fileName,
        Parents = new List<string>() { parentId }
    };
    using (var streamFile = await inputFile.OpenReadAsync()) {
        using (var stream = streamFile.AsStreamForRead()) {
            stream.Position = 0;
            var uploadRequest = _driveService.Files.Create(body, stream, inputFile.ContentType);
            uploadRequest.Fields = "id, name";
            uploadRequest.ProgressChanged += (obj) =>
            {
                    Debug.WriteLine($"sent - {obj.BytesSent}");
            };
            await uploadRequest.UploadAsync(ct);

            var file = uploadRequest.ResponseBody;
            Debug.WriteLine($"file - {file.Id}, {file.Name}");
        }
    }
}

I can only upload files < 10MB (by default). For large files(>10MB) UploadAsync doesn't finish and obj.BytesSent always 0.
When I change uploadRequest.ChunkSize the upload limit also changes.

I do something very like this for Storage all the time, and it's fine - certainly from console apps.
Are you able to reproduce this issue with a console app, or does it only happen in UWP? Are any exceptions thrown, or does the task just never complete?

I don't try console apps and exceptions aren't thrown. Task can be cancelled by CancellationToken.
p.s. Download works with large files

Could you try a console app using the same code as far as you can? Knowing whether this is a UWP-specific issue or not would be a great first step.

Console app can upload file(>10MB) successfully. The code is the same with a small difference in getting the stream.
Console app code:
string filePath;
using (var stream = new System.IO.FileStream(filePath, System.IO.FileMode.Open))

UWP app code:
IStorageFile inputFile;
using (var streamFile = await inputFile.OpenReadAsync()) {
    using (var stream = streamFile.AsStreamForRead())
...

Okay, so this is only a problem on UWP. At the moment, UWP is an unsupported platform, but we are working on UWP support - so we'll need to make sure this works at that point too.
10MB is the size at which the upload uses multiple chunks, so presumably the problem is somewhere there.

Closing as UWP is an unsupported platform. Will re-open and investigate if we add support for UWP.


emsciptenStdenv: allow reuse without ./autogen.sh

The configure phase of emscriptenStdenv expects an ./autogen.sh script,
which is annoying when this step is not needed. Good example is
emscriptenPackages.zlib which needs to override configurePhase.
Testing
I built all emscriptenPackages (json_c, zlib, libxml2) without regression.
Libxml2 still failes and the rest is building, but the output is not usable.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

please rebase your patch and i will merge it. looks good, just compiled everything lcoally.

Rebase done, thanks!


Travis build flake failure

$ ./travis/build.sh
+PATH=/home/travis/depot_tools:/home/travis/.pub-cache/bin:/home/travis/dart-sdk/bin:/home/travis/bin:/home/travis/.local/bin:/opt/pyenv/shims:/home/travis/.phpenv/shims:/home/travis/perl5/perlbrew/bin:/home/travis/.nvm/versions/node/v7.4.0/bin:/home/travis/.kiex/elixirs/elixir-1.4.5/bin:/home/travis/.kiex/bin:/home/travis/.rvm/gems/ruby-2.4.1/bin:/home/travis/.rvm/gems/ruby-2.4.1@global/bin:/home/travis/.rvm/rubies/ruby-2.4.1/bin:/home/travis/gopath/bin:/usr/local/phantomjs/bin:/usr/local/phantomjs:/usr/local/neo4j-3.2.1/bin:/usr/local/clang-3.9.0/bin:/home/travis/.gimme/versions/go1.7.4.linux.amd64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/travis/.rvm/bin:/home/travis/.phpenv/bin:/opt/pyenv/bin
+cd ..
+flutter/tools/gn --unoptimized
gn gen --check in out/host_debug_unopt
Done. Made 397 targets from 164 files in 11079ms
+ninja -C out/host_debug_unopt generate_dart_ui
ninja: Entering directory `out/host_debug_unopt'
[13/13] STAMP obj/flutter/lib/snapshot/generate_dart_ui.stamp
+flutter/travis/analyze.sh
Analyzing frontend_server...
Analyzing dart:ui library...
+flutter/travis/licenses.sh
Verifying license script is still happy...
Resolving dependencies...
Downloading archive 1.0.27...
Downloading args 0.13.7...
Downloading crypto 2.0.1...
Downloading collection 1.9.1...
Downloading convert 2.0.1...
Downloading charcode 1.1.1...
Downloading path 1.4.0...
Downloading typed_data 1.1.3...
 Please run
    pub --trace get
and include the logs in an issue on https://github.com/dart-lang/pub/issues/new
The command "./travis/build.sh" exited with 1.

This is a bug in pub (it doesn't handle 502s apparently). I'm going to close it here on the assumption that we raised it with pub already since this bug is old now.


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.11.31 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MultiLevel

Can we have multi level in this Expandable ListView??
expecting +ve response...

+1

+1

+1000


Potential issue: http://unpkg is searched for widget source

When loading 3rd party widgets, like say beakerx, we search on http://unpkg for the source for the widget. A user might not expect us to be downloading source for them (as it could be a potential security risk).
Potential options to resolve this:

Warn before downloading (with a do not ask me again)
Search on disk in the current environment for the matching JS, fallback to 1 if still can't be found
Ship a bunch of 3rd party widgets with our source and fallback to 1 if still can't be found
Ask the user to run a custom command to install the widget (this is what jupyter lab does)

#1 is already done (close). This is to track #2.

Fixed as part of #10921


Warning spam: Unexpected field name numRecords for remove action

Environment
Delta-rs version: 0.5.7
Binding: Python
Environment:

Cloud provider: Azure
OS: Ubuntu 18.04
Other: Python 3.8

Bug
What happened:
We get an enormous spam of warning logs
[2022-05-30T18:54:37Z WARN  deltalake::action] Unexpected field name `numRecords` for remove action: Row { fields: [("path", Str("part-00031-24527240-103f-4850-b36a-96523433d62d-c000.snappy.parquet")), ("deletionTimestamp", Long(1653935751443)), ("dataChange", Bool(false)), ("extendedFileMetadata", Bool(true)), ("partitionValues", MapInternal(Map { entries: [] })), ("size", Long(1444)), ("tags", Null), ("numRecords", Null)] }

It looks like I get one warning log for every remove action in the transaction log of my table.
What you expected to happen:
Opens the table without logging warnings which I'm pretty sure are un-important.
How to reproduce it:

Use delta-spark 1.2.1
Create a test delta table and apply some random modifications until you've made enough transactions to create a checkpoint.
Try to create a deltalake.DeltaTable object from that table.
You should see a bunch of warnings like the one I included above.

Python script I created to reproduce:
reproduce_deltalake_warnings.zip
More details:
I think a new version of delta-spark has introduced this new numRecords field so I guess delta-rs needs to be updated to handle this. It would be really nice to have a fix for this :slightly_smiling_face: . For large tables with long history retention these warnings are pretty unmanageable.
I have put a hack in my code which sets the env var RUST_LOG="error" to work around this for now.

Looks like this was introduced in https://github.com/delta-io/delta/commit/6f396301f74bea16ad27404a7c79e9aa698d6e2c.
@kamcheungting-db, @scottsand-db should we update the official spec to reflect this change?

I'm pretty keen to get this sorted so I'm going to have a go at making a PR for it. I've never used rust before so we'll see how it goes...


feat: initial update Vpc.Vpn -> Infrastructure.Vpn

Changelist:

moved infrastructure.vpc.vpn to infrastructure.vpn
fixed tests

@Al-Pragliola re-run the ci later and then merge the pr


Use argparse in deepweeds converter to specify paths

Feel free to do the same for cwfid, @hlydecker

Good changes; I has been thinking about something like this previously. I've updated the cwfid following your example and it works nicely.


Local RSS support?

As the title says, can we get local RSS support?
Not everybody is using a feed service. This is especially needed if you can't add Feedly support.

I will not work on local RSS support in this app. You can use the desktop app or many other mobile apps if you need local RSS.

I will not work on local RSS support in this app. You can use the desktop app or many other mobile apps if you need local RSS.

“Any other rss app? It’s quite misleading to pay for the app only to find out we can’t even add external RSS feeds. Another app I can’t use. I don’t use rss services.


🐛 [firebase_messaging] Inconsistent behavior with background message handler callback on Android.

What happened?
Firebase Cloud Messaging plugin's background message handler doesn't always work correctly. The message raised from Flutter debug console is W/FirebaseInstanceId(17720): Service took too long to process intent: com.google.android.c2dm.intent.RECEIVE App may get closed.. I get this "error" most of the times. See related issue #2181 and pull request #1774 (which claims to solve this issue). I was doing some sqlite operations with moor_flutter on that method and I completely ignored them for now. Right now the handler method is like this:
  Future<dynamic> _handleBackgroundMessage(Map<String, dynamic> message) async {
    print('message received');
    return Future<void>.value();
  }

And it doesn't event print 'message received'.
Steps to reproduce
Steps to reproduce the behavior:

Use firebase_messaging: 7.0.3,
Send only a data (not notification) message with Firebase Admin SDK (this shouldn't be important at this point),

Plugin Registry
Application.kt
class Application : FlutterApplication(), PluginRegistrantCallback {
    override fun onCreate() {
        super.onCreate()
        FlutterFirebaseMessagingService.setPluginRegistrant(this)
    }

    override fun registerWith(registry: PluginRegistry) {
        FirebaseCloudMessagingPluginRegistrant.registerWith(registry);
        SqflitePluginRegistrant.registerWith(registry)
    }
}

FirebaseCloudMessagingPluginRegistrant.kt
object FirebaseCloudMessagingPluginRegistrant {
    fun registerWith(registry: PluginRegistry) {
        if (alreadyRegisteredWith(registry)) {
            return
        }
        FirebaseMessagingPlugin.registerWith(registry.registrarFor("io.flutter.plugins.firebasemessaging.FirebaseMessagingPlugin"))
    }

    private fun alreadyRegisteredWith(registry: PluginRegistry): Boolean {
        val key = FirebaseCloudMessagingPluginRegistrant::class.java.canonicalName
        if (registry.hasPlugin(key)) return true
        registry.registrarFor(key)
        return false
    }
}

flutter doctor -v
[√] Flutter (Channel stable, 1.22.2, on Microsoft Windows [Version 10.0.18362.1139], locale en-US)
    • Flutter version 1.22.2 at C:\Users\asus\Documents\SDK\flutter-stable
    • Framework revision 84f3d28555 (3 weeks ago), 2020-10-15 16:26:19 -0700
    • Engine revision b8752bbfff
    • Dart version 2.10.2

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\asus\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

Flutter dependencies
- animations 1.1.2 [flutter]
- background_fetch 0.6.0 [flutter]
- cached_network_image 2.3.2+1 [flutter flutter_cache_manager octo_image]
- clipboard 0.1.2+8 [flutter]
- collection 1.15.0-nullsafety.3
- connectivity 0.4.9+3 [flutter meta connectivity_platform_interface connectivity_macos connectivity_for_web]
- crypto 2.1.5 [collection convert typed_data]
- dio 3.0.10 [http_parser path]
- dotted_border 1.0.6 [flutter path_drawing]
- equatable 1.2.5 [collection meta]
- extended_nested_scroll_view 1.0.1 [flutter]
- extended_sliver 1.0.1 [flutter]
- eyro_toast 0.1.0 [flutter]
- firebase_core 0.5.0+1 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_messaging 7.0.3 [meta flutter firebase_core]
- flare_flutter 2.0.6 [flutter flare_dart meta]
- fluentui_icons 0.2.0 [flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_bloc 6.0.6 [flutter bloc provider]
- flutter_local_notifications 1.4.4+3 [flutter platform flutter_local_notifications_platform_interface]
- flutter_localizations 0.0.0 [flutter intl characters collection meta path typed_data vector_math]
- flutter_mobx 1.1.0+2 [mobx flutter]
- flutter_secure_storage 3.3.5 [meta flutter]
- flutter_slidable 0.5.7 [flutter]
- flutter_svg 0.19.0 [path_drawing xml vector_math meta flutter]
- get_it 5.0.1 [async meta]
- hive 1.4.4+1 [meta crypto]
- hive_flutter 0.3.1 [flutter hive path_provider path]
- html 0.14.0+4 [csslib source_span]
- image_cropper 1.3.1 [flutter]
- image_picker 0.6.7+11 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- just_audio 0.5.4 [just_audio_platform_interface audio_session rxdart path path_provider async uuid flutter]
- logging 0.11.4
- meta 1.3.0-nullsafety.3
- mobx 1.2.1+3 [meta]
- modal_progress_hud 0.1.3 [flutter]
- moor_flutter 3.1.0 [moor sqflite meta path flutter]
- path_provider 1.6.18 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- provider 4.3.2+2 [flutter nested collection]
- pull_to_refresh 1.6.2 [flutter]
- pull_to_refresh_notification 1.1.2 [flutter]
- rxdart 0.24.1
- share 0.6.5+2 [meta mime flutter]
- signalr_client 0.1.6 [flutter logging w3c_event_source]
- sticky_headers 0.1.8+1 [flutter meta]
- timeago 2.0.27
- uni_links 0.4.0 [flutter]
- url_launcher 5.7.2 [flutter url_launcher_platform_interface url_launcher_web url_launcher_linux url_launcher_macos url_launcher_windows]

dev dependencies:
- build_runner 1.10.2 [args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style glob graphs http_multi_serv
er io js logging meta mime path pedantic pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span strea
m_channel string_scanner term_glyph typed_data]
- hive_generator 0.7.3 [build source_gen hive analyzer dartx]
- mobx_codegen 1.1.1+1 [analyzer build build_resolvers meta mobx path source_gen]
- moor_generator 3.3.1 [collection recase meta path json_annotation stream_transform args logging cli_util moor sqlparser analyzer analyzer_plugin source_span build buil
d_resolvers build_config source_gen]
- retrofit_generator 1.4.0 [dio source_gen built_collection code_builder tuple retrofit analyzer dart_style build]

dependency overrides:
- analyzer 0.39.17 [_fe_analyzer_shared args charcode cli_util collection convert crypto glob html meta package_config path pub_semver source_span watcher yaml]

transitive dependencies:
- _fe_analyzer_shared 7.0.0 [meta]
- analyzer_plugin 0.3.0 [analyzer charcode dart_style html meta path pub_semver]
- args 1.6.0
- async 2.5.0-nullsafety.1 [collection]
- audio_session 0.0.9 [flutter flutter_web_plugins rxdart]
- bloc 6.0.3 [meta]
- boolean_selector 2.1.0-nullsafety.1 [source_span string_scanner]
- build 1.3.0 [analyzer async convert crypto logging meta path glob]
- build_config 0.4.2 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_daemon 2.1.4 [built_collection built_value http_multi_server logging pedantic path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 1.3.11 [analyzer build crypto graphs logging path package_config pub_semver]
- build_runner_core 6.0.1 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pedantic pool
timing watcher yaml]
- built_collection 4.3.2 [collection quiver]
- built_value 7.1.0 [built_collection collection fixnum quiver]
- characters 1.1.0-nullsafety.3
- charcode 1.2.0-nullsafety.1
- checked_yaml 1.0.2 [json_annotation source_span yaml]
- cli_util 0.1.4 [path]
- clock 1.1.0-nullsafety.1
- code_builder 3.5.0 [built_collection built_value collection matcher meta]
- connectivity_for_web 0.3.1+2 [connectivity_platform_interface flutter_web_plugins flutter]
- connectivity_macos 0.1.0+5 [flutter]
- connectivity_platform_interface 1.0.6 [flutter meta plugin_platform_interface]
- convert 2.1.1 [charcode typed_data]
- csslib 0.16.2 [source_span]
- dart_style 1.3.6 [analyzer args path source_span]
- dartx 0.5.0 [collection path crypto characters time meta]
- fake_async 1.2.0-nullsafety.1 [clock collection]
- ffi 0.1.3
- file 5.2.1 [intl meta path]
- firebase 7.3.0 [http http_parser js]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.0 [firebase firebase_core_platform_interface flutter flutter_web_plugins meta js]
- fixnum 0.10.11
- flare_dart 2.3.4
- flutter_blurhash 0.5.0 [flutter meta]
- flutter_cache_manager 1.4.2 [flutter path_provider uuid http path sqflite pedantic clock file rxdart]
- flutter_local_notifications_platform_interface 1.0.1 [flutter plugin_platform_interface]
- flutter_plugin_android_lifecycle 1.0.11 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- glob 1.2.0 [async collection node_io path pedantic string_scanner]
- graphs 0.2.0
- http 0.12.2 [http_parser path pedantic]
- http_multi_server 2.2.0 [async]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- image_picker_platform_interface 1.1.1 [flutter meta http plugin_platform_interface]
- intl 0.16.1 [path]
- io 0.3.4 [charcode meta path string_scanner]
- js 0.6.2
- json_annotation 3.1.0
- just_audio_platform_interface 1.1.0 [flutter meta plugin_platform_interface]
- matcher 0.12.10-nullsafety.1 [stack_trace]
- mime 0.9.7
- moor 3.3.1 [meta convert collection synchronized pedantic sqlite3]
- nested 0.0.4 [flutter]
- node_interop 1.1.1 [js]
- node_io 1.1.1 [node_interop path]
- octo_image 0.3.0 [flutter flutter_blurhash]
- package_config 1.9.3 [path charcode]
- path 1.8.0-nullsafety.1
- path_drawing 0.4.1+1 [vector_math meta path_parsing flutter]
- path_parsing 0.1.4 [vector_math meta]
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 0.0.4+4 [flutter]
- path_provider_platform_interface 1.0.3 [flutter meta platform plugin_platform_interface]
- path_provider_windows 0.0.4+1 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.9.2 [meta]
- petitparser 3.1.0 [meta]
- platform 2.2.1
- plugin_platform_interface 1.0.3 [meta]
- pool 1.4.0 [async stack_trace]
- process 3.0.13 [file intl meta path platform]
- pub_semver 1.4.4 [collection]
- pubspec_parse 0.1.5 [checked_yaml json_annotation pub_semver yaml]
- quiver 2.1.3 [matcher meta]
- recase 3.0.0
- retrofit 1.3.4+1 [meta dio]
- shelf 0.7.9 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 0.2.3 [shelf web_socket_channel stream_channel]
- sky_engine 0.0.99
- source_gen 0.9.7+1 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.8.0-nullsafety.2 [charcode collection path term_glyph]
- sqflite 1.3.1+1 [flutter sqflite_common path]
- sqflite_common 1.0.2+1 [synchronized path meta]
- sqlite3 0.1.6 [collection ffi meta]
- sqlparser 0.10.1 [meta collection source_span charcode]
- stack_trace 1.10.0-nullsafety.1 [path]
- stream_channel 2.1.0-nullsafety.1 [async]
- stream_transform 1.2.0
- string_scanner 1.1.0-nullsafety.1 [charcode source_span]
- synchronized 2.2.0+2
- term_glyph 1.2.0-nullsafety.1
- test_api 0.2.19-nullsafety.2 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- time 1.3.0
- timing 0.1.1+2 [json_annotation]
- tuple 1.0.3 [quiver]
- typed_data 1.3.0-nullsafety.3 [collection]
- url_launcher_linux 0.0.1+1 [flutter]
- url_launcher_macos 0.0.1+8 [flutter]
- url_launcher_platform_interface 1.0.8 [flutter meta plugin_platform_interface]
- url_launcher_web 0.1.4+1 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- url_launcher_windows 0.0.1+1 [flutter]
- uuid 2.2.2 [crypto convert]
- vector_math 2.1.0-nullsafety.3
- w3c_event_source 1.3.2
- watcher 0.9.7+15 [async path pedantic]
- web_socket_channel 1.1.0 [async crypto stream_channel]
- win32 1.7.3 [ffi]
- xdg_directories 0.1.2 [meta path process]
- xml 4.5.1 [collection convert meta petitparser]
- yaml 2.2.1 [charcode collection string_scanner source_span]

I don't see this file in documentation which you have used - FirebaseCloudMessagingPluginRegistrant.kt .
The documentation mentions MainActivity.kt and Appliaction.kt .
Code for MainActivity.kt -
`package com.example.yourpackagename
import io.flutter.embedding.android.FlutterActivity
class MainActivity: FlutterActivity() {
}`
Code for Application.kt -
`package com.example.yourpackagename
import io.flutter.app.FlutterApplication
import io.flutter.plugin.common.PluginRegistry
import io.flutter.plugin.common.PluginRegistry.PluginRegistrantCallback
import io.flutter.plugins.GeneratedPluginRegistrant
import io.flutter.plugins.firebasemessaging.FlutterFirebaseMessagingService
class Application : FlutterApplication(), PluginRegistrantCallback {
override fun onCreate() {
super.onCreate()
FlutterFirebaseMessagingService.setPluginRegistrant(this);
}
override fun registerWith(registry: PluginRegistry?) {
io.flutter.plugins.firebasemessaging.FirebaseMessagingPlugin.registerWith(registry?.registrarFor("io.flutter.plugins.firebasemessaging.FirebaseMessagingPlugin"));
}
}`
Apart from this, you also need to do some changes in the AndroidManifest.xml and app level build.gradle. Assuming that you have done those changes already, I would suggest you to try these changes given above.
Also I would like to know what do you want to do in the background message handler, because even though the background message handler is getting fired consistently in my application but its of no use because I am unable to do anything inside it except from printing some thing in the console.
Seems that the background message handler runs as an isolate, I wanted to use Firestore in background but it isn't possible it seems, because FirebaseApp needs to be initialized which is itself not possible in an isolate.
Therefore, I tried to add what I wanted to do in sharedPreferences, so that I could perform those tasks when the app starts in the foreground, but unfortunately, I am unable to access sharedPreferences in the background message handler as well.
Seems like the backgroundMessageHandler is useless for now..

Hi @firatcetiner
As mentioned above you need to configure background code properly on the Android side
Nevertheless, I tried to reproduce data only payload (Excluding notification on Android)
Paylaod
DATA='{"priority": "high", "data": {"click_action": "FLUTTER_NOTIFICATION_CLICK", "id": "1", "status": "done"}, "to": "dPB1w6TvRnid4pErhW-WCH:APA91bHwrUwt4GqZ13vfpUiz04rRpJuNaTLSYj_a8PvpES1oCg3VWvPOPPTjolIl-A-ZZt95lInRvaygnsCgUEDRsdQv27WV4IswVKawqqABrijS2hum8M1LUncJXnwrFIs54pO7-lEe"}'
curl https://fcm.googleapis.com/fcm/send -H "Content-Type:application/json" -X POST -d "$DATA" -H "Authorization: key=AAAAcVC6H8o:APA91bF9eBcw6f4RbqJ89uYUGJ7RpMm2w0-yU8T8TIJ5LgXbjc91z_WxlOOzsUotZc6kYpqIQs7EnO5Im00xrLNuLpbkZ7VHgtFQ_Jv19W-XMi2dvWLteOZDTo77u8SzPHy-qF1bxBgp"

logs when each payload is sent
V/ActivityThread(16954): scheduleReceiver info = ActivityInfo{e28de0e com.google.firebase.iid.FirebaseInstanceIdReceiver} intent = Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11080010 pkg=com.nevercode.triage cmp=com.nevercode.triage/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) } sync = true hasCode = 210433762
D/ColorExSystemServiceHelper(16954): checkColorExSystemService className = com.google.android.gms.gcm.PushMessagingRegistrarProxy
V/ActivityThread(16954): scheduleReceiver info = ActivityInfo{9d16fc5 com.google.firebase.iid.FirebaseInstanceIdReceiver} intent = Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11080010 pkg=com.nevercode.triage cmp=com.nevercode.triage/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) } sync = true hasCode = 243983015
D/ColorExSystemServiceHelper(16954): checkColorExSystemService className = com.google.android.gms.gcm.PushMessagingRegistrarProxy

As mentioned above you need to configure background code properly on the Android side

@TahaTesser
FirebaseCloudMessagingPluginRegistrant.ks already do that. What's the difference between my code and the one above?

There is a 8.0 dev release out with major reworks to background handling if you want to give the release a try.

@Ehesp Thanks for pointing that out. By 8.0 dev I'm assuming you are referring firebase_messaging (dev) because I already tried that and nothing change.

@firatcetiner is this issue happening on emulator or physical device?
If it's happening on a physical device, which device you are using and have you tried another device?

@mdalihusain All tests are my on physical devices. I have used Xiaomi Redmi Note 8 Pro (Android 10), Xiaomi Mi 6 (Android 9). Should I worry about the manufacturer of device?

@mdalihusain All tests done on physical devices. I have used Xiaomi Redmi Note 8 Pro (Android 10), Xiaomi Mi 6 (Android 9). Should I worry about the manufacturer of device?

It's fine, mine is also Xiaomi Redmi Note 8 Pro (Android 10), and everything is working absolutely fine
I asked about the device because I have read on forums that OnePlus strictly forces to stop background processes..
Only two other reasons I can think because of which the issue is occurring -

might be related to the android manifest.xml and build.gradle configuration...
Which version of firebase messaging have you used in the dependency in build.gradle?
Please upload code of AndroidManifest.xml and build.gradle of possible
Any other flutter plugin is causing issues with Firebase messaging. You should try creating a new project and then try using Firebase messaging.

@mdalihusain Thanks for your help. Here are the files:
AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    package="com.example.myapplication">
    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.ACCESS_NOTIFICATION_POLICY"/>
    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
    <uses-permission android:name="android.permission.VIBRATE"/>
    <uses-permission android:name="android.permission.WAKE_LOCK"/>
    <application
        android:name=".Application"
        android:icon="@mipmap/ic_launcher"
        tools:replace="android:label"
        android:allowBackup="false"
        android:usesCleartextTraffic="true"
        android:fullBackupContent="false"
        tools:targetApi="m">
        <activity
            android:name=".MainActivity"
            android:launchMode="singleTop"
            android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true"
            android:windowSoftInputMode="adjustResize">

            <intent-filter>
                <action android:name="android.intent.action.MAIN"/>
                <category android:name="android.intent.category.LAUNCHER"/>
            </intent-filter>
            <intent-filter>
                <action android:name="FLUTTER_NOTIFICATION_CLICK" />
                <category android:name="android.intent.category.DEFAULT"/>
            </intent-filter>
        </activity>
        <activity
            android:name="com.yalantis.ucrop.UCropActivity"
            android:screenOrientation="portrait"
<EMAIL_ADDRESS>        <meta-data
            android:name="flutterEmbedding"
            android:value="2"/>
        <meta-data
            android:name="io.flutter.app.android.SplashScreenUntilFirstFrame"
            android:value="true"/>
        <meta-data
            android:name="io.flutter.embedding.android.SplashScreenDrawable"
            android:resource="@drawable/launch_background" />
    </application>
</manifest>

build.gradle (module)
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 29

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
    }

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        applicationId "com.exampe.myapplication"
        minSdkVersion 18
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        multiDexEnabled true
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
    compileOptions {
        sourceCompatibility "1.8"
        targetCompatibility "1.8"
    }
    buildToolsVersion = '29.0.2'
}

flutter {
    source '../..'
}

dependencies {
    implementation 'com.google.firebase:firebase-messaging:20.1.0'
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    implementation 'com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava'
    implementation 'com.android.support:multidex:1.0.3'
    testImplementation 'junit:junit:4.13'
    androidTestImplementation 'androidx.test:runner:1.3.0'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'
}

builld.gradle (project)
buildscript {
    ext.kotlin_version = '1.4.10'
    ext {
        compileSdkVersion   = 29                // or higher
        targetSdkVersion    = 29                // or higher
        appCompatVersion    = "1.0.2"           // or higher
    }
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.google.gms:google-services:4.3.3'
        classpath 'com.android.tools.build:gradle:3.6.2'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

allprojects {
    repositories {
        google()
        jcenter()
        maven {
            url "${project(':background_fetch').projectDir}/libs"
        }
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

What's the point of trying this plugin on a new project? I mean we always use other packages/plugins in our projects and it is almost impossible to determine which plugin cause incompatibilities with Firebase Messaging, or vice versa.

The build.gradle and AndroidManifest files seem to be alright...
The point with creating a new application is to make sure that another plugin is causing this issue or the problem is with Firebase messaging itself .

Well if that is the case it means I have to manually check every other plugin separately to see the incompatibilities, which is not ideal for me since I'm using tons of different packages/plugins. Anyway, I will try creating a new project using only Firebase Messaging.

@Ehesp Thanks for pointing that out. By 8.0 dev I'm assuming you are referring firebase_messaging (dev) because I already tried that and nothing change.
Dependency
 firebase_messaging:
    git:
      url: git://github.com/FirebaseExtended/flutterfire
      ref: dev
      path: ./packages/firebase_messaging

We meant 8.0.0-dev.4 - see the migration guide: https://firebase.flutter.dev/docs/migration

I confirm that firebase_messaging 8.0.0-dev.4 resolves this issue and I'm going to close it. Thank you all for your help.

I confirm that firebase_messaging 8.0.0-dev.4 resolves this issue and I'm going to close it, it would be good to have some ideas about when this new rework land on the stable channel. Thank you all for your help

@firatcetiner 1-2 weeks - providing no major issues reported whilst on dev channel.


Endless loop on terraform destroy with nodepool in state "FAILED_DESTROYING"

Description
I provisioned nodepools via terraform. After the nodepool is active I want to destroy them via terraform destroy.
Then terraform runs for more than 30 minutes trying to destroy the nodepool. Looking into the DCD UI i see that the status is "FAILED_DESTROYING" (see screenshot).
When I now cancel the terraform run via STRG-C and rerun it the nodepool get really destroyed in a matter of a few seconds.
Expected behavior
Properly destroy nodepools in state "FAILED_DESTROYING" without the need of a terraform destroy re-run
Environment
Terraform version:
OpenTofu v1.7.2

Provider version:
v6.4.17

OS:

References
https://github.com/ionos-cloud/terraform-provider-ionoscloud/issues/579

Hello! Can you provide the Terraform plan that led to this situation? I want to reproduce this scenario.
Our Terraform provider only sends the DELETE request and then waits for the resource to be deleted. In the case you described, the resource reached FAILED_DESTROYING state for some reason (API-related) so the resource wasn't deleted and the loop kept going. It's not an endless loop, it's a loop that has a specific timeout.
What I think it happened in this scenario (I still need to reproduce this to be sure):

terraform destroy sends the first DELETE request;
DELETE request fails, the API sets the nodepool to FAILED_DESTROYING state;
Terraform periodically checks the deletion of the resource (the loop) but since the resource is always there, in the FAILED_DESTROYING state, Terraform keeps on checking;
you cancel the previous command and then run terraform destroy again which sends another DELETE request, this final DELETE request successfully deletes the nodepool;

Related to the description from Expected behavior:

Properly destroy nodepools in state "FAILED_DESTROYING" without the need of a terraform destroy re-run

As I said above, the provider only sends DELETE requests to the API and waits for the resource to be deleted, the deletion process is handled by the API. If the API sets the resource in FAILED_DESTROYING state, it means that something went wrong during the deletion, it has nothing to do with the TF provider, the provider only sends the requests.

It's not an endless loop, it's a loop that has a specific timeout.

What is the timeout?

The provider did the job, the DELETE request was sent, the fact that the resource was in FAILED_DESTROYING has nothing to do with the provider. You choose to run terraform destroy again, so basically you sent another DELETE request on a resource that was in FAILED_DESTROYING and somehow it worked, but this is solely related to the API.

Mhh, that is passing the buck to and from each other. I think the provider needs to handle API failures appropriately.
For the plan and logs please refer to Internal support ticket Ticket 207171709

@salyh

What is the timeout?

3 hours,  you can see it here.

Mhh, that is passing the buck to and from each other. I think the provider needs to handle API failures appropriately.

It really isn't, besides interrupting the loop when the resource reaches a FAILED_DESTROYING state (I will analyze the implication of this) I don't think that something useful can be implemented. The provider is responsible with taking the data from the tf file and sending it to the API in case of a create/update command and with sending a DELETE request in case of a resource deletion. Let's say that, in the provider, when you receive a FAILED_DESTROYING we send a DELETE request again. There is no guarantee that the result will be different. Also, how many requests should we send before understanding that something is really not working inside the API.
The DELETE request should be done once and the API should take care of it. The provider only needs to check that the resource is properly deleted before informing the user and reflecting that change in the tf state.

I disagree - the provider can (and should) indeed send multiple DELETE requests because:

It wouldn't do any harm
DELETE is idempotent
deal with api failures

@salyh I agree with the points presented above but still, sending multiple DELETE requests doesn't guarantee that your issue will be solved since we are talking about: "Properly destroy nodepools in state "FAILED_DESTROYING" without the need of a terraform destroy re-run". The resource was in FAILED_DESTROYING, I didn't test this but from my experience with other resources, if the deletion failed in the first place, it will fail again, I'm not sure how this worked for you, I didn't play a lot with this API.
I will discuss with my colleagues from the API about this and if indeed multiple DELETE requests can lead to the deletion of the resource (even if the resource is in FAILED_DESTRYOING state), we will implement this mechanism but I'll rather see it as a feature (having the possibility to define a number of retries for a specific request) instead of a bug-solving fix.

terraform will throw an error on reaching any of these states, as they are not recoverable.


allow different XSHUT control mechanisms

In order to use many VL53L1 range sensors, the same number of Xshutdown pins (XSHUT, aka GPIO0) need to be controlled. In case the number of available general purpose output pins on the host microcontroller is not sufficient, the pins must be controlled indirectly. For example using an IO expander or a shift register.
This pull request introduces a possibility to define a subclass which does control the Xshutdown pin of the sensor using a different method. In particular the base class does not require a pin number on creation and does not store such number as member.
Although the previous class definition allows to override the relevant member functions (begin(), end(), VL53L1_On(), VL53L1_Off()) it has some drawbacks:

The invariant part of the overall algorithm, which is not specific on the control method for the pin, must be copied into the
overriding function definition. In particular delay(10);.
The subclass does contain the (inherited) member gpio0 which may not be used.

Instead the previous class VL53L1 has been designated as base class, agnostic of the method on how to control the Xshutdown pins. This class has been renamed to VL53L1Base. It has new private pure virtual helper functions which are used by the relevant member functions (listed above) to set the XSHUT pin high/low, initialize and de-initialize the control mechanism to XSHUT.
A new class called VL53L1 has been defined which does inherit from VL53L1Base and realizes the new helper functions. The helper functions implement the control of the Xshutdown signal using a GPIO number, exactly as the former class VL53L1 did.
The result is the following:

there is still a class VL53L1 which does exactly the same as previously
there is an additional abstract class VL53L1Base which requires the helper functions for the Xshutdown control to be realized

The suggested changes attempt to provide a base class which can be used to control XSHUT in different ways. Without the need to pay attention to the overall algorithm or providing and storing a pin number if not necessary.
The pull request changes many files, as the former class VL53L1 is renamed to VL53L1Base. The interesting change occurs in the vl53l1_class.* files.

Hi @dhebbeker ,
in fact we already have an example of class where the XSHUT pin is controlled from a GPIO expander and you can find it here. In fact the idea to put those methods in the class virtual was due to that scope. Actually in the inherited class the gpio0 pin is put to -1 in order to prevent a wrong usage. I will give a deeper look at your enhancement proposal but unfortunately I'm very busy in this period on other tasks. I hope to have time by July to come back on this PR.
Thanks in advance for your contribution!
Best Regards,
Carlo

Hello @cparata,
thank you for the link to the subclass. It is a very good example!
Best regards
David

I close this PR, because the fix is not really needed. The current code already implements the use case.


fix: support chat mode for chatglm3 and Baichuan2

Problem
The current code don't support chat mode for chatglm3 and Baichuan2, it will ask and answer itself.
Reason
chatglm3
Chatglm3 uses a custom tokenizer interface for word segmentation.
We can see it in https://huggingface.co/THUDM/chatglm3-6b/blob/main/tokenization_chatglm.py#L229-L240
The usage of it is in https://huggingface.co/THUDM/chatglm3-6b/blob/main/modeling_chatglm.py#L1024-L1043
Baichuan2
Baichuan2  situation is similar to chatglm3, but it is more complex and requires modifying the tokenizer.
We can see it in https://huggingface.co/baichuan-inc/Baichuan2-13B-Chat/blob/99fe8c0fb8bfb8e821d281c4302eb98999e50761/generation_utils.py
Similar adaptation codes in other frameworks
https://github.com/lm-sys/FastChat/blob/main/fastchat/model/model_chatglm.py#L86-L90

Using "examples/template baichuan. jinja" during engine startup seems to solve this problem.

在引擎启动期间使用“examples/template baichuan.jinja”似乎可以解决这个问题。

不能完全解决，只能减少出错的概率，本质原因是这些模型把user:这类的内容视为一个命令用特殊的编码处理了，而这个项目是拼接好prompt之后直接全部视为普通文本进行转换的

Using "examples/template baichuan. jinja" during engine startup seems to solve this problem.

It does not solve the problem completely, but only reduces the probability of error. The root of the problem is that these models treat role as a command with a special encoding, and this project is spliced prompt and converted directly as plain text, and the encoding of the final word segmentation result is different between the two methods

thanks for the fix, two comments:

for Baichuan tokenizer change, can you just inherit and override the huggingface implementation now?
for the serving change, it looks like we just want to use build_chat_input instead of apply_chat_template. Is that true?

I'm not sure if there is a way to inherit its class without import BaiChuan2Tokenizer dependency, because if you need to add a dependency, I don't think it makes sense to add a dependency for a model.
Yes, for these models, we do not need to use templates to splice dialogue, but can directly use the interface they provide, in fact, these interfaces are also in a certain way to splice dialogue, but in the coding time to do some special processing

@simon-mo Could you please review my code again in your spare time?

These new versions of the models can directly support VLLM. The old version has recently provided an official alternative solution, so this pull request is no longer valuable.


Design salon structure and create appropriate schema.

Created schema for document with the following fields:

name
location
services
description
imgsrc
rating
review
created_at


Validate SSL configuration before starting server

If SSL certs are not available, then every SSL connection will fail. We should
check for this condition at startup before opening the port. That way if a new
node joins a cluster and its SSL configuration is not ready, it won't try to
start accepting connections that could have gone to a healthy host.

Added a unit test.


Update github-trademark-policy.md

https://gist.github.com/GabrielMMelo/0e146f32d73978bf0d0a06786bcbc96c#gistcomment-3776249

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Hola world thanks peace
On Fri, Jun 11, 2021, 12:17 AM OPENTERMUX @.***>
wrote:

https://gist.github.com/GabrielMMelo/0e146f32d73978bf0d0a06786bcbc96c#gistcomment-3776249
Why:
Closes [issue link]
What's being changed: Check off the following:

I have reviewed my changes in staging (look for the
deploy-to-heroku link in your pull request, then click View
deployment).
For content changes, I have completed the self-review checklist
https://github.com/github/docs/blob/main/CONTRIBUTING.md#self-review.

Writer impact (This section is for GitHub staff members only):

This pull request impacts the contribution experience

I have added the 'writer impact' label
I have added a description and/or a video demo of the changes
below (e.g. a "before and after video")

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/7281
Commit Summary

Update github-trademark-policy.md

File Changes

M content/github/site-policy/github-trademark-policy.md
https://github.com/github/docs/pull/7281/files#diff-7fdc83c3443444002f360364462d925a8fdc1bd5e354b78b37eb8473cb119de0
(11)

Patch Links:

https://github.com/github/docs/pull/7281.patch
https://github.com/github/docs/pull/7281.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/7281, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUM2YKNRMNEMVR7LNVZM4QDTSGTARANCNFSM46QAJLOQ
.

เมื่อ วันศุกร์ที่ 11 มิถุนายน ค.ศ. 2021, Ti6 @.***>
เขียนว่า:

Hola world thanks peace
On Fri, Jun 11, 2021, 12:17 AM OPENTERMUX @.***>
wrote:

https://gist.github.com/GabrielMMelo/0e146f32d73978bf0d0a06786bcbc9
6c#gistcomment-3776249
Why:
Closes [issue link]
What's being changed: Check off the following:

I have reviewed my changes in staging (look for the
deploy-to-heroku link in your pull request, then click View
deployment).
For content changes, I have completed the self-review checklist
https://github.com/github/docs/blob/main/CONTRIBUTING.md#self-review.

Writer impact (This section is for GitHub staff members only):

This pull request impacts the contribution experience
I have added the 'writer impact' label
I have added a description and/or a video demo of the changes
below (e.g. a "before and after video")

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/7281
Commit Summary

Update github-trademark-policy.md

File Changes

M content/github/site-policy/github-trademark-policy.md
<https://github.com/github/docs/pull/7281/files#diff-
7fdc83c3443444002f360364462d925a8fdc1bd5e354b78b37eb8473cb119de0>
(11)

Patch Links:

https://github.com/github/docs/pull/7281.patch
https://github.com/github/docs/pull/7281.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/7281, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
AUM2YKNRMNEMVR7LNVZM4QDTSGTARANCNFSM46QAJLOQ>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/7281#issuecomment-859310163, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARZ3XJAT652DCYYKUEGMAFDTSGUBFANCNFSM46QAJLOQ
.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Neither the name of OVH SAS nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.


Allow using composite PK in M:N pivot tables

Currently SQL drivers require auto increment PK in M:N pivot tables. Add support for using composite PK there, allowing current behaviour via user-defined order column, but using composite PK as the default.
BREAKING CHANGE
To preserve stable order in collections, users will need to define the order column as id.

Available in 3.0.0-alpha.28.


Improve republish documents

Equivalent to: https://github.com/alphagov/specialist-publisher/pull/483
Hat tip to @heathd for helping with this.
Successfully tested in development.

:+1:


rclone: 1.63.0 -> 1.63.1

Diff: https://github.com/rclone/rclone/compare/v1.63.0...v1.63.1
Changelog: https://github.com/rclone/rclone/blob/v1.63.1/docs/content/changelog.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 244073 run on x86_64-linux 1

7 packages built:

celeste
git-annex-remote-rclone
librclone
rclone
rclone.man
restic
restique

Maybe we should do
patches = rclone.patches or [ ];

Added. Thanks!


Feat implement sign protocol

(This branched out from create-interactive-fill-in PR)

it only creates attestation with title & content hash
this can be used as start point to implement sign protocol :)

I didn't add create draft from audit as I didn't have time :(

Once the draft is attested it should

remove audit from draft list (in localstorage)
add audit to audit list (in localstorage)

But currently this steps takes really long time
so I checked the network tab and realized that the sign protocol library is sending endless call to rpc :) ...
For me it worked after waiting for really long time, and I suspect maybe the network is busy and library doesn't detect the updated transaction quick enough. (couldn't verify it yet but atm transaction takes longer than usual)

try {
      createAttestation(draft, client);
      await new Promise(resolve => setTimeout(resolve, 3000));
      notification.success("Attestation created");
      // Update the draft to be attested
      removeDraftAudit(draft.id);
      addAudit({
        ...draft,
        attestationId,
        attestedAt: new Date(),
      });
      router.push(`/`);
  } catch (e) {
    console.error(e);
    notification.error("Attestation failed");
  }

as I don't show the attestationId anywhere yet.


Add target to build dev images

@rgolangh this fixes the build of the images, but there is an issue with the installed backstage instance that denies any request with 401 (unauthorized) to any endpoint, including the MTA at POST /api/orchestrator/workflows/MTAAnalysis/execute
2024-04-21T07:14:39.620201885Z stdout F warn: Unable to read url, Error: Request failed for https://api.github.com/repos/parodos-dev/workflow-software-templates/contents/entities/workflow-resources.yaml?ref=main, 401 Unauthorized {"entity":"location:default/generated-ea85e27c2119a1a3afe84ddfc682f0e59f6191de","location":"url:https://github.com/parodos-dev/workflow-software-templates/blob/main/entities/workflow-resources.yaml","plugin":"catalog","service":"backstage","timestamp":"2024-04-21 07:14:39"}
2024-04-21T07:14:39.622069506Z stdout F warn: Unable to read url, Error: Request failed for https://api.github.com/repos/janus-idp/software-templates/contents/showcase-templates.yaml?ref=main, 401 Unauthorized {"entity":"location:default/generated-98132841081663352e4f33a642801f62e24befe0","location":"url:https://github.com/janus-idp/software-templates/blob/main/showcase-templates.yaml","plugin":"catalog","service":"backstage","timestamp":"2024-04-21 07:14:39"}


Depends on CC Tweaked, CC Modded is an alternative

In CurseForge the mod depends on CC Tweaked. this will also likely be true in Minecraft as well. please add CC Modded as an alternative to CC Tweaked so it can be used too.

Ok, so i just tried it with CC: Modded, it seems they got rid of an essential method i was using throughout and upon further talks with other CC developers, I have decided not to support CC: Modded

ok I will go talk about re-adding it over at CC: Modded.


Fb multitenancy ws api

This change is

Reviewed 31 of 31 files at r1.
Review status: 27 of 28 files reviewed at latest revision, 3 unresolved discussions.

oscm-installation/install/patch-SSO.xml, line 84 at r1 (raw file):

            <filter token="SSO_STS_METADATA_URL" value="${SSO_STS_METADATA_URL}" />
          </filterset>
        </copy>

Can we delete here more than filterset?

oscm-tenantmgmt/javasrc/org/oscm/tenant/dao/TenantDao.java, line 98 at r1 (raw file):

        String value = (String) query.getSingleResult();
        return value;
    }

Why native query here? It is not performance critical.

oscm-webservices/javasrc/org/oscm/webservices/handler/UserKeyQuery.java, line 30 at r1 (raw file):

        return "SELECT pu.tkey FROM PlatformUser pu JOIN organization o on pu.organizationkey=o.tkey where o.tenant_tkey is null and pu.userid=?";
    }

Does this query search for user in default tenant?

Comments from Reviewable

Hello @kowalczyka, it seems fine to me. I have some comments, please answer or fix. Please make a detailed review in your team.

Current coverage is 58.69% (diff: 40.00%)

Merging #363 into master will decrease coverage by <.01%

@@             master       #363   diff @@
==========================================
  Files          1933       1933
  Lines         98567      98574     +7
  Methods           0          0
  Messages          0          0
  Branches      12235      12235
==========================================
+ Hits          57857      57858     +1
- Misses        37648      37654     +6
  Partials       3062       3062

Powered by Codecov. Last update 035edaf...aa1ca62

Review status: 27 of 28 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

oscm-installation/install/patch-SSO.xml, line 84 at r1 (raw file):
Previously, StavrevaS (Suzana Stavreva) wrote…
> Can we delete here more than filterset?

Not really. We must leave copying of wsit and webservices config files - as without this we have no STS related webservices definitions. I only removed ther proccess of patching the STS configuration settings. To delete this part we would have to change the default configuration. Do you think we should proceedd in this direction?

oscm-tenantmgmt/javasrc/org/oscm/tenant/dao/TenantDao.java, line 98 at r1 (raw file):
Previously, StavrevaS (Suzana Stavreva) wrote…
> Why native query here? It is not performance critical.

Should I prepare the named query instead?

oscm-webservices/javasrc/org/oscm/webservices/handler/UserKeyQuery.java, line 30 at r1 (raw file):
Previously, StavrevaS (Suzana Stavreva) wrote…
> Does this query search for user in default tenant?

Yes.  It search users in default tenant.

Comments from Reviewable

@stavrevas  could you please comment my answers and questiona so that we could  proceed with this issue?

Review status: 27 of 28 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from Reviewable

Review status: 27 of 28 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

oscm-installation/install/patch-SSO.xml, line 84 at r1 (raw file):
Previously, kowalczyka (Arkadiusz Kowalczyk) wrote…
> Not really. We must leave copying of wsit and webservices config files - as without this we have no STS related webservices definitions. I only removed ther proccess of patching the STS configuration settings. To delete this part we would have to change the default configuration. Do you think we should proceedd in this direction?

It is OK, no changes here.

oscm-tenantmgmt/javasrc/org/oscm/tenant/dao/TenantDao.java, line 98 at r1 (raw file):
Previously, kowalczyka (Arkadiusz Kowalczyk) wrote…
> Should I prepare the named query instead?

Yes. We should avoid native if no reason for that.

Comments from Reviewable

Review status: 16 of 53 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

oscm-tenantmgmt/javasrc/org/oscm/tenant/dao/TenantDao.java, line 98 at r1 (raw file):
Previously, StavrevaS (Suzana Stavreva) wrote…
> Yes. We should avoid native if no reason for that.

Done.

Comments from Reviewable

Reviewed 19 of 31 files at r1, 1 of 2 files at r2, 21 of 26 files at r3, 1 of 1 files at r4, 14 of 14 files at r5.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable


run：python setup.py build develop，has error

when i run command：python setup.py build develop ，i got
No CUDA runtime is found, using CUDA_HOME='C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.5'
E:\develop2\Anaconda3\envs\lanedet\lib\site-packages\setuptools\installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer
is deprecated. Requirements should be satisfied by a PEP 517 installer.
  warnings.warn(
running build
running build_py
running egg_info
writing lanedet.egg-info\PKG-INFO
writing dependency_links to lanedet.egg-info\dependency_links.txt
writing requirements to lanedet.egg-info\requires.txt
writing top-level names to lanedet.egg-info\top_level.txt
reading manifest file 'lanedet.egg-info\SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'lanedet.egg-info\SOURCES.txt'
creating build\lib.win-amd64-3.8\lanedet\ops\csrc
copying lanedet\ops\csrc\nms.cpp -> build\lib.win-amd64-3.8\lanedet\ops\csrc
copying lanedet\ops\csrc\nms_kernel.cu -> build\lib.win-amd64-3.8\lanedet\ops\csrc
running build_ext
E:\develop2\Anaconda3\envs\lanedet\lib\site-packages\torch\utils\cpp_extension.py:304: UserWarning: Error checking compiler version
for cl: [WinError 2] 系统找不到指定的文件。
  warnings.warn(f'Error checking compiler version for {compiler}: {error}')
building 'lanedet.ops.nms_impl' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com
/visual-cpp-build-tools/

I dont know what happened.
Need i install Microsoft Visual C++ 14.0 or greater ? Or had i  do something wrong?

This issue is duplicated.
Refer this: https://github.com/Turoad/lanedet/issues/51.

This issue is duplicated. Refer this: #51.
Thanks for your replying.I got that error yesterday on windows10.(Now I guess the solution is to install a C compiler).
I ran it again on the Linux server and some other errors occurred. I blogged about these mistakes and how to fix them so that the next generation wouldn't have to face the same problem again. This is the website: https://www.cnblogs.com/swx123/p/16194224.html

This issue is duplicated. Refer this: #51.这个问题是重复的。请参考： #51 。
Thanks for your replying.I got that error yesterday on windows10.(Now I guess the solution is to install a C compiler). 感谢您的回复。我昨天在 windows10 上遇到了这个错误。（现在我想解决方案是安装 C 编译器）。
I ran it again on the Linux server and some other errors occurred. I blogged about these mistakes and how to fix them so that the next generation wouldn't have to face the same problem again. This is the website: https://www.cnblogs.com/swx123/p/16194224.html 我在Linux服务器上再次运行它，出现了一些其他错误。我在博客中介绍了这些错误以及如何修复它们，以便下一代不必再次面临同样的问题。这是网站：https://www.cnblogs.com/swx123/p/16194224.html

Did you run it successfully on the win system? There is a problem with my virtual machine and I can only try it on the win system. Currently, I have also encountered this problem and cannot solve it.

This issue is duplicated. Refer this: #51.这个问题是重复的。请参考： #51 。
Thanks for your replying.I got that error yesterday on windows10.(Now I guess the solution is to install a C compiler). 感谢您的回复。我昨天在 windows10 上遇到了这个错误。（现在我想解决方案是安装 C 编译器）。
I ran it again on the Linux server and some other errors occurred. I blogged about these mistakes and how to fix them so that the next generation wouldn't have to face the same problem again. This is the website: https://www.cnblogs.com/swx123/p/16194224.html 我在Linux服务器上再次运行它，出现了一些其他错误。我在博客中介绍了这些错误以及如何修复它们，以便下一代不必再次面临同样的问题。这是网站：https://www.cnblogs.com/swx123/p/16194224.html

Did you run it successfully on the win system? There is a problem with my virtual machine and I can only try it on the win system. Currently, I have also encountered this problem and cannot solve it.

@awslhh8
sry,i only success on ubuntu,can't help u more.
otherwise,i think virtual machine has some diffrents with true machine on GPU,so true machine maybe a better choice .
good luck.


MySQL cross reference script contains duplicates

The cross_reference-mysql.sql contains duplicates of each record. I discovered the issue when I loaded the script in MySQL and found twice the number of records then in the sqlite version. I ran the following distinct query to confirm if each record had been duplicated:
select count(*) from (select distinct vid, sv from cross_reference) a;
I initially raised the concern in my pull request #10 and another user PaulBrownMagic verified the finding against the original source file by using the following bash command:
sort cross_references.txt | uniq | wc -l
I would have happily supplied a fix by now but I'm not familiar with MySQL. I'm happy to fix if anybody has some tips.

I've created a fix in a fork and a matching pull-request #12.


fix(DIA-67): do not perform image resize in HeroRails

This PR resolves DIA-67
Description
Looks like Image by default performs a resize in Gemini impacting the quality(check screenshots), the image becomes very blurry. This PR avoids the resize and improves the quality of the HeroUnitsRail.

Before
After

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

improve hero rails image quality - araujobarret

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (improve hero rails image quality - araujobarret)

  Generated by :no_entry_sign: dangerJS against 12e06a4f454a879c6eb5da78566d9ed11c8fa6b4

Love it - thanks for this @araujobarret !! 🙌


Release request of OCMock

Can we have a new release on OCMock as this can unlock Firebase Message support on watchOS #4016. Thanks!

Will do it on the weekend.

Made the release now. I'll wait about 24h before pushing to CocoaPods.

Awesome! Please keep us posted. Thank you!

It's on CocoaPods now. So, closing this issue.

Thank you!


Mempool Collector Stats

Some early stats about transactions collected and stored with the mempool-collector:
Data collection
JSON file example: https://github.com/flashbots/mempool-archiver/blob/main/docs/example-tx-summary.json
Per hour:

70k - 100k transactions
150 - 500MB of JSON files written

Extrapolated to a day:

Up to 2.5M transactions
Up to 12 GB disk usage

Data size & compression
Looking at one particular hour specifically: 2023-08-04 UTC between [01:00, 02:00[:

Unique tx: 78,757 (find ./ -type f | wc -l)
Disk usage: 373 MB (du --si -s)
Apparent size: 134 MB (du --si -s --apparent-size)
Average file size: 1.584 KB (ls -l | gawk '{sum += $5; n++;} END {print n" "sum" "sum/n;}')

gzip individual JSON files:

Typical file size reduction: 50%
But: since the files are very small it doesn't actually decrease the disk usage:

$ du --si -s *
373M    h01
350M    h01_gz

$ du --si -s * --apparent-size
134M    h01
76M     h01_gz

more about "apparent-size": https://man7.org/linux/man-pages/man1/du.1.html
   --apparent-size
              print apparent sizes rather than device usage; although
              the apparent size is usually smaller, it may be larger due
              to holes in ('sparse') files, internal fragmentation,
              indirect blocks, and the like

zipping an hourly folder:

80% reduction in disk space needed (373 MB -> 77 MB)

$ zip -r h01 h01

$ ls -alh h01.zip
-rw-r--r-- 1 ubuntu ubuntu 74M Aug  4 10:30 h01.zip

$ du --si h01.zip
77M     h01.zip

$ du --si h01.zip --apparent-size
77M     h01.zip

indeed, disk usage reports the actually used disk space by the file.  since the filesystem stored data in blocks, then a non-sparse file will occupy diskBlockSize * roundUp(fileSize / diskBlockSize) >= fileSize.  therefore zipping many small (smaller than diskBlockSize) files is not going to change much with respect to actual disk usage.

$ du --si -s *
373M    h01
350M    h01_gz
$ du --si -s * --apparent-size
134M    h01
76M     h01_gz

Some stats after creating a summary file of 1,423,508 transactions in JSON and Parquet format:

Format
Size

CSV
314 MB

Parquet
118 MB

Perhaps the individual tx JSON file should also not contain the signature, to save 20-40% of the storage space, and because the signature is part of the rawTx anyway 🤔

everything is part of the rawtx, apart from timestamp and chainId

It's still convenient for the summarizer service not needing to parse every single rawTx and extracting the fields, although that doesn't seem too much to ask either.
I'm still undecided whether it's preferable to have the collector store some fields, or only store rawTx + timestamp

On a semi-related note: i'm still undecided whether we should store the timestamp in millis or microseconds. The problem being that microsecond precision might give the wrong impression -- that it's a reliable number. But imagine the data is coming over the network from a more distant EL node, even milliseconds will not be entirely reliable due to the network latency.


Announce 4.168.0 release

I applied Wilfred's suggestions and added a mention of universal packages.


added fade on hover button

Fixes #39  🔐
Are you a part of LGM SOC' 21 ❓

[x] Yes ✔
[ ] No ✖

Describe the changes you've made 🏆
Added fade on hover button.
Type of change 🖇
Please delete options that are not relevant.

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

Checklist: 📋

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Please create a new branch at your end and raise a PR from that branch.


Update chart readme

Once this is merged, I will commit directly the readme to gh-pages.

Once this is merged, I will commit directly the readme to gh-pages.

I see that the index.yaml file is autogenerated by the GitHub action. Could we automate the README.md distribution as well?

Added 2 GHA steps to prepare a folder with docs, and then push it to gh-pages.
An example of a succesful job run: https://github.com/viccuad/helm-charts/runs/3717738510?check_suite_focus=true#step:7:53
And the resulting gh-pages: https://viccuad.github.io/helm-charts/

Merging, it's going to the new-architecture branch, so we can review the final PR to main later on.

Closes https://github.com/kubewarden/helm-charts/issues/32.


Can't import the named export 'JsonViewer' (imported as 'JsonViewer') from default-exporting module (only default export is available)

issue

Can't import the named export 'JsonViewer' (imported as 'JsonViewer') from default-exporting module (only default export is available)

env

typescript
react 17
webpack 5

sample code
import { JsonViewer } from '@textea/json-viewer'

export function Test({ data }: { data: object }) {
  return <JsonViewer value={data} />
}

Why is the error occurring?

Can you share the repo or a minimal reproducible stackbliz/codesandbox?

Try add "allowSyntheticDefaultImports": true to your tsconfig.json

I can't disclose it because it's a company project, so I'm applying it to nextJS tutorial and sharing it.

https://github.com/pouu69/nextjs-dashboard/blob/main/app/page.tsx#L14
If you check the above repo, the error message is different, but it seems that a similar error occurs in the end.

Try add "allowSyntheticDefaultImports": true to your tsconfig.json

The error occurs as usual.

With the new App Directory, React Components are categorized into two: Server Components and Client Components, and by default they are all Server Component as mentioned in: Using Server Components in Next.js.
Components that need hooks (context, use...) need to be classified as Client Components and they need to have the directive "use client" at the top of the source file before any import.

I will add this part to the document and see if this "use client" directive should be added by JsonViewer itself.

However, the actual project is not nextjs, but the client component method.

Can you build a minimum reproduction with the same stack (ts, webpack...etc)?

Can you build a minimum reproduction with the same stack (ts, webpack...etc)?

I made it into a small structure in the next git.
Another error is occurring this time.

https://github.com/pouu69/react-json-test

Can you build a minimum reproduction with the same stack (ts, webpack...etc)?

@pionxzh
I made it into a small structure in the below git. Another error is occurring this time.

https://github.com/pouu69/react-json-test

https://github.com/pouu69/react-json-test/blob/main/src/App.tsx#L7

I have a fixed above error (screenshot)
I wrote a below cdoe on webpack config
resolve: {
  alias: {
      'react/jsx-dev-runtime': require.resolve('react/jsx-dev-runtime'),
      'react/jsx-runtime': require.resolve('react/jsx-runtime')
  }
}

What else can I fix for  you? It works ok on my machine.
I also checked the react/jsx-runtime error. Seems it can also be fixed by upgrading react to 18. I'm not too sure about the reason.

After checking the error message, I feel your webpack is choosing the browser field in package.json. Will remove it in the next version.

Can you try to update to v3.3.1 and see if it works?

What else can I fix for you? It works ok on my machine.
I also checked the react/jsx-runtime error. Seems it can also be fixed by upgrading react to 18. I'm not too sure about the reason.

Did you check if it works on v17 because I use react17?

Yes, it works on the repo you provided. However, I might still need a reproduction to determine the issue.
Your workaround for the react/jsx-runtime error is okay. However, I recommend migrating the project to React 18.
The error message you mentioned in the title shall be fixed by v3.3.1. Please test and let me know the result in your project 🙏

Any update? I will close first due to the inactivity.


Make item.js enums available to high level code

https://github.com/MephisTools/diablo2-protocol/blob/master/lib/utils/item.js
it would be useful to be able to use these enum to avoid hardcoding numbers in high level code

done
https://github.com/MephisTools/node-diablo2-data/commit/853ce601ba883ee4e1b721d6cd7928e9434f6416


https://flask2-python-template.vercel.app/

Not Found

Indeed, not found.
$ curl 'https://flask2-python-template.vercel.app/'
The deployment could not be found on Vercel.

DEPLOYMENT_NOT_FOUND

What was this supposed to be? Are you having a problem with your deploy?


Youtube fails to authenticate consistently

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.05.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
**Failed:**
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u':ytwatchlater', u'-u', u'PRIVATE', u'-p', u'PRIVATE', u'-v', u'-s', u'-j', u'--flat-playlist']
[debug] Encodings: locale ANSI_X3.4-1968, fs ANSI_X3.4-1968, out None, pref ANSI_X3.4-1968
[debug] youtube-dl version 2017.05.01
[debug] Python version 2.7.9 - Linux-3.14.0-kirkwood-tld-1-armv5tel-with-debian-8.5
[debug] exe versions: avconv 11.6-6, avprobe 11.6-6, ffmpeg 0.8.20-6
[debug] Proxy map: {}
WARNING: unable to log in: bad username or password
ERROR: This playlist does not exist.
Traceback (most recent call last):
  File "/usr/lib/python2.7/youtube_dl/YoutubeDL.py", line 760, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python2.7/youtube_dl/extractor/common.py", line 429, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python2.7/youtube_dl/extractor/youtube.py", line 2504, in _real_extract
    _, playlist = self._extract_playlist('WL')
  File "/usr/lib/python2.7/youtube_dl/extractor/youtube.py", line 2046, in _extract_playlist
    raise ExtractorError(message, expected=True)
ExtractorError: This playlist does not exist.

**Worked a couple minutes later (after a few tries):**
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u':ytwatchlater', u'-u', u'PRIVATE', u'-p', u'PRIVATE', u'-v', u'-s', u'-j', u'--flat-playlist']
[debug] Encodings: locale ANSI_X3.4-1968, fs ANSI_X3.4-1968, out None, pref ANSI_X3.4-1968
[debug] youtube-dl version 2017.05.01
[debug] Python version 2.7.9 - Linux-3.14.0-kirkwood-tld-1-armv5tel-with-debian-8.5
[debug] exe versions: avconv 11.6-6, avprobe 11.6-6, ffmpeg 0.8.20-6
[debug] Proxy map: {}
...
<end of log>

Description of your issue, suggested solution and other information
Youtube fails to authenticate consistently...works 50/50. I think it is related to new sign-in page.
https://support.google.com/accounts/answer/7338427?visit_id=0-636291563247234608-2983872999&p=signin_newlook&rd=1.

Duplicate of #12927.


Gather Text to assess performance

Gather a few different paragraphs, papers, or sentences which should be good use cases for shorter path. We can then use these pieces of text to manually compare different models or prompts.

Duplicate of #7


Calling -[RLMResults count] many times is very slow as it always reruns the query

In #850, -[RLMResults count] was changed to avoid materializing a TableView in order to get the count. This improved the performance of a single call to -count, but dramatically slowed down repeated calls. This was somewhat mitigated by the fact we were still eagerly materializing TableViews in other situations. After #2125, -count always reruns the query unless you first do some other operation that materializes the TableView.

It should be possible to have -count cache the result and only rerun the query only when we've advanced to a new version of the data. This would be much like what TableView::sync_if_needed provides.

I don't think there's any particular reason not to cache the result other than that RLMResults already has an unpleasant amount of state and it hasn't been a source of complaints.

I just ran into this. Kind of surprised me.


TypeError: Cannot read property 'latlng' of undefined

Hi,
I'm trying to get x,y coordinates on mouse move. And I'm getting error  when I trying to get it.

TypeError: Cannot read property 'latlng' of undefined
at mouseMove (dashboard:593)
at HTMLDivElement.onmousemove (dashboard:442)

Hi, great to hear that you find Leaflet useful!
However, this issue tracker is used for reporting bugs and discussing new features. For questions on using Leaflet, please use gis.stackexchange.com or stackoverflow.
If you are really sure that this is a bug in leaflet, or a feature request, please change the wording to make it look like a bug report.

Hii
This is my code I m looking for a output as a google map and I didn't get anything means no error and no result...
import React, { Component } from 'react'
import GoogleMapReact from 'google-map-react'
const AnyReactComponent = ({ text }) => { text };
class Map extends Component {
static defaultProps = {
center: { lat: 20.59, lng: 78.96 },
zoom: 11
};
render() {
return (
console.log('lat'),
<GoogleMapReact
bootstrapURLKeys={{key:"AIzaSyDb2piJIdDqoNSBYP-ut06K95wgGispQUg"}}
defaultCenter={ this.props.center }
defaultZoom={ this.props.zoom }
>
<AnyReactComponent
lat={ 20.5937 }
lng={  78.9629 }
text={'India'}
/>

);
}
}
export default Map;

@marthasankar this is Leaflet issue tracker, not Google Map


Last question in My Interest in Research (likert scale) does not look good on mobile, text overflows containers

The Answers should be stacked vertically on such a small view.

Closed with fd1842e74f14e1ab028e9365b874ca40a310921a


Prepare for Istanbul

What was wrong?
Istanbul is coming! Multiple EIPs incoming!
How was it fixed?
This PR just adds the necessary boilerplate to start Istanbul updates. It does not integrate with anything at all yet. Basically dead code.
Cute Animal Picture

Seems worth adding a test to make sure that we can create a chain and execute a transaction with it, I guess with a Constantinople opcode. It's okay if this test will fail later as Istanbul gets updated, we'll just upgrade the test.
For lint, it looks like there are some imports to remove from opcodes.py

@carver The linting error doesn't seem right since I am using all of those imports in as_opcode()
Am I doing something incorrectly where it sees this as dead code or something? Seem strange!

@carver The linting error doesn't seem right since I am using all of those imports in as_opcode()
Am I doing something incorrectly where it sees this as dead code or something? Seem strange!

Do you have some local changes that didn't get pushed or something? as_opcode() isn't being called in eth/vm/forks/istanbul/opcodes.py

Added tests for what I could see that copies Constantinople. The ethereum tests repo would probably be updated for the newer opcodes, but everything works as is now.

Ahhh, I see what I was doing wrong! I was looking at the branch where I added the opcode for eip-1344.
Will push a fix

Crap, it really doesn't seem to like an empty UPDATED_OPCODES, so I guess I'll just remove the rest of the boilerplate for that.

Note: a later PR will have to add back commits https://github.com/ethereum/py-evm/pull/1751/commits/225c119fc19b921fe1d20bafa967cc83d333ac24 and https://github.com/ethereum/py-evm/pull/1751/commits/d53a14dbb44732375ab762e3cfc0ea3509792ee8

Adding it here should get Istanbul included in quite a few tests:
https://github.com/ethereum/py-evm/blob/30eb1ae4a2d77db0f63e9a635345cc3ac718d9b8/tests/conftest.py#L71-L83

Oh nice, I missed that one. Will add!

We should create a checklist and put it somewhere in the developer documentation for creating a new VM.  This PR seems like a good template for that.


Use of undeclared type 'FSCalendarMonthPosition'

When I install FSCalendar and attempt to use it, it will always give me the error:
Use of undeclared type 'FSCalendarMonthPosition'
This does not allow me to use FSCalendarMonthPosition in the didselect function because of that.
Integration method: Cocoapods
Steps:
1.Add  pod 'FSCalendar' to podfile and install.
2. Create view controller with a calendar.
3. Create UIViewController file and add code.
Device modal and IOS version: iPhone 6s IOS 10.2
XCode version: 8.2.1
FSCalendar Version: 2.3.3
This does NOT happen in the demo project in FSCalendar-master/Example-Swift

Hey i'm getting the same problem. Did you find solution for it?

Hey got it.. use below method
```

func calendar(_ calendar: FSCalendar, didSelect date: Date) {
}

Hey got it.. use below method..
func calendar(_ calendar: FSCalendar, didSelect date: Date) { }

This type is introduced in a later version than 2.3.3. The latest is 2.7.1.

I'm seeing this error today too after installing. Downloaded the demo project from here and built/worked no problems at all. XCode 10.
What other setting(s) are required to incorporate this library cleanly into a project ?


add getters for pool stats

move the getter for numActive to the Pool<...> base class, and add a few other pool statistics getters.
we'd love to have these exposed to allow us to have metrics on the pool, and alert if we detect that we're leaking connections

@2bitoperations Thanks for your effort. Merged your PR to master, 2.6, 2.7 branches.


Exec tachikoma update<PHONE_NUMBER>1906

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage decreased (-0.009%) to 99.695% when pulling bc3ccf7c9702ede67fb850f68f59de78b093157b on pazjacket:tachikoma/update-20160331151906 into 77a776d257a2436999eb722afb99b372b7aa9f95 on hoshinotsuyoshi:master.


[Laravel 10.*] Artisan commands not working

Hello dear,
I just create new laravel project and install laravel-selfupdater.
Everything works perfectly and I thank you for that.
But non of artisan commands working in self-updater.php at all, I don't have any idea how can I fix this.
Commands are executed directly through the console without any problems.
self-updater.php file:
    'artisan_commands' => [
        'pre_update' => [
//            'tkt:pre-update' => [
//                'class' => \App\Console\Commands\PreUpdateCommand::class,
//                'params' => []
//            ]
        ],
        'post_update' => [
            'tkt:post-update' => [
                'class' => \App\Console\Commands\UpdateCommand::class,
                'params' => []
            ]
        ],
    ],

UpdateCommand.php file:
<?php

namespace App\Console\Commands;

use Illuminate\Console\Command;
use Illuminate\Support\Facades\Artisan;

class UpdateCommand extends Command
{
    protected $name = 'tkt:post-update';
    protected $signature = 'tkt:post-update';
    protected $description = 'Upgrade commands';
    public function handle()
    {
        Artisan::call('migrate');
    }
}

I think this should work correctly but it doesn't!
What do you think is the problem?

After going through the code, it seems the base source classes do not have the functionality to call the pre_update and post_update commands. Not sure if it's an intended omission or the library is still in development, but there is a way to make this work, just replace from the example
$this->updater->source()

with the following
$sourceRepository = new SourceRepository($this->updater->source(), $this->updateExecutor);

if ($sourceRepository->isNewVersionAvailable()) {

  // Your fetch and update code ...

  $sourceRepository->preUpdateArtisanCommands();

  $updated = $sourceRepository->update($release);

  if ($updated) {
      $sourceRepository->postUpdateArtisanCommands();
  }
}

where $this->updateExecutor can be injected as a dependency as shown below (or using app())
    public function __construct(private readonly UpdaterManager $updater, private readonly UpdateExecutor $updateExecutor)
    {
        parent::__construct();
    }

Don't forget the relevant imports
use Codedge\Updater\Models\UpdateExecutor;
use Codedge\Updater\SourceRepository;
use Codedge\Updater\UpdaterManager;

Thanks buddy! At that time I was very much waiting for a solution to solve my problem, but unfortunately the development was stopped. Anyway, I will check the solution you provided. I hope we can use it in future projects.


[Task]: Ballerina/OMElement Intergration

Description
This element is a key part of the Apache Axis2's AXIOM (AXIs Object Model) library, designed for efficient creation, manipulation, and management of XML documents, especially in web services contexts. When integrating Ballerina with libraries utilizing Axis2, it becomes necessary to convert Ballerina values to and from OMElements.
Describe your task(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
[ ] Facilitate a method to Convert Ballerina XML to Apache.axiom.OMElement - #42006
[ ] Facilitate a method to convert Apache.axiom.OMElement to Ballerina XML - #42007
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

22/01/2024 Update

Completed OMElement to BXML Conversion
Completed BXML to OMELEMENT Conversion
Added Test Cases to Both conversion methods
Currently checking method to add separate namespaces for attributes

23/01/2024 Update
For the attributes separate namespaces can be added


Rename proj dep

Proj4 was renamed to the new upstream name "proj."

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Viacoin: fix 0.15.1 docker

I know you won't host it, but anyways always clean to have something fixed.
Just in case another person will find your repo with viacoin.

should I close this?


Fix prefix xpath test

This PR completes #121 and #118.
The test was fixed; some of it was due to sloppy XPath, for which I opened #128

Thank @mielvds !
Fix #118


⚠ SolarQuery has degraded performance

In e98770a, SolarQuery ($SOLARQUERY_URL) experienced degraded performance:

HTTP code: 200
Response time: 653 ms

Resolved: SolarQuery performance has improved in 108281d.


Timeline Improvements

📒 Description
It contains all minor things that we could improve the Timeline feature
💻 Environment
Platform: macOS
Acceptance Criteria

[ ] After creating new time entry, the Timeline view will be reloaded from the call in library -> Cause the editor jumps

Additional issues: https://github.com/toggl/toggldesktop/pull/3036#issuecomment-519103677

Closed with #3195