How to predict using trained model?

I trained a model using the s3dis dataset out, but I see that the prediction asks for a .ply file, I don't know where this file comes from and what format is requested

The PLY format is a common format for meshes and point clouds, see https://en.wikipedia.org/wiki/PLY_(file_format).
The original S3DIS dataset comes in this format.
In the Download section of the page http://buildingparser.stanford.edu/dataset.html, you can find the instructions to download the S3DIS dataset in the original format (it involves filling in a form to request the dataset).

The PLY format is a common format for meshes and point clouds, see https://en.wikipedia.org/wiki/PLY_(file_format). The original S3DIS dataset comes in this format.
In the Download section of the page http://buildingparser.stanford.edu/dataset.html, you can find the instructions to download the S3DIS dataset in the original format (it involves filling in a form to request the dataset).
Okay thank you! I thought the raw data for the S3Dis dataset was in .h5 format, so I was a little confused and I was trying to download the S3DIS dataset to see if it would be useful

The PLY format is a common format for meshes and point clouds, see https://en.wikipedia.org/wiki/PLY_(file_format). The original S3DIS dataset comes in this format.
In the Download section of the page http://buildingparser.stanford.edu/dataset.html, you can find the instructions to download the S3DIS dataset in the original format (it involves filling in a form to request the dataset).

Okay thank you! I thought the raw data for the S3Dis dataset was in .h5 format, so I was a little confused and I was trying to download the S3DIS dataset to see if it would be useful


Working with Quick Launcher?

This may have already been answered but I saw a update just got pushed. Is it supposed to be working with the quick launcher or do i have to uninstall and redownload for it to work?

nvm. i got it to work by reinstalling.


[Type checker] Eliminate all speculative getAllConformances() calls.

Later stages should only require the "local" conformances, which are
checked as part of type checking.

@swift-ci please smoke test

@swift-ci please test source compatibility

Bah. Index-while-building's use of ValueDecl::getSatisfiedProtocolRequirements() depends on these getAllConformances() calls. We are tracking the elimination of that API in rdar://problem/41548725.

Looks like we got rid of the last of these.

Excellent; this is no longer needed


Pointer events

Frui needs an easy way to handle pointer events.
In this issue I wanted to document the overall API I am planning.
Pointer Listener
Widget that responds to low-level pointer events.
PointerListener::builder()
    .on_pointer_down(|e| { ... })
    .on_pointer_up(|e| { ... })
    .on_pointer_scroll(|e| { ... })

Pointer Region
Widget that responds to pointer entering child's widget region.
It also allows changing cursor icon (e.g. to a pointer icon when hovering over a button).
PointerRegion::builder()
    .cursor(Cursor::Pointer)
    .on_enter(|e| { ... })
    .on_move(|e| { ... })
    .on_exit(|e| { ... })

Gesture Recognizer
Widget that distinguishes between different high-level gestures.
GestureRecognizer::builder()
    .on_tap(|e| { ... })
    .on_double_tap(|e| { ... })
    .on_vertical_drag(|e| { ... })
    // ...

I was thinking about adding an ability to directly extend that widget with custom gestures:
fn add_gesture<G: Gesture>(self, gesture: G, callback: impl Fn(G::Event)) -> Self {
    // ...
}

Above builder method could then be abstracted using extension trait and used like:
GestureRecognizer::builder()
    .on_tap(|_| { ... })
    .on_my_custom_gesture(|_| { ... })

As of now, I am working on implementing PointerListener and KeyboardListener (other issue).
GestureDetector is a little bit tricky to implement and not that useful on PC, so I plan to implement it later when we will focus on supporting mobile devices. For now, PointerListener and PointerRegion should be enough for handling input on PC.

PointerListener and PointerRegion were implemented in https://github.com/fruiframework/frui/pull/10.


Feature Request : healthchecks

I've never used morph, but one feature of morph caught my attention a while ago.
I'm using colmena now (great work btw), and I would like to be able to run health check on my instances after deployments and when I feel like it.
I actually like the design of morph here : https://github.com/DBCDK/morph/blob/master/examples/healthchecks.nix#L22
A command line argument (health-check) would be great as well.
At the moment I us flake apps, but it is neither convenient nor easy to read.

This is also very interesting to me. I think it would also be nice to have healthchecks types that:

run on the local node (to verify external service connectability)
query a promql/logql endpoint and compare the results to some value, or perhaps relative to an earlier window for the same metric (granted, this one would be a lot more complicated)

@mrVanDalo Could you please share what your current solution looks like? I'm curious how tenable it might be for my relatively small use case. (~20 VMs)

At the moment I have something like this :
...
apps.${system}.test = {
  foo = {
    type = "app";
    program = toString (pkgs.writers.writeBash "foo" ''
      echo "testing foo"
      set -e
      set -x
      curl --fail https://service.example.com
      set -x
      echo "All Good"
    '');
  };
  bar = {
    type = "app";
    program = toString (pkgs.writers.writeBash "bar" ''
      echo "testing bar"
      set -e
      set -x
      ssh bar.private "systemctl is-active --quiet smartd && echo Service is running"
      set -x
      echo "All Good"
    '');
  };
};

colmena = {
    meta = {
      nixpkgs = import nixpkgs {
        system = "x86_64-linux";
        overlays = [(_self: _super: {
          unstable = nixpkgs-unstable.legacyPackages.${pkgs.system};
          })];
      };
    };

    defaults = { name, pkgs, ... }: {
      deployment.buildOnTarget = true;
      ...
    };

    foo = { name, nodes, pkgs, ... }: {
       ...
    };

    bar= { name, nodes, pkgs, ... }: {
       ...
    };
};
...

And I trigger these tests using :
nix run ".#test.foo"
nix run ".#test.bar"

I think it's not comfy, and it would be much better to put the test definition next to the service that is been tested, as well tests are running right after the deployment (of with a small delay) to make sure everything is really working.

Mm, yeah. I see what you mean. Being able to put them in my service-centric modules would definitely be a lot nicer. At this point, I'm vaguely considering just making a bunch of shell scripts I can call in the meantime with a hostname.

Okay, I decided to make something a bit more real than a pile of bash scripts.
I have a small Rust program I've put up at https://github.com/treed/colmena-health
(@zhaofengli please let me know if you'd like me to change the name away from using the name colmena)
It is currently very simple, but can be driven from config directly in the nix expressions (via colmena eval) to check HTTP endpoints and DNS resolution. I have a TODO list to add at least ssh as a check type and a few other things.
My intention is to treat this as a prototype to work out how healthchecks might work, with an eye towards eventually using it as the basis for implementing healthchecks directly in Colmena if that's acceptable.
There's a README that should help guide towards usage. Let me know if you have thoughts.

Also it's maybe worth mentioning that I haven't used Rust in a few years, and notably haven't really used async Rust ever.
So if anyone has any code-feedback, that would also be welcome.

Added an ssh check type that uses the user's own ssh because I realized that trying to make use of .ssh/config and ssh-agents with thrussh was going to be a pain. This way there shouldn't be any surprises in terms of how the ssh works compared to any other ssh done by the user.
I'll probably let this bake for a bit and start trying to add healthchecks to my stuff to test it out further.

once we have health checks colmena will be the ultimate deployment solution imo

I finally managed to create a flake module which solves this problem. Have a look
https://github.com/mrVanDalo/nixos-healthchecks
feedback welcome.


bad memory access in collection store

version from trunk, compiled on Windows x64 (VC14) for httpd 2.4.23.
persist_dbm.c, collection_store(), line 528
blob[blob_offset + 2 + len - 1] = '\0';
=> Exception 0xC0000005: Access violation reading location 0x000000005F5F4E41
var    0x0000000012f571f8 {
name=0x0000000012f57598 "__name"
name_len=318076280
value=0x000000005f5f4e41
value_len    318076360    unsigned int
}
This is for a custom counter using only numerics (increment only):
te[i].key   0x0000000012f4afd8 "blocked"
var->value points to an invalid memory location.
Btw, is it normal that name_len is incorrect?
How to troubleshoot this?

Hi @marcstern,
The first thing that we have to check is if the version of APR that was used during the compilation and/or loading time is the same one that was used by Apache. The version mismatch may lead to problems like this one that you have. During the startup of ModSecurity, it prints out those version numbers in the error_log. Can you check?

APR compiled version="1.5.2"; loaded version="1.5.2"

Hi @marcstern,
It seems that the version is right. What about the compilation flags? Apr, Apache and ModSecurity were compiled by you?

Same compile options for all modules/dll (same problem without debug and full optimisation).
CL options:
/RTCc /MP /FR"Debug" /GS /Zc:rvalueCast- /Qpar- /W3 /wd"4100" /wd"4133" /wd"4244" /wd"4267" /wd"4311" /wd"4312" /wd"4710" /wd"4711" /wd"4820" /wd"4996" /Gy /FAu /Zc:wchar_t /guard:cf /Zi /Gm- /Od /Ob0 /sdl- /fp:precise /D "_CRT_SECURE_NO_WARNINGS" /D "_WIN32_WINNT=0x0600" /D "WINDOWS" /D "_WINDLL" /D "_WIN64" /D "WIN64" /D "_WIN32" /D "WIN32" /D "x_UNICODE" /D "xUNICODE" /D "NOCOMM" /D "NOKANJI" /D "NOMCX" /D "NOHELP" /D "NOPROFILER" /D "NOSOUND" /D "_DEBUG" /fp:except /errorReport:prompt /GF- /WX- /Zc:forScope /RTC1 /GR- /arch:AVX /Gd /Oy- /MDd /openmp- /Fa"Debug" /nologo /Fo"Debug"
LINK options:
/ALLOWBIND /MANIFEST /NXCOMPAT /FUNCTIONPADMIN:6 /DYNAMICBASE:NO "advapi32.lib" "comctl32.lib" "comdlg32.lib" "gdi32.lib" "iphlpapi.lib" "kernel32.lib" "mswsock.lib" "rpcrt4.lib" "shell32.lib" "user32.lib" "uuid.lib" "winspool.lib" "wldap32.lib" "ws2_32.lib" "wtsapi32.lib" "ole32.lib" "oleaut32.lib" "odbc32.lib" "odbccp32.lib" /RELEASE /LARGEADDRESSAWARE /IMPLIB:"Debug\libaprutil-1.lib" /DLL /LTCG:NOSTATUS /MACHINE:X64 /WINMD:NO /WX:NO /OPT:NOREF /SAFESEH:NO /CLRSupportLastError /INCREMENTAL:NO /SUBSYSTEM:CONSOLE /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /OPT:NOICF /ERRORREPORT:PROMPT /CLRUNMANAGEDCODECHECK /NOLOGO /TSAWARE:NO /ASSEMBLYDEBUG:DISABLE /TLBID:1 /DELAYSIGN:NO

Hi @marcstern,
I was not able to reproduce your problem, did you managed to reproduce the same problem/error in another computer?

Related to a combination of compile options. Not sure which ones :-(


Issue: Input Box and Header Move Out of Reach with Added Items

Description
As more items are added to the task list, the entire section (including the input box and header) shifts upward, eventually becoming unreachable. This issue makes it difficult for users to continue adding new tasks once the input box is out of view.
Steps to Reproduce

Open the application.
Add tasks using the input box.
Observe that as tasks accumulate, the input box and header are pushed upward.

Expected Behavior
The input box and header should remain fixed at the top of the page. Newly added tasks should appear below the fixed input section, allowing the user to access the input box at all times.
Actual Behavior
The input box and header move upward along with the added tasks, making it difficult or impossible to add new tasks once the input box is out of view.
Screenshot

@Anshgrover23 Assign this issue to me. I would like to work on this issue.


CSP-1484: PR Jobs: Handler for EAS event UpdatedLegalEntityEvent

Added a new handler UpdatedLegalEntityEventHandler to manage the UpdatedLegalEntityEvent message.

@DevenKShah Can I get a re-approval on this please


License

I am interested in using this blade element analysis package as part of a drone performance calculator. Would you consider open sourcing your code?

Sure. It is already FOSS.


chroma-ui

We don't know exactly what users want yet in a frontend, but here are some very general ideas

View what "spaces" you have
View underlying data in the browser
Run SQL queries against those datasets in the browser

Down the road

View projections

Step 1 would be to figure out a sketch of how we would package it up.

any updates here? almost a year...

@joezein this was actually about the previous thing that chroma was building :) in the mean-time https://twitter.com/tcarambat/status/1684614486798565376 is worth serious consideration!


SparkLinker error 'DataFrame' object has no attribute 'sql_ctx'

What happens?
I'm trying to get the tutorial examples running on Azure Databricks using the PySpark back-end
Having read the fake_1000.csv into the data frame, I get the following error:
AttributeError                            Traceback (most recent call last)
<command-1982314540290032> in <cell line: 3>()
      1 # Initialise the linker, passing in the input dataset(s)
      2 from splink.spark.spark_linker import SparkLinker
----> 3 sparkLinker = SparkLinker(df)

/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.9/site-packages/splink/spark/spark_linker.py in __init__(self, input_table_or_tables, settings_dict, break_lineage_method, set_up_basic_logging, input_table_aliases, spark, break_lineage_after_blocking, num_partitions_on_repartition)
     91             for t in input_tables:
     92                 if type(t).__name__ == "DataFrame":
---> 93                     self.spark = t.sql_ctx.sparkSession
     94                     break
     95         if self.spark is None:

To Reproduce
# Set up blob storage access
spark.conf.set(
    "fs.azure.account.key.<storage>.dfs.core.windows.net",
    dbutils.secrets.get(scope="splink-secrets", key="AccountKey--Storage"))

import pandas as pd
import altair as alt
alt.renderers.enable('mimetype')

df_spark =<EMAIL_ADDRESS>header='true')
df = df_spark.toPandas()
df.head(5)

# Initialise the linker, passing in the input dataset(s)
from splink.spark.spark_linker import SparkLinker
sparkLinker = SparkLinker(df)

OS:
Azure Databricks runtime 11.3.x-scala2.12
Splink version:
3.0.0 to 3.7.0.dev1
Have you tried this on the latest master branch?

[X] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

You need to pass df_spark not df into SparkLinker

Thanks, I had originally tried that, but got the below error, hence the attempt to convert it back to pandas to match the tutorial
AttributeError                            Traceback (most recent call last)
<command-1982314540290032> in <cell line: 3>()
      1 # Initialise the linker, passing in the input dataset(s)
      2 from splink.spark.spark_linker import SparkLinker
----> 3 sparkLinker = SparkLinker(df_spark)

/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.9/site-packages/splink/spark/spark_linker.py in __init__(self, input_table_or_tables, settings_dict, break_lineage_method, set_up_basic_logging, input_table_aliases, spark, catalog, database, repartition_after_blocking, num_partitions_on_repartition)
    162         self.in_databricks = "DATABRICKS_RUNTIME_VERSION" in os.environ
    163         if self.in_databricks:
--> 164             enable_splink(spark)
    165
    166         self._set_default_break_lineage_method()

/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.9/site-packages/splink/databricks/enable_splink.py in enable_splink(spark)
     13         None
     14     """
---> 15     sc = spark.sparkContext
     16     _jar_path = similarity_jar_location()
     17     JavaURI = getattr(sc._jvm.java.net, "URI")

What version of Spark are you running?

11.3 LTS (includes Apache Spark 3.3.0, Scala 2.12)

Thanks. We're looking into this but in the meantime if you pass spark into to the linker it should work: https://github.com/moj-analytical-services/splink/blob/5c7e9b0d2dfa5c6a1acb170314f083efd5a22a1b/splink/spark/spark_linker.py#L107


Make DataTable composable

:tada: This issue has been resolved in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


BatchNormalization with GPU placement (TensorFlow)

Please make sure that the boxes below are checked before you submit your issue. If your issue is an implementation question, please ask your question on StackOverflow or join the Keras Slack channel and ask there instead of filing a GitHub issue.
Thank you!

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[x] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[x] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

I have the following sample code:
https://gist.github.com/alrawi/0f6ce637d2955ab2e9c0d4b69509f5de
I cannot get BatchNormalization to be placed on GPU. My model fits on the GPU, but for BatchNormalization I get the following warning:
WARNING:tensorflow:Tried to colocate gradients_2/batch_normalization_3/moments/sufficient_statistics/count_grad/Rank with an op batch_normalization_3/moments/sufficient_statistics/count that had a different device: /device:CPU:0 vs /device:GPU:2. Ignoring colocation property.
I am suspecting that this is a type problem, since most GPUs don't support 64 bit operations. Here is some information about my system, I have 3 GPUs, device two is shown below:
NVIDIA-SMI 367.48 Driver Version: 367.48 GeForce GTX TITAN
Suggestions?

I have a similar problem. Adding BatchNormalization causes the following output:
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Rank with an op batch_normalization_1/moments/sufficient_statistics/cou
nt that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/range_1/start with an op batch_normalization_1/moments/sufficient_stati
stics/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/range_1/delta with an op batch_normalization_1/moments/sufficient_stati
stics/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/range_1 with an op batch_normalization_1/moments/sufficient_statistics/
count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/ListDiff with an op batch_normalization_1/moments/sufficient_statistics
/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/concat/axis with an op batch_normalization_1/moments/sufficient_statist
ics/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/concat with an op batch_normalization_1/moments/sufficient_statistics/c
ount that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Gather with an op batch_normalization_1/moments/sufficient_statistics/c
ount that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Const with an op batch_normalization_1/moments/sufficient_statistics/co
unt that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Prod with an op batch_normalization_1/moments/sufficient_statistics/cou
nt that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Gather_1 with an op batch_normalization_1/moments/sufficient_statistics
/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Const_1 with an op batch_normalization_1/moments/sufficient_statistics/
count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Prod_1 with an op batch_normalization_1/moments/sufficient_statistics/c
ount that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.

Can you provide us with the placement that TF does for every op in the BN
layer? These ops are created in a name scope by the name of the layer (in
Keras 2).
On 17 March 2017 at 03:47, vsenko<EMAIL_ADDRESS>wrote:

I have a similar problem. Adding BatchNormalization causes the following
output:
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Rank with an op batch_normalization_1/moments/sufficient_statistics/cou
nt that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/range_1/start with an op batch_normalization_1/moments/sufficient_stati
stics/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/range_1/delta with an op batch_normalization_1/moments/sufficient_stati
stics/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/range_1 with an op batch_normalization_1/moments/sufficient_statistics/
count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/ListDiff with an op batch_normalization_1/moments/sufficient_statistics
/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/concat/axis with an op batch_normalization_1/moments/sufficient_statist
ics/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/concat with an op batch_normalization_1/moments/sufficient_statistics/c
ount that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Gather with an op batch_normalization_1/moments/sufficient_statistics/c
ount that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Const with an op batch_normalization_1/moments/sufficient_statistics/co
unt that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Prod with an op batch_normalization_1/moments/sufficient_statistics/cou
nt that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Gather_1 with an op batch_normalization_1/moments/sufficient_statistics
/count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Const_1 with an op batch_normalization_1/moments/sufficient_statistics/
count that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
WARNING:tensorflow:Tried to colocate gradients/batch_normalization_1/moments/sufficient_statistics/count_grad/Prod_1 with an op batch_normalization_1/moments/sufficient_statistics/c
ount that had a different device: /device:CPU:0 vs /device:GPU:0. Ignoring colocation property.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/5802#issuecomment-287323262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArWb7q8s7Okc4FjWhKsrHHMJe_rS3x7ks5rmmS0gaJpZM4Mey-n
.

Here is the placement log for the run above. I modified the code to do the placement log.
https://gist.github.com/alrawi/f92c1a6603134b2cc6b523b0c483d8b5

This seems to be somehow realted to an issue in TensorFlow.
I'm not sure why this toy example works:
import tensorflow as tf
import numpy as np

with tf.device('/gpu:2'):
    X = tf.placeholder(tf.float32, shape=[None, 100])
    Y = tf.placeholder(tf.float32, shape=[None])
    mean, var = tf.nn.moments(X, axes=[0])
    norm = (X - mean) / var
    gamma = tf.Variable(tf.ones([1, 100]))
    beta = tf.Variable(tf.zeros([1, 100]))
    loss = tf.reduce_sum(tf.squared_difference(tf.reduce_sum(gamma*norm+beta, axis=[1]), Y))
    grad = tf.gradients(loss, [gamma, beta], colocate_gradients_with_ops=True)

config = tf.ConfigProto(log_device_placement=True, allow_soft_placement=False)
sess = tf.Session(config=config)

x = np.random.random((10, 100)).astype(np.float32)
y = np.random.random((10)).astype(np.float32)

with tf.device('/gpu:2'):
    sess.run(tf.global_variables_initializer())
    resres = sess.run(grad, feed_dict={X: x, Y: y})
print(resres)

I was able to reproduce the same error with pure TensorFlow, so it seems the problem is in TensorFlow; tf.moments() and its gradient calculation on unresolved axis with GPU causes the error. I posted those results to the issue linked above.

I have the same problem.
I created a model with a BatchNormalization layer.
I then do data parallelization - I split the batch into two halves, and
apply the model on each half (on different GPUs), then concatenate results.
Batchnormalization fails with the above error.
I'm assuming that it is because it doesn't know how to compute the moving
means across multiple GPUs?
How can I get around this problem?
There used to be a mode of BatchNormalization that does not compute a
moving mean but just takes the batch's mean.
Could it be utilized somehow?
On Thu, Mar 30, 2017 at 4:12 PM, Namnamseo<EMAIL_ADDRESS>wrote:

I was able to reproduce the same error with pure TensorFlow, so it seems
the problem is in TensorFlow; tf.moments() and its gradient calculation
on unresolved axis with GPU causes the error. I posted those results to the
issue linked above.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/5802#issuecomment-290406340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFdLCCMQSTx9bhk3HsXhSsh7CZzWRKAfks5rq6pZgaJpZM4Mey-n
.

This is fixed in tensorflow/tensorflow#8906.
I tested @alrawi's sample code and monitored the device allocation. All of them are appropriately placed on GPU as intended. Device colocation error did not occur.
@fchollet, can we close it?

Sure, SG


Move fsverity package to internal

This functionality is not directly related to containerd and could move to external package at some point.

This functionality is not directly related to containerd and could move to external package at some point.

pkg/ might be a better place?

This functionality is not directly related to containerd and could move to external package at some point.

pkg/ might be a better place?

pkg (or any non-internal) makes it part of the public Go API, which means we have to support it until containerd v3; if there's no external users yet, keeping it internal may be a good thing to do


added tags to cell_metadata_keep

This is to allow the usages of tags in notebooks to also be in the repo when using the nbdev githooks.

I don't see why not, thanks!


Interfaces: begin wrapping parts of D3D API

This adds wrappers for the COM interfaces for D3D.

Hopefully the next snapshot will be able to build this.  The first snapshot with the D3D module seemed to have caused an inadvertent regression due to the XInput module.

Hopefully the next snapshot will be able to build this.  The first snapshot with the D3D module seemed to have caused an inadvertent regression due to the XInput module.


'Someone is watching' alert mentions History (which has disappeared)

When MBHD is in debug mode the user gets a security warning.
The text of the warning mentions 'See history' but there is no history anymore.

I just retested this and there is no mention of History. Also no mention in the language files.
Nothing to do.
Awaiting review and closing

Well... doing a search for "history" across the codebase does reveal quite a few dead code entries that reference it. We could do a sweep through in the interests of code hygiene. Your call though - close if you don't want to.

Marking as bounced back purely to encourage a code review of my changes.
Ready for review and close.

LGTM.
Closing


feat(build): upgrade to Go 1.18, update GoReleaser to latest version

⚠ Note: GoReleaser v1.7+ has upgraded to use Go version 1.18.0 and seems to be importing a module that requires Go 1.18, thus this PR also includes updating the actions/setup-go in our workflows to use Go version 1.18.x. Attempting to run GoReleaser without Go 1.18 resulted in a runtime error caused by a new feature in Go 1.18 that does not exist in Go 1.17.
Checklist:

[x] Update actions/setup-go in GitHub workflows
[x] Update README to reflect Go 1.18 dev requirement (double check to see if we reference older Go versions in other areas)
[x] Ensure newrelic-client-go is compatible with the CLI upgrading to Go 1.18

Resolves: #1050
Resolves: #1266

I don't have any concerns @Julien4218

Thanks for the review!


Logic to select a locale when sending a SMS seems to be wrong

Describe the issue:
We are using DefaultNotificationHandler[1] to send SMS notifications from the code snippet[2]. In [2] the logic we are referring to is incorrect because we should not look for a different locale depending on the notification channel (SMS or EMAIL). Instead, we should take the locale in the user's profile.
How to reproduce:

Add a new template (password recovery SMS template) from another language.
Change the language to a language other than EN_us (same as the above template)
Try password or username recovery with SMS (other SMS flows won't go through this flow).

Expected behavior:
Send SMS from the specified locale in the user's profile.
Possible fix
Remove the code snippet [2] and replace it with the following block.
if (userClaims.containsKey(NotificationConstants.EmailNotification.CLAIM_URI_LOCALE)) {
    locale = userClaims.get(NotificationConstants.EmailNotification.CLAIM_URI_LOCALE);
}

NOTE: Better to rename the variables since DefaultNotificationHandler should have a general implementation.

[1] - https://github.com/wso2-extensions/identity-event-handler-notification/blob/master/components/event-handler-notification/org.wso2.carbon.identity.event.handler.notification/src/main/java/org/wso2/carbon/identity/event/handler/notification/DefaultNotificationHandler.java
[2] - https://github.com/wso2-extensions/identity-event-handler-notification/blob/master/components/event-handler-notification/org.wso2.carbon.identity.event.handler.notification/src/main/java/org/wso2/carbon/identity/event/handler/notification/DefaultNotificationHandler.java#L142-L152

I have tested this with IS 6.0.0 and seems like it is working as expected. Tested for password recovery and self-registration using SMS OTP. User's local is identified and uses default locale if local is not defined in the user profile.
If a user is specifying a locale, then there needs to be a template in the registry with that type. Otherwise it won't work

Closing this since the issue cannot be reproduced


Improve "No Translate" button in TinyMCE

In Wordpress we have a TinyMCE plugin that allows marking text with <span translate="no"> tags. This functionality is very basic and does not working when spanning several other HTML Tags. A better implementation in Django would be cool. If this is programmed as a normal TinyMCE plugin, this could probably be backported to the current Wordpress plugin.

We already have a no-translate button which inserts the span. However, it does not yet work across multiple tags, so I'll leave this issue open to improve the functionality.


Flex Insights friendly changes

Hi team,
I am proposing these two changes to link the callback and outbound tasks to the original conversation.
This will help creating custom metrics in Flex Insights.

[ x ] I acknowledge that all my contributions will be made under the project's license.

Thank you so much @fplacido!! That's a great addition.
Just to bring everybody up to speed on our conversation, this will allow the callback / voicemail task to be associated to the same conversation as the original task in Flex Insight:

I'll do a proper review and some more tests in the next few days and let you know. @bermudezmt @ktalebian @rnairtwilio fell free to pitch in on this.


Latest gem release 0.4.0 doesn't get installed

The latest gem release v0.4.0 does't get installed in a rails 4.2.1 app because of activesupport dependency for this gem.
But works fine with the latest master.
@gary-rafferty Could you possibly release a new gem version which could fix this. So that i won't have to point to a github link in my gemfile

Thanks for letting me know @alfred-rp - Ive just pushed a new version to Rubygems.
Please do let me know if issue remains.

Nop the issue is resolved. Thanks :)


[FancyZones] Span across monitors setting does not function

ℹ Computer information

PowerToys version: v0.21.1
PowerToy Utility: FancyZones
Running PowerToys as Admin: No
Windows build number: Windows 10 Version 2004: 19041.450

📝 Provide detailed reproduction steps (if any)

Check the Allow zones to span across monitors checkbox
Configure a zone which uses multiple monitors via the Launch zones editor and Apply
Attempt to snap window to zones, or use Shift key to highlight zones while dragging

✔ Expected result

A window should snap to a zone
Zone highlighting ought to be functional
The Allow zones to span across monitors setting should persist even when closing settings
If there are errors "Activating" the zones, these should be raised to the user

❌ Actual result

A window will not snap to a zone when the Allow zones to span across monitors is configured
Window zone highlighting is also not functional
When FancyZones settings is closed and re-opened, the Allow zones to span across monitors checkbox is unchecked
When Allow zones to span across monitors is toggled to checked, then unchecked, zone highlighting and snapping functions, though obviously not with the multi-monitor zones

📝 Other Notes

There is a difference in framerate/refresh rate between the two monitors--could that be an issue?
System is a SurfaceBook 2 in a Surface Dock which drives a 2560 x 1440 monitor at 60 fps and a 2560 x 1440 monitor at 30 fps

The fps cannot be made the same as far as I can tell. Likely a hardware limitation.

Display is an LG 49 ultra-wide ( 5120 x 1440)

📷 Screenshots

FancyZones Settings:

Zone Editor spanning monitors:

Monitor configuration:

I have the same issue, with some more information.
Samsung 49" Ultrawide, 5120x1440, connected as 2 x DisplayPort monitors, both running at 2560x1440 @ 60Hz.

FancyZones not functional with apply across monitors - shift key or alternate mouse button do nothing when dragging windows
Set across monitors does not retain when leaving FancyZones settings
Zone editor previews across all zones correctly when trying to set zones, but applying does not "do" anything - go back into editor and it is back to the default 3 x stacked

Same issue.
Two totally separate monitors.

I'm going to roll back to the previous version as FZ is now completely broken :(
Laptop setup to drive two screens issue as described above; on a PC connected to same screen driving it as a single 5120x1440 holding shift key while moving a screen crashes Explorer (even when NOT set to allow zones to span across monitors, as there is only one). Also zone editor no longer retains any selected / edited zones.

@Swallowtail23

I'm going to roll back to the previous version as FZ is now completely broken :(

If you turn off "Allow zones to span across monitors" what is not working for you in 0.21.1?

@Swallowtail23
can you please open separates issues for the other problems you are experiencing with 0.21.1, thanks.

Same issue.
apply span across monitors but do nothong when hold Shift key

@Burning1020
have you applied a new layout after enabling the feature?

@Burning1020
have you applied a new layout after enabling the feature?

i did. i lauch editor -> choose my custom layout -> apply -> hold Shift key but the blue backgroud  frame doesn't apper -> back to editor and it back to deafult layout as mentioned above

Thank you all for reporting this, we have found the cause.

Not sure if this fits here, but custom layout on a desktop that spans two monitors not working as expected.
Layout editor appears to work, and then I  apply, but when snapping it uses another different layout pattern.
One monitor is landscape and the other portrait.

Same happens for me as of 9/7/2020 on a fully up-to-date installation of Windows 10, with PowerToys v0.21.1.
Effectively there is no multi-monitor support for Fancy Zones since the SHIFT+Drag does not work and the zone settings are not saved when that option, "Allow zones to span across windows", is active.

Fixed in 0.23.0 https://github.com/microsoft/PowerToys/releases/tag/v0.23.0


docs/proposals: clean up parser proposal

Signed-off-by: Lucas Servén Marín<EMAIL_ADDRESS>

Looks good now. Thanks!


Labs completed

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Completed labs 1 to 6
What did you learn from the changes you have made?
Building multi-layer NN and CNN models; recommendation system; image classification/recognition; text classification.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
No
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Determining the inputs and outputs of different layers.
How were these changes tested?
Running the codes, and understanding any error messages. The inputs and outputs data/arrays were difficult to visualize separately.
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[Y] I can confirm that my changes are working as intended

Reviewed and marked as completed


Error loading some IFCs

I have an error with two IFC files only :

I'm using WIT 0.0.121 (a,d web-ifc 0.0.36). IFC 2X3 is used for those IFCs.
I can't share the file publicly so I will send to you @agviegas
Thanks !

Solved. Error in my code.


Fix #15 Astro DB no longer exports type Sqlitedb

There were no tests, not sure if this will work or not. It now only supports @astrojs/db >= 0.11.

@pilcrowOnPaper could you take a look and release a new major version. I would be great to have this adapter up to date with astro new versions. Thanks

Oof, thanks for the ping


Create lint and test workflow

Problem
Deployments need to be more automatized
Solution
Lets try out github actions!

Coverage decreased (-0.02%) to 95.508% when pulling 5d2a2acb2076fd898381f52e8ddc22017f84c147 on first-github-action into b76c0940a13d818543583010f4fe63610bd2a954 on master.


Issue with artisan commands on fresh install on Windows 10

Laravel Version: 5.4.23 & 5.5 dev branch

PHP Version: 7.0

Database Driver & Version: MySQL

Using Windows 10

Description:
Creating a new project with a fresh install using laravel new project-name or composer create-project laravel/laravel project-name hits the following issue when using artisan:
> php artisan optimize

  [ErrorException]
  The Symfony\Component\Process\ProcessUtils::escapeArgument() method is deprecated since version 3.3 and will be removed in 4.0. Use a command line array or give env vars to the Process::start/run() method instead.

Script php artisan optimize handling the post-install-cmd event returned with an error

[RuntimeException]
Error Output:

Running any php artisan commands returns the same error.
Steps To Reproduce:

Install fresh Laravel app on windows 10. - laravel new project-name
This Should hit the error when php artisan optimize is run.

This will produce:
> php artisan optimize

  [ErrorException]
  The Symfony\Component\Process\ProcessUtils::escapeArgument() method is deprecated since version 3.3 and will be removed in 4.0. Use a command line array or give env vars to the Process::start/run() method instead.

Script php artisan optimize handling the post-install-cmd event returned with an error

[RuntimeException]
Error Output:

Running any artisan command with php artisan <command> will return the above error.

Check your php.ini file and find this:
scream.enabled=1

If found change it to:
scream.enabled=0

restart and let me know if it works

Perfect, thanks! It was my xdebug settings I had:
xdebug.scream = 1
Based on your example I changed it to:
xdebug.scream = 0
Now it runs as expected.

great :)

Hi,
I am using vagrant with php 7.1 and I tried to found
scream.enabled=1

and
xdebug.scream = 1

but not found

For those who will stumble here, the path to the file folks are talking about: /etc/php/7.1/fpm/conf.d/20-xdebug.ini
(tested on Ubuntu)

Hi,
I am using laradock，I can,t find the php.ini。what should i do？
My Laravel version is on 5.4.36

There is something wrong with my schedule may be cause by this problem：
[mesage_from]error:[level]3=>LOG_ERR: [message_body]错误码16384=>The Symfony\Component\Process\ProcessUtils::escapeArgument() method is deprecated since Symfony 3.3 and will be removed in 4.0. Use a command line array or give env vars to the Process::start/run() method instead

I set withoutOverlapping,  but seems not work.
schedule file
$schedule->command('produce:email')->everyFiveMinutes()->withoutOverlapping();

command file
`
public function handle()
{
$name = mt_rand(10000,99999);
    Log::info($name . ':开始运行时间'.date('Y-m-d H:i:s'));

    $this->parseAppName();

    $this->createQueue();

    if(count($this->queue) <= 0){
        return ;
    }

    foreach ($this->queue as $key => $queue) {

        $this->getHistoryId($key,$queue['filter']);

        $this->executeAdd($key,$queue);
    }

    Log::info($name .':结束运行时间'.date('Y-m-d H:i:s'));
}

`
Log File
`
[2018-07-10 09:21:08] local.INFO: 91991:开始运行时间2018-07-10 09:21:08
[2018-07-10 09:22:03] local.INFO: 51228:开始运行时间2018-07-10 09:22:03
[2018-07-10 09:23:03] local.INFO: 77517:开始运行时间2018-07-10 09:23:03
[2018-07-10 09:23:06] local.INFO: 91991:结束运行时间2018-07-10 09:23:06
`
The 51228 and 77517 run before the 91991 ended


Allow libsqlite3-sys 0.9 to be used

Maybe we should include this in the diesel 1.0.0 release?

Want me to open a PR for the 1.0 branch too ?


Question - how to install latest version into Home Assistant?

Hi
today Home Assistant installed version 0.4.2. How can I install a newer version as an addon?
Thanks

I don't quite understand your question but v0.4.2 is the latest version

I apologize for the misunderstanding. I was confused by the latest version of EMHASS 0.5.1 and I didn't realize that the addon is versioned differently.


uuid v 8.0.0 not working on node

uuid v 8.0.0 not working correctly on Node
we installed with npm install uuid to the latest version, and when running our server got this callback:
<EMAIL_ADDRESS>start D:\ThinkfulDrills\post-delete-nicke-dan node src/server.js

internal/modules/cjs/loader.js:621 throw e; ^

Error: No valid exports main found for 'D:\ThinkfulDrills\post-delete-nicke-dan\node_modules\uuid' at resolveExportsTarget (internal/modules/cjs/loader.js:618:9) at applyExports (internal/modules/cjs/loader.js:499:14) at resolveExports (internal/modules/cjs/loader.js:548:12) at Function.Module._findPath (internal/modules/cjs/loader.js:650:22) at Function.Module._resolveFilename (internal/modules/cjs/loader.js:948:27) at Function.Module._load (internal/modules/cjs/loader.js:854:27) at Module.require (internal/modules/cjs/loader.js:1023:19) at require (internal/modules/cjs/helpers.js:72:18) at Object.<anonymous> (D:\ThinkfulDrills\post-delete-nicke-dan\src\app.js:7:24) at Module._compile (internal/modules/cjs/loader.js:1128:30) { code: 'MODULE_NOT_FOUND' } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR<EMAIL_ADDRESS>start: node src/server.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the<EMAIL_ADDRESS>start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  C:\Users\Nick Evelson\AppData\Roaming\npm-cache\_logs\2020-04-30T19_37_28_990Z-debug.log

To Reproduce
Steps to reproduce the behavior:

Install 'npm install uuid'
Run 'npm start' as a script to run the server/app
See error

Expected behavior
I expected it behave normally, but this is a new patch.
Runtime

OS: [Windows 10]
Runtime: [Node.js]
Runtime Version: [13.3.0]

See this issue https://github.com/uuidjs/uuid/issues/428

Yes. Please upgrade to latest node 13.x or 14. https://github.com/uuidjs/uuid/issues/428#issuecomment-621519202


GA Migration Postcommit Go VR Flink, Samza, and Spark

As part of the migration of Precommit and Postcommit Jobs from Jenkins to GA in self-hosted runners, this PR contains:

Migrated and sharded workflow job-postcommit-go-vr-samza.yml
Migrated and sharded workflow job-postcommit-go-vr-flink.yml
Migrated and sharded workflow job-postcommit-go-vr-spark.yml

The migrated workflows were added to CI.md
DO NOT MERGE until the effort to use self-hosted runners is completed https://github.com/apache/beam/pull/22703
These workflows use base actions listed in https://github.com/apache/beam/pull/23109 (Dependency)

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damccorm

Run Java PreCommit


treat 0 bucket bound as an error.

Enforcing spec

Oh oh this is a little concerning and going to be a breaking change for many people and all our libraries, examples and integrations too. For more than a year we've had buckets of [0, 10 etc acceptable. Enforcing a spec is great but should be gradual IMHO.

@odeke-em it will still accept 0 value bucket but will silently drop. So it will not break the api.


missing io.ReaderFrom for http1.1

Go 1.8 / 1.75 / 1.6.5
osx / linux

Validation with https://middleware.vet#github.com/NYTimes/gziphandler shows that GzipResponseWriter is not implementing io.ReaderFrom for http1.1
Is it possible to implement these only for http1.1 and not for http2 while still reusing response writers?

The io.ReaderFrom is implemented by *net/http.response for HTTP 1.x connections. If the underlying connection is a TCPConn then it uses the optimised sendfile system call (see (*TCPConn).readFrom) which, according to the man page:

sendfile() copies data between one file descriptor and another. Because this copying is done within the kernel, sendfile() is more efficient than the combination of read(2) and write(2), which would require transferring data to and from user space.

Unfortunately this optimisation is not possible because gziphandler has to gzip the response body. There is just no straight path from file descriptor to file descriptor.


Export the render function without the handler

Hi!
The error rendering is really nice with your package and I'd like to use it in one of my project.
I'd like to be able to use only the rendering part, without the handler (It's a server and I don't want to exit the process if an error occurs).
Something like :
const renderError = require('pretty-exceptions/render');

try {
    // failing code
} catch(error) {
    renderError(error);
}

Thanks !

good idea ...

done, released in v1.4.0


Fetch data from the Rockets endpoint pull request

Fetch data from the Rockets
-Use URL  constant
-fetch Rocket function as asynchronous
-use dispatch function which  called with an array transformation

Hi @theresetuyi      🙋♂,
Good job so far!
You have done well reaching this point of the milestone 🤝 It's time to merge it!

Top highlight 🎯

The Pull Request follows the GitHub Flow ✅
The PR title and description are professional and descriptive ✅
Linters are working properly ✅

Suggested changes

[x] Everything is great!

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


feat: List.foldlRecOn

As discussed with @semorrison, feel free to do whatever to the branch.

@hargoniX, is this okay?

Yes this works with LeanSAT! Feel free to merge.


[templates] PR and issue templates

to: @mime-frame
cc: @airbnb/binaryalert-maintainers
size: small
Changes
Add PR and issue templates

Coverage remained the same at 95.743% when pulling 489c65209c97ce1899a2abc935c3c6816c3de54f on jacknaglieri-add-pr-templates into 74c03b81549b316bf67f2937533f387a113bf90e on master.


Remove obsolete resources caused by merging controllers

Issue to be fixed
Fixes #90
Proposed Changes

Remove old resources that are obsolote after https://github.com/knative/eventing/pull/2448

Release Note

NONE

More info on how to find what went obsolete is available at https://github.com/knative/eventing-operator/issues/90
How to verify:

TBD

Notes:

Replaced the 0.12.0.yaml in kodata with the nightly release file (v20200206-05bba2be.yaml)
That nightly release file is fetched like this: gsutil cp gs://knative-nightly/eventing/latest/eventing.yaml ./

cc @houshengbo

Removed the WIP status to see what tests do, but can somebody please add a /hold?
cc @houshengbo @k4leung4

/ok-to-test

@aliok when we update the manifest, we need to update the version as well to match in version.go

/test pull-knative-eventing-operator-integration-tests-on-latest-eventing

@houshengbo I addressed your comments. Thanks for the feedback.
As I said in https://github.com/knative/eventing-operator/pull/93, let's merge this PR first and then that one. See that PR for my reasons.


Update russian translation

All new strings copied from en.json
Change space to tab in formating of file (as done in en.json)
New lines partly translated to russian

@AleksandrSokolov are you able to resolve the conflicts? Otherwise I can have a go at it

@glutamate Sorry I just saw your comment only now. I dont understand how to deal will confict using github.


DropboxOAuth2Helper.ParseTokenFragment call cause an ArgumentException

Recently  DropboxOAuth2Helper.ParseTokenFragment started to throw ArgumentException during  authentication.
case WebAuthenticationStatus.Success:
					var response = DropboxOAuth2Helper.ParseTokenFragment(new Uri(result.ResponseData));

ResposeData= ms-app://s-x-xx-x-xxxxxxxxxx-xxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxx-xxxxxxxxxx/#access_token=xxyvxxxxxxgxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxwx-xxxxotxtkxxxml_f&token_type=bearer&uid=xxxxxxxx&account_id=dbid%xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Probably the issue happens because account_id is present.
[System.ArgumentException] = {System.ArgumentException: Unexpected values in fragment
Parameter name: redirectedUri
   at Dropbox.Api.DropboxOAuth2Helper.ParseTokenFragment(Uri redirectedUri)
....

Thanks for the report! We're looking into it.

This should be fixed in 3.2.1. Try that and let us know if you're still seeing any issues.


dynamic fwd proxy: fix race condition in filter destructor

Commit Message:
dynamic fwd proxy: fix race condition in filter destructor
Additional Description:
Dynamic fwd proxy is specific comparing to other filters because it controls upstream cluster. The filter registers itself (this pointer) in ClusterManager as cluster callbacks: https://github.com/envoyproxy/envoy/blob/release/v1.29/source/extensions/filters/http/dynamic_forward_proxy/proxy_filter.h#L37.
In the filter's destructor, tls slot destructor will remove the registered callbacks. The problem is that tls slots are not destructed atomically. Instructions to release slots are posted on each thread and main thread continues with filter destructor. This means that there is a short period of time when the filter is gone (memory was released) but callbacks on each worker thread still point to the deleted callbacks. If at that time a worker thread iterates over callbacks, like here: https://github.com/envoyproxy/envoy/blob/release/v1.29/source/common/upstream/cluster_manager_impl.cc#L1314, it will access a callback pointer which has already been released.
I observed a crash when I reconfigured a dynamic fwd proxy 2 times per second. The code crashed after ~72 hrs. When I reconfigure the filter 50 timer per second the code crashes within 10 minutes.
The fix is to introduce some order when destructor is called. When callbacks are added to each thread, the added counter is increased. That counter is decremented on each thread when callbacks are deregistered. The destructor waits on condition variable until this pointer has been removed from all threads and the counter drops to zero.
Risk Level: Low
Testing: Manual. It is difficult to simulate thread switching in unit/integration tests.
Docs Changes: No
Release Notes: No
Platform Specific Features: No
Fixes https://github.com/envoyproxy/envoy/issues/32427

/retest

/retest

@alyssawilk Thanks a lot reviewing.

first, please don't publish crash fixes without checking with envoy-setec. I think this is hard enough to exploit we don't have to treat as a zero day but let's err on the side of caution.

Unless I am missing something, I believe that the protocol of reporting crashes was followed. The crash was originally reported to setec group and the reply was to log it as public issue: #32427.

second, looks like this may be a generic problem. having any "main thread" object register for thread local callbacks, seems like a recipe for deletion races. I'd lean towards a solution that works beyond proxy filter - I'd be inclined to change the function signature for adding the callback to be a shared pointer (here to a wrapper shim, that we can detatch from the DFP config) such that the shim will self-delete once no worker threads are pointed to it.
thoughts?

That sounds like a good idea. Let me experiment with this. The other option would be to modify TLSSlot destructor to wait for all slots to be destructed before continuing with main thread.

@alyssawilk I created another PR: https://github.com/envoyproxy/envoy/pull/32798  which solves the problem at the much lower level and is probably more elegant.

Closing. Fixed in #33303.


total height not adding up to 1.0

Hi,
I might be using this package wrong, but I thought the default handling used probabilities directly as the heights in the constructed logoplots.
However, when using dataframes that are converted from torch.tensors using softmax (which I treat as probabilities), I get logoplots, where the total heights do not add up to 1, even though the input sums up to 1.0000
minimal example:
import logomaker
import matplotlib.pyplot as plt
import torch
import pandas as pd
rand = torch.randn(20,64)
array = torch.nn.functional.softmax(rand, dim=1)
array_sums = torch.sum(array, dim=1)
print("sums", array_sums)
aminoacids = "ACDEFGHIKLMNPQRSTVWY"
amino_acids = list(aminoacids)
df = pd.DataFrame(array.T, columns=amino_acids, dtype=float)
fig, ax = plt.subplots(1,1,figsize=[4,2])
logo = logomaker.Logo(df, ax=ax)
Output:
sums tensor([1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000,
1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000, 1.0000,
1.0000, 1.0000])

Expected output:
Something like figure 1C in (https://doi.org/10.1093/bioinformatics/btz921)

Adding:
df = logomaker.transform_matrix(df, normalize_values=True)
after creating the dataframe solves this, but I'm not sure why it is needed.


Fix README.md to use clone vs checkout.

The setup instructions should refer to clone rather than checkout.

@mcacek Good spot! Cheers.


New month new s*ck

Why not f*ck the RDP this month as well?

termsrv.dll

+1
Just rebuilt my PC and downloaded all available updates before disabling future updates. This puts me on 10.0.19041.789 as well.
Anyone with a working .ini yet?

termsrv.zip

Settings for 10.0.19041.789
[10.0.19041.789]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=B59D9
LocalOnlyCode.x86=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=3BC45
SingleUserCode.x86=nop
DefPolicyPatch.x86=1
DefPolicyOffset.x86=3E7C9
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
SLInitHook.x86=1
SLInitOffset.x86=67BF8
SLInitFunc.x86=New_CSLQuery_Initialize

LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=88F41
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=0CA4C
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=18A15
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1D5BC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.19041.789-SLInit]
bInitialized.x86=D0954
bServerSku.x86=D0958
lMaxUserSessions.x86=D095C
bAppServerAllowed.x86=D0964
bRemoteConnAllowed.x86=D096C
bMultimonAllowed.x86=D0970
ulMaxDebugSessions.x86=D0974
bFUSEnabled.x86=D0978

bInitialized.x64=106028
bServerSku.x64=10602C
lMaxUserSessions.x64=106030
bAppServerAllowed.x64=106038
bRemoteConnAllowed.x64=106040
bMultimonAllowed.x64=106044
ulMaxDebugSessions.x64=106048
bFUSEnabled.x64=10604C

Thank you that's works !

it's still working?

it's still working?

What do you mean under "still"?  In version 10.0.19041**.964** you need to autoupdate again ... This is the current latest public version of  Windows 10.

Applicable to https://github.com/stascorp/rdpwrap/issues/1317


switch options to using a structure instead of functions

lack of inline pointers to basic types makes things tricky.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
166

Relevant Lines:
166

💛  - Coveralls


Windows 10 as wifi device cannot connect to vtrust-flash network?

Windows 10 as a wifi device to be used during flashing cannot seem to find the hidden network vtrust-flash, I say hidden because although my raspberry pi shows wlan0 as <IP_ADDRESS>, i.e. the softAP is up, Windows 10 seems to refuse to see it.  Anyone else have this issue?  I have tried all 3 or 4 of the various Windows 10 methods to get it to connect to a hidden network, so far no joy.

It shouldn't be hidden. What is the output of smarthack-wifi.log in scripts folder?

Windows 10 works for me.

Closing due to inactivity and confirmation that Windows 10 works


Editing code appears to break demo example of tutorial

Problem Description
I have twice now followed the tutorial and succeeded in creating the my-extension example. Loading it into a page and editing the example fields has been fine. However, as soon as I change anything (even a character within a string) it appears to break and I lose the new fields and the module only asks for 'background' and 'Admin Label' in the content area. Even reverting the changes back to the original does not fix it.
This has happened to me twice now (completely separate installations of WP).
Please advise.

QA Checklist
Reporter

[ ] Helpful title used

Helpful title format: Scope(s) :: One Sentence To Describe The Issue
Example: VB :: Floating Toolbar :: Jumps To Top Of Page

[ ] Detailed description

Description should usually be 150+ characters.

[ ] Steps to reproduce included
[ ] Support Ticket URL included
[ ] Image and/or gif

Developer

[ ] Steps to reproduce proven solved
[ ] Test included and coverage acceptable and all Tests passing?
[ ] PR description has layman's description of problem and solution and "Areas Affected" listed/explained?
[ ] PR branch includes latest commits from master branch (at the time of checking)?
[ ] Estimated points on issue
[ ] Proper code documentation and conventions?
[ ] Proper RTL appearance
[ ] i18n used if applicable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?

Peer Review

[ ] PR branch includes latest commits from master branch (at the time of checking)?
[ ] Steps to reproduce proven solved
[ ] Affected areas are tested and ok
[ ] Proper code documentation and conventions
[ ] Proper RTL appearance
[ ] i18n used if applicable
[ ] Test(s) included and coverage acceptable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?

Quality Assurance

[ ] All tests passed on CircleCI.
[ ] Steps to reproduce passed, the fix works.
[ ] No errors in console or output
[ ] Affected areas are tested and ok
[ ] The fix does not change a customer's website in any surprising or unintended way

[ ] If Divi's design is adjusted, settings are migrated gracefully and invisibly

Design Review

[ ] UI is to spec
[ ] UX is to spec
[ ] Design is to spec
[ ] No surprising visual changes to a customer's website will be experienced after updating

[ ] Any/all visual changes are migrated gracefully

Dev Review

[ ] Test(s) included and coverage acceptable
[ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
[ ] Database saved/updated? Data sanitized and validated?
[ ] Variable output properly escaped and validated?
[ ] i18n used if applicable
[ ] Implementation acceptable, DRY, Scaleable, future safe
[ ] Best practices used, cleverness and grokage, ES6 use, etc.

So when I change 'Input your desired heading here.' to 'Input your desired url here.'
The module no longer displays the new input fields when editing the 'Simple Header' module.

Update: It is working ok in the Visual Builder but not in the Page Builder.

I am facing the same issue. Is there any solution for this?

In order for changes to show in the Classic Builder you must clear your browser's local storage. Let me know if that solves it for you.

Tried using 'for(var prop in localStorage)localStorage.removeItem(prop)' and 'window.localStorage.clear()' in console but that didn't help. Also cleared cache from chrome developer tools under application->clear storage.
Tried 3 different operating systems Mac, windows 10, windows 7.. all having same issue.
Let me know how I can help you debug the issue.

Hi lots0logs,
Clearing Chrome's cache did no good.
It seems to work fine in Visual Builder (which is great). I do have to exit and then reenter the VB but I guess that is expected so as to reload the changes I have made.
I can live with that. Shame (and curious) that it won't work in the Classic builder though.

I have still this problem, and tried clearing cache but did not work. Any ideas what I should do ?

Is it not working for you in the Visual Builder front end?


add delimiter prop

allows using a custom key to create string, e.g. " " (space).
a typical usage scenario of chips is tagging or entering path fragments.

Coverage remained the same at 57.361% when pulling 4347459a8104cbf0d4f52533105586c78ab5c03c on chip-add-prop-custom-delim into 22b6bcbdbb2436031971dd990bfea8b3f77ffbd7 on master.

Pretty good idea. My thoughts

How about using the character code directly? For empty space ( ) that would be 32. It would make our code easier and how would a user chose backspace as delimiter?

Would both, the default enter and the custom delimiter, work at the same time. Or does the user expect to only have the custom delimiter when it is given?


CliRunner.invoke() doesn't capture stderr

Expected Behaviour
Given a CLI program that outputs to stderr, CliRunner(mix_stderr=False).invoke() should capture said output.
Here is a minimal example:
import sys
import click
from click.testing import CliRunner

@click.command()
def hello():
    print("Hello world")
    print("Hello error", file=sys.stderr)

if __name__ == "__main__":
    runner = CliRunner(mix_stderr=False)
    res = runner.invoke(hello)
    print(f"Stdout: {res.stdout.strip()}")
    print(f"Stderr: {res.stderr.strip()}")

Expected output:
Stdout: Hello world
Stderr: Hello error

Actual Behaviour
res.stderr is an empty string and the output actually reads:
Stdout: Hello world
Stderr:

Environment

Python version: 3.7.4
Click version: 7.1.2

Use click.echo(message, err=True) to echo to stderr. click.echo exists because print does not behave consistently in many cases. In this case, if you do sys.stderr.flush() after printing, you'll get the expected output. click.echo() knows to do this automatically.

Oh ok, thanks for the info (and very quick reply!)


Improvements on the Background Feature creation process

When a player creates a background feature, that feature item is both added to the created Actor, and saved on the Items Directory (for if the DM wants to save it on a compendium for future use, for example), but that flexibility might be more than many games need, and DMs might want to prevent their players from creating background features. Therefore the next changes are planned:

Add a setting toggle to allow/disable the creation of Background Features from the tool.
Add a setting toggle for deciding if created Background Features should be saved on the Items Directory or just be transient to the Hero Creation.

Deprecating this as I have considered a better approach to strip the custom feature creation from the tool and let users do that externally only.


[Bug]: Untile/Retile does not work in three column layout

Before you make the issue, confirm that

[X] You are running the master build from GitHub actions
[X] You have read the FAQ and the usage instructions
[X] You have searched pull requests and issues and have found none similar to your issue
[X] This problem comes from a failure in the tiling system and not a missing feature

Describe the bug
In version 0.5.0, untiling/retiling worked fine. Now (version 0.5.2), windows don't get retiled, at least in the three column layout.
To reproduce
Press the shortcut for untiling/retiling twice. Window gets untiled but not retiled.
Expected behavior
Windows are retiled again.
Relevant log output
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Config set - {"debug":true,"useProcessWhitelist":false,"filterProcessName":["krunner","yakuake","kded","polkit","plasmashell"],"filterClientCaption":[""],"tilePopups":false,"borders":3,"btreeInsertionPoint":0,"keepTiledBelow":true,"defaultEngine":2,"maximizeSingle":false,"resizeAmount":0.01,"timerDelay":10,"unfullscreen":false}
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (0, , 1)
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (0, , 1)
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (1, , 1)
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (1, , 1)
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (2, , 1)
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (2, , 1)
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling ksplashqml
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling ksplashqml
Jul 21 09:10:30  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling ksplashqml
Jul 21 09:10:31  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:31  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:31  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:31  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:31  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:31  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:32  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:32  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:32  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:32  kwin_wayland[608]: qml: Polonium DBG: ksplashqml was removed
Jul 21 09:10:32  kwin_wayland[608]: qml: Polonium DBG: ksplashqml was removed
Jul 21 09:10:32  kwin_wayland[608]: qml: Polonium DBG: ksplashqml was removed
Jul 21 09:10:33  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:33  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:33  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Adding and tiling org.kde.konsole
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Adding org.kde.konsole to desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:38  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:48  kwin_wayland[608]: qml: Polonium DBG: Adding and not tiling org.kde.plasmashell
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: org.kde.plasmashell was removed
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Adding and tiling emacs
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Adding emacs to desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:10:50  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Untiling client emacs
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Removing emacs from desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Retiling client emacs
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing emacs in QRectF(1080, 435, 1920, 1200) with direction (below, right)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium ERR: Container not registered
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (0, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (1, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Building layout for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)
Jul 21 09:11:01  kwin_wayland[608]: qml: Polonium DBG: Placing clients for desktop (2, df4c8a4b-d4de-4d3c-9e4d-220e25ba0c2a, 1)

Screenshots and videos
No response
Additional context
No response

Can you enable debug mode and post a full log output?

Sure, I updated the comment above.

Problem turned out to be threecolumn specific, but I added a sneaky bandaid solution that should work well enough in case other engines have the problem as well. Try latest master build and see if it works for you.

Yeah, it works. Thanks for fixing it that fast!


[Bug]: SVG conversion back and forth.

What happened?
@g-elwell had mentioned on #33 during testing of that PR about conversion of SVGs going from to a string and then back to a component. We should investigate this and look into impacts and changes that are required. Gareth has gave reference to this as config we're likely to require.
Which environments are you experiencing the issue on?
CI (CircleCI, Travis, etc), CLI (macOS, Windows, etc)
Relevant log output
No response

Thanks for the expansive report on this @g-elwell. I definitely think it's worth making the change. It seems to me that we need to get this change in sooner rather than later as this is a breaking change that we already know about and will need to make, so best do it now. Can you open up a PR with your branch so I can review and assess from there? I'd also take a look at the Integration/Example Site that I added as part of #41 and add the example there also, just so we can keep up with integration testing.

@ampersarnie I've created #45 and checked out the example site. The SVG import in the example site uses the new syntax we're proposing so doesn't need to be updated. Is the example site just for reference or is there a way to build and run tests on it?

@g-elwell The example site is there both for reference and to ensure we've got some basic integration testing. It runs in CI and does a build with the main commands, so if the build fails we know. It'll be getting expanded into something fuller as soon as possible really.

@ampersarnie Got it thanks and happy to help with any of that if needed. The SVG import in the example site will produce a runtime error but it will be fixed if/when #45 gets merged. Otherwise this line would need to be changed to:
import { ReactComponent as LogoSVG } from '../static/logo.svg';


Important announcement for building for HoloLens or HMDs

If you're building for the HoloLens use the Vanilla Unity 2017.1.x Release  and the 10.0.15063.0 SDK
If you're building for the WMR HMDs use the Unity 2017.2.0f3 MRTP and the latest 10.0.16299.0 SDK

Is there an expected time frame / target release in which these two versions will merge into one?

They already are.

Hmm, then I'm confused. The initial comment says to stay w 2017.1x if building for HoloLens and 2017.2 MRTP for WMR HMDs. Is it that the MRTK code base is now the same, and only the Unity version (and Windows SDK) that needs to vary?

That is correct.

Are you planning on making everything work on 2017.2?

It's not us, it's unity we're waiting on.

Has this been fixed by Unity as of now, or do we still need to use 2017.1.x for HoloLens development?

long time ago.


cmd/grit: Additions to various commands for quality of life

Closes #28
Closes #9
This pull request adds the following changes:

grit add [-a|--alias] ALIAS ...: alias a node on addition.
grit list|ls all: list all nodes
grit move|mv NODE ORIGIN TARGET: Move a NODE from ORIGIN to TARGET

These seem like very useful fixes. @climech do you think it's something that can be merged soon?

Agreed, this would be very useful, especially 👍 for moving nodes


Update README to install with Yarn

Just update documentation to install with npm or Yarn. :)

Nice! Thanks.


[Splash Screen] Instantly open game in the background while intro video plays in the foreground

Extension name
Splash Screen
Feature Description
As opposed to waiting until the intro video ends to start opening the game while there's a image, it would be better to start the process as soon as I start the game, having an intro or not, and in case of an intro, when it ends it then could switch to the image, as it already does.
That would be very useful as for example myself: I have a 20s long video everytime I open a game and it can be frustrating having to wait the video to end and then even more time for the game to open.
I could get rid of the video to fix the time issue but if it would be possible to implement this feature it would be very optimal, and my videos are too cool to be removed :(
Screenshots
No response

I posted an help request on the Playnite forum searching for someone who knows coding in order to create a quick mod of Splash Screen. I hope it will work.

Bump, Sorry, but is this planned/already added?

Bump,
Would love this.

you can skip splash video/image.


[BUG] Causing crash in dev env without Create

Important Information
Minecraft Version: 1.20.1
Mod Loader System: Fabric
DramaticDoors Version: 1.20.1-3.1.5
Describe the bug
https://github.com/Kitteh6660/DramaticDoors/blob/master/common/src/main/java/com/fizzware/dramaticdoors/compat/Compats.java#L313-L315
It makes the mod depends on this mod have to depend on the extra mods.

I will look to get this fixed!

It will be fixed in mod version 3.2.0 for 1.20.1. Can it be replicated with 3.2.0?


[BUG] - Demo site doesn't have 404 enabled

Describe the bug
The demo site doesn't have custom 404 enabled, e.g., https://1bl4z3r.github.io/hermit-V2/en/about-hugo/s
I don't know why, as I found the theme by default creates a 404.html file.

Hi @xuhdev,
I have no idea how to configure 404 redirect on GitHub Pages and documentation for the same is few and far between.
Most I can say is that 404.html should be automatically fetched by Pages and returned when an invalid link is thrown. My own site (which is hosted on GitLab) does this.

Sorry for not being clear. I was trying to say that 404.html is missing on the demo site. See https://github.com/1bl4z3r/hermit-V2/tree/gh-pages, there's no 404.html.

I got you. There is no 404.html sitewide, but there is a 404 page in each language section.
en/404.html
fr/404.html
it/404.html
I have to check if we can put global 404.html or not. Most probably we cannot

Hi @xuhdev
As it turns out, you cannot add a global 404.html in multilingual page, when hosted by GitHub Pages. There is an open issue https://github.com/gohugoio/hugo/issues/5161
Relevant Hugo forum link for the same : https://discourse.gohugo.io/t/global-404-page-for-a-multilingual-site/20979
Applied workaround for now, as when it will be officially supported is not yet known. If you are following the same. Add this to hugo build command. You can use any 404.html from any multilingual directory.
hugo --minify --noBuildLock --ignoreCache --gc --verbose && cp public/en/404.html public/404.html


Update Tomcat to 9.0.96

Overview
This change mitigates a CVE found in Tomcat 9.0.87 by updating to 9.0.96.
Reference links

NVD - CVE-2024-34750

A developer build has not yet been created for this branch. Click here to go ahead and create the build...

CI Build Link:
https://sou-jenkins2.swinfra.net/job/CAFapi/job/CAFapi~opensuse-tomcat-jre11-image~fix ⁄ tomcat-9.0.96~CI


Bad code in example

Not only is the syntax not correct in one of the examples, but it's also using parameters from two separate parameter sets, which isn't possible to do.
Here's the code from the example you are providing:
New-ADServiceAccount ITFarm1 -RestrictToOutboundAuthenticationOnly - PrincipalsAllowedToRetrieveManagedPassword ITFarmHosts$
You'll notice you have a space after the dash before the PrincipalsAllowedToRetrieveManagedPassword parameter name.  You can't have a space between the dash and the parameter name.
And in regards to the multiple parameter sets, you're using both RestrictToOutboundAuthenticationOnly AND PrincipalsAllowedToRetrieveManagedPassword.  Please see this reference on the parameter sets and which parameters are allowed within each set.
https://docs.microsoft.com/en-us/powershell/module/activedirectory/new-adserviceaccount?view=winserver2012-ps

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

ID: a31db532-baae-df07-4ab6-d9714db8b33d
Version Independent ID: f6f28a52-6a57-7507-2912-7d0770f2bcaa
Content: Getting Started with Group Managed Service Accounts
Content Source: WindowsServerDocs/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts.md
Product: windows-server
Technology: security-gmsa
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


⚠ Site ANTS has degraded performance

In 08cb1b3, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 17774 ms

Resolved: Site ANTS performance has improved in 1617f5a.