Error: Singleton with CrossbowAdMob name not found or haven't registered

Crossbow version
0.2.3
What you did
Code:
use crossbow::android::*;

#[macroquad::main("project_name")]
async fn main() -> anyhow::Result<()> {

  let crossbow = CrossbowInstance::new();
  let admob: admob_android::AdMobPlugin = crossbow.get_plugin()?;

  loop {
    clear_background(WHITE);
    draw_rectangle(0., 0., 100., 100., BLUE);
    next_frame().await;
  }
}

What went wrong
I get black screen and error: Singleton with CrossbowAdMob name not found or haven't registered (adb logcat)
Thanks for all your help

Merry Christmas! Sorry for the late response.
Have you added everything required in Cargo.toml as specified in this link?

Wish you same.
I think I added all things required. I got only problem with this one:
[[package.metadata.android.manifest.application.meta_data]]
I got error that I need to add some "package" property to it (when building using crossbundle).
I've tried other plugins and I get same problems.

@kacper-cholewinski can you paste error message or your Cargo.toml? Also, did you try running examples?

The error is:
error: Invalid metadata in manifest: missing field packagefor keyandroid.manifest``
for:
[[package.metadata.android.manifest.application.meta_data]]
name = "com.google.android.gms.ads.APPLICATION_ID"
value = "ca-app-pub-3940256099942544~3347511713"

@kacper-cholewinski ... Also, did you try running examples?
That's where I've first encountered the problem.

Happy New Year btw

@kacper-cholewinski Happy New Year too.
This error looks like you forgot to specify the android manifest package in Cargo.toml:

Sorry friend, I can't reproduce this error in any example on my mac and it looks like our CI doesn't have this issue. Can you provide more info about your setup, Cargo.toml, and full error message?

Thanks for help again
I did as you suggested and now I'm in starting point:
PanicInfo { payload: Any { .. }, message: Some(called `Result::unwrap()` on an `Err` value: SingletonNotRegistered("CrossbowAdMob")), location: Location { file: "src\\__cargo_apk_mainaqyhhg.tmp", line: 11, col: 65 }, can_unwind: true }

Cargo.toml:
[package]
name = "project_name"
version = "0.1.0"
authors = REDACTED
edition = "2021"

[dependencies]
crossbow = "*"
log = "0.4"
anyhow = "1.0"
macroquad = "=0.3.7"
admob-android = "0.2.3"
crossbow-android = "0.2.3"
play-core = "0.2.3"

[patch.crates-io]
miniquad = { git = "https://github.com/not-fl3/miniquad", rev = "d67ffe6950cf73df307e2d23aaa4726f14399985" }

[package.metadata]
app_name = "Macroquad"
assets = ["assets"]
icon = "assets/icon.png"

[package.metadata.android]
app_wrapper = "quad"
release_build_targets = ["aarch64-linux-android"]
plugins_remote = ["com.crossbow.admob:admob:0.2.3", "com.crossbow.play_core:play_core:0.2.3"]

[package.metadata.android.manifest]
package = "com.crossbow.example.permissions"

[package.metadata.android.manifest.uses_sdk]
min_sdk_version = 19
target_sdk_version = 31

[[package.metadata.android.manifest.uses_permission]]
name = "android.permission.INTERNET"

[[package.metadata.android.manifest.application.meta_data]]
name = "com.google.android.gms.ads.APPLICATION_ID"
value = "ca-app-pub-3940256099942544~3347511713"

[package.metadata.apple]
release_build_targets = ["aarch64-apple-ios", "x86_64-apple-ios"]

main.rs:
use macroquad::prelude::*;

use crossbow_android::*;

#[macroquad::main("project_name")]
async fn main() {
  let crossbow = CrossbowInstance::new();
  // info!("initializing play core");
  // let play_core: play_core::PlayCorePlugin = crossbow.get_plugin().unwrap();
  info!("initializing admob");
  let admob: admob_android::AdMobPlugin = crossbow.get_plugin().unwrap();

  loop {
    clear_background(WHITE);
    draw_circle(100., 100., 100., BLUE);
    next_frame().await;
  }
}

I'm not experienced android developer and I know it wasn't good idea to start with developing mobile apps in rust (in current mobile ecosystem state), but I like this technology so much, that's why we are here :)
I hope it will help you figure out the problem

Hey, I succeeded in running your Cargo.toml (also I changed the main.rs code to the following):
use macroquad::prelude::*;
use macroquad::ui::{hash, root_ui, Skin};

use crossbow_android::*;

#[macroquad::main("project_name")]
async fn main() {
  let crossbow = CrossbowInstance::new();
  // info!("initializing play core");
  // let play_core: play_core::PlayCorePlugin = crossbow.get_plugin().unwrap();
  info!("initializing admob");
  let admob: admob_android::AdMobPlugin = crossbow.get_plugin().unwrap();

  let skin = get_skin();
  let window_skin = skin.clone();

  loop {
    clear_background(WHITE);

    root_ui().push_skin(&window_skin);
    root_ui().window(hash!(), vec2(0.0, 50.0), vec2(1000.0, 1000.0), |ui| {
        if ui.button(vec2(-15.0, 250.0), "Show ad") {
            if !admob.is_initialized().unwrap() {
                println!("Calling AdMob::initialize()");
                admob.initialize(true, "G", false, true).unwrap();
            }
            if admob.is_initialized().unwrap() && !admob.is_interstitial_loaded().unwrap() {
                println!("Calling load_interstitial()");
                admob.load_interstitial("ca-app-pub-3940256099942544/1033173712").unwrap();
            }
            if admob.is_interstitial_loaded().unwrap() {
                println!("Calling show_interstitial()");
                admob.show_interstitial().unwrap();
            }
        }
    });
    root_ui().pop_skin();

    // draw_circle(100., 100., 100., BLUE);

    next_frame().await;
  }
}

fn get_skin() -> Skin {
  let label_style = root_ui()
      .style_builder()
      .text_color(Color::from_rgba(180, 180, 120, 255))
      .font_size(30)
      .build();
  let window_style = root_ui()
      .style_builder()
      .background_margin(RectOffset::new(20.0, 20.0, 10.0, 10.0))
      .margin(RectOffset::new(-20.0, -30.0, 0.0, 0.0))
      .build();
  let button_style = root_ui()
      .style_builder()
      .background_margin(RectOffset::new(37.0, 37.0, 5.0, 5.0))
      .margin(RectOffset::new(10.0, 10.0, 0.0, 0.0))
      .text_color(Color::from_rgba(180, 180, 100, 255))
      .font_size(40)
      .build();
  let editbox_style = root_ui()
      .style_builder()
      .background_margin(RectOffset::new(0., 0., 0., 0.))
      .text_color(Color::from_rgba(120, 120, 120, 255))
      .color_selected(Color::from_rgba(190, 190, 190, 255))
      .font_size(50)
      .build();
  Skin {
      editbox_style,
      window_style,
      button_style,
      label_style,
      ..root_ui().default_skin()
  }
}

So the result is the following:

@kacper-cholewinski Can you try running this command: crossbundle run android --log? The --release flag probably has some issues.

So, I copied your code and still have same issue.
I think it could be important to add, that im using -s=native-apk flag, cause without it I got some error during daemon initializing:

@kacper-cholewinski Look, strategy native-apk builds it without gradle. It will not add plugins. Can you try build with command I mentioned and paste error log?

I pasted screenshot od error above

Looks like something is wrong with generated Gradle project. It's very hard to understand what the problem is from this error message as we with @Heezay don't have this problem... I wonder, perhaps you can try to upload somewhere generated Gradle project so that I will take a look.

I'm not sure if I know what you mean, but: https://github.com/kacper-cholewinski/crossbow-plugins
There is my whole workspace with target folder and Cargo.lock included, I hope it would help.


Few suggestions to improve tzindex

Provide non-docker build mechanism, not everyone has a docker installed and want to use, some prefer using LXC or KVM or any other type of virtualization, so maybe just add default make target to build using go and another target to build docker, should be easy, e.g.:

BUILD_TARGET=tzindex
BUILD_VERSION=dev
BUILD_COMMIT=$(git rev-parse --short HEAD)
REPO=blockwatch.cc/tzindex
VERSION=$BUILD_VERSION-$BUILD_COMMIT

# clean everything
go clean

# update dependencies
go mod download

CGO_ENABLED=0 go build -a -v -o ./${BUILD_TARGET} -ldflags "-w -X ${REPO}/cmd.VERSION=${BUILD_VERSION} -X ${REPO}/cmd.GITCOMMIT=${BUILD_COMMIT}" ${BUILD_TARGET}.go
strip ./${BUILD_TARGET}

Tag every stable release with a version and provide basic changelog. I see there is a v005 on github as a latest release, maybe switch to different version notation, e.g. v005-1.0 as I understand v005 means protocol number (protocol 005 stands for babylon) on tezos

Add shortcuts for --v --vv --vvv -v -vv -vvv as it's much easier to input and most linux/unix programs use one dash instead of two for verbose

If you try to run tzindex without specifying config.json it will fail and try to access https://<IP_ADDRESS>:8732 instead of the default one http://<IP_ADDRESS>:8732 and it's very hard to figure out for beginners that there is an issue in http scheme as there is no option in help of tzindex to switch tls on or off. Would be nice to add --tls option in the help and also switch it off by default.

Thanks!

Thanks,

1, 2 and 4 are resolved in v5.2.0
3 is GNU/Posix style and will not be fixed (it's part of an upstream dependency https://github.com/spf13/pflag)

hey @echa many thanks for the update!


 It uses member variable as the input of constructor rather than insert statement or delete statement. This PR also fixed some bugs of insert test and delete test.

Could you delete the old constructors for inset and delete plan which use statements, if not used anymore?

Don't you think we can keep the old constructor to make some tests convenient, like this: https://github.com/cmu-db/peloton/blob/master/test/planner/planner_test.cpp#L71

I don't think we should keep deprecated APIs for the convenience of tests. That can cause trouble later on. Could you help replace the test with the new API?

Coverage decreased (-0.09%) to 54.889% when pulling 21d2ae97c1a2fe2bb1f0068fc055d128489aafcc on Michael-Tieying-Zhang:master into 544e94dbaf719e70c8cd413460852b80d2ae53a2 on cmu-db:master.

Agree!

@malin1993ml is correct. Delete old API calls if the code doesn't use them anymore.

Coverage decreased (-0.08%) to 54.899% when pulling 842b0657d59534653c77879f3107e3cb97bc6887 on Michael-Tieying-Zhang:master into 544e94dbaf719e70c8cd413460852b80d2ae53a2 on cmu-db:master.

Done.


Reindexing of One Datasource using another Input Datasource gives 0 Hyperloglog values

I am facing an issue with reindexing a datasource (which involves HLL Metrics using Datasketches HLLSketch) using another datasource.
Original_Datasource - Dimensions D1,D2,D3,D4. Metrics - M1, M2, M3, M4
Cardinality_Datasource - Dimensions D1, D2. Metrics - D3Cardinality, D4Cardinality using HLLSketch. (I want to maintain cardinality of dimensions D3 and D4 for each combination of D1 and D2).
I want to reindex Cardinality_Datasource using Original_Datasource, using the following spec
{
  "type": "index_parallel",
  "spec": {
    "dataSchema": {
      "dataSource": "Cardinality_Datasource",
      "timestampSpec": {
        "column": "_time",
        "format": "auto"
      },
      "dimensionsSpec": {
        "dimensions": [
          "D1",
          "D2"
        ]
      },
      "metricsSpec": [
        {
          "name": "D3Cardinality",
          "type": "HLLSketchBuild",
          "fieldName": "D3"
        },
        {
          "name": "D4Cardinality",
          "type": "HLLSketchBuild",
          "fieldName": "D4"
        }
      ],
      "granularitySpec": {
        "type": "uniform",
        "segmentGranularity": "hour",
        "queryGranularity": "hour"
      }
    },
    "ioConfig": {
      "type": "index_parallel",
      "inputSource": {
        "type": "druid",
        "dataSource" : "Original_Datasource",
        "interval": "2020-08-11T00/2020-08-11T01"
      }
    },
    "tuningConfig": {
      "type": "index_parallel",
      "maxNumConcurrentSubTasks": 3
    }
  }
}

With this specification, I can see D1 and D2 dimensions in Cardinality_Datasource table but D3Cardinality and D4Cardinality values are all 0. Can someone please help me with this issue?

May I know if anyone can help me on this issue?

You may be running into https://github.com/apache/druid/issues/9914

Thank you for sharing the link. That helped!


SpriteContainer alpha is not applied to its children

Setting the alpha value for SpriteContainer does not update its appearance. Setting 0 will make it invisible any positive value is same as setting 1.
Example: http://jsfiddle.net/sd0fa1qa/
Left sprite has container with alpha=1, right sprite has container with alpha=0.1 and yet apperance is the same. Setting alpha value for the actual sprite works as expected.

Found the bug. SpriteContainer alpha is completely ignored in _drawWebGLKids and only child alpha is used. Since BitmapText is also in essence a sprite container in disguise this applies to it as well.
Here is my fix to webgl-0.8.2 for others stumbling to this same problem. I'm too busy at the moment to test this further and make a pull request.
@@ -975,7 +975,8 @@ this.createjs = this.createjs||{};
vertices = this._vertices,
numVertexPropertiesPerBox = SpriteStage.NUM_VERTEX_PROPERTIES_PER_BOX,
maxIndexSize = SpriteStage.MAX_INDEX_SIZE,

                  maxBoxIndex = this._maxBoxesPerDraw - 1;

                  maxBoxIndex = this._maxBoxesPerDraw - 1,

                  alphaFactor = 1;

@@ -1030,6 +1031,13 @@ this.createjs = this.createjs||{};
this._drawTexture = texture;
}

                  if (kid.parent != null &&

                      (kid.parent._spritestage_compatibility === 1 || kid.parent._spritestage_compatibility === 3)) {

                      alphaFactor = kid.parent.alpha;

                  } else {

                          alphaFactor = 1;

                  }

@@ -1063,7 +1071,7 @@ this.createjs = this.createjs||{};
vertices[offset + 8]  = vertices[offset + 13] = vEnd;
                            // Alphas:

                          vertices[offset + 4] = vertices[offset + 9] = vertices[offset + 14] = vertices[offset + 19] = kid.alpha;

                          vertices[offset + 4] = vertices[offset + 9] = vertices[offset + 14] = vertices[offset + 19] = (kid.alpha * alphaFactor);

@@ -1080,8 +1088,12 @@ this.createjs = this.createjs||{};
                    // Draw children:
                    if (kid.children) {

                          kid.alpha *= alphaFactor;

                          this._drawWebGLKids(kid.children, ctx, mtx);
                          maxBoxIndex = this._maxBoxesPerDraw - 1;

                          kid.alpha /= alphaFactor;

This likely won't be fixed, as SpriteContainer is going is deprecated in the next version of EaselJS, and we are focusing our efforts on the new WebGL implementation "StageGL", which you can find in the StageGL-beta branch on GitHub.
If you test and post a PR before we release, we would be happy to accept it.

This likely won't be fixed, as SpriteContainer is going is deprecated in the next version of EaselJS, and we are focusing our efforts on the new WebGL implementation "StageGL", which you can find in the StageGL-beta branch on GitHub.
If you test and post a PR before we release, we would be happy to accept it.

Closing this, since SpriteContainer is officially removed.


Unable to download

Unable to download from home screen. I reach (and I assume everyone else does) a 404 page.

It has been reported in issue #295 & #304. You may try to download through https://github.com/mcasimir/mobile-angular-ui/archive/master.zip

Solved


Improvement/video end time

Requires content teams to add (?/&)end=[number in seconds] for a video to automatically stop at that point

:tada: 🙌


we need Embeddings Lookup this method

Hi :
I wanna to invoke tf.nn.embedding_lookup to make embedding layer ,but the java version has not these part code.please  make it real work in java ? thank you ,

FYI, it looks like the C++ API of PyTorch implements this functionality, which we can easily use from Java:
https://github.com/bytedeco/javacpp-presets/blob/master/pytorch/src/gen/java/org/bytedeco/pytorch/EmbeddingImpl.java

Hi @mullerhai , did you tried to use tf.gather instead? According to TF documentation, embedding_lookup is just a generalization of gather.

If you could port that to Java, I'm sure we will want to merge this, yes.

Thanks @mullerhai ,
Again, the "happy path" of embedding_lookup (getting raw embeddings from a single tensor) can be replaced by a single call to tf.gather. But if you could write/port a wrapper that does also the fancy stuff (partitioning, norm, transform, ...), that would be certainly a great addition to our Java framework.

Thanks @mullerhai ,
Again, the "happy path" of embedding_lookup (getting raw embeddings from a single tensor) can be replaced by a single call to tf.gather. But if you could write/port a wrapper that does also the fancy stuff (partitioning, norm, transform, ...), that would be certainly a great addition to our Java framework.

yeah, if the tf java framework has   embedding look up method  then  we will have embedding layer, it will benefit for all users

Talking of embedding layers… @JimClarke5 , is this something you have worked on as part of the first phase for layers?

Exactly what do you mean by embedding layers? The Sequential model can contain a network of layers if that is what you mean.
I have not worked on layers for the simpler models, the plan is to get the  basic model plumbing accepted, then add more layers.
Also, I have not tackled saving the model in a SavedModelBundle yet.
There is a lot of work yet for models and layers.
Jim

On Feb 14, 2022, at 6:07 PM, Karl Lessard @.***> wrote:

Talking of embedding layers… @JimClarke5 , is this something you have worked on as part of the first phase for layers?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.

Yes I was asking if you’ve already started to port the Keras embedding layer, to make sure we are not duplicating the efforts here.

I haven’t started it. There is some plumbing for Layers you will need, like the Layer Interface and BaseLayer abstract class.
Jim

On Feb 15, 2022, at 2:00 PM, Karl Lessard @.***> wrote:

Yes I was asking if you’ve already started to port the Keras embedding layer, to make sure we are not duplicating the efforts here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.


Unity.Abstractions?

I'm using the Unity version. When I try to use container.AddDbContextFactory<...>(), I get an error like "The type IUnityContainer is defined in an assembly that is not referenced. You must add a reference to assembly 'Unity.Abstractions yadda yadda yadda'"
Any idea what I could be doing wrong?

Ah, I see... It requires version <IP_ADDRESS>? Can that be right? My version is much newer for some reason.

@okonomiyaki3000  Sorry for the very delayed answer but somehow I missed it. Did you manage to figure that out?

@vany0114 nope. I gave up and didn't use DbContextFactory.


Freeze rubocop version for stable CI

ref: https://github.com/bbatsov/rubocop/commit/dd0d60c0a87bdb6233cdeca14a13505b10f2bfae
https://github.com/ruby-grape/grape-entity/pull/277 failed as https://travis-ci.org/ruby-grape/grape-entity/jobs/295161671 from rubocop 0.48~0.51 changes.

Coverage remained the same at 92.72% when pulling a1fcb4474462da30339737719d60b4df8d573b2b on kachick:fix-rubocop into 6a384cd573580ccb7fbf79af5886a037b2358e0b on ruby-grape:master.

thanks @kachick … did you tested it with #277 and it is green?

Coverage remained the same at 92.72% when pulling 8895a69feca402b32dc0fabbc7bc60d93b9e5306 on kachick:fix-rubocop into 6a384cd573580ccb7fbf79af5886a037b2358e0b on ruby-grape:master.

https://github.com/ruby-grape/grape-entity/pull/278#issuecomment-340931764

did you tested it with #277 and it is green?

Yes, I tested in my local. But we added some changes. So I'll ensure in https://github.com/ruby-grape/grape-entity/pull/279 💪

Coverage remained the same at 92.72% when pulling c362d74460e604cd3a78faf44ef74b267bc7a47f on kachick:fix-rubocop into 6a384cd573580ccb7fbf79af5886a037b2358e0b on ruby-grape:master.

I see … cool 👍

please can you close the other PRs, think here is all in 😉

Thank you! Then, Can I close https://github.com/ruby-grape/grape-entity/pull/279 ? ⏹

Coverage remained the same at 92.72% when pulling b66105fb2b7e52df28d369d1f1cd1553fcf6ff48 on kachick:fix-rubocop into 6a384cd573580ccb7fbf79af5886a037b2358e0b on ruby-grape:master.

sorry … was a bit confused … I mean the pr with all in think #279 to be open and mörge and the other bothe close

Coverage increased (+1.8%) to 94.538% when pulling fa4081a27bcd0598ae3430de7473b3c01dcb74d6 on kachick:fix-rubocop into 6a384cd573580ccb7fbf79af5886a037b2358e0b on ruby-grape:master.

Oh sorry to misunderstood 🙇
And Thank you for the review! I'll update rest PRs 💪


[openssl] Fix building in Release only mode

Signed-off-by: Vitalii Koshura<EMAIL_ADDRESS>

This is a fix for https://github.com/microsoft/vcpkg/pull/22878#issuecomment-1090808149
@strega-nil-ms, @BillyONeal, may I have your review?

Merged https://github.com/microsoft/vcpkg/pull/23932 as @strega-nil-ms asked

anxiously waiting for this fix to land
#24003

Thanks!

still doesn't work.  same error as reported in https://github.com/microsoft/vcpkg/issues/24003
how can I roll back to version  1.1.1n#1?  is there a way to pass OPENSSL_VERSION to vcpkg install openssl ?

@winterz, I'll take a look at this issue tonight


[nrf noup] test-spec: update CI-rs-test and Ci-fem-test

Narrow down paths base on compilation dependencies.

The negation patterns are rather invalid.

test-spec updated


Feature: custom notification template

As an admin I can create a notification template for each action (update/delete/request) a service.

Cancelled


Added fontawesome/font-icon example

Uses the font-awesome icons to represent the
airports as little airplanes on the map.
It's both cute AND demonstrates using a font as an icon
alternative to a "circle" type layer.

Coverage remained the same at 98.341% when pulling 700a8cad7056d1e93784774717c8d6b80b47c37e on theduckylittle:examples/font-awesome into c9e34ca5dea40b913e1602fc781efc64601db00e on boundlessgeo:master.

Coverage remained the same at 98.341% when pulling 28767c495a089f2d3326887f062d412986121a63 on theduckylittle:examples/font-awesome into c9e34ca5dea40b913e1602fc781efc64601db00e on boundlessgeo:master.


[Bug] count(): Argument #1 ($value) must be of type Countable|array, bool given

I'm have encountered errors on many pages, that prevent page loading.
Error log: count(): Argument #1 ($value) must be of type Countable|array, bool given
I'm fix simple typo in my commit #6480da2.

Resolved as of PR #367


Engine crash running gallery smoke test

The gallery smoke test appears to be flaky, with an engine crash:
+cd examples/flutter_gallery
+flutter test
00:17 +7 -1: loading /home/travis/build/flutter/flutter/examples/flutter_gallery/test/smoke_test.dart
  Exception: Shell subprocess crashed with segmentation fault after tests finished.
  Test: /home/travis/build/flutter/flutter/examples/flutter_gallery/test/smoke_test.dart
  Shell: /home/travis/build/flutter/flutter/bin/cache/artifacts/engine/linux-x64/sky_shell

  package:stream_channel                                    _GuaranteeSink.addError
  package:flutter_tools/src/test/flutter_platform.dart 107  FlutterPlatform._startTest.<async>.<fn>.<async>
  ===== asynchronous gap ===========================
  package:flutter_tools                                     FlutterPlatform._startTest.<async>.<fn>
  package:flutter_tools/src/test/flutter_platform.dart 198  FlutterPlatform._startTest.<async>
  dart:async                                                _SyncCompleter.complete
  package:flutter_tools/src/test/flutter_platform.dart 73   FlutterPlatform._startTest.<async>.<fn>.<async>
  ===== asynchronous gap ===========================
  dart:async                                                _asyncThenWrapperHelper
  package:flutter_tools/src/test/flutter_platform.dart      FlutterPlatform._startTest
  package:flutter_tools/src/test/flutter_platform.dart 50   FlutterPlatform.loadChannel

Full log: log.txt
This was https://travis-ci.org/flutter/flutter/jobs/189313310 but I've since restarted that job so it likely won't show it any more. The PR was https://github.com/flutter/flutter/pull/7354.

To debug these, we will need the engine version of flutter version (which we likely can get from the pull request history) and then also we need the output of the segfault.  Unclear if sky_shell isn't printing the segfault output or if package:test is hiding it.
@chinmaygarde briefly looked into wiring up breakpad.  We may need something like that even for our linux sky_shell in order to get consistent stacks.  One way to debug would be to add a crash to sky_shell and see what flutter test prints in  that case.

I haven't been seeing output from segfaults in general in recent months (especially on devices).
not sure if flutter test is showing all the output in case of crash though.

I think I just opened a dupe of this; latest master from today, so I think it's still happening :(
https://github.com/flutter/flutter/issues/17989
I seem to have a totally reliable repro on my MacBook; happens every time. I tried wiping Flutter's cache folder and also flutter clean and it's still happening.


Question: best practice when using infinite scrolling while the content is being modified

I was wondering what the best practice was supposed to be when I use infinite scrolling, and the content changes server-side while a user is navigating, which leads to duplicates in the results displayed to the user.
Suppose I store news articles in Algolia and a user asks for the first 10 results (index 0 to 9) ordered by creation date (newest first).
After the user obtains the first 10 results, a different user creates a new article.
Since the article is new, it is inserted at index 0 in the ordered list of articles.
Therefore, the article that was previously at index 9 is now moved to index 10.
When the first user asks for the next page of results, he will obtain 10 results, index 10 to 19.
The user will see a duplicate, as the result he got at index 9 is also visible at index 10.
This is problematic for infinite scrolling, as the duplicates are visually right next to each other.
To stop this from happening, I use lodash
const uniqueHits = _.uniqBy(hits, 'objectID');
in the function I pass to connectInfiniteHits.
Is this best practice? Should this be handled transparently by the connector instead?

Feel free to comment further on this issue if you have more questions and you feel like this should be reopened.


Set map extent in mapinfo reducer

Set the map bounds in WGS84 in the mapinfo reducer

Coverage decreased (-0.3%) to 96.296% when pulling 33890dee50dc14da4a18440fa2e91ca9d75e86d4 on bartvde:mapinfo-extent into a02d54f082b4fecb460c602e5c56bbb35d2d4ad9 on boundlessgeo:master.

Coverage decreased (-0.09%) to 96.556% when pulling 93c4f49cd6c6c82605988665d7a43175b1ac83ad on bartvde:mapinfo-extent into a02d54f082b4fecb460c602e5c56bbb35d2d4ad9 on boundlessgeo:master.

Coverage decreased (-0.09%) to 96.556% when pulling ef17cca922a333c95ce40392bb65e7cdc8df51cc on bartvde:mapinfo-extent into a02d54f082b4fecb460c602e5c56bbb35d2d4ad9 on boundlessgeo:master.

Coverage decreased (-0.09%) to 96.556% when pulling ef17cca922a333c95ce40392bb65e7cdc8df51cc on bartvde:mapinfo-extent into a02d54f082b4fecb460c602e5c56bbb35d2d4ad9 on boundlessgeo:master.

Coverage increased (+0.2%) to 96.881% when pulling fc088f8347881f64722dd03361a04c6c01926bf4 on bartvde:mapinfo-extent into a02d54f082b4fecb460c602e5c56bbb35d2d4ad9 on boundlessgeo:master.

This is now ready for review

Coverage increased (+0.2%) to 96.881% when pulling 35162749ef8f0b6247534312d13ce91007bf75d9 on bartvde:mapinfo-extent into a02d54f082b4fecb460c602e5c56bbb35d2d4ad9 on boundlessgeo:master.


Update log parser how to

it's not clear that you need to log in while chat log is active so the log parser can detect the toon and new badges to add. maybe add a line about that :)
(I had to read the code to understand that you needed that info ^^)

Ah, yeah... simple enough. How does "Make sure that you log into your character after enabling chat logging so the logs contain a record of which character to associate the badge with" sound?


Persist Snippet Creation Across Login Sessions

When a user is not logged in and starts creating a snippet, the snippet is lost after the user clicks the login button.
Expected Behavior:
The created snippet should persist across the login process, allowing the user to continue editing or saving it after logging in.

@seveibar


Eliminate false positive warnings for spelling of "libvirt" and "multithread".

Please also update the test fixture files.


Documentation: intro and configuration

split out the introduction into a dedicated chapter
align some statements about the configuration with the latest status quo
describe how configuration templates work

Addressed all of the comments and added some "why use Infinispan" items to the introduction

I have made the changes you asked @wburns

Integrated, thanks @tristantarrant !


Add possibility to configure a price group as "cross article"

1. Why is this change necessary?
If you assign an article to a price group, the quantity to calculate the discount for the price group is based on how many items of exactly this article are in the basket. Neither does it consider variants of this article nor any other articles in the same price group.
2. What does this change do, exactly?
This PR allows you to define a scale of discount across multiple articles. The discount level is calculated depending on the total number of (different) articles of the same price group. To achieve this, a price group can be configured to be 'cross article'.
It also adds a line to the price block in the frontend detail page that shows how many articles of this price groups are in the basket already.
3. Describe each step to reproduce the issue or behaviour.
N/A
4. Please link to the relevant issues (if any).
N/A
5. Which documentation changes (if any) need to be made because of this PR?
There section about price groups config should be extended by a paragraph explaining what the config 'cross article' means.
6. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21711
Please use this issue to track the state of your pull request.

@windaishi would you mind rebasing this onto 5.6?

Hey @windaishi,
could you rebase it to 5.6? :blue_heart:

I have rebase the PR to 5.6 branch. It's ready to merge ;)

Maybe someone can tell me why the travis tests are failing?

Also, please can you add everywhere types?

Also, please can you add everywhere types?

I was unsure about that. So I assume every new PR from now should have typehints everywhere?

@windaishi only if the PR has the 5.6 branch as target :wink:

Dear reviewers. I have implemented all requested changes. May you have another look?

I tried to fix you remarks. You can have another look.

Thanks for your Contribution! :blue_heart:
Can you please squash your commits?

Done
Am Fr., 15. März 2019 um 09:14 Uhr schrieb shopwareBot <
<EMAIL_ADDRESS>
Thanks for your Contribution! 💙
Can you please squash your commits?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shopware/shopware/pull/1654#issuecomment-473196248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF8aP3fnuamPHOzLwFcbYBhVjtEzUCoRks5vW1Z6gaJpZM4Twtga
.

Done

Hi @windaishi!
Thanks once again for your PR! We imported it and presented the change to our internal QA team. Unfortunately, they found a few usability issues that need to be addressed before we can merge this change:

The display of the price group on the products detail page is very minimalistic, saying something like "You've already got X products of price group Y in your cart", which isn't very helpful. It doesn't tell him that he might get a discount (and how much of one) if he adds some other products and how he might find these other products. Something like "Add X more products of price group Y to your cart to get Z EUR (or %) discount" might be more applicable.
The name of the price group needs an additional Frontend-name that can be translated
We also need some way to show customers other products of that price group, so we can present him a link to a page where he can find all the products that would be available.

Sorry it took us so long to respond, and with such bad news. Is there any chance you might be able to implement these changes?
Cheers!

As discussed, we don't have any free capacity to implement the requested changes at the moment. Maybe someone from the community wants to step up?

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.


Twin Management.

As a developer/operator. It would be nice to have easy way to interact with device twins.

Se both the cloud and device view of the twin.
Update the cloud version.
If there some twin relates sync messages show a real-time log of them for debugging.

No longer relevant.


Investigate Signal performance and impact on solver speed

When benchmarking sparse computations on jax vs qutip, a slowdown was observed when the Signal class was used in the qutip simulation. Replacing the Signal usage with a manually defined numpy pulse function gave a 6x speedup for a small 2-transmon simulation with 3-d qubits. In addition, vectorization also caused a slowdown, with the np.vectorization wrapper causing a 2x slowdown in the same process. This testing was performed with qutip, using the qt.mesolve function.

Obviously, ideally, the signal evaluation cost when in numpy-mode should be as close as possible to just directly writing the function in numpy.
Speed tests
Based on the above I've done some speed tests for Signal evaluation in a notebook attached as Signal_speed_tests.zip. I've defined a simple envelope function written with numpy code, and compared speeds of the following:

Signal constructed with vectorized version of the envelope.
Evaluation of full signal formula using only numpy functions with no envelope vectorization.
Evaluation of the full signal formula using only numpy with the vectorized envelope.
Evaluation of the full signal formula using only numpy with Array wrapping and no envelope vectorization.
Evaluation of the full signal envelope using only numpy with Array wrapping and envelope vectorization.

Speed tests indicate that 2 is about 3x faster than 1, and 5 is about the same speed as 1 (indicating that the discrepancy between 1 and 2 can effectively be explained by the Array wrapping and vectorization). Furthermore, a variant of 2, in which the formula is evaluated as:
env = f(t)
exp_val = np.exp(w * t + phi)
return env.real * exp_val.real - env.imag * exp_val.imag

is about another 2x faster than
return np.real(f(t) * np.exp(w * t + phi))

which is the current way of evaluating the formula.
I'm somewhat amazed at the 6x speed increases in the qutip solving time based on making this swap for the coefficients - even if we achieve 6x faster Signal evaluation I wouldn't expect a 6x improvement in solving time given that's only part of the RHS calculation, but maybe there is more going on.
Recommendations
To try to fix the above I think we need to:

Eliminate the requirement that the envelope be vectorized.

While it's possible that when actually using the vectorized function in a vectorized way it could offer speed improvements over sequential evaluation, solvers don't do this, and solving speed takes precedence over everything else.
The only code that depends on this is in Signal.draw, so this will need to be changed.
The Signal documentation talks about the vectorized assumption and how to use np.vectorize, so this will need to be dropped as well.
Also, the behaviour when a numerical constant is passed as envelope currently sets up the constant function to be vectorized, so this should be modified as well.

Change all (or as much as possible) of the Array wrapping in the constructors of the signal classes to_array.

If the default backend is numpy, this function will return a raw numpy array instead of wrapping it, but if hte default backend is JAX, it will actually wrap it. to_array shouldn't be called in any RHS evaluation as it has to check through a bunch of conditions, but for a constructor it's fine.
All signal classes should be checked for this.

The above changes should be simple in principle, though I think doing away with the Array wrapping could potentially be finicky.
I'm going to change the name of this issue to be more specifically refer to the above as items that need to be done.

I think this situation is not as straightforward as believed in previous comments. Vectorization does slow down signal evaluation, but as a proportion of actual RHS evaluation time, some quick initial tests give that it is <1% of the time for a 2-level system. I.e. in principle it will have virtually no impact on overall solver speed (unless Array wrapping is further messing with solver speed). This indicates that we need to do some higher level speed tests that incorporate signal evaluation + RHS evaluation, and maybe even some full integration speed tests with solvers.

Closing as this is open ended and there is no plan to work on this.


Cannot create a new key in v0.12.0-alpha.2

Description
Create a new key from the key page. The new key is not stored in the table. No error message.
Steps to reproduce
See above.
Additional context
No response
Hedera network
other
Version
v0.12.0-alpha.2
Operating system
No response

Could not reproduce. Closing for now.


move package of document validators which closes #769

I'm worried that this PR is unacceptable because the PR brings backward incompatibility.

Coverage remained the same at 90.931% when pulling 7e2d87a99ecc30fc11197fc4a74ac4c0d85f8d08 on ocadaruma:fix-document-validator-package into b685d8d415571004c7da1724fbbc3fd20e1cd5c5 on redpen-cc:master.

Thanks a lot @ocadaruma, I will review this pr and merge soon.

Thanks a lot the refactoring @ocadaruma  LGTM!


Doesn't seem to work with VS2017

Download and install the Visual Studio Snapshot Debugger:
6.11.2018. 8:31:46 - Found installed product - Visual Studio Enterprise 2017
6.11.2018. 8:31:46 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.

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

ID: 7dd454c3-cefc-fc98-cf23-ede34510acde
Version Independent ID: c3d8dcf7-40b6-c7bc-33a5-265c7b8d186e
Content: Diagnose run-time exceptions using Azure Application Insights
Content Source: articles/application-insights/app-insights-tutorial-runtime-exceptions.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@mcurko I'm seeing the same thing, and am continuing to investigate.

@mcurko It appears that the installation instructions for the Visual Studio Snapshot Debugger were out of date, and the installation text has now been updated:
"For instructions on getting started with Snapshot Debugging, please visit https://aka.ms/pnv0qt. This extension works for Visual Studio 2017 version 15.4 and before. For Visual Studio 2017 version 15.5 and above, please install the "Snapshot Debugger" component from the Visual Studio Installer instead."

We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

I can't do that. This component is not available.

From: kobulloc-MSFT<EMAIL_ADDRESS>Sent: Friday, November 9, 2018 11:44:50 PM
To: MicrosoftDocs/azure-docs
Cc: Marko Čurko; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Doesn't seem to work with VS2017 (#18278)
Closed #18278https://github.com/MicrosoftDocs/azure-docs/issues/18278.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/18278#event-1958016112, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APNII2i6NYk2N-9Rwcxz-pcCrVVbUmEUks5utgVigaJpZM4YP5mr.

@mcurko The installation text on this is easy to miss, but for Visual Studio 2017 version 15.4 and earlier you need to download the installer from the store.  The component is only available in Visual Studio 2017 version 15.5 and above.  I hope that helps!

"NOTE: This extension works for Visual Studio 2017 version 15.4 and before. For Visual Studio 2017 version 15.5 and above, please install the "Snapshot Debugger" component from the Visual Studio Installer instead."

You can't do that if you have Visual Studio 2017 Community edition!
Regards,
Marko Čurko
Marko Čurko
Senior Developer │ Perpetuum Mobile d.o.o.
Damira Tomljanovića Gavrana 13, 10000 Zagreb
m +385 91 2305 123 │ t +385 1 6390 834
marko.curko<EMAIL_ADDRESS>│ www.perpetuum.hrhttp://www.perpetuum.hr/
<EMAIL_ADDRESS>From: kobulloc-MSFT<EMAIL_ADDRESS>Sent: Monday, November 26, 2018 7:38 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Marko Čurko<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Doesn't seem to work with VS2017 (#18278)
@mcurkohttps://github.com/mcurko The installation text on this is easy to miss, but for Visual Studio 2017 version 15.4 and earlier you need to download the installer from the store. The component is only available in Visual Studio 2017 version 15.5 and above. I hope that helps!
"NOTE: This extension works for Visual Studio 2017 version 15.4 and before. For Visual Studio 2017 version 15.5 and above, please install the "Snapshot Debugger" component from the Visual Studio Installer instead."
[image]https://user-images.githubusercontent.com/37556655/48996897-af6a2d80-f102-11e8-89f4-0a647be30d55.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/18278#issuecomment-441533560, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APNIIyqfsYlfUv0uOkf-LsO2SCZgasCTks5uy4w_gaJpZM4YP5mr.

Same as mrcurko, using VS Community 2017, and can't install the extension. Is it a feature not available in the community edition?


Using data-pfsrcset attribute instead of srcset for img tags that have a picture parent

In the documentation there are two caveats that are semi conflicting; Temporary extra HTTP Requests for picture usage in some browsers, and Source element limitations.
To remedy both of these couldn't img elements that have a picture parent use data-pfsrcset (an attribute we are already adding for the method dodgeSrcset) instead of srcset? Obviously this would break native implementation of srcset (which is kind of the point since it's a fallback anyway) but since it has source siblings it should be using them anyway. This way img elements won't incur the extra HTTP request from the browser's preparser and picturefill will still be able to get the srcset to polyfill Android 2.3.
Does anyone see a problem with this?

At a first glance, I want to say we shouldn't do this. PF is meant to be a 1:1 match with the spec, and adding this new attribute would diverge from said spec. The issue of the extra download will eventually subside and more people upgrade their browsers. The goal of this polyfill is to be irrelevant one day, and I think adding this attribute would deter from this goal.
As always though, I'd like to get @wilto, @aFarkas, or @baloneysandwiches' opinions on the matter.

The data attribute is an idea we've entertained before. The problem is that for almost all setups, revisiting markup on the server is much harder than modifying (or removing) a polyfill. Building the polyfill around the limitations of early Android seem ultimately wrongheaded. That said, I see why this could be a useful "transitional" pattern. Seems like something for a fork.

Both those points make sense to me, thanks guys.


Support for Android O

+1

+1

@austintaylor I noticed the PR was merged. Will you be creating a new release for it?

Wow thanks @billge !

@austintaylor I can't seem to find the new release on jcenter?
https://bintray.com/austintaylor/maven/com.uservoice%3Auservoice-android-sdk

@billge Looks like I forgot to hit Publish. It should be there now. Thanks for the PR!


Theme: Badge component

Is your feature request related to a problem? Please describe.
Improve the theme support to the component (and subcomponents).
Describe the solution you'd like

All default styles must be moved to the default theme;

Describe alternatives you've considered
n/a
Additional context
n/a

Give me this one


solc: 0.4.6 -> 0.4.8

Motivation for this change
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

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Sorry to revive this after merge, but I just found out this fails to build for me with sandboxing enabled. It tries to download jsoncpp during build phase. @dbrock, maybe we're testing under different conditions? Can you verify? Thanks!

Thanks for the report, @cpages. Should be fixed by fe0ef5538428b4c30cd7151431ac2903a489b68f.

Sorry, missed this. Thanks, @vbgl!!


Change Protocol to ProtocolType

Codecov Report

Merging #30 (508588d) into master (b0cad6d) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 508588d differs from pull request most recent head 88c1405. Consider uploading reports for the commit 88c1405 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##            master       #30   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           20        20
  Lines          462       462
=========================================
  Hits           462       462

Impacted Files
Coverage Δ

aioarp/_arp.py
100.00% <100.00%> (ø)

aioarp/_async.py
100.00% <100.00%> (ø)

aioarp/_client.py
100.00% <100.00%> (ø)

aioarp/_sync.py
100.00% <100.00%> (ø)

tests/test_client.py
100.00% <100.00%> (ø)

tests/test_proto.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


What if each new item in the list took their itemType value from the last item in the list? Then the user just has to add the first checkbox item, and all the rest would automatically match it.

The changes merged in #21 improve this experience, but I think matching the itemType on new items will still save users a step. They don't have to toggle the switch in the dialog if it automatically takes the value from the previous item.

Ah, that makes sense!


[ClickUp - Tasks Explorer] ...

Extension
https://www.raycast.com/aparandeh/manage-clickup-tasks
Description
Hello. I am trying to use the Clickup extension. Got the API from Clickup and the task explorer is working fine. However, the quick capture command is not working, and I keep getting an error message stating "Something went wrong, please try later. Any thoughts how to solve this? thanks
App Version: 1.59.0
System Version: 13.4.1
Steps To Reproduce

open quick capture
fill in a task
submit

Current Behaviour
error - Something went wrong, please try later.
Expected Behaviour
create a new task at clickup

It might be that the extension API has changed slightly. Let me fix some bugs this weekend.

Hi Ali,
Thanks for the reply. I managed to get all the correct ID's - Team, Space
and list - and now it's working properly.
As a suggestion it would be nice if the assignee also was part of the
extension dialog.
Thanks again
Ricardo
Sent via Superhuman @.***>
On Fri, Oct 20, 2023 at 4:52 AM, Ali Parandeh @.***>
wrote:

It might be that the extension API has changed slightly. Let me fix some
bugs this weekend.
—
Reply to this email directly, view it on GitHub
https://github.com/raycast/extensions/issues/8826#issuecomment-1772255003,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ5W2CHP2B4AV66MJIZEZV3YAIUTRAVCNFSM6AAAAAA6C3AN2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGI2TKMBQGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Question about making a bot.

I have looked at your examples for making a bot and I understand the code but what I don't understand is where is the "scene" key word coming from. You have it in your code but nothing is imported that has a scene variable or class.
def do_play(scene):
    print(scene)
    if len(scene['PlayOptions']) == 0:
        return []
return create_action(random.choice(scene['PlayOptions']))

How am I allowed to use any programming language and get what is happening and do something with it if I have no idea where scene is?

Hi, the scene create here:
def do_POST(self):
                content_length = int(self.headers['Content-Length'])
                raw_data = self.rfile.read(content_length)
                json_data = json.loads(raw_data)

                if self.path == "/trace":
                    ret = _trace.trace(json_data)
                elif self.path == "/mulligan":
                    ret = _bot.get_mulligan_action(json_data)
                elif self.path == "/play":
                    ret = _bot.get_play_action(json_data)

it is just json that came from post

in hearthstone the rock module send post request to your server-bot
your server got the post request and extract "post body"-json
your server-bot make decision and return answer as json
hearthstone-rock module make the decision

you can look to scene in this file for knowledge what it really have
https://github.com/yangyuan/hearthrock/blob/master/src/Hearthrock.Contracts/RockScene.cs

Thanks for the reply back, I will look into this more.


Server: DetermineVersion changes

This change adds commit preselection functionality to avoid comparing against all commits for the dependency and also enable lookups without a package.
For the protobuf version 21.0 hashes the change reduces the lookup time from ~ 1:14 minutes to 54 seconds.

Thanks! Could you please share grpc_cmd.sh ?


Can+t pop route using v4.9.8+2 version

Version Information

Flutter version: v3.24.3
flutter_smart_dialog version: v4.9.8+2

Describe the bug/requirement
After upgrading your package from v4.9.8+1 to v4.9.8+2 we can't pop the screen after displaying dialog. If I revert back to v4.9.8+1, everything works as expected.
Problem demo
I'm still working on minimal reproducible example similar to my app, as our app is pretty complex. Do you have any idea, what change from +1 to +2 could contribute to that? Will give you an minimal example in max 2 days, but i'm always using those parameters when displaying an dialog.
SmartDialog.show(
alignment: Alignment.center,
maskColor: Colors.black26,
clickMaskDismiss: false,
usePenetrate: false,
useSystem: true,
animationType: SmartAnimationType.scale,
useAnimation: true,
);

The main change in the +2 version is to roll back the initialization reconstruction. The previous dynamic initialization reconstruction would cause many strange problems.
I need you to provide a demo of the smallest unit that can reproduce the problem so that I can locate the specific cause.


Fix DATE-OBS issues in simulated data

This fixes #46.
The _add_infos_header() function now tries to pass keys to infos even for simulated data, but only if the keys exist. This is close to the current behaviour, but reduces the information lost between the fits and oifits files for simulated data.
The oifits.open() function now uses DATE-OBS only if it's not an empty string. If it is, it will just use TIME from the data record (if you would prefer to use a placeholder for DATE-OBS when it's missing let me know. I created a function get_timeobs() because the code I had to modify was copied in 3 places originally.
I added tests for both changes. The first test might conflict with #45, but it should be easy to fix this when one of the two PRs gets merged.
I cannot ask for reviews via Github, so I will tag you both here: @DrSoulain,  @neutrinoceros .

so it looks like this is based on top of #45 and I guess we should merge #45 first, right ?

Sorry, I had some problems with git... Hopefully now the branch is OK. It was not actually based on #45, but both added separate tests for the _add_infos_header fucntion.


Consider swapping to the nghttp2 priority algorithm

https://docs.google.com/presentation/d/1x3kWQncccrIL8OQmU1ERTJeq7F3rPwomqJ_wzcChvy8/edit

FYI @normanmaurer @Scottmitch @louiscryan

@nmittler - Yes I need to think about slide 10 a bit more...haven't had cycles but seems different than what we do.

That scheduler looks good, and is the approximate form of what I would expect most priority-aware schedulers for HTTP/2 to look like. We may want to tweak some details though.
That scheduler design is well-known to networking: it is "weighted fair queuing" (WFQ). However, normal WFQ is based on packets (with already-determined size), so it does have some modifications. With HTTP/2, CPU schedulers tend to be a better fit than networking schedulers, because for efficiency they have to introduce the idea of a quantum (like minAllocationChunk in #4464) and because they tend to react rather than predict.
Linux's O(1) scheduler has the same approach as the scheduler in #4464 (round-robin). And Linux's Completely Fair Scheduler (CFS; sections 1-3 apply to this discussion) has the same approach as seen in nghttp2. Note that I believe CFS uses a red-black tree instead of a heap just because it is slightly better suited to the kernel; they could have used a heap if they wanted.
Fair queuing in general is based on simulating "ideal" hardware that is natively able to process in parallel. E.g., if you had 3 streams, it would send bits for each stream simultaneously but at 1/3 the rate. You "simply" "monitor" how that ideal hardware would have progressed and have your real system approximate that.
The primary change I would suggest is to make the pseudo time concrete, namely: "bytes written." Linux's CFS uses "nanoseconds" as its pseudo time, which makes it much easier to understand.
That also means that the priority accounting would be different. If we keep the sum of weights of active streams per queue and then:
t[i] = t_last[p] + nsent[i] * sum_of_weights / weight[i]

So if we have three active streams, each with default priority 16, then if one is scheduled to send 10 bytes you would increment t[i] by 30 bytes (which agrees with the "ideal" model, since it should go 1/3 the rate).
It looks like nsent is just a quantum (100 bytes) in the presentation. Instead, I'd suggest we peek() at the next item in the queue, use its time + a quantum (say, 1K).

I will throw together a PR for this.

@Scottmitch w000t!

@Scottmitch, you may want to chat with @ejona86 about this ... he had some ideas for the implementation that may just involve a slight tweak of the algorithm used for the uniform distributor.

@nmittler - Sgtm. I was planning on coordinating when I got back tommorow. The tips above are helpful too.


How can I add ticks color in Y axis in chart js version 2.9.4?

In chart js 3.x, there has option for ticks
grid: {
       tickColor: 'red'
},

There has any way to get this option in version  2.9.4 ?
I am trying to get Y axis like below image in version 2.9.4, but there has no any option for tickColor

I looked into the v2.9 code and this isn't possible. You would need to fork the code and change the drawing code


empty strings or types are indistinguishable from each other

Linear view has a nice Type: __ header at the top to differentiate from other views, and an empty hex view has the address offset, but Types and Strings just show empty windows (if someone hits a hotkey to select one and doesn't realize what they did)
A very small header at the top with "Strings" or "Types" would help disambiguate since the view menu on the bottom right is a bit subtle.

A simple "No Types Defined" or "No Strings Defined" would be a good option

With the advent of the sidebar, and the updated type browser (doesn't just look like an empty box when there are no types) this is no longer an issue.


UseConsistentWhitespace.CheckOperator: Add unary operators that start with a dash (-split, -join, -not, -bnot, isplit, csplit)

PR Summary
Related: #1239
In order to enable formatting corrections of this kind: $a-join$b --> $a -join $b or reducing too much whitespace but also -split$a --> -split $a with the added code as existing code for operators assumes that something precedes it.
The reason for adding the check that the unary operator starts with a dash is is to exclude things like $a++ or !$a where we do not want a whitespace character separation by default
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[x] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

I tried this code out and noticed a couple things.
Checking that the operator starts with a dash introduces the following undesirable behavior: --$counter is changed to -- $counter. Also $counter-- is changed to $counter --
Unary operator -not does not get spacing if it follows a parenthesis such as if (-not$SomeVariable).

Converting to draft to resolve the various PRs


add write docstring action

Adding docstrings for Python code
Supporting Sphinx/Google/Numpy styles
Preserving the actual text of the original code associated with each node using libcst

LGTM

Add usage example like:

export PYTHONPATH=$PYTHONPATH:$(pwd)
python metagpt/actions/write_docstring.py workspace/cli_2048_game/cli_2048_game/game.py --overwrite

Sometimes parse code error.

LGTM


Fix for crash on Android N and below which occurred due to earlier fix for Android O

Removed the extra class as requested.


Prefill crew from most recent boarding

[-] Added localization for prefilled alert
[-] Added prefilled alert
[-] Implemented functionality for prefilled crew.
Fixes #196

also please test that id is not equal

Done it in unit tests

not sure, but looks like requires extra tab for this block

@kojiba What do you mean? What is the place for tab?

I mean +4 extra white-spaces from offset from left

I use autoformat. In this case it's ok

@akaktus  Note that this is still waiting for the review comments to be addressed

If I attempt to copy across either the vessel or the crew data then the app crashes with:
Terminating app due to uncaught exception 'RLMException', reason: 'Cannot set a link to an existing managed embedded object'
You can't embed the same Realm Object in more than one Realm Object.
I think that this is because the copy function is calling the init that copies over the model (e.g., crewMember) which is a Realm Object - instead, I think it should only copy over just the non-Realm attributes and leave the model attribute as nil.

I create method clone(), so I don't embed Realm object. This method create new instance without using init with Realm object. Problem solved.


EPOLLET in non-blocking sc_sock

Do I understand correctly that EPOLLET is not used because Windows WSAPoll does not support it?

Yes, one reason is that.
More importantly, I don't see any benefit of using it(for my use-cases). I guess that flag is just for very specific applications. Why do you want to use it? Do you have a different use-case?

According to the docs https://man7.org/linux/man-pages/man7/epoll.7.html
When used as an edge-triggered interface, for performance
reasons, it is possible to add the file descriptor inside the
epoll interface (EPOLL_CTL_ADD) once by specifying
(EPOLLIN|EPOLLOUT).  This allows you to avoid continuously
switching between EPOLLIN and EPOLLOUT
calling epoll_ctl() with EPOLL_CTL_MOD.

I assume it can be beneficial to have less kernel calls (less context switches / less lock contention).
I can see that at least Nginx uses this flag: https://github.com/nginx/nginx/blob/master/src/event/modules/ngx_epoll_module.c#L705

I remember I experimented with with EPOLLET years ago and decided it wasn't making performance any better(for my use-case). Also, it makes your app a bit complex.
Personally, I've never seen epoll_ctl() in flamegraphs. Maybe this is because of the types of app I worked on. Maybe it isn't the case with HTTP servers. I don't know.

It is not necessary that you will see epoll_ctl in flamegraphs, it makes more sense to look at the actual latency/throughput numbers.
What your use case is? I guess if it is about sending small messages across fast local network to a small number of receivers, then probably EPOLLET will not make any difference because pretty much always you must be able to send the full message right away without subscribing to EPOLLOUT at all. In case of http server it is often needed to stream large chunks of content over the slow internet to thousands of receivers and here potentially EPOLLET may make some difference (I assume otherwise this flag would be completely useless).

Yes, totally I agree. If you fill output buffer of the socket continously, it might be noticable. Just it’s never been the case for me. If you are sending small messages / you have big output buffers, if you have app level backpressure, if your app is already spending quite time somewhere else, then it won’t be noticable. Probably, these were my scenarios.

Ok, thanks for the inputs!
I'm going to play around this stuff, so far it seems like it is possible to add edge-triggered mode in a backward compatible way by adding a new flag to sc_sock_ev. For Linux and FreeBSD/MacOSX the implementation must be straightforward (use EPOLLET and EV_CLEAR flags respectively) and for Windows we could just emulate the needed behaviour (not for performance but for compatibility with the other platforms).
Are you willing to review/accept such a contribution if I do it?

Sure, it’d be great!

I started looking closely into implementation and have some questions: first of all why do we expand the events array (sc_sock_poll->events) to accommodate all the sockets? In my understanding at least epoll and kqueue assume that this array is just a small intermediate buffer for receiving the the events as a batch. Some articles even suggest to have this batch to be as small as one element in length: https://habr.com/en/post/600123/ . I don't think 1 element array would be sufficient for high load use case, but growing this array to thousands of sockets does not sound right as well. Why don't just use fixed size array (hard coded or configurable)?

We have to do it for WSAPoll if I remember correctly. For epoll or kqueue, it is not necessary but I wanted have all possible events in one go. If your array is small, you'll have to call epoll_wait() multiple times. We can use a fixed length array but I think its size should be >=1024. I usually use event loop iteration for batching. For example, assume you receive some data from network and you're supposed to write it to the disk. I read all network events (events that are reported in a single epoll_wait() call) first and then trigger a single disk write. So, if you read a few events in one iteration, obviously this is not going to work well. Making it configurable is not necessary I guess. Extra options are always confusing :) So, yeah I think we can use a hard coded smaller array if you want.

Please review #97


Assertions failed while running the Test

I am getting below error while running integration Test -
The following assertion was thrown running a test:
'package:flutter/src/rendering/object.dart': Failed assertion:
line 2215 pos 12: '!_debugDisposed': is not true.
Either the assertion indicates an error in the framework itself,
or we should provide substantially more information in this error
message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on
GitHub:
https://github.com/flutter/flutter/issues/new?template=2_bug.md
When the exception was thrown, this was the stack:
#2      RenderObject.markNeedsPaint (package:flutter/src/rendering/object.dart:2281:14)
#3      RenderAndroidView._sizePlatformView (package:flutter/src/rendering/platform_view.dart:199:5)

(elided 2 frames from class _AssertionError)

@akagupta9
Can you provide flutter doctor -v and a complete minimal reproducible code sample, ie, your main.dart and app_test.dart that shows this behavior.
Thanks.

My flutter doctor -v

complete minimal reproducible code sample, ie, your main.dart and app_test.dart that shows this behavior.

@akagupta9


[Quick Accent] Add possibility to blacklist app from trigger toys

Description of the new feature / enhancement
Please, can you add a possibility to blacklist app from trigger Quick Accent like what you did in Always on Top / FancyZones ?
Scenario when this would be used?
Playing a game regularly activates the popup which takes me out of the game for example.
Supporting information
No response

@damienleroy do you think it's possible to exclude active apps?
Also, let's call it an exclusion list 😉
In the mean time, you might want to increase the press duration or see of you could do with only spacebar or left/right keys.

It seems an MR is ongoing for this:
https://github.com/microsoft/PowerToys/pull/22004

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #21531


t-rex run 3D

Please do a different app for it with user accounts and a leaderboard

I'm already thinking about removing it because it can have a big impact on the size of the app.


Implement Github Actions CI

Add .workflow/test.yml for automatic running of unit tests on push.

You've got a lot of old commits here, so it would've made sense to branch off a clean pull of main to avoid that in the future @MichaelDeng03

Looks like our main branch history got messed up actually


"Choosing the Right Helm Resource" update for Chart v4

Description
HOLD until Chart v4 is released with pulumi-kubernetes v4.12.
This PR updates the "Choosing the Right Helm Resource For Your Use Case" guide to use the latest and greatest Chart v4 resource.
Closes https://github.com/pulumi/pulumi-kubernetes/issues/2993

Update: pulumi-kubernetes v4.12 has been released (link) including Chart v4 resource, which the revised article refers to.  But we need to hold on this a bit longer, until the api docs (here) are refreshed.


Broken link in app https://community.awallet.io/c/alphawallet-app/ios-feedback

Where should it point to now?
Maybe:
https://community.alphawallet.com/c/feedback  ?

Bump. @bootingman

https://community.alphawallet.com/c/feedback/ios-feedback
@hboon should be this one

@hboon
https://community.alphawallet.com/c/feedback/ios-feedback


Create cpp example - how to work with opencv in custom pph using DslSurfaceTransform.h

New example called 4file_custom_pph_using_opencv.cpp

Merged into the v0.29.alpha release


The serialization of a DataFrame with floats automatically casts floats into integers

def _dump_fn
import pandas as pd

df = pd.Dataframe({
                        'col_1': [1.0, 2.0, 3.0],
                        'col_2': [21.0, 31.0, 32.0],
                        'col_3': [101.0, 102.0, 103.0]
         })

df.to_csv("test.csv", float_format=f"%.17g")

df
#   col_1  col_2  col_3
# 0    1.0   21.0  101.0
# 1    2.0   31.0  102.0
# 2    3.0   32.0  103.0

df.dtypes
# col_1    float64
# col_2    float64
# col_3    float64
# dtype: object

The serialized csv:
,col_1,col_2,col_3
0,1,21,101
1,2,31,102
2,3,32,103

https://docs.python.org/3/library/string.html#format-specification-mini-language
According to the python docs the presentation type 'g' to format strings as a flaw.

... In both cases insignificant trailing zeros are removed from the significand, and the decimal point is also removed if there are no remaining digits following it, unless the '#' option is used. ...

Any particular reason why the scientific  notation is not used? 'e'

Scientific notation. For a given precision p, formats the number in scientific notation with the letter ‘e’ separating the coefficient from the exponent. The coefficient has one digit before and p digits after the decimal point, for a total of p + 1 significant digits. With no precision given, uses a precision of 6 digits after the decimal point for float, and shows all coefficient digits for Decimal. If no digits follow the decimal point, the decimal point is also removed unless the # option is used.

Any particular reason why the scientific notation is not used? 'e'

I don't remember :( Possibly it was truncating values? Really don't know.
@tadeu @arthursoprana maybe you remember?
Anyway, AFAIU, the problem is that those values are then read back as "integers", so the atol and rtol will not work anymore, is that it?
It may be ok to change it as you suggested.
IF we run into any troubles, another suggestion (and I'm unsure if it helps) would be to, instead of relying on the data type from the CSV file (which would be mistakenly read as int in this case), we use the dtype  passed as parameter to the check() function.
To be more clear, in this code, instead or using
 if np.issubdtype(obtained_column.values.dtype, np.inexact):, we could try using  if np.issubdtype(expected_column.values.dtype, np.inexact):, because (I hope) the expected_column carries the desired data type.
Let me know if that makes sense (I didn't try)

@tarcisiofischer the fix, changing to what @arthursoprana posted, fixes my issues.
My current workaround is to convert Integers to Floats. The suggested fix serializes and deserializes correctly.
This means that also rtol and atol work for me.
However i still think that the API should be extended to provide tolerances for Integers (exact type).

@tarcisiofischer the fix, changing to what @arthursoprana posted, fixes my issues.

Awesome! :D Could you please open an MR with this plus a test? (Test could do exactly what you are doing, check the dtypes. Should fail with previous implementation).

However i still think that the API should be extended to provide tolerances for Integers (exact type).

Agree. Are you planning tackling on this also?
Do you agree with me that this shouldn't be done using np.isclose as implementation?
Thanks for your efforts so far :D

@tarcisiofischer I am unsure, but I will go with what the library maintainers prefer ;-)
I was digging into similar discussions and came across a proposal for Python PEP 485 – A Function for testing approximate equality which includes the section to support non float types as well with isclose().
Also the numpy.isclose() documentation mentions in the last paragraph that:

isclose is not defined for non-numeric data types. bool is considered a numeric data-type for this purpose.

which suggests that isclose() is also intended for integers.
Regarding the edge cases you have mentioned, shouldnt the developer handle overflow errors?
https://numpy.org/doc/stable/user/basics.types.html#overflow-errors
I will try to provide a testcase before Wednesday (when I go on vacation).
Cant promise though ;-)
If the sentiment for Integer Tolerances is towards the extension of the API, I will see what I can come up with (in about 4 weeks of time)

I cannot recall any particular reason why %.{prec}g is being used instead of %.{prec}e. Perhaps we could do that?

I think that %g was preferred because it's more readable/"human-friendly".

I haven't tested, but it seems that this would not break current tests except that if anyone tries to regenerate all expected values, then there will be a diff related to the change from g to e, right?

Yes, it looks like this is what would happen, but in order to avoid the noise for regenerated values my opinion is that it would be better to just solve this issue with something similar to #96 (but with tests). With that we would also add support for true integer datasets.

Well, if that's the feeling I think you may just create some tests for the other issues and drop the idea of keeping the data types.
I still think this is not a good approach, but I won't oppose since there are more people voting for #96 solution.
I'm sorry for all the noise
Just to be clear: I prefer the changes for %g, as they solve a bug, and I think handling integers with np.isclose is wrong, because the values will be interpreted as floats, you'll have floating point comparison and may end up in unexpected situations.
Sorry you had to go through all this @HikingDev - I sincerely was just trying to move torwards what I thought was a correct direction,

However i still think that the API should be extended to provide tolerances for Integers (exact type).

I agree on this. Let's just take care so that it's consistent with the way "closeness" is checked for float's. The simplest way seems to be to just roll out our own isclose for integers using the same asymmetric definition that numpy uses:
def isclose(a, b, atol, rtol):
    return abs(a - b) <= atol + rtol * abs(b)

I'm unsure.
(a) Someone saves
pd.DataFrame({'col_1': [1.0, 2.0, 3.0], })
those are meant to be floats.
(b) Someone loads it again. Since this PR is not merged, they are now integers.
(c) Since they are integers, they'll be handled as integer comparison.
(c.1) IF you decide to use np.isclose, then integers will be converted back to float. I find this path weird, but perhaps it is guarantee that no bugs will arise from that. But then again, having atol and rtol being floats is weird for integer comparison
or
(c.2) IF you decide to handle integers in a different way, then your floats are now saved as integers and integer comparison apply, which (for me) would be unexpected.
I'm really unsure if I'm missing something here. I tried to put the path "on paper" to check it myself, but isn't it what it would happen?

I think that if is isclose is consistent for float's and int's, then we shouldn't have the (c.2) problem. It doesn't matter that the "integer floats" got converted to int, they would be compared exactly as if they were float.
I don't find having atol and rtol being floats that weird, it seems to be very practical, you can check that 10**30+1 and 10**30 are within a 1e-30 relative tolerance or 1.0 absolute tolerance without problems.

As I said, I won't oppose.
Just for the record, this may be an example of a corner case (I may be wrong, I did it quick just to check):
If dtype is float:
>>> np.isclose([100000000000000000000.], [100000000000000000001.], atol=1)
array([ True])

But, since it is loaded as int:
np.isclose([100000000000000000000], [100000000000000000001], atol=1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<__array_function__ internals>", line 180, in isclose
  File "[..]numeric.py", line 2372, in isclose
    xfin = isfinite(x)
TypeError: ufunc 'isfinite' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''

From practical perspective, this may be minor.
I won't bother you further :)

@tarcisiofischer, check it with the function I suggested on https://github.com/ESSS/pytest-regressions/issues/97#issuecomment-1165589084
(the function would need to be changed adding an all() to account for arrays/sequences)
One of my points is that the comparison between<PHONE_NUMBER>00000000000. and<PHONE_NUMBER>00000000001. is already not supported, so it's a new feature and it could be something done separately from the fix for the current problem (if that's a burden on the implementation, but I also don't oppose of doing these things together).

Just realized that this is probably the cause of a problem I have with one of my tests being flaky. Any news on when a fix might be finished? Looks like the conversation died a while back. Or did this get resolved elsewhere somehow?
Thanks!

In the past month I have twice encountered flaky tests (related with rounding differences between windows and numpy) in two different projects where the expected value is a float, but the observed turned out to be an integer, e.g.:
E   obtained_x          expected_x               diff
E       19        19.00000000000001066    0.00000000000001066
E       19        19.00000000000001066    0.00000000000001066

This test failure occurred even though the tolerance was set to default_tolerance={"atol": 1e-3}.
The failure happens because of the combination of two root causes: (1) the conversion of floats into integers due to the use of %.{prec}g instead of %.{prec}e (see above), and (2) checking only the dtype of the obtained_column in https://github.com/ESSS/pytest-regressions/blob/master/src/pytest_regressions/dataframe_regression.py#L131:
if np.issubdtype(obtained_column.values.dtype, np.inexact):

Fixing the second root cause is straightforward and I think much less problematic with regard to backward compatibility/consistency than fixing the first root cause, while being sufficient to fix those flaky tests:
if np.issubdtype(obtained_column.values.dtype, np.inexact) or np.issubdtype(expected_column.values.dtype, np.inexact):

Of course, this fix still won't be sufficient if atol >= 1 AND both obtained and expected are integers, but I think it's sufficient for all other cases.


Increase test coverage

Currently we're running into issues because we are not really testing much and end up making breaking changes without noticing. I think we should be working on improving this. I propose unit tests to be build for the following:

[ ] Both types of authentication.
[ ] Changing the settings.
[ ] All functions which have routes.
[ ] Tests for all endpoints to check if authentication is asked like expected.

I think this would be most of what would be needed.

PR #76 adds tests for my functions which have routes.

This is an ongoing process and a good practice for all new code. Most of the new PRs should have them.
Is still relevant as an issue?

I think out of the tasks set here, only one was worked on. This would be adding tests for functions which have routes. The other tasks are mainly security things.

We should add two more files then: one requesting all our paths without authenticating and another requesting all our paths authenticated.
I'll get into that


Compilation error on Ubuntu on WSL

When attempting to compile on Ubuntu running on Windows Subsystem for Linux, the build fails with some kind of template error.
$ make NOTEST=1 NOPCSC=1 NOCURL=1 NODTAPI=1 NOTELETEXT=1
  [CXX] tsAACDescriptor.cpp
In file included from /usr/include/c++/7/bits/move.h:54:0,
                 from /usr/include/c++/7/bits/stl_pair.h:59,
                 from /usr/include/c++/7/bits/stl_algobase.h:64,
                 from /usr/include/c++/7/bits/char_traits.h:39,
                 from /usr/include/c++/7/string:40,
                 from tsPlatform.h:655,
                 from tsByteBlock.h:36,
                 from tsAbstractSignalization.h:36,
                 from tsAbstractDescriptor.h:36,
                 from tsAACDescriptor.h:36,
                 from tsAACDescriptor.cpp:34:
/usr/include/c++/7/type_traits: In instantiation of 'struct std::underlying_type<unsigned char>':
tsxmlElement.h:426:107:   required by substitution of 'template<class ENUM, typename std::enable_if<std::is_enum<_Tp>::value>::type* <anonymous>, class INT> bool ts::xml::Element::getIntAttribute(ENUM&, const ts::UString&, bool, ENUM, INT, INT) const [with ENUM = unsigned char; typename std::enable_if<std::is_enum<_Tp>::value>::type* <anonymous> = <missing>; INT = <missing>]'
tsAACDescriptor.cpp:186:88:   required from here
/usr/include/c++/7/type_traits:2242:38: error: 'unsigned char' is not an enumeration type
       typedef __underlying_type(_Tp) type;
                                      ^~~~
../../Makefile.common:898: recipe for target 'release-x86_64/tsAACDescriptor.o' failed
make[2]: *** [release-x86_64/tsAACDescriptor.o] Error 1

$ g++ --version
g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

$ uname -a
Linux 4.4.0-17763-Microsoft #253-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux

Hi,
I do not have any WSL environment. I do not see this error on a true Ubuntu system. Which TSDuck commit are you using?
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic
$ gcc --version
gcc (Ubuntu 8.2.0-7ubuntu1) 8.2.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ grep COMMIT src/libtsduck/tsVersion.h
#define TS_COMMIT 1120
$
$ make NOTEST=1 NOPCSC=1 NOCURL=1 NODTAPI=1 NOTELETEXT=1
  [CXX] tsAACDescriptor.cpp
  [CXX] tsAC3Attributes.cpp
  [CXX] tsAC3Descriptor.cpp
  [CXX] tsAC4Descriptor.cpp
  [CXX] tsAES.cpp

I was attempting to build master

The specific declaration which triggers the error was added recently. This may explain a new behavior.
However, it compiles correctly with GCC 4.8.5 (CentOS 7.6), GCC 8.2.0 (Ubuntu 18.10). Note that it also compiles correctly on LLVM/clang 10.0.0 (macOS Mojave) and Visual Studio 2017 (Windows 10).
Your compilation fails on GCC 7.3.0 on an "hybrid" Windows/Linux environment. But it works on both older and newer versions of GCC, on "true" Linux platforms.
Additionally, when looking at the error message you report, it seems a compiler bug. This specific error should never happen because it would be a violation of the SFINAE principle (C++ templates).
My conclusion is that your specific version of the compiler is buggy. I can only advise to get another one.

Build succeeds when using gcc 8.2.0, so your conclusion seems correct.
Thanks for your help.

Hi,
I confirm that the version 3.16 of the TSDuck compiles in Debian WSL with gcc 6.3.0.
Commented here: https://github.com/tsduck/tsduck/issues/231#issuecomment-466795665
So after the git cloneyou can execute git checkout 00d13f9c4fb7db52e9cf3599afcc03a8facb078b and compile inside WSL.
I really need this because I prefer to compile/develop inside WSL, as the VC is a pain!
So, if the code of 3.17 can support some Debian distribution (without GCC 8) and circunvent the GCC 6 & 7 bug, then that will be welcome.
Regards.


"Accelerating" undo

Rather than undoing character by character users would like to switch from character to word-based undo if they are repeatedly hitting the undo key combo.

It's worth noting that we don't technically undo character by character. Rather we undo the last "transaction" (managed by Scribe's transaction manager), which could be more e.g. if you select and then erase a paragraph then that would be one transaction.
Example:

I wonder how other text editors solve this. It's clearly useful but it might make Scribe more complex.

@OliverJAsh tried to understand how OS/browsers do it but there was no obvious pattern. One way would be to debounce the history recording. There may or may not be subtle implications, given that some of the hack applied to normalise content editable across browsers sometimes have to fiddle with the history stack IIRC.
But featurewise, it would be nice to be closer to native undo, whatever the hell that actually is.

Suggest someone looks at the behaviour of InCopy as that seems the logical thing to copy.

Beware the obscure consequences of legacy on modernity :-)

Those who fail to learn from history are doomed to repeat it
On 11 February 2015 at 22:46, Sébastien Cevey<EMAIL_ADDRESS>wrote:

[image: horse-cart-car]
https://cloud.githubusercontent.com/assets/36964/6158151/be970d92-b23f-11e4-8ff3-1e77ad0ec8f5.jpg
Beware the obscure consequences of legacy on modernity :-)
—
Reply to this email directly or view it on GitHub
https://github.com/guardian/scribe/issues/335#issuecomment-73981753.

--
PGP Public Key http://bit.ly/Rxbzi0
--

Visit theguardian.com. On your mobile and tablet, download the Guardian
iPhone and Android apps theguardian.com/guardianapp and our tablet editions
theguardian.com/editions.  Save up to 57% by subscribing to the Guardian
and Observer - choose the papers you want and get full digital access.
Visit subscribe.theguardian.com
This e-mail and all attachments are confidential and may also be
privileged. If you are not the named recipient, please notify the sender
and delete the e-mail and all attachments immediately. Do not disclose the
contents to another person. You may not use the information for any
purpose, or store, or copy, it in any way.  Guardian News & Media Limited
is not liable for any computer viruses or other material transmitted with
or as part of this e-mail. You should employ virus checking software.
Guardian News & Media Limited is a member of Guardian Media Group plc. Registered
Office: PO Box 68164, Kings Place, 90 York Way, London, N1P 2AP.  Registered
in England Number 908396

So the initial situation discussed with Jon Hayes is that after two letter by letter undoes it would switch to word by word undo (so go through the transaction history until we see a non-letter character). This would be a bit challenging but has quite a tight focus.

This was bumped again today. I think prototyping something might be a good idea @na7hangood, I feel we're going to hear this over and over again

Can we also look at #334 when we do this?

Possible ways to define a new transaction:

On every change.
After a given interval of the last input if no new input has been made since.
On space key (repeated ones can be ignored).
On return key (repeated ones can be ignored).
On backspace and/or delete (repeated ones can be ignored).
On paste event.
On execution of any command (e.g. Bold, Italic, ...etc).
If the cursor/selection location was changed, and a new input has been made.
Combination of all or some of the above.

Previously, 1 was the default behavior. With the new undo manager, 2 is now the default. 3, 4, and 5 are possible with extra checking, but can be annoying to some users. 6 is the easiest, and can be implemented with a small change. 7, is also easy to implement, but there is a need to do minor changes on all the commands (passing a flag to force a new transaction with each command). 8 is not so trivial, especially taking into account the inconsistency with the Selection API across the browsers, but it can be made. Also with low interval, 8 becomes useless, since changing cursor location will pass that interval.


Add a biometric/password authentication

The basis is done.
We can now access to account page, Security tab and then add an authentication to our account. The generated key is store into indexedDB and you can delete it. The app will promt the biometric auth if it is configured
The problem will be that I am not good on security, so should I have to verify something more ? How to store the value of user being authenticated to not reprompt the biometric auth ?


Disable cookies for playback

This is a potential fix for 403 errors, untested.

FWIW if you're still using the master branch of Lavalink, try the dev branch -- Dev branch uses Lavaplayer 1.3.17, whereas master uses 1.3.10. A fix was included in Lavaplayer 1.3.11 which changes handling of YouTube URL signature parameters which reduces the number of 403s.
See this commit

@Devoxin I am not sure what you are talking about. @Repulser is already using the dev branch.


supercollective /create is not working

See:
https://opencollective.com/brusselstogether/create
https://opencollective.com/operationcode/create
https://opencollective.com/opensource/create
(same with uk and europe)

disregard, was looking at the /create when the correct link is /apply


Update docs for python library

This PR carries updates to python documentation. Now, people who want to install the package directly in their project can do it with pip -- skipping pip registry.

@sudosubin could you check on this one as you contributed on the python implementations? 🙏

The README is correct, the problem is that we haven't released to PyPi yet. It's now been fixed (it's on pypi).

All content appears to be correct and great.
However, since the package was distributed on PyPI, so it would be better if a section for installing from PyPI was added :D

@sudosubin I have added the requested changes and expanded the example section.


Feature: Allow drag and drop of files between tags

What feature or improvement do you think would benefit Files?
I would really enjoy and value being able to move around each file from one tag group to another with the mouse pointer, like a Kanban board, to update progress on work on each file.
Requirements

This proposal will allow dragging files/folders between containers in the tag widget
Moving an item between tags will remove the previous tag from the file

Files Version
<IP_ADDRESS>
Windows Version
Win11 22H2 10.0.22621.1265
Comments

This would work if files could only have a single tag, but considering we support multiple tags, what would be a good way to differentiate between users dragging to add a tag vs users dragging to switch the tag?

What about the sidebar? If a file has an existing tag and a user drags to a different tag in the sidebar, would you expect the existing tag to be removed?

@carlosvsilva fyi


Makefile and other updates

Closes https://github.com/defenseunicorns/uds-capability-nexus/issues/6
Closes https://github.com/defenseunicorns/uds-capability-nexus/issues/7
Closes https://github.com/defenseunicorns/uds-capability-nexus/issues/12

/test all

/test all

/test all

/test all

/test all


Compile failed on windows

Godot version:
4dbae5a738e33ffe4ab69e84c006bff2adc24cf8
OS/device including version:
windows7 sp1 x64
MSVC 14.1
Issue description:
KeyError:PROJECTSUFFIX

It's NOT like #17551
It seems to be a Sconstruct error.
What's happen?
How can I fixed it?
Steps to reproduce:
scons platform=windows vsproj=yes
I had tried no vsproj.It works fine.But do not work with vsproj=yes.

Works fine on my machine.
Might be an issue that depends on the Python & SCons version that is used?
My setup:
c:\Work\godot>python --version
Python 3.6.4

c:\Work\godot>scons --version
SCons by Steven Knight et al.:
        script: v<IP_ADDRESS>b2c53bc42290e911b334a6b44f187da698a668, 2017/11/14 13:1
6:53, by bdbaddog on hpmicrodog
        engine: v<IP_ADDRESS>b2c53bc42290e911b334a6b44f187da698a668, 2017/11/14 13:1
6:53, by bdbaddog on hpmicrodog
        engine path: ['C:\\Program Files\\Python36\\scons-3.0.1\\SCons']
Copyright (c) 2001 - 2017 The SCons Foundation

Same issue.
Setup:

Windows 10 64 bits
Python 3.6.5 (32 bits)
Scons 3.0.0

Same problem, same fix here. I think you are supposed to run it that way so the Visual Studio environment variable are set. Maybe it should be specified in the documentation ?

Can someone try https://github.com/godotengine/godot/pull/22026? This has been annoying me.