way to instantly trigger (bypassing delay) for some sensors

When the alarm is armed I'd like our backdoor sensor to instantly trigger the alarm but when the front door opens I 'd like to have a pending time to enter the code..
any way to accomplish this ?
thanks in advance and thaks A LOT for all the effort you've put in :)

You can do this in HA with automations, this isn't something the application would be able to handle.  The app isn't aware of your sensors, it just reacts to the MQTT messages sent from HA.  So probably in this case the alarm would be sent to away mode, but you would send an alarm triggered and sound your sirens when someone trips the sensor in your backyard.

Will try to get something working ;) thanks for the superfast reply !

Just tried, but when I send mqtt messages for "pending" and "triggered" the state in ha doesnt get updated.
Is this because the component doesnt have those seperate states ?

You want to call the service, not call the MQTT message.  You are in HA, so just talk directly with the service, MQTT is for communicating to components outside of HA.

Check under the developer tools, first icon, and enter the service alarm_control_panel.alarm_trigger, be aware that if you set a code, you also need this passed into the entity to trigger it.

I can directly call the app panel to trigger through mqtt, but not the HA component..
when I call the trigger service, it starts with the pending time anyway..

Calling the app with MQTT will not be the solution.  That just round trips back to HA.

Basically you want two pending times, one for home set to zero, and another for away set to 30 seconds.  Pending mode starts when the HA alarm sets to trigger, so you may have to do a nasty work around.  If someone trips the sensor for the back door, set the alarm mode to home, then call trigger, with the alarm setup for home mode to be 0 pending.  Not ideal, but off the top of my head, that is one solution.

https://www.home-assistant.io/components/manual_mqtt/
Take a look at the  pending_time, delay_time, and trigger_time.  You want a short pending and delay for your home mode.  A long trigger time means how long the siren goes off, how long the alarm is in trigger mode.

yeah, figured the same .. seems like an oversight that the HA component doesn't have a straight trigger service call.. will put in a feauture request ;)

issue created.
--> https://github.com/home-assistant/home-assistant/issues/23526

They could use a panic mode, which this feature would allow by going straight to triggered mode.

Basically you want two pending times, one for home set to zero, and another for away set to 30 seconds. Pending mode starts when the HA alarm sets to trigger, so you may have to do a nasty work around. If someone trips the sensor for the back door, set the alarm mode to home, then call trigger, with the alarm setup for home mode to be 0 pending. Not ideal, but off the top of my head, that is one solution.

Won't really work since we use both when one of us is at work while the rest is still asleep .. (wife and I both work shifts..) so we need pending times for both home and away mode

There is a night mode.  But home mode should have no pending time, you want an alarm to go off Immediately when you are home and a door is opened .  The away mode can have a delay time so you have time to disarm it.
What I suggest is you have home mode with no pending or delay time and away mode to have pending away time of 30 seconds.  If you set the alarm to away mode and enter through the front door, you have 30 seconds to enter the code.
However if the back door is ever opened while any alarm mode is set you would have an automation that sets the alarm to home mode first, then trigger mode.  This removes the delay and pending time and the alarm is sent to triggered mode automatically.
My home and away modes are already set this way, I’m just suggesting a different way to setup your automation to achieve the desired results.  Your back door forces alarm home mode first then triggers it.

There is a night mode. But home mode should have no pending time, you want an alarm to go off Immediately when you are home and a door is opened . The away mode can have a delay time so you have time to disarm it.
What I suggest is you have home mode with no pending or delay time and away mode to have pending away time of 30 seconds. If you set the alarm to away mode and enter through the front door, you have 30 seconds to enter the code.
However if the back door is ever opened while any alarm mode is set you would have an automation that sets the alarm to home mode first, then trigger mode. This removes the delay and pending time and the alarm is sent to triggered mode automatically.
My home and away modes are already set this way, I’m just suggesting a different way to setup your automation to achieve the desired results. Your back door forces alarm home mode first then triggers it.

While this is a very good suggestion.. the android app only works for home and away modes, so I should create the night mode as no delay - instant alarm and use it as inbetween mode before the trigger ?

I would either setup the night mode just as an in between mode for your back door automation to trigger the alarm instantly order your home mode to be no pending or delay time and use it.  My home mode is already zero delay or pending time because if I’m home I want the alarm to be instant.   However if you don’t want your home mode that way, hack the night mode just to use for your automation.  The app will ignore the night mode being set but will react to the alarm triggered mode, which is what is sent after the pending time has passed if you don’t enter the code to disarm.

It works ! thanks for all the help ;)


Docker agent signals not processed for running cleanup from Agent Pool

Hi guys,
I am trying to run some Docker build agents in Azure DevOps.
Everything runs fine following the instructions from :  https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops
The only problem I have is that the agent is not getting removed from the Agent Pool. If I redeploy them, they remained in the pool, so I need to remove them manually. If I enter in the shell and I kill any process(run.sh or AgentListener) then the cleaning is working. But when the Kubernetes terminate/deletes the container it seems that  the signals (INT, TERM, EXIT) are not received in this case, the cleanup procedure is not called.
trap 'cleanup; exit 0' EXIT
trap 'cleanup; exit 130' INT
trap 'cleanup; exit 143' TERM

# To be aware of TERM and INT signals call run.sh
# Running it with the --once flag at the end will shut down the agent after the build is executed
./run.sh "$@"

Is this the problem with the process with PID 1 ?
Thanks.

Hi again,
I have seen that the instructions were updated yesterday.
&

wait $!

Adding this, the signals are now received.


Add delay option

Add delay option in AnomalyzerConf. This way if we asked for to compare our data to n seasons ago worth of data and we don't have enough, evaluation the anomalous probability will return 0.0. Is reverse-compatible and this option defaults to false.

:shipit:!


Remove Clinical Trials Information from KG2

Per the discussion in the AHM today, we need to figure out what (if any) clinical trials information is currently in KG2.

Based on
match (n:`biolink:RetrievalSource`) where not n.id =~ 'umls_.*' and not n.id =~ 'OBO:.*' return n.id, n.name order by n.id;
RepoDB is not in KG2.10.1pre.
Further,
match (n)-[e]->(m) where e.predicate="biolink:applied_to_treat" and e.primary_knowledge_source="infores:chembl" return count(e)

returned no results, suggesting that the clinical trials information from chembl has been removed.
Closing this issue.


refactor(rust): tray menu handling to add/remove items and keep all the items' state in sync

System Tray Menu limitations
When initializing the tray menu, you do it through the SystemTray struct, which accepts a SystemTrayMenu instance. To populate the initial state of the tray system, you can add a list of CustomMenuItem instances with their own initial state (title, enabled/disabled, icon). With all those objects in place, a SystemTray is initialized.
When you want to modify the SystemTrayMenu at runtime, you have a limited access to it through the SystemTrayMenuHandle, which only lets you retrieve items by ID (SystemTrayMenuItemHandle) and modify their properties (title, icon, enabled/disabled).
There is no way to add new items to it, the only way I could find is to rebuild the whole menu. This has some challenges:

When recreating the CustomMenuItem items, you have to keep their previous properties (in our current design, we enable/disable the enroll and reset buttons on some situations).
There is no direct conversion between CustomMenuItem and SystemTrayMenuItemHandle.

Proposed solution
This PR adds an abstraction layer (TrayMenu) to easily manage the sections of the tray menu and keep the underlying CustomMenuItem in sync with its paired SystemTrayMenuItemHandle, so we can rebuild the menu without losing data.

Rewritten at https://github.com/build-trust/ockam/pull/5402


pull request for e2e test at 01/06/2017 07:26:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


refine LGBMClassifier metric

don't need to specify 'binary_' or 'multi_' before 'error' and 'logloss' for LGBMClassifier

@wxchan,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


is there a way to tell it to scan also phtml files?

is there a way to tell it to scan also phtml files?
I see from the code https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/1.11/Symfony/CS/Finder/DefaultFinder.php#L33 i may need to create a custom finder, but is there a way to pass it via configuration?

i got this nvm


Failed for paths with ( ) symbols

For proj files with special characters task fails.

This is due to an interesting property of the ITaskItem in MSBuild. Details on why this is occurring can be found in source for TaskItem.ItemSpec and TaskItem.ToString.
Thanks for reporting this issue.

@mikasoukhov I will include this fix the next time I publish a package. Are you blocked by this issue or can it wait?


Make OpenAPI.NET library trim-compatible

This PR removes the use of reflection in GetDisplayName for enums and adds [DynamicallyAccessMembers] attributes to CloneFromCopyConstructor.
Prior to this change, using the Microsoft.OpenApi package in an application with trimming enabled would present the following warnings:
    /_/src/Microsoft.OpenApi/Extensions/EnumExtensions.cs(27): Trim analysis warning IL2075: Microsoft.OpenApi.Extensions.EnumExtensions.GetAttributeOfType<T>(Enum): 'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors', 'DynamicallyAccessedMemberTypes.PublicMethods', 'DynamicallyAccessedMemberTypes.PublicFields', 'DynamicallyAccessedMemberTypes.PublicNestedTypes', 'DynamicallyAccessedMemberTypes.PublicProperties', 'DynamicallyAccessedMemberTypes.PublicEvents' in call to 'System.Type.GetMember(String)'. The return value of method 'System.Object.GetType()' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.
    /_/src/Microsoft.OpenApi/Any/OpenApiAnyCloneHelper.cs(23): Trim analysis warning IL2075: Microsoft.OpenApi.Any.OpenApiAnyCloneHelper.CloneFromCopyConstructor(IOpenApiAny): 'this' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors' in call to 'System.Type.GetConstructors()'. The return value of method 'System.Object.GetType()' does not have matching annotations. The source value must declare at least the same requirements as those declared on the target location it is assigned to.

Closes https://github.com/microsoft/OpenAPI.NET/issues/1715
Closes https://github.com/microsoft/OpenAPI.NET/issues/1114

Thanks for the reviews @darrelmiller and @MaggieKimani1 -- I spotted a few more issues after adding a TrimmingTest project (mostly related to ValidationRuleset) so we'll need to hold off on merging this a bit longer.

@baywet @eerhardt I think this is good for one last review...

@maggieKimani1 for final review and merge

LGTM!


142

QUESTION 142
Hotspot Question
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.


Compatibility issue between infinispan-spring4-embedded and spring-session

Hello,
I'm getting an exception when I try to use a web session backed on a infinispan datagrid from a servlet controller. The exception shows itself as follows:
java.lang.NoSuchMethodError: org.springframework.session.MapSession.setCreationTime(J)V
	at org.infinispan.spring.session.AbstractInfinispanSessionRepository.createSession(AbstractInfinispanSessionRepository.java:61) ~[infinispan-spring4-embedded-9.4.0.Final.jar:9.4.0.Final]
	at org.infinispan.spring.session.AbstractInfinispanSessionRepository.createSession(AbstractInfinispanSessionRepository.java:30) ~[infinispan-spring4-embedded-9.4.0.Final.jar:9.4.0.Final]
	at org.springframework.session.web.http.SessionRepositoryFilter$SessionRepositoryRequestWrapper.getSession(SessionRepositoryFilter.java:332) ~[spring-session-core-2.1.1.RELEASE.jar:2.1.1.RELEASE]

Here there is a simple project with a test that manifest this error:
https://github.com/fragonib/infinispan-spring-boot-starter-issue
Could  infinispan-spring-boot-starter:2.1.0.Final have a compatibility issue during the interation of its transitive dependencies infinispan-spring4-embedded-9.4.0.Final.jar:9.4.0.Final  and spring-session:2.1?

@fragonib Hi, yes, indeed, there is an incompatibility. infinispan-spring4-embedded-9.4.0.Final brings another spring session version. I have to fix this issue, and specially, we need to use infinispan 10 (coming next year) to avoid any incompatibility.
Thanks for opening the issue, I will handle it

https://issues.jboss.org/browse/ISPN-9625

@karesti  you mean related with https://issues.jboss.org/browse/ISPN-7035 ?
@fragonib The fix is on is way: https://github.com/infinispan/infinispan/pull/6496
Waiting for next version to integrate in jhipster project: https://github.com/jhipster/generator-jhipster/issues/8683

yes, that's right, thanks for the input @DanielFran

@DanielFran I realised now I copied the wrong link, the issue I was referring to was ISPN-9789

I released 2.1.1.Final, soon it will be in maven central. Let me know if it works!

I will let it open, this issue, til I get your feedback @fragonib and @DanielFran

@karesti I updated project but still waiting for new version to be available in Maven Center (https://travis-ci.org/jhipster/jhipster/jobs/465999815)
Will let you know.

Spring session with the last version is integrated now I’m closing this


Create GitHub Actions for sz-sdk-java

Create GitHub actions that do:

[ ] Unit testing: (JUnit)
[ ] Code coverage: (TBD -- OpenClover or JaCoCo)
[ ] Code format checking: (TBD -- maybe uncrustify or Artistic Style)

UPDATE: 5/14/24

[ ] Unit testing: JUnit
[ ] Code coverage: JaCoCo
[ ] Code format/syntax checking: Checkstyle
[ ] Security checking/Static Analysis: maven dependency review spotbugs / find security bugs bearer

This is working now with latest merge


Evaluation of params in destination section

Hi everyone,
Short bug description
I'd like to report what I think is a bug with TPVs parsing of params. It seems that the f-string evaluation from TPV is working properly in the tools section, however not working in the destinations section.
Debugging information:

Galaxy 24.1.1 on a Ubuntu 22.04.4 server
The venv Galaxy is running on is using Python 3.12.3 and total_perspective_vortex is installed in version 2.4.0.

Detailed description
I was setting up a self-hosted Galaxy instance using Ansible, following this tutorial. At the step job destinations I had some issues with the walltime parameter. The tutorial suggests (in a shortened way) the following setup for the tpv_rules_local.yml file:
tools:
  default:
    ...
    rules:
      - id: resource_params_defined
        if: |
          param_dict = job.get_param_values(app)
          param_dict.get('__job_resource', {}).get('__job_resource__select') == 'yes'
        cores: int(job.get_param_values(app)['__job_resource']['cores'])
        params:
           walltime: "{int(job.get_param_values(app)['__job_resource']['time'])}"

destinations:
  local_env:
    ...
    params:
      native_specification: --nodes=1 --ntasks=1 --cpus-per-task={cores} --time={params['walltime']}:00:00

However, this only works in a limited way (at least for me). In the tools section the usage "{int(job.get_param_values(app)['__job_resource']['time'])}" works fine and the walltime is properly displayed in the job info of Galaxy. See red box in the image:

However, in the destination section the native_specification: --nodes=1 --ntasks=1 --cpus-per-task={cores} --time={params['walltime']}:00:00 will not correctly parse the walltime.

The errors suggest to use self.params['walltime']. Which also only works half-way.
If I use the above-mentioned self.params['walltime'], the resulting string will be the literal "{int(job.get_param_values(app)['__job_resource']['time'])}", which are not correctly evaluated in this case. This will lead to an error with the job submission, because the walltime will look like this: --time="{int(job.get_param_values(app)['__job_resource']['time'])}":00:00.

Workaround
I have found a workaround for this issue which I'd like to share, but I think the above-mentioned way is the way the developers from TPV intended the usage, as it is also in the docs.
Code snippet for the native specification:
native_specification: --partition=galaxy2 --nodes=1 --ntasks=1 --mem={int(mem * 1000)} --cpus-per-task={cores} --time={self.params.get('walltime') if isinstance(self.params.get('walltime'), int) else job.get_param_values(app).get('__job_resource').get('walltime')}:00:00

This code will get the self.params.get('walltime') for the case that job resources are not defined and else will get the resources from the __job_resources. job.get_param_values(app).get('__job_resource').get('walltime') Needs to be called directly here and it will be evaluated correctly:
I have attached my relevant configurations for anyone who faces the same issues.
tpv_rules_local.yml.txt
job_resource_params_conf.xml.j2.txt
job_conf.yml.txt
Summary
If this is not a bug and working as intended, the issue can be closed, I just wanted to document this for anyone facing the same issues as me. If this is indeed a bug, I think it would be nice to either

Fix the issue within TPV itself.
Update the documentation in the Galaxy Ansible setup.
Update the documentation of TPV. I think TPV by example would be a fitting section.

Hope this helps. Keep up the good work! Cheers!

@lmfaber There is indeed a problem with the example. Please take a look at this conversation for a solution: https://github.com/galaxyproject/total-perspective-vortex/issues/120
We are hoping to add support for computed context variables, but till that comes, the best option is to use the very last example from that code (using env vars)

Thanks for the answer and linking the other post. I saw this post before writing my own, but somehow couldn't make the connection in my head.
I will close the issue, since it's so similar to the other one.


[FEAT]Can the links in the flash cards be previewed?

Is your feature request related to a problem? Please describe.
Now my problem is that I can't preview the md doc when my card links to another doc or itself block.
Describe the solution you'd like
I hope I can preview the doc when my flash-card content links to another.
Additional context

Hi @Ocean-Tang
Can "transclusion" help (including a ! before the link)?
Here is some info...
https://github.com/st3v3nmw/obsidian-spaced-repetition/issues/810#issuecomment-1914459824
It works for an internal link within the vault to a .md file.


Mixnet graph freezing issue

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): 1.14.0
Python version: 3.7.4
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
I have been trying to covert the Mixnet model to Core ML using the tfcoreml converter. I froze the graph, then tried converting it, and that's when I get thrown with the following error:
1199 ops in the final graph.

Loading the TF graph...
Graph Loaded.
Now finding ops in the TF graph that can be dropped for inference
Collecting all the 'Const' ops from the graph, by running it....
---------------------------------------------------------------------------
OutOfRangeError                           Traceback (most recent call last)
~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in _do_call(self, fn, *args)
   1355     try:
-> 1356       return fn(*args)
   1357     except errors.OpError as e:

~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in _run_fn(feed_dict, fetch_list, target_list, options, run_metadata)
   1340       return self._call_tf_sessionrun(
-> 1341           options, feed_dict, fetch_list, target_list, run_metadata)
   1342

~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in _call_tf_sessionrun(self, options, feed_dict, fetch_list, target_list, run_metadata)
   1428         self._session, options, feed_dict, fetch_list, target_list,
-> 1429         run_metadata)
   1430

OutOfRangeError: Node 'mixnet-s/mixnet_model/stem/batch_normalization/FusedBatchNormV3' (type: 'Add', num of outputs: 1) does not have output 5

During handling of the above exception, another exception occurred:

OutOfRangeError                           Traceback (most recent call last)
<ipython-input-12-6b7b8d71599d> in <module>
     48                      mlmodel_path=ml_model,
     49                      output_feature_names=['logits'],
---> 50                      input_name_shape_dict={})

~/anaconda3/envs/tf/lib/python3.7/site-packages/tfcoreml/_tf_coreml_converter.py in convert(tf_model_path, mlmodel_path, output_feature_names, input_name_shape_dict, image_input_names, is_bgr, red_bias, green_bias, blue_bias, gray_bias, image_scale, class_labels, predicted_feature_name, predicted_probabilities_output, add_custom_layers, custom_conversion_functions, use_coreml_3)
    619       predicted_probabilities_output=predicted_probabilities_output,
    620       add_custom_layers=add_custom_layers,
--> 621       custom_conversion_functions=custom_conversion_functions)

~/anaconda3/envs/tf/lib/python3.7/site-packages/tfcoreml/_tf_coreml_converter.py in _convert_pb_to_mlmodel(tf_model_path, mlmodel_path, output_feature_names, input_name_shape_dict, image_input_names, is_bgr, red_bias, green_bias, blue_bias, gray_bias, image_scale, class_labels, predicted_feature_name, predicted_probabilities_output, add_custom_layers, custom_conversion_functions)
    260     else:
    261       const_tensor_names = []
--> 262     tensors_evaluated = sess.run(tensors, feed_dict=input_feed_dict)
    263     for i in range(len(tensor_names)):
    264       if tensor_names[i] not in SHAPE_DICT:

~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in run(self, fetches, feed_dict, options, run_metadata)
    948     try:
    949       result = self._run(None, fetches, feed_dict, options_ptr,
--> 950                          run_metadata_ptr)
    951       if run_metadata:
    952         proto_data = tf_session.TF_GetBuffer(run_metadata_ptr)

~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in _run(self, handle, fetches, feed_dict, options, run_metadata)
   1171     if final_fetches or final_targets or (handle and feed_dict_tensor):
   1172       results = self._do_run(handle, final_targets, final_fetches,
-> 1173                              feed_dict_tensor, options, run_metadata)
   1174     else:
   1175       results = []

~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in _do_run(self, handle, target_list, fetch_list, feed_dict, options, run_metadata)
   1348     if handle is None:
   1349       return self._do_call(_run_fn, feeds, fetches, targets, options,
-> 1350                            run_metadata)
   1351     else:
   1352       return self._do_call(_prun_fn, handle, feeds, fetches)

~/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/client/session.py in _do_call(self, fn, *args)
   1368           pass
   1369       message = error_interpolation.interpolate(message, self._graph)
-> 1370       raise type(e)(node_def, op, message)
   1371
   1372   def _extend_graph(self):

OutOfRangeError: Node 'mixnet-s/mixnet_model/stem/batch_normalization/FusedBatchNormV3' (type: 'Add', num of outputs: 1) does not have output 5

I presume this is an issue with the way I am freezing the graph. The checkpoint was taken from the official Mixnet implementation. I am relatively new to TF and am still learning. Please help me resolve this issue and let me know in case further information is needed. Suggestions for converting to Core ML are also welcome. Thanks in advance!
Code to reproduce the issue
You might have to install TF 1.14.0
import tensorflow as tf
import tfcoreml as tf_converter
from tensorflow.compat.v1 import graph_util

tf.logging.set_verbosity(tf.logging.ERROR)

# Download the checkpoint
model_name = 'mixnet-s'
!wget https://storage.googleapis.com/cloud-tpu-checkpoints/mixnet/{model_name}.tar.gz -O {model_name}.tar.gz
!tar -zxvf {model_name}.tar.gz
ckpt_dir = model_name

def _freeze_graph(model_folder):
    # Retrieve the checkpoint fullpath
    checkpoint = tf.train.get_checkpoint_state(model_folder)
    input_checkpoint = checkpoint.model_checkpoint_path

    # File fullname of the freezed graph
    absolute_model_folder = "/".join(input_checkpoint.split('/')[:-1])
    output_graph = absolute_model_folder + "/model.pb"

    # Before exporting the graph, get the output nodes
    output_node_names = "logits"

    # Clear devices to allow TF to control on which device it will load operations
    clear_devices = True

    # Import the meta graph and retrieve a Saver
    saver = tf.train.import_meta_graph(input_checkpoint + '.meta',
                                       clear_devices=clear_devices)

    # Retrieve the protobuf graph definition
    graph = tf.get_default_graph()
    input_graph_def = graph.as_graph_def()

    # Start a session and restore the graph weights
    with tf.Session() as sess:
        saver.restore(sess, input_checkpoint)

        # Use a built-in TF helper to export variables to constants
        output_graph_def = graph_util.convert_variables_to_constants(
            sess,
            input_graph_def,
            output_node_names.split(",")
        )

        # Serialize and dump the output graph to the filesystem
        with tf.gfile.GFile(output_graph, "wb") as f:
            f.write(output_graph_def.SerializeToString())
        print("%d ops in the final graph." % len(output_graph_def.node))

_freeze_graph(ckpt_dir)

ml_model = 'mixnet-s/mixnet_core.mlmodel'
frozen_model = 'mixnet-s/model.pb'

tf_converter.convert(tf_model_path=frozen_model,
                     mlmodel_path=ml_model,
                     output_feature_names=['logits'],
                     input_name_shape_dict={})

@dhananjaisharma10,
Thanks for reporting the issue, Can you provide a simple and standalone code to reproduce the issue?

@dhananjaisharma10,
Thanks for reporting the issue, Can you provide a simple and standalone code to reproduce the issue?

@dhananjaisharma10,
Thanks for reporting the issue, Can you provide a simple and standalone code to reproduce the issue?

I have updated the "code to reproduce". Please let me know if you have trouble running it.

Thank you for updating the code,Issue replicating for TF-1.14 and TF-1.15rc1, kindly find the gist of colab.Thanks!

Have you considered using freeze_graph function to convert your checkpoint model to frozen model.
You can try,
from tensorflow.python.tools import freeze_graph

https://github.com/tensorflow/tensorflow/blob/f718c5af3706d99d2acb70d27cb79231650e468b/tensorflow/python/tools/freeze_graph.py#L286

Have you considered using freeze_graph function to convert your checkpoint model to frozen model.
You can try,
from tensorflow.python.tools import freeze_graph

https://github.com/tensorflow/tensorflow/blob/f718c5af3706d99d2acb70d27cb79231650e468b/tensorflow/python/tools/freeze_graph.py#L286

Yes, I have been using that as well, but was facing some issues. I was able to convert the model to Core ML without using the BN layers. I am yet to try this with BN. Will update this soon.

Have you considered using freeze_graph function to convert your checkpoint model to frozen model.
You can try,
from tensorflow.python.tools import freeze_graph

https://github.com/tensorflow/tensorflow/blob/f718c5af3706d99d2acb70d27cb79231650e468b/tensorflow/python/tools/freeze_graph.py#L286

Hi!
I tried freezing the graph with as you suggested, but I am getting the following error:
WARNING:tensorflow:From freeze.py:247: The name tf.logging.set_verbosity is deprecated. Please use tf.compat.v1.logging.set_verbosity instead.

WARNING:tensorflow:From freeze.py:247: The name tf.logging.ERROR is deprecated. Please use tf.compat.v1.logging.ERROR instead.

2019-10-04 21:24:21.124841: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2019-10-04 21:24:21.147115: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-10-04 21:24:21.148346: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x5634b8da0430 executing computations on platform Host. Devices:
2019-10-04 21:24:21.148384: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): <undefined>, <undefined>
2019-10-04 21:24:21.522500: W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1412] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set.  If you want XLA:CPU, either set that envvar, or use experimental_jit_scope to enable XLA:CPU.  To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile.
Traceback (most recent call last):
  File "freeze.py", line 263, in <module>
    feed_dict={'X:0': X})
  File "freeze.py", line 238, in _simple_run_and_freeze
    initializer_nodes="")
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/tools/freeze_graph.py", line 361, in freeze_graph
    checkpoint_version=checkpoint_version)
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/tools/freeze_graph.py", line 190, in freeze_graph_with_def_protos
    var_list=var_list, write_version=checkpoint_version)
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saver.py", line 825, in __init__
    self.build()
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saver.py", line 837, in build
    self._build(self._filename, build_save=True, build_restore=True)
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saver.py", line 875, in _build
    build_restore=build_restore)
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saver.py", line 482, in _build_internal
    names_to_saveables)
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saving/saveable_object_util.py", line 342, in validate_and_slice_inputs
    for converted_saveable_object in saveable_objects_for_op(op, name):
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saving/saveable_object_util.py", line 205, in saveable_objects_for_op
    variable, "", name)
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/training/saving/saveable_object_util.py", line 82, in __init__
    self.handle_op = var.op.inputs[0]
  File "/home/dhananjai/anaconda3/envs/tf/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2410, in __getitem__
    return self._inputs[i]
IndexError: list index out of range

Code to reproduce the error:
# You will have to work in the mixnet directory in tensorflow/tpu
import os.path as osp
import tempfile
import shutil

import numpy as np
import tensorflow as tf
from mixnet_builder import build_model
from tensorflow.python.tools.freeze_graph import freeze_graph

# A utility function to freeze rhe graph. It will be used later
def _simple_run_and_freeze(graph,
                           output_name,
                           frozen_model_file='',
                           feed_dict={}):
    model_dir = tempfile.mkdtemp()
    graph_def_file = osp.join(model_dir, 'tf_graph.pbtxt')
    checkpoint_file = osp.join(model_dir, 'tf_model.ckpt')

    tf.reset_default_graph()
    with graph.as_default() as g:
        saver = tf.train.Saver()
    with tf.Session(graph=graph) as sess:
        # initialize
        sess.run(tf.global_variables_initializer())
        # run the result
        fetch = graph.get_operation_by_name(output_name).outputs[0]
        tf_result = sess.run(fetch, feed_dict=feed_dict)
        # save graph definition somewhere
        tf.train.write_graph(sess.graph, model_dir, graph_def_file)
        # save the weights
        saver.save(sess, checkpoint_file)

    freeze_graph(input_graph=graph_def_file,
                 input_saver="",
                 input_binary=False,
                 input_checkpoint=checkpoint_file,
                 output_node_names=output_name,
                 restore_op_name="save/restore_all",
                 filename_tensor_name="save/Const:0",
                 output_graph=frozen_model_file,
                 clear_devices=True,
                 initializer_nodes="")

    if osp.exists(model_dir):
        shutil.rmtree(model_dir)

    return tf_result

if __name__ == '__main__':
    tf.logging.set_verbosity(tf.logging.ERROR)
    BATCH_SIZE = 20
    DIM1 = DIM2 = 224
    # define a TF graph: input -> MixNet -> output
    graph = tf.Graph()
    with graph.as_default() as g:
        inputs = tf.placeholder(tf.float32, shape=[BATCH_SIZE, DIM1, DIM2, 3],
                                name='X')
        logits, _ = build_model(inputs, 'mixnet-s', False)

    output_name = logits.op.name
    X = np.random.randn(BATCH_SIZE, DIM1, DIM2, 3)
    frozen_model_file = 'mixnet_s_graph.pb'
    out = _simple_run_and_freeze(graph,
                                 output_name,
                                 frozen_model_file,
                                 feed_dict={'X:0': X})

This seems something specific to the mixnet code, but please let me know if you have any pointers/
Thanks in advance!

Can you validate that the feed_dict is in the graph that is being passed to freeze_graph and that the input arrays didn't get renamed. If that doesn't work, can you provide the checkpoint and pbtxt files as well as visibility into the code that's in build_model (imported by mixnet_builder) so that we can reproduce this issue.

Can you validate that the feed_dict is in the graph that is being passed to freeze_graph and that the input arrays didn't get renamed. If that doesn't work, can you provide the checkpoint and pbtxt files as well as visibility into the code that's in build_model (imported by mixnet_builder) so that we can reproduce this issue.

Hi sir! The feed_dict is still there. I visualized the .pb file and the input and output are indeed X and logits, respectively. You can find the checkpoint for the error in the first post in this page here. I trained on normal distribution to get around that with the following script: train.py.zip. The code for build_model can be found here. Looking forward to hearing from you.

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.


The career page on KodaDot

Is your feature request related to a problem?
The big font doesn't look really pretty and as someone who would like to apply for a job, I'm missing some main descriptions or motivational slogans about working for KodaDot.
Then also I don't like the fact that for applying for the job instead of some description about the job there is only learn more, which instead of some information directs me to discord... Where unfortunately it's hard to know if people who are applying there are really interested or just people who write the same message to every discord.
It would be actually great to know who find out about the job from our web.
Describe the solution you would like
Why should I apply here for a job and don't go somewhere else? I think something catchy and positive text about working in our team (our visions) should be the first thing when users open this page.
Instead of learning more, I would have a possibility to click on the job which you are interested in and there to have information in sections like an introduction to the job, responsibilities, what experience we want to have them, what they can learn and then something about the payment.

There would be after the main information possibility to fill out the applicant's main information as name, email, twitter, website, resume, CV, portfolio and how they heard about the position.

Describe alternatives you have considered
I'll wait for what you think and then we might get into more details about how it could be... This is just an idea...
Screenshots
No response
Are there opened related issues?
No response

https://hello.kodadot.xyz/be-part-of-kodadot/join-as-a-developer/hiring


Bundle exec on Windows has no outputs

Hi all,
sorry to create new issue in something that seems so easy to solve, but I can't find a solution: I'm on Windows (completely new to gem and bundle, I'm just trying to use them for Jekyll), when I run bundle exec jekyll serve there's no output, neither with bundle exec jekyll build.
It's not a problem of Jekyll, because running that commands directly (without bundle exec) outputs as normal (but it can't compile my project due to dependency problems, and here it's why I need to use bundle).
Here's my bundle env output:

Environment
Bundler       1.17.1
  Platforms   ruby, x64-mingw32
Ruby          2.5.3p105 (2018-10-18 revision 65156) [x64-mingw32]
  Full Path   C:/Ruby25-x64/bin/ruby.exe
  Config Dir  C:/ProgramData
RubyGems      2.7.6
  Gem Home    C:/Ruby25-x64/lib/ruby/gems/2.5.0
  Gem Path    C:/Users/super/.gem/ruby/2.5.0;C:/Ruby25-x64/lib/ruby/gems/2.5.0
  User Path   C:/Users/super/.gem/ruby/2.5.0
  Bin Dir     C:/Ruby25-x64/bin
Tools
  Git         2.17.1.windows.2
  RVM         not installed
  rbenv       not installed
  chruby      not installed

Bundler Build Metadata
Built At          2018-10-25
Git SHA           2760d72d3
Released Version  true

Gemfile
Gemfile
source "https://rubygems.org"

gem "github-pages", group: :jekyll_plugins

# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]

# Performance-booster for watching directories on Windows
gem "wdm", "~> 0.1.1" if Gem.win_platform?

Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
     [...]

PLATFORMS
  x64-mingw32

DEPENDENCIES
  github-pages
  tzinfo-data
  wdm (~> 0.1.1)

BUNDLED WITH
   1.17.1

Appreciating any help!

Hi, this is what the same command (bundle exec jekyll build) shows on my Ubuntu 18.04 partition:

Configuration file: ./_config.yml
Source: .
Destination: ./_site
Incremental build: disabled. Enable with --incremental
Generating...
Jekyll Feed: Generating feed for posts
done in 1.359 seconds.
Auto-regeneration: enabled
Server address: http://<IP_ADDRESS>:4000/
Server running... press ctrl-c to stop.

 Don't know what to think.

Hi @Maik93, I know this is a very old issue, but I'll ask just in case. Are you still having this issue? I think this should be fixed in newer versions of bundler.

Yea just tried, everything works as expected!
Thanks, we can close the issue!

Thanks so much for double checking!


Resize event is not fired when we drag the browser down or maximize it.

The responsive grid fails to resize when browser window is dragged down or maximized back again. Is it possible to handle this with available functionality?

You need to use WidthProvider to provide a width to the grid.

I am already using it, everything works fine if I manually click and resize the browser, but if I click on the title bar and drag it down from full-screen mode then you get to see the problem.
Same is when I am not is full-screen mode but I go full-screen by clicking maximize button on the browser window.

Sounds like a browser bug. Have you gotten to the bottom of it? Browser/OS


Investigate why CI is failing

CI is currently failing on both ie10 and ie11. Due to the current failure on HEAD all incoming PRs are marked as red whether or not they added any new regressions. The red state adds additional burden on maintainers to go an manually diff the test logs to see if any new regressions were added. It also makes it much harder / impossible for contributors to know if their patch caused regressions.
Getting CI into a stable green state would ideally allow for more contributions from others, as well as allow for faster iteration within polymer core.
Let me know what you think, Thanks :sparkles:

Yes completely agree. When I created my PR and saw the CI failure I was confused, but apparently it was failing on other tests.

Solved, per https://github.com/Polymer/polymer/issues/2582.  All tests are green, and we've switched from our internally-managed CI server to Travis as well.

A+ work @kevinpschaaf


Fix already valid SlotSet events being duplicated in the tracker by the FormAction

Description of the problem:
This PR removed slot extraction methods from FormAction so that slot extraction is only executed by ActionExtractSlots.  The existing FormAction.validate_slots method adds already valid events to the tracker in addition to validated slots. This creates duplicate events in the tracker since the already valid events were added to the tracker initially by ActionExtractSlots.
Solution: Adapt FormAction.validate_slots to only return the validated events.
Definition of Done:

[x] already valid SlotSet events are not added to the tracker by FormAction
[x] test_forms.py is adapted with the new expected output.

Closed via #10479


Fix document types for content store & rummager

Use the artefact "kind" as document type. For non-migrated editions we're currently sending the schema name (generic_with_external_related_links) to the content store as document type. This is affecting the analytics gathering, which uses document type.
This separates the two concepts by having a separate method for the type. This will make sure we won't confuse the two anymore.
As noted in #566, @artefact.kind isn't always the correct type (the kind doesn't change
if the format changes). This will be solved by migrating all the documents. In the meantime, the kind is preferable to generic_with_external_related_links.

Send the same data to rummager as content-store. This makes sure that the rendering_app, publishing_app and content_store_document_type are the same in rummager and content store. Currently we're sending "publisher" as rendering app wrongly. We're also sending the "kind" as document type, which is not always true.

cc @davidbasalla

Looks good, this fixes the described issues!


Enable fNIRS in coreg gui

Reference issue
Conversation started over in https://github.com/mne-tools/mne-nirs/issues/419 and specifically this comment from @larsoner https://github.com/mne-tools/mne-nirs/issues/419#issuecomment-985239162
However, when I ran the coreg guy with fNIRS data no sensors were displayed.
What does this implement/fix?
Enables plotting of fNIRS sources and detectors in the coreg gui
Additional information
I am totally new to the whole coregistration concept. So please let me know if there is more I should look at.
Also I am new to guis, how do I test this change in the CI?

@GuillaumeFavelier @larsoner could you please review

Hi @rob-luke , I'm +1 to add support for fNIRS if there is a need for it. I just wonder how to integrate it. For now we have one checkbox for each element to display (HSP, HPI, EEG), should we add one for fNIRS? Or are those always associated with EEG? Also, do we want to display them by default?

I thought about maybe having a separate fNIRS box for the weights for fNIRS, but really we should probably just change that to be "Sensors". In dig we don't have a separate entry for fNIRS dig points (they are called EEG even though they're not), and we might as well always show them if they're present I think, just like we do for EEG. fNIRS needs to be close to the scalp like EEG.
It'll get trickier with OPMs because you do typically want them up against the scalp, but the technology doesn't really require it (unlike fNIRS, where your signal will degrade much faster with distance from the scalp IIUC). But for now I think just adding fNIRS to what gets shown the same way EEG does is a good start.

Thanks @GuillaumeFavelier and @larsoner
I also see there is substantial and consistent work being done on the Coreg. Would it be better for this small change to be done via one of @GuillaumeFavelier PRs? Or maybe I should wait until development has stabilised? Or I should continue here? Any preference?

I also see there is substantial and consistent work being done on the Coreg. Would it be better for this small change to be done via one of @GuillaumeFavelier PRs? Or maybe I should wait until development has stabilised? Or I should continue here? Any preference?

I'm fine with you adding fNIRS support things here, I don't mind a bad rebase/merge or two along the way in #10015 at least :)

I don't mind a bad rebase/merge or two along the way in #10015 at least :)

Looks like it didn't even create a merge conflict. I think if you fix this then we can probably merge:
mne/gui/tests/test_coreg_gui.py:113: in test_coreg_gui_pyvista
    coreg = coregistration(inst=raw_path, subject='sample',
<decorator-gen-535>:24: in coregistration
    ???
mne/gui/__init__.py:195: in coregistration
    return CoregistrationUI(
mne/gui/_coreg.py:203: in __init__
    self._set_lock_fids(fid_accurate)
mne/gui/_coreg.py:223: in _set_lock_fids
    self._lock_fids = bool(state)
/usr/share/miniconda/envs/mne/lib/python3.9/site-packages/traitlets/traitlets.py:606: in __set__
    self.set(obj, value)
/usr/share/miniconda/envs/mne/lib/python3.9/site-packages/traitlets/traitlets.py:595: in set
    obj._notify_trait(self.name, old_value, new_value)
/usr/share/miniconda/envs/mne/lib/python3.9/site-packages/traitlets/traitlets.py:1219: in _notify_trait
    self.notify_change(Bunch(
/usr/share/miniconda/envs/mne/lib/python3.9/site-packages/traitlets/traitlets.py:1229: in notify_change
    return self._notify_observers(change)
/usr/share/miniconda/envs/mne/lib/python3.9/site-packages/traitlets/traitlets.py:1266: in _notify_observers
    c(event)
mne/gui/_coreg.py:352: in _lock_fids_changed
    self._set_sensors_visibility(self._lock_fids)
mne/gui/_coreg.py:605: in _set_sensors_visibility
    actor.SetVisibility(state)
E   AttributeError: 'list' object has no attribute 'SetVisibility'

Closed in favour of #10122


Remove reserved word restriction for Organization/Sender/Receiver names

Problem statement
In #7139, we added a restriction against special characters and reserved words for Organization/Sender/Receiver names just in case this were to cause issues in the back end.  However, reserved words aren't an issue at the moment so we can remove that restriction for now.
What you need to know

isProhibitedName is the function that checks against special characters and reserved words.

Acceptance criteria

[ ] Organization/Sender/Receiver names can contain reserved words again
[ ] Organization/Sender/Receiver names still cannot contain non-alphanumeric characters

I just want to make sure we are clear here, the following character should definitely not be restricted: * Current deploy is basically broken because this character is very common in scopes

@stephenkao On staging I get this error when clicking the "edit json and save" button as shown. I did not could/not check what exact thing it was choking on, I just assumed it was the *?

@arnejduranovic Ah, gotcha gotcha.  It's from this regex, which is failing on the hyphen -- which we should absolutely allow.  I'm going to update the ticket to remove the reserved words check AND allow hyphens (which should line up with the "all lowercase + hyphenated" format that we discussed with Jim in Slack), and I'll hop on this now to unblock everyone on this point.

Ah okay I remember this now. Thanks for the help!!

No problem -- just put up a pull request if you'd like to take a look.  Thanks for re-raising this issue!


[CloudFormation Deployment Failure] Nodejs10.x is no longer supported in AWS Lambda

Describe the bug
End of support of node.js 10x on AWS Lambda has been reached on July 30, 2021. So installing the stack referred to here: https://docs.aws.amazon.com/solutions/latest/document-understanding-solution/automated-deployment.html fails with the following error
Resource handler returned message: "The runtime parameter of nodejs10.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs14.x) while creating or updating functions.

To Reproduce
Attempt to Install the stack.
Expected behavior
Installation completes correctly.
Please complete the following information about the solution:

[x] Version: [v1.0.2]
[x] Region: [eu-west-1]

Hi @mohamed-ali : Thanks for opening the issue.  The bucket notifications module used in cdk library seems to refer to  node.js 10x for the lambda runtime.
My initial theory is that updating the cdk version for the solution should fix it.

Thanks for reviewing the issue.
It seems the switch to node12 was done in CDK 1.18.0 https://github.com/aws/aws-cdk/releases/tag/v1.18.0. I'll try that out.

Hi,
I tried<EMAIL_ADDRESS>and still has the same issue. The issue, it seems, is because one of the cdk extensions is using nodejs10 implicitly. I suspect it to be aws-s3-notifications
"BucketNotificationsHandler050a0587b7544547bf325f094a3db8347ECC3691": {
      "Type": "AWS::Lambda::Function",
      "Properties": {
        "Description": "AWS CloudFormation handler for \"Custom::S3BucketNotifications\" resources (@aws-cdk/aws-s3)",
        "Code": {
          "ZipFile": "exports.handler = (event, context) => {\n    // eslint-disable-next-line @typescript-eslint/no-require-imports, import/no-extraneous-dependencies\n    const s3 = new (require('aws-sdk').S3)();\n    // eslint-disable-next-line @typescript-eslint/no-require-imports\n    const https = require('https');\n    // eslint-disable-next-line @typescript-eslint/no-require-imports\n    const url = require('url');\n    log(JSON.stringify(event, undefined, 2));\n    const props = event.ResourceProperties;\n    if (event.RequestType === 'Delete') {\n        props.NotificationConfiguration = {}; // this is how you clean out notifications\n    }\n    const req = {\n        Bucket: props.BucketName,\n        NotificationConfiguration: props.NotificationConfiguration,\n    };\n    return s3.putBucketNotificationConfiguration(req, (err, data) => {\n        log({ err, data });\n        if (err) {\n            return submitResponse('FAILED', err.message + `\\nMore information in CloudWatch Log Stream: ${context.logStreamName}`);\n        }\n        else {\n            return submitResponse('SUCCESS');\n        }\n    });\n    function log(obj) {\n        console.error(event.RequestId, event.StackId, event.LogicalResourceId, obj);\n    }\n    // tslint:disable-next-line:max-line-length\n    // adapted from https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-lambda-function-code.html#cfn-lambda-function-code-cfnresponsemodule\n    // to allow sending an error messge as a reason.\n    function submitResponse(responseStatus, reason) {\n        const responseBody = JSON.stringify({\n            Status: responseStatus,\n            Reason: reason || 'See the details in CloudWatch Log Stream: ' + context.logStreamName,\n            PhysicalResourceId: event.PhysicalResourceId || event.LogicalResourceId,\n            StackId: event.StackId,\n            RequestId: event.RequestId,\n            LogicalResourceId: event.LogicalResourceId,\n            NoEcho: false,\n        });\n        log({ responseBody });\n        const parsedUrl = url.parse(event.ResponseURL);\n        const options = {\n            hostname: parsedUrl.hostname,\n            port: 443,\n            path: parsedUrl.path,\n            method: 'PUT',\n            headers: {\n                'content-type': '',\n                'content-length': responseBody.length,\n            },\n        };\n        const request = https.request(options, (r) => {\n            log({ statusCode: r.statusCode, statusMessage: r.statusMessage });\n            context.done();\n        });\n        request.on('error', (error) => {\n            log({ sendError: error });\n            context.done();\n        });\n        request.write(responseBody);\n        request.end();\n    }\n};"
        },
        "Handler": "index.handler",
        "Role": {
          "Fn::GetAtt": [
            "BucketNotificationsHandler050a0587b7544547bf325f094a3db834RoleB6FB88EC",
            "Arn"
          ]
        },
        "Runtime": "nodejs10.x",
        "Timeout": 300
      },
      "DependsOn": [
        "BucketNotificationsHandler050a0587b7544547bf325f094a3db834RoleDefaultPolicy2CF63D36",
        "BucketNotificationsHandler050a0587b7544547bf325f094a3db834RoleB6FB88EC"
      ],
      "Metadata": {
        "aws:cdk:path": "DUSStack/BucketNotificationsHandler050a0587b7544547bf325f094a3db834/Resource"
      }
    },

Were you able to reproduce the issue from your end?
Do you have any recommendation on how to resolve this issue?
Thanks

Alright I was able to reproduce the error.
It seems if you upgrade the aws-s3-notifications package in package.json, we should be good.
So along with upgrading all cdk packages to 1.131.0, please explicitly include aws-s3-notifications at 1.131.0
Let me know if that works

Note, we will need to update a couple of deployments
We have a GitHub based deployment that supports

Dev Deploy and CICD Deploy on Github
AWS Solutions deployment

To integrate  the fix, we can move ahead with 2 options -

[ ] Updating a separate branch on GitHub with the fix. [ETA : 11/20/21]
Once this fix is in place, users on GitHub can checkout the fixed branch and continue with deployment
[ ] Merging the fix on main branch and updating the AWS Solutions deployment [ETA : TBD]
Once this is done, the AWS Solutions deployment and main branch should support the fix

1.131.0

I changed the library versions to 1.131.0 as well as the CDK Cli version on build spec. I get the following error :
This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.
(Cloud assembly schema version mismatch: Maximum schema version supported is 6.0.0, but found 14.0.0)
error Command failed with exit code 1.

Note, we will need to update a couple of deployments
We have a GitHub based deployment that supports

Dev Deploy and CICD Deploy on GitHub
Automated deploy via AWS Solutions deployment

To integrate  the fix, we can move ahead with 2 options -

[x] Updating a separate branch on GitHub with the fix. [ETA : 11/20/21]
Once this fix is in place, users on GitHub can checkout the fixed branch and continue with deployment
This is completed  : Please use the cdkUpgrade branch added as part of the PR #201

[ ] Merging the fix on main branch and updating the AWS Solutions deployment [ETA : TBD]
Once this is done, the AWS Solutions deployment and main branch should support the fix

The new version (v1.0.3) is now released.

v.1.0.3 addresses the issue with the deployment. Closing out the issue. Please reopen if you still see deployment issues


Is it possible to retrieve managed identity using ARM template

How can I retrieve managed identity for Data Factory using ARM template which will eventually be used in linked service?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9075f4a4-f8ca-9143-8998-41e2be0b39b8
Version Independent ID: 60c67249-9bd5-0a3c-10e3-839d44922d2e
Content: Managed identity for Data Factory - Azure Data Factory
Content Source: articles/data-factory/data-factory-service-identity.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@v-liatba Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

@v-liatba  Thank you for your question.  Please let me explain.
The Managed Identity is created when the Factory is created/deployed.  The Identity is not part of the ARM template.
Each time a Factory is created, it is assigned an Identity by Azure.  The identity does not exist before the Factory is created.  Therefore you cannot retrieve the Identity from an ARM template.


Quick typo fix

Just noticed these :)

Haha, ironically I typo'd the branch name myself 🦊

Nice catch -- thanks @efstajas !


Scheduled start/stop of a queue?

Any chance there is an easy way to schedule the start and stopping of a queue, through say cron?  Woudl be great for christmas displays...

@gkuchera At the moment, there is nothing built in to PixelWeb directly for this, though I'm planning a ground-up rewrite that will address this. That doesn't help you for Christmas though, so let's go the cron route :) Checkout this forum post: http://forum.maniacallabs.com/showthread.php?tid=48&pid=348#pid348
My suggestion is to write a couple bash scripts, each which do a different function (probably just queue on and queue off). Off will be easy, but the queue will be a little bit of a pain as you have to include everything in your curl request, so that will get a little verbose. Read further back in that forum thread and I note how to get what the JSON data you need is out of pixelweb. For off, do the same process, just monitor what happens when you click a "Stop" button in the PW interface.
Then, when you are happy with those on/off scripts setup cron jobs that will run each at the desired time.
One major thing I'm planning in the rewrite is the ability to just call out a queue or pre-configured animation by name instead of having to pass the entire config everytime. So... keep an eye out for that. I'm sure you'll be able to use it by next Christmas ;)


Do not put street_address_2 into errors in billing address update

street_address_2 should not be treated as a required field in address validation. This error raises because we are using i18naddress.normalize_address(data) which normalizes street_address_X like street_address. See site-packages/18naddress/__init__.py L412 -> _normalize_field("street_address", rules, cleaned_data, [], errors). In our code we have a following mapping -> ("street_address", ["street_address_1", "street_address_2"]), so in case when street_address is required then automatically _1 and _2 are required too even if we have _2 only in allowed fields.
This is the only field which is affected because we add this field manually to allowed ones: saleor.graphql.account.utils.get_allowed_fields_camel_case#L172
def get_allowed_fields_camel_case(allowed_fields: set) -> set:
    """Return set of AddressValidationRules allowed fields in camel case."""
    fields = {validation_field_to_camel_case(field) for field in allowed_fields}
    if "streetAddress1" in fields:
        fields.add("streetAddress2")
    return fields

NOTE:
Since we have a deprecated tests in saleor/graphql/checkout/tests/deprecated/ because of using mutation based on checkout id instead of token i've move tests based on token only to saleor/graphql/checkout/tests/test_checkout_billing_address_update.py and renamed saleor/graphql/checkout/tests/deprecated/test_checkout_billing_address_update.py to saleor/graphql/checkout/tests/deprecated/test_checkout_billing_address_update_deprecated.py

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-3961 Optional fields raising a REQUIRED error in Address validation


Release 0.14.0 with fixes to previous PR

@pksunkara I just have one comment. The naming of the variable did not really convey what was going on to me, so I think it would be helpful to name it something different.
Other than that, this looks good to me. If we can address that, I'll merge.


feat(settings) Add Content Security Policy nonce

Added a Content Security Policy nonce to YbugSettings.

Thank you for the contribution !


DataSnapshot example in /docs/3-retrieving-data-as-lists.md doesn't work

When I used the instructions at https://github.com/angular/angularfire2/blob/master/docs/3-retrieving-data-as-lists.md to get a snapshot of a list using the exact code on that tutorial
this.items = af.database.list('/items', { preserveSnapshot: true });
this.items
  .do(snapshots => {
    snapshots.forEach(snapshot => console.log(snapshot.key()));
  })
  .subscribe(snapshots => console.log(snapshots.length));

I get the following error
Property 'do' does not exist on type 'FirebaseListObservable<any>'
I followed the example using the 'ng' cli to setup everything.
On a similar note when I tried to "Retrieve the Snapshot" using the following code from the bottom of https://github.com/angular/angularfire2/blob/master/docs/2-retrieving-data-as-objects.md
this.item = af.database.object('/item', { preserveSnapshot: true });
this.item.subscribe(snapshot => console.log(snapshot.key()));

I got the following error
snapshot.key is not a function
In this case it was a property but when I tried to find snapshot.value() I got the same error but the value was not even a property.
Thanks for looking into this

Kind of dumb of me to ask, but did you try snapshot.value() or snapshot.val()?
The Firebase API is DataSnapshot.val() not .value();
I'm using that same syntax, also preserving the snapshot, and it works just fine.
Firebase just went through a major update like 2 months ago and snapshot.key() turned into snapshot.key and the angularfire docs weren't updated, that's why you got that error.

You're right @lf-alves. it's snapshot.val(). I've made a PR for the docs #334

Thanks for the issue then the PR!


Windows: Resize without artifacts (experiment)

We will have to return to this issue later.
For now, we can create simple resize, with prev content blit in top-left corner and
with background brush color fill new extendend window area.

Useful resource https://stackoverflow.com/questions/53000291/how-to-smooth-ugly-jitter-flicker-jumping-when-resizing-windows-especially-drag/53032800#53032800


feat: add tag for maintainer and first time contributors

Adds tags to indicate whether a PR is by a maintainer or first time contributor. These are just alias emojis which are customizable in the workspace.
🔰 is a common bumper sticker seen in Japan for beginner drivers, the shoshinsha mark. Open to other ideas here :)
Debating whether or not to keep the maintainer tag and only highlight first time contributors.

Debating whether or not to keep the maintainer tag and only highlight first time contributors.

Personally, I think it looks a bit cluttered with the maintainer tag, given that the majority have it.
Perhaps swap the maintainer tag for an external contributor tag? Then the default (no tag) is maintainer, and a tag represents an external contributor (with a special tag for first time contributors).

@dsanders11 agreed and sounds good! And I think highlighting outside contributions should be the case.


default exclusions

You might like to add these:

https://riot.im/app/.*
https://riot.im/develop/.*

Does that bug only affect Waterfox and other older versions of Firefox? I know I used to see it but I don't see that bug on Firefox 58.


Teensy3.1 - K20D50M Update i2c_api.c

The increase of the Teensy3.1 core clock to 96MHz has caused the i2c communication to fail.
Problem is caused by a workaround using core _NOP clock cycles to perform a delay in the i2c.stop function.
Clearly running at a higher core clock rate the delay is reduced resulting with the i2c.stop function exiting before completing.
Increasing the _NOP count to 110 does get round the issue, however this will lead to an unnecessary delay for the slower K20D50M Target that requires 60 to work, unless conditional code is employed.
Replacing the workaround code to test with I2C_S_BUSY_MASK has fixed the issue.
This now makes the function independent of the core clock frequency allowing the clock set up to be changed without affecting the i2c.stop operation.
Hardware tested on both Targets with several i2c devices.
I have also tested with KLxx range of platforms and is working there as well and should also work with the K22F and K64F Targets, although the code will be slightly different there.

Nice catch here. I haven't checked frdm exmaples for a while, do they still do NOP as noted in the code you changed? :)

Tried the same code and tests on the FRDM KLxx's and these are working. I can see no reason why this change can't be applied to these as well. However I think we should just do the Teensy and K20D50M for the moment to be sure.


Downscale core nodes

Discussed in https://github.com/emqx/emqx-operator/discussions/628

Originally posted by alexa22013 February 27, 2023
When I downscaled core nodes from 3 to 2 the repicant nodes were crashing
replicant node logs showed this error
[emqx-replicant-6d5577f77d-lx4: 2023-02-26T19:08:47.518993+00:00 [error] line: 182, mfa: mria_lb:list_core_nodes/1, msg: mria_lb_core_discovery divergent cluster, node<EMAIL_ADDRESS>previous_cores: [], returned_cores: ['emqx<EMAIL_ADDRESS>unknown_nodes<EMAIL_ADDRESS>how to avoid this?
Also is there any practice on when to scale core node and when to scale replicants?

it's maybe an issue. So invite @ieQu1 to help with the investigation
I had some discussions with @Rory-Z there are some key points:

Clustering via DNS
The Operator just shut down the core node in downscaling, instead of executing the emqx ctl cluster leave cmd and waiting for its completion.

it's maybe an issue. So invite @ieQu1 to help with the investigation I had some discussions with @Rory-Z there are some key points:

Clustering via DNS
The Operator just shut down the core node in downscaling, instead of executing the emqx ctl cluster leave cmd and waiting for its completion.

And after downscale code nodes, the DNS list will updated

Fixed by https://github.com/emqx/mria/pull/123/files

Fix https://github.com/emqx/mria/pull/123/files

Do we plan to introduce this fix in EMQX 5.0.19 and EMQX Enterprise 5.0.1 ?

EMQX 5.0.19 is released, close this issue.


Fix makefile and add CI job to check schema and unit tests

I would suggest changing the name of the workflow and the jobs to something more descriptive

Please propose something because I honestly can't come up with anything better :)


md-datetimepicker

We don't have a time-picker planned before beta; closing this issue since it's not actionable in the short term (trying to keep the number of issues down).

I made one from the current datepicker:
https://github.com/michael-mcanulty/md-datetimepicker

You can use amazing time picker (amazing-time-picker) for this purpose, and it is fully compatible with Angular 2-7 and Material design:
https://github.com/owsolutions/amazing-time-picker
Live demo:
https://owsolutions.github.io/amazing-time-picker
Thanks.


[RPA-632] Adds variable sidebar panel

Adds variable tab with all variables used in the process and tag then depending on if it is a global, action assigned or input/output one
Description

adds variable sidebar panel (v1) which lists all the variables used in the currently opened process
tags variables depending on if it is a global, action assigned or input/output one
variable names can be copied fromt the sidebar variables panel view (once you extend the accordion)
creates hooks for getting the variables types mentioned above
creates hook with getting all the variables used in the process
fixes issue which cause crashed when the global variables were undefined for ElementAwareAutocompleteWidget widget
fixes issue were sidebar label was not translated on language change

Motivation and Context

UX improvement

Types of changes

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

I agree to the terms of the RunBotics Contributor License Agreement.

Hm could you refactor element aware autocomplete to use the new hook?


Prefix cluster name during testing with username

What this PR does / why we need it:
now creating user specific name of cluster
this will avoid tests running by multiple users on same setup from
conflicting

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
How Has This Been Tested?:
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration and test output
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note:

closing it due to merge conflicts


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.13.3",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3b2b93a485fb7a970bc8b5daef16f4cf579d172f"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "3b2b93a485fb7a970bc8b5daef16f4cf579d172f",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "drm/amd/display: Avoid HDCP over-read and corruption\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.13.3 by commit 3b2b93a485fb7a970bc8b5daef16f4cf579d172f. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001223


Dialogs: regex version bump

Fixes #2019

Nice, was just about to create an issue about this 👍 This should also fix a conflict with semantic-kernel, which requires regex >=2023.6.3


full module on SDXL?

Is it possible to use full module on SDXL? I am using sd-script but I could not train.

you should be able to run full-module on SDXL
BUT full-module with preset=full will take "more vram" then training sdxl natively.
If what you met is OOM error. That is expected

Thank you for your answer. I appreciate you.


feat: Include padding when resizing multiple input

Remove the hard-coded 10px when accounting for padding, and use the calculated padding size instead, in case the theme has been overridden.
Note that the test appends the generated uiSelectMultiple to the DOM (and later removes it) so that getComputedStyle functions normally.

These four failing tests (which are not related to this PR) seem to happen on a fresh checkout from master now.  Not sure why, but I think it's probably a dependency-version thing.   I will be investigating further.


Export intermediate state

Description
Adds intermediate states back to non-parallel jobs. Jobs not running in parallel will now create new jobs for each page of results, allowing interrupted jobs to restart from the last successfully completed page of results instead of starting from the beginning.
This will slightly change the names of output files to bring them inline with the naming convention used for jobs run in parallel.
This should not have a noticeable impact on performance.
Related issues
Addresses [issue #].
Testing
Describe how this change was tested.
FHIR Team Checklist

Update the title of the PR to be succinct and less than 65 characters
Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
[ ] CI is green before merge
Review squash-merge requirements

Semver Change (docs)
Patch (reason)

OoM fix didn't work. It is just crashing and not getting to the error handling.


Add support for Windows (really)

The only reason I'm really even looking into logstash is because windows is so obtuse when it comes to logging; I need to get IIS and event handlers into something useful.

+1 for Windows support

Folks.. Were we able to get a module for Windows.. I am in need of it now.. :-)
Thanks..


removeLayer is not a function

From @antoinegiret on May 7, 2015 14:6
Hi, I have an error when I remove paths having a layer.
TypeError: overlay.removeLayer is not a function

Here is the definition of my layer and my path:
angular.extend($scope, {
   layers: {
      baselayers: {
         ...
      },
      overlays: {
         test: {
            name: 'test',
            visible: false,
            type: 'group'
         }
      }
   },
   paths: {}
});

...

var test = function () {
   $scope.paths['test'] = {
      layer: "test",
      type: "polyline",
      latlngs: latlngs
   };
};

And how I remove it from my map:
$scope.paths = {}

Thanks
Copied from original issue: tombatossals/angular-leaflet-directive#747

I haven't had time to look into it. Have you dug into the directive yourself?

From @antoinegiret on May 13, 2015 7:8
No solutions ?


SEC-52 update codeql

updated codeql for a common config and common ql packs.

@Zach-Johnson pls review and approve


Typo with the container name

Container name has a typo after some copy/paste. It's called "order-service" on this page, while on another page describing use of managed identity the same container name was correctly changed to "ai-service": https://learn.microsoft.com/en-us/azure/aks/open-ai-secure-access-quickstart.

@MGoedtel

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


TabBar, Tab, and TabBarVIew Widgets require roles, ARIA properties, and keyboard support (Accessibility)

Use case
The TabBar, Tab, and TabBarVIew widgets require roles, ARIA properties, and expected keyboard support to meet accessibility compliance requirements outlined in the Web Content Accessibility Guidelines (WCAG).
Proposal
WAI-ARIA Roles, States, and Properties
TabBar Widget

Use role="tablist" on the container element
Provide a label for the tab group by using aria-label OR aria-labelledby="[IDREF]" on the container element, with [IDREF] referencing the unique ID of the element that describes the purpose of the tab group
If the tablist element is vertically oriented, it has the property aria-orientation="vertical". The default value of aria-orientation for a tablist element is horizontal

Tab Widget

Use role="tab" on each tab
Use aria-controls="[IDREF]" on the tab element, with [IDREF] referencing the unique ID of the tabpanel element associated with the tab
When a tab is active (i.e. its corresponding panel is currently displayed): Use aria-selected="true" on the tab element
When a tab is inactive (i.e. its corresponding panel is NOT currently displayed): Use aria-selected="false" on the tab element
If a tab element has a popup menu, it has the property aria-haspopup set to either menu or true

TabBarView Widget

Use role="tabpanel" on the element that serves as a container for tab panel content
Provide an accessible name for the tab panel by using aria-label OR aria-labelledby="[IDREF]" on the container for the tab panel content, with [IDREF] referencing the unique ID of the tab element that controls the panel

Keyboard Interaction
Tab Key

When focus moves into the tab list, places focus on the active tab element
When the tab list contains the focus, moves focus to the next element in the page tab sequence outside the tablist, which is the tabpanel unless the first element containing meaningful content inside the tabpanel is focusable

When focus is on a tab element in a horizontal tab list:

Left Arrow: Moves focus to the previous tab. If focus is on the first tab, moves focus to the last tab. Optionally, activates the newly focused tab
Right Arrow: Moves focus to the next tab. If focus is on the last tab element, moves focus to the first tab. Optionally, activates the newly focused tab

When focus is on a tab in a tablist with either horizontal or vertical orientation:

Space or Enter: Activates the tab if it was not activated automatically on focus
Home : Moves focus to the first tab. Optionally, activates the newly focused tab
End: Moves focus to the last tab. Optionally, activates the newly focused tab
Shift + F10: If the tab has an associated popup menu, opens the menu

the topic seems to be addressed this document
as mentioned in this issue

https://github.com/flutter/flutter/issues/107861#issuecomment-2066989390

@darshankawar maybe the could be an umbrella issue for those use cases

the topic seems to be addressed this document as mentioned in this issue

Consider providing the necessary semantics for denoting tab bars for accessibility #107861 (comment)

Closing in favor of the linked issue.

Reopening based on https://github.com/flutter/flutter/issues/107861#issuecomment-2427190284

Created a NEW Chrome issue for this: https://g-issues.chromium.org/issues/383392741

I did a little test it seems once we assign the role, we don't need to produce label like 'tab 1 of 3' in the framework since the web screen reader will handle that directly.


Cannot load e5

https://github.com/embeddings-benchmark/mteb/blob/a10fa6b1c6ebb337671873c9ccffe3ed4f05fb08/mteb/models/e5_instruct.py#L167
Should it be model_name=name?

Completely correct. I have added the fix to #987


PYIC-1905 Drop VCs if storage for CIs fails

Proposed changes
What changed
If submitting to CI storage fails for whatever reason, throw an error and don't store the VC - treat it the same way as a VC storage failure and return journey error response.
Why did it change
If storing a CI in the CI storage system fails for any reason we shouldn't use the VC that was issued in to attempt to meet an identity profile.
Issue tracking

PYIC-1905

@Wynndow I've rejigged things a bit so we're now swallowing any errors as before. The idea being eventually we can remove that try-catch and catch CiPutException further up to return the journey error response (as we know throw this in CiStorageService on lambda failure).


Clickhouse table doesn't have same counts as Postgres table (following readme example)

After following the readme example, I end up with:
In Clickhouse:
SELECT SUM(abalance * sign), SUM(sign), count(0) FROM pgbench_accounts;

SELECT
    SUM(abalance * sign),
    SUM(sign),
    count(0)
FROM pgbench_accounts

┌─SUM(multiply(abalance, sign))─┬─SUM(sign)─┬─count(0)─┐
│                       -931490 │         0 │    49744 │
└───────────────────────────────┴───────────┴──────────┘

And in Postgres:
pg2ch_test=# SELECT SUM(abalance), COUNT(*) FROM pgbench_accounts;
   sum   | count
---------+--------
 -931490 | 100000
(1 row)

I see that the sums are the same but the counts are different. Is this because only changes are replicated and, thus, only rows that underwent a change are represented in Clickhouse?

not really. pg2ch creates an initial copy first, and then applies changes

not really. pg2ch creates an initial copy first, and then applies changes

Thanks for the quick reply, @mkabilov! TL;DR, I've run through the readme example a few times and it seems consistently the case that the initial copy isn't taking place. Could you let me know your thoughts on why this seems to be the case or if I'm missing something? Thanks so much! Details follow.
Versions
Ubuntu 20.04.1 LTS
postgres 12.5
Clickhouse server version 20.10.3 revision 54441

Setup & Test
PG_CONN=postgres://postgres:password@localhost:5432
cd go/src/github.com/mkabilov/pg2ch
go build

# PG & CH reset reset
psql $PG_CONN/postgres -c "DROP DATABASE pg2ch_test;"
psql $PG_CONN/postgres -c "select pg_drop_replication_slot('pg2ch_slot');"
clickhouse-client --password=password --query "drop table pgbench_accounts;"
clickhouse-client --password=password --query "drop table pgbench_accounts_buf;"

# PG setup
psql $PG_CONN/postgres -c "CREATE DATABASE pg2ch_test;"
pgbench -U postgres -d pg2ch_test -i
psql $PG_CONN/pg2ch_test -c "ALTER TABLE pgbench_accounts REPLICA IDENTITY FULL;"
psql $PG_CONN/pg2ch_test -c "CREATE PUBLICATION pg2ch_pub FOR TABLE pgbench_accounts;"
psql $PG_CONN/pg2ch_test -c "SELECT * FROM pg_create_logical_replication_slot('pg2ch_slot', 'pgoutput');"

# Clickhouse setup
clickhouse-client --password=password --query="CREATE TABLE pgbench_accounts (aid Int32, abalance Int32, sign Int8) ENGINE = CollapsingMergeTree(sign) ORDER BY aid"
clickhouse-client --password=password --query="CREATE TABLE pgbench_accounts_buf (aid Int32, abalance Int32, sign Int8, row_id UInt64) ENGINE = Memory()"

# Begin pg2ch
./pg2ch --config config.yaml > log.txt 2> log_err.txt &

# Make changes
pgbench -U postgres -d pg2ch_test --time 30 --client 10
sleep 15

# Check CH & PG
psql $PG_CONN/pg2ch_test -c "SELECT SUM(abalance), COUNT(*) FROM pgbench_accounts" > pg_result.txt
clickhouse-client --password=password --query="SELECT SUM(abalance * sign), SUM(sign) FROM pgbench_accounts" > ch_results.txt

Results
Here's the stderr output of pg2ch (stdout output is empty):
2021/01/20 15:22:48 consuming changes for table pgbench_accounts starting from 0/1560E890 lsn position
2021/01/20 15:22:48 generation_id: 51209
2021/01/20 15:22:48 Starting from 0/1560E890 lsn
2021/01/20 15:23:48 FlushToMainTable for pgbench_accounts pg table processed in 0s (rows: 51928)

Here are the contents of pg_result.txt:
   sum   | count
---------+--------
 -303129 | 100000
(1 row)

Here are the contents of ch_result.txt:
-303129	0	51928

Thanks for the quick reply, @mkabilov! TL;DR, I've run through the readme example a few times and it seems consistently the case that the initial copy isn't taking place. Could you let me know your thoughts on why this seems to be the case or if I'm missing something? Thanks so much! Details follow.
Versions
Ubuntu 20.04.1 LTS
postgres 12.5
Clickhouse server version 20.10.3 revision 54441

Setup & Test
PG_CONN=postgres://postgres:password@localhost:5432
cd go/src/github.com/mkabilov/pg2ch
go build

# PG & CH reset reset
psql $PG_CONN/postgres -c "DROP DATABASE pg2ch_test;"
psql $PG_CONN/postgres -c "select pg_drop_replication_slot('pg2ch_slot');"
clickhouse-client --password=password --query "drop table pgbench_accounts;"
clickhouse-client --password=password --query "drop table pgbench_accounts_buf;"

# PG setup
psql $PG_CONN/postgres -c "CREATE DATABASE pg2ch_test;"
pgbench -U postgres -d pg2ch_test -i
psql $PG_CONN/pg2ch_test -c "ALTER TABLE pgbench_accounts REPLICA IDENTITY FULL;"
psql $PG_CONN/pg2ch_test -c "CREATE PUBLICATION pg2ch_pub FOR TABLE pgbench_accounts;"
psql $PG_CONN/pg2ch_test -c "SELECT * FROM pg_create_logical_replication_slot('pg2ch_slot', 'pgoutput');"

# Clickhouse setup
clickhouse-client --password=password --query="CREATE TABLE pgbench_accounts (aid Int32, abalance Int32, sign Int8) ENGINE = CollapsingMergeTree(sign) ORDER BY aid"
clickhouse-client --password=password --query="CREATE TABLE pgbench_accounts_buf (aid Int32, abalance Int32, sign Int8, row_id UInt64) ENGINE = Memory()"

# Begin pg2ch
./pg2ch --config config.yaml > log.txt 2> log_err.txt &

# Make changes
pgbench -U postgres -d pg2ch_test --time 30 --client 10
sleep 15

# Check CH & PG
psql $PG_CONN/pg2ch_test -c "SELECT SUM(abalance), COUNT(*) FROM pgbench_accounts" > pg_result.txt
clickhouse-client --password=password --query="SELECT SUM(abalance * sign), SUM(sign) FROM pgbench_accounts" > ch_results.txt

Results
Here's the stderr output of pg2ch (stdout output is empty):
2021/01/20 15:22:48 consuming changes for table pgbench_accounts starting from 0/1560E890 lsn position
2021/01/20 15:22:48 generation_id: 51209
2021/01/20 15:22:48 Starting from 0/1560E890 lsn
2021/01/20 15:23:48 FlushToMainTable for pgbench_accounts pg table processed in 0s (rows: 51928)

Here are the contents of pg_result.txt:
   sum   | count
---------+--------
 -303129 | 100000
(1 row)

Here are the contents of ch_result.txt:
-303129	0	51928

Just wanted to follow-up with a naive tracing of what's going on... I could totally be wrong and appreciate your help in figuring out if this is user-error on my part or a bug or something else :).
It looks like an initial copy of a table will only occur if there's no tableLSN for that table (see here) Sure enough, every time I start pg2ch, there's always a value for tableLSN for the pgbench_accounts table. This would seem to explain the mechanism by which the initial copy seems to not occur?
All that said, I don't know what's expected; is there supposed to be no tableLSN value there until after the initial copy? Something else?
On a separate note, some results that would seem to support that everything besides the initial copy is working as expected follow. I ran pgbench a few times. After each run, I compared results between PG and CH. PG and CH both showed always the same sum. PG count was always 100000. CH counts increased between each run, presumably because different rows were being updated on each run and so those records would get replicated over to CH.
To wit:
#After 1st run of pgbench:
pg_sum: -195275
ch_sum: -195275
pg_count: 100000
ch_count: 20430

#After 2nd run of pgbench:
pg_sum: -55540
ch_sum: -55540
pg_count: 100000
ch_count: 38968

#After 3rd run of pgbench:
pg_sum: -221687
ch_sum: -221687
pg_count: 100000
ch_count: 57610

Probably worth noting that those sums are only matching because the value of abalance is initially 0 for all records in pgbench_accounts. To test that hypothesis, I ran pgbench prior to creating the replication slot to get some non-0 values for abalance. After then turning on replication and running pgbench, I got different sums for PG and CH as I suspected would happen.

Just wanted to follow-up with a naive tracing of what's going on... I could totally be wrong and appreciate your help in figuring out if this is user-error on my part or a bug or something else :).
It looks like an initial copy of a table will only occur if there's no tableLSN for that table (see here) Sure enough, every time I start pg2ch, there's always a value for tableLSN for the pgbench_accounts table. This would seem to explain the mechanism by which the initial copy seems to not occur?
All that said, I don't know what's expected; is there supposed to be no tableLSN value there until after the initial copy? Something else?
On a separate note, some results that would seem to support that everything besides the initial copy is working as expected follow. I ran pgbench a few times. After each run, I compared results between PG and CH. PG and CH both showed always the same sum. PG count was always 100000. CH counts increased between each run, presumably because different rows were being updated on each run and so those records would get replicated over to CH.
To wit:
#After 1st run of pgbench:
pg_sum: -195275
ch_sum: -195275
pg_count: 100000
ch_count: 20430

#After 2nd run of pgbench:
pg_sum: -55540
ch_sum: -55540
pg_count: 100000
ch_count: 38968

#After 3rd run of pgbench:
pg_sum: -221687
ch_sum: -221687
pg_count: 100000
ch_count: 57610

Probably worth noting that those sums are only matching because the value of abalance is initially 0 for all records in pgbench_accounts. To test that hypothesis, I ran pgbench prior to creating the replication slot to get some non-0 values for abalance. After then turning on replication and running pgbench, I got different sums for PG and CH as I suspected would happen.

Hi @mkabilov,
I'm happy to report I got this working. It looks like rm -rf the pg2ch directory and doing a  clean install fixed it. Might there be some stateful directory contents that make killing the process insufficient if one wants to start replication "from 0"?

Hi @mkabilov,
I'm happy to report I got this working. It looks like rm -rf the pg2ch directory and doing a  clean install fixed it. Might there be some stateful directory contents that make killing the process insufficient if one wants to start replication "from 0"?

Meant to close w the preceding comment. Thanks @mkabilov !

Meant to close w the preceding comment. Thanks @mkabilov !


Git merge resolution options leave a stray symbol behind

Type: Bug
I have a patch with an 88 character first line / subject, so the line ends up being 112 characters with the ">>>>>>>" and the SHA prefix and the parenthesis around the subject that visual studio code adds.  I'm not sure what settings lead to the choice, but, however it happens, the last close-parenthesis around the subject ends up wrapping to the next line.  So it would be something like this:

4f5636862bd70 (My very long subject goes here
)

All 3 automatic resolution options, "Accept Current Change", "Accept Incoming Change" and "Accept Both Changes" result in the extra parenthesis sticking around.  That's almost always going to be a particularly difficult mistake to track down in programming.
 We don't add any, that would come from Git or a formatter.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

It's an LF (ASCII 10).  I have GitLens installed but the Git resolution behavior is stock VS Code, according to the docs (I'm new to VS code).  I've attached some screen shots, in case there is still confusion.

Note the trailing close-parenthesis in the second one.


CSUB-347 weighted probabilistic threshold

Description of proposed changes:
Generate a fraction weighted by stake and a sample size fraction parameter.
Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #814 (39ffd16) into dev (88628bd) will decrease coverage by 0.25%.
The diff coverage is 93.84%.

@@            Coverage Diff             @@
##              dev     #814      +/-   ##
==========================================
- Coverage   78.24%   77.98%   -0.26%
==========================================
  Files          51       66      +15
  Lines       10317    10536     +219
==========================================
+ Hits         8073     8217     +144
- Misses       2244     2319      +75

Impacted Files
Coverage Δ

node/rpc/src/task.rs
82.22% <ø> (ø)

node/src/rpc.rs
0.00% <ø> (ø)

node/src/service/nonce_monitor.rs
0.00% <0.00%> (ø)

pallets/creditcoin/src/migrations/mod.rs
0.00% <0.00%> (ø)

pallets/creditcoin/src/ocw.rs
96.00% <ø> (-0.50%)
:arrow_down:

pallets/creditcoin/src/ocw/errors.rs
58.33% <0.00%> (-19.45%)
:arrow_down:

pallets/creditcoin/src/ocw/rpc.rs
78.61% <ø> (-3.78%)
:arrow_down:

pallets/creditcoin/src/types.rs
91.11% <0.00%> (-1.42%)
:arrow_down:

...ets/offchain-task-scheduler/runtime-api/src/lib.rs
42.85% <ø> (ø)

pallets/offchain-task-scheduler/src/tasks/error.rs
0.00% <0.00%> (ø)

... and 41 more

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

blocked by #813

Regarding the floating points...
The use of FP is fairly limited and is only used by worker threads to decide whether submitting transactions is appropriate.
The FLOPs don't look parallelizable. There may be accuracy loss but it is precise. Given that the hardware target supports standard FP64, I don't see why it could yield different results.
Doesn't risk balances directly, on average. The corner case is missing on rewards.
Nonetheless, I tried to get rid of it. I looked into parity's PerThings  implementors and rust's fixed fixed point crate but I haven't found a way yet to implement 'fixed_point.pow(fixed_point)' with logs and exponents.
Not a strong argument but, Algorand uses FP in their main consensus in the same 'sortition' use case and Algorand has a strong peer-reviewed background. Maybe the use of FLOPS in this context is justified.
Help is welcomed, this is how far I've got.


 Adapted from discussions with @akikoskinen .

@akikoskinen better now?


Installer does not get confirmation for computer restart

Microsoft PowerToys version
0.59.1
Running as admin

[ ] Yes

Area(s) with issue?
Installer
Steps to reproduce

Run the installer. It may need to be an upgrade
It will restart the system without warning you.

✔ Expected Behavior
I expected it behave like literally every other installer: get to the point where it needs to restart the computer, and ask me for permission to do so and maybe give me the option to restart later.
❌ Actual Behavior
An unexpected restart that caused data loss while I was working in another program.
Other Software
No response

Just happened here too. Win10, completely new installation of PowerToys through Microsoft Store.

This is a dupe of #18747

This is a dupe of #18747

Sure looks like it. I added a comment there for my issue and I'll close this one.


compatible with angular : 6.0.0-rc.0 and rxjs 6.0.0-beta.1

Compatible with angular : 6.0.0-rc.0 and rxjs 6.0.0-beta.1
Backward compatible
Packaging with ng-packagr
integration tests

I signed it!

For prelease testing with Angular 6.0.0-rc.0
npm i @xmlking/angular-in-memory-web-api

I'm closing because I only want to support RxJS v.6 and do not intend to support backward compat library which is deprecated in Angular v7.
Moreover, this PR updates far too many files.
But thanks for you interest and I hope you continue to find value in this library.


Latest updates (minor)

Following updates are included:

Add MEC to supported Office prod channels
Add note to check oem guides for turning on virtualization
Add location for Office policy (user)
Clarify full telemetry is not required
Updated known issues

@Dansimp

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@ekarafezov please implement the feedback. Thanks

@ekarafezov - please commit the rest of my suggested changes. Thanks.

@schmurky Please merge this P. Thanks


port the app to use the new API from OT

migration from sqlite to external API.

[ ] check all calls return as expected
[ ] fix data inconsistencies

Development of genetics portal has moved to https://github.com/opentargets/genetics.


Can't close some notifications

From AP-4317
How is the user affected? And what is the expected behavior?
On occasion, when multiple notifications appear, it is impossible to close them all. I would expect them to close when clicking the close icon.
https://github.com/chromaui/addon-visual-tests/assets/22988955/ec4fda41-7583-41b8-8c35-eddac34f8d69
Is there a workaround?
Refresh the page. This feels bad to have to do.
What are the steps for reproducing the issue?

Start a test
Go to a test with changes while the new test is running
Click the play button in the VTA addon panel while a test is running

You can also just start and stop tests from the sidebar a few times.
Other information
Side notes:

As reported in the VTA QA issue, the play button should not even be possible to click in the VTA addon when a test is running.
The progress bar seems to expand when I click that play button as well. This might be a non-issue once that superfluous play button is removed.

This problem may already be resolved, but needs verification.


API: allow SyntaxNodes to check whether they are syntax collection

This is helpful for indentation because syntax collection should not
add a new indentation level.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 73ef6bd05c12a3dca472df18ad858d974440d272