Entity <> could not be transformed and will be staged without change

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 Ubuntu 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 2.0 alpha
Python version: 3.6
CUDA/cuDNN version: 10
GPU model and memory: GTX2080Ti

Hi there, could you please have a look at the issue? A customized network module (in Keras) cannot work as for gradient backpropagation.
Log:
W0529 19:29:46.658907<PHONE_NUMBER>89632 tf_logging.py:161] Entity <bound method Layer.call of <tensorflow.python.keras.engine.training.Model object at 0x7f6404415fd0>> could not be transformed and will be staged without change. Error details can be found in the logs when running with the env variable AUTOGRAPH_VERBOSITY >= 1. Please report this to the AutoGraph team. Cause: Unexpected error transforming <bound method Layer.call of <tensorflow.python.keras.engine.training.Model object at 0x7f6404415fd0>>. If you believe this is due to a bug, please set the verbosity to 10 (on Linux, export AUTOGRAPH_VERBOSITY=10) and attach the full output when filing the bug report. Caused by: node <gast.gast.Subscript object at 0x7f61f416e4e0> has ctx unset
W0529 19:29:52.344057<PHONE_NUMBER>89632 tf_logging.py:161] Entity <function train_G at 0x7f64c79a9ae8> could not be transformed and will be staged without change. Error details can be found in the logs when running with the env variable AUTOGRAPH_VERBOSITY >= 1. Please report this to the AutoGraph team. Cause: Unexpected error transforming <function train_G at 0x7f64c79a9ae8>. If you believe this is due to a bug, please set the verbosity to 10 (on Linux, export AUTOGRAPH_VERBOSITY=10) and attach the full output when filing the bug report. Caused by: node <gast.gast.Name object at 0x7f61ad7cb588> has ctx unset
W0529 19:29:52.960978<PHONE_NUMBER>89632 optimizer_v2.py:928] Gradients does not exist for variables ['conv2d_24/kernel:0', 'conv2d_24/bias:0', 'conv2d_25/kernel:0', 'conv2d_25/bias:0', 'conv2d_26/kernel:0', 'conv2d_26/bias:0', 'conv2d_27/kernel:0', 'conv2d_27/bias:0', 'conv2d_28/kernel:0', 'conv2d_28/bias:0', 'conv2d_29/kernel:0', 'conv2d_29/bias:0', 'conv2d_30/kernel:0', 'conv2d_30/bias:0', 'conv2d_31/kernel:0', 'conv2d_31/bias:0', 'conv2d_32/kernel:0', 'conv2d_32/bias:0', 'conv2d_33/kernel:0', 'conv2d_33/bias:0', 'conv2d_34/kernel:0', 'conv2d_34/bias:0', 'conv2d_35/kernel:0', 'conv2d_35/bias:0', 'conv2d_36/kernel:0', 'conv2d_36/bias:0', 'conv2d_37/kernel:0', 'conv2d_37/bias:0', 'conv2d_38/kernel:0', 'conv2d_38/bias:0', 'conv2d_39/kernel:0', 'conv2d_39/bias:0'] when minimizing the loss.
x

@weiminson In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Also Could you provide more details about the issue and context?. Thanks!

@weiminson In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Also Could you provide more details about the issue and context?. Thanks!

@gadagashwini thanks for your reply.
I was trying to implement a network with the following structure:

each of its decoder branches are connected to a decoder like this:

However, when I try to update its gradient in a function called train_G using:
with tf.GradientTape(persistent=True) as t:
ground_truth = get_Mask(x_real)
x1_fake, x2_fake = G(ground_truth, training=True)
x1_fake_d_logit = D1(x1_fake, training=True)
x2_fake_d_logit = D2(x2_fake, training=True)
G1_loss = g_loss_fn(x1_fake_d_logit)
G2_loss = g_loss_fn(x2_fake_d_logit)
G2_grad = t.gradient(G2_loss, G.trainable_variables)
G_optimizer.apply_gradients(zip(G2_grad, G.trainable_variables))
the warning described above occurs, saying that no gradient will be obtained from the branches.
is there anything wrong with my code?

@weiminson I tried to reproduce the issue but it looks code snippet is incomplete. Please provide complete code to. Thanks!

@weiminson I tried to reproduce the issue but it looks code snippet is incomplete. Please provide complete code to. Thanks!
@gadagashwini Thanks for your reply, to reproduce the issue, I've uploaded the entire coding to
https://github.com/weiminson/debug-SplitU
Plz run tain.py to test. for the running environment, plz refer to README.

@jvishnuvardhan Could you please help to try this case? I've been stuck on this issue for more than one week... Appreciate your reply.

@mdanatg: Is this autograph related? There is an "Unexpected error transforming" in the logs

Yes, the warning is definitely related to autograph and indicates a bug, judging from the error message.
That said, I believe the gradient error is unrelated - the warning simply states that autograph will leave that code unchanged, and it's unlikely to cause that error.
So I think we're dealing with two separate issues here - it would be great if you had a code snippet (or a simplified model of it) that can reproduce the error.

@mdanatg: I believe the code has been uploaded to https://github.com/weiminson/debug-SplitU

The warning from optimizer is as expected.
@weiminson your code seems to be:
G2_grad = t.gradient(G2_loss, G.trainable_variables)
G_optimizer.apply_gradients(zip(G2_grad, G.trainable_variables))
G_optimizer is getting "all trainable variables" with G.trainable_variables, while you are providing gradients only for the ones on the G2 branch, hence it is warning you that it doesn't see any gradients for the variables in the G1 branch. The warning is to make sure you aren't doing this by mistake.
@mdanatg the autograph warning seems unrelated, but may be worth checking if it needs to be there.

The warning from optimizer is as expected.
@weiminson your code seems to be:
G2_grad = t.gradient(G2_loss, G.trainable_variables)
G_optimizer.apply_gradients(zip(G2_grad, G.trainable_variables))
G_optimizer is getting "all trainable variables" with G.trainable_variables, while you are providing gradients only for the ones on the G2 branch, hence it is warning you that it doesn't see any gradients for the variables in the G1 branch. The warning is to make sure you aren't doing this by mistake.
@mdanatg the autograph warning seems unrelated, but may be worth checking if it needs to be there.

@rajatmonga , Thanks for your reply. Actually, I did try out a training mode where one of the branches was disabled and the other was left enabled (mode 2). Consequently, it was still showing the same error. Besides, I checked the name of the layers from that Error messages, finding that these layers are names of layers of BOTH branches, which implied that neither of the branches actually worked.
Correct me if I m wrong. BTW, do you know what this error message means? Why train G could not be transformed? I believe this is the root cause of the issue.
W0529 19:29:52.344057<PHONE_NUMBER>89632 tf_logging.py:161] Entity <function train_G at 0x7f64c79a9ae8> could not be transformed and will be staged without change.

@weiminson I tried to run the code you uploaded to the github repo, but it fails with this error:
python3 train.py
Traceback (most recent call last):
  File "train.py", line 82, in <module>
    dataset, shape, len_dataset = data.make_PETCT_dataset(img_paths, args.batch_size, args.input_size)
  File "/home/mdan/debug-SplitU/data.py", line 95, in make_PETCT_dataset
    repeat=repeat)
  File "/home/mdan/debug-SplitU/tf2lib/data/dataset.py", line 127, in disk_image_batch_dataset
    repeat=repeat)
  File "/home/mdan/debug-SplitU/tf2lib/data/dataset.py", line 77, in memory_data_batch_dataset
    repeat=repeat)
  File "/home/mdan/debug-SplitU/tf2lib/data/dataset.py", line 32, in batch_dataset
    dataset = dataset.map(map_fn, num_parallel_calls=n_map_threads)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 1146, in map
    self, map_func, num_parallel_calls, preserve_cardinality=True)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 3264, in __init__
    use_legacy_function=use_legacy_function)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 2591, in __init__
    self._function = wrapper_fn._get_concrete_function_internal()
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/eager/function.py", line 1366, in _get_concrete_function_internal
    *args, **kwargs)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/eager/function.py", line 1360, in _get_concrete_function_internal_garbage_collected
    graph_function, _, _ = self._maybe_define_function(args, kwargs)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/eager/function.py", line 1648, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/eager/function.py", line 1541, in _create_graph_function
    capture_by_value=self._capture_by_value),
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/framework/func_graph.py", line 716, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 2585, in wrapper_fn
    ret = _wrapper_helper(*args)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/data/ops/dataset_ops.py", line 2530, in _wrapper_helper
    ret = func(*nested_args)
  File "/home/mdan/debug-SplitU/tf2lib/data/dataset.py", line 113, in map_fn_
    return map_fn(*parse_fn(*args))
  File "/home/mdan/debug-SplitU/tf2lib/data/dataset.py", line 107, in parse_fn
    img = tf.io.read_file(path)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/ops/gen_io_ops.py", line 626, in read_file
    "ReadFile", filename=filename, name=name)
  File "/home/mdan/.local/lib/python3.5/site-packages/tensorflow/python/framework/op_def_library.py", line 550, in _apply_op_helper
    (prefix, dtypes.as_dtype(input_arg.type).name))
TypeError: Input 'filename' of 'ReadFile' Op has type float32 that does not match expected type of string.

It seems to require the PET & CT dataset, but it's unclear how to install that.
At any rate, the two warnings are very unlikely to be related. To verify that, please change line 156 as follows:
@tf.function(autograph=False)
def train_G(x_real):

@weiminson
I had a closer look at train_G, and I believe the bug that caused the warning is already fixed in the beta1 release:
pip3 install -U tensorflow==2.0.0-beta1
I think that will require upgrading tensorflow-addons, too:
pip3 install -U tensorflow-addons
Could you try running your code under these versions and check if any of the warning remain?

+1 with what @rajatmonga said. The warning from optimizer only suggests branch 2 is not included in the backprop path, and seems to be legit in your use case. If you want to avoid such warning, the simplest way is to change your code to use G.trainable_variables to tape.watched_variables so that it only updates branch 1.
The actual error seems to be coming from NodeTransformer:
assert node.ctx is not None, 'node {} has ctx unset'.format(node)

Since we expect the warnings to clear in the beta or nightly builds, but we can't confirm from our side whether the warnings clear in the latest build, I will close this issue for now. Please re-open it if they still appear in the nightly build though. Thanks!

@weiminson
I had a closer look at train_G, and I believe the bug that caused the autograph warning is already fixed in the beta1 release:
pip3 install -U tensorflow==2.0.0-beta1
I think that will require upgrading tensorflow-addons, too:
pip3 install -U tensorflow-addons
Could you try running your code under these versions and check if any of the warnings remain?

@mdanatg : I had a similar issue. The warnings disappeared after using the beta1 release.
Thanks.


Investigate Eval hangs of Kappa defined arrows

This currently prevents Eval compute in (@some_kappa_arrow Combinatorial) (true) style evaluation for Kappa built Arrows. Extraction and term manipulation doesn't have this issue.

Both Kappa and the closure conversion now using a constructive/induction type arrow. Coq still hangs when evaluating directly (Eval compute in (@some_kappa_arrow Combinatorial) (true)), but extracting these definitions works fine. This could be due to observed remaining proof equality matches in the term construction, or could be due to typeclass resolution, more investigation is needed.

At least part of the issue was using a generic axiom in a term. Using a better-anyway lemma on a specific structure allowed evaluation. This seemed to confuse the typeclass resolution into an infinite loop.


Refactor - Add NaN to expected values (Pool 9)

Just like Uniswap V3 in the case of Pool 9 (it also applies to Pool 8 but is done in the corresponding PR), when the deltas resulting from a transaction are 0, and then you want to calculate the execution_price, this results in NaN.
In this PR, that change is applied to provide more clarity and be more faithful to the results of Uniswap tests.

This could work but the long term solution would be to create an Enum for the execution price and have some sort of definitions that wraps NaN and the numbers when done correctly. What do you think?

This could work but the long term solution would be to create an Enum for the execution price and have some sort of definitions that wraps NaN and the numbers when done correctly. What do you think?

I like this approach, though it will require a refactor in the expected_values structure, having to generate all of them again.
Is it a good "first issue"? I think it may be a good fit for a talented intern.


Unable to add pagination meta data to response dict

I want to add pagination meta data to a response when i do a GET request to my API.
I can handle the pagination djangos built -in Paginator class but the problem is that my list() expects a colection/itterator of items to serialize. So I cannot return the collection from my pagiinator + the meta data from that paginator object.

That tip was useful! Perhaps it should be in the documentation ;)


[nri-metadata-injection] disabled by default

The current implementation is casing issues and it is not straightforward to be installed.
A lot of users do not need it, but they install it anyway since it is enabled by default facing issues from time to time.
We should no enable it by default, leaving only the users interested the option to install it.
The main issue is that we should disable it only for new users, avoiding removing it after an upgrade to avoid breaking changes

After the change in the way the certificates are created this does not seem to be needed anymore.


Fix CommonJS import compatibility

🛠 Summary of changes
Fixes another regression of #395, where downstream projects can resolve the CommonJS built output, but would treat its code as ES Modules, since the project's top-level package.json includes "type": "module". It's unclear why this wouldn't have been an issue prior to #395.
Example failure: https://github.com/18F/identity-idp/pull/9992
Error:
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /Code/identity-idp/app/javascript/packages/clipboard-button/clipboard-button-element.spec.ts

I'm  not 100% about the solution here since typically a package would only contain a single, root-level package.json. However, I've tested to confirm that it works, and have seen the idea referenced in a few places:

https://2ality.com/2019/10/hybrid-npm-packages.html#option-3%3A-bare-import-esm%2C-deep-import-commonjs-with-backward-compatibility
https://github.com/nodejs/node/issues/34515#issuecomment-664209714

The alternatives could be to use either Babel CLI's (prior to 9.0.0) --out-file-extension .cjs or ESBuild's (after 9.0.0) --out-extension:.js=.cjs to control the file extension output for CommonJS. However, there's not an easy solution to change the source code's path references based on the built output type, aside from using a third-party plugin like babel-plugin-replace-import-extension.
📜 Testing Plan
This is easiest to verify via the pull request mentioned above: https://github.com/18F/identity-idp/pull/9992

cd identity-idp
git checkout dependabot/npm_and_yarn/18f/identity-design-system-8.1.1
yarn install
yarn mocha app/javascript/packages/clipboard-button/clipboard-button-element.spec.ts
Observe the error mentioned above
Apply fix manually: echo '{"type":"commonjs"}' ><EMAIL_ADDRESS>Re-run yarn mocha app/javascript/packages/clipboard-button/clipboard-button-element.spec.ts
Observe test passes successfully

Visual regression failure is being addressed separately at #402


chore: adding Nebula as GH owners [NEBULA-1290]

Adding team Nebula as code owners for files that could break local-engine

Hi @metju90 , I'll discuss with the team, if we want code-ownership of the codeSettings in VSCode with Nebula.

@bastiandoetsch shared ownership will be best. We want to be notified of potentially breaking changes for local-engine.

@bastiandoetsch Code files are now co-owned between hammerhead, zenith and nebula


Show lists in product page using Wrap widget

What

Currently all lists a product is in are displayed using a column on the product page, we could switch to using the Wrap widget to save some space

Before:

Not sure Wrap would be appropriate, given the padding of the buttons and the length of words in some languages like - no offense - German.
But I agree, the current display is not beautiful.
Perhaps Wrap with the first letters of each list title? I don't know...

can I work on this?

Sure @prathamsoni11

As I checked all lists a product buttons are in Wrap already.

Then it's probably a problem in the tiles, they shouldn't take the whole width if they don't need to

for now we can use SizedBox to reduce the width by wrapping Wrap widget by SizedBox and assigning width = screenWidth / 2.

Maybe switching to a Chip will size this automatically

Maybe switching to a Chip will size this automatically

@M123-dev "Chip" behaviour.

I haven't had a look at the code so I don't know why it's that large, but still we should make it not the whole screen width

I haven't had a look at the code so I don't know why it's that large, but still we should make it not the whole screen width

I tried something as you told me. Hope you like it.

Hi, I would like to work on this issue, it it still open?

No, it is already (pending) fixed by @prathamsoni11 https://github.com/openfoodfacts/smooth-app/pull/3647

@M123-dev this issue has been resolved.


Is there a ready-made fastapi integration service image?

Is there a ready-made fastapi integration service image?

 unstructured:
   image: downloads.unstructured.io/unstructured-io/unstructured-api:latest
   ports:
     - 8002:8002
   entrypoint: ["uvicorn", "prepline_general.api.app:app", "--log-config", "logger_config.yaml",
                "--host", "<IP_ADDRESS>", "--port", "8002"]

But it's really huge, like 17go docker image. How can we reduce this

Hi @lambda-science, another user noted this as well. I'd expect our images to be more in the 8GB range, so I wonder if we made a mistake in the hosted version. Please follow the issue over here for tracking this: https://github.com/Unstructured-IO/base-images/issues/11


Make Doubles aggregators use 64bits by default.

In good old days Druid Double Sum/Min/Max/First/Last Aggregators would aggregate double values during ingestion then this double aggregated value will be stored as a truncated float. Effectively you send to Druid a double number x and druid will store it as (float) x thus this can save 32 bits at the expense of more error accumulations/confusions.
PR https://github.com/druid-io/druid/pull/4491 has made the following changes to address the problem.

Added Float Aggregator factory that can be used if the user is okay with 32 bits floating numbers.
Made Double Aggregator factory use actual 64bits floating point numbers.
To make rolling upgrade migration smooth added a system-wide property that makes new Double Aggregator retain old behavior by default (eg doubles casted to float). This is done here https://github.com/druid-io/druid/pull/4944/

PRs 4491/4944 were released as part of 0.11 thus any cluster running 0.11 is capable of reading segments where Doubles are stored as 64 bits also all the indexing nodes understand float aggregators.
As discussed in  https://github.com/druid-io/druid/issues/4605 the plan was to make Double aggregator use 64bits by default in 0.12.
As part of the last dev meeting, I proposed to release double as 64bits by default.
FYI  this is not a blocker for 0.12 but i will be nice to get this done one day.
In Addition to that @leventov had some concerns about keeping the same names while changing the implementation. He suggested that we add new kind of aggregator and deprecated old ones, @roman feel free to elaborate more on your point of view.
IMO  it will be confusing more than helping the user if we add new aggregators and deprecate the old one.
In addition, we are not saving the user anything because at the end of the day you have to either move out from the deprecated ones or use the float aggregators instead of double.
https://groups.google.com/d/msg/druid-development/VEYkW_5dWd8/AKL6_uk5AwAJ

I am gonna move this to 0.13.0 as we have been discussing on the list.

@b-slim 0.13.0 is due to be code frozen soon -- please do the PR soon if you want it to get in!

Resolved by #5478


Operation cancelled

Hi All,
We have a user who is experiencing this error, Operation cancelled which seems to stem from signTransaction.
Unfortunately we can't reproduce and are having a hard time getting much from the user, but I thought I'd reach out to see if anyone is seeing something similar, or has an troubleshooting tips.
Basically all we are doing is asking our users to connect their wallet (popup 1), then sign a 0 amount transaction (popup 2). Each with a user action to avoid popup warnings.
We have at least 10 people regularly and successfully doing this (multiple times a day) on our web app.
This user however, seems to always get the error Operation cancelled and we have tracked the message back to the call to signTransaction.
Again, not much to go off, we are asking the client to try a different browser, new account, etc... but any tips would be welcome.
Cheers.

Update: this appears to only happen when connecting from Firefox browser.

Hell @shourovb  @hutch120
Do you know if the signTransaction popup was opened?
It was opened and closed immediately?

Popup appeared, TX appeared correctly and user was able to go through with entering password and press "Sign". Popup closed and the above error was thrown.

We are almost certainly seeing this issue: https://github.com/randlabs/myalgo-connect/issues/35#issuecomment-852994208

@hutch120 I'm not sure, because this issue blocks the MyAlgo Connect popup immediately:
https://connect.myalgo.com/docs/getting-started/important-considerations/#firefox-and-safari-issues
@M-Picco will be following this issue


The gptimer alarm doesn't trigger when set with an old counter (IDFGH-9522)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
The documentation for the gptimer states that: (from https://docs.espressif.com/projects/esp-idf/en/v5.0.1/esp32/api-reference/peripherals/gptimer.html#set-up-alarm-action)

If an alarm value is set and the timer has already exceeded this value, the alarm will be triggered immediately.

However the following code demonstrates that this doesn't seem to be the case:
static bool testCallback(::gptimer_handle_t, const ::gptimer_alarm_event_data_t*, void* userCtx)
{
      std::atomic<int>& counter = *static_cast<std::atomic<int>*>(userCtx);
      ++counter;
      return false;
}

::gptimer_handle_t gptimer_;

::gptimer_config_t config{};
config.clk_src = GPTIMER_CLK_SRC_APB;
config.direction = GPTIMER_COUNT_UP;
config.resolution_hz = 10000; // 0.1ms
config.flags.intr_shared = false;
::gptimer_new_timer(&config, &gptimer_);

::gptimer_event_callbacks_t callback{
    .on_alarm = testCallback
};
std::atomic<int> flag{0};
::gptimer_register_event_callbacks(gptimer_, &callback, &flag);

::gptimer_enable(gptimer_);

::gptimer_start(gptimer_);

::gptimer_alarm_config_t alarm{};
alarm.alarm_count = 10;
::gptimer_set_alarm_action(gptimer_, &alarm);

while (flag.load() == 0);
std::cout << "flag=" << flag.load() << std::endl;

It never prints flag=1. However, if I change alarm.alarm_count = 15000;, a value after the current counter, it works as expected. So it seems that the statement in the documentation is false.

TEST_ALARM_CALLBACK_ATTR static bool test_gptimer_alarm_late_callback(gptimer_handle_t timer, const gptimer_alarm_event_data_t *edata, void *user_data)
{
    esp_rom_printf("alarm isr count=%llu\r\n", edata->count_value);
    return false;
}

TEST_CASE("gptimer_trig_alarm_with_old_count", "[gptimer]")
{
    gptimer_config_t timer_config = {
        .resolution_hz = 10 * 1000, // 10KHz, 1 tick = 0.1ms
        .clk_src = GPTIMER_CLK_SRC_DEFAULT,
        .direction = GPTIMER_COUNT_UP,
    };
    gptimer_handle_t timer;
    TEST_ESP_OK(gptimer_new_timer(&timer_config, &timer));

    gptimer_event_callbacks_t cbs = {
        .on_alarm = test_gptimer_alarm_late_callback,
    };
    TEST_ESP_OK(gptimer_register_event_callbacks(timer, &cbs, NULL));
    TEST_ESP_OK(gptimer_enable(timer));
    TEST_ESP_OK(gptimer_start(timer));

    vTaskDelay(pdMS_TO_TICKS(1000));

    gptimer_alarm_config_t alarm_config = {
        .reload_count = 0,
        .alarm_count = 10, // 1ms
    };
    TEST_ESP_OK(gptimer_set_alarm_action(timer, &alarm_config));

    vTaskDelay(pdMS_TO_TICKS(100));

    TEST_ESP_OK(gptimer_stop(timer));
    TEST_ESP_OK(gptimer_disable(timer));
    TEST_ESP_OK(gptimer_del_timer(timer));
}

I tried with the above code, I can see the alarm interrupt is triggered.
Running gptimer_trig_alarm_with_old_count...
alarm isr count=9999
MALLOC_CAP_8BIT: Before 300800 bytes free, After 300800 bytes free (delta 0)
MALLOC_CAP_32BIT: Before 382668 bytes free, After 382668 bytes free (delta 0)
/IDF/components/driver/test_apps/gptimer/main/test_gptimer.c:559:gptimer_trig_alarm_with_old_count:PASS
Test ran in 1127ms

Thanks @suda-morris for looking into this. Indeed, your example shows that it works as intended. I just tried your example on my setup but it also doesn't work. However, if I change alarm_count to 11000 (1.1s) it prints alarm isr count=11026. So it is the same behavior as my example.
I am using an esp32, with ESP-IDF 5.0.1 and running my example on qemu. What is your setup?

I just tried on a real target (esp32 devkit) and it works as expected. Seems that the issue is with my qemu setup then. Therefore I am closing this issue. Thanks @suda-morris again for helping me here.


{ [SyntaxError: Unexpected token &] filename: 'http://localhost:4815/oauth/authorize:script' } in test/oauth-authorization-test.js

I happened to notice this line:
{ [SyntaxError: Unexpected token &] filename: 'http://localhost:4815/oauth/authorize:script' }

in the output of % vows --spec ../../test/oauth-authorization-test.js.
I cannot for the life of me reproduce this or nail down what's causing it, but I figure I'll document it in GitHub. It may not be a real error, but Vows tends to sometimes just swallow things (which is dumb for a test suite runner to do, but whatever).

Oh, this is on the utml-to-jade branch. Whoops.
#1167


Database: Add TinyORM modern C++ ORM library

Added the TinyORM modern C++ ORM library to the Database list.
TinyORM - Modern C++ ORM library. [MIT] website

Ping this, we also have vcpkg port ready and I would like to be on your list too. Thank you.

Thank you


In-Memory Engine: Provide number of MVCC versions per region from RocksDb

In-Memory Engine: Provide number of MVCC versions per region from RocksDb

/assign @afeinberg


fix(sdk): check payment method before plan upgrade and downgrade

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
9401

Relevant Lines:
93216

💛  - Coveralls


UNAVAILABLE: Network closed for unknown reason

Hi,
Executing installation plugin return with the following error
[ERROR] Failed to execute goal org.microbean:helm-maven-plugin:<IP_ADDRESS>.1.2-SNAPSHOT:install (Install your-project chart) on project demomicrotest: io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason -> [Help 1]
Configuration looks like :
<plugin>
           <groupId>org.microbean</groupId>
                <artifactId>helm-maven-plugin</artifactId>
                <version><IP_ADDRESS>.1.2-SNAPSHOT</version>
                <executions>
                    <execution>
                        <id>Install your-project chart</id>
                        <phase>install</phase>
                        <goals>
                            <goal>install</goal>
                        </goals>
                        <configuration>
                            <chartUrl>file:${project.basedir}/demomicrotest-helm</chartUrl>
                            <releaseName>${project.name}</releaseName>
                            <valuesYamlUri>file:${project.basedir}/demomicrotest-helm/values.yaml</valuesYamlUri>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

Using helm client my charts has no problem. I'm testing it on minikube.
Could you please help me to understand where I mistake in configuration ?
Thanks

Hello; thanks for using the helm-maven-plugin project.
Your configuration looks fine.
helm-maven-plugin uses the microBean Helm project under the covers, and that project uses the fabric8 Kubernetes client library.  It is that library which governs how network connections to Tiller, Helm's back-end component, are made.  Specifically, there are a lot of configuration sources that are tried by default.  I suspect that this is probably the source of your problem.  Good luck!

I'm getting the same issue. It's using the config file in ~/.kube and that configuration is correct (it works with using helm otherwise).

I'm not sure what to tell you.  As you can see from the exception, it is related to the Java implementation of the gRPC protocol (i.e. it's not something I have control over).  Maybe after debugging you could try filing a more specific issue in the https://github.com/grpc/grpc-java project?


Interquartile Range (IQR)

Is your feature request related to a problem? Please describe.
The interquartile range defines the difference between the third and the first quartile. Quartiles are the partitioned values that divide the whole series into 4 equal parts. So, there are 3 quartiles. First Quartile is denoted by Q1 known as the lower quartile, the second Quartile is denoted by Q2 and the third Quartile is denoted by Q3 known as the upper quartile. Therefore, the interquartile range is equal to the upper quartile minus lower quartile.
Describe the solution you'd like
Interquartile range IQR tells us the range
where the bulk of the values lie. The interquartile
range is calculated by subtracting the first quartile
from the third quartile.
IQR = Q3 - Q1
Additional context
For more understanding refer below example
Input :   1 , 2 , 3, 4 , 5 , 6 ,7 , 8 ,9 10 , 11
output:  3
Explain : As first we have to calculate Q2 which is median of the series so
Q2 = 6
Now , we have to calculate Q1 basically Q1 is median of series which start from first element of series till the Q2
In our example Q1 = 3
and , Q3 is median of range start after Q2 to till the last element of series
In our case Q3 = 9
and therefor the IQR for our series is 3

@Kumar-laxmi sir will you please assign me this issue please.

Assigned!
@pra9patil : C, C++, Python and Java

@Kumar-laxmi Thank you sir
I will code it and make PR before 9 PM


Add troubleshooting section to docs

Created troubleshooting.rst in docs.
Added there how to fix empty page on FF on Linux.

[ ] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[ ] Unit tests added or updated
[x] Documentation added or updated
[ ] Example(s) added or updated
[ ] Update schema.json if there are changes to the viewconf JSON structure format
[ ] Screenshot for visual changes (e.g. new tracks or UI changes)
[ ] Updated CHANGELOG.md

Thanks Ilya!
The only change I'd suggest is to make the second level heading more generic so that the sidebar remains clean. Something like:
===========
  Troubleshooting
  ===========

  Empty Page
  ==========

  HiGlass showing as an empty page in Firefox on Linux
  ----------------------------------------------------

  Due to a bug in Mesa video drivers that has since been fixed, Firefox introduced a workaround which prevents HiGlass to load.
  To disable this workaround, set ``gfx.work-around-driver-bugs=false`` in ``about:config``, and restart the browser.

  Source: https://bugzilla.mozilla.org/show_bug.cgi?id=1601682

Won't this make Troubleshooting and Empty page be on the same level in the hierarchy? Is that what you want?..

Nope

Right, yeah.
Empty page and  HiGlass showing as an empty page in Firefox on Linux look the same on GitHub though

That's OK. Google results will point to the docs page rather than the Github source so I'm not too concerned about that.

OK, so it's rendered correctly in docs? Cool.

Good enough :-)


Build a Pluggable Native Widget

There is no hint in this tutorial that I have to install an older node.js version (14) in order to make this running. The process will fail when trying this with the latest node.js version.

Thank you for your feedback. We have recently completed an overhaul of the Mx8 document which solves these issues and adds a few more improvements.
These same improvements will soon be duplicated to the Mx9 version of the document as well.


Predict error

Raw output on console.
python3 predict.py --model=./models/model__epoch_9_maxlen_150_lr_0.00125_loss_0.6931_acc_0.5005_f1_0.4944.pth --text="thisisatest_______" --alphabet=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_ Traceback (most recent call last):   File "/Users/ttran/Desktop/development/python/character-based-cnn/predict.py", line 48, in <module>     prediction = predict(args)   File "/Users/ttran/Desktop/development/python/character-based-cnn/predict.py", line 11, in predict     model = CharacterLevelCNN(args, args.number_of_classes)   File "/Users/ttran/Desktop/development/python/character-based-cnn/src/model.py", line 12, in __init__     self.dropout_input = nn.Dropout2d(args.dropout_input) AttributeError: 'Namespace' object has no attribute 'dropout_input'
What is --number_of_classes argument?  I don't have that set in the run command.

found resolution to my own issue.
add the following line to the predict.py file
    parser.add_argument("--dropout_input", type=float, default=0.1)


Control flow based type narrowing for assert(...) calls

Now that TypeScript does control flow based type analysis, and there is a never type in the works, is it possible to consider providing better type checking around assert(...) function calls that assert that a variable has a certain type at runtime?
TL;DR: some assert functions are really just type guards that signal via return/throw rather than true/false. Example:
assert(typeof s === "string"); // throws if s is not a string
s.length; // s is narrowed to string here...

Problem
Asserts are common in contract-based programming, but I've also been coming across this scenario regularly whilst traversing JavaScript ASTs based on the Parser API (I'm using babel to produce/traverse ASTs).
For example, consider the MemberExpression:

Note we can assume property is an Identifier if computed===false. This is what I'd like to write:
function foo(expr: MemberExprssion) {
    if (expr.computed) {
        // handle computed case
    }
    else {
        // since computed===false, we know property must be an Identifier
        assert(isIdentifier(expr.property));

        let name = expr.property.name;  // ERROR: name doesn't exist on Identifier|Expression
    }
}

Unfortunately that doesn't compile, because expr.property does not get narrowed after the assert(...) call.
To get the full benefit of control flow analysis currently, you have to expand the assert call inline:
...
else {
    if (!isIdentifier(expr.property)) {
        throw new AssertionError(`Expected property to be an Identifier`);
    }

    let name = expr.property.name;  // OK
}
...

While preparing the typings for babel-core, babel-types and friends, I noticed that using asserts this way is the norm. babel-types actually provides an assertXXX method for every isXXX method. These assertXXX functions are really just type guards that signal via return/throw rather than true/false.
Possible Solutions?
Not sure if it's feasible at all! But the new work on never in #8652 suggests a few possibilities.
Specific assertions: assertIsT(...)
// normal type guard
function isIdentifier(n: Node): n is Identifier {
    return n.type === 'Identifier';
}

// PROPOSED SYNTAX: assert type guard
function assertIdentifier(n: Node): n is Identifier | never {
    if (n.type !== 'Identifier') {
        throw new AssertionError(`Expected an Identifier`);
    }
}

The compiler would reason that if this assert call returns at all, then it can safely narrow the variable type in following code.
General assertions used with type guards: assert(isT(...))
The more general assert(cond: boolean) function would need a different approach and might not be feasible, but here's an idea:

    // General case
    declare function assert(cond: boolean): void;

    // PROPOSED SYNTAX: Special overload for expressions of the form assert(isT(x))
    declare function assert<T>(guard: guard is T): void | never;

For that second assert overload to work, the compiler on seeing assert(isT(x)) would have to somehow forward the x is T narrowing from the isT(x) expression to the assert(...) expression at compile-time.
Would be great if it also detected/handled things like assert(typeof x == 'string').
Not sure if any of this would meet the cost/benefit bar, but it's just an idea.

I feel like this should work:
function assertIdentifier(n: Node) :(n is Identifier) | never

But #5992 has made this impossible, by only allowing type predicates to be used as return types.

I like @isiahmeadows' idea in #12885. With that, assertIdentifier could be declared as two overloads:
declare function assertIdentifier(n: Node): n is Identifier;
declare function assertIdentifier(n: Node): never;

let x: Node = ...
assertIdentifier(x);
x; // CFA infers x is an Identifier here, since the other overload declares it never returns

@yortus I've developed that further into something more broadly useful: #13257

@yortus That wouldn't work, because n is Identifier is just a boolean subtype that narrows within if-else when it's the raw operand. In fact, that'd work closer to @chilloutman's idea than you might expect.
Regarding the function overload idea, I've developed that idea further into something far more broadly useful: #13257
Here's how it'd apply here:
declare function assertIdentifier(n: Node): [
    case n is Identifier: void,
    default: throw,
];

(n.b. The default: throw is redundant, just provided here for clarity.)

@isiahmeadows right, my snippet above based on existing syntax (i.e. without constraint types) should be:
declare function assertIdentifier(n: Identifier): void;
declare function assertIdentifier(n: Node): never;

let x: Node = ...
assertIdentifier(x);
x; // CFA infers x is an Identifier here, since the other overload declares it never returns

Any updates on this? I would love to see the chai equivalent
interface myTypeA {
   typeGaurd: "myTypeA";
   myValue: Boolean;
}

interface myTypeB {
   typeGaurd: "myTypeB";
}

// ...

const myObj: myTypeA | myTypeB = getMyObj();

expect(myObj.typeGaurd).to.equal("myType");  // type guard assert
expect(myObj.myValue).to.be.true;            // No error :)

@johnemau Chai's type definitions currently suck as-is, and they really need rewritten to not use any so much. Twice, now, I migrated a TS project's tests to clean-assert (shameless plug: I wrote it), which has sane type definitions, and it took a solid half a week to fix all the resulting type errors in it. (It had a few thousand tests, and some pretty complex types, too.)
So that's equally a failing of that library, and you wouldn't see results until that's fixed.

As for this request, here's my thought of what a proposal could look like:

This return-specific syntax would be better IMHO: assume n is Identifier, .... This allows multiple variables to be checked simultaneously.
A function with an assume return type must not return a value.
If a function is otherwise inferred as returning void and any argument is narrowed to only one type at all return points, infer the return type to assume the argument is that type, rather than void.
The return type should be treated as an unconditional type narrowing in the body.

Edit: assume types really should look like this, with a few clarifications/edits:

Syntax: assume T if n is Identifier, ...

T is any valid return type
Stuff like assume n is string if n is string and similar are equivalent to true.

Flagged: If a function has an inferred return type, then the inferred return type also assumes any arguments narrowed if they are narrowed at all return points.
Normal function return rules apply as if the enclosing assume didn't exist

For me, the most important aspect here is for there to be some way to write a generic assert function and similar functions, not just type assertions specifically.
I'm starting to move my team's large JS codebase to TypeScript, and we have an assert function that we use regularly for things like null checks. We also have an assertAndContinue function that crashes in development and returns false and logs an error in production when the condition fails.
Concrete examples of where TypeScript could do better:
assert(this.props.synthesisRulesRun != null);
const violations = cutSiteViolations(this.props.synthesisRulesRun, enzyme);

if (!assertAndContinue(field.requiredLink, `Field with id=${field.id} has no requiredLink`)) {
  return [];
}
const linkType = field.requiredLink.sampleType;

Both of these could be solved with the ! non-null assertion operator, and most other examples I could find were just null checks like these, but it still would be nice if people on my team could feel like they aren't losing anything by using assert or assertAndContinue rather than writing extra code inline.

@alangpierce In our big TypeScript project we use the following helper:
export function assertExists<A>(value: A | null | undefined): A {
    if (a != null) {
        return a;

    } else {
        throw new Error("Value doesn't exist");
    }
}

You can use it like this:
const synthesisRulesRun = assertExists(this.props.synthesisRulesRun);
const violations = cutSiteViolations(synthesisRulesRun, enzyme);

It would be ideal for TypeScript to have better support for assert, but the above is a good workaround in the meantime.

Just published ts-assert-exists based on the @Pauan’s code snippet:
import assertExists from 'ts-assert-exists';

const twitterToken: string = assertExists(
    process.env.TWITTER_TOKEN,
    'Twitter token does not exist',
);

Just to add my two-cents, while this was not a pattern that I used previously, I am seeing that this pattern is widely adopted and certainly limits the effectiveness of CFA.  I don't think it is actively on the roadmap, but it certainly would be a really useful feature to a lot of code bases.

I think this would help greatly with improving readability in certain cases, since current workarounds usually require more duplicate code (if statements with shared functions).
Now that conditional types has landed, maybe that syntax is a good fit for this feature? never would of course indicate that the methods throws, preventing completion.
declare function assertString<T>(value: T): T is string ? void : never;

@csvn
This is definitely the most consistent syntax with current TS and how I would expect it to work. It is easy to understand what's going on simply by reading this.

@demurgos does the syntax you suggest actually work today? Or is it more of an idea?

@tonyxiao
No, it does not work today.

It's a shame that return types from methods can't be used for performance reasons. Having throw expressions still require two separate methods if both validation and error message is not triial and needs to be repeated:
if (!isCircle(x)) throw incorrectTypeError(x);

assertIsCircle(x);

But I understand that

This would be wonderful - at the moment I'm doing something like this with JSON imports:
import { Foo, Bar } from './types.ts'
import { assertFoo, assertBar } from './assert.ts'
import * as fooJson from './foo.json'
import * as barJson from './bar.json'

assertFoo( fooJson )
assertBar( barJson )

export const foo = <Foo>fooJson
export const bar = <Bar>barJson

But it would be great if I could just do this, and the exported types would be Foo and Bar because of the assert functions:
import { assertFoo, assertBar } from './assert.ts'
import * as foo from './foo.json'
import * as bar from './bar.json'

assertFoo( foo )
assertBar( bar )

export { foo, bar }

Response to https://github.com/Microsoft/TypeScript/issues/8655#issuecomment-412685082

https://github.com/tc39/proposal-throw-expressions is actually an alternate solution here as well - once that proposal is through, code like (typeof x === "number") || throw "Wrong type");

This is not alternate solution. For example, in Node.js process.exit() call doesn't throw error, but terminates current execution. In addition, with throw expressions syntax still need to repeat check expression and error message in every place of usage.
If control flow analyze already understands user defined type guards, why do not add another special form for  assert like functions?

You could make an identity function with a built in assertion, if you're willing to re-assign the variable.
const foo = (a: number | null) => {
  a = shouldBe(_.isNumber, a)
  a  //  a is number
}

const shouldBe = <T>(fn: (t1) => t1 is T, t) => (fn(t) ? t : throwError(fn, t))

const throwError = (fn:Function, t) => {
  throw new Error(`not valid, ${fn.name} failed on ${t}`)
}

where _.isNumber has a type guard x is number

Implementation now available in #32695.

Being fairly new to TypeScript I explored this problem a bit from the expect syntax perspective. Thanks @orta for pointing me to this issue. Watching.

Adding new nodes in this graph is not cheap (in terms of memory/performance), and realistically we couldn't possibly add all function calls to the graph and still achieve reasonable performance.

@RyanCavanaugh Did someone ask for all function calls to be added? This is a long thread, so maybe I missed it… Anyway, is there anything wrong with special-casing assert to work like if? I think most users would expect it to work this way, given how powerful TypeScript is, and with never now introduced. I know I sure did.


After reboot: WireGuard -> Status: No peers have been configured

Assumption: A properly configured WireGuard tunnel should be connected/brought up automatically upon reboot.
Currently, WireGuard status after reboot is: No peers have been configured
Steps to recreate:

Working WireGuard configuration and connection is up.

Reboot pfSense.

VPN -> WireGuard -> Status (tab) -> Show Peers (button)
Output: No peers have been configured

Click Peers (tab)

Click pencil icon (Edit)

Delete Endpoint Port (51820 (default) appeared in this line)  <-- make a setting change, save it and apply changes to resolve the issue

Click Save Peer (button)

Click Apply Changes (button)

Click Status (tab)

Click Show Peers (button)

Peer connection shows established.

Running latest version of code:
2.6.0-DEVELOPMENT (amd64)
built on Wed Jun 09 01:03:58 EDT 2021
FreeBSD 12.2-STABLE
Name | Version | Comment
pfSense-pkg-WireGuard | 0.1.2_6 | pfSense package WireGuard (EXPERIMENTAL)
wireguard-kmod | 0.0.20210606 | WireGuard implementation for the FreeBSD kernel
wireguard-tools-lite | 1.0.20210424 | Fast, modern and secure VPN Tunnel (lite flavor)

Can confirm the same behavior on 2.5.1. After reboot WireGuard -> Status: No peers have been configured.

Interesting, I’m not seeing that on my end. All my peers come up properly on reboot.
so just to confirm, under status you see tunnel entries but # peers is 0?

Also, can you immediately download the tunnel configuration after startup using the new download feature, and redact it? I’m curious what that looks like on startup

I clicked the download icon and opened the file in textedit (Mac). I redacted parts of the private and public keys (...).
This WireGuard config file has been created automatically. Do not edit!
Description: Description
[Interface]
PrivateKey = yP8...
ListenPort = 51820
Peer: Description
[Peer]
PublicKey = 0/x2PdBGfc...
AllowedIPs = <IP_ADDRESS>/0
Endpoint = us8500.nordvpn.com:51820
PersistentKeepalive = 25

Followed these steps (redacted a key in screen capture):
Click Peers (tab)
Click pencil icon (Edit)
Delete Endpoint Port (51820 (default) appeared in this line) <-- make a setting change, save it and apply changes to resolve the issue
Click Save Peer (button)
Click Apply Changes (button)
Click Status (tab)
Click Show Peers (button)
Peer connection shows established.

Are you able to change us8500.nordvpn.com to the IP as a test and see if it comes up at reboot?
The IP looks to be <IP_ADDRESS>1 from my end but ping it to double check

Thank you.
I changed the FQDN (us8500.nordvpn.com) to the IP (<IP_ADDRESS>) and it successfully connected after reboot.
I'll close this ticket.

I’m going to look into the DNS race issue here first thing next week. It’s something we need to handle better

@infosecmatters2021
This is what I'm building. Default is 300 seconds (5 minutes), but is adjustable.

After a reboot, the handshake still show disconnected even after the endpoint DNS TTL period expires.
I downloaded the latest version (zip file) then copied all files from the pkg and www f

olders to my pfSense instance then rebooted it.

Would it be possible to get a nordvpn wireguard keypair from your for a few days for testing? Email me<EMAIL_ADDRESS>

Something new


AttributeError raised when loading glTF with mesh primitives that aren't type 4 / triangles

In io/gltf.py:293 skip_mesh is left as True when encountering a mesh primitive that isn't type 4/triangles.
As a result, at io/gltf.py:338 None is appended to meshes.
At io/gltf.py:375 the returned meshes list is enumerated and has_attribute is called on each item without checking whether it's None, leading to an AttributeError exception raised to the caller.
How best to handle this is really a design question for the library maintainers, but I think clients should either get a sensible exception explaining that the glTF has unsupported primitive modes, or be given the opportunity to handle None meshes.

Thank you for your note. To help us address this, would you be able to share a sample gltf file that causes this issue?
(this can be private for internal testing purposes only)


loadchain.py in examples does not work

Checklist

[X ] installed pyethapp inside a virtualenv

System/environment

OS: FIXME
python version: Python 2.7.13
pyethapp version: 1.5.0
installation method (pip & pypi/git & setup.py): git clone && USE_PYETHEREUM_DEVELOP=1 python setup.py develop
pyethapp branch (if applicable): develop

Expected behaviour
should ready all block in the chain and print the blk.header.number
Observed behaviour
File "loadchain.py", line 62, in
chain = get_chain()
File "loadchain.py", line 18, in get_chain
return Chain(Env(db))
File "/Users/anaconda/envs/pyethapp/lib/python2.7/site-packages/ethereum-2.0.4-py2.7.egg/ethereum/pow/chain.py", line 47, in init
elif "extraData" in genesis:
TypeError: argument of type 'Env' is not iterable
Moved past this error by setting genesis = genesis.config but then ran in to the next error
File "loadchain.py", line 62, in
chain = get_chain()
File "loadchain.py", line 18, in get_chain
return Chain(Env(db))
File "/Users/anaconda/envs/pyethapp/lib/python2.7/site-packages/ethereum-2.0.4-py2.7.egg/ethereum/pow/chain.py", line 68, in init
}, self.env)
File "/Users/anaconda/envs/pyethapp/lib/python2.7/site-packages/ethereum-2.0.4-py2.7.egg/ethereum/genesis_helpers.py", line 118, in mk_basic_state
addr = normalize_address(addr)
File "/Users/anaconda/envs/pyethapp/lib/python2.7/site-packages/ethereum-2.0.4-py2.7.egg/ethereum/utils.py", line 220, in normalize_address
raise Exception("Invalid address format: %r" % x)
Exception: Invalid address format: 'ACCOUNT_INITIAL_NONCE'
Steps to reproduce
cd examples && python loadchain.py

@bgits you are right sir.

>>> from ethereum.ethpow import check_pow
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named ethpow
>>> from ethereum.chain import Chain
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named chain

I discovered after opening this issue that pyethapp just no longer works with the current chain.

what is the substitute of this ?

You created this issue on 16 Oct .
I think, Author or contributor have to look on this .

It seems the entire project is being replaced by:
https://github.com/ethereum/py-evm
Have not had time to investigate if py-evm is in a working state yet. If it
is this ticket should be updated to start using py-evm.
On Thu, Dec 28, 2017 at 6:45 AM, ChiragMaliwal<EMAIL_ADDRESS>wrote:

You created this issue on 16 Oct .
I think, Author or contributor have to look on this .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/pyethapp/issues/264#issuecomment-354276124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD1YSP6gPzUM5TL_NldWBU2VhUZZq7uZks5tE39UgaJpZM4P54aM
.

Thanks for the update.
Yes, looks like py-evm is  in developing mode and I am also not sure py-evm is in a working state or not.


fix: Add missing android:exported to service

It's required since Android 12 and makes apps targeting Android 12 or higher fail to build.

Hello, is this going anywhere?

@DanielEliraz LGTM


[Feature Request] Refresh button for Tabs

Existing Component
Yes
Component Name
TabPane or Tabs
Description
Add a refreshable prop.
When the prop is true, show a refresh icon-button left to the close icon-button (if exists). Click on the refresh icon-button will forceUpdate the contents of the tab pane (including children components, slot contents etc.).

No plan to add this. You can do this outside the Tabs component.


Resolve dependencies with a Scala 3 partial version

Fixes #2407

Support partial versions such as "3" (previously, you had to write at least two numbers, as in "2.13")
Fix module name of forced Scala modules (scala3-library and scala3-compiler). This also fixes a bug in "cs fetch --scala-version 3.2.1 '...'" not forcing the Scala 3 version in scala3-library)
Look up Scala 3 versions (previously, only Scala 2 versions were looked up)

Note that another change in this PR is that now Coursier defaults to Scala 3 if no Scala version is provided:
$ ./mill -i cli.run fetch org.scalacheck::scalacheck:1.16.0
[467/467] cli.run
/home/julien/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scalacheck/scalacheck_3/1.16.0/scalacheck_3-1.16.0.jar
/home/julien/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.1.1/scala3-library_3-3.1.1.jar
/home/julien/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-sbt/test-interface/1.0/test-interface-1.0.jar
/home/julien/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala-library/2.13.6/scala-library-2.13.6.jar


Implement set_cursor_position on OSX with Cocoa

The implementation uses CGWarpMouseCursorPosition that accepts global screen coordinates. These are therefore offset by the current window coordinates.

Looks good to me. Have you noticed any delay as mentioned in the original issue? Also seems to fix #664

I haven't personally noticed any delay, but I haven't done extensive testing. I see on this stackoverflow answer a workaround is to call CGAssociateMouseAndMouseCursorPosition(true) immediately after warping the cursor. This post also suggests that it is a valid (if undocumented) fix.
I'll update the code to include this and test locally. I can't tell if it fixes any delay because I am not experiencing any, but I will be able to see if it causes problems.

Adding in the extra call actually made a huge difference in cursor responsiveness :)
I based this change on the current stable crates.io version but I think it should be OK to merge into master. When is the next crates.io release scheduled? I need this functionality so I am currently referencing my own local bugfix version.

@AnthIste Just submit a PR which bumps the version in the Cargo.toml


Failed to load resource

When fresh npm start, hit this issue in browser. Same goes to the demo site.
Can help to clarify what is missing?
Error message:
Failed to load resource: the server responded with a status of 404 () [object%20Module]:1

HI @akmalelias, thank you for raising this issue. 👍
Fixed with 3e05a7fa114fa8492c74760a1c14240cf6dff04f


Find out if a token is a refresh or an access token

What version of UAA are you running?
4.6.1
What output do you see from curl <YOUR_UAA>/info -H'Accept: application/json'
{"app":{"version":"4.6.1"},"links":{"uaa":"http://localhost:8080/uaa","passwd":"/forgot_password","login":"http://localhost:8080/uaa","register":"/create_account"},"zone_name":"uaa","entityID":"cloudfoundry-saml-login","commit_id":"04c8408","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2017-10-02T00:01:33+0000"}
How are you deploying the UAA?
Docker container built by us from the default JAR
What did you do?
I have a string in my hands and want to know if it is
a) a valid access token
b) a valid refresh token
c) neither of the two
I can use the /check_token endpoint to check if a token is valid, but that will silently accept both access and refresh tokens and not tell the difference. The only solution which came to my minds was detecting the -r ending on refresh tokens, but that seems like a design-choice and could be changed with any update of the UAA. Is there any other possibility?

I don't think there is any way to do this today apart from the -r suffix. The tokens are clearly labeled when they are issued to clients from the /oauth/token endpoint. Refresh tokens are usually kept secret by the client and used to get fresh access tokens on a periodic basis.
What is the usecase you're working on where you're not sure what kind of token you have?

We have services which talk with the UAA, these services are provided by the user with a string which the user pretends to be a token. For the service to validate that the token is really a token it is calling the /check_token endpoint. And then I run into the issue described above: If the user of the service mixes up some stuff and sends us a refresh-token instead of an access token, we can only distinguish between that by checking if the string ends with an -r.

For now we took the approach of detecting the -r at the end, we would be happy to have a better solution though.


Fix Apply_04/US_Crime_Rates/Exercises_with_solutions Step 8 and Step 9 .

Step 8 solution is in 1960-1-1 format instead of 1960.
Step 9 solution is 'crimes.idxmax (0)' instead of 'crime.idxmax (0)'.

Hi Mandroide . I think solved. Thanks for sharing this exercise.

Hi Mandroide . I think solved. Thanks for sharing this exercise.

Hi, I will share with you some advice. Whenever you open a pull request, avoid thrashing.


Allow partial date parsing when simple datetime formatter is used

The Spark legacy datetime formatter allows parsing date from incomplete text,
seeing code link. This PR enables partial date parsing when the LENIENT_SIMPLE
or STRICT_SIMPLE datetime formatter is used.
Relates issues: #10354, gluten#6227

@rui-mo Could you please take a look? Thanks!

@pedroerp Could you please take a look? Thanks!

@mbasmanova Could you please take a look? Thanks!

@mbasmanova Thank you for your quick feedback. This change impacts the behavior of unix_timestamp and get_timestamp which relied on DatetimeFormmater::parse. I've added docs and rebased it onto the main branch.


Tidying io

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 80.00000% with 9 lines in your changes missing coverage. Please review.

Project coverage is 84.51%. Comparing base (f793e46) to head (9cb48d4).

Files with missing lines
Patch %
Lines

NetAF/Adapters/SystemConsoleAdapter.cs
54.54%
5 Missing :warning:

NetAF/Logic/Game.cs
80.00%
1 Missing and 1 partial :warning:

NetAF/Rendering/Frames/GridTextFrame.cs
71.42%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #83      +/-   ##
==========================================
+ Coverage   84.19%   84.51%   +0.32%
==========================================
  Files          95       96       +1
  Lines        3011     3009       -2
  Branches      459      459
==========================================
+ Hits         2535     2543       +8
+ Misses        310      299      -11
- Partials      166      167       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


translate

Hello,
a really good friend of me, sent me this good software, but there is a problem.
I'm good in english, but not bi lingual, so for use this soft fully maybe u can add an update with french (and maybe other languages)
thanks to devs

tracked by #199


Add presets for even simpler installation process

ESLint presets are awesome and I think lint-staged should allow pre-configured presets as well.
In a nutshell, presets should be just plain objects that then should be added to an array during the init phase.

i'd also suggest adding the following
var result = execa.shellSync('git rev-parse --show-toplevel');
so the result.stdout can be configured as 'git-root'

Not sure how is this related to this issue. Can you elaborate on it please?

I misread thinking you meant something like an installer. then it would be handy so it automatically sets the git-root.


map crash with built w3a

how to reproduce:

Download this map https://github.com/yatyricky/Zulaman-WE/blob/master/ZAM_ruins.w3x
Extract war3map.w3a with Ladik's MPQ Editor version <IP_ADDRESS>8 (Unicode Build) StormLib v9.21
war2json
json2war
Inject w3a to map
World editor working well, can open and save
Run map, boom!

I thought it was me who forged illegal json because I reconstructed my excel based on the war2json-generated json, and rebuild json based on my excel data and then json2war.
But when I actually rolled back to a playable version, I simply extracted the w3a file, war2json and json2war on it. Wc3 still gives me the same error.
(Actually not only wc3 crashes the same way, my optimizer produces the same error log, declaring that I have lost some file, and the tool asks me to provide the correct list file)

Hi @yatyricky, thanks for providing the detailed error report.
I am following your instructions and am experiencing the same issue: the map is not playable. Please note, though, that the map you linked to gives me the same blank error message even without modifying the abilities file.
It looks like the abilities file that is being produced from the translator is different from the original .w3a file. They should be the same.
Here's a screenshot of the differences between the original map's .w3a and the translated w3a.

I'm looking into why the files are different. I am also adding "diff" unit tests to each translator, because when you take a war3map file and translate it to JSON, then back to war3map (or JSON -> war3map -> JSON) the data should never change.
Could you double check the link to the .w3x file you provided? I am receiving the error you describe even before following the next steps you provide.

Interesting, I test this map on my 1.29.2 and it’s working well (it does not have any contents though because it’s not built yet)
I also double checked that I didn’t accidentally commit corrupted map into the repo.

It seems like that the problem happens in the original data, which gives me a huge relief because I only fear of my forged custom JSON

I resolved my error message issue when launching maps (not just yours, but blank ones I created on my end) by updating WC3. I was on 1.29.0, now I am updated to 1.29.2.
Your .w3a seems functional to me. I extracted the .w3a file from the map you linked, and went in to World Editor, created a blank map, placed the .w3a in and the game launches fine.
There is still the issue with the diffs not matching (see my above screenshot), and I added new unit tests to cover this. More translators have this issue, but strangely the output war3map files still work. You can put them into a .w3x map and the map launches just fine. Still worth fixing, and I'll keep looking into it.

So is the .w3a file still presenting an issue for you? When I placed it in a blank wc3 map and launched it worked fine. Still, there are differences in the bytes the translator is producing compared to the original file you provided (which would have been written by World Editor), so I know that there are small issues lurking in the translators. But I'm not certain if this particular issue you are encountering is related to the inexact-bytes issue I am describing.

I must be drinking alcohol when I tested the w3a->json->w3a flow.
The map does launch.
But however, when I build the map with jasshelper. Jasshelper did not give any errors and wc3 crashes.
When I use my optimizer after jasshelper, my optimizer gives
Lost 24 files - These files are discarded, Please include the complete `(listfile)`
Read (102/126) files

When I use my optimizer before jasshelper, my optimizer gives NO error.

I'll do another quick test to narrow the problem.

A new day begins (in my timezone), and I'm going to divide and conquer my json to find out what exactly gives me problem. Please wait for my result.

same issue with some units, i converted from w3u and then back, map crash

I am closing this issue with the release of WC3MapTranslator 4.0. This release is tested against WC3 Reforged (1.32.9.*).


cranelift: Merge interpreter tests with runtests

Almost all the tests in the interpreter are already in the runtests folder so that we can reuse them for the backends. The distinction
between interpreter tests and runtests is no longer very clear, since they should both support the same clif code, and produce the same results.
We only have two test files:

add.clif tests the add and jump instruction, both of which are already covered in other test files, so we remove that file.

fibonacci.clif does a recursive call which is currently not supported in the filetest environment, so we keep this test interpreter only for now.

Closing and reopening to rerun CI. (It looks like we had another spurious failure)


Added several _display fields to ITSystem, for convenience.

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Remove the many subMapMutex.Lock(), Unlock() calls, possibly

Because of the nature of Go maps, iterating the subscribe set means a fair number
of subMapMutex.Lock(), Unlock() calls
It might be cleaner to translate the subscriber uniq id to an array/slice index, which
then gets iterated, skipping empties.

no longer relevat


Implemented editor override, general cleanup

This implements #44 (minus the configuration file proposal) I.e. there is now an -e / --editor command line option which will override the value in the EDITOR environment variable or the default (currently hardcoded as "vim")
Logic to pick editor in this order moved to main()

Command line option from -e / --editor
EDITOR environment variable
"vim" (this should be further adjusted to a more suitable platform-specific default value)

Added more context if the editor command fails (shows the attempted command now)
Bumped version to 1.6.1 in Cargo.toml
Changed the value name for the rename_command option to COMMAND
General cleanup based on cargo clippy output:

Removed use tempfile
Removed use wild
Calling new.replacen() with char instead of string
.into_iter() -> .iter()
Changed a number of &Vec<*> arguments to &[*]
Deriving also from Eq in addition to PartialEq

This is also a first step towards addressing #58, but I didn't want to squeeze that also into a single commit. However, depending on how quickly this gets merged, I may add commits to address that issue.

Didn't change the version number again, since it doesn't matter in case both commits get merged at once.

I stand corrected. This (or rather the second commit) still does not fully address #58.
The issue that notepad.exe opens but any attempt to save the file causes an error remains on the Windows 10 box where I tested it.

I now have a hunch. renamer appears to keep the file open while passing it to the editor. This is generally no problem, but it depends on the so called "sharing flags" whether or not anyone else is allowed to use the same file.
Showing reference from renamer to the file in question from within Process Explorer:

Just did a little experiment and it seems to confirm the hunch. Process Explorer lets one forcibly close the handle. So I sort of "pulled" the rug underneath renamer by closing its handle and lo and behold Notepad did no longer refuse to save the file in place. Result:
> cargo run -- -e notepad *
    Finished dev [unoptimized + debuginfo] target(s) in 0.12s
     Running `target\debug\renamer.exe -e notepad *`

The following replacements were found:

README.md -> README.mdd

Execute these renames?:
> Yes
  No
  Edit
  Reset

Different file (as I am re-running this over and over) and here's how renamer opens the file:

And this is how Notepad does:

As I understand it, Notepad opens the file read-only (only disallowing deletion in the sharing mode), then maps it into memory. And here's the annotated "crime scene":

renamer creates the temporary file (and keeps it open) ... then starts Notepad, providing full path to temporary file
Notepad opens the file read-only
Range of events: this is the initial access to the temporary file while Notepad loads it
Notepad closes the file (from 2.)
(After changing the buffer) Notepad opens the file to read attributes (most likely something like GetFileAttributes() which is customarily used to check for the existence of a file on Windows)
Range of events: Notepad attempting to save in place
Attempt by Notepad at opening the temporary file for writing
Sharing violation occurs due to renamer still having the file open (with share mode: Read, Write, Delete) and Notepad requesting share mode Read (NB: the share mode denotes what type of access other "parties" may request on that same file ... renamer is liberal and allows it all, but Notepad says it only wants to allow others to read the temporary file, all the while renamer keeps it open read-write).
Notepad attempting to save the ~day~ temporary file into an alternative location due to the sharing violation from 8.

I think the fix would be to create the temporary file (by whatever means Rust allows us), open a second handle to it but with read-only access and the same liberal share mode. Then closing the first read-write handle and only then starting the editor.

@mtimkovich @marcusbuffett as mentioned above, feel free to merge this already. It improves on the current state and doesn't make it worse, even though the Windows-specific issue is a little more tricky than I initially thought. But I am working on a solution to that issue as well and depending on whether or not this has been merged already, it will go here or into a new PR.

Thanks for the PR!


[Feature]: Document error event details

Description
I'm looking for documentation for the errors sent to onError
Why it is needed ?
I want to capture playback errors (to sentry for example), but some errors are expected under normal conditions of use. In particular, I want to be able to differentiate errors caused by the network being inaccessible as those are interesting to me (content is missing or corrupt or whatever other errors I don't actually know since they aren't documented) per se. There are apis that will tell me when the device is on/off line but coordinating those with rnvideo will make it challenging and it would be more practical if rnvideo just documented the errors it sends so I could make a call on what is interesting or not.
Possible implementation
Docs :)
Code sample
For example, when I'm calling fetch I can ignore the networking errors this way
if (!(error instanceof TypeError) && (error as Error).name !== "TimeoutError") {
       Sentry.captureException(error);
}

I fully agree and this issue has already be identified, can be followed up in : https://github.com/TheWidlarzGroup/react-native-video/issues/3554 and https://github.com/TheWidlarzGroup/react-native-video/issues/2694


Recommend inbuilt pprof instead of go-torch

See the rendered README here: https://github.com/uber/go-torch/tree/use_pprof

Coverage decreased (-0.5%) to 94.949% when pulling d15bf857f5694aaa6635059cb0a13be880bb3ec4 on use_pprof into ddbe52cdc30e6a165aee3a634c597e01a235e85e on master.


Create/Attach dimension scales on append (mode="r+")

This fixes an issue where dimension scales weren't created/attached when appending with mode="r+".

added tests to check for scales when appending with mode="r+"

@shoyer Here also fixing a minor but problematic issue.

@shoyer This is ready for review/merge. As this change is really very simple, I'll merge by tomorrow. We can adapt later if necessary.


Added HTML ID tags to conversation messages bodies

Added HTML tags that are needed for testing.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   96.79%   96.79%
=======================================
  Files          32       32
  Lines        1124     1124
=======================================
  Hits         1088     1088
  Misses         36       36

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 5f6dac2...7479d74. Read the comment docs.


Add new custom types

Case MultiAddress was merged into master on Polkadot, we need add those types to run with latest code. Ref PR

AFAIK this was already merged into polakdotjs upstream or @jaco?

AFAIK this was already merged into polakdotjs upstream or @jaco?

Should be, recently I updated the polkadot-js deps and it contained the required types (in my case the problem was the BlockLength)

Should be, recently I updated the polkadot-js deps and it contained the required types (in my case the problem was the BlockLength)

Should be, recently I updated the polkadot-js deps and it contained the required types (in my case the problem was the BlockLength)

Yeah i just update @polkadot/api to latest version, everything is ok, include BlockLength. Close this PR

Should be, recently I updated the polkadot-js deps and it contained the required types (in my case the problem was the BlockLength)

Yeah i just update @polkadot/api to latest version, everything is ok, include BlockLength. Close this PR


Design System: Close context menu on blur

Context
The context menu rendered an invisible mask that covered the entire screen (behind the menu). When a user clicked on this mask, the menu closed. However, to interact with the app they would have to click the app again. This wasn't great UX.
Summary

Context menu now calls onDismiss when it loses focus. The Mask component has been removed and users are able to interact with the app even if the context menu is open in the dashboard and editor.
Combined the AnimatedContextMenu and ContextMenu into one component. The animation can be used by using the animate prop.

Relevant Technical Choices
n/a
To-do
n/a
User-facing changes
Testing Instructions
New Functionality:

Clicking away from the menu should close it but also interact with the thing you're clicking on. (ex: button or another element)

Everything else should work the same.
Dashboard:

Should be able to open the menu by clicking or with the keyboard in the My Stories view
Should be able to navigate the menu with keyboard.
Tabbing away from the menu should close it.
Arrow keys should not close the menu.
When navigating with keyboard you should see the focus border.
All actions in the menu should work as before.

Editor:

Should be able to open the context menu by 'right-clicking' anywhere in the canvas. This should select the element that is under the right click.
Right clicking another element should close the previous menu and open a new menu. The clicked element should now be selected
All actions in the menu should work as before.

QA

[ ] This is a non-user-facing change and requires no QA

Same steps as above
Reviews
Does this PR have a security-related impact?
no
Does this PR change what data or activity we track or use?
no
Does this PR have a legal-related impact?
no
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[x] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #8702

Dahboard works great! that old issue with the keyboard didn't resurface which is awesome.
🤔 With the right click menu, it feels a little weird that the right click menu pretty much never closes once it's open. For instance, I right click on a text element and then i decide to add a new image. The right click menu does swap out from being for text to an image element but I would expect the menu to close when i click on the image in the media panel and then if i want to right click the image i'd do so. Could the menu just close when blur occurs not update to a new type? Is there a specific case that I'm missing?

nice catch - that should close it. Taking a look at it now

An update here:
Found the problem. Looks like the click event gets eaten up by the <InOverlay /> component. Still tracking it down. Will update here when it's fixed https://github.com/google/web-stories-wp/blob/main/packages/story-editor/src/components/library/panes/shared/libraryMoveable.js#L283-L290


appitierre and connecting it with adapt

Hi Not sure if I am doing something wrong... but I wanted to try out the aptr-uikit on my version of adapt. Unforunately it isn't working for me so far? I am just wondering if you have a tutorial or if their is a specific adapt version I should be using to get this working. I would like to test out the program with courses I have already built.

Hi @mes333 this is used for apps that support React.js as all our components are built using the framework. This isn't so much a library for Adapt but more a kit to help build UI, Interactions and apps faster. We use it internally inside our Adapt, Evolve and Bloom apps. If you're looking for a program to help build Adapt courses there's the OS version here or you can try Evolve
Hope this helps explain the use of this library


When splitting a way with a route relation, not all descendant ways belong to the route relation

Reported to me over the weekend - it looks like we have an issue with splitting ways that belong to route relations.  After they split, they don't all belong to the route relation.
This probably used to work and we changed it to work like this for Turn Restrictions.
(When splitting a way with a turn restriction, you only want one of the roads to keep the relation, but when splitting a road with other kind of relations, you want all of the surviving ways to belong to the relation).

When splitting a way with a turn restriction, you only want one of the roads to keep the relation,

When spitting a way which is a via member, both ways need to become via members.

but when splitting a road with other kind of relations, you want all of the surviving ways to belong to the relation

At least for PTv2 routes, the members do also need to have in the correct order.

Gotcha @slhh that makes sense.. So I guess there are 3 cases of what to do when splitting a relation member:

(multipolygons, sites, and other random relations) - all surviving ways become members
(routes) - all surviving ways become members, but order must be preserved
(turn restrictions) - only the ways attached to the via node remain as members of the relation / special code to consider the case where the way being split is a via way.

(1 and 2 might be the same thing actually)


is there a compatible bitmap java lib for clickhouse?

<!-- https://mvnrepository.com/artifact/com.clickhouse/org.roaringbitmap -->
<dependency>
    <groupId>com.clickhouse</groupId>
    <artifactId>org.roaringbitmap</artifactId>
    <version>1.5.0</version>
    <scope>provided</scope>
</dependency>

is this lib available?

Hi @learn2Pro, are you using a mirror? You can use maven central to check, for example: https://repo1.maven.org/maven2/com/clickhouse/org.roaringbitmap/1.5.0/.

Hi @learn2Pro, are you using a mirror? You can use maven central to check, for example: https://repo1.maven.org/maven2/com/clickhouse/org.roaringbitmap/1.5.0/.

i try but not work with this lib, the 64bitmap result still incorrect

should i contribute for this?

Finally... But the change has not released yet.
Of course you can contribute. Please use develop branch and add more tests in the pull request.
A few more things you may want to consider:

implement ClickHouseDeserializer and ClickHouseSerializer interfaces
Use input/output stream instead ByteBuffer
extract ClickHouse compatible bitmap implementation and remove RoaringBitmap dedependency - avoid unnecessary byte array copying


Migrate to the community-hosted package repositories (pkgs.k8s.io) and to dl.k8s.io

What this PR does / why we need it:
There are three changes introduced in this PR:

Migrate to the community-hosted package repositories (pkgs.k8s.io) from the deprecated Google-hosted package repository (apt.kubernetes.io and yum.kubernetes.io)

The Kubernetes project strongly encourages and recommends migrating to the new package repositories as soon as possible
Given that the Google-hosted repository is deprecated, I decided to do unconditional migration, i.e. without giving an option to opt-out from this change. This is going to make it easier for us to maintain and support this release branch in the long term. Moreover, most users are not going to notice this change at all. This change might only affect users allowlisting traffic based on IP addresses or URLs, in which case they need to update their allowlists (this is explained in the release note)

Migrate to dl.k8s.io instead of pulling binaries from the release bucket directly
The kubernetes-release bucket might get deprecated and frozen in the future as part of efforts to migrate to the community-owned infrastructure. The Kubernetes project strongly recommends using dl.k8s.io going forward
Same as the previous change, this change shouldn't affect many users. Additionally, this only affects Flatcar-based clusters. Users using allowlisting might need to update their configuration and this is explained in the release note
cri-tools is updated to v1.27.1 for clusters running Kubernetes 1.27. Kubernetes 1.28 clusters will use cri-tools v1.28.0

Additionally, tests are updated to use KubeOne 1.6 as the stable version for initially provisioning the cluster.
Which issue(s) this PR fixes:
Fixes #2870
What type of PR is this?
/kind feature
Does this PR introduce a user-facing change? Then add your Release Note here:
- [ACTION REQUIRED] Migrate from the Google-hosted package repositories (`apt.kubernetes.io` and `yum.kubernetes.io`) to the community-hosted package repositories. The Google-hosted package repositories are deprecated as of August 15, 2023 and using the community-hosted package repositories is strongly encouraged. For most users, this change shouldn't make a difference. However, if you do IP-based or URL-based allowlisting, you need to allow outgoing traffic to `pkgs.k8s.io` and `prod-cdn.packages.k8s.io`. For more details, see the official announcement: https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/
- [ACTION REQUIRED] Migrate from using the Kubernetes release bucket (`https://storage.googleapis.com/kubernetes-release/release`) to `dl.k8s.io`. This change only affects Flatcar-based clusters. The Kubernetes project is now serving all binary artifacts via `dl.k8s.io` and it's strongly encouraged to use `dl.k8s.io` over accessing the bucket directly. For most users, this change shouldn't make a difference. However, if you do IP-based or URL-based allowlisting, you might need to make changes to your allowlist. See the following announcement for more details: https://kubernetes.io/blog/2023/06/09/dl-adopt-cdn/
- Upgrade cri-tools to v1.27.1 for clusters running Kubernetes 1.27

Documentation:
TBD

(this should be mentioned in the upgrade guide)

/cherrypick release/v1.6

/test pull-kubeone-e2e-aws-amzn-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-centos-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-default-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-flatcar-install-containerd-external-v1.27.3

/test pull-kubeone-e2e-aws-rhel-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-aws-rockylinux-install-containerd-external-v1.27.3

/test pull-kubeone-e2e-azure-flatcar-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-azure-rockylinux-install-containerd-external-v1.27.3
/test pull-kubeone-e2e-openstack-default-install-containerd-external-v1.27.3

/lgtm

/approve

/retest

/test pull-kubeone-e2e-aws-amzn-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

/lgtm

/test pull-kubeone-e2e-aws-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

/test pull-kubeone-e2e-aws-amzn-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

/test pull-kubeone-e2e-aws-rhel-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-rockylinux-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3
/test pull-kubeone-e2e-aws-flatcar-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

/test pull-kubeone-e2e-openstack-centos-stable-upgrade-containerd-external-from-v1.26.6-to-v1.27.3

/retest


Self-referencing Additional Resource

This page has three items listed under Additional Resources. Item #2 of 3 is a self-referencing link back to the same page. It should be removed.

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

ID: 90e6a3e5-1d5a-358d-60c5-0a6bed89e729
Version Independent ID: 8e95d16d-aa68-38c2-ac75-008f76b767a7
Content: Add Windows Defender exceptions for Android
Content Source: hub/android/defender-settings.md
Product: dev-environment
Technology: windows-android
GitHub Login: @mattwojo
Microsoft Alias: mattwoj

Thanks @ChristopherBenson! I agree -- removed. :)


Ripple secure mode(Auth0) to local passport

Hi, can I change ripple secure mode-auth0 to local using passport and how to integrate this with pulsetile(using login form)? Can you direct us to any examples or documentation on how to do this in Ripple-Qewd?
Thanks.

@linto17 Do you find the solution?

Yes, you can install that module, after login Just store the user authentication credentials in the QEWD Session.

@linto17 : Thank
Could you please share your forked repository or give us some sample code?
It will be helpful for everyone who wants to custom Ripple.

	  var passport = require('passport');
	  var Strategy = require('passport-local').Strategy;

	  passport.use( new Strategy({
        // by default, local strategy uses username and password, we will override with email
        usernameField : 'email',
        passwordField : 'password',
        passReqToCallback : true // allows us to pass back the entire request to the callback
    },
    function(req, email, password, done) { // callback with email and password from our form

        // find a user whose email is the same as the forms email
        // we are checking to see if the user trying to login already exists
        User.findOne({ 'local.email' :  email }, function(err, user) {
            // if there are any errors, return the error before anything else
            if (err)
                return done(err);

            // if no user is found, return the message
            if (!user)
                return done(null, false, req.flash('loginMessage', 'No user found.')); // req.flash is the way to set
                 flashdata using connect-flash

            // if the user is found but the password is wrong
            if (!user.validPassword(password))
                return done(null, false, req.flash('loginMessage', 'Oops! Wrong password.')); // create the
                  login message and save it to the session as flash data

            // all is well, return successful user
            return done(null, user);
        });

    }));
	  passport.serializeUser(function(user, done) {
		  console.log("***serialze");
		  //console.log(user);
		  done(null, user);
	  });
	  passport.deserializeUser(function(user, done) {
		  console.log("***deserialze");
		  //console.log(user);
		  done(null, JSON.parse(user));
	  });
	  var app = qewd.intercept().app;
	  app.use(passport.initialize());
	  app.use(passport.session());
	  app.post('/login',
			  passport.authenticate('local', { failureRedirect: '/fail.html'}),
			  function(req, res) {
		        var message = {
		                type: 'ewd-qoper8-express',
		                expressType: 'auth0-register',
		                application: 'qewd-ripple',
		                params: req.user
		              };
	              q.handleMessage(message, function(response) {
	                console.log('*** auth0-register response: ' + JSON.stringify(response));
	                res.cookie('JSESSIONID', response.message.token);
	                //res.redirect('index.html');
	                res.sendStatus(200);
	              });
           });

It works only in qewd-ripple port(3000).

Hi @linto17 , Have you changed ripple secure mode-auth0 to local using passport yet? How do you integrate this with pulsetile(using login form)? Can you tell me more information about this issue?
Thanks,
Thanh from ThinkLabs - VN

Hi @thanh121094 , I have created a new module for login in Pulsetile and redirect from header component where the result.data.redirectTo === 'auth0' of initialise request.


Why so much fear-mongering in your manifesto instead of trying to clarify what the actual change is?

Overnight, tens of thousands of businesses, ranging from one-person shops to the Fortune 500 woke up to a new reality where the underpinnings of their infrastructure suddenly became a potential legal risk. The BUSL and the additional use grant written by the HashiCorp team are vague. Now, every company, vendor, and developer using Terraform has to wonder whether what they are doing could be construed as competitive with HashiCorp's offerings. The FAQ provides some solace for end-customers and systems integrators today, but even if you might be in the clear now, how can you build confidence that your usage won't violate the license terms in the future?

The goal of Hashicorp is clear -- prevent 3rd party providers from offering their own products and charge for it without Hashicorp gaining anything. In fact, you can even use Terraform to build and host a product that's competitive to Terraform, using Terraform v1.6+! As long as what you're building and commercially offering doesn't share Terraform v1.6+ source code. This is clarified in their FAQ:

The BSL license does not prevent developers from using our tools to build competing products. For example, if someone built a product competitive with Vault, it would be permissible to deploy that product with Terraform. Similarly, if someone built a competitive product to Terraform, they could use Vault to secure it. What the BSL license would not allow is hosting or embedding Terraform in order to compete with Terraform, or hosting or embedding Vault to compete with Vault.

This means, their license change to BSL 1.1 actually doesn't affect 99% of Terraform users in any way. But the way you've worded it (esp. in the paragraph I quoted above) seems to be aimed at causing undue alarm among your readers. Firstly, even though you point out that Hashicorp's "FAQ provides some solace", you've conveniently not linked to the said FAQ, which would have actually helped a reader to become more informed.
Please make an effort to provide a more balanced perspective on the situation, and help your readers be informed on the subject by encouraging them to read Hashicorp's original announcement and its associated FAQ.

Thanks for sharing your views!
Whether or not you are right about Hashi's intentions, OpenTF is going to be amazing. It's going to be community first, impartial, open source, and once again, amazing.
PS: This is probably better as a discussion rather than an issue, so I'm locking the conversation and welcome you to keep the conversation going there.


Fixed WAV format in soundRecorder.js:saveSound()

According to the WAV spec, the number that goes right after 'RIFF' is 36 + ... not 44 + ... - here's an excerpt from the spec:
The canonical WAVE format starts with the RIFF header:
0         4   ChunkID          Contains the letters "RIFF" in ASCII form (0x52494646 big-endian form).
4         4   ChunkSize        36 + SubChunk2Size, or more precisely: 4 + (8 + SubChunk1Size) + (8 + SubChunk2Size) This is the size of the rest of the chunk following this number.  This is the size of the entire file in bytes minus 8 bytes for the two fields not included in this count: ChunkID and ChunkSize.

thank you @dorontal !


Add Adadelta Optimizer

I have added the adadelta optimizer (https://arxiv.org/abs/1212.5701).

@levskaya can you review my pull request? Thanks!

@levskaya do you have a minute to take a look at this?

Codecov Report

Merging #700 (34d5688) into master (1aff550) will increase coverage by 0.52%.
The diff coverage is 98.87%.

@@            Coverage Diff             @@
##           master     #700      +/-   ##
==========================================
+ Coverage   80.66%   81.19%   +0.52%
==========================================
  Files          56       56
  Lines        4267     4387     +120
==========================================
+ Hits         3442     3562     +120
  Misses        825      825

Impacted Files
Coverage Δ

flax/linen/normalization.py
89.09% <ø> (ø)

flax/linen/stochastic.py
90.90% <ø> (ø)

flax/nn/base.py
92.46% <50.00%> (ø)

flax/training/checkpoints.py
98.63% <95.65%> (-1.37%)
:arrow_down:

flax/core/lift.py
96.20% <98.50%> (-0.13%)
:arrow_down:

flax/core/tracers.py
83.33% <100.00%> (+0.98%)
:arrow_up:

flax/linen/__init__.py
100.00% <100.00%> (ø)

flax/linen/attention.py
96.26% <100.00%> (-0.04%)
:arrow_down:

flax/linen/dotgetter.py
70.21% <100.00%> (ø)

flax/linen/linear.py
99.45% <100.00%> (-0.01%)
:arrow_down:

... and 10 more

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 1aff550...336492a. Read the comment docs.

@levskaya I have corrected the mistakes and added the unit tests. Can you review it now?

@kamalesh0406 - btw, in the future it's good practice to make a github PR from a working branch in your forked repo so that maintainers can do merge commits in a PR rather than your master branch.


Add load tests

This PR builds on #11 and #26. Review those PRs first!
In order to keep the code best practice and recommendable we need to make sure the apps can load fast.
This will also make it much easier for us for example to deploy them to Hugging Face spaces as requested in https://github.com/ahuang11/panel-chat-examples/issues/9.
This PR adds load testing using Locust. See the updated README for details.

I've merged with the current main branch and

added missing dependencies
cleaned up issues
fixed tests
separated developer instructions in DEVELOPER_GUIDE.md and made it work end to end. Closes #28
added the short cut command hatch run panel-serve. Closes #23

Codecov Report
All modified lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@d3b1d74). Click here to learn what that means.

:exclamation: Current head a7a4659 differs from pull request most recent head 8046d69. Consider uploading reports for the commit 8046d69 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff           @@
##             main     #12   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?       1
  Lines           ?       3
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?       3
  Partials        ?       0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.