Protocol methods shown as "Required. Default implementation provided" sound weird

Description
Given a protocol like
public protocol ClusterSingleton {
  func activateSingleton() async
  // ...
}

extension ClusterSingleton {
  public func activateSingleton() async {
    // nothing by default
  }

  // ...
}

the methods are listed as:

I'm wondering if the wording isn't rather sub-optimal here...
The strong required makes it look like the implementation HAS TO provide an implementation, but in fact, it does not have to -- since the default impl is provided, making his requirement optional to implement.
In Swift, all protocol requirements are "required", but it depends if they have an default impl or not if we have to implement them or not...
Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
Consider omitting the Required. bold wording from such protocol requirements when a default impl is found?
This might be more complex when the extension has where clauses, then probably ok to keep this as Required, but when the extension is always applied, such requirements can be seen as optional to implement.
Actual behavior
All requirements always get the bold Required. marker
Steps To Reproduce
No response
Swift-DocC-Render Version Information
5.7

\cc @willimholte
I agree the wording can be a little confusing for this specific scenario, even though it is technically correct—it is still required but the API itself has met that requirement with its default implementation and not strictly necessary for client code to provide their own implementation. I think it could be argued that the text could be dropped here as you point out.
Your note about the complexity of the scenario with where clauses has me wondering if the renderer could even special case something like this though since it wouldn't necessarily have details about that kind of information without parsing the declaration text.


Purchase order barcode fixes

Follow up to https://github.com/inventree/InvenTree/pull/5509

Fixes implementation for digikey
Improve user feedback
Simplify / refactor implementation

Closing. Will wait until https://github.com/inventree/InvenTree/pull/5919 is merged and then reassess


Versions of Github actions updated

Summary: Versions of Github actions updated
Type: Feature
Test Plan: UnitTests, ComponentTests
Jira: RIALTO-490

https://jenkins.code.rdkcentral.com/job/github-triggered/53141/ started

https://jenkins.code.rdkcentral.com/job/build-component/93573/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/17020/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/25840/ started.

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/rialto/298/rdkcentral/rialto

Commit: 2728c80f128bc91a258ea6800712a4ea8ff90f2a

Report detail: gist

https://jenkins.code.rdkcentral.com/job/github-triggered/53142/ started

https://jenkins.code.rdkcentral.com/job/build-component/93574/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/17021/ started

Sanity tests for ['RPI4 Mediaclient'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/47086/

Sanity tests for ['RPI4 Mediaclient'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/47087/

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/47092/

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: OK

Commit: 84b5507854179202ef0007e92067d3c8d78bc622


Ircc form

@nmakuch paragraph should not be in H2, should probably use "plaintext" components. tx

chatted with Mario a bit on slack but I'm going to merge this in. The form itself is awkward (I converted as is with little design intervention) and has ridiculously long labels (sometimes 2 paragraphs :s). I think a better solution to this would be a content design review as the labels for the questions themselves should probably be reworked.


munge: Fix installation paths

Description of changes
Removing src/etc/Makefile is overly intrusive, as the file is responsible for installing pkg-config file.  The issue when it would try to write to the specified out-of-store paths can be easily resolved by overriding them to ones within $out during installation.
Also set sysconfdir path properly to allow configuring it with environment.etc. There should be no problem with missing files, as nothing was installed to $out/etc previously either, other than an empty munge directory.
runstatedir defaults to $(localstatedir)/run but that has long been deprecated in favour of /run, so let’s fix that as well.
pkgconfigdir and sysconfigdir (not to be confused with the standard sysconfdir) rely on FHS for proper detection and systemdunitdir tries to run systemd --version, let’s just hardcode them.  sysconfigdir is mentioned in the newly installed munge.service and a file within is loaded as EnvironmentFile when it exists so let’s override the path for installation so the file can serve as a template in $out. The other two are installation-only so we can directly set them to $out subdirectories.
Also clean up the expression.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/unable-to-locate-pckg-installation-in-configure-phase-during-nix-build/46920/2

Result of nixpkgs-review pr 319401 run on x86_64-darwin 1

1 package built:

munge

@GrahamcOfBorg test slurm


fixed monaco overflow on server page

Tested locally
https://www.loom.com/share/fc81ff3a2a444a16b3bbdc9a1513501d

bruh.

Yes but only because you asked.


[WIP] 658 659 move data

Heavily WIP, profiles are almost gone (down to ~300 test failures now vs. 580 in the beginning 😁 ).
Help is appreciated! I left a lot of "TODO:" comments, just search for them and to what you can.
For the moment, I just commented all profile-related tests and stuff that ins't used at the moment but could possibly be reused later in this PR.

Coverage decreased (-34.2%) to 65.823% when pulling f8bcd74f3e60a18dea6061f859a0704c3af378cb on 658_659_move_data into e3e5cb113ae91fe6e27d943b8e97141f3326b338 on dev.

Coverage decreased (-20.7%) to 79.3% when pulling 87e3aade63d113f6223b9b30e413338decffdf0f on 658_659_move_data into e3e5cb113ae91fe6e27d943b8e97141f3326b338 on dev.

Coverage decreased (-20.4%) to 79.598% when pulling 71968872f8b87c1cad5488cde77fc0097e7e02e4 on 658_659_move_data into e3e5cb113ae91fe6e27d943b8e97141f3326b338 on dev.


Supporting multiple instances

Describe your question
Does MQTTnet supports multiple instances? E.g.
IMqttClientOptions_options1 = new MqttClientOptionsBuilder()...
IMqttClientOptions_options2 = new MqttClientOptionsBuilder()...
IMqttClient _client1;
IMqttClient _client2;
Task mqttClientAuthenticateResult1 = _client1.ConnectAsync(_options1);
Task mqttClientAuthenticateResult2 = _client2.ConnectAsync(_options2);
Which project is your question related to?

Client

Yes, it does. Just stay cautious to use unique client identifiers for all clients to avoid disconnection issues.


fix: check for location when extracting npm path

resolves null error when calling gen_runtime=ProtoBufRuntime.sol instead of gen_runtime=./ProtoBufRuntime.sol

i used location.StartsWith and it worked too.


[stable/grafana] Fix templating issue in dashboards-json-configmap.yaml

What this PR does / why we need it:
This PR fix a templating issue in dashboards-json-configmap.yaml file.
Which issue this PR fixes
No issue reported.
Special notes for your reviewer:
The CI should catch those templating issues running helm template
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@nhuray
Could you bump the chart to latest again please? Thank you.


我这是安装成功了吗？如何启动？

 Fix your #egg=whisper fragments.
Discarding git+https://github.com/openai/whisper.git: Requested openai-whisper from git+https://github.com/openai/whisper.git (from autocut==0.0.3) has inconsistent name: expected 'whisper', but metadata has 'openai-whisper'
Collecting srt
  Downloading srt-3.5.2.tar.gz (24 kB)
  Preparing metadata (setup.py) ... done
Collecting moviepy
  Downloading moviepy-1.0.3.tar.gz (388 kB)
     ---------------------------------------- 388.3/388.3 kB 2.0 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting opencc-python-reimplemented
  Downloading opencc_python_reimplemented-0.1.7-py2.py3-none-any.whl (481 kB)
     ---------------------------------------- 481.8/481.8 kB 7.6 MB/s eta 0:00:00
ERROR: Could not find a version that satisfies the requirement torchaudio (from autocut) (from versions: none)
ERROR: No matching distribution found for torchaudio

I installed by docker. it was interrupted:
...(more omited)
Collecting mpmath>=0.19
  Downloading mpmath-1.3.0-py3-none-any.whl (536 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 536.2/536.2 KB 2.9 MB/s eta 0:00:00
Installing collected packages: mpmath, urllib3, typing-extensions, sympy, pillow, numpy, networkx, MarkupSafe, idna, filelock, charset-normalizer, certifi, requests, jinja2, torch, torchvision, torchaudio
Successfully installed MarkupSafe-2.1.2 certifi-2022.12.7 charset-normalizer-3.1.0 filelock-3.10.0 idna-3.4 jinja2-3.1.2 mpmath-1.3.0 networkx-3.0 numpy-1.24.2 pillow-9.4.0 requests-2.28.2 sympy-1.11.1 torch-2.0.0+cpu torchaudio-2.0.1+cpu torchvision-0.15.1+cpu typing-extensions-4.5.0 urllib3-1.26.15
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: You are using pip version 22.0.4; however, version 23.0.1 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
Processing /autocut
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting whisper@ git+https://github.com/openai/whisper.git
  Cloning https://github.com/openai/whisper.git to /tmp/pip-install-q9l912qb/whisper_4911073835da4e258ba3c674ed8c9452
  Running command git clone --filter=blob:none --quiet https://github.com/openai/whisper.git /tmp/pip-install-q9l912qb/whisper_4911073835da4e258ba3c674ed8c9452
  Resolved https://github.com/openai/whisper.git to commit 6dea21fd7f7253bfe450f1e2512a0fe47ee2d258
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'done'
  WARNING: Generating metadata for package whisper produced metadata for project name openai-whisper. Fix your #egg=whisper fragments.
Discarding git+https://github.com/openai/whisper.git: Requested openai-whisper from git+https://github.com/openai/whisper.git (from autocut==0.0.3) has inconsistent name: filename has 'whisper', but metadata has 'openai-whisper'
Collecting srt
  Downloading srt-3.5.2.tar.gz (24 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting moviepy
  Downloading moviepy-1.0.3.tar.gz (388 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 388.3/388.3 KB 116.2 kB/s eta 0:00:00
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting opencc-python-reimplemented
  Downloading opencc_python_reimplemented-0.1.7-py2.py3-none-any.whl (481 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 481.8/481.8 KB 869.3 kB/s eta 0:00:00
Requirement already satisfied: torchaudio in /usr/local/lib/python3.9/site-packages (from autocut==0.0.3) (2.0.1+cpu)
Collecting parameterized
  Downloading parameterized-0.8.1-py2.py3-none-any.whl (26 kB)
ERROR: Could not find a version that satisfies the requirement whisper (unavailable) (from autocut) (from versions: 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 0.9.10, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15, 0.9.16, 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.1.10)
ERROR: No matching distribution found for whisper (unavailable)
WARNING: You are using pip version 22.0.4; however, version 23.0.1 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
The command '/bin/sh -c pip install torch torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/cpu &&     pip install .' returned a non-zero code: 1

依赖问题已更新修复


Write a Newer Readme.md

The previous readme was before the migration to trailsjs.io, so we should update the documentation to reflect that.

adding a contributors guideline could be helpful if we want it to be a sustainable project.
https://gist.github.com/PurpleBooth/b24679402957c63ec426

barebones for now revisit later and not leave dangling issues.


Updating branches does not reflect deleting branches on Github website

If you delete a branch on the website then reload branches on the extension, they will still be present.

This was a result of updateBranches() only looking at local copies of remote branches instead of actually connecting to the remote to get new info. It is now fixed (in commit be45fd6).


New (beta) Subject pages should include ability to edit and delete subject

Thanks @emilykaplan!

Closed by 7a48b3a9bde342d2e0caf4d2fe8772e39dd41c8f


Embedded logos don't render in the correct positions when SVG is loaded in Chrome/Safari

For some reason, the SVG with embedded logos renders like this in Chrome and Safari:

Even though the same SVG renders fine in Firefox:

and the PNG rendered with cairosvg.svg2png is fine too:
https://github.com/beveradb/logo-diagram-generator/blob/main/examples/full.example.light_logos.png
So, presumably something about the transform attributes I'm adding to the root svg tag for each embedded logo isn't compatible with all SVG rendering engines:
https://github.com/beveradb/logo-diagram-generator/blob/main/logo_diagram_generator/generate_diagram.py#L239
Theory: inserting a parent <g> with the transform, and inserting the logo svg inside that, might solve it.

Yup, that fixed it.
https://github.com/beveradb/logo-diagram-generator/commit/b13c09e74f57c6413a4ec97fec752124699e0a2b


Unify build script for both STM32 and ESP32

[ ] Reorganize folder structure, if needed.
[ ] Introducing a unified build script (shell-script, python or nodejs) could be a candidate solution. (instead of direct use of Make)

Target folder structure
/targets
  /kameleon-core
  /esp32-devkitc
    /main
    /components
    /...
  /linux
  /...

cmake script for the common build environment.

cmake scripts for the kameleon-core is implemented.

cmake script for the common build environment.

cmake scripts for the kameleon-core is implemented.

CMake build procedure.
cd cmake
cmake .
make

the binary is created in the cmake directory.

CMake build procedure.
cd cmake
cmake .
make

the binary is created in the cmake directory.


Jumping button sometimes not Clickable

Are you requesting a feature or reporting a bug?
Bug (maybe Feature)
What is the current behavior?
Clicking a button (which definitely exists on the page) fails when the button is moving or jumping.
(I could imagine that this could be an expected behavior correctly simulating human failure to click a button that jumps away exactly in that instant. However from a test case perspective it would be at least helpful to have an option to ensure the click if technically possible.)
What is the expected behavior?
calling t.click(buttonThatExists) should generate an onClick event
How would you reproduce the current behavior (if this is a bug)?
In practice that problem happened when trying to click a button on a page with dynamic content above the button (e.g. an image with a variable height displayed after a page update. Depending on the loading latency the height can jump at an upredictable time).
This causes non deterministic test failures even if the button exists in the DOM with a working onclick-event-listener.
Provide the test code and the tested page URL (if applicable)
To simulate/simplify this scenario I reduced it to a simple div, that changes height randomly based on setInterval(). The clickable buttons are placed below the div so that they visually jump around while always being present in the DOM.
Now when running a test trying to click either button it arbitrarily succeeds or fails. Of course this case is an exaggerated scenario hopefully isolating this from the real life case where network/render latency might cause such a problem only under rare circumstances, making it even harder to debug/fix test cases - eventually having to compensate every click that might fail due to a similar behavior.
Tested page URL:
https://jsfiddle.net/0pws3a9z/1/
Test code
import {Selector} from 'testcafe';
fixture `click-test`.page `https://jsfiddle.net/0pws3a9z/1/`;

const switchToA = Selector('#switchToA');
const switchToB = Selector('#switchToB');
const pageTitle = Selector('h1');

const hasPageTitle = title => pageTitle.withText(title).exists;

test('problem clicking jumpy button', async t => {
    //just try often enough to cause the problem
    await t.switchToIframe('[name=result]');

    for(var i = 0; i < 10; i++) {
        await t
            .click(switchToA)
            .expect(hasPageTitle('Title A')).ok() //might fail here due to lost click in previous line
            .click(switchToB)
            .expect(hasPageTitle('Title B')).ok() //might fail here due to lost click in previous line
    }
});

Specify your

operating system: Windows 10 Home Edition (64bit)
testcafe version: 0.21.1
node.js version: v8.5.0
browsers: Chrome( 68.0.3440.106)/Firefox(61.0.2 (64-bit)/IE11/edge(42.17134.1.0)

Please accept my apologies for the delayed response.

As you correctly noticed, it is difficult for a user to click a moving button. In the same manner, TestCafe can click only a visible and not moving element (i.e., when an element does not change its position) since it emulates user behavior.

In your example, the button is constantly moving and TestCafe cannot determine where and when the button is moving. As a workaround, you can determine the reason why the button (or any other element) is moving. For instance, if it is moving due to the preceding element appearance, you can wait until that element appears as follows:
await t.expect(Selector("#element").visible).ok())

If the preceding element changes its height (as in your example), you can use the ClientFunctions function to fix its height by adding some CSS styles:
const fixHeight = ClientFunction(() => { document.getElementById('#el').className = 'fixedHeight' });

#fixedHeight {
    height: 100px!important;
}

In addition, I'd like to mention that when the target element is moving, TestCafe will make another attempt to click it during the selectorTimeout period of time. If you increase this timeout value, there's a greater chance that TestCafe will click the moving element.

Thanks for your feedback. I understand that click behavior can be confusing so I've created a separate ticket with a sample example #2930. We'll consider how we can improve this behavior in the context of that issue.


Release 2017.11

This PR is the official develop to master branch pull request. Once merged this will be the 2017.11 Release.
The main features in this release are:

Credentials Override: This allows Runbook Actions and Checks to override the default SSH credentials specifying their own.
Documentation fixes: Several documentation updates to both /docs and the config/config.yml file.
Docker build fix

Coverage increased (+0.09%) to 71.179% when pulling b44b47cd573344f6e6362311bee15022f85f2c48 on develop into 1bfc1721cac018dbf66061ed4b8aba98267a7c1a on master.


dns error

unfortunately I cannot get it to run - I always get dos error. Anahi is running outside of the container. And I purged the persist folder as well...
any ideas?
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns/lib/advertisement.js:56
  dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name,
         ^
Error: dns service error: unknown
    at Error (native)
    at new Advertisement (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns/lib/advertisement.js:56:10)
    at Object.create [as createAdvertisement] (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns/lib/advertisement.js:64:10)
    at Advertiser.startAdvertising (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Advertiser.js:43:30)
    at Bridge.Accessory._onListening (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:510:20)
    at HAPServer.emit (events.js:104:17)
    at HAPServer._onListening (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:182:8)
    at EventedHTTPServer.emit (events.js:104:17)
    at EventedHTTPServer.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:62:10)
    at Server.emit (events.js:104:17)

I have the same problem

Did you manage to resolve this, same issue here?

No I did not and gave up. I now run it directly on the host. less then ideal but it works without any problems

@gazzer82 @timoschilling @snizzleorg Have a look at #15 which solved the issue for me.


0.3.2 Release

Description
Releasing 0.3.2 early due to Vulnerability fixes.
MySQL/MariaDB Upgrades from 0.3.0/0.3.1 aren't possible. Databases will need to be recreated and data re-imported.
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Yes
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have updated changelog.md with changes made

Lets hold on this until tomorrow since #286 still has issues :(


Dask Dataframe index renaming doesn't work in place

Inplace parameter doesn't behave as expected:

Thanks for repoting @marcelned! I'm able to reproduce. My guess is that since we regenerate .index each time it's accessed:
https://github.com/dask/dask/blob/ab69fe124eb36a63c092026ab082ccb08311fc79/dask/dataframe/core.py#L480-L489
There's some underlying state that rename(..., inplace=True) isn't updating that it should. Is this something you're interested in working on? (no obligation though)

Whoa I had no idea that a series could have a different name than its column name. For anyone else reading this, this is what pandas does:
import pandas as pd

df = pd.DataFrame(
    {
        "Animal": ["Falcon", "Falcon", "Parrot", "Parrot"],
        "Max Speed": [380.0, 370.0, 24.0, 26.0],
    }
)
df["Animal"].rename("Bird", inplace=True)
print(df["Animal"])
# 0    Falcon
# 1    Falcon
# 2    Parrot
# 3    Parrot
# Name: Bird, dtype: object

I think you are right to bring up the option of removing the inplace option from rename. That seems like the safest and best path forward. Are you interested in opening a pull request to implement that change?

Incidentally the inplace rename does work for a series in dask. The issue you are running into is that when you access the series by getting it off the dataframe like ddf["Animal"] you actually get a new object. So even if you then rename that inplace, you don't affect the real object. Here's where the new object gets created:
https://github.com/dask/dask/blob/e1974bffd6067659bb250fd84b6eb3f224cdb79f/dask/dataframe/core.py#L3993
I still like your idea of not allowing inplace as an option for rename, just trying to give more context about what's going on.

@jsignell @jrbourbeau I made Pull request #8133, removing the inplace argument and associated logic from the renaming function.
@jsignell the inplace argument seems to be a highly contentious issue even in base pandas: https://github.com/pandas-dev/pandas/issues/16529. It is used in edge testing cases rather than user code.
Dask being lazily evaluated (so no saving memory by inplacing data on an existing object using inplace=True) , is there a case for inplace being anywhere in the dask API?

Closed by https://github.com/dask/dask/pull/8136


CursorWindowAllocationException thrown in Query.run()

Hi,
The following exception was observed in 1.0.4.
CursorWindowAllocationException
android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed.
at android.database.CursorWindow.<init>(CursorWindow.java:104)
at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)
at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:139)
at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:133)
at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:197)
at android.database.AbstractCursor.moveToNext(AbstractCursor.java:245)
at com.couchbase.lite.android.AndroidSQLiteStorageEngine$SQLiteCursorWrapper.moveToNext(AndroidSQLiteStorageEngine.java:178)
at com.couchbase.lite.Database.getLastSequenceNumber(Database.java:294)
at com.couchbase.lite.View.updateIndex(View.java:386)
at com.couchbase.lite.Database.queryViewNamed(Database.java:2096)
at com.couchbase.lite.Query.run(Query.java:378)

Query
The query do have IndexUpdateMode.BEFORE set.
			Query query = view.createQuery();
			query.setIndexUpdateMode(IndexUpdateMode.BEFORE);
			try {
				QueryEnumerator rows = query.run();

				results = new ArrayList<>(rows.getCount());
				while(rows.hasNext()) {
					results.add(UUID.fromString((String) rows.next().getValue()));
				}
			} catch (CouchbaseLiteException e) {
				throw new RuntimeException("Couldn't get all items", e);
			}

Mapper
View's mapper
	@Override
	public void map(Map<String, Object> map, Emitter emitter) {
		if( map.get("name") != null
				&& entity.get("description") != null){

			emitter.emit(
				Arrays.asList(
					((String)map.get("name")).toLowerCase(),
					((String)map.get("description")).toLowerCase()),
				map.get("identity"));
		}
	}

I am having difficulty reproducing this issue. My apologies for lack of information as this is as much as I've managed to gather. Thought it best to have it documented tho.
Thanks
Keith

Hi @keith-redbite,
Thank you very much for reporting issue.
If your document size is larger than 2MB, it is Android SQLite limitation. see https://github.com/couchbase/couchbase-lite-android/issues/256 . If this is case, only solution is to maker document size smaller.
Please check maximum document size, average document size and number of documents which are stored. Also, we would like to know your test device model and Android version.
In case document size is smaller than 2MB, the issues root cause could be same with https://github.com/couchbase/couchbase-lite-android/issues/210 .
Current master branch code is little memory efficient during View.updateIndex(). If you have time, could you please try latest master branch version of CBL Android?
If you are using Android Studio, please specify "0.0.0-511" for CBL Android version in build.gradle file.
http://files.couchbase.com/maven2/com/couchbase/lite/couchbase-lite-android/0.0.0-511/
Or you can use CBL Android as submodule, please refer wiki page: https://github.com/couchbase/couchbase-lite-android/wiki/Add-Couchbase-Lite-to-your-project-as-a-submodule
If you are using Eclipse, currently download build is not available.
Thanks!

Closing as a duplicate of issue #310


Add data citation information

Original report on BitBucket by Taina Jääskeläinen.

Display data citation if the metadata has it?

Pending recommendations from working group


Typo: run -> runs

🔦 documentation change
Checklist

[x] documentation is changed or added

Semver Changes
patch

thanks


Epic: Heater Shaker Support in backend

As a protocol creator, I'd like to be able to exercise the OT H/S via Python Protocols (v3) and via Protocol Designer protocols (JSON schema v6).
These are the acceptance criteria outlined in QB-T163/Heater Shaker Protocol JIRA story:

Validate Python protocol with H/S can be created
Validate H/S works with other modules on deck
Validate multiple H/S can be ran in same protocol
Validate all H/S python commands can be successfully executed
Validate all controls can be accessed in modules and run tab
Validate modals pop up when starting protocol to confirm you want to stop heating and shaking
Validate H/S SVG is correct
Validate H/S SVG is in correct location according to protocol
Validate correct shaking and heating state
Validate correct current and target temperature
Validate correct current and target RPM
Validate correct module power start
Validate module alerts when hot to touch

Closing this old ZenHub epic as stale. We've moved these things to Jira.


All tests fail with an :unauthorized error code

All of my tests fail with exactly the same error:
(MatchError) no match of right hand side value: {:error, %Stripe.Error{code: :unauthorized, extra: %{card_code: :unauthorized, http_status: 401, raw_error: %{"code" => "unauthorized", "message" => "Unauthorized", "param" => nil, "type" => "unauthorized"}}, message: "Unauthorized", request_id: nil, source: :stripe, user_message: nil}}

Here's how I set up my config.exs:
config :stripity_stripe,
  api_key: System.get_env("STRIPE_TEST_SECRET_KEY"),
  api_base_url: "http://localhost:12111/v1/"

config :stripe_mock, StripeMockWeb.Endpoint, http: [port: 12111], server: true

Is there something that I may be doing wrong?

I figured out I forget to source my env...how embarassing


Routeblind hold invoice

Change Description
Description of change / link to associated issue.
Steps to Test
Steps for reviewers to follow to test the change.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[ ] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[ ] Commits follow the Ideal Git Commit Structure.
[ ] Any new logging statements use an appropriate subsystem and logging level.
[ ] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[ ] There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our Contribution Guidelines for further guidance.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

53 of 141 (37.59%)  changed or added relevant lines in 10 files are covered.
23065 unchanged lines in 394 files lost coverage.
Overall coverage decreased (-8.5%) to 50.268%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

routing/blindedpath/blinded_path.go
3
5
60.0%

routing/router.go
3
7
42.86%

lnrpc/invoicesrpc/invoices_server.go
12
19
63.16%

lnrpc/invoicesrpc/invoices.pb.go
0
10
0.0%

rpcserver.go
17
82
20.73%

Files with Coverage Reduction
New Missed Lines
%

graph/errors.go
1
94.74%

lnwire/typed_lease_expiry.go
2
78.95%

lnwire/typed_fee.go
2
66.67%

channeldb/forwarding_policy.go
2
85.14%

lnwallet/musig_session.go
2
79.29%

server.go
2
64.0%

record/hop.go
2
93.33%

lnwire/short_channel_id.go
2
89.74%

netann/sign.go
2
70.0%

contractcourt/htlc_timeout_resolver.go
2
88.87%

Totals

Change from base Build<PHONE_NUMBER>0:
-8.5%

Covered Lines:
96346

Relevant Lines:
191663

💛  - Coveralls


Governance FAQs - new topic CDS-75807

Harness Developer Pull Request
https://harness.atlassian.net/browse/CDS-75807

Preview link Policy as Code FAQs

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


When selected, feedback thumb is filled VS outlined otherwise

When selected, feedback thumb is filled VS outlined otherwise

I think I would keep the -1 hand next to it when selected

I would also have it filled for negative feedback

It is filled for negative feedback; the screenshot shows a hover (stronger violet than before)

My mouse doesn't show on screenshots (Ubuntu <3)

gotcha :+1: I would likely keep the two hands when selected to avoid the change of "structure". But not urgent of course and I guess not introduced by this PR.

I agree and am doing it right now. I merged when I saw approved, and saw your comment appear right after

👌


🐛

What were you trying to do?
I am trying to integrate vision camera in my react native app. The step tried

installed "npm i react-native-vision-camera"
change the sdk changes to support vision camera
buildToolsVersion = "30.0.2"
minSdkVersion = 26
compileSdkVersion = 31
targetSdkVersion = 31
ndkVersion = "21.4.7075529"
run the app in command to $  react-native run-android
Build succeeded but app lunch and closed automatically.
may I know anything i missing from the configuration.

Reproduceable Code
No response
What happened instead?
The app get crashed and closed automatically but build success.
Relevant log output
No response
Device
android simulator  AOSP on IA Emulator
VisionCamera Version
"react-native-vision-camera": "^2.13.3"
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Hi!
I cannot help you with your issue. You did not share any logs with me.

which logs you need. from where i need to take it from?

https://mrousavy.com/react-native-vision-camera/docs/guides/troubleshooting
Under Android, see point 6. I need adb logs

I have tried to install react-native-vision-camera in RN 0.7x but ran into build issues. My question is: can react-native-vision-camera be used with RN 0.7x?


What's the shape of the result

Reported by ansley b manke on 18 Oct 2012 00:26 UTC
This query on the Users List,
http://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2012/msg00569.html
wonders what would it take to "shape" of an expression without loading the data and making computations. Some discussion here. This would be nice to do sometime but at low priority.
Note that the task in ticket #1976 puts in place at least a nice way to get out of an over-long data read.
Ferret includes a tremendous amount of code -- the entire "get_grid" and context processing support phases of evaluation -- that exist for the express purpose of figuring out the size and shape of a result without ever loading data.  In the example session pasted below, the MODE DIAG output shows that no data are ever read, yet the size and shape of the result can be seen.  The final command, shade sst" illustrates a case where the entire domain of data is read, only to result in an error condition over shape.  Ryo's right.  This is not optimal behavior.
The trouble lies in the exceptional cases (compressing transformations like @AVE btw, are handled fine).  There are flaws that keep the pre-determining of size/shape from working as it should in all cases -- a collection of specific conditions that force Ferret to read data in order to know the shape of a result.  I'm feeling pretty fuzzy on a lot of those details at this point (it's been a while), but some of the specific things that inhibit pre-determining the size of a result include
reading from ASCII files, where the file must be read to know how long it really is
grid-changing functions where the output grid definition depend upon the input *data* values
some cases of limits being implicit instead of explicit ...

Bottom line:  Ferret does have the inner machinery capable of doing exactly what Ryo has requested most of the time.   And it would be really a nice addition to do so -- he's right.  Its just that the exceptional cases (which I do not remember so well), can turn into bad behaviors -- sometimes making Ferret do a big data access task twice, sometimes leading to an error condition.
It would be an interesting prospect to add the check that Ryo speaks of in some kind of conditional, experimental manner:
an internal list of commands that have shape restrictions -- e.g. PLOT required 1D args, SHADE requires 2D, ...
some new code that would be invoked by those commands to pre-screen the data arguments for correct shape (without reading any data) and quickly trigger error conditions if so

... but probably also needing these to cope with the exceptional cases ...

a MODE CHECK_SHAPE (so you can turn off the attempts at shape pre-screening)
qualifier /OVERRIDE_SHAPE to bypass this where it leads to trouble (YUK! UGLY)

However, I don't think this issue rises high enough in the priority list to actually do the work.  It only saves users from cases of their own carelessness -- it doesn't add new power.  But there are hundreds of times I would have enjoyed the feature myself!  if it were reliable, that is ...
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1977

Comment by andrew.wittenberg on 20 Dec 2012 23:52 UTC
I too would like to see this feature for the reasons described above.  But beyond that, I'd also argue that this would add new power, since it would allow scripts to check whether their arguments have the proper shape to be processed.  Right now, we have weirdness like this:
 	NOAA/PMEL TMAP
 	FERRET v6.83 (beta)
 	Linux 2.6.32-279.5.1.el6.x86_64 64-bit - 08/22/12
 	20-Dec-12 18:44

yes? let a = {1,2,3}+ysequence({4,5,6})
yes? let b = a[x=@ave]
yes? say `a,r=shape`
 !-> MESSAGE/CONTINUE XY
XY

which is clearly wrong, the answer should really be "Y".  Well, maybe there's a "compute-domain shape" XY and a "result shape" Y, but we really need a way to get at the latter.  Right now I often have scripts dump the darn variable to a NetCDF file and read it back in, just to get its shape - yuck!
So I'm bumping up the priority on this...

EDIT: OOPS! -- You're right Steve that I goofed on my example.  (If I had pasted "b" in there instead of "a" I would've seen that my example didn't demonstrate the issue at all -- sorry for confusing everyone!)  Thanks Ansley for correctly highlighting the real issue, which must have to do with source data that needs to be LOADed.

Comment by steven.c.hankin on 21 Dec 2012 00:08 UTC
Puzzled by this.  In the above the shape of "a" is XY, isn't it?  It is variable "b", where the X axis has been compressed out and for that we get
yes?  yes? say `b,r=shape`
 !-> MESSAGE/CONTINUE Y

Having said this, I would not be surprised to find examples (pyramids of definitions), where the true shape was getting lost.

Comment by ansley.b.manke on 21 Dec 2012 00:15 UTC
The example in comment 1 doesn't capture the issue.  for those variables the data is loaded and then the shape is returned.  But,
yes? use coads_climatology
yes? say sst,return=shape
!-> MESSAGE/CONTINUE XYT
doesn't load the data. It does a "getgrid" operation and returns the correct answer. But the shape of this variable is really XY and Ferret doesn't go far enough evaluating the grid to get that:
yes? say sst[L=@max],return=shape
!-> MESSAGE/CONTINUE XYT

Comment by andrew.wittenberg on 26 Dec 2012 22:34 UTC
Specifically, this issue applies to transformations with indefinite limits.  See ticket #1801.

Comment by steven.c.hankin on 6 Jan 2013 17:57 UTC
This ticket articulated 3 cases where it would be desirable to avoid reading the data in order to determine the shape and size of the result:

reading from ASCII files, where the file must be read to know how long it really is
grid-changing functions where the output grid definition depend upon the input data values
some cases of limits being implicit instead of explicit ...
The first two cases require reading the data by definition.  There is no general route around them.  The only articulated example of the third case has now been fixed in ticket #1801.


Container order change clashes with readiness probes

The PR to make Dapr the first container in the pod causes a regression in cases where apps have readiness probes and has Dapr waiting for the app to respond on a given port.
This causes Dapr to detect the app is running only when the failure threshold of the user app is met.

Closed via https://github.com/dapr/dapr/pull/3300.


Set random seed consistently in test_network

In order to put guaranteed bounds on the differences between reference and nineml versions of the networks in test_network the same seed must be used each time.

This has been implemented by PR #67


Consecutive updates

Use local state object instead of state to trigger actions

you are maintaing another copy of the state (like virtual state). Does that have any memory implications?

Yes this is the idea just the idea not proof tested

@elisherer I'm not sure how to implement your test


Deletes happy-npm-build

Internal

Codecov Report

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

@@           Coverage Diff           @@
##           master      #56   +/-   ##
=======================================
  Coverage   66.74%   66.74%
=======================================
  Files          47       47
  Lines        2210     2210
  Branches      466      466
=======================================
  Hits         1475     1475
  Misses        659      659
  Partials       76       76

Continue to review full report at Codecov.

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


Crop box fixed

Hello,
I use your library and I have one problematic and I search help.
I wish to have a fixed crop with already the same width. When I zoom my cropbox must be stay with the same width (maybe like http://scottcheng.github.io/cropit/). In fact, this is disturbing when I zoom the width change and when I change the crop box width change too.
How have the good parameters to have the behaviors ?
Sorry for my english, I hope you understand my need.
Thanks

Please read the documentation to find a solution or ask help on StackOverflow.


Down 500 INTERNAL_SERVER_ERROR

Hi,
I cannot access any site that is on docs.page (including https://docs.page itself). Same error for all my colleagues.
Also trying sites with custom domains, the error is the same (https://docs.buildwiththeta.com).
Code: INTERNAL_FUNCTION_INVOCATION_FAILED

Also can confirm the same issue here with docs at docs.pieces.app

I believe this is due to the ongoing AWS incident happening at the moment.
Will double check

Thanks @Ehesp just wanted to make sure your team was aware just keep us posted! :)


Update auth, dynamodb, s3, sqs to 2.17.255

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.17.193 to 2.17.255.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #946.


[HUDI-7797] Use HoodieIOFactory to return pluggable FileFormatUtils implementation

Change Logs
PR targeting master: https://github.com/apache/hudi/pull/11302
This PR targets at branch-0.x with the same set of changes.
This PR adds the flexibility to plug in custom FileFormatUtils implementation based on the HoodieStorage instance.  To realize this, two new APIs #getFileFormatUtils are added to the HoodieIOFactory so that the IO factory implementation class can customize the FileFormatUtils implementation to return.  The hardcoded logic in FileFormatUtils#getInstance for Hadoop-based implementation is moved to HoodieHadoopIOFactory class.  New tests are added in TestHoodieHadoopIOFactory.
Impact
Allows pluggable FileFormatUtils implementation
Risk level
none
Documentation Update
none
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Azure CI is green.


Update redirects in Readme

Created with https://github.com/dkhamsing/frankenstein

Thanks

:tada:


Error updating subscription

I am running into an error trying to resume a subscription via the api.
The error that I'm receiving from Lemon Squeezy is this:
{
  "jsonapi" : {
    "version" : "1.0"
  },
  "errors" : [
    {
      "status" : "400",
      "detail" : "The member data is required.",
      "source" : {
        "pointer" : "\/"
      },
      "title" : "Non-Compliant JSON:API Document"
    }
  ]
}

I don't see any Data parameter that can be set.
This is how I am attempting to cancel the subscription.
	ctx := context.Background()
	params := &lemonsqueezy.SubscriptionUpdateParams{
		Type:       "subscriptions",
		ID:         "<MY ID HERE>",
		Cancelled:  false,
	}
	apiResponseSubscription, response, err = l.Client.Subscriptions.Update(ctx, params)

It's very likely that I'm just doing something stupid.  Is this an actual bug, or an ID10T user error?

Fixed by #10


Chart labels not visible in dark mode

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to https://spendwise-seven.vercel.app/
Log in to your account (or create one if not already)
Add some expense transactions (if not already)
Switch to dark mode (if currently in light mode)
See error

Expected behaviour
The labels should be visible
Screenshots

Chnage the colour of the labels to '#B6CEFC80' when in dark mode

Assign me this issue for KWOC23


Work staggering email job choosing notice

Email already exists. Make a way to preview it and send it out.
Originally created by Tom Smyth at 2019-02-17 22:34, migrated from redmine-#9410

Duplicate of #131 and #132.


Improve pagination when viewing a list of books

On some readers, when viewing a list of books, there is no option to return to the previous page, or go to the first or last page.

the commit 11d87cd51c545ebfc6390d981b93df5d316e3793 added first, last and previous links to search and genres feeds


tag v0.12.2

Purpose
tag bi-weekly release

ugh not sure what I did wrong but I'll restart this PR


Billboard clamps too high to terrain?

Open the KML Sandcastle example:
http://localhost:8080/Apps/Sandcastle/index.html?src=KML.html&label=All

Turn on AGI World Terrain, then zoom to "Nevada Test Site Area 26."  The label is floating way above terrain.  Shouldn't it clamp to the highest resolution loaded?

I can't reproduce this in master.  @pjcozzi can you confirm and close?

I just tried in master and believe I still see the issue:

Pretty sure I just forgot to turn terrain on when I tested this. whoops.  The problem is actually pretty bad and happens by jumping to most billboards.  Some end up above the ground, some under the ground.
I've also had some problems with disappearing labels (I think they are improperly being placed under ground like the billboards:

It's possible this is a different issue, but unlikely.

I've also had some problems with disappearing labels (I think they are improperly being placed under ground like the billboards:
...

Is this #2694?

No, they are two different issues.  This issue is a nasty race condition in terrain clamping which is causing each letter to be placed in the geographically incorrect position instead of on the terrain itself.  #2694 is a draw order issue and requires us treat labels as special so they always get drawn above terrain if their origin is visible (or something similar).

The problem seems to be picking upsampled terrain. A quick check by disabling upsampling looks like it fixes the problem, but requires more testing.


fix signature verification link

This PR does 2 things:

remove an unused class that is in conflict with another one in the main project
fix the URL generated to verify a signature

This change is

The issue here is that this is part of the rendering process, i.e. we need to generate this link within the rendering process.
So for now, this is the solution we have found. We can def. create an issue to extract that (or actually just put a pin on it for when we're going to work more on the signature process) so we don't have this issue anymore.
I agree this is not an ideal architecture but this is what works right now


image-based: Create template repository for image base gadgets

We should create a template repository for creating a new gadget. The repository should include:

A sample gadget source code (could be taken from https://github.com/inspektor-gadget/inspektor-gadget/blob/v0.24.0/docs/devel/hello-world-gadget.md)
Configuration to publish the gadget (similar to existing logic in our github actions)
Tests (once we sort https://github.com/inspektor-gadget/inspektor-gadget/issues/2046 out)
Readme (describing how to use the gadget)

/cc @alban

https://github.com/inspektor-gadget/gadget-template


Re-enable OSX, switch to our fork of D-YAML and fix the bug

https://travis-ci.com/bpfkorea/agora/jobs/221461723
Well that didn't help.

Yeah I need to do some Python trickery. Will come back to it soon.

Fixed. Upstream PR as https://github.com/dlang-community/D-YAML/pull/247 but for the moment we need the CI back.

💚


Can json-schema generate draft 4?

Is there a way to define what JSON schema draft you generate?  The site generates draft7. I am using a Java API that only supports draft 4.  In my case, I was able to simply change the $schema to the following and it worked though I am not sure I would always be that lucky.
"$schema": "http://json-schema.org/draft-04/schema#",

Website does not work from me after deleting cookies... did something change after Nov 1st.
let me see if I can make this work.

The new version is now generally available on https://www.jsonschema.net
Are you experiencing the same problem there too?

Please use the settings panel


Documented command "optimum-cli onnxruntime" doesn't exist?

System Info
Python 3.9, Ubuntu 20.04, Miniconda.  CUDA GPU available

Packages installed (the important stuff):

onnx==1.13.0
onnxruntime==1.13.1
optimum==1.6.3
tokenizers==0.13.2
torch==1.13.1
transformers==4.26.0
nvidia-cublas-cu11==<IP_ADDRESS>
nvidia-cuda-nvrtc-cu11==11.7.99
nvidia-cuda-runtime-cu11==11.7.99
nvidia-cudnn-cu11==<IP_ADDRESS>

Who can help?
@lewtun, @michaelbenayoun
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
I have an existing ONNX model, which I am trying to optimize with different scenarios.  When attempting to follow the documented instructions for optimizing an existing ONNX model, the command does not exist.  I am using the instructions from this page: https://huggingface.co/docs/optimum/onnxruntime/usage_guides/optimization
NOTE: I am using zsh, which requires escaping brackets
pip install optimum
pip install optimum\[onnxruntime\]
pip install optimum\[exporters\]

Command execution:
optimum-cli onnxruntime optimize --onnx_model ../output/sentence-transformers/all-MiniLM-L6-v2/model.onnx -o output/sentence-transformers/all-MiniLM-L6-v2/model-optimized.onnx -04

Result:
usage: optimum-cli <command> [<args>]
Optimum CLI tool: error: invalid choice: 'onnxruntime' (choose from 'export', 'env')

Expected behavior
I'd expect for the command to exist, or to understand which command to use for experimenting with different ONNX optimizations.  I tried using the optimum-cli export onnx command, but that does not have options for optimization types.
I'd be happy to start from a torch model instead of using an existing ONNX model - but I'd also like to be able to specify different optimizations (-01 | -02 | -03 | -04)
Thanks!

Awesome thanks!!!!


useContractFunction state.status is always PendingSignature

When we use walletconnect/web3-provider, as provider to send a transaction with useContractFunction the status of the transaction is always PendingSignature even if user accepts / rejects the transaction.
Expected behavior is to either change the state to reflect the same or throw an Error to catch.
Current behavior status is PendingSignature

What's the version of useDapp you have installed and the version of walletconnect, so we have a possibility of debugging this?

"@usedapp/core": "^1.0.2",
"@walletconnect/web3-provider": "^1.7.8",

I did some testing and found that that issue is not with useDapp or WalletConnect, but with Metamask Mobile App.
Closing the issue here.

#803


SSS Work

Do I understand correctly that the directional dipole model now only accepts presets or manually-entered sigma values? But that the other dipole models continue to accept reflectance and dmfp?


Resolves: Add native GitHub security and versioning dependency alerts

add dependabot.yml which automatically enables Dependabot's dependency versioning scanner and dependency update PRs bot by declaring dependency ecosystems and sources in the project. For dependency security vulnerabilities scanner and vulnerable dependency update PRs bot, enable "Dependabot alerts" and "Dependabot security updates"

use the target-branch attribute, if you would like to run Dependabot's scan against a branch other than your default branch (for example if you have a separate development branch)

should you decide that certain people on your team should take care of the PRs that Dependabot creates, use the two attributes assignees and reviewers to automatically set personnel respectively.

Resolves #849

@aleks-ivanov, Thank you for all your work around this; we'll review it and merge. Please let us now when it's done.

@Haplois our pleasure entirely!
I would say it is completed now, with the small caveat that we are not 100% sure if the authentication to the private registry requires anything else. We assumed from the URL that it is an Azure auth with a token only.
If it turns out a usr/pwd combination is needed, replace the token attribute with:
username: my-usr
password: ${{ secrets.PRIVATE_REG_PWD }}

Please don't hesitate to let us know if you have any question about the contribution. 🙂

@aleks-ivanov thank you for this PR, after careful consideration we decided that this is not suitable to our needs, mainly because we have internal tools which tracks this across our organization.
Tools like dependabot might break our compatibility with our other repositories


The additional cluster_admins roles should use exact name

By using the regex from, in the case that the role name matches two different roles, the first one is selected, creating issues.
https://github.com/tx-pts-dai/terraform-aws-kubernetes-platform/blob/main/main.tf#L81
tf state show 'module.k8s_platform.data.aws_iam_roles.iam_cluster_admins["cicd"]'
# module.k8s_platform.data.aws_iam_roles.iam_cluster_admins["cicd"]:
data "aws_iam_roles" "iam_cluster_admins" {
    arns       = [
        "arn:aws:iam::911453050078:role/cci-txptsdai-cicd-iac",
        "arn:aws:iam::911453050078:role/cicd-iac",
    ]
    id         = "eu-central-1"
    name_regex = "cicd-iac"
    names      = [
        "cci-txptsdai-cicd-iac",
        "cicd-iac",
    ]
}

fixed by #38


Decide whether to version codegen/macros separately from serde

We can keep them in the same repository, but do we need to continue tying their version numbers together? It often happens that we change codegen/macros and cut a release in which serde hasn't changed at all, or vice versa.

We can reopen if anyone has a strong opinion. For now I think serde and serde_codegen make breaking changes infrequently enough that tying the versions is not a problem.

Reopening to discuss the possibility of releasing serde_codegen 0.9 while staying with serde 0.8. I need to fix the cargo version issue (#543) in order to make progress on serde_derive (#548). This would be a breaking change for serde_codegen but there is no real motivation for breaking core serde right now - the enum API I guess (#523) but that can wait.
Another option is to go all-in on Macros 1.1. Basically take all the code currently in serde_codegen and fold it into serde_derive, then delete serde_codegen and serde_macros from the codebase and never release another version of them. In the event that someone demands a codegen bug fixed on stable, we can fix it on an old 0.8 branch.
@erickt @oli-obk

Never mind, I think I can work around it for now in serde_codegen as long as I fix it in syntex/quasi/aster, which is easier.


terraform file for gitlab setup

[X] I read CONTRIBUTING.md

Notes
Since I am probably not the only one prefering Terraforms declarative style over imperative commands like those gcloud uses, I wrote this short Terraform script.
I also added a short note in the gitlab section of the README, that all steps can be reproduced using the Terraform script.

Thank you 👍


Properly support marks

At the moment, marks are just a Map<String, Object>

Currently, we don't have a use-case for marks in the Java agent.


Output files and supervisor deployment changes

NOTE: These changes depend on https://github.com/LiquidAI-project/wasmiot-modules/pull/15
I successfully tested the changes in the following ways:

Simple fibo
subtract -> fibo on a single device
take_image_predefined_paths using host webcam
infer_predefined_paths
subtract -> fibo with the functions running on two separate devices
take_image_predefined_paths -> infer_predefined_paths with the functions running on two separate devices


Fix for "Javascript error when DataTable is empty"

Override renderTableBody to draw a blank tbody without empty message to prevent conflict with datatables rendering.

@adhayward Thanks!


83 process clippy warnings

Resolves clippy warnings based on suggested fixes for all pallets.
A Clippy config file needed to be added to tweak the default settings to allow:

functions with many arguments
complex type defintions

These suggested fixes could be tackled in the future as a separate issue, but I didnt want to change too much with this PR.

I'll create a PR to the upstream repository for the suggested fixes to the substrate-node-template


Hadoop index task stopped working with 0.10.1-rc1

With the previous version of Druid everything worked fine. But after the upgrade to 0.10.1-rc1 we are getting:
2017-07-12T10:14:01,315 INFO [task-runner-0-priority-0] org.apache.hadoop.mapreduce.Job - Task Id : attempt_1499852511486_0003_m_000000_0, Status : FAILED
Error: com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) null returned by binding at io.druid.guice.JsonConfigProvider.bind(JsonConfigProvider.java:132) (via modules: com.google.inject.util.Modules$OverrideModule -> io.druid.storage.google.GoogleStorageDruidModule)
 but the 2nd parameter of io.druid.storage.google.GoogleDataSegmentPusher.<init>(GoogleDataSegmentPusher.java:56) is not @Nullable
  while locating io.druid.storage.google.GoogleAccountConfig
    for the 2nd parameter of io.druid.storage.google.GoogleDataSegmentPusher.<init>(GoogleDataSegmentPusher.java:56)
  while locating io.druid.storage.google.GoogleDataSegmentPusher
  at io.druid.storage.google.GoogleStorageDruidModule.configure(GoogleStorageDruidModule.java:94) (via modules: com.google.inject.util.Modules$OverrideModule -> io.druid.storage.google.GoogleStorageDruidModule)
  while locating io.druid.segment.loading.DataSegmentPusher annotated with @com.google.inject.multibindings.Element(setName=,uniqueId=47, type=MAPBINDER, keyType=java.lang.String)
  at io.druid.guice.PolyBind.createChoice(PolyBind.java:67) (via modules: com.google.inject.util.Modules$OverrideModule -> com.google.inject.util.Modules$OverrideModule -> io.druid.guice.LocalDataStorageDruidModule)
  while locating io.druid.segment.loading.DataSegmentPusher

That seems to be that somehow the druid.google.* aren't propagated to the hadoop task like they were before?

Anyone have any idea what might cause this? I can try all kinds of things to fix it but I'm kinda lost right now.

@erikdubbelboer after https://github.com/druid-io/druid/pull/4116 user can now propagate selected properties to hadoop workers.
Not sure how this was working for you before ?

@b-slim It seems like this is broken. When I settuningConfig.allowedHadoopPrefix to [ "druid.storage.", "druid.javascript.", "druid.google." ] I still get:
...
2017-07-13T08:07:10,806 INFO [main] io.druid.indexing.worker.executor.ExecutorLifecycle - Running with task: {
...
      "allowedHadoopPrefix" : [ "druid.storage.", "druid.javascript.", "druid.google." ]
...
2017-07-13T08:07:16,387 INFO [task-runner-0-priority-0] io.druid.indexer.HadoopDruidIndexerConfig - Running with config:
...
      "allowedHadoopPrefix" : [ "druid.storage.", "druid.javascript." ]
...

So it doesn't seem to propagate to the actual job.

@b-slim Is it because these methods pass null instead of the actual value?: https://github.com/druid-io/druid/blob/3399d1a488896d675e54c1de90a596daea1c045f/indexing-hadoop/src/main/java/io/druid/indexer/HadoopTuningConfig.java#L272-L322

This has fixed the issue for me:
diff --git a/indexing-hadoop/src/main/java/io/druid/indexer/HadoopTuningConfig.java b/indexing-hadoop/src/main/java/io/druid/indexer/HadoopTuningConfig.java
index e64c0e7..b131a5e 100644
--- a/indexing-hadoop/src/main/java/io/druid/indexer/HadoopTuningConfig.java
+++ b/indexing-hadoop/src/main/java/io/druid/indexer/HadoopTuningConfig.java
@@ -267,7 +267,7 @@ public class HadoopTuningConfig implements TuningConfig
         numBackgroundPersistThreads,
         forceExtendableShardSpecs,
         useExplicitVersion,
-        null
+        allowedHadoopPrefix
     );
   }

@@ -292,7 +292,7 @@ public class HadoopTuningConfig implements TuningConfig
         numBackgroundPersistThreads,
         forceExtendableShardSpecs,
         useExplicitVersion,
-        null
+        allowedHadoopPrefix
     );
   }

@@ -317,7 +317,7 @@ public class HadoopTuningConfig implements TuningConfig
         numBackgroundPersistThreads,
         forceExtendableShardSpecs,
         useExplicitVersion,
-        null
+        allowedHadoopPrefix
     );
   }

You want me to make a pull request?

yeah sure will review that, @erikdubbelboer thanks.

How were the properties passed down before? I thought that pre 0.10.1, properties were generally not passed down to the hadoop cluster. So it seems weird that now they'd need to be.
Or is the difference that now in 0.10.1, the druid.storage.type property is passed down, which means now druid.google. needs to be as well if you're using the google extension? If that's the case, I think we should either add druid.google. to the default list, or give the deep storage extensions some way to say what properties they need passed down; otherwise upgrading will be too much of a pain for people using the extension.

@gianm i think you are right, now that we push down the storage properties, guice tries to bind things up, hence the issues. Am not sure what is the best fix but seems like we need to push all the properties of the selected storage module at least. Any way i will send a first PR to fix the null issue (guess @erikdubbelboer is in a different timezone) and then will focus on how to solve this. @gianm should this be part of 0.10.1 ?

@b-slim I think we should at least have something in the release notes explaining the situation. Pushing down the storage properties would be even better. Perhaps we could do this by adding a getPropertyPrefixForHadoop to DataSegmentPusher and then automatically adding that prefix to allowedHadoopPrefix for whatever the deep storage is.

@b-slim
Are you planning on working on a fix beyond #4541 for 0.10.1?
If so, let's keep this is 0.10.1 and we can bring the fix into rc2.
If not, let's move this issue to 0.11.0, and I'll mention the storage extension property push in the 0.10.1 release notes.

i don't want to block the RC for this issue thought, i will get to work on it maybe next week.

I'm trying to post at the druid-development list but my messages keep on being automatically deleted (even without any links).
I don't think this only affects the Google Storage extension. I think it affects all storage extensions as all of them use different prefixes for their properties and all of them inject their config into their SegmentPushers?

I don't think this only affects the Google Storage extension. I think it affects all storage extensions as all of them use different prefixes for their properties and all of them inject their config into their SegmentPushers?

Most of them put their properties under druid.storage, so they aren't affected since the default list does include those. It looks like Google Storage and Azure are the two that don't.

I'm trying to post at the druid-development list but my messages keep on being automatically deleted (even without any links).

 I marked them as not-spam and whitelisted your email address.

Looks like the old messages are deleted though, so you might have to re-post them.

I guess if you want to store your segments in S3 you also need druid.s3: https://github.com/druid-io/druid/blob/60cdf946778d0624db6ddce0366e5fdb131437b2/extensions-core/s3-extensions/src/main/java/io/druid/storage/s3/S3StorageDruidModule.java#L77

I think S3 should be ok, since Hadoop's S3 FileSystem is used for connection from hadoop -> s3, not Druid's S3 client. So even though Druid's S3 client won't be properly instantiated, it wouldn't matter.
Has anyone tried this with 0.10.1-rc1 to confirm? I think we have but I'm not totally sure.

@gianm We did run some hadoop tests against 0.10.1 before rc1 was released for this PR: https://github.com/druid-io/druid/pull/4116, but the deep storage was HDFS in those tests.

I just ran a batch ingestion task with 0.10.1-rc1 with EMR, using S3 as deep storage, the task worked

@erikdubbelboer could you try #4562 to see if that works for you, without having to specify allowedHadoopPrefix in the task?

@gianm I looks like #4562 can't be applied to the 0.10.1 branch we are running. I tried upgrading only our middlemanager node to master but this just resulted in lots of java.io.IOException: Failed to locate service uri exceptions when starting a task. Do you have any suggestion on how to test this without having to upgrade our whole cluster to master?

@erikdubbelboer please try https://github.com/druid-io/druid/pull/4567 which is a backport of that to 0.10.1.
Although, exceptions when middleManagers are upgraded and the rest of the cluster is not, are concerning since we do want to support upgrading them first as part of a rolling update. Could you please paste the full error message & stack traces you got when you saw those errors? Might be something we need to fix.

@gianm with #4567 everything works fine. There is only one exception that repeats a couple of times at the start but it doesn't seem to affect anything:
2017-07-20 09:23:56,956 task-runner-0-priority-0 WARN JNDI lookup class is not available because this JRE does not support JNDI. JNDI string lookups will not be available, continuing configuration. java.lang.ClassCastException: Cannot cast org.apache.logging.log4j.core.lookup.JndiLookup to org.apache.logging.log4j.core.lookup.StrLookup
	at java.lang.Class.cast(Class.java:3369)
	at org.apache.logging.log4j.util.LoaderUtil.newCheckedInstanceOf(LoaderUtil.java:167)
	at org.apache.logging.log4j.core.util.Loader.newCheckedInstanceOf(Loader.java:301)
	at org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:94)
	at org.apache.logging.log4j.core.config.AbstractConfiguration.<init>(AbstractConfiguration.java:111)
	at org.apache.logging.log4j.core.config.DefaultConfiguration.<init>(DefaultConfiguration.java:48)
	at org.apache.logging.log4j.core.LoggerContext.<init>(LoggerContext.java:75)
	at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.createContext(ClassLoaderContextSelector.java:171)
	at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:145)
	at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:70)
	at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:57)
	at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:140)
	at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41)
	at org.apache.logging.log4j.LogManager.getContext(LogManager.java:182)
	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
	at org.apache.logging.log4j.jul.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:34)
	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
	at org.apache.logging.log4j.jul.LogManager.getLogger(LogManager.java:89)
	at java.util.logging.LogManager.demandLogger(LogManager.java:551)
	at java.util.logging.Logger.demandLogger(Logger.java:455)
	at java.util.logging.Logger.getLogger(Logger.java:502)
	at com.google.inject.internal.util.Stopwatch.<clinit>(Stopwatch.java:27)
	at com.google.inject.internal.InternalInjectorCreator.<init>(InternalInjectorCreator.java:61)
	at com.google.inject.Guice.createInjector(Guice.java:96)
	at com.google.inject.Guice.createInjector(Guice.java:73)
	at io.druid.guice.GuiceInjectors.makeStartupInjector(GuiceInjectors.java:60)
	at io.druid.indexer.HadoopDruidIndexerConfig.<clinit>(HadoopDruidIndexerConfig.java:105)
	at io.druid.indexing.common.task.HadoopIndexTask$HadoopDetermineConfigInnerProcessing.runTask(HadoopIndexTask.java:293)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at io.druid.indexing.common.task.HadoopTask.invokeForeignLoader(HadoopTask.java:215)
	at io.druid.indexing.common.task.HadoopIndexTask.run(HadoopIndexTask.java:177)
	at io.druid.indexing.overlord.ThreadPoolTaskRunner$ThreadPoolTaskRunnerCallable.call(ThreadPoolTaskRunner.java:436)
	at io.druid.indexing.overlord.ThreadPoolTaskRunner$ThreadPoolTaskRunnerCallable.call(ThreadPoolTaskRunner.java:408)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

The exception I'm seeing over and over again when upgrading only the middlemanager to master is:
2017-07-20T03:44:51,532 WARN [main] io.druid.indexing.common.actions.RemoteTaskActionClient - Exception submitting action for task[kill_ssps_2000-01-01T00:00:00.000Z_3000-01-01T00:00:00.000Z_2017-07-20T02:50:01.978Z]
java.io.IOException: Failed to locate service uri
	at io.druid.indexing.common.actions.RemoteTaskActionClient.submit(RemoteTaskActionClient.java:94) [druid-indexing-service-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.indexing.common.task.AbstractFixedIntervalTask.isReady(AbstractFixedIntervalTask.java:92) [druid-indexing-service-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.indexing.worker.executor.ExecutorLifecycle.start(ExecutorLifecycle.java:169) [druid-indexing-service-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_131]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_131]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131]
	at io.druid.java.util.common.lifecycle.Lifecycle$AnnotationBasedHandler.start(Lifecycle.java:364) [java-util-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.java.util.common.lifecycle.Lifecycle.start(Lifecycle.java:263) [java-util-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.guice.LifecycleModule$2.start(LifecycleModule.java:156) [druid-api-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.cli.GuiceRunnable.initLifecycle(GuiceRunnable.java:101) [druid-services-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.cli.CliPeon.run(CliPeon.java:283) [druid-services-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.cli.Main.main(Main.java:108) [druid-services-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
Caused by: java.lang.NullPointerException
	at io.druid.curator.discovery.ServerDiscoverySelector$1.apply(ServerDiscoverySelector.java:60) ~[druid-server-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.curator.discovery.ServerDiscoverySelector$1.apply(ServerDiscoverySelector.java:52) ~[druid-server-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.curator.discovery.ServerDiscoverySelector.pick(ServerDiscoverySelector.java:108) ~[druid-server-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.indexing.common.actions.RemoteTaskActionClient.getServiceInstance(RemoteTaskActionClient.java:164) ~[druid-indexing-service-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	at io.druid.indexing.common.actions.RemoteTaskActionClient.submit(RemoteTaskActionClient.java:89) ~[druid-indexing-service-0.11.0-SNAPSHOT.jar:0.11.0-SNAPSHOT]
	... 12 more
2017-07-20T03:44:51,539 INFO [main] io.druid.indexing.common.actions.RemoteTaskActionClient - Will try again in [PT4.686S].

@erikdubbelboer
The JNDI exception at startup can be ignored.
For the second exception, based on the line numbers in ServerDiscoverySelector, it looks like you've pulled in some post 0.10.1 changes (i.e., in master but not in 0.10.1-rc1 or rc2), specifically this PR that adds TLS support: https://github.com/druid-io/druid/pull/4270
I'm guessing what's happening is that the service announcement changes need to set the TLS-enabled port property are missing because only the middleManager got the upgrade, but this newer code running the middle manager expects that property to be non-null and gets an NPE here.
Can you try basing your custom branch on 0.10.1-rc2?

I'm guessing what's happening is that the service announcement changes that set the TLS-enabled port property are missing because only the middleManager got the upgrade, but this newer code running on the middleManager expects that property to be non-null and gets an NPE here.

Is that what happens when #4270 is rolled out to MMs but not overlords? If so, that makes it impossible to do a proper rolling update, and we should address it before 0.11.0.


Router is not loading correctly

Hi! I just updated everything to the new version of Storybook and this package and something weird is happening:

If I refresh the page the vueRouter() decorator is not loaded and router components and useRouter composable etc. don't exist.
If I navigate to another story everything works fine, then If I refresh the page I have the same errors again

Errors:

[Vue warn]: injection "Symbol(router)" not found.
After useRoute when I do for instance route.beforeEach: runtime.js:4 TypeError: Cannot read properties of undefined (reading 'beforeEach')
[Vue warn]: Failed to resolve component: router-link and more error related

"storybook": "^7.3.2",
"storybook-vue3-router": "^3.0.0",

Example of a story:
import { vueRouter } from 'storybook-vue3-router'
import { action } from '@storybook/addon-actions'
import { LINKS, CUSTOM_ROUTES } from '../mockdata'
import MainMenu from './MainMenu.vue'

export default {
  title: 'Navigation/MainMenu',
  component: MainMenu
}

export const Default = () => ({
  components: { MainMenu },
  data: () => ({
    ...LINKS
  }),
  methods: {
    handleAction (event) {
      action('Event:')(event)
    }
  },
  template: `

      <MainMenu
        :logoLink="logoLink"
        :links="links"
        @click="handleAction('click')"
      />

        <RouterView />

  `
})

Default.decorators = [
  vueRouter(CUSTOM_ROUTES)
]

UPDATE:
With Storybook version 7.0.25 works fine. After ^7.1.0 stop working well..

Hi @jamesalways !
I had the same problem that you are mentioning. I discovered that this happens because setup callback will not be called when story is already being rendered. Now that I understand Storybook better I created a decorator:
import { Decorator, setup } from '@storybook/vue3'
import { App } from 'vue'
import { RouterOptions, createRouter, createWebHashHistory } from 'vue-router'

const Home = { template: '
Home
' }
const About = { template: '
About
' }

export const routerOptions: RouterOptions = {
  history: createWebHashHistory(),
  routes: [
    { path: '/', component: Home },
    { path: '/about', component: About },
  ],
}

export default function withRouter(options?: RouterOptions): Decorator {
  let app: App

  setup((setupApp) => {
    app = setupApp
  })

  return (story) => {
    const router = createRouter({ ...routerOptions, ...options })
    app.use(router)
    return story()
  }
}

You can create a PR where you can call setup before makeDecorator.
https://github.com/NickMcBurney/storybook-vue3-router/blob/b8ecc62347368b0066ad88b28081e5b158086be7/src/withVueRouter.ts#L42
) =>
  let app: App;
  setup((setupApp) => {
    app = setupApp
  })
  makeDecorator({
    name: 'withVueRouter',
    parameterName: 'withVueRouter',

    wrapper: (storyFn: StoryFn, context: StoryContext) => {
      /* setup router var */
      let router

Hi @jamesalways !
I had the same problem that you are mentioning. I discovered that this happens because setup callback will not be called when story is already being rendered. Now that I understand Storybook better I created a decorator:
import { Decorator, setup } from '@storybook/vue3'
import { App } from 'vue'
import { RouterOptions, createRouter, createWebHashHistory } from 'vue-router'

const Home = { template: '
Home
' }
const About = { template: '
About
' }

export const routerOptions: RouterOptions = {
  history: createWebHashHistory(),
  routes: [
    { path: '/', component: Home },
    { path: '/about', component: About },
  ],
}

export default function withRouter(options?: RouterOptions): Decorator {
  let app: App

  setup((setupApp) => {
    app = setupApp
  })

  return (story) => {
    const router = createRouter({ ...routerOptions, ...options })
    app.use(router)
    return story()
  }
}

You can create a PR where you can call setup before makeDecorator.
https://github.com/NickMcBurney/storybook-vue3-router/blob/b8ecc62347368b0066ad88b28081e5b158086be7/src/withVueRouter.ts#L42
) =>
  let app: App;
  setup((setupApp) => {
    app = setupApp
  })
  makeDecorator({
    name: 'withVueRouter',
    parameterName: 'withVueRouter',

    wrapper: (storyFn: StoryFn, context: StoryContext) => {
      /* setup router var */
      let router

Thanks @tfoxy, I'll give this a go

Hi @NickMcBurney ! I realized that the previous decorator isn't working properly when changing values in the controls. I fixed it by calling app.use inside decorator setup:
import { Decorator, setup } from '@storybook/vue3'
import { App } from 'vue'
import { RouterOptions, createRouter, createWebHashHistory } from 'vue-router'

const Home = { template: '
Home
' }
const About = { template: '
About
' }

export const routerOptions: RouterOptions = {
  history: createWebHashHistory(),
  routes: [
    { path: '/', name: 'home', component: Home },
    { path: '/about', name: 'about', component: About },
  ],
}

export default function withRouter(options?: RouterOptions): Decorator {
  let app: App

  setup((setupApp) => {
    app = setupApp
  })

  return () => {
    return {
      setup() {
        const router = createRouter({ ...routerOptions, ...options })
        app.use(router)
      },
      template: '<story/>',
    }
  }
}

The fix works perfectly. Thanks!!
I updated the file to match the library interface and use the library when the fix is ready again.
import { Decorator, setup } from '@storybook/vue3'
import { App } from 'vue'
import { RouteRecordRaw, RouterOptions, createRouter, createWebHashHistory } from 'vue-router'

const Home = { template: '
Home
' }
const About = { template: '
About
' }

export const routerOptions: RouterOptions = {
  history: createWebHashHistory(),
  routes: [
    { path: '/', name: 'home', component: Home },
    { path: '/about', name: 'about', component: About }
  ]
}

export function vueRouter (routes?: RouteRecordRaw[]): Decorator {
  let app: App

  setup((setupApp) => {
    app = setupApp
  })

  return () => ({
    setup () {
      const router = createRouter({ ...routerOptions, routes: routes || routerOptions.routes })
      app.use(router)
    },
    template: '<story/>'
  })
}

@jamesalways We are running into the same issue and I'd like to resolve this issue for my team. Where/How can we apply the fix you mentioned above?

@jamesalways We are running into the same issue and I'd like to resolve this issue for my team. Where/How can we apply the fix you mentioned above?

@JoepRoggekamp

Create a file with the previous code wherever you want.
In the story, import and use it like this:

import { vueRouter } from 'yourPathToTheFile'

StoryName.decorators = [
  vueRouter() or   vueRouter([...routes])
]

FYI I closed then I merged fix, but auto publish script didnt work so I still need to resolve that. Should have this sorted this evening though and ill confirm version here.

Issue resolved and packaged publish: 4.0.1

Out of curiosity, has anyone run into this same issue while using autodocs? Individually each story pages appear to render without issue.

Out of curiosity, has anyone run into this same issue while using autodocs when you have multiple stories? Individually each story pages appear to render without issue.

Yeah this issue is happening for us on the docs page, not for individual stories

@dlferro  - Yes, I have run into this issue on the docs page for a component when it has multiple stories. One of the stories renders correctly, but all the others trigger errors as describe above.
I think this issue should be reopened.
Unfortunately I'm a newcomer to Storybook and haven't yet been able to identify a fix.

Hey @zejji
in this case, i think it's because the vue-router is set up multiple times.
So if you use the code shown previously, you can add a condition to use the vue-router like so :
  return () => ({
    setup() {
      if (app._context.components['RouterLink'] === undefined) {
        const router = createRouter({ ...routerOptions, routes: routes || routerOptions.routes })
        app.use(router)
      }
    },
    template: '<story/>',
  })

Hey @dlferro @zejji @pa-bouly I created #56 to fix this issue. Let me know if it works for you so that it can be merged without causing any other issue.

Thanks @tfoxy, I've tested, merged PR and published new version.
My Release Pipeline all messed up so managed to publish version 4.1.0 (initial version with fix) all the way to 4.25.0, and I can unpublish duplicate versions due to some package have this listed as a dependancy - with some very loose version requirement which means all versions are considered a dependency and blocked from unpublishing.


Fix modexp precompile output type

Codecov Report

Merging #98 (fd1e09e) into main (39f010b) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main      #98   +/-   ##
=======================================
  Coverage   83.02%   83.02%
=======================================
  Files          13       13
  Lines        3170     3170
=======================================
  Hits         2632     2632
  Misses        538      538

Files Changed
Coverage Δ

src/zks_utils.rs
31.03% <0.00%> (ø)

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


change bar width dynamically according to data

Hi,
is there any options to change width and seriesBarDistance dynamically? look at pic there is only one set of series. I want it to occupy  all chart width and increase Bar width

its my 4th issue on chartist, not a single comment any of them? thats bad @gionkunz

@Zaid-Mirza I didn't had a lot of time to work on Chartist lately but I'm just in the process of cleanup up the backlog and pick up my work on the library again so sorry for that.
Nevertheless I need to post my standard answer for this type of issue :-/

Please use http://stackoverflow.com/ for these kind of questions, we should only track bugs, feature requests or questions on internals within this Github repository.

Btw. you should use the distributeSeries option for this use-case https://gionkunz.github.io/chartist-js/examples.html#example-bar-distributed-series

@gionkunz sorry for late response, I was expecting feature which can increase/dcrease bar width according to number of data bars on Chart

Sorry I never replied to this, please re-open if still needed

Btw, for anyone else looking for a solution - I found a fiddle that addresses this https://jsfiddle.net/traviss0/gg1oj35x/
Setting the stroke width to the step length, or a fraction of the step length, in the created event seems to be a decent way.

the above jsfiddle link isn't working.
I figured out a way to do it with a similar idea.
var chart = new Chartist.Bar('.ct-chart', data, options);

        var yOffset = chart.options.axisY.offset;
        var chartWidth = chart.container.clientWidth;
        var xWidth = chartWidth - yOffset;
        var stepLength = xWidth / 3; // Replace 3 with the length of the series

        chart.on('draw', function (data) {
            if (data.type == 'bar') {
                data.element._node.style.strokeWidth = stepLength * 2 / 5;
            }
        });


decode utf8 error

Env:x64 win7, python3.6.2
I used 'sqlitebiter file test.json -o test.sqlite', the test.json is encoded as utf-8 without bom, but I get the following error:
[ERROR] sqlitebiter file: invalid json data format: path=test.json, message='gbk' codec can't decode byte 0xa6 in position 336: illegal multibyte sequence

Thank you for your report.
Could you possibly provide me the problematic JSON data?
I've tried to reproduce the problem with UTF-8 (without BOM) JSON file,
but I couldn't (sqlitebiter completed without errors).

I'm sorry that now I can't use my pc.
That json has many chinese words, you can write a simple json to test it, such as:
'''json
{
"sites": [
{ "name":"菜鸟教程" , "url":"m.runoob.com" },
{ "name":"google" , "url":"www.google.com" },
{ "name":"微博" , "url":"www.weibo.com" }
]
}
'''
The reason may be sqlitebiter read the json as gbk codec, although that json is utf8.

The following method can get the original json:

git clone this: https://github.com/Binaryify/NeteaseCloudMusicApi
cd the path and node app.js (nodejs 6.0+)
save the json from this address: http://localhost:3000/playlist/detail?id=612879229

debug info:
[DEBUG] sqlitebiter file: converting 'test.json'
[DEBUG] pytablereader: TableFileLoaderFactory.create_from_path: extension=json
[DEBUG] pytablereader: loading file: format=json, path=test.json, encoding=utf-8

[ERROR] sqlitebiter file: invalid json data format: path=test.json, message='gbk' codec can't decode byte 0xa6 in position 336: illegal multibyte sequence
[DEBUG] sqlitebiter file: ----- sqlitebiter completed -----
[DEBUG] sqlitebiter file: database path: test.sqlite
[DEBUG] sqlitebiter file: number of created table: 0
[DEBUG] sqlitebiter file:
[DEBUG] sqlitebiter file: ----- database schema -----
[DEBUG] SimpleSQLie: connect to a SQLite database: path='test.sqlite', mode=r
[DEBUG] SimpleSQLie: close connection to a SQLite database: path='G:\test.sqlite'
[DEBUG] sqlitebiter file:
[DEBUG] SimpleSQLie: close connection to a SQLite database: path='G:\test.sqlite'

original json:
test.zip

Thank you for your additional information.
I could reproduce the problem.
It looks like there are two problems, encoding and JSON format:
Problems
1. encoding
sqlitebiter not properly opening for utf8 input files some formats (include JSON files).
This cause an encoding error at Windows environment.
2. JSON file format
Original JSON file (test.json) that you mentioned in the previous comment is not convertible as it is by sqlitebiter.
Convertible JSON formats for sqlitebiter are very limited for now (details are described in here).
Solution
1. encoding
I've fix a dependency package that loading files.
Please try upgrade the sqlitebiter dependency packages with pip install sqlitebiter --upgrade.
You could convert utf8 files properly.
>type utf.json
{
"sites": [
{ "name":"闖憺ｸ滓蕗遞・ , "url":"m.runoob.com" },
{ "name":"google" , "url":"www.google.com" },
{ "name":"蠕ｮ蜊・ , "url":"www.weibo.com" }
]
}
>sqlitebiter file utf.json
[INFO] sqlitebiter file: convert 'utf.json' to 'sites' table

>sqlite3 out.sqlite
sqlite> .schema
CREATE TABLE IF NOT EXISTS 'sites' (name TEXT, url TEXT);

2. JSON file format
You could extract convertible JSON data by jq command from the JSON, and convert it by sqlitebiter.
If you have a certain database schema that you would like to extract from the JSON file.

Thank you for your reply!


/odom calculation setup inside the create 3 robot

Hello,
Is the filtering method for calculating the odometer of the robot and fusing all the sensor data available as a paper or a code-base? I want to design my own odometer and I was wondering if the original math is available so I can compare my work to it.
Sorry for reporting this as an issue, this is not the ideal place to discuss this, but I was refereed here by the IRobot Educational support team.

Hi there,
Agreed on location -- this is not a sim issue. A more appropriate place for this would be in the docs discussions forum, where there is more general conversation about the Create 3 robot.
The fused odometry algorithm in the Create 3 robot is, to my knowledge, not published.
I will try to convert this to a discussion; if I fail, I will close this and you are welcome to open a new discussion at the link above.


Moondream for Object Localization

I am wondering if Moondream can be used for grounding tasks such Object Localization? Something similar to what cogagent does with GUI but I would like to train on my custom dataset. If I fine-tune moondream on my custom dataset of images - bounding boxes + text is there a chance it would work?

Yes - the current version of moondream can detect one object per image. If you query with Bounding box: {object} it will return an array of 4 floating point numbers that indicate the relative (x1, y1) and (x2, y2) positions for the top-left and bottom-right corners. The next release will add support for multiple objects and may also change the output format. I'll post an update here when it's out.

Yes - the current version of moondream can detect one object per image. If you query with Bounding box: {object} it will return an array of 4 floating point numbers that indicate the relative (x1, y1) and (x2, y2) positions for the top-left and bottom-right corners. The next release will add support for multiple objects and may also change the output format. I'll post an update here when it's out.

what if i have a dataset of images + actions i.e.
{"x1": 420, "x2": 378, "y1": 1042, "y2": 245, "action": "swipe", "duration": 200}
would it be able to predict such actions if i train it on my dataset?
Is it possible to predict a next action for a sequence of images + actions? If not, what if I create a collage image of previous images + actions. Would it be able to learn such a task?

While making dataset for fine tuning what is the format in which we have to give the co ordinates, and are you using another regression loss or is it completely the text decoder model giving the co ordinates as string.

While making dataset for fine tuning what is the format in which we have to give the co ordinates, and are you using another regression loss or is it completely the text decoder model giving the co ordinates as string.

I have the same question.


Support for watching configmap changes

Description
This PR is to add changes to monitor a config file in /etc/config/karavi-metrics-powerflex.yaml, which contains parameters that can be modified while running the karavi-metrics-powerflex service:
COLLECTOR_ADDR:
PROVISIONER_NAMES
POWERFLEX_SDC_METRICS_ENABLED
POWERFLEX_SDC_IO_POLL_FREQUENCY
POWERFLEX_VOLUME_IO_POLL_FREQUENCY
POWERFLEX_VOLUME_METRICS_ENABLED
POWERFLEX_STORAGE_POOL_METRICS_ENABLED
POWERFLEX_STORAGE_POOL_POLL_FREQUENCY
POWERFLEX_MAX_CONCURRENT_QUERIES

All other options that are setup during install that cannot be changed without restarting the service will be stored as environment variables.
Issues
List the issues impacted by this PR:

Issue ID

dell/karavi-observability/#25

Checklist:

[x] I have performed a self-review of my own code
[x] I have run 'make check' to ensure my code does not have any formatting, vetting, linting, or security issues
[x] I have run 'make test' to ensure new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degrade
[x] I have maintained at least 90% code coverage
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ x ] Deployed updated code with corresponding helm chart changes. Updated the ConfigMap values on the k8s cluster, and checked logs for new updated polling flags and frequencies.

@sharmilarama: Thank you for submitting your pull request!
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at<EMAIL_ADDRESS>

I have made a review. I see no edits that are necessary.

e2e

Run e2e test

I have reviewed this and there are no edits required.

run e2e

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test


RollupError when having sitemap enabled and robots disabled

Describe the bug
I noticed that when using nuxt/seo (version 2.0.0-rc12 in my case) you get a rollup error when disabling robots while still having sitemap enabled.
I would not know of a use case where you dont want to combine them, but it would perhaps be good to specify it in the documentation that you need have robots enabled when using sitemap.
`[nitro 20:26:57]  ERROR  RollupError<EMAIL_ADDRESS>(3:9): "getPathRobotConfig" is not exported by "virtual:#imports", imported by<EMAIL_ADDRESS>

1: import { parseURL } from "ufo";
2: import { createFilter } from "../../../utils-pure.js";
3: import { getPathRobotConfig } from "#imports";
            ^
4: export function filterSitemapUrls(_urls, options) {
5:   const urlFilter = createFilter({`

Reproduction
No response
System / Nuxt Info
No response

Thanks, this will be supported in the next Nuxt SEO release. When a module is disabled we add a mock version of it so you can safely disable any module without breaking any composable usages.

This should be solved with the @nuxtjs/robots v4 release.


chore(variables): move global css variables out of patternfly-utilities and into patternfly-base

fix https://github.com/patternfly/patternfly-next/issues/612

Deploy preview for pf-next ready!
Built with commit 417f7e9a6001941581d3cdc993a4d110863c1f15
https://deploy-preview-639--pf-next.netlify.com

@andresgalante took a stab at this. Let me know if this isn't what you had in mind and I'm happy to keep working on it.

yes, this is what I had in mind. Thanks a lot @michael-coker
@dgutride @dmiller9911 if you guys are ok with it, we can merge it

:tada: This PR is included in version 1.0.29 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add function to MessageReceiver abi to allow contracts to report what optional outputs they want

The MessageReceiver should have a function (maybe called fn requested_outputs() -> str[512]) that allows a contract to state what optional outputs they want to fully process a message. This would be used by an automated relayer service to better construct relaying transactions.

This is now an outdated concept. The new thinking is that there will be multiple predicates created if a large need arises for messages that interact with multiple contracts.