Integer divide-by-0 during fused convolution with oneDNN on CPUs supporting AVX512 instructions

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
2.9.1, 2.10.0
Custom Code
No
OS Platform and Distribution
Windows 10
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No GPU
Current Behaviour?
With oneDNN optimisations enabled and a CPU supporting AVX512 instructions, an Integer divide-by-zero exception occurs during execution of fused convolutions with certain input sizes.
To reproduce:

Use a machine equipped with a CPU supporting AVX512 instructions (e.g. Intel i7-1165G7).
Enable oneDNN optimisations by setting the TF_ENABLE_ONEDNN_OPTS environment variable to 1 and disable GPU usage by setting the CUDA_VISIBLE_DEVICES environment variable to -1.
Run the script below.
The python.exe process will crash with an Integer divide-by-zero exception.

The problem can be worked around by setting the DNNL_MAX_CPU_ISA variable to e.g. AVX2 in order to prevent oneDNN from using AVX512 instructions.
The issue occurs in TensorFlow 2.9.1 and 2.10.0 installed using pip. To debug it, I've built 2.9.1 TensorFlow from source with (some) debugging symbols and obtained the following stack trace:
[0x0]   _pywrap_tensorflow_internal!dnnl::impl::cpu::x64::brgemm_convolution_utils::brg_blocking_t::est_eff_1x1 + 0x38d
[0x1]   _pywrap_tensorflow_internal!dnnl::impl::cpu::x64::brgemm_convolution_utils::brg_blocking_t::calc_blocks_1x1 + 0x9fc
[0x2]   _pywrap_tensorflow_internal!dnnl::impl::cpu::x64::brgemm_convolution_utils::init_1x1_conf + 0x434
[0x3]   _pywrap_tensorflow_internal!dnnl::impl::cpu::x64::brgemm_1x1_convolution_fwd_t<71>::pd_t::init + 0x2f4
[0x4]   _pywrap_tensorflow_internal!dnnl::impl::primitive_desc_t::create<dnnl::impl::cpu::x64::brgemm_1x1_convolution_fwd_t<71>::pd_t> + 0x17c
[0x5]   _pywrap_tensorflow_internal!dnnl_primitive_desc_iterator::operator++ + 0x2c1
[0x6]   _pywrap_tensorflow_internal!dnnl_primitive_desc_iterator_create + 0x1de
[0x7]   _pywrap_tensorflow_internal!dnnl::primitive_desc::primitive_desc + 0x73
[0x8]   _pywrap_tensorflow_internal!tensorflow::MklConvFwdPrimitive<float,float,float,float>::Setup + 0x6d7
[0x9]   _pywrap_tensorflow_internal!tensorflow::MklConvFwdPrimitive<float,float,float,float>::MklConvFwdPrimitive<float,float,float,float> + 0x1a8
[0xa]   _pywrap_tensorflow_internal!tensorflow::MklConvFwdPrimitiveFactory<float,float,float,float>::Get + 0x14c
[0xb]   _pywrap_tensorflow_internal!tensorflow::MklConvOp<Eigen::ThreadPoolDevice,float,float,float,float,float,int,1,0,0,1>::Compute + 0x1ba0
[0xc]   _pywrap_tensorflow_internal!tensorflow::ThreadPoolDevice::Compute + 0x4a
[0xd]   _pywrap_tensorflow_internal!tensorflow::`anonymous namespace'::ExecutorState<tensorflow::SimplePropagatorState>::ProcessSync + 0x13f
[0xe]   _pywrap_tensorflow_internal!tensorflow::`anonymous namespace'::ExecutorState<tensorflow::SimplePropagatorState>::Process + 0xf58
[0xf]   _pywrap_tensorflow_internal!std::_Func_class<void>::operator() + 0xf
[0x10]   _pywrap_tensorflow_internal!tensorflow::thread::EigenEnvironment::ExecuteTask + 0x13
[0x11]   _pywrap_tensorflow_internal!Eigen::ThreadPoolTempl<tensorflow::thread::EigenEnvironment>::WorkerLoop + 0x4b6
[0x12]   _pywrap_tensorflow_internal!std::_Func_class<void>::operator() + 0xf
[0x13]   _pywrap_tensorflow_internal!tensorflow::thread::EigenEnvironment::CreateThread::__l2::<lambda_fe7aa395b13fe170862dcdb4d85eb030>::operator() + 0x38
[0x14]   _pywrap_tensorflow_internal!std::invoke + 0x38
[0x15]   _pywrap_tensorflow_internal!std::_Invoker_ret<void,1>::_Call + 0x38
[0x16]   _pywrap_tensorflow_internal!std::_Func_impl_no_alloc<<lambda_fe7aa395b13fe170862dcdb4d85eb030>,void>::_Do_call + 0x41
[0x17]   _pywrap_tensorflow_internal!std::thread::_Invoke<std::tuple<std::function<void __cdecl(void)> >,0> + 0x18
[0x18]   ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1> + 0x42

Standalone code to reproduce the issue
import tensorflow as tf

conv2d = tf.keras.layers.Conv2D(filters=8, kernel_size=(1, 1), padding='same')
relu = tf.keras.layers.ReLU()

@tf.function
def fused_conv_bias_relu(x):
    y = conv2d(x)
    y = relu(y)
    return y

x_shape = [1, 2048, 2048, 8]
inputs = tf.random.normal(x_shape)
outputs = fused_conv_bias_relu(inputs)
print("Success!")

Relevant log output
No response

@wsmigaj,
When running on GPU (with cuDNN version 7.6.3 or later), tf.nn.depthwise_conv2d backprop to filter (and therefore also tf.keras.layers.DepthwiseConv2D) now operate deterministically (and tf.errors.UnimplementedError is no longer thrown) when op-determinism has been enabled via tf.config.experimental.enable_op_determinism.
Could you please try to run the below command before executing the code on tensorflow v2.10. I tried and was able to execute the code. Kindly find the gist of it here.
!apt install --allow-change-held-packages libcudnn8=<IP_ADDRESS>-1+cuda11.2
Thank you!

@tilakrayal
Many thanks for your response. However, my bug report concerns execution on CPUs (not GPUs), specifically CPUs supporting AVX512 instructions. Hence I don't think the cuDNN version is relevant, since this library is only used on GPUs.

@wsmigaj,
I was also able to execute the given code without any issue/error on tensorflow v2.8, v2.9 and v2.10. Kindly find the gist of it here. Could you please create a virtual environment and test your code again. Thank you!

We have re-produced this issue, looking into it, will update later!

@tilakrayal The CPU installed in the system you used to run the code does not support AVX512 instructions (I've checked using the cpuinfo package in your Colab notebook). The problem occurs only on CPUs supporting these instructions.
@huiyan2021 Thanks for letting me know! Good to hear you've been able to reproduce the issue.

@wsmigaj This is an issue in oneDNN which we are fixing, you can try to reduce the input_size if possible to avoid the crash at the timebeing, for example "x_shape = [1, 64, 64, 8]", will let you know when the issue is fixed publicly.

@huiyan2021 Many thanks for the update and suggesting a workaround. For now, we'll keep disabling the AVX512 instructions using the DNNL_MAX_CPU_ISA variable (it's great it exists!), as it's less disruptive to our workflow than changing the shape of the inputs.

@wsmigaj The issue has been fixed by https://github.com/tensorflow/tensorflow/pull/58269, please check, thanks!

@huiyan2021 Thanks a lot for fixing the bug! I confirm I can no longer reproduce it with version 2.12.0.dev20221025 of the tf-nightly package.


Adding just subcommand target does not work as intended

Adding new target entry to justfile does not work unless a comment is added on the same line that defines the target name

A subcommand target without a comment isn't even in parsed_help_a, which is the list used to determine a subcommand. The fix is more complicated than at first glance.

One idea is make everything get added to parsed_help_a, and filter out the comment-less ones for print_help. This will probably take a lot of sed editing
Another idea is to make/use a different list for subcommand discovery in justify.

Considering changing this to wontfix. If a subcommand doesn't have a comment, it's "hidden", so it shouldn't be in tab complete. Thoughts @scott-vsi?

If you want to have tab complete help without writing a help, you can add a # after the case value, and it will show up in tab complete. This is the intended use.
This means that the help will display a blank line for this command/subcommand. This is the expect behavior. If there is a great need to hide empty help targets, a flag could be added to do this. But currently there is not enough demand for this.


[Feature request] Fetching and Grouping Album Assets by Date

Platforms
dart, Android, iOS
Description
Currently, the albumAssetCount method provides only the total count of assets within an album. While useful, it is insufficient for scenarios where grouping assets by date (e.g., by month) is required — a common feature in many modern image pickers.
I was able to achieve this functionality by combining multiple SQL requests and leveraging asset counts to create custom groupings. However, this approach is not very efficient and may result in performance issues for larger datasets.
Any suggestion on a better way ?
My workaround:
var firstAsset = await album.getAssetListRange(start: 0, end: 1);
var lastAsset =
    await album.getAssetListRange(start: assetCount - 1, end: assetCount);

var startDateTime = firstAsset.first.modifiedDateTime;
var endDateTime = lastAsset.first.modifiedDateTime;

int differenceInMonths = (startDateTime.year * 12 + startDateTime.month) -
    (endDateTime.year * 12 + endDateTime.month);
DateTime currentDate = startDateTime;

int lastIndex = 0;
for (int i = 0; i <= differenceInMonths; i++) {
  DateTime startDate = DateTime(currentDate.year, currentDate.month, 1);
  DateTime endDate = DateTime(currentDate.year, currentDate.month + 1, 0,
      23, 59, 59);

  var filter = CustomFilter.sql(
    where: '''
      ${CustomColumns.android.width} IS NOT NULL
      AND ${CustomColumns.base.modifiedDate} >= ${CustomColumns.utils.convertDateTimeToSql(startDate)}
      AND ${CustomColumns.base.modifiedDate} <= ${CustomColumns.utils.convertDateTimeToSql(endDate)}
    ''',
    orderBy: [OrderByItem.desc(CustomColumns.android.modifiedDate)],
  );

  var newAlbum = album.copyWith(filterOption: filter);
  var monthlyAssetCount = await newAlbum.assetCountAsync;
  String monthKey =
      "${startDate.year}-${startDate.month.toString().padLeft(2, '0')}";
  albumStatistics[monthKey] = AlbumStatistics(
      startIndex: lastIndex, endIndex: lastIndex + monthlyAssetCount);

  lastIndex += monthlyAssetCount;

  currentDate = DateTime(currentDate.year, currentDate.month - 1);
}

Why
Reason:
This feature would make it easier to rebuild common image pickers like those found in WhatsApp or built-in photo libraries. Many popular apps use this kind of grouping to improve user experience. Adding this capability directly to the library would align it with such widely adopted use cases.
Feature Request:
Introduce a built-in way to fetch assets grouped by timeframes (e.g., months), reducing the need for multiple SQL queries and manual calculations. This feature would enhance the library's usability for developers implementing custom image pickers and similar features.

AI Summary: The user requests a built-in feature to group album assets by date (e.g., monthly), as the current method of combining multiple SQL requests is inefficient for large datasets and common image picker UIs.


What is the FPS per second?

What is the FPS per second?
How can I change the FPS rate in the application?

It's not specified by default.
You may be able to control it via media_stream_constraints media_stream_constraints (ex: https://github.com/whitphx/streamlit-webrtc/blob/3ace08de428af2be262219fd248560371346bf6d/app.py#L84).
For now, this parameter is used as an argument of navigator.mediaDevices.getUserMedia() on the frontend to initialize the media devices, and video.frameRate can be set like this.
How is code like below though I have not tested it yet?
WEBRTC_CLIENT_SETTINGS = ClientSettings(
    rtc_configuration={"iceServers": [{"urls": ["stun:stun.l.google.com:19302"]}]},
    media_stream_constraints={
        "video": {
            "frameRate": { "ideal": 10, "max": 15 }
        },
        "audio": True,
    },
)

Sorry, it's not supported yet.
Wait for the next release.

It's available on v0.21.0


Discord requires upgrade to 0.0.12

The package needs to upgraded somehow, because right now it won't be launched. See picture:

I use 20.03 channel.
Notify maintainters
@ldesgoui @MP2E @tadeokondrak

It seems like it's in the pipeline already https://github.com/NixOS/nixpkgs/pull/97708. I think it will only be available in the channels once the Hydra tests pass.
To get Discord 0.12 right now you can run
nix-env -f https://github.com/NixOS/nixpkgs/archive/release-20.03.tar.gz -iA discord

How long does a hydra test take? I still don't have it on unstable.

This is now an issue again with Discord requiring an upgrade to 0.0.14, while the NixOS repositories only have 0.0.13
What can we do while waiting for the new version to land?

I guess there is not much else that can be done other than doing:
nix-env -f https://github.com/NixOS/nixpkgs/archive/release-<LATEST_VERSION>.tar.gz -iA discord

@zakkor Yea or if you manage discord with Home-manager you can do something like
let
  unstable = import  <nixos-unstable> {}; #Or however bleeding edge you wanna be.
in
{
#...
home.packages = with pkgs; [
unstable.discord
];
#...
}

The problem is discord is pinned to a specific version in nix, and version needs to be manually bumped by humans, and so it will forever be an issue until there's someway to "unpin" a package from a hash value, and let upstream control version releases.
Maybe a discussion should be opened around adding mechanisms for this.

Since NixOS is built to be reproducible, I don't think it would be possible to introduce something like that. I don't think a package is rebuilt unless the derivation has changed, and since a hypothetical discord-latest derivation would never change, neither would the package.
However there are bots for this, like r-ryantm. I don't know how it works, or why it doesn't seem to update discord automatically, but I think that bot is the way to go, I'll create a PR for this for now.

I think that bot is the way to go, I'll create a PR for this for now.

r-ryantm already updates Discord automatically using its updateScript, but normally someone gets to it first with the stable version. https://github.com/NixOS/nixpkgs/search?q=discord+author%3Ar-ryantm&type=issues

Is this because the updateScript isn't run often enough, or is it because some other reason? It seems to pick up the canary releases quicker than the stable, or is this just bad luck? The update script is great and all, but it's not really that useful if it isn't run often enough.

I don't think there is a good resolution for this problem within the constraints of nixpkgs and its infrastructure limitations at the moment, we have discussed this at length at this point, there is no real point to keep this issue open.
The "easy" solution at the moment is installing from archive/master.tar.gz whenever the update PR is merged.
A potential solution is writing a script that manages a pin locally.

It feels like something like this would potentially work well, it manages a new nix profile where Discord is installed from master while running update-discord. profilePath needs to be created manually, update-discord may need to be run as sudo if the user is missing write permissions to profilePath, all of that can be addressed with better scripts. It does not currently create the desktop icon thing, it's probably easy to fix up.
{ stdenv
, writeShellScriptBin
, profilePath ? "/nix/var/nix/profiles/discord-in-a-profile/profile"
}:
stdenv.mkDerivation {
  pname = "discord-in-a-profile";
  version = "0.1.0";

  updater = writeShellScriptBin "update-discord" ''
    echo 'Installing or updating Discord'

    NIXPKGS_ALLOW_UNFREE=1 nix-env \
      --profile ${profilePath} \
      --install \
      --file https://github.com/NixOS/nixpkgs/archive/master.tar.gz \
      --attr discord
  '';

  runner = writeShellScriptBin "Discord" ''
    exec ${profilePath}/bin/Discord $@
  '';

  dontUnpack = true;

  installPhase = ''
    mkdir -p $out/{bin,share}

    cp $updater/bin/update-discord $out/bin/
    cp $runner/bin/Discord $out/bin/
  '';
}

Closing as there are no other steps forward.


Copy code missing ending ` tick

Using the copy code button a lot of the code is missing the ending tick (`) e.g. https://learn.microsoft.com/en-us/azure/container-apps/jobs-get-started-cli?pivots=container-apps-job-manual#query-job-execution-logs

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

ID: 8df08492-a66e-6e14-e5af-d88fb37f86b2
Version Independent ID: d05fc750-e8ab-c48b-5603-188f912094d2
Content: Create a job with Azure Container Apps
Content Source: articles/container-apps/jobs-get-started-cli.md
Service: container-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@ehalsey
Thanks for your feedback! We will investigate and update as appropriate.

@ehalsey
Thank you for bringing this to our attention.
I've delegated this to content author, who will review it and offer their insightful opinions.

Thanks for your feedback and your contribution to Azure docs.
Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.
To learn more about our feedback systems, please see Provide feedback for Microsoft Learn content.
#please-close


No Mattermost notification after update to 1.13.1

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
Hi,
i am using Uptime Kuma on a Raspberry device in docker.
Used docker container:

uptime-kuma:1-alpine

After update from Version 1.11.4 to 1.13.1 the configured Mattermost notification seems
not to work anymore for downtimes etc.

The Test notification from configuration menu works fine

👟 Reproduction steps

Setup a Monitoring for a website
Configure Mattermost notification (+ Test)
Wait or cause a downtime for the website
Downtime is tracked by Kuma Monitoring
But no notification is send in Mattermost

The Mattermost notification is set as default.
👀 Expected behavior

A notification in Mattermost when the monitored website has a downtime

😓 Actual Behavior

But no notification is send in Mattermost

🐻 Uptime-Kuma Version
1.13.1
💻 Operating System and Arch
Debian 9.13 (ARM)
🌐 Browser
Firefox (does not really metter for this issue)
🐋 Docker Version
19.03.15, build 99e3ed8919 (ARM)
🟩 NodeJS Version
n/a (Docker container)
📝 Relevant log output
No response

Just checked the last Mattermost pull request, and found that I missed @nietzscheanic's comment. The problem should be fixed in the next release.
https://github.com/louislam/uptime-kuma/pull/1298#issuecomment-1062858339

Just checked the last Mattermost pull request, and found that I missed @nietzscheanic's comment. The problem should be fixed in the next release.
#1298 (comment)

Wow! Thanks a lot for the quick check and response!
Looking forward to test out next release!
Have a great weekend!
Best,
Dolo


qa: run scripts/lean4lean_check.py as part of run_before_push.sh and pre-push.sh

This is a Python alternative to #438. It does not introduce any new Python dependencies.

@teorth I needed to check this PR

@teorth I would suggest reverting this PR. Because this other PR followed the claims process (disclosure: it was mine), and I believe it is helpful to everyone if the claims process is followed.

@teorth I would suggest reverting this PR. Pietro and I are still working out how to make sure that we can keep lean4lean up to date and make it work without further intervention. This PR was made without going through the CONTRIBUTING.md process.
Because this other PR followed the claims process (disclosure: it was mine), and further because we are still deciding how to keep lean4lean itself up to date with our toolchain, i think this PR is unhelpful at the moment.

@euprunin
I don't see a quality issue here. We have set up a contribution process precisely to ensure that people's work and time is respected. This PR does the exact opposite of that. I am well aware of how open source projects work, but there is a difference here. We would like people to take up tasks and work on them without worrying that someone else will override their work in the mean time. Likewise maintainers have an easier time assessing each task and managing them. Making PRs by completely ignoring this, violates this collaborative spirit. Even in open source projects, it is quite normal to have a contributions process (e.g. the lean4 repository for example).
Further I am quite sure that the scripts we have already written are fine. They don't call any unconventional dependencies and they work well within the versioning constraints of lean4 and mathlib.

@euprunin : One thing I agree on: We are decidedly not following the conventional open source process where overlapping PRs are fine. The whole point is to ensure respectful academic collaboration, not unrestrained competition and confusion.

@euprunin : This is also explained in the CONTRIBUTING.md file : https://github.com/teorth/equational_theories/blob/main/CONTRIBUTING.md#additional-guidelines-and-notes


adoc content in tables

adoc content is possible in tables (by just adding a in column spec everywhere
e.g. in descriptions, need to set  .withSwaggerMarkupLanguage(MarkupLanguage.ASCIIDOC) otherwise the adoc content is converted to markdown
updated some plugins and dependecies (e.g. removed javaslang and moved to vavr)
removed mavenCentral() as it should not be required as jcenter() contains everything in central (should make dependecy resolution a little faster)
regarding the deprecation warning for the git pages publish task, I will provide another PR with the required use of the new plugin. See their description for details.

close #162

Coverage increased (+0.3%) to 88.394% when pulling 6f21278aedc46cc40d3e3d55362211b598a6e0b7 on atomfrede:162-adoc-in-tables into 038ff3a40e32ab42439c7e9ec3be032008fad247 on Swagger2Markup:master.

Coverage increased (+0.3%) to 88.394% when pulling 093c00c3836bd11ca67ff6cbffdbf68571ce5aad on atomfrede:162-adoc-in-tables into 038ff3a40e32ab42439c7e9ec3be032008fad247 on Swagger2Markup:master.

thx


HV-1730 JavaBeanExecutable fails to initialize for enum type

https://hibernate.atlassian.net/browse/HV-1730
Supersedes #1049 .
It turns out the problem is really caused by the lack of a -parameters flag when model classes are compiled. When the flag is missing, we don't have any information about which parameter is implicit/synthetic, and the existing code assumes we always have that information. As a result, it inspects all the parameters without finding the implicit/synthetic ones, and ends up triggering an ArrayIndexOutOfBoundsException.
The solution provided in #1049 solves the out-of bound exception, and goes a little further by trying to "guess" which type is implicit/synthetic or not based on type erasure. This will work in some cases, but will lead to incorrect results in other cases.
This PR just takes the fix from #1049, and adds the following changes:

Splits marko's commits in two, so that it's easier to revert the fix and only keep the test, to reproduce the problem.
Adds a warning when parameter metadata (isImplicit/isSynthetic) is missing, because that may lead to incorrect generic type information being detected for method parameters.

I also checked that Marko's changes fix https://github.com/quarkusio/quarkus/issues/3284

Hi @yrodiere , @gsmet . Just want to say thanks for picking this up! Have almost no free time these past few weeks.

Hey @marko-bekhta ,
Glad to hear from you! We'll be there when you have more time :).

Merged, thanks to both of you!


⚠ PrivateHD has degraded performance

In 09a0b94, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 8777 ms

Resolved: PrivateHD performance has improved in eece27c.


Local only indicator

Summary
Add indicators for local-only and public notes on the right top:

(screenshot icon is customized - in the PR the icon is actually :biohazard:, keeping it constant with the compose note modal)

Hello, any update on this?
FYI, the CI failure is unrelated to this PR and should disappear once merged.

localOnlyかどうかの情報ってレスポンスに含めるのやめた気がするけどどうだっけ

$ curl -X POST -k -i 'https://c2.a9z.dev/api/notes/show' --data '{"noteId": "86yiwwyemv"}'
{"id":"86yiwwyemv","createdAt":"2020-05-06T06:27:05.558Z","userId":"81g9ufohhb","user":{"id":"81g9ufohhb","name":null,"username":"aqz","host":null,"avatarUrl":"https://d20bb5quu0uyhd.cloudfront.net/m/thumbnail-77a5c57d-af12-40c8-828b-a212fbdf4f8f.jpg","avatarColor":"rgb(111,118,116)","isAdmin":true,"isCat":true,"emojis":[]},"text":"ろ～かるおんり～","cw":null,"visibility":"public",
"localOnly":true,
"renoteCount":0,"repliesCount":0,"reactions":{},"emojis":[],"fileIds":[],"files":[],"replyId":null,"renoteId":null}

まだあるっぽいべ

というかBiohazardいい加減やめませんか？

それはまた別のissueにすべきでは

publicのアイコン要るかな？

Sorry for late checkup :<
Public icon can be removed from this PR (lmk what you think), although I do think adding it would be nice to make the UX more constant.
Local only indicator is needed, as people talking over TL (i.e. the person is reacting to the note, but with a separate note instead of the reply function) have caused some confusion to remote users when a local only note was involved.

publicのアイコン要るかな？

「Public」も「Home」も「Public (local only)」も対等な公開範囲のうちの1つと思ってるので
「Public」も常に表示するものかなと思ってました。

いったんlocalOnly表示するだけにしよう

👍


Better window service for tokenizers that do not decode

It is very common for tokenizers to only have a tokenize or count endpoint, and not having a decode endpoint. Currently, LocalWindowService
CohereWindowService and NoDecodingWindowService work around this by assume that concatenating the tokens from the tokenize endpoint will result in . However, this is not actually true for various reasons.
For instance, the text-bison tokenizers is not guaranteed to tokenize on the boundary of UTF-8 characters - it can end up with partial bytes within a UTF-8 character. These partial bytes are lost because HELM requires tokenizers to return strings, not bytes.
We should rethink about how we do windowing in these cases.

Also noting that the consequence of using NoDecodingWindowService with text-bison is that there may be small character-level corruptions for uncommon UTF-8 characters in the prompts to text-bison.

More discussion:
Basically we need a function truncate(original_string, num_tokens) -> truncated_string where truncated_string is a exact substring (or a minimally modified substring) of original_string.
LocalWindowService does this by doing decode(encode(original_string)[:num_tokens]).
You could also do "".join(tokenize(original_string)[:num_tokens]).
But neither of these methods are actually guaranteed to be produce an exact substring.


Added DraggableArea which limits movement of the Draggable to container

I'm aware that this is most likely not the correct way of achieving this effect, for the following reasons:

I'm not sure if ancestorRenderObjectOfType() can be used this way, based on the docs
Even if 1) is fine, this implementation has a big limit in that it simply ignores the drag if it goes beyond the bounds of the parent DecoratedBox, rather than finding the closest valid point based off of the pointer position. The latter would be quite complicated unless there's some built-in classes to do it.
Right now it only supports DecoratedBox parents

Example usage to limit the Draggable area:
Container(
  width: 280.0,
  height: 280.0,
  decoration: new BoxDecoration(
    color: Colors.grey,
    shape: BoxShape.circle,
  ),
  alignment: Alignment.center,
  child: DraggableArea(
    child: LongPressDraggable(
      hapticFeedbackOnStart: true,
      child: Container(
        width: 45.0,
        height: 45.0,
        decoration: new BoxDecoration(
          color: Colors.orange,
          shape: BoxShape.circle,
        ),
      ),
      feedback: Container(
        width: 45.0,
        height: 45.0,
        decoration: new BoxDecoration(
          color: Colors.red,
          shape: BoxShape.circle,
        ),
      ),
    ),
  ),
)

It's a very interesting idea. We'd have to make it more robust and remove some of the limitations you mentioned in order to land it in the framework. However, maybe this could live in a separate pub package?

Personally I think until those limitations are removed, this widget won't really be useful as the drag action feels junky/laggy due to the inability of calculating exact shape bounds and that ruins the user experience. If I get around to remove that limitation I might think of a package or resubmit a PR.

@eligt Can we close this PR until those limitations are removed?
Also, feel free to file an issue and we can discuss over there how this could be done.

Sure, you can close this one.


Fix for missing markerId

Sometimes after clearing and putting new pins map crashing when selecting a pin. From stacktrace I found that it can't find item in the dictionary.

@damiansikora85 Sorry for the late reply and thanks for your contribution! I'm wondering why the dictionary isn't cleared. That may be potential memory leak. Do you have any repro project you can share?

Hi, I create a sample project with this issue here: https://github.com/damiansikora85/ClusteringTest.
Repro steps:

launch app
click on map to add some pins
click one of the pins (label appears)
click Clear button
click on the label of previously selected pin

cheers

Hello how to include the project while having access to the source code?


filter objects before bulk insert

https://app.asana.com/0/1137432207089210/1146643984575450

Approved


Site design

I've done a lot of thinking about how we want to show package metadata this weekend, and I'm posting my initial draft designs here for discussion. Even though I'm planning to start implementing some parts of this tomorrow, everything is still up for open and frank review in this thread.
When I started this process, my main goal was to move away from the approach of trying to display all metadata about multiple versions of a package inline in the search results. It's already too much to take in and also doesn't show anywhere near what people need to know to make informed decisions about package quality.
The idea, as discussed previously, was to move to a "page per package" approach giving much more scope for displaying information that people can use to judge the maturity, quality, and maintenance history of a package.
I also rolled back my thinking displaying metadata from multiple package versions as part of this process. The fact that we capture all metadata from multiple versions it critical, but it's only occasionally useful for people to see. When it's useful, it's instrumental, but that tends to only be around the release of new Swift/operating system versions. The fact that we have this data is a huge advantage, but I want to be smart about displaying it.
So, here's my first draft of the per-package page, where I spent most of my time and thinking this weekend.

Some notes:
Display of multiple version metadata
You'll see an example of my idea for dealing with changing metadata between significant versions in the Languages and Platforms section. Most packages will use the same version of Swift/iOS/macOS/etc. for every version. It doesn't change that often. So let's only display it when it changes!
If all three significant versions use the same Swift versions, it just gets displayed once. Only if (in this example) the new beta upgraded Swift version would it be shown like it is here.
Prominence (or lack of) of the Swift version
You'll notice that one of the (seemingly) most essential bits of metadata, the version of Swift that's supported, is quite far down the listing. At first, this worried me too, but I think I'm OK with it after playing with it today. I think if we can get the metadata from git/GitHub about the number of releases, project start date, commits, etc. that gives an excellent indication of how active a project is. Active projects tend to support the latest version of Swift.
The Swift version needs to be there, and it is, but I don't think it's as important as that other metadata.
Contributors
Here's a basic plan that I think will work well for this line of metadata.

Any contributor with more than 10 commits is eligible to be listed here. This rule will save projects where someone fixes a typo in a README in a newly released project with just an "Initial commit."
For all eligible contributors, they are listed if they have made more than 5% of the total commits.
The name should be fetched from the GitHub API for the username
The link should go to the contributors GitHub profile.
The name and link should be able to be overridden by our extra metadata file. The list of contributors should be custom at this point, and we should replace the method above with only the names and links in the metadata file. The link may point to any web site, not just their GitHub profile. (Yes, this opens up the possibility of spam, but let's deal with that as it comes up).

Quality Score

I'm reserving some space with the grey [X] box on the right-hand side of the page for the "package quality index" score or whatever we call it. However, there are lots of decisions to make before we get to the specifics of this design. I'll raise a separate issue with some thoughts on it, maybe not tonight, but at some point.

Missing GitHub data
There metrics the sentences in this design that we're not currently collecting from the GitHub API. I didn't let that limit what I planned, but I realise we won't be able to implement all of this immediately, and that's OK 👍
Dependencies
The most obvious thing missing from this design is dependency details. I want to add this, but I feel it can be after an initial release.
Other interesting metadata
I had a quick chat with a friend of mine about this design earlier today. He mentioned a couple of metrics that he uses when evaluating a dependency. "Does it link against UIKit?" was one interesting one. "Does it swizzle any methods?" is another. I think this kind of metric might be really interesting to play with after an initial release.
I've also done some very preliminary thoughts on the home page. This gets affected by my thoughts on search though, which I'll post next! Here it is for reference though.

Pinging @finestructure just in case you didn't get a notification. No rush for feedback, maybe we can catch up over it tomorrow some time.

Oh, I didn’t - thanks for the ping! Checking now :)
I’ve also readied the next PR for review/merge.

Updated with changes from this morning's discussion:

Oops, forgot that we also decided against the logo at the top:

Love the colours and the little swift and apple icons, looks great!

Some notes after implementing the markup:

Progress
It's all got placeholder markup now, apart from:

The copy button is missing, added in #74.
Styling on the lists for the general metadata, releases, and the languages and platforms sections is still missing. I'll complete this after the view model is in progress.
The readme is missing, this can come after an initial public release as there will be issues reading in and formatting thousands of README files!

Issues and changes to the design

I simplified the markup around the default branch entry in the releases. The original design could have been really tricky to calculate with all the permutations of "What if it has no stable version, but has a beta version, but that beta version isn't on the same tree as the current master?" etc... The purpose of this section is to see how active a project is so this works:

If there's a stable version, what's the version number and how long ago was it released?
If there's a beta version, what's the version number and how long ago was it released?
What was the latest commit to the default branch?

The platforms can be really long, and a little difficult to parse when there's a full set of Apple platforms, and they change an upcoming release. Not sure how to fix this apart from splitting them into a nested bulleted list, which I don't really want to do.

My gut feeling says that this design will be fine for an initial release at least.

Alright, I iterated on this design a bit. First of all, I think the releases section will look better like this:

Icons in circles were hard to get right as they were so small, having them in lozenges gives the icons more space, and I think it makes it generally clearer what's happening too.
Then, the Language and Platforms section. If there's a change of language/platform we could do this:

Then, if there's no change in version information we could either do this:

Or, as there's no need to even reference the version numbers or branch releases if everything is the same, we could even simplify that last one to this:

What do you think?

Oh, I like these lozenges a lot!
It took me a moment to figure out how to read the "In"... in L&P (probably partly because the library version 5.1.0 is so close to the swift versions). Maybe
Version (5.1.0) supports:
...

Versions (5.2.0-beta1), and (master) support:
...

or all together:
Versions (5.1.0), (5.2.0-beta1), and (master) support:
...

would read a little better?
That would also mean it's structurally identical and easier to read overall.
I think always referencing the package versions would still be good. I.e. I think I prefer the next to last version over the last one. Might be something to look at and judge on a couple of full pages though.
Not part of this change but I just happened to notice it:
Are we intending to have times granular like that - "12 minutes ago" - or should we just use "today"? It might suggest near-time updates that we may not actually have.

Your suggestion on the wording is much better. 👍 I also agree that having all three tags visible in Language and Platforms makes it clearer why they are tags in the releases section above so I'm happy to go with that too.
I'll get these into the markup and CSS.
I think this approach also makes it easier to actually implement this too, which was at the back of my mind when designing it 👍

As always, when transitioning to markup this didn't quite look the same. I'm really torn on what looks best between three options for how this looks.
I've included the whole page as the balance of this bottom part is very much affected by the top of the page.
Option 1:

This is the tightest of the layouts and was my initial gut feeling, but the layout being out of line with the rest of the lists going down the page rubs me all kinds of wrong.
Option 2:

The lozenges are now in line with the rest of the page, but they still feel kinda disconnected from the lists above.
Option 3:

The final option I played with is to bring back the bullets on the top-level list, but that feels weird as these don't feel like they should be bulleted.
If you want to play with them all three versions are checked in and pushed (Option 1, Option 2, and Option 3.
Feedback would be very welcomed! Even if it's not any of these options, I'm happy to tweak more.

By the way, if you download all three versions of those images and just use quick look to flick between them they should all be perfectly lined up so you can see the differences clearly.

I think you're right that 1) looks a bit unbalanaced. And this will only get more pronounced when the top paragraph is actually filled out with content.
Both 2) and 3) are better in that regard but I feel 2) suffers a bit from an "inverted pyramid" effect:

I think the bullet in 3) might be best and perhaps they could be motivated better if we add a word of leading text? Like so:

Version (5.2.0) supports:

...

Versions (5.3.1-beta.1) and (master) support:

...

Another thing that might be worth trying is to find another (bigger) bullet that might work alongside the icon bullets in the first paragraph. It seems most of the disbalance stems from them being bigger than the bullets below and masking the fact that the text blocks are actually left aligned. It pulls the top paragraph more to the left, if that makes sense.
But to be honest, I think 3) with perhaps the leading "Version(s)" would be fine for launch!

Another quick thought was (obviously without the font size/spacing issues :D ):

Maybe a but further out and aligned with the "MIT" license badge

Actually, this may have some merit. It just struck me that the lozenges in the L&P section draw the eye but it's not the important info - the swift and platform versions are. I don't think we'll want to put all those in lozenges but maybe pulling them out does help a bit?

Adding a bullet certainly helps. Ironcially I had that word in there at first, but without the bullet, it doesn't work well there so I removed it while iterating. It's better now it's back:

Pulling the tags out is interesting, but as you say it's the wrong information to pull out. The natural extension to this is to put the Swift and Platform support in lozenges, but that along with the three green lozenges would be too. many. lozenges. 😂
We could use colour to draw the eye to the Swift and Platform versions, but I'd say not in lozenges. Maybe something like this?

Note: Even though the platforms look black still, it's the blue from the header. We don't want too bright a colour there as most of that sentence will be in that colour.
Honestly, I'm not in love with the new design of this bottom area. I think I'll submit the version with the additional "Version" wording,  but without those final colours for this PR and we can merge that and think on it over the next few days, and as the data goes in.

I agree, let's go with 3) + Version(s) for now!

👍 I'm updating the snapshot test and will submit a PR.

I couldn't leave it alone... 😬
Several changes, but I think I'm done!

Everything now lines up with the left-hand package title rather than being indented. This means the metadata section with the icons at the top feels slightly indented because of the icons, but it works.
Removed the lozenges, they were too heavy being repeated so much and in such close proximity. Went back to the original circle design.
Removed the language and platform icons, these are now just a bulleted list. It was all just a bit too much.

I think it's good, but feedback is always welcome.

Very nice! I agree, while the lozenges looked nice they were heavy. I wonder if the stable release colour has a bit low contrast but that's tweakable, plus ... dark mode! 😬

I'm going to call this done. ✅


add custom http requrest(#3359)

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.
#3359

ddddddone

@baiyaaaaa 能否支持一下Promise呢 https://github.com/ElemeFE/element/pull/3363

@QingWei-Li  这个支持大概什么时候能发布到npm呢？最近有新版本吗？最近希望能快点有个新版本，因为这个比较急


objects.invert

Creates a new object with key-value pairs inverted, in the case of duplicate values the latter value will overwrite the previous
Checklist

[ ] implementation
[ ] tests
[ ] jsdoc

Details
const res = Objects.invert({ a: 1, b: 2, c: 1 });
console.log(res);
> { '1': 'c', '2': 'b' }

References

_.invert

FYI, if you want to take on arrays.frequency it's all yours.

@jkvyff Your work on objects.invert got pushed to the master branch and some of the tests are failing.
https://github.com/vanillaes/absurdum/commit/6832265dc3e3ecec800e5f6ed9483ee603eb4d0b/checks?check_suite_id=350350872

My mistake, I switched branches before making the changes to the tests.

It's all good
Not publishing a broken build to NPM is what matters and the CD pre-checks make that impossible. 😁

Added in 0.47


qaoa: var assignment mode

m_varAssignmentMode: Determines the optimal configuration found by the qaoa, not only the optimal value as before. This can be handy for many optimization problems where we do not only seek the optimal value, but we are interested in the solution as well.
Had to edit Accelerator.hpp (see code) as the number of shots needs to be adjusted during the run of the qaoa algorithm before the var_assignment_mode routine starts. It would be good to think about a better way to adjust parameters of accelerators during run of the program. Is there any reason it has not been implemented yet?

Hey @Milos9304 thanks for this contribution! I've finally got a bit of time to review it. I'm a bit confused about what you are trying to accomplish. Perhaps you can provide a bit more of a description about your use case.
It is true that if you run with an Accelerator without shots set, then you'll only get expectation values on the cost function. If you then run with a shots-enabled Accelerator you'll get a bit-count dictionary that you could use. As for updating the shots on a given Accelerator, we have the updateConfiguration() method that you could use instead of adding another method to Accelerator.

Thx @amccaskey, I'm happy to explain. Perhaps I confused you with the terminology I used, I apologize,  because what I am trying to achieve is really simple. E.g. for maxcut problem, xacc is currently able to find the maximum cut value but not the partition of graph nodes into two sets which requires sampling the ansatz measurements with the optimal ansatz parametes found. In qiskit for example you run
qaoa_result = qaoa.solve(qubo)
print(qaoa_result)

with output
optimal function value: -2.0
optimal value: [0. 1. 0.]
status: SUCCESS

What I aim to achieve is the optimal_value which returns the found solution to the given qubo, or more precisely in our case(since xacc does not work with qubo formulations, but we directly specify problem hamiltonians) we determine the computational basis state corresponding to lowest eigenvalue of the problem hamiltonian.
And thanks for the updateConfiguration suggestion, I missed that. I'll update my code.


 How do i get the last insert id ? It seems that cursor.lastrowid or connection.insert_id() are not available:
                if data is None:
                    query = 'INSERT INTO solutions(origintime, lat, lon, elev, region) VALUES(%s, %s, %s, %s, %s)'
                    qparams = (dt_formated, lat, lon, elev, region)
                    try:
                        with conn.cursor() as cursor:
                            yield cursor.execute(query, qparams)
                    except Exception as e:
                        yield conn.rollback()
                        logging.error(e, exc_info=True)
                    else:
                        yield conn.commit()
                    # quake_id = conn.insert_id()
                    quake_id = cursor.lastrowid
                else:
                    quake_id = data[0]
                    crt_report_path = data[1]

Sorry, i think my insert statement was failing.


Youtube search does not work

When trying to search for a song, it does nothing. One line in server console:
[2016-03-31 22:23:55] SocketServer (debug) <IP_ADDRESS> sent: {"type":"youtubeSearch","data":{"query":"test"},"id":7}
And few errors in Chrome client console:

Also, i have SSL disabled.

Errors are normal, they happen because of adblock/YouTube player.

Yep, as said above those are normal.  Is there anything else in the server console that indicates why the search failed?  Have you input an API key for YouTube in the serverconfig?

I tried it in Firefox without any extensions and it still doesn't work, neither in Chrome incognito mode.
And no, nothing in server console except the line i posted before.

@Tonysp No errors indicating why the YouTube search would fail
Make sure your YT API key is set as "Server key" in your Google Developer Console and you have it set in your serverconfig.js files aswell.
Also make sure you have the latest version of musiqpad

Solved... I was using Browser key instead of Server key. You should specify which key to use in the example config so it doesn't happen to someone else. Thanks for the help!


feat: MYZ-7754 added hideinfobtn prop to ZCardDictionary

Feature: MYZ-7754
added "hideinfobtn" prop to ZCardDictionary
Motivation and Context
To be able to use it on "AddOrTryDictionary" modal.
Priority

[ ] 1 - Highest
[ ] 2 - High
[x] 3 - Medium
[ ] 4 - Low
[ ] 5 - Lowest
[ ] 6 - Not a Priority

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] Feature (non-breaking change which adds functionality)
[ ] Component (add a Component as approved dy Design System)
[ ] Docs (add documentation)
[ ] Chore (changes that adds small enhancement)
[ ] Breaking (fix or feature that would cause existing functionality to not work as expected)

Abstract
Screenshots
Note
ref: https://zanichelli.atlassian.net/browse/MYZ-7754
Component and Fix approval flow to Master branch
A Pull Request to be merged must have two approvals, one from a member of the product team who developed it and another from a member of the dst dev team other than the team representative.

Riesci ad aggiornare anche lo storybook?


Why is windows 10 reporting this one as a Trojan ?

I tried to download the exe file but Windows Defender (virus and threat detector thingy) is continuously preventing the download by reporting the file to be a Trojan.
How to cure this one ?

Hello,
Windows detecting it as a trojan is to be expected, as the program has behaviours such as checking processes, terminating processes and communication directly with Windows. Since it's not a signed app, Windows Defender assumes it is a virus.
There are a few ways you can solve this.

You can add an exception in Windows Defender here.
You can compile the code yourself

If the download itself is being prevented, you can temporarily disable windows defender, and re-enable it after the download is complete. (However, I don't really recommend you disable it.)

lmao fixed it by compiling it myself thnx tho!


Added jobs resource

Signed-off-by: Jake Turner<EMAIL_ADDRESS>

/azp run


Cache multiple zstd frames in CompressedCarV1BackedBlockstore

We currently only cache one zstd frame:
https://github.com/ChainSafe/forest/blob/79a1fd99928a69e60b8957b13e6f735b421cc027/src/car_backed_blockstore.rs#L335
But

executing tipsets is roughly 5x slower with compressed snapshots than without on my machine. A cache of decoded frames should close that gap, though.

@lemmih, in slack

We should cache more frames and see if that helps.

Note that we eventually want multiple CAR files sharing a single cache.

It doesn't make sense to work on this until the CAR store has matured. Otherwise, it'll just have to be rewritten.

Closed by https://github.com/ChainSafe/forest/pull/3288


feat: develop and deploy contract on solana

Solana: https://solana.com/
Rust: https://www.rust-lang.org/

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


feat(scripts): add linux deb & rpm package support to install script

WIP: This is still a WIP but is nearly complete. There are a few test failures for deb packages that should be fixed shortly.
Adds support for Linux deb & rpm packages to the install script. A new --use-native-packaging flag has been added to use package installation instead of the current binary installation method.
https://github.com/SumoLogic/sumologic-otel-collector-packaging/pull/28 contains fixes for packages that are required for the package installation via install.sh to function. A new package release is required after that PR is merged.

What are these Python scripts and docker-compose config for? Since they're so big, I'd prefer to add them in a separate PR, with some minimal documentation on how to use them, maybe some additional tooling.

The docker-compose config is a way to run both the tests against both deb & rpm packages on platforms that don't support it (e.g. macOS). It was quite helpful developing against it. I plan to add a job to test RPMs in CI as well.
Systemd requires PID 1 which doesn't easily work with containers. The Python scripts are a hack to simulate systemd & journalctl for the purpose of testing.
I agree that the Dockerfiles, config & Python scripts don't belong in this PR. I'll open a separate PR for that work and add some documentation.

I'm currently refactoring the specs & checks to remove a lot of the duplication. In doing so I discovered that I broke FIPS installation, hostmetrics installation with Linux packages only, and a few other install paths.
The ownership of config files differs between, not only binary and package installs but, non-systemd binary and systemd binary installs. This is why some of the specs check for rootUser as an owner and others check for systemUser. I'd like to drop non-systemd support in the install script to further simplify it. Is this something that we can do? @swiatekm-sumo @portertech

@amdprophet once we're "all-in" with native packages, we can look to deprecate/remove non-service managed installations.

@amdprophet What is the status of this change?

@amdprophet can this be closed, since we are moving to the packaging repo?

We reimplemented this work in https://github.com/sumologic/sumologic-otel-collector-packaging.


Rename transition.each(type, listener).

Seems like transition.on(type, listener) would be a better name, and avoid the confusion with transition.each(listener). I suppose there’s a risk that it would look like you’re trying to transition listeners on selected elements, but that’s obviously not the sort of thing that could be transitioned.

Renamed transition.on.


Add is_iter_datapipe_config

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (e0b5315) 100.00% compared to head (1941192) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #316   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          319       319
  Lines        10009     10013    +4
  Branches       966       966
=========================================
+ Hits         10009     10013    +4

Impacted Files
Coverage Δ

src/gravitorch/datapipes/__init__.py
100.00% <100.00%> (ø)

src/gravitorch/datapipes/iter/__init__.py
100.00% <100.00%> (ø)

src/gravitorch/datapipes/iter/factory.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Endless Clone when importing on PowerPC

Note:
We are using ppc64le so we have to build from source. After all installation we try to import mxnet and then python shell get stuck. We looked into system trace and found that libmxnet.so is endlessly forking at some point and finally freeze CPU. We followed the building process exactly as what the documentation provided.
Description
Environment info (Required)
ppc64le  GNU/Linux
what to do.
1. install and build mxnet on a computer with ppc64le architecture and then build from source. (the build command is listed follow).
2. open a python shell and run "import mxnet as mx", then it will get stuck.

Package used (Python/R/Scala/Julia):
I'm using python
Build info (Required if built from source)
make -j $(nproc) USE_OPENCV=0 USE_BLAS=openblas USE_CUDA=1 USE_CUDA_PATH=/mycudapath USE_CUDNN=1
Compiler (gcc/clang/mingw/visual studio):
g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
MXNet commit hash:
7d0881036959f383bab7efa22a80a9caa419274c
Build config:
(Paste the content of config.mk, or the build command.)
Steps to reproduce
(Paste the commands you ran that produced the error.)
After build mxnet and install python dependency.
Just start a python shell and run
import mxnet as mx

then the system hang.
Error Message:
You can observe the infinite fork in this system trace file.
trace.txt

@mxnet-label-bot update [Bug, Build, Python]

@Lucasyc Could you please try to build MXNet from source again with the latest Master and see if the issue still persist? Thanks!

@Lucasyc We are closing this issue for now due to inactivity from 90+ days. Please feel free to re-open it if you are still facing the issue. Thanks!
@nswamy Could you please close this issue? Thanks!


Return static vectors from incident for unique-indexed columns

This is a long overdue change that is important for consistency and predictability. It may be a small change but be warned that it is definitely breaking!
Closes #15.

Whee, this broke BipartiteFreeDiagram, I'm assuming just unboxing the vector to then apply add_part! and such is the move, we don't want methods of those guys that actually take in SVectors?

Correct, the SVector puts the size in the type, so passing SVectors around will proliferate the number of types we have to precompile.


CircuitPython Asyncio Support appears broken

I'm trying to use this with Asyncio in CircuitPython on an RP2040-based Adafruit MacroPad and I'm getting import errors and/or attribute errors whenever I try to use any of the async features.
Seems like it's trying to import the Micropython version of Asyncio, and to install that alongside CircuitPython doesn't look very viable (as the dependancies aren't drop-in replacements).  I hacked the module a bit to get it working with CircuitPython's asyncio and it doesn't seem like you need to make that many changes.
I don't know if this is doing it right, and it's not thoroughly tested as I'm not that familiar with how the module's internals work but this appears to run as intended, I think you just need to make all the async functions use ints everywhere and import asyncio instead of uasyncio:
(This deletes the try-except, which I think is necessary for some CircuitPython versions that can't support asyncio due to memory limitations, I only removed the block so that in my case it'd fail if I didn't have the correct deps installed.)
elif _implementation == "circuitpython":     from micropython import const     import asyncio     time_sleep_us = lambda usec: time.sleep( usec/1_000_000 )     time_now_us = lambda: int(time.monotonic_ns() / 1_000)     time_diff_us = lambda x, y: x - y     asyncio_sleep_ms = lambda x: asyncio.sleep_ms( x )

Thanks for reporting! I'll look into this asap

I think I'll change that part as follows:
elif _implementation == "circuitpython":
    from micropython import const
    try:
        import asyncio
    except:
        pass
    time_sleep_us = lambda usec: time.sleep( usec/1_000_000 )
    time_now_us = lambda: (time.monotonic_ns()+500)//1_000
    time_diff_us = lambda x, y: x - y
    asyncio_sleep_ms = lambda x: asyncio.sleep_ms( x )

You are completely right about importing asyncio instead of uasyncio on Circuitpython. I tested now with on a RP 2020 "Adafruit CircuitPython 7.3.3 on 2022-08-29; Raspberry Pi Pico with rp2040". Since asyncio might not be installed, I left the try/except.
I have tried to avoid floating point so I put a integer division with rounding instead. The code you proposed should also work.
I run the regression tests and it seems to work fine.

Is it working well now for you?

Works now, but the version in the commit has "ttime_now_us" instead of "time_now_us".  Fixing that typo fixes everything.

Thanks so much for pointing that out!! Now corrected.


Cannot easily change capitalization of a username

Attempting to change not_Spine to Not_Spine throws an error of how Not_Spine is already taken. The system should recognize that I'm just changing the capitalization and not throw this error.

Fixed in 0d588875a1f1899bb49d70513a0b77aa757fd4ca


Add List UI component

Current Behavior
To add new UI component.
Desired Behavior
A list is a commonly used UI component that displays a collection of items in a vertical or horizontal layout
Screenshots / Mockups

Please assign this issue to me @thekavikumar


lime.text.Font:renderGlyph returns garbled image

Maybe I'm not doing something right or maybe this is a bug. To reproduce, run lime create project font-test and then add this code to Main.hx:
import sys.io.File;

import lime.app.Application;
import lime.text.Font;
import lime.utils.Assets;
import lime.ui.KeyCode;
import lime.ui.KeyModifier;
import lime.graphics.ImageFileFormat;

class Main extends Application {

    public function new () {
        super ();
    }

    public override function onKeyDown( keyCode : KeyCode, modifier : KeyModifier ) : Void {

        switch( keyCode ) {

            case KeyCode.ESCAPE:
                window.close();

            case KeyCode.F:

            var font = Assets.getFont( 'assets/amiri-regular.ttf' );
            var point = 'b';
            var glyph = font.getGlyph( point );
            var img = font.renderGlyph( glyph, 24 );
            var bytes = img.encode( ImageFileFormat.PNG );
            // change path to whatever fits is best
            var outputPath = Sys.environment().get( 'HOME' ) + '/tmp/glyph_' + point + '.png';
            File.saveBytes( outputPath, bytes );

            default:
        }

    }
}

Run and press 'F' to get the glyph image saved to PNG.
I've tried a A b and B, and got these as a result:
a.png

A.png

b.png

B.png

This may or may not be related to #1257
Tried the code above on both 7.2.1 (master) and current develop branch, on OSX and Linux, same result (garbled images, not sure if it outputs the same images every time).

While working on some other unrelated issues (but having to do with using PNG images for textures) I connected few dots that bugged me in this issue.
After some spelunking and more testing, here's the thing:

glyph rendering happens on native side by call to FT_Render_Glyph. Whatever FT_Render_Glyph returned as raw bitmap data is copied verbatim to the output Bytes. FT_Bitmap.pitch is taken into account here so data being copied into Bytes instance has pitch (or stride) equal to FT_Bitmap.width. So far so good.
Font.renderGlyph creates new ImageBuffer and sets bitsPerPixel to 1 and this is the first issue, since:

it is a fixed value
the fixed value assumes FT_Render_Glyph always returns 1-bit-per-pixel bitmap

once Font.renderGlyph creates an ImageBuffer instance with bitsPerPixel == 1, ImageBuffer assumes that buffer data always contains pixels as 32-bit values and returns fixed stride based on this assumption

These two things: bits=per-pixel == 1 and stride == width * 4 result in Image.encode() producing wrong image of the glyph.
The glyph is ultimately rendered by a FreeType's FT_Renderer instance called in FT_Render_Glyph_Internal function. This function selects first matching renderer for the job. I didn't dig further to figure out what happens there and which renderers are registered and where. It turns out that what Font.renderGlyph returns is an 8-bit-per-pixel rendering of requested glyph in all my test cases on Linux, OSX and Windows.
Test Lime app that has workaround for this issue (based on assumption ;)  that Font.renderGlyph will always return 8-bpp image) can be found here.
Patches that address fixed values in Font.hx and ImageBuffer.hx are trivial and that is one reason I didn't create pull request. The other reason is that replacing
var buffer = new ImageBuffer(new UInt8Array(data), width, height, 1);

with
var buffer = new ImageBuffer(new UInt8Array(data), width, height, 8);

still assumes that FT_Render_Glyph_Internal will always return 8-bpp image, and that doesn't really sounds like a bug fix to me.

I believe that there was an issue (a long time ago) where we accidentally treated bitsPerPixel as if it were bytesPerPixel -- I think it was resolved everywhere but this function. Font.renderGlyph as well as Font.renderGlyphs were disabled for a long time due to underlying C++ changes, but Font.renderGlyphs as later restored -- and this issue seems to have carried over with it for renderGlyph
This should be only the alpha channel.
On the topic of 8-bit images -- I'd love to see improvements for better handling of 8- or 16-bit images in general, like this topic: https://github.com/openfl/lime/issues/872

Btw, this line in ImageBuffer also needs to be updated to something like
return width * bitsPerPixel / 8;
for this issue with renderGlyph() to be fixed. Or renderGlyph() could convert 8-bit alpha image to 32-bit image with pixels set to (0,0,0,a) or something. Otherwise the image returned by renderGlyph() will still be garbled.
width * 4 assumes that we always deal with 32-bit pixels, which for renderGlyph() is not the case.


Basic contact store v1

Module that can persist contact info. For v1 that can be locally in IndexedDB.

[x] Create(pub, [info]): contact "create contact for given pub key, optionally initialize info about contact"
[x] Update(pub, info): contact "update info for this contact"
[x] Get(pub): contact "get contact associated to given pub key"
[x] Delete(pub) "delete contact for given pub key"
[x] List(): pub[] "get all pub keys in storage"

Info is a map of key-value pairs. There might be a set of standard keys, e.g. "email", "mobile", ...
A contact basically is a pub key and associated info - while the info could be separated into the info provided and updated by the person the contact represents and the info the added by the local owner of the address book.

Added an ID field where ID is a hash of the pub, aka an address. Using that ID as index instead of pub. The current API is not the same, but has all the features. So I think it's good enough for an MVP


TypeError : 'undefined' is not an object (evaluating 'this._xhr.readyState')

Hi Jeff, I have discovered a bug in this module, I have used a small workaround to make it work, Please check it when have time in http://forum.wakanda.org/showthread.php?7914-Module-httpRequests-TypeError-undefined-is-not-an-object-(evaluating-this._xhr.readyState-)
Thanks
Igor.-

Thanks.  I'll fix ASAP.


Fixing passing --database-url as global cli arg

--database-url is passed as global cli argument, this means it may be
not part of the current ArgMatches. To solve this we need to look recursivly in all current subcommands for the database-url

Does setting the global config accomplish the same thing? If not I think we should fix this in clap.

Does setting the global config accomplish the same thing? If not I think we should fix this in clap.

The documentation of global states explicitly the current behavior, so this seems to be desired or at least not fixable without changing larger parts of clap.

NOTE: Global arguments, when matched, only exist in the command's matches that they were matched to. For example, if you defined a --flag global argument in the top most parent command, but the user supplied the arguments top cmd1 cmd2 --flag only cmd2's ArgMatches would return true if tested for ArgMatches::is_present("flag").

There is also this issue on the clap repo, but setting this flag does not solve the problem…

Can you add a few test cases?

Something like the last commit?

The last commit is the sort of thing I had in mind, yes. However, those tests pass without your code changes

Based on some cursory testing, it looks like we should only need the .setting(AppSettings::PropagateGlobalValuesDown). However, that setting causes diesel --database-url=... database drop to work, but not diesel database --database-url=... drop. The addition of the database_url_from_cli function doesn't seem to affect it.

Based on some cursory testing, it looks like we should only need the .setting(AppSettings::PropagateGlobalValuesDown). However, that setting causes diesel --database-url=... database drop to work, but not diesel database --database-url=... drop. The addition of the database_url_from_cli function doesn't seem to affect it.

Executing target/debug/diesel migration run --migration-dir some/migrations/dir  --database-url /tmp/test.db fails for me without the database_url_from_cli function.
Also this function may fix the issue with diesel --database-url=...

However, those tests pass without your code changes.

I've modified those tests to run without the DATABASE_URL environment variable. Now migration_run_runs_pending_migrations_custom_database_url_1 fails without the using database_url_from_cli

Can you add a note that we can remove that function once https://github.com/kbknapp/clap-rs/issues/978 is fixed?

You need to run rustfmt

Fixed by #1304


Missing isFullWidth prop in Table element

Table element is lacking of isFullWidth prop, so it can render is-fullwidth css rule from bulma.

Also, the isSelected modifier is missing for


SSL certficate in load balancer

My use case for this module is as follows.
The SSL certificate is stored on the load balance and not on the server running Apache. All request to the load balancer come in as https requests, and passed on to the Apache webserver as http requests. Is there a way to let the module aware that SSL is being handled by upfront by the load balancer?
Thanks

See: https://github.com/pingidentity/mod_auth_openidc/wiki#8-how-do-i-run-mod_auth_openidc-behind-a-reverse-proxy


[Ready for review - Testing progress, don't merge] Enable updateResourceAsync

CreateableTaskGroup is renamed to createUpdateTaskGroup as the group contains task that can  run update action on a resource

Renamed ResourceCreator to ResourceCreatorUpdator and it exposes new method updateResourceAsync

CreatableUpdatableImpl now contains default implementation of CreateAsync and UpdateAsync

CreatableImpl inherites from CreatableUpdatableImpl and adding a new base class AppliableImpl that inherits from CreatableUpdatableImpl
This will enable a resource which is only creatable to extends from CreatableImpl and anything that is applicable only to derive from ApplicableImpl.

Can one of the admins verify this patch?

Runtime changes detected. pull request created. CI running:

Runtime changes detected. pull request created. CI running:

Runtime changes detected. pull request created. CI running:

@jianghaolu addressed your comments, please take a look when you get chance.

merging as changes are approved.


Why is this happening can anyone suggest a reason

Two equally empty viewmodel files , one gets accepted as a datacontext the other does not?  I can see no difference  except the one that works I created before updateing visual studio today.The file properties seem the same for both. My apologies if this turns out to be a newbie error but I only recently tried Template 10.
Alan

Remamed the file that was accepted and it is now no longer accepted. By the way I am using vs community.

Community should not make a difference. In one screen shot you are using a custom ViewModelBase. Are you still doing that anywhere? If so, then I might assume it is in there.

Ok for some reason I know not why his problem has gone away


Add a release phase to Heroku Procfile to autorun migration on deploy.

https://devcenter.heroku.com/articles/release-phase#defining-a-release-command
https://stackoverflow.com/questions/36410107/running-manage-py-migrate-during-heroku-deployment

Just tried a deploy to Heroku and it seems to work as expected, the migrations are run as shown below.
Receive code from GitHub
Build feature/autorun-migrate-heroku-deploy
Release phase
Operations to perform:
Apply all migrations: activity, admin, apply_home, auth, categories, contenttypes, determinations, funds, home, images, navigation, news, people, postgres_search, projects, public_funds, review, sessions, social_django, standardpages, taggit, users, utils, wagtailadmin, wagtailcore, wagtaildocs, wagtailembeds, wagtailforms, wagtailimages, wagtailredirects, wagtailsearch, wagtailsearchpromotions, wagtailusers
Running migrations:
No migrations to apply.
Release finished
Deploy to Heroku
Your app was successfully deployed.


Delete unused images

We have a fair few unused images in the repo.

Last time we tried to delete unused files there were too many problems so we gave up.

😄 yeah ... I think that's what I was remembering. I believe that in one attempt very early on many years ago that I screwed up and deleted one or a few and had to put them back!

Yeah, I thought this would be a good thing to do but I quickly realised there's more to it, as you've said. I'd like to come back and revisit this, but it'll have to be another day.


Comment fixes; Various updates

I would have opened this on pschumm/Stata.tmbundle, but issues aren't enabled on that.
I don't use TextMate, but Github uses pschumm/Stata.tmbundle for its syntax highlighting on Markdown documents on the site.
I'm the author of the Stata syntax highlighting package for Atom, and Atom happens to use the same syntax highlighting as TextMate, so the rules are transferrable to this package (I would just have to convert cson to plist format).
There are some errors with this package, for example, I just fixed comments syntax highlighting in Atom, so that it's more accurate than the do file editor. See this document to see Atom, the do file editor, and Github Markdown's highlighting (i.e. this package) side by side. The Github syntax highlighting could be improved in this regard.
Would you accept some PRs in this regard? I think that Github's highlighting will update automatically if the master branch on pschumm/Stata.tmbundle is updated.

@pschumm

Would definitely welcome involvement of any kind, as the TextMate mode could certainly use some attention/improvement. And I'd be keen to have some consistency between what is available with TextMate and what is available with Atom (and VS Code), for cross-platform compatibility. Will take a look at the differences in comment highlighting you reference above.


please port paper to arxiv

i found out last night that arxiv does not support minted. sigh. so its back to lstlistings for the paper
so can u switch minted ==> lstlistings in the paper? the challenge will be keeping all the letters in circles appearing in the revised doc.

so are we submitted to arxiv now?


Usage of deprecated functions

Current Behavior
Currently deprecated functions are used.
Expected Behavior
Use new replacements.
Steps To Reproduce
List of used deprecated functions:

util.log
url.parse
slice
substr

List of replaced deprecated functions:

util.isArray
sass.renderSync

Environment

Node-RED version: 4-dev
Node.js version: 20

util.log usaged addressed by https://github.com/node-red/node-red/pull/4875


How do you pronounce "zod"?

I've encountered a slight issue regarding the pronunciation of "zod". While this may seem a minor point, I believe understanding the correct pronunciation will contribute to accurate communication when discussing the software in my community, which largely consists of non-native English speakers.
There's currently no phonetic guide or pronunciation key available in the software's documentation. Therefore, I kindly request some guidance on the matter. How should "Zod" be pronounced? If possible, could you provide this information in the International Phonetic Alphabet (IPA) or some other universally recognized format?

I believe it's pronounced almost the same as "God" and "rod". I've heard Colin speak of it before on YouTube and this is how it sounds. Not very familiar with IPA sorry.


Terminating app due to uncaught exception 'NSRangeException'

When i open the map view the app crash.
i try to check where is the crash, the map view crash before viewDidLoad.
The trace of the error is this:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '-[__NSCFArray objectAtIndex:]: index (0) beyond bounds (0)'
i check in crashlytics to view where is the error and the report is in this file:
TSClusterMapView.m line 36
-[TSClusterMapView initWithCoder:]
There is the code where i put the annotations:
 self.annotations = [PoiAnnotation]()
          for i in 0 ..< self.pois.count {
               if let poi = self.pois.objectAtIndex(i) as? Pois {
                    let marker = Marker.init(
                         title: poi.title, subtitle: String(poi.poi_type_id), latitude: (poi.lat as NSString).doubleValue, longitude: (poi.lng as NSString).doubleValue, poi:poi
                    )
                    annotations.append(marker.annotation)
               }
          }
          if let annotationFilter = self.defaults.objectForKey("annotationFilter") as? [Int] {
               print(annotationFilter)
               self.filterCategoriesbyExistentFilter(annotationFilter)
          }
          self.mapView.addClusteredAnnotations(annotations)

This is only occurred in one device Iphone 5s.
I'm using version 2.10 of the pod.

Do you have a full stack trace?
Does this crash happen when you add annotations or during the initialization? If it is during initialization you might have an issue outside the scope of this framework.


Use makepkg config when updating pkgver

Sometimes packages check the compiler and its options. It can fail
during the pkgver update if the default makepkg.conf (/etc/makepkg.conf)
has been modified.
This commit forces makepkg to use the given makepkg_conf instead.
Example: package checking that the compiler is gcc and default makepkg
uses clang.

Part/duplicate of #720
Please check if that one works as intended.

Indeed, I didn't see this one.
Thanks!


tcamsrc num-buffers=1 does not produce a buffer

Hello,
I am trying to make a snapshot from DFK 38UX267 to process it further. It apperas, tcamsrc num-buffers=1 does not produce data.
There is an example pipeline:
gst-launch-1.0 tcamsrc serial=SERIAL num-buffers=1 ! videoconvert ! jpegenc ! filesink location=image.jpg
image.jpg is always empty!
Thanks,
Maxim

Hello Maxim
The pipeline does not work, because the video formats can not be negotiated. Please use a pipeline like
gst-launch-1.0 tcamsrc num-buffers=30 ! video/x-bayer,format=rggb,width=640,height=480,framerate=30/1 ! bayer2rgb ! videoconvert ! ximagesink
Stefan

I am not sure about the "rggb". please use tcam-ctrl -c for a list of valid formats

I confirm that there is a bug in tcamsrc.
gst-launch-1.0 tcamsrc serial=SERIAL num-buffers=1 ! videoconvert ! jpegenc ! filesink location=image.jpg
Creates an empty file
but
gst-launch-1.0 v4l2src device=/dev/video0 num-buffers=1 ! videoconvert ! jpegenc ! filesink location=image.jpg
Works as expected.

There is no bug. The format provided from tcamsrc can not be read by videoconvert, as I already wrote. I also posted a working pipeline. Did you use that?
Stefan

Stefan,
Your pipeline sets num-buffers to 30, but I want to capture one buffer
Maxim

Stefan,
gst-launch-1.0 tcamsrc num-buffers=30 ! video/x-bayer,format=rggb,width=640,height=480,framerate=30/1 ! bayer2rgb ! videoconvert ! ximagesink
works fine, but
gst-launch-1.0 tcamsrc num-buffers=1 ! video/x-bayer,format=rggb,width=640,height=480,framerate=30/1 ! bayer2rgb ! videoconvert ! jpegenc ! filesink location=image.jpg
does not work at all

Set the buffers to 2 and see, what happens.
Use
multifilesink location=image%d.jpg

Hello
we found, that the first provided image is damaged, therefore, please set num-buffers to 3. For currently unknown reason, this provides 2 images only and the second should be ok.


Resolved IDENTITY-3102

Above commented issues are resolved in https://github.com/wso2/carbon-identity/pull/950


TOOL-Enable-RemoteDesktop

Win32_TerminalServiceSetting doesn't work with standart parameter, I need to use

Authentication

with value

PacketPrivacy

$Splatting = @{
	Class = "Win32_TerminalServiceSetting"
	NameSpace = "root\cimv2\terminalservices"
	ComputerName = $Computer
	Authentication = 'PacketPrivacy'
	ErrorAction = 'Stop'
	ErrorVariable = 'ErrorProcessGetWmi'
}

Thanks for your comment  @TechASP
Indeed I see that in the following document (in the remarks) Win32_TerminalServiceSetting class requires to include it.
I just updated the function


Sort services by port

Useful when you have lots of services with the same port but different products.
Closes #93

Looks like it breaks the search, need further testing

@ilyaglow Did this end up working?

@tomsteele yep, finally. I also added sorting by product at first place as you can see. Didn't measure the performance impact though, but I hardly feel the difference.


Not working for Genshin

The script seems to be no longer working for Genshin (Still works for Honkai and Star Rail).

I guess so. In this case the bot should return an error message to indicate the failure of signing in. However, it send an "OK" message to the discord server. This should be fixed I believe.
Mihoyo added intensive anti-bot verification on the CN server which made auto sign-in nearly impossible. Hopefully, this won't happen to the international server.

Might be a bit hard to fix the "OK" message, as this is what HoYoLAB is returning from the API request. HoYoLAB is telling us that the check-in worked when it didn't.

Can we maybe add user-agent, and x-http-referrer reader to the scripts and. The end-server are probably checking for user agents and referrer like mentioned here: https://github.com/canaria3406/hoyolab-auto-sign/issues/11#issuecomment-1588510392
I will try to add the code to the header below to my scripts, and will report the result here tomorrow:
const header = {
    Cookie: token,
    'x-rpc-app_version': '2.34.1',
    'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36',
    'x-rpc-client_type': '4',
    'Referer': 'https://webstatic.mihoyo.com/',
    'Origin': 'https://webstatic.mihoyo.com'
  };

this change to header worked for me

this change to header worked for me

My account still requires captcha even after putting those header in the script.
The verification process probably done randomly or after certain days passed after checking-in without a user-agent/referrer, just a speculation though, cannot confirm anything...
Probably we want to push in the header changes to main anyway, just to make the script more like a human action to hoyoverse server logs.

yeah i agree, do u wanna do the pull request? i dont wanna take credit for ur work lmao

I've opened one at https://github.com/canaria3406/hoyolab-auto-sign/pull/17 please have a look

Today, the script successfully checked in my genshin account without captcha verification.
Will report here again if the captcha came back.

A commit in a similar python project seems to include some challenge parameters in the header:
https://github.com/thesadru/genshin.py/commit/2d6f7d19485edb33c1529d50babd89dde64353c8
Though I'm not sure where you would get the actual solved challenge parameter from.

seems to be working once again by doing nothing. although the captcha in the browser still showed up when you claim check in manually

It´s broken for me again :(
(Broke today)
(Telegramm)
Check-in completed for (me)
Genshin: Auto check-in failed due to CAPTCHA blocking. Please stop this script immediately and perform manual check-in for at least one week before attempting to use this script again.
After I manually collected it, it´s giving me the same message.

Mine also started breaking today.
I can see some repo (like one mentioned above) might able to successfully bypass the geetest captcha, but i would not want to do it. Pretty sure it's borderline against their ToS.
Will report here again if i find another solution.

Pretty sure it's borderline against their ToS.

The entire script already is.

I needed to change const bannedCheck = hoyolabResponse.data?.gt_result?.is_risk; to const bannedCheck = hoyolabResponse.data.data?.gt_result?.is_risk; (add one more data) because the first one returns undefined, there are two data nodes and we need to get the deepest one.
...
    [Symbol(kUniqueHeaders)]: null
  },
  data: {
    retcode: 0,
    message: 'OK',
    data: { code: 'ok', first_bind: false, gt_result: [Object] }
  }


soc: arm: nxp_imx: rt: Configure settings for TRNG IP

RT platforms that support TRNG IP (rt10xx and rt6xx) need to set
RNG and CSRNG to Xoroshiro and CTR_DRBG respectively instead of
using TRNG as random source.
Fixes: #37307
Signed-off-by: David Leach<EMAIL_ADDRESS>

Affects/is affected by #37187, which deprecates XOROSHIRO

@JordanYates, I'm not sure I can do anything about the conflict at the moment. I apologize for not being aware of the update pending for Xoroshiro to Xoshiro. One of us will have to modify/rebase depending on which one gets merged into the repo first.

@JordanYates, I'm not sure I can do anything about the conflict at the moment. I apologize for not being aware of the update pending for Xoroshiro to Xoshiro. One of us will have to modify/rebase depending on which one gets merged into the repo first.

That's fine, it wasn't a complaint, just a notification.

Understood ... now it is a race ;-)


Support all configuration options for initial position when processing events using EventProcessorClient

To resolve #26434.

still need to improve the configuration properties hint.

still need to improve the configuration properties hint.

How about convert it to draft?


chore: Add test files for Course Repository

Description
Here is the section for descriptions
Suggestions

[ ] bullet point
[ ] fdsf

@binchoi Hi check this code


Project Development

Benefit
Preparation and planning for revenue-generating projects.
Acceptance Criteria
Scope and estimates for as many projects as possible, and plans and agreements in place for at least two new projects.
Continue

[ ] GOEO UBC - Broadband residential #508
[x] DEQ/DWQ - Beneficial Uses and Surface Water Quality - they completed this on their own
[ ] DEQ/DTS - Environment Incidents ("Spills") SF map widget Or DTS SalesForce team - Enterprise map integration solution #501
[ ] DWR - BioBase: UGRC consultation for replacement of BioBase by the Wildlife Habitat Assessment Tool
[ ] DWR - Roadkill (enhancements and tech debt)
[x] UAN - Camp Williams map ref #423
[ ] WFRC - bikeways ref #371

New

[x] DAQ Survey123:TEMPO interaction (Teri Houskeeper) - we could be consultants to their internal project
[ ] DHHS American Indian/Alaska Native Health and Family Services (Alex Merrill) - Tribal Facilities Map
[ ] Legislative Revenue and Taxation Committee (Chris Stitt) - Parcel tax rate map
[ ] DFCM - leased property mapping (Wayne Christensen & Lee Fairbourn)
[ ] DWS - zoning data (Alyssa Gamble)
[ ] DHHS SUD Prevention (David Watkins) - mapping alcohol outlet density and other alcohol-related metrics like Colorado #464

Notes
No response
Risks

Client communication
Quantity of projects

Issue Reference
refs #

This will be helpful for chris at some point.


Add feature flag to disable default retry policy

There is default retry policy hard coded which will retry twice on connection issue or 503 introduced by https://github.com/istio/istio/pull/10566:
https://github.com/istio/istio/blob/master/pilot/pkg/networking/core/route/retry/retry.go#L34-L48
func DefaultPolicy() *route.RetryPolicy {
	policy := route.RetryPolicy{
		NumRetries:           &wrappers.UInt32Value{Value: 2},
		RetryOn:              "connect-failure,refused-stream,unavailable,cancelled,retriable-status-codes",
		RetriableStatusCodes: []uint32{http.StatusServiceUnavailable},
		RetryHostPredicate: []*route.RetryPolicy_RetryHostPredicate{
			// to configure retries to prefer hosts that haven’t been attempted already,
			// the builtin `envoy.retry_host_predicates.previous_hosts` predicate can be used.
			xdsfilters.RetryPreviousHosts,
		},
		// TODO: allow this to be configured via API.
		HostSelectionRetryMaxAttempts: 5,
	}
	return &policy
}

In our production environment we have thousands of VirtualServices created without retry policy which means it's using the default.
For most cases we don't see issue but we are seesing problems with idempotent POST request retry and some POST requests are actually payout, which eventually caused double payout issue.
Here is one case we got for the double pay due to retry:
IngressGateway access log
2024-04-14 08:31:51.000
bytes_received=85 bytes_sent=0 configId= duration=0 filename=accesslog method=POST path=/create_repayments protocol=HTTP/1.1 response_code=0 response_code_details=downstream_remote_disconnect response_flags=DC start_time=2024-04-14T00:31:51.244Z

Sidecar access log
2024-04-14 08:31:52.000
bytes_received=85 bytes_sent=0 configId= duration=0 filename=accesslog method=POST path=/create_repayments protocol=HTTP/1.1 response_code=0 response_code_details=downstream_remote_disconnect response_flags=DC route_name=default start_time=2024-04-14T00:31:51.244Z

So we want to disable the default retry and instead one by one by setting the VirtualService retry num to 0, it could be better to have a feature flag globally.
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

https://github.com/istio/api/blob/master/mesh/v1alpha1/config.proto#L1318 - you can use Mesh Config to configure default retry policy

Please see my comments here: https://github.com/istio/istio/issues/51704#issuecomment-2188555136; i don't believe Istios default retry policy should include retryable-status-codes.

i don't believe Istios default retry policy should include retryable-status-codes.

I think it can have retryable-status-codes for services to use x-envoy-retriable-statuscodes and control status codes themselves. Defaulting to 503 is not correct IMO

i don't believe Istios default retry policy should include retryable-status-codes.

I think it can have retryable-status-codes for services to use x-envoy-retriable-statuscodes and control status codes themselves. Defaulting to 503 is not correct IMO

👍 also works.

Just to call out i went down a rabbithole today (https://github.com/istio/istio/issues/51762) trying to retry 503's that were actually caused by reset.
They were again resets before headers, so an istio level default policy of retry-before-request would have saved me from that!
Also I learned that the 503 you see in the case of a UC won't be retried by Istios default policy anyway because it isn't a "real" 503 (see the linked issue).  Therefore the only 503 being retried by istio right now is one returned from an upstream (easily happens in a microservice architecture as you'll get 503UC (destination) -> 503 (middle service) -> app

defaultHttpRetryPolicy is availabie in https://istio.io/latest/docs/reference/config/istio.mesh.v1alpha1/. Also a valid point wrt to whether our default-defaults should change though

@howardjohn I think defaults should probably change, I don't think it's good for Istio to have "unsafe" defaults enabled by default.

I think it would be better to remove the retriable-status-codes 503 since for most cases we don't know if the 503 is retriable, especially for the post request.

I agree. I am working on a PR for that


onSuccess doesn't return any data

onSuccess seems not working properly in version 1.0.30. it doesn't return token at all. and tested the onError and no error was raised.
however, I tried to downgrade to 1.0.29 and 1.0.28 and when I did, I've got an error that says:
One of the sources for assign has an enumerable key on the prototype chain. This is an edge case that we do not support. This error is a performance optimization and not spec compliant.
react: 16.0.0-alpha.12,
react-native": ^0.46.4,
expo:  20.0.1

Could you please test again with the last one?


[WIP] Enable Temporary Alloc Bufferization pass

This doesn't enable vectorization on elementwise and just with the temporary buffer -> amdaie.buffer.
I noticed my last local state was enabling vectorization on elementwise because I was trying to test Relu too once "Matmul + truncf" worked hence forgot to disable and went on to add changes to lit tests.
Adding this as WIP because I'll immediately try to add fixes for enabling vectorization on elementwise/Relu - so can just reuse the lit test changes that I added previously.

Closing this as it's already being taken care of by https://github.com/nod-ai/iree-amd-aie/pull/822


Can you elaborate on how to run the app with this in bubble notification?

Can you elaborate on how to run the app with this in bubble notification?

Just follow the example and try to implement it with notification button or background calls


adding a new variable to grade in lab 1

We are checking a new variable to know the number of trials they are executing. This number will have to be always 2 so we check it in the grader

closing as this variable check is not needed


Fixed ItemList indexing

Fixing #5772
Also added functionality for unselecting items in itemlist while clicking in empty space.

Nice first PR :)
Several small issues in the form that would be nice to fix by amending the commit (git commit --amend):

Use tabs for indentation and not spaces, like done in the rest of the code
Don't let your IDE strip trailing whitespace on lines you did not edit, this adds noise to the diff
Don't keep commented out code, with git it's easy to find out when code was added/removed, so we don't need to keep dead code (even though the current source is ridden with it... it's a long running effort).

Thanks for advices. :)

Hm, your git client did something weird to the history, there are now 3 commits, the two first one being conflicting and the third one is an empty merge commit. I guess I'll cherry-pick a50377a if the PR is considered good to merge :)

I cherry-picked the commit manually and pushed it in your name ;)
I also removed the unused closest_dist variable as seen in #5857.


Specifying Direct Upload Project's Production Branch

Is there a way to specify which branch should be the "production" branch? I do not see a setting if the Pages project is created as a Direct Upload project.
I created a couple of Pages projects when direct upload was made available. In order to get the Pages project to publish to "production", I had to use a branch named production (which I prefer). It worked even when using this GitHub action repository (using "production" would publish to the production environment and any other branch would create a preview environment)
I created a Pages project today. Now, it seems that I have to use a branch named "main" to get it to publish to production.

Ideally there should be a separate production argument that allows users to pick which builds are production builds.
This is more flexible (e.g. if multiple release branches exist for different versions,...). However, this doesn't seem to be supported by the CloudFlare API


Rich Presence doesn't work anymore

Hey there, the Rich Presence API that you're using is deprecated and no longer works.
I forked your project and fixed the issue by using Lachee's API. Maybe we should consider merging sometime?
Thanks

@CodeMyst don't know if you'll see this so I'm mentioning you

Thanks for mentioning me, otherwise I wouldn't have seen it.  My version had a lot of issues.
I would be very open to merging and would like to contribute some code if needed as well. Tomorrow I'll check out your project and we can go from there. Do you have any ideas on how we should merge the projects into one?

We could keep Avalonia however I don't know how it works or how to update it properly. I'm currently planning to change the Deezer API since the old one seems to throw an SSL error after you use it for 20-30 minutes.

Huh I didn't notice that with the API before. Unfortunately that's the only one you can use.
Also I'll look into some other UI options and check Avalonia again, in the current repo Avalonia doesn't work on some machines for some reason.

Unfortunately that's the only one you can use.

What about E.Deezer?

From the looks of it, it's just a wrapper around the official Deezer API.

Might fix the issue, you never know lol

I'll try reproducing the issue you had first.

I can fix the code and you could add a proper UI and we could merge those in a future Deezcord 2.0 update. What do you think?

fine by me!
-------- Original message --------
From: Sergiu Bucur<EMAIL_ADDRESS>Date: 13/04/2020 22:58 (GMT+01:00)
To: CodeMyst/deezcord<EMAIL_ADDRESS>Cc: CodeMyst<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [CodeMyst/deezcord] Rich Presence doesn't work anymore (#6)
I can fix the code and you could add a proper UI and we could merge those in a future Deezcord 2.0 update. What do you think?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/CodeMyst/deezcord/issues/6#issuecomment-613094829, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB4Y7JGSCEMYQ2XXEFJDCHDRMN4H5ANCNFSM4METHMEA.

@b1sergiu I made a basic avalonia app in the v2 branch, could you submit a PR with your code into it and i'll hook it up?

I'm not yet ready, I'll try to finish the project tomorrow. I had to contact the E.Deezer developer and it took a long time

Hmm okay, I'm still pretty certain we don't need an api wrapper like E.Deezer but I'll do some tests tomorrow.

Hey, I don't think I'm going to use E.Deezer anymore. I find it hard to use and it's barely documented at all. Should I just leave the old API as is?

Sure

Hey, I'm back. Sorry for the wait. I will update the code and issue a pull request.

Done. Here it is

will check the PR tomorrow if i can!
-------- Original message --------
From: Sergiu Bucur<EMAIL_ADDRESS>Date: 13/05/2020 22:39 (GMT+01:00)
To: CodeMyst/deezcord<EMAIL_ADDRESS>Cc: CodeMyst<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [CodeMyst/deezcord] Rich Presence doesn't work anymore (#6)
Done. Here it ishttps://github.com/CodeMyst/deezcord/pull/7
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/CodeMyst/deezcord/issues/6#issuecomment-628233793, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB4Y7JEK7DMSD3FISMZQS7TRRMARHANCNFSM4METHMEA.

also, from a quick glance, it seems you leaked your api keys... :/

...fuck my life


Problems with loading .env file

Problems with loading .env file
.env file does only load when loadenv() is used with a specified path.
Only loadenv('.env') does work.

The issue was resolved in the latest release of version 0.1.5. From now on, default values are used, if no environment variables are specified. However, it is still possible to load environment variables before starting the middleware. To do so, use values similar to that in the .env.example-file.

The issue was resolved in the latest release of version 0.1.5. From now on, default values are used, if no environment variables are specified. However, it is still possible to load environment variables before starting the middleware. To do so, use values similar to that in the .env.example-file.