nvfuserex has problems taking getitem.

          getitem_nvfuser tests failed for a similar reason to https://github.com/Lightning-AI/lightning-thunder/blob/54bb6146ff757905925f8d9ea2197870c4971011/thunder/tests/opinfos.py#L3113-L3115. I can again create a wrapper so `slice` objects don't get passed to FusionDefinitionWrapper. But I'd love to hear thoughts from @jjsjann123 and @kevinstephano who may have a better fix.

Originally posted by @wujingyue in https://github.com/Lightning-AI/lightning-thunder/issues/191#issuecomment-2119408081
cc @tfogal

To reproduce this, check out branch wjy/bookend and run pytest thunder/tests/test_ops.py -k test_core_vs_torch_consistency_getitem_nvfuser_cuda_float32 -s.
The branch disables bookend (a workaround that we want to get rid of) so slice prims are given to nvfuser, adds some debug prints and highlights the failing test.

E       ValueError: Trying to extract a dtype from object slice(1, 3, 1) with unknown type <class 'slice'>!

thunder/core/dtypes.py:300: ValueError

This is triggered by to_descriptors which tries to compute a cache key for the function signature and fails on slice.
However, even with that check removed,
diff --git a/thunder/executors/nvfuserex_impl.py b/thunder/executors/nvfuserex_impl.py
index bc0708ef..e30bf428 100644
--- a/thunder/executors/nvfuserex_impl.py
+++ b/thunder/executors/nvfuserex_impl.py
@@ -368,13 +368,13 @@ def to_descriptors(args) -> tuple:
         if isinstance(arg, Number):
             return type(arg)
         elif isinstance(arg, tuple):
-            if len(arg) != 0:
-                numbertype, _ = check_same_dtype(*arg)
-                check(
-                    numbertype == int,
-                    lambda: f"tuple in nvfuser only supports int, but found {numbertype}",
-                    exception_type=AssertionError,
-                )
+            # if len(arg) != 0:
+            #     numbertype, _ = check_same_dtype(*arg)
+            #     check(
+            #         numbertype == int,
+            #         lambda: f"tuple in nvfuser only supports int, but found {numbertype}",
+            #         exception_type=AssertionError,
+            #     )
             return type(arg)
         elif isinstance(arg, torch.Tensor):
             return (*get_tensor_descriptor(arg), arg.dtype)

nvFuser still fails with the following RuntimeError:
RuntimeError: Tracer cannot infer type of slice(1, 3, 1)
:Only tensors and (possibly nested) tuples of tensors, lists, or dictsare supported as inputs or outputs of traced functions, but instead got value of type slice.

FWIW, @jjsjann123 and I briefly looked at the Thunder trace before and after nvFusion.
*** before nvFusion ***
# Constructed by Dead Code Elimination (took 0 milliseconds)
import thunder
import thunder.torch as ltorch
import torch
from thunder.executors.torchex import no_autocast

@torch.no_grad()
@no_autocast
def computation(a, b):
  # a: "cuda:0 f32[5, 5]"
  # b: "tuple"
  t0 = ltorch.getitem(a, b)  # t0: "cuda:0 f32[2, 2]"
    # t0 = prims.slice_prim(a, [1, 2], [3, 4], [1, 1])  # t0: "cuda:0 f32[2, 2]"
  return t0

*** after nvFusion ***
# Constructed by Fusion (took 1 milliseconds)
import torch
from thunder.executors.torchex import no_autocast

@torch.no_grad()
@no_autocast
def computation(a, b):
  # a: "cuda:0 f32[5, 5]"
  # b: "tuple"
  [t0] = nvFusion0(a, b)
    # t0 = prims.slice_prim(a, [1, 2], [3, 4], [1, 1])  # t0: "cuda:0 f32[2, 2]"
  return t0

@jjsjann123 felt like there's something wrong with the trace to begin with. b isn't used any more and has been baked in as constant already.

@jjsjann123 can take a first stab at debugging and then pass it off to someone.
triage team: 1) thoughts? 2) who do we consider the maintainer of the nvfuser executor? Ivan? 3) maybe same as (2), but who can we assign this to to drive a solution?

This will be fixed by #544 . Thank a lot to @kiya00 for helping out.


apt-get update fails

Description
apt-get update fails with Certificate verification failed.
Err:48 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release
  Certificate verification failed: The certificate is NOT trusted. The received OCSP status response is invalid.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]

Area for Triage:

Bug:
Run sudo apt-get update
  sudo apt-get update
  sudo apt-get -y install libsodium23 libsodium-dev
  sudo apt-get -y install libsystemd0 libsystemd-dev
  sudo apt-get -y remove --purge software-properties-common
  sudo apt-get -y autoremove
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    CABAL_VERSION: <IP_ADDRESS>
    CABAL_BUILDDIR: dist-newstyle
    CACHE_VERSION: 9w76Z3Q
Hit:1 http://azure.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://azure.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:3 http://azure.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]
Get:5 http://dl.google.com/linux/chrome/deb stable InRelease [1811 B]
Hit:6 https://packages.microsoft.com/repos/azure-cli focal InRelease
Get:7 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease [10.5 kB]
Get:8 https://cli-assets.heroku.com/apt ./  Packages [620 B]
Get:44 https://dl.bintray.com/sbt/debian  Release [815 B]
Get:45 https://packages.cloud.google.com/apt cloud-sdk/main amd64 Packages [163 kB]
Get:46 https://download.mono-project.com/repo/ubuntu stable-focal/main amd64 Packages [46.8 kB]
Get:47 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4/multiverse amd64 Packages [8916 B]
Err:48 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release
  Certificate verification failed: The certificate is NOT trusted. The received OCSP status response is invalid.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
Get:49 http://ppa.launchpad.net/git-core/ppa/ubuntu focal/main amd64 Packages [3056 B]
Get:50 https://apt.postgresql.org/pub/repos/apt focal-pgdg/main amd64 Packages [191 kB]
Reading package lists...
E: The repository 'https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release' no longer has a Release file.
Error: Process completed with exit code 100.

See https://github.com/input-output-hk/ouroboros-network/runs/2102194655?check_suite_focus=true
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Image version
Environment: ubuntu-20.04
Version: 20210302.0
Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20210302.0/images/linux/Ubuntu2004-README.md
Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F
Expected behavior
This should not fail.
Actual behavior
apt-get update fails with Certificate verification failed.
Repro steps
For repository and create PR.

Hey, @newhoggy !
Seems that the problem was temporary and does not persist now. Could you please check it one more time?

Also seeing this on all of our actions

This hit me too. https://github.com/scottgigante/SingleCellOpenProblems/runs/2113835105?check_suite_focus=true
Fixed it by moving to ubuntu-18.04.

Happened on both ubuntu-18.04 and ubuntu-20.04 earlier today, but seems to be fixed now.
on:
  workflow_dispatch:

jobs:
  test:
    runs-on: ubuntu-18.04
    steps:
    - run: sudo apt update

Seems that the problem is somehow connected with Opensuse repositories, because my test builds on Ubuntu 20  are successful, but there is definitely a percent of errors and all of them are: https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  Release' no longer has a Release file.
Opensuse statuspage is green so I guess that the problem should be rare or temporary.

Just to share very quickly, here's a workaround if you just need to get workflows running again:
sudo rm /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list
sudo apt-get update -y

(I posted with more context in #2938, but that was closed as a duplicate of this.)

Yeah, it's happening for me again.  https://github.com/input-output-hk/cardano-node/runs/2113990824?check_suite_focus=true

Broken now in 18.04: https://github.com/singlecellopenproblems/SingleCellOpenProblems/runs/2123070567?check_suite_focus=true

I think GitHub should really strongly consider removing or commenting out some of the apt sources that they're adding to the images.
Right now, an apt update will hit these (if I'm grepping right):
azure.archive.ubuntu.com
dl.google.com
ppa.launchpad.net
security.ubuntu.com
apt.postgresql.org
cli-assets.heroku.com
dl.bintray.com
dl.yarnpkg.com
download.mono-project.com
download.opensuse.org
packagecloud.io
packages.cloud.google.com
packages.microsoft.com
repo.mongodb.org
storage.googleapis.com

If someone is running apt update, it's probably because they want to install something which isn't already installed. If it's an Ubuntu package it should be supported, but for anything else users can add the repos themselves. (I don't even know if the VMs have universe packages enabled, but I wouldn't even expect that as a user. Only enabling the main repo seems pretty reasonable.)
Maybe I'm in the minority, but I would be 100% willing to put up with fixing any of my org's builds to add needed repos if they're removed, in exchange for less flaky apt update.
The whole set could be cut down to something like
azure.archive.ubuntu.com
security.ubuntu.com
ppa.launchpad.net

That's that many fewer ways for an update to fail.
Plus, since almost everyone running workflows doesn't want to update the version of mongo, or podman, or whatever else is installed, this is a significant amount of network traffic which can be removed.
Either that or mirror more of these packages to a repo owned and operated by GitHub / Microsoft, so they can control things.

@sirosen , In general, I agree since it is not the first time when such big number of apt repos bring issues. But we need to investigate it carefully before. I have created the separate issue to track this investigation: https://github.com/actions/virtual-environments/issues/2951

@sirosen exactly!
MS should not add anything to what Ubuntu ships with. All of these extra PPAs should be removed. Alternative: provide a ubuntu-20.04-vanilla. I'd then switch to that.

mirror more of these packages to a repo owned and operated by GitHub / Microsoft, so they can control thing

mirroring wouldn't cut it for me: it is not only about trusting operationally the upstream PPA ops, but that plus trusting the upstream developers feeding into those PPAs.
eg "dl.bintray.com"  gives me shivers .. the idea that the build box we use in CIs at any time could be fed crap/attacks

Hi, @newhoggy !
I'm still sure that this problem is highly related to Opensuse, repository list on Ubuntu images will be discussed/changed within the Investigate reducing the count of apt sources on Hosted Ubuntu images issue, so I'll close this one, but feel free to reopen it if you have any concerns.
Thank you!.

@LeonidLapshin no, I think this is only related to MS specific infrastructure, and I think MS should not try to blame SuSE for screwing up.
In fact, my suspicion is that MS is running some caching and/or TLS intercepting middleboxes. The latter would be even more worrying.
The reason is that this happened twice in the last weeks, for different PPAs, at least:

dl.bintray.com
download.opensuse.org

I think it is unlikely the those 2 different and independent upstream PPAs would screw up TLS certificate updates within just two weeks.
All of this makes me nervous enough to think about moving all our runners to self-hosted.

Hey, @oberstet !
We've taken a closer look to these issues and it seems that cases are different:

dl.bintray.com returns 502 error code (server-side) in this case the connection was succeeded, but unfortunately we got 502 error
download.opensuse.org can not establish https connection due to OSCP error

download.opensuse.org uses a wildcard cert issued by Letsencrypt and the OSCP verification URL is http://r3.i.lencr.org/

PS C:\Users\Leonid> openssl s_client -connect download.opensuse.org:443 -servername download.opensuse.org -status
CONNECTED(000001A4)
depth=1 C = US, O = Let's Encrypt, CN = R3
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = opensuse.org
verify return:1
OCSP response:
======================================
OCSP Response Data:
    OCSP Response Status: successful (0x0)
    Response Type: Basic OCSP Response
    Version: 1 (0x0)
    Responder Id: C = US, O = Let's Encrypt, CN = R3

Somehow this web-server returned invalid response (I guess that all software sometimes throw errors) and the connection was not succeded. That can be caused by almost everything in the middle, as you can see that the problem does not reproduces every time so it's really hard to say something definite.
Just an assumption:
If you look at Letsencrypt status page you will see that there was

Degraded Performance...

...some maintenance on our backend infrastructure...

on March, 7 and 17  respectively, related to

acme-v01.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production), ocsp.root-x1.letsencrypt.org, {e1,e2,r3,r4}.o.lencr.org & ocsp.int-x{3..4}.letsencrypt.org".

I guess that Letsencrypt infra had some troubles with this scope of web services and this can be the root cause of apt-get update failure, hope these details are efficient enough.

Thanks for checking and having a close look!
Obviously, I don't know what really happened. As a matter of fact, I just ran the command you posted, and it works just fine (now). pls see below.

That can be caused by almost everything in the middle

Like Windows? ;) seriously, I hope the GitHub infrastructure still runs on Linux. anyways, I don't "believe" LE is to blame: I did check the failing HTTPS link in Chromium/Ubuntu at the time when it was broken in the CI: no problems.
Sure, certificate stapling and online revocation checking .. is complex. All the x509 stuff is actually deeply broken by design .. I have some strong opinions here .. sorry;)
But as said: I do not know what actually happened .. maybe LE was the origin of the problem, maybe, by co-incidence both SuSE and bintray.com. I don't know.
Finally: all of that actually doesn't matter, because the real solution IMO is to remove all PPAs. Just what Ubuntu ships. Done.


Fix e2e::ledger_tests::invalid_transactions in eth-bridge-integration branch

Fixes #1207
NB: while this PR is draft, this isn't definitely fixed!

pls update wasm

Similar fix has been integrated into https://github.com/anoma/anoma/pull/1196 so this PR may be closed


Database Refreshing Out of Date

I have a Docker image built using this for easy updating of a pack we have on Curse and run a server of. I am running into issues where an update is pushed and approved on Curse (in this case 6 hours ago), but the mcdex database doesn't appear to refresh that frequently (10 hours in the past, at time of writing).
Is there documentation of how the cache file is built so I may run that locally and be able to pull updates in near real-time from Curse?

Hi @matt-claycomb -
The crawler is not publicly available as I do not want people inadvertently creating significant load on the CF servers by trying to do real-time polling. This is in part because the CF servers do not update in anything close to real time. From what I've seen things can show up on their site immediately, but from an API perspective it can be several hours before it's visible (weird, I know). The other reason I do not release the crawler is that it's using an undocumented API which has/does change on a regular basis and I don't want to deal with all the support issues therein.
The best possible outcome here would be to get CF to open a real API endpoint that could be polled/monitored in real time, but I doubt they'll do that.
I'm sorry I can't help you beyond this. :/

Of note, the crawler does run a few times per day, but there was another API break that caused it to miss files over the past few days. I've corrected this, so it should be more timely moving forward.

I understand - I wasn't even sure if it was an API or if you actually crawled and scraped data from the human-readable pages.
I just had my concerns as I had seen the db multiple days out of date in the past, and wanted to make sure it wasn't something like a 1 week interval.


Investigate using the common build template for Cosmos

Cosmos sdk pipeline doesn't use the common build template. Need to investigate if we need to add some more extension points that is better then duplicating the build template. This is true for javascript, python and java.

In particular we should look to remove these file:
https://github.com/Azure/azure-sdk-for-js/blob/master/eng/pipelines/templates/stages/cosmos-sdk-client.yml
https://github.com/Azure/azure-sdk-for-java/blob/master/eng/pipelines/templates/stages/cosmos-sdk-client.yml
https://github.com/Azure/azure-sdk-for-python/blob/master/eng/pipelines/templates/stages/cosmos-sdk-client.yml
Instead use the standard client yml templates. If needed we can add more extension points to enable any special cosmos scenarios but we need to remove the duplicated root templates. In the past release cycle there were at least 2 cases (https://github.com/Azure/azure-sdk-for-js/pull/10546/ and https://github.com/Azure/azure-sdk-for-js/pull/10550) were we missed updating these duplicated templates which caused cosmos builds to fail.

@sima-zhu, you'll want to work with @weshaggard to understand what's needed here.


Support directional search and automatic jump to match

The extension currently does a bidirectional search. Using directional search (s/S for after/before the cursor) enables automatic jumping to the first match and reduces the number of tags to be generated.

I surely can add an additional setting to set the search direction, but im not entirly sure how the smart jump would work. What exactly would be the condition for the cursor to jump to the first match?

leap.nvim has a set of "safe" labels (a subset of the main labels). If the number of matches is less than the number of safe labels - i.e. the safe labels are enough to cover all matches - the cursor is moved to the first match. Afterwards, you can go to the other matches by typing their labels as usual or ignore them and continue editing as you like.
These are the important ideas:

This is only possible for directional search because the concept of "first match" is undefined with bidirectional search
The safe labels set must not contain characters you're likely to use after a jump. E.g. hjlk, wbe, etc. See :h leap-config on neovim to see both sets.
leap.nvim uses capital letters, but this extension doesn't. That extends the label set further than this can.

leap.nvim also allows you to move to the next match using <enter> and the previous with <tab>, with the special case that s<enter><enter> repeats the last search.


chore: automated PR to update ReleaseNotes for 202401.09.0 VHD

This is an automated PR to bump ReleaseNotes for the VHD release with image version 202401.09.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2288

Relevant Lines:
2884

💛  - Coveralls


Map, View Map button and transition Issues in mobile

There are a few issues and lots of error messages in the console about the map, but showing on the list page.
Issues include.

An inconsistent big delay when clicking the 'View Map' button in mobile

Sometimes it loads showing the whole country

it then sometimes loads the map with an strange loading icon for ~5 seconds

The color of the button remains dark

Map is very slow to load after clearing search (though this may be a separate issue, and I'll create it as such)

[ ] ### Issues on list page

[ ] ### Map load button remains dark, as if it hasn't released from being selected

[ ] ### Dark View map/list button persists into list view

[ ] ### Clearing search affects subsequent map load

https://github.com/user-attachments/assets/ebb98482-7ac9-4c3d-836c-bb1323fac151

We can look at that above when you're here, since you can't recreate it @jbeard4.
These are the steps

click 'Explore services'
from the list click 'view map'
on the map search for something (e.g., DHS). This will take you back to the list (though i think we'd expect it to stay on the map, idk.
go back to the map, clear the search
go back to the list
try to go back to the map... i can't get it to do that consitently. The focus freezes on the 'View map' button.


Add .clang-format and .clang-tidy

This template is great and I used it to get started on a new c++ project easily!
Would you be open to me creating a PR with .clang-format and .clang-tidy to this repo?
I'm new to C++ and not sure what are the most popular tools but seems like linting and formatting are essential especially in c++.

@chinwobble sure yes, go ahead, I'd be happy to have those files as well.


Add support for http.batch()

We cannot deprecate the built-in k6 convert support until this tool outputs concurrent requests with http.batch()

I've increased the priority of this because its lack is causing other issues with k6. Trying to k6 archive a user's 22k LoC script generated by the new HAR converter (so, one with plenty of needless response = http.verb(whatever) needless repetition and no http.batch()) didn't finish in the 11 minutes I waited for it to finish... :astonished:
Slightly editing that same script so it's suitable for --compatibility-mode=base, k6 archive finished in under a second! So, the previous long wait time was likely due to the Babel transpile. I didn't remember us having such issues with previous huge scripts, so I spent some time writing a bunch of regexes to transform the script to one that used http.batch(), and then k6 archive finished in 39 seconds.
So, http.batch() support is important not only because it will make for more realistic load-tests and will allow us to slowly retire the built-in converter, the current output also causes k6 (or, rather, Babel) to choke on it.

The K6 convert has been completely removed in K6 v0.48.0 released in Dec, 23. So, it would be good to prioritize this issue further in order to support script generation that mimics the application more accurately by adding http.batch() to trigger multiple request in parallel as happens in modern browsers with HTTP2 protocol.
Moreover, The script generated by current version of har-to-k6 is expected to report high response time because of missing http.batch() implementation. I believe, it would be good to report this to users in the form of warning when using  har-to-k6, until this issue is resolved.

I'm fallbacking to go version, as I need batching ;-(


Pinned tabs overlap when folder names are visible

VSCode Version: 1.50.0-insider
OS Version: Windows 10

Steps to Reproduce:

Set your pin tab size to "normal": "workbench.editor.pinnedTabSizing": "normal"
Open an empty folder
Create 2 folders (in my example they are called folder1 and folder2)
Create a file in each folder that are named the same (in my example they are called file.txt)
Open both files and pin one of them
Notice that the tabs overlap because the pinned tab is not taking the folder name into account

Does this issue occur when all extensions are disabled?: Yes
/cc @bpasero

via https://github.com/microsoft/vscode/commit/09a78db5ef427ab945a2773239ab9fd6a9ef5e1c

@bpasero I do not believe that commit solves this problem. From what I can see that commit is changing the default to be "normal" which is not what this bug refers to.

@ChristopherHaws yeah but it also fixes a bad logic here:
https://github.com/microsoft/vscode/commit/09a78db5ef427ab945a2773239ab9fd6a9ef5e1c#diff-40eb1f52e432c4163061705abdfb5d61R1059


[$5] Use new endpoint to get member suggestions

To fix the first part of the issue https://github.com/topcoder-platform/micro-frontends-taas-admin-app/issues/51.
We've implemented a proxy endpoint in TaaS API which would return member suggestions no only to admins, but also to Booking Manager users.
So we have to update Admin App to not use ${config.API.V3}/members/_suggest/${fragment} and use /v5/taas-teams/members-suggest/{fragment}.
Update code to do so.

Verified on Dev Env. Suggestions are getting displayed now for Booking Manager role.

Paid via https://www.topcoder.com/challenges/0f2822a0-5250-4668-baec-7c885f852a4a

Verified on Prod with @nkumar-topcoder


Support for menu in interaction response

Fixes #26
Note: The wait flag and Reaction menus rely on bot being an attribute of interaction. This will not be the case until https://github.com/nextcord/nextcord/pull/348 is merged.*
This PR allows menus to be sent in response to an interaction such as components and slash commands.
Differences between menus in message commands and slash commands:
pages.start(interaction=interaction) will be used in place of pages.start(ctx)
Sending an initial message with interaction response:
await self.interaction.response.send_message(**kwargs)
return await self.interaction.original_message()

Sending an initial message with message commands:
return await channel.send(**kwargs)

*Workaround for using wait and Reaction menus in interaction response before https://github.com/nextcord/nextcord/pull/348 is merged:
class ClientInteraction:
    """Interaction with client and bot as additional attributes"""

    def __init__(self, client: nextcord.Client, interaction: Interaction):
        self.bot = self.client = client
        self.interaction = interaction

    def __getattribute__(self, name: str):
        try:
            return object.__getattribute__(self, name)
        except AttributeError:
            return getattr(self.interaction, name)

@bot.slash_command(guild_ids=[TESTING_GUILD_ID], name="confirm")
async def confirm_example(interaction: Interaction):
    pages = menus.MenuPages(source=MySource(range(1, 100)))
    await pages.start(interaction=ClientInteraction(bot, interaction))

This chnage is going to work well, I'm exited about this.


Internal server error caused by MYSQL_ATTR_INIT_COMMAND

I was trying to install the latest Pagekit (0.10.1) with PHP built-in web server and SQLite on Ubuntu.
STEPS I FOLLOWED:

Extracted Pagekit archive into  /.../pagekit/directory.
Launched PHP dev server. cd /.../pagekit/ && php -S localhost:8000
Visited http://localhost:8000 on browser.

WHAT I SAW:

http://localhost:8000 gave a blank screen instead of the installation wizard.
PHP dev server gave Undefined class constant 'MYSQL_ATTR_INIT_COMMAND' in /.../pagekit/app/modules/database/index.php on line 85.

// app/modules/database/index.php line 85

'driverOptions' => [
     PDO::MYSQL_ATTR_INIT_COMMAND => 'SET NAMES utf8 COLLATE utf8_unicode_ci'
]

Obviously I didn't have MySQL installed and configured but ideally that shouldn't be a problem because I was going to use SQLite. Commenting out PDO::MYSQL_ATTR_INIT_COMMAND => 'SET NAMES utf8 COLLATE utf8_unicode_ci' fixed the problem and I was able to complete the installation. However uncommenting it after the installation caused 500 error again.
SYSTEM:

PHP 5.6.10
SQLite 3.8.2
Required PHP modules installed: JSON, Session, ctype, Tokenizer, SimpleXML, DOM, mbstring, PCRE 8.0+, ZIP, PDO, pdo_sqlite, sqlite3, cURL, iconv.

Just note that i have same issue except i downloaded and extracted latest archive from an official site and use php-fpm module on nginx.
Here's my phpinfo.


This file has been edited

Have you read the Contributing Guidelines on Pull Requests?
Yes.
Description
Segregate Even and Odd nodes in a Linked List using C.
Checklist

[x] I've read the contribution guidelines.

[x] I've checked the issue list before deciding what to submit.

[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

Please fill the PR template and mention the details of your contribution, also mention the linked issue as here #6816.

@all-contributors bot please add @radhikaaojha for code


'$' character in identifier

In JavaScript, the '$' character is not special and can appear in identifiers.  jQuery makes extensive use of this.
For example:
var img = document.createElement('img');
img.src = "mylogo.jpg";
$(img).click(function() {
    alert('clicked!');
});

Language.Javascript fails to parse the '$' character.

@garious What version of language-javascript are you using? The $ symbol has been correctly parsed since version 0.3.0?  The current version is 0.4.5.
See the above commit, runtests.hs line 288, where I have added your test case, and it passes. The rest is just white space changes in the file.

I'm sorry, I contacted the owner of the wrong JavaScript package!  It was 'hjs' that had this issue.  Looks I should be using your library instead!

No problem. It has prompted me to bring it up to 5.1 standard, so
is.perhaps a good thing.
On Jan 21, 2012 7:26 PM, "Greg Fitzgerald" <
<EMAIL_ADDRESS>wrote:

I'm sorry, I contacted the owner of the wrong JavaScript package!  It was
'hjs' that had this issue.  Looks I should be using your library instead!

Reply to this email directly or view it on GitHub:
https://github.com/alanz/language-javascript/issues/2#issuecomment-3597519


Feature Request: Support Load & Store Trials

Support Load & Store Trials Please!

Thank you for the feature request!
It sounds nice, so let me consider how to implement that this week.


python310Packages.dvclive: 2.13.0 -> 2.13.1

Diff: https://github.com/iterative/dvclive/compare/refs/tags/2.13.0...2.13.1
Changelog: https://github.com/iterative/dvclive/releases/tag/2.13.1
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

2 packages failed to build:

python311Packages.dvclive
python311Packages.dvclive.dist

2 packages built:

python310Packages.dvclive
python310Packages.dvclive.dist


Add basic support for records in type checker; add then separator for sequential composition of actions

Add basic support for record decls and projection in type checker / adapt the old Sig/Join stuff to Record/Project (but keep basic support for SigDecl).
Add then separator for sequential composition of actions

NOTE / TODO: I haven't yet implemented checking of record expressions in the type checker. I have only done the minimum required to get the combined scoping+typing to work for record projections

Edit: There is a subtle thing to do with the names in Project and RecordExpr that I will look into / clean up tomorrow, but it's something that will only affect the backend / translation


Python 2 and 3 compatibility

This PR address one of the goals of #243 -- making v1.0.0 compatible both Python 2 and 3

[x] get unit tests to run

[x] base
[x] blocks
[x] images
[x] images_io
[x] readers
[x] series
[x] series_io
[x] timerseries

[x] update Travis to test both Python 2 and 3

@freeman-lab I think this is ready to go. A couple of change highlights:

Added six to the requirements. This package provides a level of abstraction for for accessing standard library functions/modules that changes names/locations between Python 2 and 3. Without this package, the code needed to make things compatible with Python 2 and 3 simultaneously would have been much much uglier.

There's a big difference between the way that Python 2 handles binary data (encoded as strings) and how Python 3 does it (a dedicated bytes object). When reading/writing text data to a file in binary mode (something that all of Thunder's readers/writers do), this means that, in Python 3, you now need to explicitly specify an encoding/decoding scheme. I have use utf-8 everywhere.

While not necessarily a Python 2 vs 3 problem, I added pillow to the requirements as well. When testing my Python 3 changes, I made a minimal Conda environment, and the base version of SciPy does not pull Pillow along with it, but it is needed to use scipy.mis.imread. Thus, it seems best to explicitly put this in the requirements.txt file so anyone pip-installing Thunder doesn't end up without it.

Amazing work on this @jwittenbach ! And doesn't seem like it was as bad as I feared. I left a handful of suggestions and comments, all fairly minor, the main one involving xrange. My thinking was we want to be as forward-looking as possible with these changes, even if it's a bit more work.
The other major comment is re: pillow, we do depend on scikit-image, and that depends on pillow, so I'm confused why you found it necessary to specify? I've always found pillow to be a minefield as a dependency, so while I'm not surprised something is funny, I'd also love to not have to deal with it ourselves, and if that means making a couple things optional, that's fine.

@freeman-lab Implemented all of the changes that we agreed on. The requirements list is beautifully short now :smile:

Awesome @jwittenbach  this looks good to me, merging in. Terrific work on this!


Annotate Fiber.[] and Fiber.[]=

Add method definitions to rbi/core/fiber.rbi for Fiber.[] and Fiber.[]= methods.
Motivation
Right now, we're getting Sorbet errors when doing Fiber[:a] and Fiber[:a] = 1, but these methods do exist
Test plan
I have not added tests for these, should I?

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_QHtyrPVHvv9gDY
→ https://go/builds/bui_QHtyzJWGF79MyV
→ https://go/builds/bui_QHtyZvD5ufYXdG


updating Meetup Pro guidelines

WIP

This is still a draft BTW (I changd the status because I wanted to see the preview)


Plans to support upcoming Kafka v0.11 ?

Any plans so far? 0.11 is about to be released fairly soon, adding support for message headers.
Thanks.

I would like to, but I have no time to work on it in the next little while. I'm happy to accept pull requests though.

We plan to add support for that, should we agree about transaction protocol before any work starts on this?

It'd be awesome if we could start using the projects tab to make a 0.11 roadmap. I'm sure that'd bring more people together to work on v0.11 support

What's the extent of work on this? Is there anything outlined as would be happy to pick it up if there's some low hanging fruit?

There's a bunch of work that can be done here, and a lot of the initial stuff is pretty straightforward low-hanging fruit.
The first batch of work is all foundational:

Add all the new errors (codes 45-55) to errors.go (easy).
Implement all the new request/response objects (keys 19-33) with the appropriate encode/decode methods and tests (easy). Each request/response pair can be done separately/in-parallel.

With that in place there's then a bunch of other improvements we can make to expose new functionality using the new request/response objects. Some of this should be pretty easy (e.g. a Client.AddTopic method) and some of it will be quite complicated (e.g. transaction support in the producer).
The other piece of work for 0.11 is to adapt to the new Message and MessageSet structures. The pure wire format changes shouldn't be too hard (though doing them without breaking old versions won't be entirely trivial). However, the switch to a non-recursive compressions structure and varint encoding looks really messy if we want to maintain backwards compatibility. I haven't had time to really dig into what would be required here.

I have already started (and almost finished) the work on using the new wire format for messages (now called Record and RecordBatch), but of course without all the transactional support. We mostly need it for the Headers extension. The way I implemented it for now was to add a separate field to the FetchResponseBlock for RecordBatch and I split consumer.parseResponse into separate functions dealing with old and new versions (based on the API version). And I'm implementing similar thing for producer path.
I thought I replied to this issue before, but it seems I didn't.

Just curious, if anybody made Headers part work? Or still planning to submit patch request?
Thanks.

Yes. I have it working and I just need to add a couple more tests and will post it tomorrow, hopefully.

After merging the PRs above, we support the new kafka 0.11 message format, including the ability to set headers.
There's no support for transactions or idempotent messages. I'm not planning to work on supporting these as I don't have an immediate use case for them.

@wladh  - does this also mean that you support Kafka v1.0.0 as well (with the same exceptions as above)?

@mastersingh24 - I didn't test it, but looking at the code, it seems Kafka 1.0.0 uses the same record format version as Kafka 0.11, so it should work.

@eapache - are you planning to release a new version anytime soon?

Yes, sorry, thanks for reminding me. Monday, probably.

v1.14 released with record-batch support.

Hello. Is there a plan (any other Issue or MR) to support the newly added Kafka transactions?

I am not working on it, since we don’t need it at the moment. I don’t know if anybody else is planning to submit a patch.

I have a working version of both consuming and producing using the transactional features that I'll try to finish off soon.
Would love some input on the API for producing, which currently looks like this:
type TransactionalProducer interface {
    AsyncProducer

    Begin() error
    CommitOffsets(groupID string, offsets map[string][]*PartitionOffsetMetadata) error
    Commit() error
    Abort() error
}

So producing looks something like so (as usual, errors ignored for brevity):
addr := []string{"localhost:9092"}

conf := NewConfig()
transactionID := "transaction_id"
conf.Producer.Transaction.ID = &transactionID
conf.Producer.Transaction.Timeout = 1 * time.Second
conf.Version = V1_0_0_0

// Embeds an `AsyncProducer`, and enforces necessary config constraints.
// Sends off the `InitProducerID`-request with the `TransactionID`.
producer, _ := NewTransactionalProducer(addr, conf)

go func() {
    for err := range producer.Errors() {
        // If we encounter a producer error the whole transaction
        // is aborted. Any calls to `Abort()`/`Commit()` will be no-ops
        // and a new transaction has to be started.
    }
}()

_ = producer.Begin()

// Adds sequence numbers and sends `AddPartitionsToTxn` request when encountering
// previously unseen topic-partitions.
producer.Input() <- &ProducerMessage{Topic: topic, Value: StringEncoder("hello")}

// Commit offsets through producer (`AddOffsetsToTxn` + `TxnOffsetCommit`)
_ = producer.CommitOffsets("groupid", map[string][]*PartitionOffsetMetadata{
    "topic": []*PartitionOffsetMetadata{
        {
            Offset:    11,
            Partition: 0,
        },
}})

// Will drain the messages and then send `EndTxn`.
_ = producer.Abort()
// or
_ = producer.Commit()

@eapache — what do you think would be the best way to submit this?
Thinking of splitting it into:
a) the request/response pairs (InitProducerID, AddPartitionsToTxn, AddOffsetsToTxn, EndTxn, TxnOffsetCommit)
b) the idempotent producer
c) the transactional producer + consumer (simplifies test design to submit these together).

Re. API my biggest question/concern is whether it even makes sense to add txn support to the async producer, or whether it should just be a feature of the sync producer? In the example code you provide, there is no guarantee that those messages have even been produced yet when you call Commit; you would have to watch for the appropriate Success/Error channel response which seems like a lot of work and easy to get wrong.
Re. submission, that sounds like a reasonable split but I can't really say for sure without seeing the code :)

Yes, I agree — it probably makes more sense to base it off the SyncProducer for the reasons you mention. And it makes error handling significantly easier. The only reason for going that async route is because the Java producer seems to do everything async (incl transactions) and I thought this was the API people was more or less expecting.

as a note, this is mostly due to previous API decisions made in sarama by the async producer (the channel based mechanism for waiting for Success and Error). The Java producer is async by default, but can wait for messages per send trivially. I don't think using the sync producer for transactional messaging counts as "full support", as the sync producer is so slow as to make it unusable except at very low throughput. In our testing adding transactions to the JVM producer doesn't change performance very much at all if the transaction batches are set large enough.

I'm not entirely clear on how the java producer works, but in principle if you don't wait for messages then transactions don't provide any value at all because you don't know whether a message is present in the transaction or not when you commit?
@tcrayford I'm curious what kind of code you would expect to be able to write with transactions in the async producer?
FWIW, the sync producer is a tiny wrapper on the async producer, so it can provide exactly the same performance if you use SendMessages with appropriately large batches, or just call SendMessage from multiple goroutines.

I'm not entirely clear on how the java producer works, but in principle if you don't wait for messages then transactions don't provide any value at all because you don't know whether a message is present in the transaction or not when you commit?

If you check an example eg here, you can see that you explicitly add messages produced and the offsets committed to the transaction.  So you do know whether a message is in the transaction - you added it.
IMHO this provides a lot of value - I'd call it the milestone where streaming systems are as general purpose a business rule paradigm as an RDBMS (assuming, that is, you are using "local state" paradigm, i.e. rocksdb/leveldb backing to a kafka topic).  Just without global mutable state, and able to support much higher scales of throughput even with complex transactions.

I'm also interested about transactional features. Any plans to deliver them in near future?

@Destidom Idempotent producer support has been merged in Oct 2018 https://github.com/Shopify/sarama/pull/1152 (not sure how complete that is though).
What are the outstanding features of Kafka v0.11 that we're missing?

What about the transactional producer and the exactly once semantic support? Is there any plan for that feature?

This catch-all issue seems like it has been superceded. Please open new issues for any functionality you believe is still missing from Sarama


Add multiple interfaces to rtsold call

We need to get all of the router info from rtsold so need to add multiple interfaces. Something like this, it works but maybe not the best way.

Geez, why can't these daemons run in parallel? :(
So there is a "-a" option here. If we make sure we only fire dhcp6fc for interfaces that have a valid config around (we can check this as we use it pre-merge for dhcp6c.conf) that would suffice, no?

The daft thing is that if you read the rtsold(8) it sort of contradicts itself...  I've been going round in circles trying to figure out why I am getting the same route address for both my WAN interfaces... then it struck me, they are both VLANs off the same interface on the primary router!
OK, let me try the -a option, I assume that means we don't spec interfaces in the command?

Yep, this and d8c8129889aa should prevent any non-expected fallout

-a option works, defaultgw6 and routerv6 are created for both my WAN interfaces.

I'll do a full test once you pull this in.

Do you mean "pull this in" as in I add -a and close the PR, or do you want to amend this PR to include -a to be pulled in? :)

:) doing the changes now...

Argh.. this logging bug is £$%"%!!!!
I THINK it's working OK. :)

Merged, thanks!

Master is now at bc5405bd54cd, what do you think?


Next: Moved html-init script to example directory and added documentation

I don't know if moving the init script out of the library code per se is something you would consider. IMHO it's not something which should be part of the core source. I think some example code would be good whatever we do.
This PR could be valid for the master version as well, but it would probably cause breakage, so maybe not.
If we do decide to keep the auto-initialisation code in core maybe we could add some code to dynamically load wavesurfer.js (and maybe plugin code) from CDN so the init script can be the only code which needs to be added. (To keep it really simple) – What do you think?
Edit1: Maybe it would be a good idea to use a hyphen in the custom html tag in preparation for custom elements (which require at least one hyphen in them)
Edit2: Also the auto-init-code could check for window.wavesurferOptions global variable and use those to extend the wavesurfer defaults. (So if there are 50 wavesurfer html tags on a page and they should all have a violet waveColor we don't have to set that as attribute in each).
I'm thinking of something like this:
<script>
  window.wavesurferOptions = {
    waveColor: 'violet',
    plugins: {
      timeline: {
        fontFamily: 'Times New Roman'
      },
      // ... if we want other plugin options valid for the whole page put them here
    }
  };
</script>

Then using the custom html element like this:

data-pluginName-pluginOption overrides/sets an option for a plugin
data-plugins is a comma-separated list of plugins to initialise (could also just use the plugins property in wavesurferOptions to determine which to use)

<wave-surfer
  data-progress-color="purple"
  data-url="../media/demo.wav"
  data-plugins="timeline,myOtherImaginaryPlugin"
  data-timeline-font-size="13px">
</wave-surfer>

wavesurfer.min.js and any plugin code we may need is being loaded automagically by this script
<script src="://my-awesome-cdn.example/wavesurfer-auto-init.min.js"></script>

Broken build should be fixed by https://github.com/katspaugh/wavesurfer.js/pull/891

I like the idea of fetching plugins from a CDN, but I don't think auto-init should be a separate script that bootstraps everything else. It's not much code and is quite common. For example, masonry.js does that.
Regarding renaming the tag to wave-surfer – again, I don't see the point of breaking some existing code on the internet with no benefit.

Okay. Sounds like a plan. I was thinking that we could use the same API 1:1 for when custom elements are the new standard. (Assuming that web components/custom elements will be the kind of frontend tech that gets traction and is widely adopted) – Except that one small detail (that they need a hyphen in them) – But maybe we can just change that API when and if the time comes.


UI : Re-style citation and symbol underlines

I've made the following changes

Recolour the underline to "#333"
Restyle the underline to "dotted" from "solid"
Correct a bug in the ui Readme file
Add height and width corrections to the bounding boxes for annotations

Merged in at https://github.com/allenai/scholar-reader/commit/8470e17dbd4943a1808b59caf7bc5d7e946f57cf! Thanks @nuwandavek !


3k²~ image encoded in lossless mode has color artifact above effort 4

Describe the bug
When using cjxl to encode a particular 2096x2088 PNG image to lossless JPEG XL, a reddish 48x40 rectangle appears at the bottom-right corner of the encoded JXL.
To Reproduce
Encode this image using cjxl -d 0 -e 5

Expected behavior
The encoded JXL should contain all pixels of the PNG unaltered.
Screenshots
This is a 512x512 crop of the bottom-right corner of the encoded JXL

Environment

OS: Windows 10
Compiler version: Unknown (downloaded from GitHub releases)
CPU type: x86_64
cjxl/djxl version string: JPEG XL encoder v0.10.2 e148959 [AVX2,SSE2]

Additional context
The image I had this issue on was the cover art for femtanyl's "CHASER" EP at original size, which is slightly graphic.
This would be rather distracting, so the provided test image is that cover art with the graphic part blacked out.
It exhibits the same problem as the source image.

Someone on the discord inspired me to check whether this was a regression:

0.9.3 encodes and does not exhibit this problem at all
0.10.0 and 0.10.1 crash when attempting to encode the image
0.10.2 and 0.10.3 encode the image with this bug.

I can confirm with JPEG XL encoder v0.10.2 7b9701eb

bug confirmed today with the last commit of master: cjxl v0.10.2 7b9701eb

The static release 0.8.2 seems to also have the bug, and the static release 0.10.2 gives a green square instead of red :D https://discord.com/channels/794206087879852103/848189884614705192/1265570789046882315

@veluca93 any idea what could cause this?
It seems to happen only when using multiple threads and when using streaming encode. The problem region is aligned with DC groups and corresponds to a DC group that is very small. Some kind of race condition maybe?
This is a high-priority bug imo.


VEGA-2235 fixed file path to access css file for tiny mce editor

VEGA-2235 #patch

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

Comparison is base (3eacf9d) 74.10% compared to head (6f1dda2) 74.10%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #446   +/-   ##
=======================================
  Coverage   74.10%   74.10%
=======================================
  Files         102      102
  Lines        4147     4147
=======================================
  Hits         3073     3073
  Misses        770      770
  Partials      304      304

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


responsive-sketchpad is not responsive

Window resizing does not make the sketchpad adjust its size.
How to reproduce: resize window to a small size on http://theisensanders-wf.github.io/responsive-sketchpad/

Previously there was an input slider on the page that triggered the sketchpad resize. I've changed to to resize with the window


Add first 5.0 stuff

This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Removed pods structure to align with our best practices for addon development.
Refactored all components to derive from frost-component from ember-frost-core (Resolves #44]

Changes Unknown when pulling 78f86164a899087477ceeb5d3b70bd292688618e on job13er:add-first-5.0-stuff into ** on ciena-frost:5.0-beta**.

@job13er Looks like we still do need these changes in. We did upgrade this repo though so I think we need a merge of the latest into this work. Probably no need to push it to a beta branch anymore though?

@rox163 Sorry, I totally forgot I even had this PR open. I don't have any particular need for this anymore, and actually don't even have that fork anymore. So I'll leave this in case you or anyone else wants to use what I did, but I have no need to get it merged anywhere.


Refactor the verify script into a test

Originally posted by @lewisjared in https://github.com/openmethane/openmethane-prior/issues/8#issuecomment-2116762252

Verify emissions script now integrated in tests/test_om_prior.py


kubectl reject annotation information without any warning

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
/kind bug
Kubernetes version (use kubectl version):
master
What happened:
If we use k create -f <file name> --save-config=true or kubectl apply <file name>, and this file have annotations with type not map[string]string, then kubectl will quietly reject those annotations.
For example, you have a yaml described object wich annotation is:
metadata:
  name: test
  annotations:
    a: haha
    b: 1

We can see b: 1 is not a correct annotation type. Then you use kubectl apply or kubectl create --save-config create this object, you will get an object with annotations like:
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ConfigMap","metadata":{"annotations":{},"name":"test","namespace":"default"}}

And if you already have this object with annotations, after the kubectl apply command, the annotation will be cleared.
What you expected to happen:
In this case, kubectl should error out, with an err invalid annotation or something else.
How to reproduce it (as minimally and precisely as possible):

Create a file with content like:

kind: ConfigMap
apiVersion: v1
metadata:
  name: test
  annotations:
    a: haha
    b: 1

Use k create -f <file name> --save-config=true or kubectl apply <file name> to create this object.
Check the new created object annotations.

Anything else we need to know:

@apelisse Can you help me confirm is this an bug or not, thanks. : )

Here are the two things I see:

Annotations are discarded without a warning or any message. You can't know what it's doing and/or why.
It shouldn't discard the annotation.

With regard to 1, I certainly agree that this is wrong. For 2., it also looks like a bug, but I'm much less certain.
I find it surprising that the code doesn't fail the validation. Do you think you can investigate that?

@apelisse Of course, actually, I already did. : )
In kubectl apply or kubectl create --save-config use case, kubectl need to get object annotations, and apply kubectl.kubernetes.io/last-applied-configuration annotation.
If this annotation not with type map[string]string, function NestedStringMap will return err, but the interface GetAnnotations will deprecate this err and return an empty map.
NestedStringMap: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured/helpers.go#L159
GetAnnotations: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/apis/meta/v1/unstructured/unstructured.go#L316
I think there are two way to fix this problem:

Add annotation validation. But the object is unstructed, so gonna be a little complex.
Add kubectl.kubernetes.io/last-applied-configuration annotation after object is created.

Add kubectl.kubernetes.io/last-applied-configuration annotation after object is created.

What do you mean "after is created"?
Also, I was expecting the object to be validated before we add the annotation.

I mean, we use the yaml file(whatever the annotation is) create the object first, if any field wrong, will return an error.
If object succefully created, then we can path kubectl.kubernetes.io/last-applied-configuration if needed.
Just a thought in my mind, don't know if it is feasible.

Yeah, would you mind looking at it? Because we definitely have validation in kubectl apply (which should fail on that object), maybe we just have to run it slightly earlier in the process.

Sure, I'll try to fix it. : )

/assign


FR: Clarifications or options on conflict overrisdes

There is a conflict between two options I use:
heading-blank-lines = true (Bottom=false)
empty-line-around-tables = true
expect:
# Heading
## Subheading

| col1 | col2 | col3 | col4 | col5 |
| ---- | ---- | ---- | ---- | ---- |
| xxxx | xxxx | xxxx | xxxx | xxxx |

to result in no change (and of course if there is no gap to add one), but instead results in the gap being removed:
# Heading

## Subheading
| col1 | col2 | col3 | col4 | col5 |
| ---- | ---- | ---- | ---- | ---- |
| xxxx | xxxx | xxxx | xxxx | xxxx |

Desired behaviour is that heading-blank-lines are respected, but any other whitespace requests override that. This occurs for code blocks and blockquotes also, but those are less of an issue because only "pretty" table rendering depends on a gap above a table being present (this also occasionally causes the Advanced Tables plugin "format all tables" to break the table, but that is not your fault, but a related annoyance!).

Hey @davidjroos . This actually has been fixed for the next release (see #751 ). The issue was that bottom was removing blank lines if set to false when in reality it should do nothing in that case.

Looks good after some quick tests thanks -  I did search but clearly not well enough!
It also looks to fix the similar conflicts with codeblocks and blockquotes :)

No problem. I did not rename that issue to a better name so it made it a little harder to find.


fix alignment and long GIF

Fixes two issues:

ligand was not being aligned together with the protein, so was placed way outside of pocket by GIF viz.
-> done by jumping alignment step to just after loading trajectory instead of after application of centering etc
hotfix for https://github.com/choderalab/asapdiscovery/issues/671, still need to make a more modular solution.
-> done by adding a default value of start based on the default MD protocol

Developers certificate of origin

[x] I certify that this contribution is covered by the MIT license as defined in our LICENSE and adheres to the Developer Certificate of Origin.

should be ready to go - testing on lilac now.


[BUG] When show reward ad fail, the app will freeze

Describe the bug
When show reward ad fail, the app will freeze
To Reproduce
Show the reward multiple time, and it will fail to show the reward ad, and the app freeze.
(if I minimize the app now, and switch back, it will back to normal)
Additional context
XCode Messages
(first call, it's OK)
******** stop animation!
2021-06-22 17:24:25.127527+0800 babacity[60464:2638552] [UIDevice.battery] Error retrieving battery status: result=-536870184 percent=100 hasExternalConnected=1 isCharging=0 isFullyCharged=1
2021-06-22 17:24:25.214409+0800 babacity[60464:2638867] [connection] nw_endpoint_handler_set_adaptive_read_handler [C3.1 <IP_ADDRESS>:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en1, ipv4, dns)] unregister notification for read_timeout failed
2021-06-22 17:24:25.214460+0800 babacity[60464:2638867] [connection] nw_endpoint_handler_set_adaptive_write_handler [C3.1 <IP_ADDRESS>:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en1, ipv4, dns)] unregister notification for write_timeout failed
2021-06-22 17:24:33.084812+0800 babacity[60464:2638552] rewardedAd:userDidEarnReward:
2021-06-22 17:24:33.084895+0800 babacity[60464:2638552] Reward received with currency coins , amount 10.000000
2021-06-22 17:24:37.779815+0800 babacity[60464:2638552] Ad did dismiss full screen content.
start animation!
(second call, it's freeze)
2021-06-22 17:24:37.781765+0800 babacity[60464:2638552] [aqme] MESubmixGraph.h:293:setMixerChannelLayout: (0x8ec300b2): scope 1, element 0, tag=0x0, 4 channel descriptions [Discrete-0, Discrete-1, L, R]: error -10851
******** stop animation!
2021-06-22 17:25:22.248383+0800 babacity[60464:2638552] rewardedAd:didFailToPresentWithError

Hi @ippan how do you make the Rewarded ad fail to appear?

I use MobileAds.show_rewarded()
close reward
and MobileAds.show_rewarded() again
and it fail

I'v tested this before on my samsung but it doesn't crash and does nothing instead of crash. But to workaround for now you can try something like this:
if MobileAds.rewarded_loaded:
    MobileAds.show_rewarded()
else:
    OS.Alert("No video for now :'(")  // You can use your custom Toast or something like that to let user know

thanks👍🏻  this solve my problem.

Hi @ippan, i don't know if this is a best practice, but to double ensure it always working. You should connect to  rewarded_ad_closed
In side of it you can try to load reward if it doesn't exist like below:
if !MobileAds.rewarded_loaded:
    MobileAds.load_rewarded()

It's a double check and my way of using. But since we'v checked it again before load. I think it's safe

@kyoz thanks for helping!
I will do more tests and if I find any bugs I will report it here in this issue.


Consider renaming this package

The name of this package misleadingly suggests that it provides a synchronous (i.e. non-"async") version of the fetch() API. This is not the case. The package has an entirely different purpose, and it does not provide synchronous interface. In a sense it is even more "async" than regular fetch(). Please consider renaming this package.

I will do asap. Thanks for raising.

NPM doesn't allow package renaming. Have renamed the repo.


Performance

Discussed in https://github.com/smartcorelib/smartcore/discussions/260

Originally posted by thegwan April 17, 2023
Are there any performance expectations for the algorithms implemented in this library? Should I expect them to be comparable to or faster than equivalent scikit-learn implementations?
My anecdotal tests show that they are quite a bit slower in both training and inference (I've been playing with decision tree in particular), but would like to confirm if this is expected.

Do you have any benchmarking results to show here?


[torchlib] torch.where(x) - default overload - is actually not implemented

As the title said the overload is not implemented in aten_where. It should be decomposed into nonzero function by pytorch.
Now it throws error as there is not enough parameters. Minimal reproducible example:
import torch

class Model(torch.nn.Module):
	def forward(self, x):
		return torch.where(x)

torch.onnx.export(Model(), (torch.tensor([0, 1, 2, 0, 3]),), dynamo=True)

<class 'ValueError'>: Required parameter 'self' is not provided. Signature: pkg.onnxscript.torch_lib::aten_where(condition: T_condition, self: TTensor, other: TTensor) -> (TTensor) where T_condition=BOOL, TTensor=INT8 | FLOAT16 | INT16 | INT32 | UINT8 | FLOAT | BOOL | COMPLEX128 | BFLOAT16 | COMPLEX64 | DOUBLE | INT64. Args: (SymbolicTensor('x', type=Tensor(INT64), shape=[5], producer=None, index=None),). Kwargs: {}.

As for the tests I would have thought it is handled by the ops_test.py but apparently it is not.

As a side note, the pylint is somehow broken for this file (at least).

I hit NotImplementedError though. It's not decomposed.

Based on this PR: https://github.com/pytorch/pytorch/issues/21798
The real fix is to implement: https://github.com/microsoft/onnxscript/blob/99cf79fd4ab150e3726b36fb3e9104304e203200/onnxscript/function_libs/torch_lib/ops/core.py#L6355 and register aten::where under it.
Something like:
# aten::where.default is the same as aten::nonzero_numpy
# https://github.com/pytorch/pytorch/issues/21798
@torch_op("aten::where", trace_only=True)
def aten_nonzero_numpy(self: TensorType) -> TensorType:
    """nonzero_numpy(Tensor self) -> Tensor[]"""
    nonzero = aten_nonzero(self)
    return aten_unbind(nonzero, dim=1)

And enable its test in ops_test.py.

The odd thing is it works for me by just removing it. Let me just install fresh venv and try again

OK, on today's nightly build of torch the decompositions does not work but on the stable version and the nightly from last week it have worked... 😮💨

You are right, on nightly build of torch the decompositions does not work but on the stable version it do... 😮💨
I think that it is better if it is decomposed by the pytorch, as there should be decomposition of where(x) to the nonzero in any way.
Something like:
if a is None and b is None:
    return torch.nonzero(pred, as_tuple=True)

here, which is actually where the NotImplementedError originates

@titaiwangms with this PR it works without any other change. I have no idea why as it seems to me there is no decomposition that would handle it.
But I will probably make PR from my previous comment in any way.

@titaiwangms with this PR it works without any other change. I have no idea why as it seems to me there is no decomposition that would handle it but it works.
But I would probably make PR from my previous comment in any way.

aten.where.default was overwritten by the second decomp table leading to a different result.


[FLINK-20658][connectors/jdbc] Establish connection through driver with given name

What is the purpose of the change
Establish jdbc connection through driver with given name.
Brief change log

Establish jdb connection through driver with given name.

Verifying this change
This change is already covered by existing tests:

SimpleJdbcConnectionProviderTest.testEstablishDriverConnection(ignored previously)

This change added tests and can be verified as follows:

SimpleJdbcConnectionProviderTest.testEstablishUnregisteredDriverConnection

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

e2e tests failed unrelated, I have reported it to FLINK-21025.


Speedup version bump tests

Description of the change
Attempt to speed up test suite by focusing on the slowest tests as described in https://github.com/spacchetti/spago/issues/440
Locally this change seems to have shaved off ~20s of test running time.
Checklist:

[x] Added the change to the "Unreleased" section of the changelog
[ ] Added some example of the new feature to the README
[x] Added a test for the contribution (if applicable)

@f-f just wanted to check with you what's the general strategy around PR reviews. Should I wait for your review/approval before I merge, or is just one review enough, like in the case of this PR?

@jhrcek great point, thanks for asking. This has not come up before so that's why we don't have a written policy about it yet
I think a review from a contributor is enough to merge, no need to wait for my review :)

@jhrcek thanks for doing this 🙂


otbr-agent crash

https://github.com/openthread/openthread/blob/687e04f6d460ec48b7b5b88216ed4b6d7348b81c/src/lib/spinel/radio_spinel_impl.hpp#L2226
in csl mode, when SSED send child update request, otbr-agent always crash at this.
the crash log is below:
Mar 22 16:47:37 mi otbr-agent[77754]: 00:00:06.790 [I] BorderRouter--: Evaluating routing policy
Mar 22 16:47:37 mi otbr-agent[77754]: 00:00:06.790 [I] BorderRouter--: Send OMR prefix fd18:a7f5:5aec:1::/64 in RIO (valid lifetime = 1800 seconds)
Mar 22 16:47:37 mi otbr-agent[77754]: 00:00:06.790 [I] BorderRouter--: Sent Router Advertisement on interface 2
Mar 22 16:47:37 mi otbr-agent[77754]: 00:00:06.791 [I] BorderRouter--: Router advertisement scheduled in 16 seconds
Mar 22 16:47:37 mi otbr-agent[77754]: 00:00:06.791 [I] BorderRouter--: Start evaluating routing policy, scheduled in 16000 milliseconds
Mar 22 16:47:37 mi otbr-agent[77754]: 00:00:06.791 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:e405:4a65:2b26:7f68 on interface 2
Mar 22 16:47:39 mi otbr-agent[77754]: 00:00:08.934 [I] BorderRouter--: Router solicitation times out
Mar 22 16:47:39 mi otbr-agent[77754]: 00:00:08.934 [I] BorderRouter--: Received Router Solicitation from fe80:0:0:0:e405:4a65:2b26:7f68 on interface 2
Mar 22 16:47:39 mi otbr-agent[77754]: 00:00:08.934 [I] BorderRouter--: Start evaluating routing policy, scheduled in 856 milliseconds
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.790 [I] BorderRouter--: Evaluating routing policy
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.790 [I] BorderRouter--: Send OMR prefix fd18:a7f5:5aec:1::/64 in RIO (valid lifetime = 1800 seconds)
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.791 [I] BorderRouter--: Sent Router Advertisement on interface 2
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.791 [I] BorderRouter--: Router advertisement scheduled in 209 seconds
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.791 [I] BorderRouter--: Start evaluating routing policy, scheduled in 209000 milliseconds
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.791 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:e405:4a65:2b26:7f68 on interface 2
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.803 [I] Mac-----------: Frame rx failed, error:Drop, len:120, seqnum:87, type:Data, src:aa929392c2e906f2, dst:72bc91b0e3d9e227, sec:yes, ackreq:yes
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.932 [I] BorderRouter--: Vicarious router solicitation time out
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.934 [I] BorderRouter--: Router solicitation times out
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:09.934 [I] BorderRouter--: Start evaluating routing policy, scheduled in 2857 milliseconds
Mar 22 16:47:40 mi otbr-agent[77754]: 00:00:10.151 [I] Mle-----------: Child CSL synchronization expired
Mar 22 16:47:41 mi otbr-agent[77754]: 00:00:10.953 [W] Platform------: radio tx timeout
Mar 22 16:47:41 mi otbr-agent[77754]: 00:00:10.953 [C] Platform------: BSD TCP function() at radio_spinel_impl.hpp:2226: RadioSpinelNoResponse
Mar 22 16:47:41 mi systemd[1]: otbr-agent.service: Main process exited, code=exited, status=6/NOTCONFIGURED
Mar 22 16:47:41 mi systemd[1]: otbr-agent.service: Failed with result 'exit-code'.
Mar 22 16:47:46 mi systemd[1]: otbr-agent.service: Scheduled restart job, restart counter is at 56.
Mar 22 16:47:47 mi otbr-agent[77901]: [INFO]-UTILS---: Running 0.3.0-3e501c4efd

@nykh2010 , can you provide more detail about your setup?

RCP and SSED platform are EFR32MG21 of Silabs.
ot-br-posix is build ./script/setup directly.
SSED connect to Border Router directly.

@romacdon @suveshpratapa , can you help take a look?

@nykh2010  can you provide additional info on your RCP environment?  Where are you building this from? ot-efr32?    If you are using Simplicity Studio what GSDK version are you using?

RCP is build by Simplicity Studio 5, the detail of SDK version is  "Gecko SDK Suite: Amazon, Bluetooth 3.3.0, Bluetooth Mesh 2.2.0, EmberZNet <IP_ADDRESS>, Flex <IP_ADDRESS>, MCU <IP_ADDRESS>, Micrium OS Kernel, OpenThread <IP_ADDRESS> (GitHub-9dedd1869), Platform <IP_ADDRESS>, USB <IP_ADDRESS>, Wi-SUN <IP_ADDRESS>, Z-Wave SDK <IP_ADDRESS> (v4.0.0)". The hardware is a USB stick of mg21.

Hi @nykh2010!
It sounds like you're using our major SDK release <IP_ADDRESS>, tagged with the following compatible GitHub versions. Please check both of them:
openthread @ 9dedd1869
ot-br-posix @ 58d09bee8
Note however, that we have a number of bug fixes we added around the low power feature in patch release <IP_ADDRESS>, with the following GitHub commits.  We suggest you use the latest <IP_ADDRESS> SDK if possible:
openthread @ 3b79cb0d084
ot-br-posix @ 5be35949c6f

@suveshpratapa ok, thank you! I will use the newest SDK and try again.

Closing stale issue.


Failed to load the segmentation

Now I am using the 5.7.0 32881 3d slicer with EC2 ubuntu 22.04.
When I try using the cpu version of  torch(2.2.1),everything works fine. However, when I use cu118 version, I get this error: failed to load the segmentation. Check ...
This seems to be error with SlicerNNUnet(with segmentationlogic.py)
Can you guys have a look?
Thank you.

Hi @dentistfrankchen,
Thank you for using our extension.
Could you also provide us with the run logs when you use CUDA?
The error you have is probably due to insufficient hardware capabilities when running on the GPU.
What hardware do you have on your machine ? (RAM & GPU & GPU VRAM)
Best,
Thibault

Same problem 32Gb RAM, Nvidia 3060 16Gb

@Matemusi thank you for reporting this problem.
Something apparently went wrong when decoding the logs coming from nnUNet.
We will be updating the SlicerNNUNet library for this problem (the fix should be available in the next preview version).

@Thibault-Pelletier As I understood the problem was in the long path to the files. I reinstalled slicer and extansion into just "C:\slicer" and it worked.

@Matemusi thanks for the feedback, glad that the extension now works correctly on your end!


Bump cert-manager to v11.5

Changes

Bump cert-manager to v11.5

Fixes #588
Release Note
net-certmanager is now tested with a minimal cert-manager version v11.5

Docs
None

/lgtm
/approve


EventHub: updated Package and added new test BYOK and Clusters

Swagger PR Links :
https://github.com/Azure/azure-rest-api-specs/pull/9207
https://github.com/Azure/azure-rest-api-specs/pull/9245
https://github.com/Azure/azure-rest-api-specs/pull/9321
https://github.com/Azure/azure-rest-api-specs/pull/9335

@isra-fel, added all swagger PRs regarding changes, added release notes and updated version.  please review and let me know if any changes needed


HDFilmCehennemi: Subtitles and audio are not synchronized.

Source information
HDFilmCehennemi 13.6
Source language
Turkish
Steps to reproduce

Open the movie you want to watch on HDFilmCehennemi

Expected behavior
Watch the selected movie with subtitles, video and sound synchronized.
Actual behavior
The subtitles, video and audio do not play in sync as they should, and sometimes the subtitles and sometimes the audio play first and the video plays intermittently.
Aniyomi version
Preview r6691
Android version
Android 11
Other details
This problem occurred after the last update of the extension. There was no such problem before.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Have you checked if this happens in the source itself?
By the way, you said that "There was no such problem before", but all the latest update did was add subtitles support to the Rapidrame extractor, which nullifies any correlation with audio synchronization problems or even subtitle problems on other hosters.


[BUG] AmazonMQ No metrics data found

Is there an existing issue for this?

[X] I have searched the existing issues

YACE version
since v0.39.0-alpha
Config file
apiVersion: v1alpha1
sts-region: eu-central-1
discovery:
jobs:
- type: mq
regions:
- eu-central-1
period: 300
length: 300
metrics:
- name: CpuUtilization
statistics:
- Maximum
Current Behavior
Works with version v0.38.0-alpha
After update to newer yace version:
No Metric Data for AmazonMQ
Debug Logs:
{"account":"1234","arn":"","job_type":"mq","level":"debug","msg":"No metrics data found","region":"eu-central-1","time":"2023-04-26T15:04:46Z"}
Expected Behavior
Metrics Data found.
Steps To Reproduce
Tested versions v0.39.0-alpha to v0.50.0
Anything else?
No response

Hi @vihongu, are your resources correctly tagged? Can you please post the output of aws cloudwatch list-metrics --namespace mq? Thanks!

We are seeing the same issue with AmazonMQ and discovery configs. Our output for that command is very empty. Note that mq is not the typical namespace, and using AWS/AmazonMQ returns what we'd expect.
aws cloudwatch list-metrics --namespace mq returns:
{
    "Metrics": []
}

So probably mq is not a correct alias for AWS/AmazonMQ, we might need to remove it.

From our experience, it appears as though discovery is working, but mapping dimensions from metrics results in "No metrics data found".

@cristiangreco, I've added a test for the associator in #914  that I believe represents the behavior that @ChrisDBaldwin and I are seeing. The discovery of ActiveMQ brokers appears to work correctly, but metrics have a dimension with a numbered suffix (i.e. -1) whether it is a single-instance broker or active standby broker configuration. In an active/standby configuration, each broker would push a metric (i.e. sampleBroker-1', sampleBroker-2, sampleBroker-3`). It seems we need a way to tell the associator how to match the dimension. Perhaps a match function could be used that could be defined for each service supported by auto-discovery?
I'll look at adding a test case for the max dimension associator next. We appreciate your insights toward resolving this. Thanks!

Hi, thanks for your response!
The output of the command is:
{
"Metrics": [ ]
}
With aws cloudwatch list-metrics --namespace AWS/AmazonMQ we got the list of our metrics.
We also tested the config
jobs:

type: AWS/AmazonMQ

with the same output. ("msg":"No metrics data found")

So this is about two different issues I think:

one is the fact that type: AWS/AmazonMQ should be used in place of type: mq
the other problem the peculiar name of broker with a numbered suffix. I think this has been reported in the past, but I kinda remember it only affected active/standby pairs (i.e. single instance brokers don't have the suffix)

I'll try to reproduce that this week.

I believe this is fixed in https://github.com/nerdswords/yet-another-cloudwatch-exporter/pull/917
You'll need to use -enable-feature=max-dimensions-associator, because the fix on the old associator algorithm is messy. Would you be able to test it and confirm?
(PS: I decided to special-case the AmazonMQ matching rather than introducing a generic mechanism for matching weird names. If this pattern comes up more often then the code can be reworked)

Built a image from Branch #917 and used the feature flag, confirmed metrics are being exported properly thanks!

Closing this ticket now that #917 has been merged.


[AMBARI-23687] - Log Search UI: the UI does not load the initial data

What changes were proposed in this pull request?
The problem was that UI did not load the initial data on logs screen loading.
There are few changes in order to fix this:

the activeLogsType property handling is changed in LogsContainerService in order to be sure in timing (change only when the store changed and populate the filter forms before use its values)
The cluster selection and the wrong routing in shipper config also caused timing issues

On the fly fixes:

Background of the diagramm
Navigation bar fixes for authorized and not authorized state

How was this patch tested?
Manually and with unit tests.
Please review Ambari Contributing Guide before opening a pull request.
@aBabiichuk please review it. Thanks.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2101/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2150/
Test PASSed.


nomad_0_11: 0.11.6 -> 0.11.7

Motivation for this change
closes: https://github.com/NixOS/nixpkgs/issues/106214
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.


Pin Ordering Question

Hello,
I'm using the following test.csv file to create a symbol:
TestIC,,,,,,
,,,,,,
Pin,Unit,Name,Type,Side,Style,Hidden
A1,,FUNC1_IN,in,left,,
A2,,FUNC1_IN,in,left,,
B1,,FUNC1_OUT,out,right,,
B2,,FUNC1_OUT,out,right,,
C1,,FUNC2_IN,in,left,,
C2,,FUNC2_IN,in,left,,
D1,,FUNC2_OUT,out,right,,
D2,,FUNC2_OUT,out,right,,
E1,,FUNC3_IN,in,left,,
E2,,FUNC3_IN,in,left,,
F1,,FUNC3_OUT,out,right,,
F2,,FUNC3_OUT,out,right,,

Then I run kipart with default options:
kipart test.csv

The pin order on the left side is as expected (FUNC1, FUNC2, FUNC3) but on the right side it is reversed (FUNC3, FUNC2, FUNC1 from top to bottom)
How can I keep the pins on the left and right sides aligned (e.g. FUNC1 pins above FUNC2 pins on both sides)? Am I missing something in the documentation?

Currently, kipart proceeds around the chip in a counter-clockwise direction. So when it gets to the right side, it starts placing pins at the bottom and proceeds upward. You'll have to reverse the order of the right-side pins or else rearrange the pins in the symbol editor.

Thanks for the reply. I ended up mirroring the right side pins in the symbol editor.


Consume expired

Description
Changes proposed in this pull request:

KEB consumes "expired" param

Related issue(s)

/retest

/retest


Remove DependencyInfoBlock

ref: https://gitlab.com/fdroid/checkupdates-bot-fdroiddata/-/jobs/8365078083
We find that there is a DependencyInfoBlock in your APK.
It's a Signing block added by AGP and encrypted with the Google public key so it can't be read by anyone else except Google. You can read more about it here and here.
While this was added a while ago, we were only enforcing it for new apps, and recently we started scanning updates too.
Could you please disable it with the following code?
android {
    dependenciesInfo {
        // Disables dependency metadata when building APKs.
        includeInApk = false
        // Disables dependency metadata when building Android App Bundles.
        includeInBundle = false
    }
}

Thanks!

Thank you for informing me about this. I'll remove the DependencyInfoBlock from apks, as the bundle should only be distributed through Google Play. I hope this is enough to solve this issue.


Add repository to package.json

Helps people click through to the repo from npmjs.org

Hi,
thanks for your contribution. You are right, a repository needs to be in there. Please fix the npm install issue and I will merge as soon as possible.
Regards,
Ben

Oops!
I made sure to add the comma to previous entry.
Closing this pull request in lieu of another pull request to have a cleaner commit history.


Minor changes to get the engine working with interledger.rs

The account is is a URL parameter instead of part of the body
The txHash is used as the idempotency key for settlements
The scale should be configured on the connector for an account and the engine it uses

You  run https://github.com/emschwartz/interledger-rs/blob/xrp-integration/examples/xrp_settlements_test.sh as: XRP_ENGINE_ROOT=/path/to/settlement-xrp ./xrp_settlements_test.sh

@gakonst Thanks for this.
I have added circleci for testing and linting to master. Can you merge that into your repo and push and it should run that against your PR.
So is the assumption that the SE does not handle scale conversion now? Do we have a discussion somewhere where the pro's/con's of this was discussed for reference.


It won't Connect, just keep connecting, anybody have the same prob or just my internet went nuts?

just mc server is down

try connect another ip in url param (it should work on 1.16.5 offline mode)

how do i use offline the server thing is down

just configure online-mode=false in server.properties


Make Filter for Included Scope in Resource Group optional

Describe your changes
Comment Triggers

PR Check triggers

Build: trigger build
Sub Category Field Check: trigger subcategoryfieldcheck

its a required field in api docs https://apidocs.harness.io/tag/Harness-Resource-Group#operation/createResourceGroupV2!ct=application/json&path=resourceGroup/includedScopes/filter&t=request

@rathodmeetsatish
Yep I have a support issue open right now that the docs they provide are incorrect.

This PR has been automatically closed due to inactivity.


Investigate Memory Models

The following structures use dynamic memory in some way:

Toy_Bucket
Toy_Ast
Toy_Routine
Toy_Bytecode
Toy_String
Toy_Array
Toy_Stack
Toy_Table

Toy_Bucket, specifically, is intended to be a custom allocator system, yet also uses the malloc system under the hood - this might be the wrong way to do it, as malloc handles the internal memory systems as well - there could be unnecessary redundancy here.
The fact of the matter is, I simply don't know enough about malloc to really understand the best approach to take. So, consider this an official request for assistance. Help a dummy understand, please.
Edit: I'd love for this language to work on platforms outside of windows/macos/linux one day, especially game consoles. Portability is a good idea.

Superceded by #160


[ios] release view from controller when popped from stack

This issue is related to #92.
Issue
I got issue when playing video with react-native-video. The video keep playing (still hear sound) when go back.
react-native: 0.61.5
react-native-screens: 2.0.0-alpha.22

Solution
When controller popped, try to assign view to nil to break the cycle.

react-native-video should probably also implement didMoveToWindow and willMoveToWindow, so that the video always pauses/stops when transitioning away.
Example swift code:
@objc(didMoveToWindow)
  override func didMoveToWindow() {
    super.didMoveToWindow()

    let isVisible = superview != nil && window != nil
    let isDetachedView = superview != nil && window == nil

    if (isVisible) {

    } else if (isDetachedView && !invalidated) {
      self.pause()
    // If the bridge invalidates it should stop playing
    } else if (isDetachedView && invalidated) {
      self.stop()
    }
  }

  override func willMove(toWindow newWindow: UIWindow?) {
    super.willMove(toWindow: newWindow)

    let wasDetached = superview != nil && window == nil && newWindow != nil
    if (wasDetached) {

    }
  }


Missing description / formatting issue

It would be nice to see a description at the top, not just for each overload. Because they probably all do the same.
Also, there's a remark only for the last overload (with one parameter) that finally explains (sort of) what these methods do and why. But it has additional paragraph breaks in the middle of the sentence.
I'd also wish for a more detailed explanation of how this is done, to imagine why I should use this magic.

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

ID: d38e24cd-3568-ee10-e18c-6262faeeb5bb
Version Independent ID: 4b23ab47-87c7-32b1-a0ca-9c13d5ec93e5
Content: HashCode.Combine Method (System)
Content Source: xml/System/HashCode.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Hi @ygoe, thanks for your feedback. Yes, docs.microsoft.com now allows us to do this instead of having to add remarks individually because all overaloads are now all in one page. But the size of the reference is huge and we haven't had time to make this sort of improvement yet since we migrated the content. I've added this to our backlog.


Add a few features for debugging

Just a little quicky thing to add some things that will help debug queries. I also added a separate dev-requirements.txt file where I put Django Debug toolbar, mainly because it's a bit of a superfluous thing that doesn't need to get installed in production. If there are any other requirements like that, maybe we can shift them over?

Good idea - I'll create an issue for moving additional dev requirements into the file you created.


resolve to wrong module with aliasFields

webpack-test/cases/resolving/browser-field should pass

Here are the missing pieces:

node_modules is missing from https://github.com/web-infra-dev/rspack/tree/main/webpack-test/cases/resolving/browser-field

To pass this: https://github.com/web-infra-dev/rspack/blob/6f85b0360cf8a65569c2d5188c882269c891688b/webpack-test/cases/resolving/browser-field/index.js#L2

We need to set browserField: true in the webpack config
https://github.com/web-infra-dev/rspack/blob/6f85b0360cf8a65569c2d5188c882269c891688b/packages/rspack/src/config/zod.ts#L321-L325
But it seems like there is a big mismatch between all these configs - See https://www.rspack.dev/config/resolve.html#resolvealiasfield and https://webpack.js.org/configuration/resolve/#resolvealiasfields

I'm still investigating on how to pass
https://github.com/web-infra-dev/rspack/blob/6f85b0360cf8a65569c2d5188c882269c891688b/webpack-test/cases/resolving/browser-field/index.js#L40-L43

For debugging what's being passed into oxc_resolver:
cd webpack-test
OXC_RESOLVER=TRACE pnpm t -- -t "resolving browser-field" | grep  alias_fields

and you should see alias_fields: [["browser"]]


connect to multiple upstreams

Flux can be told to connect to an upstream service with the --connect and --token options.
For testing, it would be useful to be able to connect to multiple upstream services.

A typical flux --connect looks like --connect wss://cloud.weave.works/api/flux.
In Weave Scope, upstreams can be specified as https://<token>@<host>, so perhaps here we could support multiple --connect options like --connect<EMAIL_ADDRESS>--connect<EMAIL_ADDRESS>Tokens in --connect would override any specified --token.

A stepping stone, in case that is easier, would be to have 1 "proper" upstream and 0..n read-only upstreams.

Flux v2, based on the GitOps Toolkit has support multiple notification providers https://toolkit.fluxcd.io/guides/notifications/


⚠ Bofrost.de has degraded performance

In e036c10, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1412 ms

Resolved: Bofrost.de performance has improved in 6c20594 after 6 minutes.


anyone train with tf >=1.4

have anyone train with tf>=1.4, company server cannot  allow switch cuda8,

It failed on Tensorflow 1.13 (works in 1.4). haven't tried any other versions

It failed on Tensorflow 1.13 (works in 1.4). haven't tried any other versions

can you run c_ops/build.sh ? tf <1.4 should be installed from source?

I was able to get the model to run in a virtual environment with a pre-compiled binary for TF 1.9 (so just a pip installed version).
What I had to do was the following:

In aster/c_ops/CMakeLists.txt, on line 5 under compiler flags, change the flag -D_GLIBCXX_USE_CXX11_ABI=0 to -D_GLIBCXX_USE_CXX11_ABI=1
Run make clean if you've already tried building this.
Rerun build.sh.
Next, in aster/core/sync_attention_wrapper.py, I encountered an error with the outputs of _compute_attention() around line 50. I guess newer versions of TF have this function outputting 3 values, so I captured the last one, which is supposed to contain info about the next state.
Finally, I had to pass this captured value to the call to seq2swq.AttentionWrapperState() around line 65 as an additional arg attention_state=original_next_state.

Doing this, I was able to run an evaluation script using a model I had trained using the older TF version. I didn't perform any tests to compare the equivalency of the model's performance, but the outputs seemed okay.
Hope this helps.


Apple Home cannot control brightness

Brightnes-control via Apple Home does not work. Lights stay on the same brightness-level. Color/Temperature-changes do work, so this is unlike #4 .
Log-extract:
[ 2024-10-29T18:36:19.423Z ] [ INFO  ] [ matter.js / Behavior                     ]: Invoke d6b0f3aeb2aa425bab69f4dae9d6179c.aggregator.light_kueche_licht_decke.levelControl.moveToLevelWithOnOff online#cf27612@95e72c54 level: 249 transitionTime: null optionsMask: { executeIfOff: false, coupleColorTempToLevel: false } optionsOverride: { executeIfOff: false, coupleColorTempToLevel: false }
[ 2024-10-29T18:36:19.446Z ] [ INFO  ] [ matter.js / Behavior                     ]: Invoke d6b0f3aeb2aa425bab69f4dae9d6179c.aggregator.light_kueche_licht_decke.levelControl.moveToLevelWithOnOff online#cf27614@95e72c54 level: 57 transitionTime: null optionsMask: { executeIfOff: false, coupleColorTempToLevel: false } optionsOverride: { executeIfOff: false, coupleColorTempToLevel: false }

Viele Grüsse
Aebgit

I see. In the old implementation I just needed to implement moveToLevel but not moveToLevelWithOnOff. Seems some voice assistants need the second one and some need the first one.


Fix performance regression for ArrayDataAdapter with Torch backend.

Updated ArrayDataset to handle full batches at a time to avoid collating batches of size 1.
See https://github.com/keras-team/keras/issues/19120
The benchmark provided in the issue was run both on CPU and GPU, performance is back to what it was in 3.0.2.

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

Comparison is base (c8700f4) 80.14% compared to head (feec83a) 53.75%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #19133       +/-   ##
===========================================
- Coverage   80.14%   53.75%   -26.39%
===========================================
  Files         341      357       +16
  Lines       36163    38397     +2234
  Branches     7116     7486      +370
===========================================
- Hits        28982    20640     -8342
- Misses       5578    16258    +10680
+ Partials     1603     1499      -104

Flag
Coverage Δ

keras
53.75% <100.00%> (-26.24%)
:arrow_down:

keras-jax
?

keras-numpy
53.75% <100.00%> (-3.34%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


exporter fails with error 400

Running with v0.6.0
My configuration is:
stackdriver_exporter:
    container_name: stackdriver_exporter
    image: frodenas/stackdriver-exporter:v0.6.0
    volumes:
      - /data/xxx.json:/tmp/xxx.json
    ports:
      - 9255:9255
    environment:
      - GOOGLE_APPLICATION_CREDENTIALS=/tmp/xxx.json
      - STACKDRIVER_EXPORTER_COLLECTOR_FILL_MISSING_LABEL=true
      - STACKDRIVER_EXPORTER_GOOGLE_PROJECT_ID=yyy
      - STACKDRIVER_EXPORTER_MONITORING_METRICS_TYPE_PREFIXES="serviceruntime.googleapis.com"
    restart: always

And i keep getting this error:
time="2019-05-23T09:42:01Z" level=error msg="Error while getting Google Stackdriver Monitoring metrics: googleapi: Error 400: Field filter had an invalid value of \"metric.type = starts_with(\"\"serviceruntime.googleapis.com\"\")\": Could not parse filter \"metric.type = starts_with(\\\"\\\"serviceruntime.googleapis.com\\\"\\\")\"; syntax error at line 1, column 26, token '\"\"', badRequest" source="monitoring_collector.go:138"

what is wrong with my configuration?

Ok, I found it - I needed to remove " around prefix value...


rename EventProcessor* to RoundManager*

renamed the type, fields, lens
run-everything passes

All looks good, @haroldcarr.  Thanks for your first contribution (to this repo)! :-)


How to schedule co-routines acros different processes?

I notice the actual task (Component::Process) is wrapped with a lambda and passed to the coroutine factory as described in component.h, allowing for the scheduler to create a task based on the component name and the task function.
But I assume that each component is loaded by a separate mainborad process upon launch, and the intended component object is created within that process, along with other util classes that support CyberRT (e.g., scheduler).
I wonder if the schedulers are isolated across the processes though being singleton within its process. How can the task functions (XXXComponent::Proc) from different processes be co-scheduled in the form of co-routines?
Thanks for you reply!

And what if the task function itself is multi-thread? Are the threads it creates also handled by the scheduler as co-routine tasks?


feat(track) track call improvements for LP2.

As discussed yesterday, we will have to each message only two events: view and Accept.


something error in params.feature_hashing_dimension parameters

I have run your codes in python/benchmark/random_benchmark.py
but if I run your code in high dimension setting
such as with dimension $d=10000$
I want to set params_cp.feature_hashing_dimension = 1024
but error occors
AttributeError: '_falconn.LSHConstructionParameters' object has no attribute 'feature_hashing_dimension'

Any solution about this?

@selous123  the python wrapper  does not support sparse datasets yet, and that is the reason this param is not exposed yet.
See here: https://github.com/FALCONN-LIB/FALCONN/blob/master/src/python/wrapper/python_wrapper.cc#L517


Generate random message id.

About message ID, the CoAP specification say  :
"4.4.  Message Correlation ...
... Several implementation strategies can be employed for generating Message IDs. ... ...  It is strongly recommended that the initial value of the variable (e.g., on startup) be randomized, in order to make successful off-path attacks on the protocol less likely."
So, I propose to replace the predictible way to generate message ID by using srand() and rand() from stdlib.

Project moved to http://github.com/eclipse/wakaama


dose it support sourcemap?

i use typescript-to-lua transform typescript to lua, dose it support sourcemap?
like ZeroBraneStudio can debug Moonscript/GSL-shell.

Its should. But I did not test it

I use it like this,emm, nothing happend

Can you provide simple instruction how to setup it in zbs,  so i can to test it and fix in vscode?

Also, can you test mobdebug.lua module from this repo with ZBS

Moonscript
and
GSL-shell.

Can you provide simple instruction how to setup it in zbs, so i can to test it and fix in vscode?

I draged mobdebug.lua from this repo to my project. ZBS debug lua right.

Also, can you test mobdebug.lua module from this repo with ZBS