Log viewer: Show live view of current server time

It would be useful to see the current time and perhaps the time zone at the server in the log viewer. This allows better comprehension of time zone differences.

Implemented, done!


Add union, union_with methods to SparseSet

Misc:

Added asymptomic complexity table to the README since tabular information is easier to read at a glance
Added Clone implementations to all types

@thass0 I'm not too opinionated on the naming, happy to change either of them


Use Event stream in Validator Clock

It's sort of TODO. We should use the event stream here but in a future PR
Originally posted by @dapplion in https://github.com/ChainSafe/lodestar/pull/2416#discussion_r620653675

Already done in
https://github.com/ChainSafe/lodestar/blob/2ed2e03d0ca3e2d6e04e503d4e1beb2deedd47a7/packages/validator/src/services/chainHeaderTracker.ts#L22


Remove sprockets-rails

Do we need this anymore? I guess that Rails 8.0 transitions from sprockets to propshaft? We still have sprockets. Maybe we don't need it? Or, if we do, maybe it should be migrated to propshaft?

I don't think that this is going to work, because I think that activeadmin seems to break with this removal of sprockets.
~/code/david_runger  remove-sprockets ✔ 4↥  12:16:00 PM
❯ rs
=> Booting Puma
=> Rails 8.0.0 application starting in development
=> Run `bin/rails server --help` for more startup options
Exiting
/home/david/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/railties-8.0.0/lib/rails/railtie/configuration.rb:109:in `method_missing': undefined method `assets' for an instance of Rails::Application::Configuration (NoMethodError)
Did you mean?  asset_host
	from /home/david/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/activeadmin-3.2.5/lib/active_admin/engine.rb:13:in `block (2 levels) in <class:Engine>'

A similar error also occurred in CI (link).
I think I am going to try opening a new PR migrating from sprockets to propshaft. Maybe that will work.

I think I am going to try opening a new PR migrating from sprockets to propshaft. Maybe that will work.

Nevermind. The upgrade process is a lot more than I want to take on.


Incorrect cell formula in DefineByWorkload worksheet impacts calculations

On the DefineByWorkload worksheet the cells used to calculate figures for the Standard_A2_v2 sku are incorrectly copied from the Standard_A1_v2 row.
Effected cells:
F:190
N:190

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

ID: 0361b690-092e-77c1-fccb-1c2aeba5e259
Version Independent ID: ac57d31d-4356-2d99-9f1c-976513f353ec
Content: Azure Stack Hub Capacity Planner - Azure Stack Hub
Content Source: azure-stack/operator/azure-stack-capacity-planner.md
Service: azure-stack
Sub-service: azure-stack-hub
GitHub Login: @BryanLa
Microsoft Alias: bryanla

Hello @dfencegit,
Thank you for your feedback. We will investigate and update the thread further.


Fix JPEG color-space issues in Safari

The JPEG color-space issue in Mobile Safari now is also present in Safari.  We having nothing better than user-agent scraping to determine if we need to convert to a limited set of color spaces with JFIF headers.  Test against recent Safari and Chrome user agent strings.

For the record, this issue was introduced into the non-mobile version of Safari 10.1, which came out in March.

@jbeezley Would you mind reviewing this?  I have field confirmation that it fixes the problem.


Reactant generation from product

Hi! Is there a script to generate reactants from products? E.g. if I have a list of products, how can I generate the reactants from it? Thanks!

Hi,
I think this script should be useful for you - https://github.com/vsomnath/graphretro/blob/main/scripts/eval/single_edit_lg.py
It takes the products from a CSV file, and predicts their reactants.
Best,
Vignesh

Hi, Thanks! I made some tweeking in the single_edit_lg.py script and I was able to save them into a CSV as well. Thanks for the quick response!


Only import needed libraries

For example, if only serial connection is needed, libraries for NI cards should not be imported.

I agree, however, all libraries still need to be installed. We should check the good practices regarding importing in this way...


[pilot] Some minor cleanup of bootstrap code

This helps to clarify dependencies that are k8s-specific.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: nmittler
Assign the PR to them by writing /assign @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
506ccfe09fe1037fad127a49c5e51a86dc982552
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
506ccfe09fe1037fad127a49c5e51a86dc982552
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
506ccfe09fe1037fad127a49c5e51a86dc982552
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
506ccfe09fe1037fad127a49c5e51a86dc982552
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
506ccfe09fe1037fad127a49c5e51a86dc982552
link
/test e2e-simple

prow/istio-pilot-e2e.sh
506ccfe09fe1037fad127a49c5e51a86dc982552
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ZackButcher
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [ZackButcher]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Why was cluster removed ?? Reviewers , please make sure not code is removed without making sure the people working on that code review and approve. Renames,  removals, move of code must be discussed first !
I would suggest reverting this and doing it again.

You mean the removal of the variable? It wasn't being used beyond the scope of the k8s code, so it was created inline instead.

Renames, removals, move of code must be discussed first !

I disagree, in general ... these sorts o things are normal steps in development and should be generally be encouraged.
I'll roll back this PR for now, since it seems to be causing some heartburn.


jest-resolve: Package subpath './build/defaultResolver.js' is not defined by "exports"

🐛 Bug Report
Before<EMAIL_ADDRESS>it was possible to import a default resolver from jest-resolve build folder. After that version it became impossible. This commit seems to introduce the issue.
This is the error I'm getting:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './build/defaultResolver.js' is not defined by "exports" in /home/v1rtl/Coding/tinyhttp/node_modules/jest-resolve/package.json

To Reproduce
Steps to reproduce the behavior:

Install jest-resolve
Create a resolve.cjs file
Import jest-resolve/build/defaultResolver:

// resolver.cjs

const defaultResolve = require('jest-resolve/build/defaultResolver.js')

Run node resolve.cjs

Expected behavior
It should import without errors.
Link to repl or repo (highly encouraged)
Reproduction repository: https://github.com/talentlessguy/jest-resolve-repro
envinfo

  System:
    OS: Linux 5.10 Manjaro Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Binaries:
    Node: 16.2.0 - ~/n/bin/node
    Yarn: 1.22.10 - ~/.yarn/bin/yarn
    npm: 7.13.0 - ~/n/bin/npm
  npmPackages:
    jest: ^27.0.2 => 27.0.2

You shouldn’t use any stuffs directly from build, that is the recommendation. If you wish to use any internal APIs, you need to request them to be exported in index.js

@ahnpnl thanks for responding quickly!
yeah seems like new Resolver(..., opts) does the same thing
closing then


Integrate plugins with Gradle composite build in Stack

https://docs.gradle.org/current/userguide/composite_builds.html

Duplicate #13.


Add support for Django 2.1

Description
Add Django 2.1 to the testing matrix and documentation.
Motivation and Context
We want to ensure that this library works on Django 2.1.
How Has This Been Tested?
Tested on TravisCI.
Types of changes

[ ] 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 change)

Checklist:

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

Codecov Report

Merging #418 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #418   +/-   ##
=======================================
  Coverage   97.32%   97.32%
=======================================
  Files          14       14
  Lines         672      672
  Branches       93       93
=======================================
  Hits          654      654
  Misses          9        9
  Partials        9        9

Continue to review full report at Codecov.

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


Output Discrepancy in XLA Compiled Models with tf.divide, tf.math.reduce_prod, and tf.cos Involving Extra Node

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.15.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.3 LTS
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
In TensorFlow 2.15.0, a model involving tf.divide, tf.math.reduce_prod, and tf.cos, along with an additional concat node returning, exhibits different outputs under XLA compilation compared to a simpler model without the extra node.
You can reproduce this issue using the Colab notebook I have prepared.
Additional Context
In our efforts to understand and locate the root cause of this issue, we have conducted several tests and experiments.
Removing an Operator: If any one of the operators (tf.divide, tf.math.reduce_prod, tf.cos) is removed from either model, the discrepancy under XLA compilation is no longer triggered.
Removing transposed_concat or replacing with concat from Model2's Return: Omitting or replacing the output transposed_concat will not trigger this error.
Standalone code to reproduce the issue
from typing import Dict
import tensorflow as tf
import pickle
import os
import numpy as np

params = [
tf.random.uniform(shape=[49, 9, 1], dtype=tf.float32),
]
class Model1(tf.keras.Model):
    def __init__(self):
        super().__init__()
        # Tensor objects (with comments for shapes)
        self.p0 = tf.constant(params[0]) # [49, 9, 1] float32

    @tf.function(jit_compile=True)
    def __call__(self, inp):
        # Forward pass logic using TensorFlow operations
        # inp: [7, 5, 49, 1, 1] : float32
        div = tf.divide(inp, self.p0)
        transposed_div = tf.transpose(div, perm=[0, 1, 3, 2, 4])
        red = tf.math.reduce_prod(transposed_div, axis=2)
        cos = tf.cos(red)
        return red, cos,

class Model2(tf.keras.Model):
    def __init__(self):
        super().__init__()
        # Tensor objects (with comments for shapes)
        self.p0 = tf.constant(params[0]) # [49, 9, 1] float32

        # Layers or other Keras model objects

    @tf.function(jit_compile=True)
    def __call__(self, inp):
        # Forward pass logic using TensorFlow operations
        # inp: [7, 5, 49, 1, 1] : float32
        div = tf.divide(inp, self.p0)
        transposed_div = tf.transpose(div, perm=[0, 1, 3, 2, 4])
        concat = tf.concat([transposed_div, transposed_div], axis=2)
        transposed_concat = tf.transpose(concat, perm=[1, 0, 2, 3, 4])
        red = tf.math.reduce_prod(transposed_div, axis=2)
        cos = tf.cos(red)
        return red, cos, transposed_concat

inputs = [
tf.random.uniform(shape=[7, 5, 49, 1, 1], dtype=tf.float32),
]
model1 = Model1()
model2 = Model2()
device = "cpu"
with tf.device(device):
    tf.config.run_functions_eagerly(True)
    out1 = model1(*inputs)
    out2 = model2(*inputs)
    print(f'=========eager_output(version:{tf.__version__})================')
    try :
        for i in range(min(len(out1),len(out2))):
            np.testing.assert_allclose(out1[i].numpy(), out2[i].numpy(), rtol=0.001, atol=0.001, err_msg=f'at checking {i}th')
        print("XLA_eager does not trigger assertion")
    except AssertionError as e:
        print("XLA_eager triggers assertion")
        print(e)
    tf.config.run_functions_eagerly(False)
    out1 = model1(*inputs)
    out2 = model2(*inputs)
    print(f'=========compiled_output(version:{tf.__version__})================')
    try :
        for i in range(min(len(out1),len(out2))):
            np.testing.assert_allclose(out1[i].numpy(), out2[i].numpy(), rtol=0.001, atol=0.001, err_msg=f'at checking {i}th')
        print("XLA_complie does not trigger assertion")
    except AssertionError as e:
        print("XLA_complie triggers assertion")
        print(e)

Relevant log output
=========eager_output(version:2.15.0)================
XLA_eager does not trigger assertion
=========compiled_output(version:2.15.0)================
XLA_complie triggers assertion

Not equal to tolerance rtol=0.001, atol=0.001
at checking 1th
Mismatched elements: 77 / 1715 (4.49%)
Max absolute difference: 0.85310125
Max relative difference: 32.919815
 x: array([[[[-0.067188],
         [ 0.995112],
         [ 0.119131],...
 y: array([[[[-0.067309],
         [ 0.995112],
         [ 0.119131],...
=========RUNNING WITH PICKLE FILES=========== # on AMD CPU
=========eager_output(version:2.15.0)================
XLA_eager does not trigger assertion
=========compiled_output(version:2.15.0)================
XLA_complie triggers assertion

Not equal to tolerance rtol=0.001, atol=0.001
at checking 1th
Mismatched elements: 1080 / 1715 (63%)
Max absolute difference: 1.9984823
Max relative difference: 360.84747
 x: array([[[[ 0.942858],
         [-0.681655],
         [-0.800721],...
 y: array([[[[ 0.738128],
         [-0.681655],
         [-0.800721],...

Hi @GwiHwan-Go ,
I have replicated the reported difference in results with and without jit_compile. Attaching gist for reference.

Hi @Gwihwan-Go,
I reproduced the same issue in TF 2.15.0 and also latest Tensorflow version (TF 2.18.0). The issue might be occuring because XLA optimizations can reorder, approximate, or alter numerical calculations for performance, especially when sensitive operations (like tf.divide, tf.reduce_prod, tf.cos) and complex output nodes (like transposed_concat) interact. This leads to subtle inconsistencies in numerical results. Could you please refer to the gist file for more information.
Thank you.


ucommon: fix error handling compatibility

Compilation fails due to changes regarding the error handling function throw() between C++14 and C++17 Standard. Fixing this is inside the code is a bit more complicated and should be done upstream.
Description of changes
I simply added -std=c++14 to CXXFLAGS as a temporary fix.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

ZHF: #172160
ping @NixOS/nixos-release-managers

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

1 package marked as broken and skipped:

sipwitch

3 packages built:

ccrtp
twinkle
ucommon


ndk/aaudio: Fix link to AudioTrack#write

Fixes https://github.com/rust-windowing/android-ndk-rs/pull/108#discussion_r554393678
Autolinks escape [] resulting in AudioTrack#write(float%5B%5D,%20int,%20int,%20int) which is not resolved to the right anchor on android.com. Using <a> however does not apply escaping rules, allowing the link to work properly.

Ended up fixing it after all, sorry for lots-of-PRs spam :grimacing:

Ended up fixing it after all, sorry for lots-of-PRs spam :grimacing:


Rename unvalid to invalid

Thanks for working on this library! 😄
I think unvalid should be renamed to invalid, as that is the correct term for something not being valid. 😄

Fixed, now.
I already had changed this, but missed the doku: tanks!


Add Coverage

Add codecov badge and coverage report

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9415808). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #366   +/-   ##
=========================================
  Coverage          ?   70.74%
=========================================
  Files             ?       18
  Lines             ?     1685
  Branches          ?        0
=========================================
  Hits              ?     1192
  Misses            ?      493
  Partials          ?        0

Continue to review full report at Codecov.

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


chartjs how to  add dollar sign to Y coordinate and tooltip

I am using chart.js  to set up a chart for month sale amount.
So i want the  Y coordinate and tool-tip of the chart  have a dollar sign($)  before the amount number.
How can i do that?
I am using version 2, and looks like results i google out are all for version 1 which was not working for me.
Thanks

@liucf see the Creating Custom Tick Formats under http://www.chartjs.org/docs/#scales-common-configuration
The tooltips section has information on the callbacks used to create the strings. The one that you need to use is the label callback


Error when using tf.constant to provide input to Keras model.predict

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
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): Linux (Google Colab)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): 1.13.1
Python version: 2.7/3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10
GPU model and memory: K80

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
This is a followup to the issue  raised in MIT's TensorFlow labs. When I use a TensorFlow tensor created using tf.constant as input to Keras model.predict it gives an error. However, when I directly feed in the same tensor to the Keras model it gives output as expected.
Describe the expected behavior
According to the documentation provided, model.predict should also be able to take a TensorFlow tensor as input.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
# Import relevant packages
from tensorflow.keras import Sequential
from tensorflow.keras.layers import Dense

# Define the number of inputs and outputs
n_input_nodes = 2
n_output_nodes = 3

# First define the model
model = Sequential()

'''TODO: Define a dense (fully connected) layer to compute z'''
dense_layer = Dense(n_output_nodes, input_shape=(n_input_nodes,),activation='sigmoid') # TODO

# Add the dense layer to the model
model.add(dense_layer)

Now when I do prediction using:
# Test model with example input
x_input = tf.constant([[1.0,2.]], shape=(1,2))
'''TODO: feed input into the model and predict the output!'''
print(model.predict(x_input)) # TODO

I get following error:

InvalidArgumentError: In[0] is not a matrix. Instead it has shape [2]
[[{{node MatMul_3}}]] [Op:StatefulPartitionedCall]

When I use directly feed the tensor:
# Test model with example input
x_input = tf.constant([[1,2.]], shape=(1,2))
'''TODO: feed input into the model and predict the output!'''
print model(x_input)

I get the expected behaviour:

tf.Tensor([[0.31025296 0.48313126 0.7821198 ]], shape=(1, 3), dtype=float32)

@aamini also had the same behavior. Is this expected in TensorFlow 2.0 or a bug?. If it is expected, please update the documentation.

Thanks for the bug report @sibyjackgrove, it looks like this is fixed in the latest tf-nightly as I'm unable to reproduce

Thanks for update @omalleyt12 will try it out.


how to aggregate gradients by weight

tf.gradients has a parameter aggregation_method. As default, it will sum up all the gradients. What should I do if I want to sum up all the gradients by weight? To be more specific, I want to apply a weight to each gradient, then sum them up. This weight may also comes from a tensorflow variable. I asked a question about this in stackoverflow and attached a minimal code snippet.
http://stackoverflow.com/questions/42464742/how-to-weight-gradient-in-different-examples

Stack overflow is the correct place for that question.


Cocaine gem is deprecated

hi!
cocaine is deprecated and have been renamed Terrapin:
https://github.com/thoughtbot/cocaine
Upgrading to Terrapin is expected to be as simple as replacing the Cocaine constant with Terrapin.
Cocaine::CommandLine.new("echo", "hello")

should become
Terrapin::CommandLine.new("echo", "hello")

This is not a big issue, but this occurs a noisy log everytime we launch a server
Thank you !

Nevermind, saw the pull request too late:
https://github.com/jonbuda/miro/pull/37


symbolize by water quality variable

Running the mapping tools that symbolize by water quality variable has an error in arcmap.
Traceback (most recent call last):
  File "<string>", line 648, in execute
  File "<string>", line 114, in insert_layer
  File "C:\Python27\ArcGIS10.4\lib\site-packages\amaptor\functions.py", line 68, in make_layer_with_file_symbology
    layer.dataSource = feature_class
  File "c:\program files (x86)\arcgis\desktop10.4\arcpy\arcpy\arcobjects\_base.py", line 89, in _set
    return setattr(self._arc_object, attr_name, cval(val))
RuntimeError: LayerObject: Set attribute dataSource does not exist

Failed to execute (GenerateMonth).

I've resolved this issue in new versions of amaptor (something that requires one line of code in Pro required a huge function in ArcMap - I really like Pro :)). Updating amaptor to the latest version will resolve this.
Some new issues in mapping have cropped up though, but they're unrelated, so I'll close this issue and file a new one. Mapping still isn't perfect in ArcMap, but the map generates properly for the most part (a few variables have issues).


ftINIT helpers

Main improvements in this PR:
*Added help functions that are used together with ftINIT in RAVEN. A pull request containing the ftINIT implementation has been done separately in RAVEN, but the changes should not be dependent on each other.
I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Selected develop as a target branch

Ok, I'm still going through some of the details on this PR, though so far it looks ok to me. But why are the yaml conversion tests failing?

Yeah, I don't get that either, I cannot see that I have done anything with that. What I understood from the error messages is that it fails to allocate some resource for running them?

Ok, I'm still going through some of the details on this PR, though so far it looks ok to me. But why are the yaml conversion tests failing?

Now resolved.


Remove $cursor selector?

Hi @Yomguithereal ,
I am working on the article and now I introduce the {$cursor: ['path']} before facets. What I notice though is that $cursor is not currently doing what you want it to do.
var MyComp = React.createClass({
  mixins: [branch],
  cursors: {
    projects: ['projects', {$cursor: ['currentProjectId']}]
  }
});

There are two problems here:

The cursor does not update when the currentProjectId updates (Which we agreed is a bug)
If the project updates inside the projects cursor it does not update either? (Which is also a bug?)

The thing is that a facet solves this issue and more clearly defines what cursors are active. Thought I like what $cursor does, it just makes the API more complex and hides its implementation details compared to:
var projectFacet = {
  cursors: {
    projects: ['projects'],
    id: ['currentProjectId']
  },
  get: function (data) {
    return data.projects[data.id];
  }
}

I am a big fant of writing more syntax to reduce API alternatives and hiding implementation details. The facet syntax tells the developer what it actually does, which the $cursor does not.
Anyways, just my 2 cents. Let me know if you want the $cursor in the article, but I think it is wise to move it to a "you can also do it like this" later on... as FACETS is the really awesome thing here :-)

My opinion here is that $cursor is just sugar. It's just a hidden bonus of the library, not one of its main feature like facets are. As such, I do not document them very conspicuously (even more since I should fix them ;-)). I wouldn't showcase them in a blog article, for instance. To me it's more of a "you can also do it like this" thing indeed.

Cool! I agree :-)
On Sat 25 Apr 2015 at 14:16 Guillaume Plique<EMAIL_ADDRESS>wrote:

My opinion here is that $cursor is just sugar. It's just a hidden bonus
of the library, not one of its main feature like facets are. As such, I do
not document them very conspicuously (even more since I should fix them
;-)). I wouldn't showcase them in a blog article, for instance. To me it's
more of a "you can also do it like this" thing indeed.
—
Reply to this email directly or view it on GitHub
https://github.com/Yomguithereal/baobab/issues/204#issuecomment-96189809
.

I ran into into something similar. I tried writing a facet like this, which didn't work (excuse the CS syntax):
selectedUserOrders:
  cursors:
    selectedOrders: ['users', {$cursor: ['selectedUserId']}, 'orders']
  get: (data) ->
    data.selectedOrders

Maybe it was wishful thinking that it would realize that it should listen to updates on 'selectedUserId'? :smile:. This works though:
selectedUserOrders:
  cursors:
    users: ['users']
    selectedUserId: ['selectedUserId']
  get: (data) ->
    data.users[data.selectedUserId]?.orders

Would be nice to have the former because the use and intent of selectedUserId are co-located, whereas in the latter case I have not constrained myself at all with those cursor declarations; I could use them for anything when really I'm just going to use it to build a path of sorts.
BTW, fantastic library! Thanks so much!

Thanks @JohnAmican.
The $cursor not listening to the correct paths is clearly a bug (related to #196) and shall be corrected in a near future.

On a side note @christianalfoni, @JohnAmican, @RJ: did you have time to test the $cursor thingy and do you think it's really valuable over facets? The code associated to the feature is a bit messy and hard to clean so I was wondering whether I should keep it.

i'm currently using a combination of facets and cursors defined by a function that can access this.props.
Haven't needed the $cursor thing since i've done that, but i'm only testing this on a small experimental project. I am much more interested in a general nested facet api (alluded to in #226) than the $cursor thing :)

Hi there,
My opinion is that $cursor should be removed. It is easier to learn Baobab if you only have Facets to do dynamic stuff. And Facets can do what $cursor does and Facets does it "inside the application state", not in the components, which I think is the right place to do it :-)

Question for you @christianalfoni, @RJ: would you go to v2 by removing $cursor or do you think it is benign enough not to generate a semver major?

Oh... good question. I do not think there is a right answer for that one. Technically it is v2 in regards of breaking API? But its such a minor break I believe By default NPM only updates minor versions anyway so nobody should have a "sudden break".
So to conclude, fits more with a major version change and "NOTE!!!" on release info I think :-)

By major version change you mean a minor 1.2.0 with a NOTE or a 2.0.0?

Ah, sorry, yeah... 1.2.0 with a NOTE. NPM updates patch versions by default.

$cursor is now dropped in V2.


Value binding only first time

Hello,
i have problem that checkbox value is set only first time opening ckeditor.
If i go to read second time value is not set.
This function is called 3 times. Sometimes is value seted, sometime is not.
Seted is always if i add debugger line and pause function, than run again.
Have You any idea ? Version of angular si 2 newest ...
/**
 * Implements ControlValueAccessor
 */
writeValue(value) {
    debugger; ----> FROM 3 TIMES IS ACCESSED, TWO TIMES VALUE IS NOT UNDEFINED
    this.value = value;
    if (this.instance)
        this.instance.setData(value);
}

One thing, what this line is doing ?
@Reflect.metadata('parameters', [null, [new OptionalMetadata()]])

Hi,
I don't have lot of of time to work on this project atm and I don't have tested with the last version of Angular 2.
@Reflect.metadata('parameters', [null, [new OptionalMetadata()]])
This make a depency injection @Optional in the component's constructor.
I'll try to examine your problem soon.

Hello,
Can you share a sample repo or a plunker to help me reproduce your problem ?
You can start with one these :

ES2016 and JSPM : https://github.com/chymz/angular2-jspm-seed/tree/ng2-ckeditor
TypeScript with cli : https://github.com/chymz/ng2-cli-ckeditor-sample
Plunker sample : https://embed.plnkr.co/hnB0R3/

Thanks !

No activity for 1 month


parsing.csv error ಠ_ಠ

in fora:
let s =  """
        A,B,C
        1,2,3
        4,5,6
        7,8,9
        """
let res = parsing.csv(s)
res

parsing.csv thinks the first row is bad for some reason and leaves it out
I hit this on the python side.

I'd say this is probably low-priority, since most examples will be left-justified


Show search results stats in new sidebar

Description
This adds a sidebar to the new library and public pages which shows stats on the current search results.

The metadata values are clickable. The effect in future will be to filter the current results. (Question: will it add a filter to the current filter set or replace the current set?)
The sidebar shows for the projects view as well, but not visualizations, because it not clear how or why we would summarize their metadata.

The data for both views currently comes from the same api calls that the DiscoveryView makes. That means they only summarize what is currently loaded, not all possible results! (@tfrcarvalho and I have discussed other data approaches)
See @happyimadesignr mocks https://chanzuckerberg.invisionapp.com/share/EAQPA523SD9#/screens/348888814 .
The main differences are that

Some of the stats are missing such as "non-host reads". It is not clear how to get these both efficiently for projects and samples, because they are not returned in the initial fetches.
There is no date graphic. This we can do in a later PR. (Note: I think treating date as a text field is still useful.)
"Sample info" host and tissue are not shown. I'm not sure what these mean given that metadata also appears below. @happyimadesignr ?
The "summary info / similar data" tabs do not exist. This will come in a later PR when similar data is ready.
I renamed "Sample info" to "Overall" to better reflect its contents.
I added a count of projects.
The whole page width is different, pending addition of the left hand filters.
I sorted the metadata values alphabetically. (Question: should this be by frequency?)

Test and Reproduce
Outline the steps to test or reproduce the PR here.

go to /library
wait for samples
see sidebar filled in with data
click on project tab
see sidebar filled in
go to /public
repeat 2 thru 5 above

Thanks for sharing! So neat to see all the different tissue types already. Thanks for listing out things you’re still working on.

To answer the filter question, it should add a filter to the current filter set rather than replace it.
You’re right, the host and tissue aren’t needed in the overview as they are in the section below.
Keep in mind for later, this panel will also show in Browse and inside a project.
Why does it say host is unknown, when it's listed in the table?
Why are the dates created only one, where you can see on the left there were uploads from different times?
We’ll also need to toggle to open and close this panel.
I owe you colors for the bar charts, they will be our categorical colors. Maybe @tfrcarvalho can point you to those.
I owe you some specs too for details of spacing and sizing

@happyimadesignr

Keep in mind for later, this panel will also show in Browse and inside a project.

I hadn't thought of that. Can you point me to any mocks for those?

Why does it say host is unknown, when it's listed in the table?

I'm converting blank values from the database into "unknown". I have no idea where they are coming from.

Why are the dates created only one, where you can see on the left there were uploads from different times?

This was a bug. Good catch!

We’ll also need to toggle to open and close this panel.

Ok I will add this now.


Integrate AI

I don't want to send user data to OpenAI. I'm waiting until it's more feasible to run LLMs locally.

https://webllm.mlc.ai/


mediapipe warning

When the Processor class is imported, all possible processors are also imported. This results in this warning being displayed, even though I have no intention of using the processor that requires mediapipe. Would it be possible to move this warning into runtime? Such that the warning is only displayed if one tried to use the relevant processor?

The same is true of:
  /home/user/mambaforge/envs/env/lib/python3.10/site-packages/controlnet_aux/open_pose/hand.py:4: DeprecationWarning: Please use `gaussian_filter` from the `scipy.ndimage` namespace, the `scipy.ndimage.filters` namespace is deprecated.

which comes from open_pose, and
  /home/user/mambaforge/envs/env/lib/python3.10/site-packages/timm/models/registry.py:4: DeprecationWarning: Importing from timm.models.registry is deprecated, please import via timm.models
    warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.models", DeprecationWarning)

which comes from segment anything.

I would maybe not import the processor in this case and just directly import each sub module

When I import the specific processor (e.g., from controlnet_aux.open_pose import OpenposeDetector), I still get this output:
/home/richardbrown/mambaforge/envs/inpaint_dreambooth/lib/python3.10/site-packages/controlnet_aux/mediapipe_face/mediapipe_face_common.py:7: UserWarning: The module 'mediapipe' is not installed. The package will have limited functionality. Please install it using the command: pip install 'mediapipe'
  warnings.warn(
/home/richardbrown/mambaforge/envs/inpaint_dreambooth/lib/python3.10/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_5m_224 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_5m_224. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/richardbrown/mambaforge/envs/inpaint_dreambooth/lib/python3.10/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_11m_224 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_11m_224. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/richardbrown/mambaforge/envs/inpaint_dreambooth/lib/python3.10/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_21m_224 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_21m_224. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/richardbrown/mambaforge/envs/inpaint_dreambooth/lib/python3.10/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_21m_384 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_21m_384. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/richardbrown/mambaforge/envs/inpaint_dreambooth/lib/python3.10/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_21m_512 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_21m_512. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)

I think this is because everything is imported in the base level __init__.py.


convert all arrays in a dataset into the same unit

Hi,
If I have a quantified Dataset ds, trying to convert all arrays in the Dataset into the same unit yields an error:
>>> import xarray as xr
>>> import pint_xarray
>>> ds = xr.Dataset({'test': xr.DataArray([1,2,3], attrs={'units': 'kg'})}).pint.quantify()
>>> ds.pint.to('g')
~/.local/lib/python3.8/site-packages/pint_xarray/accessors.py in to(self, units, **unit_kwargs)
    639             b        (x) float64 <Quantity([-1000.  -750.  -500.  -250.     0.], 'gra...
    640         """
--> 641         units = either_dict_or_kwargs(units, unit_kwargs, "to")
    642
    643         return conversion.convert_units(self.ds, units)

~/.local/lib/python3.8/site-packages/pint_xarray/accessors.py in either_dict_or_kwargs(positional, keywords, method_name)
     90     if positional is not None:
     91         if not is_dict_like(positional):
---> 92             raise ValueError(
     93                 f"the first argument to .{method_name} must be a dictionary"
     94             )

ValueError: the first argument to .to must be a dictionary

The workaround is to generate a temporary dictionary like so:
>>> ds.pint.to({x: 'g' for x in ds.keys()})
<xarray.Dataset>
Dimensions:  (dim_0: 3)
Dimensions without coordinates: dim_0
Data variables:
    test     (dim_0) float64 <Quantity([1000. 2000. 3000.], 'gram')>

However, I think that is kind of ugly. Given that converting a whole dataset to the same unit is rather intuitive and (I guess) common, I think it would be great if Dataset.pint.to supported this directly.
I could also have a look at writing a patch, but I'll be at pydata later this week, so I won't be able to look at this until next week.
Cheers,
Mika

when designing this method I considered Dataset objects to rarely have a single shared dimensionality. I guess that is not true, especially outside the earth sciences?
My only concern when implementing this is that the error reporting could be a pain: there's only a single exception per incompatible dimensionality so we'd have to check the compatibility separately.

I could also have a look at writing a patch

yes, please. And don't worry about being slow, we're not in a hurry to release the next version.

Given that converting a whole dataset to the same unit is rather intuitive and (I guess) common

I'm not sure how common this is - single-variable datasets are normally just represented as DataArrays, and multi-variable datasets are (in my personal experience) normally variables with different units, but shared coordinates.
There might be another way to do this currently which is possibly slightly nicer too? Something like
for var in ds:
    var.pint.to('unit')

I would be interested to hear how you think the API could be improved though :)

This is a job for map! ds.map(lambda x: x.pint.to("unit")

thanks for the hint, @dcherian, that does indeed work and would be a bit easier to remember than creating a temporary dict (which would convert only the data variables). If we go for this, it might be better to declare this a documentation bug and add the map trick to the examples section of the Dataset.pint.to docstring.

I'm not sure how common this is - single-variable datasets are normally just represented as DataArrays, and multi-variable datasets are (in my personal experience) normally variables with different units, but shared coordinates.

Maybe my use case (one Dataset of DataArrays each describing emissions of one gas) is also special, but I found I need to convert a whole multi-variable Dataset quite often, sometimes just to convert a Dataset into a DataArray, sometimes to normalize to a standard unit before 'dequantify'ing and storing the Dataset as a CSV.

thanks for sharing your use case, @mikapfl, this makes it so much easier to decide whether or not to include this shortcut.
What do you think about the Dataset.map trick? It's definitely a bit more to write than the syntax you propose but doesn't require changing anything.
Just for reference, the reason why we have been so reluctant to add this is that if it turns out to be a bad decision later we would have to go through a deprecation cycle to remove it. Then again, the library is intentionally marked with the alpha trove classifier, so we would be able to keep the deprecation cycle fairly short. I guess we can try introducing the new syntax as a experimental feature, and roll back if we notice there's anything wrong with it. Thoughts, @xarray-contrib/pint-xarray-devs?

I think ds.map(lambda x: x.pint.to('unit')) is more readable than ds.pint.to({x: 'unit' for x in ds.keys()}), so just documenting that would also be fine. However, it was surprising to me that ds.pint.to('unit') didn't work, I instinctively always try that first before remembering I have to treat Datasets differently than DataArrays.
Either way you decide, I can prepare a pull request. (-:

upon consideration, I think converting all data variables to the same unit if just a string / unit object were passed makes Dataset.pint.to a bit more like DataArray.pint.to, so if you still need this feel free to send in a PR (I'm sorry for taking so long to decide)


Will the discussion ever come back?

What is your question?
I quite liked the PsychEngine discussion.

if it's not coming back then am jumping off a cliff

if it's not coming back then am jumping off a cliff

me too

Again, ShadowMario confirmed that the discussions are not coming back due to how hard it is to moderate.

if it's not coming back then am jumping off a cliff

me too

miter ef en ef is beck??

Discussion is best place with codes
I hope that there will be people who will create discussions

https://github.com/mayo78/PSYCHDISCUSSIONS/discussions/1


Doesn't work with secured service over HTTPS - include token in map service request

My portal and ArcGIS Server are secured over HTTPS (ArcGIS Server federated with Portal). I created a web map including the ENC service: https://servername/ags/rest/services/ENC/MapServer/exts/Maritime%20Chart%20Service/MapServer.
In Web AppBuilder I have added the Maritime Display widget.  As soon as I click on the Maritime Display widget my ENC service goes away and I can only see the basemap.  After some digging I realized that the request for the map service tiles is not including a token so the tiles return empty (an error message, "Token Required" is returned).
The widgets need to be able to work with ENC map services over HTTPS.

I've tried this again and it is working.  I will update this issue if I experience it again.


Circle QRCode generation

Image Generation
I want to display generated QRCode image with bootstrap circle. but when I try to put it in circle wrapper of bootstrap the scanner unable to read.
Can we make the output image as circle frame like https://i.pinimg.com/564x/8a/a0/05/8aa00528c91b6443d59ad55daa130e98.jpg
Thank you

Hi @Sopheakmorm ,
currently there is no rendering class, which creates round QR code graphics. But feel free to write your own renderer. Therefore have a look at the QRCode class (https://github.com/codebude/QRCoder/blob/master/QRCoder/QRCode.cs) as also at the AbstractQrCode class (https://github.com/codebude/QRCoder/blob/master/QRCoder/AbstractQRCode.cs). As you can see all renderers work with the abstract class. So create a new class like "RoundQRCode.cs" which implements AbstractQRCode and write the rendering logic to draw a round QRCode. Additional information can be found here: https://github.com/codebude/QRCoder/wiki/Advanced-usage---QR-Code-renderers
If you don't want to write your own class, you can try to take the QRCode graphic, and draw a white border around it via Graphics class from .NET framework. Thus the circle class of Bootstrap should only cut off the white space and not the QRCode itself, which should keep the code readable as a result.

Hi @codebude,
I will create RouldQRCode.cs implementation and then make pull request with you.
Thank you anyway.

@Sopheakmorm did you have any luck making the round render?

Hi @bugnuker. It's success.

@Sopheakmorm do you have any example of your results? I don't intend to see what you wrote (unless you want to share) but rather your results while extending qrcoder.

Hi @mikewcameron ,
never got a PR from @Sopheakmorm, but meanwhile @nigelthorne setup the ArtQRCode, which was embedded and overhauled just last week. So you might want to have a look...

ArtQRCode wiki (how to use)
CI-build package

The ArtQRCode will be part of the next official QRCoder release (1.4.2). If you want to test it right now, either checkout the Github repository and compile it yourself or simply use the GithubPackages CI-package linked above. (If you need help with GithubPackages, check this wiki section and the blog post linked there.)

Hi @mikewcameron, it was long time ago. let me find it first.

The round codes are just the square codes with some extra stuff around the edges and circles used for the corners.  I like the "merge the dots into lines" look about it.


Create marketing and PR for this repo

Post a link with some screenshots and try to attract users, testers & possibly contributors from this Slack channel

Post the link also here.

Also cooment on reddit here


Access a Classic Schema from SAP Business Application Studio

Tutorials: https://developers.sap.com/tutorials/hana-cloud-access-cross-container-schema.html
I cannot create the classic schema "PLAIN" due to "insufficient privilege". Is there a way around this?

Also, your screenshots had a DB called HANA_Cloud_trial.... which is not available on my HANA DB Explorer. Did I miss any steps?

I suspect that you are not connect in the Database Explorer with the correct user.  You are likely using an HDI container connection.  For this step in the tutorial you must use a connection via the user DBADMIN. Did you open the Database Explorer via the HANA Cloud Management screen as described in step 1?
https://developers.sap.com/tutorials/hana-cloud-access-cross-container-schema.html#3acab07e-02a5-4d5d-bc32-59ddbc48e6b5
And are you sure you are open the SQL Console via the entry for the DBADMIN user as in step 2?
From the SQL Console you can issue SELECT CURRENT_USER FROM DUMMY to verify your connection and user.  If you are using DBADMIN then it certainly should have the authorization to perform the operations in this step.

Thank you so much. I was able to navigate there using the steps in your video. No wonder you advised we bookmark it, a bit tricky to find.
On Thursday, February 25, 2021, 03:17:42 PM EST, Thomas Jung<EMAIL_ADDRESS>wrote:
I suspect that you are not connect in the Database Explorer with the correct user. You are likely using an HDI container connection. For this step in the tutorial you must use a connection via the user DBADMIN. Did you open the Database Explorer via the HANA Cloud Management screen as described in step 1?
https://developers.sap.com/tutorials/hana-cloud-access-cross-container-schema.html#3acab07e-02a5-4d5d-bc32-59ddbc48e6b5
And are you sure you are open the SQL Console via the entry for the DBADMIN user as in step 2?
From the SQL Console you can issue SELECT CURRENT_USER FROM DUMMY to verify your connection and user. If you are using DBADMIN then it certainly should have the authorization to perform the operations in this step.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Implement proper cancellation

Need to thread a CancellationToken so that we can shutdown the engine when needed.

done


Handling of client context for remotely handled messages

Currently, the entire set of workflow functions run in a single application sandbox. As a result, when the first function of the workflow is triggered, the triggering client context is created at the handling sandbox instance.
In the future, it is possible that the client context remains at one sandbox instance, whereas the remaining functions are instantiated at one or more remote sandbox instances. If one such remotely executing function instance is the last one in the workflow, the result cannot be returned to the original client because the remote sandbox does not have the correct client context (i.e., client connection).
Furthermore, in the current state, any session function update message may be redirected to any sandbox instance, which may not necessarily be the one running the session function instances. Although the message can be delivered via the metadata for session function instances, any returned response will fail as described in the above paragraph.
One solution is to make client connection state transfer from the originating sandbox's frontend to the last one, which may not be straightforward to do.
Another solution is to send back the final result to the originating sandbox where the correct client context is still kept. In this proposal, the following would need to be done:

For any incoming message, the sandbox frontend attaches its address as metadata to the message (i.e., "__client_origin").
Outgoing messages (i.e., results published to "end" topic) are retrieved by the sandbox frontend, which then finds the correct client context. In this case, if there is no such client context, the frontend will check the metadata to find the originating sandbox frontend address. The sandbox frontend will then send a special message to ther originating sandbox frontend (i.e., "X-MFN-Action": "Remote-Result").
The originating frontend will handle the special message by extracting the execution id and the result value. It will then look up the correct client context using the execution id and return the response to the client.

Thoughts, comments?

It should work.  One comment: since the interaction happens across
different sandboxes and even hosts, would it be possible to use service
mesh or data layer to exchange metadata (and context)?
On Tue, Oct 13, 2020 at 12:37 PM Istemi Ekin Akkus<EMAIL_ADDRESS>wrote:

Currently, the entire set of workflow functions run in a single
application sandbox. As a result, when the first function of the workflow
is triggered, the triggering client context is created at the handling
sandbox instance.
In the future https://github.com/knix-microfunctions/knix/wiki/Roadmap,
it is possible that the client context remains at one sandbox instance,
whereas the remaining functions are instantiated at one or more remote
sandbox instances. If one such remotely executing function instance is the
last one in the workflow, the result cannot be returned to the original
client because the remote sandbox does not have the correct client context
(i.e., client connection).
Furthermore, in the current state, any session function update message may
be redirected to any sandbox instance, which may not necessarily be the one
running the session function instances. Although the message can be
delivered via the metadata for session function instances, any returned
response will fail as described in the above paragraph.
One solution is to make client connection state transfer from the
originating sandbox's frontend to the last one, which may not be
straightforward to do.
Another solution is to send back the final result to the originating
sandbox where the correct client context is still kept. In this proposal,
the following would need to be done:

For any incoming message, the sandbox frontend attaches its address
as metadata to the message (i.e., "__client_origin").
Outgoing messages (i.e., results published to "end" topic) are
retrieved by the sandbox frontend, which then finds the correct client
context. In this case, if there is no such client context, the frontend
will check the metadata to find the originating sandbox frontend address.
The sandbox frontend will then send a special message to ther originating
sandbox frontend (i.e., "X-MFN-Action": "Remote-Result").
The originating frontend will handle the special message by
extracting the execution id and the result value. It will then look up the
correct client context using the execution id and return the response to
the client.

Thoughts, comments?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/knix-microfunctions/knix/issues/88, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQSEDB7EJ2JNIP7FVRURRDSKQUVLANCNFSM4SOSSHJQ
.

metadata is attached to each message as it passes through the functions of the workflow.
The interaction is assuming that the originating sandbox is found via some metadata kept by the platform (in this case, the message metadata that's flowing; in the case of session function instances, it's the data layer). That lookup might also happen at the routing layer (e.g., service mesh), but I think that would mix the 'network layer' with the 'platform layer', and may not be ideal, but I may have misunderstood something.
As for the context, I am referring to the client connection information (e.g., TCP state). Not sure whether that's straightforward to transfer at all.

Hi Ekin,
don’t know if that helps, but the context object recently has been extended to enable a client to transfer information to the function:
client_context – (mobile apps) Client context that's provided to Lambda by the client application.
o   client.installation_id
o   client.app_title
o   client.app_version_name
o   client.app_version_code
o   client.app_package_name
o   custom – A dict of custom values set by the mobile client application.
o   env – A dict of environment information provided by the AWS SDK.
So with the above we can already transfer metadata from a client to any function  in form of a custom dict.
BR Klaus
From: Istemi Ekin Akkus<EMAIL_ADDRESS>Sent: Tuesday, October 13, 2020 10:53 PM
To: knix-microfunctions/knix<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [knix-microfunctions/knix] Handling of client context for remotely handled messages (#88)
metadata is attached to each message as it passes through the functions of the workflow.
The interaction is assuming that the originating sandbox is found via some metadata kept by the platform (in this case, the message metadata that's flowing; in the case of session function instances, it's the data layer). That lookup might also happen at the routing layer (e.g., service mesh), but I think that would mix the 'network layer' with the 'platform layer', and may not be ideal, but I may have misunderstood something.
As for the context, I am referring to the client connection information (e.g., TCP state). Not sure whether that's straightforward to transfer at all.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/knix-microfunctions/knix/issues/88#issuecomment-708002694, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADFTJEMD76UFH43X67LFSOTSKS433ANCNFSM4SOSSHJQ.

Yes, we have a similar encapsulation/decapsulation mechanism that includes other metadata that is not exposed to the user code.
The context I am referring to here is the "client connection" (i.e., HTTP request) that was used to start the workflow execution, which is available at the originating sandbox's frontend.


tests: add basic verify test

Codecov Report

Merging #63 (84c2d22) into master (700b4a6) will increase coverage by 1.32%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #63      +/-   ##
==========================================
+ Coverage   44.98%   46.31%   +1.32%
==========================================
  Files          28       28
  Lines        1107     1099       -8
  Branches      139      136       -3
==========================================
+ Hits          498      509      +11
+ Misses        585      563      -22
- Partials       24       27       +3

Impacted Files
Coverage Δ

src/commands/verify.ts
29.87% <100.00%> (+14.57%)
:arrow_up:

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Allow user to login to a subdomain

What was added:

Add settings cog to the
Create login modal and connect to existing autologin function when clicked.

What wasn't:

A button for yes/no was not possible because the nested component does not have access to the close function.
Does not have option to open in new window.

Missing translations.

Closes #340


Question about CategoryValueEncoder and ContinuousValueEncoder for value encoder

Hello, first thanks to the creators for the good GitHub repo!
I have one quick question regarding the value encoder that should be used for binned input data. From the paper, it seems CategoryValueEncoder is more appropriate but from the tutorials  Tutorial_Integration.py and Tutorial_Annotation.py it seems that both encoders can be used. Is there any preference of one encoder over the other for binned input data?

+1

Hi, you can use the default settings in the tutorials. We use continuous MLP as binned value encoder. In the paper, we also stated as "We use fully connected layers, denoted as embx, for the binned expression values to enhance expressivity. This choice enables the modeling of the ordinal relation of gene expression values."


[Autocomplete] Return key clears currently selected option

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
After selecting an option, if you press the "enter" (return) keyboard key, the value is cleared.
Expected Behavior 🤔
If wrapped in a form element, the return key should trigger a submit of that form.
Possibly, if the disableClearable prop is set to false then the return key could be seen as clicking the "X" button to clear the field.  If it is set to true then it shouldn't clear anything!
Steps to Reproduce 🕹
It's present on all of the demos on https://material-ui.com/components/autocomplete/ if you select an option for any of the demos and then press the "enter" key, the value is removed/cleared.
Context 🔦
I have a form with a single autocomplete field, the only other action is a button to submit the form.
After interacting with the autocomplete field and selecting a value, I wanted to trigger the form submit by using the "enter" key, rather than tabbing to the submit button and then pressing "enter".
Using the "enter" key to submit a form is expected behaviour (for me at least!), and having it clear the current field is the opposite of what I was expecting.

@chapmanio Thank you for the bug report! Yeah, it's not great!
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index 72d7c84c3..2a447c1a1 100644
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -527,7 +527,7 @@ export default function useAutocomplete(props) {
         handleFocusTag(event, 'next');
         break;
       case 'Enter':
-        if (highlightedIndexRef.current !== -1) {
+        if (highlightedIndexRef.current !== -1 && popupOpen) {
           // We don't want to validate the form.
           event.preventDefault();
           selectNewValue(event, filteredOptions[highlightedIndexRef.current]);

What do you think of this fix? Do you want to submit a pull request? :)


The spec for header union operations seems incomplete

First, it only lists two operations, setValid and setInvalid.
Second, there is no discussion about the semantics of assigning invalid fields. I recall we had a long debate about the meaning of:
header_union HU { H1 h1; H2 h2; }
HU u;
H1 h;
h.setInvalid();
u.field =h;

The spec does not say whether this invalidates the valid fields of the union.
Notice that the compiler expands a header union into a field-by-field copy:
HU u1; HU u2;
u1 = u2;

is translated to
u1.h1 = u2.h1;
u1.h2 = u2.h2;

This is correct only if copying invalid headers does not disturb the valid ones.

However, the spec implies that this is not true.

@mbudiu-vmw wrote: "Second, there is no discussion about the semantics of assigning invalid fields."
It appears to me that the spec if quite explicit on this topic.  Quoting from Section 8.19 "Operations on Header Unions" below:
We can understand an assignment to a union field

u.hi = e
as equivalent to

  u.hi.setValid();
  u.hi = e;
if e is valid and

  u.hi.setInvalid();
otherwise.

If I am interpreting that correctly, then your example code in the original comment above:
header_union HU { H1 h1; H2 h2; }
HU u;
H1 h;
h.setInvalid();
u.field =h;

The spec explicitly says that the HU should end in a state where all of its members are invalid.
How can that section of the spec be interpreted otherwise?

The spec does not explain whether an existing valid field is invalidated when assigning a different field with an invalid value. Either interpretation would be possible.

Please read the entire section on operations on header unions and tell me if you still believe it is open to interpretation.  I don't see how it is.  For example, see this text:
More formally, if u is an expression whose type is a header union U with fields ranged over by hi, then the following operations can be used to manipulate u:
u.hi.setValid(): sets the valid bit for header hi to true and sets the valid bit for all other headers to false, which implies that it is unspecified what value reading any member header of u will return.
u.hi.setInvalid(): if the valid bit for any member header of u is true then sets it to false, which implies that it is unspecified what value reading any member header of u will return.

If you mean that this phrase is ambiguous "if the valid bit for any member header of u is true then sets it to false", I believe the intent when it was written was more explicitly the following.
"assign false to the valid bit for every member header of u"
I would be open to changing that sentence to be more explicit if you think it is open to interpretation.

Fixed by #1220

Closing this issue, as it appears to have been resolved by the commit mentioned by Mihai above.


Using Windows Forms in PS 7 Unexpected behaviour and errors

System Details Output
### VSCode extensions:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>

### PSES version: <IP_ADDRESS>

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Issue Description
When trying to use Windows Forms in a Powershell script I get errors that I don't get when running the same script/lines in Powershell ISE
Expected Behaviour
Running this:
# Init PowerShell Gui
Add-Type -AssemblyName System.Windows.Forms

# Create a new form
$LocalForm                    = New-Object system.Windows.Forms.Form

# Define the size, title and background color
$LocalForm.ClientSize         = '500,300'
$LocalForm.text               = "LazyAdmin - PowerShell GUI Example"
$LocalForm.BackColor          = "#ffffff"

# Display the form
[void]$LocalForm.ShowDialog()

Should run smoothly without any errors.
Actual Behaviour
However, I get the following errors:

SetValueInvocationException:
Line |
   8 |  $LocalForm.ClientSize         = '500,300'
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception setting "ClientSize": "Cannot convert the "500,300" value of type "System.String" to type "System.Drawing.Size"."

SetValueInvocationException:
Line |
  10 |  $LocalForm.BackColor          = "#ffffff"
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception setting "BackColor": "Cannot convert the "#ffffff" value of type "System.String" to type "System.Drawing.Color"."

I get it to work with the following changes :
$LocalForm.ClientSize         = New-Object System.Drawing.Size(500,300)
$LocalForm.text               = "Azure VM Decommission"
$LocalForm.BackColor          = [System.Drawing.Color]::White

Notice that if I tried to use:
$LocalForm.BackColor          = New-Object System.Drawing.Color("White")
I would get:
 A constructor was not found. Cannot find an appropriate constructor for type System.Drawing.Color.
So I had to use
$LocalForm.BackColor          = [System.Drawing.Color]::White

/cc @TylerLeonhardt Have you any thoughts about the issue?

@DanteNahuel do you get the same result running your code in a PowerShell 7 console outside of VS Code?

@TylerLeonhardt
Indeed, same errors.

This seems to be a type system thing; PowerShell isn't automatically processing the type lookup to coerce the constructor arguments to constructor calls.
In the case of System.Drawing.Size there is a constructor, so I wonder if this occurs because it's a struct.
In the case of System.Drawing.Color, there's no constructor but there is a ColorConverter.
@SteveL-MSFT and @daxian-dbw and possibly @vexx32 might know if changes have been made for coercions relating to this.

Sorry, It is known issue in .Net Core 3.1 and we get the fix with .Net Core 5.0 only. See #10869

I wonder if it's related to the TypeConverter changes that we ran into before with some of the System.Drawing.Point casts from string?

@vexx32 In the repo is a link to .Net Core 3 code where we can see full list affected Type converters.

@iSazonov so there's no fix currently?
Or do we fix it by installing .net core 5.0 in the running system?
I'm sorry if this is a silly question, I'm very new to Dev

@DanteNahuel While I am working on fix .Net Core team fixed this for 5.0 and I stopped my work.
Yes, we get 5.0 release in October.
I still have no understanding how we could move PS 7.1 to .Net 5.0 since it is not LTS. So MSFT team should make a conclusion about #10869 /cc @SteveL-MSFT

@iSazonov  so even if .Net Core 5.0 releases in October, PS 7.1 has yet to use it?
So this could be a long lasting bug?
That's bad...Not having an easy, linear way of using WinForms in new scripts is bad enough, but not having backwards compatibility for this functionality is huge.

PS 7.1 has yet to use it

PS 7.1 will use it, but PS 7 set to the LTS channel won't get that update

@rjmholt so the only workaround is the way I did it?
New-Object System.Drawing.Font("Microsoft Sans Serif",13)
and
[System.Drawing.Color]::White
?

#10869 is not a breaking change and could be in 7.0 as servicing update otherwise we will get many feedback about issues with WinForms.

not having backwards compatibility for this functionality is huge.

Unfortunately type-level APIs like this are out of our control; we rely on .NET's implementation completely.
It may turn out that this is something we can fix in PowerShell, but there are some things that are changed at the fundamental .NET layer.

so the only workaround is the way I did it?

If you're targeting 5.1 I'd recommend:
[System.Drawing.Font]::new("Microsoft Sans Serif", 13)

But the New-Object syntax is compatible with PowerShell 3 and up (compared to 5 and up), so it depends on the versions you're targeting.
Converting scripts to that syntax will work will all PowerShells.
Is there another kind of workaround you're looking for?

@rjmholt No, no, I understand this is completely dependant on .Net's implementation since it's an API call. But it still a big deal.
That workaround works, but the main problem is that the code is inconsistant which makes it a lot harder to read.


Away day: inconsistency between bluebird instances

I'm communicating with the three Bluebird instances running on our Azure VM and I'm getting incosistencies. The Bluebirds are operating on ports 5000, 5001 and 5002.
I created a single aircraft and pos?acid=all command gives me:

port 5000 : "No aircraft in simulation"
port 5001 : Returns the correct aircraft information
port 5002 : Also returns the aircraft information

Port 5000 doesn't seem to be pointing to the same Bluesky instance if that's possible?

On second thought, it seems that Bluebird crashes silently and stops responding properly. Current state is that two of the three Bluebird instances (running on Azure on ports 5000 and 5001) are responding "No aircraft in simulation", when the third Bluebird instance responds correctly with a list of planes.


Support Carthage

Please support Carthage on the Swift 2 branch. You just need to share the build scheme and push it. Thanks!

Should be good to go!
https://github.com/cezarywojcik/CWStatusBarNotification/commit/88623f80a289bb7e416607b289729677eced029c

Great!

Sorry for the misunderstanding but you need to push the build scheme for the framework, not for the demo.

Ah, I guess the misunderstanding came about because the demo build scheme is the only build scheme. The library was meant to be used by importing the two *.swift files.
As an exercise, though, I went ahead and tried settings things up as a framework. I haven't used either Carthage or custom frameworks in the past, though, so I'm hoping I set things up correctly.
https://github.com/cezarywojcik/CWStatusBarNotification/commit/be8a8e51a901bc54bf133f47b051c46112dd71ff
However, I was only able to get the framework to work myself when using a workspace, though I'm somewhat new to this, so I'm not sure if I'm importing the framework incorrectly or whether something is set up incorrectly.
Let me know if things work as intended for you. If not, feel free to submit a PR.

Thanks so much for you effort @cezarywojcik. We're slowly getting there!
Another thing about Carthage. It looks for the schemes in the alphabetically first Xcode project file. So at the moment it takes the demo instead of the framework. Would you mind to change that as well? :+1:

I assumed Carthage would know to choose a framework project. Alphabetical listing seems... silly.
I googled around and it seems like Carthage picks the root-most, alphabetically sorted project. I would prefer not to have to reorganize just because Carthage likes things a certain way. Do you know of a way to just specify the project for Carthage to target? I Googled around real quick and couldn't find a way.
If there's not a way, I'll find a way to reorganize things, but I would prefer not to have to do that.

Well at the moment the workaround is the do carthage checkout, go the the cloned repository and delete the demo folder by hand before running carthage build. I guess that's the price one has to pay by not having a dedicated Carthage.spec or something like this.


Feedback: rename GitHub repo

I feel like I should rename the repository to php-date instead of laravel-date as it is not limited to be used with Laravel only. What do you guys think?

Or we could also call it something like 'Carbonic', or something.

I think Carbonic is better one

It will be a bit confusing with Carbon no? And if you don't know the repo, php-date is more intuitive to find in a search. Maybe something to reminds internationalization : universal-date.

Maybe just jenssegers/date? It is much cleaner.

Or maybe diem or tempus (from latin)

Maybe die shouldn't be in the word. Then I think tempus sounds better.


Action and Func Delegates in C#

Action and Func Delegates in C#

Source code for Evaluation article on Action and Func delegates in C#


Update Typedoc

Typedoc is out of date. Updating it will require a major upgrade of @m-ld/typedoc-theme, because the way themes work has changed.
$ npm update
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/typescript
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| 4.0.x" from<EMAIL_ADDRESS>npm ERR! node_modules/typedoc
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Duplicate of #155


Segmentation Fault while executing CarlaUE4.sh

Hi,
While executing ./CarlaUE4.sh in Xubuntu to run Carla the terminal prints me the following error:
Increasing per-process limit of core file size to infinity.
Signal 11 caught.
Malloc Size=131076 LargeMemoryPoolOffset=131092
CommonLinuxCrashHandler: Signal=11
Malloc Size=65535 LargeMemoryPoolOffset=196655
Malloc Size=78304 LargeMemoryPoolOffset=274976
Segmentation fault (core dumped)
Do you know what's happening and why do I get this error?

That doesn't give much info, could it be related to this #757?

Sorry I finaly solve it.
Thank you!

Sorry I finaly solve it.
Thank you!

How do you solve it then? I have the similar problem as you...
Thanks!

Hey @RogerAylagas, how did you solve it?
@jingzhao3200 did you end dup solving it?


 tag not working within SSML

Microsoft.CognitiveServices.Speech
C# SDK  Not working
I simply want to embed Audio as mentioned
(https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/speech-synthesis-markup
When the following SSML is called into the SpeechSynthesizer.SpeakSsmlAsync, the system returns a Cancel error:
Connection was closed by the remote host. Error code: 1007. Error details: Unsupported voice . USP state: 3. Received audio size: 0bytes.
I am clearly providing a URL with a valid file and I believe I have well formed the audio tag as per the documentation:
<speak version='1.0' xml:lang='en-US'>
<audio src="https://www.upsilondynamics.com/Content/TwilioGreetings/notify.wav" />
<voice xml:lang='en-US' xml:gender='male' name='en-US-GuyNeural'>
Hello World, this is a test!</voice>
</speak>

Embedding it within the VOICE tag is preferable, it also dos not work:
<speak version='1.0' xml:lang='en-US'>
<voice xml:lang='en-US' xml:gender='male' name='en-US-GuyNeural'>
<audio src="https://www.upsilondynamics.com/Content/TwilioGreetings/notify.wav" />
Hello World, this is a test!
</voice>
</speak>

@upsilondynamics Can you please provide us with the URL of the Azure Doc you are having issues with? We look forward to your reply.

https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/speech-synthesis-markup
Contains documentation relating to this, this is with regard to Cognitive Services .NET SPEECH SDK.
Can we possibly have this issue moved or re-created to the proper location so the issue can be resolved?

@upsilondynamics I think you have put this issue to the right forum: https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/433 Let's keep eyes on it. I will close this here.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Created sum_of_each_element_of_matrix.c

Created a user input array of square matrix ,which print matrix first then sum of element of matrix.

Sir , as you have asked me to change the directory, I did exactly as you asked me to do .


Azure: Avoid redundant network roundtrips for generating pre-signed URLs

The current implementation of the Azure Blockstore will perform a network roundtrip to the Azure server on each generation of a pre-signed URL. This adds latency and might count towards rate limits.
Desired behavior: do the minimal amount of roundtrips to the Azure server (might be just 1 roundtrip to fetch the delegation token and cache it locally?)

cc @N-o-Z @Jonathan-Rosenberg @arielshaqed

Closing as done


Spring caches config value

Step to reproduce:
Initially Config.test is set to 1.
I go into the console and Config.test would return 1.
Exit the console.
Then I change it to 2 in YAML.
When I start the console again, Config.test still returns 1.
Only after a Config.reload! call would Config.test return 2.
*** Up until here I can understand. What I consider strange is the below:
Even after a Config.reload!, the new value would only stay until I close the console
And if I exit the console again and start another console, it would still return 1.
Calling spring stop can remedy this issue, as the console would not cache the old value after that.
I would expect that given I have called reload!, the new value should be available in the Spring copy of memory.

Seems like I discovered the same behaviour. For tests, I performed the resetting with:
Object.send(:remove_const, 'Config')
load 'config.rb'


Array.filter is not a function

> Getting content from source space
ERR! Failed with
 TypeError: Array.filter is not a function
ERR! Failed with
     at filterType (/home/basti/.node_modules/lib/node_modules/contentful-space-sync/dist/get/get-source-space.js:69:16)

This happens both with the installed binary from npm as well as when running node dist/space-sync.js directly.

Uh, when I use babel-node to run dist/space-sync.js it fails with a different error, which is rather weird:
> Getting content from source space
ERR! Failed with
 DefaultLocaleNotDeletable: DELETE https://api.contentful.com:443/spaces/nwszylcdhgm6/locales/1TKFHYy0NBZKqL0PKj3sP4?access_token=0db1c6b9cfc43fcfd35a3404f050fa2a00dccaa4e6a
11c8414da7386010e1e4d Cannot delete a default locale. {"sys":{"type":"Error","id":"DefaultLocaleNotDeletable"},"requestId":"9e1-607131206","message":"Cannot delete a default
 locale."}

It tries to delete the default locale when getting the source space?!

Hi there,
regarding the first issue, what version of node are you running this on?
As for the second, api.contentful.com is used only to send data to the destination space. Is nwszylcdhgm6 the ID of the space you are using as the source space?
Also, I see you've pasted the whole URL including the access_token, which if this is the management token is probably not a good idea to have it out in the open. If you'd like to show me your configuration and more details that can be sensitive feel free to contact me directly by email at<EMAIL_ADDRESS>

regarding the first issue, what version of node are you running this on?

v5.0.0

As for the second, api.contentful.com is used only to send data to the destination space. Is nwszylcdhgm6 the ID of the space you are using as the source space?

Ah, you're right. That was destination space.

Also, I see you've pasted the whole URL including the access_token, which if this is the management token is probably not a good idea to have it out in the open.

Ugh, I will probably never get used to the fact that you use access tokens as URL params, so they're visible everywhere you can see requests. Thanks for the hint, already deleted.

v5.0.0

Right! That's out! I think I haven't tested it yet on that version, so I'll give it a try. There might be some not obvious weirdness with ES6 and the compiled babel code.

Ah, you're right. That was destination space.

So what happens essentially is, as we don't get the locales and content types via the sync endpoint, we don't know exactly which ones were deleted and/or updated. So what the script does is, it gets all the CTs/locales on the source and destination space, and in the destination space deletes the ones that stopped existing in the source space.
I've written this in the readme but let me know if that wasn't entirely obvious and I'll try to improve it.
Regarding as to why this was trying to delete the default locale, and with the explanation above: did you make changes to the locales in the destination space? Or did you change which locale is the default in the source space?

Ugh, I will probably never get used to the fact that Contentful uses access tokens as URL params, so they're visible everywhere you can see requests. Thanks for the hint, already deleted.

Not always, we can also send them as headers. In fact, that's a good idea for the upcoming rewrite of the contentful-management.js library, so I'll write it down.

Regarding as to why this was trying to delete the default locale, and with the explanation above: did you make changes to the locales in the destination space? Or did you change which locale is the default in the source space?

I'm not sure anymore. I did fix a locale issue afterwards where en-US was set as default for a space that was supposed to use sth else, so that should be the explanation then.

Not always, we can also send them as headers. In fact, that's a good idea for the upcoming rewrite of the contentful-management.js library, so I'll write it down.

The delivery JS client does this as well, and it'd be great to change it there, too. ;)

I have the same issue so I thought I'd post some more log that I get to hopefully make debug eassier.

Contentful Space Sync:
Let's sync some content across spaces!

No previous sync token found or fresh sync requested.
Synchronizing fresh content from bu3jhz3mxna4 to 9ekxodx7z4ou

Getting content from source space
ERR! Failed with
TypeError: Array.filter is not a function
ERR! Failed with
at filterType (/usr/local/lib/node_modules/contentful-space-sync/dist/get/get-source-space.js:69:16)
ERR! Failed with
at /usr/local/lib/node_modules/contentful-space-sync/dist/get/get-source-space.js:33:48
ERR! Failed with
at lib$es6$promise$$internal$$tryCatch (/usr/local/lib/node_modules/contentful-space-sync/node_modules/contentful-management/node_modules/es6-promise/dist/es6-promise.js:331:16)
ERR! Failed with
at lib$es6$promise$$internal$$invokeCallback (/usr/local/lib/node_modules/contentful-space-sync/node_modules/contentful-management/node_modules/es6-promise/dist/es6-promise.js:343:17)
ERR! Failed with
at lib$es6$promise$$internal$$publish (/usr/local/lib/node_modules/contentful-space-sync/node_modules/contentful-management/node_modules/es6-promise/dist/es6-promise.js:314:11)
ERR! Failed with
at lib$es6$promise$asap$$flush (/usr/local/lib/node_modules/contentful-space-sync/node_modules/contentful-management/node_modules/es6-promise/dist/es6-promise.js:125:9)
ERR! Failed with
at doNTCallback0 (node.js:428:9)
ERR! Failed with
at process._tickCallback (node.js:357:13)
ERR! Failed with
[TypeError: Array.filter is not a function]

Essentially this was due to babel-polyfill not being included, and I wrongly assumed the babel compiler would take care of that for me.
Issue is fixed in 1.2.1, just released.

Thanks!


Incorrect IPFIX TemplateField type checking

Hi,
not completely sure if actually an issue, but it seems there is bug within the datatype-check of the IPFIX TemplateFields in lines 769-785 of ipfix.py. The datatype check in the respective lines 772, 775, and 777 are not checking for the actual datatype (i.e., string) of the IPFIX TemplateField but for its name (i.e., applicationGroupName).
I think to fix this, line 742 should be changed to
discovered_fields.append((field_type.name, field_type_id, datatype))

Accordingly line 769 should be changed to
for index, ((field_type_name, field_type_id, field_datatype), value) in enumerate(zip(discovered_fields, pack)):

and the aforementioned lines 772, 775, and 777 should check field_datatype instead of field_type_name.
Hope this description of the problem helps.
Best :)

Hi @bof64665,
thanks for your bug report! You are right, the name is not even needed at this point if I see it correctly.
Commit a94ad57 implements your proposed fix and even removes the .name. Would you take a look? 🙂

Hi @bitkeks,
looks fine to me. Thanks for fixing this issue :)


feat(@embark/test-runner): make vm default node

This makes the VM  (ganache) the default node for tests.
This can still be changed using --node ws://localhost:8546, but there is a bug/not implemented change where the blockchain node always uses the config, so when we implement customizing the blockchain config in the individual tests, we should fix it for --node too.

Rebased

I read through the PR, but it wasn't clear to me how exactly it makes the vm the default for the tests, e.g. there aren't any changes to the test runner package itself. Can you explain?

@emizzle thanks for your review. The reason why I didn't create a VM module that starts Ganache like you suggested is that since it's only the proxy that handles it, it can use it as a provider directly, which is faster than using the ganache-cli, start it, wait for it to be ready and then use the endpoint for the proxy to connect.
That said, I agree that passing node around like that is a bit error prone, so I'll try to think of a way to make it cleaner

I changed the node @emizzle but I did it in another PR because I needed to touch a lot in that part too.
You can find the commit here: https://github.com/embark-framework/embark/pull/1870/commits/165202ac901311f0b93f656de76928a2561c88af

Don't merge yet. I rebased and it is mergeable, but something is broken in it that I can't figure out yet

Thanks for the update @jrainville. In commit https://github.com/embark-framework/embark/commit/165202ac901311f0b93f656de76928a2561c88af, it still feels odd that we need to depend on the name of a blockchain client to start the proxy. I really feel like it should be agnostic of the client name and just start based on the endpoint in the config.

Alright, finished rebasing and fixing.
Basically, the problem was that when we close the blockchain node and restart it, modules had their own instance of web3 that pointed to the old provider.
Now, this is fixed by reseting _web3 when blockchain:started is called.
We might be able to have something cleaner if we had a web3 module that other modules could request the web3 object from.

@emizzle are you talking about the if (endpoint === vm)? If so, I agree that it's not as ideal as having a node to just connect the endpoint to, but in our case, the VM can be (and is in Ganache's case) literally a provider.
This means that the proxy doesn't have to connect to a url, but just to the ganache provider. that way, we don't have to wait for the ganache cli to be ready, meaning it's simpler for us and faster for the user.


win_api: make get_version more resilient - checks for api version in dict

Windows 11 is using WebAuthn API version 3. This causes a KeyError when using the API version to access a value in the WEBAUTHN_STRUCT_VERSIONS dict because it only has keys 1 and 2.
This PR extends the conditional to first ensure that the API version is in the keys of WEBAUTHN_STRUCT_VERSIONS to avoid the KeyError.
As of right now, all API calls my application uses are working on Windows 11 with this small change.

I went a bit further and updated the structs for API 3, but I don't currently have a Windows 11 installation to test with, so I'd really appreciate it if you could report back on whether or not that works for you! https://github.com/Yubico/python-fido2/tree/windows-api3

@dainnilsson - While I can't speak for all of the changes in your branch, I can confirm that it is working for my use case on Windows 11. It was tested through WindowsClient.make_credential() and WindowsClient.get_assertion() calls.

Thanks! This has now been fixed in 9f5cab8.

Thanks for patching this!
@dainnilsson any updates on a release?

This was included in 0.9.2 which was released in October of last year.